Activity log for bug #789733

Date Who What changed Old value New value Message
2011-05-29 02:16:39 Eliah Kagan bug added bug
2011-05-29 02:17:00 Eliah Kagan visibility private public
2011-05-29 02:20:24 Eliah Kagan description Binary package hint: update-manager On a Lubuntu Maverick i386 system in a Lubuntu Desktop session, I opened an LXTerminal window very shortly after logging on, and I ran "sudo apt-get update". That completed successfully, but Apport informed me that check-new-release-gtk had crashed with ImportError in build_ui(). This system has update-manager 1:0.142.2. I suspect that the crash is due to an unexpected package manager locking conflict. This is the second time this crash has occurred on this machine; it occurred about one day previously, under the same conditions, but I was unable to report it with Apport due to some old package versions (which I since upgraded). ProblemType: Crash DistroRelease: Ubuntu 10.10 Package: update-manager 1:0.142.23 ProcVersionSignature: Ubuntu 2.6.35-29.51-generic 2.6.35.12 Uname: Linux 2.6.35-29-generic i686 Architecture: i386 Date: Sat May 28 19:48:03 2011 ExecutablePath: /usr/lib/update-manager/check-new-release-gtk InstallationMedia: Lubuntu 10.10 "Maverick Meerkat" - i386 (20101010) InterpreterPath: /usr/bin/python2.6 PackageArchitecture: all ProcCmdline: /usr/bin/python2.6 /usr/lib/update-manager/check-new-release-gtk ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash PythonArgs: ['/usr/lib/update-manager/check-new-release-gtk'] SourcePackage: update-manager Title: check-new-release-gtk crashed with ImportError in build_ui() UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare Binary package hint: update-manager On a Lubuntu Maverick i386 system in a Lubuntu Desktop session, I opened an LXTerminal window very shortly after logging on, and I ran "sudo apt-get update". That completed successfully, but Apport informed me that check-new-release-gtk had crashed with ImportError in build_ui(). This system has update-manager 1:0.142.2. I suspect that the crash is due to an unexpected package manager locking conflict (and that if I had waited to run apt-get until after check-new-release-gtk acquired a lock, the crash would not have occurred). This is the second time this crash has occurred on this machine; it occurred about one day previously, under the same conditions, but I was unable to report it with Apport due to some old package versions (which I since upgraded). ProblemType: Crash DistroRelease: Ubuntu 10.10 Package: update-manager 1:0.142.23 ProcVersionSignature: Ubuntu 2.6.35-29.51-generic 2.6.35.12 Uname: Linux 2.6.35-29-generic i686 Architecture: i386 Date: Sat May 28 19:48:03 2011 ExecutablePath: /usr/lib/update-manager/check-new-release-gtk InstallationMedia: Lubuntu 10.10 "Maverick Meerkat" - i386 (20101010) InterpreterPath: /usr/bin/python2.6 PackageArchitecture: all ProcCmdline: /usr/bin/python2.6 /usr/lib/update-manager/check-new-release-gtk ProcEnviron:  LANG=en_US.UTF-8  SHELL=/bin/bash PythonArgs: ['/usr/lib/update-manager/check-new-release-gtk'] SourcePackage: update-manager Title: check-new-release-gtk crashed with ImportError in build_ui() UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
2011-06-07 06:48:32 Apport retracing service tags apport-crash i386 maverick need-duplicate-check apport-crash i386 maverick
2011-06-07 06:48:33 Apport retracing service bug added subscriber Crash bug triagers for Ubuntu packages
2012-05-31 02:34:35 Ubuntu Foundations Team Bug Bot update-manager (Ubuntu): importance Undecided Medium
2014-09-05 01:20:25 Launchpad Janitor update-manager (Ubuntu): status New Confirmed