Bug 464693 – crash in System Log: logging out root

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 464693 - crash in System Log: logging out root


Summary:	crash in System Log: logging out root


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-08-08 13:12 UTC by evanrobe
Modified:	2007-08-08 20:33 UTC

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

Description evanrobe 2007-08-08 13:12:00 UTC

Version: 2.18.0

What were you doing when the application crashed?
logging out root


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 Wed May 23 22:12:25 EDT 2007 ppc
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 47136768 vsize: 47136768 resident: 10170368 share: 7602176 rss: 10170368 rss_rlim: 4294967295
CPU usage: start_time: 2212250531 rtime: 271 utime: 242 stime: 29 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 805575248 (LWP 2876)]
(no debugging symbols found)
0x0effc298 in __waitpid_nocancel () from /lib/libpthread.so.0

+ Trace 153712

Thread 1 (Thread 805575248 (LWP 2876))

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

Comment 1 Bruno Boaventura 2007-08-08 20:33:46 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 442846 ***