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 528768 - crash in File Browser: Open a shared folder on ...
crash in File Browser: Open a shared folder on ...
Status: RESOLVED DUPLICATE of bug 522534
Product: nautilus
Classification: Core
Component: general
2.20.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-04-18 16:02 UTC by odinoxp
Modified: 2008-04-23 00:11 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description odinoxp 2008-04-18 16:02:46 UTC 
Version: 2.20.0

What were you doing when the application crashed?
Open a shared folder on windows pc


Distribution: Debian lenny/sid
Gnome Release: 2.22.1 2008-04-08 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24.3 #2 SMP PREEMPT Sun Mar 23 22:55:03 CET 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 92667904 vsize: 92667904 resident: 30007296 share: 16510976 rss: 30007296 rss_rlim: 4294967295
CPU usage: start_time: 1208534412 rtime: 341 utime: 315 stime: 26 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/nautilus'

(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6c0c720 (LWP 2961)]
[New Thread 0xb4abfb90 (LWP 2986)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 195555

Thread 1 (Thread 0xb6c0c720 (LWP 2961))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 <signal handler called>
  • #6 ??
  • #7 ??
  • #8 ??
  • #9 ??
  • #10 ??
    from /usr/lib/libglib-2.0.so.0
  • #11 ??
  • #12 ??
  • #13 ??
  • #14 ??
    from /usr/lib/libglib-2.0.so.0
  • #15 ??
  • #0 __kernel_vsyscall 






Comment 1


Bruno Boaventura





          2008-04-18 21:47:46 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


odinoxp





          2008-04-21 08:12:28 UTC
        



Distribution: Debian lenny/sid
Gnome Release: 2.22.1 2008-04-08 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24.3 #2 SMP PREEMPT Sun Mar 23 22:55:03 CET 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 95670272 vsize: 95670272 resident: 24465408 share: 16482304 rss: 24465408 rss_rlim: 4294967295
CPU usage: start_time: 1208765049 rtime: 332 utime: 308 stime: 24 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/nautilus'

[Thread debugging using libthread_db enabled]
[New Thread 0xb6bb5720 (LWP 5270)]
[New Thread 0xb54c2b90 (LWP 5429)]
[New Thread 0xb4cc1b90 (LWP 5427)]
0xffffe410 in __kernel_vsyscall ()




+
Trace
    195746






Thread 1
          (Thread 0xb6bb5720 (LWP 5270))


    

  • 
#0
__kernel_vsyscall

    • 

  • 
#1
waitpid

    
                from
                /lib/i686/cmov/libpthread.so.0

    

    • 

  • 
#2
IA__g_spawn_sync

    
                at /build/buildd/glib2.0-2.16.3/glib/gspawn.c
                  line
                  374

    

    • 

  • 
#3
IA__g_spawn_command_line_sync

    
                at /build/buildd/glib2.0-2.16.3/glib/gspawn.c
                  line
                  682

    

    • 

  • 
#4
??

    
                from
                /usr/lib/gtk-2.0/modules/libgnomebreakpad.so

    

    • 

  • 
#5
<signal handler called>

    • 

  • 
#6
istr_hash

    
                at nautilus-directory-async.c
                  line
                  170

    

    • 

  • 
#7
g_hash_table_insert_internal

    
                at /build/buildd/glib2.0-2.16.3/glib/ghash.c
                  line
                  118

    

    • 

  • 
#8
istr_set_insert

    
                at nautilus-directory-async.c
                  line
                  189

    

    • 

  • 
#9
dequeue_pending_idle_callback

    
                at nautilus-directory-async.c
                  line
                  848

    

    • 

  • 
#10
directory_load_callback

    
                at nautilus-directory-async.c
                  line
                  1035

    

    • 

  • 
#11
dispatch_job_callback

    
                at gnome-vfs-job.c
                  line
                  237

    

    • 

  • 
#12
g_idle_dispatch

    
                at /build/buildd/glib2.0-2.16.3/glib/gmain.c
                  line
                  4087

    

    • 

  • 
#13
IA__g_main_context_dispatch

    
                at /build/buildd/glib2.0-2.16.3/glib/gmain.c
                  line
                  2009

    

    • 

  • 
#14
g_main_context_iterate

    
                at /build/buildd/glib2.0-2.16.3/glib/gmain.c
                  line
                  2642

    

    • 

  • 
#15
IA__g_main_loop_run

    
                at /build/buildd/glib2.0-2.16.3/glib/gmain.c
                  line
                  2850

    

    • 

  • 
#16
IA__gtk_main

    
                at /tmp/buildd/gtk+2.0-2.12.9/gtk/gtkmain.c
                  line
                  1163

    

    • 

  • 
#17
main

    
                at nautilus-main.c
                  line
                  556

    

    • 

  • 
#0
__kernel_vsyscall

    • 













Comment 3


André Klapper





          2008-04-23 00:11:40 UTC
        



same trace as bug 522534 comment 201.






Comment 4


André Klapper





          2008-04-23 00:11:53 UTC
        




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