Bug 872744

Summary: [abrt] rhythmbox-2.98-4.fc18: Process /usr/bin/rhythmbox was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Hein Kerstgens <kerstgens>
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:ad140f6ebd0e6c18858764c8919e0de824d846a1
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-05 12:49:34 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: core_backtrace
none
File: environ
none
File: backtrace
none
File: limits
none
File: cgroup
none
File: executable
none
File: maps
none
File: dso_list
none
File: proc_pid_status
none
File: open_fds
none
File: var_log_messages
none
File: build_ids none

Description Hein Kerstgens 2012-11-02 21:28:45 UTC 
Description of problem:
copy a file to mobile device caused a crash

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

Additional info:
libreport version: 2.0.18
abrt_version:   2.0.17
backtrace_rating: 4
cmdline:        rhythmbox
crash_function: rhythmdb_query_model_artist_sort_func
kernel:         3.6.3-3.fc18.x86_64

truncated backtrace:
:Thread no. 1 (10 frames)
: #0 rhythmdb_query_model_artist_sort_func at rhythmdb-query-model.c:3012
: #1 node_find_closest at gsequence.c:1764
: #2 node_insert_sorted at gsequence.c:2002
: #3 g_sequence_insert_sorted_iter at gsequence.c:1027
: #4 g_sequence_insert_sorted at gsequence.c:717
: #5 rhythmdb_query_model_insert_into_main_list at rhythmdb-query-model.c:1322
: #6 rhythmdb_query_model_do_insert at rhythmdb-query-model.c:1626
: #12 rhythmdb_emit_entry_signals_idle at rhythmdb.c:1341
: #16 g_main_context_iteration at gmain.c:3351
: #17 g_application_run at gapplication.c:1624
Comment 1 Hein Kerstgens 2012-11-02 21:28:48 UTC 
Created attachment 637264 [details]
File: core_backtrace
Comment 2 Hein Kerstgens 2012-11-02 21:28:50 UTC 
Created attachment 637265 [details]
File: environ
Comment 3 Hein Kerstgens 2012-11-02 21:28:53 UTC 
Created attachment 637266 [details]
File: backtrace
Comment 4 Hein Kerstgens 2012-11-02 21:28:55 UTC 
Created attachment 637267 [details]
File: limits
Comment 5 Hein Kerstgens 2012-11-02 21:28:57 UTC 
Created attachment 637268 [details]
File: cgroup
Comment 6 Hein Kerstgens 2012-11-02 21:28:59 UTC 
Created attachment 637269 [details]
File: executable
Comment 7 Hein Kerstgens 2012-11-02 21:29:04 UTC 
Created attachment 637270 [details]
File: maps
Comment 8 Hein Kerstgens 2012-11-02 21:29:07 UTC 
Created attachment 637271 [details]
File: dso_list
Comment 9 Hein Kerstgens 2012-11-02 21:29:09 UTC 
Created attachment 637272 [details]
File: proc_pid_status
Comment 10 Hein Kerstgens 2012-11-02 21:29:11 UTC 
Created attachment 637273 [details]
File: open_fds
Comment 11 Hein Kerstgens 2012-11-02 21:29:13 UTC 
Created attachment 637274 [details]
File: var_log_messages
Comment 12 Hein Kerstgens 2012-11-02 21:29:15 UTC 
Created attachment 637275 [details]
File: build_ids
Comment 13 Fedora End Of Life 2013-12-21 09:16:07 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 12:49:40 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.