similar to: [PATCH] Handle ISO_Level3_Shift keysym as AltGr in ioemu/vncfb

On Fri, Mar 31, 2006 at 01:33:18PM -0600, Tom Spear wrote: > Hi all, this is a call for volunteers. I am hoping that certain developers > participating in another thread are willing to rewrite the keyboard code, > but we need people to test. If you are interested, please reply here saying > that you are interested, and what kind of keyboard you use, as well as the > layout you use

Hi, I would like to use CorelDraw 11 under linux with wine (20040813). I have successfully installed this from the CDs, and I can start using the following DLL overrides / config: [AppDefaults\\CorelDrw.exe\\Version] "Windows"="nt40" [AppDefaults\\CorelDrw.exe\\WinMM] "Drivers" = "" [AppDefaults\\CorelDrw.exe\\DllOverrides] "wintab32" =

Hi there, It took me a while to find out that there were no xen-vncfb included in the binary x86_64 (don''t know about the other architectures) tarball, and that it was causing xm create to fail (obviously, when the domU had vfb defined). Is there a reason for this? Or they just forgot? Thanks, Marconi. _______________________________________________ Xen-users mailing list

Hi, I have seen a lot of unused xen-vncfb. Can they be kill manually ? Does "domid" run sequentially ? Will it be safe for me to execute "kill -9 12614 11905 10581 11037 11688" below ? Kindly advice. Thanks !! ================================================================= [root@machine xen]# ps -ef | grep -i dbn0 root 10581 1 0 10:02 ? 00:00:00

Hi, I installed the current stable wine from the source a few hours ago on my RedHat9 System. Yes, using the --with-nptl switch. Well, most things are running well, but there is a real great problem! When ever I press the AltGr Key, I get the ^ sign and nothin happend concerning the email "at" sign, the special brackets and so on. I have a Toshiba notebook, 2430-101 with a qwertz

Welcome to the club ;-) ===== Sylvain Petreolle (spetreolle at users dot sourceforge dot net) ICQ #170597259 No more War ! "What if tomorrow the War could be over ?" Morpheus, in "Reloaded". For the Law of Oil and Fire, Im an European that lives in France. For all my Brothers and friends, Im a human living on Earth.

I notice that when I connect from a Windows VNC client (any VNC distribution it seems) to the Centos desktop (Gnome) I cannot send AltGr key combinations. The vncserver on the CentOS side is vino from Gnome. I cannot check if the same happens when connecting from a CentOS machine to a CentOS machine, but it looks more like Gnome simply ignores AltGr when sent over VNC. Why would it do this?

When access to a Xen DomU (Linux) from a VNC client in Windows, alt-gr key is not working properly. When Alt + another key pressed, vncserver receives Altgr down, Altgr up and key down messages in order, that causes incorrect output. With following patch, when vncerver receives key down message, it first check if the keysym needs altgr modifer, if it needs altgr modifier but altgr is not

Full_Name: Zoran Bosnic Version: 2.4.0 OS: Windows XP SP2 Submission from: (NULL) (212.235.140.146) This is a problem that occurs in R GUI Script Editor and is connected to Windows regional settings. Since I live in Slovenia, my computer has a keyboard with additional slovenian international characters. I am therefore using Windows XP SP2 with Input Language (=Keyboard Locale, Control

> Thanks all point about security, I''ll do as follows. > I thought that the point was the following two. > > > 1. Storage place of encrypted password > Should I store it in /etc/xen/passwd ? > Or, should I wait for DB of Xen that will be released in > the future? The xend life cycle management patches were posted by Alistair a couple of months back.

The following series of 10 patches is a merge of the xenfb and xenconsoled functionality into the qemu-dm code. The general approach taken is to have qemu-dm provide two machine types - one for xen paravirt, the other for fullyvirt. For compatability the later is the default. The goals overall are to kill LibVNCServer, remove alot of code duplication and/or parallel impls of the same concepts, and