[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 297671] ktorrent UI freezes, on start of app. and during download of torrents
From:       Michael Pyne <mpyne () kde ! org>
Date:       2012-04-09 22:53:07
Message-ID: bug-297671-17878-y8LoEWIv0z () http ! bugs ! kde ! org/
[Download RAW message or body]

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

Michael Pyne <mpyne@kde.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
                 CC|                            |mpyne@kde.org
     Ever confirmed|0                           |1

--- Comment #3 from Michael Pyne <mpyne@kde.org> ---
I can confirm this bug, and that it affects more than just ktorrent. It's also
tremendously annoying, why does IPC have to be so much of a problem with this
major release of KDE? I'll add backtraces as I can, but the common thread I've
seen has been a backtrace like:

#0  0x00007fbee63643e8 in poll () from /lib64/libc.so.6
#1  0x00007fbedac1ddca in socket_do_iteration () from /usr/lib64/libdbus-1.so.3
#2  0x00007fbedac1c47f in _dbus_transport_do_iteration ()
   from /usr/lib64/libdbus-1.so.3
#3  0x00007fbedac09693 in _dbus_connection_do_iteration_unlocked ()
   from /usr/lib64/libdbus-1.so.3
#4  0x00007fbedac0aeed in _dbus_connection_block_pending_call ()
   from /usr/lib64/libdbus-1.so.3
#5  0x00007fbedac09fcd in dbus_connection_send_with_reply_and_block ()
   from /usr/lib64/libdbus-1.so.3
#6  0x00007fbee7be1e2d in q_dbus_connection_send_with_reply_and_block (
    error=0x7fff0bf18a30, timeout_milliseconds=-1, message=0x24a0ec0, 
    connection=0x21908b0) at /kdesvn/src/qt/src/dbus/qdbus_symbols_p.h:135
#7  QDBusConnectionPrivate::sendWithReply (this=0x218c520, message=..., 
    sendMode=<optimized out>, timeout=-1)
    at /kdesvn/src/qt/src/dbus/qdbusintegrator.cpp:1904
#8  0x00007fbee7bcc95b in QDBusConnection::call (this=0x2b7a928, message=..., 
    mode=<optimized out>, timeout=<optimized out>)
    at /kdesvn/src/qt/src/dbus/qdbusconnection.cpp:597
#9  0x00007fbee7bf0034 in QDBusAbstractInterface::callWithArgumentList (
    this=0x2b6fc58, mode=QDBus::Block, method=..., args=...)
    at /kdesvn/src/qt/src/dbus/qdbusabstractinterface.cpp:468

So far I've seen it affecting Kontact/Akonadi, Phonon (as used by JuK), the
logout dialog and konqueror (or KIO). This bug occurs with kdelibs git-master
(perhaps it will be a simple as downgrading kdelibs to 4.8.1 to fix though?).
DBus 1.4.18 and 1.4.20 are both affected in my testing.

Example error output for Phonon:
juk(5599) Phonon::KdePlatformPlugin::createBackend: using backend:  "GStreamer"
juk(5599)/phonon (KDE plugin): QDBusError("org.freedesktop.DBus.Error.NoReply",
"Did not receive a reply. Possible causes include: the remote application did
not send a reply, the message bus security policy blocked the reply, the reply
timeout expired, or the network connection was broken.") 
juk(5599)/phonon (KDE plugin): QDBusError("org.freedesktop.DBus.Error.NoReply",
"Did not receive a reply. Possible causes include: the remote application did
not send a reply, the message bus security policy blocked the reply, the reply
timeout expired, or the network connection was broken.") 
juk(5599)/phonon (KDE plugin): QDBusError("org.freedesktop.DBus.Error.NoReply",
"Did not receive a reply. Possible causes include: the remote application did
not send a reply, the message bus security policy blocked the reply, the reply
timeout expired, or the network connection was broken.") 

As best I can tell, the DBus session bus remains active and responsive
throughout, but calls seemingly randomly hang.

-- 
You are receiving this mail because:
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]