Bug 268304 - PolicyKit crashed at shutdown
Summary: PolicyKit crashed at shutdown
Status: RESOLVED WORKSFORME
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:
: 262880 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-03-12 18:13 UTC by Unknown
Modified: 2018-11-29 04:49 UTC (History)
1 user (show)

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 Unknown 2011-03-12 18:13:51 UTC
Application: polkit-kde-authentication-agent-1 (0.99.0)
KDE Platform Version: 4.6.1 (4.6.1)
Qt Version: 4.7.2
Operating System: Linux 2.6.37.1-1.2-desktop x86_64
Distribution: "openSUSE 11.4 (x86_64)"

-- Information about the crash:
The system was shutting down when that application crashed.

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

Thread 3 (Thread 0x7f6db0748700 (LWP 3617)):
#0  __lll_lock_wait () at ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:136
#1  0x00007f6dbef34294 in _L_lock_999 () from /lib64/libpthread.so.0
#2  0x00007f6dbef340aa in __pthread_mutex_lock (mutex=0x6ffd50) at pthread_mutex_lock.c:61
#3  0x00007f6dbc4c60fd in on_worker_message_about_to_be_sent (worker=<value optimized out>, message=0x9d0d90, user_data=0x771100) at gdbusconnection.c:2176
#4  0x00007f6dbc4db00d in _g_dbus_worker_emit_message_about_to_be_sent (worker=0x6f9a30) at gdbusprivate.c:518
#5  maybe_write_next_message (worker=0x6f9a30) at gdbusprivate.c:1303
#6  0x00007f6dbc4db115 in write_message_in_idle_cb (user_data=<value optimized out>) at gdbusprivate.c:1356
#7  0x00007f6dbc9e4bd3 in g_main_dispatch (context=0x6f62b0) at gmain.c:2440
#8  g_main_context_dispatch (context=0x6f62b0) at gmain.c:3013
#9  0x00007f6dbc9e53b0 in g_main_context_iterate (context=0x6f62b0, block=1, dispatch=1, self=<value optimized out>) at gmain.c:3091
#10 0x00007f6dbc9e5a35 in g_main_loop_run (loop=0x6f6290) at gmain.c:3299
#11 0x00007f6dbc4d9244 in gdbus_shared_thread_func (data=<value optimized out>) at gdbusprivate.c:276
#12 0x00007f6dbca0c466 in g_thread_create_proxy (data=0x6f6390) at gthread.c:1897
#13 0x00007f6dbef31a3f in start_thread (arg=0x7f6db0748700) at pthread_create.c:297
#14 0x00007f6dbf21b67d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#15 0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7f6dafef1700 (LWP 9641)):
#0  0x00007f6dbf20e0ad in read () at ../sysdeps/unix/syscall-template.S:82
#1  0x00007f6dbc9e6aab in read (data=<value optimized out>) at /usr/include/bits/unistd.h:45
#2  child_watch_helper_thread (data=<value optimized out>) at gmain.c:4293
#3  0x00007f6dbca0c466 in g_thread_create_proxy (data=0x8c8550) at gthread.c:1897
#4  0x00007f6dbef31a3f in start_thread (arg=0x7f6dafef1700) at pthread_create.c:297
#5  0x00007f6dbf21b67d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#6  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f6dc1b18820 (LWP 3616)):
[KCrash Handler]
#6  magazine_chain_pop_head (mem_size=32) at gslice.c:492
#7  thread_memory_magazine1_alloc (mem_size=32) at gslice.c:795
#8  g_slice_alloc (mem_size=32) at gslice.c:833
#9  0x00007f6dbc9c9255 in g_data_set_internal (datalist=0x9d1290, key_id=56, data=0x641a20, destroy_func=0x7f6dbc75e350 <g_object_notify_queue_free>) at gdataset.c:401
#10 g_datalist_id_set_data_full (datalist=0x9d1290, key_id=56, data=0x641a20, destroy_func=0x7f6dbc75e350 <g_object_notify_queue_free>) at gdataset.c:598
#11 0x00007f6dbc760862 in g_object_notify_queue_freeze (object=0x9d1280, property_name=<value optimized out>) at gobjectnotifyqueue.c:77
#12 g_object_notify_by_spec_internal (object=0x9d1280, property_name=<value optimized out>) at gobject.c:981
#13 g_object_notify (object=0x9d1280, property_name=<value optimized out>) at gobject.c:1024
#14 0x00007f6dbc4c79a7 in g_dbus_connection_send_message_unlocked (connection=0x771100, message=0x9d1280, flags=<value optimized out>, out_serial=0x0, error=<value optimized out>) at gdbusconnection.c:1458
#15 0x00007f6dbc4c7cfb in remove_match_rule (connection=0x771100, subscription_id=2, out_removed_subscribers=0x6f7e20) at gdbusconnection.c:3058
#16 unsubscribe_id_internal (connection=0x771100, subscription_id=2, out_removed_subscribers=0x6f7e20) at gdbusconnection.c:3287
#17 0x00007f6dbc4cd21d in g_dbus_connection_signal_unsubscribe (connection=0x771100, subscription_id=2) at gdbusconnection.c:3322
#18 0x00007f6dbc4d71f9 in g_dbus_proxy_finalize (object=0x741050) at gdbusproxy.c:156
#19 0x00007f6dbc75e114 in g_object_unref (_object=0x741050) at gobject.c:2734
#20 0x00007f6dbcc9b4ca in ?? () from /usr/lib64/libpolkit-gobject-1.so.0
#21 0x00007f6dbc75e114 in g_object_unref (_object=0x70d580) at gobject.c:2734
#22 0x00007f6dc123824b in PolkitQt1::Authority::~Authority() () from /usr/lib64/libpolkit-qt-core-1.so.1
#23 0x00007f6dc1238299 in PolkitQt1::Authority::~Authority() () from /usr/lib64/libpolkit-qt-core-1.so.1
#24 0x00007f6dc123c46a in QGlobalStaticDeleter<PolkitQt1::AuthorityHelper>::~QGlobalStaticDeleter() () from /usr/lib64/libpolkit-qt-core-1.so.1
#25 0x00007f6dbf17d5a1 in __run_exit_handlers (status=0, listp=0x7f6dbf4af4a8, run_list_atexit=true) at exit.c:78
#26 0x00007f6dbf17d5f5 in exit (status=80) at exit.c:100
#27 0x00007f6dbf166c04 in __libc_start_main (main=0x40ac00 <_start+8240>, argc=1, ubp_av=0x7fff9f55efc8, init=<value optimized out>, fini=<value optimized out>, rtld_fini=<value optimized out>, stack_end=0x7fff9f55efb8) at libc-start.c:258
#28 0x0000000000408bf9 in _start ()

Possible duplicates by query: bug 254300.

Reported using DrKonqi
Comment 1 Lamarque V. Souza 2011-05-17 23:22:18 UTC
*** Bug 262880 has been marked as a duplicate of this bug. ***
Comment 2 Andrew Crouthamel 2018-10-29 22:35:28 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Bug Janitor Service 2018-11-13 14:31:11 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Bug Janitor Service 2018-11-29 04:49:33 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!