Bug 222305 - Frequent crash of kded4
Summary: Frequent crash of kded4
Status: RESOLVED DUPLICATE of bug 220190
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR crash
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-11 23:54 UTC by Loïc Grenié
Modified: 2010-01-12 00:12 UTC (History)
0 users

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 Loïc Grenié 2010-01-11 23:54:51 UTC
Version:            (using KDE 4.3.4)
Compiler:          gcc (Debian 4.4.2-3) 4.4.2 
OS:                Linux
Installed from:    Debian testing/unstable Packages

I see frequent crashes of kded4. I've looked twice and both times it crashed in the position described by this bug report.

 -- Backtrace:
Application: Démon de KDE (kdeinit4), signal: Segmentation fault
-nw -n -batch -x /tmp/kde-grenies0URow/drkonqicF5440.tmp -p 32136
The current source language is "auto; currently c".
[KCrash Handler]
#5  0x00007f482d0c9cbe in QtPrivate::QStringList_contains (that=0x7fff80120320, str=..., cs=Qt::CaseSensitive) at tools/qstringlist.cpp:318
#6  0x00007f481e715a76 in HalPower::brightness(QString const&) () from /usr/lib/kde4/solid_hal_power.so
#7  0x00007f481f5beca4 in Solid::Control::PowerManager::brightness(QString const&) () from /usr/lib/libsolidcontrol.so.4
#8  0x00007f481eb3ced1 in PowerDevilDaemon::poll(int) () from /usr/lib/kde4/kded_powerdevil.so
#9  0x00007f481eb3dc5c in PowerDevilDaemon::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/kde4/kded_powerdevil.so
#10 0x00007f482d176df2 in QMetaObject::activate (sender=0x832970, from_signal_index=<value optimized out>, to_signal_index=36, argv=0x0) at kernel/qobject.cpp:3112
#11 0x00007f481eb3f831 in ?? () from /usr/lib/kde4/kded_powerdevil.so
#12 0x00007f481eb3f89e in ?? () from /usr/lib/kde4/kded_powerdevil.so
#13 0x00007f482bd392d6 in KAppX11HackWidget::publicx11Event (this=<value optimized out>, _event=0x7fff80122390) at ../../kdeui/kernel/kapplication.cpp:900
#14 KApplication::x11EventFilter (this=<value optimized out>, _event=0x7fff80122390) at ../../kdeui/kernel/kapplication.cpp:950
#15 0x00007f482b13d39f in qt_x11EventFilter (ev=0x7fff80122390) at kernel/qapplication_x11.cpp:377
#16 0x00007f482b1504c1 in QApplication::x11ProcessEvent (this=0x7fff80122770, event=0x7fff80122390) at kernel/qapplication_x11.cpp:3273
#17 0x00007f482b17976c in x11EventSourceDispatch (s=0x6b6120, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#18 0x00007f4829ff913a in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#19 0x00007f4829ffc998 in ?? () from /lib/libglib-2.0.so.0
#20 0x00007f4829ffcb4c in g_main_context_iteration () from /lib/libglib-2.0.so.0
#21 0x00007f482d18a39c in QEventDispatcherGlib::processEvents (this=0x611770, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:407
#22 0x00007f482b178f1f in QGuiEventDispatcherGlib::processEvents (this=0x8c15f0, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#23 0x00007f482d160562 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#24 0x00007f482d160934 in QEventLoop::exec (this=0x7fff801226c0, flags=...) at kernel/qeventloop.cpp:201
#25 0x00007f482d162ba4 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#26 0x00007f4821d8fc3b in kdemain (argc=<value optimized out>, argv=<value optimized out>) at ../../kded/kded.cpp:936
#27 0x0000000000406e9e in launch (argc=1, _name=<value optimized out>, args=<value optimized out>, cwd=<value optimized out>, envc=0, envs=<value optimized out>, reset_env=false, tty=0x0, 
    avoid_loops=false, startup_id_str=0x40a057 "0") at ../../kinit/kinit.cpp:677
#28 0x0000000000408a6a in main (argc=<value optimized out>, argv=<value optimized out>, envp=<value optimized out>) at ../../kinit/kinit.cpp:1740
Comment 1 Christoph Feck 2010-01-12 00:12:28 UTC

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