Bug 583873

Summary: [abrt] crash in simdock-1.2-7.fc12: Process /usr/bin/simdock was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Serapio Montoya <crackadict>
Component: simdockAssignee: Terje Røsten <terje.rosten>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: lpoetter, tconley66, terje.rosten
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:8dd3a1c079a37c19d133a78e074a0279e1b7902d
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-11-15 22:39:37 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description Serapio Montoya 2010-04-20 05:04:06 UTC
abrt 1.0.8 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: simdock
component: simdock
executable: /usr/bin/simdock
kernel: 2.6.32.11-99.fc12.i686
package: simdock-1.2-7.fc12
rating: 4
reason: Process /usr/bin/simdock was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

Comment 1 Serapio Montoya 2010-04-20 05:04:23 UTC
Created attachment 407726 [details]
File: backtrace

Comment 2 Terje Røsten 2010-05-04 18:53:00 UTC
I have trouble reproducing this.

Also, strange is the reference to pulseaudio in the backtrace, however
I can't understand how simdock is related to pulseaudio.

What did you do to create the crash?

Comment 3 Terje Røsten 2010-05-04 18:57:35 UTC
Hi Lennart,

adding you to the CC: list on this one. 

From some reason pulseaudio pops up the in backstrace.

Similar crashed in  #587303 and #568247.

Any ideas?

Comment 4 Lennart Poettering 2010-05-06 23:08:03 UTC
That bt simply shows the libcanberra event sound thread running. The segfault is in another thread. This indicates the problem is unrelated to PA/libcanberra. As long as the segfault is not in PA's thread just ignore that the PA/libcanberra thread even shows up!

Comment 5 Karel Klíč 2010-05-25 09:49:49 UTC
*** Bug 587303 has been marked as a duplicate of this bug. ***

Comment 6 Bug Zapper 2010-11-03 16:44:21 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 7 Terje Røsten 2010-11-15 22:39:37 UTC

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