For anyone who finds this bug due to docker-compose no longer working,
and misses the last line of the original bug report about Compose v2,
the practical solution for most folks AFAICT will be to purge the
`docker-compose` package and install `docker-compose-v2`, and transition
to using the `docke
Public bug reported:
Hello Ubuntu PAM maintainers. I've noticed that while not fatal, there
are profile parsing errors when pam-auth-update encounters typical
comment lines as it attempts to treat each new line that isn't part of
another field as a $fieldname like so:
Use of uninitialized value
Public bug reported:
Working with pam-auth-update and custom profiles in /usr/share/pam-
configs I'm discovering a lack of flexibility with regard to ordering
and being able to cleanly stack different auth modules.
This relates to both unix and sss profiles using '[success=end
default=ignore]'.
+1 Ubuntu 20.04 LTS server
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1899218
Title:
Incorrect warning from apparmor_parser on force complained profiles
To manage notifications about this bug go
Apologies - I don't remember the full specifics here but IIRC, the
Mandiant FireEye HX agent foolishly re-implements Linux Audit, and it's
every bit as terrible as that sounds. We discovered that we needed to
basically purge both FireEye HX and Auditd on the system, then install
Auditd, then disab
Sadly it looks like both graphite-api and graphite-web have showstopper
breakage on Ubuntu 20.04. This sort of thing makes it hard to keep
operating systems on the current LTS if they need to do anything
important.
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
Perhaps this could be rebased on the working 1.16, and they could fix
the broken manpage details all at once.(graphite-manage syncdb vs
graphite-manage migrate...)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
*** This bug is a duplicate of bug 1824874 ***
https://bugs.launchpad.net/bugs/1824874
Actually, found the workaround in the other ticket for anyone else who finds
this via web search:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1824874/comments/12
ALT+F2, then type 'r' & hit
*** This bug is a duplicate of bug 1824874 ***
https://bugs.launchpad.net/bugs/1824874
This is wicked annoying. Anyone know what the actual element's process
is so that I can kill it without losing my Gnome session?
--
You received this bug notification because you are a member of Ubuntu
B
Public bug reported:
Audit package installation failure report via ABRT
ProblemType: Package
DistroRelease: Ubuntu 19.10
Package: auditd 1:2.8.5-2ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-51.44-generic 5.3.18
Uname: Linux 5.3.0-51-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.8
AptOrdering:
li
Hrm - any word on this one? We just hit it for 18.04 and it's a real
bummer because on hosts that it happens on for us, it happens every time
and we haven't figure out how to actually work around it. Purging
auditd and reinstalling errors in the same way every time.
--
You received this bug not
Here's what we see:
# apt-get install auditd
Reading package lists... Done
Building dependency tree
Reading state information... Done
Suggested packages:
audispd-plugins
The following NEW packages will be installed:
auditd
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
N
Public bug reported:
The code example in step 4, showing proxy-server.conf needs the
following change to result in a working Keystone-backed Swift
installation that makes average users able to interact with Swift as
desired.
-operator_roles = Member,admin,swiftoperator
+operator_roles = Member,ad
13 matches
Mail list logo
