ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput
<eruditehermit>
ok it's the entrypoint but it can't find it
<eruditehermit>
this time it's worth building in docker, it's a path issue i'm pretty sure
RAOF has quit [Remote host closed the connection]
RAOF has joined #wayland
<eruditehermit>
so close
FreeFull has joined #wayland
andymandias has quit [Ping timeout: 480 seconds]
staceee has quit [Ping timeout: 480 seconds]
cpli has quit [Ping timeout: 480 seconds]
fabiancodes has quit [Ping timeout: 480 seconds]
cpli has joined #wayland
fabiancodes has joined #wayland
geemili has quit [Ping timeout: 480 seconds]
tkna has joined #wayland
tkna has quit [Ping timeout: 480 seconds]
geemili has joined #wayland
jonesv has quit [Ping timeout: 480 seconds]
staceee has joined #wayland
jonesv has joined #wayland
guacamolie has quit [Ping timeout: 480 seconds]
kennylevinsen has quit [Ping timeout: 480 seconds]
guacamolie has joined #wayland
kennylevinsen has joined #wayland
andymandias has joined #wayland
<whot>
eruditehermit: fwiw you don't need --filesystem=xdg-run/eis-0 anymore
<eruditehermit>
whot: ok I removed that
<eruditehermit>
whot: building locally has different issues =P
<eruditehermit>
nothing is free
<eruditehermit>
ok on the CI build it didn't fix things
<eruditehermit>
my local build I'm stuck because it can't flatpak build-init properly
<eruditehermit>
whot: had to run the container --privileged
<eruditehermit>
you want me to drop this right: export LIBEI_SOCKET=$XDG_RUNTIME_DIR/eis-0
<whot>
i *think* you can now just start normal input-leap and it will DTRT instead of wrapping it via that script. That script pre-dates most of the implementation
<whot>
yes, you can drop that export
<eruditehermit>
whot: if you have time, can you test the flatpak?
<whot>
unfortunately no, i'm completely swamped for the rest of the week
<eruditehermit>
ok
<whot>
change to `command: input-leap` and see how that works, that should start the gui (iirc)
<eruditehermit>
is it safe to change the compile flag that disable the GUI?
<whot>
you might need a few more deps then but otherwise yes
<eruditehermit>
-DINPUTLEAP_BUILD_GUI=OFF
<eruditehermit>
ah qt5
<whot>
might be worth using the KDE runtime for that though not sure that one has the required bits to build libportal
<whot>
but saves you having to install all of qt manually
<eruditehermit>
whot: yeah I'm trying with the kde runtime
<eruditehermit>
can you build with 2 runtimes?
<whot>
i don't think so but not sure
andymandias has quit [Ping timeout: 480 seconds]
<eruditehermit>
ok well let's see if it works
<eruditehermit>
your config looks pretty complex
<whot>
I think the only one I added was the key toggle, the rest is the default template
<eruditehermit>
I assume this is the InputLeap.conf
<eruditehermit>
what is server.name
<eruditehermit>
just a file with your IP address?
<whot>
huh?
andymandias has joined #wayland
<eruditehermit>
whot: the error I pasted: https://bpa.st/MZQPU talks about 2 config files
<whot>
hmm, I don't remember. the path is wrong too, should be input-leap, not InputLeap (I think)
<whot>
oh, I think I remember: the client requires the server name to connect but you can't easily add args to a flatpak so this was the way around it. echo "foo" > server.name means the flatpak will run `input-leapc foo`
<eruditehermit>
so I'm a bit confused, will there be 2 executables a server and a client we need to export
<eruditehermit>
looks like input-leapc and input-leaps
<whot>
again, if you just start input-leap it will present you with the GUI to select client or server
<eruditehermit>
ah yeah building with GUI is going to be trickier
<eruditehermit>
changing to KDE runtime breaks the portal build
<whot>
this flatpak wrapper script was written quite early for debugging and testing, so definitely don't take it as gospel, it was a PoC mostly
<whot>
the best way around that would be to replace libportal with QtDbus :)
<whot>
we didn't do that because ETIME
<eruditehermit>
haha this requires more understanding of the code
<eruditehermit>
but more specifically the understanding of qt and portal
<whot>
hence ETIME :)
<eruditehermit>
which I could eventually get to but it's probably not a short term thing
<eruditehermit>
I was hoping to be able to test it without the gui
<eruditehermit>
if I can get a small win, I will try to get the GUI to work tomorrow
crazybyte has quit [Quit: Bye]
crazybyte has joined #wayland
<whot>
replace quokka and tassie with your host names and save that as config and you should be able to run it as server
<whot>
and echo your server's hostname into server.name on the client and you should be able to run it as client
<eruditehermit>
ok sounds good
<eruditehermit>
whot: which of quokka and tassie are the client/server?
<whot>
whichever one matches $HOSTNAME iirc
andymandias has quit [Ping timeout: 480 seconds]
andymandias has joined #wayland
<eruditehermit>
interestingly I thought barrier used gtk
eruditehermit has quit [Ping timeout: 480 seconds]
tzimmermann has joined #wayland
checkfoc_us has quit []
checkfoc_us has joined #wayland
mxz_ has joined #wayland
leon-anavi has joined #wayland
glennk has joined #wayland
mceier is now known as Guest3134
mceier has joined #wayland
Guest3134 has quit [Ping timeout: 480 seconds]
eruditehermit has joined #wayland
coldfeet has joined #wayland
coldfeet has quit [Remote host closed the connection]
<eruditehermit>
whot: is there anything sacared about your shell script wrapper? Is there anything stopping me from writing a bash shell script with proper cli args to be able to read configs from arbitrary locations?
<eruditehermit>
I couldn't get the mouse/kbd sharing working between my computers
<bluetail>
if software isnt doing it, I can recommend a ezcoo usb switch
<eruditehermit>
bluetail: which one, there seems to be one for $30 and one for $130
<eruditehermit>
software would be ideal because it's supposed to be seamless =P
<eruditehermit>
however I've given up a day to try to get it to work so maybe I should take a hint
fmuellner has joined #wayland
<eruditehermit>
I appreciate everyone's help and suggestions. Thank you for the support and responding to all the questions. I've learned a lot so it was interesting.
<bluetail>
eruditehermit EZ-SW24-U3L for 16.99
jmnemoni has quit [Remote host closed the connection]
<bluetail>
The larger ezcoo models with video were not working for me properly
<bluetail>
I use a programmable IR remote to switch
<eruditehermit>
that looks nice
<eruditehermit>
I have a ugreen one at work which has a select button however, it never works properly the first time. I have to wake it up by switching from one input to the other
<eruditehermit>
output really
<ofourdan>
eruditehermit: I do not see your script using "--use-ei"
<ofourdan>
(the command line spawned)
<ofourdan>
so I do not think it's using EI actually
<ofourdan>
which would be a requirement to work with Wayland
<eruditehermit>
ofourdan: whot told me there were some EI lines not necessary
<ofourdan>
I think it it has the choice between x11 and ei, it will chose the former still
<eruditehermit>
ofourdan: did you run with: flatpak run com.github.inputleap.InputLeap
<ofourdan>
yes
<eruditehermit>
did the GUI pop up?
<ofourdan>
I can se input-leap connecting to the portal, but it doesn;t interact with the compositor, so I suspect it is not using ei
<ofourdan>
yes, the gui showed up
<bluetail>
eruditehermit I have it paired with ddcutil so I automatically switch display out too!
<eruditehermit>
but I am on kde 5.27 so maybe it's fine
<ofourdan>
tbh, I have no idea whether kde 5.27 had support for that
<eruditehermit>
is there a way to easily fix the --use-ei flag to start with
<eruditehermit>
I can try 2 gnome machines tomorrow
<ofourdan>
anyhow, all thta to say, AFAICS, your flatpak has all it takes to work on a Wayland + EI setup, except that the GUI is not passing the required --use-ei option - Would be a nice thing to contribute upstream ^_~
<eruditehermit>
the flatpak stuff or adding the --use-ei?
<ofourdan>
adding the --use-ei
<ofourdan>
so one can use input-leap GUI with a Wayland + EI setup
<eruditehermit>
lol, I'd have to learn qt and learn this code base.
<eruditehermit>
I'm not saying I won't, it'd just not happen immediately
<eruditehermit>
I'm not saying I won't try, whether I can actually do it is another question
<ofourdan>
usually, what I do in a case like that. is to search for an existing UI string, and take example
<ofourdan>
(search in the code, I mean)
<eruditehermit>
yeah
<ofourdan>
failing that, filing an issue upstream would be a good first tep as well :)
<eruditehermit>
really this shouldn't even be a configurable really. It should be autodetected when wayland is enabled
<eruditehermit>
perhaps I am misinterpreting, upstream didn't seem too pleased with me messing with this =P
<ofourdan>
problem is x11 is also available through Xwayland, and strictly speaking EI is agnostic to the windowing system, it should work with x11 as well
<ofourdan>
ah, what makes you think that?
<eruditehermit>
I talked to them on libera irc and they almost sounded like not having packages was a feature because it's too early to make a release
<eruditehermit>
I'll try submitting this flatpak stuff as a PR and raising an issue
<eruditehermit>
I imagine it's faster for them to do all this stuff on their own than answer questions
<ofourdan>
thanks! it's noice to have that flatpak updated, that's a good starting point!
<ofourdan>
*nice
<eruditehermit>
I wanted the automated build so I didn't have to build it myself
<ofourdan>
I reckon that's how most contributions start from, wanting something that's not there yet :)
jmnemoni has joined #wayland
jmnemoni has quit [Remote host closed the connection]
jmnemoniqueueanon has joined #wayland
<bluetail>
eruditehermit for ddcutil u want sudoers or group
<eruditehermit>
bluetail: I have bookmarked your code and will have a look tomorrow. It's super late here
<eruditehermit>
thank you
<eruditehermit>
ofourdan: thanks for your help testing too
<eruditehermit>
i'll submit the PR and issue tomorrow and see if the devs are around to chat
<eruditehermit>
ofourdan: are you on #inputleap-dev or #inputleap on libera?
<eruditehermit>
or just a curious user?
<eruditehermit>
fedora 40 has rpms so the flatpak is least useful to you I guess
mclasen has joined #wayland
mclasen has quit [Ping timeout: 480 seconds]
<eruditehermit>
ok gnight thanks again
noord has quit [Quit: bye]
noord has joined #wayland
eruditehermit has quit [Ping timeout: 480 seconds]
noord has quit []
noord has joined #wayland
kts has quit [Quit: Leaving]
nerdopolis has joined #wayland
kasper93 has quit [Remote host closed the connection]
kts has joined #wayland
kts has quit [Quit: Leaving]
Moprius has joined #wayland
Brainium has joined #wayland
Moprius has quit [Quit: bye]
mohit81582263530 has quit [Quit: mohit81582263530]
mohit81582263530 has joined #wayland
mclasen has joined #wayland
mclasen has quit []
nerdopolis has quit [Ping timeout: 480 seconds]
leon-anavi has quit [Read error: Connection reset by peer]
<sewn>
what would happen if a registry global_remove event was sent to delete an object (eg. seat) that another object (eg. ext_idle_notification_v1) is tied to?