Summary: | KTorrent segfault [invalid QAbstractSocketEngine::state, QNativeSocketEngine::waitForReadOrWrite, ..., KIO::SocketConnectionBackend::sendCommand, KIO::Connection::sendnow] | ||
---|---|---|---|
Product: | [Unmaintained] kio | Reporter: | George R. Goffe <grgoffe> |
Component: | general | Assignee: | David Faure <faure> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | andresbajotierra, Daniel, gentoo, grgoffe, joris.guisson |
Priority: | NOR | ||
Version: | 4.5 | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi New crash information added by DrKonqi |
Description
George R. Goffe
2011-02-05 10:25:12 UTC
This is a bug in KIO, reassigning to kdelibs Created attachment 56994 [details]
New crash information added by DrKonqi
ktorrent (4.1beta1) on KDE Platform 4.5.5 (KDE 4.5.5) using Qt 4.7.1
I was just doing what ktorrent users do, downloading data. This is a bug in ktorrent-4.1beta1 and seems to happen almost every time I try to use ktorrent. Reverting back to 4.0.5 of ktorrent seems to resolve the problem temporarily but the problem re-appears. Update back to the beta seems to resolve the problem temporarily but then it re-appears.
-- Backtrace (Reduced):
#7 QAbstractSocketEngine::state (this=0x0) at socket/qabstractsocketengine.cpp:186
#8 0x03fb8fab in QNativeSocketEngine::waitForReadOrWrite (this=0x126c71a0, readyToRead=0xbfc4bedf, readyToWrite=0xbfc4bede, checkRead=true, checkWrite=true, msecs=-1, timedOut=0x0) at socket/qnativesocketengine.cpp:988
#9 0x03fcb427 in QAbstractSocket::waitForBytesWritten (this=0x122fa548, msecs=-1) at socket/qabstractsocket.cpp:1894
#10 0x033efa9b in KIO::SocketConnectionBackend::sendCommand (this=0x1272c7b0, task=...) at /usr/src/debug/kdelibs-4.5.5/kio/kio/connection.cpp:294
#11 0x033f0d2b in KIO::Connection::sendnow (this=0xfb2e818, _cmd=85, data=...) at /usr/src/debug/kdelibs-4.5.5/kio/kio/connection.cpp:505
Created attachment 57155 [details]
New crash information added by DrKonqi
ktorrent (4.1beta1) on KDE Platform 4.5.5 (KDE 4.5.5) using Qt 4.7.1
- What I was doing when the application crashed:
First invocation of ktorrent rc1, various popups relating to "already downloading" and what looks like the popup you get when you first start a torrent, including the duplicate popup for the same torrent by the way.
-- Backtrace (Reduced):
#7 QAbstractSocketEngine::state (this=0x0) at socket/qabstractsocketengine.cpp:186
#8 0x03fb8fab in QNativeSocketEngine::waitForReadOrWrite (this=0x1171c748, readyToRead=0xbff9bf1f, readyToWrite=0xbff9bf1e, checkRead=true, checkWrite=true, msecs=-1, timedOut=0x0) at socket/qnativesocketengine.cpp:988
#9 0x03fcb427 in QAbstractSocket::waitForBytesWritten (this=0xebd8888, msecs=-1) at socket/qabstractsocket.cpp:1894
#10 0x05531a9b in KIO::SocketConnectionBackend::sendCommand (this=0xed89348, task=...) at /usr/src/debug/kdelibs-4.5.5/kio/kio/connection.cpp:294
#11 0x05532d2b in KIO::Connection::sendnow (this=0x1182feb0, _cmd=85, data=...) at /usr/src/debug/kdelibs-4.5.5/kio/kio/connection.cpp:505
[Comment from a bug triager] Bug 243512 seems also related to this crash. Dario, I must apologize for making extra work for you. This is a dup of 266122. The developer and I are working this one. I think there's a bug with Drkonqi but they don't want to accept the bug, saying that it belongs to Fedora 14 group. Drkonqi has some usabilty issues. It invites the user to install debuginfo pkgs, spawns a konsole to do this but any output from this process disappears before it can be recorded and then returns to the debuginfo invitation... claiming that the backtrace is invalid. This seems like a catch 22. backtrace is invalid; install debuginfo pkgs;backtrace is invalid... They don't seem to be very receptive to suggestions either. Maybe I'm doing this the wrong way? George... [Comment from a bug triager] Mh, may be the root cause is related to the one in bug 266122; but the backtrace is not the same; so I can't be sure I see you are referring to the DrKonqi bug 265493. As George already explained; DrKonqi "install debug symbol" feature only calls a script; and every distribution should implement that script. That is the cause that bug is considered to be on Fedora side. I'm going to add a comment on that report Dario, THANK you for that explanation... It was the missing piece. 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 265492] KTorrent segfault [invalid QAbstractSocketEngine::state, QNativeSocketEngine::waitForReadOrWrite, ..., KIO::SocketConnectionBackend::sendCommand, KIO::Connection::sendnow] To: grgoffe@yahoo.com Date: Saturday, February 12, 2011, 9:28 AM https://bugs.kde.org/show_bug.cgi?id=265492 --- Comment #6 from Dario Andres <andresbajotierra gmail com> 2011-02-12 18:28:51 --- [Comment from a bug triager] Mh, may be the root cause is related to the one in bug 266122; but the backtrace is not the same; so I can't be sure I see you are referring to the DrKonqi bug 265493. As George already explained; DrKonqi "install debug symbol" feature only calls a script; and every distribution should implement that script. That is the cause that bug is considered to be on Fedora side. I'm going to add a comment on that report Created attachment 58387 [details]
New crash information added by DrKonqi
ktorrent (4.1.0) on KDE Platform 4.6.1 (4.6.1) using Qt 4.7.1
This crash is for ktorrent-4.1.0-1.fc14.i686 but was present with the beta1 version compiled on this system.
This crash happened after about 5 - 10 minutes of execution of ktorrent. I had done nothing much earlier except move 3 torrents to another filesystem. This appears to have worked successfully. The moving of data has not been present during other crashes.
I will start ktorrent again with your suggested gdb options and append the output of the bt command and the where command.
Do you need other info?
-- Backtrace (Reduced):
#7 QAbstractSocketEngine::state (this=0x0) at socket/qabstractsocketengine.cpp:186
#8 0x00c92fab in QNativeSocketEngine::waitForReadOrWrite (this=0xa7c3a58, readyToRead=0xbff07a0f, readyToWrite=0xbff07a0e, checkRead=true, checkWrite=true, msecs=-1, timedOut=0x0) at socket/qnativesocketengine.cpp:988
#9 0x00ca5427 in QAbstractSocket::waitForBytesWritten (this=0xa6ae088, msecs=-1) at socket/qabstractsocket.cpp:1894
#10 0x0618825b in KIO::SocketConnectionBackend::sendCommand (this=0xaa07688, task=...) at /usr/src/debug/kdelibs-4.6.1/kio/kio/connection.cpp:294
#11 0x061894eb in KIO::Connection::sendnow (this=0xaa1e278, _cmd=85, data=...) at /usr/src/debug/kdelibs-4.6.1/kio/kio/connection.cpp:505
*** Bug 272218 has been marked as a duplicate of this bug. *** *** Bug 275877 has been marked as a duplicate of this bug. *** *** Bug 275928 has been marked as a duplicate of this bug. *** *** This bug has been marked as a duplicate of bug 274544 *** *** Bug 222780 has been marked as a duplicate of this bug. *** |