Description of problem: How to reproduce the crash: - Start midori - Top-right menù - Preferences - "Extensions" tab - Advertisement blocker 0.6 preferences - Exit from the configuration window I suspect that the problem is related with the extension (indeed everything seems to start from the configuration window of the "Advertisement blocker" extension. Version-Release number of selected component: midori-0.4.6-1.fc17 Additional info: libreport version: 2.0.18 abrt_version: 2.0.18 backtrace_rating: 4 cmdline: midori crash_function: g_type_check_value kernel: 3.6.10-2.fc17.x86_64 truncated backtrace: :Thread no. 1 (10 frames) : #0 g_type_check_value at gtype.c:4140 : #1 g_value_unset at gvalue.c:271 : #4 _g_closure_invoke_va at gclosure.c:840 : #7 gtk_real_button_released at gtkbutton.c:1725 : #13 gtk_button_button_release at gtkbutton.c:1617 : #15 _gtk_marshal_BOOLEAN__BOXED at gtkmarshalers.c:86 : #20 gtk_widget_event_internal at gtkwidget.c:5017 : #21 gtk_widget_event at gtkwidget.c:4814 : #22 gtk_propagate_event at gtkmain.c:2490 : #23 gtk_main_do_event at gtkmain.c:1685
Created attachment 674284 [details] File: core_backtrace
Created attachment 674285 [details] File: environ
Created attachment 674286 [details] File: limits
Created attachment 674287 [details] File: backtrace
Created attachment 674288 [details] File: cgroup
Created attachment 674289 [details] File: smolt_data
Created attachment 674290 [details] File: xsession_errors
Created attachment 674291 [details] File: executable
Created attachment 674292 [details] File: maps
Created attachment 674293 [details] File: dso_list
Created attachment 674294 [details] File: proc_pid_status
Created attachment 674295 [details] File: open_fds
Created attachment 674296 [details] File: var_log_messages
So, the crash always happens after going to the ad blocker prefs window?
Yes. It happens systematically. The two steps required (for my setting) to reproduce the bug: http://tinypic.com/r/2ywh45i/6 http://tinypic.com/r/10gmizc/6 If I can help you in any other way let me know! Thanks for your efforts.
Can you try this scratch build and see if the problem persists? http://koji.fedoraproject.org/koji/taskinfo?taskID=4863660
The problem seems to be fixed. Thanks :)
Sadly, pushing this as a general update to f17 is not too good either, as it changes behavior/interface some. I'll ponder the tradeoffs here...
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 WONTFIX if it remains open with a Fedora 'version' of '17'. 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 prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 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 to Fedora 17's end of life. 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 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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. Thank you for reporting this bug and we are sorry it could not be fixed.