Bug 449189 – crash in System Log: restating system after c...

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 449189 - crash in System Log: restating system after c...


Summary:	crash in System Log: restating system after c...


Status:	RESOLVED DUPLICATE of bug 443359

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-06-19 16:56 UTC by balford
Modified:	2007-06-20 01:39 UTC

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

Description balford 2007-06-19 16:56:59 UTC

Version: 2.18.1

What were you doing when the application crashed?
restating system after changing ethernet port


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 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: 41050112 vsize: 41050112 resident: 22429696 share: 14548992 rss: 22429696 rss_rlim: 4294967295
CPU usage: start_time: 1182271762 rtime: 37 utime: 32 stime: 5 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 -1208989984 (LWP 3310)]
(no debugging symbols found)
0x00f31402 in __kernel_vsyscall ()

+ Trace 142194

Thread 1 (Thread -1208989984 (LWP 3310))

#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 (124 sec old) ---------------------
xinetd (pid 2274) is running...
ConsoleKit
console-kit-daemon (pid 2559) is running...
ConsoleKit
console-kit-daemon (pid 2559) is running...
chargen-dgram
xinetd (pid 2274) is running...
rpcbind
rpcbind (pid 2060) is running...
rpcbind
rpcbind (pid 2060) is running...
named
rndc: connect failed: 127.0.0.1#953: connection refused
named
rndc: connect failed: 127.0.0.1#953: connection refused
--------------------------------------------------

Comment 1 Pedro Villavicencio 2007-06-20 01:39:53 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 443359 ***