After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 670070 - nautilus crashed with SIGSEGV in g_thread_pool_set_max_idle_time()
nautilus crashed with SIGSEGV in g_thread_pool_set_max_idle_time()
Status: RESOLVED INCOMPLETE
Product: nautilus
Classification: Core
Component: general
3.2.x
Other Linux
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2012-02-14 14:19 UTC by Vadim Rutkovsky
Modified: 2012-02-14 19:27 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Vadim Rutkovsky 2012-02-14 14:19:30 UTC
Original Report: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/917744

Crash occurred while opening my home folder from the launcher

DistroRelease: Ubuntu 12.04
Package: nautilus 1:3.2.1-2ubuntu9

Stacktrace:
  • #0 g_thread_pool_set_max_idle_time
    at /build/buildd/glib2.0-2.31.10/./glib/gthreadpool.c line 985
  • #1 g_timeout_set_expiration
    at /build/buildd/glib2.0-2.31.10/./glib/gmain.c line 3789
  • #2 ??
  • #3 ??

Comment 1 Cosimo Cecchi 2012-02-14 19:27:19 UTC
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!