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 542812 - crash in Computer: Navigation sur réseau lo...
crash in Computer: Navigation sur réseau lo...
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-07-13 18:44 UTC by Aurélien DUNAND
Modified: 2008-07-14 15:06 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description Aurélien DUNAND 2008-07-13 18:44:20 UTC 
Version: 2.20.0

What were you doing when the application crashed?
Navigation sur réseau local (vers un PC windows XP pro)


Distribution: Debian lenny/sid
Gnome Release: 2.22.2 2008-05-29 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-1-686 #1 SMP Thu May 8 02:16:39 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Nuvola
Icon Theme: SphereCrystal

Memory status: size: 82735104 vsize: 82735104 resident: 28450816 share: 16728064 rss: 28450816 rss_rlim: 4294967295
CPU usage: start_time: 1215944369 rtime: 1005 utime: 894 stime: 111 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6b37940 (LWP 3434)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 202719

Thread 1 (Thread 0xb6b37940 (LWP 3434))

  • #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


Susana





          2008-07-13 21:45:41 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


Aurélien DUNAND





          2008-07-14 14:41:49 UTC
        



Distribution: Debian lenny/sid
Gnome Release: 2.22.3 2008-06-30 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-1-686 #1 SMP Thu May 8 02:16:39 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Nuvola
Icon Theme: SphereCrystal

Memory status: size: 73670656 vsize: 73670656 resident: 27914240 share: 16646144 rss: 27914240 rss_rlim: 4294967295
CPU usage: start_time: 1216045507 rtime: 369 utime: 328 stime: 41 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 0xb6ad8720 (LWP 17588)]
0xffffe410 in __kernel_vsyscall ()




+
Trace
    202790






Thread 1
          (Thread 0xb6ad8720 (LWP 17588))


    

  • 
#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.10/gtk/gtkmain.c
                  line
                  1163

    

    • 

  • 
#17
main

    
                at nautilus-main.c
                  line
                  556

    

    • 

  • 
#0
__kernel_vsyscall

    • 













Comment 3


Cosimo Cecchi





          2008-07-14 15:06:04 UTC
        



Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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