Bug 902055

Summary: [abrt] lxpolkit-0.1.0-4.fc18: main: Process /usr/libexec/lxpolkit was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: chillihead666
Component: lxpolkitAssignee: Christoph Wickert <christoph.wickert>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: buczynski_michael, christoph.wickert, iain.f.bell, weidemann.m
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:c1f164927f18dfa1d54d89e9b1d74c110cff3d97
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-05 15:24:37 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description chillihead666 2013-01-20 16:50:15 UTC
Description of problem:
When logging in via VNC Tiger

Version-Release number of selected component:
lxpolkit-0.1.0-4.fc18

Additional info:
backtrace_rating: 4
cmdline:        /usr/libexec/lxpolkit
core_backtrace: c74b5287e577702f2c36ae130fb5678d3620a342 0x1832 main /usr/libexec/lxpolkit -
crash_function: main
executable:     /usr/libexec/lxpolkit
kernel:         3.7.2-204.fc18.i686
remote_result:  NOTFOUND
uid:            1000

Truncated backtrace:
Thread no. 1 (0 frames)

Potential duplicate: bug 727905

Comment 1 chillihead666 2013-01-20 16:50:18 UTC
Created attachment 683702 [details]
File: backtrace

Comment 2 chillihead666 2013-01-20 16:50:20 UTC
Created attachment 683703 [details]
File: cgroup

Comment 3 chillihead666 2013-01-20 16:50:22 UTC
Created attachment 683704 [details]
File: dso_list

Comment 4 chillihead666 2013-01-20 16:50:24 UTC
Created attachment 683705 [details]
File: environ

Comment 5 chillihead666 2013-01-20 16:50:26 UTC
Created attachment 683706 [details]
File: limits

Comment 6 chillihead666 2013-01-20 16:50:28 UTC
Created attachment 683707 [details]
File: maps

Comment 7 chillihead666 2013-01-20 16:50:30 UTC
Created attachment 683708 [details]
File: open_fds

Comment 8 chillihead666 2013-01-20 16:50:32 UTC
Created attachment 683709 [details]
File: proc_pid_status

Comment 9 chillihead666 2013-01-20 16:50:34 UTC
Created attachment 683710 [details]
File: var_log_messages

Comment 10 Christoph Wickert 2013-01-27 16:11:23 UTC
*** Bug 882614 has been marked as a duplicate of this bug. ***

Comment 11 Fedora End Of Life 2013-12-21 10:36:47 UTC
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.

Comment 12 Fedora End Of Life 2014-02-05 15:24:39 UTC
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.