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
columbarius has joined #wayland
co1umbarius has quit [Ping timeout: 480 seconds]
AJ_Z0 has joined #wayland
nerdopolis has quit [Ping timeout: 480 seconds]
nerdopolis has joined #wayland
Arnavion has quit [Ping timeout: 480 seconds]
Arnavion has joined #wayland
<pounce>
qq: if a wayland client is halfway between a hiDPI output and low DPI output, what is the intended behaviour of when the client is halfway between both outputs?
<pounce>
i presume it is sent an `enter` event for the hidpi output, where it is rendered at native resolution, and the compositor has the responsibility of downscaling it on the other moutput?
<pounce>
/s/moutput/output/
fmuellner has quit [Ping timeout: 480 seconds]
<danieldg>
pounce: correct
<danieldg>
the client may get enter events for both outputs, and take max(scale_factors)
<danieldg>
and any client can send a buffer at any scale; the compositor has to handle that anyway
Company has quit [Quit: Leaving]
mclasen has quit [Ping timeout: 480 seconds]
nerdopolis has quit [Ping timeout: 480 seconds]
adarshgm has joined #wayland
zebrag has quit [Quit: Konversation terminated!]
emery has quit [Remote host closed the connection]
emery has joined #wayland
slattann has joined #wayland
dcz has joined #wayland
caveman has joined #wayland
moses has quit [Read error: Connection reset by peer]
elibrokeit has quit [Read error: Connection reset by peer]
moses has joined #wayland
milesrout has quit [Read error: Connection reset by peer]
kennylevinsen has quit [Read error: Connection reset by peer]
staceee has quit [Read error: Connection reset by peer]
elibrokeit has joined #wayland
WhyNotHugo has quit [Read error: Connection reset by peer]
c7s has quit [Read error: Connection reset by peer]
ifreund has quit [Read error: Connection reset by peer]
txtsd has quit [Read error: Connection reset by peer]
milesrout has joined #wayland
kennylevinsen has joined #wayland
staceee has joined #wayland
WhyNotHugo has joined #wayland
txtsd has joined #wayland
c7s has joined #wayland
ifreund has joined #wayland
tzimmermann has joined #wayland
slattann has left #wayland [#wayland]
slattann has joined #wayland
<slattann>
Test Msg
flyingketh[m] has quit []
cool110 has joined #wayland
cool110 has quit [Remote host closed the connection]
cool110 has joined #wayland
<wb9688>
Test successful
cool110_ has quit [Ping timeout: 480 seconds]
floof58 has quit [Ping timeout: 480 seconds]
jgrulich has joined #wayland
fahien has joined #wayland
rasterman has joined #wayland
bittin has quit [Remote host closed the connection]
<pq>
emersion, I think the lack of proper API with full details (up to what GBM has nowadays) is the main reason. So yeah, lack of control, and maybe also lack of queries to find out what you actually got.
<emersion>
oh, we don't even get the modifier?
<emersion>
ah, no, we do get that
<pq>
but then again, the Unix Device Memory Allocator project is all about "just" API, so API is kinda the most important part
<emersion>
so we "just" have no control over allocation, so proper negotiation is impossible
<pq>
yup
MajorBiscuit has joined #wayland
<pq>
IMO that's reason enough to avoid it, it's a lottery
<pq>
also there is probably fun with hardware that cannot texture from and render to the same formats directly
<pq>
(the driver does a resolve or blit internally when necessary, or something)
<pq>
(maybe even with a separate hardware block)
mbalmer has joined #wayland
<daniels>
yeah, and also that you may very well have internal formats which can't be described by a modifier, so export implies reallocation, or that you can create EGLImages from very exotic sources which aren't supported for interchange
slattann has quit [Quit: Leaving.]
caveman has quit [Ping timeout: 480 seconds]
slattann has joined #wayland
manuel1985 has joined #wayland
mbalmer has quit []
fahien has quit [Ping timeout: 480 seconds]
fahien has joined #wayland
mclasen has joined #wayland
rgallaispou has joined #wayland
manuel1985 has quit [Ping timeout: 480 seconds]
fmuellner has joined #wayland
MajorBiscuit has quit [Quit: WeeChat 3.5]
MajorBiscuit has joined #wayland
rgallaispou1 has joined #wayland
rgallaispou has quit [Ping timeout: 480 seconds]
adarshgm has quit [Ping timeout: 480 seconds]
slattann has quit [Read error: Connection reset by peer]
mclasen_ has joined #wayland
Company has joined #wayland
mclasen has quit [Ping timeout: 480 seconds]
fahien has quit [Ping timeout: 480 seconds]
slattann has joined #wayland
nerdopolis has joined #wayland
floof58 has joined #wayland
mvlad has joined #wayland
mbalmer has joined #wayland
adarshgm has joined #wayland
fahien has joined #wayland
adarshgm has quit [Ping timeout: 480 seconds]
rasterman has quit [Quit: Gettin' stinky!]
bodiccea has quit [Remote host closed the connection]
bodiccea has joined #wayland
bodiccea has quit [Quit: Leaving]
bodiccea has joined #wayland
jgrulich_ has joined #wayland
jgrulich_ has quit [Remote host closed the connection]
jgrulich has quit [Ping timeout: 480 seconds]
jgrulich has joined #wayland
manuel1985 has joined #wayland
mclasen_ has quit [Ping timeout: 480 seconds]
manuel1985 has quit [Ping timeout: 480 seconds]
jgrulich has quit [Remote host closed the connection]
rv1sr has joined #wayland
rv1sr has quit []
ofourdan has quit [Ping timeout: 480 seconds]
zebrag has joined #wayland
slattann has quit []
ybogdano has joined #wayland
tzimmermann has quit [Quit: Leaving]
mclasen has joined #wayland
<zebrag>
Hi, I'm trying to have wayland running, maybe you can spot something obvious I've missed: https://paste.debian.net/1247105/
<zebrag>
every suggestions I've googled so far not concerned plain intel hd graphics
MajorBiscuit has quit [Read error: No route to host]
ppascher has quit [Ping timeout: 480 seconds]
<mvlad>
zebrag, looks like you do not have the i915 driver loaded? Do you have anything under /dev/dri?
<zebrag>
hi
<zebrag>
ls /dev/dri
<zebrag>
by-path card0 renderD128
<mvlad>
oh, probably there's something else has drm master for the device. (X for instance).
<zebrag>
But yes, it seems I have no "drm" at all, I was counting on modesetting, Also I've installed xserver-xorg-video-intel
<zebrag>
"has drm master for the device"?
<mvlad>
another application/compositor has opened the device.
<zebrag>
okay, like sddm holding the resource?
<kennylevinsen>
zebrag: xserver-xorg-video-intel is an old-style xorg driver thing. All you need is mesa.
<kennylevinsen>
The relevant error is the logind one
<zebrag>
kennylevinsen: right, but how do I do that?
<kennylevinsen>
How did you try to launch the compositor? Over ssh? Systemd unit? Try going to an empty VT/tty and start the compositor directly from there.
<zebrag>
through sddm
<kennylevinsen>
yeah go run it from a tty and see if that works
<zebrag>
I've also tried `startplasma-wayland` from ssh
<zebrag>
okay trying tty
<kennylevinsen>
(systemd-logind wont let you start stuff over ssh without tinkering around first)
<zebrag>
okay, trying from tty gives the exact same error as in the above paste "maybe another compositor is running"...
<zebrag>
maybe I should kill sddm?
<zebrag>
how do I do that?
<mvlad>
pkill sddm/killall sddm, over ssh.
<mvlad>
or maybe you have a systemd unit...?
<zebrag>
yes, systemd unit
<zebrag>
`systemctl stop display-manager`?
<zebrag>
so that stopped sddm, and I've tried restarting startplasma-wayland from tty, and I get same error, with possibly additional "could not determine $DISPLAY"
cabal704 has joined #wayland
<zebrag>
kennylevinsen: about the mesa stuff, it there something I should install to have it?
<mvlad>
unlikely, the KDE compositor would have depends on it.
<zebrag>
yes, that would be libegl1 and it's been installed
<zebrag>
d... any idea what I could try?
<mvlad>
apart from making sure nothing else is actually opened the DRI node, no. The DISPLAY message is odd, it looks like it wants to talk to the X server rather than to start the wayland compositor.
<mvlad>
(not familiar with the KDE compositor)
<zebrag>
mvlad: I could try with another compositor available from debian?
<mvlad>
I'm using pretty often weston, but I also try out things with gnome-shell. I launch it from a tty like the following gnome-shell --display-server --wayland
<zebrag>
with weston touch screen is working out of the box, wacom pen/digitizer is not activated though (it was activated in sddm, but sddm is using x11, I think)
<xaltsc>
Hey, are there reasons for the object ids to change during a session, or can I assume that they always stay the same ?
<emersion>
object IDs are re-used aggressively
<emersion>
so, if object ID 42 represents a wl_seat which is destroyed, it may be re-used for a completely unrelated object, say a wl_buffer
<xaltsc>
emersion: What kind of data can I use then to keep track of an object ? The c pointer ?
<emersion>
the C pointer isn't enough: when the object is destroyed by the client, malloc(3) may re-use that chunk of memory later on
<emersion>
can you explain what's your goal here?
<xaltsc>
emersion: I'm trying to track data in a map, and I need to find a way to assign a WlSomething object to the object used to track its data.
<emersion>
what kind of program are you writing?
<emersion>
what's your high-level goal?
<emersion>
write a new library to speak the wayland wire protocol instead of using libwayland?
<xaltsc>
I'm trying to make a tool to expose the status of my compositor
<emersion>
so, you're writing a wayland client, correct?
<emersion>
and you use the rust wayland library
<emersion>
so why do you need to "track objects"?
<emersion>
each protocol has its own lifetime rules for objects
<emersion>
some objects are created by the client and destroyed by the client
<emersion>
some objects are created by the client and destroyed by the server
<emersion>
etc
<xaltsc>
emersion: Because I can't request the data given by the events after they've been sent
<emersion>
the protocol spec describes this
<xaltsc>
emersion: what does the protocol describe ?
<emersion>
sorry, i don't understand the problem you're trying to solve
<xaltsc>
For instance, let's say I'm trying to gather all the data about an output with the Events. How can I figure out that the Name, Scale, Geometry, etc, events pertain to the same output ?
slattann has quit [Read error: Connection reset by peer]
fmuellner has quit []
fmuellner has joined #wayland
fahien has quit []
<any1>
Are you trying to build a tool like wlhax?
fmuellner has quit []
pnowack has joined #wayland
fmuellner has joined #wayland
pnowack has quit []
fmuellner has quit []
fmuellner has joined #wayland
fmuellner has quit []
fmuellner has joined #wayland
fmuellner has quit []
fmuellner has joined #wayland
fmuellner has quit [Ping timeout: 480 seconds]
<zebrag>
mvlad: `aptitude -R install mesa-utils` then `gnome-shell --display-server --wayland` in a tty. Works right out of the box. Even wacom digitizer is working perfectly.
ybogdano has quit [Read error: Connection reset by peer]
ybogdano has joined #wayland
rasterman has quit [Quit: Gettin' stinky!]
dcz has quit [Ping timeout: 480 seconds]
fmuellner has joined #wayland
manuel1985 has joined #wayland
mvlad has quit [Ping timeout: 480 seconds]
mbalmer has quit []
spstarr has joined #wayland
manuel1985 has quit [Ping timeout: 480 seconds]
ybogdano is now known as Guest4935
ybogdano has joined #wayland
<kennylevinsen>
xaltsc: your tool looks like a regular wayland client. For e.g. wl_output, the registry advertises them and you bind them. You get an ID when you bind it, and it will remain valid until you release it.
Guest4935 has quit [Ping timeout: 480 seconds]
<kennylevinsen>
the geometry and name events will be sent on your object id, tying everything together
<kennylevinsen>
You can think of them somewhat like a C heap pointer - it's pretty random, but is valid until you free(3) it.
jmdaemon has joined #wayland
spstarr has quit [Remote host closed the connection]
rv1sr has joined #wayland
ybogdano has quit [Ping timeout: 480 seconds]
rv1sr has quit []
fmuellner has quit []
fmuellner has joined #wayland
fmuellner has quit []
fmuellner has joined #wayland
fmuellner has quit []
fmuellner has joined #wayland
fmuellner has quit []
fmuellner has joined #wayland
fmuellner has quit []
fmuellner has joined #wayland
fmuellner has quit []
fmuellner has joined #wayland
fmuellner has quit []
fmuellner has joined #wayland
fmuellner has quit []
fmuellner has joined #wayland
fmuellner has quit []
fmuellner has joined #wayland
The_Company has joined #wayland
fmuellner has quit []
fmuellner has joined #wayland
Company has quit [Ping timeout: 480 seconds]
ybogdano has joined #wayland
fmuellner has quit []
fmuellner has joined #wayland
fmuellner has quit [Remote host closed the connection]
fmuellner has joined #wayland
fmuellner has quit [Remote host closed the connection]
fmuellner has joined #wayland
fmuellner has quit []
fmuellner has joined #wayland
floof58 has quit [Ping timeout: 480 seconds]
floof58 has joined #wayland
<zebrag>
I do have wacom digitizer working out of the box with gnome-shell, but not with weston. What can I do to fix that?