virtualbox-ose upgrade causes update-manager crash

Thanks for your bugreport.

Please attach the files in /var/log/dist-upgrade/ to this bugreport.

Thanks,
 Michael

This is a bug in virtualbox-ose, I reassing:

2008-04-25 07:46:21,759 ERROR got an error from dpkg for pkg: '/var/cache/apt/archives/virtualbox-ose_1.5.6-dfsg-6ubuntu1_i386.deb': 'subprocess pre-installation script returned error exit status 1
'
2008-04-25 07:46:21,759 DEBUG running apport_pkgfailure() virtualbox-ose: subprocess pre-installation script returned error exit status 1

I've asked in the duplicate bug 222425 already:

Any chance you had answered "No" to the following question, which would abort installation/upgrades?

 Proceed with virtualbox-ose upgrade despite losing snapshots?
 You are currently upgrading virtualbox-ose to a new upstream version. All
 snapshots will be discarded by this upgrade, because snapshots are
 version-specific.

It seems so, looking at main.log:
2008-04-25 06:16:13,537 WARNING no activity on terminal for 240 seconds (Preparing virtualbox-ose)
2008-04-25 07:46:21,759 ERROR got an error from dpkg for pkg: '/var/cache/apt/archives/virtualbox-ose_1.5.6-dfsg-6ubuntu1_i386.deb': 'subprocess pre-installation script returned error exit status 1
'

@Daniel Hahler

I don't remember the exact content of the error-message-dialogue in the upgrade-process.
But I'm sure there was no choice-button like "yes" or "no".
After closing the message the upgrade-process skipped installation of virtualbox-ose,
and continued with the next steps up to the end.
After Reboot the virtualbox-ose package installs fine using Synaptics.

Was there maybe a question to skip the setup of a hanging program or something alike?
I'll try to reproduce this in a virtualbox image later (Gutsy => Hardy upgrade with virtualbox-ose/-modules).

Maybe on the console, but not in the error-message-dialogue. And after closing the message, the console filled up with new messages of the continuing upgrade-process. I had no chance for influencing the szene.

This bug report was created because of this crash (from term.log), which needs to be fixed in update-manager, as far as I can see:

Traceback (most recent call last):
  File "logging/__init__.py", line 753, in emit
    self.flush()
  File "logging/__init__.py", line 731, in flush
    self.stream.flush()
IOError: [Errno 9] Bad file descriptor
    self.flush()
  File "logging/__init__.py", line 731, in flush
    self.stream.flush()
IOError: [Errno 9] Bad file descriptor
    self.flush()
  File "logging/__init__.py", line 731, in flush
    self.stream.flush()
IOError: [Errno 9] Bad file descriptor
hardy: Fatal IO error 9 (Bad file descriptor) on X server :0.0.

Re-assigning the bug to update-manager.
I have just reproduced this by upgrading a Gutsy system to Hardy, and when asked to proceed with the virtualbox-ose upgrade, despite losing all snapshots, I did not put the checkbox there (i.e. canceled the upgrade of virtualbox-ose).
This caused two bug reports. This one here for update-manager and bug 210212 for virtualbox-ose.

In fact, the error report happened because of the dpkg failure when configuring the virtualbox-ose. Reassigning back.

Steve, as far as I can see there are two crashes caused by the same reason: the virtualbox-ose debconf question not being answered/seen.
The other one is bug 210212.

The reason appears to be the same, but my point was that update-manager should not crash on this, if possible.

Daniel,
    thank you for the work you are putting in on this project.

I hope that you enjoy the programming and want to make sure that we
appreciate your efforts.

Cheers,
Steve Noolan

 Not doing something you can't do ... is not a moral victory.

Mob 0171 597 0863 (Inside Bangladesh)
Mob +880 171 597 0863 (Outside Bangladesh)
Skype (08) 8121 7819 (VOIP via Skype)
Skype snoolan
eMail <email address hidden>

Daniel Hahler wrote:
> Steve, as far as I can see there are two crashes caused by the same reason: the virtualbox-ose debconf question not being answered/seen.
> The other one is bug 210212.
>
> The reason appears to be the same, but my point was that update-manager
> should not crash on this, if possible.
>
>

@daniel: if you reproduced the issue, could you please tell me in what way update-manager crashes? does it segfault or raise a python excpetion? what did you do to reproduce it? was installing virtualbox prior to the upgrade enough?

@Michael: yes I could reproduce it and it caused two bug reports to be created.
IIRC the above quoted python exception is the part where update-manager crashed.

This bug was fixed in the package virtualbox-ose - 2.0.4-dfsg-0ubuntu1

---------------
virtualbox-ose (2.0.4-dfsg-0ubuntu1) intrepid; urgency=low

  [ Jonathan Ernst ]
  * Virtualbox should go in Accessories, not in System tools (LP: #288590)

  [ Daniel Hahler ]
  * New upstream version (LP: #288957)
    - Updated debian/patches/09-initscript.dpatch (one hunk rejected/obsolete)
  * Drop debconf question about losing snapshots because of upgrading: it is
    no longer relevant and the default (cancel upgrade) caused a lot of
    trouble (LP: #288178, #221736)
    - debian/virtualbox-ose.preinst.in, debian/virtualbox-ose.templates,
      debian/rules
  * Improve patch for disabling the "check for updates" dialog (LP: #272212)
    - debian/patches/13-disable-update-action.dpatch
  * Disable registration request at Sun (LP: #285684, #271603)
    - debian/patches/14-disable-registration-request.dpatch

 -- Daniel Hahler <email address hidden> Sun, 26 Oct 2008 02:23:42 +0100