[Touch-packages] [Bug 1850702] Re: [Samsung Notebook 7 Pro, Realtek ALC256, headphone jack] Headphone sound is faint and distorted (but works fine in Windows)
Is it confirmed that this bug is fixed in newer Kernels? I am running 5.4.0.66 and have this problem in a Samsung laptop as well. Thank you. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1850702 Title: [Samsung Notebook 7 Pro, Realtek ALC256, headphone jack] Headphone sound is faint and distorted (but works fine in Windows) Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I can't get sound of my laptop (Samsung Notebook 7 Force) through the headphone jack. The speakers work fine. When I plug a headphone, I can hear the sound being played very faintly. If I bump the volume to the maximum, that is. The sound is very distorted, like a buzz effect being applied over it. I noticed that if I delete /.config/pulse the distortion goes away, but the sound remains very low. After some time, the buzzing effect comes back. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.15 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: KDE Date: Wed Oct 30 16:03:41 2019 InstallationDate: Installed on 2019-10-29 (1 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: filipe 1294 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-10-29 (1 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 RelatedPackageVersions: linux-restricted-modules-5.3.0-19-generic N/A linux-backports-modules-5.3.0-19-generic N/A linux-firmware1.183.1 Tags: eoan Uname: Linux 5.3.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/10/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P02REZ.040.190610.FL dmi.board.asset.tag: No Asset Tag dmi.board.name: NP760XBE-XW1BR dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGL9947A0Y-C01-G003-S0001+10.0.17763 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP02REZ.040.190610.FL:bd06/10/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn760XBE:pvrP02REZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP760XBE-XW1BR:rvrSGL9947A0Y-C01-G003-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.family: Notebook 7 Series dmi.product.name: 760XBE dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PREZ dmi.product.version: P02REZ dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: filipe 1294 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-10-29 (1 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 RelatedPackageVersions: linux-restricted-modules-5.3.0-19-generic N/A linux-backports-modules-5.3.0-19-generic N/A linux-firmware1.183.1 Tags: eoan Uname: Linux 5.3.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/10/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P02REZ.040.190610.FL dmi.board.asset.tag: No Asset Tag dmi.board.name: NP760XBE-XW1
[Touch-packages] [Bug 1766628] Re: apparmor denies VLC to open files in devmode
AppArmor just enforces the policies that were given to it; please report this issue to whoever packaged the snap you're using. Thanks ** Changed in: apparmor (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1766628 Title: apparmor denies VLC to open files in devmode Status in apparmor package in Ubuntu: Invalid Bug description: I see failures in VLC trying to open files and prefs while VLC snap seemingly uses devmode since this is on Debian "testing". Failures: ^[[1;3CApr 24 17:50:24 coal kernel: [ 7997.906298] audit: type=1400 audit(1524581424.694:1944): apparmor="DENIED" operation="link" info="Failed name lookup - deleted entry" error=-2 profile="snap.vlc.vlc" name="/home/thresh/snap/vlc/288/.local/share/#268898190" pid=19173 comm="vlc" requested_mask="l" denied_mask="l" fsuid=1000 ouid=1000 Apr 24 17:50:24 coal kernel: [ 7997.906308] audit: type=1400 audit(1524581424.694:1945): apparmor="DENIED" operation="link" profile="snap.vlc.vlc" name="/home/thresh/snap/vlc/288/.local/share/user-places.xbel.tbcache" pid=19173 comm="vlc" requested_mask="l" denied_mask="l" fsuid=1000 ouid=1000 target="/home/thresh/snap/vlc/288/.local/share/#268898190" Apr 24 17:50:24 coal kernel: [ 7997.912113] audit: type=1400 audit(1524581424.698:1946): apparmor="DENIED" operation="link" info="Failed name lookup - deleted entry" error=-2 profile="snap.vlc.vlc" name="/home/thresh/snap/vlc/288/.local/share/#268898190" pid=19173 comm="vlc" requested_mask="l" denied_mask="l" fsuid=1000 ouid=1000 Apr 24 17:50:24 coal kernel: [ 7997.912122] audit: type=1400 audit(1524581424.698:1947): apparmor="DENIED" operation="link" profile="snap.vlc.vlc" name="/home/thresh/snap/vlc/288/.local/share/user-places.xbel" pid=19173 comm="vlc" requested_mask="l" denied_mask="l" fsuid=1000 ouid=1000 target="/home/thresh/snap/vlc/288/.local/share/#268898190" Apr 24 17:50:28 coal kernel: [ 8001.418173] audit: type=1400 audit(1524581428.206:1948): apparmor="DENIED" operation="link" info="Failed name lookup - deleted entry" error=-2 profile="snap.vlc.vlc" name="/home/thresh/snap/vlc/288/.local/share/#268898190" pid=19173 comm="vlc" requested_mask="l" denied_mask="l" fsuid=1000 ouid=1000 Apr 24 17:50:28 coal kernel: [ 8001.418180] audit: type=1400 audit(1524581428.206:1949): apparmor="DENIED" operation="link" profile="snap.vlc.vlc" name="/home/thresh/snap/vlc/288/.local/share/user-places.xbel.tbcache" pid=19173 comm="vlc" requested_mask="l" denied_mask="l" fsuid=1000 ouid=1000 target="/home/thresh/snap/vlc/288/.local/share/#268898190" Apr 24 17:50:28 coal kernel: [ 8001.422473] audit: type=1400 audit(1524581428.210:1950): apparmor="DENIED" operation="link" info="Failed name lookup - deleted entry" error=-2 profile="snap.vlc.vlc" name="/home/thresh/snap/vlc/288/.local/share/#268898190" pid=19173 comm="vlc" requested_mask="l" denied_mask="l" fsuid=1000 ouid=1000 Apr 24 17:50:28 coal kernel: [ 8001.422481] audit: type=1400 audit(1524581428.210:1951): apparmor="DENIED" operation="link" profile="snap.vlc.vlc" name="/home/thresh/snap/vlc/288/.local/share/user-places.xbel" pid=19173 comm="vlc" requested_mask="l" denied_mask="l" fsuid=1000 ouid=1000 target="/home/thresh/snap/vlc/288/.local/share/#268898190" Apr 24 17:50:28 coal kernel: [ 8001.556305] audit: type=1400 audit(1524581428.342:1952): apparmor="DENIED" operation="link" info="Failed name lookup - deleted entry" error=-2 profile="snap.vlc.vlc" name="/run/user/1000/snap.vlc/#511744" pid=19173 comm="vlc" requested_mask="l" denied_mask="l" fsuid=1000 ouid=1000 Apr 24 17:50:28 coal kernel: [ 8001.556318] audit: type=1400 audit(1524581428.342:1953): apparmor="DENIED" operation="link" profile="snap.vlc.vlc" name="/run/user/1000/snap.vlc/vlcxkYxzT.1.slave-socket" pid=19173 comm="vlc" requested_mask="l" denied_mask="l" fsuid=1000 ouid=1000 target="/run/user/1000/snap.vlc/#511744" Apr 24 17:50:28 coal kernel: [ 8001.556324] audit: type=1400 audit(1524581428.342:1954): apparmor="DENIED" operation="link" info="Failed name lookup - deleted entry" error=-2 profile="snap.vlc.vlc" name="/run/user/1000/snap.vlc/#511744" pid=19173 comm="vlc" requested_mask="l" denied_mask="l" fsuid=1000 ouid=1000 Apr 24 17:50:28 coal kernel: [ 8001.556332] audit: type=1400 audit(1524581428.342:1955): apparmor="DENIED" operation="link" profile="snap.vlc.vlc" name="/run/user/1000/snap.vlc/vlcbTrpmK.1.slave-socket" pid=19173 comm="vlc" requested_mask="l" denied_mask="l" fsuid=1000 ouid=1000 target="/run/user/1000/snap.vlc/#511744" Apr 24 17:50:28 coal kernel: [ 8001.556338] audit: type=1400 audit(1524581428.342:1956): apparmor="DENIED" operation="link" info="Failed name lookup - deleted entry" error=-2 profile="snap.vlc.vlc" name="/run/user/1000/snap.vlc/#511744" pid=19173 comm="vlc" requ
[Touch-packages] [Bug 1766628] Re: apparmor denies VLC to open files in devmode
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apparmor (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1766628 Title: apparmor denies VLC to open files in devmode Status in apparmor package in Ubuntu: Confirmed Bug description: I see failures in VLC trying to open files and prefs while VLC snap seemingly uses devmode since this is on Debian "testing". Failures: ^[[1;3CApr 24 17:50:24 coal kernel: [ 7997.906298] audit: type=1400 audit(1524581424.694:1944): apparmor="DENIED" operation="link" info="Failed name lookup - deleted entry" error=-2 profile="snap.vlc.vlc" name="/home/thresh/snap/vlc/288/.local/share/#268898190" pid=19173 comm="vlc" requested_mask="l" denied_mask="l" fsuid=1000 ouid=1000 Apr 24 17:50:24 coal kernel: [ 7997.906308] audit: type=1400 audit(1524581424.694:1945): apparmor="DENIED" operation="link" profile="snap.vlc.vlc" name="/home/thresh/snap/vlc/288/.local/share/user-places.xbel.tbcache" pid=19173 comm="vlc" requested_mask="l" denied_mask="l" fsuid=1000 ouid=1000 target="/home/thresh/snap/vlc/288/.local/share/#268898190" Apr 24 17:50:24 coal kernel: [ 7997.912113] audit: type=1400 audit(1524581424.698:1946): apparmor="DENIED" operation="link" info="Failed name lookup - deleted entry" error=-2 profile="snap.vlc.vlc" name="/home/thresh/snap/vlc/288/.local/share/#268898190" pid=19173 comm="vlc" requested_mask="l" denied_mask="l" fsuid=1000 ouid=1000 Apr 24 17:50:24 coal kernel: [ 7997.912122] audit: type=1400 audit(1524581424.698:1947): apparmor="DENIED" operation="link" profile="snap.vlc.vlc" name="/home/thresh/snap/vlc/288/.local/share/user-places.xbel" pid=19173 comm="vlc" requested_mask="l" denied_mask="l" fsuid=1000 ouid=1000 target="/home/thresh/snap/vlc/288/.local/share/#268898190" Apr 24 17:50:28 coal kernel: [ 8001.418173] audit: type=1400 audit(1524581428.206:1948): apparmor="DENIED" operation="link" info="Failed name lookup - deleted entry" error=-2 profile="snap.vlc.vlc" name="/home/thresh/snap/vlc/288/.local/share/#268898190" pid=19173 comm="vlc" requested_mask="l" denied_mask="l" fsuid=1000 ouid=1000 Apr 24 17:50:28 coal kernel: [ 8001.418180] audit: type=1400 audit(1524581428.206:1949): apparmor="DENIED" operation="link" profile="snap.vlc.vlc" name="/home/thresh/snap/vlc/288/.local/share/user-places.xbel.tbcache" pid=19173 comm="vlc" requested_mask="l" denied_mask="l" fsuid=1000 ouid=1000 target="/home/thresh/snap/vlc/288/.local/share/#268898190" Apr 24 17:50:28 coal kernel: [ 8001.422473] audit: type=1400 audit(1524581428.210:1950): apparmor="DENIED" operation="link" info="Failed name lookup - deleted entry" error=-2 profile="snap.vlc.vlc" name="/home/thresh/snap/vlc/288/.local/share/#268898190" pid=19173 comm="vlc" requested_mask="l" denied_mask="l" fsuid=1000 ouid=1000 Apr 24 17:50:28 coal kernel: [ 8001.422481] audit: type=1400 audit(1524581428.210:1951): apparmor="DENIED" operation="link" profile="snap.vlc.vlc" name="/home/thresh/snap/vlc/288/.local/share/user-places.xbel" pid=19173 comm="vlc" requested_mask="l" denied_mask="l" fsuid=1000 ouid=1000 target="/home/thresh/snap/vlc/288/.local/share/#268898190" Apr 24 17:50:28 coal kernel: [ 8001.556305] audit: type=1400 audit(1524581428.342:1952): apparmor="DENIED" operation="link" info="Failed name lookup - deleted entry" error=-2 profile="snap.vlc.vlc" name="/run/user/1000/snap.vlc/#511744" pid=19173 comm="vlc" requested_mask="l" denied_mask="l" fsuid=1000 ouid=1000 Apr 24 17:50:28 coal kernel: [ 8001.556318] audit: type=1400 audit(1524581428.342:1953): apparmor="DENIED" operation="link" profile="snap.vlc.vlc" name="/run/user/1000/snap.vlc/vlcxkYxzT.1.slave-socket" pid=19173 comm="vlc" requested_mask="l" denied_mask="l" fsuid=1000 ouid=1000 target="/run/user/1000/snap.vlc/#511744" Apr 24 17:50:28 coal kernel: [ 8001.556324] audit: type=1400 audit(1524581428.342:1954): apparmor="DENIED" operation="link" info="Failed name lookup - deleted entry" error=-2 profile="snap.vlc.vlc" name="/run/user/1000/snap.vlc/#511744" pid=19173 comm="vlc" requested_mask="l" denied_mask="l" fsuid=1000 ouid=1000 Apr 24 17:50:28 coal kernel: [ 8001.556332] audit: type=1400 audit(1524581428.342:1955): apparmor="DENIED" operation="link" profile="snap.vlc.vlc" name="/run/user/1000/snap.vlc/vlcbTrpmK.1.slave-socket" pid=19173 comm="vlc" requested_mask="l" denied_mask="l" fsuid=1000 ouid=1000 target="/run/user/1000/snap.vlc/#511744" Apr 24 17:50:28 coal kernel: [ 8001.556338] audit: type=1400 audit(1524581428.342:1956): apparmor="DENIED" operation="link" info="Failed name lookup - deleted entry" error=-2 profile="snap.vlc.vlc" name="/run/user/1000/snap.vlc/#511744" pid=19173 comm="vlc" requested_mask="l" denied_mask="l" fsuid=1000 ouid=1000 Apr 24 17:50
[Touch-packages] [Bug 1920067] Re: Xorg with EVDI can't start with Mesa 21.0
For those of you who landed here looking for how to use DisplayLink in Hirsute, I wrote up a workaround here: https://blog.kamens.us/2021/03/19 /update-on-using-displaylink-with-ubuntu-21-04-hirsute-hippo/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1920067 Title: Xorg with EVDI can't start with Mesa 21.0 Status in mesa package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: As I indicated in a bug report I filed earlier today, https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1920059, evdi-dkms can no longer compile the evdi kernel module with the 5.11 kernel. So, to work around this, I need to keep using the 5.10 kernel instead. But I can't, because when I boot with the 5.10 kernel this is what shows up in /var/log/Xorg.0.log when gdm3 tries to start up the login screen (note: I have an NVIDIA graphics card, which is why (I believe) Wayland isn't being used here): [ 857.957] (EE) modeset(G0): drmSetMaster failed: Device or resource busy [ 857.957] (EE) Fatal server error: [ 857.957] (EE) AddScreen/ScreenInit failed for gpu driver 0 -1 [ 857.957] (EE) [ 857.957] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 857.957] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. [ 857.957] (EE) [ 858.144] (EE) Server terminated with error (1). Closing log file. This is probably not what you will see in the Xorg.0.log (if any) attached automatically to this bug because I've completely wiped the evdi kernel module from my system since that was the only way I could get a display manager up so I could use ubuntu-bug to submit this bug. Here's what I updated today: 2021-03-18 15:03:26 upgrade sysvinit-utils:amd64 2.96-5ubuntu1 2.96-6ubuntu1 2021-03-18 15:03:27 upgrade cron:amd64 3.0pl1-136ubuntu1 3.0pl1-136ubuntu2 2021-03-18 15:03:28 upgrade gpg-wks-client:amd64 2.2.20-1ubuntu2 2.2.20-1ubuntu3 2021-03-18 15:03:28 upgrade dirmngr:amd64 2.2.20-1ubuntu2 2.2.20-1ubuntu3 2021-03-18 15:03:29 upgrade gpg-wks-server:amd64 2.2.20-1ubuntu2 2.2.20-1ubuntu3 2021-03-18 15:03:29 upgrade gnupg-utils:amd64 2.2.20-1ubuntu2 2.2.20-1ubuntu3 2021-03-18 15:03:29 upgrade gpg-agent:amd64 2.2.20-1ubuntu2 2.2.20-1ubuntu3 2021-03-18 15:03:30 upgrade gpg:amd64 2.2.20-1ubuntu2 2.2.20-1ubuntu3 2021-03-18 15:03:30 upgrade gpgconf:amd64 2.2.20-1ubuntu2 2.2.20-1ubuntu3 2021-03-18 15:03:30 upgrade gnupg-l10n:all 2.2.20-1ubuntu2 2.2.20-1ubuntu3 2021-03-18 15:03:31 upgrade gnupg:all 2.2.20-1ubuntu2 2.2.20-1ubuntu3 2021-03-18 15:03:31 upgrade gpgsm:amd64 2.2.20-1ubuntu2 2.2.20-1ubuntu3 2021-03-18 15:03:31 upgrade gpgv:amd64 2.2.20-1ubuntu2 2.2.20-1ubuntu3 2021-03-18 15:03:32 upgrade libjs-sphinxdoc:all 3.5.1-2 3.5.2-1 2021-03-18 15:03:33 upgrade libnfsidmap2:amd64 0.25-5.1ubuntu2 0.25-6 2021-03-18 15:03:33 install linux-modules-5.11.0-11-generic:amd64 5.11.0-11.12 2021-03-18 15:03:35 install linux-image-5.11.0-11-generic:amd64 5.11.0-11.12 2021-03-18 15:03:36 install linux-modules-extra-5.11.0-11-generic:amd64 5.11.0-11.12 2021-03-18 15:03:40 upgrade linux-generic:amd64 5.10.0.14.16 5.11.0.11.12 2021-03-18 15:03:40 upgrade linux-image-generic:amd64 5.10.0.14.16 5.11.0.11.12 2021-03-18 15:03:41 install linux-headers-5.11.0-11:all 5.11.0-11.12 2021-03-18 15:03:44 install linux-headers-5.11.0-11-generic:amd64 5.11.0-11.12 2021-03-18 15:03:47 upgrade linux-headers-generic:amd64 5.10.0.14.16 5.11.0.11.12 2021-03-18 15:03:47 upgrade linux-libc-dev:amd64 5.10.0-14.15 5.11.0-11.12 2021-03-18 15:03:48 upgrade slack-desktop:amd64 4.13.0 4.14.0 2021-03-18 15:03:52 upgrade xwayland:amd64 2:1.20.10-3ubuntu3 2:21.0.99.902-0ubuntu1 2021-03-18 15:56:42 upgrade at:amd64 3.1.23-1.1ubuntu2 3.1.23-1.1ubuntu3 At first glance I don't understand how any of these could be causing this behavior. Potentially relevant: I had to recompile and reinstall the evdi kernel module while booted into 5.10 because when I install the 5.11 kernel dkms removed the module from 5.10 and then failed to rebuild it because the 5.11 build failed (or something I don't really understand why dkms does what it does *sigh*). I don't see how that should matter because the recompiled version of the module should have been identical, but *shrug*. As noted above, when I remove the evdi kernel modules from /lib/modules and reboot with 5.10 the problem goes away, so this does appear to be an evdi issue. In short: despite the fact that it's not clear how upgrading any of the modules listed above would cause evdi that used to work to suddenly stop working, that appears to be the case. Any advice would be appreciated because now I can't use the displays connected to my DisplayLink hub with
[Touch-packages] [Bug 1916485] Re: test -x fails inside shell scripts in containers
** No longer affects: glibc (Ubuntu Hirsute) ** No longer affects: glibc (Ubuntu Groovy) ** No longer affects: glibc (Ubuntu Focal) ** No longer affects: glibc (Ubuntu Bionic) ** No longer affects: glibc (Ubuntu Xenial) ** No longer affects: glibc (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1916485 Title: test -x fails inside shell scripts in containers Status in docker.io package in Ubuntu: New Status in libseccomp package in Ubuntu: Fix Committed Status in runc package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in docker.io source package in Xenial: New Status in libseccomp source package in Xenial: New Status in runc source package in Xenial: New Status in systemd source package in Xenial: New Status in docker.io source package in Bionic: New Status in libseccomp source package in Bionic: New Status in runc source package in Bionic: Fix Committed Status in systemd source package in Bionic: New Status in docker.io source package in Focal: New Status in libseccomp source package in Focal: New Status in runc source package in Focal: Fix Committed Status in systemd source package in Focal: New Status in docker.io source package in Groovy: New Status in libseccomp source package in Groovy: New Status in runc source package in Groovy: Fix Committed Status in systemd source package in Groovy: Fix Released Status in docker.io source package in Hirsute: New Status in libseccomp source package in Hirsute: Fix Committed Status in runc source package in Hirsute: Fix Released Status in systemd source package in Hirsute: Fix Released Bug description: (SRU template for systemd) [impact] bash (and some other shells) builtin test command -x operation fails [test case] on any affected host system, start nspawn container, e.g.: $ sudo apt install systemd-container $ wget https://cloud-images.ubuntu.com/hirsute/current/hirsute-server-cloudimg-amd64-root.tar.xz $ mkdir h $ cd h $ tar xvf ../hirsute-server-cloudimg-amd64-root.tar.xz $ sudo systemd-nspawn Then from a bash shell, verify if test -x works: root@h:~# ls -l /usr/bin/gpg -rwxr-xr-x 1 1000 1000 1083472 Jan 16 09:53 /usr/bin/gpg root@h:~# test -x /usr/bin/gpg || echo "fail" fail [regression potential] any regression would likely occur during a syscall, most likely faccessat2(), or during other syscalls. [scope] this is needed for b/f this is fixed upstream by commit bcf08acbffdee0d6360d3c31d268e73d0623e5dc which is in 247 and later, so this is fixed in h this was pulled into Debian at version 246.2 in commit e80c5e5371ab77792bae94e0f8c5e85a4237e6eb, so this is fixed in g in x, the entire systemd seccomp code is completely different and the patch doesn't apply, nor does it appear to be needed, as the problem doesn't reproduce in a h container under x. [other info] this needs fixing in libseccomp as well [original description] glibc regression causes test -x to fail inside scripts inside docker/podman, dash and bash are broken, mksh and zsh are fine: root@0df2ce5d7a46:/# test -x /usr/bin/gpg || echo Fail root@0df2ce5d7a46:/# dash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# mksh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# zsh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# root@0df2ce5d7a46:/# zsh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# mksh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# dash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail The -f flag works, as does /usr/bin/test: # bash -c "test -f /usr/bin/gpg || echo Fail" # bash -c "/usr/bin/test -x /usr/bin/gpg || echo Fail" # [Original bug report] root@84b750e443f8:/# lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 root@84b750e443f8:/# dpkg -l gnupg apt Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-===--== ii apt2.1.20 amd64commandline package manager ii gnupg 2.2.20-1ubuntu2 all GNU privacy guard - a free PGP replacement Hi, for 3 days our CI pipelines to recreate Docker images fails for the Hirsute images. From comparison this seems to be caused by apt 2.1.20. The build fails with: 0E: gnupg, gnupg2 and unupg1 do not seem to be installed, but one
[Touch-packages] [Bug 1780332] Re: vaultlocker does not ensure that udev is triggered to create /dev/disk/by-uuid/ symlink and fails
Could somebody please test this _without_ work arounds on Bionic and
later?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1780332
Title:
vaultlocker does not ensure that udev is triggered to create /dev/disk
/by-uuid/ symlink and fails
Status in vaultlocker:
Fix Released
Status in cryptsetup package in Ubuntu:
Incomplete
Status in lvm2 package in Ubuntu:
Incomplete
Status in systemd package in Ubuntu:
Incomplete
Bug description:
When an encrypted device is setup up a UUID (osd_fsid) is passed from
the charm to be used in the cryptsetup command which accepts a UUID to
place into the LUKS header (shown in cryptsetup luksDump ).
https://github.com/openstack/charm-ceph-osd/blob/stable/18.05/lib/ceph/utils.py#L1788-L1804
UUID comes from osd_fsid
https://github.com/openstack-charmers/vaultlocker/blob/8c9cb85dc3ed5dbf18c66a810d189a5230d85c34/vaultlocker/shell.py#L69-L80
# else statement is used here
block_uuid = str(uuid.uuid4()) if not args.uuid else args.uuid
dmcrypt.luks_format(key, block_device, block_uuid) # creates a LUKS
header
# ...
dmcrypt.luks_open(key, block_uuid) # sets up a device with device mapper
decrypting it via dmcrypt
https://github.com/openstack-
charmers/vaultlocker/blob/d813233179bdf2eec8ed101c702a8e552a966f44/vaultlocker/dmcrypt.py#L44-L56
This UUID is visible in blkid output
/dev/sdc: UUID="" TYPE="crypto_LUKS"
and a udev rule exists to create a /dev/disk/by-uuid/ symlink (which is normally used for filesystem -> block device
resolution)
https://git.launchpad.net/~usd-import-team/ubuntu/+source/lvm2/tree/udev/13-dm-disk.rules.in#n25
ENV{ID_FS_USAGE}=="filesystem|other|crypto", ENV{ID_FS_UUID_ENC}=="?*",
SYMLINK+="disk/by-uuid/$env{ID_FS_UUID_ENC}"
Where vaultlocker fails is in luks_open command (right after luks_format)
# cryptsetup --batch-mode --key-file - open UUID=
crypt- --type luks
because it tries to access /dev/disk/by-uuid/ which
does not exist.
This happens since udev rules are not re-triggered to create this
symlink after a LUKS device is created.
Solution: call the command below after luks_format before luks_open
udevadm settle --exit-if-exists=/dev/disk/by-uuid/
To manage notifications about this bug go to:
https://bugs.launchpad.net/vaultlocker/+bug/1780332/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920248] [NEW] Anker Soundcore Life Q10 microphone not working
Public bug reported: I have a ThinkPad E560 with ubuntu 20.04 and I'm trying to use my Soundcore Life Q10 with it, but the microphone doesn't work. I tried also to follow some answers here, but no one worked for me. I tried to use blueman, but I get Failed to change profile to headset_head_unit. I tried to install oFono, but I cannot compile phonesim due to some problem with dependencies version. I think that PulseAudio does not support HFP out of the box, and I found many other people that has this problem (see for example https://itectec.com/ubuntu/ubuntu-use-bluetooth-headset-with-microphone- hfp-in-ubuntu-18-04/) Is there any way to make my headset working? ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: bluetooth microphone pulseaudio -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1920248 Title: Anker Soundcore Life Q10 microphone not working Status in pulseaudio package in Ubuntu: New Bug description: I have a ThinkPad E560 with ubuntu 20.04 and I'm trying to use my Soundcore Life Q10 with it, but the microphone doesn't work. I tried also to follow some answers here, but no one worked for me. I tried to use blueman, but I get Failed to change profile to headset_head_unit. I tried to install oFono, but I cannot compile phonesim due to some problem with dependencies version. I think that PulseAudio does not support HFP out of the box, and I found many other people that has this problem (see for example https://itectec.com/ubuntu/ubuntu-use-bluetooth-headset-with- microphone-hfp-in-ubuntu-18-04/) Is there any way to make my headset working? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1920248/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1902109] Re: rsync uses lchmod and fails in Ubuntu >= 20.10 if /proc isn't mounted
Actually, as far as I can tell this failure affects a much wider set of
cases. I am seeing this on a standard install as long as the (default)
"use chroot" option is being used.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
https://bugs.launchpad.net/bugs/1902109
Title:
rsync uses lchmod and fails in Ubuntu >= 20.10 if /proc isn't mounted
Status in GLibC:
Confirmed
Status in glibc package in Ubuntu:
Invalid
Status in rsync package in Ubuntu:
Triaged
Status in glibc source package in Groovy:
Invalid
Status in rsync source package in Groovy:
Won't Fix
Bug description:
Rsync in Ubuntu 20.10 fails when /proc isn't mounted, while it worked before.
This happens because AC_CHECK_FUNC(lchmod) returns "yes" in 20.10, while it
returned "no" before.
Steps to reproduce:
# Emulate /proc not being mounted
$ mount --bind / /mnt
$ chroot /mnt rsync -a /bin/ls .
rsync: [receiver] failed to set permissions on "/.ls.CDExhu": Operation not
supported (95)
rsync error: some files/attrs were not transferred (see previous errors)
(code 3) at main.c(1330) [sender=3.2.3]
I reported this issue upstream in
https://github.com/WayneD/rsync/issues/109 but the rsync developer
says it's a problem in libc, and it might well be.
Simple C code to reproduce the problem without rsync:
printf("lchmod returned: %d\n", lchmod("/tmp/ls", 0755));
If /tmp/ls is e.g. mode=0123, and needs to be changed, lchmod fails
when /proc isn't mounted, yet it succeeds if it is mounted.
Python had a similar issue, and they ended up avoiding
AC_CHECK_FUNC(lchmod) under Linux:
https://bugs.python.org/issue34652
https://github.com/python/cpython/commit/69e96910153219b0b15a18323b917bd74336d229#diff-49473dca262eeab3b4a43002adb08b4db31020d190caaad1594b47f1d5daa810R3140
```c
if test "$MACHDEP" != linux; then
AC_CHECK_FUNC(lchmod)
fi
```
So I'm not sure which package is causing the bug here. Should autoconf
return false? Should libc implement lchown without the bug? Or should
rsync skip lchmod under Linux, like python did?
To manage notifications about this bug go to:
https://bugs.launchpad.net/glibc/+bug/1902109/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1894172] Re: isc-dhcp-server using wrong env variable for INTERFACES
Hello,
I just did the verification and the upgrade seems to be working as
intended for me. I went ahead and added the verficiation-done tag (and
the release-specific tags as well!).
** Tags removed: verification-needed verification-needed-bionic
verification-needed-focal verification-needed-groovy
** Tags added: verification-done verification-done-bionic
verification-done-focal verification-done-groovy
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1894172
Title:
isc-dhcp-server using wrong env variable for INTERFACES
Status in isc-dhcp package in Ubuntu:
Fix Released
Status in isc-dhcp source package in Bionic:
Fix Committed
Status in isc-dhcp source package in Focal:
Fix Committed
Status in isc-dhcp source package in Groovy:
Fix Committed
Bug description:
[Impact]
When checking isc-dhcp-server unit file it was seen that isc-dhcp-
server is being started by:
ConditionPathExists=/etc/default/isc-dhcp-server
ConditionPathExists=|/etc/ltsp/dhcpd.conf
ConditionPathExists=|/etc/dhcp/dhcpd.conf
[Service]
EnvironmentFile=/etc/default/isc-dhcp-server
RuntimeDirectory=dhcp-server
# The leases files need to be root:dhcpd even when dropping privileges
ExecStart=/bin/sh -ec '\
CONFIG_FILE=/etc/dhcp/dhcpd.conf; \
if [ -f /etc/ltsp/dhcpd.conf ]; then CONFIG_FILE=/etc/ltsp/dhcpd.conf;
fi; \
[ -e /var/lib/dhcp/dhcpd.leases ] || touch /var/lib/dhcp/dhcpd.leases; \
chown root:dhcpd /var/lib/dhcp /var/lib/dhcp/dhcpd.leases; \
chmod 775 /var/lib/dhcp ; chmod 664 /var/lib/dhcp/dhcpd.leases; \
exec dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid
-cf $CONFIG_FILE $INTERFACES'
But the /etc/default/isc-dhcp-server file sets $INTERFACESv4 and
$INTERFACESv6.
This causes the service to listen on all interfaces, which is what the
user might not want. In case the user wants to use *only* IPv6 and not
IPv4, this could maybe lead to problems as what the user intended to
do could be really different from what the outcome turns out to be
(because of this bug).
The previous upload(er) forgot to mention (and split) the INTERFACES
variable to v4 and v6 and as a result, it has been this way for so
long.
The SRU would split the variables into respective names, thereby
making sure that what /etc/default/isc-dhcp-serve sets, is available
in the respective service file.
[Test Plan]
To reproduce this bug, simply do the following:
$ lxc launch ubuntu-daily:focal isc-dhcp-lp1894172-focal
$ lxc shell isc-dhcp-lp1894172-focal
# apt update && apt install isc-dhcp-server -y
# grep "INTERFACES" /etc/default/isc-dhcp-server
INTERFACESv4=""
INTERFACESv6=""
grep "INTERFACES" /lib/systemd/system/isc-dhcp-server.service
exec dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid
-cf $CONFIG_FILE $INTERFACES'
# grep "INTERFACES" /lib/systemd/system/isc-dhcp-server6.service
exec dhcpd -user dhcpd -group dhcpd -f -6 -pf /run/dhcp-server/dhcpd6.pid
-cf $CONFIG_FILE $INTERFACES'
With this, it is clearly visible that even though /lib/systemd/system
/isc-dhcp-server{,6}.service file uses the INTERFACES variable but the
/etc/default/isc-dhcp-server defines 2 different variables,
INTERFACESv4 and INTERFACESv6.
After the SRU is performed, the respective services files should use
INTERFACESv4 and INTERFACESv6 variable, instead of just INTERFACES.
To ensure smooth upgrade of this package, we'd check if the user
hasn't manually set a INTERFACESv{4,6} variable to workaround this
bug. If they have, then we simply check and make sure, we use the
correct variable.
[Where problems could occur]
The problem could occur if the user has manually set some different
workaround for this bug and so the usual upgrade could break some of
their old configuration(s).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1894172/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920130] Re: System icons missing in kubuntu 21.04
Just to show window decorations ** Attachment added: "screenshot3.png" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1920130/+attachment/5478239/+files/screenshot3.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1920130 Title: System icons missing in kubuntu 21.04 Status in xorg package in Ubuntu: New Bug description: Hi, just testing Kubuntu 21.04 on a spare machine. The upgrade initially was fine, but I then install kdenlive and krita which has messed up the system icons and window decorations (corners of windows are showing black squares). I have been through all the normal checks and even created a new user, but the bug still persists. The system Icons are broken in the system and nothing to do with the user account. lsb_release -rd Description:Ubuntu Hirsute Hippo (development branch) Release:21.04 Looking at the following may shed some light on the problem... Thanks, Paul. more .xsession-errors property "maximumWidth" file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "maximumWidth" file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "maximumWidth" libpng warning: iCCP: profile 'ICC profile': 'RGB ': RGB color space not permitted on grayscale PNG libpng warning: iCCP: profile 'ICC profile': 'RGB ': RGB color space not permitted on grayscale PNG QSGTextureAtlas: texture atlas allocation failed, code=501 file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/AbstractApplicationItem.qml:94: TypeError: Cannot read pro perty 'position' of null file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/AbstractApplicationItem.qml:93: TypeError: Cannot read pro perty 'background' of null file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/newstuff/qml/Page.qml:130: TypeError: Cannot read property 'useLabel' of null file:///usr/share/kpackage/kcms/kcm_splashscreen/contents/ui/main.qml:42:13: QML ColumnLayout: Cannot anchor to an ite m that isn't a parent or sibling. qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 55182, resource id: 69206064, major code: 18 (ChangePr operty), minor code: 0 qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 64351, resource id: 69206065, major code: 18 (ChangePr operty), minor code: 0 QQmlEngine::setContextForObject(): Object already has a QQmlContext file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "maximumWidth" file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "maximumWidth" file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "maximumWidth" QSGTextureAtlas: texture atlas allocation failed, code=501 file:///usr/share/kpackage/kcms/kcm_style/contents/ui/main.qml:52:13: QML ColumnLayout: Cannot anchor to an item that isn't a parent or sibling. xsettingsd: Reloading configuration xsettingsd: Loaded 11 settings from /home/paul/.config/xsettingsd/xsettingsd.conf kdeinit5: Got SETENV 'GTK_RC_FILES=/etc/gtk/gtkrc:/home/paul/.gtkrc:/home/paul/.config/gtkrc' from launcher. kdeinit5: Got SETENV 'GTK2_RC_FILES=/etc/gtk-2.0/gtkrc:/home/paul/.gtkrc-2.0:/home/paul/.config/gtkrc-2.0' from launch er. QDBusConnection: error: could not send signal to service "" path "//home/paul/.kde/share/config/kdeglobals" interface "org.kde.kconfig.notify" member "ConfigChanged": Invalid object path: //home/paul/.kde/share/config/kdeglobals QQmlEngine::setContextForObject(): Object already has a QQmlContext file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls.2/org.kde.desktop/ScrollView.qml:86:25: QML ScrollBar: Bindi ng loop detected for property "visible" file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kcm/GridViewKCM.qml:65:5: QML GridView: Binding loop detected for pro perty "rightPadding" file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "maximumWidth" file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirig
[Touch-packages] [Bug 1920130] Re: System icons missing in kubuntu 21.04
Some updates: All kde apps when starting report on the command line (Eg. when starting kate): Icon theme "Breeze" not found. tried reinstalling breeze-icon-theme but its still the same. The package is there, but kde cannot find it after the upgrade to 21.04 from 20.10. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1920130 Title: System icons missing in kubuntu 21.04 Status in xorg package in Ubuntu: New Bug description: Hi, just testing Kubuntu 21.04 on a spare machine. The upgrade initially was fine, but I then install kdenlive and krita which has messed up the system icons and window decorations (corners of windows are showing black squares). I have been through all the normal checks and even created a new user, but the bug still persists. The system Icons are broken in the system and nothing to do with the user account. lsb_release -rd Description:Ubuntu Hirsute Hippo (development branch) Release:21.04 Looking at the following may shed some light on the problem... Thanks, Paul. more .xsession-errors property "maximumWidth" file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "maximumWidth" file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "maximumWidth" libpng warning: iCCP: profile 'ICC profile': 'RGB ': RGB color space not permitted on grayscale PNG libpng warning: iCCP: profile 'ICC profile': 'RGB ': RGB color space not permitted on grayscale PNG QSGTextureAtlas: texture atlas allocation failed, code=501 file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/AbstractApplicationItem.qml:94: TypeError: Cannot read pro perty 'position' of null file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/AbstractApplicationItem.qml:93: TypeError: Cannot read pro perty 'background' of null file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/newstuff/qml/Page.qml:130: TypeError: Cannot read property 'useLabel' of null file:///usr/share/kpackage/kcms/kcm_splashscreen/contents/ui/main.qml:42:13: QML ColumnLayout: Cannot anchor to an ite m that isn't a parent or sibling. qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 55182, resource id: 69206064, major code: 18 (ChangePr operty), minor code: 0 qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 64351, resource id: 69206065, major code: 18 (ChangePr operty), minor code: 0 QQmlEngine::setContextForObject(): Object already has a QQmlContext file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "maximumWidth" file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "maximumWidth" file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "maximumWidth" QSGTextureAtlas: texture atlas allocation failed, code=501 file:///usr/share/kpackage/kcms/kcm_style/contents/ui/main.qml:52:13: QML ColumnLayout: Cannot anchor to an item that isn't a parent or sibling. xsettingsd: Reloading configuration xsettingsd: Loaded 11 settings from /home/paul/.config/xsettingsd/xsettingsd.conf kdeinit5: Got SETENV 'GTK_RC_FILES=/etc/gtk/gtkrc:/home/paul/.gtkrc:/home/paul/.config/gtkrc' from launcher. kdeinit5: Got SETENV 'GTK2_RC_FILES=/etc/gtk-2.0/gtkrc:/home/paul/.gtkrc-2.0:/home/paul/.config/gtkrc-2.0' from launch er. QDBusConnection: error: could not send signal to service "" path "//home/paul/.kde/share/config/kdeglobals" interface "org.kde.kconfig.notify" member "ConfigChanged": Invalid object path: //home/paul/.kde/share/config/kdeglobals QQmlEngine::setContextForObject(): Object already has a QQmlContext file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls.2/org.kde.desktop/ScrollView.qml:86:25: QML ScrollBar: Bindi ng loop detected for property "visible" file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kcm/GridViewKCM.qml:65:5: QML GridView: Binding loop detected for pro perty "rightPadding" file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop
[Touch-packages] [Bug 1920130] Re: System icons missing in kubuntu 21.04
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1920130 Title: System icons missing in kubuntu 21.04 Status in xorg package in Ubuntu: New Bug description: Hi, just testing Kubuntu 21.04 on a spare machine. The upgrade initially was fine, but I then install kdenlive and krita which has messed up the system icons and window decorations (corners of windows are showing black squares). I have been through all the normal checks and even created a new user, but the bug still persists. The system Icons are broken in the system and nothing to do with the user account. lsb_release -rd Description:Ubuntu Hirsute Hippo (development branch) Release:21.04 Looking at the following may shed some light on the problem... Thanks, Paul. more .xsession-errors property "maximumWidth" file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "maximumWidth" file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "maximumWidth" libpng warning: iCCP: profile 'ICC profile': 'RGB ': RGB color space not permitted on grayscale PNG libpng warning: iCCP: profile 'ICC profile': 'RGB ': RGB color space not permitted on grayscale PNG QSGTextureAtlas: texture atlas allocation failed, code=501 file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/AbstractApplicationItem.qml:94: TypeError: Cannot read pro perty 'position' of null file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/AbstractApplicationItem.qml:93: TypeError: Cannot read pro perty 'background' of null file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/newstuff/qml/Page.qml:130: TypeError: Cannot read property 'useLabel' of null file:///usr/share/kpackage/kcms/kcm_splashscreen/contents/ui/main.qml:42:13: QML ColumnLayout: Cannot anchor to an ite m that isn't a parent or sibling. qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 55182, resource id: 69206064, major code: 18 (ChangePr operty), minor code: 0 qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 64351, resource id: 69206065, major code: 18 (ChangePr operty), minor code: 0 QQmlEngine::setContextForObject(): Object already has a QQmlContext file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "maximumWidth" file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "maximumWidth" file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "maximumWidth" QSGTextureAtlas: texture atlas allocation failed, code=501 file:///usr/share/kpackage/kcms/kcm_style/contents/ui/main.qml:52:13: QML ColumnLayout: Cannot anchor to an item that isn't a parent or sibling. xsettingsd: Reloading configuration xsettingsd: Loaded 11 settings from /home/paul/.config/xsettingsd/xsettingsd.conf kdeinit5: Got SETENV 'GTK_RC_FILES=/etc/gtk/gtkrc:/home/paul/.gtkrc:/home/paul/.config/gtkrc' from launcher. kdeinit5: Got SETENV 'GTK2_RC_FILES=/etc/gtk-2.0/gtkrc:/home/paul/.gtkrc-2.0:/home/paul/.config/gtkrc-2.0' from launch er. QDBusConnection: error: could not send signal to service "" path "//home/paul/.kde/share/config/kdeglobals" interface "org.kde.kconfig.notify" member "ConfigChanged": Invalid object path: //home/paul/.kde/share/config/kdeglobals QQmlEngine::setContextForObject(): Object already has a QQmlContext file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls.2/org.kde.desktop/ScrollView.qml:86:25: QML ScrollBar: Bindi ng loop detected for property "visible" file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kcm/GridViewKCM.qml:65:5: QML GridView: Binding loop detected for pro perty "rightPadding" file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "maximumWidth" file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding lo
[Touch-packages] [Bug 1920133] Re: normal use then sys seizure then reboot
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1920133 Title: normal use then sys seizure then reboot Status in xorg package in Ubuntu: New Bug description: I was using VS Code system seized up then rebooted no error messages ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-67.75-generic 5.4.94 Uname: Linux 5.4.0-67-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Mar 19 12:15:31 2021 DistUpgraded: 2021-01-09 08:43:22,797 DEBUG /openCache(), new cache size 67902 DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family Integrated Graphics Controller [1043:84ca] InstallationDate: Installed on 2015-08-23 (2034 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-67-generic root=UUID=155c3c3c-daa6-414c-ac3d-0f8c492592c0 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to focal on 2021-01-09 (69 days ago) dmi.bios.date: 07/21/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V LX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2501:bd07/21/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2021-01-13T09:36:03.851337 version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 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 1:2.10.6-1 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 xserver.bootTime: Mon Aug 20 17:24:57 2018 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1920133/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920130] [NEW] System icons missing in kubuntu 21.04
You have been subscribed to a public bug: Hi, just testing Kubuntu 21.04 on a spare machine. The upgrade initially was fine, but I then install kdenlive and krita which has messed up the system icons and window decorations (corners of windows are showing black squares). I have been through all the normal checks and even created a new user, but the bug still persists. The system Icons are broken in the system and nothing to do with the user account. lsb_release -rd Description:Ubuntu Hirsute Hippo (development branch) Release:21.04 Looking at the following may shed some light on the problem... Thanks, Paul. more .xsession-errors property "maximumWidth" file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "maximumWidth" file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "maximumWidth" libpng warning: iCCP: profile 'ICC profile': 'RGB ': RGB color space not permitted on grayscale PNG libpng warning: iCCP: profile 'ICC profile': 'RGB ': RGB color space not permitted on grayscale PNG QSGTextureAtlas: texture atlas allocation failed, code=501 file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/AbstractApplicationItem.qml:94: TypeError: Cannot read pro perty 'position' of null file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/AbstractApplicationItem.qml:93: TypeError: Cannot read pro perty 'background' of null file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/newstuff/qml/Page.qml:130: TypeError: Cannot read property 'useLabel' of null file:///usr/share/kpackage/kcms/kcm_splashscreen/contents/ui/main.qml:42:13: QML ColumnLayout: Cannot anchor to an ite m that isn't a parent or sibling. qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 55182, resource id: 69206064, major code: 18 (ChangePr operty), minor code: 0 qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 64351, resource id: 69206065, major code: 18 (ChangePr operty), minor code: 0 QQmlEngine::setContextForObject(): Object already has a QQmlContext file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "maximumWidth" file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "maximumWidth" file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "maximumWidth" QSGTextureAtlas: texture atlas allocation failed, code=501 file:///usr/share/kpackage/kcms/kcm_style/contents/ui/main.qml:52:13: QML ColumnLayout: Cannot anchor to an item that isn't a parent or sibling. xsettingsd: Reloading configuration xsettingsd: Loaded 11 settings from /home/paul/.config/xsettingsd/xsettingsd.conf kdeinit5: Got SETENV 'GTK_RC_FILES=/etc/gtk/gtkrc:/home/paul/.gtkrc:/home/paul/.config/gtkrc' from launcher. kdeinit5: Got SETENV 'GTK2_RC_FILES=/etc/gtk-2.0/gtkrc:/home/paul/.gtkrc-2.0:/home/paul/.config/gtkrc-2.0' from launch er. QDBusConnection: error: could not send signal to service "" path "//home/paul/.kde/share/config/kdeglobals" interface "org.kde.kconfig.notify" member "ConfigChanged": Invalid object path: //home/paul/.kde/share/config/kdeglobals QQmlEngine::setContextForObject(): Object already has a QQmlContext file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls.2/org.kde.desktop/ScrollView.qml:86:25: QML ScrollBar: Bindi ng loop detected for property "visible" file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kcm/GridViewKCM.qml:65:5: QML GridView: Binding loop detected for pro perty "rightPadding" file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "maximumWidth" file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "maximumWidth" file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "maximumWidth" QSGTextureAtlas: texture atlas allocation failed, code=501 file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls.2/org.kde.desktop/private/M
[Touch-packages] [Bug 1920133] [NEW] normal use then sys seizure then reboot
You have been subscribed to a public bug: I was using VS Code system seized up then rebooted no error messages ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-67.75-generic 5.4.94 Uname: Linux 5.4.0-67-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Mar 19 12:15:31 2021 DistUpgraded: 2021-01-09 08:43:22,797 DEBUG /openCache(), new cache size 67902 DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family Integrated Graphics Controller [1043:84ca] InstallationDate: Installed on 2015-08-23 (2034 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-67-generic root=UUID=155c3c3c-daa6-414c-ac3d-0f8c492592c0 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to focal on 2021-01-09 (69 days ago) dmi.bios.date: 07/21/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V LX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2501:bd07/21/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2021-01-13T09:36:03.851337 version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 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 1:2.10.6-1 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 xserver.bootTime: Mon Aug 20 17:24:57 2018 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.7 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug crash focal ubuntu -- normal use then sys seizure then reboot https://bugs.launchpad.net/bugs/1920133 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1876570] Re: Could not resume from hibernation when swap is specified as device
This bug was fixed in the package initramfs-tools - 0.139ubuntu2 --- initramfs-tools (0.139ubuntu2) hirsute; urgency=medium * scripts/local-premount/resume: - Use readlink -f to correctly handle non-symlink $resume (LP: #1876570) * d/t/control: - autopkgtests running qemu need root, add needs-root restriction * hook-functions: - when MODULES=list there will be no 'kernel' dir, so don't try to find anything there, as it will log an 'error' this is needed for amd64-ata-only autopkgtest to pass, or we would need to ignore the 'error' with allow-stderr -- Dan Streetman Thu, 18 Mar 2021 14:48:17 -0400 ** Changed in: initramfs-tools (Ubuntu Hirsute) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1876570 Title: Could not resume from hibernation when swap is specified as device Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: In Progress Status in initramfs-tools source package in Focal: In Progress Status in initramfs-tools source package in Groovy: In Progress Status in initramfs-tools source package in Hirsute: Fix Released Bug description: [impact] unable to resume from hibernation when resume= boot param is specified as device path [test case] set up device/partition for swap, e.g. /dev/vda2 add 'resume=/dev/vda2' kernel boot parameter hibernate power system back on; it should resume from /dev/vda2 instead of coldboot [regression potential] any regression would likely result in failure to correctly resume from hibernation, incorrectly attempting to resume from hibernation, or failing to resume from hibernation. [scope] this is needed in b/f/g/h this bug was introduced, ironically, by bug 1644975, which was added in bionic, so this bug doesn't exist in xenial. this code that introduced this bug isn't included in Debian, so no change is needed there. [original description] I originally experienced this on Pop!_OS but I have reproduced it on a freshly installed Ubuntu. 1. Ubuntu 20.04 LTS 2. initramfs-tools-core 0.136ubuntu6 3. I expect the system to resume from hibernation when running pm_hibernate 4. The system starts up anew when I try to resume I have setup a swap partition on /dev/vda2 in /etc/fstab. To enable hibernate I added the kernel parameter "resume=/dev/vda2" to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub and run update-grub. From debugging initramfs it tries to follow a symbolic link DEV=$(readlink "$resume") (see /usr/share/initramfs-tools/scripts/local-premount/resume, line 35) which works well when swap is specified with uuid. When swap is specified as a device directly the readlink returns an empty string and the system does not resume from hibernation. To verify this I added the parameter -f to readlink and run "update- initramfs -u". The system now hibernates successfully. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 3 13:26:02 2020 InstallationDate: Installed on 2020-05-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1876570/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1912091] Re: Memory Leak GNU Tar 1.33
The fix is in the newer version which is included in the current Ubuntu https://bugs.launchpad.net/ubuntu/+source/tar/1.34+dfsg-1 it still need to be applied to older series though ** Changed in: tar (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tar in Ubuntu. https://bugs.launchpad.net/bugs/1912091 Title: Memory Leak GNU Tar 1.33 Status in tar package in Ubuntu: Fix Released Bug description: An issue was discovered in GNU Tar 1.33 and earlier. There is a memory leak in read_header() in list.c in the tar application. Occastionally, ASAN detects an out of bounds memory read. Valgrind confirms the memory leak in the standard tar tool installed by default. This degrades the availability of the tar tool, and could potentially result in other memory-related issues. Common Weakness Enumeration IDs for reference: CWE-401: Missing Release of Memory after Effective Lifetime CWE-125: Out-of-bounds Read Attached to this report is a PoC malcrafted file "1311745-out- bounds.tar" VALGRIND OUTPUT: valgrind tar -xf 1311745-out-bounds.tar ==3776== Memcheck, a memory error detector ==3776== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==3776== Using Valgrind-3.16.1 and LibVEX; rerun with -h for copyright info ==3776== Command: tar -xf output/1311745-out-bounds.tar ==3776== tar: Unexpected EOF in archive tar: Exiting with failure status due to previous errors ==3776== ==3776== HEAP SUMMARY: ==3776== in use at exit: 1,311,761 bytes in 2 blocks ==3776== total heap usage: 52 allocs, 50 frees, 1,349,212 bytes allocated ==3776== ==3776== LEAK SUMMARY: ==3776==definitely lost: 1,311,745 bytes in 1 blocks ... NOTE: Version 1.30, 1.32, 1.33 were tested and confirmed to be vulnerable. lsb_release -rd Description: Ubuntu 20.04.1 LTS Release: 20.04 apt-cache policy tar tar: Installed: 1.30+dfsg-7ubuntu0.20.04.1 Candidate: 1.30+dfsg-7ubuntu0.20.04.1 --- Carlos To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tar/+bug/1912091/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1903048] Re: [SRU] Bluetooth won't activate on the pi 400
Thanks, uploaded to the focal queue now! ** Changed in: bluez (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1903048 Title: [SRU] Bluetooth won't activate on the pi 400 Status in bluez package in Ubuntu: Fix Released Status in bluez source package in Focal: Fix Committed Status in bluez source package in Groovy: Fix Released Status in bluez source package in Hirsute: Fix Released Bug description: [Impact] Without these patches, Bluetooth is inoperable on the recently released Raspberry Pi 400. [Test Case] * Boot the Ubuntu Desktop for Pi image on a Pi 400. * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is not enabled and attempting to activate it fails * Enable the -proposed repository for the release (groovy) * sudo apt update * sudo apt install bluez * sudo reboot * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is active and that Bluetooth devices (e.g. mice, mobile phones, headphones, etc.) can connect and operate correctly [Regression Potential] Extremely low (on groovy in particular, this has the same version of bluez as hirsute). The only significant risk is to non-Pi platforms or dongles which also use the Broadcom 43xx (or Cypress 305) chips for Bluetooth which might be inadvertently affected by these patches. [Original Description] The new Pi 400 has a slightly different Wifi/BT chip to the Pi4. Whilst wifi works happily, Bluetooth fails to operate. This doesn't appear to be an issue with either the firmware (the latest versions from upstream Raspbian have been tried), or the kernel (a known-good raspi kernel has been tested under Ubuntu), but with Bluez itself. Specifically, tracing the initialization with btmon on Raspbian and Ubuntu, the stack consistently fails when attempting to "Set Default PHY" on the latter. Curiously, under Ubuntu the adapter also appears to lack a MAC address. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903048/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1902464] Re: The rear panel of Lenovo P620 doesn't support more than one audio device at the same time
Since alsa-ucm-conf is updated by following the upstream version. ``` commit aa74f4c12eefcc98582572d2fc48982cf7478b51 (tag: pkg/import/1.2.4-1) Author: Jordi Mallach Date: Mon Dec 7 22:13:23 2020 +0100 1.2.4-1 (patches unapplied) Imported using git-ubuntu import. Notes (changelog): * New upstream release. * Update Standards-Version to 4.5.1, with no changes needed. ``` Above commit already brought https://github.com/alsa-project/alsa-ucm- conf/tree/master/ucm2/USB-Audio for P620 parts. ** Changed in: alsa-ucm-conf (Ubuntu) Assignee: Hui Wang (hui.wang) => (unassigned) ** Changed in: alsa-ucm-conf (Ubuntu) Status: New => Fix Released ** Description changed: After backporting following patches from PA and alsa-ucm-conf and then it works. https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/290 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/354 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/355 https://github.com/alsa-project/alsa-ucm-conf/tree/master/ucm2/USB-Audio + [landed by aa74f4c12eefcc98582572d2fc48982cf7478b51] Here is the test PPA: https://launchpad.net/~os369510/+archive/ubuntu/oem-package-test Since the upstream not yet accepted those patches, the regression potential may quite high. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1902464 Title: The rear panel of Lenovo P620 doesn't support more than one audio device at the same time Status in HWE Next: New Status in OEM Priority Project: Confirmed Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: New Bug description: After backporting following patches from PA and alsa-ucm-conf and then it works. https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/290 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/354 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/355 https://github.com/alsa-project/alsa-ucm-conf/tree/master/ucm2/USB- Audio [landed by aa74f4c12eefcc98582572d2fc48982cf7478b51] Here is the test PPA: https://launchpad.net/~os369510/+archive/ubuntu/oem-package-test Since the upstream not yet accepted those patches, the regression potential may quite high. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1902464/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1902464] Re: The rear panel of Lenovo P620 doesn't support more than one audio device at the same time
@Seb, do you think I can work on SRU https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/354 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/355 these two patches? since the #290 patch seems like still need a long time discussion on upstream and only this patch have high potential regression risk. so far I need to backport these three patches and maintain on our archive. If we could reduce the scope then it will be helpful in current situation. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1902464 Title: The rear panel of Lenovo P620 doesn't support more than one audio device at the same time Status in HWE Next: New Status in OEM Priority Project: Confirmed Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: New Bug description: After backporting following patches from PA and alsa-ucm-conf and then it works. https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/290 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/354 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/355 https://github.com/alsa-project/alsa-ucm-conf/tree/master/ucm2/USB- Audio [landed by aa74f4c12eefcc98582572d2fc48982cf7478b51] Here is the test PPA: https://launchpad.net/~os369510/+archive/ubuntu/oem-package-test Since the upstream not yet accepted those patches, the regression potential may quite high. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1902464/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920106] Re: Eye strain on using ubuntu but not windows
Thanks for the bug report. In order to assign this bug to the correct component and investigate it properly we will need more information about what is specifically wrong with the image. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1920106 Title: Eye strain on using ubuntu but not windows Status in Ubuntu: Incomplete Bug description: I am not sure if the bug is with intel drivers or with font rendering or with xorg but I am facing eye strain on ubuntu(and other distributions as well, and other desktop environments too) but not on windows. Although I'm not sure, if I had to guess I would say bug is in intel drivers. The issue exists when I switch to wayland as well. I have tried tweaking hinting and aliasing settings of fonts using gnome- tweaks(or equivalent in other DEs) but to no effect. Maybe something is wrong with colors on linux so I copied my ICC profile from windows over to linux and applied it but that didn't work either. I just want a fix for my problem as it prevents me from using ubuntu. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.39 Thu Jan 21 21:54:06 UTC 2021 GCC version: 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: Fri Mar 19 11:38:32 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:8a56] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:09ea] InstallationDate: Installed on 2021-03-19 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. Vostro 14 5401 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-45-generic root=UUID=18819299-a0e3-4e05-83b0-9d0f57b4c653 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2020 dmi.bios.release: 1.5 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.3 dmi.board.name: 0C54N1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.3:bd12/18/2020:br1.5:svnDellInc.:pnVostro145401:pvr:rvnDellInc.:rn0C54N1:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 14 5401 dmi.product.sku: 09EA dmi.sys.vendor: Dell 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 N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1920106/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920106] Re: Eye strain on using ubuntu but not windows
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1920106 Title: Eye strain on using ubuntu but not windows Status in xorg package in Ubuntu: New Bug description: I am not sure if the bug is with intel drivers or with font rendering or with xorg but I am facing eye strain on ubuntu(and other distributions as well, and other desktop environments too) but not on windows. Although I'm not sure, if I had to guess I would say bug is in intel drivers. The issue exists when I switch to wayland as well. I have tried tweaking hinting and aliasing settings of fonts using gnome- tweaks(or equivalent in other DEs) but to no effect. Maybe something is wrong with colors on linux so I copied my ICC profile from windows over to linux and applied it but that didn't work either. I just want a fix for my problem as it prevents me from using ubuntu. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.39 Thu Jan 21 21:54:06 UTC 2021 GCC version: 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: Fri Mar 19 11:38:32 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:8a56] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:09ea] InstallationDate: Installed on 2021-03-19 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. Vostro 14 5401 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-45-generic root=UUID=18819299-a0e3-4e05-83b0-9d0f57b4c653 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2020 dmi.bios.release: 1.5 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.3 dmi.board.name: 0C54N1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.3:bd12/18/2020:br1.5:svnDellInc.:pnVostro145401:pvr:rvnDellInc.:rn0C54N1:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 14 5401 dmi.product.sku: 09EA dmi.sys.vendor: Dell 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 N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1920106/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920106] [NEW] Eye strain on using ubuntu but not windows
You have been subscribed to a public bug: I am not sure if the bug is with intel drivers or with font rendering or with xorg but I am facing eye strain on ubuntu(and other distributions as well, and other desktop environments too) but not on windows. Although I'm not sure, if I had to guess I would say bug is in intel drivers. The issue exists when I switch to wayland as well. I have tried tweaking hinting and aliasing settings of fonts using gnome-tweaks(or equivalent in other DEs) but to no effect. Maybe something is wrong with colors on linux so I copied my ICC profile from windows over to linux and applied it but that didn't work either. I just want a fix for my problem as it prevents me from using ubuntu. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.39 Thu Jan 21 21:54:06 UTC 2021 GCC version: 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: Fri Mar 19 11:38:32 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:8a56] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:09ea] InstallationDate: Installed on 2021-03-19 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. Vostro 14 5401 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-45-generic root=UUID=18819299-a0e3-4e05-83b0-9d0f57b4c653 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2020 dmi.bios.release: 1.5 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.3 dmi.board.name: 0C54N1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.3:bd12/18/2020:br1.5:svnDellInc.:pnVostro145401:pvr:rvnDellInc.:rn0C54N1:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 14 5401 dmi.product.sku: 09EA dmi.sys.vendor: Dell 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 N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A 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 ubuntu -- Eye strain on using ubuntu but not windows https://bugs.launchpad.net/bugs/1920106 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1906653] Re: Backport systemd to make uevents "sticky"
@Dan I see, thank you anyway :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1906653 Title: Backport systemd to make uevents "sticky" Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Won't Fix Status in systemd source package in Groovy: Won't Fix Status in systemd source package in Hirsute: Fix Released Bug description: Base on lwn 837033 [0], Linux 4.12 introduced two new uevents "bind" and "unbind" to the Linux device model which resulted in a number of software issues. So in this PR [1] which minimize issues resulting from this kernel change (but not avoid them entirely) by make uevent "sticky", meaning that once a tag is assigned to a device it will not be removed from the device again until the device itself is removed (i.e. unplugged). An example causing by this issue, I had a usb printer (non-ippusbxd) which connected to my laptop, but after unplugging it from my laptop, the .device unit were still present, if a different printer gets plugged to the same USB port then, it won't be configured correctly. [0] https://lwn.net/Articles/837033/ [1] https://github.com/systemd/systemd/pull/16853/files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1906653/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
