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
Seirdy has quit []
Seirdy has joined #wayland
rasterman has quit [Quit: Gettin' stinky!]
Tedesco has quit [Ping timeout: 480 seconds]
columbarius has joined #wayland
co1umbarius has quit [Ping timeout: 480 seconds]
ar1nov has joined #wayland
arinov has quit [Ping timeout: 480 seconds]
ar1nov has quit [Ping timeout: 480 seconds]
soreau has quit [Remote host closed the connection]
soreau has joined #wayland
maxzor__ has quit [Remote host closed the connection]
<qukami>
Anyone know how to remove trackpad acceleration with gnome?
<psykose>
gnome-tweaks might have an option
<qukami>
I checked that and it only has an option for mouse accel, rather than for the trackpad
<qukami>
It also doesn't seem to even work for mouse accel
<qukami>
Other than this minor gripe, gnome with wayland has been great
<qukami>
Really liking the built in trackpad gestures, 3 finger swiping etc..
<psykose>
gsettings set org.gnome.desktop.peripherals.touchpad.speed = -1 perhaps
<qukami>
That seems to just lower the trackpad sensitivity to really low
<qukami>
theres still a difference when moving your finger slow across the pad vs fasts
<psykose>
unlucky
<qukami>
dang
<qukami>
There's just no key for trackpad accel in the gsettings database or whatever
chenshijhie has quit [Remote host closed the connection]
<psykose>
under libinput there is accel_profile flat/adaptive, pointer_accel, but no idea how gnome tries or doesn't to expose them
chenshijhie has joined #wayland
<qukami>
Yeah, I saw that. I think this is a gnome issue rather than a wayland issue
<psykose>
or something to do with libinput, but yes, not wayland specific
marmarek has quit [Ping timeout: 480 seconds]
rasterman has joined #wayland
qukami has quit [Quit: WeeChat 3.3]
chenshijhie has quit [Ping timeout: 480 seconds]
chenshijhie has joined #wayland
d_ed has quit [Ping timeout: 480 seconds]
pnowack has joined #wayland
maxzor has joined #wayland
chenshijhie has quit [Remote host closed the connection]
dcz has joined #wayland
d_ed has joined #wayland
Arnavion has quit [Ping timeout: 480 seconds]
<emersion>
maybe we could start using GitLab release assets instead of filling up the website repo
mbalmer_ has quit [Read error: Connection reset by peer]
mbalmer has joined #wayland
Wanderer has quit [Remote host closed the connection]
dri-logger has quit [Remote host closed the connection]
dri-logger has joined #wayland
glisse has quit [Remote host closed the connection]
glisse has joined #wayland
barbarossa93 has joined #wayland
maxzor has quit [Ping timeout: 480 seconds]
Tedesco has joined #wayland
Tedesco has quit []
Tedesco has joined #wayland
Tedesco has quit []
Tedesco has joined #wayland
midnight-long has joined #wayland
midnight-long has quit [Remote host closed the connection]
Tedesco has quit [Quit: Leaving]
Tedesco has joined #wayland
bladerunner567 has joined #wayland
marmarek has joined #wayland
<bladerunner567>
Would wayland work ok with amd ati drivers?
<vyivel>
wayland the protocol will "work" even without drivers
<pq>
do you mean the proprietary drivers?
<bladerunner567>
nah, amd ati drivers are open source. What I mean is, the CPU is quite old
<pq>
the open source AMD graphics drivers support everything any Wayland system might need.
<bladerunner567>
Also what about steam? Does that work now?
<pq>
Work in what sense? It does run via Xwayland and games in particular too.
<pq>
Have you had specific problems before?
<bladerunner567>
Well, I've been using Xorg X11 untill now, and I found out about the differences between Xorg and Wayland. Many people are saying that wayland isn't quite there yet, so I was wondering if switching is a wise choice
<pq>
That is a tough question, it depends on your needs, your games, and your desktop environment too.
<bladerunner567>
I'm using Arch with Qtile wm
<dottedmag>
bladerunner567: Wayland is a protocol. It's similar to saying "TCP is not there yet". You need to check specific Wayland compositors that implement the protocol
<pq>
the best way to know is to try - there are no big reasons why it should utterly fail, but maybe there are practical details that happen to be a blocker for you
<pq>
hence I will not claim it just works, but I also think it should work in general
<bladerunner567>
dottedmag yes, I understand. I mean that, the issues with steam and proton I heard of. So, if xwayland is a fix, I don't have any problems with
<bladerunner567>
with it*
<bladerunner567>
pq: yes, I will try. the experience with xorg isn't very pleasant untill now, especially the compositors cause too much problems for me
<bladerunner567>
Also, before switching I wanna ask about the config files. The ATI config files are specifically for xorg, which I need to fix screen tearing. What would I if I noticed screen tearing issues on wayland?
<psykose>
wayland has forced vsync
<zamundaaa[m]>
Then you'd need to report a very serious driver bug
<psykose>
in the sense of there should be no screen tearing with no config, just start qtile in wayland and see how it goes
<bladerunner567>
Oh, alright. Thanks for help guys! :)
<zamundaaa[m]>
On a side note, as you had problems with X11 compositors, don't get frightened away by the fact that Wayland requires a compositor.
<zamundaaa[m]>
While they seem like very similar things, there's super giant differences.
<bladerunner567>
wait what? I thought wayland is just one package
<emersion>
wayland is just a protocol
<emersion>
then there are various pieces of software speaking the protocol
<emersion>
"compositors" and "clients"
<emersion>
wayland compositor examples: GNOME, KDE, sway, weston, etc
<emersion>
(simplifying a bit here)
<bladerunner567>
ahhh.. so which should I use?
<kennylevinsen>
you use whatever you want
<emersion>
just lime you choose a X11 WM, you need to pick one
<emersion>
like*
<psykose>
in x land you install the xorg-server thing, a wm, and maybe a compositor for it (generally)
<psykose>
on wayland you usually just install one thing
<psykose>
the thing you are using currently has wayland support somewhere in the config, not sure if it's a separate packaging on what you are running
dcz_ has joined #wayland
dcz has quit [Ping timeout: 480 seconds]
<bladerunner567>
but didn't emersion just say, I'd need a compositor?
<emersion>
the compositor is the only thing you need
<bladerunner567>
ohhhh
<bladerunner567>
now it makes sense
<emersion>
yeah. the terminology is confusing when you're used to X11's
<bladerunner567>
Ok, so I get a compositor and additional packages like xorg-xwayland for steam? I don't see a guide on the website
<psykose>
unless you want to try a different compositor
<bladerunner567>
oh alright
<pq>
hmm, the qtile wayladn todo list says: "XWayland -- not being implemented. Instead, use cage"
<psykose>
ah, that means you can't use anything x inside it like steam
maxzor_ has joined #wayland
<psykose>
then you should pick something else- i dunno, sway is probably the most polished in the tiling space
<bladerunner567>
I don't quite understand
<psykose>
the compositor needs to implement xwayland support to use it, and xwayland support is needed to open x-only applications like steam
<psykose>
since qtile doesn't, you can only run wayland applications, which is a large amount of things, but not most games/steam, so you need another compositor
<pq>
bladerunner567, I think "use Wayland" should be a means to an end, and not a goal in itself. There is a much bigger difference between Wayland-based desktops than between the same desktop with Wayland vs. X11 architecture.
<pq>
so you might want to choose a desktop first, and then see if you like it better with Wayland or X11.
<bladerunner567>
by desktop you're referring to de?
<pq>
yes, a de or something you build yourself from pieces
<pq>
steam, proton, and many games are X11 apps. Xwayland translates X11 to Wayland, to allow those apps to run on a Wayland-based desktop.
<bladerunner567>
and that's not possible on qtile u say?
<pq>
unfortunately, Xwayland requires explicit support from a Wayland compositor, and qtile seems to say it does not support it.
<bladerunner567>
ahh, I really like qtile tho lol
<emersion>
qtile recommends to run steam and such inside cage
<pq>
I suppose the "use cage" is a suggestion to use *another* Wayland compositor called "cage" to run X11 apps
<pq>
So you might run qtile, inside that cage, and inside that steam.
<ofourdan>
funny, soon we'll get as many wayland compositors as X11 window managers
<pq>
that was the idea from the beginning, right? ;-)
<emersion>
bladerunner567: if qtile is better with X11, it's perfectly fine to just stick with X11
<ofourdan>
you mean Xorg I support :þ
<ofourdan>
*suppose
maxzor_ has quit [Ping timeout: 480 seconds]
<emersion>
well, both are correct in this case :P
<bladerunner567>
Xorg isn't working out for me lol, that's why
<ofourdan>
true :D
<bladerunner567>
it works but I have to run it without a compositor + tearfree option in xconf which is causing some weird lag
maxzor_ has joined #wayland
<bladerunner567>
I've spent a week trying to fix these problems but nothing works.
<daniels>
emersion: yeah I'd be happy to start using release assets
<emersion>
the most painful part will be to figure out how to update the release script :S
<daniels>
I mean we could also just stop using the release script ...
<daniels>
have a CI pipeline which only runs when you push a tag
<daniels>
then just copy & paste the shortlog into the mail yourself
maxzor_ has quit [Ping timeout: 480 seconds]
<pq>
wasn't there something about gpg signatures? or is that only on the email with the hash?
<emersion>
i sign the tarball i upload
<emersion>
but yeah we could just stop using the release script
<MrCooper>
last I checked, GitLab supported only .zip and .tar.bz2 (or something as anachronistic) for release artifacts; has this been improved?