Bug 482355 – crash in System Log: Logging out normally

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 482355 - crash in System Log: Logging out normally


Summary:	crash in System Log: Logging out normally


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:	2007-10-01 20:02 UTC by peter
Modified:	2007-10-06 11:08 UTC

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

Description peter 2007-10-01 20:02:22 UTC

Version: 2.18.1

What were you doing when the application crashed?
Logging out normally


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.22.9-91.fc7 #1 SMP Thu Sep 27 20:47:39 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 277155840 vsize: 277155840 resident: 20701184 share: 14684160 rss: 20701184 rss_rlim: 18446744073709551615
CPU usage: start_time: 1191261506 rtime: 622 utime: 577 stime: 45 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 "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496311120 (LWP 4148)]
(no debugging symbols found)
0x00000030edc0d945 in waitpid () from /lib64/libpthread.so.0

+ Trace 166942

Thread 1 (Thread 46912496311120 (LWP 4148))

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



----------- .xsession-errors (3936 sec old) ---------------------
BackupPC
BackupPC is stopped
BackupPC
BackupPC is stopped
BackupPC
BackupPC is stopped
syslog
syslogd (pid 1850) is running...
klogd (pid 1853) is running...
syslog
syslogd (pid 1850) is running...
klogd (pid 1853) is running...
syslog
syslogd (pid 4547) is running...
klogd (pid 4550) is running...
--------------------------------------------------

Comment 1 Susana 2007-10-06 11:08:44 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 ***