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 507367 - crash in File Browser: When open the nautilus b...
crash in File Browser: When open the nautilus b...
Status: RESOLVED DUPLICATE of bug 483884
Product: nautilus
Classification: Core
Component: general
2.20.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-01-04 22:03 UTC by felixdrp
Modified: 2008-01-05 18:59 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description felixdrp 2008-01-04 22:03:14 UTC 
Version: 2.20.0

What were you doing when the application crashed?
When open the nautilus browser in mi home directory


Distribution: Debian lenny/sid
Gnome Release: 2.20.2 2007-11-29 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.23-1-amd64 #1 SMP Fri Dec 21 15:18:24 UTC 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10400000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glossy
Icon Theme: gnome

Memory status: size: 75247616 vsize: 75247616 resident: 24137728 share: 15011840 rss: 24137728 rss_rlim: 18446744073709551615
CPU usage: start_time: 1199485015 rtime: 308 utime: 287 stime: 21 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/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xf6bb06c0 (LWP 8628)]
0xffffe405 in __kernel_vsyscall ()

+ Trace 184101

Thread 1 (Thread 0xf6bb06c0 (LWP 8628))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 IA__g_spawn_sync
    at /tmp/buildd/glib2.0-2.14.4/glib/gspawn.c line 369
  • #3 IA__g_spawn_command_line_sync
    at /tmp/buildd/glib2.0-2.14.4/glib/gspawn.c line 677
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 <signal handler called>
  • #6 nautilus_icon_factory_possibly_free_cached_icon
    at nautilus-icon-factory.c line 611
  • #7 g_hash_table_foreach_remove_or_steal
    at /tmp/buildd/glib2.0-2.14.4/glib/ghash.c line 620
  • #8 nautilus_icon_factory_sweep
    at nautilus-icon-factory.c line 636
  • #9 g_timeout_dispatch
    at /tmp/buildd/glib2.0-2.14.4/glib/gmain.c line 3488
  • #10 IA__g_main_context_dispatch
    at /tmp/buildd/glib2.0-2.14.4/glib/gmain.c line 2061
  • #11 g_main_context_iterate
    at /tmp/buildd/glib2.0-2.14.4/glib/gmain.c line 2694
  • #12 IA__g_main_loop_run
    at /tmp/buildd/glib2.0-2.14.4/glib/gmain.c line 2898
  • #13 IA__gtk_main
    at /gtk+2.0-2.12.3/gtk/gtkmain.c line 1163
  • #14 main
    at nautilus-main.c line 556
  • #15 __libc_start_main
    from /lib/i686/cmov/libc.so.6
  • #16 _start
  • #0 __kernel_vsyscall 


----------- .xsession-errors ---------------------
(nautilus:8628): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed
(nautilus:8628): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed
(nautilus:8628): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(nautilus:8628): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed
(nautilus:8628): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(nautilus:8628): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed
(nautilus:8628): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
warning: Lowest section in system-supplied DSO at 0xffffe000 is .hash at ffffe0b4
--------------------------------------------------
Comment 1 André Klapper 2008-01-05 18:59:15 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 483884 ***