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
<wlb>
weston/main: Pekka Paalanen * color: simplify color manager API with weston_output_color_outcome https://gitlab.freedesktop.org/wayland/weston/commit/dfba19abde95 include/libweston/libweston.h libweston/color-lcms/color-lcms.c libweston/color-noop.c libweston/color.h libweston/compositor.c
jmabr has quit [Remote host closed the connection]
sychill has quit [Ping timeout: 480 seconds]
jmabr has joined #wayland
sychill has joined #wayland
jmabr has quit [Remote host closed the connection]
sychill has quit []
Company has joined #wayland
sychill has joined #wayland
Moprius has joined #wayland
<pq>
interesting behavior on my HDR monitor... if maximum display mastering luminance is set to 100 nits or lower, the picture is weird brightness capped image.
<pq>
if it's 101 or greater, it's "HDR" image
<pq>
when maxDML=100 and I also add minDML=0.0001, the weirdness disappear and it look like a normal dark image
<pq>
oh well
duxco has joined #wayland
ppascher has joined #wayland
duxsco has quit [Ping timeout: 480 seconds]
<kennylevinsen>
I wonder when you'll be frustrated enough with monitors that you start to make your own reference designs
<emersion>
unfortunately the "PQ" brand is already taken by LG
<emersion>
also this is an unambitious project compared to daniels'
rgallaispou1 has quit [Read error: Connection reset by peer]
rgallaispou has quit [Ping timeout: 480 seconds]
rgallaispou has joined #wayland
jmabr has quit [Remote host closed the connection]
devilhorns has joined #wayland
jmabr has joined #wayland
tzimmermann has quit [Quit: Leaving]
jgrulich has quit [Remote host closed the connection]
Diablo-D3 has joined #wayland
<Diablo-D3>
hey all
<Diablo-D3>
is there an environment variable or dotfile that I can set to change desktop dpi?
<daniels>
Diablo-D3: not as such, no - whichever compositor / desktop environment you're using will let you configure a per-output scale factor
<Diablo-D3>
its specifically weston
<Diablo-D3>
I know I can do it in weston.ini, but in this case I dont have control over it
lxsameer has quit [Ping timeout: 480 seconds]
___nick___ has quit []
___nick___ has joined #wayland
___nick___ has quit []
<daniels>
yeah, in that case ~/.config/weston.ini is that exact dotfile ...
<Diablo-D3>
yeah, this is the weird corner case of wslg
<Diablo-D3>
the user running weston isnt mine, and its not in a vm that I can screw with
___nick___ has joined #wayland
duxco has quit [Quit: Leaving]
duxsco has joined #wayland
bigeye has joined #wayland
maxzor has quit [Ping timeout: 480 seconds]
<ManMower>
doesn't WSLg take dpi from windows settings? or you want to override it just for WSLg and not for windows apps?
<ManMower>
I think to change desktop dpi in WSLg you'd still need to have that environment variable set before weston launches in the system distro... I don't think there is such an env var even there though.
<ManMower>
oh, there is. WESTON_RDP_DEBUG_DESKTOP_SCALING_FACTOR
<ManMower>
and if you really need to override, you may find yourself needing to build your own system distro https://github.com/microsoft/wslg/blob/main/CONTRIBUTING.md with changes to wslgd which launches weston. might be a bit of trouble...
<Diablo-D3>
ManMower: no
<Diablo-D3>
scaling factor doesnt work that way, its used for the RDP client side to software scale
<Diablo-D3>
you have to set WESTON_RDP_DISABLE_HI_DPI_SCALING=true
<Diablo-D3>
to turn off RDP-side scaling, but then it lacks any way of changing weston's own dpi
<ManMower>
oh, ok
<Diablo-D3>
yeah, they kind of shot themselves in the foot
<ManMower>
I'm kind of not understanding the problem case... like, weston's own DPI should be accurate and based on the monitor configuration. what's the footgun?
<Diablo-D3>
wslg never sets it
<Diablo-D3>
like, it never actually informs weston of the dpi
<Diablo-D3>
so, for example, my laptop is 200%, I get two choices, either I have weston at 100% and it scales the RDP client to 200%, or I get weston at 100% and it doesnt scale
<Diablo-D3>
at no point do I get weston at 200%
<ManMower>
hrm, I think maybe you should file an issue against WSLg in github
<Diablo-D3>
its a known issue, but its also microsoft
<Diablo-D3>
might get a fix next year =/
<ManMower>
is there an issue for it in their system already?
<Diablo-D3>
yes
<Diablo-D3>
is there any way to tell weston after its started to change the dpi?
<ManMower>
no. but there's a way (as pasted above) to build your own wslg containers, and that would let you edit weston.ini
<Diablo-D3>
yeah, Im trying to avoid that
<ManMower>
sadly, I think that's the best I've got
nurupo has quit [Quit: nurupo.ga]
nurupo has joined #wayland
jmdaemon has joined #wayland
<Diablo-D3>
good old microsoft, snatching defeat from the jaws of victory, oh well
<Diablo-D3>
thanks for trying
Diablo-D3 has left #wayland [#wayland]
duxsco has quit [Quit: Leaving]
<daniels>
software? imperfect? :o
slattann has joined #wayland
<slattann>
Test Mesg
Azem has quit [Read error: Connection reset by peer]
<ManMower>
that's only the second most surprising merge request of the week. :)
rgallaispou1 has joined #wayland
hergertme has quit [Remote host closed the connection]
hergertme has joined #wayland
rgallaispou has quit [Ping timeout: 480 seconds]
jmabr has quit [Quit: Leaving]
rgallaispou1 has quit [Read error: Connection reset by peer]
rgallaispou has joined #wayland
<daniels>
ManMower: the random MIME is alas unsurprising
<ManMower>
is that a new spam thing? :(
duxsco has quit [Quit: duxsco]
<ManMower>
is there some webapp or something that normally has a file at that location?
duxsco has joined #wayland
lxsameer has joined #wayland
mvlad has quit [Remote host closed the connection]
duxsco has quit [Remote host closed the connection]
duxsco has joined #wayland
jmabr has joined #wayland
sychill has quit [Ping timeout: 480 seconds]
dcz_ has quit [Ping timeout: 480 seconds]
sychill has joined #wayland
duxco has joined #wayland
duxsco has quit [Ping timeout: 480 seconds]
jmabr has quit [Quit: Leaving]
rasterman has quit [Quit: Gettin' stinky!]
danvet has quit [Ping timeout: 480 seconds]
lxsameer has quit [Ping timeout: 480 seconds]
duxco has quit [Quit: Leaving]
duxsco has joined #wayland
rv1sr has quit []
hardening has quit [Ping timeout: 480 seconds]
<daniels>
no, it’s just that we’re one of the first search hits for GitLab with open registration, and people fork and upload changes with random files from their disk
<daniels>
we had that with Bugzilla where registering with us and filing nonsense sandbox bugs was a part of the course too
<daniels>
open-registration services: not even once
ppascher has quit [Ping timeout: 480 seconds]
cool110 has quit [Remote host closed the connection]