Description of problem: cryptkeeper is set to run on the start of my Gnome session. The crash happened when I clicked on its icon in the tray. It appears to be repoducable every time so far. Version-Release number of selected component: cryptkeeper-0.9.5-10.fc22 Additional info: reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: cryptkeeper crash_function: strcmp executable: /usr/bin/cryptkeeper global_pid: 4351 kernel: 4.3.4-200.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 strcmp at ../sysdeps/x86_64/strcmp.S:210 #1 is_mounted at encfs_wrapper.cpp:49 #2 sico_activated at main.cpp:507 #3 _g_closure_invoke_va at gclosure.c:831 #6 emit_activate_signal at gtkstatusicon.c:1314 #7 gtk_status_icon_button_press at gtkstatusicon.c:1804 #8 _gtk_marshal_BOOLEAN__BOXED at gtkmarshalers.c:86 #13 gtk_widget_event_internal at gtkwidget.c:5017 #14 gtk_widget_event at gtkwidget.c:4814 #15 gtk_propagate_event at gtkmain.c:2501 Potential duplicate: bug 807168
Created attachment 1129471 [details] File: backtrace
Created attachment 1129472 [details] File: cgroup
Created attachment 1129473 [details] File: core_backtrace
Created attachment 1129474 [details] File: dso_list
Created attachment 1129475 [details] File: environ
Created attachment 1129476 [details] File: limits
Created attachment 1129477 [details] File: maps
Created attachment 1129478 [details] File: mountinfo
Created attachment 1129479 [details] File: namespaces
Created attachment 1129480 [details] File: open_fds
Created attachment 1129481 [details] File: proc_pid_status
Created attachment 1129482 [details] File: var_log_messages
This appears to be the same problem that was reported in bug 1193874 and never fixed. I posted a patch there in comment #12 that kept it from crashing on me. The patch will need to be updated to the latest version of cryptkeeper. I still experience the problem under Fedora 23 if I use the unpatched distribution version of cryptkeeper.
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.