** No longer affects: vino (Ubuntu Feisty)
** No longer affects: vnc4 (Ubuntu Feisty)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/112955
Title:
vino (vnc) keyboard mapping problem
To manage noti
** Changed in: tightvnc (Ubuntu)
Importance: Undecided => Low
** Changed in: vnc4 (Ubuntu)
Importance: Undecided => Low
** Changed in: vnc4 (Ubuntu Feisty)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: vnc4 (Ubuntu Feisty)
Status: Invalid => Won't Fix
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/112955
Title:
vino (vnc) keyboard mapping problem
To mana
The verification-needed tag is added by the SRU team when the upload is
approved in the -proposed pocket.
** Tags removed: verification-needed
** Also affects: tightvnc (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: tightvnc (Ubuntu Feisty)
--
You received this bug
** Package changed: tightvnc (Baltix) => tightvnc
** Changed in: tightvnc
Importance: Undecided => Unknown
** Changed in: tightvnc
Status: Confirmed => Unknown
** Changed in: tightvnc
Remote watch: None => SourceForge.net Tracker #2232405
--
You received this bug notification becaus
** Changed in: tightvnc (Baltix)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/112955
Title:
vino (vnc) keyboard mapping problem
To manage notifications about this b
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: vnc4 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/112955
Title:
vino (
** Changed in: vino
Importance: Unknown => Medium
--
vino (vnc) keyboard mapping problem
https://bugs.launchpad.net/bugs/112955
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
beastiezee :i can confirm that the XKL_XMODMAP_DISABLE xstartup does NOT
fix the problem with the lower 's' key being mapped to the shutdown
button on the gnome desktop in 10.04 unbuntu.
I also noticed I have the same problem including the lower case letter
"m" which is mapped to the email and cha
Feisty is no more supported.
** Changed in: vnc4 (Ubuntu Feisty)
Status: New => Invalid
--
vino (vnc) keyboard mapping problem
https://bugs.launchpad.net/bugs/112955
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Haven't seen this posted, which sums up the problem I have (shift key
doesn't do its job over VNC):
http://machine-cycle.blogspot.com/2009/02/vnc-shifty-keyboard-
problems.html
Note that this isolates the problem to gnome-settings-daemon.
For x11vnc (which I use) the workaround is the -xkb optio
vino btw works like a charm on all my boxes. However, it is very limited
and does not allow for multiple sessions on multiple logins. vino worked
out of the box with no setup other than the normal GUI.
** Also affects: vnc4 (Ubuntu)
Importance: Undecided
Status: New
--
vino (vnc) keybo
i can confirm that the XKL_XMODMAP_DISABLE xstartup does NOT fix the
problem with the lower 's' key being mapped to the shutdown button on
the gnome desktop in 10.04 unbuntu. I have it installed on 6 systems 2
that were upgraded and 5 fresh installs 64 & 32 bit. I have the same
problem Y Chow has i
The XKL_XMODMAP_DISABLE workaround partially works in 10.04. I am
running tightvncserver. The lower case "s" key causes the shutdown menu
to be selected. Upper case "S" functions correctly. There might be
other keys that don't work properly but lower case "s" is the only one
I've discovered so
I can also confirm in Karmic the XKL_XMODMAP_DISABLE fix worked. I
should point out that I did not have this problem in 8.10 Hardy. Or it
was fixed in some other way.
--
vino (vnc) keyboard mapping problem
https://bugs.launchpad.net/bugs/112955
You received this bug notification because you are
I can also confirm Karmic and XKL_XMODMAP_DISABLE fix worked
--
vino (vnc) keyboard mapping problem
https://bugs.launchpad.net/bugs/112955
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubu
This bug is still present in Karmic. Adding the fake keyboard only seems
to work for me if I start the VNC server from an ssh session on the
remote client. The gconf-tool setting up the [aa] keyboard command does
work, but messes with the desktop themes. However the
XKL_XMODMAP_DISABLE fix worked.
** Branch linked: lp:ubuntu/feisty-proposed/vino
--
vino (vnc) keyboard mapping problem
https://bugs.launchpad.net/bugs/112955
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
http
I'm using Jaunty and everything is working fine for me after I removed
tightvncserver and instead installed vnc4server.
--
vino (vnc) keyboard mapping problem
https://bugs.launchpad.net/bugs/112955
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Comment #55 works for a non-Ubuntu Linux as well! Tested on both Arch
and Redhat. Thank you Bassu Khan for that!
--
vino (vnc) keyboard mapping problem
https://bugs.launchpad.net/bugs/112955
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
Found the same problem on 9.04 Jaunty Jackalope.
Comment #55 works, even for a french mapping.
--
vino (vnc) keyboard mapping problem
https://bugs.launchpad.net/bugs/112955
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Does this issue resolved?
I'm using Ubuntu 9.04, still can't get comment #31 works.
Any clue?
--
vino (vnc) keyboard mapping problem
https://bugs.launchpad.net/bugs/112955
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
^ Almost same as Sakari's issue.
Using Jolly VNC client and/or Screen Sharing in Mac OS X 10.5.7 to connect to
Ubuntu 9.04 tightvncserver (1.3.4?).
Get jobbled/garbled keys in a terminal.
ssh works fine from same Mac.
Used the XKL_XMODMAP_DISABLE fix as described and that seemed to work.
--
v
I have this bug between a xtightvnc client on Jaunty and the
tightvncserver on Debian Lenny. I'm using Finnish keyboards with
otherwise en_GB locales.
Just confirming that Bassu's XKL_XMODMAP_DISABLE fix on the Lenny server
fixed this issue for me as well.
--
vino (vnc) keyboard mapping problem
Just like to add that this bug is present on my Jaunty system running on
ARM using tightvncserver and GNOME. Bassu's XKL_XMODMAP_DISABLE fix does
seem to correct this problem.
--
vino (vnc) keyboard mapping problem
https://bugs.launchpad.net/bugs/112955
You received this bug notification because
** Changed in: vino (Ubuntu Feisty)
Assignee: Sebastien Bacher (seb128) => Ubuntu Desktop Bugs (desktop-bugs)
--
vino (vnc) keyboard mapping problem
https://bugs.launchpad.net/bugs/112955
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
Just got that fixed by adding 'export XKL_XMODMAP_DISABLE=1' in
$HOME/.vnc/xstartup before the last line /etc/X11/Xsession
Making the server apps work in Ubuntu is like riding a horse without a
paddle... :P !!
--
vino (vnc) keyboard mapping problem
https://bugs.launchpad.net/bugs/112955
You rece
Yes, another pain in Ubuntu? But the question is why doesn't this occur
in Fedora, CentOS and Redhat... :P
--
vino (vnc) keyboard mapping problem
https://bugs.launchpad.net/bugs/112955
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
This is still a problem under jaunty at this point. The workaround
mentioned in this thread re: keyboard layouts does still work, but is
naturally very annoying.
This issue seems to be reported and being tracked on the tightvnc
sourceforge page, but no progress at this stage:
http://sourceforge.
One additional comment on this workaround:
https://bugs.launchpad.net/ubuntu/+source/vino/+bug/112955/comments/31
After typing the characters 'us' (appearing as 'mb'), this keymap needs to be
moved to
the top of the list, so that it is the first keymap attempted to be applied.
Everything else w
I've also encountered this issue with TightVNC and the hardy release. My
solution was to capture the xmodmap -pke output as ${HOME}/.Xmodmap at
the login screen (DISPLAY=:0 XAUTHORITY=/var/lib/gdm/:0.Xauth sudo
xmodmap -pke > ${HOME}/.Xmodmap). When gnome-settings-daemon starts up
and finds an .Xmo
and in the final release
--
vino (vnc) keyboard mapping problem
https://bugs.launchpad.net/bugs/112955
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mai
The problem also exists in Hardy (beta).
--
vino (vnc) keyboard mapping problem
https://bugs.launchpad.net/bugs/112955
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://list
The workaround is not sufficient for everyone (certainly not me), since
it has to be performed for every user. On multi-user systems, this can
quickly become a problem. In addition, the workaround assumes that a US
keyboard layout is OK for everyone, which is not the case when different
layouts are
Sorry, this is a production system.
I already rue the upgrade to gutsy because I experienced nasty problems with
setserial and lirc.
Using hardy is not an option.
--
vino (vnc) keyboard mapping problem
https://bugs.launchpad.net/bugs/112955
You received this bug notification because you are a m
Thanks Wolfgang.
With this workaround the keyboard works. I'm happy now.
BTW: I get a XKB error on Gnome startup. I think it complains about the unknown
"aa" layout.
--
vino (vnc) keyboard mapping problem
https://bugs.launchpad.net/bugs/112955
You received this bug notification because you are
Re wjs
https://bugs.launchpad.net/ubuntu/+source/vino/+bug/112955/comments/31
I too can confirm this workaround solves the issue.
You can perform the same setting without the graphical gconf-editor using the
following command (e.g. via SSH):
gconftool --set /desktop/gnome/peripherals/keyboard/kb
Could you try if that's still an issue using hardy?
--
vino (vnc) keyboard mapping problem
https://bugs.launchpad.net/bugs/112955
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu
After upgrade to Ubuntu 7.10 still suffering of this bug.
I'm tired of working with KDE...
@anonym: Would you tell me how to implement your "aa" fix?
--
vino (vnc) keyboard mapping problem
https://bugs.launchpad.net/bugs/112955
You received this bug notification because you are a member of Ubunt
C'mon people. This is embarrassing. This seemingly huge bug has been
around since may 07. I fixed it too by giving gnome a non-existant
keymap "aa" to load on startup, but this is hardly a fix for production
environments. Do the gnome devs know about the problem, or do they not
care? How do we
This is in -proposed for over three months now, and testing feedback has
been mostly negative. I removed the -proposed version.
** Changed in: vino (Ubuntu Feisty)
Status: Fix Committed => Won't Fix
--
vino (vnc) keyboard mapping problem
https://bugs.launchpad.net/bugs/112955
You received
Problem can be workaround as described in below link (provided by Randy
in this bug report on 7.04)
https://bugs.launchpad.net/ubuntu/+source/vino/+bug/112955/comments/3
The reason it worked for me on 7.04 is probably because I installed that
one from scratch. Keyboard problems from the moment I u
I'm using vncserver (apt-get vncserver) as the server application and realvnc
as my client.
This worked fine on Ubuntu 7.04 and no longer works on 7.10. No changes were
done at client side, so I'm not convinced the problem is at client side.
I tried using the VINO application, then the keyboard
@wjs: Your problem seems to be client related.
Try to connect to the vino using another client, like vinagre (version
from svn) - http://www.gnome.org/projects/vinagre/
--
vino (vnc) keyboard mapping problem
https://bugs.launchpad.net/bugs/112955
You received this bug notification because you ar
112955] Re: vino (vnc) keyboard mapping problem
I installed Gutsy final from scratch, with the new vino version all my
problems are solved. Every key works perfectly out of the box
--
vino (vnc) keyboard mapping problem
https://bugs.launchpad.net/bugs/112955
You received this bug notification
I installed Gutsy final from scratch, with the new vino version all my
problems are solved. Every key works perfectly out of the box
--
vino (vnc) keyboard mapping problem
https://bugs.launchpad.net/bugs/112955
You received this bug notification because you are a member of Ubuntu
Bugs, which is t
I had the same problem with the Final Stable release of Ubuntu 7.10,
using TightVNC Server. WSJ's trick noted above of typing US (displayed
as mb) in the Configuration Editor > desktop > gnome > peripherals >
keyboard > kbd Layout key worked great, but this seems more like a
bandage than a real f
Under "desktop > gnome > peripherals > keyboard > kbd" I had two entries, "it
nodeadkeys" (my correct keyboard) and "us". Removing "us" solved almost of my
issues, and now capital letters and shifted characters work !
The only non-working ones are: 6k àà ìì, they should be 6& à° ì^. Also AltGr
c
Thank you very much for this work-around wjs! That worked for me as
well. I had to logout and log back in, but it worked. My keybindings
are no longer funky anymore, thank you thank you thank you thank you!
--
vino (vnc) keyboard mapping problem
https://bugs.launchpad.net/bugs/112955
You recei
One correction to the above (i went back and tested):
I had to type the letters "u" and "s" (which output as "m" and "b") in
that field. So, it figures that you should just need to type whatever 2
character string that applies to your keyboard.
HTH,
Will
--
vino (vnc) keyboard mapping problem
I have a temporary workaround for US English keyboard. I don't know if
it will work for any other keyboard settings but you might try and
report back.
1) Open gconf editor in a terminal:
$gconf-editor
obviously if you are trying to do this with a messed up terminal, you
won't be able to. The
i installed with a dvorak keyboard setup and i can confirm the same
problems other people are having. capital letters don't work at all
through remote desktop (but these parens type just fine) which should be
obvious as i am typing this message via a remote desktop connection to
my computer right
i'm using vino 2.18.1-0ubuntu1.1 from feisty-proposed, with an italian keyboard.
capital letters do not work at all, neither with shift or caps lock, and none
of the special characters above the numbers. some other special keys work, \|
'- èé +* òç ù§ ,; .: -_<>
--
vino (vnc) keyboard mapping p
The patch applied in 2.18.0-ubuntu1.1 broke vino much harder on my system - I
can't write any capital letters now (as well as any characters created by
pressing shift+number). My keyboard settings: us,il grp_led:scroll
grp:switch_toggle (set through the gnome keyboard layout setting dialog,
ins
The only way I can fix this is to
1) set Preferences > Themes to anything but 'Human'
2) Reboot (logout may work, dunno)
3) Log back in.
Key mapping will now work correctly
I am using TIghtVNC 1.3.9
Cheers,
Will
--
vino (vnc) keyboard mapping problem
https://bugs.launchpad.net/bugs/1129
I've discovered a work-around which works for my particular environment,
but which may also work for others. I suffered from the same symptoms,
and eventually started booting into KDE to "fix" it, but it was still
"broken", just slightly less so. For instance, my right-arrow key was
mapped incorr
This release has fixed the bug for me - I had to reboot (rather than just
disconnect / reconnect to the updated vino) but after that the | < > keys
(which were the most annoying ones) work fine.
Thanks for your help with this.
--
vino (vnc) keyboard mapping problem
https://bugs.launchpad.net/bu
Sorry - spoke too soon. All the keys appear to work (haven't tried
function keys yet) EXCEPT for shift+3 (£ sign on a UK keyboard) and
shift+7 (ampersand - &).
Instead of £ I get 3 and instead of & I get k (lower case).
When using a local keyboard / screen these keys do what they should do.
--
Just tried the proposed update on feisty
(pool/main/v/vino/vino_2.18.1-0ubuntu1.1_i386.deb), restarted my X
session and I still see problems with keyboard mappings (I'm using en_GB
keyboard on both machines).
< = \
> = |
{ = [
} = ]
and more.
--
vino (vnc) keyboard mapping problem
https://bugs.
Accepted into feisty-proposed, please go ahead with QA testing.
** Tags added: verification-needed
** Changed in: vino (Ubuntu Feisty)
Status: In Progress => Fix Committed
--
vino (vnc) keyboard mapping problem
https://bugs.launchpad.net/bugs/112955
You received this bug notification bec
the package has been uploaded to feisty-proposed now
--
vino (vnc) keyboard mapping problem
https://bugs.launchpad.net/bugs/112955
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubunt
http://launchpadlibrarian.net/8554101/vino.debdiff is good for upload if
you s/gutsy/feisty-proposed/ :-)
** Changed in: vino (Ubuntu Feisty)
Assignee: Ubuntu Desktop Bugs => Sebastien Bacher
Status: Triaged => In Progress
--
vino (vnc) keyboard mapping problem
https://bugs.launchpad
The changes are a proposed update for feisty, the patch is already used
in gutsy and is working correctly on the machine where I've tested it
--
vino (vnc) keyboard mapping problem
https://bugs.launchpad.net/bugs/112955
You received this bug notification because you are a member of Ubuntu
Bugs, w
** Attachment added: "patched used to fix the bug"
http://launchpadlibrarian.net/8554102/90_from_svn_fix_keyboard_mapping_bug.patch
--
vino (vnc) keyboard mapping problem
https://bugs.launchpad.net/bugs/112955
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Changed in: vino (Ubuntu Feisty)
Importance: Undecided => High
Assignee: (unassigned) => Ubuntu Desktop Bugs
Status: New => Triaged
** Attachment added: "debdiff for update"
http://launchpadlibrarian.net/8554101/vino.debdiff
--
vino (vnc) keyboard mapping problem
https://bu
> And do you know a workaround, which is not "walk around"?
I suppose the problem does lie with the keyboard selection, so I simply fix the
type if I did not select the correct mapping in the first place. I suppose
someone could actually fix the pacakge in 7.04. I've not bothered since the bug
d
> I'm one of the administrators who fell victim to this bug.
And do you know a workaround, which is not "walk around"?
To address the Ubuntu release process - I think this criterion for
"high-impact bugs" applies here: "Bugs which represent severe
regressions from the previous release of Ubuntu"
"From my point of view this bug has to be fixed in 7.04 too. This is a
major bug. It breaks VNC and makes Ubuntu unusable for a large group of
users, especially for admins managing lots of machines via VNC."
I'm one of the administrators who fell victim to this bug. Bugs can be
very embarrassing w
Which release of Ubuntu do you use? This bug is fixed only in unstable
7.10 and not in stable 7.04.
>From my point of view this bug has to be fixed in 7.04 too. This is a
major bug. It breaks VNC and makes Ubuntu unusable for a large group of
users, especially for admins managing lots of machines
"There seems to be no update! Please explain how I get the fix. Thanks."
The fix has been released for Gutsy, but not Feisty. He did say, "Fixed
in Tribe 3", so please be a bit more aware of the release process.
Please read https://wiki.ubuntu.com/StableReleaseUpdates
--
vino (vnc) keyboard map
So you say it's fixed. How do I get the fix? Doing:-
apt-get update
apt-get upgrade
only installed updates to firefox! And:-
apt-get install vino/vncserver
Gives the following:-
[EMAIL PROTECTED]:~# apt-get install vino
Reading package lists... Done
Building dependency tree
Reading stat
Fixed with tribe 3.
** Changed in: vino (Ubuntu)
Status: Fix Committed => Fix Released
--
vino (vnc) keyboard mapping problem
https://bugs.launchpad.net/bugs/112955
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu
It seems to depend on the language/keyboard setting during the Ubuntu
installation. If this is not US English, the keyboard via VNC is broken.
Please fix this bug in stable release.
--
vino (vnc) keyboard mapping problem
https://bugs.launchpad.net/bugs/112955
You received this bug notification b
hrm. one of my fresh installs didn't work by my upgraded machine works
fine, so nevermind. Seems to be a user specific problem on my side.
--
vino (vnc) keyboard mapping problem
https://bugs.launchpad.net/bugs/112955
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Might someone propose this bug fix for a stable release update? I
believe this affects all 7.04 installs, so this means NO installations
of vino work on 7.04. This means all installations of 7.04 are broken
and unusable.
--
vino (vnc) keyboard mapping problem
https://bugs.launchpad.net/bugs/11295
** Changed in: vino (upstream)
Status: Unconfirmed => Fix Released
--
vino (vnc) keyboard mapping problem
https://bugs.launchpad.net/bugs/112955
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ub
Fixed upstream.
** Changed in: vino (Ubuntu)
Status: Confirmed => Fix Committed
--
vino (vnc) keyboard mapping problem
https://bugs.launchpad.net/bugs/112955
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs m
** Changed in: vino (upstream)
Status: Unknown => Unconfirmed
--
vino (vnc) keyboard mapping problem
https://bugs.launchpad.net/bugs/112955
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-
I've sent the bug upstream,
http://bugzilla.gnome.org/show_bug.cgi?id=440429
** Bug watch added: GNOME Bug Tracker #440429
http://bugzilla.gnome.org/show_bug.cgi?id=440429
** Also affects: vino (upstream) via
http://bugzilla.gnome.org/show_bug.cgi?id=440429
Importance: Unknown
Sta
For what it's worth. I've experienced this exact same issue on a fresh
install of 7.04, so it appears that it's not limited to just upgrades.
--
vino (vnc) keyboard mapping problem
https://bugs.launchpad.net/bugs/112955
You received this bug notification because you are a member of Ubuntu
Bugs,
I have the same problem described in "bug description". On 7.04, I can
start a vnc server (tightvnc), and the keyboard is fine until I type
"gnome-session", after which point it's remapped as described.
If instead, I run:
gnome-wm &
gnome-panel &
nautilus --no-default-window &
gnome-cups-icon &
g
Thakns. If it is GNOME then it's something about the way that GNOME and vino
interact. I'm typing this whilst locally attached to a GNOME session on the
machine that exhibits the problem when connected to via VNC, and all the
keymappings work fine.
--
vino (vnc) keyboard mapping problem
htt
I think the problem is GNOME, not VNC or vino. I am connecting from a Mac
Powerbook G4 using Chicken of the VNC 2.0b4, to a freshly upgraded x86 Ubuntu"
7.04 running tightvnc server 1.2.9-21. When I launch programs from X, I have
no trouble typing. However, when I run gnome-session, the key
83 matches
Mail list logo
