Bug 1057293

Summary:

[abrt] midori: g_type_check_instance_cast(): midori killed by SIGSEGV

Product:

[Fedora] Fedora

Reporter:

Mo <terentew-wa>

Component:

midori

Assignee:

Kevin Fenzi <kevin>

Status:

CLOSED EOL

QA Contact:

Fedora Extras Quality Assurance <extras-qa>

Severity:

unspecified

Docs Contact:

Priority:

unspecified

Version:

CC:

kevin

Target Milestone:

---

Target Release:

---

Hardware:

x86_64

OS:

Unspecified

Whiteboard:

abrt_hash:19d7128495867ae7731dc9de6e3db91aa7190147

Fixed In Version:

Doc Type:

Bug Fix

Doc Text:

Story Points:

---

Clone Of:

Environment:

Last Closed:

2015-06-30 00:52:03 UTC

Type:

---

Regression:

---

Mount Type:

---

Documentation:

---

CRM:

Verified Versions:

Category:

---

oVirt Team:

---

RHEL 7.3 requirements from Atomic Host:

Cloudforms Team:

---

Target Upstream Version:

Embargoed:

Attachments:

Description	Flags
File: backtrace	none
File: cgroup	none
File: core_backtrace	none
File: dso_list	none
File: environ	none
File: limits	none
File: maps	none
File: open_fds	none
File: proc_pid_status	none
File: var_log_messages	none
File: exploitable	none

Description Mo 2014-01-23 18:59:46 UTC

Description of problem:
ad bookmark

Version-Release number of selected component:
midori-0.5.6-1.fc20

Additional info:
reporter:       libreport-2.1.11
backtrace_rating: 4
cmdline:        midori
crash_function: g_type_check_instance_cast
executable:     /usr/bin/midori
kernel:         3.12.6-300.mx.fc20.R.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 g_type_check_instance_cast at /lib64/libgobject-2.0.so.0
 #1 midori_bookmarks_add_item_cb at /usr/src/debug/midori-0.5.6/panels/midori-bookmarks.c:225
 #6 midori_browser_edit_bookmark_dialog_new at /usr/src/debug/midori-0.5.6/midori/midori-browser.c:1236
 #11 _gtk_action_emit_activate at /lib64/libgtk-x11-2.0.so.0
 #12 _g_closure_invoke_va at /lib64/libgobject-2.0.so.0
 #15 gtk_widget_activate at /lib64/libgtk-x11-2.0.so.0
 #16 gtk_menu_shell_activate_item at /lib64/libgtk-x11-2.0.so.0
 #17 gtk_menu_shell_button_release at /lib64/libgtk-x11-2.0.so.0
 #18 _gtk_marshal_BOOLEAN__BOXED at /lib64/libgtk-x11-2.0.so.0
 #23 gtk_widget_event_internal at /lib64/libgtk-x11-2.0.so.0

Comment 1 Mo 2014-01-23 18:59:50 UTC

Created attachment 854573 [details]
File: backtrace

Comment 2 Mo 2014-01-23 18:59:53 UTC

Created attachment 854574 [details]
File: cgroup

Comment 3 Mo 2014-01-23 18:59:56 UTC

Created attachment 854575 [details]
File: core_backtrace

Comment 4 Mo 2014-01-23 18:59:59 UTC

Created attachment 854576 [details]
File: dso_list

Comment 5 Mo 2014-01-23 19:00:02 UTC

Created attachment 854577 [details]
File: environ

Comment 6 Mo 2014-01-23 19:00:05 UTC

Created attachment 854578 [details]
File: limits

Comment 7 Mo 2014-01-23 19:00:22 UTC

Created attachment 854579 [details]
File: maps

Comment 8 Mo 2014-01-23 19:00:25 UTC

Created attachment 854580 [details]
File: open_fds

Comment 9 Mo 2014-01-23 19:00:27 UTC

Created attachment 854581 [details]
File: proc_pid_status

Comment 10 Mo 2014-01-23 19:00:31 UTC

Created attachment 854582 [details]
File: var_log_messages

Comment 11 Mo 2014-01-23 19:00:34 UTC

Created attachment 854583 [details]
File: exploitable

Comment 12 Kevin Fenzi 2014-01-23 22:16:40 UTC

This happens with adding any bookmark? 

Does the problem persist with the version from updates-testing?

su
yum clean expire-cache
yum --enablerepo=updates-testing update midori

Comment 13 Mo 2014-01-28 13:10:42 UTC

yes,any bookmark,but not every time

the problem persist still after testing update

Midori 0.5.7 ((null))
GTK+ 2.24.22 (2.24.22)	Glib 2.38.2 (2.38.2)
WebKitGTK+ 2.2.3 (2.2.3)	libSoup 2.44.2
cairo 1.13.1 (1.13.1)	libnotify 0.7.6
gcr No	granite No

Comment 14 Fedora End Of Life 2015-05-29 10:38:40 UTC

This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora  'version'
of '20'.

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 20 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.

Comment 15 Fedora End Of Life 2015-06-30 00:52:03 UTC

Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.