Open kleshas opened 5 months ago
looks like AirVPN was causing the blank screen. Mullvad VPN doesn't have this issue. I do still have the issue with out_to_wayland=true not working.
Having the same issue with out_to_wayland = true
not displaying any window.
The issue started somewhere between versions 1.19.6 and 1.21.6. With the deb package in Ubuntu 24.04 (1.19.6), I can still see a window when using Wayland. With the 1.21.6 AppImage, the window is blank as described.
I'll download some other AppImage versions and see if I can find the exact version where this issue began.
Edit: The issue starts with version 1.21.0. The AppImage for 1.20.2 displays a window when using Wayland, and the 1.21.0 AppImage does not.
own_window_type
does nothing on Wayland. In future, it should allow configuring window to require sizing/placement like X11 counterparts, for now it's always on the background layer of zwlr-layer-shell
.
Closed issue confirms this bug on KDE besides Sway, so I'm merging them here as this one is older.
cc @maxulm
Related to #1916
@abkein confirms this issue on Hyprland as well.
Running hyprctl
reveals that window is mapped, focusable, and should be visible:
Window 5ef2019dbb90 -> ./src/conky:
mapped: 1
hidden: 0
at: 2,28
size: 956,1050
workspace: 3 (3)
floating: 0
pseudo: 0
monitor: 0
class: kitty
title: ./src/conky
initialClass: kitty
initialTitle: kitty
pid: 687435
xwayland: 0
pinned: 0
fullscreen: 0
fullscreenClient: 0
grouped: 0
tags:
swallowing: 0
focusHistoryID: 1
So this probably has something to do with how buffers are drawn/swapped.
Hi, i can confirm this also happens in labwc (wlroots based). It works if i use it via xwayland, but if wayland fallback is enabled and selected, there is no window.
This is what works at the moment for me:
out_to_wayland = false,
out_to_x=true,
What happened?
Running sway, updated arch (new install). AMD 6750XT
Not sure when it started but recently my previously-working config only shows a blank window. I saw a link on google saying this can be caused by an external IP lookup happening too often, but removing that from my config didn't help.
When out_to_x=true, out_to_wayland=false I get a blank conky window. When out_to_x=false, out_to_wayland=true I don't get a window at all (though there is a conky running in htop).
Actually, it seems that the window DOES eventually populate, but after a few mins, and it seems to not be doing any further updates (I have a time entry in the config, it hasn't changed for 5 mins).
With out_to_wayland=true there is no change using own_window_type override, desktop or normal. Running from command line: conky -c ~/.conkyrc conky: drawing to single buffer conky: FOUND: console conky: FOUND: ncurses conky: FOUND: file conky: FOUND: x11 conky: FOUND: wayland
and nothing after.
conky-cairo (1.21.2) has the error: "unknown setting out_to_wayland, and Unable to find a usable display output when using out_to_wayland=true
Version
all from 1.18
Which OS/distro are you seeing the problem on?
Arch Linux
Conky config
Stack trace
No response
Relevant log output
No response