GNOME Bugzilla – Bug 112899
magicdev just crashed during normal system use...
Last modified: 2004-12-22 21:47:04 UTC
Package: magicdev Severity: normal Version: 1.1.4 Synopsis: magicdev just crashed during normal system use... Bugzilla-Product: magicdev Bugzilla-Component: general BugBuddy-GnomeVersion: 2.0 (2.2.0.1) Description: Description of Problem: just crashed. not even using cd-rom. just surfing the web... Debugging Information: Backtrace was generated from '/usr/bin/magicdev' (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)...[New Thread 1086116032 (LWP 4075)] (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)...0xffffe002 in ?? ()
+ Trace 36830
Thread 1 (Thread 1086116032 (LWP 4075))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-05-13 09:06 ------- Unknown version 1.1.x in product magicdev. Setting version to the default, "unspecified". Reassigning to the default owner of the component, otaylor@redhat.com.
This looks like the mysterious gtk+ crash that is showing up everywhere [See specifically bug 105745 for more info]. A number of people are getting this, but the stack traces are unfortunately useless and we don't know how to reproduce the problem. Can you get a stacktrace with symbols for us? [If you're using RedHat 9, you can do so with the following easy method; otherwise this will require recompiling from source: Install http://people.redhat.com/otaylor/tmp/gtk2-debuginfo-2.2.1-4.i386.rpm and if the problem occurs again, submit the backtrace you get. Installing the debuginfo package will make the backtrace much more useful.] I am adding myself to the cc and marking as needinfo for now.
i'll install the debuginfo rpm and watch for it to happen again. now that i've read about how the other instances of the bug have revealed themselves, i believe i've seen some as well. I've seen the panel dying unexpectedly quite often... at least a few times a week. i think i should be able to get a useful strack trace... if it's the panel stack trace that i get and not the magicdev one (seen only once compared to the many for the panel) should i enter a separate bug for it? or attach it to one of the NUMEROUS already existing bugs? (which one?) thanx for all the help.
If the stack trace looks similar you can just put the new stack trace in this bug report. If you're not sure or if you don't want to check (it's possible some of your crashes have a different cause...), feel free to open a new bug report. However, if you suspect it is the same bug, please mention something along the lines of "I believe this is the same bug as bug 112899" in your bug report so that it's easier for us to find duplicates. Thanks for trying to get us a stack trace with debugging symbols.
If you have any more useful information about these crashes, please post them in bug 105745. *** This bug has been marked as a duplicate of 105745 ***