[Bug 552721] New: "zypper dup" 11.1 -> 11.2 RC2 kills X11 clients (VMWare?)
http://bugzilla.novell.com/show_bug.cgi?id=552721 Summary: "zypper dup" 11.1 -> 11.2 RC2 kills X11 clients (VMWare?) Classification: openSUSE Product: openSUSE 11.2 Version: RC 2 Platform: i686 OS/Version: openSUSE 11.2 Status: NEW Severity: Major Priority: P5 - None Component: Update Problems AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: haffner@astro.wisc.edu QAContact: jsrain@novell.com Found By: --- User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_6_1; en-us) AppleWebKit/531.9 (KHTML, like Gecko) Version/4.0.3 Safari/531.9 Following http://en.opensuse.org/Upgrade/11.2 with a fairly vanilla, fully up-to-date 11.1 installation (e.g., no non-openSUSE repos), "zypper dup" causes the X session to falter after installing xorg-x11-fonts-core, killing the terminal session that zypper is running in. The X server is not reset nor is much of the low-level gnome session, but all visible clients die, including the desktop and taskbar. I'm left with a blank X session, no windows, and apparent window manager (although metacity did restart around the time of the failure). No errors in Xorg.0.log. xsession-errors reveals the likely reason for why nothing works after the hiccup: gnome-panel: error while loading shared libraries: libgnome-desktop-2.so.7: cannot open shared object file: No such file or directory nautilus: error while loading shared libraries: libeel-2.so.2: cannot open shared object file: No such file or directory Window manager warning: Failed to load theme "Gilouche": Failed to find a valid file for theme Gilouche Not surprisingly, this looks like errors due to some packages not being installed yet. If "zypper dup" is run on a text console or via ssh, the installation continues just fine even though the X session is left in this zombie state. There's no error or warnings that look related to this failure when xorg-x11-fonts-core is being installed, although the post-install SuSEconfig.fonts is run twice, which is odd. I can't test this on a real machine, but it's fully reproducible in my VMware Fusion 3.0 VMs on multiple tries and different computers. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=552721
zhu rensheng
http://bugzilla.novell.com/show_bug.cgi?id=552721
User jkupec@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=552721#c1
Ján Kupec
http://bugzilla.novell.com/show_bug.cgi?id=552721
User sndirsch@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=552721#c2
Stefan Dirsch
http://bugzilla.novell.com/show_bug.cgi?id=552721
User sndirsch@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=552721#c3
--- Comment #3 from Stefan Dirsch
http://bugzilla.novell.com/show_bug.cgi?id=552721
User jkupec@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=552721#c4
--- Comment #4 from Ján Kupec
I suggest to set $YAST_IS_RUNNING" to "instsys" to avoid running these SuSEconfig scripts, but instead run SuSEconfig at the end of the installation. This is what is doing YaST as well - as far as I know. It also saves *a lot* of time.
Could you give this a try and give us feedback whether it helps?
YAST_IS_RUNNING=instsys zypper dup ... SuSEconfig
(this might be worth a try, i just have a comment:) If the script is the cause, won't the X session freeze/crash at the end of installation then? Maybe the crash can't be avoided i don't know. If it can't, we'll need to advise users to run the dist-upgrade from the text terminal, not from X. If it can be fixed, then it should work also without 'YAST_IS_RUNNING=instsys', since it's supposed to work also with plain 'rpm'. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=552721
User jkupec@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=552721#c5
--- Comment #5 from Ján Kupec
BTW, if the issue would be really related to this package you would be able to reproduce it by running
zypper up xorg-x11-fonts-core
even with rpm -U ...; zypper up and dup use the same rpm command to update the package.
which you probably can't.
Matt? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=552721
User sndirsch@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=552721#c6
--- Comment #6 from Stefan Dirsch
If the script is the cause, won't the X session freeze/crash at the end of installation then?
Could be, but better at the end of the installation than in between. ;-)
Maybe the crash can't be avoided i don't know. If it can't, we'll need to advise users to run the dist-upgrade from the text terminal, not from X.
Sure. BTW I always run such an upgrade in screen. So I still have control via ssh if I lose my display completely. :-)
If it can be fixed, then it should work also without 'YAST_IS_RUNNING=instsys', since it's supposed to work also with plain 'rpm'.
I believe we would see the same issues if we would use what you're calling plain 'rpm'. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=552721
Stefan Dirsch
http://bugzilla.novell.com/show_bug.cgi?id=552721
User haffner@astro.wisc.edu added comment
http://bugzilla.novell.com/show_bug.cgi?id=552721#c7
--- Comment #7 from Matt Haffner
http://bugzilla.novell.com/show_bug.cgi?id=552721
User haffner@astro.wisc.edu added comment
http://bugzilla.novell.com/show_bug.cgi?id=552721#c8
Matt Haffner
http://bugzilla.novell.com/show_bug.cgi?id=552721
User sndirsch@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=552721#c9
--- Comment #9 from Stefan Dirsch
A side note, the /var/adm/update-scripts/ in fetchmsttfonts that runs after all packages are installed fires off /usr/sbin/fonts-config explicitly> without using SuSEconfig.fonts or checking YAST_IS_RUNNING...
This is a seperate topic. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=552721
User sndirsch@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=552721#c10
Stefan Dirsch
http://bugzilla.novell.com/show_bug.cgi?id=552721
User haffner@astro.wisc.edu added comment
http://bugzilla.novell.com/show_bug.cgi?id=552721#c11
--- Comment #11 from Matt Haffner
http://bugzilla.novell.com/show_bug.cgi?id=552721
User jkupec@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=552721#c12
Ján Kupec
I'll let one of you more official types decide if this resolves the report or if you want to leave it open to address the underlying problem.
Stefan, please you decide whether to close this as WONTFIX, or whether to dig into it deeper later. Back to you.
One final note for the record: It occurred to me that I hadn't mentioned that I run GNOME and hadn't tried to see if the client deaths happen under KDE.
Probably not. I believe we would get a lot of reports like this otherwise. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=552721
User sndirsch@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=552721#c13
Stefan Dirsch
participants (1)
-
bugzilla_noreply@novell.com