Bug 888808

Summary: [abrt] rhythmbox-2.97-1.fc17: __pthread_mutex_lock: Process /usr/bin/rhythmbox was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Sergey Kurtsev <skurtsev>
Component: rhythmboxAssignee: Bastien Nocera <bnocera>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: bnocera
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:865ed7e9ec6d8ef4e37e3f6b322288aeecff6a5d
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-07-31 21:23:16 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
File: build_ids
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: xsession_errors
none
File: smolt_data none

Description Sergey Kurtsev 2012-12-19 14:49:55 UTC
Version-Release number of selected component:
rhythmbox-2.97-1.fc17

Additional info:
backtrace_rating: 4
cmdline:        rhythmbox
crash_function: __pthread_mutex_lock
executable:     /usr/bin/rhythmbox
kernel:         3.6.7-4.fc17.i686.PAE
remote_result:  NOTFOUND
uid:            1000
var_log_messages: Dec 19 18:34:55 sk abrt[13249]: Saved core dump of pid 25844 (/usr/bin/rhythmbox) to /var/spool/abrt/ccpp-2012-12-19-18:34:48-25844 (318750720 bytes)

Truncated backtrace:
Thread no. 1 (4 frames)
 #0 __pthread_mutex_lock at pthread_mutex_lock.c:51
 #1 g_mutex_lock at gthread-posix.c:208
 #2 g_main_context_acquire at gmain.c:2624
 #4 g_thread_proxy at gthread.c:801

Comment 1 Sergey Kurtsev 2012-12-19 14:49:58 UTC
Created attachment 666109 [details]
File: backtrace

Comment 2 Sergey Kurtsev 2012-12-19 14:50:01 UTC
Created attachment 666110 [details]
File: build_ids

Comment 3 Sergey Kurtsev 2012-12-19 14:50:12 UTC
Created attachment 666111 [details]
File: cgroup

Comment 4 Sergey Kurtsev 2012-12-19 14:50:15 UTC
Created attachment 666112 [details]
File: core_backtrace

Comment 5 Sergey Kurtsev 2012-12-19 14:50:18 UTC
Created attachment 666113 [details]
File: dso_list

Comment 6 Sergey Kurtsev 2012-12-19 14:50:22 UTC
Created attachment 666114 [details]
File: environ

Comment 7 Sergey Kurtsev 2012-12-19 14:50:25 UTC
Created attachment 666115 [details]
File: limits

Comment 8 Sergey Kurtsev 2012-12-19 14:50:29 UTC
Created attachment 666116 [details]
File: maps

Comment 9 Sergey Kurtsev 2012-12-19 14:50:31 UTC
Created attachment 666117 [details]
File: open_fds

Comment 10 Sergey Kurtsev 2012-12-19 14:50:34 UTC
Created attachment 666118 [details]
File: proc_pid_status

Comment 11 Sergey Kurtsev 2012-12-19 14:50:36 UTC
Created attachment 666119 [details]
File: xsession_errors

Comment 12 Sergey Kurtsev 2012-12-19 14:50:38 UTC
Created attachment 666120 [details]
File: smolt_data

Comment 13 Fedora End Of Life 2013-07-03 20:52:27 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. 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 '17'.

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 17'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 17 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, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

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.

Comment 14 Fedora End Of Life 2013-07-31 21:23:23 UTC
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.