adept crashes because it can't ask to keep a configuration file or to use a newer version

Bug #149803 reported by Jeroen Maris
2
Affects Status Importance Assigned to Milestone
adept (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: adept-updater

This bug probably deserves high priority, as it breaks the updating mechanism and leaves novice users with a broken system, that may not even boot.

Today I used adept_updater to get some new updates. One of these updates wanted to install a new version of the configuration file `/etc/default/linux-restricted-modules-common'. Adept crashed due to an error that would break a package or something. Then I opened Konsole and did an `aptitude upgrade`. I got the message "dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem.". So I entered 'dpkg --configure -a' and it came up with the text below:
-----------------------------------
Processing triggers for initramfs-tools ...
update-initramfs: Generating /boot/initrd.img-2.6.22-13-generic
Setting up linux-restricted-modules-common (2.6.22.4-13.6) ...

Configuration file `/etc/default/linux-restricted-modules-common'
 ==> Modified (by you or by a script) since installation.
 ==> Package distributor has shipped an updated version.
   What would you like to do about it ? Your options are:
    Y or I : install the package maintainer's version
    N or O : keep your currently-installed version
      D : show the differences between the versions
      Z : background this process to examine the situation
 The default action is to keep your current version.
*** linux-restricted-modules-common (Y/I/N/O/D/Z) [default=N] ? D

Configuration file `/etc/default/linux-restricted-modules-common'
 ==> Modified (by you or by a script) since installation.
 ==> Package distributor has shipped an updated version.
   What would you like to do about it ? Your options are:
    Y or I : install the package maintainer's version
    N or O : keep your currently-installed version
      D : show the differences between the versions
      Z : background this process to examine the situation
 The default action is to keep your current version.
*** linux-restricted-modules-common (Y/I/N/O/D/Z) [default=N] ? Y
Installing new version of config file /etc/default/linux-restricted-modules-common ...
-----------------------------------
I think I know what the problem is. Because the Nvidia binary driver in the repository's is version 100.14.11, I manually installed version 100.14.19. During installation I needed to edit the file '/etc/default/linux-restricted-modules-common' to add the modules `nv` and `nvidia_new` to the blacklist.

The bug is that adept crashes in stead of asking me whether I want to keep the old file or replace it with the maintainers version.
By the way, I chose to replace mine with the maintainer's version, as I will need to recompile the Nvidia-driver for my new kernel. I can then add those two modules to the blacklist again.

Revision history for this message
Jeroen Maris (jealma) wrote :

uname -a: Linux Nemo 2.6.22-12-generic #1 SMP Sun Sep 23 18:11:30 GMT 2007 i686 GNU/Linux

Revision history for this message
Jeroen Maris (jealma) wrote :
Revision history for this message
Jeroen Maris (jealma) wrote :
Revision history for this message
Jeroen Maris (jealma) wrote :

Steps to reproduce:
1) be sure to have a Kubuntu Gutsy system, on which the 2.6.22-13 kernel update is not yet installed
2) before updating, edit the file /etc/default/linux-restricted-modules-common and add some module to the blacklist. For example: change `Blacklist=""` to `Blacklist="nv nvidia_new"` (this is common for people who manually install the nvidia-driver)
3) use `kdese adept_updater` (or the tray applet) to get the updates. Adept will crash as shown in the screenshot below.
4) open Konsole, become root and enter `aptitude upgrade`; you will get a message, informing you that dpkg is broken
5) enter `dpkg --configure -a` to fix the problem. Dpkg will inform you that the package maintainer has released a new version of the file `/etc/default/linux-restricted-modules-common`. You will be asked whether you want to replace the old file with the new one, keep the old one or view the differences. Choose to install the new file.

Revision history for this message
Jeroen Maris (jealma) wrote :

Remark: in my previous message in step 3, I used `kdese adept_updater`. This should be `kdesu adept_updater`.

I got this bug on an AMD x2 system with a Nvidia 7300GT graphics card and the Nvidia 100.14.19 driver. I have been able to reproduce this bug on a virtual machine (VirtualBox) without the nvidia-driver. Only difference is that a direct `aptitude upgrade` helps and that one doesn't need to execute `dpkg --configure -a`.

Revision history for this message
Rav (thecheatah) wrote :

I can confirm this on two different machines. It is rather annoying.

I do however remember seeing some sort of a gui message box asking me if I wanted to replace a file and it had the ability to show diffs (I might have seen it upgrading from feisty to gutsy). So I guess it might be implemented already. Maybe just doesn't handle all of the cases well.

I also think this bug should be given a higher priority.

Revision history for this message
Juan Carlos Torres (jucato) wrote :

Marking this as a duplicate of bug #158043 (although this report has more information).

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.