GNOME Bugzilla – Bug 354731
crash in Deskbar: attempting to set a shor...
Last modified: 2007-02-07 06:24:19 UTC
What were you doing when the application crashed? attempting to set a shortcut key to bring up the deskbar in deskbar preferences. the key i was attempting to set was specific to my model of keyboard (ms comfort curve 2000 usb) and is apparently mapped to 0x7a ("search" key). Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.0 2006-09-04 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 0 vsize: 0 resident: 0 share: 0 rss: 0 rss_rlim: 0 CPU usage: start_time: 0 rtime: 0 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 Traceback (most recent call last):
+ Trace 71778
(keyval, egroup, level, consumed_modifiers) = keymap.translate_keyboard_state(event.hardware_keycode, event.state, event.group)
*** Bug 355328 has been marked as a duplicate of this bug. ***
*** Bug 355571 has been marked as a duplicate of this bug. ***
*** Bug 357272 has been marked as a duplicate of this bug. ***
*** Bug 361246 has been marked as a duplicate of this bug. ***
This looks like a bug in the pygtk bindings. Since the documentation says it will always return the Keymap for the display. Therefore it is safe for deskbar to expect just that :) Reassigning...
I think that the behavior is correct, this just needs to be reflected in the documentation.
*** Bug 363047 has been marked as a duplicate of this bug. ***
*** Bug 363737 has been marked as a duplicate of this bug. ***
Ho-hum. This is a crash in deskbar-applet, and that's not going to change according to comment 6. Fixing your docs is a good thing, but that won't make deskbar-applet crash any less. ;) Rob, Johan, please see bug 363776 for the PyGTK part of this issue. Moving back to deskbar-applet. Confirming as per duplicates.
Oh, right -- I'm not a Python hacker, so I just hope I got the description at least somewhat correct. Feel free to adjust. ;)
*sigh* I'm getting tired. Please disregard comment 10...
*** Bug 365353 has been marked as a duplicate of this bug. ***
*** Bug 365540 has been marked as a duplicate of this bug. ***
*** Bug 366584 has been marked as a duplicate of this bug. ***
This was fixed in 2.16.1 release. Thanks for all the reports.
*** Bug 368194 has been marked as a duplicate of this bug. ***
*** Bug 370060 has been marked as a duplicate of this bug. ***
*** Bug 370417 has been marked as a duplicate of this bug. ***
*** Bug 370975 has been marked as a duplicate of this bug. ***
*** Bug 373995 has been marked as a duplicate of this bug. ***
*** Bug 377678 has been marked as a duplicate of this bug. ***
*** Bug 382953 has been marked as a duplicate of this bug. ***
*** Bug 386299 has been marked as a duplicate of this bug. ***
*** Bug 385822 has been marked as a duplicate of this bug. ***
*** Bug 392852 has been marked as a duplicate of this bug. ***
*** Bug 393211 has been marked as a duplicate of this bug. ***
*** Bug 405128 has been marked as a duplicate of this bug. ***