thanks a lot for the quick upload.
Now that wpasupplicant 2.10 is more widely available, I've seen this issue
popping up at several places. I'm not sure if it's only related to FRITZ!Boxes
but those alone are extremely popular in Germany, so I would have hated if the
next LTS potentially breaks
If it's enabled in the toolchain, is there still a need to explicitly
enable it (like in this case via --enable-lto) in individual packages?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bu
Public bug reported:
Please consider syncing the following changes from Debian
https://tracker.debian.org/news/1315963/accepted-network-manager-1364-2-source-into-unstable/
For more background see https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=1003907
Seeing that Ubuntu 22.04 will ship wpasu
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995655 maybe?
** Bug watch added: Debian Bug tracker #995655
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995655
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to system
I have to add, that I don't have such a NIS or LDAP setup to test this
myself.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1934393
Title:
systemd-logind network access
@Dan: have you actually confirmed, that building and running userdbd
solves those issues with NIS and LDAP?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1934393
Title:
> Other than the obvious approach of enabling systemd-userdb for Ubuntu,
I don't see how that would help, given that sytemd-userdb.service has
RestrictAddressFamilies=AF_UNIX AF_NETLINK AF_INET AF_INET6
You basically have the same issue as with systemd-logind.service. Or am I
missing something
1) Include drop-in conf files for systemd-logind and systemd-udevd to
remove the networking sandbox
Those drop-in configs should be shipped in the nis package. I don't see
a reason to ship a drop-in for systemd-udevd, fwiw.
--
You received this bug notification because you are a member of Ubuntu
** Bug watch added: Debian Bug tracker #878625
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878625
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1915502
Title:
"s
See also https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878625
Am Do., 10. Juni 2021 um 20:23 Uhr schrieb Michael Biebl :
>
> The relevant upstream bug report afaics is
> https://github.com/systemd/systemd/issues/7074
>
> Am Do., 10. Juni 2021 um 20:14 Uhr schrieb Michael Biebl
The relevant upstream bug report afaics is
https://github.com/systemd/systemd/issues/7074
Am Do., 10. Juni 2021 um 20:14 Uhr schrieb Michael Biebl :
>
> Am Do., 10. Juni 2021 um 14:50 Uhr schrieb Dan Streetman
> <1915...@bugs.launchpad.net>:
> >
> > Ok, so it does soun
Am Do., 10. Juni 2021 um 14:50 Uhr schrieb Dan Streetman
<1915...@bugs.launchpad.net>:
>
> Ok, so it does sound like this and bug 1916235 are the same issue. And
> this might be 'as designed', since upstream systemd wants systemd-logind
> to talk to systemd-userdb instead of directly connecting to
Turns out, the missing fsck progress bar is a regression:
https://github.com/systemd/systemd/issues/17157
** Bug watch added: github.com/systemd/systemd/issues #17157
https://github.com/systemd/systemd/issues/17157
--
You received this bug notification because you are a member of Ubuntu
Touch
>From my personal POV, I consider the progress bar more important then the
>ability to interrupt fsck with CTRL+C.
Nowadays, SSDs are much more common and enable_periodic_fsck = 0 has been the
default for many years now. So this is much less of an issue today then it was
back in 2015, I think.
As for text-only boot: Maybe we could convince upstream to enable
verbose mode once an fsck takes longer then say 30s (similar to how the
eye-of-cyclon animation kicks in when services take a long time to
start). With something like that implemented, dropping fsckd might be an
option, I think.
--
I would be happy to see this patch merged upstream.
There was an attempt a few years ago:
https://lists.freedesktop.org/archives/systemd-devel/2015-March/029186.html
Eventually it was removed again:
https://github.com/systemd/systemd/commit/96d9117ad2db7d8c13f7898127eee8939e88daf1
https://lists.f
It would be good adding this information to the upstream bug tracker.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1803993
Title:
Password appears on the VT1 screen
Sta
Looking at the discussion at
https://gitlab.freedesktop.org/xorg/xserver/issues/857#note_201402 this
might be a bug in plymouth which is supposedly fixed in plymouth 0.9.4.
Could users who can reliably reproduce the issue post if they have
plymouth installed and if so, which version?
** Bug watch
@rbalint if you can reliably reproduce the issue, it would probably be a
good idea if you follow up on that upstream bug tracker
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bug
In Debian, the values in debian/control are only used when the package is
uploaded intially to the archive. The override entry is created from that.
Changing the contents of the archive override is done by the ftp-masters. If
you later change the contents of debian/control does not have an influe
Public bug reported:
Packages shipping gobject introspection should be in the dedicated
section "introspection". This archive section was added a while ago, see
also the corresponding entry in the debian policy 3.9.3.0:
2.6. Version 3.9.3.0
Released February, 2012.
Public bug reported:
Hi,
the following conffile is marked as obsolete in my dpkg status db
/etc/bash_completion.d/ufw 50de7ccdcddb779093156f133d9c0a5e obsolete
Ufw now ships /usr/share/bash-completion/completions/ufw, so the
conffile should be removed on upgrades.
ProblemType: Bug
DistroRelea
Public bug reported:
The following files are marked obsolete after the upgrade to 16.04:
/etc/init/pulseaudio.conf 6244f8d452b29be7d17219b2db34138f obsolete
/etc/init.d/pulseaudio df2873ee4f4673d53e3562a0de6e8aa0 obsolete
/etc/default/pulseaudio 777f75f5521eab11c647da5c55544b1b obsolete
/etc/
Public bug reported:
The following conffiles were not cleaned up after the upgrade to 16.04:
/etc/bash_completion.d/gdbus 3c6022ac0bf85f2f374358a52456e803 obsolete
/etc/bash_completion.d/gsettings ed6dbd29972bb65275e46f1cb1ac5062 obsolete
/etc/bash_completion.d/gresource 305f04df5006e28bbee350
@pitti: will /etc/systemd/system/tmp.mount override a /tmp mount point
from /etc/fstab (/run vs /etc)?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1545707
Title:
Error
An explicit reload should not be necessary for "enable".
I also can't reproduce the problem:
$ cp /usr/share/systemd/tmp.mount /etc/systemd/system/tmp2.mount
$ systemctl enable tmp2.mount
Created symlink from /etc/systemd/system/local-fs.target.wants/tmp2.mount to
/etc/systemd/system/tmp2.moun
fwiw, halt-local.service was hooked up in final.target and contains the
following:
[Unit]
Description=/usr/sbin/halt.local Compatibility
ConditionFileIsExecutable=/usr/sbin/halt.local
DefaultDependencies=no
After=shutdown.target
Before=final.target
To apply that to my /etc/systemd/system/foo.serv
man bootup(7)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1532553
Title:
/etc/halt.local has become /usr/sbin/halt.local
Status in systemd package in Ubuntu:
Fix Com
Add a native service file and hook it up in the shutdown.target. That's
the cleanest solution.
/etc/systemd/system/foo.service
[Unit]
Description=Run service on shutdown
[Service]
ExecStart=/bin/true
[Install]
WantedBy=shutdown.target
--
You received this bug notification because you are a mem
Or make that
WantedBy=final.target, if you want to execute it during late shutdown.
See man systemd.special(7)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1532553
Title:
Before the introduction of systemd in Debian and Ubuntu, /etc/halt.local was
not supported at all.
Neither sysvinit nor upstart executed that file/script. So I'm mildly suprised,
when you say "it always worked".
We decided to not introduce support for this legacy, sysv specific
service, which af
Public bug reported:
The package declares a dependency on systemd-shim.
With systemd being the default init, this dependency is no longer required and
actually wanted.
The dependency on systemd-services should also either be replaced with a
dependency on systemd (or libpam-systemd, depending on
(In reply to Simon McVittie from comment #7)
> (In reply to Simon McVittie from comment #6)
> > Perhaps it would be better to make the stop command exit
> > nonzero?
>
> Straw man:
>
> ExecStop=/bin/sh -c "echo Stopping the system dbus-daemon is not supported.
> Reboot the system instead.; exit 1
ExecStop=/bin/true was my first idea, but Martin rightfully pointed out, that
this doesn't influence KillMode, i.e. we need KillMode=none.
With that KillMode setting, I think we can actually drop ExecStop=/bin/true, so
what remains is
KillMode=none
systemd has a final killing spree, before it u
dbus would be stopped by the final killing spree.
This usually looks like this
Sending SIGTERM to remaining processes...
Sending SIGKILL to remaining processes...
Unmounting file systems.
All filesystems unmounted.
Deactivating swaps.
All swaps deactivated.
Detaching loop devices.
All loop devi
This is what "-n" is for.
Incidentally, this is also used in rsyslog.service file for systemd.
2015-03-29 14:25 GMT+02:00 Hadmut Danisch :
> Public bug reported:
>
> Hi,
>
> it's rather a feature request than a bug report:
>
> I had to package several network services in docker images (and to star
Let me chime in here as maintainer of NM in Debian: The reason why we
ship the patch, which removes Wants/Before=network.target is, that this
lead to dependency cycles if services/sysv init scripts in rcS
(sysinit.target) had Should-Start/Required-Start: $network, like for
example /etc/init.d/rpcbi
Sorry, meant Before=network.target, of course...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1431774
Title:
cifs mount hangs on shutdown - NetworkManager needs
38 matches
Mail list logo
