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 599247 - gnome-keybinding-properties dies while opening
gnome-keybinding-properties dies while opening
Status: RESOLVED DUPLICATE of bug 591392
Product: gnome-control-center
Classification: Core
Component: [obsolete] Keybinding
2.26.x
Other Linux
: Normal normal
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-10-21 22:34 UTC by FelipeDarder
Modified: 2009-10-22 16:28 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description FelipeDarder 2009-10-21 22:34:22 UTC 
Debian/Squeeze amd64

gnome-control-center 2.26.0-1
glib2.0-2.22.2-2
(there are not any new versions available not even in sid)

Every time i attemp to open gnome-keybinding-properties console returns this.

-----------------------------
pilipe@pipedsk:~$ gnome-keybinding-properties

(gnome-keybinding-properties:6422): Gtk-CRITICAL **: gtk_tree_store_get_value: assertion `VALID_ITER (iter, tree_store)' failed

(gnome-keybinding-properties:6422): GLib-GObject-WARNING **: /tmp/buildd/glib2.0-2.22.2/gobject/gtype.c:3940: type id `0' is invalid

(gnome-keybinding-properties:6422): GLib-GObject-WARNING **: can't peek value table for type `<invalid>' which is not currently referenced
Violación de segmento
pilipe@pipedsk:~$ 
-----------------------------

Googled everywhere without results. Also didn't find any -dbg package in order to give you a proper debug.

THANKS! :)
Comment 1 Jens Granseuer 2009-10-22 16:28:03 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 bug 591392 ***