[Bug 373158] New: cancellation of online update does not work correctly
https://bugzilla.novell.com/show_bug.cgi?id=373158 Summary: cancellation of online update does not work correctly Product: openSUSE 10.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: estellnb@gmail.com QAContact: jsrain@novell.com Found By: Community of Practice Yast2-Online-Update: click on cancel user has to wait very long until update window vanishes afterwards sw-install can not be run because online_update process is still running unterminated in the background:
ps ax|gi "yast|sw_single" 15998 pts/4 S 0:00 /bin/bash /sbin/YaST2 16021 pts/4 S 0:02 /usr/lib/YaST2/bin/y2controlcenter 19124 pts/4 S 0:00 /bin/bash /sbin/yast2 online_update 19148 pts/4 Sl 8:39 /usr/lib/YaST2/bin/y2base online_update qt 19235 pts/4 S 0:00 /bin/bash /sbin/yast2 sw_single 19259 pts/4 Sl 0:01 /usr/lib/YaST2/bin/y2base sw_single qt 19289 pts/5 R+ 0:00 egrep -i --color yast|sw_single kill 19124 kill 19148 Nevertheless locks are released correctly by kills so that user can proceed.
-- 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=373158
Cyril Hrubis
https://bugzilla.novell.com/show_bug.cgi?id=373158
User jsuchome@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=373158#c1
Jiří Suchomel
https://bugzilla.novell.com/show_bug.cgi?id=373158
User estellnb@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=373158#c2
--- Comment #2 from Elmar Stellnberger (AT/K)
https://bugzilla.novell.com/show_bug.cgi?id=373158
User estellnb@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=373158#c3
Elmar Stellnberger (AT/K)
https://bugzilla.novell.com/show_bug.cgi?id=373158
User jsuchome@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=373158#c4
Jiří Suchomel
https://bugzilla.novell.com/show_bug.cgi?id=373158
User estellnb@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=373158#c5
Elmar Stellnberger (AT/K)
https://bugzilla.novell.com/show_bug.cgi?id=373158
User jsuchome@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=373158#c6
Jiří Suchomel
https://bugzilla.novell.com/show_bug.cgi?id=373158
User jsuchome@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=373158#c7
Jiří Suchomel
https://bugzilla.novell.com/show_bug.cgi?id=373158
User estellnb@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=373158#c8
Elmar Stellnberger (AT/K)
https://bugzilla.novell.com/show_bug.cgi?id=373158
User estellnb@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=373158#c9
--- Comment #9 from Elmar Stellnberger (AT/K)
https://bugzilla.novell.com/show_bug.cgi?id=373158
User jsuchome@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=373158#c10
Jiří Suchomel
https://bugzilla.novell.com/show_bug.cgi?id=373158
User estellnb@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=373158#c11
--- Comment #11 from Elmar Stellnberger (AT/K)
https://bugzilla.novell.com/show_bug.cgi?id=373158
User jsuchome@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=373158#c12
--- Comment #12 from Jiří Suchomel
Abort button not functional.
I guess this is true, but this is currently not our problem.
window close: processes are apparently left over. ** Try it once and you know it **
Do you think I closed the bug as WORKSFORME without trying it? So, again: closing the window works correctly for me. That doesn't mean there is not a bug, I think the important part may be at which time the window is closed (I also tried to ask you for that). To get additional information, I asked for full /var/log/YaST2/ directory.(In reply to comment #11 from Elmar Stellnberger (AT/K)) -- 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=373158
User estellnb@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=373158#c13
Elmar Stellnberger (AT/K)
https://bugzilla.novell.com/show_bug.cgi?id=373158
User jsuchome@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=373158#c14
Jiří Suchomel
Please do not ask me for anything you can reproduce and test on your own, ...
See previous comments: I _cannot_ reproduce your problem.
since my resources are very limited by the time.
The only think I'm asking you for is the whole directory with YaST log files. That's no extra work, you already have it on your system. Use "save_y2logs" command for it, as described in http://en.opensuse.org/Bugs/YaST#Attachments_-_y2logs.2C_hwinfo_etc. -- 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=373158
User jsuchome@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=373158#c15
--- Comment #15 from Jiří Suchomel
https://bugzilla.novell.com/show_bug.cgi?id=373158
User estellnb@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=373158#c16
--- Comment #16 from Elmar Stellnberger (AT/K)
https://bugzilla.novell.com/show_bug.cgi?id=373158
User estellnb@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=373158#c17
Elmar Stellnberger (AT/K)
https://bugzilla.novell.com/show_bug.cgi?id=373158
User jsuchome@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=373158#c18
Jiří Suchomel
https://bugzilla.novell.com/show_bug.cgi?id=373158
User sh@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=373158#c19
Stefan Hundhammer
https://bugzilla.novell.com/show_bug.cgi?id=373158
User estellnb@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=373158#c20
Elmar Stellnberger (AT/K)
https://bugzilla.novell.com/show_bug.cgi?id=373158
User sh@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=373158#c21
Stefan Hundhammer
What else should it be about;
FACTORY, for example.
we do not have an opensuse-updater in 10.2,
Yes, there is/was.
since the updater of 10.2 is based on rug/zenworks.
From your descriptions I am still not sure if we are talking about the same
..but this is irrelevant anyway. In comment #0, you wrote about the y2base process and y2controlcenter. That's something different from the opensuse-updater. The opensuse-updater is a systray applet that _starts_ the YaST2 sw_single module. /sbin/yast2 is a shell script that ultimately starts a /usr/lib/YaST2/bin/y2base process which contains both the package/patch selector and the YCP interpreter. thing. So let me try to summarize it. You started YaST2 from the shell (/sbin/yast2). Absent any other command line option to start a YaST2 module directly, that /sbin/yast2 script started the Qt-based YaST2 control center (y2controlcenter).
From there, you obviously started the single package selection (y2base sw_single) AND the online update (y2base online_update).
So much I can deduce from the "ps" output you posted. This is where problems must have started. Both the package selector and the online update use libzypp to access the zypp database. One of those processes (the first one started, most likely PID 19148, y2base online_update) must have obtained a lock on the package database. No problem with that one. The second one (most likely PID 19259, y2base sw_single) could NOT obtain a zypp database lock. There must have been pop-up dialogs telling you about that: A first dialog telling you that the package database is locked with a "Continue" and a "Retry" button (no "Cancel"). "Retry" retries obtaining the zypp DB lock, and in that scenario of course will fail again and post the same "Continue"/"Retry" dialog again. Upon "Continue", you get another error dialog with just an "OK" button. Pressing that one will terminate the sw_single module. All that works flawlessly for me. Sometimes there is a short wait (2-3 seconds) until I get the first error dialog, but that is to be expected. I don't even see a "Cancel" button anywhere there. So which button was it you used?
not reproducible? i can hardly believe that.
OF COURSE we try to reproduce that kind of thing when we get a bug report. What do you think we are doing here?
So what can we do about it? Has anyone already had a look at the code?
Frankly, I don't like that tone. -- 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=373158
User estellnb@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=373158#c22
Elmar Stellnberger (AT/K)
https://bugzilla.novell.com/show_bug.cgi?id=373158
User sh@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=373158#c23
Stefan Hundhammer
https://bugzilla.novell.com/show_bug.cgi?id=373158
User sh@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=373158#c24
--- Comment #24 from Stefan Hundhammer
participants (1)
-
bugzilla_noreply@novell.com