GNU bug report logs - #66339
Gnome-team dbus socket in /var/run/dbus, not /run/dbus

Previous Next

Package: guix;

Reported by: Vivien Kraus <vivien.kraus <at> univ-reims.fr>

Date: Wed, 4 Oct 2023 12:53:02 UTC

Severity: normal

Done: Liliana Marie Prikler <liliana.prikler <at> gmail.com>

Bug is archived. No further changes may be made.

Full log

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Vivien Kraus <vivien.kraus <at> univ-reims.fr>
To: bug-guix <bug-guix <at> gnu.org>
Subject: Gnome-team dbus socket in /var/run/dbus, not /run/dbus
Date: Wed, 04 Oct 2023 12:51:11 +0200

Dear guix,

The gnome-team branch starts the dbus service to provide a system
session socket in /var/run/dbus, but the dbus client expects it in
/run/dbus. This is the case for gdm and upowerd, and possibly many
more.

If I add

(symlink "/var/run/dbus" "/run/dbus")

in the script provided by dbus-activation (gnu/services/dbus.scm), then
gdm starts, and I can log in (with XFCE, GNOME still can’t load) and
verify upowerd works.

I don’t think this is a good solution though. I think we need to dig
into how to bind the socket in /run/dbus, and check the dbus clients to
make sure they all expect the socket in /run/dbus.

Best regards,

Vivien
This bug report was last modified 1 year and 284 days ago.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.