attempt to upgrade to saucy failed early with segfault

[Rachel Greenham]

I attempted an only-slightly-premature upgrade to saucy using the usual "update-manager -d" command. It progressed as far as accepting my agreement to its warning that saucy is beta, then crashed out with a segfault. This is what I got at the commandline:

rachel@twilight:~$ update-manager -d
Checking for a new Ubuntu release
authenticate 'saucy.tar.gz' against 'saucy.tar.gz.gpg'
extracting 'saucy.tar.gz'
Segmentation fault (core dumped)

I don't know where that core got dumped, I can't find it; not in my or root's homedir, not in /tmp (including not obviously in /tmp/ubuntu-release-upgrader*; everything else in /tmp too old to be relevant), /var/tmp, /var/crash. If you can tell me where it would have been dumped, in time for it to not get deleted by some automated process, I'll attach it. :-)

In /var/log/syslog:

Oct 7 14:46:22 twilight dbus[943]: [system] Activating service name='org.debian.apt' (using servicehelper)
Oct 7 14:46:22 twilight AptDaemon: INFO: Initializing daemon
Oct 7 14:46:22 twilight dbus[943]: [system] Successfully activated service 'org.debian.apt'
Oct 7 14:46:22 twilight AptDaemon.PackageKit: INFO: Initializing PackageKit compat layer
Oct 7 14:46:22 twilight AptDaemon: INFO: UpdateCache() was called
Oct 7 14:46:22 twilight AptDaemon.Trans: INFO: Queuing transaction /org/debian/apt/transaction/3bc15aa69aa04957989401fe18a6152b
Oct 7 14:46:22 twilight AptDaemon.Worker: INFO: Simulating trans: /org/debian/apt/transaction/3bc15aa69aa04957989401fe18a6152b
Oct 7 14:46:22 twilight AptDaemon.Worker: INFO: Processing transaction /org/debian/apt/transaction/3bc15aa69aa04957989401fe18a6152b
Oct 7 14:46:23 twilight AptDaemon.Worker: INFO: Updating cache
Oct 7 14:46:35 twilight AptDaemon.Worker: INFO: Finished transaction /org/debian/apt/transaction/3bc15aa69aa04957989401fe18a6152b
Oct 7 14:47:36 twilight kernel: [450419.246918] saucy[13491]: segfault at 8 ip 00007ff9aeb8e03f sp 00007fff74322890 error 4 in libGL.so.313.30[7ff9aeae9000+cf000]

Similarly at the end of dmesg output (earlier output from too long ago to be relevant):

[450419.246918] saucy[13491]: segfault at 8 ip 00007ff9aeb8e03f sp 00007fff74322890 error 4 in libGL.so.313.30[7ff9aeae9000+cf000]

As it looks relevant, I have nvidia-313-updates installed:

rachel@twilight:~$ apt-cache policy nvidia-313-updates
nvidia-313-updates:
  Installed: 313.30-0ubuntu1
  Candidate: 313.30-0ubuntu1
  Version table:
 *** 313.30-0ubuntu1 0
        500 http://gb.archive.ubuntu.com/ubuntu/ raring/restricted amd64 Packages
        100 /var/lib/dpkg/status

Some more machine context, as I'm not sure what would have been harvested automatically, or what would be relevant:

GPU is a geForce 210 (GT218); running two 1080p resolution monitors via dvi and hdmi ports. update-manager was being run on the secondary (hdmi-connected) monitor.

Synergy server is running on this machine, its client being another Ubuntu system already upgraded to Saucy (which doesn't have nvidia graphics).

I guess if I wanted to push through with an upgrade immediately I'd instead try it server-style, using do-release-upgrade, but I reckoned as we're close to release, someone might want to have at this one. :-)

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: update-manager 1:0.186.2
ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8
Uname: Linux 3.8.0-31-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.9.2-0ubuntu8.3
Architecture: amd64
Date: Mon Oct 7 14:54:12 2013
GsettingsChanges:
 b'com.ubuntu.update-manager' b'first-run' b'false'
 b'com.ubuntu.update-manager' b'launch-time' b'1381153579'
 b'com.ubuntu.update-manager' b'show-details' b'true'
 b'com.ubuntu.update-manager' b'window-height' b'625'
 b'com.ubuntu.update-manager' b'window-width' b'654'
InstallationDate: Installed on 2013-03-11 (209 days ago)
InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213)
MarkForUpload: True
PackageArchitecture: all
SourcePackage: update-manager
UpgradeStatus: Upgraded to raring on 2013-10-07 (0 days ago)

[Rachel Greenham (rachel-strangenoises)]

btw the line added automatically "UpgradeStatus: Upgraded to raring on 2013-10-07 (0 days ago)" is a lie. I upgraded to raring a couple of months ago i think (Perhaps Aug 24 judging by the timestamps of some files). I'm guessing whereever it got that date was probably just overwritten by the attempted upgrade to saucy?

[wilbur.harvey (wilbur-harvey)]

I have the same problem.
I also have nvidia 313 updates installed and am running dual monitors (2560x1600).

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[cpisbell (chrisisbell)]

I have the same problem. Also running nvidia driver but single monitor.

[Rachel Greenham (rachel-strangenoises)]

FWIW I did eventually (ok, probably about two days later) go ahead and do the upgrade at the terminal using sudo do-release-upgrade, and that went fine. But it makes me unavailable to test a fix.