Segfault trying to upgrade to saucy from raring

[Aaron Bentley]

When I attempt to upgrade to saucy, update-manager crashes around extracting the tarball:
$ sudo update-manager -d
[sudo] password for abentley:
Checking for a new Ubuntu release
authenticate 'saucy.tar.gz' against 'saucy.tar.gz.gpg'
extracting 'saucy.tar.gz'
Segmentation fault (core dumped)

$ lsb_release -rd
Description: Ubuntu 13.04
Release: 13.04
$ apt-cache policy update-manager
update-manager:
  Installed: 1:0.186.2
  Candidate: 1:0.186.2
  Version table:
 *** 1:0.186.2 0
        500 http://archive.ubuntu.com/ubuntu/ raring-updates/main amd64 Packages
        100 /var/lib/dpkg/status
     1:0.186 0
        500 http://archive.ubuntu.com/ubuntu/ raring/main amd64 Packages

[Brian Murray (brian-murray)]

Is there an apport crash file in /var/crash regarding this?

[Aaron Bentley (abentley)]

No, there are no files in /var/crash at all.

[Brian Murray (brian-murray)]

There may be a folder in /tmp/ named ubuntu-release-upgrader-XYZ which will contain saucy.tar.gz. Can you manually try extracting it?

[Aaron Bentley (abentley)]

The tarball was there, plus a bunch of files. Extracting the files appeared to complete successfully.

I renamed ubuntu-release-upgrader-vijh2f to asdf and re-ran "update-manager -d". It crashed at the same point, slightly differently:

$ sudo 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

I diffed the old directory against the new one, to see if the second extraction had completed successfully:
l# diff . ../asdf -r
diff: ./demoted.cfg: Too many levels of symbolic links
diff: ../asdf/demoted.cfg: Too many levels of symbolic links
diff: ./DistUpgrade: recursive directory loop
Binary files ./DistUpgradeApport.pyc and ../asdf/DistUpgradeApport.pyc differ
Binary files ./DistUpgradeAufs.pyc and ../asdf/DistUpgradeAufs.pyc differ
Binary files ./DistUpgradeConfigParser.pyc and ../asdf/DistUpgradeConfigParser.pyc differ
Binary files ./DistUpgradeGettext.pyc and ../asdf/DistUpgradeGettext.pyc differ
Binary files ./DistUpgradeMain.pyc and ../asdf/DistUpgradeMain.pyc differ
Binary files ./DistUpgradeVersion.pyc and ../asdf/DistUpgradeVersion.pyc differ
Binary files ./DistUpgradeViewGtk3.pyc and ../asdf/DistUpgradeViewGtk3.pyc differ
Binary files ./DistUpgradeView.pyc and ../asdf/DistUpgradeView.pyc differ
Binary files ./__init__.pyc and ../asdf/__init__.pyc differ
Binary files ./SimpleGtk3builderApp.pyc and ../asdf/SimpleGtk3builderApp.pyc differ
Binary files ./trustdb.gpg and ../asdf/trustdb.gpg differ

Since the tarball didn't include any pyc files, I deduce that the tarball was completely extracted and the crash happened when trying to run or compile the extracted files.

[Brian Murray (brian-murray)]

Looking at the function it only extracts the tar file, see http://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu-release-upgrader/trunk/view/head:/DistUpgrade/DistUpgradeFetcherCore.py#L133

[Aaron Bentley (abentley)]

That would be consistent with my comment #4. I tried again and got basically the same thing:
$ update-manager -d
debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied
debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied
debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied
debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied
Checking for a new Ubuntu release
authenticate 'saucy.tar.gz' against 'saucy.tar.gz.gpg'
extracting 'saucy.tar.gz'
Real-time signal 0

[Launchpad Janitor (janitor)]

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

[Aaron Bentley (abentley)]

Today, "sudo update-manager -d" got past the untar, and is now running. Fixed as far as I'm concerned.

[Aaron Bentley (abentley)]

That upgrade aborted due to low disk space. I got "Real-time signal 0" on the next attempt, so it looks like a transient failure now.

[Aaron Bentley (abentley)]

Okay, it looks like "sudo" was the cause. When I ran "upgrade-manager -d" without sudo, it successfully started the installer. I must have done that by accident the first time (comment #8).

[Brian Murray (brian-murray)]

In the bug this bug was made a duplicate of people mention using the nvidia binary driver. Were you using that?

[Aaron Bentley (abentley)]

Yes, I was.

Brian Murray <email address hidden> wrote:
>*** This bug is a duplicate of bug 1203534 ***
> https://bugs.launchpad.net/bugs/1203534
>
>In the bug this bug was made a duplicate of people mention using the
>nvidia binary driver. Were you using that?
>
>--
>You received this bug notification because you are subscribed to the
>bug
>report.
>https://bugs.launchpad.net/bugs/1223894
>
>Title:
> Segfault trying to upgrade to saucy from raring
>
>To manage notifications about this bug go to:
>https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1223894/+subscriptions

--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.