Open harridu opened 2 years ago
CendioOssman
commented
2 years ago Hmm... Odd. Does this happen with other window managers, or just fvwm3?
The menu is handled by FLTK, so I'd appreciate if you could try if the same thing happens with the general Linux build you can download from us. If that works then it would indicate some problem with how FLTK is built.
harridu
commented
2 years ago There is no such problem for fvwm2, for example. See https://github.com/fvwmorg/fvwm3/issues/519
samhed
commented
2 years ago What an annoying bug :laughing:
Did you test our build?
CendioOssman
commented
2 years ago No response. Closing.
harridu
commented
1 year ago @CendioOssman , @samhed Due to this bug I haven't used fvwm3 anymore. I gave it (version 1.0.6a built by Debian) a new chance this morning, but the problem is still in :-(.
I do not know what you mean by "Did you test our build?"
Would you mind to reopen this issue?
CendioOssman
commented
1 year ago I do not know what you mean by "Did you test our build?"
If you go to our release page, then there is a generic Linux build (the .tar.gz one) available via Sourceforge. Please try that and see if it also has the same issue. That allows us to determine whether it is a Debian specific issue or not.
harridu
commented
1 year ago You mean your source code is on github, but prebuilt binaries are on Sourceforge? A link to this would be very nice. I couldn't find it.
The fvwm3-1.0.6a.tar.gz on the release page on github provides just the source files, AFAICT. I had built fvwm3 on my own when I opened this ticket, anyway. There was no fvwm3 package provided by Debian at that time.
harridu
commented
1 year ago To be sure I have rebuilt fvwm3 1.0.6a using my own source package and the sources from the gitlab release page, ignoring Debian's modifications. Same problem. Here is the log file: build.log.gz
CendioOssman
commented
1 year ago The file in question would be this one:
https://sourceforge.net/projects/tigervnc/files/stable/1.13.1/tigervnc-1.13.1.x86_64.tar.gz/download
harridu
commented
12 months ago Hi Pierre, sorry for the late response.
I have uninstalled the local Debian packages for tigervnc, extracted the binary tgz file in /usr/local/stow, fixed my $PATH and tried the downloaded vncviewer binary: Same result. The F8 menu is missing again.
samhed
commented
11 months ago Same result. The F8 menu is missing again.
The F8 menu didn't seem to be missing in the video, but would rather "run away" as in the issue title. Does our 1.13.1 build behaves the same way as Debian's 1.11.0 build here?
I'm not familiar with fvwm3. Do you have some settings that might affect this? I'm thinking about stuff like "focus follows mouse" or similar.
Does other vncviewer windows behave the same way? (options window, connection info, about dialog etc.)
harridu
commented
9 months ago Sorry for the late response. I am not a regular user.
Today I got no F8 popup at all (using the version built on Debian), so I tried your binaries again: No problem. After that Debian's version worked well, too, in the same XWindow session! I wouldn't agree to blame Debian here. There are still some details to reveal. It is hard to reproduce.
harridu
commented
9 months ago On the next try immediately after my last comment the problem was back, even for the version downloaded from sourceforge.
Describe the bug Sometimes the F8 menu appears to run away from the mouse. Sometimes it is not shown at all (or off screen).
To Reproduce
Expected behavior The context menu is supposed to pop up under the mouse pointer.
Screenshots https://user-images.githubusercontent.com/832164/137118637-5dbb0a2f-095a-4e42-bb42-def4e7e189a9.mp4
The other case (the F8 menu does not show up) is not shown here.
Client (please complete the following information):
Server (please complete the following information):