Application: polkit-kde-authentication-agent-1 (0.99.0) KDE Platform Version: 4.6.2 (4.6.2) Qt Version: 4.7.2 Operating System: Linux 2.6.35.12-90.fc14.i686.PAE i686 Distribution: "Fedora release 14 (Laughlin)" -- Information about the crash: - What I was doing when the application crashed: logging out This bug is reproducible every logout This seems to have been happening since removal of the qt3 rpm package using YUM The crash can be reproduced every time. -- Backtrace: Application: PolicyKit1-KDE (polkit-kde-authentication-agent-1), signal: Segmentation fault [Current thread is 1 (Thread 0xb77719b0 (LWP 2759))] Thread 3 (Thread 0xb5773b70 (LWP 2800)): #0 g_main_context_poll (context=0x91a9170, block=1, dispatch=1, self=<value optimized out>) at gmain.c:3090 #1 g_main_context_iterate (context=0x91a9170, block=1, dispatch=1, self=<value optimized out>) at gmain.c:2775 #2 0x005bc04b in g_main_loop_run (loop=0x91a91f0) at gmain.c:2988 #3 0x00a96ed5 in gdbus_shared_thread_func (data=0x0) at gdbusprivate.c:277 #4 0x005e4bd0 in g_thread_create_proxy (data=0x91a9200) at gthread.c:1897 #5 0x003b1e99 in start_thread (arg=0xb5773b70) at pthread_create.c:301 #6 0x002c4d2e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:133 Thread 2 (Thread 0xb4c30b70 (LWP 3900)): #0 0x00173424 in __kernel_vsyscall () #1 0x003b93fb in read () at ../sysdeps/unix/syscall-template.S:82 #2 0x005bcf7d in read (data=0x0) at /usr/include/bits/unistd.h:45 #3 child_watch_helper_thread (data=0x0) at gmain.c:4011 #4 0x005e4bd0 in g_thread_create_proxy (data=0x9254e40) at gthread.c:1897 #5 0x003b1e99 in start_thread (arg=0xb4c30b70) at pthread_create.c:301 #6 0x002c4d2e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:133 Thread 1 (Thread 0xb77719b0 (LWP 2759)): [KCrash Handler] #7 g_type_check_instance_is_a (type_instance=0x90d7d70, iface_type=80) at gtype.c:3941 #8 0x006dbfad in g_object_unref (_object=0x90d7d70) at gobject.c:2629 #9 0x0206c420 in ?? () from /usr/lib/libpolkit-agent-1.so.0 #10 0x006dc13c in g_object_unref (_object=0x9271120) at gobject.c:2695 #11 0x00df1071 in PolkitQt1::Agent::Session::Private::~Private (this=0x92683a0, __in_chrg=<value optimized out>) at /usr/src/debug/polkit-qt-1-0.99.0/agent/polkitqt1-agent-session.cpp:49 #12 0x00df10b5 in PolkitQt1::Agent::Session::~Session (this=0x922f528, __in_chrg=<value optimized out>) at /usr/src/debug/polkit-qt-1-0.99.0/agent/polkitqt1-agent-session.cpp:77 #13 0x00df1113 in PolkitQt1::Agent::Session::~Session (this=0x922f528, __in_chrg=<value optimized out>) at /usr/src/debug/polkit-qt-1-0.99.0/agent/polkitqt1-agent-session.cpp:78 #14 0x024abf56 in qDeleteInEventHandler (o=0x922f528) at kernel/qobject.cpp:3986 #15 0x024ae800 in QObject::event (this=0x922f528, e=0x91603e0) at kernel/qobject.cpp:1200 #16 0x0596854c in QApplicationPrivate::notify_helper (this=0x90d2a10, receiver=0x922f528, e=0x91603e0) at kernel/qapplication.cpp:4462 #17 0x0596d252 in QApplication::notify (this=0xbf8cc60c, receiver=0x922f528, e=0x91603e0) at kernel/qapplication.cpp:3862 #18 0x06b2d4bb in KApplication::notify (this=0xbf8cc60c, receiver=0x922f528, event=0x91603e0) at /usr/src/debug/kdelibs-4.6.2/kdeui/kernel/kapplication.cpp:311 #19 0x02498f63 in QCoreApplication::notifyInternal (this=0xbf8cc60c, receiver=0x922f528, event=0x91603e0) at kernel/qcoreapplication.cpp:731 #20 0x0249ccb5 in sendEvent (receiver=0x0, event_type=52, data=0x90b56c0) at kernel/qcoreapplication.h:215 #21 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=52, data=0x90b56c0) at kernel/qcoreapplication.cpp:1372 #22 0x0249ce8e in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=52) at kernel/qcoreapplication.cpp:1265 #23 0x0249cfa1 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1015 #24 0x05966358 in QApplication::exec () at kernel/qapplication.cpp:3736 #25 0x080509f7 in _start () Possible duplicates by query: bug 270172, bug 269847, bug 268616, bug 267771, bug 266324. Reported using DrKonqi
[Comment from a bug triager] This issue is being tracked at bug 258916, merging. Thanks *** This bug has been marked as a duplicate of bug 258916 ***