Bug 248636

Summary: Crash when logging out
Product: [Plasma] policykit-kde-agent-1 Reporter: MartinG <gronslet>
Component: polkit-kde-authentication-agent-1Assignee: Jaroslav Reznik <jreznik>
Status: RESOLVED WORKSFORME    
Severity: crash CC: alex.merry, artem.goncharov, arvidjaar, balcaen.john, bruno, cacouret, Carth_Onasi, g111, ian.fardoe, jarin.franek, matthias.nagel, olivier.lahaye1, rad.n, sven.burmeister, thomasbelvin, tubits, valir
Priority: NOR Keywords: triaged
Version: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: Crash output reproduced with patched polkit-qt-1

Description MartinG 2010-08-21 22:17:31 UTC
Application: polkit-kde-authentication-agent-1 (0.1)
KDE Platform Version: 4.5.00 (KDE 4.5.0)
Qt Version: 4.7.0
Operating System: Linux 2.6.36-0.0.rc0.git1.fc15.x86_64 x86_64
Distribution: "Fedora release 15 (Finian)"

-- Information about the crash:
- What I was doing when the application crashed:
I ran systemsettings, and selected one user to hide from the login screen (KDM), applied and then chose logout from the K-menu.

-- Backtrace:
Application: PolicyKit1-KDE (polkit-kde-authentication-agent-1), signal: Segmentation fault
82	T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[Current thread is 1 (Thread 0x7fad5f56e840 (LWP 3651))]

Thread 2 (Thread 0x7fad51cb9710 (LWP 3658)):
#0  __lll_lock_wait () at ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:136
#1  0x00007fad5f1854a4 in _L_lock_996 () from /lib64/libpthread.so.0
#2  0x00007fad5f1852ba in __pthread_mutex_lock (mutex=0x7fad5dab45a8) at pthread_mutex_lock.c:61
#3  0x00007fad5d7d9ee5 in g_datalist_id_set_data_full (datalist=0x7fad4c003f10, key_id=53, data=0x0, destroy_func=0) at gdataset.c:588
#4  0x00007fad5ded05df in g_object_real_dispose (object=0x7fad4c003f00) at gobject.c:769
#5  0x00007fad5ded080b in g_object_unref (_object=0x7fad4c003f00) at gobject.c:2543
#6  0x00007fad5e1bb403 in read_with_control_data_free (data=0x7fad4c003b70) at gdbusprivate.c:122
#7  0x00007fad5d7ee3be in g_source_callback_unref (cb_data=<value optimized out>) at gmain.c:1152
#8  0x00007fad5d7ee91a in g_source_destroy_internal (source=0x7fad4c003a00, context=0xf94460, have_lock=1) at gmain.c:931
#9  0x00007fad5d7f1f91 in g_main_dispatch (context=0xf94460) at gmain.c:2144
#10 g_main_context_dispatch (context=0xf94460) at gmain.c:2672
#11 0x00007fad5d7f2700 in g_main_context_iterate (context=0xf94460, block=1, dispatch=1, self=<value optimized out>) at gmain.c:2750
#12 0x00007fad5d7f2d72 in g_main_loop_run (loop=0xf8e700) at gmain.c:2958
#13 0x00007fad5e1bb554 in shared_thread_func (data=<value optimized out>) at gdbusprivate.c:248
#14 0x00007fad5d819746 in g_thread_create_proxy (data=0xf96800) at gthread.c:1897
#15 0x00007fad5f182d5b in start_thread (arg=0x7fad51cb9710) at pthread_create.c:301
#16 0x00007fad5e71fbcd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115

Thread 1 (Thread 0x7fad5f56e840 (LWP 3651)):
[KCrash Handler]
#6  0x00007fad5d7da078 in g_data_set_internal (datalist=0xddb8b0, key_id=53, data=0x0, destroy_func=0) at gdataset.c:319
#7  g_datalist_id_set_data_full (datalist=0xddb8b0, key_id=53, data=0x0, destroy_func=0) at gdataset.c:592
#8  0x00007fad5ded0882 in g_object_unref (_object=0xddb8a0) at gobject.c:2567
#9  0x0000003914406170 in PolkitQt1::Agent::Listener::~Listener (this=0xf80500, __in_chrg=<value optimized out>) at /usr/src/debug/polkit-qt-1-0.95.1/agent/polkitqt1-agent-listener.cpp:69
#10 0x0000000000408039 in PolicyKitListener::~PolicyKitListener (this=0xf80500, __in_chrg=<value optimized out>) at /usr/src/debug/polkit-kde-1-0.95.1/agent/policykitlistener.cpp:42
#11 0x000000390fb6d7b4 in QObjectPrivate::deleteChildren (this=0xdda3a0) at kernel/qobject.cpp:1949
#12 0x000000390fb722f2 in QObject::~QObject (this=0x7fff81340500, __in_chrg=<value optimized out>) at kernel/qobject.cpp:945
#13 0x00000039113bca49 in QApplication::~QApplication (this=0x7fff81340500, __in_chrg=<value optimized out>) at kernel/qapplication.cpp:1031
#14 0x000000000040873e in main (argc=3, argv=0x7fff81340738) at /usr/src/debug/polkit-kde-1-0.95.1/agent/main.cpp:41

Reported using DrKonqi
Comment 1 Christoph Feck 2010-09-25 20:10:02 UTC
According to bug 249000 this was fixed in r1176246 by Radek Novacek.

WebSVN link: http://websvn.kde.org/?revision=1176246&view=revision
Comment 2 Christoph Feck 2010-09-25 20:10:47 UTC
*** Bug 249000 has been marked as a duplicate of this bug. ***
Comment 3 Christoph Feck 2010-09-25 20:11:04 UTC
*** Bug 250461 has been marked as a duplicate of this bug. ***
Comment 4 Christoph Feck 2010-09-25 20:11:11 UTC
*** Bug 250792 has been marked as a duplicate of this bug. ***
Comment 5 Christoph Feck 2010-09-25 20:11:35 UTC
*** Bug 251667 has been marked as a duplicate of this bug. ***
Comment 6 Christoph Feck 2010-09-25 20:12:08 UTC
*** Bug 251776 has been marked as a duplicate of this bug. ***
Comment 7 Christoph Feck 2010-09-25 20:12:31 UTC
*** Bug 251833 has been marked as a duplicate of this bug. ***
Comment 8 Christoph Feck 2010-09-25 20:16:09 UTC
*** Bug 252363 has been marked as a duplicate of this bug. ***
Comment 9 Gökçen Eraslan 2010-09-25 20:51:13 UTC
(In reply to comment #1)
> According to bug 249000 this was fixed in r1176246 by Radek Novacek.
> 
> WebSVN link: http://websvn.kde.org/?revision=1176246&view=revision

polkit-kde-1 was not working with polkit-0.98 and I've talked to rnovacek about the issue and he did a workaround to make it work. 

Now, polkit-kde-1 works with new polkit but, crash still continues during exit. 

Cristoph can you reopen the issue?
Comment 10 Christoph Feck 2010-09-25 23:06:50 UTC
Sure, but is the backtrace any different? If yes, you might better file a new bug report.
Comment 11 tumbeliina 2010-09-26 14:30:24 UTC
My 64-bit mandriva cooker has krash four times when I shutdown. First krash happened at 5th september after that I have shutdown tree times with polkit-kde-authentication-agent-1-20100926-xxxxx.kcrash notification.
Comment 12 Christoph Feck 2010-09-28 01:04:46 UTC
*** Bug 252595 has been marked as a duplicate of this bug. ***
Comment 13 Radek Novacek 2010-09-30 14:47:25 UTC
This is two different bugs - first is compatibility with polkit-0.98 which I fixed. The second one is crashing on shutdown which is not fixed now. Can I ask everyone who can reproduce this issue for more detail description? I'm unable to reproduce the bug, so I can't fix it.

This information would be helpful:
* polkit, polkit-qt and polkit-kde version
* distribution
* is the crash happens every time?
* what did you done before the crash? some polkit authorizations etc.?
Comment 14 Artem Goncharov 2010-10-01 11:50:23 UTC
1)
polkit-0.98-4.fc14.x86_64                                                                                                                                    
polkit-debuginfo-0.98-4.fc14.x86_64                                                                                                                          
polkit-kde-0.95.1-6.fc14.x86_64                                                                                                                              
polkit-kde-debuginfo-0.95.1-6.fc14.x86_64                                                                                                                    
polkit-qt-0.95.1-3.fc13.x86_64                                                                                                                               
polkit-qt-debuginfo-0.95.1-3.fc13.x86_64 
2) Fedora 14
3) yes, crash happens every time
4) probably there were some authorizations during session, however crash always occurs during shutdown
Comment 15 Andrey Borzenkov 2010-10-02 08:05:47 UTC
(In reply to comment #13)
> This information would be helpful:
> * polkit, polkit-qt and polkit-kde version

I do not know exact packaging details and am a bit confused by polkit/PolicyKit so here are all packages:

{pts/1}% rpm -qa polkit\* lib64polkit\*
polkit-0.99-1mdv2011.0
lib64polkit2-0.9-7mdv2010.1
lib64polkit1_0-0.99-1mdv2011.0
lib64polkit-qt-gui-10-0.96.1-1mdv2011.0
polkit-gnome-0.99-1mdv2011.0
polkit-kde-1-0.95.1-3mdv2010.1
lib64polkit-qt-gui0-0.9.3-1mdv2010.1
lib64polkit-qt-core-10-0.96.1-1mdv2011.0
lib64polkit-gnome0-0.9.2-6mdv2011.0
lib64polkit-qt-agent-10-0.96.1-1mdv2011.0
polkit-qt-1-devel-0.96.1-1mdv2011.0
lib64polkit-qt-core0-0.9.3-1mdv2010.1
lib64polkitkdeprivate4-4.5.68-1mdv2011.0
lib64polkit-devel-0.9-7mdv2010.1
polkit-debug-0.99-1mdv2011.0
polkit-qt-devel-0.9.3-1mdv2010.1
lib64polkit1-devel-0.99-1mdv2011.0

> * distribution

Mandriva cooker updated daily

> * is the crash happens every time?

At some point it did happen every time; then I did not see but just today it crashed again

> * what did you done before the crash? some polkit authorizations etc.?

I did not do any explicit authorization (i.e. - no dialogue box or like); but of course I do not know what happens under the hood. E.g. I suspend notebook twice a day using powerdevil and this should authorize this action as far as I understand.

Here is stack trace from the latest crash; I realized that I did not have polkit-qt-1-debug installed, did it now.
Thread 1 (Thread 0x7f0cc1cdc720 (LWP 3576)):
[KCrash Handler]
#6  0x00007f0cbd1ba578 in g_data_set_internal (datalist=0x25a88b0, key_id=53, data=0x0, destroy_func=0) at gdataset.c:325
#7  g_datalist_id_set_data_full (datalist=0x25a88b0, key_id=53, data=0x0, destroy_func=0) at gdataset.c:598
#8  0x00007f0cbcf52a0a in g_object_unref (_object=0x25a88a0) at gobject.c:2682
#9  0x00007f0cc1261630 in PolkitQt1::Agent::Listener::~Listener() () from /usr/lib64/libpolkit-qt-agent-1.so.0
#10 0x00000000004079c5 in _start ()
Comment 16 MartinG 2010-10-02 08:52:50 UTC
* polkit, polkit-qt and polkit-kde version
$ rpm -qa polkit polkit-qt  polkit-kde 
polkit-0.98-4.fc15.x86_64
polkit-kde-0.95.1-6.fc15.x86_64
polkit-0.98-4.fc15.i686
polkit-qt-0.96.1-1.fc15.x86_64

* distribution
Fedora Rawhide (kernel-2.6.36-0.28.rc6.git0.fc15.x86_64)

* is the crash happens every time?
I rarely log out, only use suspend/resume. But I think it happens every time I reboot for a new kernel.

* what did you done before the crash? some polkit authorizations etc.?
Not sure what polkit is even doing :-P , but I regularly update my system - could it be some yum plugin that is doing something?

$ yum --changelog --skip-broken upgrade
Loaded plugins: auto-update-debuginfo, changelog, fastestmirror, presto, refresh-packagekit
...
Comment 17 Mike Grindle 2010-10-04 23:09:58 UTC
I started having the same problem after a system update. Everytime I logout I get this error message:
"polkit-kde-authentication-agent-1 PID:4051 Signal:11 (Segmentation fault)"

I had done nothing in the systems settings module. I did notice that on the prior update of KDE to v4.5.1 that I lost the user-id value in the login screen on bootup.

*** the polkit package was part of a more extensive update:

[2010-10-04 08:36] upgraded kernel26 (2.6.35.5-1 -> 2.6.35.7-1)
[2010-10-04 08:36] upgraded libgl (7.8.2-1 -> 7.8.2-3)
[2010-10-04 08:36] upgraded qt (4.6.3-1 -> 4.7.0-2)
[2010-10-04 08:36] upgraded libdbusmenu-qt (0.6.0-1 -> 0.6.4-1)
[2010-10-04 08:36] upgraded libnice (0.0.13-1 -> 0.0.13-2)
[2010-10-04 08:36] upgraded librsvg (2.26.3-1 -> 2.32.0-2)
[2010-10-04 08:36] upgraded libssh (0.4.5-1 -> 0.4.6-1)
[2010-10-04 08:36] upgraded libtool (2.2.10-3 -> 2.4-1)
[2010-10-04 08:36] upgraded man-pages (3.26-1 -> 3.27-1)
[2010-10-04 08:36] installed glproto (1.4.12-1)
[2010-10-04 08:36] upgraded mesa (7.8.2-1 -> 7.8.2-3)
[2010-10-04 08:36] upgraded nss (3.12.7-1 -> 3.12.8-1)
[2010-10-04 08:36] upgraded polkit (0.96-2 -> 0.98-1)
[2010-10-04 08:36] installed gobject-introspection (0.9.10-1)

Version information from pacman:
polkit 0.98-1
polkit-kde 0.95.1-2
polkit-qt 0.95.1-1

All that I could generage from debug:

Application: polkit-kde-authentication-agent-1 (0.1)
KDE Platform Version: 4.5.1 (KDE 4.5.1)
Qt Version: 4.7.0
Operating System: Linux 2.6.35-ARCH x86_64

-- Information about the crash:
<In detail, tell us what you were doing  when the application crashed.>

The crash can be reproduced every time.

-- Backtrace:
A useful backtrace could not be generated

Report to https://bugs.kde.org
Comment 18 Artem Goncharov 2010-10-08 10:08:18 UTC
For me this issue was fixed with 2 ways:
1 (prefferable) - updates to PackageKit-0.6.9-4 (before it was 0.6.7-2)
2 (fedora fix) - update to polkit-qt-0.96.1-2.fc14

I assume that problem was exactly in PackageKit
Comment 19 Andrey Borzenkov 2010-10-08 17:25:18 UTC
(In reply to comment #18)
> For me this issue was fixed with 2 ways:
> 1 (prefferable) - updates to PackageKit-0.6.9-4 (before it was 0.6.7-2)
> 2 (fedora fix) - update to polkit-qt-0.96.1-2.fc14
> 
> I assume that problem was exactly in PackageKit

I did not even have packagekit installed at all and still had this issue. So may be something was done in polkit-qt indeed. Do you have possibility to revert polkit-qt to verify that it was indeed the reason?
Comment 20 Artem Goncharov 2010-10-08 19:55:47 UTC
Yes, I did checked it exactly without polkit-qt fix, just updating all PackageKit* packages to 0.6.9 version (leaving polkit as is) fixed issue for me.
Comment 21 Artem Goncharov 2010-10-08 20:08:09 UTC
(In reply to comment #19)
> 
> I did not even have packagekit installed at all and still had this issue. So
> may be something was done in polkit-qt indeed. Do you have possibility to
> revert polkit-qt to verify that it was indeed the reason?

Please note, that PackageKit is case sensitive (at least in Fedora). I did following tests (updating and downgrading packages):
1) PackageKit*-0.6.7 and polkit-qt-0.96.1-1 - problem exists
2) PackageKit*-0.6.9 and polkit-qt-0.96.1-1 - problem does not exist
3) PackageKit*-0.6.7 and polkit-qt-0.96.1-2 - problem does not exist
4) PackageKit*-0.6.9 and polkit-qt-0.96.1-2 - problem does not exist
Comment 22 Andrey Borzenkov 2010-10-08 20:23:55 UTC
(In reply to comment #21)
> Please note, that PackageKit is case sensitive (at least in Fedora). 

I use Mandriva, it packages it as packagekit. In any case I use version 0.6.9 and just had this crashed today.

> I did following tests (updating and downgrading packages):
> 1) PackageKit*-0.6.7 and polkit-qt-0.96.1-1 - problem exists
> 3) PackageKit*-0.6.7 and polkit-qt-0.96.1-2 - problem does not exist

This does not point fingers at PackageKit ... :)
Comment 23 Artem Goncharov 2010-10-08 20:40:17 UTC
(In reply to comment #22)
> (In reply to comment #21)
> > Please note, that PackageKit is case sensitive (at least in Fedora). 
> 
> I use Mandriva, it packages it as packagekit. In any case I use version 0.6.9
> and just had this crashed today.

Pity, however this worked for me. Maybe Fedora's packagekit contains some additional fixes

> 
> > I did following tests (updating and downgrading packages):
> > 1) PackageKit*-0.6.7 and polkit-qt-0.96.1-1 - problem exists
> > 3) PackageKit*-0.6.7 and polkit-qt-0.96.1-2 - problem does not exist
> 
> This does not point fingers at PackageKit ... :)

This was complete matrix just to show that both updates resolves issue.

P.S. In Fedora this issue is tracked by https://bugzilla.redhat.com/show_bug.cgi?id=637064
Comment 24 Gökçen Eraslan 2010-10-13 15:49:27 UTC
This patch[1] fixes the issue. Can you commit that and close the bug as FIXED?

(By the way, this patch[2] is wrong and makes polkit-kde-1 unusable, you should remove that)

[1] http://pkgs.fedoraproject.org/gitweb/?p=polkit-qt.git;a=blob;f=polkit-qt-0.96.1-null-checking.patch;h=0ec2a8e380102d1769d20addeaa1e8b73a7069d6;hb=HEAD

[2] http://pkgs.fedoraproject.org/gitweb/?p=polkit-qt.git;a=blob;f=polkit-qt-0.96.1-fix-deprecated-warnings.patch;h=fa136b0ffaccd65e78ff30dc98254a373cfc7ad9;hb=HEAD
Comment 25 Christoph Feck 2010-10-13 20:30:01 UTC
*** Bug 254089 has been marked as a duplicate of this bug. ***
Comment 26 Christoph Feck 2010-10-14 15:55:14 UTC
*** Bug 254124 has been marked as a duplicate of this bug. ***
Comment 27 Gökçen Eraslan 2010-10-18 11:58:21 UTC
Created attachment 52640 [details]
Crash output reproduced with patched polkit-qt-1

Hmm, I think I'm wrong, Fedora patches does not solve the issue. I can still reproduce the crash. Trace is attached.
Comment 28 Jaroslav Reznik 2010-10-18 12:23:30 UTC
(In reply to comment #27)
> Created an attachment (id=52640) [details]
> Crash output reproduced with patched polkit-qt-1
> 
> Hmm, I think I'm wrong, Fedora patches does not solve the issue. I can still
> reproduce the crash. Trace is attached.

Even latest version? https://admin.fedoraproject.org/updates/polkit-qt-0.96.1-4.fc14
Comment 29 Gökçen Eraslan 2010-10-18 13:43:45 UTC
(In reply to comment #28)
> (In reply to comment #27)
> Even latest version?
> https://admin.fedoraproject.org/updates/polkit-qt-0.96.1-4.fc14

Ah, I didn't know that you've updated patches. It seems OK now, I couldn't reproduce it now. Thanks.
Comment 30 Alex Merry 2010-10-18 19:34:42 UTC
I'm on Archlinux, with polkit-qt 0.96.1-3 (polkit-0.98), which includes both of the patches in comment #24.  But I still get this crash when I log out.  polkit-kde-1 is from trunk today.

I don't have packagekit at all.
Comment 31 Christoph Feck 2010-11-09 18:59:41 UTC
*** Bug 256462 has been marked as a duplicate of this bug. ***
Comment 32 Valentin Rusu 2010-11-12 23:56:38 UTC
Hello,
On my openSuSE 11.4 M3 this happens quite often on system shutdown. The sequence is :
- choose k -> shutdown
- click ok - the windowing system quits (no more window decorations, no more networking as knetworkmanager just quit)
- the crash handler pops-up - and this time I anticipated it by installing polkit-kde debug symbols, so I could save the crash on the disk, in order to put it here :)
- when closing the crash handler, the shutdown sequence continues as expected.

Here is my crash report :

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

Thread 3 (Thread 0xb2d82b70 (LWP 2552)):
#0  0xb5e732d7 in g_main_context_prepare () from /usr/lib/libglib-2.0.so.0
#1  0xb5e74002 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0xb5e74b0f in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#3  0xb5d6e261 in ?? () from /usr/lib/libgio-2.0.so.0
#4  0xb5e9d484 in ?? () from /usr/lib/libglib-2.0.so.0
#5  0xb5f92b25 in start_thread () from /lib/libpthread.so.0
#6  0xb635f2ee in clone () from /lib/libc.so.6

Thread 2 (Thread 0xb23d7b70 (LWP 5719)):
#0  0xffffe430 in __kernel_vsyscall ()
#1  0xb634e81b in read () from /lib/libc.so.6
#2  0xb5e759e7 in ?? () from /usr/lib/libglib-2.0.so.0
#3  0xb5e9d484 in ?? () from /usr/lib/libglib-2.0.so.0
#4  0xb5f92b25 in start_thread () from /lib/libpthread.so.0
#5  0xb635f2ee in clone () from /lib/libc.so.6

Thread 1 (Thread 0xb5900760 (LWP 2476)):
[KCrash Handler]
#7  0xb5e57217 in g_datalist_id_set_data_full () from /usr/lib/libglib-2.0.so.0
#8  0xb5dec7e6 in g_object_unref () from /usr/lib/libgobject-2.0.so.0
#9  0xb74c3351 in PolkitQt1::Agent::Listener::~Listener (this=0x815f698, __in_chrg=<value optimized out>) at /usr/src/debug/polkit-qt-1-0.96.1/agent/polkitqt1-agent-listener.cpp:69
#10 0x0804f300 in PolicyKitListener::~PolicyKitListener (this=0x815f698, __in_chrg=<value optimized out>) at /usr/src/debug/polkit-kde-1-svn1074649/agent/policykitlistener.cpp:42
#11 0xb710aa64 in QObjectPrivate::deleteChildren() () from /usr/lib/libQtCore.so.4
#12 0xb710f91c in QObject::~QObject() () from /usr/lib/libQtCore.so.4
#13 0xb70f9dd0 in QCoreApplication::~QCoreApplication() () from /usr/lib/libQtCore.so.4
#14 0xb662a3dd in QApplication::~QApplication() () from /usr/lib/libQtGui.so.4
#15 0xb75c4128 in KApplication::~KApplication() () from /usr/lib/libkdeui.so.5
#16 0xb75c4198 in KUniqueApplication::~KUniqueApplication() () from /usr/lib/libkdeui.so.5
#17 0x0804f9ea in main (argc=) at /usr/src/debug/polkit-kde-1-svn1074649/agent/main.cpp:41
Comment 33 Christoph Feck 2010-11-27 03:02:13 UTC
*** Bug 258033 has been marked as a duplicate of this bug. ***
Comment 34 g111 2011-03-02 08:44:01 UTC
I do have this problem after a recent dist-upgrade in debian/sid, too.

libpolkit-agent-1-0          0.99-3     
libpolkit-agent-1-dev        0.99-3     
libpolkit-backend-1-0        0.99-3     
libpolkit-backend-1-dev      0.99-3     
libpolkit-gobject-1-0        0.99-3     
libpolkit-gobject-1-dev      0.99-3     
libpolkit-qt-1-0             0.95.1-1   
libpolkit-qt-1-dev           0.95.1-1   
polkit-kde-1                 0.95.1-2+b1

debian/sid currently still is using KDE 4.4.5 (with pim packages up to 4.4.7).

The crash happens every time on logout. I do not have to do anything else, just log in, wait until KDE has completely loaded and then log out.

As the crash handler is only shown for 2 seconds, I cannot offer you an crash report, at least I do not know how I could do this.

Gert
Comment 35 Radek Novacek 2011-03-03 08:40:52 UTC
I can't tell what is wrong without backtrace, but you can try to upgrade polkit-qt to version 0.96.

Note that polkit-qt-0.99 and polkit-kde-0.99 are compatible with at least kde-4.6.
Comment 36 Matthias Nagel 2011-03-31 11:45:21 UTC
I have the same bug with Gentoo and the following packages

kde-base/kdebase-meta-4.4.5
kde-base/kdelibs-4.4.5-r4
sys-auth/consolekit-0.4.4
sys-auth/polkit-0.99-r1
sys-auth/polkit-kde-0.95.1-r1
sys-auth/polkit-qt-0.96.1

In four of five times I see this crash during logout. Unfortunately the crash handlers closes after a few seconds. Hence I do not have a real chance to save the backtrace. But from the glimpse that I can catch it seems similar to the backtraces above.
Comment 37 Christoph Feck 2011-04-12 01:55:47 UTC
*** Bug 268561 has been marked as a duplicate of this bug. ***
Comment 38 g111 2011-04-12 08:40:17 UTC
To add to my comment #34:
After some dist-upgrades in debian/sid the crash did disappear. With KDE4.6.1 (from debian/experimental-snapshots) and the following package versions the logout does work fine:
libpolkit-agent-1-0            0.101-2  
libpolkit-agent-1-dev          0.101-2  
libpolkit-backend-1-0          0.101-2  
libpolkit-backend-1-dev        0.101-2  
libpolkit-gobject-1-0          0.101-2  
libpolkit-gobject-1-dev        0.101-2  
libpolkit-qt-1-1               0.99.0-1 
libpolkit-qt-1-dev             0.99.0-1 
polkit-kde-1                   0.99.0-1 

Greetings,
Gert
Comment 39 S. Burmeister 2012-03-11 23:20:12 UTC
works for me in KDE 4.8.1.
Comment 40 Alex Merry 2013-01-11 22:39:11 UTC
Anyone still getting this with recent releases (4.8 onwards)?
Comment 41 Bruno Friedmann 2013-01-12 16:38:57 UTC
Doesn't appear recently on 4.8x & 4.9x
Comment 42 g111 2013-01-13 13:43:13 UTC
I have never seen this anymore for months now (Currently using KDE4.9/KUbuntu). So I assume this as fixed.
Comment 43 Andrew Crouthamel 2018-09-24 02:18:37 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 set the bug status 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 44 Andrew Crouthamel 2018-10-27 04:06:15 UTC
Dear Bug Submitter,

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!