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.