Description of problem: trying to get repo server data to modify my kickstarts with and the meta data gets slammed open like 5x and midori crashes.repo data was sent incorrectly on purpose through browser to get server information. Version-Release number of selected component: midori-0.5.11-1.fc22 Additional info: reporter: libreport-2.6.2 backtrace_rating: 4 cmdline: midori crash_function: magazine_chain_pop_head executable: /usr/bin/midori global_pid: 14550 kernel: 4.1.8-200.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 magazine_chain_pop_head at gslice.c:539 #1 thread_memory_magazine1_alloc at gslice.c:842 #2 g_slice_alloc at gslice.c:998 #3 gdk_region_rectangle at gdkregion-generic.c:169 #4 gtk_widget_region_intersect at gtkwidget.c:5293 #5 gtk_container_propagate_expose at gtkcontainer.c:2753 #6 gtk_container_expose at gtkcontainer.c:2661 #7 _gtk_marshal_BOOLEAN__BOXED at gtkmarshalers.c:86 #12 gtk_widget_event_internal at gtkwidget.c:5017 #13 gtk_widget_send_expose at gtkwidget.c:4846 Potential duplicate: bug 859037
Created attachment 1080845 [details] File: backtrace
Created attachment 1080846 [details] File: cgroup
Created attachment 1080847 [details] File: core_backtrace
Created attachment 1080848 [details] File: dso_list
Created attachment 1080849 [details] File: environ
Created attachment 1080850 [details] File: limits
Created attachment 1080851 [details] File: maps
Created attachment 1080852 [details] File: mountinfo
Created attachment 1080853 [details] File: namespaces
Created attachment 1080854 [details] File: open_fds
Created attachment 1080855 [details] File: proc_pid_status
Created attachment 1080856 [details] File: var_log_messages
Is the repo data url public? Which url?
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.