You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should drop the hacks to remove the flatpak workarounds added in #780 and #859 once the underlying issues (flatpak/xdg-dbus-proxy#21 and flatpak/xdg-dbus-proxy#46) are fixed and the fixes have reached LT releases of major distros.
The text was updated successfully, but these errors were encountered:
Just for the record the latest xdg-dbus-proxy release 0.1.6 fixes both the issues. It's not yet widely available in major distros though. We'll probably want to wait another 6 months before removing these workarounds.
zeenix
added a commit
to zeenix/zbus
that referenced
this issue
Oct 4, 2024
Now that we're down to only two authentication mechanisms with one of
them being no-authentication, this really makes sense since we can just
autodetect what authentication method to use for a specific socket type
on a specific platform.
This also simplifies the handshake logic and will allow us to pipeline the
whole client-side handshake in the future, when we can drop the
xdg-dbus-proxy [workarounds].
As they say in the famous Queen song:
Hey! One man, one goal
Ha, one mission
One heart, one soul
Just one solution
One flash of light
Yeah, one God, one vision
One flesh, one bone, one true religion
One voice, one hope, one real decision
Whoa, whoa, whoa, whoa, whoa, whoa
Give me one vision, yeah
Fixesdbus2#731.
[workarounds]: dbus2#781
We should drop the hacks to remove the flatpak workarounds added in #780 and #859 once the underlying issues (flatpak/xdg-dbus-proxy#21 and flatpak/xdg-dbus-proxy#46) are fixed and the fixes have reached LT releases of major distros.
The text was updated successfully, but these errors were encountered: