I'm having the same xorg crash problem on Xubuntu 24.04 beta, see
#2061246 (dup'ed to here.) I can reproduce the problem with a Ubuntu
24.04 beta install, but there xorg always crashes, unlike the
Xubuntu/xfce4 flavor where the first login after booting fails but
trying again immediately will succ
*** This bug is a duplicate of bug 1869629 ***
https://bugs.launchpad.net/bugs/1869629
** This bug has been marked a duplicate of bug 1869629
please add /etc/mdns.allow to /etc/apparmor.d/abstractions/mdns
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
This problem is indeed somewhat pervasive, I also filed bug 1869632 on
cups-browsed doing the same thing, for the same reason. I suspect more
will pop up. I don't think libnss_mdns is too widely used, most people
would use libnss_mdns_minimal. I only have to use libnss_mdns because
my ISP is insan
Bug also exists in package version 1.27.3-1 (current version in focal)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1869632
Title:
AppArmor profile denied access to /etc/mdns.allow
To manage notif
Public bug reported:
Many messages in syslog
audit: type=1400 audit(1585521672.468:40): apparmor="DENIED"
operation="open" profile="/usr/sbin/cups-browsed" name="/etc/mdns.allow"
pid=1323 comm="cups-browsed" requested_mask="r" denied_mask="r" fsuid=0
ouid=0
This is caused by configuring libnss-m
As a workaround, hanging /etc/apparmor.d/local/usr.sbin.chronyd to
include
/etc/mdns.allow r,
and reloading with
sudo apparmor_parser -r /etc/apparmor.d/usr.sbin.chronyd
made it shut up.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
Public bug reported:
Many repetitions of
audit: type=1400 audit(1585517168.705:63): apparmor="DENIED"
operation="open" profile="/usr/sbin/chronyd" name="/etc/mdns.allow"
pid=1983815 comm="chronyd" requested_mask="r" denied_mask="r" fsuid=123
ouid=0
in log. I use libnss-mdns for .local name reso
Looking into this, it seems the problem is that /usr/lib/systemd/scripts
/chronyd-starter.sh expects to be able to check for the cap_sys_time
capability by grepping the output of "capsh --print" for
"^Current.*cap_sys_time". However, in Focal the output of "capsh
--print" for a root process is jus
ExecStart twice is what I meant (this is the way to replace the command
from the base definition instead of adding another command to the list,
see the systemd.unit man page for details.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
No, ExecStart twice is correct. This is the way systemd overrides
work; normally a value for a keyword adds to the list of values from
the base .service definition. I don't want that, I want to replace
it. The special ExecStart= with no value tells systemd to reset the
base value to empty, th
Be aware the messages will come back next time you boot after
upgrading a package that touches something in /etc, which will trigger
another scan by ureadahead. Better is the workaround I gave back in
#9, but really what I recommend is just purge ureadahead. ureadahead
only ever can help the seco
Similarly, I have set in apt.conf.d
Acquire::https::Proxy "DIRECT";
(because apt-cacher-ng can't cache https) and I get
proxy 'DIRECT' looks invalid
The regexp definitely needs to be broadened.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Tags added: manpage
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/605300
Title:
ureadahead man page does not include exit status
To manage notifications about this bug go to:
https://bugs.launch
/sbin/ureadahead is writing out warnings every time it gets a relative
path from debugfs. This seems excessively wordy, but putting a -q on
the ExecStart in ureadahead.service would shut it up.
I did a systemd drop-in as a workaround by creating
/etc/systemd/system/ureadahead.service.d/quiet.conf
I had what appears to be a variant of this problem on a machine upgraded
from Lucid; selecting logoff/restart from the unity bar resulted in no
restart, and after manual restart an initctl crash was reported.
Installing the proposed change seems to have fixed it, thanks.
--
You received this bug
15 matches
Mail list logo
