** Description changed: Binary package hint: update-manager - I just wanted the damn window to go away! + I just wanted the window to go away! ProblemType: Crash DistroRelease: Ubuntu 10.10 Package: update-manager 1:0.142.23 ProcVersionSignature: Ubuntu 2.6.35-28.50-generic 2.6.35.11 Uname: Linux 2.6.35-28-generic x86_64 NonfreeKernelModules: openafs Architecture: amd64 Date: Tue May 17 12:35:05 2011 ExecutablePath: /usr/lib/update-manager/check-new-release-gtk InterpreterPath: /usr/bin/python2.6 PackageArchitecture: all ProcCmdline: /usr/bin/python2.6 /usr/lib/update-manager/check-new-release-gtk ProcEnviron: - PATH=(custom, no user) - LANG=en_US.UTF-8 - SHELL=/bin/bash + PATH=(custom, no user) + 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 GError in on_button_dont_upgrade_clicked() Traceback: - Traceback (most recent call last): - File "/usr/lib/update-manager/check-new-release-gtk", line 106, in on_button_dont_upgrade_clicked - self.new_dist.name) - GError: No database available to save your configuration: Unable to store a value at key '/apps/update-manager/check_new_release_ignore', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf + Traceback (most recent call last): + File "/usr/lib/update-manager/check-new-release-gtk", line 106, in on_button_dont_upgrade_clicked + self.new_dist.name) + GError: No database available to save your configuration: Unable to store a value at key '/apps/update-manager/check_new_release_ignore', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf UserGroups: adm audio cdrom dialout floppy plugdev video
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/784130 Title: check-new-release-gtk crashed with GError in on_button_dont_upgrade_clicked() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/784130/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
