Public bug reported:
Package apparmor-profiles
To reproduce the bug
apt install apparmor-profiles
apt install php-fpm
php-fpm installation will crash
Resolution
**
a) It's safer to set by default the php-fpm profile in complain mode
/etc/apparmor.d/php-fpm
Line
Important context from https://lists.debian.org/debian-security-
announce/2024/msg00057.html :
Andres Freund discovered that the upstream source tarballs for xz-utils,
the XZ-format compression utilities, are compromised and inject
malicious code, at build time, into the resulting liblzma5
Tracked down the cause to the Docker host, which runs on jammy, not
knowing about fchmodat2(). The syscall should normally return ENOTSUP
when called with AT_SYMLINK_NOFOLLOW on Linux, but the Docker seccomp
profile causes it to return EPERM, which confuses tar(1). Closing.
** Changed in: tar
Public bug reported:
This concerns tar 1.35+dfsg-3 in Ubuntu noble. This does NOT affect tar
1.34+dfsg-1.2ubuntu1.1 in mantic.
I'm seeing errors like this:
$ tar xvJf /extern/source/chromium_122.0.6261.111.orig.tar.xz --wildcards
Public bug reported:
I am seeing this on Ubuntu noble with polkitd 123-3.
After debootstrap'ing a minimal system, I run
# apt-get install linux-generic
which pulls in polkitd as a dependency. In the output, I see the
following:
Setting up polkitd (123-3) ...
Creating group
Thank you for the clarifications, Tim. For what it's worth, my Ubuntu
22 non-graphical shell *does* have DBUS_SESSION_BUS_ADDRESS to the same
value that appears in a Wayland session
("unix:path=/run/user/1000/bus"). So the bug you mention being exposed
does not occur for me.
It is also set
Some clues:
If I start Ubuntu 22 with kernel argument `systemd.unit=multi-
user.target` (i.e. non-graphical) then start Wayland with
`XDG_SESSION_TYPE=wayland dbus-run-session gnome-session` then
DBUS_SESSION_BUS_ADDRESS gets set to something like
Public bug reported:
With HP OfficeJet 7740 Pro A3/A4 duplex printer the A4 page size is not
selected properly and results in an incorrectly sized test page: "Media
limits: 0.42 x 0.42 to 27.52 x 35.14 cm". In the printer set-up summary
the media is described as "unknown" when A4 is selected as
You are correct that the multicast support has been removed in NTPsec.
This was intentional:
https://docs.ntpsec.org/latest/ntpsec.html
"Broadcast- and multicast modes, which are impossible to secure, have been
removed."
The Debian maintainers of the "ntp" package decided to stop maintaining
Public bug reported:
On startup the left of my two screens (DP1.2 connected) appears fussy,
although not unreadable the font is not distinct. Furthermore, the
computer start up logo - in this case "intel nuc" remains in the middle
of the left screen. It always seems to be one screen that goes
Reopening this issue as I am still observing the net_admin denial in
jammy.
** Changed in: cups (Ubuntu)
Status: Expired => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
** Also affects: lightdm (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1922414
Title:
ssh-agent fails to start
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: richard2268 F pulseaudio
/dev/snd/controlC1: richard2268 F pulseaudio
CasperMD5CheckResult: unknown
Date: Sat Jun 17 11:50:04 2023
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with
return
-process /usr/bin/dpkg returned an error code (1)
richard@richard-desktop:~$ reboot
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-73-generic 5.15.0-73.80
ProcVersionSignature: Ubuntu 5.19.0-42.43~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-42-generic x86_64
ApportVersion
** Tags added: multiseat
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1371250
Title:
LightDM fails to switch to greeter on logout if allow-user-
switching=false
** Changed in: debconf (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to debconf in Ubuntu.
https://bugs.launchpad.net/bugs/551637
Title:
debconf seems to require a controlling
** Changed in: gnupg (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnupg in Ubuntu.
https://bugs.launchpad.net/bugs/706011
Title:
gpg --key-gen doesn't have enough entropy and
Cannot reproduce in Ubuntu 22.04.2 LTS.
** Changed in: apport
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1098197
Title:
apport-gtk
** Changed in: glib2.0 (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1332623
Title:
Thunar behaves inconsistently with
** Package changed: ubuntu => apparmor (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1992430
Title:
Snap based apps crash after 5.19.0-18->5.19.0-19 kernel
is
playing, it does not continually send audio packets to the headphones
allowing the other device to play audio correctly, irrespective of which
device is deemed the priority by the headphones.
$ lsb_release -rd
Description:Ubuntu 22.04.1 LTS
Release:22.04
richard@richard-dell:~
$ sudo
Could this be a related issue, when deployment to aks fails, due to a
connection refused when pulling images from azure container
registry(ImagePullBackOff). This problem started this morning out of the blue.
Credentials for azure container service are ok and about every 20 image pulls I
get
Glad I found this bug report. Deleting the cert fixed the problem for me
as well. I'm not sure why the cert changed and it would be nice to be
notified that it changed and to be offered the option to have it
replaced.
--
You received this bug notification because you are a member of Ubuntu
Touch
Just had this message on Ubuntu 22.04.1 (5.15.0-46-generic) - was unable
to boot. Related or not, the suggesting to update /etc/fstab in the
comments above got me able to boot again.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
@Nick Rosbrook (enr0n): Your suggestion
(https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1981622/comments/10)
doesn't work on Kubuntu 22.04 fresh install, fully patched, probably
because modprobe@mtdpstore.service doesn't appear in the file. I have
tried commenting out everything that isn't
Affects me using fully updated Ubuntu 20.04.4 LTS
I used the changes noted in your fontconfig merge request (applied to
files in /etc/fonts/conf.avail/ 30-metric-aliases.conf and
45-latin.conf) and it cleared up kerning issues I was having with a
different PDF form! Thanks Gunnar and xiota!
--
*** This bug is a duplicate of bug 1949970 ***
https://bugs.launchpad.net/bugs/1949970
This appears to have been addressed in bug #1949970 by making use of a
feature of the PAM config. In /etc/pam.d/lightdm, I see e.g.
-authoptionalpam_gnome_keyring.so
-authoptional
Note to everyone watching this bug:
The file that John modified above is in the "extra profiles" section of
the upstream AppArmor source repository. It may be found on an Ubuntu
system at
/usr/share/apparmor/extra-profiles/sbin.dhclient
and in jammy, it has his fix.
However, the
This message...
type=AVC msg=audit(1625678140.496:1898): apparmor="DENIED"
operation="open" profile="/{,usr/}sbin/dhclient"
name="/proc/8537/task/8540/comm" pid=8537 comm="dhclient"
requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
...is actually for a different issue, discussed at LP:
Note that the /proc/XX/task/YY/comm denials are addressed in LP:
#1918410.
That leaves two of this sort:
audit: type=1400 audit(1645193286.560:2012): apparmor="DENIED"
operation="mknod" profile="/{,usr/}sbin/dhclient"
name="/run/NetworkManager/dhclient-oob_net0.pid" pid=103303
** Tags added: jammy
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1965923
Title:
rc.apparmor.functions should not mount /sys/kernel/security inside a
chroot
Public bug reported:
This concerns apparmor 3.0.4-2ubuntu2 in Ubuntu jammy.
When I run a command like aa-teardown(8), it will mount securityfs on
/sys/kernel/security if this is not already mounted.
On bare metal, this is reasonable. But in a chroot environment, the
command should probably exit
*** This bug is a duplicate of bug 1964814 ***
https://bugs.launchpad.net/bugs/1964814
Hello, i'm having the same problem on my system aswell. 22.04 - unfortunatly
i did try to follow
#Achim Behrens advice to remove, delete /lib/firmware/ath11k/WCN6855/hw2.1
manually and the update will
Public bug reported:
can't install pip because python2.7 has no zlib support
root@XX:~# python2 get-pip.py
Traceback (most recent call last):
File "get-pip.py", line 23974, in
main()
File "get-pip.py", line 199, in main
bootstrap(tmpdir=tmpdir)
File "get-pip.py", line 82, in
My software-properties-gtk is 0.99.9.8 on Ubuntu 20.04.3
$ software-properties-gtk
Response:
ERROR:dbus.proxies:Introspect error on :1.2681:/:
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message
recipient disconnected from message bus without replying
Traceback (most
I think Ubuntu probably needs gusb 0.3.9 or newer to fix this.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libusb in Ubuntu.
https://bugs.launchpad.net/bugs/1960768
Title:
fwupd crash on stop
Status in OEM Priority
Created attachment 144195
New crash information added by DrKonqi
gwenview (21.08.1) using Qt 5.15.2
- What I was doing when the application crashed:
1. used darktable to create a jpg from nef
2. opened jpg with showfoto (success, including metadata)
3. attempted to open jpg with gwenview,
that worked
** Changed in: pulseaudio (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1946153
Title:
[Lenovo ThinkPad P1
so it seems this is a partial fix, system sounds are still broken, and
the gnome speaker test is still broken, but sound is working for
specific applications. sound will work for chromium and firefox,
testing with "speaker-test -t wav -c" also results in no sound. this
shows up as "alsa plugin
performed the above upgrade, it did not resolve the issue
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1946153
Title:
[Lenovo ThinkPad P1 Gen 2, Conexant CX8070,
Public bug reported:
laptop is connected to a thinkpad thunderbolt 3 dock, sound worked while
connect until the latest update a few days ago on 20.04
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pulseaudio 1:13.99.1-1ubuntu3.11
ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140
Created attachment 141971
New crash information added by DrKonqi
gwenview (20.12.3) using Qt 5.15.2
- What I was doing when the application crashed:
This seems to happen reliably on jpg's produced by darktable.
Darktable-rendered pics all cause the crash. These were all NEF (Nikon)
raw
Public bug reported:
not sure it just didn't install
ProblemType: Package
DistroRelease: Ubuntu 21.04
Package: openssh-server 1:8.4p1-5ubuntu1.1
ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22
Uname: Linux 5.11.0-31-generic x86_64
NonfreeKernelModules: wl
ApportVersion:
I was able to verify this is fixed in iputils-ping 20210202-1. That is,
I saw this same problem, grabbed those sources from Debian, built them,
and tested again. Accordingly, this should already be fixed in Ubuntu
impish.
--
You received this bug notification because you are a member of Ubuntu
FWIW, the fix in focal-proposed looks good on my end as well.
I can confirm that the /etc/dhcp/dhclient-enter-hooks.d/resolved script
now has the is-enabled check, and while I won't be able to test out
resolvconf, I regard the updated conditional as equivalent to my
previous known-good workaround
Yes, it is still an issue in focal. Was there an update since last year
that should have addressed this?
** Changed in: systemd (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd
Thank you @ddstreet, I'm happy to see this as well. I'd like to get rid
of the workaround I've been using for this issue:
# dpkg-divert --divert /etc/dhcp/dhclient-enter-
hooks.d/resolved.DISABLED --rename /etc/dhcp/dhclient-enter-
hooks.d/resolved
--
You received this bug notification because
By following the same test procedure done in #18 and #19, the Hirsute
build of pam_faillock was successfully validated.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
https://bugs.launchpad.net/bugs/1927796
By following the same test procedure done in #18 and #19, the Groovy
build of pam_faillock was successfully validated.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
https://bugs.launchpad.net/bugs/1927796
By following the same test procedure done in #18 and #19, the Focal
build of pam_faillock was successfully validated.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
https://bugs.launchpad.net/bugs/1927796
Additional tests done on bionic: after changing the parameters set in
/etc/security/faillock.conf to:
deny=2
unlock_time=20
By trying to authenticate with the wrong password 2 times, it was
verified that the account was locked for the amount of time set to the
unlock_time parameter (20s).
--
Tested pam_faillock module for pam on bionic.
Test consisted on setting up pam_faillock with the following
configuration, as described in the man page:
/etc/security/faillock.conf file example:
deny=4
unlock_time=1200
silent
/etc/pam.d/config file example:
auth required
Public bug reported:
[IMPACT]
There is a known issue in pam_tally2 which may cause an account to be lock down
even with correct password, in a busy node environment where simultaneous
logins takes place (https://github.com/linux-pam/linux-pam/issues/71).
There are already two customer cases
Public bug reported:
Selected logs:
https://paste.ubuntu.com/p/gMbk2ntQyz/
https://paste.ubuntu.com/p/F8n72kCbJJ/
lshw:
https://paste.ubuntu.com/p/3Z9jwBdyVt/
If I try and use the bluetooth toggle in gnome settings upon boot it
won't do anything. If I have the bluetooth settings window open in
Hello! I do apologise. I spend half my time talking to BSD systems and
`netstat -f inet` is equivalent to `netstat --protocol=inet` on Ubuntu.
Indeed, as you point out I should probably be using `ip route show`. I
tend to use `netstat` because its output is much easier to read.
So this is
Public bug reported:
Attempting to run
netstat -f inet
results in
netstat: feature `AF BLUETOOTH' not supported.
Please recompile `net-tools' with newer kernel source or full configuration.
Both my net-tools and kernel packages are fully up-to-date. (Version
details are in the report
** Tags removed: verification-needed
** Tags added: verification-done
--
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/1908473
Title:
rsyslog-relp: imrelp module leaves
I tested this on Focal. I installed librelp0 and restart rsyslog. Prior
to the change, sockets were stacking up in CLOSE-WAIT (both from normal
use and from the netcat test). After the change, sockets are being
closed correctly.
** Tags removed: verification-needed-focal
** Tags added:
I think the problem was in the headphones. I found I was having trouble
on my phone as well. I contacted Sony support and they had me try a soft
reset of the headset, which seems to have restored function. I am still
getting bad mic sound on bluetooth, but I think it is just the low
quality sound
The test package fixes the issue for me.
--
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/1908473
Title:
rsyslog-relp: imrelp module leaves sockets in CLOSE_WAIT state
I can't seem to get the DG80 working correctly under PopOS 20.10. It
works great for listening to music (though that worked directly on
bluetooth without issues) but I can't seem to get the correct mode for
talk. Since you say you have success with it, I will play with it some
more before
I installed pulseaudio-modules-bt and it does give some new options for
sound output and possibly better sound, but microphone sound quality was
still iffy. Recorded sound on Audacity seemed better and was slightly
louder (according to the DB meter), but a test call on Microsoft Teams
was still
Disappointing. I've just ordered a 1mii B10 USB Bluetooth 5.0 Audio
Transmitter as a workaround...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1838151
Title:
Poor
PulseAudio 14.0 is out [1], so hopefully there's no other blocker to merge
missing features:
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/227
1: https://www.freedesktop.org/wiki/Software/PulseAudio/Notes/14.0/
--
You received this bug notification because you are a
Public bug reported:
My Epson printer disappeared from the list of registered printers.
I could not assign a suitable driver, even though a relevant package supplied
by Epson was already installed (under /opt).
It turned out that the logs contained messages like this one:
audit: type=1400
Public bug reported:
When suspending my freshly installed 20.04.1 system I noticed that on waking a
password is not required. lightdm does not have locking enabled on suspend. A
workaround I found from pszafer
on archlinux blog.
Quoted below:
create lockscreen.sh file somewhere in your
Closing stale bug report as invalid.
ddclient 3.9.1-7 (not yet released) will have many debconf improvements.
Please wait for that version to be released. If the debconf questions in
that version are still insufficient, please reopen.
** Changed in: debconf (Ubuntu)
Status: New => Invalid
First I reverted isc-dhcp-server back to the original focal version, since I
had an updated version from the PPA:
$ sudo apt install isc-dhcp-server=4.4.1-2.1ubuntu5
isc-dhcp-common=4.4.1-2.1ubuntu5
Then I install the update packages:
$ sudo apt update
$ sudo apt install
Andrew, 1:9.11.16+dfsg-3~build1 is wrong. The correct version is
1:9.11.16+dfsg-3~ubuntu1 (~ubuntu1 instead of ~build1).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
Excellent. I'm available to test the -proposed update for focal whenever
it is ready.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1872118
Title:
[SRU] DHCP Cluster
Jorge, I agree with Gianfranco Costamagna that a rebuild of isc-dhcp is
NOT required. Why do you think it is?
Presumably BIND also uses these libraries? If so, it seems like the Test
Case should involve making sure BIND still seems to work, and that BIND
should be mentioned in the Regression
Note that the upstream debian 3.6 package uses --enable-fat,
but that also builds libnettle.so.8.
It would be nice to have this configure option added to the
3.5.1 package which builds libnettle.so.7.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
No crashes to report.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1872118
Title:
DHCP Cluster crashes after a few hours
Status in DHCP:
New
Status in bind9-libs
Jorge, it sounds like ISC might think there is a more fundamental issue here:
https://gitlab.isc.org/isc-projects/dhcp/-/issues/121#note_152804
** Bug watch added: gitlab.isc.org/isc-projects/dhcp/-/issues #121
https://gitlab.isc.org/isc-projects/dhcp/-/issues/121
--
You received this bug
Jorge, I have been running for 25 hours on the patched version with no
crashes on either server.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1872118
Title:
DHCP
I ran:
sudo apt install \
isc-dhcp-server=4.4.1-2.1ubuntu6~ppa1 \
libdns-export1109=1:9.11.16+dfsg-3~ppa1 \
libirs-export161=1:9.11.16+dfsg-3~ppa1 \
libisc-export1105=1:9.11.16+dfsg-3~ppa1 && \
sudo systemctl restart isc-dhcp-server
The restart at the end was just for
** Bug watch added: gitlab.isc.org/isc-projects/dhcp/issues #128
https://gitlab.isc.org/isc-projects/dhcp/issues/128
** Also affects: dhcp via
https://gitlab.isc.org/isc-projects/dhcp/issues/128
Importance: Unknown
Status: Unknown
--
You received this bug notification because
I was able to reproduce this with 4.4.2 plus the Ubuntu packaging. I did
not try with stock 4.4.2 from source.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1872118
Public bug reported:
rsyslogd: error during parsing file /etc/rsyslog.d/FILENAME.conf, on or
before line 22: imrelp: librelp does not support input parameter
'tls.tlscfgcmd'; it probably is too old (1.5.0 or higher should be
fine); ignoring setting now. [v8.2001.0 try
Reviewed patches and they look good to me.
However, in the future, we should consider another possibility: disable
FIPS mode for libNSS3 by default, since that lib isn't FIPS-certified.
This can prevent customers from mistakenly think the opposite.
--
You received this bug notification because
** Changed in: nss (Ubuntu)
Assignee: (unassigned) => Richard Maciel Costa (richardmaciel)
** Changed in: nss (Ubuntu Bionic)
Assignee: (unassigned) => Richard Maciel Costa (richardmaciel)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pa
Thank you for taking the time to report this issue. As you note, this is
a long-standing feature of Ubuntu that Canonical leverages to help
understand our user base and improve and prioritize work that makes
Ubuntu better for all. I can assure you that all information is GDPR
compliant and that we
Public bug reported:
This concerns apparmor 2.13.3-7ubuntu5 in Ubuntu focal.
Saw this during a Firefox test run:
May 29 17:25:32 test-ubuntu64 kernel: [ 818.399967] audit: type=1400
audit(1590787532.023:69): apparmor="DENIED" operation="open"
profile="firefox"
Public bug reported:
This concerns apparmor-profiles 2.13.3-7ubuntu5 in Ubuntu focal.
I use the usr.sbin.nscd profile in enforce mode, and am seeing the
following messages in /var/log/syslog . I don't know if the SIGABRT is
related:
May 27 04:39:56 test-ubuntu64 kernel: [ 199.392521] audit:
I should note that Software Updater now gives a pop-up even before showing the
packages available to update that says:
"Failed to download repository information
Check your Internet connection."
And it just hangs endlessly; I cannot even close the pop-up window.
Whereas apt-get is giving the
Yes, I am.
When I download the file myself via firefox, I get a file that matches
the hash it is supposed to be and this also matches the file in
/var/lib/apt/lists of which the file in /var/lib/apt/lists/partial is
merely a symlink.
I ran an ISP transparent proxy test and it came up negative.
Public bug reported:
Upon reboot of Ubuntu 20.04, the selected sound device is not
remembered. Instead, another device is selected as default.
Current solution: Manually open the settings and select "Digital Output
(S/PDIF)", where my headphones are connected, on every reboot.
Expected
That's why I hedged on having something like "apparmor unload". What
you're saying explains why "restart" and "reload" are distinct actions
(I'd never been clear on this), so having a new action that is "like
'stop' but actually does stop apparmor, even though that is not usually
what you want"
A related issue: "/etc/init.d/apparmor stop" should invoke aa-
teardown(8). Depending on the semantics of the apparmor "service," this
could also be "/etc/init.d/apparmor unload" or the like. I was surprised
to find that "apparmor stop" was not actually unloading the profiles, as
I had assumed.
Thanks. I am in complete agreement.
I don't need (or even want) AppArmor to automagically update the kernel
state right after changing something under /etc/apparmor.d/, because
having to do a SIGHUP/restart/etc. is already normal practice. But I do
expect that a reboot/reload will take care of
Aaaand the upstream has decided they can't/won't fix this issue.
One thing that bothers me about this whole situation is that, in order
for background services like this one to be cleaned up after logout,
they need to behave "correctly." From my point of view, this is
backwards.
When the system
Hello John,
I did not take any specific action to unload a profile from the kernel.
Instead, I rebooted the system, under the assumption that this would
wipe the slate clean, with everything reloading cleanly from
/etc/apparmor.d/.
The new profile I developed was under a new filename, because I
Public bug reported:
My setup: office with two screens and a long cable to a TV screen in the
next room. The TV screen is off.
Error: Upon starting ubuntu, GDM shows only blank screens. When the TV
is unplugged, I can see the GDM login screen. Moving mouse pointer to
one of the screens in my
Public bug reported:
This concerns apparmor 2.13.3-7ubuntu5 in Ubuntu focal.
If I delete a profile from /etc/apparmor.d/, reboot the system, and then
look in /var/cache/apparmor/.0/, I still see a file for the
compiled form of the profile.
The same occurs if the profile is "deleted" by
Thanks for being on top of this, Sergio. I'm surprised that a LP search
for "boot_id" in this project did not turn up this existing bug report.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
Public bug reported:
This concerns apparmor 2.13.3-7ubuntu5 in Ubuntu focal.
I have AppArmor actively enforcing policy on my system. In
/var/log/syslog, I see a number of the following two sorts of messages:
May 12 04:44:21 image-ubuntu64 kernel: [ 26.667094] audit: type=1400
I have confirmed that the fix in -proposed fixes the issue for me.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to kmod in Ubuntu.
https://bugs.launchpad.net/bugs/1872863
Title:
QEMU/KVM display is garbled when booting
** Also affects: systemd via
https://github.com/systemd/systemd/issues/6077
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Tags removed: focal
** Summary changed:
- gnome-terminal unduly forces umask=0022
+ 'systemd --user' unduly forces umask=0022
** Changed in: gnome-terminal (Ubuntu)
Status: Confirmed => Invalid
** Changed in: dbus (Ubuntu)
Status: Confirmed => Invalid
** Changed in:
This issue persists in lightdm 1.30.0-0ubuntu3.1 in Ubuntu focal.
I see the warnings not only for pam_kwallet.so, but also its successor
pam_kwallet5.so, as well as pam_gnome_keyring.so (which I do not have
installed). All three of these are referenced in /etc/pam.d/lightdm and
1 - 100 of 526 matches
Mail list logo
