Your message dated Sun, 9 Nov 2025 23:50:25 -0500
with message-id 
<caaajcmyrihlum4bycd861bxp5s7zykfnajm_hz8mxnwqmrd...@mail.gmail.com>
and subject line closing old gnome-settings-daemon bugs
has caused the Debian Bug report #966614,
regarding gsd-housekeeping: Failed to enumerate children of 
/var/tmp/systemd-private...
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
966614: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966614
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gnome-settings-daemon
Version: 3.30.2-3

$ apt policy gnome-settings-daemon
gnome-settings-daemon:
  Installed: 3.30.2-3
  Candidate: 3.30.2-3
  Version table:
 *** 3.30.2-3 500
        500 http://deb.debian.org/debian buster/main amd64 Packages
        100 /var/lib/dpkg/status

I have a bunch of lines like this in my systemd journal logs:

I have a bunch of lines like this for several services:

Jul 31 02:35:45 debian gsd-housekeepin[1546]: Failed to enumerate
children of 
/var/tmp/systemd-private-e7659f24f12a46ba8f34fda22628c99f-upower.service-E5eC1k:
Error opening directory
'/var/tmp/systemd-private-e7659f24f12a46ba8f34fda22628c99f-upower.service-E5eC1k':
Permission denied

looking at the journal logs, they are full of almost nothing but lines
like that for various services.

uname -a
Linux debian 4.19.0-9-amd64 #1 SMP Debian 4.19.118-2+deb10u1
(2020-06-07) x86_64 GNU/Linux

libc6 Version: 2.28-10

I have not modified anything with the config for that package. I'm
using the default buster setup.

--- End Message ---
--- Begin Message ---
There have been many changes to Debian since this bug was originally
reported. If you are still experiencing this issue with Debian 13 (or
with Debian 12 or Testing or Unstable), please report a new bug.

Thank you,
Jeremy BĂ­cha

--- End Message ---

Reply via email to