Bug 256462 - crash at logout
Summary: crash at logout
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-11-09 18:52 UTC by Bruno Friedmann
Modified: 2010-11-09 18:59 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-11-09 18:52:13 UTC
Application: polkit-kde-authentication-agent-1 (0.1)
KDE Platform Version: 4.5.3 (KDE 4.5.3)
Qt Version: 4.7.0
Operating System: Linux 2.6.36-rc4-16-desktop x86_64
Distribution: "openSUSE 11.4 Milestone 3 of 6 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
To reproduce that, open a kde session with konsole, with a tabs and root console (not open). as user emit a su -l work, and ctrl+d
The pc was put in suspend to disk, and then wake-up.
reopen the kde session, do the su -l work and then close it by ctrl+d
let konsole open, and the root tab with the Password prompt
Now try to quit 
And you come here.

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 0x7f42a9058800 (LWP 3588))]

Thread 2 (Thread 0x7f4298519710 (LWP 3612)):
#0  __lll_lock_wait () at ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:136
#1  0x00007f42a4d7b2a4 in _L_lock_999 () from /lib64/libpthread.so.0
#2  0x00007f42a4d7b0ba in __pthread_mutex_lock (mutex=0x7f42a46f59e8) at pthread_mutex_lock.c:61
#3  0x00007f42a4434ee5 in g_datalist_id_set_data_full (datalist=0x786110, key_id=53, data=0x0, destroy_func=0) at gdataset.c:594
#4  0x00007f42a41c8eef in g_object_real_dispose (object=0x786100) at gobject.c:884
#5  0x00007f42a41c912a in g_object_unref (_object=0x786100) at gobject.c:2658
#6  0x00007f42a3f37984 in on_worker_message_about_to_be_sent (worker=<value optimized out>, message=0x6d5230, user_data=<value optimized out>) at gdbusconnection.c:2086
#7  0x00007f42a3f4a43d in _g_dbus_worker_emit_message_about_to_be_sent (worker=0x78c6a0) at gdbusprivate.c:518
#8  maybe_write_next_message (worker=0x78c6a0) at gdbusprivate.c:1294
#9  0x00007f42a3f4a533 in write_message_in_idle_cb (user_data=<value optimized out>) at gdbusprivate.c:1347
#10 0x00007f42a444ff43 in g_main_dispatch (context=0x783b10) at gmain.c:2149
#11 g_main_context_dispatch (context=0x783b10) at gmain.c:2702
#12 0x00007f42a4450720 in g_main_context_iterate (context=0x783b10, block=1, dispatch=1, self=<value optimized out>) at gmain.c:2780
#13 0x00007f42a4450da5 in g_main_loop_run (loop=0x744930) at gmain.c:2988
#14 0x00007f42a3f485b4 in gdbus_shared_thread_func (data=<value optimized out>) at gdbusprivate.c:277
#15 0x00007f42a4477676 in g_thread_create_proxy (data=0x76e950) at gthread.c:1897
#16 0x00007f42a4d78a4f in start_thread (arg=0x7f4298519710) at pthread_create.c:297
#17 0x00007f42a6b489fd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#18 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f42a9058800 (LWP 3588)):
[KCrash Handler]
#6  0x00007f42a4435078 in g_data_set_internal (datalist=0x63eeb0, key_id=53, data=0x0, destroy_func=0) at gdataset.c:325
#7  g_datalist_id_set_data_full (datalist=0x63eeb0, key_id=53, data=0x0, destroy_func=0) at gdataset.c:598
#8  0x00007f42a41c917a in g_object_unref (_object=0x63eea0) at gobject.c:2682
#9  0x00007f42a8692f80 in PolkitQt1::Agent::Listener::~Listener (this=0x6b0ee0, __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 254300, bug 254124, bug 254089, bug 252595.

Reported using DrKonqi
Comment 1 Christoph Feck 2010-11-09 18:59:40 UTC

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