Bug 694328 - [abrt] polkit-gnome-0.97-4.fc14: vasprintf: Process /usr/libexec/polkit-gnome-authentication-agent-1 was killed by signal 11 (SIGSEGV)
Summary: [abrt] polkit-gnome-0.97-4.fc14: vasprintf: Process /usr/libexec/polkit-gnome...
Keywords:
Status: CLOSED DUPLICATE of bug 694329
Alias: None
Product: Fedora
Classification: Fedora
Component: polkit-gnome
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: David Zeuthen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:cde33ddd25dfcb867d0832fa35d...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-07 01:12 UTC by Alex Bartl
Modified: 2013-03-06 04:06 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-20 16:30:57 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (217.08 KB, text/plain)
2011-04-07 01:12 UTC, Alex Bartl 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Alex Bartl 2011-04-07 01:12:40 UTC 
abrt version: 1.1.17
architecture: i686
Attached file: backtrace, 222288 bytes
cmdline: /usr/libexec/polkit-gnome-authentication-agent-1
component: polkit-gnome
Attached file: coredump, 10227712 bytes
crash_function: vasprintf
executable: /usr/libexec/polkit-gnome-authentication-agent-1
kernel: 2.6.35.11-83.fc14.i686.PAE
package: polkit-gnome-0.97-4.fc14
rating: 4
reason: Process /usr/libexec/polkit-gnome-authentication-agent-1 was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1301255305
uid: 42

How to reproduce
-----
1. sorry, no clue 
2.
3.
Comment 1 Alex Bartl 2011-04-07 01:12:44 UTC 
Created attachment 490449 [details]
File: backtrace
Comment 2 abrt-bot 2012-03-20 16:30:57 UTC 
Backtrace analysis found this bug to be similar to bug #694329, closing as duplicate.

Bugs which were found to be similar to this bug: 
  plymouth: bug #694329
  thunderbird: bug #649215

This comment is automatically generated.

*** This bug has been marked as a duplicate of bug 694329 ***
Note You need to log in before you can comment on or make changes to this bug.