GNOME Bugzilla – Bug 355557
crash in System Log: Gnome-btdownload, is ser...
Last modified: 2007-03-09 08:39:10 UTC
Version: 2.16.0 What were you doing when the application crashed? Gnome-btdownload, is seriously broken and locks up when ever a torrent is begun, I was going to view the log files while it was locked up to see if I could get any information from the lockup Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.0 2006-09-04 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 31170560 vsize: 0 resident: 31170560 share: 0 rss: 12705792 rss_rlim: 0 CPU usage: start_time: 1158054157 rtime: 0 utime: 36 stime: 0 cutime:32 cstime: 0 timeout: 4 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/gnome-system-log' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1225075024 (LWP 14587)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 72171
Thread 1 (Thread -1225075024 (LWP 14587))
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. Getting the debug symbols for the GNOME stack will also enhance the chances to discover the reason why the BT client locks up.
*** Bug 356211 has been marked as a duplicate of this bug. ***
*** Bug 356503 has been marked as a duplicate of this bug. ***
Closing this bug report as no further information has been provided. Anybody please feel free to reopen this bug if you can provide the information Emmanuele asked for. Thanks!
Marking as duplicate of bug 364106 as bug 364106 provides a stacktrace with debug symbols.
*** This bug has been marked as a duplicate of 364106 ***
*** Bug 407604 has been marked as a duplicate of this bug. ***
*** Bug 413374 has been marked as a duplicate of this bug. ***
*** Bug 415043 has been marked as a duplicate of this bug. ***
*** Bug 415989 has been marked as a duplicate of this bug. ***
*** Bug 416122 has been marked as a duplicate of this bug. ***
*** Bug 416337 has been marked as a duplicate of this bug. ***