Bug 191984 - Crashed when tried to set max download speed. Caused the signal 11 (sigsegv).
Summary: Crashed when tried to set max download speed. Caused the signal 11 (sigsegv).
Status: RESOLVED DUPLICATE of bug 188447
Alias: None
Product: ktorrent
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Joris Guisson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-08 01:15 UTC by Haris
Modified: 2009-05-08 02:41 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Haris 2009-05-08 01:15:07 UTC
Version:           3.2.1 (using KDE 4.2.2)
OS:                Linux
Installed from:    Ubuntu Packages

I use the new Ubuntu 9.04 and Gnome desktop environment. The application crashed when I tried to set the max download speed from the context menu on the tray icon.  I repeated the procedure a couple of more times and the same thing happened.  It gave a message that a fatal error occured and it couldn't create valid backtrace...





This backtrace appears to be of no use.
This is probably because your packages are built in a way which prevents creation of proper backtraces, or the stack frame was seriously corrupted in the crash.

(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 0xb5795700 (LWP 21197)]
[New Thread 0xb1f5bb90 (LWP 21201)]
[New Thread 0xb275cb90 (LWP 21200)]
0xb7fd0410 in __kernel_vsyscall ()
[Current thread is 0 (LWP 21197)]

Thread 3 (Thread 0xb275cb90 (LWP 21200)):
#0  0xb7fd0410 in __kernel_vsyscall ()
#1  0xb5c91412 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0
#2  0xb65b0344 in pthread_cond_timedwait () from /lib/tls/i686/cmov/libc.so.6
#3  0xb718b359 in ?? () from /usr/lib/libQtCore.so.4
#4  0xb718b48b in QThread::msleep () from /usr/lib/libQtCore.so.4
#5  0xb7ec7165 in ?? () from /usr/lib/libbtcore.so.10
#6  0xb7ec79f8 in ?? () from /usr/lib/libbtcore.so.10
#7  0xb718b96e in ?? () from /usr/lib/libQtCore.so.4
#8  0xb5c8d4ff in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#9  0xb65a149e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 2 (Thread 0xb1f5bb90 (LWP 21201)):
#0  0xb7fd0410 in __kernel_vsyscall ()
#1  0xb5c910e5 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0
#2  0xb65b02ed in pthread_cond_wait () from /lib/tls/i686/cmov/libc.so.6
#3  0xb718c9b2 in QWaitCondition::wait () from /usr/lib/libQtCore.so.4
#4  0xb7ec66be in ?? () from /usr/lib/libbtcore.so.10
#5  0xb7ec79f8 in ?? () from /usr/lib/libbtcore.so.10
#6  0xb718b96e in ?? () from /usr/lib/libQtCore.so.4
#7  0xb5c8d4ff in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#8  0xb65a149e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 1 (Thread 0xb5795700 (LWP 21197)):
#0  0xb7fd0410 in __kernel_vsyscall ()
#1  0xb655c7a6 in nanosleep () from /lib/tls/i686/cmov/libc.so.6
#2  0xb655c5be in sleep () from /lib/tls/i686/cmov/libc.so.6
#3  0xb7a078b2 in ?? () from /usr/lib/libkdeui.so.5
#4  0xb7a08274 in KCrash::defaultCrashHandler () from /usr/lib/libkdeui.so.5
#5  <signal handler called>
#6  0xb6cfaac2 in QMenu::findIdForAction () from /usr/lib/libQtGui.so.4
#7  0xb6cfc29d in ?? () from /usr/lib/libQtGui.so.4
#8  0xb6d02b5b in ?? () from /usr/lib/libQtGui.so.4
#9  0xb6d03632 in QMenu::mouseReleaseEvent () from /usr/lib/libQtGui.so.4
#10 0xb7a7e7e5 in KMenu::mouseReleaseEvent () from /usr/lib/libkdeui.so.5
#11 0xb68ddbd3 in QWidget::event () from /usr/lib/libQtGui.so.4
#12 0xb6d05a19 in QMenu::event () from /usr/lib/libQtGui.so.4
#13 0xb6886f2c in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#14 0xb688fba1 in QApplication::notify () from /usr/lib/libQtGui.so.4
#15 0xb799794d in KApplication::notify () from /usr/lib/libkdeui.so.5
#16 0xb727fa3b in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#17 0xb688ec0e in QApplicationPrivate::sendMouseEvent () from /usr/lib/libQtGui.so.4
#18 0xb68fec96 in ?? () from /usr/lib/libQtGui.so.4
#19 0xb68fdd37 in QApplication::x11ProcessEvent () from /usr/lib/libQtGui.so.4
#20 0xb6928cfa in ?? () from /usr/lib/libQtGui.so.4
#21 0xb5bd1b88 in IA__g_main_context_dispatch (context=0x8132490) at /build/buildd/glib2.0-2.20.1/glib/gmain.c:1814
#22 0xb5bd50eb in g_main_context_iterate (context=0x8132490, block=1, dispatch=1, self=0x8128458) at /build/buildd/glib2.0-2.20.1/glib/gmain.c:2448
#23 0xb5bd5268 in IA__g_main_context_iteration (context=0x8132490, may_block=1) at /build/buildd/glib2.0-2.20.1/glib/gmain.c:2511
#24 0xb72ab438 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#25 0xb69283f5 in ?? () from /usr/lib/libQtGui.so.4
#26 0xb727e06a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#27 0xb727e4aa in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#28 0xb7280959 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#29 0xb6886da7 in QApplication::exec () from /usr/lib/libQtGui.so.4
#30 0x08064fa9 in _start ()
#0  0xb7fd0410 in __kernel_vsyscall ()
Comment 1 Dario Andres 2009-05-08 02:41:32 UTC
Marking as duplicate of bug 188447
Thanks

*** This bug has been marked as a duplicate of bug 188447 ***