Bug 456572 – crash in System Log: apagar el sistema

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 456572 - crash in System Log: apagar el sistema


Summary:	crash in System Log: apagar el sistema


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-07-13 12:44 UTC by esllaut
Modified:	2007-07-13 19:44 UTC

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

Description esllaut 2007-07-13 12:44:45 UTC

Version: 2.18.1

What were you doing when the application crashed?
apagar el sistema


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.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 281812992 vsize: 281812992 resident: 21684224 share: 15151104 rss: 21684224 rss_rlim: 18446744073709551615
CPU usage: start_time: 1184308807 rtime: 260 utime: 241 stime: 19 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 46912519703280 (LWP 2469)]
(no debugging symbols found)
0x00002aaaab368945 in ?? ()

+ Trace 147764

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



----------- .xsession-errors ---------------------
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib64/libcroco-0.6.so.3" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib64/libbz2.so.1" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: Unable to set global thread event mask: generic error
Error while reading shared library symbols:
Cannot find new threads: generic error
/usr/share/bug-buddy/gdb-cmd:3: Error in sourced command file:
Cannot find new threads: generic error
--------------------------------------------------

Comment 1 Susana 2007-07-13 19:44: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 442846 ***