I saw this problem recently on a system running a very old version of Debian
testing. It's running xserver-xorg 6.8.2.dfsg.1-11 and VMware Workstation
5.5.6.
It looks like this is a problem with VMware, not with the X server or anything
else. VMware apparently clears all the modifier maps when i
I can also confirm this problem. xmms complains when trying to load the plugin:
/usr/lib/xmms/Input/libxmms-flac.so: undefined symbol: safe_realloc_add_4op_
According to the flac CVS repository, this is defined as a static (and possibly
inlined)
function in one of the header files, so the defi
Public bug reported:
Binary package hint: console-setup
In feisty, /bin/setupcon reads the XKB model, layout, variant, and options from
/etc/default/console-setup. However, there is no way to tell it to use an
alternate XKB rules file.
I'll attach a patch to setupcon that allows an "XKBRULES" v
** Attachment added: "setupcon.patch"
http://launchpadlibrarian.net/9284747/setupcon.patch
--
no way to specify alternate xkb rules in setupcon
https://bugs.launchpad.net/bugs/139712
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubunt
** Attachment added: "Patch to ckbcomp to handle multiple xkb rule consequents"
http://launchpadlibrarian.net/9284715/ckbcomp.patch
--
ckbcomp cannot handle multiple consequents in xkb rules
https://bugs.launchpad.net/bugs/139710
You received this bug notification because you are a member of
Public bug reported:
Binary package hint: console-setup
My XKB rules file has a set of rules with multiple consequents:
! model layout = keycodessymbols
dbied qwerty = maltron(qwerty) maltron(qwerty)
dbied maltron = maltron(
Public bug reported:
Binary package hint: bash
In /etc/bash_completion, the completion for the "ssh" command doesn't use the
"-o filenames" option. As a result, filename processing isn't performed on the
completed results. (In particular, this includes adding a trailing slash to
directory names
Public bug reported:
Binary package hint: bash
In feisty, the /etc/bash_completion file uses ${COMP_WORDS[COMP_CWORD]}" to
find the token being completed. This isn't quite correct, since it always
returns the full token, even if the cursor is in the middle of the token.
For example, say the com
** Attachment added: "Patch to /etc/bash_completion that fixes the problem"
http://launchpadlibrarian.net/9283873/bash_completion.patch
--
bash completion doesn't work in the middle of a word
https://bugs.launchpad.net/bugs/139666
You received this bug notification because you are a member of
