Bug 1285746

Summary: [abrt] rhythmbox: WTFCrash(): rhythmbox killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Pablo Ganuza <pabloganuza>
Component: rhythmboxAssignee: David King <amigadave>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 23CC: bnocera
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/203a2df9bb85bc71fd29effb637d3c59fd730fa9
Whiteboard: abrt_hash:1fe17efe907076a549fba67beee846669db0d7f1;VARIANT_ID=workstation;
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-12-20 16:18:58 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: mountinfo
none
File: namespaces
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Pablo Ganuza 2015-11-26 11:38:15 UTC
Description of problem:
Rhythmbox wasn't even playing. I stopped the playback to make a phone call and after 10 minutes or so it just crashed with no apparent reason.

Version-Release number of selected component:
rhythmbox-3.2.1-3.fc23

Additional info:
reporter:       libreport-2.6.3
backtrace_rating: 4
cmdline:        rhythmbox
crash_function: WTFCrash
executable:     /usr/bin/rhythmbox
global_pid:     3302
kernel:         4.2.6-300.fc23.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 WTFCrash at Source/WTF/wtf/Assertions.cpp:333
 #1 WTF::CrashOnOverflow::overflowed at Source/WTF/wtf/CheckedArithmetic.h:78
 #2 WTF::Vector<WTF::String, 0ul, WTF::CrashOnOverflow>::at at Source/WTF/wtf/Vector.h:583
 #3 WTF::Vector<WTF::String, 0ul, WTF::CrashOnOverflow>::operator[] at Source/WTF/wtf/Vector.h:603
 #4 WebCore::PasteboardHelper::fillDataObjectFromDropData at Source/WebCore/platform/gtk/PasteboardHelper.cpp:255
 #5 WebCore::GtkDragAndDropHelper::handleDragDataReceived at Source/WebCore/platform/gtk/GtkDragAndDropHelper.cpp:155
 #6 webkit_web_view_drag_data_received at Source/WebKit/gtk/webkit/webkitwebview.cpp:1584
 #7 _gtk_marshal_VOID__OBJECT_INT_INT_BOXED_UINT_UINT at gtkmarshalers.c:5525
 #11 g_signal_emit_by_name at gsignal.c:3479
 #12 gtk_drag_selection_received at gtkdnd.c:1828

Comment 1 Pablo Ganuza 2015-11-26 11:38:21 UTC
Created attachment 1099231 [details]
File: backtrace

Comment 2 Pablo Ganuza 2015-11-26 11:38:22 UTC
Created attachment 1099232 [details]
File: cgroup

Comment 3 Pablo Ganuza 2015-11-26 11:38:24 UTC
Created attachment 1099233 [details]
File: core_backtrace

Comment 4 Pablo Ganuza 2015-11-26 11:38:27 UTC
Created attachment 1099234 [details]
File: dso_list

Comment 5 Pablo Ganuza 2015-11-26 11:38:29 UTC
Created attachment 1099235 [details]
File: environ

Comment 6 Pablo Ganuza 2015-11-26 11:38:30 UTC
Created attachment 1099236 [details]
File: exploitable

Comment 7 Pablo Ganuza 2015-11-26 11:38:31 UTC
Created attachment 1099237 [details]
File: limits

Comment 8 Pablo Ganuza 2015-11-26 11:38:35 UTC
Created attachment 1099238 [details]
File: maps

Comment 9 Pablo Ganuza 2015-11-26 11:38:37 UTC
Created attachment 1099239 [details]
File: mountinfo

Comment 10 Pablo Ganuza 2015-11-26 11:38:38 UTC
Created attachment 1099240 [details]
File: namespaces

Comment 11 Pablo Ganuza 2015-11-26 11:38:39 UTC
Created attachment 1099241 [details]
File: open_fds

Comment 12 Pablo Ganuza 2015-11-26 11:38:40 UTC
Created attachment 1099242 [details]
File: proc_pid_status

Comment 13 Pablo Ganuza 2015-11-26 11:38:42 UTC
Created attachment 1099243 [details]
File: var_log_messages

Comment 14 Fedora Admin XMLRPC Client 2016-09-15 15:17:10 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 15 Fedora Admin XMLRPC Client 2016-09-16 07:09:38 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 16 Fedora End Of Life 2016-11-24 13:45:29 UTC
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. 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 EOL if it remains open with a Fedora  'version'
of '23'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 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 this bug is closed as described in the policy above.

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 17 Fedora End Of Life 2016-12-20 16:18:58 UTC
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.