You have been subscribed to a public bug:
Since last update the screen resolution is as it it was without graphic
acceleration
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-45-generic
You have been subscribed to a public bug:
I made a total reinstallation of ubuntu 20.04 thinking that this would solve
the problem, but it came back as soon as I applied all the updates.
I, then reinstalled again but with ubuntu 20.10 and the problem is still there.
ProblemType: Bug
Thanks for the bug report.
Firstly, you seem to have an AMD Radeon GPU, but the Nvidia driver is
installed. Please uninstall the Nvidia driver in case that is causing
problems.
Secondly, next time a crash happens please:
1. Wait 10 seconds
2. Reboot
3. Run this command: journalctl -b-1 >
** Package changed: ubuntu => xorg (Ubuntu)
--
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/1919412
Title:
display, resolution bug
Status in xorg package in Ubuntu:
New
** Package changed: ubuntu => xorg (Ubuntu)
--
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/1919407
Title:
display bug, incorrect resolution
Status in xorg package in
*** This bug is a duplicate of bug 1919285 ***
https://bugs.launchpad.net/bugs/1919285
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1919285, so it is being marked as such. Please
open-vm-tools fixed in
open-vm-tools (2:11.2.5-2ubuntu1) hirsute; urgency=medium
* d/p/fix-FTFBS-glib2.0-2.66.3.patch: fix FTBFS with glib2.0 >=2.66.3
-- Christian Ehrhardt Mon, 08
*** This bug is a duplicate of bug 1897965 ***
https://bugs.launchpad.net/bugs/1897965
** This bug has been marked a duplicate of bug 1897965
PulseAudio doesn't work when pipewire is installed (ie. KDE)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
> A temporary workaround for others experiencing this issue would be to run
> "systemctl edit
> systemd-logind" and enter the following:
>
> [Service]
> RestrictAddressFamilies=AF_INET
> IPAddressAllow=any
it sounds like your problem isn't the /etc/shadow issue, it's due to
systemd-logind
** Description changed:
+ [impact]
+
+ if a non-template service file is created as a symlink to a template
+ service file outside the normal unit file paths, systemd will fail
+ assertion and crash
+
+ [test case]
+
+ su -
+ cat < /crashsystemd@.service
+ [Unit]
+ Description=Template for
** Changed in: systemd (Ubuntu Groovy)
Assignee: Dan Streetman (ddstreet) => (unassigned)
** Changed in: systemd (Ubuntu Focal)
Assignee: Dan Streetman (ddstreet) => (unassigned)
** Changed in: systemd (Ubuntu Groovy)
Status: In Progress => Incomplete
** Changed in: systemd
** Tags removed: ddstreet
--
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/1823171
Title:
systemd-resolve hides DS records in explicit queries
Status in systemd package in
** Changed in: systemd (Ubuntu)
Status: Confirmed => Incomplete
--
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/1853669
Title:
systemd resolves own hostname to link
*** This bug is a duplicate of bug 1880258 ***
https://bugs.launchpad.net/bugs/1880258
** This bug has been marked a duplicate of bug 1880258
Add trailing dot to make connectivity-check.ubuntu.com. absolute and reduce
NXDOMAIN warning noise
--
You received this bug notification because
For the systemd packages, this is better fixed by Debian and then inherited by
Ubuntu, and there is Debian MR to do this:
https://salsa.debian.org/systemd-team/systemd/-/merge_requests/121
Once that's merged, Ubuntu will pick it up in the next release.
For other packages that create user
** Tags removed: ddstreet
--
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/1858210
Title:
timedatectl doesn't list all timezones
Status in systemd package in Ubuntu:
*** This bug is a duplicate of bug 1919285 ***
https://bugs.launchpad.net/bugs/1919285
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1919285, so it is being marked as such. Please
Public bug reported:
I've been getting freezes on Ubunyu 20.04 on my Dell Latitude 7420
laptop with a secondary display connected through a WD19 Dell dock. I'm
on the supposedly-certified 5.6.0-1048-oem kernel, have tried 5.8 and
5.10 without much success (other types of freezes). Some freezes
Hi, any sign that this issue is being looked at?
--
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/1913940
Title:
Wifi keeps disconnecting and reconnecting all the time
Status
@William, thanks for the work. Some of those patches are 'forwarded:
no', anything blocking upstreaming the fixes? That would be preferable
to do before upload because experience from the previous SRU round
showed it's likely to not happen otherwise
--
You received this bug notification because
** Summary changed:
- Xorg freeze
+ System freeze
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Package changed: linux (Ubuntu) => linux-oem-5.6 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in
--- Comment From heinz-werner_se...@de.ibm.com 2021-03-17 08:12 EDT---
IBM bugzilla status-> closed, workaround available, upstream activitiy by
Canonical.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
Also is the correct version 5.53-0ubuntu3.1 ?
--
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/1903048
Title:
[SRU] Bluetooth won't activate on the pi 400
Status in bluez
This bug was fixed in the package mesa - 21.0.0-1
---
mesa (21.0.0-1) experimental; urgency=medium
* New upstream release. (LP: #1917763)
* control: Add directx-headers-dev to build-depends for amd64 and arm64
on Linux, which is what WSL2 currently supports.
-- Timo
> Kernel says: x [1266..5678], y [1162..4694]
> Touchpad sends: x [1266..5678], y [1161..4694] -^C
unless I'm reading that wrong, the kernel reports exactly the same range
as the touchpad sends, so there should be no need for the hwdb to carry
x/y values overridding the kernel-reported ranges
In
opened Debian MR
https://salsa.debian.org/systemd-team/systemd/-/merge_requests/122
** Changed in: systemd (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Description changed:
[impact]
if a non-template service file is created as a symlink to a template
service file outside the normal unit file paths, systemd will fail
assertion and crash
[test case]
su -
cat < /crashsystemd@.service
[Unit]
Description=Template for
I mean one of the header files is referencing another header file using the
wrong path
On Tue, 9 Mar 2021 at 10:20, Matthias Klose <1899...@bugs.launchpad.net>
wrote:
> this is correct behavior. The headers are searched in
> /usr/include/python3.8
>
>
> ** Package changed: gcc-defaults (Ubuntu)
** Merge proposal linked:
https://code.launchpad.net/~ddstreet/ubuntu/+source/systemd/+git/systemd/+merge/399820
--
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/1887744
Given that the logind issue is an AppArmor issue and, per my previous
comment, "the two running jobs are systemd-logind.service and
snapd.seeded.service", I suspect that we'll find that snapd is running
into similar sorts of issues. I'll take a quick look now.
--
You received this bug
FWIW I know what the snapd issue is, the issue is that snapd does not
and will not work in a nested LXD container, we need to add code to make
snapd.seeded.service die/exit gracefully in this situation.
** Also affects: snapd
Importance: Undecided
Status: New
** Changed in: snapd
Yep, that's what I've found; cloud-init is just waiting for its later
stages to run, which are blocked by snapd.seeded.service exiting.
** Changed in: cloud-init
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
marking as invalid since the user 'systemd-timesync' is reserved for use
by systemd, so this is a local configuration issue
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
> adduser: The user `systemd-timesync' already exists, but is not a
system user. Exiting.
something created a user named 'systemd-timesync' on your system, which
is a username that systemd in focal reserves for its own use, so the
upgrade failed. You should remove your 'systemd-timesync' user to
as Debian/Ubuntu inherit the mount unit from upstream, this would
probably be best proposed there first, unless there is some compelling
reason that Debian and/or Ubuntu should diverge behavior with upstream
for debugfs.
--
You received this bug notification because you are a member of Ubuntu
it's interesting that apparmor appears to work ok in the first-level
container, but fails in the nested container, e.g.:
$ lxc shell lp1905493-f
root@lp1905493-f:~# systemctl status apparmor
● apparmor.service - Load AppArmor profiles
Loaded: loaded (/lib/systemd/system/apparmor.service;
This bug was fixed in the package cron - 3.0pl1-136ubuntu2
---
cron (3.0pl1-136ubuntu2) hirsute; urgency=medium
* d/p/f/inherit-path.patch: Add -P option to inherit PATH from environment,
thanks to Tom Jones for the patch (Closes: #688716)
* Inherit PATH by default (LP:
I wonder if this is actually a problem with the specific apparmor
profile that's created by lxd, maybe it doesn't provide enough
permissions to allow the container's lxd to correctly pass the apparmor
profile down to the nested container. Similar to how lxd locks down
containers a bit too tight by
@seb128 it turns out Dave had already forwarded the patches, so I
included the URLs in this new debdiff
@vanvugt I set the version to ubuntu3.1 rather than ubuntu4
** Patch added: "Focal SRU"
The systemd-logind problem is due to dbus defaulting to apparmor mode
'enabled', but apparmor can't do much of anything inside a container so
it fails to start, and dbus can't contact it.
In the 2nd level container, create a file like '/etc/dbus-1/system.d/no-
apparmor.conf' with content:
As I mentioned in my last comment, I'm skeptical that the benefit of
backporting would outweigh the potential problems it would introduce to
existing stable releases.
I'm marking this as wont-fix for that reason. I don't think we should
consider this unless you can provide specific examples of
for reference, the PR linked in the description is included upstream in
v247 so this is fixed in h, i'll mark the bug as such
** Also affects: systemd (Ubuntu Hirsute)
Importance: Undecided
Status: Confirmed
** Also affects: systemd (Ubuntu Focal)
Importance: Undecided
marking as invalid as this appears to be a misconfiguration or other
issue localized to your specific system
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
** Changed in: systemd (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: tracker (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tracker in Ubuntu.
Hello,
Still have this issue ... could anyone help/investigate please?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1913977
Title:
Bad sound quality (no bass) on
45 matches
Mail list logo
