[Bug 274578] New: kded4 busy loop after suspend on ram resume
Daniele Depetrini
daniele.depetrini at criticalpath.net
Tue May 31 08:10:02 BST 2011
https://bugs.kde.org/show_bug.cgi?id=274578
Summary: kded4 busy loop after suspend on ram resume
Product: kde
Version: unspecified
Platform: Ubuntu Packages
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
AssignedTo: unassigned-bugs at kde.org
ReportedBy: daniele.depetrini at criticalpath.net
Version: unspecified (using KDE 4.6.2)
OS: Linux
After resuming a session from "suspend on memory", if connected to network
before the connection, kded4 consume 100% CPU (one core). I've generated a core
file with gcore and the looping thread is always showing a backtrace like:
Thread 3 (Thread 1930):
#0 0x00007ffe295fb078 in rtnl_link_get_ifindex at plt () from
/usr/lib/ntrack/modules/ntrack-libnl1.so
#1 0x00007ffe295fb4ee in ?? () from /usr/lib/ntrack/modules/ntrack-libnl1.so
#2 0x00007ffe295fba9d in _ntrack_arch_process_data () from
/usr/lib/ntrack/modules/ntrack-libnl1.so
#3 0x00007ffe29a07ecb in QNtrack::socketActivated(int) () from
/usr/lib/libntrack-qt4.so.1
#4 0x00007ffe29a0822a in QNtrack::qt_metacall(QMetaObject::Call, int, void**)
() from /usr/lib/libntrack-qt4.so.1
#5 0x00007ffe48d145f8 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () from /usr/lib/libQtCore.so.4
#6 0x00007ffe48d5bb7e in QSocketNotifier::activated(int) () from
/usr/lib/libQtCore.so.4
#7 0x00007ffe48d19f4b in QSocketNotifier::event(QEvent*) () from
/usr/lib/libQtCore.so.4
#8 0x00007ffe480c09e4 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/libQtGui.so.4
#9 0x00007ffe480c53aa in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/libQtGui.so.4
#10 0x00007ffe49a7a866 in KApplication::notify(QObject*, QEvent*) () from
/usr/lib/libkdeui.so.5
#11 0x00007ffe48cff49c in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib/libQtCore.so.4
#12 0x00007ffe48d29da9 in ?? () from /usr/lib/libQtCore.so.4
#13 0x00007ffe44d5cbcd in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#14 0x00007ffe44d5d3a8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#15 0x00007ffe44d5d639 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#16 0x00007ffe48d2a3ef in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
from /usr/lib/libQtCore.so.4
#17 0x00007ffe48167dfe in ?? () from /usr/lib/libQtGui.so.4
#18 0x00007ffe48cfe882 in
QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from
/usr/lib/libQtCore.so.4
#19 0x00007ffe48cfeabc in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from
/usr/lib/libQtCore.so.4
#20 0x00007ffe48d02ecb in QCoreApplication::exec() () from
/usr/lib/libQtCore.so.4
#21 0x00007ffe394fd135 in kdemain () from
/usr/lib/kde4/libkdeinit/libkdeinit4_kded4.so
#22 0x0000000000406dd3 in _start ()
I may supply full cores if needed.
Daniele.
Reproducible: Always
Steps to Reproduce:
Connect on network, both wired and wireless. Suspend on ram. Resume the PC.
Actual Results:
most kde functionalities not working. kded4 uses 100% CPU
Expected Results:
Works like a charm :-)
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the Unassigned-bugs
mailing list