Bug 918269

Summary: [abrt] rhythmbox-2.98-4.fc18: __pthread_mutex_lock: Process /usr/bin/rhythmbox was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Sam Tuke <mail>
Component: rhythmboxAssignee: Bastien Nocera <bnocera>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: 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: 2014-02-05 19:41:19 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: smolt_data
none
File: var_log_messages none

Description Sam Tuke 2013-03-05 19:19:14 UTC
Description of problem:
I dragged and dropped 10 mp3 files from Nemo file manager into the RhythmnBox playlist window

Version-Release number of selected component:
rhythmbox-2.98-4.fc18

Additional info:
backtrace_rating: 4
cmdline:        rhythmbox
crash_function: __pthread_mutex_lock
executable:     /usr/bin/rhythmbox
kernel:         3.7.9-201.fc18.i686
uid:            1000

Truncated backtrace:
Thread no. 1 (4 frames)
 #0 __pthread_mutex_lock at pthread_mutex_lock.c:50
 #1 g_mutex_lock at gthread-posix.c:210
 #2 g_main_context_acquire at gmain.c:2776
 #4 g_thread_proxy at gthread.c:797

Potential duplicate: bug 888808

Comment 1 Sam Tuke 2013-03-05 19:19:17 UTC
Created attachment 705613 [details]
File: backtrace

Comment 2 Sam Tuke 2013-03-05 19:19:19 UTC
Created attachment 705614 [details]
File: build_ids

Comment 3 Sam Tuke 2013-03-05 19:19:21 UTC
Created attachment 705615 [details]
File: cgroup

Comment 4 Sam Tuke 2013-03-05 19:19:23 UTC
Created attachment 705616 [details]
File: core_backtrace

Comment 5 Sam Tuke 2013-03-05 19:19:26 UTC
Created attachment 705617 [details]
File: dso_list

Comment 6 Sam Tuke 2013-03-05 19:19:28 UTC
Created attachment 705618 [details]
File: environ

Comment 7 Sam Tuke 2013-03-05 19:19:30 UTC
Created attachment 705619 [details]
File: limits

Comment 8 Sam Tuke 2013-03-05 19:19:33 UTC
Created attachment 705620 [details]
File: maps

Comment 9 Sam Tuke 2013-03-05 19:19:35 UTC
Created attachment 705621 [details]
File: open_fds

Comment 10 Sam Tuke 2013-03-05 19:19:38 UTC
Created attachment 705622 [details]
File: proc_pid_status

Comment 11 Sam Tuke 2013-03-05 19:19:41 UTC
Created attachment 705623 [details]
File: smolt_data

Comment 12 Sam Tuke 2013-03-05 19:19:43 UTC
Created attachment 705624 [details]
File: var_log_messages

Comment 13 Fedora End Of Life 2013-12-21 11:53:50 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 '18'.

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 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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 18'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 2014-02-05 19:41:19 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

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