Routine update of Maverick results in GNOME & power problems

[Matthew Smith]

Binary package hint: apt

I performed a routine upgrade of Maverick on my Dell laptop using the Update Manager this afternoon (15:37 BST). The following packages were upgraded, according to /var/log/apt/history.log :

Start-Date: 2010-10-20 15:37:37
Upgrade: libc-bin:i386 (2.12.1-0ubuntu6, 2.12.1-0ubuntu7), libutouch-grail1:i386 (1.0.14-0ubuntu1, 1.0.15-0ubuntu1), gnome-settings-daemon:i386 (2.32.0-0ubuntu2, 2.32.0-0ubuntu3), libc-dev-bin:i386 (2.12.1-0ubuntu6, 2.12.1-0ubuntu7), libwebkit-1.0-2:i386 (1.2.4-1ubuntu1, 1.2.5-0ubuntu0.10.10.1), gconf2:i386 (2.31.91-0ubuntu3, 2.31.91-0ubuntu3.1), linux-headers-2.6.35-22:i386 (2.6.35-22.34, 2.6.35-22.35), google-chrome-beta:i386 (7.0.517.36-r61761, 7.0.517.41-r62167), linux-libc-dev:i386 (2.6.35-1022.34, 2.6.35-1022.35), libgpod4:i386 (0.7.94-0ubuntu2, 0.7.95-1), gconf-defaults-service:i386 (2.31.91-0ubuntu3, 2.31.91-0ubuntu3.1), jockey-common:i386 (0.5.10-0ubuntu5, 0.5.10-0ubuntu5.1), linux-headers-2.6.35-22-generic:i386 (2.6.35-22.34, 2.6.35-22.35), libgconf2-4:i386 (2.31.91-0ubuntu3, 2.31.91-0ubuntu3.1), udev:i386 (162-2, 162-2.1), dkms:i386 (2.1.1.2-3ubuntu1, 2.1.1.2-3ubuntu1.1), libpoppler7:i386 (0.14.3-0ubuntu1, 0.14.3-0ubuntu1.1), libgudev-1.0-0:i386 (162-2, 162-2.1), libgpod-common:i386 (0.7.94-0ubuntu2, 0.7.95-1), gconf2-common:i386 (2.31.91-0ubuntu3, 2.31.91-0ubuntu3.1), libudev0:i386 (162-2, 162-2.1), libc6-dev:i386 (2.12.1-0ubuntu6, 2.12.1-0ubuntu7), libgconf2-dev:i386 (2.31.91-0ubuntu3, 2.31.91-0ubuntu3.1), poppler-utils:i386 (0.14.3-0ubuntu1, 0.14.3-0ubuntu1.1), jockey-gtk:i386 (0.5.10-0ubuntu5, 0.5.10-0ubuntu5.1), linux-image-2.6.35-22-generic:i386 (2.6.35-22.34, 2.6.35-22.35), libc6:i386 (2.12.1-0ubuntu6, 2.12.1-0ubuntu7), libwebkit-1.0-common:i386 (1.2.4-1ubuntu1, 1.2.5-0ubuntu0.10.10.1), gdm-guest-session:i386 (0.16, 0.17), libpoppler-glib5:i386 (0.14.3-0ubuntu1, 0.14.3-0ubuntu1.1)
End-Date: 2010-10-20 15:40:46

On reboot (as required), the following problems were encountered:

- While booting, machine appears to hang while "checking battery state" (I had hit Esc to get rid of the splash screen so I could see the messages)
- When GDM appeared, widgets sometimes do not appear correctly, including the user selector, and the kernel messages are not replaced by a GDM background
- A system alert message saying something like "GNOME Power Configuration not been installed correctly, please contact your administrator" appears in top right (I am the administrator)
- Many GNOME preferences have been lost once GNOME starts, including widget styling (displays in basic GTK "Windows" style rather than the chosen style - Clearlooks in my case, and when you use the Appearance app in the System/Preferences menu and select a widget style, it changes the style for that window alone, not panels or any other app)
- My top panel had been rearranged with everything bunched up together (rather than some things at far left and others at far right) and it didn't fill the width of the screen as it had before (i.e. "Expand" lost)
- Other GNOME prefs lost, e.g. it makes sounds when I do pretty much everything, and I had disabled them before, Alt+Tab no longer switches windows

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: apt 0.8.3ubuntu7
ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
NonfreeKernelModules: wl
Architecture: i386
Date: Wed Oct 20 16:29:44 2010
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100427.1)
ProcEnviron:
 LANG=en_GB.utf8
 SHELL=/bin/bash
SourcePackage: apt

[Matthew Smith (indigojo)]

I ran the same update on my 64-bit desktop machine a few days later, and had no problems. Also, a further update to my laptop cured the problems i had been having on the laptop. My laptop also has bad sectors on the root file system partition, which may be the cause of my problems.

[Matthew Smith (indigojo)]

This bug was not a bug; it was due to bad sectors on my hard drive which has been replaced.

[Robert Roth (evfool)]

This bug report is being closed due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.