Bug #7149 no results shown in resultset
Submitted: 9 Dec 2004 21:24 Modified: 10 Dec 2004 18:05
Reporter: [ name withheld ] Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Query Browser Severity:S2 (Serious)
Version:1.1.2-1 OS:Linux (linux suse 9.1)
Assigned to: Alfredo Kojima CPU Architecture:Any

[9 Dec 2004 21:24] [ name withheld ]
Description:
I have installed zhe query browser on my suse 9.1 linux system. First i used the .rpm file and later the .tar.gz file. With both I experienced the same problems.
After starting the query browser from a console, i get the following warning twice:

(libsigc++:4471): glibmm-WARNING **: Object::Object(): Did you really mean to call this?

After starting the query browser, the big problem is, if I want to execute a sql-command, the resultset is not shown. The resultset is empty. Nothing is displayed. At the console I get those hints:
(libsigc++:4471): glibmm-WARNING **: Object::Object(): Did you really mean to call this?

(libsigc++:4471): GLib-GObject-WARNING **: cannot add interface type `GtkTreeModel' to type `GObject', since type `GtkListStore' already conforms to interface

(libsigc++:4471): Gtk-CRITICAL **: file gtktreemodel.c: line 697 (gtk_tree_model_get_n_columns): assertion `GTK_IS_TREE_MODEL (tree_model)' failed

(libsigc++:4471): GLib-GObject-WARNING **: gsignal.c:1893: signal `row_changed' is invalid for instance `0x86e99d8'

(libsigc++:4471): GLib-GObject-WARNING **: gsignal.c:1893: signal `row_inserted' is invalid for instance `0x86e99d8'

(libsigc++:4471): GLib-GObject-WARNING **: gsignal.c:1893: signal `row_has_child_toggled' is invalid for instance `0x86e99d8'

(libsigc++:4471): GLib-GObject-WARNING **: gsignal.c:1893: signal `row_deleted' is invalid for instance `0x86e99d8'

(libsigc++:4471): GLib-GObject-WARNING **: gsignal.c:1893: signal `rows_reordered' is invalid for instance `0x86e99d8'

(libsigc++:4471): Gtk-CRITICAL **: file gtktreemodel.c: line 738 (gtk_tree_model_get_iter): assertion `GTK_IS_TREE_MODEL (tree_model)' failed

(libsigc++:4471): glibmm-WARNING **: Object::Object(): Did you really mean to call this?

(libsigc++:4471): GLib-GObject-WARNING **: cannot add interface type `GtkTreeModel' to type `GObject', since type `GtkListStore' already conforms to interface

(libsigc++:4471): Gtk-CRITICAL **: file gtktreemodel.c: line 697 (gtk_tree_model_get_n_columns): assertion `GTK_IS_TREE_MODEL (tree_model)' failed

(libsigc++:4471): GLib-GObject-WARNING **: gsignal.c:1893: signal `row_changed' is invalid for instance `0x86e37d0'

(libsigc++:4471): GLib-GObject-WARNING **: gsignal.c:1893: signal `row_inserted' is invalid for instance `0x86e37d0'

(libsigc++:4471): GLib-GObject-WARNING **: gsignal.c:1893: signal `row_has_child_toggled' is invalid for instance `0x86e37d0'

(libsigc++:4471): GLib-GObject-WARNING **: gsignal.c:1893: signal `row_deleted' is invalid for instance `0x86e37d0'

(libsigc++:4471): GLib-GObject-WARNING **: gsignal.c:1893: signal `rows_reordered' is invalid for instance `0x86e37d0'

(libsigc++:4471): Gtk-CRITICAL **: file gtktreemodel.c: line 738 (gtk_tree_model_get_iter): assertion `GTK_IS_TREE_MODEL (tree_model)' failed

At the bottom of the resultset tab i can find the information, that "x rows fetched in 0:xxxx"
The next strange thing is that by right clicking in the (not displayed) resultset the query browser crashes.
The Information at the console is the following:

/usr/bin/mysql-query-browser: line 9:  4547 Speicherzugriffsfehler  $MYPATH/mysql-query-browser-bin
(the translation for the german Speicherzugriffsfehler is something like error on accessing the memory)

How to repeat:
start Suse 9.1
open a console
start mysql-query-browser
connect to an mysql server
execute a sql-command like: Select * from table1;
(see nothing)
click right in the resultset
(mysql-query-browser crashes)

Suggested fix:
??
[10 Dec 2004 13:39] Wesley Hampton
I can verify this on several other machines running SuSE 9.1 as well.  I have used most every other development version of Query Browser and have not seen this problem.  I noticed that there were similar errors when I started up MySQL Administrator as well.
[10 Dec 2004 18:05] Alfredo Kojima
This was caused by a problem in the linked libraries. It has been fixed and the next release will 
not have this problem.

Thank you for reporting.