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 613506 - Segmentation fault when launching with directory specified
Segmentation fault when launching with directory specified
Status: RESOLVED OBSOLETE
Product: nautilus
Classification: Core
Component: Crashers
2.30.x
Other Linux
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-03-21 15:49 UTC by Tim Koopman
Modified: 2011-09-28 13:00 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Tim Koopman 2010-03-21 15:49:13 UTC
When launching Nautilus with a directory as an argument, Nautilus segfaults. Except if that directory happens to be the user's home directory.
After opening the home directory, all further invocations are completed without any problem.

Version is 2.28.4

Program received signal SIGSEGV, Segmentation fault.

Thread 140736969058064 (LWP 3480)

  • #0 strcmp
    from /lib/libc.so.6
  • #1 _g_local_file_info_get
    from /usr/lib/libgio-2.0.so.0
  • #2 g_local_file_query_info
    from /usr/lib/libgio-2.0.so.0
  • #3 query_info_async_thread
    from /usr/lib/libgio-2.0.so.0
  • #4 run_in_thread
    from /usr/lib/libgio-2.0.so.0
  • #5 io_job_thread
    from /usr/lib/libgio-2.0.so.0
  • #6 g_thread_pool_thread_proxy
    from /usr/lib/libglib-2.0.so.0
  • #7 g_thread_create_proxy
    from /usr/lib/libglib-2.0.so.0
  • #8 start_thread
    from /lib/libpthread.so.0
  • #9 clone
    from /lib/libc.so.6
  • #10 ??

Comment 1 Fabio Durán Verdugo 2010-03-21 22:21:58 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!
Comment 2 Tim Koopman 2010-03-22 20:45:50 UTC
(gdb) run /
Starting program: /usr/bin/nautilus /
[Thread debugging using libthread_db enabled]
[New Thread 0x7fffeae0d710 (LWP 27256)]
[Thread 0x7fffeae0d710 (LWP 27256) exited]
[New Thread 0x7fffeae0d710 (LWP 27281)]
[New Thread 0x7fffe375c710 (LWP 27282)]
[Thread 0x7fffe375c710 (LWP 27282) exited]
[New Thread 0x7fffe375c710 (LWP 27283)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffeae0d710 (LWP 27281)]
strcmp () at ../sysdeps/x86_64/strcmp.S:100
100		movlpd	(%rsi), %xmm2
(gdb) thread apply all bt
[New Thread 0x7fffda8ab710 (LWP 27284)]

Thread 6 (Thread 0x7fffda8ab710 (LWP 27284))

  • #0 clone
    at ../sysdeps/unix/sysv/linux/x86_64/clone.S line 84
  • #1 ??
    at pthread_create.c line 216
  • #2 ??
  • #3 ??

Thread 5 (Thread 0x7fffe375c710 (LWP 27283))

  • #0 __lll_lock_wait
    at ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S line 136
  • #1 _L_cond_lock_1024
    from /lib/libpthread.so.0
  • #2 __pthread_mutex_cond_lock
    at ../nptl/pthread_mutex_lock.c line 61
  • #3 pthread_cond_timedwait
    at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S line 298
  • #4 g_cond_timed_wait_posix_impl
    at gthread-posix.c line 242
  • #5 g_async_queue_pop_intern_unlocked
    at gasyncqueue.c line 365
  • #6 g_thread_pool_wait_for_new_task
    at gthreadpool.c line 220
  • #7 g_thread_pool_thread_proxy
    at gthreadpool.c line 254
  • #8 g_thread_create_proxy
    at gthread.c line 635
  • #9 start_thread
    at pthread_create.c line 297
  • #10 clone
    at ../sysdeps/unix/sysv/linux/x86_64/clone.S line 112
  • #11 ??

Thread 3 (Thread 0x7fffeae0d710 (LWP 27281))

  • #0 strcmp
    at ../sysdeps/x86_64/strcmp.S line 100
  • #1 _g_local_file_info_get
    at glocalfileinfo.c line 1598
  • #2 g_local_file_query_info
    at glocalfile.c line 1186
  • #3 query_info_async_thread
    at gfile.c line 4670
  • #4 run_in_thread
    at gsimpleasyncresult.c line 676
  • #5 io_job_thread
    at gioscheduler.c line 182
  • #6 g_thread_pool_thread_proxy
    at gthreadpool.c line 265
  • #7 g_thread_create_proxy
    at gthread.c line 635
  • #8 start_thread
    at pthread_create.c line 297
  • #9 clone
    at ../sysdeps/unix/sysv/linux/x86_64/clone.S line 112
  • #10 ??

Thread 1 (Thread 0x7ffff7fbe760 (LWP 26964))

  • #0 clone
    at ../sysdeps/unix/sysv/linux/x86_64/clone.S line 84
  • #1 do_clone
    at ../nptl/sysdeps/pthread/createthread.c line 75
  • #2 create_thread
    at ../nptl/sysdeps/pthread/createthread.c line 205
  • #3 __pthread_create_2_1
    at pthread_create.c line 550
  • #4 g_thread_create_posix_impl
    at gthread-posix.c line 355
  • #5 IA__g_thread_create_full
    at gthread.c line 663
  • #6 g_thread_pool_start_thread
    at gthreadpool.c line 366
  • #7 IA__g_thread_pool_push
    at gthreadpool.c line 504
  • #8 g_file_real_query_info_async
    at gfile.c line 4700
  • #9 set_metadata_callback
    at nautilus-vfs-file.c line 136
  • #10 complete_in_idle_cb_for_thread
    at gsimpleasyncresult.c line 650
  • #11 g_main_dispatch
    at gmain.c line 1960
  • #12 IA__g_main_context_dispatch
    at gmain.c line 2513
  • #13 g_main_context_iterate
    at gmain.c line 2591
  • #14 IA__g_main_loop_run
    at gmain.c line 2799
  • #15 IA__gtk_main
    at gtkmain.c line 1218
  • #16 main
    at nautilus-main.c line 544

Comment 3 Cosimo Cecchi 2010-04-09 10:37:20 UTC
Not reproducible here with Nautilus 2.30 and GLib 2.24.
Please reopen if you can still see the bug with an up-to-date GNOME stack.
Comment 4 Tim Koopman 2010-04-09 10:58:46 UTC
Problem is still there using Nautilus 2.30.0 and glib 2.24.0. 
Forgot to say that this problem only happens if Nautilus is not running yet. So desktop rendering has to be turned off.

  • #0 strcmp
    from /lib/libc.so.6
  • #1 _g_local_file_info_get
    at glocalfileinfo.c line 1600
  • #2 g_local_file_query_info
    at glocalfile.c line 1192
  • #3 query_info_async_thread
    at gfile.c line 4824
  • #4 run_in_thread
    at gsimpleasyncresult.c line 679
  • #5 io_job_thread
    at gioscheduler.c line 182
  • #6 g_thread_pool_thread_proxy
    at gthreadpool.c line 315
  • #7 g_thread_create_proxy
    at gthread.c line 1893
  • #8 start_thread
    from /lib/libpthread.so.0
  • #9 clone
    from /lib/libc.so.6
  • #10 ??

Comment 5 Cosimo Cecchi 2010-04-09 11:18:04 UTC
I still can't reproduce. Which directory are you trying to open? Do you have permissions there? Are you using spatial mode or browser mode?

Could you paste here the command line you use to spawn Nautilus?
Comment 6 Tim Koopman 2010-04-09 11:40:12 UTC
Any directory that is not my home directory.

$ nautilus /
Segmentation fault
$ nautilus ~/src
Segmentation fault

While rummaging through the gconf options to enable spatial view, I disabled desktop_is_home_dir and now it works. Although that is not really what I want.
Comment 7 Akhil Laddha 2011-09-28 06:42:23 UTC
Can you please check again whether this issue still happens in GNOME 3.0.2 or 3.2 and update this report by adding a comment and changing the "Version"
field? Thanks a lot.
Comment 8 Tim Koopman 2011-09-28 09:01:04 UTC
It works in 3.0.2
Comment 9 Cosimo Cecchi 2011-09-28 13:00:02 UTC
Thanks, closing as OBSOLETE then.