abrt version: 1.1.18
Attached file: backtrace, 9371 bytes
Attached file: coredump, 9523200 bytes
reason: Process /usr/libexec/lxpolkit was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
How to reproduce: Starting LXDE with Thinlink.
Created attachment 516535 [details]
Is this crash reproducable, means does it happen every time you log in?
Are you running other PolicyKit authentication agents? Please give me the output of 'ps -A | grep pol'
(In reply to comment #0)
> How to reproduce: Starting LXDE with Thinlink.
Can you tell me more about this?
(In reply to comment #2)
> Is this crash reproducable, means does it happen every time you log in?
Yes, it happens every time i log in.
> Are you running other PolicyKit authentication agents? Please give me the
> output of 'ps -A | grep pol'
It gives me no output.
> (In reply to comment #0)
> > How to reproduce: Starting LXDE with Thinlink.
> Can you tell me more about this?
Its a FOSS-based terminal server software based on VNC. As Gnome 3.0 is far from optimal for terminal servers i plan to switch to LXDE before upgrading to F 15. There is also some applet that fail to start but i think thats a result of this bug.
I also got the following crash that by some reason got automatically filed as bug 499183, which is a different bug.
These crashes are probably related, kdeutils-printer-applet also crash when i log in to KDE using ThinLinc.
Latest Crash: ons 3 aug 2011 17.32.03
Reason: connection.py:630:call_blocking:DBusException: org.freedesktop.DBus.Error.AccessDenied: Connection ":1.7240" is not allowed to own the service "com.redhat.NewPrinterNotification" due to security policies in the configuration file
Comment: This error also occur when logging in to KDE.
Bug Reports: Status: CLOSED ERRATA
OS Release: Fedora release 16 (Verne)
I see this when I start LXDE as a remote desktop.
I'm using nx (nomachine provided packages) to connect from F15 to the F16 machine where this error shows up but I'm not sure if that's related to this crash. I'm seeing other issues with X that keep me from running X locally on the F16 machine.
*** Bug 758884 has been marked as a duplicate of this bug. ***
*** Bug 758876 has been marked as a duplicate of this bug. ***
Same error here - running LXDE on my netbook (Acer Aspire One AOA150) running Rawhide (lxpolkit-0.1.0-1.fc16.i686 updated 31 Dec 2011) updated from F16 since Rawhide is currently uninstallable.
$ ps -A | grep pol
837 ? 00:00:01 polkitd
Problem persists with full update (1 Jan 2012)
~$ rpm -qa | egrep -i "lxpolkit|glibc|pam" | sort
I have the same situation as in comment #4.
Lxpolkit crashes every time I log in to a new nx session, but not if I start X locally. F16 & LXDE running on an Asus eeepc 900.
~]$ rpm -qa | egrep -i "lxpolkit|glibc|pam|freenx" | sort
OS Release: Fedora release 16 (Verne)
Created attachment 571140 [details]
This message is a notice that Fedora 14 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 14. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.
(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 14 reached 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 to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.
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.
The process we are following is described here: