Description of problem: # start rhythmbox # connect apple ios 6 device # drag & drop songs from rhytmbox library on to the device # crash Version-Release number of selected component: rhythmbox-2.99.1-1.fc19 Additional info: reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: rhythmbox crash_function: lockdownd_start_service executable: /usr/bin/rhythmbox kernel: 3.9.8-300.fc19.x86_64 runlevel: N 5 uid: 13346 xsession_errors: Truncated backtrace: Thread no. 1 (10 frames) #0 lockdownd_start_service at lockdown.c:1518 #1 itdb_iphone_start_sync at itdb_iphone.c:105 #2 itdb_start_sync at itdb_itunesdb.c:6299 #3 rb_ipod_db_save_async at rb-ipod-db.c:903 #4 rb_ipod_db_add_track_internal at rb-ipod-db.c:421 #5 rb_ipod_db_add_track at rb-ipod-db.c:465 #6 impl_track_added at rb-ipod-source.c:1644 #7 rb_transfer_target_track_added at rb-transfer-target.c:137 #8 rb_marshal_VOID__BOXED_STRING_UINT64_STRING_POINTER at rb-marshal.c:1327 #13 track_transfer_completed at rb-track-transfer-batch.c:486
Created attachment 767397 [details] File: backtrace
Created attachment 767398 [details] File: cgroup
Created attachment 767399 [details] File: core_backtrace
Created attachment 767400 [details] File: dso_list
Created attachment 767401 [details] File: environ
Created attachment 767402 [details] File: limits
Created attachment 767403 [details] File: maps
Created attachment 767404 [details] File: open_fds
Created attachment 767405 [details] File: proc_pid_status
Created attachment 767406 [details] File: var_log_messages
Connected my iPod to the laptop. Tried to browse the songs on it. Segfault occurred. reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: rhythmbox crash_function: lockdownd_start_service executable: /usr/bin/rhythmbox kernel: 3.9.8-300.fc19.x86_64 package: rhythmbox-2.99.1-1.fc19 reason: Process /usr/bin/rhythmbox was killed by signal 11 (SIGSEGV) runlevel: N 5 uid: 1000 xsession_errors:
adding music...160GB reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: rhythmbox crash_function: lockdownd_start_service executable: /usr/bin/rhythmbox kernel: 3.9.9-301.fc19.i686.PAE package: rhythmbox-2.99.1-1.fc19 reason: Process /usr/bin/rhythmbox was killed by signal 11 (SIGSEGV) runlevel: N 5 uid: 1000
plugins|enable ipod connectivity. found unitialized ipod want to initialize ? type ipod 16GB myPhone Yes. reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: rhythmbox crash_function: lockdownd_start_service executable: /usr/bin/rhythmbox kernel: 3.9.9-302.fc19.x86_64 package: rhythmbox-2.99.1-1.fc19 reason: Process /usr/bin/rhythmbox was killed by signal 11 (SIGSEGV) runlevel: N 5 uid: 1000 xsession_errors:
Seeing this issue here as well.
Ping? Is there any other information that would be helpful for you to have for this?
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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 19 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 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.