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
caveman has quit [Remote host closed the connection]
anarsoul has quit [Ping timeout: 480 seconds]
caveman has joined #wayland
peeterm has quit [Server closed connection]
peeterm has joined #wayland
jmabr_ has quit [Remote host closed the connection]
sstiller has joined #wayland
al has quit [Server closed connection]
al has joined #wayland
anarsoul has joined #wayland
vindicator has joined #wayland
devilhorns has joined #wayland
caveman has quit [Ping timeout: 480 seconds]
duxsco has quit [Quit: duxsco]
Company has joined #wayland
duxsco has joined #wayland
<vindicator>
Welp, looks like the debugging is going to be a bit more involved as I'm no particularly familiar with how function typedefs work ("typedef char *(EGLAPIENTRYP PFNEGLGETDISPLAYDRIVERCONFIGPROC) (EGLDisplay dpy);" or "EGLAPI EGLBoolean EGLAPIENTRY eglInitialize (EGLDisplay dpy, EGLint *major, EGLint *minor);")
caveman has joined #wayland
<vindicator>
From what I can tell is that those are all essentially stubs that get implemented elsewhere. Anyone know where I'd find the eglInitialize implementation? I presume it'd be something by Intel (my haswell IGP).
<mvlad>
vindicator, that's in mesa. You can tweak mesa to print things to stderr as well. https://docs.mesa3d.org/envvars.html, see MESA_DEBUG. If it's not off should print some init failure messages.
emersion has quit [Server closed connection]
emersion has joined #wayland
<daniels>
vindicator: if you're trying to debug eglinfo not loading GBM, I would just leave it alone
<daniels>
normal user programs are not expected to be able to work with GBM
<daniels>
they don't need to in any case - KWin is the only thing which needs to handle GBM - if it couldn't then it can't start
<daniels>
if you have another more specific issue then you'll need to debug something else
<vindicator>
I just wanted to make sure I was getting away from x11 as much as I could. I know KDE has a wrapper and figured when the time comes that x11 is fully dropped, that my system isn't going to be left in the dust if I could. Are you sure KDE wouldn't start even if it has a wrapper to fall back on?
<vindicator>
*x11 wrapper
<daniels>
that only starts if you have an existing running X11 server
<daniels>
and Weston doesn't have that at all, so when you have Weston starting and happily reporting EGL functionality using your Intel driver, then you're definitely fine
GentooPhysicist393 has quit [Server closed connection]
GentooPhysicist393 has joined #wayland
<vindicator>
Running eglgears_wayland gives me a segfault
<vindicator>
"libEGL debug" shows not finding "optional" stuff, so that doesn't seem to be the cause, but later it also spits out 6 instances of "No DRI config supports native format <specificFormats>"
<mvlad>
vindicator, it only has wl-shell support and it crashes in some other parts. Looking for adding support for xdg-shell, will post something a bit later.
<vindicator>
I had just saw that github issue. Going to see what "wl-shell" is all about (presuming "wayland shell")
<daniels>
weston-simple-egl
<vindicator>
yup, that works.
<vindicator>
oooo, I like the "smoke"
cmeissl[m] has quit [Server closed connection]
<mvlad>
ah, there's already a MR for it.... somehow got abandoned.
cmeissl[m] has joined #wayland
<vindicator>
I was playing with the "stacking" program and it was the first time I encountered "transient". It's interesting how it functions. I'd say it was something like a "modal" window, but only to it's parent. And not even really "modal" since you can still interact with the parent. It's just a higher visual layer that doesn't change.
<vindicator>
The "transformed" program brought up something, did nothing, then segfault.
ecloud has quit [Ping timeout: 480 seconds]
ecloud has joined #wayland
davidre has quit [Server closed connection]
davidre has joined #wayland
Guest389 has quit [Server closed connection]
dreda has joined #wayland
dreda is now known as Guest670
Shimmy0 has quit [Server closed connection]
Shimmy0 has joined #wayland
vindicator has left #wayland [#wayland]
erc has joined #wayland
Hypfer has quit [Server closed connection]
Hypfer has joined #wayland
wolfshappen has quit [Server closed connection]
wolfshappen has joined #wayland
floof58_ has joined #wayland
floof58 has quit [Ping timeout: 480 seconds]
floof58_ is now known as floof58
<macc24>
in kiosk shell, if i have a program running on internal display, and i plug in second monitor via displayport or hdmi, what would happen?