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 357272 - crash in Deskbar: Pressing a "media" butto...
crash in Deskbar: Pressing a "media" butto...
Status: RESOLVED DUPLICATE of bug 354731
Product: deskbar-applet
Classification: Deprecated
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Deskbar Applet Maintainer(s)
Deskbar Applet Maintainer(s)
: 404099 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-09-23 00:54 UTC by Chris Jones
Modified: 2007-02-04 12:39 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Chris Jones 2006-09-23 00:54:44 UTC 
What were you doing when the application crashed?
Pressing a "media" button on a Logitech cordless keyboard to map it to the keyboard shortcut in deskbar.


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 73024

  • File "/usr/lib/python2.4/site-packages/deskbar/ui/DeskbarPreferencesUI.py", line 103 in __on_key_press_event 
    (keyval, egroup, level, consumed_modifiers) = keymap.translate_keyboard_state(event.hardware_keycode, event.state, event.group)
TypeError: unpack non-sequence 






Comment 1


Karsten Bräckelmann





          2006-09-23 01:07:31 UTC
        



Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 354731 ***






Comment 2


Damien Durand





          2007-02-04 12:39:27 UTC
        



*** Bug 404099 has been marked as a duplicate of this bug. ***