Your message dated Sat, 18 Apr 2020 20:52:28 +0200
with message-id <[email protected]>
and subject line Re: /usr/lib/environment.d/99-environment.conf:3: invalid
variable name "export NO_AT_BRIDGE", ignoring
has caused the Debian Bug report #955046,
regarding /usr/lib/environment.d/99-environment.conf:3: invalid variable name
"export NO_AT_BRIDGE", ignoring
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.)
--
955046: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955046
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 244.3-1
Severity: minor
Dear Maintainer,
* What led up to the situation?
Logs show the message from systemd:
/usr/lib/environment.d/99-environment.conf:3: invalid variable name "export
NO_AT_BRIDGE", ignoring.
* What outcome did you expect instead?
No such message in the logs
Thanks in advance,
xiscu
-- Package-specific info:
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (900, 'testing'), (10, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.4.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages systemd depends on:
ii adduser 3.118
ii libacl1 2.2.53-6
ii libapparmor1 2.13.3-7
ii libaudit1 1:2.8.5-2+b1
ii libblkid1 2.34-0.1
ii libc6 2.30-2
ii libcap2 1:2.32-1
ii libcryptsetup12 2:2.3.0-1
ii libgcrypt20 1.8.5-5
ii libgnutls30 3.6.12-2
ii libgpg-error0 1.37-1
ii libidn2-0 2.3.0-1
ii libip4tc2 1.8.4-3
ii libkmod2 27-2
ii liblz4-1 1.9.2-2
ii liblzma5 5.2.4-1+b1
ii libmount1 2.34-0.1
ii libpam0g 1.3.1-5
ii libpcre2-8-0 10.34-7
ii libseccomp2 2.4.3-1
ii libselinux1 3.0-1+b1
ii libsystemd0 244.3-1
ii mount 2.34-0.1
ii util-linux 2.34-0.1
Versions of packages systemd recommends:
ii dbus 1.12.16-2
Versions of packages systemd suggests:
ii policykit-1 0.105-26
pn systemd-container <none>
Versions of packages systemd is related to:
pn dracut <none>
ii initramfs-tools 0.136
pn libnss-systemd <none>
ii libpam-systemd 244.3-1
ii udev 244.3-1
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi
On Sat, 28 Mar 2020 09:55:34 +0100 xiscu <[email protected]> wrote:
> Package: systemd
> Version: 244.3-1
> Followup-For: Bug #955046
>
> Ok, I see now that /usr/lib/99-environment.conf is just a link to
> /etc/environment
>
> ~# ll /usr/lib/environment.d/99-environment.conf
> lrwxrwxrwx 1 root root 16 Feb 15 15:44
> /usr/lib/environment.d/99-environment.conf -> /etc/environment
>
> :~# cat /etc/environment
> # Silence warning on dbus: Couldn't register with accessibility bus...
> NO_AT_BRIDGE=1
>
>
> I'll keep an eye on the logs...
I'm going to close this bug under the assumption that adding "export
FOO" to /etc/environment is not something that was explicitly documented
as proper usage of /etc/environment (a "random" Ubuntu bug report
doesn't really count in my book).
If there is official documentation in that regard and we can thus assume
that this is a more widespread problem, please reopen the bug report and
point to the relevant documentation.
Regards,
Michael
signature.asc
Description: OpenPGP digital signature
--- End Message ---
