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 415185 - crash in Deskbar: Trying to change the key...
crash in Deskbar: Trying to change the key...
Status: RESOLVED DUPLICATE of bug 354953
Product: deskbar-applet
Classification: Deprecated
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Deskbar Applet Maintainer(s)
Deskbar Applet Maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2007-03-06 05:59 UTC by pandarel
Modified: 2007-03-06 17:12 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description pandarel 2007-03-06 05:59:02 UTC 
What were you doing when the application crashed?
Trying to change the keyboard shorcut key with <ALt Gr> F3


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (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 116220

  • File "/usr/lib/python2.4/site-packages/deskbar/ui/DeskbarPreferencesUI.py", line 121 in __on_key_press_event 
    self.__cancel()
  • File "/usr/lib/python2.4/site-packages/deskbar/ui/DeskbarPreferencesUI.py", line 135 in __cancel 
    self.set_accelerator_name(self.__old_value)
  • File "/usr/lib/python2.4/site-packages/deskbar/ui/DeskbarPreferencesUI.py", line 55 in set_accelerator_name 
    (keyval, mods) = gtk.accelerator_parse(value)
TypeError: Gtk.accelerator_parse() argument 1 must be string, not None 






Comment 1


Susana





          2007-03-06 17:12:41 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 354953 ***