GNOME Bugzilla – Bug 325159
gedit crashes
Last modified: 2006-01-27 14:14:26 UTC
Distribution: Fedora Core release 4 (Stentz) Package: gedit Severity: normal Version: GNOME2.10.0 2.10.2 Gnome-Distributor: Red Hat, Inc Synopsis: gedit crashes Bugzilla-Product: gedit Bugzilla-Component: general Bugzilla-Version: 2.10.2 BugBuddy-GnomeVersion: 2.0 (2.10.0) Description: Description of the crash: I have no idea what happened, but it seems to happen whenever I leave gedit open for a a while without using it, and then I try to open something. Steps to reproduce the crash: No idea, I was just trying to open a file in a copy of gedit that had been running for a few days with quite a few files open (6-10?) Expected Results: gedit crashes How often does this happen? Every few days. Additional Information: This email was generated by Bug Buddy. I've been ignoring this problem for a long time. This time I decided to let Bug Buddy run. Sorry if this report is not of any use. Debugging Information: Backtrace was generated from '/usr/bin/gedit' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) `shared object read from target memory' has disappeared; keeping its symbols. (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208247680 (LWP 11656)] [New Thread -1212535888 (LWP 12721)] [New Thread -1212265552 (LWP 14125)] [New Thread -1211917392 (LWP 11661)] [New Thread -1211577424 (LWP 11660)] [New Thread -1211311184 (LWP 11659)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0x001b4402 in __kernel_vsyscall ()
+ Trace 64843
Thread 3 (Thread -1212265552 (LWP 14125))
------- Bug created by bug-buddy at 2005-12-28 18:21 ------- Unknown version 2.10.2 in product gedit. Setting version to "2.10.x".
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.
I've installed the gedit-debug package (as of 2005-12-28). Now, of course, gedit refuses to crash for me. I will start banging away at it early next week.
I have not been able to reproduce this bug since I added the debug symbols for gedit. Around 2005-12-29 I discovered that I had misconfigured grub so it was not using any of the updated kernel versions I installed for the last 6 months (getting config file from wrong partition). Previous to that I had been running kernel 2.6.11-1.1369_FC4. As of 2005-12-29 I have been running kernel 2.6.14-1.1653_FC4. I wonder if it would be best to close this bug and I will file another bug if it happens again?
I'm going to close it. Feel free to reopen it if it happens again.
gnome-vfs issue in thread 3 most likeley
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report? *** This bug has been marked as a duplicate of 312943 ***