Greetings, I would like this problem fixed. How about you?
a) Does VMWare have a physical office in Manhattan by chance? How about near Fort Lauderdale, FL? b) Does anyone know the e-mail address or name and physical location of a VMWare software developer? c) Will anyone physically join me in going there? (NYC is also a great place for a trip!) Thanks! On Mon, Aug 25, 2008 at 3:27 PM, Ronny Ager-Wick <[EMAIL PROTECTED]>wrote: > I remember having this problem even with Dapper, that's so long time ago > I can't even remember the version number... I have no idea what x.org > version I used back then, but surely it can't have been v.7.3? > At that time, as I didn't manage to solve it and didn't really need > VMWare, I just stopped using it. It's only when I reinstalled it on > Gutsy (7.10), and then Hardy (8.04) that I really tried hard finding a > solution and have been using setxbmap ever since. But mostly I avoid the > problem by not triggering it, for example by: > When switching the VM for using it in windowed mode, give the VM the > keyb and mouse by clicking inside the window and release it with Crtl-Alt. > When switching the VM for using it in full screen, do NOT click inside > the VM to give it keyb/mouse, but rather press Crtl-Alt-Enter when > VMWare viewer is the active window. Release with Crtl-Alt as usual. > > If I accidentally switch to full screen mode after using the VM in > windowed mode, there's a 100% chance the problem will occur, so when > that happens I just run setxkbmap. > > I know, not a solution, but at least it's livable. As I'm using the free > version of vmware, I can live with it until: > 1. They fix it > 2. VirtualBox becomes stable enough to use > > Ronny. > > Milleman wrote: > > Just wanted to add to my previous posting... > > > > If it turns out to be an "issue" with the newer x.org v7.3, that may be > > somewhat different from the v7.2, I'll would anyhow consider the whole > > problem as a VMWare problem that has to be fixed by the VMWare team. If > > VMWare isn't fully compatible with x.org v7.3, then it must be their > > mission to make it compatible. > > > > > > -- > Shift key (and caps lock) stop working when using VMWare > https://bugs.launchpad.net/bugs/195982 > You received this bug notification because you are a direct subscriber > of the bug. > > Status in The Linux Kernel: Invalid > Status in "linux" source package in Ubuntu: New > Status in "xorg" source package in Ubuntu: Triaged > Status in Gentoo Linux: New > > Bug description: > After a day or so of running the shift key mysteriously stops working as > does the cap lock. In other words I cannot enter shifted characters of any > kind. The keyboard is connected to a KVM and all other systems respond to it > properly. In additional any VMWare sessions I have open respond correctly. > So I have the condition where all non-vmware applications in Ubuntu Hardy > (all updates applied as of 2008-02-26 at 12:43 UTC) fail to recognize the > shift key BUT applications within an active (a paused/restarted session also > works) VMWare sessions running DO recognize the key. > > When this condition occurs ALL applications (except those within a VMWare > session) are also unstable and will usually crash within a few keystrokes.If > I continue to operate in this mode. I cannot pinpoint what, if any, > application triggers this. It has always happened while working within > terminal/browser/vmware sessions and NOT when opening a new application. It > could be related to the KVM switch, but none of my other systems (2 > Mandriva, 1 Windows) are affected by this. > > This bug has been present on my system for a number of days across daily > updates and reboots (if the update requested it) and I think since I > installed Hardy Alpha 1. > > A work around: log off and back on. A reboot/restart does not appear to be > needed. > > Error logs show some unusual activity. > > --- MARK ---- > ... > ... kernel ... rtc lost 7 interrupts ... > --- MARK --- > .... > > Plus some segfaults indicating which application crashed as I tried to type > into it (mouse works fine). > > System: HP dv9743cl (which otherwise works lovely) > Ubuntu: Hardy 8.04 (from lsb-release) > > ---- > TEST CASE: > 1. Click inside the VM and > 2. Hold any of the Ctrl, Alt and/or shift keys while releasing the > keyboard/mouse to the host OS (which you obviously do when you press > Crtl-Alt to revert back to windowed mode, as the cursor is then released > from the VM). > > WORKAROUND: > After this happens to recover your keyboard execute 'setxkbmap' in a > terminal > -- Shift key (and caps lock) stop working when using VMWare https://bugs.launchpad.net/bugs/195982 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/mailman/listinfo/ubuntu-bugs
