GNOME Bugzilla – Bug 334202
DnD icons across dual-monitor boundary causes crash
Last modified: 2006-03-24 06:16:00 UTC
Steps to reproduce: 1. Click and drag icon on desktop or icon in window across boundary between monitors 2. Nautilus quits Stack trace: Other information: Using dual monitor setup, non TwinView/Xinerama.
In fact, it happens to a lot of other programs too (e.g. dragging names around in Gaim). The error may not lie with Nautilus, but with the x-server.
Thanks for the bug report. Without a stack trace from the crash it's very hard to determine what caused it. Can you provide us with one? Please see http://live.gnome.org/GettingTraces for more information on how to do so.
I doubt this backtrace is very helpful. Seems like it's crashing in the libraries themselves and not nautilus (which supports idea that it goes beyond nautilus). Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found) `system-supplied DSO at 0xffffe000' 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) (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) [Thread debugging using libthread_db enabled] [New Thread -1226905920 (LWP 2470)] [New Thread -1237914704 (LWP 2472)] [New Thread -1236886608 (LWP 2471)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 67197
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 320126 ***