[Touch-packages] [Bug 1880222] Re: ubuntu bionic-backports Hash Sum mismatch
[Expired for apt (Ubuntu) because there has been no activity for 60 days.] ** Changed in: apt (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1880222 Title: ubuntu bionic-backports Hash Sum mismatch Status in apt package in Ubuntu: Expired Status in update-manager package in Ubuntu: Expired Bug description: # apt-get update (proceeded normally until...) Err:24 http://us.archive.ubuntu.com/ubuntu bionic-backports i386 Contents (deb) Hash Sum mismatch Hashes of expected file: - Filesize:724924 [weak] - SHA256:d59f30b35a9fd0f52922cbf3a4bf1f0713e816a209cca57bac1dbc56af3c9a77 - SHA1:0d1e53232da2c41febc6cccecfc4000f930c3450 [weak] - MD5Sum:dfa1f7010a23b70c967aef7600ebd49f [weak] Hashes of received file: - SHA256:1c97d900fc3b9168c38bf870b1dd7c71be88ff72e0751c1551b8129c8de98740 - SHA1:a725025e50c3ebd60dd16058594340b4ca9c97e2 [weak] - MD5Sum:925bb2a78f81a2dc9b4269a6f5e9ece5 [weak] - Filesize:90948 [weak] Release file created at: Fri, 22 May 2020 16:49:51 + Fetched 254 MB in 51s (5,014 kB/s) Reading package lists... Done E: Failed to fetch store:/var/lib/apt/lists/partial/us.archive.ubuntu.com_ubuntu_dists_bionic-backports_Contents-i386.gz Hash Sum mismatch Hashes of expected file: - Filesize:724924 [weak] - SHA256:d59f30b35a9fd0f52922cbf3a4bf1f0713e816a209cca57bac1dbc56af3c9a77 - SHA1:0d1e53232da2c41febc6cccecfc4000f930c3450 [weak] - MD5Sum:dfa1f7010a23b70c967aef7600ebd49f [weak] Hashes of received file: - SHA256:1c97d900fc3b9168c38bf870b1dd7c71be88ff72e0751c1551b8129c8de98740 - SHA1:a725025e50c3ebd60dd16058594340b4ca9c97e2 [weak] - MD5Sum:925bb2a78f81a2dc9b4269a6f5e9ece5 [weak] - Filesize:90948 [weak] Release file created at: Fri, 22 May 2020 16:49:51 + E: Some index files failed to download. They have been ignored, or old ones used instead. $ apt-get -v apt 1.6.12ubuntu0.1 (amd64) Also, Software Updater (version 1:18.04.11.12) after hitting "Install" gives pop-up: "Requires installation of untrusted packages This requires installing packages from unauthenticated sources." Only options: "Settings..." and "OK" And it is not OK; I have not configured any unauthenticated sources! This occurs when enabling updates from Ubuntu Base (but not Security updates). I expected to not get such errors and updating to occur normally. $ lsb_release -rd Description: Ubuntu 18.04.4 LTS Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1880222/+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 1880222] Re: ubuntu bionic-backports Hash Sum mismatch
[Expired for update-manager (Ubuntu) because there has been no activity for 60 days.] ** Changed in: update-manager (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1880222 Title: ubuntu bionic-backports Hash Sum mismatch Status in apt package in Ubuntu: Expired Status in update-manager package in Ubuntu: Expired Bug description: # apt-get update (proceeded normally until...) Err:24 http://us.archive.ubuntu.com/ubuntu bionic-backports i386 Contents (deb) Hash Sum mismatch Hashes of expected file: - Filesize:724924 [weak] - SHA256:d59f30b35a9fd0f52922cbf3a4bf1f0713e816a209cca57bac1dbc56af3c9a77 - SHA1:0d1e53232da2c41febc6cccecfc4000f930c3450 [weak] - MD5Sum:dfa1f7010a23b70c967aef7600ebd49f [weak] Hashes of received file: - SHA256:1c97d900fc3b9168c38bf870b1dd7c71be88ff72e0751c1551b8129c8de98740 - SHA1:a725025e50c3ebd60dd16058594340b4ca9c97e2 [weak] - MD5Sum:925bb2a78f81a2dc9b4269a6f5e9ece5 [weak] - Filesize:90948 [weak] Release file created at: Fri, 22 May 2020 16:49:51 + Fetched 254 MB in 51s (5,014 kB/s) Reading package lists... Done E: Failed to fetch store:/var/lib/apt/lists/partial/us.archive.ubuntu.com_ubuntu_dists_bionic-backports_Contents-i386.gz Hash Sum mismatch Hashes of expected file: - Filesize:724924 [weak] - SHA256:d59f30b35a9fd0f52922cbf3a4bf1f0713e816a209cca57bac1dbc56af3c9a77 - SHA1:0d1e53232da2c41febc6cccecfc4000f930c3450 [weak] - MD5Sum:dfa1f7010a23b70c967aef7600ebd49f [weak] Hashes of received file: - SHA256:1c97d900fc3b9168c38bf870b1dd7c71be88ff72e0751c1551b8129c8de98740 - SHA1:a725025e50c3ebd60dd16058594340b4ca9c97e2 [weak] - MD5Sum:925bb2a78f81a2dc9b4269a6f5e9ece5 [weak] - Filesize:90948 [weak] Release file created at: Fri, 22 May 2020 16:49:51 + E: Some index files failed to download. They have been ignored, or old ones used instead. $ apt-get -v apt 1.6.12ubuntu0.1 (amd64) Also, Software Updater (version 1:18.04.11.12) after hitting "Install" gives pop-up: "Requires installation of untrusted packages This requires installing packages from unauthenticated sources." Only options: "Settings..." and "OK" And it is not OK; I have not configured any unauthenticated sources! This occurs when enabling updates from Ubuntu Base (but not Security updates). I expected to not get such errors and updating to occur normally. $ lsb_release -rd Description: Ubuntu 18.04.4 LTS Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1880222/+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 1861941] Re: bcache by-uuid links disappear after mounting bcache0
About blkid fix: Ryan has explained carefully how to obtain FS UUID from
the backing device at:
https://github.com/systemd/systemd/pull/16317#issuecomment-655574875
and about bcache-export-cached wrapper he created for simulating
CACHED_UUID and CACHED_LABEL (at 69-bcache.rules) and to create
/dev/bcache/{by-uuid,by-label}/{CACHED_UUID,CACHED_LABEL} symlinks.
He explained that having /dev/bcache/{by-uuid,by-label} is mandatory to
maintain same names for multiple bcache'd environments over reboots.
Currently, with the bcache-export-cached fix applied, it is *not*
mandatory to have systemd-udev fix to correctly create bcache symlinks
(or not) at /dev/disk/{by-uuid,by-label}: libblkid could have more
information regarding bcache backing devices, but judging by upstream
developers disposition they don't seem too worried about having that
feature since ID_FS_TYPE=bcache is already provided. (So, having
/dev/disk/by-uuid/XXX pointing to bcache backing devices would continue
happening...)
Summary:
Having the bcache-tools fix is enough for this bug (LP: #1861941) and
there could be changes to systemd-udev (I doubt judging by discussions
at https://github.com/systemd/systemd/pull/16317), or libblkid, that
could provide more information regarding bcache device types. If those
changes happen, we would need to revisit this bug.
IMHO,
I like the "skip_bcache_fs_type" approach done by Ryan to systemd-udev.
I'll maintain that as a delta to udev until
https://github.com/systemd/systemd/pull/16317 is fixed (if ever).
So, for now, PPA contains fix for bcache-tools for Groovy and Focal (and
will for Bionic) and that is enough to make /dev/bcache/XXX to work and
be stable after reboots. I'll keep the udev fix for Groovy and SRU that
fix for Focal and Bionic and upload to the PPA as well.
After all that is done, I'll tell kernel team to revert the bcache patch
on Bionic, Focal and Groovy kernels since it is not needed and will
reduce their delta and reduce chances of regressions over time.
--
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/1861941
Title:
bcache by-uuid links disappear after mounting bcache0
Status in bcache-tools package in Ubuntu:
In Progress
Status in systemd package in Ubuntu:
In Progress
Status in bcache-tools source package in Bionic:
In Progress
Status in systemd source package in Bionic:
In Progress
Status in bcache-tools source package in Focal:
In Progress
Status in systemd source package in Focal:
In Progress
Bug description:
1.
root@ubuntu:~# lsb_release -rd
Description: Ubuntu Focal Fossa (development branch)
Release: 20.04
2.
root@ubuntu:~# lsb_release -rd
Description: Ubuntu Focal Fossa (development branch)
Release: 20.04
root@ubuntu:~# apt-cache policy linux-image-virtual
linux-image-virtual:
Installed: 5.4.0.12.15
Candidate: 5.4.0.12.15
Version table:
*** 5.4.0.12.15 500
500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status
root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic
linux-image-5.4.0-12-generic:
Installed: 5.4.0-12.15
Candidate: 5.4.0-12.15
Version table:
*** 5.4.0-12.15 500
500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status
3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/
+ ls -al /dev/bcache/by-uuid/
total 0
drwxr-xr-x 2 root root 60 Feb 4 23:31 .
drwxr-xr-x 3 root root 60 Feb 4 23:31 ..
lrwxrwxrwx 1 root root 13 Feb 4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a
-> ../../bcache0
4.
root@ubuntu:~# ls -al /dev/bcache/by-uuid
ls: cannot access '/dev/bcache/by-uuid': No such file or directory
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-12-generic 5.4.0-12.15
ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
Uname: Linux 5.4.0-12-generic x86_64
ApportVersion: 2.20.11-0ubuntu16
Architecture: amd64
Date: Tue Feb 4 23:31:52 2020
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=C.UTF-8
SHELL=/bin/bash
SourcePackage: linux-signed-5.4
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+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 1882248] Re: [SRU] plug headset won't proper reconfig ouput to it on machine with default output
@Seb, for the pulseaudio bionic, I remember you already pushed a build for this SRU to the queue, so @foundation team, could you please build it since our oem project is waiting for this fix. thx. -- 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/1882248 Title: [SRU] plug headset won't proper reconfig ouput to it on machine with default output Status in HWE Next: New Status in OEM Priority Project: Confirmed Status in linux-oem package in Ubuntu: New Status in pulseaudio package in Ubuntu: Fix Released Status in linux-oem source package in Bionic: Fix Released Status in pulseaudio source package in Bionic: Fix Committed Bug description: This is for pulseaudio bionic: [Impact] On a Dell machine without internal spk and internal mic, after freshly install the bionic on it, the active profile is Off, after users plug a headset to it and users select the headset from the pop-up dialogue, users expect the profile changes to analog-stereo (headset is on it), but the active_profile is still Off. [Fix] Upstream already has a patch to fix it, cherrypiack that patch to bionic. And that patch is already in the eoan, focal, ... [Test Case] freshly install the bionic with this patch on that dell machine, plug headset and select the headset from UI, the profile changes to analog-stereo, and play some sound, we could hear it from the headset [Regression Risk] Low, this patch is already in the upstream for a long time, and it is already in the eoan and focal. For linux kernel (oem-b): [Impact] On a Dell machine without internal spk and internal mic, after freshly install the bionic on it, and users plug a headset, the sound couldn't output from headset. [Fix] reverse the order of headset mic and headphone mic [Test Case] freshly install the bionic with this patch on that dell machine, plug headset and play sound, we could hear the sound from headset. [Regression Risk] Low, this patch only affects the machine without internal mic and internal spk, and I already tested this patch on the machine without internal mic and internal spk, it worked well. target machine does not have built-in speaker, and the monitor does not have an audio output (like d-sub VGA) As first boot, there will be a "dummy output" in g-c-c. After plug-in headset, there will be a headset appear in g-c-c, but it won't be automatically selected even it's chosen in the pop-up window. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1882248/+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 1861941] Re: bcache by-uuid links disappear after mounting bcache0
PPA containing (for now) fixes for Groovy and Focal: https://launchpad.net/~rafaeldtinoco/+archive/ubuntu/lp1861941 will contain fix for Bionic as well. Testcase: https://paste.ubuntu.com/p/37KGy2Smnp/ Testcase passes for both versions when having PPA pkgs installed. -- 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/1861941 Title: bcache by-uuid links disappear after mounting bcache0 Status in bcache-tools package in Ubuntu: In Progress Status in systemd package in Ubuntu: In Progress Status in bcache-tools source package in Bionic: In Progress Status in systemd source package in Bionic: In Progress Status in bcache-tools source package in Focal: In Progress Status in systemd source package in Focal: In Progress Bug description: 1. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 2. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 5.4.0.12.15 Candidate: 5.4.0.12.15 Version table: *** 5.4.0.12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic linux-image-5.4.0-12-generic: Installed: 5.4.0-12.15 Candidate: 5.4.0-12.15 Version table: *** 5.4.0-12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/ + ls -al /dev/bcache/by-uuid/ total 0 drwxr-xr-x 2 root root 60 Feb 4 23:31 . drwxr-xr-x 3 root root 60 Feb 4 23:31 .. lrwxrwxrwx 1 root root 13 Feb 4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a -> ../../bcache0 4. root@ubuntu:~# ls -al /dev/bcache/by-uuid ls: cannot access '/dev/bcache/by-uuid': No such file or directory ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Tue Feb 4 23:31:52 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+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 1888598] [NEW] pulseaudio has is buggy with hdmi audio and sleep/wake
Public bug reported: on a fresh Ubuntu 20.04 x64 install, I've noticed some troubling bugs with pulseaudio after putting my system to sleep and then waking it up. these bugs aren't present on a fresh boot, only after resuming from sleep: - it forgets which sound output device it's set to, and always reverse to the motherboard's S/PDIF output. - I have two devices connected to my video card, one is a displayport monitor, and one is a home theater receiver via HDMI. it confuses the two, and randomly switches which device it thinks is capable of surround sound. - it sometimes refuses to switch to the correct audio device, and just resets any choice back to the internal S/PDIF, until the system is rebooted. as you can imagine, this a pretty frustrating state of affairs. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.4 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tessa 3387 F pulseaudio /dev/snd/pcmC1D7p: tessa 3387 F...m pulseaudio /dev/snd/controlC2: tessa 3387 F pulseaudio /dev/snd/controlC0: tessa 3387 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 22 18:38:42 2020 InstallationDate: Installed on 2020-07-15 (7 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3503 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: GRYPHON Z97 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx 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.:bvr3503:bd04/18/2018:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnGRYPHONZ97:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1888598 Title: pulseaudio has is buggy with hdmi audio and sleep/wake Status in pulseaudio package in Ubuntu: New Bug description: on a fresh Ubuntu 20.04 x64 install, I've noticed some troubling bugs with pulseaudio after putting my system to sleep and then waking it up. these bugs aren't present on a fresh boot, only after resuming from sleep: - it forgets which sound output device it's set to, and always reverse to the motherboard's S/PDIF output. - I have two devices connected to my video card, one is a displayport monitor, and one is a home theater receiver via HDMI. it confuses the two, and randomly switches which device it thinks is capable of surround sound. - it sometimes refuses to switch to the correct audio device, and just resets any choice back to the internal S/PDIF, until the system is rebooted. as you can imagine, this a pretty frustrating state of affairs. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.4 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tessa 3387 F pulseaudio /dev/snd/pcmC1D7p: tessa 3387 F...m pulseaudio /dev/snd/controlC2: tessa 3387 F pulseaudio /dev/snd/controlC0: tessa 3387 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 22 18:38:42 2020 InstallationDate: Installed on 2020-07-15 (7 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3503 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: GRYPHON Z97 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx 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:
[Touch-packages] [Bug 1888571] Re: Screen flickering and glitching after install
> Intel integrated driver causes screen flickering with Ubuntu install. I think you mean the generic 'modeset' driver, which is the correct driver to use and the one shown in your XorgLog attachments. If you were using 'xserver-xorg-video-intel' then please just uninstall that package. It should not be used and commonly causes problems (bug 1867668). Most likely I think this is a kernel bug relating to: [ 117.852074] sof-audio-pci :00:1f.3: error: no reply expected, received 0x0 [ 117.944970] sof-audio-pci :00:1f.3: firmware boot complete [ 170.252664] sof-audio-pci :00:1f.3: error: no reply expected, received 0x0 [ 170.347691] sof-audio-pci :00:1f.3: firmware boot complete [ 235.442471] sof-audio-pci :00:1f.3: error: no reply expected, received 0x0 [ 235.537670] sof-audio-pci :00:1f.3: firmware boot complete ... ** Tags added: ice-lake-flicker ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Summary changed: - Screen flickering and glitching after install + [Ice Lake] Screen flickering and glitching after install -- 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/1888571 Title: [Ice Lake] Screen flickering and glitching after install Status in linux package in Ubuntu: Confirmed Bug description: Intel integrated driver causes screen flickering with Ubuntu install. Windows did not have this issue ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 22 15:41:42 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Iris Plus Graphics G7 [103c:875a] InstallationDate: Installed on 2020-07-22 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: HP HP ENVY Laptop 13-ba0xxx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=9f807172-2b35-4ad1-9f33-5a912ad7c579 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/04/2020 dmi.bios.vendor: Insyde dmi.bios.version: F.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 875A dmi.board.vendor: HP dmi.board.version: 07.34 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.10:bd06/04/2020:svnHP:pnHPENVYLaptop13-ba0xxx:pvrType1ProductConfigId:rvnHP:rn875A:rvr07.34:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY Laptop 13-ba0xxx dmi.product.sku: 8KD13AV dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 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/linux/+bug/1888571/+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 1888442] Re: upgrade did not go well
These cryptsetup warnings and errors are indeed due to my zfs use, I see them several times a month for the life of the machine, roughly the last ten months. Don't let the 'error' there scare you, as it did me. I don't understand them, but they also don't appear to have any consequences. The problem is visible well before the cryptsetup is run: Fetched 110 MB in 15s (7,164 kB/s) Extracting templates from packages: 100% Preconfiguring packages ... (Reading database ... 214052 files and directories currently installed.) Preparing to unpack .../base-files_11ubuntu5.1_amd64.deb ... Warning: Stopping motd-news.service, but it can still be activated by: motd-news.timer Unpacking base-files (11ubuntu5.1) over (11ubuntu5) ... Failed to reload daemon: Connection timed out Failed to reload daemon: Connection timed out Setting up base-files (11ubuntu5.1) ... It's entirely possible systemctl daemon-reload commands were failing because I undocked my laptop. (The dmesg buffer did have some ugly stuff in it.) But I've heard more than one person complain about apt upgrades including systemd packages leading to system instability, and that feels more like what I saw. Thanks ** Package changed: zfs-linux (Ubuntu) => systemd (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/1888442 Title: upgrade did not go well Status in systemd package in Ubuntu: New Bug description: Hello, I had some problems during my most recent apt upgrade. A confounding factor to these problems was removing my laptop from its docking station a few minutes earlier. $ sudo apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following NEW packages will be installed: linux-headers-5.4.0-42 linux-headers-5.4.0-42-generic linux-image-5.4.0-42-generic linux-modules-5.4.0-42-generic linux-modules-extra-5.4.0-42-generic python3-click python3-colorama The following packages will be upgraded: base-files libnss-mymachines libnss-systemd libpam-systemd libpulse-mainloop-glib0 libpulse0 libpulsedsp libseccomp2 libsystemd0 libudev1 libvirt-clients libvirt-daemon libvirt-daemon-driver-qemu libvirt-daemon-driver-storage-rbd libvirt-daemon-driver-storage-zfs libvirt-daemon-system libvirt-daemon-system-systemd libvirt0 linux-firmware linux-generic linux-headers-generic linux-image-generic pulseaudio pulseaudio-utils python3-distupgrade sudo systemd systemd-container systemd-journal-remote systemd-sysv systemd-timesyncd ubuntu-drivers-common ubuntu-release-upgrader-core udev 34 upgraded, 7 newly installed, 0 to remove and 0 not upgraded. Need to get 110 MB/184 MB of archives. After this operation, 360 MB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://wopr.domain/ubuntu focal-proposed/main amd64 base-files amd64 11ubuntu5.1 [60.1 kB] Get:2 http://wopr.domain/ubuntu focal-proposed/main amd64 libnss-systemd amd64 245.4-4ubuntu3.2 [95.6 kB] Get:3 http://wopr.domain/ubuntu focal-proposed/universe amd64 systemd-journal-remote amd64 245.4-4ubuntu3.2 [61.9 kB] Get:4 http://wopr.domain/ubuntu focal-proposed/main amd64 udev amd64 245.4-4ubuntu3.2 [1,363 kB] Get:5 http://wopr.domain/ubuntu focal-proposed/main amd64 libudev1 amd64 245.4-4ubuntu3.2 [78.9 kB] Get:6 http://wopr.domain/ubuntu focal-proposed/main amd64 libvirt-daemon-system amd64 6.0.0-0ubuntu8.2 [67.5 kB] Get:7 http://wopr.domain/ubuntu focal-proposed/main amd64 libvirt-clients amd64 6.0.0-0ubuntu8.2 [343 kB] Get:8 http://wopr.domain/ubuntu focal-proposed/main amd64 libvirt-daemon-driver-qemu amd64 6.0.0-0ubuntu8.2 [605 kB] Get:9 http://wopr.domain/ubuntu focal-proposed/universe amd64 libvirt-daemon-driver-storage-zfs amd64 6.0.0-0ubuntu8.2 [21.4 kB] Get:10 http://wopr.domain/ubuntu focal-proposed/main amd64 libvirt-daemon-driver-storage-rbd amd64 6.0.0-0ubuntu8.2 [28.3 kB] Get:11 http://wopr.domain/ubuntu focal-proposed/main amd64 libvirt0 amd64 6.0.0-0ubuntu8.2 [1,444 kB] Get:12 http://wopr.domain/ubuntu focal-proposed/main amd64 libvirt-daemon amd64 6.0.0-0ubuntu8.2 [404 kB] Get:13 http://wopr.domain/ubuntu focal-proposed/main amd64 libnss-mymachines amd64 245.4-4ubuntu3.2 [131 kB] Get:14 http://wopr.domain/ubuntu focal-proposed/main amd64 libseccomp2 amd64 2.4.3-1ubuntu3.20.04.3 [42.4 kB] Get:15 http://wopr.domain/ubuntu focal-proposed/main amd64 systemd-container amd64 245.4-4ubuntu3.2 [317 kB] Get:16 http://wopr.domain/ubuntu focal-proposed/main amd64 libvirt-daemon-system-systemd amd64 6.0.0-0ubuntu8.2 [12.3 kB] Get:17 http://wopr.domain/ubuntu focal-proposed/main amd64 systemd-sysv amd64 245.4-4ubuntu3.2 [10.3 kB] Get:18 http://wopr.domain/ubuntu focal-proposed/main amd64 systemd-timesyncd amd64 245.4-4ubuntu3.2 [28.0 kB]
[Touch-packages] [Bug 1861941] Re: bcache by-uuid links disappear after mounting bcache0
Focal Merge Request: FOCAL: https://tinyurl.com/y3tbd3un -- 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/1861941 Title: bcache by-uuid links disappear after mounting bcache0 Status in bcache-tools package in Ubuntu: In Progress Status in systemd package in Ubuntu: In Progress Status in bcache-tools source package in Bionic: In Progress Status in systemd source package in Bionic: In Progress Status in bcache-tools source package in Focal: In Progress Status in systemd source package in Focal: In Progress Bug description: 1. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 2. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 5.4.0.12.15 Candidate: 5.4.0.12.15 Version table: *** 5.4.0.12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic linux-image-5.4.0-12-generic: Installed: 5.4.0-12.15 Candidate: 5.4.0-12.15 Version table: *** 5.4.0-12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/ + ls -al /dev/bcache/by-uuid/ total 0 drwxr-xr-x 2 root root 60 Feb 4 23:31 . drwxr-xr-x 3 root root 60 Feb 4 23:31 .. lrwxrwxrwx 1 root root 13 Feb 4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a -> ../../bcache0 4. root@ubuntu:~# ls -al /dev/bcache/by-uuid ls: cannot access '/dev/bcache/by-uuid': No such file or directory ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Tue Feb 4 23:31:52 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+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 1888442] [NEW] upgrade did not go well
You have been subscribed to a public bug: Hello, I had some problems during my most recent apt upgrade. A confounding factor to these problems was removing my laptop from its docking station a few minutes earlier. $ sudo apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following NEW packages will be installed: linux-headers-5.4.0-42 linux-headers-5.4.0-42-generic linux-image-5.4.0-42-generic linux-modules-5.4.0-42-generic linux-modules-extra-5.4.0-42-generic python3-click python3-colorama The following packages will be upgraded: base-files libnss-mymachines libnss-systemd libpam-systemd libpulse-mainloop-glib0 libpulse0 libpulsedsp libseccomp2 libsystemd0 libudev1 libvirt-clients libvirt-daemon libvirt-daemon-driver-qemu libvirt-daemon-driver-storage-rbd libvirt-daemon-driver-storage-zfs libvirt-daemon-system libvirt-daemon-system-systemd libvirt0 linux-firmware linux-generic linux-headers-generic linux-image-generic pulseaudio pulseaudio-utils python3-distupgrade sudo systemd systemd-container systemd-journal-remote systemd-sysv systemd-timesyncd ubuntu-drivers-common ubuntu-release-upgrader-core udev 34 upgraded, 7 newly installed, 0 to remove and 0 not upgraded. Need to get 110 MB/184 MB of archives. After this operation, 360 MB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://wopr.domain/ubuntu focal-proposed/main amd64 base-files amd64 11ubuntu5.1 [60.1 kB] Get:2 http://wopr.domain/ubuntu focal-proposed/main amd64 libnss-systemd amd64 245.4-4ubuntu3.2 [95.6 kB] Get:3 http://wopr.domain/ubuntu focal-proposed/universe amd64 systemd-journal-remote amd64 245.4-4ubuntu3.2 [61.9 kB] Get:4 http://wopr.domain/ubuntu focal-proposed/main amd64 udev amd64 245.4-4ubuntu3.2 [1,363 kB] Get:5 http://wopr.domain/ubuntu focal-proposed/main amd64 libudev1 amd64 245.4-4ubuntu3.2 [78.9 kB] Get:6 http://wopr.domain/ubuntu focal-proposed/main amd64 libvirt-daemon-system amd64 6.0.0-0ubuntu8.2 [67.5 kB] Get:7 http://wopr.domain/ubuntu focal-proposed/main amd64 libvirt-clients amd64 6.0.0-0ubuntu8.2 [343 kB] Get:8 http://wopr.domain/ubuntu focal-proposed/main amd64 libvirt-daemon-driver-qemu amd64 6.0.0-0ubuntu8.2 [605 kB] Get:9 http://wopr.domain/ubuntu focal-proposed/universe amd64 libvirt-daemon-driver-storage-zfs amd64 6.0.0-0ubuntu8.2 [21.4 kB] Get:10 http://wopr.domain/ubuntu focal-proposed/main amd64 libvirt-daemon-driver-storage-rbd amd64 6.0.0-0ubuntu8.2 [28.3 kB] Get:11 http://wopr.domain/ubuntu focal-proposed/main amd64 libvirt0 amd64 6.0.0-0ubuntu8.2 [1,444 kB] Get:12 http://wopr.domain/ubuntu focal-proposed/main amd64 libvirt-daemon amd64 6.0.0-0ubuntu8.2 [404 kB] Get:13 http://wopr.domain/ubuntu focal-proposed/main amd64 libnss-mymachines amd64 245.4-4ubuntu3.2 [131 kB] Get:14 http://wopr.domain/ubuntu focal-proposed/main amd64 libseccomp2 amd64 2.4.3-1ubuntu3.20.04.3 [42.4 kB] Get:15 http://wopr.domain/ubuntu focal-proposed/main amd64 systemd-container amd64 245.4-4ubuntu3.2 [317 kB] Get:16 http://wopr.domain/ubuntu focal-proposed/main amd64 libvirt-daemon-system-systemd amd64 6.0.0-0ubuntu8.2 [12.3 kB] Get:17 http://wopr.domain/ubuntu focal-proposed/main amd64 systemd-sysv amd64 245.4-4ubuntu3.2 [10.3 kB] Get:18 http://wopr.domain/ubuntu focal-proposed/main amd64 systemd-timesyncd amd64 245.4-4ubuntu3.2 [28.0 kB] Get:19 http://wopr.domain/ubuntu focal-proposed/main amd64 libpam-systemd amd64 245.4-4ubuntu3.2 [186 kB] Get:20 http://wopr.domain/ubuntu focal-proposed/main amd64 systemd amd64 245.4-4ubuntu3.2 [3,796 kB] Get:21 http://wopr.domain/ubuntu focal-proposed/main amd64 libsystemd0 amd64 245.4-4ubuntu3.2 [271 kB] Get:22 http://wopr.domain/ubuntu focal-proposed/main amd64 libpulse-mainloop-glib0 amd64 1:13.99.1-1ubuntu3.5 [11.7 kB] Get:23 http://wopr.domain/ubuntu focal-proposed/main amd64 libpulsedsp amd64 1:13.99.1-1ubuntu3.5 [21.7 kB] Get:24 http://wopr.domain/ubuntu focal-proposed/main amd64 pulseaudio-utils amd64 1:13.99.1-1ubuntu3.5 [55.0 kB] Get:25 http://wopr.domain/ubuntu focal-proposed/main amd64 pulseaudio amd64 1:13.99.1-1ubuntu3.5 [815 kB] Get:26 http://wopr.domain/ubuntu focal-proposed/main amd64 libpulse0 amd64 1:13.99.1-1ubuntu3.5 [263 kB] Get:27 http://wopr.domain/ubuntu focal/main amd64 python3-colorama all 0.4.3-1build1 [23.9 kB] Get:28 http://wopr.domain/ubuntu focal/main amd64 python3-click all 7.0-3 [64.8 kB] Get:29 http://wopr.domain/ubuntu focal-proposed/main amd64 ubuntu-drivers-common amd64 1:0.8.4~0.20.04.1 [45.2 kB] Get:30 http://wopr.domain/ubuntu focal-proposed/main amd64 sudo amd64 1.8.31-1ubuntu1.1 [513 kB] Get:31 http://wopr.domain/ubuntu focal-proposed/main amd64 ubuntu-release-upgrader-core all 1:20.04.23 [23.6 kB] Get:32 http://wopr.domain/ubuntu focal-proposed/main amd64 python3-distupgrade all 1:20.04.23 [103 kB] Get:33 http://wopr.domain/ubuntu focal-proposed/main amd64 linux-firmware
[Touch-packages] [Bug 1861941] Re: bcache by-uuid links disappear after mounting bcache0
** Merge proposal linked: https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/bcache-tools/+git/bcache-tools/+merge/387909 -- 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/1861941 Title: bcache by-uuid links disappear after mounting bcache0 Status in bcache-tools package in Ubuntu: In Progress Status in systemd package in Ubuntu: In Progress Status in bcache-tools source package in Bionic: In Progress Status in systemd source package in Bionic: In Progress Status in bcache-tools source package in Focal: In Progress Status in systemd source package in Focal: In Progress Bug description: 1. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 2. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 5.4.0.12.15 Candidate: 5.4.0.12.15 Version table: *** 5.4.0.12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic linux-image-5.4.0-12-generic: Installed: 5.4.0-12.15 Candidate: 5.4.0-12.15 Version table: *** 5.4.0-12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/ + ls -al /dev/bcache/by-uuid/ total 0 drwxr-xr-x 2 root root 60 Feb 4 23:31 . drwxr-xr-x 3 root root 60 Feb 4 23:31 .. lrwxrwxrwx 1 root root 13 Feb 4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a -> ../../bcache0 4. root@ubuntu:~# ls -al /dev/bcache/by-uuid ls: cannot access '/dev/bcache/by-uuid': No such file or directory ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Tue Feb 4 23:31:52 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+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 1861941] Re: bcache by-uuid links disappear after mounting bcache0
Groovy Merge Request: BUG: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1861941 PPA: https://launchpad.net/~rafaeldtinoco/+archive/ubuntu/lp1861941 GROOVY: https://tinyurl.com/yxonp5hz -- 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/1861941 Title: bcache by-uuid links disappear after mounting bcache0 Status in bcache-tools package in Ubuntu: In Progress Status in systemd package in Ubuntu: In Progress Status in bcache-tools source package in Bionic: In Progress Status in systemd source package in Bionic: In Progress Status in bcache-tools source package in Focal: In Progress Status in systemd source package in Focal: In Progress Bug description: 1. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 2. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 5.4.0.12.15 Candidate: 5.4.0.12.15 Version table: *** 5.4.0.12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic linux-image-5.4.0-12-generic: Installed: 5.4.0-12.15 Candidate: 5.4.0-12.15 Version table: *** 5.4.0-12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/ + ls -al /dev/bcache/by-uuid/ total 0 drwxr-xr-x 2 root root 60 Feb 4 23:31 . drwxr-xr-x 3 root root 60 Feb 4 23:31 .. lrwxrwxrwx 1 root root 13 Feb 4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a -> ../../bcache0 4. root@ubuntu:~# ls -al /dev/bcache/by-uuid ls: cannot access '/dev/bcache/by-uuid': No such file or directory ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Tue Feb 4 23:31:52 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+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 1861941] Re: bcache by-uuid links disappear after mounting bcache0
** Merge proposal linked: https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/bcache-tools/+git/bcache-tools/+merge/387908 -- 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/1861941 Title: bcache by-uuid links disappear after mounting bcache0 Status in bcache-tools package in Ubuntu: In Progress Status in systemd package in Ubuntu: In Progress Status in bcache-tools source package in Bionic: In Progress Status in systemd source package in Bionic: In Progress Status in bcache-tools source package in Focal: In Progress Status in systemd source package in Focal: In Progress Bug description: 1. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 2. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 5.4.0.12.15 Candidate: 5.4.0.12.15 Version table: *** 5.4.0.12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic linux-image-5.4.0-12-generic: Installed: 5.4.0-12.15 Candidate: 5.4.0-12.15 Version table: *** 5.4.0-12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/ + ls -al /dev/bcache/by-uuid/ total 0 drwxr-xr-x 2 root root 60 Feb 4 23:31 . drwxr-xr-x 3 root root 60 Feb 4 23:31 .. lrwxrwxrwx 1 root root 13 Feb 4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a -> ../../bcache0 4. root@ubuntu:~# ls -al /dev/bcache/by-uuid ls: cannot access '/dev/bcache/by-uuid': No such file or directory ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Tue Feb 4 23:31:52 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+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 1861941] Re: bcache by-uuid links disappear after mounting bcache0
Debian patch submitted (removed previous patch and proposed new one based on what was proposed to upstream): https://salsa.debian.org/debian/bcache-tools/-/merge_requests/2 Tests are good, I could run testcase multiple times and wasn't able to reproduce the original issue. ** Changed in: bcache-tools (Ubuntu) Status: Fix Released => In Progress ** Changed in: bcache-tools (Ubuntu Bionic) Status: Triaged => In Progress ** Changed in: bcache-tools (Ubuntu Focal) Status: Confirmed => In Progress ** Changed in: systemd (Ubuntu Focal) Status: Triaged => In Progress ** Changed in: systemd (Ubuntu Bionic) Status: Triaged => In Progress ** Changed in: systemd (Ubuntu) Status: Fix Released => In Progress -- 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/1861941 Title: bcache by-uuid links disappear after mounting bcache0 Status in bcache-tools package in Ubuntu: In Progress Status in systemd package in Ubuntu: In Progress Status in bcache-tools source package in Bionic: In Progress Status in systemd source package in Bionic: In Progress Status in bcache-tools source package in Focal: In Progress Status in systemd source package in Focal: In Progress Bug description: 1. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 2. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 5.4.0.12.15 Candidate: 5.4.0.12.15 Version table: *** 5.4.0.12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic linux-image-5.4.0-12-generic: Installed: 5.4.0-12.15 Candidate: 5.4.0-12.15 Version table: *** 5.4.0-12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/ + ls -al /dev/bcache/by-uuid/ total 0 drwxr-xr-x 2 root root 60 Feb 4 23:31 . drwxr-xr-x 3 root root 60 Feb 4 23:31 .. lrwxrwxrwx 1 root root 13 Feb 4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a -> ../../bcache0 4. root@ubuntu:~# ls -al /dev/bcache/by-uuid ls: cannot access '/dev/bcache/by-uuid': No such file or directory ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Tue Feb 4 23:31:52 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+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 1861941] Re: bcache by-uuid links disappear after mounting bcache0
I'm setting this bug to In Progress so I can better track reverted fix and the new one in both packages for all Ubuntu versions. -- 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/1861941 Title: bcache by-uuid links disappear after mounting bcache0 Status in bcache-tools package in Ubuntu: In Progress Status in systemd package in Ubuntu: In Progress Status in bcache-tools source package in Bionic: In Progress Status in systemd source package in Bionic: In Progress Status in bcache-tools source package in Focal: In Progress Status in systemd source package in Focal: In Progress Bug description: 1. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 2. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 5.4.0.12.15 Candidate: 5.4.0.12.15 Version table: *** 5.4.0.12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic linux-image-5.4.0-12-generic: Installed: 5.4.0-12.15 Candidate: 5.4.0-12.15 Version table: *** 5.4.0-12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/ + ls -al /dev/bcache/by-uuid/ total 0 drwxr-xr-x 2 root root 60 Feb 4 23:31 . drwxr-xr-x 3 root root 60 Feb 4 23:31 .. lrwxrwxrwx 1 root root 13 Feb 4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a -> ../../bcache0 4. root@ubuntu:~# ls -al /dev/bcache/by-uuid ls: cannot access '/dev/bcache/by-uuid': No such file or directory ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Tue Feb 4 23:31:52 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+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 1861941] Re: bcache by-uuid links disappear after mounting bcache0
Upstream patch submitted (amended from Ryan's previous patch) with a minor PATH fix: - https://github.com/koverstreet/bcache-tools/pull/6/ -- 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/1861941 Title: bcache by-uuid links disappear after mounting bcache0 Status in bcache-tools package in Ubuntu: In Progress Status in systemd package in Ubuntu: In Progress Status in bcache-tools source package in Bionic: In Progress Status in systemd source package in Bionic: In Progress Status in bcache-tools source package in Focal: In Progress Status in systemd source package in Focal: In Progress Bug description: 1. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 2. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 5.4.0.12.15 Candidate: 5.4.0.12.15 Version table: *** 5.4.0.12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic linux-image-5.4.0-12-generic: Installed: 5.4.0-12.15 Candidate: 5.4.0-12.15 Version table: *** 5.4.0-12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/ + ls -al /dev/bcache/by-uuid/ total 0 drwxr-xr-x 2 root root 60 Feb 4 23:31 . drwxr-xr-x 3 root root 60 Feb 4 23:31 .. lrwxrwxrwx 1 root root 13 Feb 4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a -> ../../bcache0 4. root@ubuntu:~# ls -al /dev/bcache/by-uuid ls: cannot access '/dev/bcache/by-uuid': No such file or directory ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Tue Feb 4 23:31:52 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+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 1869117] Re: python-pip install fails in Ubuntu 20.04 unmet dependencies (Focal)
** No longer affects: python2.7 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1869117 Title: python-pip install fails in Ubuntu 20.04 unmet dependencies (Focal) Status in python-pip package in Ubuntu: Won't Fix Bug description: apt-get install python-pip fails in Ubuntu 20.04: The following packages have unmet dependencies: python-pip : Depends: python-pip-whl (= 18.1-5ubuntu1) but 20.0.2-2 is to be installed Recommends: python-all-dev (>= 2.6) but it is not going to be installed Recommends: python-wheel but it is not going to be installed E: Unable to correct problems, you have held broken packages. The python-pip package needs to be updated to accept newer versions of python-pip-whl. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1869117/+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 583994] Re: Consider replacing ntpdate calls by 'ntpd -g'
** Changed in: ntp (Debian) Importance: Unknown => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/583994 Title: Consider replacing ntpdate calls by 'ntpd -g' Status in NTP: Invalid Status in ntp package in Ubuntu: Invalid Status in ubuntu-meta package in Ubuntu: Fix Released Status in ntp package in Debian: New Bug description: Binary package hint: ntp Given that 'ntpdate' is being obsoleted upstream [1], we should replace 'ntpdate' usage by: * ntpd -qg (if we really want to set the time and exit), or * ntpd-g (if we want to keep ntpd running) the '-q' option will set the clock once, and exit; the 'g' allows for large corrections to the clock, like what is done by 'ntpdate'. [1] http://www.eecis.udel.edu/~mills/ntp/html/ntpdate.html To manage notifications about this bug go to: https://bugs.launchpad.net/ntp/+bug/583994/+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 1222602] Re: [regression] [gen3] Mesa 9.2 makes Unity unusable on Atom class hardware and 943/945 graphics controllers
** Changed in: mesa Importance: Unknown => Undecided ** Changed in: mesa Remote watch: gitlab.freedesktop.org/mesa/mesa/issues #727 => None ** Changed in: mesa Status: New => Won't Fix -- 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/1222602 Title: [regression] [gen3] Mesa 9.2 makes Unity unusable on Atom class hardware and 943/945 graphics controllers Status in Mesa: Won't Fix Status in Nux: Fix Released Status in Release Notes for Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in nux package in Ubuntu: Fix Released Status in unity package in Ubuntu: Invalid Bug description: After the upgrade to Mesa 9.2.0 unity is barely usable. Dash, Alt+Tab switcher and Alt+F2 command line shows in more than 1 minute, using 100% cpu. A downgrade to mesa 9.1.6-2ubuntu2 restores full performance. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libgl1-mesa-glx 9.2-1ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-5.11-generic 3.11.0 Uname: Linux 3.11.0-5-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.12.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Sep 9 01:51:45 2013 DistUpgraded: 2013-09-08 20:36:47,811 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 945GSE Express Integrated Graphics Controller [8086:27ae] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. Device [1462:0110] Subsystem: Micro-Star International Co., Ltd. Device [1462:0110] InstallationDate: Installed on 2013-09-07 (1 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) MachineType: MICRO-STAR INTERNATIONAL CO., LTD U90/U100 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-5-generic root=UUID=674329c8-d0a6-4954-89c0-72821cfa0ba8 ro quiet splash vt.handoff=7 SourcePackage: mesa UpgradeStatus: Upgraded to saucy on 2013-09-08 (0 days ago) dmi.bios.date: 12/01/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: U90/U100 dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.board.version: Ver.001 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.chassis.version: Ver.001 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.3:bd12/01/2009:svnMICRO-STARINTERNATIONALCO.,LTD:pnU90/U100:pvrVer.001:rvnMICRO-STARINTERNATIONALCO.,LTD:rnU90/U100:rvrVer.001:cvnMICRO-STARINTERNATIONALCO.,LTD:ct10:cvrVer.001: dmi.product.name: U90/U100 dmi.product.version: Ver.001 dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD version.compiz: compiz 1:0.9.10+13.10.20130828.2-0ubuntu1 version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu6 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Mon Sep 9 01:46:55 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1001 vendor HSD xserver.version: 2:1.14.2.901-2ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1222602/+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 1879206] Re: cups hplip not install printer
It might be that the same bug affected me after upgrading to 20.04 with another printer: https://answers.launchpad.net/hplip/+question/690767 I also recently tried hplip 3.20.6 for a freshly installed xubuntu, but it did not help. (the result of hp-check brought the same result as https://answers.launchpad.net/hplip/+question/690767 (#5). I was forced to downgrade the system again because it is essential to keep the printer functional. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1879206 Title: cups hplip not install printer Status in cups package in Ubuntu: Incomplete Status in hplip package in Ubuntu: Incomplete Bug description: After upgrading to Ubuntu 20.04 I can't print anymore. Description: Ubuntu 20.04 LTS Release: 20.04 cups: Installato: 2.3.1-9ubuntu1.1 Candidato: 2.3.1-9ubuntu1.1 Tabella versione: *** 2.3.1-9ubuntu1.1 500 500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 2.3.1-9ubuntu1 500 500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages hplip: Installato: 3.20.3+dfsg0-2 Candidato: 3.20.3+dfsg0-2 Tabella versione: *** 3.20.3+dfsg0-2 500 500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status I tried to reinstall the printer, but it is not being re-saved by cups / hplip ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 18 02:24:07 2020 InstallationDate: Installed on 2020-05-17 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lpstat: device for DeskJet_3630: hp:/usb/DeskJet_3630_series?serial=CN8AM7H3230658 MachineType: LENOVO 80G0 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/DeskJet_3630.ppd'] failed with exit code 2: grep: /etc/cups/ppd/DeskJet_3630.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=6a8469e0-ecea-4a86-8040-b0caaa938fe4 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2014 dmi.bios.vendor: LENOVO dmi.bios.version: A7CN40WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lancer 5A6 dmi.board.vendor: LENOVO dmi.board.version: SDK0F82993WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-30 dmi.modalias: dmi:bvnLENOVO:bvrA7CN40WW:bd07/18/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrSDK0F82993WIN:cvnLENOVO:ct10:cvrLenovoG50-30: dmi.product.family: IDEAPAD dmi.product.name: 80G0 dmi.product.sku: LENOVO_MT_80G0_BU_idea_FM_Lenovo G50-30 dmi.product.version: Lenovo G50-30 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1879206/+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 1888575] [NEW] Split motd-news config into a new package
Public bug reported: The motd-news script is largely useless for desktop users, as they rarely login via a text console. It makes more sense for server users. We can use package dependencies to have the motd-news script enabled on servers, but disabled on desktops, and still handle upgrades. This is the plan: - move /etc/default/motd-news from base-files into a NEW package (motd-news-config) - have ubuntu-server depend on motd-news-config (or recommends) - have base-files break current ubuntu-server, so that if base-files if upgraded and ubuntu-server is installed, ubuntu-server will also be upgraded to the new version which has the depends (or recommends) on motd-news-config Care must be taken to preserve a changed /etc/default/motd-news when the upgrade installs the new motd-news-config package. For example, on a server that has set ENABLED=0 in /etc/default/motd-news and upgrades to the new base-files and ubuntu-server, and gets the new motd-config-news package, ENABLED=0 must remain set. ** Affects: base-files (Ubuntu) Importance: Undecided Assignee: Andreas Hasenack (ahasenack) Status: In Progress ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Assignee: Andreas Hasenack (ahasenack) Status: In Progress ** Affects: base-files (Ubuntu Xenial) Importance: Undecided Assignee: Andreas Hasenack (ahasenack) Status: In Progress ** Affects: ubuntu-meta (Ubuntu Xenial) Importance: Undecided Assignee: Andreas Hasenack (ahasenack) Status: In Progress ** Affects: base-files (Ubuntu Bionic) Importance: Undecided Assignee: Andreas Hasenack (ahasenack) Status: In Progress ** Affects: ubuntu-meta (Ubuntu Bionic) Importance: Undecided Assignee: Andreas Hasenack (ahasenack) Status: In Progress ** Affects: base-files (Ubuntu Focal) Importance: Undecided Assignee: Andreas Hasenack (ahasenack) Status: In Progress ** Affects: ubuntu-meta (Ubuntu Focal) Importance: Undecided Assignee: Andreas Hasenack (ahasenack) Status: In Progress ** Affects: base-files (Ubuntu Groovy) Importance: Undecided Assignee: Andreas Hasenack (ahasenack) Status: In Progress ** Affects: ubuntu-meta (Ubuntu Groovy) Importance: Undecided Assignee: Andreas Hasenack (ahasenack) Status: In Progress ** Also affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Also affects: base-files (Ubuntu Groovy) Importance: Undecided Assignee: Andreas Hasenack (ahasenack) Status: In Progress ** Also affects: ubuntu-meta (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: base-files (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: ubuntu-meta (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: base-files (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: ubuntu-meta (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: base-files (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: ubuntu-meta (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: base-files (Ubuntu Xenial) Assignee: (unassigned) => Andreas Hasenack (ahasenack) ** Changed in: base-files (Ubuntu Bionic) Assignee: (unassigned) => Andreas Hasenack (ahasenack) ** Changed in: base-files (Ubuntu Focal) Assignee: (unassigned) => Andreas Hasenack (ahasenack) ** Changed in: ubuntu-meta (Ubuntu Xenial) Assignee: (unassigned) => Andreas Hasenack (ahasenack) ** Changed in: ubuntu-meta (Ubuntu Bionic) Assignee: (unassigned) => Andreas Hasenack (ahasenack) ** Changed in: ubuntu-meta (Ubuntu Focal) Assignee: (unassigned) => Andreas Hasenack (ahasenack) ** Changed in: ubuntu-meta (Ubuntu Groovy) Assignee: (unassigned) => Andreas Hasenack (ahasenack) ** Changed in: base-files (Ubuntu Xenial) Status: New => In Progress ** Changed in: base-files (Ubuntu Bionic) Status: New => In Progress ** Changed in: base-files (Ubuntu Focal) Status: New => In Progress ** Changed in: ubuntu-meta (Ubuntu Xenial) Status: New => In Progress ** Changed in: ubuntu-meta (Ubuntu Bionic) Status: New => In Progress ** Changed in: ubuntu-meta (Ubuntu Focal) Status: New => In Progress ** Changed in: ubuntu-meta (Ubuntu Groovy) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1888575 Title: Split motd-news config into a new package Status in base-files package in Ubuntu: In Progress Status in ubuntu-meta package in Ubuntu: In Progress Status in base-files source package in Xenial: In Progress Status in ubuntu-meta source package in Xenial: In Progress Status in
[Touch-packages] [Bug 1888572] Re: motd-news: use wget instead of curl
This was fixed for groovy in https://launchpad.net/ubuntu/+source/base- files/11ubuntu9 ** Changed in: base-files (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1888572 Title: motd-news: use wget instead of curl Status in base-files package in Ubuntu: Fix Released Status in base-files source package in Xenial: In Progress Status in base-files source package in Bionic: In Progress Status in base-files source package in Focal: In Progress Bug description: The motd-news script is using curl, but since that is an optional package, there is no guarantee that it will be installed. The script correctly checks for its presence before trying to use it, though, so it won't fail. As we don't want to add such a dependency to the base- files package, we should switch to wget, which is standard. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1888572/+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 1888572] [NEW] motd-news: use wget instead of curl
Public bug reported: The motd-news script is using curl, but since that is an optional package, there is no guarantee that it will be installed. The script correctly checks for its presence before trying to use it, though, so it won't fail. As we don't want to add such a dependency to the base-files package, we should switch to wget, which is standard. ** Affects: base-files (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: base-files (Ubuntu Xenial) Importance: Undecided Assignee: Andreas Hasenack (ahasenack) Status: In Progress ** Affects: base-files (Ubuntu Bionic) Importance: Undecided Assignee: Andreas Hasenack (ahasenack) Status: In Progress ** Affects: base-files (Ubuntu Focal) Importance: Undecided Assignee: Andreas Hasenack (ahasenack) Status: In Progress ** Also affects: base-files (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: base-files (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: base-files (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: base-files (Ubuntu Xenial) Status: New => In Progress ** Changed in: base-files (Ubuntu Bionic) Status: New => In Progress ** Changed in: base-files (Ubuntu Focal) Status: New => In Progress ** Changed in: base-files (Ubuntu Xenial) Assignee: (unassigned) => Andreas Hasenack (ahasenack) ** Changed in: base-files (Ubuntu Bionic) Assignee: (unassigned) => Andreas Hasenack (ahasenack) ** Changed in: base-files (Ubuntu Focal) Assignee: (unassigned) => Andreas Hasenack (ahasenack) ** Changed in: base-files (Ubuntu) Assignee: Andreas Hasenack (ahasenack) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1888572 Title: motd-news: use wget instead of curl Status in base-files package in Ubuntu: Fix Released Status in base-files source package in Xenial: In Progress Status in base-files source package in Bionic: In Progress Status in base-files source package in Focal: In Progress Bug description: The motd-news script is using curl, but since that is an optional package, there is no guarantee that it will be installed. The script correctly checks for its presence before trying to use it, though, so it won't fail. As we don't want to add such a dependency to the base- files package, we should switch to wget, which is standard. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1888572/+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 1888571] [NEW] Screen flickering and glitching after install
Public bug reported: Intel integrated driver causes screen flickering with Ubuntu install. Windows did not have this issue ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 22 15:41:42 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Iris Plus Graphics G7 [103c:875a] InstallationDate: Installed on 2020-07-22 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: HP HP ENVY Laptop 13-ba0xxx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=9f807172-2b35-4ad1-9f33-5a912ad7c579 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/04/2020 dmi.bios.vendor: Insyde dmi.bios.version: F.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 875A dmi.board.vendor: HP dmi.board.version: 07.34 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.10:bd06/04/2020:svnHP:pnHPENVYLaptop13-ba0xxx:pvrType1ProductConfigId:rvnHP:rn875A:rvr07.34:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY Laptop 13-ba0xxx dmi.product.sku: 8KD13AV dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 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 -- 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/1888571 Title: Screen flickering and glitching after install Status in xorg package in Ubuntu: New Bug description: Intel integrated driver causes screen flickering with Ubuntu install. Windows did not have this issue ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 22 15:41:42 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Iris Plus Graphics G7 [103c:875a] InstallationDate: Installed on 2020-07-22 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: HP HP ENVY Laptop 13-ba0xxx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=9f807172-2b35-4ad1-9f33-5a912ad7c579 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/04/2020 dmi.bios.vendor: Insyde dmi.bios.version: F.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 875A dmi.board.vendor: HP dmi.board.version: 07.34 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.10:bd06/04/2020:svnHP:pnHPENVYLaptop13-ba0xxx:pvrType1ProductConfigId:rvnHP:rn875A:rvr07.34:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY Laptop 13-ba0xxx dmi.product.sku: 8KD13AV dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2
[Touch-packages] [Bug 1405452] Re: Typo in man page ("introduce a much improvement mechanism")
Looks like a patch was created some time ago. What steps are required in
order to close out this bug?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1405452
Title:
Typo in man page ("introduce a much improvement mechanism")
Status in One Hundred Papercuts:
Triaged
Status in wpa package in Ubuntu:
Triaged
Status in wpa package in Debian:
New
Bug description:
"introduce a much improvement mechanism" should be "introduce a much
improved mechanism".
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: wpasupplicant 2.1-0ubuntu4
ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
Uname: Linux 3.16.0-28-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Dec 24 16:19:30 2014
InstallationDate: Installed on 2014-12-19 (4 days ago)
InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64
(20141022.1)
SourcePackage: wpa
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1405452/+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 1880541] Re: package udev 245.4-4ubuntu3 failed to install/upgrade: podproces zainstalowany pakiet udev skrypt post-installation returned error code 1
ubuntu@lp1880541-f:~$ dpkg -l udev|grep udev ii udev 245.4-4ubuntu3 amd64/dev/ and hotplug management daemon ubuntu@lp1880541-f:~$ sudo groupadd kvm groupadd: group 'kvm' already exists ubuntu@lp1880541-f:~$ grep kvm /etc/group kvm:x:108: ubuntu@lp1880541-f:~$ sudo groupdel kvm ubuntu@lp1880541-f:~$ grep kvm /etc/group ubuntu@lp1880541-f:~$ sudo groupadd kvm ubuntu@lp1880541-f:~$ grep kvm /etc/group kvm:x:1001: ubuntu@lp1880541-f:~$ sudo apt install udev Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libudev1 The following packages will be upgraded: libudev1 udev 2 upgraded, 0 newly installed, 0 to remove and 31 not upgraded. Need to get 1440 kB of archives. After this operation, 2048 B of additional disk space will be used. Do you want to continue? [Y/n] y Get:1 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 udev amd64 245.4-4ubuntu3.1 [1362 kB] Get:2 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 libudev1 amd64 245.4-4ubuntu3.1 [78.3 kB] Fetched 1440 kB in 1s (1423 kB/s) (Reading database ... 66302 files and directories currently installed.) Preparing to unpack .../udev_245.4-4ubuntu3.1_amd64.deb ... Unpacking udev (245.4-4ubuntu3.1) over (245.4-4ubuntu3) ... Preparing to unpack .../libudev1_245.4-4ubuntu3.1_amd64.deb ... Unpacking libudev1:amd64 (245.4-4ubuntu3.1) over (245.4-4ubuntu3) ... Setting up libudev1:amd64 (245.4-4ubuntu3.1) ... Setting up udev (245.4-4ubuntu3.1) ... The group `kvm' already exists and is not a system group. Exiting. dpkg: error processing package udev (--configure): installed udev package post-installation script subprocess returned error exit status 1 Processing triggers for systemd (245.4-4ubuntu3.1) ... Processing triggers for man-db (2.9.1-1) ... Processing triggers for libc-bin (2.31-0ubuntu9) ... Errors were encountered while processing: udev E: Sub-process /usr/bin/dpkg returned an error code (1) (clear the error and downgrade udev again, and add -proposed to apt sources) ubuntu@lp1880541-f:~$ dpkg -l udev|grep udev ii udev 245.4-4ubuntu3 amd64/dev/ and hotplug management daemon ubuntu@lp1880541-f:~$ sudo groupadd kvm groupadd: group 'kvm' already exists ubuntu@lp1880541-f:~$ dpkg -l udev|grep udev ii udev 245.4-4ubuntu3 amd64/dev/ and hotplug management daemon ubuntu@lp1880541-f:~$ grep kvm /etc/group kvm:x:108: ubuntu@lp1880541-f:~$ sudo groupdel kvm ubuntu@lp1880541-f:~$ grep kvm /etc/group ubuntu@lp1880541-f:~$ sudo groupadd kvm ubuntu@lp1880541-f:~$ grep kvm /etc/group kvm:x:1001: ubuntu@lp1880541-f:~$ sudo apt install udev Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libudev1 The following packages will be upgraded: libudev1 udev 2 upgraded, 0 newly installed, 0 to remove and 46 not upgraded. Need to get 1442 kB of archives. After this operation, 4096 B of additional disk space will be used. Do you want to continue? [Y/n] y Get:1 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 udev amd64 245.4-4ubuntu3.2 [1363 kB] Get:2 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 libudev1 amd64 245.4-4ubuntu3.2 [78.9 kB] Fetched 1442 kB in 1s (1415 kB/s) (Reading database ... 66302 files and directories currently installed.) Preparing to unpack .../udev_245.4-4ubuntu3.2_amd64.deb ... Unpacking udev (245.4-4ubuntu3.2) over (245.4-4ubuntu3) ... Preparing to unpack .../libudev1_245.4-4ubuntu3.2_amd64.deb ... Unpacking libudev1:amd64 (245.4-4ubuntu3.2) over (245.4-4ubuntu3) ... Setting up libudev1:amd64 (245.4-4ubuntu3.2) ... Setting up udev (245.4-4ubuntu3.2) ... The group `kvm' already exists and is not a system group. Exiting. update-initramfs: deferring update (trigger activated) Processing triggers for systemd (245.4-4ubuntu3.1) ... Processing triggers for man-db (2.9.1-1) ... Processing triggers for libc-bin (2.31-0ubuntu9) ... Processing triggers for initramfs-tools (0.136ubuntu6.2) ... update-initramfs: Generating /boot/initrd.img-5.4.0-40-generic ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- 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/1880541 Title: package udev 245.4-4ubuntu3 failed to install/upgrade: podproces zainstalowany pakiet udev skrypt post-installation returned error code 1 Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Committed Bug description: [impact] during upgrade, udev may fail to configure, interrupting the upgrade [test case] on 18.04, create a non-system group 'kvm', then upgrade to 20.04 [regression potential] any regression would likely
[Touch-packages] [Bug 1876018] Re: 40-vm-hotadd.rules attempts to set non-existent sysfs parameters
focal:
with the reproducer hack from the description (comment out the 'goto'
line in the udev rule), and the system rebooted:
ubuntu@lp1876018-f:~$ dpkg -l systemd|grep systemd
ii systemd245.4-4ubuntu3.1 amd64system and service manager
ubuntu@lp1876018-f:~$ journalctl -g vm-hotadd
-- Logs begin at Wed 2020-07-22 18:11:53 UTC, end at Wed 2020-07-22 18:46:23
UTC. --
Jul 22 18:45:15 lp1876018-f sudo[12380]: ubuntu : TTY=ttyS0 ;
PWD=/home/ubuntu ; USER=root ; COMMAND=/usr/bin/vi
/lib/udev/rules.d/40-vm-hotadd.rules
-- Reboot --
Jul 22 18:45:48 lp1876018-f systemd-udevd[457]: memory0:
/usr/lib/udev/rules.d/40-vm-hotadd.rules:9 Failed to write
ATTR{/sys/devices/system/memory/memory0/state}, ignoring: Invalid argument
Jul 22 18:45:48 lp1876018-f systemd-udevd[457]: memory1:
/usr/lib/udev/rules.d/40-vm-hotadd.rules:9 Failed to write
ATTR{/sys/devices/system/memory/memory1/state}, ignoring: Invalid argument
Jul 22 18:45:48 lp1876018-f systemd-udevd[457]: memory10:
/usr/lib/udev/rules.d/40-vm-hotadd.rules:9 Failed to write
ATTR{/sys/devices/system/memory/memory10/state}, ignoring: Invalid argument
...(many more)...
and with the udev rule again edited after the systemd upgrade (since it
replaces the edited file), and the system rebooted:
ubuntu@lp1876018-f:~$ dpkg -l systemd|grep systemd
ii systemd245.4-4ubuntu3.2 amd64system and service manager
ubuntu@lp1876018-f:~$ journalctl -b -g vm-hotadd
-- Logs begin at Wed 2020-07-22 18:11:53 UTC, end at Wed 2020-07-22 18:50:00 UT>
-- No entries --
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
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/1876018
Title:
40-vm-hotadd.rules attempts to set non-existent sysfs parameters
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Xenial:
In Progress
Status in systemd source package in Bionic:
In Progress
Status in systemd source package in Focal:
Fix Committed
Bug description:
[impact]
40-vm-hotadd.rules unconditionally tries onlining memory, which
results in logged error messages if the memory is already online
[test case]
since this rules file restricts operation to only hyper-v or xen
guests, boot a hyper-v or xen vm guest, and check for logged error
msgs like:
Apr 29 22:36:46 focal01 systemd-udevd[266]: memory7:
/usr/lib/udev/rules.d/40-vm-hotadd.rules:9 Failed to write
ATTR{/sys/devices/system/memory/memory7/state}, ignoring: Invalid
argument
alternately, to test on a vm guest other than hyper-v or xen,
comment/remove the 'GOTO="vm_hotadd_end"' line from the rules file and
reboot.
[regression potential]
as this adds a check before attempting to online memory for hyper-v
and xen vm guests, any regression would likely involve failure to
correctly online all memory on those guest platforms.
[scope]
this rule has been around for a long time, so is needed for x/b/f/g.
[original description]
In focal, udev's 40-vm-hotadd.rules (from debian/extra/rules-ubuntu)
tries to write to invalid (as of 5.4.0-1010-azure) sysfs nodes
resulting in warnings such as:
Apr 29 22:36:46 focal01 systemd-udevd[266]: memory7:
/usr/lib/udev/rules.d/40-vm-hotadd.rules:9 Failed to write
ATTR{/sys/devices/system/memory/memory7/state}, ignoring: Invalid
argument
Perhaps 40-vm-hotadd.rules needs to be updated for 5.4 semantics,
removed, or something else. This behavior is present on systems
upgraded from 18.04 (via d-r-u) as well as new focal systems, upon
first reboot of the VM.
udev: 245.4-4ubuntu3
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1876018/+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 1838329] Re: Cryptswap periodically fails to mount at boot due to missing a udev notification
I wasn't able to reproduce this myself, due to the failure being dependent on timing, but I set up the reproducer from the upstream bug and rebooted several times with the proposed package, and had no problems/regressions. Marking this verified. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- 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/1838329 Title: Cryptswap periodically fails to mount at boot due to missing a udev notification Status in systemd: New Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: New Status in systemd source package in Focal: Fix Committed Status in systemd source package in Groovy: Fix Released Bug description: [impact] systems using cryptsetup-based encrypted swap may hang during boot due to udevd missing the notification that swap has been setup on the newly created swap device. [test case] see original description, and reproduction is intermittent based on timing [regression potential] any regression would likely occur during, or after, boot when creating an encrypted swap device and/or while waiting to activate the new swap device. Regressions may cause failure to correctly enable swap and/or hung boot waiting for the swap device. [scope] this was (potentially) fixed upstream with PR 15836, which is not yet included in any upstream release, so this is needed in all releases, including groovy. also note while the upstream bug is closed, and code review seems to indicate this *should* fix this specific issue, there are some comments in the upstream bug indicating it may not completely solve the problem, although there is no further debug of the new reports. [original description] On some systems, cryptsetup-based encrypted swap partitions cause systemd to get stuck at boot. This is a timing-sensitive Heisenbug, so the rate of occurrence varies from one system to another. Some hardware will not experience the issue at all, others will only occasionally experience the issue, and then there are the unlucky who are unable to boot at all, no matter how many times they restart. The workaround is for the cryptsetup-generator to generate cryptswap service entries that call `udevadm trigger` after `mkswap`. This will ensure that the udev event is triggered, so that systemd is notified that the encrypt swap partition is ready to activate. This patch has already been submitted upstream to systemd, but it was not accepted because it is a workaround for the side effect of systemd not seeing the udev event upon creating the swap partition. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1838329/+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 1888543] [NEW] hwclock: fails to set time on glibc 2.31
Public bug reported: With glibc 2.31, hwclock from busybox is unable to set the system time due to the changes in settimeofday behavior. The problem has been reported upstream in [1] which also contains a patch. hwclock from busybox is important as it's used on the Raspberry Pi to set the system time when an RTC is present. This bug applies to focal and groovy. [1] https://bugs.busybox.net/show_bug.cgi?id=12756 ** Affects: busybox (Ubuntu) Importance: Undecided Status: New ** Affects: busybox (Debian) Importance: Unknown Status: Unknown ** Bug watch added: Debian Bug tracker #966074 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966074 ** Also affects: busybox (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966074 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/1888543 Title: hwclock: fails to set time on glibc 2.31 Status in busybox package in Ubuntu: New Status in busybox package in Debian: Unknown Bug description: With glibc 2.31, hwclock from busybox is unable to set the system time due to the changes in settimeofday behavior. The problem has been reported upstream in [1] which also contains a patch. hwclock from busybox is important as it's used on the Raspberry Pi to set the system time when an RTC is present. This bug applies to focal and groovy. [1] https://bugs.busybox.net/show_bug.cgi?id=12756 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1888543/+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 1886161] Re: UU should work on roaming laptops
This is not going to happen in apt. It's a question for desktop how to do that, probably disabling the downloading in apt, and using gnome's package kit refresh stuff instead. ** Also affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1886161 Title: UU should work on roaming laptops Status in apt package in Ubuntu: New Status in gnome-settings-daemon package in Ubuntu: New Bug description: For many if not most laptop computers, Unattended Upgrades seems all but useless by design. For upgrades to happen, with default config, 3 conditions must be met: - an internet connection must be up and running when the timer or cron or anacron tries the unattended upgrade - the connection must not be metered, whatever that means (Skip-Updates-On-Metered-Connections "true") - the computer must be plugged in (OnlyOnACPower "true") These are insurmountable problems for many laptops on the go. Inevitably, security upgrades will almost never run unattended on such computers. I discovered with shock that Unattended Upgrades had almost never run on my laptop. I tried all possible config tweaks. Nothing worked reliably and in the end I gave up and wrote a upgrade script which uses Network Manager's connection-up hook. Unattended Upgrades needs to do something like this out of the box. Users should not need to write scripts to ensure security upgrades. Unattended upgrades is an excellent project for servers. But it really needs to work, out of the box, on laptops too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1886161/+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 1877769] Re: [SRU] Rewinding cache triggers obsolete adjustments consuming a lot of CPU
Hello Balint, or anyone else affected, Accepted unattended-upgrades into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/unattended- upgrades/2.3ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: unattended-upgrades (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1877769 Title: [SRU] Rewinding cache triggers obsolete adjustments consuming a lot of CPU Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Focal: Fix Committed Status in unattended-upgrades package in Debian: Fix Released Bug description: [Impact] * Unattended-upgrades consumes excessive amount of CPU when rewinding cache trying to mark packages to upgrade or install even when they are already marked to be upgraded or installed. This can be triggered by packages held back. [Test Case] * Run test_rewind.py: -Fixed output: $ python3 test_rewind.py INFO:root:Allowed origins are: o=Ubuntu,a=lucid-security INFO:root:Initial blacklist: ant-doc INFO:root:Initial whitelist (not strict): DEBUG:root:Marking not allowed with -32768 pin DEBUG:root:Applying pinning: PkgFilePin(id=0, priority=-32768) DEBUG:root:Applying pin -32768 to package_file: DEBUG:root:Applying pinning: PkgPin(pkg='/^ant-doc/', priority=-32768) DEBUG:root:APT::VersionedKernelPackages is not set DEBUG:root:adjusting candidate version: test-package=2.0 DEBUG:root:adjusting candidate version: test2-package=2.0 DEBUG:root:falling back to adjusting test2-package's dependencies DEBUG:root:falling back to adjusting z-package's dependencies DEBUG:root:sanity check failed for: set() : no package is selected to be upgraded or installed . -- Ran 1 test in 0.022s OK - Not fixed output: $ python3 test_rewind.py INFO:root:Allowed origins are: o=Ubuntu,a=lucid-security INFO:root:Initial blacklist: ant-doc INFO:root:Initial whitelist (not strict): DEBUG:root:Marking not allowed with -32768 pin DEBUG:root:Applying pinning: PkgFilePin(id=0, priority=-32768) DEBUG:root:Applying pin -32768 to package_file: DEBUG:root:Applying pinning: PkgPin(pkg='/^ant-doc/', priority=-32768) DEBUG:root:APT::VersionedKernelPackages is not set DEBUG:root:adjusting candidate version: test-package=2.0 DEBUG:root:adjusting candidate version: test2-package=2.0 DEBUG:root:falling back to adjusting test2-package's dependencies DEBUG:root:falling back to adjusting z-package's dependencies DEBUG:root:sanity check failed for: set() : no package is selected to be upgraded or installed DEBUG:root:falling back to adjusting test-package's dependencies DEBUG:root:falling back to adjusting test2-package's dependencies DEBUG:root:falling back to adjusting test3-package's dependencies DEBUG:root:falling back to adjusting test-package's dependencies DEBUG:root:falling back to adjusting test2-package's dependencies DEBUG:root:falling back to adjusting test3-package's dependencies . -- Ran 1 test in 0.024s (Note the extra "DEBUG:root:falling back to adjusting" ... lines) [Regression Potential] * Minimal. The very small change fixes how call_checked() verifies that the package to be upgrades/installed is indeed marked to either being installed or upgraded. In the worst case, if call_checked() erroneously returns success for a package as a result of a regression, unattended-upgrades does not fall back to adjusting packages to make marking successful. Later unattended-upgrades
[Touch-packages] [Bug 1883082] Re: Crash when using Package-Whitelist-Strict
Hello Jose, or anyone else affected,
Accepted unattended-upgrades into focal-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/unattended-
upgrades/2.3ubuntu0.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: unattended-upgrades (Ubuntu Focal)
Status: New => Fix Committed
** Tags added: verification-needed verification-needed-focal
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1883082
Title:
Crash when using Package-Whitelist-Strict
Status in unattended-upgrades package in Ubuntu:
Fix Released
Status in unattended-upgrades source package in Focal:
Fix Committed
Bug description:
[Impact]
* Unattended-upgrades crashes when strict whitelist is enabled and
there is an update available.
[Test Case]
Set up a system with at least one updated package available:
$ lxc launch ubuntu:focal ff-uu-strict
Creating ff-uu-strict
Starting ff-uu-strict
$ lxc shell ff-uu-strict
root@ff-uu-strict:~# apt update
...
root@ff-uu-strict:~# apt list --upgradable
Listing... Done
open-vm-tools/focal-updates 2:11.1.0-2~ubuntu20.04.1 amd64 [upgradable
from: 2:11.0.5-4]
N: There is 1 additional version. Please use the '-a' switch to see it
Set up strict whitelist not covering the package:
root@ff-uu-strict:~# echo 'Unattended-Upgrade::Package-Whitelist-Strict
"true";' > /etc/apt/apt.conf.d/51unattended-upgrades-whitelist
root@ff-uu-strict:~# echo 'Unattended-Upgrade::Package-Whitelist {"foo";}'
>> /etc/apt/apt.conf.d/51unattended-upgrades-whitelist
Run unattended-upgrades:
root@ff-uu-strict:~# unattended-upgrade
The fixed version does not crash here, the not fixed one does.
[Regression Potential]
Minimal. The fix adds only one extra check to not crash dereferencing
None.
[Original Bug Text]
Hi,
I'm trying to use unattended-upgrades only with a few packages from a
list; to do that I tried this simple /etc/apt/apt.conf.d/51local-ua
file:
root@focal-ua:~# cat /etc/apt/apt.conf.d/51local-ua
Unattended-Upgrade::Package-Whitelist-Strict "true";
Unattended-Upgrade::Package-Whitelist {
"firefox";
"bash";
"openssh-server";
}
When running unattended-upgrades in dry run mode I get this crash:
root@focal-ua:~# unattended-upgrade --debug --dry-run
Running on the development release
Starting unattended upgrades script
Allowed origins are: o=Ubuntu,a=focal, o=Ubuntu,a=focal-security,
o=UbuntuESMApps,a=focal-apps-security, o=UbuntuESM,a=focal-infra-security,
o=UbuntuESM,a=focal-security
Initial blacklist:
Initial whitelist (strict): firefox bash openssh-server
Marking not allowed
with -32768 pin
Marking not allowed
with -32768 pin
Marking not allowed
with -32768 pin
Marking not allowed
with -32768 pin
Marking not allowed with -32768 pin
Marking not allowed
with -32768 pin
Marking not allowed with -32768 pin
Marking not allowed
with -32768 pin
Marking not allowed with -32768 pin
Marking not allowed
with -32768 pin
An error occurred: '>' not supported between instances of 'apt_pkg.Version'
and 'int'
Traceback (most recent call last):
File "/usr/bin/unattended-upgrade", line 1983, in main
res = run(options, rootdir, mem_log, logfile_dpkg,
File "/usr/bin/unattended-upgrade", line 2124, in run
cache = UnattendedUpgradesCache(rootdir=rootdir)
File "/usr/bin/unattended-upgrade", line 171, in __init__
apt.Cache.__init__(self, rootdir=rootdir)
File "/usr/lib/python3/dist-packages/apt/cache.py", line 170, in __init__
self.open(progress)
File "/usr/bin/unattended-upgrade", line 330, in open
self.apply_pinning(self.pinning_from_config())
File "/usr/bin/unattended-upgrade", line 302, in
[Touch-packages] [Bug 1885730] Re: Bring back ondemand.service or switch kernel default governor for pstate - pstate now defaults to performance governor
passing intel_pstate=disable_hwp on the kernel commandline causes the kernel to scale the Core i5-8250U down to 1.6 GHz in performance mode, but that's still a bit off from the 900 MHz it scales down to in powersave mode. I believe Windows also does not run the CPUs in performance mode by default on mobile devices (but in balanced or balanced performance), I don't know about stationary ones. Performance governor on laptops should be restricted to gamemode. -- 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/1885730 Title: Bring back ondemand.service or switch kernel default governor for pstate - pstate now defaults to performance governor Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Status in linux source package in Groovy: Confirmed Status in systemd source package in Groovy: Invalid Bug description: In a recent merge from Debian we lost ondemand.service, meaning all CPUs now run in Turbo all the time when idle, which is clearly suboptimal. The discussion in bug 1806012 seems misleading, focusing on p-state vs other drivers, when in fact, the script actually set the default governor for the pstate driver on platforms that use pstate. Everything below only looks at systems that use pstate. pstate has two governors: performance and powerstate. performance runs CPU at maximum frequency constantly, and powersave can be configured using various energy profiles energy profiles: - performance - balanced performance - balanced power - power It defaults to balanced performance, I think, but I'm not sure. Whether performance governor is faster than powersave governor is not even clear. https://www.phoronix.com/scan.php?page=article=linux50-pstate- cpufreq=5 benchmarked them, but did not benchmark the individual energy profiles. For a desktop/laptop, the expected behavior is the powersave governor with balanced_performance on AC and balanced_power on battery. I don't know about servers or VMs, but the benchmark series seems to indicate it does not really matter much performance wise. I think most other distributions configure their kernels to use the powersave governor by default, whereas we configure it to use the performance governor and then switch it later in the boot to get the maximum performance during bootup. It's not clear to me that's actually useful. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885730/+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 1885730] Re: Bring back ondemand.service or switch kernel default governor for pstate - pstate now defaults to performance governor
The performance governor is the right choice for servers, but it's not the right choice on non-server platforms, it's also not the default kernel setting, it was set because we have the ondemand.service in userspace that can change it back to ondemand (or well we have the service because of that change in the kernel :D). Fans do not necessarily spin, and you might not actually notice any significant changes in power usage, but the expectation of a desktop user is that the CPU scales its frequencies down, which recent-ish Intel CPUs (Skylake+) on like a ThinkPad T480s - which manage the pstates in hardware instead of software like the old MacBook does - don't do. If we compare this to Red Hat, what they do is CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y in RHEL and CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y in fedora. Power usage, at 3-6% CPU usage: Powersave: I see 0.9-1.4W power usage on the cores Performance, I see 1.6-2.5W -- 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/1885730 Title: Bring back ondemand.service or switch kernel default governor for pstate - pstate now defaults to performance governor Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Status in linux source package in Groovy: Confirmed Status in systemd source package in Groovy: Invalid Bug description: In a recent merge from Debian we lost ondemand.service, meaning all CPUs now run in Turbo all the time when idle, which is clearly suboptimal. The discussion in bug 1806012 seems misleading, focusing on p-state vs other drivers, when in fact, the script actually set the default governor for the pstate driver on platforms that use pstate. Everything below only looks at systems that use pstate. pstate has two governors: performance and powerstate. performance runs CPU at maximum frequency constantly, and powersave can be configured using various energy profiles energy profiles: - performance - balanced performance - balanced power - power It defaults to balanced performance, I think, but I'm not sure. Whether performance governor is faster than powersave governor is not even clear. https://www.phoronix.com/scan.php?page=article=linux50-pstate- cpufreq=5 benchmarked them, but did not benchmark the individual energy profiles. For a desktop/laptop, the expected behavior is the powersave governor with balanced_performance on AC and balanced_power on battery. I don't know about servers or VMs, but the benchmark series seems to indicate it does not really matter much performance wise. I think most other distributions configure their kernels to use the powersave governor by default, whereas we configure it to use the performance governor and then switch it later in the boot to get the maximum performance during bootup. It's not clear to me that's actually useful. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885730/+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 1885562] Autopkgtest regression report (nss/2:3.49.1-1ubuntu1.3)
All autopkgtests for the newly accepted nss (2:3.49.1-1ubuntu1.3) for focal have finished running. The following regressions have been reported in tests triggered by the package: libreoffice/1:6.4.4-0ubuntu0.20.04.1 (arm64, armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#nss [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nss in Ubuntu. https://bugs.launchpad.net/bugs/1885562 Title: [fips] freebl_fipsSoftwareIntegrityTest fails in FIPS mode Status in nss package in Ubuntu: Fix Released Status in nss source package in Bionic: Fix Committed Status in nss source package in Focal: Fix Committed Status in nss source package in Groovy: Fix Released Bug description: [Impact] * Prevents using some parts of nss in FIPS mode - e.g. libfreeblpriv3.so (failed asserts). The library during initialization tries to verify it's own binaries against signatures in chk files shipped along with it (created at build time). They are installed at /usr/lib/$(DEB_HOST_MULTIARCH)/nss while it tries to look for them at /usr/lib/$(DEB_HOST_MULTIARCH). [Test Case] * Setup Ubuntu 18.04 in FIPS mode. * sudo apt install chrony * sudo chronyd -d * chronyd: util.c:373 UTI_IPToRefid: Assertion `MD5_hash >= 0' failed. [Regression Potential] * Fix introduces 2 new artifacts to the filesystem (symlinks to the chk files). It may cause alerts in e.g. CI systems. [Other Info] Original bug description: In FIPS mode there are some additional checks performed. They lead to verifying binaries signatures. Those signatures are shipped in the libnss3 package as *.chk files installed in /usr/lib/$(DEB_HOST_MULTIARCH)/nss. Along with those files are the libraries themselves (libfreebl3.so libfreeblpriv3.so libnssckbi.so libnssdbm3.so libsoftokn3.so). Those libraries are symlinked to be present in /usr/lib/$(DEB_HOST_MULTIARCH): ls -l /usr/lib/x86_64-linux-gnu/libfreeblpriv3.so lrwxrwxrwx 1 root root 21 Jun 10 18:54 /usr/lib/x86_64-linux-gnu/libfreeblpriv3.so -> nss/libfreeblpriv3.so The client binaries are linked against the symlinks, so when the verification happens (lib/freebl/shvfy.c) the mkCheckFileName function takes path to the symlink to the shlib and replaces the .so extension with .chk. Then it tries to open that file. Obviosly it fails, because the actual file is in /usr/lib/$(DEB_HOST_MULTIARCH)/nss. [Test case] sudo apt install chrony sudo chronyd -d chronyd: util.c:373 UTI_IPToRefid: Assertion `MD5_hash >= 0' failed. Potential solutions: Solution A: Drop the /usr/lib/$(DEB_HOST_MULTIARCH)/nss directory and put all signatures and libs in /usr/lib/$(DEB_HOST_MULTIARCH). Solution B: Create symlinks to *.chk files in /usr/lib/$(DEB_HOST_MULTIARCH) (like it is done for *.so). Solution C: Implement and upstream NSS feature of resolving symlinks and looking for *.chk where the symlinks lead to. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1885562/+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 1861941] Re: bcache by-uuid links disappear after mounting bcache0
TODOs (currently being started): 1 - adjust/add bcache-tools patch to use bcache-super-show (full path) (bcache-tools - bionic | focal | groovy) 1.1 - Ubuntu kernel patches for CACHED UUID resubmission could be removed (linux - bionic | focal | groovy) IF (1) is done and SRU'ed 1.2 - Work with upstream so they merge @raharper's patch 2 - drop systemd patch for /dev/disk/by-uuid | /dev/bcache/by-uuid ?? (systemd - bionic | focal | groovy) - I prefer to keep this patch and open upstream discussion for (3) 3 - blkid should not report FS_UUID for bcache backing devices (not a filesytem) (blkid - bionic | focal | groovy) - would avoid useless dev/disk/by-uuid, just like the systemd patch - blkid would have to be SRUed to all or systemd patch kept - will drive upstream discussion 4 - provide a temporary PPA with all fixes before SRU happens (MAAS tests) -- 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/1861941 Title: bcache by-uuid links disappear after mounting bcache0 Status in bcache-tools package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in bcache-tools source package in Bionic: Triaged Status in systemd source package in Bionic: Triaged Status in bcache-tools source package in Focal: Confirmed Status in systemd source package in Focal: Triaged Bug description: 1. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 2. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 5.4.0.12.15 Candidate: 5.4.0.12.15 Version table: *** 5.4.0.12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic linux-image-5.4.0-12-generic: Installed: 5.4.0-12.15 Candidate: 5.4.0-12.15 Version table: *** 5.4.0-12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/ + ls -al /dev/bcache/by-uuid/ total 0 drwxr-xr-x 2 root root 60 Feb 4 23:31 . drwxr-xr-x 3 root root 60 Feb 4 23:31 .. lrwxrwxrwx 1 root root 13 Feb 4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a -> ../../bcache0 4. root@ubuntu:~# ls -al /dev/bcache/by-uuid ls: cannot access '/dev/bcache/by-uuid': No such file or directory ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Tue Feb 4 23:31:52 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+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 1884265] Re: [fips] ntpq segfaults when attempting to use MD5 from FIPS-openssl library.
** Also affects: ntp (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1884265
Title:
[fips] ntpq segfaults when attempting to use MD5 from FIPS-openssl
library.
Status in ntp package in Ubuntu:
New
Status in openssl package in Ubuntu:
In Progress
Status in ntp source package in Bionic:
New
Status in openssl source package in Bionic:
In Progress
Bug description:
[Impact]
In FIPS mode on Bionic MD5 is semi-disabled causing some applications to
segfault.
ntpq uses crypto hashes to authenticate its requests. By default it
uses md5. However, when compiled with openssl it creates a lists of
acceptable hashes from openssl that can be used.
This issue is only applicable in bionic and when using fips-openssl.
[Test Steps]
Test case:
sudo apt install ntp
ntpq -p
Segmentation fault (core dumped)
What happens there is ntpq wants to iterate all available digests
(list_digest_names in ntpq.c). It uses EVP_MD_do_all_sorted for this
task.
EVP_MD_do_all_sorted eventually runs openssl_add_all_digests_int in c_alld.c.
For FIPS mode it adds:
EVP_add_digest(EVP_md5());
What happens later in ntpq is (list_md_fn function inside ntpq.c):
ctx = EVP_MD_CTX_new();
EVP_DigestInit(ctx, EVP_get_digestbyname(name));
EVP_DigestFinal(ctx, digest, _len);
First digest it gets is MD5, but while running EVP_DigestInit for it, it gets
to this point (openssl/crypto/evp/digest.c EVP_DigestInit_ex):
#ifdef OPENSSL_FIPS
if (FIPS_mode()) {
if (!(type->flags & EVP_MD_FLAG_FIPS)
&& !(ctx->flags & EVP_MD_CTX_FLAG_NON_FIPS_ALLOW)) {
EVPerr(EVP_F_EVP_DIGESTINIT_EX, EVP_R_DISABLED_FOR_FIPS);
return 0;
}
}
#endif
Due to type->flags for MD5 being 0 there's an error set
(EVP_R_DISABLED_FOR_FIPS).
After getting back to ntpq.c:
ctx->engine and ctx->digest are not set (due to the mentioned error), hence
inside EVP_DigestFinal_ex (openssl/crypto/evp/digest.c)
OPENSSL_assert(ctx->digest->md_size <= EVP_MAX_MD_SIZE);
causes a segfault (ctx->digest is NULL).
So either MD5 shouldn't be added in FIPS mode or it should have the
EVP_MD_FLAG_FIPS to be properly initialized.
[Regression Potential]
I don't think this should regress ntpq + openssl from the Ubuntu
archive.
Current archive ntpq + openssl behaviour:
openssl includes all message digests and hands ntpq a sorted digest-list.
ntpq doesn't check return from EVP_Digest(Init|Final) and assumes all is well
and sticks all digests into its list regardless if it is working or not.
i.e.
ntpq> help keytype
function: set key type to use for authenticated requests, one of:
MD4, MD5, RIPEMD160, SHA1, SHAKE128
If somehow openssl library is corrupted and sends back erroneous
results, its possible the authentication will just not ever work.
Newly fixed archive ntpq + oenssl beahviour:
openssl includes all message digests and hands ntpq a sorted digest-list.
ntpq checks each one and includes each working digest. With a non-corrupted
openssl, everything works fine and ntpq includes each into its list. Ends up
with a list identical to the one above.
If somehow opensll library is corrupted and sends back erroneous
results, ntpq will hopefully catch it by checking return code and
include only those algos that appear to be working. Its possible
authentication will work for ntpq.
The difference will be seen in ntpq + fips-openssl. ntpq will check
return, and for fips-not-approved algos, return will indicate an
error. So these algos will be skipped and ntpq will not include into
its digest list. Resulting in a much shorter list of only fips-
approved algos.
i.e.
ntpq> help keytype
function: set key type to use for authenticated requests, one of:
SHA1, SHAKE128
Since md5 is ntpq's default auth algo, this will need to be changed to one of
the above algos in the config files.
But I think it is somewhat understood that MD5 is bad in a FIPS environment.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1884265/+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 1873961] Comment bridged from LTC Bugzilla
--- Comment From z...@us.ibm.com 2020-07-22 10:07 EDT--- Download "iproute2_4.15.0-2ubuntu1.2_ppc64el.deb" from: https://launchpad.net/~smb/+archive/ubuntu/bionic/+packages Installed it on Genesis OS (4.15.0-1039-ibm-gt). New "tc" command sum value: root@ltcgen4:~# sum /sbin/tc 45845 729 I am able to see the correct tcp_flags mask with this new /sbin/tc". The new package works. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1873961 Title: tc filter show tcp_flags wrong mask value Status in The Ubuntu-power-systems project: In Progress Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Bionic: In Progress Bug description: [SRU Justification] Impact: The tc command does not show the correct values for tcp_flags (and ip_tos) on filter rules. This might break other scripts parsing that output but at least confuses users. Fix: Backport of "tc: fix bugs for tcp_flags and ip_attr hex output" from upstream iproute2. Testcase: tc qdisc add dev lo ingress tc filter add dev lo parent : prio 3 proto ip flower ip_tos 0x8/32 tc filter add dev lo parent : prio 5 proto ip flower ip_proto tcp \ tcp_flags 0x909/f00 tc filter show dev lo parent : filter protocol ip pref 3 flower chain 0 filter protocol ip pref 3 flower chain 0 handle 0x1 eth_type ipv4 ip_tos a9606c10 <-- bad, should be 0x8/32 not_in_hw filter protocol ip pref 5 flower chain 0 filter protocol ip pref 5 flower chain 0 handle 0x1 eth_type ipv4 ip_proto tcp tcp_flags 909909 <-- bad, should be 0x909/f00 not_in_hw Note that the ip_tos value in the -j[son] output is correct, while the tcp_flags value is is incorrect in both cases. Risk of Regression: Low: Usually scripts would use the json output and that has at least the ip output correct. And the values shown in the bad case seem to be little useful. So it seems unlikely anybody relied on them. But cannot completely be ruled out. === Original description === ---Problem Description--- Problem Descriptions "tc" utility does not show correct TC rule's tcp_flags mask correctly in current "iproute2" package shipped on Genesis. # dpkg -l |grep iproute2 ii iproute2 4.15.0-2ubuntu1 ppc64el networking and traffic control tools ---Steps to Reproduce--- Steps to reproduce the problem: 1) Add a tc rule to the testing VF (i.e. p0v2_r): # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1 flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 2 skip_sw action mirred egress redirect dev p0v0_r 2) Validate the added TC rule: # tc filter show dev p0v2_r root filter protocol ip pref 5 flower chain 1 filter protocol ip pref 5 flower chain 1 handle 0x1 src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff eth_type ipv4 ip_proto tcp tcp_flags 22 /* <--- Wrong */ skip_sw in_hw action order 1: mirred (Egress Redirect to device p0v0_r) stolen 3) If we add the tcp_flags using explicit mask 0x7: # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1 flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 0x2/7 skip_sw action mirred egress redirect dev p0v0_r After that, using "tc filter show dev p0v2_r root" to verify, we still see the same output (tcp_flags 22) as shown in 2) above, which is wrong. Userspace tool common name: tc The userspace tool has the following bit modes: 64-bit Userspace package: iproute2 == Fixes: There are 2 patches to fix the issue: patch 1: commit b85076cd74e77538918d35992b1a9cd17ff86af8 Author: Stephen Hemminger Date: Tue Sep 11 08:29:33 2018 -0700 lib: introduce print_nl Common pattern in iproute commands is to print a line seperator in non-json mode. Make that a simple function. /* This patch declares global variable "const char *_SL_ = "\n";" in lib/utils.c to be used by 2nd patch */ patch 2: commit e8bd395508cead5a81c2bebd9d3705a9e41ea8bc Author: Keara Leibovitz Date: Thu Jul 26 09:45:30 2018 -0400 tc: fix bugs for tcp_flags and ip_attr hex output Fix hex output for both the ip_attr and tcp_flags print functions. With the above 2 patches pull in, the new "tc" utility will show the correct tcp_flags mask: # tc filter show dev p0v2 root filter protocol ip pref 5 flower chain 1 filter protocol ip pref 5 flower chain 1 handle 0x1 src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff eth_type ipv4 ip_proto tcp tcp_flags 0x2/7 /* <--- Correct */ skip_sw in_hw action order 1: mirred (Egress Redirect to device p0v0_r) stolen This bug affects tc in Ubuntu 18.04.1 stock image. To manage notifications about this bug go to:
[Touch-packages] [Bug 1886161] Re: UU should work on roaming laptops
It is actually APT that triggers the u-u runs, so if there is anything that can be fixed around timing that can be done on APT. I agree that it would be desired to download packages even on roaming laptops. ** Package changed: unattended-upgrades (Ubuntu) => apt (Ubuntu) ** Changed in: apt (Ubuntu) Status: Invalid => Opinion ** Changed in: apt (Ubuntu) Status: Opinion => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1886161 Title: UU should work on roaming laptops Status in apt package in Ubuntu: New Bug description: For many if not most laptop computers, Unattended Upgrades seems all but useless by design. For upgrades to happen, with default config, 3 conditions must be met: - an internet connection must be up and running when the timer or cron or anacron tries the unattended upgrade - the connection must not be metered, whatever that means (Skip-Updates-On-Metered-Connections "true") - the computer must be plugged in (OnlyOnACPower "true") These are insurmountable problems for many laptops on the go. Inevitably, security upgrades will almost never run unattended on such computers. I discovered with shock that Unattended Upgrades had almost never run on my laptop. I tried all possible config tweaks. Nothing worked reliably and in the end I gave up and wrote a upgrade script which uses Network Manager's connection-up hook. Unattended Upgrades needs to do something like this out of the box. Users should not need to write scripts to ensure security upgrades. Unattended upgrades is an excellent project for servers. But it really needs to work, out of the box, on laptops too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1886161/+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 1873961] Re: tc filter show tcp_flags wrong mask value
Test build of proposed change at: https://launchpad.net/~smb/+archive/ubuntu/bionic ** Merge proposal linked: https://code.launchpad.net/~smb/ubuntu/+source/iproute2/+git/iproute2/+merge/387837 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1873961 Title: tc filter show tcp_flags wrong mask value Status in The Ubuntu-power-systems project: In Progress Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Bionic: In Progress Bug description: [SRU Justification] Impact: The tc command does not show the correct values for tcp_flags (and ip_tos) on filter rules. This might break other scripts parsing that output but at least confuses users. Fix: Backport of "tc: fix bugs for tcp_flags and ip_attr hex output" from upstream iproute2. Testcase: tc qdisc add dev lo ingress tc filter add dev lo parent : prio 3 proto ip flower ip_tos 0x8/32 tc filter add dev lo parent : prio 5 proto ip flower ip_proto tcp \ tcp_flags 0x909/f00 tc filter show dev lo parent : filter protocol ip pref 3 flower chain 0 filter protocol ip pref 3 flower chain 0 handle 0x1 eth_type ipv4 ip_tos a9606c10 <-- bad, should be 0x8/32 not_in_hw filter protocol ip pref 5 flower chain 0 filter protocol ip pref 5 flower chain 0 handle 0x1 eth_type ipv4 ip_proto tcp tcp_flags 909909 <-- bad, should be 0x909/f00 not_in_hw Note that the ip_tos value in the -j[son] output is correct, while the tcp_flags value is is incorrect in both cases. Risk of Regression: Low: Usually scripts would use the json output and that has at least the ip output correct. And the values shown in the bad case seem to be little useful. So it seems unlikely anybody relied on them. But cannot completely be ruled out. === Original description === ---Problem Description--- Problem Descriptions "tc" utility does not show correct TC rule's tcp_flags mask correctly in current "iproute2" package shipped on Genesis. # dpkg -l |grep iproute2 ii iproute2 4.15.0-2ubuntu1 ppc64el networking and traffic control tools ---Steps to Reproduce--- Steps to reproduce the problem: 1) Add a tc rule to the testing VF (i.e. p0v2_r): # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1 flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 2 skip_sw action mirred egress redirect dev p0v0_r 2) Validate the added TC rule: # tc filter show dev p0v2_r root filter protocol ip pref 5 flower chain 1 filter protocol ip pref 5 flower chain 1 handle 0x1 src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff eth_type ipv4 ip_proto tcp tcp_flags 22 /* <--- Wrong */ skip_sw in_hw action order 1: mirred (Egress Redirect to device p0v0_r) stolen 3) If we add the tcp_flags using explicit mask 0x7: # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1 flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 0x2/7 skip_sw action mirred egress redirect dev p0v0_r After that, using "tc filter show dev p0v2_r root" to verify, we still see the same output (tcp_flags 22) as shown in 2) above, which is wrong. Userspace tool common name: tc The userspace tool has the following bit modes: 64-bit Userspace package: iproute2 == Fixes: There are 2 patches to fix the issue: patch 1: commit b85076cd74e77538918d35992b1a9cd17ff86af8 Author: Stephen Hemminger Date: Tue Sep 11 08:29:33 2018 -0700 lib: introduce print_nl Common pattern in iproute commands is to print a line seperator in non-json mode. Make that a simple function. /* This patch declares global variable "const char *_SL_ = "\n";" in lib/utils.c to be used by 2nd patch */ patch 2: commit e8bd395508cead5a81c2bebd9d3705a9e41ea8bc Author: Keara Leibovitz Date: Thu Jul 26 09:45:30 2018 -0400 tc: fix bugs for tcp_flags and ip_attr hex output Fix hex output for both the ip_attr and tcp_flags print functions. With the above 2 patches pull in, the new "tc" utility will show the correct tcp_flags mask: # tc filter show dev p0v2 root filter protocol ip pref 5 flower chain 1 filter protocol ip pref 5 flower chain 1 handle 0x1 src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff eth_type ipv4 ip_proto tcp tcp_flags 0x2/7 /* <--- Correct */ skip_sw in_hw action order 1: mirred (Egress Redirect to device p0v0_r) stolen This bug affects tc in Ubuntu 18.04.1 stock image. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1873961/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1884255] Re: [AMD/ATI] SBx00 Azalia (Intel HDA) Audio Ubuntu 20.04 not working
I made this video after the last updates, which include: pulseaudio-libraries and linux-firmwares. I created a new user, to see if it was a desktop problem or user settings, but the problem remained. We are available. Hugs. Thanks. ** Attachment added: "sem título.webm" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1884255/+attachment/5394894/+files/sem%20t%C3%ADtulo.webm -- 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/1884255 Title: [AMD/ATI] SBx00 Azalia (Intel HDA) Audio Ubuntu 20.04 not working Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: When you start playing some audio, the sound disappears. 00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) Subsystem: ASUSTeK Computer Inc. M5A78L LE Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel uname -a Linux Marcelo-STI-FX6300 5.4.0-37-generic #41-Ubuntu SMP Wed Jun 3 18:57:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux alsa-info !! !!ALSA Information Script v 0.4.65 !! !!Script ran on: Fri Jun 19 13:38:12 UTC 2020 !!Linux Distribution !!-- Ubuntu 20.04 LTS \n \l DISTRIB_ID=Ubuntu DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS" NAME="Ubuntu" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04 LTS" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies /privacy-policy" UBUNTU_CODENAME=focal !!DMI Information !!--- Manufacturer: System manufacturer Product Name: System Product Name Product Version: System Version Firmware Version: 1201 Board Vendor: ASUSTeK Computer INC. Board Name:M5A78L-M LX/BR !!ACPI Device Status Information !!--- /sys/bus/acpi/devices/ATK0110:00/status15 /sys/bus/acpi/devices/PNP0103:00/status15 /sys/bus/acpi/devices/PNP0400:00/status15 /sys/bus/acpi/devices/PNP0501:00/status15 /sys/bus/acpi/devices/PNP0C0C:00/status11 /sys/bus/acpi/devices/PNP0C0F:00/status9 /sys/bus/acpi/devices/PNP0C0F:01/status9 /sys/bus/acpi/devices/PNP0C0F:02/status9 /sys/bus/acpi/devices/PNP0C0F:03/status9 /sys/bus/acpi/devices/PNP0C0F:04/status9 /sys/bus/acpi/devices/PNP0C0F:05/status9 /sys/bus/acpi/devices/PNP0C0F:06/status9 /sys/bus/acpi/devices/PNP0C0F:07/status9 /sys/bus/acpi/devices/device:20/status 15 /sys/bus/acpi/devices/device:21/status 15 !!Kernel Information !!-- Kernel release:5.4.0-37-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.4.0-37-generic Library version:1.2.3 Utilities version: 1.2.2 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [SB ]: HDA-Intel - HDA ATI SB HDA ATI SB at 0xfe9f4000 irq 16 !!PCI Soundcards installed in the system !!-- 00:14.2 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) [1002:4383] Subsystem: ASUSTeK Computer Inc. M5A78L LE [1043:8445] !!Modprobe options (Sound related) !! snd_pcsp: index=-2 snd_usb_audio: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_usb_audio: index=-2 snd_usb_caiaq: index=-2 snd_usb_ua101: index=-2 snd_usb_us122l: index=-2 snd_usb_usx2y: index=-2 snd_cmipci: mpu_port=0x330 fm_port=0x388 snd_pcsp: index=-2 snd_usb_audio: index=-2 snd_hda_intel: model=auto snd_hda_intel: dmic detect=0 !!Loaded sound module options !!--- !!Module: snd_hda_intel align_buffer_size : -1 bdl_pos_adj : -1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1 beep_mode : N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N dmic_detect : Y enable : Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y enable_msi : -1 id :
[Touch-packages] [Bug 1885755] Re: test-cap-list fails with Linux 5.8 due to new capabilities
The test still fails with systemd 245.6-3ubuntu3. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-groovy-canonical-kernel-team- bootstrap/groovy/amd64/s/systemd/20200721_162550_a22c1@/log.gz ** Changed in: systemd (Ubuntu) Status: Fix Released => Confirmed -- 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/1885755 Title: test-cap-list fails with Linux 5.8 due to new capabilities Status in systemd package in Ubuntu: Confirmed Bug description: == test-cap-list === Assertion 'capability_set_to_string_alloc(c, ) == 0' failed at src/test/test-cap-list.c:60, function test_capability_set_one(). Aborting. FAIL: test-cap-list (code: 134) This seems to be a result of new capabilities added in 5.8. systemd builds an array to convert capability numbers to strings, and these new capabilities are not in its array, so the test bombs out when trying to look up the string for a capability it doesn't know about. Rebuilding systemd using headers from Linux 5.8 should fix this issue. Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/amd64/s/systemd/20200630_154532_b7979@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/arm64/s/systemd/20200630_155538_0c63d@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/ppc64el/s/systemd/20200630_162720_b3e1b@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/s390x/s/systemd/20200630_140417_c5bdb@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1885755/+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 1886161] Re: UU should work on roaming laptops
@rbalint As I detailed, the problems cannot *all* be resolved by config. The biggest one, the first above, is still there. If you turn on a laptop when (1) an update is overdue and (2) there is not yet an internet connection, then the update will not run even if the connection becomes available 5 minutes later. This is an **absolutely typical** situation when on the go and connecting to new wifi networks. Perhaps this is anacron's fault, or systemd's or something, I am not sure. What is certain is that, in the real world, in this common situation, unattended upgrades does not upgrade Ubuntu unattended. I believe that is a significant problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1886161 Title: UU should work on roaming laptops Status in unattended-upgrades package in Ubuntu: Invalid Bug description: For many if not most laptop computers, Unattended Upgrades seems all but useless by design. For upgrades to happen, with default config, 3 conditions must be met: - an internet connection must be up and running when the timer or cron or anacron tries the unattended upgrade - the connection must not be metered, whatever that means (Skip-Updates-On-Metered-Connections "true") - the computer must be plugged in (OnlyOnACPower "true") These are insurmountable problems for many laptops on the go. Inevitably, security upgrades will almost never run unattended on such computers. I discovered with shock that Unattended Upgrades had almost never run on my laptop. I tried all possible config tweaks. Nothing worked reliably and in the end I gave up and wrote a upgrade script which uses Network Manager's connection-up hook. Unattended Upgrades needs to do something like this out of the box. Users should not need to write scripts to ensure security upgrades. Unattended upgrades is an excellent project for servers. But it really needs to work, out of the box, on laptops too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1886161/+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 1888494] [NEW] ss outputs lots of trailing spaces
Public bug reported: $ ss -atn | head -n 5 | tr ' ' '_' State__Recv-Q_Send-Q___Local_Address:Port_Peer_Address:Port_Process_ LISTEN_0__4096_127.0.0.53%lo:530.0.0.0:* LISTEN_0__224__127.0.0.1:5430__0.0.0.0:* LISTEN_0__1280.0.0.0:220.0.0.0:* LISTEN_0__5127.0.0.1:631___0.0.0.0:* These trailing spaces cause problems when piping ss output through grep or anything else unless the terminal window is very wide. The spaces are present even when stdout is a terminal, indeed if I maximize my terminal window (its width becomes a very reasonable 172 characters) and run ss without arguments, the output is interleaved with blank lines. env -i changes nothing. The spaces should be trimmed before output regardless of whether stdout is a terminal. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: iproute2 5.5.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Jul 22 14:05:53 2020 SourcePackage: iproute2 UpgradeStatus: Upgraded to focal on 2020-04-26 (86 days ago) ** Affects: iproute2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1888494 Title: ss outputs lots of trailing spaces Status in iproute2 package in Ubuntu: New Bug description: $ ss -atn | head -n 5 | tr ' ' '_' State__Recv-Q_Send-Q___Local_Address:Port_Peer_Address:Port_Process_ LISTEN_0__4096_127.0.0.53%lo:530.0.0.0:* LISTEN_0__224__127.0.0.1:5430__0.0.0.0:* LISTEN_0__1280.0.0.0:220.0.0.0:* LISTEN_0__5127.0.0.1:631___0.0.0.0:* These trailing spaces cause problems when piping ss output through grep or anything else unless the terminal window is very wide. The spaces are present even when stdout is a terminal, indeed if I maximize my terminal window (its width becomes a very reasonable 172 characters) and run ss without arguments, the output is interleaved with blank lines. env -i changes nothing. The spaces should be trimmed before output regardless of whether stdout is a terminal. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: iproute2 5.5.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Jul 22 14:05:53 2020 SourcePackage: iproute2 UpgradeStatus: Upgraded to focal on 2020-04-26 (86 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1888494/+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 1886854] Re: Race in load-module snap policy check in classic confinement
Yes, I do believe it's the same PA instance, I had not noticed it restarting (e.g. pavucontrol losing the connection) when testing around this bug. Also, I'm not sure if it helps, but the module likes to spam a ton of pulseaudio[11451]: E: [pulseaudio] module-snap-policy.c: AppArmor profile could not be retrieved. pulseaudio[11451]: E: [pulseaudio] module-snap-policy.c: AppArmor profile could not be retrieved. pulseaudio[11451]: E: [pulseaudio] module-snap-policy.c: AppArmor profile could not be retrieved. pulseaudio[11451]: E: [pulseaudio] module-snap-policy.c: AppArmor profile could not be retrieved. into the log even when *not* running as a snap. I don't know if this is related as I've found it to be harmless to the functionality of my programm when running outside snaps. -- 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/1886854 Title: Race in load-module snap policy check in classic confinement Status in pulseaudio package in Ubuntu: New Bug description: SUMMARY = When running a snap in classic confinement, that needs access to PA_COMMAND_LOAD_MODULE and PA_COMMAND_UNLOAD_MODULE. These sometimes succeed and sometimes fail with "Access denied". After running "pacmd unload-module module-snap-policy" and unloading the snap policy module, these work reliably. I have verified this in a fresh install of Ubuntu 20.04 in a VM. STEPS TO REPRODUCE = a) Either build a snap with classic confinement that sends these commands on the pulseaudio native protocol socket. (This is how I found the bug) b) Or, what I did here to easier reproduce, abuse the sandbox of a random classic snap: Download the attached bug.tgz with a minimal reproducer. It contains the source code for a program that sends load and unload commands to pulse. Unfortunately `pacmd` has a pid-file check that fails inside the sandbox and doesn't work. The reproducer does essentially the same as "pacmd load/unload-module" though. (a pre-compiled x64 binary is also included in case you don't have a go compiler and dare to run an untrusted binary in a VM) Unpack the tgz, build it, if necessary with "go mod download && go build" Grab a random classic mode snap to use its sandbox as a test bed: $ sudo snap install atom --classic atom 1.48.0 from Snapcrafters installed Open a shell in its sandbox: snap run --shell atom Navigate to the compiled binary and execute it a few times: user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:10 PulseAudio connection created successfully 2020/07/08 18:46:10 Couldn't load module, error message: PulseAudio error: commandLoadModule -> Access denied user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:11 PulseAudio connection created successfully Loaded Module sucessfully at index: 40 user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:12 PulseAudio connection created successfully Loaded Module sucessfully at index: 41 user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:12 PulseAudio connection created successfully 2020/07/08 18:46:12 Couldn't load module, error message: PulseAudio error: commandLoadModule -> Access denied user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:14 PulseAudio connection created successfully 2020/07/08 18:46:14 Couldn't load module, error message: PulseAudio error: commandLoadModule -> Access denied user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:14 PulseAudio connection created successfully 2020/07/08 18:46:14 Couldn't load module, error message: PulseAudio error: commandLoadModule -> Access denied user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:15 PulseAudio connection created successfully 2020/07/08 18:46:15 Couldn't load module, error message: PulseAudio error: commandLoadModule -> Access denied Succeeds and fails apparently at random. Now from a non-sandboxed shell, run pacmd unload-module module-snap-policy to unload the snap-policy module from pulseaudio, now run ./bug a few more times. It now succeeds reliably, every time. Side note, with the real program on my actual machine, the race seems to behave slightly differently. It seems not to work the first time an application is started, but closing it and reopening it seems to make it work pretty reliably afterwards. Restarting "snapd", causes the following run the snap to fail again. EXPECTED BEHAVIOUR == The pulseaudio snap policy module should correctly determine and enforce it's policy. ACTUAL BEHAVIOUR The pulseaudio snap policy module seemingly at random denies access
[Touch-packages] [Bug 1886854] Re: Race in load-module snap policy check in classic confinement
I think I need to dig into this further. The fact you're seeing a few successful module loads with different module indexes would indicate it is the same Pulse Audio instance. -- 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/1886854 Title: Race in load-module snap policy check in classic confinement Status in pulseaudio package in Ubuntu: New Bug description: SUMMARY = When running a snap in classic confinement, that needs access to PA_COMMAND_LOAD_MODULE and PA_COMMAND_UNLOAD_MODULE. These sometimes succeed and sometimes fail with "Access denied". After running "pacmd unload-module module-snap-policy" and unloading the snap policy module, these work reliably. I have verified this in a fresh install of Ubuntu 20.04 in a VM. STEPS TO REPRODUCE = a) Either build a snap with classic confinement that sends these commands on the pulseaudio native protocol socket. (This is how I found the bug) b) Or, what I did here to easier reproduce, abuse the sandbox of a random classic snap: Download the attached bug.tgz with a minimal reproducer. It contains the source code for a program that sends load and unload commands to pulse. Unfortunately `pacmd` has a pid-file check that fails inside the sandbox and doesn't work. The reproducer does essentially the same as "pacmd load/unload-module" though. (a pre-compiled x64 binary is also included in case you don't have a go compiler and dare to run an untrusted binary in a VM) Unpack the tgz, build it, if necessary with "go mod download && go build" Grab a random classic mode snap to use its sandbox as a test bed: $ sudo snap install atom --classic atom 1.48.0 from Snapcrafters installed Open a shell in its sandbox: snap run --shell atom Navigate to the compiled binary and execute it a few times: user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:10 PulseAudio connection created successfully 2020/07/08 18:46:10 Couldn't load module, error message: PulseAudio error: commandLoadModule -> Access denied user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:11 PulseAudio connection created successfully Loaded Module sucessfully at index: 40 user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:12 PulseAudio connection created successfully Loaded Module sucessfully at index: 41 user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:12 PulseAudio connection created successfully 2020/07/08 18:46:12 Couldn't load module, error message: PulseAudio error: commandLoadModule -> Access denied user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:14 PulseAudio connection created successfully 2020/07/08 18:46:14 Couldn't load module, error message: PulseAudio error: commandLoadModule -> Access denied user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:14 PulseAudio connection created successfully 2020/07/08 18:46:14 Couldn't load module, error message: PulseAudio error: commandLoadModule -> Access denied user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:15 PulseAudio connection created successfully 2020/07/08 18:46:15 Couldn't load module, error message: PulseAudio error: commandLoadModule -> Access denied Succeeds and fails apparently at random. Now from a non-sandboxed shell, run pacmd unload-module module-snap-policy to unload the snap-policy module from pulseaudio, now run ./bug a few more times. It now succeeds reliably, every time. Side note, with the real program on my actual machine, the race seems to behave slightly differently. It seems not to work the first time an application is started, but closing it and reopening it seems to make it work pretty reliably afterwards. Restarting "snapd", causes the following run the snap to fail again. EXPECTED BEHAVIOUR == The pulseaudio snap policy module should correctly determine and enforce it's policy. ACTUAL BEHAVIOUR The pulseaudio snap policy module seemingly at random denies access when the snap has the permissions to do an operation. ADDITIONAL INFORMATION == $ lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 $ apt-cache policy pulseaudio pulseaudio: Installed: 1:13.99.1-1ubuntu3.3 Candidate: 1:13.99.1-1ubuntu3.3 Version table: *** 1:13.99.1-1ubuntu3.3 500 500 http://ch.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:13.99.1-1ubuntu3.2 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 1:13.99.1-1ubuntu3 500 500
[Touch-packages] [Bug 1873961] Re: tc filter show tcp_flags wrong mask value
** Changed in: ubuntu-power-systems Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1873961 Title: tc filter show tcp_flags wrong mask value Status in The Ubuntu-power-systems project: In Progress Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Bionic: In Progress Bug description: [SRU Justification] Impact: The tc command does not show the correct values for tcp_flags (and ip_tos) on filter rules. This might break other scripts parsing that output but at least confuses users. Fix: Backport of "tc: fix bugs for tcp_flags and ip_attr hex output" from upstream iproute2. Testcase: tc qdisc add dev lo ingress tc filter add dev lo parent : prio 3 proto ip flower ip_tos 0x8/32 tc filter add dev lo parent : prio 5 proto ip flower ip_proto tcp \ tcp_flags 0x909/f00 tc filter show dev lo parent : filter protocol ip pref 3 flower chain 0 filter protocol ip pref 3 flower chain 0 handle 0x1 eth_type ipv4 ip_tos a9606c10 <-- bad, should be 0x8/32 not_in_hw filter protocol ip pref 5 flower chain 0 filter protocol ip pref 5 flower chain 0 handle 0x1 eth_type ipv4 ip_proto tcp tcp_flags 909909 <-- bad, should be 0x909/f00 not_in_hw Note that the ip_tos value in the -j[son] output is correct, while the tcp_flags value is is incorrect in both cases. Risk of Regression: Low: Usually scripts would use the json output and that has at least the ip output correct. And the values shown in the bad case seem to be little useful. So it seems unlikely anybody relied on them. But cannot completely be ruled out. === Original description === ---Problem Description--- Problem Descriptions "tc" utility does not show correct TC rule's tcp_flags mask correctly in current "iproute2" package shipped on Genesis. # dpkg -l |grep iproute2 ii iproute2 4.15.0-2ubuntu1 ppc64el networking and traffic control tools ---Steps to Reproduce--- Steps to reproduce the problem: 1) Add a tc rule to the testing VF (i.e. p0v2_r): # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1 flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 2 skip_sw action mirred egress redirect dev p0v0_r 2) Validate the added TC rule: # tc filter show dev p0v2_r root filter protocol ip pref 5 flower chain 1 filter protocol ip pref 5 flower chain 1 handle 0x1 src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff eth_type ipv4 ip_proto tcp tcp_flags 22 /* <--- Wrong */ skip_sw in_hw action order 1: mirred (Egress Redirect to device p0v0_r) stolen 3) If we add the tcp_flags using explicit mask 0x7: # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1 flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 0x2/7 skip_sw action mirred egress redirect dev p0v0_r After that, using "tc filter show dev p0v2_r root" to verify, we still see the same output (tcp_flags 22) as shown in 2) above, which is wrong. Userspace tool common name: tc The userspace tool has the following bit modes: 64-bit Userspace package: iproute2 == Fixes: There are 2 patches to fix the issue: patch 1: commit b85076cd74e77538918d35992b1a9cd17ff86af8 Author: Stephen Hemminger Date: Tue Sep 11 08:29:33 2018 -0700 lib: introduce print_nl Common pattern in iproute commands is to print a line seperator in non-json mode. Make that a simple function. /* This patch declares global variable "const char *_SL_ = "\n";" in lib/utils.c to be used by 2nd patch */ patch 2: commit e8bd395508cead5a81c2bebd9d3705a9e41ea8bc Author: Keara Leibovitz Date: Thu Jul 26 09:45:30 2018 -0400 tc: fix bugs for tcp_flags and ip_attr hex output Fix hex output for both the ip_attr and tcp_flags print functions. With the above 2 patches pull in, the new "tc" utility will show the correct tcp_flags mask: # tc filter show dev p0v2 root filter protocol ip pref 5 flower chain 1 filter protocol ip pref 5 flower chain 1 handle 0x1 src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff eth_type ipv4 ip_proto tcp tcp_flags 0x2/7 /* <--- Correct */ skip_sw in_hw action order 1: mirred (Egress Redirect to device p0v0_r) stolen This bug affects tc in Ubuntu 18.04.1 stock image. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1873961/+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 1886854] Re: Race in load-module snap policy check in classic confinement
I think there's two issues at play here. The hooks we added for module loading/unloading as part of USN-4355-1 simply check if the client has an AppArmor label that looks like it belongs to a snap and denies access if found. This will also deny access to classic snaps, which is probably a mistake. The race condition you've encountered is probably a case of "policy module not in effect" vs. "policy module in effect" rather than a race in the behaviour of the policy module itself. This probably indicates that Pulse is servicing client requests before it has completely started. For the first issue, we can make the hook request info about the snap and allow access to classic snaps. For the second, I think we just need to load module-snap-policy earlier during start up. -- 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/1886854 Title: Race in load-module snap policy check in classic confinement Status in pulseaudio package in Ubuntu: New Bug description: SUMMARY = When running a snap in classic confinement, that needs access to PA_COMMAND_LOAD_MODULE and PA_COMMAND_UNLOAD_MODULE. These sometimes succeed and sometimes fail with "Access denied". After running "pacmd unload-module module-snap-policy" and unloading the snap policy module, these work reliably. I have verified this in a fresh install of Ubuntu 20.04 in a VM. STEPS TO REPRODUCE = a) Either build a snap with classic confinement that sends these commands on the pulseaudio native protocol socket. (This is how I found the bug) b) Or, what I did here to easier reproduce, abuse the sandbox of a random classic snap: Download the attached bug.tgz with a minimal reproducer. It contains the source code for a program that sends load and unload commands to pulse. Unfortunately `pacmd` has a pid-file check that fails inside the sandbox and doesn't work. The reproducer does essentially the same as "pacmd load/unload-module" though. (a pre-compiled x64 binary is also included in case you don't have a go compiler and dare to run an untrusted binary in a VM) Unpack the tgz, build it, if necessary with "go mod download && go build" Grab a random classic mode snap to use its sandbox as a test bed: $ sudo snap install atom --classic atom 1.48.0 from Snapcrafters installed Open a shell in its sandbox: snap run --shell atom Navigate to the compiled binary and execute it a few times: user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:10 PulseAudio connection created successfully 2020/07/08 18:46:10 Couldn't load module, error message: PulseAudio error: commandLoadModule -> Access denied user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:11 PulseAudio connection created successfully Loaded Module sucessfully at index: 40 user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:12 PulseAudio connection created successfully Loaded Module sucessfully at index: 41 user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:12 PulseAudio connection created successfully 2020/07/08 18:46:12 Couldn't load module, error message: PulseAudio error: commandLoadModule -> Access denied user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:14 PulseAudio connection created successfully 2020/07/08 18:46:14 Couldn't load module, error message: PulseAudio error: commandLoadModule -> Access denied user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:14 PulseAudio connection created successfully 2020/07/08 18:46:14 Couldn't load module, error message: PulseAudio error: commandLoadModule -> Access denied user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:15 PulseAudio connection created successfully 2020/07/08 18:46:15 Couldn't load module, error message: PulseAudio error: commandLoadModule -> Access denied Succeeds and fails apparently at random. Now from a non-sandboxed shell, run pacmd unload-module module-snap-policy to unload the snap-policy module from pulseaudio, now run ./bug a few more times. It now succeeds reliably, every time. Side note, with the real program on my actual machine, the race seems to behave slightly differently. It seems not to work the first time an application is started, but closing it and reopening it seems to make it work pretty reliably afterwards. Restarting "snapd", causes the following run the snap to fail again. EXPECTED BEHAVIOUR == The pulseaudio snap policy module should correctly determine and enforce it's policy. ACTUAL BEHAVIOUR The pulseaudio snap policy module seemingly at random denies access when the snap has the
[Touch-packages] [Bug 1873961] Re: tc filter show tcp_flags wrong mask value
** Description changed: + [SRU Justification] + + Impact: The tc command does not show the correct values for tcp_flags + (and ip_tos) on filter rules. This might break other scripts parsing + that output but at least confuses users. + + Fix: Backport of "tc: fix bugs for tcp_flags and ip_attr hex output" + from upstream iproute2. + + Testcase: + tc qdisc add dev lo ingress + tc filter add dev lo parent : prio 3 proto ip flower ip_tos 0x8/32 + tc filter add dev lo parent : prio 5 proto ip flower ip_proto tcp \ + tcp_flags 0x909/f00 + + tc filter show dev lo parent : + + filter protocol ip pref 3 flower chain 0 + filter protocol ip pref 3 flower chain 0 handle 0x1 + eth_type ipv4 + ip_tos a9606c10 <-- bad, should be 0x8/32 + not_in_hw + filter protocol ip pref 5 flower chain 0 + filter protocol ip pref 5 flower chain 0 handle 0x1 + eth_type ipv4 + ip_proto tcp + tcp_flags 909909 <-- bad, should be ßx0ß0/f00 + not_in_hw + + Note that the ip_tos value in the -j[son] output is correct, while the tcp_flags value is + is incorrect in both cases. + + Risk of Regression: + Low: Usually scripts would use the json output and that has at least the ip output correct. And the values shown in the bad case seem to be little useful. So it seems unlikely anybody relied on them. But cannot completely be ruled out. + + + === Original description === + ---Problem Description--- Problem Descriptions "tc" utility does not show correct TC rule's tcp_flags mask correctly in current "iproute2" package shipped on Genesis. # dpkg -l |grep iproute2 ii iproute2 4.15.0-2ubuntu1 ppc64el networking and traffic control tools - - + ---Steps to Reproduce--- - Steps to reproduce the problem: + Steps to reproduce the problem: 1) Add a tc rule to the testing VF (i.e. p0v2_r): # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1 flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 2 skip_sw action mirred egress redirect dev p0v0_r - + 2) Validate the added TC rule: # tc filter show dev p0v2_r root filter protocol ip pref 5 flower chain 1 filter protocol ip pref 5 flower chain 1 handle 0x1 - src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff - eth_type ipv4 - ip_proto tcp - tcp_flags 22 /* <--- Wrong */ - skip_sw - in_hw - action order 1: mirred (Egress Redirect to device p0v0_r) stolen - + src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff + eth_type ipv4 + ip_proto tcp + tcp_flags 22 /* <--- Wrong */ + skip_sw + in_hw + action order 1: mirred (Egress Redirect to device p0v0_r) stolen + 3) If we add the tcp_flags using explicit mask 0x7: # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1 flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 0x2/7 skip_sw action mirred egress redirect dev p0v0_r - - After that, using "tc filter show dev p0v2_r root" to verify, we still see the same output (tcp_flags 22) as shown in 2) above, which is wrong. - - Userspace tool common name: tc - - The userspace tool has the following bit modes: 64-bit + + After that, using "tc filter show dev p0v2_r root" to verify, we still + see the same output (tcp_flags 22) as shown in 2) above, which is wrong. + + Userspace tool common name: tc + + The userspace tool has the following bit modes: 64-bit Userspace package: iproute2 == Fixes: There are 2 patches to fix the issue: patch 1: commit b85076cd74e77538918d35992b1a9cd17ff86af8 Author: Stephen Hemminger Date: Tue Sep 11 08:29:33 2018 -0700 - lib: introduce print_nl - Common pattern in iproute commands is to print a line seperator - in non-json mode. Make that a simple function. + lib: introduce print_nl + Common pattern in iproute commands is to print a line seperator + in non-json mode. Make that a simple function. /* This patch declares global variable "const char *_SL_ = "\n";" in lib/utils.c to be used by 2nd patch */ - + patch 2: commit e8bd395508cead5a81c2bebd9d3705a9e41ea8bc Author: Keara Leibovitz Date: Thu Jul 26 09:45:30 2018 -0400 - tc: fix bugs for tcp_flags and ip_attr hex output - Fix hex output for both the ip_attr and tcp_flags print functions. - + tc: fix bugs for tcp_flags and ip_attr hex output + Fix hex output for both the ip_attr and tcp_flags print functions. + With the above 2 patches pull in, the new "tc" utility will show the correct tcp_flags mask: # tc filter show dev p0v2 root filter protocol ip pref 5 flower chain 1 filter protocol ip pref 5 flower chain 1 handle 0x1 - src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff - eth_type ipv4 - ip_proto tcp - tcp_flags 0x2/7 /* <--- Correct */ - skip_sw - in_hw - action order 1: mirred (Egress Redirect to device p0v0_r) stolen + src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff + eth_type ipv4 + ip_proto
[Touch-packages] [Bug 1888442] Re: upgrade did not go well
You seem to be using ZFS on root (which is EXPERIMENTAL AFAIK). ... update-initramfs: Generating /boot/initrd.img-5.4.0-41-generic cryptsetup: ERROR: Couldn't resolve device rpool/ROOT/ubuntu cryptsetup: WARNING: Couldn't determine root device ... ** Package changed: systemd (Ubuntu) => zfs-linux (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/1888442 Title: upgrade did not go well Status in zfs-linux package in Ubuntu: New Bug description: Hello, I had some problems during my most recent apt upgrade. A confounding factor to these problems was removing my laptop from its docking station a few minutes earlier. $ sudo apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following NEW packages will be installed: linux-headers-5.4.0-42 linux-headers-5.4.0-42-generic linux-image-5.4.0-42-generic linux-modules-5.4.0-42-generic linux-modules-extra-5.4.0-42-generic python3-click python3-colorama The following packages will be upgraded: base-files libnss-mymachines libnss-systemd libpam-systemd libpulse-mainloop-glib0 libpulse0 libpulsedsp libseccomp2 libsystemd0 libudev1 libvirt-clients libvirt-daemon libvirt-daemon-driver-qemu libvirt-daemon-driver-storage-rbd libvirt-daemon-driver-storage-zfs libvirt-daemon-system libvirt-daemon-system-systemd libvirt0 linux-firmware linux-generic linux-headers-generic linux-image-generic pulseaudio pulseaudio-utils python3-distupgrade sudo systemd systemd-container systemd-journal-remote systemd-sysv systemd-timesyncd ubuntu-drivers-common ubuntu-release-upgrader-core udev 34 upgraded, 7 newly installed, 0 to remove and 0 not upgraded. Need to get 110 MB/184 MB of archives. After this operation, 360 MB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://wopr.domain/ubuntu focal-proposed/main amd64 base-files amd64 11ubuntu5.1 [60.1 kB] Get:2 http://wopr.domain/ubuntu focal-proposed/main amd64 libnss-systemd amd64 245.4-4ubuntu3.2 [95.6 kB] Get:3 http://wopr.domain/ubuntu focal-proposed/universe amd64 systemd-journal-remote amd64 245.4-4ubuntu3.2 [61.9 kB] Get:4 http://wopr.domain/ubuntu focal-proposed/main amd64 udev amd64 245.4-4ubuntu3.2 [1,363 kB] Get:5 http://wopr.domain/ubuntu focal-proposed/main amd64 libudev1 amd64 245.4-4ubuntu3.2 [78.9 kB] Get:6 http://wopr.domain/ubuntu focal-proposed/main amd64 libvirt-daemon-system amd64 6.0.0-0ubuntu8.2 [67.5 kB] Get:7 http://wopr.domain/ubuntu focal-proposed/main amd64 libvirt-clients amd64 6.0.0-0ubuntu8.2 [343 kB] Get:8 http://wopr.domain/ubuntu focal-proposed/main amd64 libvirt-daemon-driver-qemu amd64 6.0.0-0ubuntu8.2 [605 kB] Get:9 http://wopr.domain/ubuntu focal-proposed/universe amd64 libvirt-daemon-driver-storage-zfs amd64 6.0.0-0ubuntu8.2 [21.4 kB] Get:10 http://wopr.domain/ubuntu focal-proposed/main amd64 libvirt-daemon-driver-storage-rbd amd64 6.0.0-0ubuntu8.2 [28.3 kB] Get:11 http://wopr.domain/ubuntu focal-proposed/main amd64 libvirt0 amd64 6.0.0-0ubuntu8.2 [1,444 kB] Get:12 http://wopr.domain/ubuntu focal-proposed/main amd64 libvirt-daemon amd64 6.0.0-0ubuntu8.2 [404 kB] Get:13 http://wopr.domain/ubuntu focal-proposed/main amd64 libnss-mymachines amd64 245.4-4ubuntu3.2 [131 kB] Get:14 http://wopr.domain/ubuntu focal-proposed/main amd64 libseccomp2 amd64 2.4.3-1ubuntu3.20.04.3 [42.4 kB] Get:15 http://wopr.domain/ubuntu focal-proposed/main amd64 systemd-container amd64 245.4-4ubuntu3.2 [317 kB] Get:16 http://wopr.domain/ubuntu focal-proposed/main amd64 libvirt-daemon-system-systemd amd64 6.0.0-0ubuntu8.2 [12.3 kB] Get:17 http://wopr.domain/ubuntu focal-proposed/main amd64 systemd-sysv amd64 245.4-4ubuntu3.2 [10.3 kB] Get:18 http://wopr.domain/ubuntu focal-proposed/main amd64 systemd-timesyncd amd64 245.4-4ubuntu3.2 [28.0 kB] Get:19 http://wopr.domain/ubuntu focal-proposed/main amd64 libpam-systemd amd64 245.4-4ubuntu3.2 [186 kB] Get:20 http://wopr.domain/ubuntu focal-proposed/main amd64 systemd amd64 245.4-4ubuntu3.2 [3,796 kB] Get:21 http://wopr.domain/ubuntu focal-proposed/main amd64 libsystemd0 amd64 245.4-4ubuntu3.2 [271 kB] Get:22 http://wopr.domain/ubuntu focal-proposed/main amd64 libpulse-mainloop-glib0 amd64 1:13.99.1-1ubuntu3.5 [11.7 kB] Get:23 http://wopr.domain/ubuntu focal-proposed/main amd64 libpulsedsp amd64 1:13.99.1-1ubuntu3.5 [21.7 kB] Get:24 http://wopr.domain/ubuntu focal-proposed/main amd64 pulseaudio-utils amd64 1:13.99.1-1ubuntu3.5 [55.0 kB] Get:25 http://wopr.domain/ubuntu focal-proposed/main amd64 pulseaudio amd64 1:13.99.1-1ubuntu3.5 [815 kB] Get:26 http://wopr.domain/ubuntu focal-proposed/main amd64 libpulse0 amd64 1:13.99.1-1ubuntu3.5 [263 kB] Get:27 http://wopr.domain/ubuntu focal/main
[Touch-packages] [Bug 1873961] Re: tc filter show tcp_flags wrong mask value
Oh, so the upstream patch had the test case all the time and I just blanked it, looking at the content there and visible comments in this bug report only. :/ Thanks for the pointer. That should be all needed and I can go on with the SRU process. ** Changed in: iproute2 (Ubuntu Bionic) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1873961 Title: tc filter show tcp_flags wrong mask value Status in The Ubuntu-power-systems project: Triaged Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Bionic: In Progress Bug description: ---Problem Description--- Problem Descriptions "tc" utility does not show correct TC rule's tcp_flags mask correctly in current "iproute2" package shipped on Genesis. # dpkg -l |grep iproute2 ii iproute2 4.15.0-2ubuntu1 ppc64el networking and traffic control tools ---Steps to Reproduce--- Steps to reproduce the problem: 1) Add a tc rule to the testing VF (i.e. p0v2_r): # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1 flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 2 skip_sw action mirred egress redirect dev p0v0_r 2) Validate the added TC rule: # tc filter show dev p0v2_r root filter protocol ip pref 5 flower chain 1 filter protocol ip pref 5 flower chain 1 handle 0x1 src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff eth_type ipv4 ip_proto tcp tcp_flags 22 /* <--- Wrong */ skip_sw in_hw action order 1: mirred (Egress Redirect to device p0v0_r) stolen 3) If we add the tcp_flags using explicit mask 0x7: # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1 flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 0x2/7 skip_sw action mirred egress redirect dev p0v0_r After that, using "tc filter show dev p0v2_r root" to verify, we still see the same output (tcp_flags 22) as shown in 2) above, which is wrong. Userspace tool common name: tc The userspace tool has the following bit modes: 64-bit Userspace package: iproute2 == Fixes: There are 2 patches to fix the issue: patch 1: commit b85076cd74e77538918d35992b1a9cd17ff86af8 Author: Stephen Hemminger Date: Tue Sep 11 08:29:33 2018 -0700 lib: introduce print_nl Common pattern in iproute commands is to print a line seperator in non-json mode. Make that a simple function. /* This patch declares global variable "const char *_SL_ = "\n";" in lib/utils.c to be used by 2nd patch */ patch 2: commit e8bd395508cead5a81c2bebd9d3705a9e41ea8bc Author: Keara Leibovitz Date: Thu Jul 26 09:45:30 2018 -0400 tc: fix bugs for tcp_flags and ip_attr hex output Fix hex output for both the ip_attr and tcp_flags print functions. With the above 2 patches pull in, the new "tc" utility will show the correct tcp_flags mask: # tc filter show dev p0v2 root filter protocol ip pref 5 flower chain 1 filter protocol ip pref 5 flower chain 1 handle 0x1 src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff eth_type ipv4 ip_proto tcp tcp_flags 0x2/7 /* <--- Correct */ skip_sw in_hw action order 1: mirred (Egress Redirect to device p0v0_r) stolen This bug affects tc in Ubuntu 18.04.1 stock image. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1873961/+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 1878076] Re: GTK save-dialogs input-focus moves from filename to file search if a folder is selected
The bug appears to be fixed for me in the current stable version of Ubuntu 20.04 with all updates applied. Can someone double check that the following steps work correctly: 1. Open "save" menu from some gnome app (e.g. gedit) 2. Start typing -> expected to type on filename 3. Change folder from left panel 4. Start typing again -> expected to type on filename -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1878076 Title: GTK save-dialogs input-focus moves from filename to file search if a folder is selected Status in GTK+: New Status in gtk+3.0 package in Ubuntu: Triaged Bug description: This bug is also reported on GNOME's GTK GitLab: https://gitlab.gnome.org/GNOME/gtk/issues/326 ## Steps to reproduce 1. Open any GTK app which uses save dialogs (e.g. gedit) 2. Press save 3. A save dialog appears and the filename is highlighted (if typing at this point you edit the file name) 4. Click on a different folder (e.g. Downloads) 5. The filename is still highlighted, hinting that the focus is still there 6. Type and find yourself searching for a file in the selected folder -- Current behavior -- The higlighting (on the file name) hints a focus which is not the actual input focus, and the actual input focus (the search bar) is hidden until one starts to type, which I think to be confusing and unexpected. Also, clicking back on the highlighted filename you lose the highlighting, so you have to highlight again some already highlighted text; I think this to be confusing and counterintuitive. -- Expected outcome -- Highlighting and focus need to match. If they don't that's a UX bug, and there are several options to solve it, some examples: - keep highlighting as is and keep focus on the filename, this whould require finding a different path for file search (I think this is the most productive option, because I assume a user wants to change the folder and eventually rename or name the file, which I consider more likely than a user wanting to search for a file within a save-file dialog); - keep filesearch as is, but show its bar before typing begins, and remove any highlighting from filename. For reference, Windows 10's native save-file dialogs disables the highlighting when clicking on a different folder. Typing does nothing at that point. Tested on gedit 3.36.1 on Ubuntu 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgtk-3-0 3.24.18-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon May 11 21:53:37 2020 InstallationDate: Installed on 2020-04-03 (37 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2020-05-04T10:26:46.106768 To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1878076/+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 1878076] Re: GTK save-dialogs input-focus moves from filename to file search if a folder is selected
It appears the bug is still around when changing folder from the main view, rather than using the sidebar -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1878076 Title: GTK save-dialogs input-focus moves from filename to file search if a folder is selected Status in GTK+: New Status in gtk+3.0 package in Ubuntu: Triaged Bug description: This bug is also reported on GNOME's GTK GitLab: https://gitlab.gnome.org/GNOME/gtk/issues/326 ## Steps to reproduce 1. Open any GTK app which uses save dialogs (e.g. gedit) 2. Press save 3. A save dialog appears and the filename is highlighted (if typing at this point you edit the file name) 4. Click on a different folder (e.g. Downloads) 5. The filename is still highlighted, hinting that the focus is still there 6. Type and find yourself searching for a file in the selected folder -- Current behavior -- The higlighting (on the file name) hints a focus which is not the actual input focus, and the actual input focus (the search bar) is hidden until one starts to type, which I think to be confusing and unexpected. Also, clicking back on the highlighted filename you lose the highlighting, so you have to highlight again some already highlighted text; I think this to be confusing and counterintuitive. -- Expected outcome -- Highlighting and focus need to match. If they don't that's a UX bug, and there are several options to solve it, some examples: - keep highlighting as is and keep focus on the filename, this whould require finding a different path for file search (I think this is the most productive option, because I assume a user wants to change the folder and eventually rename or name the file, which I consider more likely than a user wanting to search for a file within a save-file dialog); - keep filesearch as is, but show its bar before typing begins, and remove any highlighting from filename. For reference, Windows 10's native save-file dialogs disables the highlighting when clicking on a different folder. Typing does nothing at that point. Tested on gedit 3.36.1 on Ubuntu 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgtk-3-0 3.24.18-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon May 11 21:53:37 2020 InstallationDate: Installed on 2020-04-03 (37 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2020-05-04T10:26:46.106768 To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1878076/+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 1886644] Re: SRU the current 3.36.4 stable update
It's worth checking with the security team indeed, thanks for pointing that out, meanwhile it doesn't hurt to have it in -proposed and get some initial testing there -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1886644 Title: SRU the current 3.36.4 stable update Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution-data-server source package in Focal: Fix Committed Bug description: * Impact That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/evolution-data-server/-/blob/gnome-3-36/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Check that the calendar integration in GNOME and gnome-calendar is working, also test evolution with an email account. * Regression potential There is no specific change or feature to test in the upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1886644/+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 1883082] Re: Crash when using Package-Whitelist-Strict
This bug was fixed in the package unattended-upgrades - 2.5
---
unattended-upgrades (2.5) unstable; urgency=medium
[ Jose Manuel Santamaria Lema ]
* Fix crash occuring when strict whitelist is in use (LP: #1883082)
[ Balint Reczey ]
* Fix indentation and type error
* Fix ambiguous variable name (Closes: #963314)
* Run GitHub Action's autopkgtest on Groovy
-- Balint Reczey Tue, 21 Jul 2020 15:42:17 +0200
** Changed in: unattended-upgrades (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1883082
Title:
Crash when using Package-Whitelist-Strict
Status in unattended-upgrades package in Ubuntu:
Fix Released
Status in unattended-upgrades source package in Focal:
New
Bug description:
[Impact]
* Unattended-upgrades crashes when strict whitelist is enabled and
there is an update available.
[Test Case]
Set up a system with at least one updated package available:
$ lxc launch ubuntu:focal ff-uu-strict
Creating ff-uu-strict
Starting ff-uu-strict
$ lxc shell ff-uu-strict
root@ff-uu-strict:~# apt update
...
root@ff-uu-strict:~# apt list --upgradable
Listing... Done
open-vm-tools/focal-updates 2:11.1.0-2~ubuntu20.04.1 amd64 [upgradable
from: 2:11.0.5-4]
N: There is 1 additional version. Please use the '-a' switch to see it
Set up strict whitelist not covering the package:
root@ff-uu-strict:~# echo 'Unattended-Upgrade::Package-Whitelist-Strict
"true";' > /etc/apt/apt.conf.d/51unattended-upgrades-whitelist
root@ff-uu-strict:~# echo 'Unattended-Upgrade::Package-Whitelist {"foo";}'
>> /etc/apt/apt.conf.d/51unattended-upgrades-whitelist
Run unattended-upgrades:
root@ff-uu-strict:~# unattended-upgrade
The fixed version does not crash here, the not fixed one does.
[Regression Potential]
Minimal. The fix adds only one extra check to not crash dereferencing
None.
[Original Bug Text]
Hi,
I'm trying to use unattended-upgrades only with a few packages from a
list; to do that I tried this simple /etc/apt/apt.conf.d/51local-ua
file:
root@focal-ua:~# cat /etc/apt/apt.conf.d/51local-ua
Unattended-Upgrade::Package-Whitelist-Strict "true";
Unattended-Upgrade::Package-Whitelist {
"firefox";
"bash";
"openssh-server";
}
When running unattended-upgrades in dry run mode I get this crash:
root@focal-ua:~# unattended-upgrade --debug --dry-run
Running on the development release
Starting unattended upgrades script
Allowed origins are: o=Ubuntu,a=focal, o=Ubuntu,a=focal-security,
o=UbuntuESMApps,a=focal-apps-security, o=UbuntuESM,a=focal-infra-security,
o=UbuntuESM,a=focal-security
Initial blacklist:
Initial whitelist (strict): firefox bash openssh-server
Marking not allowed
with -32768 pin
Marking not allowed
with -32768 pin
Marking not allowed
with -32768 pin
Marking not allowed
with -32768 pin
Marking not allowed with -32768 pin
Marking not allowed
with -32768 pin
Marking not allowed with -32768 pin
Marking not allowed
with -32768 pin
Marking not allowed with -32768 pin
Marking not allowed
with -32768 pin
An error occurred: '>' not supported between instances of 'apt_pkg.Version'
and 'int'
Traceback (most recent call last):
File "/usr/bin/unattended-upgrade", line 1983, in main
res = run(options, rootdir, mem_log, logfile_dpkg,
File "/usr/bin/unattended-upgrade", line 2124, in run
cache = UnattendedUpgradesCache(rootdir=rootdir)
File "/usr/bin/unattended-upgrade", line 171, in __init__
apt.Cache.__init__(self, rootdir=rootdir)
File "/usr/lib/python3/dist-packages/apt/cache.py", line 170, in __init__
self.open(progress)
File "/usr/bin/unattended-upgrade", line 330, in open
self.apply_pinning(self.pinning_from_config())
File "/usr/bin/unattended-upgrade", line 302, in pinning_from_config
and policy.get_candidate_ver(pkg) > -1: # type: ignore
TypeError: '>' not supported between instances of 'apt_pkg.Version' and 'int'
Extracting content from
/var/log/unattended-upgrades/unattended-upgrades-dpkg.log since 2020-06-11
09:38:25
Traceback (most recent call last):
File "/usr/bin/unattended-upgrade", line 2512, in
sys.exit(main(options))
File "/usr/bin/unattended-upgrade", line 1983, in main
res = run(options, rootdir, mem_log, logfile_dpkg,
File "/usr/bin/unattended-upgrade", line 2124, in run
cache = UnattendedUpgradesCache(rootdir=rootdir)
File "/usr/bin/unattended-upgrade", line 171, in __init__
apt.Cache.__init__(self, rootdir=rootdir)
File "/usr/lib/python3/dist-packages/apt/cache.py", line 170, in __init__
self.open(progress)
File "/usr/bin/unattended-upgrade", line 330, in open
[Touch-packages] [Bug 1885562] Autopkgtest regression report (nss/2:3.35-2ubuntu2.10)
All autopkgtests for the newly accepted nss (2:3.35-2ubuntu2.10) for bionic have finished running. The following regressions have been reported in tests triggered by the package: libreoffice/1:6.0.7-0ubuntu0.18.04.10 (s390x) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#nss [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nss in Ubuntu. https://bugs.launchpad.net/bugs/1885562 Title: [fips] freebl_fipsSoftwareIntegrityTest fails in FIPS mode Status in nss package in Ubuntu: Fix Released Status in nss source package in Bionic: Fix Committed Status in nss source package in Focal: Fix Committed Status in nss source package in Groovy: Fix Released Bug description: [Impact] * Prevents using some parts of nss in FIPS mode - e.g. libfreeblpriv3.so (failed asserts). The library during initialization tries to verify it's own binaries against signatures in chk files shipped along with it (created at build time). They are installed at /usr/lib/$(DEB_HOST_MULTIARCH)/nss while it tries to look for them at /usr/lib/$(DEB_HOST_MULTIARCH). [Test Case] * Setup Ubuntu 18.04 in FIPS mode. * sudo apt install chrony * sudo chronyd -d * chronyd: util.c:373 UTI_IPToRefid: Assertion `MD5_hash >= 0' failed. [Regression Potential] * Fix introduces 2 new artifacts to the filesystem (symlinks to the chk files). It may cause alerts in e.g. CI systems. [Other Info] Original bug description: In FIPS mode there are some additional checks performed. They lead to verifying binaries signatures. Those signatures are shipped in the libnss3 package as *.chk files installed in /usr/lib/$(DEB_HOST_MULTIARCH)/nss. Along with those files are the libraries themselves (libfreebl3.so libfreeblpriv3.so libnssckbi.so libnssdbm3.so libsoftokn3.so). Those libraries are symlinked to be present in /usr/lib/$(DEB_HOST_MULTIARCH): ls -l /usr/lib/x86_64-linux-gnu/libfreeblpriv3.so lrwxrwxrwx 1 root root 21 Jun 10 18:54 /usr/lib/x86_64-linux-gnu/libfreeblpriv3.so -> nss/libfreeblpriv3.so The client binaries are linked against the symlinks, so when the verification happens (lib/freebl/shvfy.c) the mkCheckFileName function takes path to the symlink to the shlib and replaces the .so extension with .chk. Then it tries to open that file. Obviosly it fails, because the actual file is in /usr/lib/$(DEB_HOST_MULTIARCH)/nss. [Test case] sudo apt install chrony sudo chronyd -d chronyd: util.c:373 UTI_IPToRefid: Assertion `MD5_hash >= 0' failed. Potential solutions: Solution A: Drop the /usr/lib/$(DEB_HOST_MULTIARCH)/nss directory and put all signatures and libs in /usr/lib/$(DEB_HOST_MULTIARCH). Solution B: Create symlinks to *.chk files in /usr/lib/$(DEB_HOST_MULTIARCH) (like it is done for *.so). Solution C: Implement and upstream NSS feature of resolving symlinks and looking for *.chk where the symlinks lead to. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1885562/+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
