Bug 725309 - [abrt] pulseaudio-0.9.21-7.fc14: _dbus_list_unlink: Process /usr/bin/pulseaudio was killed by signal 11 (SIGSEGV)
Summary: [abrt] pulseaudio-0.9.21-7.fc14: _dbus_list_unlink: Process /usr/bin/pulseaud...
Keywords:
Status: CLOSED DUPLICATE of bug 725304
Alias: None
Product: Fedora
Classification: Fedora
Component: pulseaudio
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Lennart Poettering
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:5aaeaacfe15ed52c6648ee732c3...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-25 04:50 UTC by David Clark
Modified: 2012-03-20 15:07 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-20 15:07:43 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (30.30 KB, text/plain)
2011-07-25 04:50 UTC, David Clark
no flags Details

Description David Clark 2011-07-25 04:50:06 UTC
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 31031 bytes
cmdline: /usr/bin/pulseaudio --start --log-target=syslog
component: pulseaudio
Attached file: coredump, 21663744 bytes
crash_function: _dbus_list_unlink
executable: /usr/bin/pulseaudio
kernel: 2.6.35.6-45.fc14.x86_64
package: pulseaudio-0.9.21-7.fc14
rating: 4
reason: Process /usr/bin/pulseaudio was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1311569138
uid: 500

How to reproduce
-----
1. Crashed right after logging into my system.
2.
3.

Comment 1 David Clark 2011-07-25 04:50:08 UTC
Created attachment 514970 [details]
File: backtrace

Comment 2 abrt-bot 2012-03-20 15:07:43 UTC
Backtrace analysis found this bug to be similar to bug #725304, closing as duplicate.

Bugs which were found to be similar to this bug: 
  evolution: bug #735640
  evolution-data-server: bug #563518, bug #566506, bug #739968
  pulseaudio: bug #725304

This comment is automatically generated.

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


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