[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/367097
Ti
Brandon Williams, thank you for reporting this and helping make Ubuntu better.
Jaunty reached EOL on October 23, 2010.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We were wondering if this is still an issue in a supported release? If
so, coul
*** This bug is a duplicate of bug 295216 ***
https://bugs.launchpad.net/bugs/295216
** This bug has been marked a duplicate of bug 295216
Wireless toggle function key not connected
--
custom keyboard shortcut inactive on login
https://bugs.launchpad.net/bugs/367097
You received this bug
Bug still exits.
Additional info is here:
https://bugs.launchpad.net/netbook-remix/+bug/295216
--
custom keyboard shortcut inactive on login
https://bugs.launchpad.net/bugs/367097
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubunt
@Brandon,
There is no issue here. Try a 10.04 live image. These are mapped by
default correctly.
** Changed in: gnome-control-center (Ubuntu)
Status: Confirmed => Incomplete
--
custom keyboard shortcut inactive on login
https://bugs.launchpad.net/bugs/367097
You received this
This is a problem with gnome + metacity + UNR (I don't know whether it
also happens without UNR). I believe that it is specific to some key
combinations. The only key combination that I am aware of that is
problematic is the one I indicated in the bug report. It might be a
problem for some others,
Thank you for your bug report, is the issue specific to some
combinaisons? Do you have xfce installed?
** Changed in: gnome-control-center (Ubuntu)
Importance: Undecided => Low
** Changed in: gnome-control-center (Ubuntu)
Status: New => Incomplete
--
custom keyboard shortcut inactive
Oops ... no ... setxkbmap is not required, but both calls to gconftool-2
_are_ required. With only the one that Luca recommends, the workaround
does not achieve the desired effect.
--
custom keyboard shortcut inactive on login
https://bugs.launchpad.net/bugs/367097
You received this bug notificat
For me, the call to setxkbmap was required.
I'm not sure whether both calls to gconftool-2 were required. I will try
to remember to try this again later.
--
custom keyboard shortcut inactive on login
https://bugs.launchpad.net/bugs/367097
You received this bug notification because you are a memb
I played a little on this. Setting the shortcut to a different
keycode/keybinding (e.g. Alt+F12) gnome-control-center (or maybe better
gnome-settings-daemon) seems able to remember the value after
logout/login and even after reboot.
Instead, setting the keycode/keybindint to Fn+2, I think you simp
I experimented a little more and discovered that, no, setxkbmap is not
required. The two calls to gconftool-2 are enough to enable the desired
shortcut.
--
custom keyboard shortcut inactive on login
https://bugs.launchpad.net/bugs/367097
You received this bug notification because you are a member
As a work-around, I wrote this script:
#!/bin/sh
setxkbmap
gconftool-2 --set --type=string /desktop/gnome/keybindings/custom0/binding
XF86WLAN
gconftool-2 --set --type=string /desktop/gnome/keybindings/custom0/binding
XF86AudioNext
I then configured the script to run at login using the 'Startu
12 matches
Mail list logo
