update manager crashed while updating from Gutsy to Heron

[mj]

Binary package hint: update-manager

I updated from Gutsy to Heron beta, and the update manager said it was crashing and that my system would be unstable, something about xorg. I seem to have 8.04 installed just fine, but the error said to report the bug.

ProblemType: Bug
Architecture: i386
Date: Mon Apr 21 02:08:57 2008
DistroRelease: Ubuntu 8.04
Package: update-manager 1:0.87.21
PackageArchitecture: all
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
SourcePackage: update-manager
Uname: Linux 2.6.22-14-generic i686

[Michael Vogt (mvo)]

Thanks for your bugreport.

2008-04-21 01:48:38,074 ERROR got an error from dpkg for pkg: 'xserver-xorg': 'subprocess post-installation script returned error exit status 1
'
2008-04-21 01:48:38,074 DEBUG running apport_pkgfailure() xserver-xorg: subprocess post-installation script returned error exit status 1

This is a bug in the xserver-xorg package, please attach the file /var/log/dist-upgrade/apt-term.log to this bugreport as well to make finding the cause of the problem easier.

Thanks,
 Michael

[mj (matthew-jorden)]

I tried uploading the apt-term.log, and Launchpad says it wont upload an empty file.

[Brian Murray (brian-murray)]

From term.log:

Setting up xserver-xorg (1:7.3+10ubuntu10) ...
No protocol specified
Gtk-WARNING **: cannot open display: :0.0 at /usr/share/perl5/Debconf/FrontEnd/Gnome.pm line 60.
dpkg: error processing xserver-xorg (--configure):
 subprocess post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of xorg:
 xorg depends on xserver-xorg; however:
  Package xserver-xorg is not configured yet.

[Bryce Harrington (bryce)]

Can anyone else reproduce this bug?

Also, whenever reporting X issues, please always attach an Xorg.0.log.

Looking at the attached files, none of them indicate why X failed, just that it was not running as expected. So there is not enough info to troubleshoot this yet. See http://wiki.ubuntu.com/X/Reporting for tips on what types of files to include.

[exogenetic (exogenetic)]

Machine #1 Single, Clean, Recent install of Gutsy --- Upgrade sucessful
Machine #2 Triple boot: Window/Gutsy/Hardy Beta--- Total Crash

Machine #1 (logs will be attached in next comment) Upgrade from Gutsy to Hardy Beta. Went fine with one odd error. Noted error message dealing with X followed by another message saying it was not a fatal error, distribution upgrade in progress. The machine briefly threw me back into the login screen before restarting.

Machine#2 (logs attached) I thought I'd repeat the bug and succeeded. I have a lot of developer software on it. I was trying out compilers to learn the basics of C. I am not a developer. Many errors and messages dealing with KDE. Kdevelop installed.

I was able to retrieve the logs because I upgraded the Gutsy partition, which I'm calling a loss. Attached is what I retrieved from the third partition which still runs Hardy just fine.

The compressed file attached includes the Xorg configuration and logs both before and after the aborted install.
I retrieved the everything concerning APT that I could.

[mj (matthew-jorden)]

I used the upgrade manager to download some reccomended updates to Heron, and now my sound and internet aren't working, so I can't post the xorg log file you asked for. Sorry!

I think I'm gonna go back to Gutsy for a week or two then try Heron again. Looks nice from the screenshots, just doesn't seem to be ready for my Thinkpad T42 laptop for some reason. Thanks to everyone in the Ubuntu community, its a great OS, I think I'm just to much of a newb to try out release candidates.

[exogenetic (exogenetic)]

This is from machine #1
The logs show a lot of broken dependencies dealing with X11.

I hope you find this helpful. Files are prefixed with Gutsy and Hardy, as I copied many of them before and after the upgrade.

[exogenetic (exogenetic)]

In my first comment the attachment "Configuration logs from crashed system"

The logs came from the crashed partition. I may not have mad that clear.
They are prefixed "Before" and "After" for logs I knew to copy before attempting the aborted upgrade.

[exogenetic (exogenetic)]

I reinstalled Gutsy on partition #2 of machine #2
Machine #2 is:
Dell D610 refer to "Configuation logs from crashed system" for lspci -vvnn, configuration, etc.

I left partition #2 of machine #2 in the default Gutsy configuration and upgraded to Hardy today without problem.

I do modify my xorg.conf file because my touchpad is too sluggish.
This is the mod:
        Option "MinSpeed" "1"

Here is the appropriate section of the xorg.conf file:

Section "InputDevice"
 Identifier "Synaptics Touchpad"
 Driver "synaptics"
 Option "SendCoreEvents" "true"
 Option "Device" "/dev/psaux"
 Option "Protocol" "auto-dev"
 Option "HorizEdgeScroll" "0"
        Option "MinSpeed" "1"

This mod was applied to the old partition #2 before the aborted upgrade.
It was applied to the new partition #2 after installing Hardy this time.

I included this in case it might be relevant.

I filed a typical Hardware Testing report that notes the need for this mod.

[Steve Langasek (vorlon)]

Martin,

This bug was filed about a crash in the xserver-xorg postinst script during upgrade. I don't see any evidence in your comments that the problem you experienced is at all related to this - you seem to be reporting an X crash, which is not what happened to mj? Please file a separate bug report for your issue.

[Steve Langasek (vorlon)]

Bryce, it seems unlikely that X would have not been running here, after all update-manager is an X application. The real problem is that the xserver-xorg postinst is failing for an unknown reason.

mj, it seems we really do need your continued help to be able to track this bug; many people have run the RC (and now the release) without encountering this failure, including many Thinkpad users. Is there a chance that you can try upgrading again to find out whether the bug is reproducible?

[exogenetic (exogenetic)]

Nautilus did not completely load because of update manager crash. I did receive same error messages as the Thinkpad. Tried to reproduce my bug twice to no effect. Will repost if I see something similar.
Will try to read more carefully and use Apport outside of system crash.
Thank you for the work you do. It is appreciated.

[mj (matthew-jorden)]

I have since upgraded to the 'final' Hardy Heron release, and I had no trouble at all, no error messages. I don't have any of the files or logs or anything saved from the RC when I ran into the bug.

How can I help with this bug? Would it be useful is I tried to reinstall Heron and see if the bug happens again?

The video drivers for my card always seem to be a little buggy (ATI radeon mobility, I forget the model but its not supported by fglrx), could that be the problem with Xorg? Everything is running great now, 8.04 seems to be a really awesome product.

[Bryce Harrington (bryce)]

Steve, no I meant that X is *supposed* to be running but for some unknown reason crashes, and the stuff that expected X to be running notice that it ain't, and issue errors to that effect. *Why* X crashed or stopped running is the real question here.

@Martin, thanks for the attaching all the logs, which I've gone through in review. However the most needed one - the one from the partition that crashed, I gather you didn't collect? The logs you've shown so far don't show a crash, and like Slangasek I suspect you may have an unrelated issue that should be filed separately.

@mj, I'm glad to hear your issue has resolved with the latest Hardy. Since that worked, your prior attempt may have been something spurious. It would indeed be helpful if you could see if the issue is reproducible in another upgrade. Otherwise, if no one else reproduces the issue definitively either, this probably doesn't need to be milestoned.

[Bryce Harrington (bryce)]

Here is the log from term.log around the point of failure:

Setting up xserver-xorg-video-all (1:7.3+10ubuntu10) ...
Setting up xorg-driver-fglrx (1:7.1.0-8-3+2.6.24.12-16.34) ...
 * Starting atieventsd
   ...done.
Setting up xserver-xorg (1:7.3+10ubuntu10) ...
No protocol specified
Gtk-WARNING **: cannot open display: :0.0 at /usr/share/perl5/Debconf/FrontEnd/Gnome.pm line 60.
dpkg: error processing xserver-xorg (--configure):
 subprocess post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of xorg:
 xorg depends on xserver-xorg; however:
  Package xserver-xorg is not configured yet.
dpkg: error processing xorg (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of ubuntu-desktop:
 ubuntu-desktop depends on xorg; however:
  Package xorg is not configured yet.
dpkg: error processing ubuntu-desktop (--configure):
 dependency problems - leaving unconfigured
Setting up language-pack-en (1:8.04+20080415) ...

Slangasek might be right that X isn't crashed, but from the several errors about it not being accessible at :0.0, it's at least not running in a fashion that other things expect. It would be handy to have the Xorg.0.log and maybe /etc/X11/xorg.conf to check how X is configured.

I notice in the above that atieventsd is being started right prior to xserver-xorg being configured. One hypothesis is that perhaps this (or some other step in the -fglrx config) resulted in changes that confused the subsequent xserver-xorg configuration step.

[Steve Langasek (vorlon)]

This may be attributable to atieventsd; whatever it is, it seems to be unreproducible now including for the original submitter, so I'm dropping the 8.04.1 milestone from the bug - we can reconsider it for .1 if we get some traction on reproducing/debugging, or if we get more reports of the same bug to suggest it's more than a one-off experience.

[Bryce Harrington (bryce)]

This is sounding a lot like #194249, for which there were a LOT of reports during Hardy, and that got resolved late in the release. I'm going to dupe this to it based on that assumption; please un-dupe if the issue re-appears.