GNOME Bugzilla – Bug 324165
Crashes when sending windows to a different screen.
Last modified: 2006-01-25 08:03:48 UTC
stribution: Ubuntu 5.10 (breezy) Package: gnome-panel Severity: Normal Version: GNOME2.12.1 0 Gnome-Distributor: Ubuntu Synopsis: Crashes when sending windows to a different screen. Bugzilla-Product: gnome-panel Bugzilla-Component: Window Selector Applet Bugzilla-Version: 0 BugBuddy-GnomeVersion: 2.0 (2.12.0) Description: Description of the crash: I use dual monitors on ATI (not widescreen). When I send an window to the other screen, wnck-applet always crashes. Steps to reproduce the crash: 1. open an image in the gimp (on Screen 1) 2. choose View -> Move to a different screen -> Screen 0 Expected Results: How often does this happen? Always Additional Information: Debugging Information: Backtrace was generated from '/usr/libexec/wnck-applet' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (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 -1224059200 (LWP 8388)] (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) 0xffffe410 in ?? ()
+ Trace 64625
Thread 1 (Thread -1224059200 (LWP 8388))
------- Bug moved to this database by unknown@gnome.bugs 2005-12-15 11:59 UTC ------- Bugreport had an attachment. This cannot be imported to Bugzilla. Contact bugmaster@gnome.org if you are willing to write a patch for this. Unknown version 0 in product gnome-panel. Setting version to "unspecified". The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@gnome.bugs. Previous reporter was 112@anykey.cz.
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.
Bug 317333 has a good stack trace. *** This bug has been marked as a duplicate of 317333 ***