[Bug 1947185] Re: GNOME on Wayland does not initially display conky output
I should probably explain: Weston is a Wayland compositor, but it appears Conky's error message is about wanting an X11 compositor feature that it thinks is missing. In a Wayland session, X11 composition is provided by 'Xwayland'. So this bug is somewhere between Conky and Xwayland. This is only a problem because Conky only supports X11. The discussion about Conky supporting Wayland natively is in: https://github.com/brndnmtthws/conky/issues/56 ** Also affects: xwayland (Ubuntu) Importance: Undecided Status: New ** Changed in: xwayland (Ubuntu) Status: New => Confirmed ** Summary changed: - GNOME on Wayland does not initially display conky output + Conky does not initially display in Wayland sessions ** Bug watch added: github.com/brndnmtthws/conky/issues #56 https://github.com/brndnmtthws/conky/issues/56 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947185 Title: Conky does not initially display in Wayland sessions To manage notifications about this bug go to: https://bugs.launchpad.net/conky/+bug/1947185/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947185] Re: GNOME on Wayland does not initially display conky output
Weston is a compositor, and it is the reference compositor for Wayland. The problem you describe in Weston sounds to me like Conky is using X11 and complaining about the Xwayland layer it is communicating through. So this might be a bug in Xwayland or Conky. Either way it appears to already have a discussion open in https://github.com/brndnmtthws/conky/issues/1087 ** Bug watch added: github.com/brndnmtthws/conky/issues #1087 https://github.com/brndnmtthws/conky/issues/1087 ** Also affects: conky via https://github.com/brndnmtthws/conky/issues/1087 Importance: Unknown Status: Unknown ** Changed in: conky (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947185 Title: GNOME on Wayland does not initially display conky output To manage notifications about this bug go to: https://bugs.launchpad.net/conky/+bug/1947185/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947185] Re: GNOME on Wayland does not initially display conky output
Yesterday evening I upgraded my laptop to Ubuntu 20.10, so today I tried the same on my HP Elitebook 8460p laptop based on an i5-2520M and there conky displayed as I expected. Also I had no flickering of top-bar and Ubuntu dock with VMs or videos in full screen. By the way that flickering also occurs with Xorg in my Ryzen 3 2200G. Maybe we have to spit both issues in 2 bug reports? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947185 Title: GNOME on Wayland does not initially display conky output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/conky/+bug/1947185/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947185] Re: GNOME on Wayland does not initially display conky output
The Weston try out is irrelevant. In Weston Conky refuses to start and gives an error message about the display and it does it all the time. I use transparency and for that, conky requires a compositor, see the following text about that setting: own_window_argb_visual ARGB can be used for real transparency, note that a composite manager is required for real transparency. Weston does not have a compositor, so it does not run at all. I run Ubuntu 21.10 also in a Virtualbox VM since 5 months and there Conky displays normally. Everything is fine.The difference between both installations the Ryzen 3 2200G and the Virtualbox VM are the drivers from AMD or Virtualbox. I have another anomaly, which I did not report yet, when I display a VM or a video in full screen, the top bar and Ubuntu-dock of the Host (Ubuntu 20.10 flicker strongly through the full screen display of e.g. Ubuntu; Windows or videos. Fortunately it stops, when I left and right click with the mouse a few times. That issue is also new since 21.10 and it only happens on the Ryzen and not in a Virtualbox. In general I have issues with the display of stuff at the border of the screen. Both the Ubuntu-dock and Conky use transparency. Again the difference between both systems the Ryzen 3 2200G and the Virtualbox VM are the drivers from AMD or Virtualbox. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947185 Title: GNOME on Wayland does not initially display conky output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/conky/+bug/1947185/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947185] Re: GNOME on Wayland does not initially display conky output
You can try: sudo apt install weston and then log into Weston instead of GNOME. If it works in Weston then we have a GNOME bug, otherwise it is a Conky bug. ** Changed in: conky (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947185 Title: GNOME on Wayland does not initially display conky output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/conky/+bug/1947185/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947185] Re: GNOME on Wayland does not initially display conky output
I do not expect the error is in conky: 1. The error does not appear, when I login with xorg. The error did not appear in 21.04. 2. The conky window is of course somewhat outside of the standard application windows; It has no windows boundaries, the background of the window is transparent and it is in the bottom right corner. 3. The following bypass in the login script worked; #!/bin/bash sleep 2 conky -d sleep 1 killall conky sleep 1 conky -d The first time the windows is not displayed but conky is started, the second time conky is started and the display is perfect. For conky there is no difference between both starts, for wayland there is probably a difference. The sleep time has no influence, since I also tried the first one with 8 seconds and that did not help. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947185 Title: GNOME on Wayland does not initially display conky output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/conky/+bug/1947185/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
