ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput
Brainium has quit [Quit: Konversation terminated!]
Brainium has joined #wayland
Brainium has quit [Quit: Konversation terminated!]
Brainium has joined #wayland
<orowith2os[m]>
gitlab seems to be down, but: xdg-decoration-v2 would be pretty nice.
iconoclasthero has joined #wayland
Brainium has quit [Quit: Konversation terminated!]
Brainium has joined #wayland
glennk has joined #wayland
Brainium has quit [Quit: Konversation terminated!]
Brainium has joined #wayland
linkmauve has left #wayland [Error from remote client]
naveenk2 has joined #wayland
Brainium has quit [Quit: Konversation terminated!]
Brainium has joined #wayland
garnacho has quit [Ping timeout: 480 seconds]
naveenk2 has quit [Ping timeout: 480 seconds]
nerdopolis has quit [Ping timeout: 480 seconds]
feaneron has quit [Ping timeout: 480 seconds]
naveenk2 has joined #wayland
Brainium has quit [Quit: Konversation terminated!]
naveenk2 has quit [Ping timeout: 480 seconds]
naveenk2 has joined #wayland
glennk has quit [Ping timeout: 480 seconds]
dcz_ has joined #wayland
naveenk2 has quit [Ping timeout: 480 seconds]
naveenk2 has joined #wayland
sima has joined #wayland
rasterman has joined #wayland
iconoclasthero_ has joined #wayland
alarumbe has quit [Quit: ZNC 1.8.2+deb3.1+deb12u1 - https://znc.in]
iconoclasthero has quit [Ping timeout: 480 seconds]
naveenk2 has quit [Ping timeout: 480 seconds]
coldfeet has joined #wayland
garnacho has joined #wayland
<pq>
naveenk2, your Weston log said: "Starting with no config file." So it doesn't find your config.
<naveenk2>
pq: I see this file in weston dir weston.ini.in where I have added [core] as color-management=true
<pq>
weston.ini.in is not weston.ini
<naveenk2>
hmm :(
<pq>
naveenk2, 'man weston.ini' explains how Weston searches for it, and the Weston log prints which file it actually found, or didn't.
<pq>
naveenk2, the *.in files in the git tree are templates that the build system should process.
<pq>
the processed files end up in the build directory frontend/weston.ini and ivi-shell/weston.ini
<naveenk2>
okay
<naveenk2>
Do I need to manually copy it to $HOME/.config/weston.ini
<pq>
if you want to use the examples, yes, or use the weston -c command line option.
<pq>
I'd recommend starting from an empty file, though, and add only what you need.
<naveenk2>
okay that make sense, I will add from empty file
<pq>
naveenk2, btw. weston-image can use embedded ICC profiles and forward those to the compositor.
vyivel has quit [Remote host closed the connection]
vyivel has joined #wayland
<naveenk2>
pq: what about client/color.c ? should it also work ?
<naveenk2>
I want to enahnce it for plane color maybe another client app kms_color.c
<naveenk2>
pq: why do I see a transparent window when launching weston-color client app?
<naveenk2>
'~/weston-color -w 640 -h 360 -R 1.0 -G 1.0 -B 1.0 -A 1.0 -p srgb -t pq -m 100.0 -M 400.0 -r 400.0' Do I need to be specific with these parameters, I was trying to play around with the values, but nothing seems to work
<naveenk2>
there failure in weston logs: [09:21:46.087] color-lcms error: failed to create a color transformation.
<naveenk2>
[09:21:46.087] Failed to create color transformation for a surface.
coldfeet has joined #wayland
coldfeet_ has joined #wayland
coldfeet_ has quit []
rasterman has quit [Quit: Gettin' stinky!]
<pq>
naveenk2, Weston does not implement parametric image descriptions yet. It's my WIP.
<pq>
you can only use ICC profiles for now
<pq>
hence the failure to create a color transformation