** Changed in: gconf-cleaner (Debian)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/764041
Title:
gconf-cleaner crashed with SIGABRT in raise()
To manage no
Still occuring in Raring beta 2. Running as root (via sudo or
otherwise) is not a solution, as then it simply cleans gconf for the
root user.
In my case the issue is not reproducible using the root user, however I
need to save and clean keys for my day-to-day user which has years of
cruft.
--
** Changed in: gconf-cleaner (Debian)
Status: Unknown => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/764041
Title:
gconf-cleaner crashed with SIGABRT in raise()
To manage notific
** Bug watch added: Debian Bug tracker #689831
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689831
** Also affects: gconf-cleaner (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689831
Importance: Unknown
Status: Unknown
--
You received this bug notification bec
Try running it with root access: sudo gconf-cleaner
This should work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/764041
Title:
gconf-cleaner crashed with SIGABRT in raise()
To manage notificati
** Also affects: gconf-cleaner via
http://code.google.com/p/gconf-cleaner/issues/detail?id=18
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/764041
Titl
Happened in Precise (bug #970195).
---
StacktraceTop:
g_assertion_message (domain=, file=,
line=, func=0x4071d0 "_gconf_cleaner_value_to_string",
message=0x7f45a2a23ba0 "code should not be reached") at
/build/buildd/glib2.0-2.32.0/./glib/gtestutils.c:1861
_gconf_cleaner_value_to_string (value=0x
Yes, I am able to reproduce it.
The problem is that gconf-editor does not support the GConfSchema value.
Reported upstream: http://code.google.com/p/gconf-cleaner/issues/detail?id=18
** Bug watch added: code.google.com/p/gconf-cleaner/issues #18
http://code.google.com/p/gconf-cleaner/issues/det
Here's how I reproduce this bug:
I am presently with natty beta installed with the latest update as of 15
minutes ago.
1. Run gconf-cleaner from terminal or menu.
2. Click forward. Gconf-cleaner Analyzes system conf.
(At this point, there are multiple warnings. See gc.log)
3. Step 3, click Save
Thanks for this report. However I am not reproduce the crash...
When does it happen? When you click the "Save As" button, or when you click the
"Save" button in the "Save As" window?
Is there any output if you run it from a terminal?
** Changed in: gconf-cleaner (Ubuntu)
Status: New => Inc
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/764041
Title:
gconf-cleaner crashed with SIGABRT in raise()
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
11 matches
Mail list logo