1 |
On 2022-10-26, Matt Connell <matt@×××××××.tech> wrote: |
2 |
> On Wed, 2022-10-26 at 16:22 +0000, Grant Edwards wrote: |
3 |
>> Apparently, that error is cause by lack of a DBUS session. I just |
4 |
>> happened to stumble across a posting somewhere by somebody who had the |
5 |
>> same problem. How they figured out that was the problem remains a |
6 |
>> mystery. |
7 |
> |
8 |
> It is likely that nobody else noticed this because dbus has moved into |
9 |
> that "it is assumed to be there" tier of daemons these days. |
10 |
|
11 |
The problem wasn't that the daemon was missing. There is a DBUS |
12 |
daemon, and other things that use DBUS (e.g. notifications) work fine. |
13 |
|
14 |
What was apparently missing was a "session" |
15 |
|
16 |
$ set | grep dbus |
17 |
|
18 |
$ dbus-launch bash |
19 |
|
20 |
$ set | grep DBUS |
21 |
DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-45cBmpKpTX,guid=b783eda6500beba7132e450b63596c64 |
22 |
|
23 |
> Like most GNOME components, the GNOME developers are assuming all of |
24 |
> GNOME is available all of the time. |
25 |
|
26 |
Yep. |
27 |
|
28 |
-- |
29 |
Grant |