f_ changed the topic of #wayback to: Wayback - a wayland-based X11 environment | https://wayback.freedesktop.org/ | src: https://gitlab.freedesktop.org/wayback/wayback | logs: https://libera.catirclogs.org/wayback | matrix bridge: #wayback:catircservices.org
<Wayback> @Conan_Kudo merged merge request: !70 xwayback: simplify argument parsing and main body (https://gitlab.freedesktop.org/wayback/wayback/-/merge_requests/70)
grufwub has quit [Remote host closed the connection]
grufwub has joined #wayback
_whitelogger has joined #wayback
_whitelogger has joined #wayback
jvvv has quit [Quit: WeeChat 4.6.3]
tsundoku- has joined #wayback
zdykstra has quit [Ping timeout: 276 seconds]
ToyKeeper has quit [Ping timeout: 248 seconds]
zdykstra has joined #wayback
ToyKeeper has joined #wayback
tsundoku has quit [Ping timeout: 276 seconds]
thomas_adam has quit [Ping timeout: 265 seconds]
thomas_adam has joined #wayback
<dramforever[m]1> <f_> Catherine, dramforever[m]1: does regular wlroots/TinyWL/wayland work on your hardware?
<dramforever[m]1> yes
<dramforever[m]1> it's just specifically kwin + xwayland that crashes
<dramforever[m]1> <Consolatis[m]1> https://gitlab.freedesktop.org/mesa/mesa/-/blob/main/src/gallium/frontends/dri/dri_drawable.c#L99 seems to check it though so not sure what is going on. Might already be fixed in master or something
<dramforever[m]1> wait really, that's it, just one nullptr check
<dramforever[m]1> looks like they're targeting mesa 25.2.x release
<dramforever[m]1> i suppose they could just backport it to 25.1.x
<dramforever[m]1> <whitequark[cis]> wait, do you have the same dell laptop as i do?
<dramforever[m]1> inspiron 7590 iirc
<dramforever[m]1> yup that fixes it
<dramforever[m]1> lol
__0x1eaf has joined #wayback
_whitelogger has joined #wayback
<f_> whitequark[cis]: your logger is going up and down lately, are you doing some maintenance?
* f_ didn't remember it going up/down this much
<whitequark[cis]> no
<f_> ah ok
<whitequark[cis]> it's restarted automatically whenever the connection drops or there are no messages for a while
<whitequark[cis]> maybe IRC is less active lately
<f_> maybe
jvvv has joined #wayback
<f_> Okay, so is wayback supposed to be Xserver-compatible or Xorg-compatible?
<f_> Because Xwayland supports everything Xserver(1) supports
<f_> (options-wise), but lacks some things Xorg(1) supports
<navi> Xorg
<navi> for example `vtXX` is a option Xorg supports that was crutial for my old X setup before i moved to wayland
jvvv has quit [Quit: WeeChat 4.6.3]
<f_> ok what I thoight
<f_> *thought
<f_> And also should we support the Xwayland-specific options?
<f_> or we should blacklist them and ignore them?
cow is now known as cow_
cow has joined #wayback
<Consolatis[m]1> there are some that might potentially be useful at some point, like the -hidpi one. Not sure though
<Consolatis[m]1> maybe its best to not use wayland output scaling at all and rely on Xorg for that
<f_> yeah the main goal is to be an Xserver replacement
<f_> so some unrelated things will have to go
<f_> (unrelated for an Xserver that is)
<navi> looking over Xwayland's options, -listenfd and -initfd might be useful for people writing their own init things around Xwayback, *maybe*
<navi> everything else seems... eh
<f_> ok
cow has quit [Quit: cow]
cow has joined #wayback
<whitequark[cis]> i'd want to play with -hidpi, it's possible there are some setups where it would work better
arraybolt3 has joined #wayback
<anabelae[m]> Is there any other place, where conversation is being held concerning this project, that should be followed to stay up to date. Excluding the git repo itself
<axtlos> its pretty much all here and on the git repo
<axtlos> ariadne posts updates on her fedi account sometimes, but you should be able to also gather those from git or here
Achill[m] has quit [Quit: Idle timeout reached: 172800s]
__0x1eaf has quit [Quit: Lost terminal]
<f_> anabelae[m]: and also the website, it will have updates regarding releases and such
<f_> but other than that that's pretty much it. There's no mailing list either
jvvv has joined #wayback
<Consolatis[m]1> I wonder if xrandr --setmonitor could maybe be used for making X11 aware of multiple outputs. https://superuser.com/questions/1183820/split-single-monitor-into-multiple-using-xrandr sounds like it but didn't do anything for me when testing (although on Xwayland 24.1.6)