Skip to content
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

Closed
voltumna opened this issue May 23, 2020 · 4 comments
Assignees
Labels
type:bug Something's broken!
Milestone

Comments

@voltumna
Copy link

is this a real bug?

@ThomasAdam
Copy link
Member

No, I'll need to remove the debug... thanks for the reminder.

@ThomasAdam
Copy link
Member

@voltumna -- feel free to write a patch to remove it.

@voltumna
Copy link
Author

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 😄

@ThomasAdam
Copy link
Member

Hi @voltumna

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,

For this, you'll need to install the header files for these packages. Some Linux distributions have these as -deve packages, hence:

libxpm-dev
libpng-dev

etc, etc.

but luckily, I can simply ignore this error smile

No problem, I'll remove this.

-- Thomas

@ThomasAdam ThomasAdam self-assigned this May 24, 2020
@ThomasAdam ThomasAdam added the type:bug Something's broken! label May 24, 2020
@ThomasAdam ThomasAdam added this to the 1.0 milestone May 24, 2020
ThomasAdam added a commit that referenced this issue Jun 7, 2020
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
mikeandmore pushed a commit to mikeandmore/fvwm3 that referenced this issue Nov 28, 2020
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
@ThomasAdam ThomasAdam added this to FVWM3 Sep 18, 2022
@ThomasAdam ThomasAdam moved this to Done in FVWM3 Sep 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:bug Something's broken!
Projects
Status: Done
Development

No branches or pull requests

2 participants