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 453541 - crash in Open Folder: Fedora 7 was just instal...
crash in Open Folder: Fedora 7 was just instal...
Status: RESOLVED DUPLICATE of bug 452749
Product: nautilus
Classification: Core
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-07-04 00:25 UTC by awerntz
Modified: 2007-07-04 13:05 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description awerntz 2007-07-04 00:25:35 UTC
Version: 2.18.1

What were you doing when the application crashed?
Fedora 7 was just installed. Gkrellm, Wallpaper tray, and SystemMonitor were running. System was performing initial system update of 67 or so updates.


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 92200960 vsize: 92200960 resident: 33263616 share: 14036992 rss: 33263616 rss_rlim: 4294967295
CPU usage: start_time: 1183503301 rtime: 1468 utime: 1351 stime: 117 cutime:0 cstime: 2 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 -1208981792 (LWP 18757)]
(no debugging symbols found)
0x009a6402 in __kernel_vsyscall ()

Thread 1 (Thread -1208981792 (LWP 18757))

  • #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 ??
    from /usr/lib/libeel-2.so.2
  • #11 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #12 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #13 ??
    from /lib/libgobject-2.0.so.0
  • #14 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #15 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #16 ??
    from /usr/lib/libeel-2.so.2
  • #17 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #18 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #19 ??
    from /lib/libgobject-2.0.so.0
  • #20 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #21 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #22 ??
    from /usr/lib/libgnome-desktop-2.so.2
  • #23 ??
    from /usr/lib/libeel-2.so.2
  • #24 ??
    from /usr/lib/libeel-2.so.2
  • #25 ??
  • #26 ??
  • #27 ??
    from /lib/libglib-2.0.so.0
  • #28 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #29 ??
    from /lib/libglib-2.0.so.0
  • #30 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #31 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #32 main
  • #0 __kernel_vsyscall


----------- .xsession-errors (7 sec old) ---------------------
localuser:Alan being added to access control list
SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/18642
Loading "installonlyn" plugin
** Message: Found best visual for GL: 0x24
--- Hash table keys for warning below:
--> file:///home/Alan
(nautilus:18958): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above)
** Message: Found best visual for GL: 0x24
(nautilus:18757): GLib-CRITICAL **: g_markup_parse_context_end_parse: assertion `context->state != STATE_ERROR' failed
--------------------------------------------------
Comment 1 palfrey 2007-07-04 13:05: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?

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