Bug 481667 – crash in System Log: logout the session....

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 481667 - crash in System Log: logout the session....


Summary:	crash in System Log: logout the session....


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-09-29 18:41 UTC by jim
Modified:	2007-10-06 11:06 UTC

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

Description jim 2007-09-29 18:41:22 UTC

Version: 2.18.1

What were you doing when the application crashed?
logout the session....


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 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: 75378688 vsize: 75378688 resident: 36724736 share: 16592896 rss: 36724736 rss_rlim: 4294967295
CPU usage: start_time: 1191090922 rtime: 365 utime: 339 stime: 26 cutime:78 cstime: 5 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 -1208736032 (LWP 2834)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 166463

Thread 1 (Thread -1208736032 (LWP 2834))

#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 ---------------------
nfslock
rpc.statd (pid 1758) 正在執行...
nfslock
rpc.statd (pid 1758) 正在執行...
pcscd
pcscd (pid 1888) 正在執行...
pcscd
pcscd (pid 1888) 正在執行...
readahead_later
readahead_later
(bug-buddy:3265): Gtk-WARNING **: Failed to set text from markup due to error parsing markup: 第 1 行第 40 個字發生錯誤：元素‘b’已關閉，但開啟中的元素是‘span’
--------------------------------------------------

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