Description of problem: Happened on boot Version-Release number of selected component: upower-0.9.17-2.fc18 Additional info: libreport version: 2.0.13 abrt_version: 2.0.12 backtrace_rating: 4 cmdline: /usr/libexec/upowerd crash_function: up_polkit_init kernel: 3.6.0-0.rc2.git2.1.fc18.x86_64 truncated backtrace: :Thread no. 1 (8 frames) : #2 up_polkit_init at up-polkit.c : #3 g_type_create_instance at gtype.c : #4 g_object_constructor at gobject.c : #7 up_polkit_new at up-polkit.c : #8 up_qos_init at up-qos.c : #9 g_type_create_instance at gtype.c : #10 g_object_constructor at gobject.c : #13 up_qos_new at up-qos.c
Created attachment 608877 [details] File: core_backtrace
Created attachment 608878 [details] File: environ
Created attachment 608879 [details] File: limits
Created attachment 608880 [details] File: backtrace
Created attachment 608881 [details] File: cgroup
Created attachment 608882 [details] File: maps
Created attachment 608883 [details] File: dso_list
Created attachment 608884 [details] File: open_fds
Created attachment 608885 [details] File: var_log_messages
> #0 g_logv (log_domain=0x41bf39 "UPower", Why do you think this is a polkit bug?!?
It's crashing in up_polkit_init()
(In reply to comment #11) > It's crashing in up_polkit_init() But up_polkit_init() is not part of polkit... My guess is that polkitd is masked or for some reason does not start (there's a yum/selinux bug causing the polkitd user to not get created, maybe you are hitting that) and your application does not handle polkit_authority_get_sync() returning NULL. Please see http://www.freedesktop.org/software/polkit/docs/latest/polkit-apps.html
It just appears on each start after upgrade to F18, and KDE battery applet is not working (shows nothing connected) backtrace_rating: 4 Package: upower-0.9.18-2.fc18 OS Release: Fedora release 18 (Spherical Cow)
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.