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 457534 - crash in System Log: Logging out of gnome ses...
crash in System Log: Logging out of gnome ses...
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-16 23:56 UTC by bomr
Modified: 2007-07-27 00:24 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description bomr 2007-07-16 23:56:42 UTC 
Version: 2.18.0

What were you doing when the application crashed?
Logging out of gnome session (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.20-2925.9.fc7xen #1 SMP Tue May 22 09:29:36 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 282939392 vsize: 282939392 resident: 14417920 share: 8683520 rss: 14417920 rss_rlim: 18446744073709551615
CPU usage: start_time: 1184628718 rtime: 586 utime: 507 stime: 79 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 46912496434576 (LWP 8028)]
(no debugging symbols found)
0x0000003e0b80d865 in waitpid () from /lib64/libpthread.so.0

+ Trace 148495

Thread 1 (Thread 46912496434576 (LWP 8028))

  • #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 ---------------------
Writing new pickle
/usr/lib/cups/filter/foomatic-rip: found
** Message: <info>  Forcing device '/org/freedesktop/NetworkManager/Devices/eth0'
** Message: <info>  You are now connected to the wired network.
(nm-vpn-properties:8954): libglade-WARNING **: unknown child property `padding' for container `GtkAlignment'
(nm-vpn-properties:8954): libglade-WARNING **: unknown child property `expand' for container `GtkAlignment'
(nm-vpn-properties:8954): libglade-WARNING **: unknown child property `fill' for container `GtkAlignment'
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x3800007 specified for 0x38001d5 (Connection).
Saving session: gnome-terminal --window-with-profile-internal-id=Default --show-menubar --role=gnome-terminal-5195--1506216004-1184613686 --active --geometry 123x53+67+59 --title root@rod:~/gnome-comm
--------------------------------------------------
Comment 1 Pedro Villavicencio 2007-07-27 00:24:51 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 ***