GNOME Bugzilla – Bug 347888
gedit crashes on startup
Last modified: 2006-07-25 15:38:25 UTC
Distribution: Goobuntu "5.10 20060706" (breezy) Package: gedit Severity: Normal Version: GNOME2.12.1 2.12.1 Gnome-Distributor: Ubuntu Synopsis: gedit crashes on startup Bugzilla-Product: gedit Bugzilla-Component: general Bugzilla-Version: 2.12.1 BugBuddy-GnomeVersion: 2.0 (2.12.0) Description: Description of the crash: After upgrading from hoary to breezy, gedit always crashes on startup Steps to reproduce the crash: 1. run gedit 2. the "this application has closed unexpectedly" dialog apears. Expected Results: Gedit running normally How often does this happen? Every time I run gedit, either from menus or when run from a gnome-terminal commandline. Additional Information: From the commandline there is no output in .xsession-errors or on the console at all. Also, running "gedit --disable-crash-dialog" doesn't disable the crash dialog and has no affect. Running "gedit --help" doesn't crash and correctly outputs the help information. Debugging Information: Backtrace was generated from '/usr/bin/gedit' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208121120 (LWP 32454)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 69412
Thread 1 (Thread -1208121120 (LWP 32454))
------- Bug created by bug-buddy at 2006-07-18 09:29 ------- Unknown version 2.12.1 in product gedit. Setting version to "2.12.x".
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 318099 ***
abo, please see bug 318099 comment 6 for more information and how to work around this issue.
Wow... fast response. Thanks for the rapid assistance. However, are you sure you've used the right bug number for the duplicate? That bug seems to be related to uim and gnome-cups-manager. I have just managed to fix this problem myself by doing the following; 1) log out of the gnome xsession 2) at a console, made sure gconf was not still running 3) did; $ rm -Rf ~/.gconf/apps/gedit-2 4) logged back into gnome xsession and it worked. I suspect in this case it was something screwy in the old hoary gconf that the new breezy gconf didn't like.
(In reply to comment #3) > Wow... fast response. Thanks for the rapid assistance. > > However, are you sure you've used the right bug number for the duplicate? That > bug seems to be related to uim and gnome-cups-manager. Yes, I am sure. :) The relevant part of the stacktrace is right below the top-most "<signal handler called>" string (highlighted green in bugzilla). The crash is related to UIM, just as has been mentioned in bug 318099. Also, if you have a look at the other duplicates, they are not only gnome-cups-manager. > I have just managed to fix this problem myself by doing the following; No matter how you did that, I'm glad you found a quick solution that works for you. :)