GNOME Bugzilla – Bug 444066
crash in Window Selector: send eclipse to another ...
Last modified: 2007-07-02 04:41:07 UTC
Version: 2.18.0 What were you doing when the application crashed? send eclipse to another desktop while starting Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 36380672 vsize: 36380672 resident: 11034624 share: 8462336 rss: 11034624 rss_rlim: 4294967295 CPU usage: start_time: 1180983294 rtime: 301 utime: 273 stime: 28 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/libexec/wnck-applet' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1209051424 (LWP 2627)] (no debugging symbols found) 0x008fb402 in __kernel_vsyscall ()
+ Trace 138229
Thread 1 (Thread -1209051424 (LWP 2627))
----------- .xsession-errors (24 sec old) --------------------- Sending reload event... Sending reload event... Sending reload event... Sending reload event... Sending reload event... Sending reload event... Sending reload event... Sending reload event... Sending reload event... Sending reload event... Sending reload event... Sending reload event... Sending reload event... Sending reload event... Sending reload event... --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance! (Since bugzilla policy for bad_stacktrace is now to mark as INCOMPLETE. Mass changing all of these. Search for "dieguito-doing-incomplete-spam" to delete all this from your inbox.)
*** Bug 446288 has been marked as a duplicate of this bug. ***
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 420713 ***