[Bug 219945] New: It's possible to kill sw_single leaving it as a stale process, locking zypp forever
https://bugzilla.novell.com/show_bug.cgi?id=219945 Summary: It's possible to kill sw_single leaving it as a stale process, locking zypp forever Product: openSUSE 10.2 Version: Beta 2 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: sh@novell.com ReportedBy: wstephenson@novell.com QAContact: jsrain@novell.com This is a bug which a stupid impatient user would see: 1) Start sw_single 2) Decide you wanted inst_source instead and click Abort at bottom of the window ASAP. 3) You get a strange error message "could not access installation media 20062032-134656 CD1" as a result of clicking Abort - bug? 4) Click abort on that and every other error message that comes up 5) I get another error message "There was an error in installation source initialization. http://foo/bar: Cannot create the installation source. OK that. 6) Now sw_single is busy (y2log: Parsing filelist from ..../filelists.xml.gz ) but no UI feedback is given. Duncan says a callback is not used at this point that should be. This seems to continue indefinitely (BUG). 7) Get frustrated and ctrl-alt-esc sw_single's window - which closes. 8) Now both yast2 sw_single and sw_single qt are stale, state S and Sl respectively (BUG). As a result the zypp db has a valid lock on it as the process is still there, and any other package operations are locked, so the naive user has to reboot. My ideas: 1) React appropriately when the user clicks the Abort button 2) Show the 'parsing' feedback, or abort if this cannot succeed due to the user previously shooting all the install sources down while trying to abort. 3) End the processes cleanly when the window is xkilled. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=219945 ------- Comment #1 from wstephenson@novell.com 2006-11-10 09:54 MST ------- Created an attachment (id=104712) --> (https://bugzilla.novell.com/attachment.cgi?id=104712&action=view) yast2 log -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=219945 sh@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|sh@novell.com |lslezak@novell.com ------- Comment #2 from sh@novell.com 2006-11-13 05:31 MST ------- Whatever Ctrl-Alt-Esc does, it does not seem to be the right thing. If it only kills one of the two threads of this process, the other one will hang around in an undefined state. Sometimes it might get a SIGPIPE, but depending on its internal status it might as well not. The valid part of this report is handling the "Abort" button. This seems to have a problem - either on the callback side (YCP packager) or (less likely) on the libzypp side. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=219945 lslezak@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- Comment #3 from lslezak@novell.com 2006-11-13 05:56 MST ------- The bug seems to be in the callback handling side (packager or bindings). -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=219945 ------- Comment #4 from lslezak@novell.com 2006-11-24 08:13 MST ------- I think the problem is in the YCP handlers, there is [Abort} check, but the popup with progress bar doesn't have any [Abort] button, the `abort event is from the main dialog. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=219945 lslezak@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mludvig@logix.net.nz ------- Comment #5 from lslezak@novell.com 2007-06-06 08:44 MST ------- *** Bug 229466 has been marked as a duplicate of this bug. *** -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=219945 User lslezak@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=219945#c6 Ladislav Slezak <lslezak@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #6 from Ladislav Slezak <lslezak@novell.com> 2008-03-06 02:06:52 MST --- The callbacks are reimplemented in 11.0 - the callbacks use the main dialog window (no popups) and there is [Abort] button. So suppose the problem is fixed. -- 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.
participants (1)
-
bugzilla_noreply＠novell.com