Version-Release number of selected component: usermode-gtk-1.111-4.fc20 Additional info: reporter: libreport-2.1.12 backtrace_rating: 4 cmdline: /usr/bin/hddtemp -q /dev/sdb crash_function: g_thread_new executable: /usr/bin/consolehelper-gtk kernel: 3.12.8-300.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #2 g_thread_new at gthread.c:840 #3 _g_dbus_shared_thread_ref at gdbusprivate.c:306 #4 _g_dbus_worker_new at gdbusprivate.c:1680 #5 initable_init at gdbusconnection.c:2652 #6 g_bus_get_sync at gdbusconnection.c:7033 #7 g_daemon_vfs_init at gdaemonvfs.c:297 #8 g_type_create_instance at gtype.c:1868 #9 g_object_new_internal at gobject.c:1746 #12 try_implementation at giomodule.c:759 #13 _g_io_module_get_default at giomodule.c:858
Created attachment 870215 [details] File: backtrace
Created attachment 870216 [details] File: cgroup
Created attachment 870217 [details] File: core_backtrace
Created attachment 870218 [details] File: dso_list
Created attachment 870219 [details] File: environ
Created attachment 870220 [details] File: limits
Created attachment 870221 [details] File: maps
Created attachment 870222 [details] File: open_fds
Created attachment 870223 [details] File: proc_pid_status
Created attachment 870224 [details] File: var_log_messages
Thanks for your report. The backtrace is: > giomodule.c: try_implementation # Sufficient error handling > .,. > gvfs/...: g_daemon_vfs_init # Sufficient error handling for the try_implementation caller at least > g_bus_get_sync # OK error handling > gdbusconnection.c:initable_init # Can return an error > _g_dbus_worker_new # Cannot return an error > _g_dbus_shared_thread_ref # Cannot return an error > g_thread_new # Fails, aborts on error Per bug #1011179, callers should use g_thread_try_new() to be able to deal with failures. Because g_bus_get_sync as an API does support returning an error, it's unexpected that _g_dbus_* just fails on an error. Looking at the various abrt reports around g_thread_new(), a failure to create a thread is not so unusual, so it seems GLib users should be able to, or at least should have the option to, handle such a situation without aborting. To reproduce: choose an "appropriate" value of $N, and run > (ulimit -u $N; mock --help) "appropriate" is about number of user's threads, about $(ps x m|wc -l) - $(ps x|wc -l) . Very low values will cause bash reporting errors; $N -1 will result in > Cannot fork(). and $N in > (mock:10532): GLib-ERROR **: creating thread 'gmain': Error creating thread: Resource temporarily unavailable
I filled upstream bug report for the issue: https://bugzilla.gnome.org/show_bug.cgi?id=731554
Upstream rejected your challenge, you might want to re-open because it is still a bug
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.
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.