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 351819 - Nautilus hangs accessing ssh folder
Nautilus hangs accessing ssh folder
Status: RESOLVED DUPLICATE of bug 350685
Product: nautilus
Classification: Core
Component: general
2.15.x
Other All
: Normal blocker
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-08-17 19:44 UTC by Priit Laes (IRC: plaes)
Modified: 2006-08-18 06:10 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Priit Laes (IRC: plaes) 2006-08-17 19:44:00 UTC 
Please describe the problem:
Nautilus hangs accessing ssh folder

Steps to reproduce:
1. Create an ssh connection
2. Click on it
3. "Opening ... " window pops up


Actual results:
Nautilus hangs

Expected results:
Window with the ssh folder contents is opened or warning is showed that it cannot be done.

Does this happen every time?


Other information:
     eax:FFFFFFFC ebx:B7122120  ecx:00000000  edx:00000002     eflags:00000202
     esi:00000000 edi:00000000  esp:BFDA3F38  ebp:BFDA3F78     eip:FFFFE410
     cs:0073  ds:007B  es:007B  fs:0000  gs:0033  ss:007B    o d I t s z a p c 
[007B:BFDA3F38]---------------------------------------------------------[stack]
BFDA3F68 : 3B 96 06 B7  F4 0F 12 B7 - E0 2F 12 B7  00 00 00 00 ;......../......
BFDA3F58 : C6 B1 1A B7  B0 F6 13 08 - 98 3F DA BF  20 00 00 00 .........?.. ...
BFDA3F48 : 20 21 12 B7  F4 0F 12 B7 - 20 21 12 B7  30 E1 06 B7  !...... !..0...
BFDA3F38 : 78 3F DA BF  02 00 00 00 - 00 00 00 00  FE DE 0C B7 x?..............
[007B:FFFFFFFC]---------------------------------------------------------[ data]
FFFFFFFC : Error while running hook_stop:
Cannot access memory at address 0xfffffffc
0xffffe410 in __kernel_vsyscall ()
gdb> thread apply all bt
  1 Thread -1224816976 (LWP 7950)  0xffffe410 in __kernel_vsyscall ()
gdb> bt

+ Trace 70624

  • #0 __kernel_vsyscall
  • #1 __lll_mutex_lock_wait
    from /lib/libc.so.6
  • #2 _L_mutex_lock_104
    from /lib/libc.so.6
  • #3 _XReply
    at XlibInt.c line 1714
  • #4 __libc_fork
    at ../nptl/sysdeps/unix/sysv/linux/i386/../fork.c line 92
  • #5 __fork
    at ../nptl/sysdeps/unix/sysv/linux/pt-fork.c line 26
  • #6 libgnomeui_segv_handle
    at gnome-ui-init.c line 789
  • #7 <signal handler called>
  • #8 __kernel_vsyscall
  • #9 *__GI_raise
    at ../nptl/sysdeps/unix/sysv/linux/raise.c line 64
  • #10 *__GI_abort
    at abort.c line 88
  • #11 __libc_message
    at ../sysdeps/unix/sysv/linux/libc_fatal.c line 170
  • #12 malloc_printerr
  • #13 *__GI___libc_free
    at malloc.c line 3447
  • #14 IA__g_free
    at gmem.c line 187
  • #15 nautilus_recent_add_file
    at nautilus-recent.c line 76
  • #16 activate_callback
    at fm-directory-view.c line 8464
  • #17 file_list_file_ready_callback
    at nautilus-file.c line 5949
  • #18 ready_callback_call
    at nautilus-directory-async.c line 1237
  • #19 nautilus_directory_async_state_changed
    at nautilus-directory-async.c line 1849
  • #20 link_info_done
    at nautilus-directory-async.c line 2927
  • #21 lacks_link_info
    at nautilus-directory-async.c line 1709
  • #22 has_problem
    at nautilus-directory-async.c line 1741
  • #23 request_is_satisfied
    at nautilus-directory-async.c line 1810
  • #24 nautilus_directory_check_if_ready_internal
    at nautilus-directory-async.c line 1332
  • #25 vfs_file_check_if_ready
    at nautilus-vfs-file.c line 85
  • #26 nautilus_file_check_if_ready
    at nautilus-file.c line 5529
  • #27 nautilus_icon_factory_is_icon_ready_for_file
    at nautilus-icon-factory.c line 975
  • #28 nautilus_bookmark_update_icon
    at nautilus-bookmark.c line 327
  • #29 bookmark_file_changed_callback
    at nautilus-bookmark.c line 374
  • #30 IA__g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #31 IA__g_closure_invoke
    at gclosure.c line 490
  • #32 signal_emit_unlocked_R
    at gsignal.c line 2438
  • #33 IA__g_signal_emit_valist
    at gsignal.c line 2197
  • #34 IA__g_signal_emit
    at gsignal.c line 2241
  • #35 nautilus_file_emit_changed
    at nautilus-file.c line 5459
  • #36 nautilus_directory_emit_change_signals
    at nautilus-directory.c line 762
  • #37 nautilus_file_changed
    at nautilus-file.c line 5405
  • #38 get_info_callback
    at nautilus-directory-async.c line 2794
  • #39 dispatch_job_callback
    at gnome-vfs-job.c line 229
  • #40 g_idle_dispatch
    at gmain.c line 3924
  • #41 IA__g_main_context_dispatch
    at gmain.c line 2043
  • #42 g_main_context_iterate
    at gmain.c line 2675
  • #43 IA__g_main_loop_run
    at gmain.c line 2879
  • #44 IA__gtk_main
    at gtkmain.c line 1000
  • #45 main
    at nautilus-main.c line 366
  • #46 __libc_start_main
    at libc-start.c line 238
  • #47 _start 






Comment 1


Christian Kirbach





          2006-08-17 22:29:24 UTC
        



possible duplicate of bug 350685

can you try that patch, please, or update to latest cvs?






Comment 2


Priit Laes (IRC: plaes)





          2006-08-18 06:10:59 UTC
        



Yep, a dup of bug 350685

Thanks :)

*** This bug has been marked as a duplicate of 350685 ***