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 534199 - crash in Home Folder:
crash in Home Folder:
Status: RESOLVED DUPLICATE of bug 522534
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-05-21 14:51 UTC by alano.br
Modified: 2008-05-21 23:27 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description alano.br 2008-05-21 14:51:00 UTC 
What were you doing when the application crashed?



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

System: Linux 2.6.24-1-amd64 #1 SMP Sat May 10 09:28:10 UTC 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Nuvola
Icon Theme: Nuvola

Memory status: size: 456032256 vsize: 456032256 resident: 32600064 share: 17965056 rss: 32600064 rss_rlim: 18446744073709551615
CPU usage: start_time: 1211379900 rtime: 520 utime: 479 stime: 41 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0x2b4260059240 (LWP 3574)]
0x00002b425984fedf in waitpid () from /lib/libpthread.so.0

+ Trace 198310

Thread 1 (Thread 0x2b4260059240 (LWP 3574))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #2 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #4 <signal handler called>
  • #5 istr_hash
    at nautilus-directory-async.c line 170
  • #6 ??
    from /usr/lib/libglib-2.0.so.0
  • #7 dequeue_pending_idle_callback
    at nautilus-directory-async.c line 848
  • #8 directory_load_callback
    at nautilus-directory-async.c line 1035
  • #9 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #10 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #11 ??
    from /usr/lib/libglib-2.0.so.0
  • #12 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #13 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 main
    at nautilus-main.c line 556
  • #15 __libc_start_main
    from /lib/libc.so.6
  • #16 _start
  • #0 waitpid
    from /lib/libpthread.so.0 


----------- .xsession-errors (20 sec old) ---------------------
Playing WAVE '/usr/share/amsn/skins/default/sounds/type.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo
Playing WAVE '/usr/share/amsn/skins/default/sounds/type.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo
Playing WAVE '/usr/share/amsn/skins/default/sounds/type.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo
Playing WAVE '/usr/share/amsn/skins/default/sounds/type.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo
report junk?? Boletim do Empreendedor - Sebrae/PR
Playing WAVE '/usr/share/amsn/skins/default/sounds/type.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo
Playing WAVE '/usr/share/amsn/skins/default/sounds/type.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo
Playing WAVE '/usr/share/amsn/skins/default/sounds/type.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo
Playing WAVE '/usr/share/amsn/skins/default/sounds/type.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo
Playing WAVE '/usr/share/amsn/skins/default/sounds/type.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-05-21 23:27:57 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 ***