Bug 265493 - While trying to report a ktorrent bug, Drkonqi refuses to generate a report
Summary: While trying to report a ktorrent bug, Drkonqi refuses to generate a report
Status: RESOLVED DOWNSTREAM
Alias: None
Product: drkonqi
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Dario Andres
URL:
Keywords:
: 265787 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-02-05 10:25 UTC by George R. Goffe
Modified: 2011-02-24 20:52 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description George R. Goffe 2011-02-05 10:25:59 UTC
Version:           unspecified (using KDE 4.5.5) 
OS:                Linux

Ktorrent is failing and Drkonqi goes through it's dialogue and then claims that there is NOT enough information to make a meaningful report and then offers options. #1, install debug symbols which, when selected, fails even though debug symbols are present (see included back trace generated). #2, attempt to continue asks if I'm willing to do some debugging which leads to #1 above.

Reproducible: Always

Steps to Reproduce:
ktorrent beta1 fails
drkonqi is invoked
the fun begins

Actual Results:  
failure to make a report

Expected Results:  
A valid and useful report is expected.

Application: KTorrent (ktorrent), signal: Segmentation fault
[Current thread is 1 (Thread 0xb7766ab0 (LWP 24003))]

Thread 5 (Thread 0xb579fb70 (LWP 24098)):
#0  0x00f05416 in __kernel_vsyscall ()
#1  0x00cf239b in pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i486/pthread_cond_wait.S:169
#2  0x4200b057 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /usr/lib/libQtWebKit.so.4
#3  0x00cede99 in start_thread (arg=0xb579fb70) at pthread_create.c:301
#4  0x00c2cd2e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:133

Thread 4 (Thread 0x95149b70 (LWP 24468)):
#0  0x00f05416 in __kernel_vsyscall ()
#1  0x00c21c36 in __poll (fds=0xd7f4c58, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87
#2  0x06126436 in net::Poll::poll (this=0x87a09c8, timeout=-1) at /tools/ktorrent/libktorrent-1.1beta1/src/net/poll.cpp:99
#3  0x06122992 in net::DownloadThread::waitForSocketReady (this=0x87a09c0) at /tools/ktorrent/libktorrent-1.1beta1/src/net/downloadthread.cpp:128
#4  0x06122a9f in net::DownloadThread::update (this=0x87a09c0) at /tools/ktorrent/libktorrent-1.1beta1/src/net/downloadthread.cpp:48
#5  0x06122d38 in net::NetworkThread::run (this=0x87a09c0) at /tools/ktorrent/libktorrent-1.1beta1/src/net/networkthread.cpp:48
#6  0x03ce2e6a in QThreadPrivate::start (arg=0x87a09c0) at thread/qthread_unix.cpp:285
#7  0x00cede99 in start_thread (arg=0x95149b70) at pthread_create.c:301
#8  0x00c2cd2e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:133

Thread 3 (Thread 0x94948b70 (LWP 24469)):
#0  0x00f05416 in __kernel_vsyscall ()
#1  0x00cf239b in pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i486/pthread_cond_wait.S:169
#2  0x03ce1e8a in QMutexPrivate::wait (this=0x87a0958, timeout=-1) at thread/qmutex_unix.cpp:84
#3  0x03cde4b2 in QMutex::lock (this=0x8114c34) at thread/qmutex.cpp:167
#4  0x06121060 in net::SocketMonitor::lock (this=0x8114c30) at /tools/ktorrent/libktorrent-1.1beta1/src/net/socketmonitor.cpp:82
#5  0x06122225 in net::UploadThread::update (this=0x87a0dc8) at /tools/ktorrent/libktorrent-1.1beta1/src/net/uploadthread.cpp:49
#6  0x06122d38 in net::NetworkThread::run (this=0x87a0dc8) at /tools/ktorrent/libktorrent-1.1beta1/src/net/networkthread.cpp:48
#7  0x03ce2e6a in QThreadPrivate::start (arg=0x87a0dc8) at thread/qthread_unix.cpp:285
#8  0x00cede99 in start_thread (arg=0x94948b70) at pthread_create.c:301
#9  0x00c2cd2e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:133

Thread 2 (Thread 0x94147b70 (LWP 24470)):
#0  0x00f05416 in __kernel_vsyscall ()
#1  0x00cf239b in pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i486/pthread_cond_wait.S:169
#2  0x03ce3567 in wait (this=0xd24d0b4, mutex=0xd24d0b0, time=4294967295) at thread/qwaitcondition_unix.cpp:88
#3  QWaitCondition::wait (this=0xd24d0b4, mutex=0xd24d0b0, time=4294967295) at thread/qwaitcondition_unix.cpp:160
#4  0x06125f37 in net::ReverseResolverThread::run (this=0xd24d0a8) at /tools/ktorrent/libktorrent-1.1beta1/src/net/reverseresolver.cpp:123
#5  0x03ce2e6a in QThreadPrivate::start (arg=0xd24d0a8) at thread/qthread_unix.cpp:285
#6  0x00cede99 in start_thread (arg=0x94147b70) at pthread_create.c:301
#7  0x00c2cd2e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:133

Thread 1 (Thread 0xb7766ab0 (LWP 24003)):
[KCrash Handler]
#7  0x03fb8f21 in QNativeSocketEngine::waitForReadOrWrite (this=) at socket/qnativesocketengine.cpp:952
Comment 1 George Kiagiadakis 2011-02-05 11:52:14 UTC
(In reply to comment #0)
> Thread 1 (Thread 0xb7766ab0 (LWP 24003)):
> [KCrash Handler]
> #7  0x03fb8f21 in QNativeSocketEngine::waitForReadOrWrite (this=) at
> socket/qnativesocketengine.cpp:952

This is indeed a useless backtrace of Thread 1 that crashed, so drkonqi correctly rates it as useless. It looks like you have some, but not all the required debugging symbols.

The "install debug symbols" functionality is an extension that is implemented differently in each distribution (so that every distribution can integrate it properly with their package manager). If this feature fails, then you should report this to your distribution's bug tracker.
Comment 2 George R. Goffe 2011-02-05 20:34:23 UTC
I'm using Fedora Core 14. Isn't this the bug tracker for Fedora Core 14?
Comment 3 George Kiagiadakis 2011-02-05 21:27:00 UTC
(In reply to comment #2)
> I'm using Fedora Core 14. Isn't this the bug tracker for Fedora Core 14?

No, this is the bugtracker for KDE, the desktop environment that you run on Fedora.
Comment 4 George R. Goffe 2011-02-06 01:25:31 UTC
George,

Are you guys working with RedHat/Fedora?

I'm beginning to see the need for some collaboration.

George...
Comment 5 George Kiagiadakis 2011-02-08 17:33:14 UTC
*** Bug 265787 has been marked as a duplicate of this bug. ***
Comment 6 Dario Andres 2011-02-12 18:31:14 UTC
[Comment from a bug triager]
We can't work with all the distributions (because there are many of them), but someone could report this issue at the Fedora bugtracker (https://bugzilla.redhat.com/index.cgi) so they get notified of the failing "install debug symbols" script
Comment 7 George R. Goffe 2011-02-12 18:48:47 UTC
Dario,

I have reported it... somewhat...

See:

Red Hat Bugzilla – Bug 675496
    

    
      While trying to report a ktorrent bug, Drkonqi refuses to generate a 

Regards,

George...

"It's not what you know that hurts you, It's what you know that ain't so." Wil Rogers

--- On Sat, 2/12/11, Dario Andres <andresbajotierra@gmail.com> wrote:

From: Dario Andres <andresbajotierra@gmail.com>
Subject: [Bug 265493] While trying to report a ktorrent bug, Drkonqi refuses to generate a report
To: grgoffe@yahoo.com
Date: Saturday, February 12, 2011, 9:31 AM

https://bugs.kde.org/show_bug.cgi?id=265493





--- Comment #6 from Dario Andres <andresbajotierra gmail com>  2011-02-12 18:31:14 ---
[Comment from a bug triager]
We can't work with all the distributions (because there are many of them), but
someone could report this issue at the Fedora bugtracker
(https://bugzilla.redhat.com/index.cgi) so they get notified of the failing
"install debug symbols" script