Upgrade 13.04 to 13.10 Fail real-time signal 0

Bug #1241684 reported by Allan Kelly
96
This bug affects 22 people
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
Triaged
High
Unassigned

Bug Description

I clicked upgrade button on update-manager window
System prompted for authentication
release note panel appeared, clicked upgrade button
a download panel appeared briefly, upgrade does not proceed

In a command window:
xxxxxx@DeskTop:~$ update-manager
Checking for a new Ubuntu release
authenticate 'saucy.tar.gz' against 'saucy.tar.gz.gpg'
extracting 'saucy.tar.gz'
Real-time signal 0
xxxxxx@DeskTop:~$

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: Fri Oct 18 16:46:02 2013
GsettingsChanges:
 b'com.ubuntu.update-manager' b'first-run' b'false'
 b'com.ubuntu.update-manager' b'launch-time' b'1382106783'
 b'com.ubuntu.update-manager' b'show-details' b'true'
 b'com.ubuntu.update-manager' b'window-height' b'600'
 b'com.ubuntu.update-manager' b'window-width' b'600'
InstallationDate: Installed on 2011-11-01 (716 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
MarkForUpload: True
PackageArchitecture: all
SourcePackage: update-manager
UpgradeStatus: Upgraded to raring on 2013-10-18 (0 days ago)

Revision history for this message
Allan Kelly (wolasallank) wrote :
tags: added: dist-upgrade
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in update-manager (Ubuntu):
status: New → Confirmed
Revision history for this message
Allan Kelly (wolasallank) wrote :

This bug was flagged as a duplicate of 1203534, but now apparently is no longer a duplicate.

As posts in the sometime duplicate suggested the problem occurred in front end of do-release-upgrade command with the NVIDIA driver, and could be avoided by using non proprietary driver, I tried switching from NVIDIA driver to nouveau driver.
As I posted on the erstwhile duplicate bug, the upgrade ran successfully from update-manager GUI.

Revision history for this message
D. Hugh Redelmeier (hugh-mimosa) wrote :

I think I hit this too.

Very puzzling because I first I used the GUI without invoking it from a terminal. It worked for a while and then silently went away. Not even an oil slick.

When I invoked it from a terminal (sudo update-manager -d) it had this "Signal 0" message (which makes no sense to me since there is no signal 0 -- signals start at 1).

This was enough for me to google and get here. But no solution was presented here, so I went to <https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1203534> (thanks Kelly).

From there I learned that the proprietary nVidia driver was the trigger for the problem. I searched in vain for a GUI tool to switch back to Nouveau (there used to be one in Settings: Hardware, but no more -- pity!). I tried the canned apt-get commands but they didn't work.

What appears to be working is using the command "do-release-upgrade". Thanks to <https://launchpad.net/~ric-almeida> for mentioning this in 1203534

Unfortunately, because do-release-upgrade is working (as I type this), I cannot go back and capture precise information about the "sudo update-manager -d" failure.

Revision history for this message
Ken Pratt (kenpratt) wrote :

When I run sudo update-manager -d:

kpratt@flipper:~$ sudo update-manager -d
Checking for a new Ubuntu release
Segmentation fault (core dumped)
kpratt@flipper:~$

Changed in update-manager (Ubuntu):
status: Confirmed → Triaged
importance: Undecided → High
Revision history for this message
Brian Murray (brian-murray) wrote :

I tried upgrading to trusty from saucy with the nvidia driver loaded and was unable to recreate this bug. The upgrade continued past extracting the tarball and successfully started running it.

Revision history for this message
Brian Murray (brian-murray) wrote :

If anybody has successfully upgraded to Saucy it would be great if they could try the upgrade to Trusty and see if it still fails to start.

Revision history for this message
Jim (jdblaich) wrote :

On one machine with the nvidia driver the update-manager -d worked. On a second one done this morning this error occurred. Both have the proprietary nvidia drivers.

do-release-upgrade seems to have allowed me to continue.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.