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
Created attachment 933187 [details] File: backtrace
Created attachment 933188 [details] File: cgroup
Created attachment 933189 [details] File: core_backtrace
Created attachment 933190 [details] File: dso_list
Created attachment 933191 [details] File: environ
Created attachment 933192 [details] File: exploitable
Created attachment 933193 [details] File: limits
Created attachment 933194 [details] File: maps
Created attachment 933195 [details] File: open_fds
Created attachment 933196 [details] File: proc_pid_status
Created attachment 933197 [details] File: var_log_messages
making as https://bugzilla.gnome.org/show_bug.cgi?id=735492
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
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.