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 484524 - crash in System Log: Logging out from root ac...
crash in System Log: Logging out from root ac...
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-10-07 21:56 UTC by dj
Modified: 2007-10-08 19:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description dj 2007-10-07 21:56:16 UTC 
Version: 2.18.1

What were you doing when the application crashed?
Logging out from root account 


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.22.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 36978688 vsize: 36978688 resident: 18575360 share: 15179776 rss: 18575360 rss_rlim: 4294967295
CPU usage: start_time: 1191785661 rtime: 358 utime: 324 stime: 34 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 -1208666400 (LWP 2945)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 168623

Thread 1 (Thread -1208666400 (LWP 2945))

  • #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 (21 sec old) ---------------------
nfsd is stopped
rpc.rquotad is stopped
nfs
rpc.mountd (pid 3690) is running...
nfsd (pid 3686 3685 3684 3683 3682 3681 3680 3679) is running...
rpc.rquotad (pid 3658) is running...
(nautilus:2821): libgnomevfs-WARNING **: gnome-vfs-monitor.c: A monitor handle was destroyed before it was added to the method hash table. This is a bug in the application and can cause crashes. It is
(vino-preferences:3766): GLib-CRITICAL **: g_base64_decode: assertion `input_length > 1' failed
(vino-preferences:3766): GLib-CRITICAL **: g_base64_encode: assertion `len > 1' failed
(vino-preferences:3766): GConf-CRITICAL **: gconf_client_set_string: assertion `val != NULL' failed
Saving session: gnome-terminal --window-with-profile-internal-id=Default --show-menubar --role=gnome-terminal-3157--258216689-1191787689 --active --geometry 80x47+678+25 --title dj@linux:/etc/postfix 
--------------------------------------------------
Comment 1 Susana 2007-10-08 19:47:32 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


*** This bug has been marked as a duplicate of 442846 ***