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 545202 - 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-07-28 18:36 UTC by marcelolaia
Modified: 2008-07-28 18:55 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description marcelolaia 2008-07-28 18:36:00 UTC 
What were you doing when the application crashed?



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

System: Linux 2.6.25-2-686 #1 SMP Fri Jul 18 17:46:56 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 104112128 vsize: 104112128 resident: 44752896 share: 17162240 rss: 44752896 rss_rlim: 4294967295
CPU usage: start_time: 1217239513 rtime: 1102 utime: 994 stime: 108 cutime:1 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xb6b8e720 (LWP 3568)]
0xb7fbf424 in __kernel_vsyscall ()

+ Trace 204031

Thread 1 (Thread 0xb6b8e720 (LWP 3568))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 IA__g_spawn_sync
    at /tmp/buildd/glib2.0-2.16.4/glib/gspawn.c line 374
  • #3 IA__g_spawn_command_line_sync
    at /tmp/buildd/glib2.0-2.16.4/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 /tmp/buildd/glib2.0-2.16.4/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 /tmp/buildd/glib2.0-2.16.4/glib/gmain.c line 4090
  • #13 IA__g_main_context_dispatch
    at /tmp/buildd/glib2.0-2.16.4/glib/gmain.c line 2012
  • #14 g_main_context_iterate
    at /tmp/buildd/glib2.0-2.16.4/glib/gmain.c line 2645
  • #15 IA__g_main_loop_run
    at /tmp/buildd/glib2.0-2.16.4/glib/gmain.c line 2853
  • #16 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #17 main
    at nautilus-main.c line 556
  • #0 __kernel_vsyscall 


----------- .xsession-errors ---------------------
** Message: GetValue variable 2 (2)
Aviso do gerenciador de janelas: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x30000cb (Iceweasel)
Aviso do gerenciador de janelas: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Aviso do gerenciador de janelas: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x30000cb (Iceweasel)
Aviso do gerenciador de janelas: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Aviso do gerenciador de janelas: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x30000cb (Iceweasel)
Aviso do gerenciador de janelas: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
** (nautilus:3568): WARNING **: Não foi encontrada descrição para o tipo MIME "x-directory/smb-share" (o arquivo é "SharedDocs"), por favor notifique a lista de discussão do gnome-vfs.
Cannot access memory at address 0x0
Cannot access memory at address 0x0
--------------------------------------------------
Comment 1 A. Walton 2008-07-28 18:55:56 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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