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 455491 - crash in System Log: Apagar el ordenador.
crash in System Log: Apagar el ordenador.
Status: RESOLVED DUPLICATE of bug 442846
Product: gnome-utils
Classification: Deprecated
Component: logview
2.18.x
Other All
: High critical
: ---
Assigned To: gnome-utils Maintainers
gnome-utils Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-07-10 10:33 UTC by esllaut
Modified: 2007-07-11 10:08 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description esllaut 2007-07-10 10:33:22 UTC 
Version: 2.18.1

What were you doing when the application crashed?
Apagar el ordenador.


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: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 286171136 vsize: 286171136 resident: 27545600 share: 20123648 rss: 27545600 rss_rlim: 18446744073709551615
CPU usage: start_time: 1184050951 rtime: 2482 utime: 2417 stime: 65 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 46912496311696 (LWP 2700)]
(no debugging symbols found)
0x000000310c00d865 in waitpid () from /lib64/libpthread.so.0

+ Trace 146963

Thread 1 (Thread 46912496311696 (LWP 2700))

  • #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 (65 sec old) ---------------------
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib64/libgnome-desktop-2.so.2" is not at the expected address (wrong library or version mismatch?)
warning: .dynamic section for "/usr/lib64/libgnome-window-settings.so.1" is not at the expected address (wrong library or version mismatch?)
warning: .dynamic section for "/usr/lib64/libpanel-applet-2.so.0" is not at the expected address (wrong library or version mismatch?)
(bug-buddy:4857): GLib-GObject-WARNING **: invalid uninstantiatable type `proximity-in-event' in cast to `GObject'
(bug-buddy:4857): GLib-GObject-CRITICAL **: g_object_get_data: assertion `G_IS_OBJECT (object)' failed
(bug-buddy:4857): GLib-CRITICAL **: g_hash_table_destroy: assertion `hash_table->ref_count > 0' failed
(bug-buddy:4857): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
--------------------------------------------------
Comment 1 Damien Durand 2007-07-11 10:08:13 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 ***