Bug#784328: FVWM: fvwm hotkey problem inside vnc

On Mon, 29 Feb 2016 09:33:23 +0100 Claude Krantz wrote: > > Dear Thomas, > > As far as I understand Hendriks analysis, there is indeed nothing upstream > FVWM > can do about this. He included the fvwm mailing list before his analysis > showed > that the bug is

Bug#784328: FVWM: fvwm hotkey problem inside vnc

Hi, Thomas Adam writes: > On 28 February 2016 at 23:05, Hendrik Tews wrote: >> The XKEYBOARD doc clearly say, no Xkb function should be called >> if the server does not provide XKEYBOARD. And indeed, inside >> vnc4server, XkbKeycodeToKeysym does

Bug#784328: FVWM: fvwm hotkey problem inside vnc

Dear Thomas, As far as I understand Hendriks analysis, there is indeed nothing upstream FVWM can do about this. He included the fvwm mailing list before his analysis showed that the bug is introduced in Debian. Hendriks analysis indeed suggests to me that, until all X servers shipped with

Bug#784328: FVWM: fvwm hotkey problem inside vnc

On 28 February 2016 at 23:05, Hendrik Tews wrote: > The XKEYBOARD doc clearly say, no Xkb function should be called > if the server does not provide XKEYBOARD. And indeed, inside > vnc4server, XkbKeycodeToKeysym does always return 0. (I attach a > small test program that

Bug#784328: FVWM: fvwm hotkey problem inside vnc

Hendrik Tews writes: > I found the culprit: It's the Debian deprecated.patch, which I > attach below, in case you are interested. I analyzed the problem a bit further. The patch deprecated.patch replaces various occurrences of XKeycodeToKeysym with XkbKeycodeToKeysym,

Bug#784328: FVWM: fvwm hotkey problem inside vnc

Here is the patch. To me it looks like these changes have been introduced in the first 2.6.5 Debian package. Bye, Hendrik This email and any attachments thereto may contain private, confidential, and/or privileged material for the sole use of the intended recipient. Any review, copying, or

Bug#784328: FVWM: fvwm hotkey problem inside vnc

I found the culprit: It's the Debian deprecated.patch, which I attach below, in case you are interested. This means it's a Debian packaging bug. Debian applies this deprecated.patch during build, thereby apparently making fvwm incompatible with the X xerver running inside vnc. In retrospect, I

Bug#784328: FVWM: fvwm hotkey problem inside vnc

Hendrik Tews writes: > Dan Espen writes: > >> On the Debian list they say: >> >> So after all, this bug may have been triggered by a change in VNC >> rather than in FVWM. >> >> I don't see how Fvwm can help. >> Try the VNC folks. > > I

Bug#784328: FVWM: fvwm hotkey problem inside vnc

Dan Espen writes: > On the Debian list they say: > > So after all, this bug may have been triggered by a change in VNC > rather than in FVWM. > > I don't see how Fvwm can help. > Try the VNC folks. I agree that it looks like the problem is outside fvwm. However, I

Bug#784328: FVWM: fvwm hotkey problem inside vnc

Hi, [reincluding the fvwm list, because I still have the hope that our observations might trigger an idea that leads to a solution] Claude, thanks for restating your FreeBSD observation, I was not aware of that. From that I conclude that the bug is fixed or introduced by either - the Debian or

Bug#784328: FVWM: fvwm hotkey problem inside vnc

Dear Hendrick, Thanks for pointing out that this issue has been raised before on the fvwm mailing list: https://www.mail-archive.com/fvwm@lists.math.uh.edu/msg16901.html Indeed the problem Raphael describes seem identical to the one I have with fvwm 2.6.5 inside tightvncserver on Debian.

Bug#784328: FVWM: fvwm hotkey problem inside vnc

Hendrik Tews writes: > Dear all, > > [sorry for crossposting - but I would like to connect different > sources about this problem] > > The problem is that fvwm does not install any keybindings when > started inside a vncserver, see Debian bug #784328 or Raphael's > post