Package: systemd
Version: 256.7-1
Severity: minor
Hey.
This is probalby not a real problem and if at all rather just a
cosmetic issue... so I'm totally fine if you just close the bug
without changing anything, and this is merely a heads up in case
no one ever noticed it before:
When e.g. deboot
Package: systemd
Version: 256.6-1
Severity: minor
Hey.
This happens since perhaps a few months when upgrading the systemd package:
Setting up systemd (256.6-1) ...
/usr/lib/tmpfiles.d/legacy.conf:13: Duplicate line for path "/run/lock",
ignoring.
(Reading database ... 120487 files and directorie
Package: systemd
Version: 256.5-1
Severity: important
Hey.
I think since version 256 there's systemd-ssh-generator and friends including
/etc/ssh/ssh_config.d/20-systemd-ssh-proxy.conf which is a non-conffile that
is a symlink to:
/usr/lib/systemd/ssh_config.d/20-systemd-ssh-proxy.conf
as such,
Package: init-system-helpers
Version: 1.66
Severity: normal
Hey.
I've just got that error during an upgrade run:
# aptitude
Performing actions...
Retrieving bug reports... Done
Parsing Found/Fixed information... Done
Reading changelogs... Done
apt-listchanges: Do you want to continue? [Y/n]
apt-
Oh and one more:
The underlying /tmp (i.e. when not mounted) is now still
1777/drwxrwxrwt .
It might make sense to change that to e.g. 0755/drwxr-xr-x?
Of course that would leave a defunct /tmp if the tmpfs is unmounted,
but at the same time prevent accidental writes there.
So depends on wheth
Package: systemd
Version: 256~rc3-6
Severity: normal
Hey.
When /tmp was switched over to tmpfs, it seems that there was no cleanup of
the underlying /tmp (i.e. on the underlying fs), so any files that had been
there, are still there and will – unless manually removed – remain there
forever.
No
Just for the records:
There's now a fix for this at:
https://github.com/systemd/systemd/pull/30074
(which I confirmed working)
>From my side it's not super important to have that cherry picked.
I'd hope it might still make it into 255, so for that I can easily wait
and it saves you guys some wo
Control: forwarded -1 https://github.com/systemd/systemd/issues/30083
On Fri, 2023-11-17 at 13:48 +, Luca Boccassi wrote:
> Please open an issue on github and attach debug level logs showing
> the
> error
Done.
Cheers,
Chris.
On Fri, 2023-11-17 at 15:37 +0100, Michael Biebl wrote:
> downgrades are not officially supported by Debian.
Sure... and if it's not fixable... well then it's not. But at least it
would be better then to abort the downgrade if it's detected that e.g.
a DE is running.
In my case it didn't matter bu
Package: systemd
Version: 255~rc2-1
Severity: normal
Hey.
The following two issues are both solved when downgrading to 254.5-1 (and
completely
rebooting the system, before trying again - they also shop up again, only after
completely rebooting the upgraded systemd again):
1) I have a somewhat s
Package: debhelper
Version: 13.11.7
Severity: wishlist
X-Debbugs-Cc: pkg-systemd-maintain...@lists.alioth.debian.org
Hey there.
Would it make sense and be possible for the systemd debhelper programs to
support systemd generators?
I think of something like just copying the file to the right loca
Hey.
On Fri, 2021-07-02 at 10:50 -0400, Felipe Sateler wrote:
> systemctl show -p Id,UnitFileState,UnitFilePreset '*.service'
That seems promising... thx.
When I do something like:
systemctl show -p Id,UnitFileState,UnitFilePreset '*' | paste - - - - | grep
-E -v $'^[^\t]+\tUnitFileState=([^
Hey there.
Perhaps someone can help me with this, cause I couldn't find any real
good solution.
I've noticed that e.g. after upgrading some of the university’s nodes
from buster to bullseye, there were some units which were not in the
default vendor state, e.g.:
# systemctl status fstrim.timer
On Sun, 2021-06-27 at 15:00 +0200, Michael Biebl wrote:
> I fail to see the security benefit here? What do we gain by (not)
> pre-allocating a system group like systemd-coredump?
Well it's not a big issue... but as always: something that is not even
there, may not be abused in the first place.
On Sat, 2021-06-26 at 20:07 +0200, Michael Biebl wrote:
> Then systemd would just setup all groups that are used by systemd
> (and
> sub-packages).
Seems to be a good change... but it would then still set up *all*
users, whether the respective part is used or no.
> Personally, I don't think it's
Package: systemd
Version: 245.5-2
Severity: normal
Hey.
I've just noted the following behaviour.
/lib/systemd/system/smartmontools.service has:
[Install]
WantedBy=multi-user.target
Alias=smartd.service
Which leads to:
# tree /etc/systemd/system
/etc/systemd/system
├── multi-user.target.wants
On Wed, 2019-04-03 at 00:15 +0200, Michael Biebl wrote:
> Feel free to submit additions/corrections/updates to the release-
> notes,
> if you think those changes are not satisfactory.
I think it's good start... one perhaps missing thing:
I vaguely recall to have read somewhere, that some of the *
Package: systemd-sysv
Version: 240-1
Severity: wishlist
Hey.
Maybe I couldn't just find it, but it seems there is no central place
which describes which "legacy" packages can be removed when running
systemd... respectively which services could be (optionally) replaced
by which systemd service/su
Control: reopen -1
Control: reassign -1 cinnamon 3.8.8-1
On Thu, 2018-08-16 at 01:05 +0200, Michael Biebl wrote:
> In any case, this looks like a cinnamon issue.
Well I reopened & reassigned it for now. Maybe the cinnamon maintainers
have some idea.
> As for the weird Xorg issue: My guess is, t
I'm afraid, I have no idea why mine doesn't restart ^^
Cheers,
Chris.
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
On Wed, 2018-08-15 at 22:33 +0200, Michael Biebl wrote:
> If I restart logind via "systemctl restart systemd-logind", my X
> session
> is terminated on sid.
Nope... just tried it again (also sid)... cinnamon just continues to
run.
> I'm curious why that is not the case for you.
> Are you using Wa
On Wed, 2018-08-15 at 22:07 +0200, Michael Biebl wrote:
> Are you sure then that logind is actually restarted?
I just manually tried (actually logind was just a guess to be the cause
for the pop up not appearing... so I tried several services before)
> needrestart is
> not
> supposed to restart l
Hey Michael.
On Wed, 2018-08-15 at 21:02 +0200, Michael Biebl wrote:
> I suppose what you are seeing is that Xorg exited.
No,.. my X doesn't exit... the only thing that happens is, that when I
press the power button, no dialog that asks what should be done pops up
(as it does when logind wasn't re
Package: systemd
Version: 239-7
Severity: important
Hi.
Since some systemd ugprade (unfortunately I don't remember which one it was
exactly, cause I
hit the problem only rarely)... when systemd-logind has been restarted, e.g. by
needrestart
after upgraded and I press the powerbutton, cinnamon s
Package: libnss-mymachines
Version: 239-6
Severity: important
Hi.
When libnss-mymachines it automatically adds the respective
entries to /etc/nsswitch.conf and it seems to place
"mymachines" after "dns".
This is IMO bad (and actually even a security hole), as it would
resolve DNS names before t
25 matches
Mail list logo
