Mailinglist Archive: opensuse-bugs (14787 mails)
| < Previous | Next > |
[Bug 219945] New: It's possible to kill sw_single leaving it as a stale process, locking zypp forever
- From: bugzilla_noreply@xxxxxxxxxx
- Date: Fri, 10 Nov 2006 09:50:26 -0700 (MST)
- Message-id: <bug-219945-21960@xxxxxxxxxxxxxxxxxxxxxxxxx/>
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@xxxxxxxxxx
ReportedBy: wstephenson@xxxxxxxxxx
QAContact: jsrain@xxxxxxxxxx
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.
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@xxxxxxxxxx
ReportedBy: wstephenson@xxxxxxxxxx
QAContact: jsrain@xxxxxxxxxx
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.
| < Previous | Next > |