Bug 674788 - [abrt] PackageKit-0.5.8-13.el6: pthread_mutex_lock: Process /usr/sbin/packagekitd was killed by signal 11 (SIGSEGV)
Summary: [abrt] PackageKit-0.5.8-13.el6: pthread_mutex_lock: Process /usr/sbin/package...
Keywords:
Status: CLOSED DUPLICATE of bug 668350
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: PackageKit
Version: 6.1
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Richard Hughes
QA Contact: desktop-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-03 10:50 UTC by Siddharth
Modified: 2018-11-26 19:23 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-08-18 10:11:58 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Siddharth 2011-02-03 10:50:57 UTC 
Description of problem:
abrt version: 1.1.13
architecture: x86_64
cmdline: /usr/sbin/packagekitd
component: PackageKit
crash_function: pthread_mutex_lock
executable: /usr/sbin/packagekitd
reason: Process /usr/sbin/packagekitd was killed by signal 11 (SIGSEGV)

Version-Release number of selected component (if applicable):
kernel: 2.6.32-71.14.1.el6.x86_64
package: PackageKit-0.5.8-13.el6
Red Hat Enterprise Linux Server release 6.0 (Santiago)

How reproducible:
Random crash

Steps to Reproduce:
1.
2.
3.
  
Actual results:
Application packagekit was killed.

Expected results:
Application packagekit should not killed.

Additional info:
Comment 4 Chris Williams 2011-02-24 22:14:49 UTC 
This bug was not resolved before development freeze.  We are now making preparations for the launch of 6.1 and are only accepting critical and high impact bugs.  We're reflagging this bug for 6.2 to continue the review and work needed to resolve this bug.
Comment 6 Richard Hughes 2011-08-18 10:11:58 UTC 

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