[SOLVED] Growing file bloat in ~/.dbus/session-bus and /root/.dbus/session-bus

Altoid · 2025-09-24 08:14:31

Hello:

stultumanto wrote:

... also missing /etc/machine-id.

They may have moved somewhere less conspicuous.
ie: hidden it

Or maybe it has become a part of the systemd OS.

I don't have one in my Daedalus system: I deleted it.
No issues.

stultumanto wrote:

... two files in ~/.dbus/session-id/.
... created back on 8-24 ...

That one you can delete.
If what we have seen up to now holds, the system behaviour should be that the -0 file gets overwitten at boot.

Best,

A.

greenjeans · 2025-09-24 14:28:03

Ceres system completely lacks the file at /etc/default/dbus. Nonetheless, dbus is definitely installed and running. I'm also missing /etc/machine-id.

On a new Devuan install there shouldn't be an /etc/machine-id, so that seems correct.

Another puzzle: there are exactly two files in ~/.dbus/session-id/.

I don't even have that folder on my Daedalus installs, just ~/.dbus/session-bus/, perhaps somebody has renamed it in Ceres.

fsmithred · 2025-09-24 15:50:45

The -0, -1, or -10 at the end of the filename corresponds to the $DISPLAY that was used.

If you switch to console without stopping the desktop, log in and then start a second desktop on :1, you'll get another file in ~/.dbus/session-bus with the same number as /var/lib/dbus/machine-id except with -1 at the end, but only if there's a number in dbus/machine-id. If you delete that file first, you won't get another one in your home unless you also restart dbus. (e.g. cycle through 'init 1' and 'ctrl-d')

> ctrl-alt-f1 to get to console
> log in as user
Run:
  startx -- :1

grunchy · 2025-09-24 22:04:05

hello, everyone. interesting thread. similar to user479 in post #44, i
wanted to add some more data for completeness.

i noticed the accumulating files last year but was not curious enough
to search for more information. just added rm's to my weekly clean-up
script.

based on another post, i commented-out IDTYPE=RANDOM, which prevents
the file accumulation and reverted the changes to my clean-up script.

based on this thread it appears that IDTYPE=RANDOM is a "good thing"
so those deletes will be getting added back.

my set-up is daedalus+KDE so sddm and pulseaudio are also installed.

on my system, the machine-id is defined in /var/lib/dbus/machine-id.
there is no /etc/machine-id file.

in addition to the ~/.dbus/session-bus and /root/.dbus/session-bus
directories mentioned in post #1, with KDE there is also the
/var/lib/sddm/.dbus/session-bus directory to clean-up.

and pulseaudio pollutes ~/.config/pulse with 6 files/directories, so
need to clean-up these as well:

<machine-id>-card-database.tdb
<machine-id>-default-sink
<machine-id>-default-source
<machine-id>-device-volumes.tdb
<machine-id>-runtime
<machine-id>-stream-volumes.tdb

no idea how this will change with excalibur.

greenjeans · 2025-09-25 16:17:01

Really appreciate the info @grunchy! I only have Mate and Openbox here to test on.

Dbus really gets around it seems.

So looks like whatever display manager is used, a folder is created in /var/lib/(display-manager)/.dbus/session-bus/*

But i'm still trying to figure out what purpose it serves and how they got there, after logging in and out of that partition multiple times yesterday, that folder was not added to by the system, still just 21 files that all show they were created when I started a snapshot last week.

The init script is working perfectly it seems, several days of testing now and no issues.

To clean /var/lib/(display-manager)/.dbus/session-bus/* in a similar fashion would take some extra work, have to list all available display managers, there's not that many but still.

And now I just found in /var/lib/NetworkManager some 181 files, 5 of which are config/info files of one sort or another, and all the rest are eth0-lease files, and all of those say they were created at the exact same time I started that snapshot last Wednesday.

So 176 files that all do the same thing, sample filename and it's contents:
internal-f368e190-5bd0-37e6-b42d-75f71b63df1d-eth0.lease

# This is private data. Do not parse.
ADDRESS=192.168.2.5

greenjeans · 2025-09-25 17:29:23

Further testing to come, might be something on my end, but the network manager files shouldn't be accumulating like that, I don't know that it has anything to do with Snapshot, I think Caja's properties tab are confusing some dates compared to PcmanFM.

The officially official Devuan Forum!

#51 2025-09-24 08:14:31

Re: [SOLVED] Growing file bloat in ~/.dbus/session-bus and /root/.dbus/session-bus

#52 2025-09-24 14:28:03

Re: [SOLVED] Growing file bloat in ~/.dbus/session-bus and /root/.dbus/session-bus

#53 2025-09-24 15:50:45

Re: [SOLVED] Growing file bloat in ~/.dbus/session-bus and /root/.dbus/session-bus

#54 2025-09-24 22:04:05

Re: [SOLVED] Growing file bloat in ~/.dbus/session-bus and /root/.dbus/session-bus

#55 2025-09-25 16:17:01

Re: [SOLVED] Growing file bloat in ~/.dbus/session-bus and /root/.dbus/session-bus

#56 2025-09-25 17:29:23

Re: [SOLVED] Growing file bloat in ~/.dbus/session-bus and /root/.dbus/session-bus

Board footer