Bug 284497 - Crashed on reboot
Summary: Crashed on reboot
Status: RESOLVED DUPLICATE of bug 258916
Alias: None
Product: policykit-kde-agent-1
Classification: Plasma
Component: polkit-kde-authentication-agent-1 (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Jaroslav Reznik
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-19 19:41 UTC by Patrick Carson
Modified: 2011-10-20 18:28 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 Patrick Carson 2011-10-19 19:41:32 UTC
Application: polkit-kde-authentication-agent-1 (0.99.0)
KDE Platform Version: 4.6.00 (4.6.0) "release 6"
Qt Version: 4.7.1
Operating System: Linux 2.6.37.1-1.2-desktop x86_64
Distribution: "openSUSE 11.4 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
I was Rebooting after installing critical  updates on Suse Linux

-- Backtrace:
Application: PolicyKit1-KDE (polkit-kde-authentication-agent-1), signal: Segmentation fault
[Current thread is 1 (Thread 0x7f3c506a9800 (LWP 13079))]

Thread 3 (Thread 0x7f3c3f66d700 (LWP 13103)):
#0  0x00007f3c4bd7b0a4 in pthread_mutex_lock () from /lib64/libpthread.so.0
#1  0x00007f3c4b654876 in g_main_context_check () from /lib64/libglib-2.0.so.0
#2  0x00007f3c4b655132 in ?? () from /lib64/libglib-2.0.so.0
#3  0x00007f3c4b655a35 in g_main_loop_run () from /lib64/libglib-2.0.so.0
#4  0x00007f3c4b149244 in ?? () from /lib64/libgio-2.0.so.0
#5  0x00007f3c3f66d700 in ?? ()
#6  0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7f3c3ee00700 (LWP 7023)):
#0  0x00007f3c4bd7c67e in __pthread_mutex_unlock_usercnt () from /lib64/libpthread.so.0
#1  0x00007f3c4b656af0 in ?? () from /lib64/libglib-2.0.so.0
#2  0x00007f3c4b67c466 in ?? () from /lib64/libglib-2.0.so.0
#3  0x00007f3c4bd78a3f in start_thread () from /lib64/libpthread.so.0
#4  0x00007f3c4dc6967d in clone () from /lib64/libc.so.6
#5  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f3c506a9800 (LWP 13079)):
[KCrash Handler]
#6  g_type_check_instance_is_a (type_instance=0x793aa0, iface_type=<value optimized out>) at gtype.c:3957
#7  0x00007f3c4b3cdfcb in g_object_unref (_object=0x793aa0) at gobject.c:2668
#8  0x00007f3c4ac7475b in polkit_agent_session_finalize (object=0x772ea0) at polkitagentsession.c:127
#9  0x00007f3c4b3ce114 in g_object_unref (_object=0x772ea0) at gobject.c:2734
#10 0x00007f3c4fa59db4 in PolkitQt1::Agent::Session::~Session (this=0x7d0260, __in_chrg=<value optimized out>) at /usr/src/debug/polkit-qt-1-0.99.1/agent/polkitqt1-agent-session.cpp:77
#11 0x00007f3c4fa59df9 in PolkitQt1::Agent::Session::~Session (this=0x7d0260, __in_chrg=<value optimized out>) at /usr/src/debug/polkit-qt-1-0.99.1/agent/polkitqt1-agent-session.cpp:78
#12 0x00007f3c4f01da98 in QObject::event (this=0x7d0260, e=<value optimized out>) at kernel/qobject.cpp:1181
#13 0x00007f3c4e3d5d14 in QApplicationPrivate::notify_helper (this=0x63f300, receiver=0x7d0260, e=0x6b5210) at kernel/qapplication.cpp:4445
#14 0x00007f3c4e3de22a in QApplication::notify (this=<value optimized out>, receiver=0x7d0260, e=0x6b5210) at kernel/qapplication.cpp:4324
#15 0x00007f3c500089e6 in KApplication::notify (this=0x7fff18b52e50, receiver=0x7d0260, event=0x6b5210) at /usr/src/debug/kdelibs-4.6.0/kdeui/kernel/kapplication.cpp:311
#16 0x00007f3c4f009bfc in QCoreApplication::notifyInternal (this=0x7fff18b52e50, receiver=0x7d0260, event=0x6b5210) at kernel/qcoreapplication.cpp:733
#17 0x00007f3c4f00d3f5 in relock (receiver=0x0, event_type=52, data=0x615590) at ../../src/corelib/thread/qmutex.h:121
#18 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=52, data=0x615590) at kernel/qcoreapplication.cpp:1390
#19 0x00007f3c4f00d6ee in QCoreApplication::exec () at kernel/qcoreapplication.cpp:997
#20 0x000000000040af0d in _start ()

Possible duplicates by query: bug 284399, bug 283702, bug 283007, bug 282937, bug 282352.

Reported using DrKonqi
Comment 1 Christoph Feck 2011-10-20 18:28:43 UTC

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