-
-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FindScreenOfXY: couldn't find screen at 555 x 134 returning first monitor. This is a bug. #93
Comments
No, I'll need to remove the debug... thanks for the reminder. |
@voltumna -- feel free to write a patch to remove it. |
Oh alright, thank you :) I wish I knew how to create a patch, sorry, I am a user, I am checking the logs because my fvwm3 seems to be missing a lot of supports: xpm, png, ttf etc... and I am looking at how to do it, but luckily, I can simply ignore this error 😄 |
Hi @voltumna
For this, you'll need to install the header files for these packages. Some Linux distributions have these as
etc, etc.
No problem, I'll remove this. -- Thomas |
It's not likely that we're able to map a coordinate to a screen. However, sometimes this can happen early on in FVWM's start up. This error is misleading -- and instead we should remove it. Fixes #93
It's not likely that we're able to map a coordinate to a screen. However, sometimes this can happen early on in FVWM's start up. This error is misleading -- and instead we should remove it. Fixes fvwmorg#93
is this a real bug?
The text was updated successfully, but these errors were encountered: