Bug 1135809

Summary: [abrt] bijiben: on_owncloud_volume_mounted(): bijiben killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Jim Campbell <jim>
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
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/897b4ff5983a7838a5e2e081c239c8efae44175e
Whiteboard: abrt_hash:57b8d04480f44c883ed90ab67689d218b41f1f56
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 12:04:59 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: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Jim Campbell 2014-08-31 21:03:49 UTC 
Description of problem:
I opened bijiben, and then started typing into a note. It crashed immediately. 

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

Additional info:
reporter:       libreport-2.2.3
backtrace_rating: 4
cmdline:        bijiben
crash_function: on_owncloud_volume_mounted
executable:     /usr/bin/bijiben
kernel:         3.17.0-0.rc2.git3.1.fc22.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (6 frames)
 #0 on_owncloud_volume_mounted
 #1 g_simple_async_result_complete at /lib64/libgio-2.0.so.0
 #2 complete_in_idle_cb at /lib64/libgio-2.0.so.0
 #4 g_main_context_iterate.isra at /lib64/libglib-2.0.so.0
 #5 g_main_context_iteration at /lib64/libglib-2.0.so.0
 #6 g_application_run at /lib64/libgio-2.0.so.0
Comment 1 Jim Campbell 2014-08-31 21:03:51 UTC 
Created attachment 933187 [details]
File: backtrace
Comment 2 Jim Campbell 2014-08-31 21:03:52 UTC 
Created attachment 933188 [details]
File: cgroup
Comment 3 Jim Campbell 2014-08-31 21:03:53 UTC 
Created attachment 933189 [details]
File: core_backtrace
Comment 4 Jim Campbell 2014-08-31 21:03:54 UTC 
Created attachment 933190 [details]
File: dso_list
Comment 5 Jim Campbell 2014-08-31 21:03:54 UTC 
Created attachment 933191 [details]
File: environ
Comment 6 Jim Campbell 2014-08-31 21:03:55 UTC 
Created attachment 933192 [details]
File: exploitable
Comment 7 Jim Campbell 2014-08-31 21:03:56 UTC 
Created attachment 933193 [details]
File: limits
Comment 8 Jim Campbell 2014-08-31 21:03:57 UTC 
Created attachment 933194 [details]
File: maps
Comment 9 Jim Campbell 2014-08-31 21:03:58 UTC 
Created attachment 933195 [details]
File: open_fds
Comment 10 Jim Campbell 2014-08-31 21:03:59 UTC 
Created attachment 933196 [details]
File: proc_pid_status
Comment 11 Jim Campbell 2014-08-31 21:03:59 UTC 
Created attachment 933197 [details]
File: var_log_messages
Comment 12 Pierre-Yves Luyten 2014-09-01 21:18:55 UTC 
making as https://bugzilla.gnome.org/show_bug.cgi?id=735492
Comment 13 Jaroslav Reznik 2015-03-03 16:15:52 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Comment 14 Fedora End Of Life 2016-07-19 12:04:59 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.