https://bugzilla.novell.com/show_bug.cgi?id=307364 Andreas Jaeger changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.provo.novell.com |yast2-maintainers@suse.de -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=307364#c2 Stefan Hundhammer changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |bluedzins@wp.pl --- Comment #2 from Stefan Hundhammer 2007-09-05 03:46:52 MST --- If I understand you correctly, you pressed your machine's "power off" button. Is that correct? AFAIK that "power off" button is translated into DBUS events that ultimately are sent to the desktop that in turn translate this event into a "session end" event like described above. Which desktop are you using? Did the system finally shut down (despite the complaint) or not? One way or the other, "power off" is NOT the method of choice if something goes wrong on a Linux system. MS Windows users got used to rebooting if anything looks suspicious, but this is a bad approach for a Linux system. On Linux, you can get control of applications that do something you don't want in various ways: On the command line, use the "kill" command with the process ID (PID) and a signal number. If you don't know the PID (which is the normal case), you can find it out with the "ps" command. Alternatively, you can use the "killall" command which kills all processes with a given name: killall -9 y2base sends a signal #9 (SIGKILL) to all "y2base" processes (y2base is the YaST2 binary). On KDE, there is also "ksysguard" that does the same as "ps" and "kill" with a nice GUI. KDE also has the "kill cursor": Press Ctrl-Alt-Esc, and the mouse cursor turns into a skull and crossed bones. The application you click on with that cursor will die a SIGKILL death. BTW since YaST2 is running as "root" (with superuser privileges), you need root privileges to kill it, of course. So in the case of YaST2, you have to use something like sudo killall -9 y2base which ultimately is also the reason why a desktop session running as non-root cannot simply kill a running YaST2 process. Did you try to terminate it with "root" privileges? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=307364#c4 Maciej Pilichowski changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|bluedzins@wp.pl | --- Comment #4 from Maciej Pilichowski 2007-09-05 05:09:33 MST --- Stefan, thank you very much for such explanation. I'll try to answer your questions step by step, but maybe at first once again the situation. I was surprised by ETA the SM gave me -- during installation SM is not responding to user action (try "abort") so I was hoping I press power off (it is soft power off button, not power cut off like in older desktop) and SM will notice it and just install the current package and leave the rest. It didn't happen. You know, when the software is not responding, what can you do? Btw. it would be really nice to see some emergency abort feature (skip the current and the rest) and emergency rollback (skip current + rest, but rollback all installed in current session).

AFAIK that "power off" button is translated into DBUS events that ultimately are sent to the desktop that in turn translate this event into a "session end" event like described above.

AFAIK -- yes.

Which desktop are you using?

KDE.

Did the system finally shut down (despite the complaint) or not?

Well, after I killed all yast (killall ...) from root, yes, I was able to shut it down.

One way or the other, "power off" is NOT the method of choice if something goes wrong on a Linux system.

I am not taking about unplugging it, power off button is a normal and convenient way to shutdown the system. It works exactly the same if I press ctrl+alt+del and choose "shutdown". And about going wrong -- what choice did I have, if I am missing something please let me know (waiting ~12 hours is not acceptable for me).

KDE also has the "kill cursor":

THANK YOU!

Did you try to terminate it with "root" privileges?

Sure it worked. But it is a brute force method of interruption. Program does not have chance (ok, it has a bit, it could intercept this signal, but it is really low level). Note, that it is more useful to get signal in Qt level about power-off button press and manage aborting program in GUI mode -- in nice, user-friendly manner. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=307364 J. Daniel Schmidt changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jdsn@novell.com AssignedTo|yast2-maintainers@suse.de |sh@novell.com Severity|Major |Enhancement -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=307364#c7 --- Comment #7 from Stefan Hundhammer 2007-09-05 08:39:25 MST --- (In reply to comment #4 from Maciej Pilichowski)

Btw. it would be really nice to see some emergency abort feature (skip the current and the rest) and emergency rollback (skip current + rest, but rollback all installed in current session).

I am afraid rollback is very much out of reach (albeit often requested to uninstall patches, for example): There is no reliable way to undo whatever any of those pre-install or post-install (or pre-uninstall / post-uninstall) scripts did. This is a problem of how RPM works in principle.

...

One way or the other, "power off" is NOT the method of choice if something goes wrong on a Linux system.

I am not taking about unplugging it, power off button is a normal and convenient way to shutdown the system. It works exactly the same if I press ctrl+alt+del and choose "shutdown".

Right. Which is yet another not-method-of-choice to fix problems under Linux. ;-)

And about going wrong -- what choice did I have, if I am missing something please let me know (waiting ~12 hours is not acceptable for me).

The time estimate is just that: An estimate. If your connection is very slow but then becomes quicker after a while, the initial estimate may be way off. There is no real way to predict how long a package download and installation will take, yet it was requested so often that we were forced to implement something that really is completely bogus: We wait for a while (1 min) and watch the data transfer rate during this time and then extrapolate that to the remaining packages. This of course assumes that the transfer rate will remain the same, which may or may not be the case. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.