** Attachment removed: CoreDump.gz
http://launchpadlibrarian.net/6198868/CoreDump.gz
--
[apport] gconf-editor crashed with SIGSEGV
https://bugs.launchpad.net/bugs/83272
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
The crash file are sometime not useful, closing the bug for now then,
feel free to reopen i fthat happens again
** Changed in: gconf-editor (Ubuntu)
Status: Needs Info = Rejected
--
[apport] gconf-editor crashed with SIGSEGV
https://launchpad.net/bugs/83272
--
ubuntu-bugs mailing list
I have no idea how to reproduce this, it just happened once. How often
do the coredumps not allow you to get a backtrace? :(
--
[apport] gconf-editor crashed with SIGSEGV
https://launchpad.net/bugs/83272
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Thank you for your bug report. For some reason the coredump doesn't
allow to get a debug backtrace. Could you try to get a new crash file
with libglib2.0-0-dbg libgtk2.0-0-dbg gconf-editor-dbgsym installed?
** Changed in: gconf-editor (Ubuntu)
Importance: Undecided = Medium
Assignee:
** Attachment added: CoreDump.gz
http://librarian.launchpad.net/6198868/CoreDump.gz
** Attachment added: ProcMaps.txt
http://librarian.launchpad.net/6198869/ProcMaps.txt
** Attachment added: ProcStatus.txt
http://librarian.launchpad.net/6198870/ProcStatus.txt
** Attachment added:
