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 591392 - crash in Keyboard Shortcuts: Crashed opening
crash in Keyboard Shortcuts: Crashed opening
Status: RESOLVED FIXED
Product: gnome-control-center
Classification: Core
Component: [obsolete] Keybinding
2.27.x
Other All
: High critical
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
: 597843 599247 604662 607380 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2009-08-11 00:18 UTC by Luca Ferretti
Modified: 2010-01-19 08:58 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28


Description Luca Ferretti 2009-08-11 00:18:36 UTC 
Version: 2.27.5

What were you doing when the application crashed?
Crashed opening


Distribution: Ubuntu 9.04 (jaunty)
Gnome Release: 2.27.5 2009-08-09 (JHBuild)
BugBuddy Version: 2.27.1

System: Linux 2.6.28-14-generic #47-Ubuntu SMP Sat Jul 25 01:19:55 UTC 2009 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10600000
Selinux: No
Accessibility: Enabled
GTK+ Theme: Clearlooks
Icon Theme: gnome
GTK+ Modules: gnomebreakpad, gail:atk-bridge, canberra-gtk-module

Memory status: size: 187535360 vsize: 187535360 resident: 12656640 share: 9900032 rss: 12656640 rss_rlim: 18446744073709551615
CPU usage: start_time: 1249949873 rtime: 15 utime: 12 stime: 3 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/opt/gnome2/bin/gnome-keybinding-properties'

[Thread debugging using libthread_db enabled]
[New Thread 0x7f31410347d0 (LWP 25601)]
0x00007f313dd1fb85 in waitpid () from /lib/libpthread.so.0

+ Trace 216872

Thread 1 (Thread 0x7f31410347d0 (LWP 25601))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 IA__g_spawn_sync
    at gspawn.c line 382
  • #2 IA__g_spawn_command_line_sync
    at gspawn.c line 694
  • #3 bugbuddy_segv_handle
    at gnome-breakpad.cc line 369
  • #4 <signal handler called>
  • #5 IA__gtk_tree_model_get_valist
    at gtktreemodel.c line 1443
  • #6 IA__gtk_tree_model_get
    at gtktreemodel.c line 1405
  • #7 find_section
    at gnome-keybinding-properties.c line 536
  • #8 append_keys_to_tree
    at gnome-keybinding-properties.c line 569
  • #9 reload_key_entries
    at gnome-keybinding-properties.c line 896
  • #10 main
    at gnome-keybinding-properties.c line 1861
  • #0 waitpid
    from /lib/libpthread.so.0 


---- Critical and fatal warnings logged during execution ----

** Gtk **: gtk_tree_store_get_value: assertion `VALID_ITER (iter, tree_store)' failed 


----------- .xsession-errors ---------------------
** (nautilus:25306): WARNING **: Can not get _NET_WORKAREA
** (nautilus:25306): WARNING **: Can not determine workarea, guessing at layout
[WARN 25003] The SessionAdded signal on the org.freedesktop.ConsoleKit.Seat interface for object /org/freedesktop/ConsoleKit/Seat1 has the wrong signature! Your system is misconfigured.
[WARN 25003] The SessionRemoved signal on the org.freedesktop.ConsoleKit.Seat interface for object /org/freedesktop/ConsoleKit/Seat1 has the wrong signature! Your system is misconfigured.
** (gnome-system-monitor:25596): WARNING **: SELinux was found but is not enabled.
(gnome-keybinding-properties:25601): Gtk-CRITICAL **: gtk_tree_store_get_value: assertion `VALID_ITER (iter, tree_store)' failed
(gnome-keybinding-properties:25601): GLib-GObject-WARNING **: gtype.c:3940: type id `0' is invalid
(gnome-keybinding-properties:25601): GLib-GObject-WARNING **: can't peek value table for type `<invalid>' which is not currently referenced
--------------------------------------------------
Comment 1 Jens Granseuer 2009-08-11 16:04:21 UTC 
Should be fixed by

commit 5998aa90c08051cc520dfb64ede78783ef9cc2c4
Author: Jens Granseuer <...>
Date:   Tue Aug 11 18:01:55 2009 +0200

    Fix crash when iterating through the tree model
    
    Don't use indices to move through iterators, don't skip the first
    section, and verify that we got a new iterator before using it
    (bug #591392).
Comment 2 Akhil Laddha 2009-10-09 06:41:32 UTC 
*** Bug 597843 has been marked as a duplicate of this bug. ***
Comment 3 Jens Granseuer 2009-10-22 16:28:04 UTC 
*** Bug 599247 has been marked as a duplicate of this bug. ***
Comment 4 Akhil Laddha 2009-12-16 04:24:47 UTC 
*** Bug 604662 has been marked as a duplicate of this bug. ***
Comment 5 Jens Granseuer 2010-01-19 08:58:32 UTC 
*** Bug 607380 has been marked as a duplicate of this bug. ***