Bug 1236285

Summary: [abrt] bijiben: biji_item_delete(): bijiben killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Milan Zink <mzink>
Component: bijibenAssignee: Pierre-Yves Luyten <py>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: py, srrosten
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/d658160e45ca8b73b0ff6a22a728880c530f3add
Whiteboard: abrt_hash:fc67f644f9483ffe3eeb4aa372403a4de4dc5c3e
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 15:05:11 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: mountinfo
none
File: namespaces
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Milan Zink 2015-06-27 10:06:03 UTC 
Description of problem:
Hello, bijiben (or gnome notes crashed) on right-click over empty note. Unfortunately, I'm not able to reproduce it again.

Version-Release number of selected component:
bijiben-3.16.2-1.fc22

Additional info:
reporter:       libreport-2.6.0
backtrace_rating: 4
cmdline:        bijiben
crash_function: biji_item_delete
executable:     /usr/bin/bijiben
global_pid:     14337
kernel:         4.0.5-300.fc22.x86_64
runlevel:       N 5
type:           CCpp
uid:            24473

Truncated backtrace:
Thread no. 1 (10 frames)
 #1 biji_item_delete at biji-item.c:290
 #6 gtk_widget_dispose at gtkwidget.c:11967
 #7 webkit_web_view_dispose at Source/WebKit/gtk/webkit/webkitwebview.cpp:1389
 #9 gtk_scrolled_window_forall at gtkscrolledwindow.c:2252
 #10 gtk_container_destroy at gtkcontainer.c:1524
 #15 gtk_widget_dispose at gtkwidget.c:11967
 #17 gtk_overlay_forall at gtkoverlay.c:526
 #18 gtk_container_destroy at gtkcontainer.c:1524
 #23 gtk_widget_dispose at gtkwidget.c:11967
 #25 gtk_widget_destroy at gtkwidget.c:4794
Comment 1 Milan Zink 2015-06-27 10:06:07 UTC 
Created attachment 1043854 [details]
File: backtrace
Comment 2 Milan Zink 2015-06-27 10:06:08 UTC 
Created attachment 1043855 [details]
File: cgroup
Comment 3 Milan Zink 2015-06-27 10:06:10 UTC 
Created attachment 1043856 [details]
File: core_backtrace
Comment 4 Milan Zink 2015-06-27 10:06:12 UTC 
Created attachment 1043857 [details]
File: dso_list
Comment 5 Milan Zink 2015-06-27 10:06:14 UTC 
Created attachment 1043858 [details]
File: environ
Comment 6 Milan Zink 2015-06-27 10:06:15 UTC 
Created attachment 1043859 [details]
File: limits
Comment 7 Milan Zink 2015-06-27 10:06:17 UTC 
Created attachment 1043860 [details]
File: maps
Comment 8 Milan Zink 2015-06-27 10:06:19 UTC 
Created attachment 1043861 [details]
File: mountinfo
Comment 9 Milan Zink 2015-06-27 10:06:20 UTC 
Created attachment 1043862 [details]
File: namespaces
Comment 10 Milan Zink 2015-06-27 10:06:21 UTC 
Created attachment 1043863 [details]
File: open_fds
Comment 11 Milan Zink 2015-06-27 10:06:23 UTC 
Created attachment 1043864 [details]
File: proc_pid_status
Comment 12 Milan Zink 2015-06-27 10:06:24 UTC 
Created attachment 1043865 [details]
File: var_log_messages
Comment 13 Fedora End Of Life 2016-07-19 15:05:11 UTC 
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.