Bug 569049 - [abrt] crash in polkit-0.96-1.fc13: Process /usr/libexec/polkit-1/polkitd was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in polkit-0.96-1.fc13: Process /usr/libexec/polkit-1/polkitd was...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: polkit
Version: rawhide
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: David Zeuthen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:a312453ea14949d024164746251...
: 567342 568080 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-02-27 19:50 UTC by Gene Snider
Modified: 2010-04-06 03:50 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-04-06 03:50:08 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (9.91 KB, text/plain)
2010-02-27 19:50 UTC, Gene Snider 		no flags Details
View All

Description Gene Snider 2010-02-27 19:50:44 UTC 
abrt 1.0.8 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/libexec/polkit-1/polkitd
comment: The segfault appears to occur during shutdown.
component: polkit
executable: /usr/libexec/polkit-1/polkitd
kernel: 2.6.33-1.fc13.x86_64
package: polkit-0.96-1.fc13
rating: 3
reason: Process /usr/libexec/polkit-1/polkitd was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Rawhide)

How to reproduce
-----
1.Boot up Fedora.
2.Restart or shutdown Fedora.
3.
Comment 1 Gene Snider 2010-02-27 19:50:45 UTC 
Created attachment 396781 [details]
File: backtrace
Comment 2 Matthias Clasen 2010-03-01 04:51:05 UTC 
*** Bug 567342 has been marked as a duplicate of this bug. ***
Comment 3 Matthias Clasen 2010-03-01 04:54:14 UTC 
*** Bug 568080 has been marked as a duplicate of this bug. ***
Comment 4 Gene Snider 2010-03-09 18:36:23 UTC 
This bug seems to have been fixed, I'm not seeing that error any more.

Gene
Comment 5 Matthias Clasen 2010-04-06 03:50:08 UTC 
thanks for letting us know.
Note You need to log in before you can comment on or make changes to this bug.