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
danvet has quit [Ping timeout: 480 seconds]
rv1sr has quit []
columbarius has joined #wayland
co1umbarius has quit [Ping timeout: 480 seconds]
Brainium has quit [Quit: Konversation terminated!]
<hays> hey all what could be causing SDL init to fail due to no video device
fmuellner has joined #wayland
<bl4ckb0ne> thats probably a SDL issue, but it looks like it fails to init the wayland video driver for whatever reason
<soreau> maybe WAYLAND_DISPLAY isn't set or something
<bl4ckb0ne> yeah my bet is on failure to get the display
co1umbarius has joined #wayland
columbarius has quit [Read error: Connection reset by peer]
<hays> wayland_display is set
<hays> wayland-1
<soreau> is XDG_RUNTIME_DIR also set?
<hays> to /var/run
<soreau> did you check the WAYLAND_DEBUG output?
<hays> how woudl i do that
<bl4ckb0ne> WAYLAND_DEBUG=1 when launching your bin
<hays> no additional output
<hays> for what its worth, mpv also does same thing.. sdl init fails
<soreau> this probably means it's trying to use x11 path
<hays> x11 is not installed
<hays> this is from console
<soreau> did you build sdl yourself? maybe it's missing wayland support
<hays> --enable-video-wayland
<hays> its compiled with wayland support. looking at log now
nerdopolis has quit [Ping timeout: 480 seconds]
fmuellner has quit [Ping timeout: 480 seconds]
alarumbe has joined #wayland
alarumbe has quit []
alarumbe has joined #wayland
alarumbe has quit []
alarumbe has joined #wayland
Company has quit [Quit: Leaving]
alarumbe has quit [Quit: ZNC 1.8.2+deb2 - https://znc.in]
dadwadw has joined #wayland
dcz_ has joined #wayland
frytaped has joined #wayland
radu24284303951534727071489559 has quit [Ping timeout: 480 seconds]
dadwadw has quit []
molinari has joined #wayland
kts has joined #wayland
molinari has quit [Ping timeout: 480 seconds]
danvet has joined #wayland
molinari has joined #wayland
rv1sr has joined #wayland
lockywolf has quit []
molinari has quit [Ping timeout: 480 seconds]
frytaped has quit [Quit: WeeChat 3.6]
lockywolf has joined #wayland
molinari has joined #wayland
molinari has quit [Ping timeout: 480 seconds]
MajorBiscuit has joined #wayland
sav10 has joined #wayland
sav10 has quit [Remote host closed the connection]
sav10_ has joined #wayland
rasterman has joined #wayland
floof58 is now known as Guest705
floof58 has joined #wayland
Guest705 has quit [Ping timeout: 480 seconds]
MajorBiscuit has quit [Quit: WeeChat 3.6]
sav10_ has quit [Remote host closed the connection]
kts has quit [Quit: Leaving]
DragoonAethis has quit [Quit: hej-hej!]
fmuellner has joined #wayland
DragoonAethis has joined #wayland
smallville7123 has quit [Quit: Konversation terminated!]
smallville7123 has joined #wayland
nerdopolis has joined #wayland
TheDisruptiveCollective|JoinOu has joined #wayland
fmuellner has quit [Ping timeout: 480 seconds]
fmuellner has joined #wayland
<nielsdg> sure, was just mentioning it couldn't violate a spec it didn't implement in the first place
alarumbe has joined #wayland
eroux has quit [Remote host closed the connection]
Company has joined #wayland
eroux has joined #wayland
manuel1985 has joined #wayland
floof58 is now known as Guest739
floof58 has joined #wayland
manuel1985 has quit [Ping timeout: 480 seconds]
Guest739 has quit [Ping timeout: 480 seconds]
molinari has joined #wayland
junaid has joined #wayland
<hays> what are reasons one would get a "connection refused" from wayland?
<bl4ckb0ne> failed to connect to the display
<hays> yeah im trying to figur eout why its not connecting to the display
<hays> connect(6, {sa_family=AF_UNIX, sun_path="/var/run/wayland-1"}, 21) = -1 ECONNREFUSED (Connection refused)
<bl4ckb0ne> permissions maybe
rv1sr has quit []
<mjt> it means it is not listening
<mjt> permission denied will return different error
<hays> mjt: why wouldn't it be listening?
dcz_ has quit [Ping timeout: 480 seconds]
<mjt> well, it's your system, no? I've no idea
<mjt> I just said what this error means
<mjt> ECONNREFUSED
<mjt> A connect() on a stream socket found no one listening on the remote address.
<hays> is wayland a daemon that needs to be running?
<hays> sorry very new to this
<bl4ckb0ne> a compositor needs to be running yes
<hays> such as sway
<hays> the above error is from sway
<mjt> /var/run/wayland-1 is a strange name for a wayland socket
<mjt> usually it is /run/user/$UID/wayland-0
<i509VCB> There can be multiple servers running at the same time
<mjt> and?
<i509VCB> You'll typically have the WAYLAND_DISPLAY set to the socket name for the client to use
<mjt> which resolves to a socket in $XDG_RUNTIME_DIR
<i509VCB> Hmm yeah that's odd
<mjt> it's very unlikely that XDG_RUNTIME_DIR is /var/run
<mjt> it smells it is not set up correctly and have some default value
<mjt> if it's after sudo/su, it kind of explains things but still it's not the right value for XDG_RUNTIME_DIR
<hays> XDG_RUNTIME_DIR=/var/run
<mjt> sure it is
<hays> there is a patch applied to allow wayland to run as root
<mjt> it's not the right value for it
<mjt> allow running *sway* as root
<hays> sorry yews
<hays> yes
<mjt> where's your sway listening?
<hays> what do you mean? right now say fails to launch
<mjt> find its pid and do lsof -p $pid
<hays> sway fails to launch with the error
<mjt> heh
<hays> sorry i said that but maybe it was missed
<mjt> so do you have $WAYLAND_DISPLAY set *before* starting sway?
<mjt> it is sway should should set this variable, fwiw
<hays> WAYLAND_DISPLAY=wayland-1
<mjt> and why do you set it?
<hays> that i do not know
<mjt> heh
<mjt> unset it and try again
<mjt> that's some strange stuff going on really. Setting random stuff to random values.. :)
<hays> yeah im getting into this but i don't know everything
<kennylevinsen> you're running an old version of sway if you need that patch
<hays> mjt: set HDMI-A-2 as primary <-- well this is wrong im plugged into HDMA-A-1
<hays> mjt: sway tried to launch
<mjt> that's a strange patch as well.. why they changed the format of sway socket? there's no need to :)
julio7359 has joined #wayland
<kennylevinsen> if sway itself fails to start with a Wayland socket error, then WAYLAND_DISPLAY is erroneously set when starting sway which causes it to run in nested mode.
<mjt> < mjt> and why do you set it?
<mjt> :)
<hays> yeah hold on im trying stuff
<kennylevinsen> also note that you are looking for #sway on libera chat, #wayland is for protocol and implementation discussions
danvet has quit [Ping timeout: 480 seconds]
<hays> yes thats becoming clearer
julio7359 has quit [Remote host closed the connection]
junaid has quit [Ping timeout: 480 seconds]
nerdopolis has quit [Read error: Connection reset by peer]
nerdopolis has joined #wayland
DynamiteDan has joined #wayland
<DynamiteDan> Greeting. I am a longtime user of linux, bit never built a a graphical app on it. Could someone provide me with some info (a link) on how to start building native WayLand clients? Thanks in advance
Szadek has quit [Quit: WeeChat 3.7.1]
Szadek has joined #wayland
<soreau> you might have a look at https://github.com/emersion/hello-wayland
<soreau> you can also use a toolkit such as gtk, which hides many of the platform details
<DynamiteDan> thanks soreau !
<DynamiteDan> My focus is understanding the Wayland layer :)
<soreau> basically there's libwayland that implements server and client libraries, which facilitate communication across a socket between the two
rasterman has quit [Quit: Gettin' stinky!]
<DynamiteDan> exactly what I need for my study :)
<DynamiteDan> thank you so much
<soreau> np
hardening has quit [Ping timeout: 480 seconds]
floof58 is now known as Guest755
floof58 has joined #wayland
Guest755 has quit [Ping timeout: 480 seconds]