Bug 510145 – crash in System Log: Shutting down

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 510145 - crash in System Log: Shutting down


Summary:	crash in System Log: Shutting down


Status:	RESOLVED DUPLICATE of bug 442846

Product:	gnome-utils
Classification:	Deprecated
Component:	logview
Version:	2.18.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	gnome-utils Maintainers
QA Contact:	gnome-utils Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-01-17 11:03 UTC by johnh
Modified:	2008-02-13 10:23 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description johnh 2008-01-17 11:03:08 UTC

Version: 2.18.0

What were you doing when the application crashed?
Shutting down


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: 37539840 vsize: 37539840 resident: 13561856 share: 9207808 rss: 13561856 rss_rlim: 4294967295
CPU usage: start_time: 1200565412 rtime: 296 utime: 274 stime: 22 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 -1208883488 (LWP 30168)]
(no debugging symbols found)
0x00c15402 in __kernel_vsyscall ()

+ Trace 185679

Thread 1 (Thread -1208883488 (LWP 30168))

#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 (9 sec old) ---------------------
winbind
winbindd is stopped
winbind
winbindd is stopped
wpa_supplicant
wpa_supplicant is stopped
wpa_supplicant
wpa_supplicant is stopped
ypbind
ypbind is stopped
ypbind
ypbind is stopped
/usr/share/system-config-selinux/system-config-selinux.py:69: Warning: IA__g_object_get_valist: object class `GnomeProgram' has no property named `default-icon'
  xml = gtk.glade.XML ("/usr/share/system-config-selinux/system-config-selinux.glade", domain=PROGNAME)
Saving session: gnome-terminal --window-with-profile-internal-id=Default --show-menubar --role=gnome-terminal-30171-916379552-1200565434 --active --geometry 80x24+158+511 --title root@linux2:~ --worki
--------------------------------------------------

Comment 1 Gianluca Borello 2008-02-13 10:23:19 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 ***