Description of problem: Random crash while fetching podcasts Was seeing the same crash on debian Version-Release number of selected component: rhythmbox-3.2.1-1.fc22 Additional info: reporter: libreport-2.5.1 backtrace_rating: 4 cmdline: rhythmbox crash_function: totem_pl_parser_add_itms executable: /usr/bin/rhythmbox global_pid: 5633 kernel: 4.0.4-301.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 var_log_messages: [System Logs]:\n-- Logs begin at Mon 2015-05-25 20:00:16 AEST, end at Wed 2015-06-03 06:28:05 AEST. -- Truncated backtrace: Thread no. 1 (7 frames) #0 totem_pl_parser_add_itms at totem-pl-parser-podcast.c:775 #1 totem_pl_parser_parse_internal at totem-pl-parser.c:1807 #2 totem_pl_parser_parse_with_base at totem-pl-parser.c:2122 #3 totem_pl_parser_parse at totem-pl-parser.c:2204 #4 rb_podcast_parse_load_feed at rb-podcast-parse.c:218 #5 rb_podcast_manager_thread_parse_feed at rb-podcast-manager.c:1132 #6 g_thread_proxy at gthread.c:764 Potential duplicate: bug 785456
Created attachment 1034059 [details] File: backtrace
Created attachment 1034060 [details] File: cgroup
Created attachment 1034061 [details] File: core_backtrace
Created attachment 1034062 [details] File: dso_list
Created attachment 1034063 [details] File: environ
Created attachment 1034064 [details] File: limits
Created attachment 1034065 [details] File: maps
Created attachment 1034066 [details] File: mountinfo
Created attachment 1034067 [details] File: namespaces
Created attachment 1034068 [details] File: open_fds
Created attachment 1034069 [details] File: proc_pid_status
Reported upstream with a patch https://bugzilla.redhat.com/show_bug.cgi?id=1227544
Wrong url, meant https://bugzilla.gnome.org/show_bug.cgi?id=750428
Patch commit upstream
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.