Description of problem: I pressed the Syncronize button to sync my android phone Version-Release number of selected component: rhythmbox-3.0.1-3.fc20 Additional info: reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: rhythmbox crash_function: rb_sync_settings_sync_category executable: /usr/bin/rhythmbox kernel: 3.12.6-300.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 rb_sync_settings_sync_category at rb-sync-settings.c:170 #1 build_sync_itinerary at rb-sync-state.c:296 #2 rb_sync_state_update at rb-sync-state.c:381 #3 impl_constructed at rb-sync-state.c:466 #4 g_object_new_internal at gobject.c:1785 #5 g_object_new_valist at gobject.c:2002 #7 rb_sync_state_new at rb-sync-state.c:447 #8 update_sync at rb-media-player-source.c:365 #9 sync_idle_cb_update_sync at rb-media-player-source.c:783 #13 g_main_context_iteration at gmain.c:3774 Potential duplicate: bug 701746
Created attachment 845559 [details] File: backtrace
Created attachment 845560 [details] File: cgroup
Created attachment 845561 [details] File: core_backtrace
Created attachment 845562 [details] File: dso_list
Created attachment 845563 [details] File: environ
Created attachment 845564 [details] File: exploitable
Created attachment 845565 [details] File: limits
Created attachment 845566 [details] File: maps
Created attachment 845567 [details] File: open_fds
Created attachment 845568 [details] File: proc_pid_status
Created attachment 845569 [details] File: var_log_messages
I've hit this one also.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 '20'. 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 20 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.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.