Ticket #1646 (new defect)

Opened 3 years ago

Last modified 3 years ago

No way to force-close (kill) an activity

Reported by: sascha_silbe Owned by: tomeu
Priority: Unspecified by Maintainer Milestone: Unspecified by Release Team
Component: sugar Version: Git as of bugdate
Severity: Major Keywords:
Cc: Distribution/OS: Unspecified
Bug Status: New

Description

If an activity has gotten into a state where it doesn't close itself anymore, there's no way for the user to do a clean shutdown (the only option left is forcibly powering off the machine).
Several other UIs are offering to forcibly close an application if it doesn't voluntarily close after a certain amount of time. Another option is offerring the option to kill the application in the regular menu (like e.g. ion3 does), but IMO the first option is better since it's harder to accidently shoot yourself in the foot.

Change History

Changed 3 years ago by sascha_silbe

Oh, just to be clear: While the issue of "no clean shutdown possible" can be solved by simply ignoring activities that refuse to close during shutdown IMO it should not be _necessary_ to do a shutdown just to kill a renegade activity.

Note: See TracTickets for help on using tickets.