commit 5a8b6d7a16c3e1584c4c76f36bf3f071f51d98b1
Author: Fabio Fantoni <fantonifabio@tiscali.it>
Date: Fri Aug 7 20:59:26 2026 +0200
update changelog
commit 12281d6e45e3496b94a32cb97243c7bcd642407c
Author: Fabio Fantoni <fantonifabio@tiscali.it>
Date: Fri Aug 7 20:55:52 2026 +0200
d/patches: use the running user D-Bus session bus instead of dbus-launch
require_dbus_session() only looked at DBUS_SESSION_BUS_ADDRESS, so with
the variable unset cinnamon-session re-exec'd itself under `dbus-launch
--exit-with-session` even when the user already had a session bus
running on the well-known socket at $XDG_RUNTIME_DIR/bus. That starts a
second bus, splitting activatable services and portals across the two,
and with only dbus-user-session installed (no dbus-launch binary) the
session does not start at all. X11 logins usually escape this because
the display manager wraps the session in a script that exports
DBUS_SESSION_BUS_ADDRESS, but the Wayland session does not go through
those wrappers.
The first patch asks GDBus for the session bus address (it looks for the
socket at $XDG_RUNTIME_DIR/bus since GLib 2.50) and exports it, so every
child of the session ends up on the same bus; the dbus-launch fallback
stays for setups without a user bus. Same approach as gnome-session in
leader-main.c.
The second patch fixes the fallback itself: `if (!execvp (...))` was
never true, since execvp() returns only on failure and then always -1,
so the "No session bus and could not exec dbus-launch" error was dead
code and the session silently carried on with no bus at all. Both
patches come from linuxmint/cinnamon-session#212.
Tested in a sid chroot: with a bus on $XDG_RUNTIME_DIR/bus the patched
binary no longer execs dbus-launch while the archive build does; with no
user bus the dbus-launch fallback still starts a session bus as before;
and with neither, the session now aborts with the error message instead
of continuing without a bus.
Closes: #835846
Assisted-by: Claude Code:claude-opus-5
Among the 1 debian patch available in version 6.6.4-1 of the package, we noticed the following issues: