I encountered this same issue on Ubuntu 22.04.03 LTS (systemd
249.11-0ubuntu3.11).
After `usermod -a -G `, processes that are spawned or
restarted by systemd user service units do not pick up the new group
(`grep Group /proc//status` does not include the new group) until
after the `systemd
** Changed in: systemd (Ubuntu)
Status: Invalid => Confirmed
--
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/1811295
Title:
systemctl daemon-reexec does not update
The problem is that Xfwm's built-in compositor and virgl don't play nice
together.
Work-around: Boot the VM with virgl=off (on the video device) or gl=off
(on the display), run xfwm4-tweaks-settings in the VM, select the
"Compositor" tab, and uncheck "Enable display compositing". Then shut
down
This is still broken in Artful, but is fixed in Bionic.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1670494
Title:
'wpa_supplicant -D nl80211 -W' hangs with some Intel
No. If I monitor interrupts, the Alps device actually stops sending
interrupts when the touchpad or trackstick stutters.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Public bug reported:
init_wpa_supplicant() in /etc/wpa_supplicant/functions.sh runs
wpa_supplicant with the -W option, which causes it to wait for wpa_cli
to attach. init_wpa_supplicant() then attaches wpa_cli to
wpa_supplicant.
When the nl80211 driver is used with some Intel cards,
I don't think -u would be necessary if /etc/network/if-up.d/ntpdate were
using the correct lock file (/var/lock/ntpdate vs /run/lock/ntpdate, as
I pointed out in comment #27).
But I do agree that either adding -u or fixing the lock file path would
be a simple solution to this problem.
--
You
Yes, it looks to me like sntp is a sufficient replacement for ntpdate.
However, sntp is not currently packaged for Debian or Ubuntu:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793837
In addition, prior to that bug being introduced, sntp was included in
the 'ntp' package, so sntp could not
My original issue is definitely a duplicate of Bug #1575572 and the fix
for that bug solves the specific problem described in Comment #8.
The issues described by Lars Kollstedt and others are a separate issue
... My original issue was that systemd would not start ntp.service if
Aha! I've found the issue.
/etc/network/if-up.d/ntpdate is called when each network interface comes
up. This happens before network.target is reached, so it happens before
ntp.service would normally be automatically started by systemd.
/etc/network/if-up.d/ntpdate calls `invoke-rc.d ntp stop`,
** Attachment added: "list-deps.txt"
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1577596/+attachment/4654853/+files/list-deps.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ntp in Ubuntu.
Attached.
Also attached the output of `systemctl list-dependencies` in case that
helps any.
$ systemctl status ntp
ntp.service - LSB: Start NTP daemon
Loaded: loaded (/etc/init.d/ntp; bad; vendor preset: enabled)
Active: inactive (dead)
Docs: man:systemd-sysv-generator(8)
May 03
I came across a box that was running Ubuntu 15.10 with ntpd. systemd was
automatically starting ntpd on boot on that system:
# systemctl status ntp
ntp.service - LSB: Start NTP daemon
Loaded: loaded (/etc/init.d/ntp)
Active: active (running) since Sun 2016-04-24 14:48:26 EDT; 1 weeks 1
Public bug reported:
After updating from 14.04 to 16.04 on a number of my systems, ntpd no
longer starts at boot on any of those systems.
`systemctl status ntp` shows:
ntp.service - LSB: Start NTP daemon
Loaded: loaded (/etc/init.d/ntp; bad; vendor preset: enabled)
Active: inactive
You can also set Apt::Default-Release to the Version instead of the
Suite. In other words, 'Apt::Default-Release "16.04";' will match all
of the package sources for xenial.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt
@robert-katzschmann:
Make sure wpa_cli is running:
# ps aux | grep wpa
/sbin/wpa_supplicant -s -B -P /run/wpa_supplicant.wlan0.pid -i wlan0 -W -D wext
-c /etc/wpa_supplicant/wpa_supplicant.conf
/sbin/wpa_cli -B -P /run/wpa_action.wlan0.pid -i wlan0 -p
/var/run/wpa_supplicant -a /sbin/wpa_action
ifupdown 0.7.54ubuntu1.3 fixes this bug for me in Wily.
@dbilunov: Would you mind testing the trusty-proposed package?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=545766
** Bug watch added: Debian Bug tracker #545766
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=545766
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in
@Dariusz: Works for me on Wily. Nice find, this is a much better fix
than my proposed patch. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1545302
Title:
wpa-roam
See bug #1545363 - my patch for that bug happens to remove the use of
the ifstate file. However, fixing that does not solve the "ifup:
recursion detected ..." issue. The environment variable still needs to
be removed to fix the recursion issue.
After thinking about it some more, I think it may
Oops ... missed "inet dhcp" on the "iface dhcp_dns" line above. That line
should be:
iface dhcp_dns inet dhcp
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1545302
Title:
** Description changed:
There are situations where I have multiple APs (living on separate
networks) in range simultaneously and I need to be able to manually
choose between them (to manually move between those separate networks).
To handle this, I have multiple wpa_supplicant config
My configuration:
/etc/network/interfaces
auto wlan0
iface wlan0 inet manual
wpa-driver wext
wpa-roam /etc/wpa_supplicant/wpa.conf
wpa-roam-default-iface dhcp
iface dhcp inet dhcp
dns-nameservers 8.8.8.8 8.8.4.4
iface dhcp_dns
/etc/wpa_supplicant/wpa.conf
network={
ssid="x"
Updating my patch ... The environment variable also needs to be unset
before calling ifdown.
** Attachment added: "patch"
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1545302/+attachment/4572496/+files/patch
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
The following versions of ifupdown introduced a recursion check using
"IFUPDOWN_" environment variables along with a new locking mechanism
for ifup (see #1337873):
0.7.47.2ubuntu4.2 (in Trusty)
0.7.54ubuntu1.1 (in Wily)
0.7.54ubuntu2 (in Xenial)
This recursion check breaks
*** This bug is a duplicate of bug 1545302 ***
https://bugs.launchpad.net/bugs/1545302
** This bug has been marked a duplicate of bug 1545302
wpa-roam broken by fix for ifupdown #1337873
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
Public bug reported:
There are situations where I have multiple APs (living on separate
networks) in range simultaneously and I need to be able to manually
choose between them (to manually move between those separate networks).
To handle this, I have multiple wpa_supplicant config files for each
I have also verified the fix on Trusty.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1366829
Title:
7.4.4-1ubuntu2.1 makes rsyslogd to take all the CPU in OpenVZ
Pull request has been accepted upstream.
Since there are now a bunch of upstream commits involved in the complete
fix, I'm attaching an updated 11-fix-infinite-loop-openvz-vms.patch file
for the ubuntu packages which contains all the necessary changes.
I also posted updated ubuntu package
Sorry, there were two issues:
1) The condition that the fix was testing for (EBADF on read before dropping
privileges) was not a reliable indicator of the underlying problem. I should
really have tested for EPERM on read after dropping privileges.
2) I only applied the fix to imkmsg, it also
Test case:
* Install rsyslog 7.4.4-1ubuntu2.1 on an Ubuntu system that runs inside an
OpenVZ container (If necessary, use ProxMox to quickly establish an OpenVZ
container environment)
* Verify that '$KLogPermitNonKernelFacility on' is set in /etc/rsyslog.conf
* Restart rsyslog to make sure any
** Attachment added: Upstream fix
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1366829/+attachment/4254548/+files/patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
Fixed here: https://github.com/rsyslog/rsyslog/pull/138
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1366829
Title:
Updating to rsyslog - 7.4.4-1ubuntu2.1 makes
33 matches
Mail list logo
