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 484804 - crash in System Log: shutting down
crash in System Log: shutting down
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-08 17:54 UTC by sscholle
Modified: 2007-10-08 19:49 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description sscholle 2007-10-08 17:54:23 UTC 
Version: 2.18.0

What were you doing when the application crashed?
shutting down


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.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: 38572032 vsize: 38572032 resident: 13840384 share: 8753152 rss: 13840384 rss_rlim: 4294967295
CPU usage: start_time: 1191812001 rtime: 504 utime: 475 stime: 29 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 -1208097056 (LWP 24351)]
(no debugging symbols found)
0x00bf0402 in __kernel_vsyscall ()

+ Trace 168832

Thread 1 (Thread -1208097056 (LWP 24351))

  • #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 ---------------------
(nautilus:11703): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above)
Loading "installonlyn" plugin
Window manager warning: GtkMenu failed to grab the pointer
Loading "installonlyn" plugin
(nautilus:2731): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text()
(gnome-system-log:24351): Gtk-CRITICAL **: gtk_tree_selection_real_modify_range: assertion `start_node != NULL' failed
--- Hash table keys for warning below:
--> file:///root
(nautilus:16574): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above)
Saving session: gnome-terminal --window-with-profile-internal-id=Default --show-menubar --role=gnome-terminal-3061-326874953-1191776264 --active --geometry 80x24+357+113 --title root@dev:/var/www/html
--------------------------------------------------
Comment 1 Susana 2007-10-08 19:49:00 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 ***