GNOME Bugzilla – Bug 146597
gnome-nettool crashes
Last modified: 2006-07-03 13:23:36 UTC
Distribution: SuSE Linux 9.1 (i586) Package: GStreamer Severity: normal Version: GNOME2.6.1 0.99.1 Gnome-Distributor: GARNOME Synopsis: gnome-nettool crashes Bugzilla-Product: GStreamer Bugzilla-Component: don't know Bugzilla-Version: 0.99.1 BugBuddy-GnomeVersion: 2.0 (2.6.1.1) Description: Description of the crash: gnome-nettool crashes always Steps to reproduce the crash: 1. just start it 2. 3. Expected Results: How often does this happen? always Additional Information: (gnome-nettool:9732): Gtk-CRITICAL **: file gtktreemodel.c: line 998 (gtk_tree_model_get_iter_first): assertion `GTK_IS_TREE_MODEL (tree_model)' failed (gnome-nettool:9732): Gtk-CRITICAL **: file gtktreemodel.c: line 998 (gtk_tree_model_get_iter_first): assertion `GTK_IS_TREE_MODEL (tree_model)' failed (gnome-nettool:9734): Gtk-CRITICAL **: file gtktreemodel.c: line 998 (gtk_tree_model_get_iter_first): assertion `GTK_IS_TREE_MODEL (tree_model)' failed (gnome-nettool:9734): Gtk-CRITICAL **: file gtktreemodel.c: line 998 (gtk_tree_model_get_iter_first): assertion `GTK_IS_TREE_MODEL (tree_model)' failed Debugging Information: Backtrace was generated from '/opt/gnome/bin/gnome-nettool' Using host libthread_db library "/lib/tls/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 1087600672 (LWP 9734)] 0xffffe410 in ?? ()
+ Trace 48044
Thread 1 (Thread 1087600672 (LWP 9734))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-07-09 03:29 ------- Unknown version 0.99.1 in product GStreamer. Setting version to "0.3.3". Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "GStreamer". Setting to default milestone for this product, 'HEAD' The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@bugzilla.gnome.org. Previous reporter was cweinberg@freenet.de. Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Is your computer connected using a traditional modem? May you paste the output of /sbin/ifconfig here? (If still cashes in that way).
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!