Hide Forgot
Description of problem: 1) Plug the iPod Touch 1G 2) Launch rhythmbox 3) Click on the iPod icon in the left pane When run under gdb we hit: Program received signal SIGSEGV, Segmentation fault. 0x0000003f3fe318dd in type_check_is_value_type_U (type=133143986208) at gtype.c:4131 4131 if (node && node->mutatable_check_cache) It is a duplicate of: https://bugzilla.redhat.com/show_bug.cgi?id=1023745 Version-Release number of selected component: rhythmbox-2.99.1-1.fc19 Additional info: reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: rhythmbox crash_function: type_check_is_value_type_U executable: /usr/bin/rhythmbox kernel: 3.11.6-201.fc19.x86_64 runlevel: N 5 type: CCpp uid: 503 Truncated backtrace: Thread no. 1 (10 frames) #0 type_check_is_value_type_U at gtype.c:4131 #1 g_type_check_value_holds at gtype.c:4180 #2 playcounts_plist_read at itdb_itunesdb.c:1178 #3 playcounts_init at itdb_itunesdb.c:1319 #4 itdb_parse_internal at itdb_itunesdb.c:3309 #5 itdb_parse at itdb_itunesdb.c:3364 #6 rb_ipod_db_load at rb-ipod-db.c:794 #7 rb_ipod_db_new at rb-ipod-db.c:826 #8 rb_ipod_load_songs at rb-ipod-source.c:1279 #9 ensure_loaded at rb-ipod-source.c:1917
Created attachment 820776 [details] File: backtrace
Created attachment 820777 [details] File: cgroup
Created attachment 820778 [details] File: core_backtrace
Created attachment 820779 [details] File: dso_list
Created attachment 820780 [details] File: environ
Created attachment 820781 [details] File: exploitable
Created attachment 820782 [details] File: limits
Created attachment 820783 [details] File: maps
Created attachment 820784 [details] File: open_fds
Created attachment 820785 [details] File: proc_pid_status
Created attachment 820786 [details] File: var_log_messages
1. Plug iPod 1G in 2. Start rhythmbox 3. rhythmbox crashes reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: rhythmbox /run/user/1000/gvfs/afc:host=4d0beef9bf201f3d2095f37354d864d44c4b7290 crash_function: type_check_is_value_type_U executable: /usr/bin/rhythmbox kernel: 3.11.9-200.fc19.x86_64 package: rhythmbox-2.99.1-1.fc19 reason: Process /usr/bin/rhythmbox was killed by signal 11 (SIGSEGV) runlevel: N 5 type: CCpp uid: 1000
(In reply to r.v.f from comment #12) > 1. Plug iPod 1G in > 2. Start rhythmbox > 3. rhythmbox crashes > You may try to rebuild libgpod with this patch: https://bugzilla.redhat.com/attachment.cgi?id=821354&action=diff This is not the ultimate fix but it is enough to use gtkpod with my 1G.
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.