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 488581 - crash in Open Folder: retirned from filing ano...
crash in Open Folder: retirned from filing ano...
Status: RESOLVED DUPLICATE of bug 439977
Product: nautilus
Classification: Core
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-10-20 11:35 UTC by Thomas M Steenholdt
Modified: 2007-10-20 14:41 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description Thomas M Steenholdt 2007-10-20 11:35:48 UTC
Version: 2.18.3

What were you doing when the application crashed?
retirned from filing another bug (last one i'll report - probably the same)


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.23.1-4.fc7 #1 SMP Fri Oct 12 20:26:14 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks_Cairo-Hedgehog
Icon Theme: Neu

Memory status: size: 89378816 vsize: 89378816 resident: 25948160 share: 18661376 rss: 25948160 rss_rlim: 4294967295
CPU usage: start_time: 1192880117 rtime: 30 utime: 25 stime: 5 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 -1209137440 (LWP 4828)]
[New Thread -1254286448 (LWP 4834)]
[New Thread -1243796592 (LWP 4833)]
[New Thread -1233306736 (LWP 4832)]
[New Thread -1211237488 (LWP 4829)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1209137440 (LWP 4828))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 ??
    from /usr/lib/libgnome-desktop-2.so.2
  • #5 ??
    from /usr/lib/libgnome-desktop-2.so.2
  • #6 ??
    from /usr/lib/libgnome-desktop-2.so.2
  • #7 gnome_bg_create_pixmap
    from /usr/lib/libgnome-desktop-2.so.2
  • #8 ??
    from /usr/lib/libeel-2.so.2
  • #9 ??
    from /usr/lib/libeel-2.so.2
  • #10 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #11 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #12 ??
    from /lib/libgobject-2.0.so.0
  • #13 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #14 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #15 gtk_widget_realize
    from /usr/lib/libgtk-x11-2.0.so.0
  • #16 gtk_widget_map
    from /usr/lib/libgtk-x11-2.0.so.0
  • #17 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #18 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #19 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #20 gtk_container_forall
    from /usr/lib/libgtk-x11-2.0.so.0
  • #21 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #22 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #23 ??
    from /lib/libgobject-2.0.so.0
  • #24 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #25 ??
    from /lib/libgobject-2.0.so.0
  • #26 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #27 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #28 gtk_widget_map
    from /usr/lib/libgtk-x11-2.0.so.0
  • #29 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #30 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #31 gtk_container_forall
    from /usr/lib/libgtk-x11-2.0.so.0
  • #32 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #33 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #34 ??
    from /lib/libgobject-2.0.so.0
  • #35 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #36 ??
    from /lib/libgobject-2.0.so.0
  • #37 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #38 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #39 gtk_widget_map
    from /usr/lib/libgtk-x11-2.0.so.0
  • #40 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #41 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #42 gtk_container_forall
    from /usr/lib/libgtk-x11-2.0.so.0
  • #43 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #44 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #45 ??
    from /lib/libgobject-2.0.so.0
  • #46 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #47 ??
    from /lib/libgobject-2.0.so.0
  • #48 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #49 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #50 gtk_widget_map
    from /usr/lib/libgtk-x11-2.0.so.0
  • #51 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #52 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #53 gtk_container_forall
    from /usr/lib/libgtk-x11-2.0.so.0
  • #54 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #55 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #56 ??
    from /lib/libgobject-2.0.so.0
  • #57 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #58 ??
    from /lib/libgobject-2.0.so.0
  • #59 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #60 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #61 gtk_widget_map
    from /usr/lib/libgtk-x11-2.0.so.0
  • #62 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #63 ??
  • #64 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #65 ??
    from /lib/libgobject-2.0.so.0
  • #66 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #67 ??
    from /lib/libgobject-2.0.so.0
  • #68 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #69 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #70 gtk_widget_map
    from /usr/lib/libgtk-x11-2.0.so.0
  • #71 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #72 ??
  • #73 ??
  • #74 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #75 ??
    from /lib/libgobject-2.0.so.0
  • #76 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #77 ??
    from /lib/libgobject-2.0.so.0
  • #78 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #79 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #80 gtk_widget_show
    from /usr/lib/libgtk-x11-2.0.so.0
  • #81 nautilus_window_show_window
  • #82 nautilus_window_info_show_window
  • #83 ??
  • #84 ??
  • #85 ??
  • #86 ??
  • #87 ??
    from /lib/libglib-2.0.so.0
  • #88 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #89 ??
    from /lib/libglib-2.0.so.0
  • #90 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #91 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #92 main
  • #0 __kernel_vsyscall


----------- .xsession-errors ---------------------
(bug-buddy:4795): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
Initializing nautilus-open-terminal extension
(nautilus:4805): GLib-CRITICAL **: g_markup_parse_context_end_parse: assertion `context->state != STATE_ERROR' failed
(bug-buddy:4815): GLib-GObject-WARNING **: invalid uninstantiatable type `GParamChar' in cast to `GObject'
(bug-buddy:4815): GLib-GObject-CRITICAL **: g_object_get_data: assertion `G_IS_OBJECT (object)' failed
(bug-buddy:4815): GLib-CRITICAL **: g_hash_table_destroy: assertion `hash_table->ref_count > 0' failed
(bug-buddy:4815): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
Initializing nautilus-open-terminal extension
(nautilus:4828): GLib-CRITICAL **: g_markup_parse_context_end_parse: assertion `context->state != STATE_ERROR' failed
--------------------------------------------------
Comment 1 Christoph Wolk 2007-10-20 14:41:19 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?

You're right, seems like they were the same bug. If you could reproduce it with debugging symbols installed, it would help the developers a lot. Thanks!

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