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 486754 - crash in Computer: reset computer
crash in Computer: reset computer
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-15 08:17 UTC by allan-s
Modified: 2007-10-19 02:51 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description allan-s 2007-10-15 08:17:51 UTC
Version: 2.18.1

What were you doing when the application crashed?
reset computer


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: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 99762176 vsize: 99762176 resident: 26361856 share: 19763200 rss: 26361856 rss_rlim: 4294967295
CPU usage: start_time: 1192450638 rtime: 60 utime: 18 stime: 42 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 -1208715552 (LWP 2751)]
(no debugging symbols found)
0x00bdc402 in __kernel_vsyscall ()

Thread 1 (Thread -1208715552 (LWP 2751))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 g_cclosure_marshal_VOID__ENUM
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 g_cclosure_marshal_VOID__ENUM
    from /usr/lib/libgnome-desktop-2.so.2
  • #5 g_cclosure_marshal_VOID__ENUM
    from /usr/lib/libgnome-desktop-2.so.2
  • #6 g_cclosure_marshal_VOID__ENUM
    from /usr/lib/libgnome-desktop-2.so.2
  • #7 gnome_bg_create_pixmap
    from /usr/lib/libgnome-desktop-2.so.2
  • #8 g_cclosure_marshal_VOID__ENUM
    from /usr/lib/libeel-2.so.2
  • #9 g_cclosure_marshal_VOID__ENUM
    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:2729): libglade-WARNING **: Error loading image: 無法識別圖片檔‘/usr/share/bug-buddy/bug-buddy.png’的圖片格式
(bug-buddy:2729): libglade-WARNING **: could not convert string to type `GdkPixbuf' for property `pixbuf'
** Message: Failed to close thumbnail pixbuf loader for /usr/share/icons/Mist/16x16/places/gnome-fs-directory.png: 無法識別的圖片檔格式
** Message: Failed to close thumbnail pixbuf loader for /usr/share/icons/gnome/16x16/mimetypes/gnome-fs-regular.png: 無法識別的圖片檔格式
** Message: Failed to close thumbnail pixbuf loader for /usr/share/icons/Mist/16x16/places/user-home.png: 無法識別的圖片檔格式
** Message: Failed to write /usr/share/icons/gnome/48x48/emblems/emblem-desktop.png to thumbnail pixbuf loader: 無法識別的圖片檔格式
(nautilus:2751): GLib-CRITICAL **: g_markup_parse_context_end_parse: assertion `context->state != STATE_ERROR' failed
(bug-buddy:2758): Gtk-WARNING **: Failed to set text from markup due to error parsing markup: 第 1 行第 40 個字發生錯誤:元素‘b’已關閉,但開啟中的元素是‘span’
(bug-buddy:2758): libglade-WARNING **: Error loading image: 無法識別圖片檔‘/usr/share/bug-buddy/bug-buddy.png’的圖片格式
(bug-buddy:2758): libglade-WARNING **: could not convert string to type `GdkPixbuf' for property `pixbuf'
--------------------------------------------------
Comment 1 Christoph Wolk 2007-10-19 02:51:06 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 439977 ***