<navi>
> If WAYLAND_SOCKET is set, it's interpreted as a file descriptor number referring to an already opened socket. In this case, the socket is used as-is and name is ignored.
<axtlos>
hm it still gets stuck
<navi>
any code i can look at?
<axtlos>
uhh i could send diffs for wayland-compositor and xwayback
<jvvv>
i was working on that yesterday using a pipe, was getting stuck just like axtlos said...
<jvvv>
i started adding print statements in Xwayland, it was getting stuck at a wl_display_roundtrip call... i gotta look at my stuff again to see where in Xwayland that was happening
arraybolt3 has joined #wayback
<jvvv>
found it. getting stuck at xserver/hw/xwayland/xwayland-screen.c: xwl_screen_roundtrip, just before the while loop; this called by xwl_screen_init.
<navi>
wait
<navi>
i may be a bit stupid
<navi>
duh
<navi>
it's `wl_client_create(display, socket)`
<navi>
not `wl_display_add_socket_fd`
<axtlos>
in the compositor?
<axtlos>
oh
<axtlos>
yeah
<navi>
yep
<navi>
axtlos: why is xwayback connecting to the server?
<navi>
the compositor*
<axtlos>
for xdg-output
<navi>
if that can't be avoided, we'll have to make two socketpairs, one for xwayback and one for xwayland
<navi>
> for xdg-output -- nothing seems to be reading the events?
<navi>
it's storing them in a struct alright
<axtlos>
i mean not only xdg-output, also wl-output
<axtlos>
to get the available outputs
<axtlos>
right now it only uses the first one, but that information will probably be required for Xinerama support
<navi>
"probably" -- wouldn't it be better to leave this code out until we're sure of what we need for Xinerama?
<axtlos>
uhhh
<axtlos>
i guess so
<navi>
anyway
<navi>
don't call close on wayback_session_socket either
<navi>
libwayland will do that when the wl_client is destroyed
<axtlos>
oh i thought i removed all close calls
<navi>
https://bpa.st/PEHA -- that's the diff i made to test, here i commented out the xdg_output code so i didn't need to make two socketpairs
<axtlos>
ok that works
<axtlos>
thanks
<axtlos>
oh also is there any significant difference between having set_cloexec in the compositor instead of xwayback
<navi>
if you set the cloexec flag before exec-ing wayback-compositor, it'll close the file descriptor, and wayback-compositor will not be able to use it
<axtlos>
oh ok
<axtlos>
navi: alright so xdg-output is actually needed right now
<axtlos>
i initially added it so that it can set the geometry for XWayland, I then mistakenly thought that XWayland was correctly detecting the resolution, but testing on real hardware showed that it doesn't
<axtlos>
so now we're back at setting the geometry from the commandline, for which xdg-output is needed
<navi>
i'll look at xwayland code tomorrow (ugh, pain) and see if there's anything we're missing that xwayland expects
<axtlos>
sounds good
<navi>
i'm kind of assuming that proper xinerama support would not involve Xwayback doing anything, since after both the compositor and xwayland are executed, there's nothing Xwayback can realistically send to Xwayland
<navi>
but i might be wrong, thus, will be checking
<axtlos>
i cant really comment on that, i honestly have no idea how we could implement xinerama
<navi>
it's gonna need some support from the Xwayland side
<navi>
but i don't know how much of that work is already done
<axtlos>
doesn't seem like there was any work done for that, i dont see any commits, merge requests or issues regarding xinerama on xwayland
<axtlos>
anyways im gonna go to bed now, its already way too late
<navi>
axtlos: for xwayback, you can do `wl_display_connect_fd` (or smth), instead of setting WAYLAND_SOCKET
<navi>
(WAYLAND_SOCKET is needed for Xwayland still tho)
<navi>
oh it's 4am here
<navi>
going to bed as well
<leah>
i checked devuan again. it was still open on my screen from yesterday. apparently they also do wayland
<leah>
which means, if they're merging xlibre, that they're willing enough to maintain two X implementations
<leah>
xwayland from xorg, and xlibre
<leah>
they didn't remove wayland
<leah>
their distro is still crap. it's always out of date. and i have no problem with systemd.
<leah>
interesting, someone here yesterday called them "reactionary". i',ve never heard that word applied to a linux distro, but i suppose it fits
<leah>
reactionary, in the context of new software. they respond by sticking to the old things
<leah>
their core premise though is quite noble. the idea of choice, and i respect their willingness to go to such maintenance efforts.
<leah>
i've looked at their distro before and it's quite elegant the way they handle it. e.g. most of their packages are redirects to debian packages and they only host what they modify
<leah>
but their vision is flawed
<leah>
they add choice of other init systems but also remove systemd. they should keep systemd as a choice.
<leah>
but i sympathise with the sentiment of "i don't like being forced to change", so i respect efforts such as theirs, even if some of the developers are a bit sus
<leah>
by the same token, i could probably de secribed as reactionary in my software choices, at times. on x11 for example. though there is a nuance in my case, because i recognise wayland's superiority, and would like to port lxde to it, rather than insist that xorg is better (itt isn't. x sucks)
<leah>
i also observe that many projects are revolutionary as opposed to evolutionary, in their development; i prefer the latter, in my own projects
<leah>
"move fast and break things" isn't my cup of tea. i like: "move fast to fix things"
<leah>
more technological conservativism is a good thing
<leah>
wayland is evolutionary
<leah>
and the fact that there isn't one solution, but many (compositors), that basically keeps everything in check because when the protocol changes, everyone has to be happy
<leah>
the bsd projects have another term for this: principle of least surprise
<leah>
i'm leah rowe of libreboot. the one you're thinking of is leah neukirchen
<leah>
mblaze looks like it might be useful to me, since i use a maildir-based mail server
<jvvv>
i think my lapap is using libreboot, or at least a modified version of
<jvvv>
mblaze is good
<leah>
it's even funnier when leah2 is in the same channel.
<leah>
someone pings her but uses tab complete and pings me instead
<leah>
she actuallyy registered "leah" first, when libera started; i was "leah" on freenode and she was leah2.
<leah>
when libera started, i asked leah2 very nicely if she would release the "leah" (without number) nick to me, which she kindly did
<leah>
so as to continue the old way from before
<jvvv>
oh, cool
<leah>
interesting. i wonder if other people make that same mistake too
<leah>
if someone had never heard of "leah rowe" but knew libreboot. went to #libreboot and saw "leah", but theyy had heard of leah neukirchen
<leah>
probably a non-issue, but even still
<leah>
perhaps the leahs on libera should usne surnames. so i'd be leahr and leah2 would be leahk
<leah>
to solve this problem
<jvvv>
i don't think it a big deal
<jvvv>
either way... sounds like she is good person, you are both part of good software projects i think, so if some confusion, it is not important
<jvvv>
that is my two cents, maybe worth only one
<jvvv>
ah, so my bios is not libreboot, but coreboot... i remembered wrong
<ToyKeeper>
One day when I was particularly frustrated with Poettering, I set up a new computer using Devuan instead of Debian. Nothing worked. It was all stuff I know how to fix, given the time, but ... distro-level work like that was my day job, and I didn't want to do it at home too. So I switched back to Debian and saved myself a ton of work.
<ToyKeeper>
I expected it to be like Debian-before-systemd, where most stuff would "just work" without fiddling. But it was not. They had removed systemd, but (at the time, at least) had not done the work to make things function without it.
<ToyKeeper>
Hopefully that has changed since then.
<ToyKeeper>
I liked oldschool init, but ultimately don't much care which init my system uses, as long as I don't *have* to care.
<ToyKeeper>
Some old tech still matters though, because it was a genuinely good idea which is worth keeping around. Like, network transparency. Almost every aspect of computing has become more and more network transparent, because it's just so dang useful.
<ToyKeeper>
... except for Wayland, which went in precisely the opposite direction.
<ToyKeeper>
And Mir, Canonical's Wayland clone.
<ToyKeeper>
I recall the sprint meeting when the Mir devs talked about their plan to drop Xorg from Ubuntu and use only Mir. Someone asked if it that meant it had support for tools like x2x now, and the Mir team were like "Nah, nobody uses that stuff anyway."
<f_>
07:42 <leah> but i sympathise with the sentiment of "i don't like being forced to change", so i respect efforts such as theirs, even if some of the developers are a bit sus
<ToyKeeper>
Immediately, about half the people in the room raised their hand. The meeting lead pointed at one. He said something like "Uh, I use that stuff daily. I *need* it to do my job. Is that why everyone else's hand is up?" *nods, all around the room*
<f_>
leah: debian literally supports non-systemd inits, making Devuan useless
<f_>
They could, instead of working on devuan, come to debian to maintain the init systems supported there...
<ToyKeeper>
... and then within a week or two, upper management announced they were no longer going to drop Xorg. And a few months later, they announced they were instead abandoning the Mir project and Unity and switching to Gnome.
<ari>
oh, cute, someone on signal just mistook me for ari-adne (put a dash in there to avoid highlighting)
<f_>
ari-adne :P
<f_>
Guess what happened earlier in the channel regarding to that :D
<f_>
19:05 ::: mode/#wayback [-o ari] by Ariadne
<f_>
19:05 ::: mode/#wayback [-o Ariadne] by Ariadne
<ari>
oh, missed that xD
<ToyKeeper>
Tab completion strikes again! :D
<f_>
yep
<leah>
honestly, we should just assign each irc user a uuid or something
<leah>
it would avoid a lot of naming confusion
seroquel has joined #wayback
<seroquel>
➜ sq pkg search wlroots
<seroquel>
wlroots015-0.15.1_5 Modular Wayland compositor library (deprecated 0.15.* series)
<seroquel>
wlroots017-0.17.4_2 Modular Wayland compositor library (deprecated 0.17.* series)
<seroquel>
wlroots018-0.18.2 Modular Wayland compositor library (current 0.18.* series)
<seroquel>
I'll have to see if I can get .19 added
<seroquel>
looks cool though
<axtlos>
huh what distro is that?
<seroquel>
FreeBSD
<axtlos>
wait whats sq then
<seroquel>
username
<axtlos>
ohh
<seroquel>
that prompt is confuzling sorry lol
<axtlos>
though if its freebsd then it already has wlroots 19
<axtlos>
ah its not in the quartely repo yet
<seroquel>
most people can't figure out how to wayland to work on freebsd at all I managed to but every time you hit control-c it tears down the whole window manager and server
<seroquel>
someone seemed to think it has something to do with sddm
<axtlos>
how are you starting wayland
<seroquel>
select it from sddm
<seroquel>
I haven't tried starting it from cmdline
<axtlos>
you should try that
<axtlos>
i always started it from the cmdline on freebsd, never had that issue
<seroquel>
yea I'll give that a shot in a bit I figured that'd be worth trying if nothing else did you ever figure out like what the deal is with discrete graphics does it just work ?
<axtlos>
yeah as long as you have drm-kmod and nvidia-kmod installed itll just work
<seroquel>
ok cool
<seroquel>
yeah it took me a while before I figured out kld_list="nvidia-modeset i915kms" need both of those for X or wayland to even start xD
<seroquel>
well the i915kms in particular
<seroquel>
I was kinda half expecting it to just load on its own but nah xD
<seroquel>
I gotta go clean my kithen up a bit and then crash for a few I will catch you guys a bit later
* seroquel
&
<f_|cis>
<leah> "honestly, we should just..." <- irc users do have uuids
<leah>
i was being joking
<f_>
the users you see with only numbers and letters, starting with a number - that's their user ID :P
<f_>
atheme services also assign a (separate) user id to you
<leah>
my uuid is leah
<f_>
no not that
<f_>
your nick is leah
<leah>
yes
<f_>
your uuid is something something 204AKD45F somethign like that
<f_>
When in a netsplit you can try changing nick to someone that has the same nick on the other side and then you'll be force-renamed to your uuid
<f_>
But generally UUIDs are otherwise not exposed to users
<f_>
they're mostly only for S2S stuff
<leah>
i am leah
<ToyKeeper>
you are leah
<ToyKeeper>
destroyer of worlds
<ToyKeeper>
creator of libreboot
<ToyKeeper>
provider of cookies
<ToyKeeper>
to all who hunger
<ToyKeeper>
and i hunger
<ToyKeeper>
plz give cookies
<leah>
i mean
<leah>
ok
<ToyKeeper>
... or tacos
<ToyKeeper>
omg tacos
<ToyKeeper>
nom
<leah>
i did wonder what happened to my cookies
<f_>
leah: I did give them to you
<f_>
did you lose them?
<leah>
yes, apparently i've been giving them away for free
<f_>
strange
<leah>
you lose track of details when you're omnipetent, as this person alleges i am
<leah>
btw. this isn't #librespeech
<leah>
i really don't want to keep spamming ariadne's project :P
<f_>
It isn't
<ToyKeeper>
Apologies. Will try to keep silly off-topic impulses to myself in the future.
<f_|cis>
no worries
fitrh has joined #wayback
fitrh has quit [Remote host closed the connection]
fitrh has joined #wayback
f_|ic has joined #wayback
fitrh has quit [Remote host closed the connection]
stacksize has joined #wayback
<stacksize>
how do i run it with a wm?
<axtlos>
just give wayback the wm command
<stacksize>
oh ty
<axtlos>
like `wayback i3`
<stacksize>
gotcha
<stacksize>
and what if i have a whole xinitrc script?
<stacksize>
how do i have all that stuff run
<axtlos>
i dont think that works currently
<axtlos>
youd have to make it a shell script and put it in PATH
<stacksize>
ahh
<stacksize>
ic
<axtlos>
but i'll be adding xinitrc support with the wayback-session split
<stacksize>
oh awesome
stacksize has quit [Quit: leaving]
stacksize has joined #wayback
<stacksize>
everything is super small
<stacksize>
like so small that i literally cant read it
<stacksize>
theres not enough pixels to distinguish characters
<stacksize>
wm is dwm
<axtlos>
youll have to set the right resolution through xrandr
<stacksize>
is this a known issue?
<stacksize>
oh
<stacksize>
ic
<axtlos>
yes i encountered that too with i3, but only on real hardware
<stacksize>
ik that multi monitor isnt supported rn so thats not a problem
<stacksize>
yes im on real hw
<stacksize>
okay ill brb
stacksize has quit [Client Quit]
stacksize has joined #wayback
<stacksize>
uh oh
<stacksize>
xrandr: cannot find mode 1280x1024
<stacksize>
shows up in list tho
<stacksize>
oh wait the display name is diff
<stacksize>
works now ty
<f_>
I think I had that issue with fvwm3
<f_>
the menus were tiny but the fvwm bar was okay I think
<axtlos>
for me the bar was also really slow
<stacksize>
is the XWAYLAND0 display name going to be replaced or will it always be like this?
<stacksize>
and multi monitor support is planned?
<axtlos>
multi monitor support is planned
<stacksize>
i have 2 monitors but my secondary one is on, is there any way i can prevent that?
<stacksize>
like would turning off my secondary monitor force it to go on the 1st one
<axtlos>
i think its a bit too early to say wether the display names will stay the same though
<f_>
oh now that I tried again yes everything is small
<axtlos>
no the monitor cant be turned off
<f_>
axtlos: my computer begs to differ ;)
<axtlos>
oh?
<f_>
but that's because it can't handle 3 displays at the same time.
<axtlos>
ah
<stacksize>
do i need to unplug the monitor or can i just power it off
<f_>
So one of them is off (the wrong one even!)
<axtlos>
its better to unplug, since the wayback compositor still uses the monitor so you can lose your cursor
<f_>
From what I can tell multimonitor is not even there at all, fvwm3 only shows up on the absolute wrong display (my laptop's display, in clamshell mode)
<f_>
but I'm sure it'll only improve :)
<stacksize>
if i turn off the monitor after i quit my wayland session, would that work
<axtlos>
yeah XWayland doesn't support multi monitor right now
<stacksize>
so it should only see the correct monitor?
<f_>
stacksize: What do you mean?
<f_>
You turn it off from wlr/xrandr?
<stacksize>
well everything is on the wrong monitor rn
<stacksize>
no i mean pressing power button on my monitor
<stacksize>
after i quit wayland session
<stacksize>
then starting again
<axtlos>
youd have to unplug it, turning it off will still have the connection there
<f_>
Ah don't think it'll work if your laptop still detects it as plugged in
<stacksize>
darn it
<axtlos>
like the cable connection
<stacksize>
im on desktop
<f_>
for example my hp v220 vga monitor, regardless of if it's off or not, will still show up as being there in `wlr-randr`
<stacksize>
would unplugging it from wall do it or do i need to disconnect from pc
<f_>
It depends
<axtlos>
disconnect it from the pc
<f_>
but I'd recommend disconnecting it from the PC
<f_>
that's much easier
stacksize has quit [Quit: leaving]
stacksize has joined #wayback
<stacksize>
works
<stacksize>
had to unplug from pc like you said
<stacksize>
now my problem is, my display supports 120hz, how can i enable that?
<axtlos>
the wayland compositor should default to that
<axtlos>
if xwayland isnt at 120hz then you probably have to set it through xrandr
<stacksize>
it only sees it as having 60hz when i do xrandr
<axtlos>
it may still be running at 120hz
<stacksize>
it isnt
<stacksize>
im confident of that
<stacksize>
it barely even looks like 60hz to me
<stacksize>
also are there any plans to fix screen lockers? i got "Xlib: extension DPMS missing on display :0."
<axtlos>
hm maybe the compositor isnt running at 120hz
<stacksize>
yeah i dont think it is
<axtlos>
uhh screen lockers worked for me
<axtlos>
at least the xfce one did
<axtlos>
though if the compositor isnt running at the right refresh rate then there isnt really anything you can do about it right now
<stacksize>
alright well atleast you know abt the problem, maybe you could look into it eventually
<stacksize>
screen locker that im trying to use is slock
<stacksize>
you can test it if you want, i assume youd have the same problem
<stacksize>
for some reason on my main display it assumed 1920x1080 but on my secondary monitor i needed to explicitly set it as 1280x1024
<axtlos>
do you mind opening an issue about the refresh rate?
<axtlos>
the screen resolution part already has one
f_|ic has quit [Quit: Connection closed for inactivity]
<stacksize>
i dont have a github account
stacksize has quit [Quit: leaving]
stacksize has joined #wayback
<stacksize>
im back
britney has quit [Quit: WeeChat 4.6.3]
britney has joined #wayback
user0thenyancat_ has joined #wayback
<user0thenyancat_>
hi :)
<f_>
hi
vyivel has joined #wayback
whitequark[cis] has quit [Quit: Idle timeout reached: 172800s]
<stacksize>
hello
<stacksize>
i dont have github, so how should i report the issue
<axtlos>
oh sorry i missed your messages previously, I'll open an issue for you
<ToyKeeper>
I hope dpms works, or will work eventually. I routinely use "xset dpms force off" as my screensaver, like on a notebook to turn the screen off while not in active use.
stacksize has quit [Ping timeout: 244 seconds]
<navi>
(i hope i'm not being too much / a problem, with those code reviews)
<axtlos>
oh lord no not at all!! they're actually super helpful