I still had this bug on 13.04 with FreeNX ppa package connecting to the
13.04 server from a 12.04 client. The only solution (no specific
setkbmap or xmodmap line worked [even matching what I got in 'xev' !], I
could not find evdev in keyboard options [despite it in kernel and
xorg.conf.d], and no
Sure. What do you mean by "check the gnome-settings-daemon"? What am I
supposed to do exactly?
--
Regression: Connecting to FreeNX breaks keyboard layout in Intrepid
https://bugs.launchpad.net/bugs/289918
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
Oh by the way you may want to check the gnome-settings-daemon. This
caused the problems for me.
** Changed in: freenx-server
Status: Invalid => Fix Released
--
Regression: Connecting to FreeNX breaks keyboard layout in Intrepid
https://bugs.launchpad.net/bugs/289918
You received this bug
Please Open a new bug unless you are running Intrepid/FreeNX.
** Changed in: freenx-server
Status: Confirmed => Fix Released
** Changed in: metacity (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: freenx-server
Status: Fix Released => Invalid
** Changed in: freenx
** Changed in: metacity (Ubuntu)
Status: Incomplete => Confirmed
--
Regression: Connecting to FreeNX breaks keyboard layout in Intrepid
https://bugs.launchpad.net/bugs/289918
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity
** Changed in: freenx-server
Status: Invalid => Confirmed
--
Regression: Connecting to FreeNX breaks keyboard layout in Intrepid
https://bugs.launchpad.net/bugs/289918
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in ubu
This is broken for me and none of the workarounds have helped. My client and
server machines are both running Lucid. I am running the official NX client
and server so the bug is not in freenx.
I'd be nice if we could get the importance bumped up from low and hopefully get
the bug assigned to s
It just won't work for me.
My cursor keys are still messed up.
i can use xmodmap to make them works, but Alt_R modifier won't (in italian
layout i cannot write @,#,[,] )
Also setxkbmap doesn't work, no matter what option i use, i get:
"Error loading new keyboard description"
I don't use any xorg.c
I've just managed to get things working on my machines.
My guess is that re-loading the evdev module did the trick (I actually
did a full server reboot).
I was already using evdev as the keyboard on both the server and client.
That was working fine until I upgraded the server to KDE 4. This (re-
Using nxserver 3.4.0 on the server (running hardy, with Gnome/metacity
as the desktop environment) and nxclient 3.4.0 on the clients (running
Ubuntu 9.10 or Windows XP), I did not see this problem since several
months. Anyone else?
** Changed in: metacity (Ubuntu)
Status: Confirmed => Incom
Just wanted to say thanks to Johan from comment #44. This works for me.
I'm using an Ubuntu 9.04 client, connecting to an OpenSUSE 10.3 server.
I've added a few things to Johan's lines...
xmodmap -e "keycode 110=Home"
xmodmap -e "keycode 113=Left"
xmodmap -e "keycode 114=Right"
xmodmap -e "keycode
I'm not sure if it is related, but I have noticed that certain apps that
pass keypresses (Ctrl+Alt+Delete) to a sub program like virt-manager are
still broken even if the keymap is right inside KDE. This works on the
console just fine, just not within FreeNX.
--
Regression: Connecting to FreeNX
Still a problem in karmic
--
Regression: Connecting to FreeNX breaks keyboard layout in Intrepid
https://bugs.launchpad.net/bugs/289918
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in ubuntu.
--
desktop-bugs mailing list
des
still a problem, reproduced in Jaunty.
--
Regression: Connecting to FreeNX breaks keyboard layout in Intrepid
https://bugs.launchpad.net/bugs/289918
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in ubuntu.
--
desktop-bugs mai
** Changed in: metacity (Ubuntu)
Importance: Undecided => Low
--
Regression: Connecting to FreeNX breaks keyboard layout in Intrepid
https://bugs.launchpad.net/bugs/289918
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in ubu
It also happens with KDE, maybe you have this package already installed
--
Regression: Connecting to FreeNX breaks keyboard layout in Intrepid
https://bugs.launchpad.net/bugs/289918
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity
To fix this bug, on the server type:
apt-get install xkb-data
then type:
setxkbmap
(or restart nx)
The file /usr/share/X11/xkb/rules/xorg is the file that was needed.
This could be fixed with a dependency in one of the nx packages.
--
Regression: Connecting to FreeNX breaks keyboard lay
Same thing here connecting from Intrepid client (x86) - to an arch linux
freenx server - i.e no arrow keys, etc
- I could always connect from gentoo, arch linux and opensuse fine -
however I use KDE on these systems
I have just tried connecting from Intrepid with kde4.2 and it works fine.
i.e
Running the following commands when logged in on the server via NX fixes
the cursor keys for me:
xmodmap -e "keycode 113=Left"
xmodmap -e "keycode 114=Right"
xmodmap -e "keycode 111=Up"
xmodmap -e "keycode 116=Down"
I have a US keyboard.
--
Regression: Connecting to FreeNX breaks keyboard layou
On Thu, Jan 22, 2009 at 12:00 PM, mabawsa wrote:
> Nope on evdev managed keyboards server-side cause all navigation keys to
> map incorrectly.
This is the way it works. With this updated nxagent, it converts the evdev
keycodes into pc105 keycodes. So it is a predictable behavior.
>
> kb101-us
By the navigation keys I mean:
up (mapped to enter), left (nothing), down (nothing), right (nothing)
arrow keys
pageup (nothing), pagedn (nothing), Home (nothing), End (nothing)
Delete (prntscrn), Insert (nothing), prntscrn (nothing)
The brackets show what I have seen when I use evdev managed key
Nope on evdev managed keyboards server-side cause all navigation keys to
map incorrectly.
kb101-us on server and evdev-us on the client causes the delete key to
be mapped as printscrn
For now as long as the client and server are kb101-us the fix works.
I have not tried the jp106 keyboard yet. I w
So, you have this problem with the jp106 keymap?
Did you tried to set the keymap to jp106 on the server too?
There are other keys wrong mapped or just the delete key?
On Thu, Jan 22, 2009 at 2:50 AM, mabawsa wrote:
> Correction:
> The generic 101 US works when it is set on both client and serv
Correction:
The generic 101 US works when it is set on both client and server. I had only
tried edev client and Generic 101 on the server. Edev on the server side breaks
the navigation keys. This is still a problem as I also access these machines
using Japanese keyboards (106 keys).
--
Regress
I have tried edev managed -US and 101 Generic US. Both produce the same
result.
--
Regression: Connecting to FreeNX breaks keyboard layout in Intrepid
https://bugs.launchpad.net/bugs/289918
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
What is your client keymap?
On Wed, Jan 21, 2009 at 8:43 PM, mabawsa wrote:
> Same story using an intrepid client and Hardy server. The navigation
> keys are restored using the generic 101 keyboard but the delete key
> always maps to printscreen. This configuration worked without any fix
> prior
Same story using an intrepid client and Hardy server. The navigation
keys are restored using the generic 101 keyboard but the delete key
always maps to printscreen. This configuration worked without any fix
prior to the update.
--
Regression: Connecting to FreeNX breaks keyboard layout in Intrepi
Intrepid server and intrepid client for me. If I change from the edev
managed keyboard to the generic 101 keyboard the arrow keys work.
However the delete key maps to print screen still.
--
Regression: Connecting to FreeNX breaks keyboard layout in Intrepid
https://bugs.launchpad.net/bugs/289918
I'd be very happy if this bug could be fixed on the client side. After
all, it was a client change that introduced the bug and there are
situations where you have no influence over what's installed on the
server.
--
Regression: Connecting to FreeNX breaks keyboard layout in Intrepid
https://bugs.
Fixed packages work fine here with German keyboard and Intrepid client.
--
Regression: Connecting to FreeNX breaks keyboard layout in Intrepid
https://bugs.launchpad.net/bugs/289918
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity
After th update things have got worse. The down arrow key is mapped to
enter and delete is mapped to printscreen. The other navigation keys so
not work. The killall metacity workaround no longer works.
--
Regression: Connecting to FreeNX breaks keyboard layout in Intrepid
https://bugs.launchpad.n
Bug fixed in new NX release
On the build queue on freenx-team ppa.
** Changed in: freenx-server
Status: New => Fix Released
--
Regression: Connecting to FreeNX breaks keyboard layout in Intrepid
https://bugs.launchpad.net/bugs/289918
You received this bug notification because you are a me
Upstream bug for reference:
http://www.nomachine.com/tr/view.php?id=TR11F02131
--
Regression: Connecting to FreeNX breaks keyboard layout in Intrepid
https://bugs.launchpad.net/bugs/289918
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to m
> NX 3.3.0 on the build queue on my PPA:
> https://edge.launchpad.net/~marceloshima/+archive
>
> 1 week of testing before going to freenx-team ppa.
> Needs FreeNX >= 0.7.3+svn612-0freenxteam9.
>
> Let me know your experiences.
I tried the newest version from https://launchpad.net/~freenx-
team/+ar
Another workaround is to use ctrl together with f,b,n and p instead of
the arrow keys.
--
Regression: Connecting to FreeNX breaks keyboard layout in Intrepid
https://bugs.launchpad.net/bugs/289918
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscri
I agree that this is a bug on the client, eg Ubuntu 8.10 - why should I
be forced to upgrade *all* my server systems (which don't run Ubuntu of
any flavour) just because I upgraded my client OS - note "OS" - not
client software.
Alex
On Tue, 2008-11-25 at 18:15 +, Martin Emrich wrote:
> Fixin
NX 3.3.0 on the build queue on my PPA:
https://edge.launchpad.net/~marceloshima/+archive
1 week of testing before going to freenx-team ppa.
Needs FreeNX >= 0.7.3+svn612-0freenxteam9.
Let me know your experiences.
Troubleshooting:
If "$ xprop -root | grep XKB" prints "_XKB_RULES_NAMES_BACKUP(STR
Fixing or working-around this problem for every service does not really
feel very satisfactory. I just upgraded NX Free on server and client,
and after a quick test it seems to work. But I still sometimes (not
always) have to do "setxkbmap -model evdev -layout de" on my laptop to
make the keyboard
Daniel Holbert wrote:
> FWIW, I have this exact same problem using VMWare Workstation with this setup:
> host = Ubuntu 8.10
> guest= Ubuntu 8.04
> VMWare Workstation version = 6.5.0 build-118166
>
> In this setup, UpArrow triggers 'save screenshot' (in the guest),
> RightControl types out "^[
FWIW, I have this exact same problem using VMWare Workstation with this setup:
host = Ubuntu 8.10
guest= Ubuntu 8.04
VMWare Workstation version = 6.5.0 build-118166
In this setup, UpArrow triggers 'save screenshot' (in the guest),
RightControl types out "^[[6~", PageDown triggers context men
The problem with the evdev-solution is that it causes problems for those
users that may be on the physical machine. E.g. when I log into my home
server over FreeNX the keyboard now works. However if I log in locally
the keyboard is broken (same problem - except now in reverse).
Hence one must ei
I too have had this problem. Fixed by Preferences -> Keyboard -> Layouts
-> Generic -> Evdev (Apply System-Wide..) followed by killall metacity
on the remote.
--
Regression: Connecting to FreeNX breaks keyboard layout in Intrepid
https://bugs.launchpad.net/bugs/289918
You received this bug notifi
The same at my configuration (Interprid -> Hardy, both system uses
NoMachin FreeNX).
Problem has been solved using Keybard -> Layouts -> Generic -> Evdev and
killall metacity on both sides.
--
Regression: Connecting to FreeNX breaks keyboard layout in Intrepid
https://bugs.launchpad.net/bugs/289
I found that setting my keyboard on the client to Generic->102 key
(Intl) fixed it for me. I'm running Kubuntu but I installed gnome
specifically to address this issue (The KDE system config stuff is
crap). Switching back to KDE, it also seemed OK. NB: I am using KDM as
my DM.
Using evdev from the
Right, the updates from intrepid-proposed do not fix this issue.
--
Regression: Connecting to FreeNX breaks keyboard layout in Intrepid
https://bugs.launchpad.net/bugs/289918
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in ubu
It is not fixed yet. No easy fix, only workarounds.
On Tue, Nov 4, 2008 at 4:26 PM, jmcantrell <[EMAIL PROTECTED]> wrote:
> I noticed that there were some updates to some of the affected packages.
> Can anyone confirm that this is fixed? I have downgraded my client to
> Hardy, so I'm unable to te
do you have proposed updates enabled in software sources?
--
Regression: Connecting to FreeNX breaks keyboard layout in Intrepid
https://bugs.launchpad.net/bugs/289918
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in ubuntu.
-
This is still broken for me.
Client: Fully up-to-date Intrepid, NX client version 3.2.0-13
Server: CentOS 4.6, NX server version 2.1.0-72
--
Regression: Connecting to FreeNX breaks keyboard layout in Intrepid
https://bugs.launchpad.net/bugs/289918
You received this bug notification because you
I noticed that there were some updates to some of the affected packages.
Can anyone confirm that this is fixed? I have downgraded my client to
Hardy, so I'm unable to test.
--
Regression: Connecting to FreeNX breaks keyboard layout in Intrepid
https://bugs.launchpad.net/bugs/289918
You received t
Changing the affected package to metacity because xorg-server is
reporting the right keycode.
** Changed in: metacity (Ubuntu)
Sourcepackagename: xorg-server => metacity
--
Regression: Connecting to FreeNX breaks keyboard layout in Intrepid
https://bugs.launchpad.net/bugs/289918
You received thi
** Changed in: xorg-server (Ubuntu)
Sourcepackagename: gnome-control-center => xorg-server
--
Regression: Connecting to FreeNX breaks keyboard layout in Intrepid
https://bugs.launchpad.net/bugs/289918
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is sub
I tried it with Gnome, KDE, IceWM and even a bare xterm on the server
side, all with the same effect. So I don't think it has anything to do
with the chosen desktop environment.
--
Regression: Connecting to FreeNX breaks keyboard layout in Intrepid
https://bugs.launchpad.net/bugs/289918
You recei
This is a bug in gnome-control-center.
The keyboard model is changed, but the key bindings are not updated to use
the new keycodes.
To repeat this behavior you need to:
1 ) Use evdev driver.
2 ) Start the X session using xfree86 or xorg xkb rules.
3 ) Up arrow will take an screenshot.
4 ) Chan
53 matches
Mail list logo
