I have the same problem. I try to do do-release-upgrade on my Ubuntu 22 but
fail because of gdm3... After force reboot my PC I start kernel recovery and
recovery my apt source.list using cp sources.list.distUpgrade sources.list Then
I start apt update and get message. I already waiting more than
This bug appears to have been fixed in 8.32.0-1ubuntu4. Looks like this
was an issue with the Apparmor profile.
rsyslog (8.32.0-1ubuntu4) bionic; urgency=medium
[ Jamie Strandboge ]
* debian/usr.sbin.rsyslogd: updates for bionic (LP: #1766600)
- allow rsyslog modules in multiarch director
Hi Brian,
This is actually the same issue.
I am seeing the same error message quoted by the original reporter, but
that message is filtered through systemd---it is not direct output from
rsyslogd. What I provided was the direct output, that actually shows
what's going on.
I think this needs to b
@Daniel Richard G. - that is a different error message please open a
separate bug report.
** Changed in: rsyslog (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: rsyslog (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766317
Title:
pa
I am seeing this same error in Bionic. Some further telemetry:
# /usr/sbin/rsyslogd -n
rsyslog internal message (3,-2066): could not load module
'/usr/lib/x86_64-linux-gnu/rsyslog/lmnet.so', dlopen:
/usr/lib/x86_64-linux-gnu/rsyslog/lmnet.so: failed to map segment from shared
object
[v8.32.0 t