GNOME Bugzilla – Bug 465690
crash in System Log: viewing log, downloading...
Last modified: 2007-12-03 16:30:42 UTC
Version: 2.18.1 What were you doing when the application crashed? viewing log, downloading updates 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.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 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: 48799744 vsize: 48799744 resident: 27353088 share: 16789504 rss: 27353088 rss_rlim: 4294967295 CPU usage: start_time: 1186844140 rtime: 91 utime: 74 stime: 17 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 -1208797472 (LWP 18418)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 154431
Thread 1 (Thread -1208797472 (LWP 18418))
----------- .xsession-errors --------------------- PackageSackError: No Package Matching kernel.i686 Local variables in innermost frame: highdict: {} self: <yum.packageSack.ListPackageSack object at 0x1025b0ac> naTup: ('kernel', 'i686') where: None libnm_glib_nm_state_cb: dbus returned an error. (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files Loading "installonlyn" plugin (gnome-system-log:18407): Gtk-CRITICAL **: _gtk_tree_view_find_path: assertion `node != NULL' failed (gnome-system-log:18418): Gtk-CRITICAL **: _gtk_tree_view_find_path: assertion `node != NULL' failed --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 488119 ***