I used "sudo force_start=1 /etc/init.d/apport start" to temporarily start apport in order to file this bug (seeing as how apport is disabled in the stable jaunty version).
** Description changed: Binary package hint: gconf-editor this crash is pretty easy to reproduce: - 0. First make sure you have a bookmark on some key inside gconf-editor - and then close it + 0. First make sure you have a bookmark on some key inside gconf-editor and then close it + 1. ALT-F2 enter "gconf-editor" - Now repeat these steps: - 1. ALT-F2 enter "gconf-editor" + Now repeat these steps (2-3 times is usually enough to trigger the crash, unfortunately I don't have 100% solid repro but with these steps I find it pretty easy to trigger the crash): 2. Select "File :: New Settings Window" (a new gconf-editor window appears) 3. Close the original gconf-editor window but leave the newly created one. 4. Select "Bookmarks :: YourBookmark" in the remaining "newly created" gconf-editor ProblemType: Crash Architecture: amd64 DistroRelease: Ubuntu 9.04 ExecutablePath: /usr/bin/gconf-editor Package: gconf-editor 2.26.0-0ubuntu1 ProcCmdline: gconf-editor ProcEnviron: LANG=en_DK.UTF-8 SHELL=/bin/bash Signal: 11 SourcePackage: gconf-editor StacktraceTop: ORBit_c_stub_invoke () from /usr/lib/libORBit-2.so.0 ConfigDatabase_all_dirs () gconf_engine_all_dirs () gconf_client_all_dirs () ?? () Title: gconf-editor crashed with SIGSEGV in ORBit_c_stub_invoke() Uname: Linux 2.6.28-11-generic x86_64 UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare -- gconf-editor crashed with SIGSEGV in ORBit_c_stub_invoke() https://bugs.launchpad.net/bugs/364702 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
