GNOME Bugzilla – Bug 347059
Crash when starting nautilus-sendto
Last modified: 2006-07-29 18:46:32 UTC
Steps to reproduce: Subject: Crash when starting gnome-sendto Distribution: Ubuntu 6.06 (dapper) Package: nautilus-sendto Severity: Normal Version: GNOME2.14.2 0.5 Gnome-Distributor: Ubuntu Synopsis: Crash when starting gnome-sendto Bugzilla-Product: nautilus-sendto Bugzilla-Component: general Bugzilla-Version: 0.5 BugBuddy-GnomeVersion: 2.0 (2.14.1) Description: Description of the crash: The program crashed right after executing "gnome-sendto". The window could be shown, but not "correctly"; see http://www.myimg.de/?img=BildschirmfotoSendenan144.png Steps to reproduce the crash: 1. Start "gnome-sendto" Expected Results: Program should start. How often does this happen? Always Debugging Information: Backtrace was generated from '/usr/bin/nautilus-sendto' (no debugging symbols found) 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) [Thread debugging using libthread_db enabled] [New Thread -1224013056 (LWP 16346)] [New Thread -1259623504 (LWP 16347)] (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) (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 __kernel_vsyscall ()
+ Trace 69253
Thread 1 (Thread -1224013056 (LWP 16346))
Stack trace: Other information:
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 317081 ***
This actually is not a duplicate of bug 317081, which already is fixed in the version used by this report. This crash is caused by the issue mentioned in bug 348941. Patch attached there, marking properly as duplicate, thus raising awareness and priority of that bug. (See bug 349029 comment 5 for details.) Sorry for the noise. *** This bug has been marked as a duplicate of 348941 ***