01:52 <DemiMarie> Is there any interest in merging the fix for the infinite loop in libwayland-server on overly-large messages?

06:46 <smith1727> hi all. i have no idea if this is the right place to ask, but this problem slices through a lot of layers. if i leave my fedora desktop with wayland on (to for example download and install Fedora 42), and turn my projector (and AV receiver) off, when i come back home and turn the projector (and AV receiver) on, there is no (i suppose dpms) signal and to get a picture i need to long-press the hardware power off button on my desktop's case, turn

06:46 <smith1727> it on again and only then does the projector receive the signal. i think i tried everything at this point, but i am hoping you guys can help me out. if i try playing around with the projector and AV receiver, turning them on and off, nothing helps --- it really is the desktop that is not _sending_ the signal, it seems.

07:01 <vyivel> smith1727: i'm assuming you use gnome, so report this to them

07:01 <smith1727> great idea, thanks a lot!

08:18 <wlb> weston/main: Marius Vlad * 9 commits https://gitlab.freedesktop.org/wayland/weston/compare/8e7ca3a47003e9489c34222850700ad4af4eb200...300d0590442b402b4de5db426f3aaf8f15b69e6e

08:18 <wlb> weston Merge request !1763 merged \o/ (weston_surface_damage() does it wrong https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/1763)

08:27 <MrCooper> smith1727: sounds like a kernel issue, mutter turns on all connected displays in response to any input

08:42 <smith1727> MrCooper, thanks for letting me know about mutter. btw, someone solved this by install xscreensaver (?), i tried it to see.

08:44 <MrCooper> that can't really make a difference with GNOME (not even with Xorg, let alone Wayland)

08:45 <smith1727> gotcha. maybe fedora is slow in updating the kernel. i'll try the newest and see if that helps

08:45 <smith1727> i have 6.13.something

09:01 <Ermine> fedora in front of me has 6.14.x fwiw

09:07 <smith1727> MrCooper, updated to kernel 6.14.8. waking the display up from a locked screen works, but i think it also did previously.

09:07 <smith1727> perhaps gnome does some deeper sleep/hibernate thing?

09:10 <smith1727> aaaah, i see, there is suspend.

09:10 <smith1727> but yeah, when i do it from the menu, i can wake it up (not by mouse, but by keypress on the keyboard)

09:10 <smith1727> could it be that some automatic suspend raises the issue?

14:08 <wlb> weston Merge request !1764 opened by Derek Foreman (derekf) Remove weston_view_damage_below https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/1764 [Core compositor], [libweston API]