Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 592686 - [abrt] crash in pavucontrol-0.9.10-1.fc12: Process /usr/bin/pavucontrol was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in pavucontrol-0.9.10-1.fc12: Process /usr/bin/pavucontrol was k...
Status: CLOSED DUPLICATE of bug 546928
Alias: None
Product: Fedora
Classification: Fedora
Component: pavucontrol
Version: 12
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Lennart Poettering
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:74a592f5682e15db9a65882a968...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-05-16 09:13 UTC by Dematron
Modified: 2010-05-25 08:28 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2010-05-25 08:28:25 UTC

Attachments (Terms of Use)
File: backtrace (deleted)
2010-05-16 09:13 UTC, Dematron
no flags Details

Description Dematron 2010-05-16 09:13:51 UTC
abrt 1.0.9 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: pavucontrol
component: pavucontrol
crash_function: StreamWidget::onMuteToggleButton
executable: /usr/bin/pavucontrol
global_uuid: 74a592f5682e15db9a65882a9687f23e5c1a9e38
package: pavucontrol-0.9.10-1.fc12
rating: 4
reason: Process /usr/bin/pavucontrol was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

Comment 1 Dematron 2010-05-16 09:13:54 UTC
Created attachment 414328 [details]
File: backtrace

Comment 2 Karel Klíč 2010-05-25 08:28:25 UTC

*** This bug has been marked as a duplicate of bug 546928 ***

Comment 3 Karel Klíč 2010-05-25 08:28:25 UTC
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #546928.

Sorry for the inconvenience.

Note You need to log in before you can comment on or make changes to this bug.