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 536642 - crash in Home Folder: opened folder on win2k s...
crash in Home Folder: opened folder on win2k s...
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-06-04 16:22 UTC by info
Modified: 2008-06-04 19:36 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description info 2008-06-04 16:22:12 UTC 
What were you doing when the application crashed?
opened folder on win2k share


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

System: Linux 2.6.25-2-486 #1 Wed May 14 15:56:16 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Mist
Icon Theme: Mist

Memory status: size: 161075200 vsize: 161075200 resident: 88842240 share: 17920000 rss: 88842240 rss_rlim: 4294967295
CPU usage: start_time: 1212556477 rtime: 29051 utime: 27555 stime: 1496 cutime:248 cstime: 106 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xb6b52720 (LWP 23624)]
0xb7f06430 in __kernel_vsyscall ()

+ Trace 199573

Thread 1 (Thread 0xb6b52720 (LWP 23624))

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


----------- .xsession-errors ---------------------
[00000537] main playlist: nothing to play
[00000537] main playlist: stopping playback
** (update-notifier:23643): WARNING **: no cdrom: disk
closing
Fenstermanager-Warnung:Received a _NET_WM_MOVERESIZE message for 0x141fc50 (Dokumente ); these messages lack timestamps and therefore suck.
Fenstermanager-Warnung:Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x800114 (Zugriff au)
Fenstermanager-Warnung: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!!!
Cannot access memory at address 0x0
Cannot access memory at address 0x0
--------------------------------------------------
Comment 1 Pedro Villavicencio 2008-06-04 19:36:11 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 ***