Bug 254124 - Closing the kde session : kded crash
Summary: Closing the kde session : kded crash
Status: RESOLVED DUPLICATE of bug 248636
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-14 10:12 UTC by Bruno Friedmann
Modified: 2010-10-14 15:55 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Bruno Friedmann 2010-10-14 10:12:37 UTC
Application: polkit-kde-authentication-agent-1 (0.1)
KDE Platform Version: 4.5.2 (KDE 4.5.2)
Qt Version: 4.7.0
Operating System: Linux 2.6.36-rc4-16-desktop x86_64
Distribution: "openSUSE 11.4 Milestone 2 of 6 (x86_64)"

-- Information about the crash:
During this kde session, I change two times my network connection. and launch 2 differents vpn connections.
Just before closing, I've runned the system settings, to adjust global keyboard shortcut. ( klipper plasmoid doesn't shown actually ).
I close klipper, asking to be open at next start
Launch close session

The crash can be reproduced some of the time.

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

Thread 2 (Thread 0x7fa0134bb710 (LWP 3661)):
#0  __lll_lock_wait () at ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:136
#1  0x00007fa01fbcc2a4 in _L_lock_999 () from /lib64/libpthread.so.0
#2  0x00007fa01fbcc0ba in __pthread_mutex_lock (mutex=0x7fa01f546f28) at pthread_mutex_lock.c:61
#3  0x00007fa01f2865f5 in g_datalist_id_set_data_full (datalist=0x7b2d90, key_id=53, data=0x0, destroy_func=0) at gdataset.c:594
#4  0x00007fa01f019b7f in g_object_real_dispose (object=0x7b2d80) at gobject.c:884
#5  0x00007fa01f019dab in g_object_unref (_object=0x7b2d80) at gobject.c:2658
#6  0x00007fa01ed9b4d3 in read_with_control_data_free (data=0x690cb0) at gdbusprivate.c:123
#7  0x00007fa01f29dc8e in g_source_callback_unref (cb_data=<value optimized out>) at gmain.c:1182
#8  0x00007fa01f29e12a in g_source_destroy_internal (source=0x73d580, context=0x62ec30, have_lock=1) at gmain.c:961
#9  0x00007fa01f2a1751 in g_main_dispatch (context=0x62ec30) at gmain.c:2174
#10 g_main_context_dispatch (context=0x62ec30) at gmain.c:2702
#11 0x00007fa01f2a1ec0 in g_main_context_iterate (context=0x62ec30, block=1, dispatch=1, self=<value optimized out>) at gmain.c:2780
#12 0x00007fa01f2a2545 in g_main_loop_run (loop=0x62ed10) at gmain.c:2988
#13 0x00007fa01ed9b634 in gdbus_shared_thread_func (data=<value optimized out>) at gdbusprivate.c:277
#14 0x00007fa01f2c8df6 in g_thread_create_proxy (data=0x7ac340) at gthread.c:1897
#15 0x00007fa01fbc9a4f in start_thread (arg=0x7fa0134bb710) at pthread_create.c:297
#16 0x00007fa021999a0d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#17 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7fa023ead800 (LWP 3652)):
[KCrash Handler]
#6  0x00007fa01f286788 in g_data_set_internal (datalist=0x63d8b0, key_id=53, data=0x0, destroy_func=0) at gdataset.c:325
#7  g_datalist_id_set_data_full (datalist=0x63d8b0, key_id=53, data=0x0, destroy_func=0) at gdataset.c:598
#8  0x00007fa01f019e22 in g_object_unref (_object=0x63d8a0) at gobject.c:2682
#9  0x00007fa0234e4f80 in PolkitQt1::Agent::Listener::~Listener (this=0x649850, __in_chrg=<value optimized out>) at /usr/src/debug/polkit-qt-1-0.96.1/agent/polkitqt1-agent-listener.cpp:69
#10 0x0000000000408aa9 in _start ()

This bug may be a duplicate of or related to bug 248636.

Possible duplicates by query: bug 254089, bug 252595.

Reported using DrKonqi
Comment 1 Christoph Feck 2010-10-14 15:55:14 UTC

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