update-manager crashes when trying to upgrade to 13.10 when nvidia video driver in use

[Dariusz Gadomski]

The update manager segfaults when trying to upgrade from 13.04 to 13.10 when using the nvidia driver.

Steps to reproduce:
1. $ sudo update-manager -c -d
2. Press the 'Upgrade...' button.

Expected result:
Another window appears asking to confirm the upgrade.

Actual result:
After message on checking the availability of a new Ubuntu release I get a Segmentation fault (core dumped) message.

ProblemType: BugDistroRelease: Ubuntu 13.04
Package: update-manager 1:0.186.1
ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11
Uname: Linux 3.8.0-22-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.9.2-0ubuntu8.3
Architecture: amd64
Date: Sun Jul 21 18:14:09 2013
GsettingsChanges:
 b'com.ubuntu.update-manager' b'first-run' b'false'
 b'com.ubuntu.update-manager' b'launch-time' b'1374423191'
 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'617'
InstallationDate: Installed on 2013-05-25 (56 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MarkForUpload: True
PackageArchitecture: allSourcePackage: update-manager
UpgradeStatus: No upgrade log present (probably fresh install)

[Launchpad Janitor (janitor)]

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

[Mark Bennison (mark-bennison)]

Just to add to this, I also get a message in the terminal that says "Real-time signal 0".

Note also that after 3 attempts to do this, it got a little further and then crashed again. The terminal output is:

Checking for a new Ubuntu release
WARNING:root:fetch result != continue (2)
Traceback (most recent call last):
  File "/usr/bin/do-release-upgrade", line 152, in <module>
    fetcher.run()
  File "/usr/lib/python3/dist-packages/DistUpgrade/DistUpgradeFetcherCore.py", line 278, in run
    _("Fetching the upgrade failed. There may be a network "
  File "/usr/lib/python3/dist-packages/DistUpgrade/DistUpgradeFetcher.py", line 50, in error
    return error(self.window_main.window_main, summary, message)
AttributeError: 'NoneType' object has no attribute 'window_main'

Also I sent an apport error, but it didn't offer to show raise a bug, Note sure if this is wholly related to this bug, but I am posting here for those more knowledgeable to advise!

[Horst Schirmeier (horst)]

foo@bar:/media$ update-manager -d
Checking for a new Ubuntu release
authenticate 'saucy.tar.gz' against 'saucy.tar.gz.gpg'
extracting 'saucy.tar.gz'
Real-time signal 0

Note that I did this in a read-only directory. When running, e.g., in /tmp, it works reproducibly.

[Simone Bordet (simone-bordet)]

See also https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1241684

[Simone Bordet (simone-bordet)]

I have an NVIDIA card, and was using the binary driver.
I have switched to the open source driver, and retried the upgrade, and it worked for me, no more "Real-time signal 0" error nor core dumped.

[B. Clausius (barcc)]

I am also using the NVIDIA binary driver. I did the upgrade in a terminal with do-release-upgrade that worked.

The bug is not in update-manager but in the Gtk3 frontend of the command do-release-upgrade from the source package ubuntu-release-upgrader (update-manager internally invokes do-release-upgrade).

Try this command:
/usr/bin/pkexec /usr/bin/do-release-upgrade --frontend=DistUpgradeViewGtk3
It fails as described above.

[Leonardo Donelli (learts92)]

I'm also using the NVIDIA binary driver (304.something).
I can confirm that upgrading with `do-release-upgrade` works.

[Allan Kelly (wolasallank)]

As comment #6 above, I switched from NVIDIA to nouveau driver.
Upgrade ran fine from update-manager GUI.

[Ricardo Almeida (ric-almeida)]

Another one on NVIDIA binary driver... do-release-upgrade works

[Dave S (dsokolowsky)]

I also had the problem and NVIDIA driver. Completed the do-release-upgrade method last night.

[Brian Murray (brian-murray)]

Does this only happen when using 'sudo update-manager -d' with the nvidia driver, or does it also happen with just 'update-manager -d' and the nvidia driver?

[ChrisiPK (chrisipk)]

@brian-murray Yes, it also happens without sudo. The update manager prompts for the password after clicking the "Upgrade..." button and it fails after that.

[Brian Murray (brian-murray)]

When clicking the upgrade button the following command is called:

/usr/bin/pkexec /usr/bin/do-release-upgrade --frontend=DistUpgradeViewGtk3 -d

Could you please try that in a terminal? Thanks in advance.

[klap-in (klap-in)]

@brian-murray

- I got the update popup, after usual update. I try the upgrade button, but it fails silence.
- Next i tried in a terminal: /usr/bin/pkexec /usr/bin/do-release-upgrade --frontend=DistUpgradeViewGtk3 -d
This fails with a segfault.
- Next i tried again that command in a terminal and now the upgrade runs fine.

[Brian Murray (brian-murray)]

On Tue, Nov 05, 2013 at 09:50:42AM -0000, klap-in wrote:
> @brian-murray
>
> - I got the update popup, after usual update. I try the upgrade button, but it fails silence.
> - Next i tried in a terminal: /usr/bin/pkexec /usr/bin/do-release-upgrade --frontend=DistUpgradeViewGtk3 -d
> This fails with a segfault.
> - Next i tried again that command in a terminal and now the upgrade runs fine.

To be clear you ran this command, /usr/bin/pkexec
/usr/bin/do-release-upgrade --frontend=DistUpgradeViewGtk3 -d, two times
in a terminal and the second time it worked?

--
Brian Murray

[Dave S (dsokolowsky)]

On a second system w/Nvidia.

Failed 4 times using:
"in a terminal: /usr/bin/pkexec /usr/bin/do-release-upgrade --frontend=DistUpgradeViewGtk3 -d"

twice with result:
Checking for a new Ubuntu release
authenticate 'saucy.tar.gz' against 'saucy.tar.gz.gpg'
extracting 'saucy.tar.gz'
Real-time signal 0

third time was:
Checking for a new Ubuntu release
authenticate 'saucy.tar.gz' against 'saucy.tar.gz.gpg'
extracting 'saucy.tar.gz'
Segmentation fault (core dumped)

then tried from /tmp:
Checking for a new Ubuntu release
Real-time signal 0

Finally ran do-release-upgrade, as with previous system, and it's off and running.

[Ronny Klaeboe (icemover)]

Changing display-driver worked for me. Ref comment #6.

[Walter Ribeiro (wribeirojr)]

One more bug to NVidia list.