Bug 151991

Summary: kde should have a forceful shutdown policy
Product: [I don't know] kde Reporter: Ritesh Raj Sarraf <kde-bugs>
Component: generalAssignee: Unassigned bugs mailing-list <unassigned-bugs>
Status: RESOLVED NOT A BUG    
Severity: wishlist    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Ritesh Raj Sarraf 2007-11-07 18:37:43 UTC 
Version:            (using KDE Devel)
Installed from:    Compiled sources
OS:                Linux

Have already filed bugzilla #151202 for KDE 3.5.X. Filing a new one for KDE 4.X


See Bug #80091 for some similar information 
 
 Just wanted to put some more input. I think this issue might not be specific to kget, it should be a more generic issue. 
 
 Let's take an example. 
 In klaptopdaemon, I instruct it to hibernate at BAT => 5 mins and shutdown at BAT => 2 mins. 
 
 Currently, if you have a USB disk attached to the laptop, hibernate is aborted because of the USB disk partitions. That's fine. So when it reaches 2 mins, it tries to shutdown. 
 
 At this moment, if I have an editor open with unsaved changes, the shutdown is put on hold because an app is asking for user intervention. This eventually leads to battery drain and the machine is off. 
 
 I think there should be a more general signal, which when sent from kde apps to kde, it should do some default behavior and "Just Shutdown". It should try to apply the best policy in such cases. For example, if a document was in edit mode (and not saved), it should make a copy of it saved temporarily. 
 
 No applications should hold the process of shutdown for KDE.
Comment 1 David Faure 2007-11-07 18:39:51 UTC 
On Wednesday 07 November 2007, Ritesh Raj Sarraf wrote:
> Have already filed bugzilla #151202 for KDE 3.5.X. Filing a new one for KDE 4.X


Oh yeah, what a good idea. We don't have enough open bug reports, let's make copies of the
ones we already have....
Comment 2 Pino Toscano 2007-11-07 18:42:19 UTC 
The current report is bug #151201, FWIW.
Comment 3 Pino Toscano 2007-11-07 18:42:35 UTC 
erm, correct...