Bug 909022

Summary: [abrt] rhythmbox-2.98-4.fc18: __memmove_ssse3_back: Process /usr/bin/rhythmbox was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Daniel Duggan <seve141>
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: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:8ad9f0b6782aca7d318d2951ad6088a3b9402f46
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-05 19:01:11 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: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Daniel Duggan 2013-02-08 04:25:14 UTC
Version-Release number of selected component:
rhythmbox-2.98-4.fc18

Additional info:
backtrace_rating: 4
cmdline:        rhythmbox http://www.nhnewsviewsblues.org/ArnieArnesen/AAA_02072013_hour1.mp3
crash_function: __memmove_ssse3_back
executable:     /usr/bin/rhythmbox
kernel:         3.7.5-201.fc18.x86_64
remote_result:  NOTFOUND
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 __memmove_ssse3_back at ../sysdeps/x86_64/multiarch/memcpy-ssse3-back.S:1554
 #1 memmove at /usr/include/bits/string3.h:57
 #2 delete at dbus-string.c:1175
 #4 _dbus_string_delete at dbus-string.c:1200
 #5 load_message at dbus-message.c:4171
 #6 _dbus_message_loader_queue_messages at dbus-message.c:4245
 #7 _dbus_transport_get_dispatch_status at dbus-transport.c:1101
 #8 _dbus_transport_queue_messages at dbus-transport.c:1128
 #9 _dbus_connection_get_dispatch_status_unlocked at dbus-connection.c:4211
 #10 dbus_connection_get_dispatch_status at dbus-connection.c:4342

Comment 1 Daniel Duggan 2013-02-08 04:25:17 UTC
Created attachment 694921 [details]
File: backtrace

Comment 2 Daniel Duggan 2013-02-08 04:25:19 UTC
Created attachment 694922 [details]
File: cgroup

Comment 3 Daniel Duggan 2013-02-08 04:25:20 UTC
Created attachment 694923 [details]
File: core_backtrace

Comment 4 Daniel Duggan 2013-02-08 04:25:22 UTC
Created attachment 694924 [details]
File: dso_list

Comment 5 Daniel Duggan 2013-02-08 04:25:23 UTC
Created attachment 694925 [details]
File: environ

Comment 6 Daniel Duggan 2013-02-08 04:25:25 UTC
Created attachment 694926 [details]
File: limits

Comment 7 Daniel Duggan 2013-02-08 04:25:26 UTC
Created attachment 694927 [details]
File: maps

Comment 8 Daniel Duggan 2013-02-08 04:25:28 UTC
Created attachment 694928 [details]
File: open_fds

Comment 9 Daniel Duggan 2013-02-08 04:25:29 UTC
Created attachment 694929 [details]
File: proc_pid_status

Comment 10 Daniel Duggan 2013-02-08 04:25:31 UTC
Created attachment 694930 [details]
File: var_log_messages

Comment 11 Fedora End Of Life 2013-12-21 11:14:05 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 12 Fedora End Of Life 2014-02-05 19:01:11 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.