[kdelibs] [Bug 315009] New: Segfault after updating KDE to 4.10

Peter Huyoff peter.huyoff at gmx.de
Tue Feb 12 18:01:20 GMT 2013


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

            Bug ID: 315009
           Summary: Segfault after updating KDE to 4.10
    Classification: Unclassified
           Product: kdelibs
           Version: unspecified
          Platform: openSUSE RPMs
                OS: Linux
            Status: UNCONFIRMED
          Severity: crash
          Priority: NOR
         Component: kded
          Assignee: unassigned-bugs at kde.org
          Reporter: peter.huyoff at gmx.de

Application: kded4 ($Id$)
KDE Platform Version: 4.10.00 "release 546"
Qt Version: 4.8.4
Operating System: Linux 3.4.28-2.20-desktop x86_64
Distribution: "openSUSE 12.2 (x86_64)"

-- Information about the crash:
- Unusual behavior I noticed:

Sice updating KDE to 4.10, this segfault occures, when kde comes up after
login. Then the desktop environment runs stable, but jbidwatcher
(http://www.jbidwatcher.com/) must be started manually. Maybe this program
causes the segfault, when it starts automatically.

The crash can be reproduced every time.

-- Backtrace:
Application: KDE-Dienst (kdeinit4), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f9bbcb8b780 (LWP 2716))]

Thread 2 (Thread 0x7f9ba0718700 (LWP 2723)):
#0  0x00007f9bba1e014f in poll () from /lib64/libc.so.6
#1  0x00007f9bb6f2f684 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x00007f9bb6f2f7a4 in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x00007f9bbb830136 in QEventDispatcherGlib::processEvents
(this=0x7f9b980008f0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#4  0x00007f9bbb80094f in QEventLoop::processEvents
(this=this at entry=0x7f9ba0717d10, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007f9bbb800bd8 in QEventLoop::exec (this=0x7f9ba0717d10, flags=...) at
kernel/qeventloop.cpp:204
#6  0x00007f9bbb7030b0 in QThread::exec (this=<optimized out>) at
thread/qthread.cpp:542
#7  0x00007f9bbb7e10bf in QInotifyFileSystemWatcherEngine::run (this=0xbf20f0)
at io/qfilesystemwatcher_inotify.cpp:256
#8  0x00007f9bbb70608c in QThreadPrivate::start (arg=0xbf20f0) at
thread/qthread_unix.cpp:338
#9  0x00007f9bac231764 in ?? () from /usr/X11R6/lib64/libGL.so.1
#10 0x00007f9bbb46fe0e in start_thread () from /lib64/libpthread.so.0
#11 0x00007f9bba1e82cd in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f9bbcb8b780 (LWP 2716)):
[KCrash Handler]
#6  0x00007f9b96644d0e in PackageKit::Transaction::d_func (this=0x0) at
/usr/src/debug/PackageKit-Qt-0.8.7/src/transaction.h:1238
#7  0x00007f9b9663d5e8 in PackageKit::Transaction::error (this=0x0) at
/usr/src/debug/PackageKit-Qt-0.8.7/src/transaction.cpp:203
#8  0x00007f9b9687080c in Updater::checkForUpdates (this=0x9eb520,
systemReady=<optimized out>) at
/usr/src/debug/apper-0.8.0/apperd/Updater.cpp:100
#9  0x00007f9b9687238d in ApperdThread::updatesChanged (this=0xd9bc40) at
/usr/src/debug/apper-0.8.0/apperd/ApperdThread.cpp:263
#10 0x00007f9bbb8170ff in QMetaObject::activate (sender=0xdb9f70, m=<optimized
out>, local_signal_index=<optimized out>, argv=0x0) at kernel/qobject.cpp:3548
#11 0x00007f9bbb81ef8f in QSingleShotTimer::timerEvent (this=0xdb9f70) at
kernel/qtimer.cpp:317
#12 0x00007f9bbb81640c in QObject::event (this=0xdb9f70, e=<optimized out>) at
kernel/qobject.cpp:1165
#13 0x00007f9bba98f85c in QApplicationPrivate::notify_helper
(this=this at entry=0x959db0, receiver=receiver at entry=0xdb9f70,
e=e at entry=0x7fff6b9d58d0) at kernel/qapplication.cpp:4562
#14 0x00007f9bba993cda in QApplication::notify (this=0x7fff6b9d5dd0,
receiver=0xdb9f70, e=0x7fff6b9d58d0) at kernel/qapplication.cpp:4423
#15 0x00007f9bbc5a2a96 in KApplication::notify (this=0x7fff6b9d5dd0,
receiver=0xdb9f70, event=0x7fff6b9d58d0) at
/usr/src/debug/kdelibs-4.10.0/kdeui/kernel/kapplication.cpp:311
#16 0x00007f9bbb801bfe in QCoreApplication::notifyInternal
(this=0x7fff6b9d5dd0, receiver=0xdb9f70, event=0x7fff6b9d58d0) at
kernel/qcoreapplication.cpp:946
#17 0x00007f9bbb8329a1 in sendEvent (event=0x7fff6b9d58d0, receiver=<optimized
out>) at kernel/qcoreapplication.h:231
#18 QTimerInfoList::activateTimers (this=0x95c460) at
kernel/qeventdispatcher_unix.cpp:637
#19 0x00007f9bbb82fab4 in timerSourceDispatch (source=<optimized out>) at
kernel/qeventdispatcher_glib.cpp:186
#20 timerSourceDispatch (source=<optimized out>) at
kernel/qeventdispatcher_glib.cpp:180
#21 0x00007f9bbb82fad1 in idleTimerSourceDispatch (source=<optimized out>) at
kernel/qeventdispatcher_glib.cpp:233
#22 0x00007f9bb6f2f3b5 in g_main_context_dispatch () from
/usr/lib64/libglib-2.0.so.0
#23 0x00007f9bb6f2f6e8 in ?? () from /usr/lib64/libglib-2.0.so.0
#24 0x00007f9bb6f2f7a4 in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#25 0x00007f9bbb830116 in QEventDispatcherGlib::processEvents (this=0x817790,
flags=...) at kernel/qeventdispatcher_glib.cpp:424
#26 0x00007f9bbaa2fbee in QGuiEventDispatcherGlib::processEvents
(this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#27 0x00007f9bbb80094f in QEventLoop::processEvents
(this=this at entry=0x7fff6b9d5b50, flags=...) at kernel/qeventloop.cpp:149
#28 0x00007f9bbb800bd8 in QEventLoop::exec (this=0x7fff6b9d5b50, flags=...) at
kernel/qeventloop.cpp:204
#29 0x00007f9bbb805878 in QCoreApplication::exec () at
kernel/qcoreapplication.cpp:1218
#30 0x00007f9ba7a6ca30 in kdemain (argc=1, argv=0x8c4eb0) at
/usr/src/debug/kdelibs-4.10.0/kded/kded.cpp:924
#31 0x0000000000408856 in launch (argc=argc at entry=1, _name=_name at entry=0x40b246
"kded4", args=args at entry=0x0, cwd=cwd at entry=0x0, envc=envc at entry=0,
envs=<optimized out>, envs at entry=0x0, reset_env=reset_env at entry=false,
tty=tty at entry=0x0, avoid_loops=avoid_loops at entry=false,
startup_id_str=startup_id_str at entry=0x40b0c6 "0") at
/usr/src/debug/kdelibs-4.10.0/kinit/kinit.cpp:726
#32 0x0000000000405f99 in main (argc=4, argv=<optimized out>,
envp=0x7fff6b9d67c0) at /usr/src/debug/kdelibs-4.10.0/kinit/kinit.cpp:1841

Reported using DrKonqi

-- 
You are receiving this mail because:
You are the assignee for the bug.



More information about the Unassigned-bugs mailing list