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 447382 - crash in System Log: logging out as root
crash in System Log: logging out as root
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-06-14 01:19 UTC by mikesphar
Modified: 2007-06-14 15:03 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description mikesphar 2007-06-14 01:19:42 UTC 
Version: 2.18.1

What were you doing when the application crashed?
logging out as root


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.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 37494784 vsize: 37494784 resident: 8396800 share: 6373376 rss: 8396800 rss_rlim: 4294967295
CPU usage: start_time: 1181778313 rtime: 345 utime: 208 stime: 137 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 -1208342816 (LWP 3017)]
(no debugging symbols found)
0x00c63402 in __kernel_vsyscall ()

+ Trace 140830

Thread 1 (Thread -1208342816 (LWP 3017))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 gtk_main_quit
    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 gtk_main_quit
    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 gtk_main_quit
    from /usr/lib/libgnomeui-2.so.0
  • #11 _SmcProcessMessage
    from /usr/lib/libSM.so.6
  • #12 IceProcessMessages
    from /usr/lib/libICE.so.6
  • #13 gtk_main_quit
    from /usr/lib/libgnomeui-2.so.0
  • #14 gtk_main_quit
    from /lib/libglib-2.0.so.0
  • #15 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #16 gtk_main_quit
    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 (5651 sec old) ---------------------
(gnome-background-properties:2968): GdkPixbuf-CRITICAL **: gdk_pixbuf_composite: assertion `src != NULL' failed
(gnome-background-properties:2968): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_width: assertion `pixbuf != NULL' failed
(gnome-background-properties:2968): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_height: assertion `pixbuf != NULL' failed
(gnome-background-properties:2968): GdkPixbuf-CRITICAL **: gdk_pixbuf_composite: assertion `src != NULL' failed
(gnome-background-properties:2968): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_width: assertion `pixbuf != NULL' failed
(gnome-background-properties:2968): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_height: assertion `pixbuf != NULL' failed
(gnome-background-properties:2968
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Damien Durand 2007-06-14 15:03:00 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 ***