[Bug 1707431] Re: package gdnsd 2.2.0-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Changed in: gdnsd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1707431 Title: package gdnsd 2.2.0-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdnsd/+bug/1707431/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1636926] Re: package gdnsd 1.11.1-1 [modified: usr/bin/gdnsd_geoip_test usr/sbin/gdnsd usr/share/doc/gdnsd/README.md] failed to install/upgrade: subprocess installed post-installation script retu
** Changed in: gdnsd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1636926 Title: package gdnsd 1.11.1-1 [modified: usr/bin/gdnsd_geoip_test usr/sbin/gdnsd usr/share/doc/gdnsd/README.md] failed to install/upgrade: subprocess installed post-installation script returned error exit status 139 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdnsd/+bug/1636926/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1633806] Re: package gdnsd 1.11.1-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Changed in: gdnsd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1633806 Title: package gdnsd 1.11.1-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdnsd/+bug/1633806/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
** Changed in: linux (Ubuntu) Assignee: Phan Thanh Long (phanlong2811) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 To manage notifications about this bug go to: https://bugs.launchpad.net/pop-os/+bug/1887190/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908777] Re: Typoed digits are not working
** Changed in: tuxmath (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908777 Title: Typoed digits are not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tuxmath/+bug/1908777/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907978] Re: Nemo 4.4.2 Capital letters in path not working
** Changed in: nemo (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907978 Title: Nemo 4.4.2 Capital letters in path not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nemo/+bug/1907978/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907880] Re: Mistakes in French translation.
** Changed in: mtpaint (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907880 Title: Mistakes in French translation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mtpaint/+bug/1907880/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914889] Re: dns timeout didn't result in tempfail
I agree with your analysis. I don’t know how to reproduce this, it is probably best to report the bug to the upstream project. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914889 Title: dns timeout didn't result in tempfail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opendkim/+bug/1914889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914374] Re: Multiple issues on HP ZBook 15 G7 after installing 20.04.2 image
This bug was fixed in the package ubuntu-drivers-common - 1:0.8.6.5 --- ubuntu-drivers-common (1:0.8.6.5) hirsute; urgency=medium * tests/test_ubuntu_drivers.py: - Add testcase for list-oem --package-list. * UbuntuDrivers/detect.py: - Fix the way we validate the nvidia modules metapackages (LP: #1914374). -- Alberto Milone Wed, 03 Feb 2021 19:13:21 +0100 ** Changed in: ubuntu-drivers-common (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914374 Title: Multiple issues on HP ZBook 15 G7 after installing 20.04.2 image To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1914374/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914051] Re: `ubuntu-drivers list-oem --package-list` is broken
This bug was fixed in the package ubuntu-drivers-common - 1:0.8.6.5 --- ubuntu-drivers-common (1:0.8.6.5) hirsute; urgency=medium * tests/test_ubuntu_drivers.py: - Add testcase for list-oem --package-list. * UbuntuDrivers/detect.py: - Fix the way we validate the nvidia modules metapackages (LP: #1914374). -- Alberto Milone Wed, 03 Feb 2021 19:13:21 +0100 ** Changed in: ubuntu-drivers-common (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914051 Title: `ubuntu-drivers list-oem --package-list` is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1914051/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913651] Re: /usr/bin/ubuntu-drivers:PermissionError:/usr/bin/ubuntu-drivers@480:__call__:main:invoke:invoke:invoke:new_func:invoke:autoinstall:command_install
This bug was fixed in the package ubuntu-drivers-common - 1:0.8.6.5 --- ubuntu-drivers-common (1:0.8.6.5) hirsute; urgency=medium * tests/test_ubuntu_drivers.py: - Add testcase for list-oem --package-list. * UbuntuDrivers/detect.py: - Fix the way we validate the nvidia modules metapackages (LP: #1914374). -- Alberto Milone Wed, 03 Feb 2021 19:13:21 +0100 ** Changed in: ubuntu-drivers-common (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913651 Title: /usr/bin/ubuntu-drivers:PermissionError:/usr/bin/ubuntu- drivers@480:__call__:main:invoke:invoke:invoke:new_func:invoke:autoinstall:command_install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1913651/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912835] Re: ESP should be fscked
This bug was fixed in the package livecd-rootfs - 2.711 --- livecd-rootfs (2.711) hirsute; urgency=medium * Perform fsck on all rootfs. (LP: #1912835) * functions: stop removing systemd-detect-virt unconditionally in undivert_grub (LP: #1902260) -- Dimitri John Ledkov Fri, 05 Feb 2021 12:48:44 + ** Changed in: livecd-rootfs (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912835 Title: ESP should be fscked To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1912835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902260] Re: systemd-detect-virt is missing on Groovy EC2 AMI
This bug was fixed in the package livecd-rootfs - 2.711 --- livecd-rootfs (2.711) hirsute; urgency=medium * Perform fsck on all rootfs. (LP: #1912835) * functions: stop removing systemd-detect-virt unconditionally in undivert_grub (LP: #1902260) -- Dimitri John Ledkov Fri, 05 Feb 2021 12:48:44 + ** Changed in: livecd-rootfs (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902260 Title: systemd-detect-virt is missing on Groovy EC2 AMI To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1902260/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902483] Re: Sparse file not allowed (on btrfs), 20.04
** Changed in: grub2 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902483 Title: Sparse file not allowed (on btrfs), 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1902483/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914911] [NEW] bluefs doesn't compact log file
Public bug reported:
For a certain type of workload, the bluefs might never compact the log file,
which would cause the bluefs log file slowly grows to a huge size
(some bigger than 1TB for a 1.5T device).
This bug could eventually cause osd crash and failed to restart as it couldn't
get through the bluefs replay phase during boot time.
We might see below log when trying to restart the osd:
bluefs mount failed to replay log: (5) Input/output error
There are more details in the bluefs perf counters when this issue happened:
e.g.
"bluefs": {
"gift_bytes": 811748818944,
"reclaim_bytes": 0,
"db_total_bytes": 888564350976,
"db_used_bytes": 867311747072,
"wal_total_bytes": 0,
"wal_used_bytes": 0,
"slow_total_bytes": 0,
"slow_used_bytes": 0,
"num_files": 11,
"log_bytes": 866545131520,
"log_compactions": 0,
"logged_bytes": 866542977024,
"files_written_wal": 2,
"files_written_sst": 3,
"bytes_written_wal": 32424281934,
"bytes_written_sst": 25382201
}
As we can see the log_compactions is 0, which means it's never compacted and
the log file size(log_bytes) is already 800+G. After the compaction, the log
file size would reduced to around
1 G
Here is the PR[1] that addressed this bug, we need to backport this to ubuntu
12.2.13
[1] https://github.com/ceph/ceph/pull/17354
** Affects: ceph (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1914911
Title:
bluefs doesn't compact log file
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1914911/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914769] Re: Kubuntu 20.04 USB boot disk fails
It turns out this is because of a broken USB stick. Working while using Ubuntu Studio, breaking somewhere in the process of 'burning' Kubuntu. With a new USB, installation works as expected. ** Changed in: kubuntu-meta (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914769 Title: Kubuntu 20.04 USB boot disk fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1914769/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914769] Re: Kubuntu 20.04 USB boot disk fails
Not sure if 'invalid' or 'fix released' fits better, for now marking this as invalid. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914769 Title: Kubuntu 20.04 USB boot disk fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1914769/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914913] [NEW] package nodejs 10.19.0~dfsg-3ubuntu1 failed to install/upgrade: installed nodejs package pre-removal script subprocess returned error exit status 2
Public bug reported: error while purging nodejs file ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nodejs 10.19.0~dfsg-3ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Feb 7 16:15:36 2021 DuplicateSignature: package:nodejs:10.19.0~dfsg-3ubuntu1 Removing nodejs (10.19.0~dfsg-3ubuntu1) ... update-alternatives: error: cannot stat file '/usr/bin/nodejs': Too many levels of symbolic links dpkg: error processing package nodejs (--remove): installed nodejs package pre-removal script subprocess returned error exit status 2 ErrorMessage: installed nodejs package pre-removal script subprocess returned error exit status 2 InstallationDate: Installed on 2021-02-05 (1 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: nodejs Title: package nodejs 10.19.0~dfsg-3ubuntu1 failed to install/upgrade: installed nodejs package pre-removal script subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nodejs (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914913 Title: package nodejs 10.19.0~dfsg-3ubuntu1 failed to install/upgrade: installed nodejs package pre-removal script subprocess returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nodejs/+bug/1914913/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914914] [NEW] grub not installed in mbr
Public bug reported: installation went smoothly until grub ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubiquity 20.10.13 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 NonfreeKernelModules: wl zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.455 Date: Sun Feb 7 10:24:41 2021 InstallCmdLine: BOOT_IMAGE=(loop)/casper/vmlinuz root=UUID=7BC3-D6B9 iso-scan/filename=/xubuntu-20.10-desktop-amd64.iso file=/cdrom/preseed/xubuntu.seed noprompt quiet splash --- maybe-ubiquity debian-installer/language=en keyboard-configuration/layoutcode?=fr keyboard-configuration/variantcode?=oss LiveMediaBuild: Xubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) RebootRequiredPkgs: linux-image-5.8.0-25-generic linux-base SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy ubiquity-20.10.13 xubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914914 Title: grub not installed in mbr To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1914914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914913] Re: package nodejs 10.19.0~dfsg-3ubuntu1 failed to install/upgrade: installed nodejs package pre-removal script subprocess returned error exit status 2
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914913 Title: package nodejs 10.19.0~dfsg-3ubuntu1 failed to install/upgrade: installed nodejs package pre-removal script subprocess returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nodejs/+bug/1914913/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848923] Re: pollinate.service fails to start: ERROR: should execute as the [pollinate] user
Thanks Christian! Interesting, the "ERROR: should execute as the
[pollinate] user" looks quite unrelated to any networking setup and
smelled like a package postinst/systemd unit bug.
I started trying to reproduce this outside of the Ubuntu CI, with a most
naïve
curl -O
https://cloud-images.ubuntu.com/daily/server/groovy/current/groovy-server-cloudimg-amd64.img
curl -O
https://github.com/cockpit-project/bots/raw/master/machine/cloud-init.iso
qemu-system-x86_64 -enable-kvm -nographic -m 2048 -device virtio-rng-pci
-drive file=groovy-server-cloudimg-amd64.img,if=virtio -snapshot -cdrom
cloud-init.iso
(that cloud-init is nothing special, just to get root:foobar and
admin:foobar accounts, see [1])
But this fails to start ssh.service, and neither does it actually run
cloud-init, so there is no way to log in and examine further. But indeed
it seems to have started pollinate:
[ OK ] Finished Pollinate to seed…seudo random number generator.
Starting OpenBSD Secure Shell server...
[ OK ] Started Dispatcher daemon for systemd-networkd.
[FAILED] Failed to start OpenBSD Secure Shell server.
See 'systemctl status ssh.service' for details.
Our CI uses libvirt for everything, which of course makes a CLI
reproducer a lot more difficult. It's fairly easy when actually using
our python wrappers:
git clone https://github.com/cockpit-project/bots/
bots/vm-run ubuntu-stable
(log in as root:foobar)
This downloads the actual image to ~/.cache/cockpit-images and creates a
transient domain with a transient overlay. I attach the `virsh dumpxml`
output, but of course that has a lot of absolute file system paths in
it, UUIDs, and other junk that is specific to my system.
There the pollinate user exists
# id pollinate
uid=111(pollinate) gid=1(daemon) groups=1(daemon)
# systemctl cat pollinate
[..]
[Service]
User=pollinate
ExecStart=/usr/bin/pollinate
Type=oneshot
which looks right.
I edited the systemd unit to run pollinate through /bin/sh -ex, and that did
reveal something:
Feb 07 09:24:10 ubuntu sh[2449]: + set -e
Feb 07 09:24:10 ubuntu sh[2449]: + set -f
Feb 07 09:24:10 ubuntu sh[2449]: + PKG=pollinate
Feb 07 09:24:10 ubuntu sh[2450]: + mktemp -d -t pollinate.
Feb 07 09:24:10 ubuntu sh[2449]: + TMPDIR=/tmp/pollinate.77BPmzGSfzFm
Feb 07 09:24:10 ubuntu sh[2449]: + trap rm -rf /tmp/pollinate.77BPmzGSfzFm
2>/dev/null || true EXIT HUP INT QUIT TERM
Feb 07 09:24:10 ubuntu sh[2449]: + CACHEDIR=/var/cache/pollinate
Feb 07 09:24:10 ubuntu sh[2449]: + FLAG=/var/cache/pollinate/seeded
Feb 07 09:24:10 ubuntu sh[2449]: + LOG=/var/cache/pollinate/log
Feb 07 09:24:10 ubuntu sh[2451]: + hostname
Feb 07 09:24:10 ubuntu sh[2449]: + HOSTNAME=ubuntu
Feb 07 09:24:10 ubuntu sh[2449]: + STRICT=0
Feb 07 09:24:10 ubuntu sh[2453]: + logger -V
Feb 07 09:24:10 ubuntu sh[2454]: + awk {print $4}
Feb 07 09:24:10 ubuntu sh[2449]: + logger_ver=2.36
Feb 07 09:24:10 ubuntu sh[2449]: + dpkg --compare-versions 2.36 ge 2.26.2
Feb 07 09:24:10 ubuntu sh[2449]: + LOGGER=logger --id=2449
Feb 07 09:24:10 ubuntu sh[2449]: + [ -t 0 ]
Feb 07 09:24:10 ubuntu sh[2449]: + [ -r /etc/default/pollinate ]
Feb 07 09:24:10 ubuntu sh[2449]: + . /etc/default/pollinate
Feb 07 09:24:10 ubuntu sh[2449]: + BINARY=1
Feb 07 09:24:10 ubuntu sh[2449]: + QUIET=0
Feb 07 09:24:10 ubuntu sh[2449]: + WAIT=10
Feb 07 09:24:10 ubuntu sh[2449]: + DEVICE=/dev/urandom
Feb 07 09:24:10 ubuntu sh[2449]: + SERVER=https://entropy.ubuntu.com/
Feb 07 09:24:10 ubuntu sh[2449]: + POOL=
Feb 07 09:24:10 ubuntu sh[2449]: + CURL_OPTS=--cacert
/etc/pollinate/entropy.ubuntu.com.pem --capath /dev/null
Feb 07 09:24:10 ubuntu sh[2449]: + [ ! -z ]
Feb 07 09:24:10 ubuntu sh[2449]: + [ -z ]
Feb 07 09:24:10 ubuntu sh[2449]: + [ ! -w /var/cache/pollinate ]
Feb 07 09:24:10 ubuntu sh[2449]: + error should execute as the [pollinate] user
Feb 07 09:24:10 ubuntu sh[2449]: + logger --id=2449 -t pollinate ERROR: should
execute as the [pollinate] user
/var/cache/pollinate indeed does not exist.
I added
CacheDirectory=pollinate
to the systemd unit, and that fixes it.
[1] https://github.com/cockpit-project/bots/blob/master/machine/make-
cloud-init-iso
** Attachment added: "virsh dumpxml"
https://bugs.launchpad.net/ubuntu/+source/pollinate/+bug/1848923/+attachment/5461032/+files/ubuntu-2004.xml
** Summary changed:
- pollinate.service fails to start: ERROR: should execute as the [pollinate]
user
+ pollinate.service fails to start: ERROR: should execute as the [pollinate]
user -- missing CacheDirectory=
** Changed in: pollinate (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848923
Title:
pollinate.service fails to start: ERROR: should execute as the
[pollinate] user -- missing CacheDirectory=
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pollinate/+bug/18489
[Bug 1914915] [NEW] Sound or Audio is breaking
Public bug reported: When I am watching videos sound is breaking ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.10 ProcVersionSignature: hostname 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: balashanmugam 1437 F pulseaudio CasperMD5CheckResult: skip Date: Sun Feb 7 15:27:47 2021 InstallationDate: Installed on 2021-02-05 (1 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) ProcEnviron: LANGUAGE=en_IN:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2020 dmi.bios.vendor: VMware, Inc. dmi.bios.version: VMW71.00V.16722896.B64.2008100651 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnVMware,Inc.:bvrVMW71.00V.16722896.B64.2008100651:bd08/10/2020:svnVMware,Inc.:pnVMware7,1:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware7,1 dmi.product.version: None dmi.sys.vendor: VMware, Inc. ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914915 Title: Sound or Audio is breaking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1914915/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914914] Re: grub not installed in mbr
** Package changed: ubiquity (Ubuntu) => grub-installer (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914914 Title: grub not installed in mbr To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1914914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881473] Re: printer communication error
Yes, similar issue. 2x fresh installs of 20.04.1. Using a Brother MFC-J890DW, and trying to connect USB. Keep getting 'several printers' automatically created, but generally don't work, and appear not to be USB. Scanning is also hit and miss. Have tried using automatically created printers, and also installing the Brother drivers. Sometimes works, (via network mostly), but after a reboot, broken again. Uninstall/reinstall. Used to 'just work'. Last OS was an older version of Mint. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881473 Title: printer communication error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1881473/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895896] Re: HP Officejet Pro 6830 can not be connected via USB
Similar issue with Brother MFC-J890DW. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895896 Title: HP Officejet Pro 6830 can not be connected via USB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1895896/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914915] Re: Sound or Audio is breaking
Try setting the system into performance mode. https://www.cult-of-tech.net/2018/08/linux-ubuntu-cpu-power-frequency- scaling -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914915 Title: Sound or Audio is breaking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1914915/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892276] Re: thumbnails stretched on desktop 20.04 after previous bug fix release
Confirm htd95's fileItem.js fixes this for me on newly upgraded Ubuntu 20.04.2. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892276 Title: thumbnails stretched on desktop 20.04 after previous bug fix release To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1892276/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914917] [NEW] trackpad not recognised
Public bug reported: I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0 U: Uniq= H: Handlers=kbd event0 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input1 U: Uniq= H: Handlers=event1 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0003 Version= N: Name="Sleep Button" P: Phys=PNP0C0E/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=4000 0 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3 U: Uniq= H: Handlers=kbd event3 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab41 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input4 U: Uniq= H: Handlers=sysrq kbd event4 leds B: PROP=0 B: EV=120013 B: KEY=1 c0200 0 0 700f0203 3802078f870f401 febfffdfffef fffe B: MSC=10 B: LED=7 I: Bus=0019 Vendor= Product= Version= N: Name="Acer WMI hotkeys" P: Phys=wmi/input0 S: Sysfs=/devices/virtual/input/input5 U: Uniq= H: Handlers=rfkill kbd event5 B: PROP=0 B: EV=13 B: KEY=1c 0 0 0 0 160080c00 30 10 0 B: MSC=10 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input6 U: Uniq= H: Handlers=kbd event6 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Front Headphone" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1b.0/sound/card0/input7 U: Uniq= H: Handlers=event7 B: PROP=0 B: EV=21 B: SW=4 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=3" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1b.0/sound/card0/input8 U: Uniq= H: Handlers=event8 B: PROP=0 B: EV=21 B: SW=140 I: Bus=0003 Vendor=1241 Product= Version=0100 N: Name="HID 1241:" P: Phys=usb-:00:14.0-2/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-2/1-2:1.0/0003:1241:.0001/input/input9 U: Uniq= H: Handlers=mouse0 event9 B: PROP=0 B: EV=17 B: KEY=7 0 0 0 0 B: REL=903 B: MSC=10 I: Bus=0003 Vendor=064e Product=9404 Version=0100 N: Name="VGA Webcam: VGA Webcam" P: Phys=usb-:00:14.0-4/button S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/input/input10 U: Uniq= H: Handlers=kbd event10 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-41-generic 5.8.0-41.46~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Feb 7 11:15:17 2021 InstallationDate: Installed on 2021-02-07 (0 days ago) InstallationMedia: Xubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.8 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914917 Title: trackpad not recognised To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1914917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914918] [NEW] The snap being updated in the background causes both old and new tabs to die to SIGTRAP
Public bug reported: The last few background updates of chromium have made some old tabs suddenly crash with SIGTRAP and it also makes it impossible to open new tabs, those die instantly with a SIGTRAP as well. This is incredibly destructive to whatever might be the dying tabs' unsaved state and there's no warning about it. Yet again a snap-related change rolled out to users with absolutely amateur-tier testing. Ubuntu: 20.04.2 Snap: 2.48+20.04 Chromium: 88.0.4324.150 ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914918 Title: The snap being updated in the background causes both old and new tabs to die to SIGTRAP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1914918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777708] Re: Desktop briefly becomes unresponsive when typing on 2 keyboards at the same time
Hi :) I also have the R-Go Tools Split keyboard and is having the exact same issue no Ubuntu 20.04. I also had the same issue on Ubuntu 18.04. But I found a way to fix it. If I change the display server from X11/Xorg to Wayland then the problem goes away! :D I just followed this guide: https://linuxconfig.org/how-to-enable-disable-wayland-on- ubuntu-20-04-desktop?fbclid =IwAR1yAApu1CItCAnngvHbZgCta1WzY718qk8dqdRXJdVkclm-_xWbOFDGmAw So my suspection is that this is a problem with the default display server in Ubuntu. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/108 Title: Desktop briefly becomes unresponsive when typing on 2 keyboards at the same time To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/108/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914860] Re: /usr/bin/ldd no longer work in package libc-bin 2.33-0ubuntu1
fixed in -proposed ** Changed in: glibc (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914860 Title: /usr/bin/ldd no longer work in package libc-bin 2.33-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1914860/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914920] [NEW] package base-files 11ubuntu5 failed to install/upgrade: new base-files package pre-installation script subprocess returned error exit status 127
Public bug reported: Update after new installation get error ProblemType: Package DistroRelease: Ubuntu 20.04 Package: base-files 11ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Feb 7 12:58:18 2021 ErrorMessage: new base-files package pre-installation script subprocess returned error exit status 127 InstallationDate: Installed on 2021-02-07 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: base-files Title: package base-files 11ubuntu5 failed to install/upgrade: new base-files package pre-installation script subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: base-files (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914920 Title: package base-files 11ubuntu5 failed to install/upgrade: new base-files package pre-installation script subprocess returned error exit status 127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1914920/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914919] [NEW] UC20 initrd misses modules to boot from USB disk
Public bug reported: Trying to use a default USB boot on a Raspberry Pi using either an USB3 UAS SSD enclosure or even a simple USB 2 stick fails (due to the missing console output it simply hangs indefinitely with a black screen https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1914608). seemingly neither the usb_storage module nor uas, enclosure or required scsi drivers are included in the initrd, this makes using the UC20 images with a fast USB3 disk impossible. ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Description changed: Trying to use a default USB boot on a Raspberry Pi using either an USB3 UAS SSD enclosure or even a simple USB 2 stick fails (due to the missing - console output it simply hangs indefinitely with a black screen). + console output it simply hangs indefinitely with a black screen + LP#1914608 ). seemingly neither the usb_storage module nor uas, enclosure or required scsi drivers are included in the initrd, this makes using the UC20 images with a fast USB3 disk impossible. ** Description changed: Trying to use a default USB boot on a Raspberry Pi using either an USB3 UAS SSD enclosure or even a simple USB 2 stick fails (due to the missing - console output it simply hangs indefinitely with a black screen - LP#1914608 ). + console output it simply hangs indefinitely with a black screen #1914608 + ). seemingly neither the usb_storage module nor uas, enclosure or required scsi drivers are included in the initrd, this makes using the UC20 images with a fast USB3 disk impossible. ** Description changed: Trying to use a default USB boot on a Raspberry Pi using either an USB3 UAS SSD enclosure or even a simple USB 2 stick fails (due to the missing - console output it simply hangs indefinitely with a black screen #1914608 - ). + console output it simply hangs indefinitely with a black screen + https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1914608). seemingly neither the usb_storage module nor uas, enclosure or required scsi drivers are included in the initrd, this makes using the UC20 images with a fast USB3 disk impossible. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914919 Title: UC20 initrd misses modules to boot from USB disk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1914919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1656836] Re: No more keyboard shortcut for inserting the date?
** Changed in: gnote Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1656836 Title: No more keyboard shortcut for inserting the date? To manage notifications about this bug go to: https://bugs.launchpad.net/gnote/+bug/1656836/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914920] Re: package base-files 11ubuntu5 failed to install/upgrade: new base-files package pre-installation script subprocess returned error exit status 127
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914920 Title: package base-files 11ubuntu5 failed to install/upgrade: new base-files package pre-installation script subprocess returned error exit status 127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1914920/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914860] Re: /usr/bin/ldd no longer work in package libc-bin 2.33-0ubuntu1
** Bug watch added: Debian Bug tracker #982203 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982203 ** Also affects: glibc (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982203 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914860 Title: /usr/bin/ldd no longer work in package libc-bin 2.33-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1914860/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914922] [NEW] my resolv.conf file was pointing to the wrong place
Public bug reported: ❯ ls -l /etc/resolv.conf lrwxrwxrwx 1 root root 39 Feb 1 11:03 /etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.conf Linux zabbixproxy 5.4.0-1028-raspi #31-Ubuntu SMP PREEMPT Wed Jan 20 11:30:45 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: resolvconf (not installed) ProcVersionSignature: Ubuntu 5.4.0-1028.31-raspi 5.4.78 Uname: Linux 5.4.0-1028-raspi aarch64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: arm64 CasperMD5CheckResult: skip Date: Sun Feb 7 12:07:02 2021 ImageMediaBuild: 20210201.1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/usr/bin/zsh SourcePackage: resolvconf UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: resolvconf (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 focal uec-images -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914922 Title: my resolv.conf file was pointing to the wrong place To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1914922/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914925] [NEW] instalation of 20.10 using USB post install GRUB instal failed
Public bug reported: Tried many times. Tried re-downloading and installing ios on SDCard. Tried 2 x new SDCards, tried to fix with Boot Repair post install... always the same. PC uses Rampage V board set to only UEFI, no security and no fast boot as instructed on Ubuntu Forum ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubiquity 20.10.13 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.455 Date: Sun Feb 7 12:32:01 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) RebootRequiredPkgs: linux-image-5.8.0-41-generic linux-base linux-image-5.8.0-25-generic linux-base SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy ubiquity-20.10.13 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914925 Title: instalation of 20.10 using USB post install GRUB instal failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1914925/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 195982] Re: Shift key (and caps lock) stop working when using VMWare
Wow, I did not expect this bug from 2008 to resurface in 2021! To quote myself in 2008: > As I'm using the free version of vmware, I can live with it until: > 1. They fix it > 2. VirtualBox becomes stable enough to use #2 happened many *many* years ago, so I can no longer test this issue, that was never really resolved beyond the sort-of-workaround with setxkbmap in over 12 years... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/195982 Title: Shift key (and caps lock) stop working when using VMWare To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/195982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914109] Re: gcc-7: Internal compiler error: Error reporting routines re-entered
it's an ICE on illegal-code. It doesn't ICE with GCC 8 in bionic.
Unlikely to be fixed in bionic, and also fixed in focal and newer
versions.
$ g++-8 -c -std=c++17 minimized.cc
minimized.cc: In function ‘void a()’:
minimized.cc:46:31: warning: ISO C++ forbids converting a string constant to
‘char*’ [-Wwrite-strings]
y(0, 0, "", an, x::t, {});
^
minimized.cc: In instantiation of ‘y::y(int, char, s, y::aj, x, int)
[with ah = {double}; y::aj = I]:: [with auto:1 = b<0>]’:
minimized.cc:31:6: required from ‘void u(m, v) [with v =
y::y(int, char, s, y::aj, x, int) [with ah = {double}; y::aj =
I]::; w = long int; w ...af = {0}]’
minimized.cc:37:6: required from ‘y::y(int, char, s, y::aj, x, int)
[with ah = {double}; y::aj = I]’
minimized.cc:46:31: required from here
minimized.cc:39:15: error: ‘’ has incomplete type
int{[&](J) {}};
^
minimized.cc:29:27: note: declaration of ‘class J’
template class J;
^
minimized.cc:39:7: error: cannot convert ‘y::y(int, char, s, y::aj, x,
int) [with ah = {double}; y::aj = I]:: [with auto:1 =
b<0>]::)>’ to ‘int’ in initialization
int{[&](J) {}};
^~~
** Changed in: gcc-7 (Ubuntu)
Status: New => Fix Released
** Changed in: gcc
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1914109
Title:
gcc-7: Internal compiler error: Error reporting routines re-entered
To manage notifications about this bug go to:
https://bugs.launchpad.net/gcc/+bug/1914109/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914928] [NEW] GenericReceiveOffload in .link file ignored by systemd-networkd
Public bug reported: All of the following match options: [Match] #Type=vxlan #Driver=vxlan Path=* [Link] GenericReceiveOffload=off lead to: ethtool -k vxlan2009 |grep generic-receive generic-receive-offload: on I would expect the the option to be off. IDX LINK TYPE OPERATIONAL SETUP 1 lo loopback carrier unmanaged 25 vxlan2009 vxlancarrier configured 26 vxlan2009.0099 vlan carrier configured vxlan2009.netdev: [NetDev] Name=vxlan2009 Kind=vxlan MTUBytes=8950 [VXLAN] Id=2009 Group=239.1.1.43 MacLearning=1 DestinationPort=4789 vxlan2009.network: [Match] Name = vxlan2009 [Link] MTUBytes = 8950 [Network] VLAN=vxlan2009.0099 DHCP = no LinkLocalAddressing = no ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.4 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Feb 7 13:47:30 2021 MachineType: QEMU Standard PC (Q35 + ICH9, 2009) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-65-generic root=UUID=97786d27-c04a-4592-a087-f19a689468a9 ro console=tty1 console=ttyS0 SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2020-08-27 (163 days ago) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.13.0-48-gd9c812dda519-prebuilt.qemu.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-5.1 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.13.0-48-gd9c812dda519-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-5.1:cvnQEMU:ct1:cvrpc-q35-5.1: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-5.1 dmi.sys.vendor: QEMU ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal uec-images -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914928 Title: GenericReceiveOffload in .link file ignored by systemd-networkd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1914928/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914928] Re: GenericReceiveOffload in .link file ignored by systemd-networkd
Sorry about this - figured out vxlan.link is not applied because /lib/systemd/network/99-default.link is applied. Please close. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914928 Title: GenericReceiveOffload in .link file ignored by systemd-networkd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1914928/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914929] [NEW] Raspberry Pi u-boot-rpi package version 2020.10+dfsg-1ubuntu0~20.10.1 prevents Bluetooth Devices Connecting
Public bug reported: After updating this package version from 2020.04+dfsg-2ubuntu1 to 2020.10+dfsg-1ubuntu0~20.10.1 any Bluetooth device on a Raspberry Pi 4 8GB will no longer be able to pair. After the package install all previously paired devices disappear. The devices when attempting to repair will then connect then disconnect immediately afterwards, Subsequent attempts to connect will fail with "no route to host error". Not attempts to remove and re add the devices seems to resolve the problem To fix the issue you have to uninstall this package and go back to the previous versions. Any devices you had paired before the upgrade will re appear ... but if you tried to pair them after the upgrade they will continue to have the same connect and disconnect behavior. However this time removing the device and repairing will fix the problem. Any device you did not attempt to connect / re pair after the upgrade work seamlessly again without any need to remove the device. I have recreated this issue on Ubuntu MATE Ubuntu 20.10 Groovy ** Affects: u-boot (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914929 Title: Raspberry Pi u-boot-rpi package version 2020.10+dfsg-1ubuntu0~20.10.1 prevents Bluetooth Devices Connecting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/1914929/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914930] [NEW] gjs loose gnome-shell parent and become zombie process
Public bug reported: Multiple zombie gjs process. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gjs 1.66.1-1 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Sun Feb 7 14:07:37 2021 InstallationDate: Installed on 2018-01-01 (1132 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171221) SourcePackage: gjs UpgradeStatus: Upgraded to groovy on 2019-10-19 (476 days ago) ** Affects: gjs (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914930 Title: gjs loose gnome-shell parent and become zombie process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1914930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914929] Re: Raspberry Pi u-boot-rpi package version 2020.10+dfsg-1ubuntu0~20.10.1 prevents Bluetooth Devices Connecting
** Description changed: After updating this package version from 2020.04+dfsg-2ubuntu1 to 2020.10+dfsg-1ubuntu0~20.10.1 any Bluetooth device on a Raspberry Pi 4 8GB will no longer be able to pair. After the package install all previously paired devices disappear. - The devices when attempting to repair will then connect then disconnect - immediately afterwards, Subsequent attempts to connect will fail with - "no route to host error". Not attempts to remove and re add the devices - seems to resolve the problem + The devices when attempting to re-pair will then connect then disconnect + immediately afterwards on initial pairing. Subsequent attempts to + connect will fail with "no route to host" error. No subsequentattempts + to remove and re add the devices seems to resolve the problem. To fix the issue you have to uninstall this package and go back to the previous versions. Any devices you had paired before the upgrade will re appear ... but if - you tried to pair them after the upgrade they will continue to have the - same connect and disconnect behavior. However this time removing the + you tried to pair them *after* the upgrade they will continue to have + the same connect and disconnect behavior. However this time removing the device and repairing will fix the problem. Any device you did not attempt to connect / re pair after the upgrade - work seamlessly again without any need to remove the device. + work seamlessly again without any need to remove and repair the device. I have recreated this issue on Ubuntu MATE Ubuntu 20.10 Groovy ** Description changed: - After updating this package version from 2020.04+dfsg-2ubuntu1 to - 2020.10+dfsg-1ubuntu0~20.10.1 any Bluetooth device on a Raspberry Pi 4 - 8GB will no longer be able to pair. + After updating this package (u-boot-rpi) version from 2020.04+dfsg- + 2ubuntu1 to 2020.10+dfsg-1ubuntu0~20.10.1 any Bluetooth device on a + Raspberry Pi 4 8GB will no longer be able to pair. After the package install all previously paired devices disappear. The devices when attempting to re-pair will then connect then disconnect immediately afterwards on initial pairing. Subsequent attempts to connect will fail with "no route to host" error. No subsequentattempts to remove and re add the devices seems to resolve the problem. To fix the issue you have to uninstall this package and go back to the previous versions. Any devices you had paired before the upgrade will re appear ... but if you tried to pair them *after* the upgrade they will continue to have the same connect and disconnect behavior. However this time removing the device and repairing will fix the problem. Any device you did not attempt to connect / re pair after the upgrade work seamlessly again without any need to remove and repair the device. I have recreated this issue on Ubuntu MATE Ubuntu 20.10 Groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914929 Title: Raspberry Pi u-boot-rpi package version 2020.10+dfsg-1ubuntu0~20.10.1 prevents Bluetooth Devices Connecting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/1914929/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 580933] Re: arping should return when there is nothing left to do
** Changed in: iputils (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/580933 Title: arping should return when there is nothing left to do To manage notifications about this bug go to: https://bugs.launchpad.net/iputils/+bug/580933/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 580933] Re: arping should return when there is nothing left to do
** Bug watch added: Debian Bug tracker #686944 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686944 ** Also affects: iputils via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686944 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/580933 Title: arping should return when there is nothing left to do To manage notifications about this bug go to: https://bugs.launchpad.net/iputils/+bug/580933/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914932] [NEW] Kernel updates marked as "manually installed", prevents old kernels cleanup
Public bug reported: Actually, I'm not 100% sure it's Discover's fault, but I'm quite confident it could the source of the problem. On 2021-01-27, when trying to install the latest kernel version for my Kubuntu 20.04 installation, I went out of space in my /boot partition. Looking at the installed kernels, I saw that I had 6 (SIX!) old kernels installed, including the one I was running on. I knew I had all the automatic kernel update and cleaning in place thanks to unattended-upgrades, because I looked at it some time ago, so, I took back the Ubuntu documentation page at https://help.ubuntu.com/community/RemoveOldKernels and re-read it from scratch. Substantially this sentence is enlightening: Note: The following methods will only remove kernels that are marked as being automatically installed as described above. My problem was that all the installed kernels where marked as MANUALLY INSTALLED: $ apt-mark showauto 'linux-image-.*' linux-image-generic $ apt-mark showmanual 'linux-image-.*' linux-image-5.4.0-54-generic linux-image-5.4.0-56-generic linux-image-5.4.0-58-generic linux-image-5.4.0-59-generic linux-image-5.4.0-62-generic linux-image-5.4.0-64-generic linux-image-5.4.0-65-generic (note: the last kernel version was the one I was not able to completely install due to insufficient disk space) Also, looking at /etc/apt/apt.conf.d/01autoremove-kernels I had: rc linux-image-5.4.0-42-generic5.4.0-42.46 amd64Signed kernel image generic rc linux-image-5.4.0-48-generic5.4.0-48.52 amd64Signed kernel image generic rc linux-image-5.4.0-51-generic5.4.0-51.56 amd64Signed kernel image generic rc linux-image-5.4.0-52-generic5.4.0-52.57 amd64Signed kernel image generic rc linux-image-5.4.0-53-generic5.4.0-53.59 amd64Signed kernel image generic rc linux-image-5.4.0-60-generic5.4.0-60.67 amd64Signed kernel image generic ii linux-image-5.4.0-62-generic5.4.0-62.70 amd64Signed kernel image generic ii linux-image-5.4.0-64-generic5.4.0-64.72 amd64Signed kernel image generic iF linux-image-5.4.0-65-generic5.4.0-65.73 amd64Signed kernel image generic ii linux-image-generic 5.4.0.65.68 amd64Generic Linux kernel image So, some kernel versions were indeed automatically pruned in the past (those marked with "rc"), but other are missing there and indeed they were marked as "manually installed". Running "apt autoremove" manually of course does not remove old kernels, for the same reason. I'm pretty sure the problem lies here: some kernel version were automatically installed by unattended-upgrades (and these where automatically purged), some others were installed by me by hitting "update all" button in Discover, when it periodically notifies me about new updates. So, looking again at the Ubuntu wiki page, I see: In Ubuntu 16.04 kernels installed by Software Updater are marked as being automatically installed. In Ubuntu 14.04 only kernels installed by unattended-upgrades are marked as being automatically installed. See bug #1439769 for details. So, I suspect such a "bug" is still present in Kubuntu 20.04 Discover, which marks all kernels installed through it as "manually installed". This problem has also been reported already at: https://bugs.kde.org/show_bug.cgi?id=430296 https://github.com/hughsie/PackageKit/issues/450 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: plasma-discover 5.18.5-0ubuntu0.1 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sun Feb 7 14:47:01 2021 InstallationDate: Installed on 2020-10-05 (124 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: plasma-discover UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: plasma-discover (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914932 Title: Kernel updates marked as "manually installed", prevents old kernels cleanup To manage notifications about
[Bug 1864871] Re: Failed to init Intel sound card in 20.04
After many months, I had the opportunity to put my hands on the computer that had these audio problems: (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864871/comments/31) ...and now the audio works without any workaround. Current Ubuntu version: 20.04.2 Kernel: 5.8.0-41 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864871 Title: Failed to init Intel sound card in 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1414279] Re: Installer crashed right toward the end of the process, just after a fatal error when grub failed to install.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: grub-installer (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/1414279 Title: Installer crashed right toward the end of the process, just after a fatal error when grub failed to install. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1414279/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 580933] Re: arping should return when there is nothing left to do
** Changed in: iputils Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/580933 Title: arping should return when there is nothing left to do To manage notifications about this bug go to: https://bugs.launchpad.net/iputils/+bug/580933/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895643] Re: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS
At Fosdem 21 conference it was announced that next summer Thunderbird 91 will be released, which again will include fundamental changes. My impression is that this time many months have been wasted because of unclear procedures and responsibilities - not because of unsolvable technical problems. (I hope we will see Thunderbird 78 before version 91 is out... - just kidding) @osomon: Thank you Olivier for taking care of this issue. Would you please write a short post mortem after the successful backport, where the difficulties have been, what steps to take and what responsible persons to contact to solve such a situation in future? This will definitely not be the last major Thunderbird update that needs to be back ported to LTS. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895643 Title: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1895643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904368] Re: eclipse ide has huge padding and inconsistencies
** Changed in: yaru-theme (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904368 Title: eclipse ide has huge padding and inconsistencies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1904368/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910149] Re: adb devices crashes with munmap_chunk(): invalid pointer
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: android-platform-system-core (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/1910149 Title: adb devices crashes with munmap_chunk(): invalid pointer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android-platform-system-core/+bug/1910149/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910149] Re: adb devices crashes with munmap_chunk(): invalid pointer
same issue, also after clearing ~/.android
[ 7521.901775] usb 1-2: new high-speed USB device number 9 using xhci_hcd
[ 7522.033001] usb 1-2: New USB device found, idVendor=18d1, idProduct=4ee7,
bcdDevice= 4.14
[ 7522.033004] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 7522.033005] usb 1-2: Product: Mi 9T Pro
[ 7522.033007] usb 1-2: Manufacturer: Xiaomi
[ 7522.033008] usb 1-2: SerialNumber: ea48f411
$ grep 18d1 /lib/udev/rules.d/51-android.rules
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ENV{adb_user}="yes"
$ dpkg -S /lib/udev/rules.d/51-android.rules
android-sdk-platform-tools-common: /lib/udev/rules.d/51-android.rules
$ dpkg -l android-sdk-platform-tools-common | tail -n1
ii android-sdk-platform-tools-common 27.0.0+12all Tools for
interacting with an Android platform - Common files
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1910149
Title:
adb devices crashes with munmap_chunk(): invalid pointer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/android-platform-system-core/+bug/1910149/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1576559] Re: Refused to switch profile to headset_head_unit: Not connected
Same issue here. As many others here, I need to use the mic at work's meetings and I needed to spent extra money on a wired headset because of this bug made my airpods useless for the task. elementary OS 5.1.7 Hera, Built on Ubuntu 18.04.4 LTS. Linux 4.15.0-135-generic. $pactl list cards Card #0 Name: alsa_card.pci-_00_1b.0 Driver: module-alsa-card.c Owner Module: 7 Properties: alsa.card = "0" alsa.card_name = "HDA Intel" alsa.long_card_name = "HDA Intel at 0xf000 irq 26" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-:00:1b.0" sysfs.path = "/devices/pci:00/:00:1b.0/sound/card0" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "27d8" device.product.name = "NM10/ICH7 Family High Definition Audio Controller" device.form_factor = "internal" device.string = "0" device.description = "Built-in Audio" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" Profiles: input:analog-stereo: Analog Stereo Input (sinks: 0, sources: 1, priority: 60, available: no) output:analog-stereo: Analog Stereo Output (sinks: 1, sources: 0, priority: 6000, available: yes) output:analog-stereo+input:analog-stereo: Analog Stereo Duplex (sinks: 1, sources: 1, priority: 6060, available: yes) output:iec958-stereo: Digital Stereo (IEC958) Output (sinks: 1, sources: 0, priority: 5500, available: yes) output:iec958-stereo+input:analog-stereo: Digital Stereo (IEC958) Output + Analog Stereo Input (sinks: 1, sources: 1, priority: 5560, available: yes) off: Off (sinks: 0, sources: 0, priority: 0, available: yes) Active Profile: output:analog-stereo+input:analog-stereo Ports: analog-input-mic: Microphone (priority: 8700, latency offset: 0 usec, not available) Properties: device.icon_name = "audio-input-microphone" Part of profile(s): input:analog-stereo, output:analog-stereo+input:analog-stereo, output:iec958-stereo+input:analog-stereo analog-output-speaker: Speakers (priority: 1, latency offset: 0 usec) Properties: device.icon_name = "audio-speakers" Part of profile(s): output:analog-stereo, output:analog-stereo+input:analog-stereo analog-output-headphones: Headphones (priority: 9000, latency offset: 0 usec, not available) Properties: device.icon_name = "audio-headphones" Part of profile(s): output:analog-stereo, output:analog-stereo+input:analog-stereo iec958-stereo-output: Digital Output (S/PDIF) (priority: 0, latency offset: 0 usec) Part of profile(s): output:iec958-stereo, output:iec958-stereo+input:analog-stereo Card #7 Name: bluez_card.AC_80_1C_01_34_B0 Driver: module-bluez5-device.c Owner Module: 33 Properties: device.description = "Baseus Encok W04 Pro" device.string = "AC:80:1C:01:34:B0" device.api = "bluez" device.class = "sound" device.bus = "bluetooth" device.form_factor = "headset" bluez.path = "/org/bluez/hci0/dev_AC_80_1C_01_34_B0" bluez.class = "0x240404" bluez.alias = "Baseus Encok W04 Pro" device.icon_name = "audio-headset-bluetooth" device.intended_roles = "phone" Profiles: a2dp_sink: High Fidelity Playback (A2DP Sink) (sinks: 1, sources: 0, priority: 40, available: yes) headset_head_unit: Headset Head Unit (HSP/HFP) (sinks: 1, sources: 1, priority: 30, available: no) off: Off (sinks: 0, sources: 0, priority: 0, available: yes) Active Profile: off Ports: headset-output: Headset (priority: 0, latency offset: 0 usec) Part of profile(s): a2dp_sink, headset_head_unit headset-input: Headset (priority: 0, latency offset: 0 usec, not available) Part of profile(s): headset_head_unit $ bluetoothctl [NEW] Controller 00:1A:7D:DA:71:11 siemens-AMILO-Pi-1505 [default] [NEW] Device AC:80:1C:01:34:B0 Fran Hdez's Airpods [NEW] Device 4B:A3:18:BC:21:5B Sony Home Sound System [NEW] Device 2B:20:C2:C6:E1:5D Bose QC25 [NEW] Device B1:81:AE:C5:1D:20 Home Living Room Pioneer Sound System Agent registered [Fran Hdez's Airpods]# info AC:80:1C:0
[Bug 1914848] Re: linux kernel 5.8 jammed
trying completed ubuntu-bug evince trying send bug report linux kernel 5.8 is jammed and freeze -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914848 Title: linux kernel 5.8 jammed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1914848/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914939] [NEW] backport libseccomp 2.4.4+ for faccessat2
Public bug reported: The next release of Alpine Linux intends to use the faccessat2(2) syscall for access(3). This currently fails under Ubuntu Docker, regardless of using the separate Docker package repository, since it forbids faccessat2. This bug is similar to bug #1876055, but requests backporting of 2.4.4 instead of 2.4.3. I believe this change is likely low risk and can be applied to all supported Ubuntu versions. Alternatively, I also see in bug #1891810 that libseccomp 2.5 is being considered for backporting. This would also be acceptable for our purposes, but is obviously a higher-risk change for Ubuntu. ** Affects: libseccomp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914939 Title: backport libseccomp 2.4.4+ for faccessat2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1914939/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0
This doesn't seem to be fixed with recent Ubuntu kernels. I have constant GPU hangs too. kernel: Linux luto 5.8.0-41-generic #46~20.04.1-Ubuntu SMP [ 20.503897] i915 :00:02.0: vgaarb: deactivate vga console [ 20.505641] i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [ 20.525280] [drm] Initialized i915 1.6.0 20200515 for :00:02.0 on minor 0 [ 20.570726] fbcon: i915drmfb (fb0) is primary device [ 20.570858] i915 :00:02.0: fb0: i915drmfb frame buffer device [ 2252.688165] unhandled error in i915_error_to_vmf_fault: -22 [ 2252.688324] WARNING: CPU: 1 PID: 1455 at drivers/gpu/drm/i915/gem/i915_gem_mman.c:211 i915_error_to_vmf_fault+0x7a/0x90 [i915] [ 2252.688325] Modules linked in: nls_iso8859_1 snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_intel snd_intel_dspcfg snd_ice1712 snd_hda_codec snd_cs8427 snd_i2c snd_ice17xx_ak4xxx snd_ak4xxx_adda i915 snd_ac97_codec snd_hda_core snd_mpu401_uart snd_hwdep snd_seq_midi drm_kms_helper input_leds cec snd_seq_midi_event rc_core i2c_algo_bit snd_rawmidi fb_sys_fops snd_seq syscopyarea sysfillrect ac97_bus snd_pcm snd_seq_device snd_timer sysimgblt at24 snd soundcore serio_raw mac_hid sch_fq_codel w83627ehf hwmon_vid coretemp parport_pc ppdev lp drm parport ip_tables x_tables autofs4 uas usb_storage hid_generic usbhid hid gpio_ich i2c_i801 psmouse i2c_smbus pata_acpi lpc_ich r8169 realtek video [ 2252.688398] RIP: 0010:i915_error_to_vmf_fault+0x7a/0x90 [i915] [ 2252.688450] vm_fault_gtt+0x1d7/0x540 [i915] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872001 Title: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914940] [NEW] libsbigudrv2 contains udev rules prevent firmware from loading
Public bug reported:
The libsbigudrv2 package contains several minor udev rule errors that
prevents firmware from loading. These include queries to SYSFS instead
of ATTR, assignment of ENV{DEVTYPE}, and a missing comma (causing
1801362). These items cause the rule to not apply to the underlying
devices and the firmware load command not to run.
I have fixed all of these locally. Is there an upstream package to which
these should be contributed? If not, how do I submit a patch here?
** Affects: sbig (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1914940
Title:
libsbigudrv2 contains udev rules prevent firmware from loading
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sbig/+bug/1914940/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914848] Re: linux kernel 5.8 jammed
only linux kernel 5.4 is working linux kernel 5.8 is jammed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914848 Title: linux kernel 5.8 jammed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1914848/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914941] [NEW] [needs-packaging] davfs2 1.5.6-1
Public bug reported: Dear all, when installing davfs2 from universe (Ubuntu 20.04), the resulting davfs2 version is 1.5.5-1. I just did an installation from scratch to check this. However, this version has a bug leading to a segmentation fault when running the umount.davfs command. Moreover, the system "hangs" when shutting down, and finally reports that it is waiting for process mount.davfs. I found several reports concerning the segmentation fault, an the common solution seems to be to opt for the bugfix release 1.5.6-1 instead of 1.5.5-1. I am not familiar enough with linux / debian to do the packaging myself, and I think this is a general issue. Perhaps someone from the MOTUs can help here ? Best regards, Martin ** Affects: davfs2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914941 Title: [needs-packaging] davfs2 1.5.6-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/davfs2/+bug/1914941/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879633] Re: Killer 500s (QCA6390) WLAN/BT [17cb:1101] unavailable
Thanks once again, @vicamo! Had to download additionally https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/plain/ath11k/QCA6390/hw2.0/board-2.bin and now finally detach my XPS 17 from the docking station and *still* have Internet!!! (3 months after getting it) I guess if the linux-firmware gets upgraded, I can again apply the instructions above and install linux-oem-20.04b, right? How can I "pin" linux-firmware? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879633 Title: Killer 500s (QCA6390) WLAN/BT [17cb:1101] unavailable To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1879633/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766076] Re: USB over thunderbolt turns off every once in a while
I have a very similar issue with a WD19TB under Ubuntu 20.04 (Dell Latitude 5410) and desperately browsing the net, looking for solutions. Everything works fine until I resume from suspend. Then all USB devices connected to the dock start having failures (like missing key presses for the keyboard, mouse becoming sluggish until the device is disconnected, or sound becoming bad, also I suspect the ethernet port of the dock doesn't work well anymore). This is most likely *not* a thunderbolt authorization issue (I tried all the security modes: no security/user based/key based, all show the same behavior), which is a definite difference with many reports I found here and there (and makes it hard to find the same exact one as the one I have). The present issues description from the opener seems close enough, including dmesg output (although the opener had a Dell 16TB dock). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766076 Title: USB over thunderbolt turns off every once in a while To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1766076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853784] Re: Format button has no effect when I right click a USB and select Format
Same problem in Ubuntu 20.04.2 LTS "org.gnome.Nautilus[12977]: Не удалось разобрать целочисленное значение «2a7» для --xid" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853784 Title: Format button has no effect when I right click a USB and select Format To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1853784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766076] Re: USB over thunderbolt turns off every once in a while
#106 - please open a separate issue to debug this. The architecture for the WD19TB is very different than the TB16 and it shouldn't be conflated into this issue. The most interesting things to include in your issue - please first try this kernel: https://launchpad.net/ubuntu/+source /linux-oem-5.10. If it persists, can you please open an issue with 'ubuntu-bug linux-oem-5.10' which will attach all the logs to your issue? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766076 Title: USB over thunderbolt turns off every once in a while To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1766076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914946] [NEW] Clean "Focal" 20.04.2 install fails on Lenovo Thinkpad T14s - grub fails - 20.04.1 works
Public bug reported: What I did: Downloaded the newest 20.04.1 USB image. (kernel 5.8 is said to be stable with T14s AMD) Boot the live USB on an Thinkpad T14s with Ryzen 4750U. Install Ubuntu on 20.04.1 and wipe the entire disk thus replace Windows 10. What happened: Everything installs seamlessy. (1) installs the EFI "boot" on the first partition (2) installs the main ext4 "/" on the second partition But the EFI "boot" image contains a faulty grub bootloader. There are no ubuntu kernels to boot up it is just an empty grub2. Problem: T14s AMD does not allow traditional MBR legacy boot, thus I had to install Ubuntu by means of UEFI boot. 20.04.1 installer fails to set up it properly. Solution: The original 20.04.1 USB installer handles the EFI partition correctly. ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914946 Title: Clean "Focal" 20.04.2 install fails on Lenovo Thinkpad T14s - grub fails - 20.04.1 works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1914946/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914945] [NEW] iftop ignores passively sniffed IPv6 traffic
Public bug reported: IPv4 traffic is displayed but IPv6 is not, when running iftop against a passive promiscuous network interface. ** Affects: iftop (Ubuntu) Importance: Undecided Status: New ** Patch added: "0001-Support-passively-sniffing-IPv6.patch" https://bugs.launchpad.net/bugs/1914945/+attachment/5461080/+files/0001-Support-passively-sniffing-IPv6.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914945 Title: iftop ignores passively sniffed IPv6 traffic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iftop/+bug/1914945/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 660504] Re: pacat --file-format option doesn't work
#5 This is still an issue on 20.04 LTS https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/822 ** Bug watch added: gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues #822 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/822 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/660504 Title: pacat --file-format option doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/660504/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914947] [NEW] My display is so slow
Public bug reported: My display performance is so slow sometimes it will crash or resolution is bad ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: hostname 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Feb 7 23:02:45 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2021-02-05 (1 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. VMware Virtual USB Mouse Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware7,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic root=UUID=fd8451d8-78e6-471e-aa1e-cae417c043fb ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2020 dmi.bios.vendor: VMware, Inc. dmi.bios.version: VMW71.00V.16722896.B64.2008100651 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnVMware,Inc.:bvrVMW71.00V.16722896.B64.2008100651:bd08/10/2020:svnVMware,Inc.:pnVMware7,1:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware7,1 dmi.product.version: None dmi.sys.vendor: VMware, Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal resolution ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914947 Title: My display is so slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1914947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914946] Re: Clean "Focal" 20.04.2 install fails on Lenovo Thinkpad T14s - grub fails - 20.04.1 works
** Description changed: What I did: Downloaded the newest 20.04.1 USB image. (kernel 5.8 is said to be stable with T14s AMD) Boot the live USB on an Thinkpad T14s with Ryzen 4750U. - Install Ubuntu on 20.04.1 and wipe the entire disk thus replace Windows 10. + Install Ubuntu on 20.04.1 and wipe the entire disk thus replace Windows 10. What happened: Everything installs seamlessy. (1) installs the EFI "boot" on the first partition (2) installs the main ext4 "/" on the second partition But the EFI "boot" image contains a faulty grub bootloader. There are no ubuntu kernels to boot up it is just an empty grub2. Problem: - T14s AMD does not allow traditional MBR legacy boot, thus I had to install Ubuntu by means of UEFI boot. 20.04.1 installer fails to set up it properly. + T14s AMD does not allow traditional MBR legacy boot, thus I had to install Ubuntu by means of UEFI boot. 20.04.2 installer fails to set up it properly. Solution: The original 20.04.1 USB installer handles the EFI partition correctly. ** Description changed: What I did: Downloaded the newest 20.04.1 USB image. (kernel 5.8 is said to be stable with T14s AMD) Boot the live USB on an Thinkpad T14s with Ryzen 4750U. Install Ubuntu on 20.04.1 and wipe the entire disk thus replace Windows 10. What happened: - Everything installs seamlessy. + Everything installs seamlessy. I've used the simple "wipe disk" option without any extra customizations. (1) installs the EFI "boot" on the first partition (2) installs the main ext4 "/" on the second partition But the EFI "boot" image contains a faulty grub bootloader. There are no ubuntu kernels to boot up it is just an empty grub2. Problem: - T14s AMD does not allow traditional MBR legacy boot, thus I had to install Ubuntu by means of UEFI boot. 20.04.2 installer fails to set up it properly. + T14s AMD does not allow traditional MBR legacy boot, thus I had to install Ubuntu by means of UEFI boot. 20.04.1 installer fails to set up it properly. Solution: The original 20.04.1 USB installer handles the EFI partition correctly. ** Description changed: What I did: Downloaded the newest 20.04.1 USB image. (kernel 5.8 is said to be stable with T14s AMD) Boot the live USB on an Thinkpad T14s with Ryzen 4750U. Install Ubuntu on 20.04.1 and wipe the entire disk thus replace Windows 10. What happened: Everything installs seamlessy. I've used the simple "wipe disk" option without any extra customizations. (1) installs the EFI "boot" on the first partition - (2) installs the main ext4 "/" on the second partition + (2) installs the main ext4 "/" on the second partition with all files. But the EFI "boot" image contains a faulty grub bootloader. There are no ubuntu kernels to boot up it is just an empty grub2. Problem: T14s AMD does not allow traditional MBR legacy boot, thus I had to install Ubuntu by means of UEFI boot. 20.04.1 installer fails to set up it properly. + I was not able debug anything because I was not able to mount the faulty EFI "boot" partition with the live USB. Solution: The original 20.04.1 USB installer handles the EFI partition correctly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914946 Title: Clean "Focal" 20.04.2 install fails on Lenovo Thinkpad T14s - grub fails - 20.04.1 works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1914946/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913567] Re: Sync puppet 5.5.22-1 (universe) from Debian unstable (main)
And finally it migrated. ** Changed in: puppet (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913567 Title: Sync puppet 5.5.22-1 (universe) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1913567/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914948] [NEW] Incorrect package description
Public bug reported: The package description says that this is a "Common Lisp HTTP client". That is clearly incorrect because https://common-lisp.net/project/zip/ says that cl-zip is "a library for .zip-file reading and writing, written in Common Lisp." ** Affects: cl-zip (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914948 Title: Incorrect package description To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cl-zip/+bug/1914948/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914949] [NEW] Resume from S3 not working with i915 driver (linux 5.4 and 5.8)
Public bug reported: Using kernel 5.4.0-65, the system does not wake up anymore from suspend to ram (S3). The screen stays black, only the backlight comes on. Following the instructions in "wiki.ubuntu.com/DebuggingKernelSuspend", it shows that this PCI device is the problem: 00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 18) This is a 1st gen Intel HD graphics (Ironlake) Testing various versions of kernels 5.4.0.x , I found that the problem seems to be introduced with 5.4.0-59 Versions after -59 don't wake up, and versions until 5.4.0-58 work fine. Testing 5.8.0-41, it doesn't wake up. Testing mainline 5.11.0-051100rc6-generic, it works fine. ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914949 Title: Resume from S3 not working with i915 driver (linux 5.4 and 5.8) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1914949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914948] Re: Incorrect package description
I noticed that the description for cl-zip is nearly the same as that for cl-drakma. Description for cl-zip: Description-en: Common Lisp HTTP client Zip is a full-featured HTTP client implemented in Common Lisp. It knows how to handle HTTP/1.1 chunking, persistent connections, re-usable sockets, SSL, continuable uploads, file uploads, cookies, and more. Description for cl-drakma: Description-en: Common Lisp HTTP client Drakma is a full-featured HTTP client implemented in Common Lisp. It knows how to handle HTTP/1.1 chunking, persistent connections, re-usable sockets, SSL, continuable uploads, file uploads, cookies, and more. Is this some kind of mistake caused by incorrect copy & paste? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914948 Title: Incorrect package description To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cl-zip/+bug/1914948/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912951] Re: No network connectivity with kernel 5.8
*** This bug is a duplicate of bug 1872908 *** https://bugs.launchpad.net/bugs/1872908 This bug was a duplicate. Focal just pushed an update to the bcmwl package that fixed the bug: >From 6.30.223.271+bdcom-0ubuntu5 to 6.30.223.271+bdcom-0ubuntu7~20.04.1. Wifi is working again. ** Changed in: linux-signed-hwe-5.8 (Ubuntu) Status: Confirmed => Fix Released ** This bug has been marked a duplicate of bug 1872908 bcmwl kernel module does not build with kernel version 5.6 or 5.8 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912951 Title: No network connectivity with kernel 5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1912951/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912928] Re: No network connectivity with kernel 5.8
*** This bug is a duplicate of bug 1872908 *** https://bugs.launchpad.net/bugs/1872908 ** This bug is no longer a duplicate of bug 1912951 No network connectivity with kernel 5.8 ** This bug has been marked a duplicate of bug 1872908 bcmwl kernel module does not build with kernel version 5.6 or 5.8 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912928 Title: No network connectivity with kernel 5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912928/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1913567] Re: Sync puppet 5.5.22-1 (universe) from Debian unstable (main)
Wonderful. Thank you. > On 7 Feb 2021, at 18:05, Dmitry Shachnev <1913...@bugs.launchpad.net> wrote: > > And finally it migrated. > > ** Changed in: puppet (Ubuntu) > Status: Fix Committed => Fix Released > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1913567 > > Title: > Sync puppet 5.5.22-1 (universe) from Debian unstable (main) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1913567/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913567 Title: Sync puppet 5.5.22-1 (universe) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1913567/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914949] Re: Resume from S3 not working with i915 driver (linux 5.4 and 5.8)
apport information ** Tags added: apport-collected ulyana ** Description changed: Using kernel 5.4.0-65, the system does not wake up anymore from suspend to ram (S3). The screen stays black, only the backlight comes on. Following the instructions in "wiki.ubuntu.com/DebuggingKernelSuspend", it shows that this PCI device is the problem: 00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 18) This is a 1st gen Intel HD graphics (Ironlake) Testing various versions of kernels 5.4.0.x , I found that the problem seems to be introduced with 5.4.0-59 Versions after -59 don't wake up, and versions until 5.4.0-58 work fine. Testing 5.8.0-41, it doesn't wake up. Testing mainline 5.11.0-051100rc6-generic, it works fine. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.16 + Architecture: amd64 + CasperMD5CheckResult: skip + CurrentDesktop: X-Cinnamon + DistroRelease: Linux Mint 20 + HibernationDevice: RESUME=UUID=31673f7c-6b7f-4407-bc0b-e8f0652008be + InstallationDate: Installed on 2018-09-11 (879 days ago) + InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717 + MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. + Package: linux (not installed) + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-65-generic root=UUID=6de19ac7-7f66-4b39-a81f-3c955a60ae7a ro quiet splash + ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 + RelatedPackageVersions: + linux-restricted-modules-5.4.0-65-generic N/A + linux-backports-modules-5.4.0-65-generic N/A + linux-firmware1.187.9 + Tags: ulyana + Uname: Linux 5.4.0-65-generic x86_64 + UnreportableReason: In diesem Bericht geht es um ein Paket, welches nicht installiert ist. + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: False + dmi.bios.date: 05/25/2010 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: P1.30 + dmi.board.name: HM55-HT + dmi.board.vendor: ASRock + dmi.chassis.asset.tag: To Be Filled By O.E.M. + dmi.chassis.type: 3 + dmi.chassis.vendor: To Be Filled By O.E.M. + dmi.chassis.version: To Be Filled By O.E.M. + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.30:bd05/25/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM55-HT:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: + dmi.product.family: To Be Filled By O.E.M. + dmi.product.name: To Be Filled By O.E.M. + dmi.product.sku: To Be Filled By O.E.M. + dmi.product.version: To Be Filled By O.E.M. + dmi.sys.vendor: To Be Filled By O.E.M. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1914949/+attachment/5461100/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914949 Title: Resume from S3 not working with i915 driver (linux 5.4 and 5.8) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1914949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914949] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1914949/+attachment/5461102/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914949 Title: Resume from S3 not working with i915 driver (linux 5.4 and 5.8) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1914949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914949] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1914949/+attachment/5461103/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914949 Title: Resume from S3 not working with i915 driver (linux 5.4 and 5.8) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1914949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914949] AudioDevicesInUse.txt
apport information ** Attachment added: "AudioDevicesInUse.txt" https://bugs.launchpad.net/bugs/1914949/+attachment/5461101/+files/AudioDevicesInUse.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914949 Title: Resume from S3 not working with i915 driver (linux 5.4 and 5.8) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1914949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914949] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1914949/+attachment/5461104/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914949 Title: Resume from S3 not working with i915 driver (linux 5.4 and 5.8) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1914949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914949] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1914949/+attachment/5461109/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914949 Title: Resume from S3 not working with i915 driver (linux 5.4 and 5.8) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1914949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914949] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1914949/+attachment/546/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914949 Title: Resume from S3 not working with i915 driver (linux 5.4 and 5.8) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1914949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914949] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1914949/+attachment/5461108/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914949 Title: Resume from S3 not working with i915 driver (linux 5.4 and 5.8) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1914949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914949] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1914949/+attachment/5461113/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914949 Title: Resume from S3 not working with i915 driver (linux 5.4 and 5.8) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1914949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914949] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1914949/+attachment/5461114/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914949 Title: Resume from S3 not working with i915 driver (linux 5.4 and 5.8) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1914949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914949] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1914949/+attachment/5461117/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914949 Title: Resume from S3 not working with i915 driver (linux 5.4 and 5.8) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1914949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914949] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1914949/+attachment/5461115/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914949 Title: Resume from S3 not working with i915 driver (linux 5.4 and 5.8) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1914949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914949] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1914949/+attachment/5461105/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914949 Title: Resume from S3 not working with i915 driver (linux 5.4 and 5.8) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1914949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914949] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1914949/+attachment/5461107/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914949 Title: Resume from S3 not working with i915 driver (linux 5.4 and 5.8) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1914949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914949] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1914949/+attachment/5461116/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914949 Title: Resume from S3 not working with i915 driver (linux 5.4 and 5.8) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1914949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914949] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1914949/+attachment/5461106/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914949 Title: Resume from S3 not working with i915 driver (linux 5.4 and 5.8) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1914949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914949] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1914949/+attachment/5461118/+files/acpidump.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914949 Title: Resume from S3 not working with i915 driver (linux 5.4 and 5.8) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1914949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914949] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1914949/+attachment/5461112/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914949 Title: Resume from S3 not working with i915 driver (linux 5.4 and 5.8) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1914949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914949] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1914949/+attachment/5461110/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914949 Title: Resume from S3 not working with i915 driver (linux 5.4 and 5.8) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1914949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Hi Coiby To answer your question in message #359 > In hybrid mode, does external monitor work for you? The answer is yes, it works. I tested the hotplug of an HDMI external monitor, it was detected by Ubuntu 20.04 and worked by default as an extended desktop (both internal & external display used, not cloned). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 To manage notifications about this bug go to: https://bugs.launchpad.net/pop-os/+bug/1887190/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912506] Re: package libnvidia-common-450-server (not installed) failed to install/upgrade: trying to overwrite '/usr/share/nvidia/nvidia-application-profiles-450.102.04-key-documentation', whic
a workaround for me was this https://askubuntu.com/questions/1285472/ubuntu-18-04-broken-install- problem-with-libnvidia-common-450-package sudo apt-get -o Dpkg::Options::="--force-overwrite" install -f libnvidia-common-450-server -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912506 Title: package libnvidia-common-450-server (not installed) failed to install/upgrade: trying to overwrite '/usr/share/nvidia/nvidia- application-profiles-450.102.04-key-documentation', which is also in package libnvidia-common-450 450.102.04-0ubuntu0.20.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-450-server/+bug/1912506/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914953] [NEW] grub2 incompatibility between at_keyboard and gfxterm modules lead to impossible to type passphrase or access ubuntu grub2 menu on a fully encrypted installation
Public bug reported: Hello, On a fresh installed Ubuntu 20.04.1 LTS (tested with Mate & Ubuntu with two different brands and configurations of laptops) fully luks encrypted systems using this guide https://help.ubuntu.com/community/Full_Disk_Encryption_Howto_2019 with the fellowing configurations: laptop 1 (Dell): x64_86 BIOS/GPT /dev/sda1 => bios_grub /dev/sda2 => luks encrypted LVM with VG,LV /boot, /root, /home, /swap laptop 2 (Acer): x64_86 UEFI/GPT /dev/sda1 => ESP /dev/sda2 => luks encrypted LVM with VG,LV /boot, /root, /home, /swap It's impossible with : => 1st stage grub: /dev/sda1 bios_grub (core.img) or ESP partition (grub.efi) => 2nd stage grub: /dev/sda2/LUKS_VOL/LVM/boot/grub to: 1- set a local grub keyboard layout (French) to type passphrase in 1st stage grub 2- access (edit mode or typing command under grub console) in 2nd stage grub Here all my tests results from the last 3 days on the two laptops at same time: [0] Defaults setting after installation : 1st stage grub: US keyboard layout (standard) 2nd stage grub: gfxterm module loaded (install defaults) => 1st stage grub: almost impossible to type strong passphrase with accentuated characters and special characters due typos error and keyboard layout difference and unlock encrypted luks volume => 2nd stage grub: working without trouble, can access ubuntu grub menus, edit command and type command in the grub console as normal. [1] Modfied settings after installation : 1st stage grub only 1st stage grub: FR keyboard layouts with at_keyboard module ([1A] grub core image config at the end) 2nd stage grub: gfxterm module loaded (no modification from default installation) => 1st stage grub: can type strong passphrase and unlock at the first attempt the luks encrypted volume => 2nd stage grub: Impossible to access grub menus, edit command and type command in the grub console [2] Modfied settings after installation : 2nd stage grub only 1st stage grub: default grub core.img after installation with US layout 2nd stage grub: gfxterm module loaded + at_keybord, "terminal_input at_keyboard", keymap fr.gkb ([2A] grub.cfg config at the end) => 1st stage grub: almost impossible to type strong passphrase as in test case [0] => 2nd stage grub: almost Impossible to access grub menus, edit command and type command in the grub console). I need to repeat the same keystrokes 7 times or more give me only one keystroke at screen (and PC speaker beep every 1x or 4x keystrokes but it's really secondary).. Ressetting "terminal_output console" (by removing at_keyboard) or "terminal_input console" (by removing gfxterm) (by typing t(x7+2xbeep)e(x7+3xbeep)+r(x7+4xbeep)+m(x7+1xbeep)...) resolved the situation. [3] Modfied settings after installation : 1nd stage grub only 1st stage grub: FR keyboard layouts with at_keybord + gfxterm module 2nd stage grub: gfxterm module loaded (no modification from default installation) => 1st stage grub: Impossible to type strong passphrase as in test case [0] but this time it's due to gfxterm and at_keyboard loaded at same time and each character must be typed 7x or more times (+ beep) so impossible to know what you are typping because nothing is printed at screen while you type your password. By accessing grub minimal console due to a limited core.img and removing at_keybord with "terminal_input console" or removing gfxterm with "terminal_output console" resolved the situation but typing such command as set prefix=(memdisk), ... cryptomount -u xyzaabac, set root='lvmid/Eh2HHw-Bceq-VfsK-Kz01-kaeg-dRbz-Rwcntf/nVAE5f-GOrJ-wvu3-RTN0-mzAe-G4Oo-mzTQrN' and then passphrase without any typos erros at first attempt with a different keyboard layout was a real challenge. => 2nd stage grub: Impossible to access grub menus, edit command and type command in the grub console with at_keybord eg: "terminal_input at_keyboard" is loaded even in 1st stage grub. Conclusion: It seems that if grub at_keyboard module is loaded with "terminal_input at_keyboard" (to load a custom keyboard layout tested with german, italian, french ...) even only in the 1st stage grub ... it's almost impossible to access any grub menu (edit command or console) in grub (same level) or even in another child grub as the 2nd stage if grub gfxterm module is loaded too. So, for international users typing a strong passphrase is almost impossible without using something like "test123" or "qwerty123" and keeping access on any child grub. For me it's something like critical because I can use a secure installation with all partition/data encrypted but I can't type a strong passphrase (eg "C0udéeM+(@rpantÀ)") or access any child grub menu or console if any grub at_keyboard module is loaded (at a upper level or at same level) with a gfxterm module somewhere else (at same level or at a child level). I found an old bug report at debian.org but it seems resolved with grub 2.02+dfsg1-11. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741464 I ap
