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 506561 - crash in Open Folder: Clicked an icon in the f...
crash in Open Folder: Clicked an icon in the f...
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: 2007-12-31 12:17 UTC by debian
Modified: 2008-01-01 17:44 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description debian 2007-12-31 12:17:03 UTC 
Version: 2.20.0

What were you doing when the application crashed?
Clicked an icon in the folder being opened


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

System: Linux 2.6.22-3-k7 #1 SMP Mon Nov 12 09:12:50 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 150282240 vsize: 150282240 resident: 99655680 share: 15093760 rss: 99655680 rss_rlim: 4294967295
CPU usage: start_time: 1199102001 rtime: 2590 utime: 2281 stime: 309 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 0xb6bad6c0 (LWP 3277)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 183621

Thread 1 (Thread 0xb6bad6c0 (LWP 3277))

  • #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 (9 sec old) ---------------------
(nautilus:3277): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(nautilus:3277): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(nautilus:3277): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(nautilus:3277): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(nautilus:3277): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(nautilus:3277): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(nautilus:3277): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(nautilus:3277): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-01-01 17:44:17 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 ***