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 525608 - crash in Home Folder:
crash in Home Folder:
Status: RESOLVED DUPLICATE of bug 525181
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-04-01 18:33 UTC by alano.br
Modified: 2008-04-04 10:46 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description alano.br 2008-04-01 18:33:44 UTC 
What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.22.0 2008-03-14 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-1-amd64 #1 SMP Mon Feb 11 13:47:43 UTC 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Industrial
Icon Theme: Noia

Memory status: size: 449323008 vsize: 449323008 resident: 26976256 share: 17899520 rss: 26976256 rss_rlim: 18446744073709551615
CPU usage: start_time: 1207074782 rtime: 149 utime: 132 stime: 17 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/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x2b2fe56e5b80 (LWP 13642)]
(no debugging symbols found)
0x00002b2fdf1f334f in waitpid () from /lib/libpthread.so.0

+ Trace 193923

Thread 1 (Thread 0x2b2fe56e5b80 (LWP 13642))

  • #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 ??
  • #6 ??
    from /usr/lib/libglib-2.0.so.0
  • #7 ??
  • #8 ??
  • #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 ??
  • #15 __libc_start_main
    from /lib/libc.so.6
  • #16 ??
  • #17 ??
  • #18 ??
  • #0 waitpid
    from /lib/libpthread.so.0 


----------- .xsession-errors ---------------------
 InfoLayer :: Show (Vector* vec...
 InfoLayer :: Show (Vector* vec...
Aviso do gerenciador de janelas: Janela WM_TRANSIENT_FOR inválida 0x2800016 especificada para 0x285e38d (Selecciona).
Aviso do gerenciador de janelas: Janela WM_TRANSIENT_FOR inválida 0x2800016 especificada para 0x285e6a5 (Selecciona).
Aviso do gerenciador de janelas: Janela WM_TRANSIENT_FOR inválida 0x2800016 especificada para 0x285e98b (Selecciona).
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
Initializing gnome-mount extension
Initializing gnome-mount extension
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-04-04 10:46:10 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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