Bug 1098698

Summary: [abrt] rhythmbox: rb_playlist_source_mark_dirty(): rhythmbox killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Sam Tygier <samtygier>
Component: rhythmboxAssignee: Bastien Nocera <bnocera>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: bnocera
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/6b0497d4aeee3ec1670bcd827c502256c2fb1b05
Whiteboard: abrt_hash:d717e3376072d2d1ca79e586d663e08494854747
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 11:32:15 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: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Sam Tygier 2014-05-17 10:47:01 UTC 
Version-Release number of selected component:
rhythmbox-3.0.2-3.fc21

Additional info:
reporter:       libreport-2.2.2
backtrace_rating: 4
cmdline:        rhythmbox
crash_function: rb_playlist_source_mark_dirty
executable:     /usr/bin/rhythmbox
kernel:         3.15.0-0.rc5.git2.9.fc21.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 rb_playlist_source_mark_dirty at rb-playlist-source.c:1110
 #5 g_settings_real_change_event at gsettings.c:277
 #6 ffi_call_unix64 at ../src/x86/unix64.S:76
 #7 ffi_call at ../src/x86/ffi64.c:522
 #8 g_cclosure_marshal_generic_va at gclosure.c:1541
 #9 _g_closure_invoke_va at gclosure.c:831
 #12 settings_backend_changed at gsettings.c:337
 #13 g_settings_backend_invoke_closure at gsettingsbackend.c:267
 #14 g_main_context_invoke_full at gmain.c:5500
 #15 g_main_context_invoke at gmain.c:5461
Comment 1 Sam Tygier 2014-05-17 10:47:08 UTC 
Created attachment 896567 [details]
File: backtrace
Comment 2 Sam Tygier 2014-05-17 10:47:10 UTC 
Created attachment 896568 [details]
File: cgroup
Comment 3 Sam Tygier 2014-05-17 10:47:12 UTC 
Created attachment 896569 [details]
File: core_backtrace
Comment 4 Sam Tygier 2014-05-17 10:47:15 UTC 
Created attachment 896570 [details]
File: dso_list
Comment 5 Sam Tygier 2014-05-17 10:47:17 UTC 
Created attachment 896571 [details]
File: environ
Comment 6 Sam Tygier 2014-05-17 10:47:19 UTC 
Created attachment 896572 [details]
File: exploitable
Comment 7 Sam Tygier 2014-05-17 10:47:24 UTC 
Created attachment 896573 [details]
File: limits
Comment 8 Sam Tygier 2014-05-17 10:47:27 UTC 
Created attachment 896574 [details]
File: maps
Comment 9 Sam Tygier 2014-05-17 10:47:28 UTC 
Created attachment 896575 [details]
File: open_fds
Comment 10 Sam Tygier 2014-05-17 10:47:30 UTC 
Created attachment 896576 [details]
File: proc_pid_status
Comment 11 Sam Tygier 2014-05-17 10:47:32 UTC 
Created attachment 896577 [details]
File: var_log_messages
Comment 12 Jaroslav Reznik 2015-03-03 15:49:19 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Comment 13 Fedora End Of Life 2016-07-19 11:32:15 UTC 
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.