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 516106 - crash in System Log: shutting down computer, ...
crash in System Log: shutting down computer, ...
Status: RESOLVED DUPLICATE of bug 442846
Product: gnome-utils
Classification: Deprecated
Component: logview
2.18.x
Other All
: High critical
: ---
Assigned To: gnome-utils Maintainers
gnome-utils Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-02-12 20:59 UTC by coolmusclecar
Modified: 2008-02-13 10:22 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description coolmusclecar 2008-02-12 20:59:12 UTC
Version: 2.18.1

What were you doing when the application crashed?
shutting down computer, closing applications


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

System: Linux 2.6.22.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 58077184 vsize: 58077184 resident: 16941056 share: 7725056 rss: 16941056 rss_rlim: 4294967295
CPU usage: start_time: 1202843169 rtime: 2896 utime: 2708 stime: 188 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/sbin/gnome-system-log'

(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 -1208912160 (LWP 5677)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1208912160 (LWP 5677))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 ??
  • #5 _gnome_marshal_BOOLEAN__INT_ENUM_BOOLEAN_ENUM_BOOLEAN
    from /usr/lib/libgnomeui-2.so.0
  • #6 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #7 ??
    from /lib/libgobject-2.0.so.0
  • #8 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #9 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #10 ??
    from /usr/lib/libgnomeui-2.so.0
  • #11 _SmcProcessMessage
    from /usr/lib/libSM.so.6
  • #12 IceProcessMessages
    from /usr/lib/libICE.so.6
  • #13 ??
    from /usr/lib/libgnomeui-2.so.0
  • #14 ??
    from /lib/libglib-2.0.so.0
  • #15 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #16 ??
    from /lib/libglib-2.0.so.0
  • #17 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #18 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #19 main
  • #0 __kernel_vsyscall


----------- .xsession-errors (13 sec old) ---------------------
Another program is modifying document
Another program is modifying document
Another program is modifying document
(gnome-help:4495): Bonobo-CRITICAL **: bonobo_object_corba_objref: assertion `BONOBO_IS_OBJECT (object)' failed
** (nautilus:3240): WARNING **: No description found for mime type "  h	/x-log" (file is "vmware.log"), please tell the gnome-vfs mailing list.
User requested abort: Exiting because of failed disk operation.
PowerOn
VMXVmdbLoadUsbDevices: New set of 1 USB devices
VIDE: (0x1f0) OUTB Cmd 0xb0, Unknown ATA Command on drive 0
VIDE: (0x1f0) OUTB Cmd 0xb0, Unknown ATA Command on drive 0
VIDE: (0x1f0) OUTB Cmd 0xb0, Unknown ATA Command on drive 0
VIDE: (0x1f0) OUTB Cmd 0xb0, Unknown ATA Command on drive 0
Saving session: gnome-terminal --window-with-profile-internal-id=Default --show-menubar --role=gnome-terminal-6041-911392077-1202843370 --active --geometry 80x24+0+49 --title root@localhost:~ --workin
--------------------------------------------------
Comment 1 Gianluca Borello 2008-02-13 10:22:39 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 442846 ***