ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput | register your nick to speak
danvet has quit [Ping timeout: 480 seconds]
Lucretia has quit []
columbarius has joined #wayland
co1umbarius has quit [Ping timeout: 480 seconds]
fmuellner has quit [Ping timeout: 480 seconds]
hendursaga has quit [Remote host closed the connection]
hendursaga has joined #wayland
boistordu has quit [Ping timeout: 480 seconds]
aswar002 has quit [Quit: No Ping reply in 180 seconds.]
aswar002 has joined #wayland
Sachiel has quit [Quit: WeeChat 3.2]
Sachiel has joined #wayland
shashank1202_ has joined #wayland
zebrag has quit [Quit: Konversation terminated!]
pnowack has joined #wayland
rpigott has quit [Read error: Connection reset by peer]
rpigott has joined #wayland
Dami has joined #wayland
hardening has joined #wayland
danvet has joined #wayland
leon-p has quit [Quit: leon-p]
shashank1202_ has quit [Quit: Connection closed for inactivity]
<DemiMarieObenour[m]>
Does Weston have any protection against trivial denial of service attacks?
<emersion>
no
___nick___ has joined #wayland
___nick___ has quit []
___nick___ has joined #wayland
ryoshu has joined #wayland
hardening_ has joined #wayland
tzimmermann has quit [Quit: Leaving]
hardening has quit [Ping timeout: 480 seconds]
st3r4g has joined #wayland
danvet has quit [Ping timeout: 480 seconds]
___nick___ has quit [Ping timeout: 480 seconds]
ppascher has quit [Ping timeout: 480 seconds]
danvet has joined #wayland
rasterman has quit [Quit: Gettin' stinky!]
dcz_ has quit [Ping timeout: 480 seconds]
pnowack has quit [Quit: pnowack]
fmuellner has joined #wayland
novakane has quit [Quit: WeeChat 3.3]
danvet has quit [Ping timeout: 480 seconds]
zebrag has quit [Ping timeout: 480 seconds]
zebrag has joined #wayland
<zebrag>
Possible misunderstanding about screen energy saving. The PC sends a message to the monitor to power off. The monitor, say it's broken, turns back on, after two hours. The PC is just unaware of that. But why then, the second unrelated monitor turns back on too?
<zebrag>
I've had a problem of monitor randomly turning back on, sometimes never, sometimes often, for sth like 4 years, and I'm thinking I have no clue what component the issue should be attributed to.
<zebrag>
I would think the first step should be to monitor when, if not why, the screens turn back on.
| has quit [Read error: Connection reset by peer]
| has joined #wayland
kennylevinsen has quit [Remote host closed the connection]
kennylevinsen has joined #wayland
leon-p_ has joined #wayland
leon-p has quit [Ping timeout: 480 seconds]
<DemiMarieObenour[m]>
What heuristics is Wine on Wayland using?
<kennylevinsen>
wine wayland support is not upstream - it's "stuck" in a collabora fork of wine if I'm not mistaken
<kennylevinsen>
but the general idea is that things like windows and X11 just allows you to do whatever, including using regular windows for popups/context menus/whatever by just positioning them absolute where you want them, without there necessarily being a proper relationship between the windows