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

Issue with second monitor after recent updates #3953

Closed
Irubataru opened this issue Sep 14, 2024 · 4 comments
Closed

Issue with second monitor after recent updates #3953

Irubataru opened this issue Sep 14, 2024 · 4 comments

Comments

@Irubataru
Copy link

Irubataru commented Sep 14, 2024

Output of awesome --version:

awesome v4.3-1666-gd53eb1be6-dirty (Too long)
 • Compiled against Lua 5.4.7 (running with 0.9.2)
 • API level: 4
 • D-Bus support: yes
 • xcb-errors support: no
 • execinfo support: yes
 • xcb-randr version: 1.6
 • LGI version: /usr/share/lua/5.4/lgi/version.lua
 • Transparency enabled: yes
 • Custom search paths: no

Description

After recently updating my system (arch, using the AUR awesome-git package, I have tried recompiling it), I am having issues with my second monitor. Nothing shows up on it except the mouse cursor. If I clone the display it works fine, and if I play around with the resolution of it then it sometimes shows "something", but it's messed up, and when I move a window to the monitor it simply disappears regardless if some of the background and title bar is visible on it.

image

Not sure if this is an awesome issue, but I also don't know how to debug it. If I downgrade to the Arch awesome package (version 4.3-4) it works, but my config doesn't. It also fails with an empty config. Link to my config.

Edit: I tried rolling arch back to the last state I thought it worked, and rebuilt awesome, but it still doesn't work. Seems my system is just broken somehow 🤷‍♀️

@Irubataru
Copy link
Author

Irubataru commented Sep 14, 2024

My guess is that this doesn't directly relate to recent changes in awesome, I have made a thread on the Archlinux forums.

@Irubataru Irubataru closed this as not planned Won't fix, can't repro, duplicate, stale Sep 14, 2024
@actionless
Copy link
Member

also try running awesome in --no-argb mode

@Irubataru
Copy link
Author

It turned out to be an issue with picom ^^

@vredesbyyrd
Copy link

This should be fixed in picom now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants