update-gconf-defaults crashed with IOError in write_and_apply_entries()

Bug #444542 reported by userdce
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gconf (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: gconf

update-gconf-defaults crashed with IOError in write_and_apply_entries()

ProblemType: Crash
Architecture: amd64
Date: Tue Oct 6 18:31:54 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/update-gconf-defaults
InterpreterPath: /usr/bin/python2.6
NonfreeKernelModules: nvidia
Package: gconf2 2.28.0-0ubuntu1
ProcCmdline: /usr/bin/python /usr/bin/update-gconf-defaults
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_IN
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-11.38-generic
PythonArgs: ['/usr/bin/update-gconf-defaults']
SourcePackage: gconf
Title: update-gconf-defaults crashed with IOError in write_and_apply_entries()
Uname: Linux 2.6.31-11-generic x86_64
UserGroups: adm admin audio cdrom dialout dip fax fuse lpadmin netdev plugdev sambashare tape vboxusers video

Revision history for this message
userdce (userdce) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #444544, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

tags: removed: need-duplicate-check
visibility: private → public
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.