[Touch-packages] [Bug 1878094] Re: Ubuntu 20.04 / Pulseaudio RTP receive broken sound
The bug was submitted for Ubuntu 20.04, which is an LTS release. The comment changing the status to "Fix Released" mentions a fix is available for Ubuntu 20.10 (groovy), which is the next, non-LTS release. I'm not familiar with the procedure of back-porting code to LTS releases, but since upstream did not release a new mayor/minor version but a small bug fix, the bug fix should not be that problematic to be included in Ubuntu 20.04. Are there any chances for this bug to be fixed in the reported version Ubuntu 20.04, too? -- 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/1878094 Title: Ubuntu 20.04 / Pulseaudio RTP receive broken sound Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Fix Released Bug description: just upgraded some of my computers to Ubuntu 20.04, also tried with fresh install, in all case the pulseaudio rtp receive module is giving me very poor sound. Easily reproducible on a single machine : pacmd load-module module-null-sink sink_name=MyNullSink pacmd load-module module-rtp-send source=MyNullSink.monitor loop=true pacmd load-module module-rtp-recv And then play something in the null sink, loopback sound will be bad (lags). What I noticed : if I open the rtp stream with vlc, it's ok, sound is good. Ubuntu 20 uses PulseAudio 13.99, aka (I guess) PulseAudio 14 which implements RTP through gstreamer, which is new. So I tested my rtp stream with gstreamer: gst-launch-1.0 udpsrc address=224.0.0.56 port=46586 caps="application/x-rtp, media=audio, payload=10, clock-rate=44100" ! .recv_rtp_sink_0 rtpbin ! rtpL16depay ! audioconvert ! audioresample ! pulsesink And it works fine, so I definitively believe there is an issue in the new module-rtp-recv.so bundled with PulseAudio and that is now based on gstreamer. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 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 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/by-id', '/dev/snd/by-path', '/dev/snd/controlC2', '/dev/snd/pcmC2D0c', '/dev/snd/controlC1', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 11 22:22:55 2020 InstallationDate: Installed on 2019-03-31 (407 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-05-09 (2 days ago) dmi.bios.date: 09/13/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1404 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX H370-I GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1404:bd09/13/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXH370-IGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer modified.conffile..etc.pulse.daemon.conf: [modified] modified.conffile..etc.pulse.default.pa: [modified] modified.conffile..etc.pulse.system.pa: [modified] modified.conffile..etc.xdg.autostart.pulseaudio.desktop: [deleted] mtime.conffile..etc.pulse.daemon.conf: 2020-05-10T12:17:27.278185 mtime.conffile..etc.pulse.default.pa: 2020-05-10T12:13:15.278817 mtime.conffile..etc.pulse.system.pa: 2020-05-11T16:24:47.654012 To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1878094/+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 1878094] Re: Ubuntu 20.04 / Pulseaudio RTP receive broken sound
Now requested a fix for 20.04. ** Tags added: rls-ff-incoming -- 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/1878094 Title: Ubuntu 20.04 / Pulseaudio RTP receive broken sound Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Fix Released Bug description: just upgraded some of my computers to Ubuntu 20.04, also tried with fresh install, in all case the pulseaudio rtp receive module is giving me very poor sound. Easily reproducible on a single machine : pacmd load-module module-null-sink sink_name=MyNullSink pacmd load-module module-rtp-send source=MyNullSink.monitor loop=true pacmd load-module module-rtp-recv And then play something in the null sink, loopback sound will be bad (lags). What I noticed : if I open the rtp stream with vlc, it's ok, sound is good. Ubuntu 20 uses PulseAudio 13.99, aka (I guess) PulseAudio 14 which implements RTP through gstreamer, which is new. So I tested my rtp stream with gstreamer: gst-launch-1.0 udpsrc address=224.0.0.56 port=46586 caps="application/x-rtp, media=audio, payload=10, clock-rate=44100" ! .recv_rtp_sink_0 rtpbin ! rtpL16depay ! audioconvert ! audioresample ! pulsesink And it works fine, so I definitively believe there is an issue in the new module-rtp-recv.so bundled with PulseAudio and that is now based on gstreamer. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 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 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/by-id', '/dev/snd/by-path', '/dev/snd/controlC2', '/dev/snd/pcmC2D0c', '/dev/snd/controlC1', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 11 22:22:55 2020 InstallationDate: Installed on 2019-03-31 (407 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-05-09 (2 days ago) dmi.bios.date: 09/13/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1404 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX H370-I GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1404:bd09/13/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXH370-IGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer modified.conffile..etc.pulse.daemon.conf: [modified] modified.conffile..etc.pulse.default.pa: [modified] modified.conffile..etc.pulse.system.pa: [modified] modified.conffile..etc.xdg.autostart.pulseaudio.desktop: [deleted] mtime.conffile..etc.pulse.daemon.conf: 2020-05-10T12:17:27.278185 mtime.conffile..etc.pulse.default.pa: 2020-05-10T12:13:15.278817 mtime.conffile..etc.pulse.system.pa: 2020-05-11T16:24:47.654012 To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1878094/+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 1928048] [NEW] Get black screen on bootup
Public bug reported: Recently installed xubuntu using live usb, the problem is after installation the os is not booting. i had to use "nomodeset" to access the environment. what i want is to boot into my OS easily without making changes in codes or creating nomodesets. just as how windows logs in easily. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE Date: Tue May 11 12:37:15 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:362a] InstallationDate: Installed on 2021-05-11 (0 days ago) InstallationMedia: Xubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO Lenovo C320 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=234ce4f5-05c2-46d4-8195-ccc7a37c627e ro quiet splash vt.handoff=7 nomodeset SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2012 dmi.bios.release: 0.21 dmi.bios.vendor: LENOVO dmi.bios.version: E4KT21AUS dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: LENOVO dmi.board.version: To be filled by O.E.M. dmi.chassis.type: 13 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnLENOVO:bvrE4KT21AUS:bd05/08/2012:br0.21:svnLENOVO:pnLenovoC320:pvrLenovoProduct:rvnLENOVO:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct13:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Lenovo C320 dmi.product.sku: To be filled by O.E.M. dmi.product.version: Lenovo Product dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.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 ** Description changed: - Recently installed xubuntu using live usb, the problem is after - installation the os is not booting. i had to use "nomodeset" to access - the environment. - + Recently installed xubuntu using live usb, the problem is after installation the os is not booting. i had to use "nomodeset" to access the environment. + what i want is to boot into my OS easily without making changes in codes or creating nomodesets. just as how windows logs in easily. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE Date: Tue May 11 12:37:15 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: - Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) -Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:362a] + Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) + Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:362a] InstallationDate: Installed on 2021-05-11 (0 days ago) InstallationMedia: Xubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO Lenovo C320 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=234ce4f5-05c2-46d4-8195-ccc7a37c627e ro quiet splash vt.handoff=7 nomodeset SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2012 dmi.bios.release: 0.21 dmi.bios.vendor: LENOVO dmi.bios.version: E4KT21AUS dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: To be filled by O.E.M.
[Touch-packages] [Bug 1928048] Re: Get black screen on bootup
Thanks for the bug report. We will need to see a system log from a failed boot. To do that, please: 1. Reproduce the bug again (without nomodeset). 2. Reboot with nomodeset. 3. Run: journalctl -b-1 > prevboot1.txt journalctl -b-2 > prevboot2.txt 4. Attach the resulting text files here. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1928048 Title: Get black screen on bootup Status in xorg-server package in Ubuntu: Incomplete Bug description: Recently installed xubuntu using live usb, the problem is after installation the os is not booting. i had to use "nomodeset" to access the environment. what i want is to boot into my OS easily without making changes in codes or creating nomodesets. just as how windows logs in easily. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE Date: Tue May 11 12:37:15 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:362a] InstallationDate: Installed on 2021-05-11 (0 days ago) InstallationMedia: Xubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO Lenovo C320 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=234ce4f5-05c2-46d4-8195-ccc7a37c627e ro quiet splash vt.handoff=7 nomodeset SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2012 dmi.bios.release: 0.21 dmi.bios.vendor: LENOVO dmi.bios.version: E4KT21AUS dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: LENOVO dmi.board.version: To be filled by O.E.M. dmi.chassis.type: 13 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnLENOVO:bvrE4KT21AUS:bd05/08/2012:br0.21:svnLENOVO:pnLenovoC320:pvrLenovoProduct:rvnLENOVO:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct13:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Lenovo C320 dmi.product.sku: To be filled by O.E.M. dmi.product.version: Lenovo Product dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.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/xorg-server/+bug/1928048/+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 1926437] Re: [SRU] Backport zstd support, fix bug in python-apt
The xenial SRU should be good to go now, the snapcraft failures are
unrelated and also reproduced in vorlon's retry of snapcraft itself.
--
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/1926437
Title:
[SRU] Backport zstd support, fix bug in python-apt
Status in apt package in Ubuntu:
Fix Released
Status in python-apt package in Ubuntu:
New
Status in apt source package in Xenial:
Fix Released
Status in python-apt source package in Xenial:
Fix Committed
Status in python-apt source package in Bionic:
Fix Committed
Status in python-apt source package in Focal:
Fix Committed
Status in python-apt source package in Groovy:
Fix Committed
Status in python-apt source package in Hirsute:
Fix Committed
Status in python-apt source package in Impish:
New
Bug description:
[Impact]
APT in xenial needs to learn about zstd support to enable Launchpad to work
with zstd packages.
python-apt in all releases needs to be adjusted to pass the compressor
names instead of programs to ExtractTar, as otherwise, if
/usr/bin/zstd does not exist, it will pass "false" as the compressor,
and then ExtractTar fails (same for other compressors).
On hirsute, the python-apt upload also includes some new
annotations for build-dependencies, as it's a straight upload of the 2.2
stable series.
[Test plan]
The apt regression tests cover the compression methods extensively, including
even stored compressed lists in /var/lib/apt and fetching Packages files
compressed with such methods, for all compression methods.
The final test is to make apt_inst.DebFile("glibc-doc-
reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall() from
1923845 work in python3-apt.
For hirsute, the build dependency changes will verify themselves
during the build ;)
[Where problems could occur]
APT:
The changes to APT are adding the zstd compression backend to FileFd
and then linking it into the configuration. The former is adding new
code, triggered only on zstd files, and should not be able to cause
regressions.
The latter is a bunch of small lines here and there, and it caused
issues during backporting in the test suite because it expected
compressors in a specific order. However, chances are that nothing
else has as stringent requirements as the test suite, so I don't
believe that is a problem for existing users.
Bugs can of course be in the code dealing with zstd, and that might
open you up to security vulnerabilities in the zstd code if you pass
APT zstd compressed files.
A regression can be if clients used apt-helper cat-file to cat a zstd-
compressed file ending in .zst - they'll now get uncompressed content,
rather than compressed.
python-apt:
The change just replaces Binary with Name, aligning the code with APT
itself, so it's so trivial, we don't expect regressions.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1926437/+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 1914278] Re: discover is not removing unused kernels
this bug is somehow in packagekit. I do not use some ui/gui for packagekit, nor unattended-upgrades nor ather automatic update tools. Normally I use apt. apt-mark showmanual | egrep linux-'[g|m|h|i]' linux-generic linux-headers-5.4.0-73 linux-headers-5.4.0-73-generic linux-image-5.4.0-73-generic linux-modules-5.4.0-73-generic linux-modules-extra-5.4.0-73-generic the kernel comes new. This appears after I upgrade with pkcon from commandline. As long I use apt all is okay. -- 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/1914278 Title: discover is not removing unused kernels Status in apt package in Ubuntu: Invalid Status in discover package in Ubuntu: New Status in packagekit package in Ubuntu: New Status in unattended-upgrades package in Ubuntu: Invalid Bug description: With the machines I help administer, we have been finding situations where the /boot directory is filling-up beyond 3 kernels on LUKS encrypted systems. apt autoremove is not removing old kernels as expected. This may also be an issue with unattended-upgrades since I found the following line commented-out by default: // Remove unused automatically installed kernel-related packages // (kernel images, kernel headers and kernel version locked tools). // Unattended-Upgrade::Remove-Unused-Kernel-Packages "true"; We have had a system with as many as 15 kernel packages installed as a result of this not working as expected. The majority of these machines are using Discover to do their package upgrading, which uses PackageKit as its backend. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apt 2.0.4 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Feb 2 09:29:01 2021 InstallationDate: Installed on 2020-11-07 (87 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1914278/+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 1887964] Re: VG unavailable after upgrade from 18.04 to 20.04 Cannot process volume group vg01 Volume group "vg01" not found
So I upgraded from 18.04 LTS to 20.04 LTS too and found that the installed 5.4 kernel panics complaining something about volume group. I booted the 4.15 kernel wich put in a volume group warning too but at least runs. After adding 8.8.8.8 to the resolv.conf the machine is almost ready to work with (yup, I run my own dns/dhcp/dovecot/postfix which all need attention once that kernel/vg bug is no longer in the way). Since my /boot partition is small, I initially thought the ramdisk image is missing/broken/corrupted (there were some warnings in the upgrade process which got stuck between cannot upgrade and cannot restore to initial state - which let me to reboot the machine, trying to fix that on my own). So I uninstalled the 4.4 kernel so only 4.15 and 5.4 are left. While grub was updating I noticed several WARNING: PV /dev/sda1 in VG nameOfVolumeGroup is using an old PV header, modify the VG to update. So I ran sudo vgck --updatemetadata nameOfVolumeGroup to fix that, hoping it would suffice to make 5.4 boot. It didn't: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown- block(0,0) So I booted the 4.15 which complained Volume Group not found nameOfVolumeGroup Cannot process volume group nameOfVolumeGroup but at least booted. Once the machine is booted the volume seems to be accessible, not sure why. Not sure why that didn't work for 5.4. I checked /etc/crypttab but as I don't have crypted drives it contains only the comment header, hexdump -C shows it ends with 0a so no problem there. Now I'm a bit lost: - why is grub still giving me the option to boot the 4.4 kernel, although it's uninstalled? - why does 5.4 fail to process the volume group and panic? - why does 4.15 complain about the vg but still manages to start? (the only good thing so far) - what should I do to make 5.4 (and updated kernels in the future) work on this system? - why does dns does not fall back to 8.8.8.8 or something if the local dns got broken by the update (yeah, that's another issue - point me in the right direction or I'll search for that once the kernel/vg foo is fixed) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1887964 Title: VG unavailable after upgrade from 18.04 to 20.04 Cannot process volume group vg01 Volume group "vg01" not found Status in lvm2 package in Ubuntu: Confirmed Status in lvm2 source package in Focal: Confirmed Bug description: After upgrading a laptop configured with LVM from 18.04 to 20.04 the volume group is no longer found. During boot the console shows Volume group "vg01" not found Cannot process volume group vg01 Gave up waiting for suspend/resume device ALERT! /dev/mapper/vg01-root does not exist. Dropping to a shell! Attached dist-upgrade logs and console output. Tried the "vgck --updatemetadata vg01" recommended on this bug report: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874381 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1887964/+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 1927796] Re: [SRU]pam_tally2 can cause accounts to be locked by correct password. pam_faillock use is the recommended fix
** Also affects: pam (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: pam (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: pam (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: pam (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: pam (Ubuntu Impish) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1927796 Title: [SRU]pam_tally2 can cause accounts to be locked by correct password. pam_faillock use is the recommended fix Status in pam package in Ubuntu: Confirmed Status in pam source package in Bionic: New Status in pam source package in Focal: New Status in pam source package in Groovy: New Status in pam source package in Hirsute: New Status in pam source package in Impish: Confirmed Bug description: [IMPACT] There is a known issue in pam_tally2 which may cause an account to be lock down even with correct password, in a busy node environment where simultaneous logins takes place (https://github.com/linux-pam/linux-pam/issues/71). There are already two customer cases from Canonical clients complaining about this behavior (00297697 and 00303806). Also, potentially, this will cause further problems in the future, since both STIG benchmarks and CIS benchmarks rely on pam_tally2 to lock accounts when wrong passwords are used. And both benchmarks - but specially STIG - requires use of a lot of audit rules, which can lead to the busy node environment. The issue impacts all pam_tally2 versions distributed in all currently supported Ubuntu versions and also the next unreleased one. Note that, according to https://github.com/linux-pam/linux-pam/issues/71, there is no plan to fix this issue! [FIX] This fix proposes to add pam_faillock module to the PAM package, so users of pam_tally2 having issues can migrate to pam_faillock. We also plan to modify the current STIG benchmarks to rely on pam_faillock instead of pam_tally2, but in order to do so, we need the pam_faillock module to be available. Note that we don't propose to remove pam_tally2, since not every user of this module is affected. [TEST] Tested on a VM installed with Focal server iso and on another with Bionic server iso. Enabled pam_faillock module as recommeded by its man page. Then tried to log over ssh with an incorrect password, until the account got locked. Waited for the configured grace time to unlock and logged in using the correct password. Note that, since the pam_tally2 issue is caused by a racing condition, with a hard to recreate environment (we could not even reproduce it with pam_tally2), we could not reproduce the conditions to test pam_faillock with. [REGRESSION POTENTIAL] The regression potential for this is small, since we're not removing the old pam_tally2 module, just adding another one. So anyone still using pam_tally2 will be able to do so. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1927796/+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 1926316] Re: lxappearance crashes on launch
The glib update has been synced to impish, https://bugs.launchpad.net/ubuntu/+source/glib2.0/2.68.1-2 There is also a SRU in the hirsute queue ** Changed in: glib2.0 (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: glib2.0 (Ubuntu) Assignee: (unassigned) => Iain Lane (laney) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1926316 Title: lxappearance crashes on launch Status in glib2.0 package in Ubuntu: Fix Released Bug description: Backtrace of the segmentation fault Program received signal SIGSEGV, Segmentation fault. 0x7790c79d in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 (gdb) bt #0 0x7790c79d in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7790ccc1 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7790cf41 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7790d079 in g_key_file_load_from_file () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x55407072 in load_icon_themes_from_dir () #5 0x554073dd in icon_theme_init () #6 0x55404c92 in main () Strace shows that the programs borks while trying to load the icon theme "/usr/share/icons/gnome/index.theme". ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: lxappearance 0.6.3-1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown Config_System_openbox: Error: [Errno 2] No such file or directory: '/etc/xdg/lxsession/openbox/desktop.conf' CurrentDesktop: lxde Date: Tue Apr 27 21:47:03 2021 Icons_Default: No icons theme configured by default InstallationDate: Installed on 2021-01-12 (105 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: lxappearance UpgradeStatus: Upgraded to hirsute on 2021-04-22 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1926316/+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 1887964] Re: VG unavailable after upgrade from 18.04 to 20.04 Cannot process volume group vg01 Volume group "vg01" not found
FYI: my system is quite old, I started with 8.04 server LTS and upgraded since so my problems are rarely reproducible on systems that were conceived later. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1887964 Title: VG unavailable after upgrade from 18.04 to 20.04 Cannot process volume group vg01 Volume group "vg01" not found Status in lvm2 package in Ubuntu: Confirmed Status in lvm2 source package in Focal: Confirmed Bug description: After upgrading a laptop configured with LVM from 18.04 to 20.04 the volume group is no longer found. During boot the console shows Volume group "vg01" not found Cannot process volume group vg01 Gave up waiting for suspend/resume device ALERT! /dev/mapper/vg01-root does not exist. Dropping to a shell! Attached dist-upgrade logs and console output. Tried the "vgck --updatemetadata vg01" recommended on this bug report: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874381 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1887964/+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 1887964] Re: VG unavailable after upgrade from 18.04 to 20.04 Cannot process volume group vg01 Volume group "vg01" not found
Update: I installed 5.4.0-73 via update, grub config got updated but after reboot only 5.4.0-72 (the broken one) 4.15 4.4 (the uninstalled one) appeared in the grub menu. After "reparing" the grub update (see: https://askubuntu.com/a/1207143), the machine boots into 5.4.0-73 without major issues. There are still a bunch of warnings but at least it starts. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1887964 Title: VG unavailable after upgrade from 18.04 to 20.04 Cannot process volume group vg01 Volume group "vg01" not found Status in lvm2 package in Ubuntu: Confirmed Status in lvm2 source package in Focal: Confirmed Bug description: After upgrading a laptop configured with LVM from 18.04 to 20.04 the volume group is no longer found. During boot the console shows Volume group "vg01" not found Cannot process volume group vg01 Gave up waiting for suspend/resume device ALERT! /dev/mapper/vg01-root does not exist. Dropping to a shell! Attached dist-upgrade logs and console output. Tried the "vgck --updatemetadata vg01" recommended on this bug report: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874381 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1887964/+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 1925823] Re: losts or misinterprets the newline character coming from mouse paste
** Summary changed: - losts or ignore the newline character coming from mouse paste + losts or misinterprets the newline character coming from mouse paste -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1925823 Title: losts or misinterprets the newline character coming from mouse paste Status in bash package in Ubuntu: Confirmed Bug description: If there is a complete bash command with terminating newline in the cut and paste buffer, and it is pasted into a gnome-terminal, then the command is *not* executed, the newline is ignored by the terminal. But in return this bug, the pasted command is showed in reverse coloring, what is very disturbing when a command is not executed, but decorated in a funny way instead. This is new in 21.04, the dropping commands into a gnome-terminal worked fine in 20.10, ... ... and in the last 27 years of my linux usage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1925823/+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 1928082] [NEW] the minimize display freezes
Public bug reported: the display freezes when i try minimizing after a very long use time ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 11 13:09:28 2021 DistUpgraded: 2021-04-26 11:56:19,497 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-io-error-quark: Failed to execute child process “./xorg_fix_proprietary.py”: Failed to execve: No such file or directory (1)) DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.18, 5.11.0-16-generic, x86_64: installed virtualbox, 6.1.18, 5.8.0-50-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f3] InstallationDate: Installed on 2019-06-10 (701 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 23445HU ProcEnviron: LANGUAGE=en_NG:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NG SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=65bd11b5-874d-460b-8539-b2b68af2927a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to hirsute on 2021-04-26 (15 days ago) dmi.bios.date: 03/06/2014 dmi.bios.release: 2.64 dmi.bios.vendor: LENOVO dmi.bios.version: G1ETA4WW (2.64 ) dmi.board.asset.tag: Not Available dmi.board.name: 23445HU dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrG1ETA4WW(2.64):bd03/06/2014:br2.64:efr1.13:svnLENOVO:pn23445HU:pvrThinkPadT430:rvnLENOVO:rn23445HU:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430 dmi.product.name: 23445HU dmi.product.sku: LENOVO_MT_2344 dmi.product.version: ThinkPad T430 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4 version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute ubuntu wayland-session -- 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/1928082 Title: the minimize display freezes Status in xorg package in Ubuntu: New Bug description: the display freezes when i try minimizing after a very long use time ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 11 13:09:28 2021 DistUpgraded: 2021-04-26 11:56:19,497 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-io-error-quark: Failed to execute child process “./xorg_fix_proprietary.py”: Failed to execve: No such file or directory (1)) DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.18, 5.11.0-16-generic, x86_64: installed virtualbox, 6.1.18, 5.8.0-50-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f3] InstallationDate: Installed on 2019-06-10 (701 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 23445HU ProcEnviron: LANGUAGE=en_NG:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NG SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=65bd11b5-874d-460b-8539-b2b68af2927a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom
[Touch-packages] [Bug 1927796] Re: [SRU]pam_tally2 can cause accounts to be locked by correct password. pam_faillock use is the recommended fix
The debdiffs in comment #1 currently create a multiarch manpage collision because of a pam packaging particularity. (See bug 1558597 for an example) I will update the debdiffs to correct the issue and will post them here once done. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1927796 Title: [SRU]pam_tally2 can cause accounts to be locked by correct password. pam_faillock use is the recommended fix Status in pam package in Ubuntu: Confirmed Status in pam source package in Bionic: New Status in pam source package in Focal: New Status in pam source package in Groovy: New Status in pam source package in Hirsute: New Status in pam source package in Impish: Confirmed Bug description: [IMPACT] There is a known issue in pam_tally2 which may cause an account to be lock down even with correct password, in a busy node environment where simultaneous logins takes place (https://github.com/linux-pam/linux-pam/issues/71). There are already two customer cases from Canonical clients complaining about this behavior (00297697 and 00303806). Also, potentially, this will cause further problems in the future, since both STIG benchmarks and CIS benchmarks rely on pam_tally2 to lock accounts when wrong passwords are used. And both benchmarks - but specially STIG - requires use of a lot of audit rules, which can lead to the busy node environment. The issue impacts all pam_tally2 versions distributed in all currently supported Ubuntu versions and also the next unreleased one. Note that, according to https://github.com/linux-pam/linux-pam/issues/71, there is no plan to fix this issue! [FIX] This fix proposes to add pam_faillock module to the PAM package, so users of pam_tally2 having issues can migrate to pam_faillock. We also plan to modify the current STIG benchmarks to rely on pam_faillock instead of pam_tally2, but in order to do so, we need the pam_faillock module to be available. Note that we don't propose to remove pam_tally2, since not every user of this module is affected. [TEST] Tested on a VM installed with Focal server iso and on another with Bionic server iso. Enabled pam_faillock module as recommeded by its man page. Then tried to log over ssh with an incorrect password, until the account got locked. Waited for the configured grace time to unlock and logged in using the correct password. Note that, since the pam_tally2 issue is caused by a racing condition, with a hard to recreate environment (we could not even reproduce it with pam_tally2), we could not reproduce the conditions to test pam_faillock with. [REGRESSION POTENTIAL] The regression potential for this is small, since we're not removing the old pam_tally2 module, just adding another one. So anyone still using pam_tally2 will be able to do so. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1927796/+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 1925823] Re: losts or misinterprets the newline character coming from mouse paste
Sorry that I edited the original bug report, but I think it was better to make it more informative, and not to grab these improvements of the bug description among the comments. Read please, re-read please the new version of the bug report. ** Description changed: + Quiete a few experients shows, that bash misinterprets the newline- + character coming from mouse paste, while in the same terminals the emacs + or vim or alpine and many other character oriented programs interprest + correctly. + + The problem is specific to the situation when we are at a bash prompt of + a new version of bash we got in Ubuntu 21.04. As soon as I invoke an ssh + session, the interpretation of the newline-caharcter becomes correct, + since the remote older bash interprets correctly. + + >>> Newline bug of first kind: + If there is a complete bash command with terminating newline in the cut and paste buffer, and it is pasted into a gnome-terminal, then the command is *not* executed, the newline is ignored by the terminal. - But in return this bug, the pasted command is showed in reverse - coloring, + >>> Newline bug of second kind: - what is very disturbing when a command is not executed, but decorated in - a funny way instead. + If I prepare a bash command say - This is new in 21.04, the dropping commands into a gnome-terminal worked - fine in 20.10, ... + cp target-directory - ... and in the last 27 years of my linux usage. + and I collect into the paste buffer "source-file newline-character" + + and I drop it IN BETWEEN the prepared "cp" and "target-directory" + + then the result is wrong: + + instead of interpreting the newline-character as "push enter" + + the command is broken into the followint 2 lines: + + cp source-file + + target-directory + + and I get an error message about missing target specification. + + cp: missing destination file operand after 'source-file' + Try 'cp --help' for more information. + bash: target-directory: Is a directory + + I found better to make this original bug descripton more informative. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1925823 Title: losts or misinterprets the newline character coming from mouse paste Status in bash package in Ubuntu: Confirmed Bug description: Quiete a few experients shows, that bash misinterprets the newline- character coming from mouse paste, while in the same terminals the emacs or vim or alpine and many other character oriented programs interprest correctly. The problem is specific to the situation when we are at a bash prompt of a new version of bash we got in Ubuntu 21.04. As soon as I invoke an ssh session, the interpretation of the newline-caharcter becomes correct, since the remote older bash interprets correctly. >>> Newline bug of first kind: If there is a complete bash command with terminating newline in the cut and paste buffer, and it is pasted into a gnome-terminal, then the command is *not* executed, the newline is ignored by the terminal. >>> Newline bug of second kind: If I prepare a bash command say cp target-directory and I collect into the paste buffer "source-file newline-character" and I drop it IN BETWEEN the prepared "cp" and "target-directory" then the result is wrong: instead of interpreting the newline-character as "push enter" the command is broken into the followint 2 lines: cp source-file target-directory and I get an error message about missing target specification. cp: missing destination file operand after 'source-file' Try 'cp --help' for more information. bash: target-directory: Is a directory I found better to make this original bug descripton more informative. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1925823/+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 1928088] [NEW] Empty pockets don't end up in the cache - E: The value 'hirsute-backports' is invalid for APT::Default-Release as such a release is not available in the sources
Public bug reported: [Impact] If a pocket is empty, apt will not download the empty packages files, causing the repository to not be added to the cache. This in turn breaks commands such as using apt install -t hirsute-backports as apt is unable to find the release in the archive. [Test plan] Assuming an empty pocket is around, use apt install -t - to see it's in the cache. An appropriate test case for empty stuff should be added to the test suite as well (FIXME before SRUing), the test suite is extensive and prevents most regressions [Where problems could occur] TBD [Other info] Originally reported at https://www.reddit.com/r/Kubuntu/comments/n9vg9e/cant_make_backports_repo_for_hirsute_to_work/ ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Description changed: [Impact] If a pocket is empty, apt will not download the empty packages files, causing the repository to not be added to the cache. This in turn breaks commands such as using apt install -t hirsute-backports as apt is unable to find the release in the archive. [Test plan] Assuming an empty pocket is around, use apt install -t - to see it's in the cache. An appropriate test case for empty stuff should be added to the test suite as well (FIXME before SRUing), the test suite is extensive and prevents most regressions [Where problems could occur] TBD + + [Other info] + Originally reported at https://www.reddit.com/r/Kubuntu/comments/n9vg9e/cant_make_backports_repo_for_hirsute_to_work/ -- 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/1928088 Title: Empty pockets don't end up in the cache - E: The value 'hirsute- backports' is invalid for APT::Default-Release as such a release is not available in the sources Status in apt package in Ubuntu: New Bug description: [Impact] If a pocket is empty, apt will not download the empty packages files, causing the repository to not be added to the cache. This in turn breaks commands such as using apt install -t hirsute-backports as apt is unable to find the release in the archive. [Test plan] Assuming an empty pocket is around, use apt install -t - to see it's in the cache. An appropriate test case for empty stuff should be added to the test suite as well (FIXME before SRUing), the test suite is extensive and prevents most regressions [Where problems could occur] TBD [Other info] Originally reported at https://www.reddit.com/r/Kubuntu/comments/n9vg9e/cant_make_backports_repo_for_hirsute_to_work/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1928088/+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 1928100] [NEW] TLS handshake is fatal, not transient - hence not retried
Public bug reported: [Impact] TLS handshakes are reported as fatal errors rather than transient errors like other connection errors on unencrypted connections. This seems wrong - a server may just be spinning up or down and fail during the handshake, and prevents retrying such downloads [Test plan] A test case has been added to the integration test suite that ensures handshake errors are retried upon configuration. [Where problems could occur] Transient errors do not cause an error exit from apt update, so scripts relying on errors from TLS handshakes in such situations will fail. ** Affects: apt (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/1928100 Title: TLS handshake is fatal, not transient - hence not retried Status in apt package in Ubuntu: New Bug description: [Impact] TLS handshakes are reported as fatal errors rather than transient errors like other connection errors on unencrypted connections. This seems wrong - a server may just be spinning up or down and fail during the handshake, and prevents retrying such downloads [Test plan] A test case has been added to the integration test suite that ensures handshake errors are retried upon configuration. [Where problems could occur] Transient errors do not cause an error exit from apt update, so scripts relying on errors from TLS handshakes in such situations will fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1928100/+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 1926437] Re: [SRU] Backport zstd support, fix bug in python-apt
This bug was fixed in the package python-apt - 2.2.0
---
python-apt (2.2.0) unstable; urgency=medium
[ Helmut Grohne ]
* Annotate test dependencies with (Closes: #980719)
[ Julian Andres Klode ]
* debian/rules: Re-enable PIE hardening
* Mirror list updates
* debfile: Pass `Name` instead of `Binary` to ExtractTar.
Passing the binary causes it to fail trying to find the `false`
compressor when a binary for a given compressor is not installed.
(LP: #1926437)
* debian/gbp.conf: Branch name is main
-- Julian Andres Klode Thu, 29 Apr 2021 09:49:08
+0200
** Changed in: python-apt (Ubuntu Impish)
Status: New => Fix Released
--
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/1926437
Title:
[SRU] Backport zstd support, fix bug in python-apt
Status in apt package in Ubuntu:
Fix Released
Status in python-apt package in Ubuntu:
Fix Released
Status in apt source package in Xenial:
Fix Released
Status in python-apt source package in Xenial:
Fix Committed
Status in python-apt source package in Bionic:
Fix Committed
Status in python-apt source package in Focal:
Fix Committed
Status in python-apt source package in Groovy:
Fix Committed
Status in python-apt source package in Hirsute:
Fix Committed
Status in python-apt source package in Impish:
Fix Released
Bug description:
[Impact]
APT in xenial needs to learn about zstd support to enable Launchpad to work
with zstd packages.
python-apt in all releases needs to be adjusted to pass the compressor
names instead of programs to ExtractTar, as otherwise, if
/usr/bin/zstd does not exist, it will pass "false" as the compressor,
and then ExtractTar fails (same for other compressors).
On hirsute, the python-apt upload also includes some new
annotations for build-dependencies, as it's a straight upload of the 2.2
stable series.
[Test plan]
The apt regression tests cover the compression methods extensively, including
even stored compressed lists in /var/lib/apt and fetching Packages files
compressed with such methods, for all compression methods.
The final test is to make apt_inst.DebFile("glibc-doc-
reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall() from
1923845 work in python3-apt.
For hirsute, the build dependency changes will verify themselves
during the build ;)
[Where problems could occur]
APT:
The changes to APT are adding the zstd compression backend to FileFd
and then linking it into the configuration. The former is adding new
code, triggered only on zstd files, and should not be able to cause
regressions.
The latter is a bunch of small lines here and there, and it caused
issues during backporting in the test suite because it expected
compressors in a specific order. However, chances are that nothing
else has as stringent requirements as the test suite, so I don't
believe that is a problem for existing users.
Bugs can of course be in the code dealing with zstd, and that might
open you up to security vulnerabilities in the zstd code if you pass
APT zstd compressed files.
A regression can be if clients used apt-helper cat-file to cat a zstd-
compressed file ending in .zst - they'll now get uncompressed content,
rather than compressed.
python-apt:
The change just replaces Binary with Name, aligning the code with APT
itself, so it's so trivial, we don't expect regressions.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1926437/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1903048] Re: [SRU] Bluetooth won't activate on the pi 400
This bug was fixed in the package bluez - 5.53-0ubuntu3.1 --- bluez (5.53-0ubuntu3.1) focal; urgency=medium * Add support for the pi 400 (LP: #1903048) -- William 'jawn-smith' Wilson Mon, 15 Mar 2021 19:25:22 + ** Changed in: bluez (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1903048 Title: [SRU] Bluetooth won't activate on the pi 400 Status in bluez package in Ubuntu: Fix Released Status in bluez source package in Focal: Fix Released Status in bluez source package in Groovy: Fix Released Status in bluez source package in Hirsute: Fix Released Bug description: [Impact] Without these patches, Bluetooth is inoperable on the recently released Raspberry Pi 400. [Test Case] * Boot the Ubuntu Desktop for Pi image on a Pi 400. * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is not enabled and attempting to activate it fails * Enable the -proposed repository for the release (groovy) * sudo apt update * sudo apt install bluez * sudo reboot * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is active and that Bluetooth devices (e.g. mice, mobile phones, headphones, etc.) can connect and operate correctly [Regression Potential] Extremely low (on groovy in particular, this has the same version of bluez as hirsute). The only significant risk is to non-Pi platforms or dongles which also use the Broadcom 43xx (or Cypress 305) chips for Bluetooth which might be inadvertently affected by these patches. [Original Description] The new Pi 400 has a slightly different Wifi/BT chip to the Pi4. Whilst wifi works happily, Bluetooth fails to operate. This doesn't appear to be an issue with either the firmware (the latest versions from upstream Raspbian have been tried), or the kernel (a known-good raspi kernel has been tested under Ubuntu), but with Bluez itself. Specifically, tracing the initialization with btmon on Raspbian and Ubuntu, the stack consistently fails when attempting to "Set Default PHY" on the latter. Curiously, under Ubuntu the adapter also appears to lack a MAC address. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903048/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1927796] Re: [SRU]pam_tally2 can cause accounts to be locked by correct password. pam_faillock use is the recommended fix
** Patch added: "Hirsute debdiff" https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1927796/+attachment/5496423/+files/pam_1.3.1-5ubuntu6.21.04.1.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1927796 Title: [SRU]pam_tally2 can cause accounts to be locked by correct password. pam_faillock use is the recommended fix Status in pam package in Ubuntu: Confirmed Status in pam source package in Bionic: New Status in pam source package in Focal: New Status in pam source package in Groovy: New Status in pam source package in Hirsute: New Status in pam source package in Impish: Confirmed Bug description: [IMPACT] There is a known issue in pam_tally2 which may cause an account to be lock down even with correct password, in a busy node environment where simultaneous logins takes place (https://github.com/linux-pam/linux-pam/issues/71). There are already two customer cases from Canonical clients complaining about this behavior (00297697 and 00303806). Also, potentially, this will cause further problems in the future, since both STIG benchmarks and CIS benchmarks rely on pam_tally2 to lock accounts when wrong passwords are used. And both benchmarks - but specially STIG - requires use of a lot of audit rules, which can lead to the busy node environment. The issue impacts all pam_tally2 versions distributed in all currently supported Ubuntu versions and also the next unreleased one. Note that, according to https://github.com/linux-pam/linux-pam/issues/71, there is no plan to fix this issue! [FIX] This fix proposes to add pam_faillock module to the PAM package, so users of pam_tally2 having issues can migrate to pam_faillock. We also plan to modify the current STIG benchmarks to rely on pam_faillock instead of pam_tally2, but in order to do so, we need the pam_faillock module to be available. Note that we don't propose to remove pam_tally2, since not every user of this module is affected. [TEST] Tested on a VM installed with Focal server iso and on another with Bionic server iso. Enabled pam_faillock module as recommeded by its man page. Then tried to log over ssh with an incorrect password, until the account got locked. Waited for the configured grace time to unlock and logged in using the correct password. Note that, since the pam_tally2 issue is caused by a racing condition, with a hard to recreate environment (we could not even reproduce it with pam_tally2), we could not reproduce the conditions to test pam_faillock with. [REGRESSION POTENTIAL] The regression potential for this is small, since we're not removing the old pam_tally2 module, just adding another one. So anyone still using pam_tally2 will be able to do so. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1927796/+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 1927796] Re: [SRU]pam_tally2 can cause accounts to be locked by correct password. pam_faillock use is the recommended fix
** Patch added: "Focal debdiff" https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1927796/+attachment/5496425/+files/pam_1.3.1-5ubuntu4.2.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1927796 Title: [SRU]pam_tally2 can cause accounts to be locked by correct password. pam_faillock use is the recommended fix Status in pam package in Ubuntu: Confirmed Status in pam source package in Bionic: New Status in pam source package in Focal: New Status in pam source package in Groovy: New Status in pam source package in Hirsute: New Status in pam source package in Impish: Confirmed Bug description: [IMPACT] There is a known issue in pam_tally2 which may cause an account to be lock down even with correct password, in a busy node environment where simultaneous logins takes place (https://github.com/linux-pam/linux-pam/issues/71). There are already two customer cases from Canonical clients complaining about this behavior (00297697 and 00303806). Also, potentially, this will cause further problems in the future, since both STIG benchmarks and CIS benchmarks rely on pam_tally2 to lock accounts when wrong passwords are used. And both benchmarks - but specially STIG - requires use of a lot of audit rules, which can lead to the busy node environment. The issue impacts all pam_tally2 versions distributed in all currently supported Ubuntu versions and also the next unreleased one. Note that, according to https://github.com/linux-pam/linux-pam/issues/71, there is no plan to fix this issue! [FIX] This fix proposes to add pam_faillock module to the PAM package, so users of pam_tally2 having issues can migrate to pam_faillock. We also plan to modify the current STIG benchmarks to rely on pam_faillock instead of pam_tally2, but in order to do so, we need the pam_faillock module to be available. Note that we don't propose to remove pam_tally2, since not every user of this module is affected. [TEST] Tested on a VM installed with Focal server iso and on another with Bionic server iso. Enabled pam_faillock module as recommeded by its man page. Then tried to log over ssh with an incorrect password, until the account got locked. Waited for the configured grace time to unlock and logged in using the correct password. Note that, since the pam_tally2 issue is caused by a racing condition, with a hard to recreate environment (we could not even reproduce it with pam_tally2), we could not reproduce the conditions to test pam_faillock with. [REGRESSION POTENTIAL] The regression potential for this is small, since we're not removing the old pam_tally2 module, just adding another one. So anyone still using pam_tally2 will be able to do so. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1927796/+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 1927796] Re: [SRU]pam_tally2 can cause accounts to be locked by correct password. pam_faillock use is the recommended fix
** Patch added: "Bionic debdiff" https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1927796/+attachment/5496426/+files/pam_1.1.8-3.6ubuntu2.18.04.3.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1927796 Title: [SRU]pam_tally2 can cause accounts to be locked by correct password. pam_faillock use is the recommended fix Status in pam package in Ubuntu: Confirmed Status in pam source package in Bionic: New Status in pam source package in Focal: New Status in pam source package in Groovy: New Status in pam source package in Hirsute: New Status in pam source package in Impish: Confirmed Bug description: [IMPACT] There is a known issue in pam_tally2 which may cause an account to be lock down even with correct password, in a busy node environment where simultaneous logins takes place (https://github.com/linux-pam/linux-pam/issues/71). There are already two customer cases from Canonical clients complaining about this behavior (00297697 and 00303806). Also, potentially, this will cause further problems in the future, since both STIG benchmarks and CIS benchmarks rely on pam_tally2 to lock accounts when wrong passwords are used. And both benchmarks - but specially STIG - requires use of a lot of audit rules, which can lead to the busy node environment. The issue impacts all pam_tally2 versions distributed in all currently supported Ubuntu versions and also the next unreleased one. Note that, according to https://github.com/linux-pam/linux-pam/issues/71, there is no plan to fix this issue! [FIX] This fix proposes to add pam_faillock module to the PAM package, so users of pam_tally2 having issues can migrate to pam_faillock. We also plan to modify the current STIG benchmarks to rely on pam_faillock instead of pam_tally2, but in order to do so, we need the pam_faillock module to be available. Note that we don't propose to remove pam_tally2, since not every user of this module is affected. [TEST] Tested on a VM installed with Focal server iso and on another with Bionic server iso. Enabled pam_faillock module as recommeded by its man page. Then tried to log over ssh with an incorrect password, until the account got locked. Waited for the configured grace time to unlock and logged in using the correct password. Note that, since the pam_tally2 issue is caused by a racing condition, with a hard to recreate environment (we could not even reproduce it with pam_tally2), we could not reproduce the conditions to test pam_faillock with. [REGRESSION POTENTIAL] The regression potential for this is small, since we're not removing the old pam_tally2 module, just adding another one. So anyone still using pam_tally2 will be able to do so. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1927796/+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 1927796] Re: [SRU]pam_tally2 can cause accounts to be locked by correct password. pam_faillock use is the recommended fix
** Patch added: "Groovy debdiff" https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1927796/+attachment/5496424/+files/pam_1.3.1-5ubuntu6.20.10.1.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1927796 Title: [SRU]pam_tally2 can cause accounts to be locked by correct password. pam_faillock use is the recommended fix Status in pam package in Ubuntu: Confirmed Status in pam source package in Bionic: New Status in pam source package in Focal: New Status in pam source package in Groovy: New Status in pam source package in Hirsute: New Status in pam source package in Impish: Confirmed Bug description: [IMPACT] There is a known issue in pam_tally2 which may cause an account to be lock down even with correct password, in a busy node environment where simultaneous logins takes place (https://github.com/linux-pam/linux-pam/issues/71). There are already two customer cases from Canonical clients complaining about this behavior (00297697 and 00303806). Also, potentially, this will cause further problems in the future, since both STIG benchmarks and CIS benchmarks rely on pam_tally2 to lock accounts when wrong passwords are used. And both benchmarks - but specially STIG - requires use of a lot of audit rules, which can lead to the busy node environment. The issue impacts all pam_tally2 versions distributed in all currently supported Ubuntu versions and also the next unreleased one. Note that, according to https://github.com/linux-pam/linux-pam/issues/71, there is no plan to fix this issue! [FIX] This fix proposes to add pam_faillock module to the PAM package, so users of pam_tally2 having issues can migrate to pam_faillock. We also plan to modify the current STIG benchmarks to rely on pam_faillock instead of pam_tally2, but in order to do so, we need the pam_faillock module to be available. Note that we don't propose to remove pam_tally2, since not every user of this module is affected. [TEST] Tested on a VM installed with Focal server iso and on another with Bionic server iso. Enabled pam_faillock module as recommeded by its man page. Then tried to log over ssh with an incorrect password, until the account got locked. Waited for the configured grace time to unlock and logged in using the correct password. Note that, since the pam_tally2 issue is caused by a racing condition, with a hard to recreate environment (we could not even reproduce it with pam_tally2), we could not reproduce the conditions to test pam_faillock with. [REGRESSION POTENTIAL] The regression potential for this is small, since we're not removing the old pam_tally2 module, just adding another one. So anyone still using pam_tally2 will be able to do so. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1927796/+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 1925379] Re: Auto-Correct in LibreOffice does not work with 3.24.25-1ubuntu4
This bug report is missing SRU information as described here: https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template Additionally, the version number 3.24.25-1ubuntu5 isn't great as if there is another SRU of gtk+3.0 it'd be version 3.24.25-1ubuntu5.1 (because 3.24.25-1ubuntu6 is in Impish). Subsequently, I'm going to reject this and reupload it as 3.24-25-1ubuntu4.1. -- 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/1925379 Title: Auto-Correct in LibreOffice does not work with 3.24.25-1ubuntu4 Status in gtk+3.0 package in Ubuntu: Fix Released Status in gtk+3.0 source package in Hirsute: In Progress Bug description: I just did a fresh install of Ubuntu 21.04 (smooth as silk), but then discovered that Auto-Correct in LibreOffice does not work. Yesterday, when I was still running 20.04, Auto-Correct worked fine -- same LibreOffice version, same LibreOffice profile, same LibreOffice document, and no changes on my part to my LibreOffice settings since I installed Ubuntu 21.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1925379/+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 1927796] Re: [SRU]pam_tally2 can cause accounts to be locked by correct password. pam_faillock use is the recommended fix
I have uploaded packages for processing by the SRU team. ** Changed in: pam (Ubuntu Bionic) Status: New => In Progress ** Changed in: pam (Ubuntu Focal) Status: New => In Progress ** Changed in: pam (Ubuntu Groovy) Status: New => In Progress ** Changed in: pam (Ubuntu Hirsute) Status: New => In Progress ** Changed in: pam (Ubuntu Impish) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1927796 Title: [SRU]pam_tally2 can cause accounts to be locked by correct password. pam_faillock use is the recommended fix Status in pam package in Ubuntu: Fix Committed Status in pam source package in Bionic: In Progress Status in pam source package in Focal: In Progress Status in pam source package in Groovy: In Progress Status in pam source package in Hirsute: In Progress Status in pam source package in Impish: Fix Committed Bug description: [IMPACT] There is a known issue in pam_tally2 which may cause an account to be lock down even with correct password, in a busy node environment where simultaneous logins takes place (https://github.com/linux-pam/linux-pam/issues/71). There are already two customer cases from Canonical clients complaining about this behavior (00297697 and 00303806). Also, potentially, this will cause further problems in the future, since both STIG benchmarks and CIS benchmarks rely on pam_tally2 to lock accounts when wrong passwords are used. And both benchmarks - but specially STIG - requires use of a lot of audit rules, which can lead to the busy node environment. The issue impacts all pam_tally2 versions distributed in all currently supported Ubuntu versions and also the next unreleased one. Note that, according to https://github.com/linux-pam/linux-pam/issues/71, there is no plan to fix this issue! [FIX] This fix proposes to add pam_faillock module to the PAM package, so users of pam_tally2 having issues can migrate to pam_faillock. We also plan to modify the current STIG benchmarks to rely on pam_faillock instead of pam_tally2, but in order to do so, we need the pam_faillock module to be available. Note that we don't propose to remove pam_tally2, since not every user of this module is affected. [TEST] Tested on a VM installed with Focal server iso and on another with Bionic server iso. Enabled pam_faillock module as recommeded by its man page. Then tried to log over ssh with an incorrect password, until the account got locked. Waited for the configured grace time to unlock and logged in using the correct password. Note that, since the pam_tally2 issue is caused by a racing condition, with a hard to recreate environment (we could not even reproduce it with pam_tally2), we could not reproduce the conditions to test pam_faillock with. [REGRESSION POTENTIAL] The regression potential for this is small, since we're not removing the old pam_tally2 module, just adding another one. So anyone still using pam_tally2 will be able to do so. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1927796/+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 1926843] Re: online accounts integration with fb isn't working
Hello Lars, or anyone else affected, Accepted gnome-online-accounts into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /gnome-online-accounts/3.38.1-1ubuntu1.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- hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. 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: gnome-online-accounts (Ubuntu Hirsute) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-hirsute -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1926843 Title: online accounts integration with fb isn't working Status in gnome-online-accounts package in Ubuntu: Fix Released Status in gnome-online-accounts source package in Hirsute: Fix Committed Bug description: * Impact The online accounts setting are proposing a facebook item which isn't working * Test case Go to settings -> online account, browse the accounts option proposed, facebook shouldn't be in the list since it doesn't work. * Regression potential The change is to disable the facebook provider using the upstream provided build option. Check that facebook isn't listed anymore but that the other providers still are. Since it's a build option change it could fail to build so check for that as well on launchpad. Since the facebook service currently doesn't consider gnome-online- accounts as a valid client there should be no user with that provider configured. Even if there were since the service isn't working they would see a functional regression. --- Hi i tryed to use gnome-control-center online-accounts to make easy like windows 10 to login to email or add other login so its more easy with ID to use pincode or other ID fingerprint and other. But its look its much issue compared with windows 10 with thunderbird, firefox, and other program. Worst is facebook only little windows with issue with login? ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-online-accounts 3.38.1-1ubuntu1 Uname: Linux 5.12.0-051200-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat May 1 19:38:03 2021 InstallationDate: Installed on 2019-05-07 (725 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gnome-online-accounts UpgradeStatus: Upgraded to hirsute on 2021-04-06 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1926843/+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 1926843] Please test proposed package
Hello Lars, or anyone else affected, Accepted gnome-online-accounts into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /gnome-online-accounts/3.38.1-1ubuntu1.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- hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. 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. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1926843 Title: online accounts integration with fb isn't working Status in gnome-online-accounts package in Ubuntu: Fix Released Status in gnome-online-accounts source package in Hirsute: Fix Committed Bug description: * Impact The online accounts setting are proposing a facebook item which isn't working * Test case Go to settings -> online account, browse the accounts option proposed, facebook shouldn't be in the list since it doesn't work. * Regression potential The change is to disable the facebook provider using the upstream provided build option. Check that facebook isn't listed anymore but that the other providers still are. Since it's a build option change it could fail to build so check for that as well on launchpad. Since the facebook service currently doesn't consider gnome-online- accounts as a valid client there should be no user with that provider configured. Even if there were since the service isn't working they would see a functional regression. --- Hi i tryed to use gnome-control-center online-accounts to make easy like windows 10 to login to email or add other login so its more easy with ID to use pincode or other ID fingerprint and other. But its look its much issue compared with windows 10 with thunderbird, firefox, and other program. Worst is facebook only little windows with issue with login? ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-online-accounts 3.38.1-1ubuntu1 Uname: Linux 5.12.0-051200-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat May 1 19:38:03 2021 InstallationDate: Installed on 2019-05-07 (725 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gnome-online-accounts UpgradeStatus: Upgraded to hirsute on 2021-04-06 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1926843/+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 1928001] Re: [SRU] New stable release 2.68.1
Hello Iain, or anyone else affected, Accepted glib2.0 into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/glib2.0/2.68.1-1~ubuntu21.04.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- hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. 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: glib2.0 (Ubuntu Hirsute) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-hirsute -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1928001 Title: [SRU] New stable release 2.68.1 Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Hirsute: Fix Committed Bug description: [ Description ] Take this new upstream stable release. * Fix a crash in `GKeyFile` when parsing a file which contains translations using a `GKeyFile` instance which has loaded another file previously (#2361) * Pin GIO DLL in memory on Windows (!2016) * Bugs fixed: - #2361 g_key_file_load_from_file segfaults on "Key[*]="like lines - !1997 Backport !1996 “Include glibconfig.h to get the G_OS_UNIX token” to glib-2-68 - !2016 GIO W32: Pin gio DLL - !2021 Backport MR !2016 (GIO W32: Pin gio DLL) into glib-2-68 - !2022 Few fixes and notes for building on Visual Studio 2012 and earlier - !2034 Backport MR !2032 (gkeyfile: Drop a redundant check) into glib-2-68 - !2035 Backport !2026 “Split g_test_log() messages that contain multiple lines” to glib-2-68 [ QA ] Upstream release, so QA already performed by maintainers https://wiki.ubuntu.com/StableReleaseUpdates/GNOME This upload will trigger many autopkgtests that we expect to not be regressed by this upload. [ What could go wrong ] This update contains fixes in multiple places so multiple apps could be affected. The consequences of a broken GLib can range from some functions returning bad results sometimes, which have minimal runtime implications, up to the system simply crashing all the time. Pretty much all parts of GNOME use GLib, so test anything in the desktop that you can. If you reboot the machine and can get to the desktop, that's already tested GLib extensively. But also run applications like GNOME terminal, Files and Epiphany. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1928001/+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 1928001] Please test proposed package
Hello Iain, or anyone else affected, Accepted glib2.0 into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/glib2.0/2.68.1-1~ubuntu21.04.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- hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. 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. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1928001 Title: [SRU] New stable release 2.68.1 Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Hirsute: Fix Committed Bug description: [ Description ] Take this new upstream stable release. * Fix a crash in `GKeyFile` when parsing a file which contains translations using a `GKeyFile` instance which has loaded another file previously (#2361) * Pin GIO DLL in memory on Windows (!2016) * Bugs fixed: - #2361 g_key_file_load_from_file segfaults on "Key[*]="like lines - !1997 Backport !1996 “Include glibconfig.h to get the G_OS_UNIX token” to glib-2-68 - !2016 GIO W32: Pin gio DLL - !2021 Backport MR !2016 (GIO W32: Pin gio DLL) into glib-2-68 - !2022 Few fixes and notes for building on Visual Studio 2012 and earlier - !2034 Backport MR !2032 (gkeyfile: Drop a redundant check) into glib-2-68 - !2035 Backport !2026 “Split g_test_log() messages that contain multiple lines” to glib-2-68 [ QA ] Upstream release, so QA already performed by maintainers https://wiki.ubuntu.com/StableReleaseUpdates/GNOME This upload will trigger many autopkgtests that we expect to not be regressed by this upload. [ What could go wrong ] This update contains fixes in multiple places so multiple apps could be affected. The consequences of a broken GLib can range from some functions returning bad results sometimes, which have minimal runtime implications, up to the system simply crashing all the time. Pretty much all parts of GNOME use GLib, so test anything in the desktop that you can. If you reboot the machine and can get to the desktop, that's already tested GLib extensively. But also run applications like GNOME terminal, Files and Epiphany. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1928001/+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 1926843] Autopkgtest regression report (gnome-online-accounts/3.38.1-1ubuntu1.1)
All autopkgtests for the newly accepted gnome-online-accounts (3.38.1-1ubuntu1.1) for hirsute have finished running. The following regressions have been reported in tests triggered by the package: libgdata/0.18.1-1 (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/hirsute/update_excuses.html#gnome-online-accounts [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 gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1926843 Title: online accounts integration with fb isn't working Status in gnome-online-accounts package in Ubuntu: Fix Released Status in gnome-online-accounts source package in Hirsute: Fix Committed Bug description: * Impact The online accounts setting are proposing a facebook item which isn't working * Test case Go to settings -> online account, browse the accounts option proposed, facebook shouldn't be in the list since it doesn't work. * Regression potential The change is to disable the facebook provider using the upstream provided build option. Check that facebook isn't listed anymore but that the other providers still are. Since it's a build option change it could fail to build so check for that as well on launchpad. Since the facebook service currently doesn't consider gnome-online- accounts as a valid client there should be no user with that provider configured. Even if there were since the service isn't working they would see a functional regression. --- Hi i tryed to use gnome-control-center online-accounts to make easy like windows 10 to login to email or add other login so its more easy with ID to use pincode or other ID fingerprint and other. But its look its much issue compared with windows 10 with thunderbird, firefox, and other program. Worst is facebook only little windows with issue with login? ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-online-accounts 3.38.1-1ubuntu1 Uname: Linux 5.12.0-051200-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat May 1 19:38:03 2021 InstallationDate: Installed on 2019-05-07 (725 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gnome-online-accounts UpgradeStatus: Upgraded to hirsute on 2021-04-06 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1926843/+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 1876570] Please test proposed package
Hello Rasmus, or anyone else affected, Accepted initramfs-tools into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/initramfs- tools/0.137ubuntu12.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- groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-groovy. 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: initramfs-tools (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1876570 Title: Could not resume from hibernation when swap is specified as device Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: In Progress Status in initramfs-tools source package in Focal: Fix Committed Status in initramfs-tools source package in Groovy: Fix Committed Status in initramfs-tools source package in Hirsute: Fix Released Bug description: [impact] unable to resume from hibernation when resume= boot param is specified as device path [test case] set up device/partition for swap, e.g. /dev/vda2 add 'resume=/dev/vda2' kernel boot parameter hibernate power system back on; it should resume from /dev/vda2 instead of coldboot [regression potential] any regression would likely result in failure to correctly resume from hibernation, incorrectly attempting to resume from hibernation, or failing to resume from hibernation. [scope] this is needed in b/f/g/h this bug was introduced, ironically, by bug 1644975, which was added in bionic, so this bug doesn't exist in xenial. this code that introduced this bug isn't included in Debian, so no change is needed there. [original description] I originally experienced this on Pop!_OS but I have reproduced it on a freshly installed Ubuntu. 1. Ubuntu 20.04 LTS 2. initramfs-tools-core 0.136ubuntu6 3. I expect the system to resume from hibernation when running pm_hibernate 4. The system starts up anew when I try to resume I have setup a swap partition on /dev/vda2 in /etc/fstab. To enable hibernate I added the kernel parameter "resume=/dev/vda2" to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub and run update-grub. From debugging initramfs it tries to follow a symbolic link DEV=$(readlink "$resume") (see /usr/share/initramfs-tools/scripts/local-premount/resume, line 35) which works well when swap is specified with uuid. When swap is specified as a device directly the readlink returns an empty string and the system does not resume from hibernation. To verify this I added the parameter -f to readlink and run "update- initramfs -u". The system now hibernates successfully. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 3 13:26:02 2020 InstallationDate: Installed on 2020-05-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1876570/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1927779] Please test proposed package
Hello Dan, or anyone else affected, Accepted initramfs-tools into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/initramfs- tools/0.136ubuntu6.5 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. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1927779 Title: MODULES=list results in error Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: Invalid Status in initramfs-tools source package in Focal: Fix Committed Status in initramfs-tools source package in Groovy: Fix Committed Bug description: [impact] setting MODULES=list in /etc/initramfs-tools/initramfs.conf results in an error/warning when running update-initramfs [test case] edit initramfs.conf to change MODULES=list and run update-initramfs: $ grep MODULES /etc/initramfs-tools/initramfs.conf # MODULES: [ most | netboot | dep | list ] MODULES=list $ sudo update-initramfs -u update-initramfs: Generating /boot/initrd.img-5.8.0-48-generic find: ‘/var/tmp/mkinitramfs_Yr04uh/lib/modules/5.8.0-48-generic/kernel’: No such file or directory [regression potential] any regression would likely result in an initramfs that did not include the correct/required modules, and/or failure to build a new initramfs [scope] this is needed for f and g. this is not fixed in debian, but is fixed in h and i. the code in b is different and doesn't include this bug, so this doesn't apply to b. for debian, MR open: https://salsa.debian.org/kernel-team/initramfs-tools/-/merge_requests/48 [other info] this caused some of the 'amd64-*' autopkgtests to fail in h until it was fixed. those autopkgtests don't exist in g and earlier so this was not noticed until now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1927779/+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 1876570] Please test proposed package
Hello Rasmus, or anyone else affected, Accepted initramfs-tools into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/initramfs- tools/0.136ubuntu6.5 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. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1876570 Title: Could not resume from hibernation when swap is specified as device Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: In Progress Status in initramfs-tools source package in Focal: Fix Committed Status in initramfs-tools source package in Groovy: Fix Committed Status in initramfs-tools source package in Hirsute: Fix Released Bug description: [impact] unable to resume from hibernation when resume= boot param is specified as device path [test case] set up device/partition for swap, e.g. /dev/vda2 add 'resume=/dev/vda2' kernel boot parameter hibernate power system back on; it should resume from /dev/vda2 instead of coldboot [regression potential] any regression would likely result in failure to correctly resume from hibernation, incorrectly attempting to resume from hibernation, or failing to resume from hibernation. [scope] this is needed in b/f/g/h this bug was introduced, ironically, by bug 1644975, which was added in bionic, so this bug doesn't exist in xenial. this code that introduced this bug isn't included in Debian, so no change is needed there. [original description] I originally experienced this on Pop!_OS but I have reproduced it on a freshly installed Ubuntu. 1. Ubuntu 20.04 LTS 2. initramfs-tools-core 0.136ubuntu6 3. I expect the system to resume from hibernation when running pm_hibernate 4. The system starts up anew when I try to resume I have setup a swap partition on /dev/vda2 in /etc/fstab. To enable hibernate I added the kernel parameter "resume=/dev/vda2" to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub and run update-grub. From debugging initramfs it tries to follow a symbolic link DEV=$(readlink "$resume") (see /usr/share/initramfs-tools/scripts/local-premount/resume, line 35) which works well when swap is specified with uuid. When swap is specified as a device directly the readlink returns an empty string and the system does not resume from hibernation. To verify this I added the parameter -f to readlink and run "update- initramfs -u". The system now hibernates successfully. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 3 13:26:02 2020 InstallationDate: Installed on 2020-05-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1876570/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1917780] Please test proposed package
Hello Ioanna, or anyone else affected, Accepted initramfs-tools into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/initramfs- tools/0.136ubuntu6.5 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. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1917780 Title: initramfs-tools does not include fsck binaries in the initrd if all mount pass are 0 Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: In Progress Status in initramfs-tools source package in Focal: Fix Committed Status in initramfs-tools source package in Groovy: Fix Committed Bug description: [Impact] * initramfs-tools does not include fsck in initrd if MNT_PASS equals zero in the fstab entries. This has lead to the following situation : when dropping to initramfs shell during boot due to fs errors, we are not able to run fsck manually because it is not included in initrd. fsck should be included regardless of the MNT_PASS value. [Test Plan] * change /etc/fstab with PASSNO set to 0 for all entries * update-initramfs -u * lsinitramfs that is just generated * observe that it includes fsck utilities for the filesystems in /etc/fstab. I.e. fsck.ext4 e2fsck must exist [Where problems could occur] * The initramfs size will increase slightly upon upgrade, for the same initramfs-tools default options & kernel. However, one can control and remove fsck binaries (or include more of them) by setting FSTYPE variable in the initramfs settings. [scope] this is required for b/f/g this is fixed already in h and i [other info] debian MR is open: https://salsa.debian.org/kernel-team/initramfs-tools/-/merge_requests/49 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1917780/+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 1917780] Please test proposed package
Hello Ioanna, or anyone else affected, Accepted initramfs-tools into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/initramfs- tools/0.136ubuntu6.5 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. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1917780 Title: initramfs-tools does not include fsck binaries in the initrd if all mount pass are 0 Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: In Progress Status in initramfs-tools source package in Focal: Fix Committed Status in initramfs-tools source package in Groovy: Fix Committed Bug description: [Impact] * initramfs-tools does not include fsck in initrd if MNT_PASS equals zero in the fstab entries. This has lead to the following situation : when dropping to initramfs shell during boot due to fs errors, we are not able to run fsck manually because it is not included in initrd. fsck should be included regardless of the MNT_PASS value. [Test Plan] * change /etc/fstab with PASSNO set to 0 for all entries * update-initramfs -u * lsinitramfs that is just generated * observe that it includes fsck utilities for the filesystems in /etc/fstab. I.e. fsck.ext4 e2fsck must exist [Where problems could occur] * The initramfs size will increase slightly upon upgrade, for the same initramfs-tools default options & kernel. However, one can control and remove fsck binaries (or include more of them) by setting FSTYPE variable in the initramfs settings. [scope] this is required for b/f/g this is fixed already in h and i [other info] debian MR is open: https://salsa.debian.org/kernel-team/initramfs-tools/-/merge_requests/49 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1917780/+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 1917780] Please test proposed package
Hello Ioanna, or anyone else affected, Accepted initramfs-tools into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/initramfs- tools/0.137ubuntu12.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- groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-groovy. 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: initramfs-tools (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1917780 Title: initramfs-tools does not include fsck binaries in the initrd if all mount pass are 0 Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: In Progress Status in initramfs-tools source package in Focal: Fix Committed Status in initramfs-tools source package in Groovy: Fix Committed Bug description: [Impact] * initramfs-tools does not include fsck in initrd if MNT_PASS equals zero in the fstab entries. This has lead to the following situation : when dropping to initramfs shell during boot due to fs errors, we are not able to run fsck manually because it is not included in initrd. fsck should be included regardless of the MNT_PASS value. [Test Plan] * change /etc/fstab with PASSNO set to 0 for all entries * update-initramfs -u * lsinitramfs that is just generated * observe that it includes fsck utilities for the filesystems in /etc/fstab. I.e. fsck.ext4 e2fsck must exist [Where problems could occur] * The initramfs size will increase slightly upon upgrade, for the same initramfs-tools default options & kernel. However, one can control and remove fsck binaries (or include more of them) by setting FSTYPE variable in the initramfs settings. [scope] this is required for b/f/g this is fixed already in h and i [other info] debian MR is open: https://salsa.debian.org/kernel-team/initramfs-tools/-/merge_requests/49 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1917780/+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 1927779] Re: MODULES=list results in error
Hello Dan, or anyone else affected, Accepted initramfs-tools into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/initramfs- tools/0.137ubuntu12.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- groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-groovy. 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: initramfs-tools (Ubuntu Groovy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-groovy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1927779 Title: MODULES=list results in error Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: Invalid Status in initramfs-tools source package in Focal: Fix Committed Status in initramfs-tools source package in Groovy: Fix Committed Bug description: [impact] setting MODULES=list in /etc/initramfs-tools/initramfs.conf results in an error/warning when running update-initramfs [test case] edit initramfs.conf to change MODULES=list and run update-initramfs: $ grep MODULES /etc/initramfs-tools/initramfs.conf # MODULES: [ most | netboot | dep | list ] MODULES=list $ sudo update-initramfs -u update-initramfs: Generating /boot/initrd.img-5.8.0-48-generic find: ‘/var/tmp/mkinitramfs_Yr04uh/lib/modules/5.8.0-48-generic/kernel’: No such file or directory [regression potential] any regression would likely result in an initramfs that did not include the correct/required modules, and/or failure to build a new initramfs [scope] this is needed for f and g. this is not fixed in debian, but is fixed in h and i. the code in b is different and doesn't include this bug, so this doesn't apply to b. for debian, MR open: https://salsa.debian.org/kernel-team/initramfs-tools/-/merge_requests/48 [other info] this caused some of the 'amd64-*' autopkgtests to fail in h until it was fixed. those autopkgtests don't exist in g and earlier so this was not noticed until now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1927779/+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 1876570] Re: Could not resume from hibernation when swap is specified as device
Hello Rasmus, or anyone else affected, Accepted initramfs-tools into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/initramfs- tools/0.137ubuntu12.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- groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-groovy. 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: initramfs-tools (Ubuntu Groovy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-groovy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1876570 Title: Could not resume from hibernation when swap is specified as device Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: In Progress Status in initramfs-tools source package in Focal: Fix Committed Status in initramfs-tools source package in Groovy: Fix Committed Status in initramfs-tools source package in Hirsute: Fix Released Bug description: [impact] unable to resume from hibernation when resume= boot param is specified as device path [test case] set up device/partition for swap, e.g. /dev/vda2 add 'resume=/dev/vda2' kernel boot parameter hibernate power system back on; it should resume from /dev/vda2 instead of coldboot [regression potential] any regression would likely result in failure to correctly resume from hibernation, incorrectly attempting to resume from hibernation, or failing to resume from hibernation. [scope] this is needed in b/f/g/h this bug was introduced, ironically, by bug 1644975, which was added in bionic, so this bug doesn't exist in xenial. this code that introduced this bug isn't included in Debian, so no change is needed there. [original description] I originally experienced this on Pop!_OS but I have reproduced it on a freshly installed Ubuntu. 1. Ubuntu 20.04 LTS 2. initramfs-tools-core 0.136ubuntu6 3. I expect the system to resume from hibernation when running pm_hibernate 4. The system starts up anew when I try to resume I have setup a swap partition on /dev/vda2 in /etc/fstab. To enable hibernate I added the kernel parameter "resume=/dev/vda2" to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub and run update-grub. From debugging initramfs it tries to follow a symbolic link DEV=$(readlink "$resume") (see /usr/share/initramfs-tools/scripts/local-premount/resume, line 35) which works well when swap is specified with uuid. When swap is specified as a device directly the readlink returns an empty string and the system does not resume from hibernation. To verify this I added the parameter -f to readlink and run "update- initramfs -u". The system now hibernates successfully. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 3 13:26:02 2020 InstallationDate: Installed on 2020-05-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1876570/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1876570] Please test proposed package
Hello Rasmus, or anyone else affected, Accepted initramfs-tools into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/initramfs- tools/0.136ubuntu6.5 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. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1876570 Title: Could not resume from hibernation when swap is specified as device Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: In Progress Status in initramfs-tools source package in Focal: Fix Committed Status in initramfs-tools source package in Groovy: Fix Committed Status in initramfs-tools source package in Hirsute: Fix Released Bug description: [impact] unable to resume from hibernation when resume= boot param is specified as device path [test case] set up device/partition for swap, e.g. /dev/vda2 add 'resume=/dev/vda2' kernel boot parameter hibernate power system back on; it should resume from /dev/vda2 instead of coldboot [regression potential] any regression would likely result in failure to correctly resume from hibernation, incorrectly attempting to resume from hibernation, or failing to resume from hibernation. [scope] this is needed in b/f/g/h this bug was introduced, ironically, by bug 1644975, which was added in bionic, so this bug doesn't exist in xenial. this code that introduced this bug isn't included in Debian, so no change is needed there. [original description] I originally experienced this on Pop!_OS but I have reproduced it on a freshly installed Ubuntu. 1. Ubuntu 20.04 LTS 2. initramfs-tools-core 0.136ubuntu6 3. I expect the system to resume from hibernation when running pm_hibernate 4. The system starts up anew when I try to resume I have setup a swap partition on /dev/vda2 in /etc/fstab. To enable hibernate I added the kernel parameter "resume=/dev/vda2" to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub and run update-grub. From debugging initramfs it tries to follow a symbolic link DEV=$(readlink "$resume") (see /usr/share/initramfs-tools/scripts/local-premount/resume, line 35) which works well when swap is specified with uuid. When swap is specified as a device directly the readlink returns an empty string and the system does not resume from hibernation. To verify this I added the parameter -f to readlink and run "update- initramfs -u". The system now hibernates successfully. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 3 13:26:02 2020 InstallationDate: Installed on 2020-05-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1876570/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1917780] Re: initramfs-tools does not include fsck binaries in the initrd if all mount pass are 0
Hello Ioanna, or anyone else affected, Accepted initramfs-tools into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/initramfs- tools/0.137ubuntu12.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- groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-groovy. 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: initramfs-tools (Ubuntu Groovy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-groovy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1917780 Title: initramfs-tools does not include fsck binaries in the initrd if all mount pass are 0 Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: In Progress Status in initramfs-tools source package in Focal: Fix Committed Status in initramfs-tools source package in Groovy: Fix Committed Bug description: [Impact] * initramfs-tools does not include fsck in initrd if MNT_PASS equals zero in the fstab entries. This has lead to the following situation : when dropping to initramfs shell during boot due to fs errors, we are not able to run fsck manually because it is not included in initrd. fsck should be included regardless of the MNT_PASS value. [Test Plan] * change /etc/fstab with PASSNO set to 0 for all entries * update-initramfs -u * lsinitramfs that is just generated * observe that it includes fsck utilities for the filesystems in /etc/fstab. I.e. fsck.ext4 e2fsck must exist [Where problems could occur] * The initramfs size will increase slightly upon upgrade, for the same initramfs-tools default options & kernel. However, one can control and remove fsck binaries (or include more of them) by setting FSTYPE variable in the initramfs settings. [scope] this is required for b/f/g this is fixed already in h and i [other info] debian MR is open: https://salsa.debian.org/kernel-team/initramfs-tools/-/merge_requests/49 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1917780/+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 1927779] Please test proposed package
Hello Dan, or anyone else affected, Accepted initramfs-tools into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/initramfs- tools/0.137ubuntu12.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- groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-groovy. 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: initramfs-tools (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1927779 Title: MODULES=list results in error Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: Invalid Status in initramfs-tools source package in Focal: Fix Committed Status in initramfs-tools source package in Groovy: Fix Committed Bug description: [impact] setting MODULES=list in /etc/initramfs-tools/initramfs.conf results in an error/warning when running update-initramfs [test case] edit initramfs.conf to change MODULES=list and run update-initramfs: $ grep MODULES /etc/initramfs-tools/initramfs.conf # MODULES: [ most | netboot | dep | list ] MODULES=list $ sudo update-initramfs -u update-initramfs: Generating /boot/initrd.img-5.8.0-48-generic find: ‘/var/tmp/mkinitramfs_Yr04uh/lib/modules/5.8.0-48-generic/kernel’: No such file or directory [regression potential] any regression would likely result in an initramfs that did not include the correct/required modules, and/or failure to build a new initramfs [scope] this is needed for f and g. this is not fixed in debian, but is fixed in h and i. the code in b is different and doesn't include this bug, so this doesn't apply to b. for debian, MR open: https://salsa.debian.org/kernel-team/initramfs-tools/-/merge_requests/48 [other info] this caused some of the 'amd64-*' autopkgtests to fail in h until it was fixed. those autopkgtests don't exist in g and earlier so this was not noticed until now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1927779/+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 1927779] Please test proposed package
Hello Dan, or anyone else affected, Accepted initramfs-tools into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/initramfs- tools/0.136ubuntu6.5 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. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1927779 Title: MODULES=list results in error Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: Invalid Status in initramfs-tools source package in Focal: Fix Committed Status in initramfs-tools source package in Groovy: Fix Committed Bug description: [impact] setting MODULES=list in /etc/initramfs-tools/initramfs.conf results in an error/warning when running update-initramfs [test case] edit initramfs.conf to change MODULES=list and run update-initramfs: $ grep MODULES /etc/initramfs-tools/initramfs.conf # MODULES: [ most | netboot | dep | list ] MODULES=list $ sudo update-initramfs -u update-initramfs: Generating /boot/initrd.img-5.8.0-48-generic find: ‘/var/tmp/mkinitramfs_Yr04uh/lib/modules/5.8.0-48-generic/kernel’: No such file or directory [regression potential] any regression would likely result in an initramfs that did not include the correct/required modules, and/or failure to build a new initramfs [scope] this is needed for f and g. this is not fixed in debian, but is fixed in h and i. the code in b is different and doesn't include this bug, so this doesn't apply to b. for debian, MR open: https://salsa.debian.org/kernel-team/initramfs-tools/-/merge_requests/48 [other info] this caused some of the 'amd64-*' autopkgtests to fail in h until it was fixed. those autopkgtests don't exist in g and earlier so this was not noticed until now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1927779/+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 1917780] Please test proposed package
Hello Ioanna, or anyone else affected, Accepted initramfs-tools into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/initramfs- tools/0.130ubuntu3.12 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- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. 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. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1917780 Title: initramfs-tools does not include fsck binaries in the initrd if all mount pass are 0 Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: Fix Committed Status in initramfs-tools source package in Focal: Fix Committed Status in initramfs-tools source package in Groovy: Fix Committed Bug description: [Impact] * initramfs-tools does not include fsck in initrd if MNT_PASS equals zero in the fstab entries. This has lead to the following situation : when dropping to initramfs shell during boot due to fs errors, we are not able to run fsck manually because it is not included in initrd. fsck should be included regardless of the MNT_PASS value. [Test Plan] * change /etc/fstab with PASSNO set to 0 for all entries * update-initramfs -u * lsinitramfs that is just generated * observe that it includes fsck utilities for the filesystems in /etc/fstab. I.e. fsck.ext4 e2fsck must exist [Where problems could occur] * The initramfs size will increase slightly upon upgrade, for the same initramfs-tools default options & kernel. However, one can control and remove fsck binaries (or include more of them) by setting FSTYPE variable in the initramfs settings. [scope] this is required for b/f/g this is fixed already in h and i [other info] debian MR is open: https://salsa.debian.org/kernel-team/initramfs-tools/-/merge_requests/49 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1917780/+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 1917780] Re: initramfs-tools does not include fsck binaries in the initrd if all mount pass are 0
Hello Ioanna, or anyone else affected, Accepted initramfs-tools into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/initramfs- tools/0.130ubuntu3.12 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- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. 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: initramfs-tools (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1917780 Title: initramfs-tools does not include fsck binaries in the initrd if all mount pass are 0 Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: Fix Committed Status in initramfs-tools source package in Focal: Fix Committed Status in initramfs-tools source package in Groovy: Fix Committed Bug description: [Impact] * initramfs-tools does not include fsck in initrd if MNT_PASS equals zero in the fstab entries. This has lead to the following situation : when dropping to initramfs shell during boot due to fs errors, we are not able to run fsck manually because it is not included in initrd. fsck should be included regardless of the MNT_PASS value. [Test Plan] * change /etc/fstab with PASSNO set to 0 for all entries * update-initramfs -u * lsinitramfs that is just generated * observe that it includes fsck utilities for the filesystems in /etc/fstab. I.e. fsck.ext4 e2fsck must exist [Where problems could occur] * The initramfs size will increase slightly upon upgrade, for the same initramfs-tools default options & kernel. However, one can control and remove fsck binaries (or include more of them) by setting FSTYPE variable in the initramfs settings. [scope] this is required for b/f/g this is fixed already in h and i [other info] debian MR is open: https://salsa.debian.org/kernel-team/initramfs-tools/-/merge_requests/49 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1917780/+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 1876570] Please test proposed package
Hello Rasmus, or anyone else affected, Accepted initramfs-tools into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/initramfs- tools/0.130ubuntu3.12 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- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. 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. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1876570 Title: Could not resume from hibernation when swap is specified as device Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: Fix Committed Status in initramfs-tools source package in Focal: Fix Committed Status in initramfs-tools source package in Groovy: Fix Committed Status in initramfs-tools source package in Hirsute: Fix Released Bug description: [impact] unable to resume from hibernation when resume= boot param is specified as device path [test case] set up device/partition for swap, e.g. /dev/vda2 add 'resume=/dev/vda2' kernel boot parameter hibernate power system back on; it should resume from /dev/vda2 instead of coldboot [regression potential] any regression would likely result in failure to correctly resume from hibernation, incorrectly attempting to resume from hibernation, or failing to resume from hibernation. [scope] this is needed in b/f/g/h this bug was introduced, ironically, by bug 1644975, which was added in bionic, so this bug doesn't exist in xenial. this code that introduced this bug isn't included in Debian, so no change is needed there. [original description] I originally experienced this on Pop!_OS but I have reproduced it on a freshly installed Ubuntu. 1. Ubuntu 20.04 LTS 2. initramfs-tools-core 0.136ubuntu6 3. I expect the system to resume from hibernation when running pm_hibernate 4. The system starts up anew when I try to resume I have setup a swap partition on /dev/vda2 in /etc/fstab. To enable hibernate I added the kernel parameter "resume=/dev/vda2" to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub and run update-grub. From debugging initramfs it tries to follow a symbolic link DEV=$(readlink "$resume") (see /usr/share/initramfs-tools/scripts/local-premount/resume, line 35) which works well when swap is specified with uuid. When swap is specified as a device directly the readlink returns an empty string and the system does not resume from hibernation. To verify this I added the parameter -f to readlink and run "update- initramfs -u". The system now hibernates successfully. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 3 13:26:02 2020 InstallationDate: Installed on 2020-05-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1876570/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1876570] Re: Could not resume from hibernation when swap is specified as device
Hello Rasmus, or anyone else affected, Accepted initramfs-tools into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/initramfs- tools/0.130ubuntu3.12 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- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. 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: initramfs-tools (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1876570 Title: Could not resume from hibernation when swap is specified as device Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: Fix Committed Status in initramfs-tools source package in Focal: Fix Committed Status in initramfs-tools source package in Groovy: Fix Committed Status in initramfs-tools source package in Hirsute: Fix Released Bug description: [impact] unable to resume from hibernation when resume= boot param is specified as device path [test case] set up device/partition for swap, e.g. /dev/vda2 add 'resume=/dev/vda2' kernel boot parameter hibernate power system back on; it should resume from /dev/vda2 instead of coldboot [regression potential] any regression would likely result in failure to correctly resume from hibernation, incorrectly attempting to resume from hibernation, or failing to resume from hibernation. [scope] this is needed in b/f/g/h this bug was introduced, ironically, by bug 1644975, which was added in bionic, so this bug doesn't exist in xenial. this code that introduced this bug isn't included in Debian, so no change is needed there. [original description] I originally experienced this on Pop!_OS but I have reproduced it on a freshly installed Ubuntu. 1. Ubuntu 20.04 LTS 2. initramfs-tools-core 0.136ubuntu6 3. I expect the system to resume from hibernation when running pm_hibernate 4. The system starts up anew when I try to resume I have setup a swap partition on /dev/vda2 in /etc/fstab. To enable hibernate I added the kernel parameter "resume=/dev/vda2" to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub and run update-grub. From debugging initramfs it tries to follow a symbolic link DEV=$(readlink "$resume") (see /usr/share/initramfs-tools/scripts/local-premount/resume, line 35) which works well when swap is specified with uuid. When swap is specified as a device directly the readlink returns an empty string and the system does not resume from hibernation. To verify this I added the parameter -f to readlink and run "update- initramfs -u". The system now hibernates successfully. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 3 13:26:02 2020 InstallationDate: Installed on 2020-05-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1876570/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1571506] Re: update-initramfs should include firmware from /lib/firmware/updates
Hello Qiang, or anyone else affected, Accepted initramfs-tools into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/initramfs- tools/0.130ubuntu3.12 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- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. 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: initramfs-tools (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags removed: verification-done ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1571506 Title: update-initramfs should include firmware from /lib/firmware/updates Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: Fix Committed Status in initramfs-tools source package in Focal: Fix Released Status in initramfs-tools source package in Groovy: Fix Released Status in initramfs-tools source package in Hirsute: Fix Released Bug description: [Impact] * Firmware files under /lib/firmware/updates would not be processed when running update-initramfs * The kernel org specifies that this is a location where firmware can be stored, so we should search there [Test Case] * Stage some firmware under /lib/firmware/updates * Run update-initramfs and ensure that the firmware in /lib/firmware/updates is found and included in the initramfs [Where problems could occur] * Since dpkg places no files in /lib/firmware/updates, we could end up picking up firmware changes that we did not intend [Other info] * This change already exists in groovy and beyond. It was pulled in when initramfs-tools version 0.137 was merged from Debian according to the kernel doc http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/firmware_class/README Linux kernel will search firmware from "/lib/firmware/updates/" UTS_RELEASE, "/lib/firmware/updates", "/lib/firmware/" UTS_RELEASE, "/lib/firmware" But the add module function in initramfs-tools won't search the "/lib/firmware/updates". This problem applies to all Ubuntu releases. Attach patch to fix this. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: initramfs-tools 0.103ubuntu4.2 ProcVersionSignature: Ubuntu 4.2.0-30.36~14.04.1-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic i686 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: i386 CurrentDesktop: Unity Date: Mon Apr 18 14:24:29 2016 InstallationDate: Installed on 2014-04-23 (725 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1571506/+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 1571506] Please test proposed package
Hello Qiang, or anyone else affected, Accepted initramfs-tools into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/initramfs- tools/0.130ubuntu3.12 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- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. 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. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1571506 Title: update-initramfs should include firmware from /lib/firmware/updates Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: Fix Committed Status in initramfs-tools source package in Focal: Fix Released Status in initramfs-tools source package in Groovy: Fix Released Status in initramfs-tools source package in Hirsute: Fix Released Bug description: [Impact] * Firmware files under /lib/firmware/updates would not be processed when running update-initramfs * The kernel org specifies that this is a location where firmware can be stored, so we should search there [Test Case] * Stage some firmware under /lib/firmware/updates * Run update-initramfs and ensure that the firmware in /lib/firmware/updates is found and included in the initramfs [Where problems could occur] * Since dpkg places no files in /lib/firmware/updates, we could end up picking up firmware changes that we did not intend [Other info] * This change already exists in groovy and beyond. It was pulled in when initramfs-tools version 0.137 was merged from Debian according to the kernel doc http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/firmware_class/README Linux kernel will search firmware from "/lib/firmware/updates/" UTS_RELEASE, "/lib/firmware/updates", "/lib/firmware/" UTS_RELEASE, "/lib/firmware" But the add module function in initramfs-tools won't search the "/lib/firmware/updates". This problem applies to all Ubuntu releases. Attach patch to fix this. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: initramfs-tools 0.103ubuntu4.2 ProcVersionSignature: Ubuntu 4.2.0-30.36~14.04.1-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic i686 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: i386 CurrentDesktop: Unity Date: Mon Apr 18 14:24:29 2016 InstallationDate: Installed on 2014-04-23 (725 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1571506/+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 1925742] Missing SRU information
Thanks for uploading the fix for this bug report to -proposed. However, when reviewing the package in -proposed and the details of this bug report I noticed that the bug description is missing information required for the SRU process. You can find full details at http://wiki.ubuntu.com/StableReleaseUpdates#Procedure but essentially this bug is missing some of the following: a statement of impact, a test case and details regarding where problems may occur. Thanks in advance! -- 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/1925742 Title: Recent iCloud versions trigger an issue in IMAP x Status in evolution-data-server package in Ubuntu: Fix Released Bug description: There is a recently introduced bug in evolution-data-server which broke access to email in iCloud. The bug has been fixed yesterday by Evolution's developer: https://gitlab.gnome.org/GNOME/evolution/-/issues/1468 However, the package in Ubuntu (at least in Focal Fosa) still needs to be updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1925742/+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 1926254] Re: x509 Certificate verification fails when basicConstraints=CA:FALSE, pathlen:0 on self-signed leaf certs
Performing verification for Focal Generating the ssl certificates, and reproducing the problem with version 1.1.1f-1ubuntu2.3 from -updates. ubuntu@select-lobster:~$ sudo apt-cache policy openssl | grep Installed Installed: 1.1.1f-1ubuntu2.3 ubuntu@select-lobster:~$ mkdir reproducer ubuntu@select-lobster:~$ cd reproducer ubuntu@select-lobster:~/reproducer$ mkdir CA ubuntu@select-lobster:~/reproducer$ cat << EOF >> rootCA.cnf > [ req ] > prompt = no > distinguished_name = req_distinguished_name > x509_extensions = usr_cert > > [ req_distinguished_name ] > C = DE > O = Test Org > CN = Test RSA PSS Root-CA > > [ usr_cert ] > basicConstraints = critical,CA:TRUE > keyUsage = critical,keyCertSign,cRLSign > subjectKeyIdentifier = hash > authorityKeyIdentifier = keyid:always > EOF ubuntu@select-lobster:~/reproducer$ cat << EOF >> subCA.cnf > [ req ] > prompt = no > distinguished_name = req_distinguished_name > x509_extensions = usr_cert > > [ req_distinguished_name ] > C = DE > O = Test Org > CN = Test RSA PSS Sub-CA > > [ usr_cert ] > basicConstraints = critical,CA:TRUE,pathlen:0 > keyUsage = critical,keyCertSign,cRLSign > subjectKeyIdentifier = hash > authorityKeyIdentifier = keyid:always > EOF ubuntu@select-lobster:~/reproducer$ cat << EOF >> user.cnf > [ req ] > prompt = no > distinguished_name = req_distinguished_name > x509_extensions = usr_cert > > [ req_distinguished_name ] > C = DE > O = Test Org > CN = Test User > > [ usr_cert ] > basicConstraints = critical,CA:FALSE,pathlen:0 > keyUsage = critical,digitalSignature,keyAgreement > extendedKeyUsage = clientAuth,serverAuth > subjectKeyIdentifier = hash > authorityKeyIdentifier = keyid:always > EOF ubuntu@select-lobster:~/reproducer$ openssl genpkey -algorithm RSA-PSS -out rootCA_key.pem -pkeyopt rsa_keygen_bits:2048 ..+ + ubuntu@select-lobster:~/reproducer$ openssl req -config rootCA.cnf -set_serial 01 -new -batch -sha256 -nodes -x509 -days 9125 -out CA/rootCA_cert.pem -key rootCA_key.pem -sigopt rsa_padding_mode:pss -sigopt rsa_pss_saltlen:-1 ubuntu@select-lobster:~/reproducer$ openssl genpkey -algorithm RSA-PSS -out subCA_key.pem -pkeyopt rsa_keygen_bits:2048 + + ubuntu@select-lobster:~/reproducer$ openssl req -config subCA.cnf -new -out subCA_req.pem -key subCA_key.pem -sigopt rsa_padding_mode:pss -sigopt rsa_pss_saltlen:-1 ubuntu@select-lobster:~/reproducer$ openssl x509 -req -sha256 -in subCA_req.pem -CA CA/rootCA_cert.pem -CAkey rootCA_key.pem -out CA/subCA_cert.pem -CAserial rootCA_serial.txt -CAcreateserial -extfile subCA.cnf -extensions usr_cert -days 4380 -sigopt rsa_padding_mode:pss -sigopt rsa_pss_saltlen:-1 Signature ok subject=C = DE, O = Test Org, CN = Test RSA PSS Sub-CA Getting CA Private Key ubuntu@select-lobster:~/reproducer$ c_rehash CA Doing CA ubuntu@select-lobster:~/reproducer$ openssl genpkey -algorithm RSA-PSS -out user1_key.pem -pkeyopt rsa_keygen_bits:2048 ...+ .+ ubuntu@select-lobster:~/reproducer$ openssl req -config user.cnf -new -out user1_req.pem -key user1_key.pem -sigopt rsa_padding_mode:pss -sigopt rsa_pss_saltlen:-1 ubuntu@select-lobster:~/reproducer$ openssl x509 -req -sha256 -in user1_req.pem -CA CA/subCA_cert.pem -CAkey subCA_key.pem -out user1_cert.pem -CAserial subCA_serial.txt -CAcreateserial -extfile user.cnf -extensions usr_cert -days 1825 -sigopt rsa_padding_mode:pss -sigopt rsa_pss_saltlen:-1 Signature ok subject=C = DE, O = Test Org, CN = Test User Getting CA Private Key Now, we verify the certificates: ubuntu@select-lobster:~/reproducer$ openssl verify -CAfile CA/rootCA_cert.pem -untrusted CA/subCA_cert.pem user1_cert.pem C = DE, O = Test Org, CN = Test User error 20 at 0 depth lookup: unable to get local issuer certificate error user1_cert.pem: verification failed We see verification fail, due to CA:FALSE,pathlen:0 basicConstraints. I then enabled -proposed, and installed openssl and libssl1.1 version 1.1.1f-1ubuntu2.4 If we then repeat the certificate validation: ubuntu@select-lobster:~/reproducer$ openssl verify -CAfile CA/rootCA_cert.pem -untrusted CA/subCA_cert.pem user1_cert.pem user1_cert.pem: OK The certificates validate properly. Additionally, if we examine the new unit tests added to openssl's testsuite in the buildlog for focal: https://launchpadlibrarian.net/537505620/buildlog_ubuntu-focal- amd64.openssl_1.1.1f-1ubuntu2.4_BUILDING.txt.gz we see: ../../../test/certs/ee-pathlen.pem: OK ../../util/shlib_wrap.sh ../../apps/openssl verify -auth_level 1 -purpose sslserver -trusted ../../../test/certs/root-cert.pem -untrusted ../../../test/certs/ca-cert.pem ../../../test/certs/ee-pathlen.pem => 0 ok 84 - accept non-ca with pathlen:0 by default CN = server.example error 41 at 0 depth lookup: invalid or inconsistent certificate extension error ../../../test/certs/ee-pathlen.pem: verification failed ../../util/shlib_wrap.sh ../../apps/openssl verify -auth_level 1
[Touch-packages] [Bug 1928082] Re: the minimize display freezes
Thanks for the bug report. Next time the freeze happens, please: 1. Wait 10 seconds. 2. Reboot. 3. Run: journalctl -b-1 > prevboot.txt 4. Attach the resulting text file here. 5. Also check for crashes using these instructions: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1928082 Title: the minimize display freezes Status in gnome-shell package in Ubuntu: Incomplete Bug description: the display freezes when i try minimizing after a very long use time ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 11 13:09:28 2021 DistUpgraded: 2021-04-26 11:56:19,497 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-io-error-quark: Failed to execute child process “./xorg_fix_proprietary.py”: Failed to execve: No such file or directory (1)) DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.18, 5.11.0-16-generic, x86_64: installed virtualbox, 6.1.18, 5.8.0-50-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f3] InstallationDate: Installed on 2019-06-10 (701 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 23445HU ProcEnviron: LANGUAGE=en_NG:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NG SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=65bd11b5-874d-460b-8539-b2b68af2927a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to hirsute on 2021-04-26 (15 days ago) dmi.bios.date: 03/06/2014 dmi.bios.release: 2.64 dmi.bios.vendor: LENOVO dmi.bios.version: G1ETA4WW (2.64 ) dmi.board.asset.tag: Not Available dmi.board.name: 23445HU dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrG1ETA4WW(2.64):bd03/06/2014:br2.64:efr1.13:svnLENOVO:pn23445HU:pvrThinkPadT430:rvnLENOVO:rn23445HU:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430 dmi.product.name: 23445HU dmi.product.sku: LENOVO_MT_2344 dmi.product.version: ThinkPad T430 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4 version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1928082/+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 1888016] Re: Slow wifi, buggy bluethooth, slow startup. SEND HELP
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1888016 Title: Slow wifi, buggy bluethooth, slow startup. SEND HELP Status in network-manager package in Ubuntu: Confirmed Bug description: new to ubuntu and linux in general. installed it two days ago. get repeated errors thoughout the day. it's really bugging me. i hope my system doesn't crash soon. 22:55:57 kernel: rtw_pci :03:00.0: failed to send h2c command 22:50:39 kernel: ACPI Error: Aborting method \_SB.PCI0.LPC0.EC0._Q42 due to previous error (AE_NOT_EXIST) (20190816/psparse-529) 22:50:36 kernel: rtw_pci :03:00.0: failed to send h2c command 22:50:34 bluetoothd: Failed to set mode: Blocked through rfkill (0x12) 22:28:09 kernel: rtw_pci :03:00.0: failed to send h2c command 21:47:54 kernel: ACPI Error: Aborting method \_SB.PCI0.LPC0.EC0._Q42 due to previous error (AE_NOT_EXIST) (20190816/psparse-529) 21:33:57 kernel: rtw_pci :03:00.0: failed to send h2c command 20:48:55 kernel: ACPI Error: Aborting method \_SB.PCI0.LPC0.EC0._Q42 due to previous error (AE_NOT_EXIST) (20190816/psparse-529) 20:48:16 kernel: rtw_pci :03:00.0: failed to send h2c command 20:20:28 kernel: ACPI Error: Aborting method \_SB.PCI0.LPC0.EC0._Q42 due to previous error (AE_NOT_EXIST) (20190816/psparse-529) 20:20:25 kernel: rtw_pci :03:00.0: failed to send h2c command 20:20:23 bluetoothd: Failed to set mode: Blocked through rfkill (0x12) 20:20:23 kernel: rtw_pci :03:00.0: failed to send h2c command 18:50:51 kernel: ACPI Error: Aborting method \_SB.PCI0.LPC0.EC0._Q42 due to previous error (AE_NOT_EXIST) (20190816/psparse-529) 18:35:47 kernel: rtw_pci :03:00.0: failed to send h2c command 17:51:56 kernel: ACPI Error: Aborting method \_SB.PCI0.LPC0.EC0._Q42 due to previous error (AE_NOT_EXIST) (20190816/psparse-529) 17:48:39 kernel: rtw_pci :03:00.0: failed to send h2c command 17:48:37 kernel: debugfs: File 'force_bredr_smp' in directory 'hci0' already present! 17:46:44 kernel: rtw_pci :03:00.0: failed to send h2c command 17:26:22 udev-configure-: no corresponding CUPS device found 17:26:20 hpfax: [17493]: error: Failed to create /var/spool/cups/tmp/.hplip 17:19:56 kernel: rtw_pci :03:00.0: failed to send h2c command 16:53:01 kernel: ACPI Error: Aborting method \_SB.PCI0.LPC0.EC0._Q42 due to previous error (AE_NOT_EXIST) (20190816/psparse-529) 16:46:20 kernel: rtw_pci :03:00.0: failed to send h2c command 16:41:25 kernel: ACPI Error: Aborting method \_SB.PCI0.LPC0.EC0._Q42 due to previous error (AE_NOT_EXIST) (20190816/psparse-529) 16:33:06 kernel: rtw_pci :03:00.0: failed to send h2c command 16:03:52 bluetoothd: Unable to get io data for :1.72/Profile/HSPHSProfile/1108--1000-8000-00805f9b34fb: getpeername: Transport endpoint is not connected (107) 16:02:58 kernel: rtw_pci :03:00.0: failed to send h2c command 16:01:10 kernel: ACPI Error: Aborting method \_SB.PCI0.LPC0.EC0._Q42 due to previous error (AE_NOT_EXIST) (20190816/psparse-529) 16:01:08 kernel: rtw_pci :03:00.0: failed to send h2c command 16:01:06 bluetoothd: Failed to set mode: Blocked through rfkill (0x12) 15:10:21 kernel: rtw_pci :03:00.0: failed to send h2c command 14:55:02 kernel: ACPI Error: Aborting method \_SB.PCI0.LPC0.EC0._Q42 due to previous error (AE_NOT_EXIST) (20190816/psparse-529) 14:54:29 kernel: rtw_pci :03:00.0: failed to send h2c command 13:56:04 kernel: ACPI Error: Aborting method \_SB.PCI0.LPC0.EC0._Q42 due to previous error (AE_NOT_EXIST) (20190816/psparse-529) 13:17:41 kernel: rtw_pci :03:00.0: failed to send h2c command 12:57:06 kernel: ACPI Error: Aborting method \_SB.PCI0.LPC0.EC0._Q42 due to previous error (AE_NOT_EXIST) (20190816/psparse-529) 12:56:45 kernel: rtw_pci :03:00.0: failed to send h2c command 11:58:54 gdm-session-wor: gkr-pam: unable to locate daemon control file 11:58:47 kernel: rtw_pci :03:00.0: failed to send h2c command 11:58:44 bluetoothd: Failed to set mode: Blocked through rfkill (0x12) 11:58:43 kernel: rtw_pci :03:00.0: failed to send h2c command 11:58:39 kernel: ACPI Error: Aborting method \_SB.PCI0.LPC0.EC0._Q42 due to previous error (AE_NOT_EXIST) (20190816/psparse-529) 11:58:39 bluetoothd: Failed to set mode: Blocked through rfkill (0x12) 11:58:36 kernel: ACPI Error: Aborting method \_SB.WLBU._STA due to previous error (AE_NOT_FOUND) (20190816/psparse-529) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-14 (4 days ago) InstallationMed
[Touch-packages] [Bug 1926254] Re: x509 Certificate verification fails when basicConstraints=CA:FALSE, pathlen:0 on self-signed leaf certs
Performing verification for Groovy. I went and generated the ssl certificates and attempted to verify them with the openssl version 1.1.1f-1ubuntu4.3 from -updates. ubuntu@deep-mako:~$ sudo apt-cache policy openssl | grep Installed Installed: 1.1.1f-1ubuntu4.3 ubuntu@deep-mako:~$ mkdir reproducer ubuntu@deep-mako:~$ cd reproducer ubuntu@deep-mako:~/reproducer$ mkdir CA ubuntu@deep-mako:~/reproducer$ cat << EOF >> rootCA.cnf > [ req ] > prompt = no > distinguished_name = req_distinguished_name > x509_extensions = usr_cert > > [ req_distinguished_name ] > C = DE > O = Test Org > CN = Test RSA PSS Root-CA > > [ usr_cert ] > basicConstraints = critical,CA:TRUE > keyUsage = critical,keyCertSign,cRLSign > subjectKeyIdentifier = hash > authorityKeyIdentifier = keyid:always > EOF ubuntu@deep-mako:~/reproducer$ cat << EOF >> subCA.cnf > [ req ] > prompt = no > distinguished_name = req_distinguished_name > x509_extensions = usr_cert > > [ req_distinguished_name ] > C = DE > O = Test Org > CN = Test RSA PSS Sub-CA > > [ usr_cert ] > basicConstraints = critical,CA:TRUE,pathlen:0 > keyUsage = critical,keyCertSign,cRLSign > subjectKeyIdentifier = hash > authorityKeyIdentifier = keyid:always > EOF ubuntu@deep-mako:~/reproducer$ cat << EOF >> user.cnf > [ req ] > prompt = no > distinguished_name = req_distinguished_name > x509_extensions = usr_cert > > [ req_distinguished_name ] > C = DE > O = Test Org > CN = Test User > > [ usr_cert ] > basicConstraints = critical,CA:FALSE,pathlen:0 > keyUsage = critical,digitalSignature,keyAgreement > extendedKeyUsage = clientAuth,serverAuth > subjectKeyIdentifier = hash > authorityKeyIdentifier = keyid:always > EOF ubuntu@deep-mako:~/reproducer$ openssl genpkey -algorithm RSA-PSS -out rootCA_key.pem -pkeyopt rsa_keygen_bits:2048 + + ubuntu@deep-mako:~/reproducer$ openssl req -config rootCA.cnf -set_serial 01 -new -batch -sha256 -nodes -x509 -days 9125 -out CA/rootCA_cert.pem -key rootCA_key.pem -sigopt rsa_padding_mode:pss -sigopt rsa_pss_saltlen:-1 ubuntu@deep-mako:~/reproducer$ openssl genpkey -algorithm RSA-PSS -out subCA_key.pem -pkeyopt rsa_keygen_bits:2048 ..+ .+ ubuntu@deep-mako:~/reproducer$ openssl req -config subCA.cnf -new -out subCA_req.pem -key subCA_key.pem -sigopt rsa_padding_mode:pss -sigopt rsa_pss_saltlen:-1 ubuntu@deep-mako:~/reproducer$ openssl x509 -req -sha256 -in subCA_req.pem -CA CA/rootCA_cert.pem -CAkey rootCA_key.pem -out CA/subCA_cert.pem -CAserial rootCA_serial.txt -CAcreateserial -extfile subCA.cnf -extensions usr_cert -days 4380 -sigopt rsa_padding_mode:pss -sigopt rsa_pss_saltlen:-1 Signature ok subject=C = DE, O = Test Org, CN = Test RSA PSS Sub-CA Getting CA Private Key ubuntu@deep-mako:~/reproducer$ c_rehash CA Doing CA ubuntu@deep-mako:~/reproducer$ openssl genpkey -algorithm RSA-PSS -out user1_key.pem -pkeyopt rsa_keygen_bits:2048 ...+ .+ ubuntu@deep-mako:~/reproducer$ openssl req -config user.cnf -new -out user1_req.pem -key user1_key.pem -sigopt rsa_padding_mode:pss -sigopt rsa_pss_saltlen:-1 ubuntu@deep-mako:~/reproducer$ openssl x509 -req -sha256 -in user1_req.pem -CA CA/subCA_cert.pem -CAkey subCA_key.pem -out user1_cert.pem -CAserial subCA_serial.txt -CAcreateserial -extfile user.cnf -extensions usr_cert -days 1825 -sigopt rsa_padding_mode:pss -sigopt rsa_pss_saltlen:-1 Signature ok subject=C = DE, O = Test Org, CN = Test User Getting CA Private Key Now going and verifying the certificates: ubuntu@deep-mako:~/reproducer$ openssl verify -CAfile CA/rootCA_cert.pem -untrusted CA/subCA_cert.pem user1_cert.pem C = DE, O = Test Org, CN = Test User error 20 at 0 depth lookup: unable to get local issuer certificate error user1_cert.pem: verification failed We see verification failed, again on CA:FALSE,pathlen:0 basicConstraints. Now if we enable -proposed and install openssl 1.1.1f-1ubuntu4.4. $ openssl verify -CAfile CA/rootCA_cert.pem -untrusted CA/subCA_cert.pem user1_cert.pem user1_cert.pem: OK The certificate verifies properly. The problem is fixed. Additionally, if we examine the new unit tests added to openssl's testsuite in the buildlog for Groovy: https://launchpadlibrarian.net/537503607/buildlog_ubuntu-groovy- amd64.openssl_1.1.1f-1ubuntu4.4_BUILDING.txt.gz We see: ../../util/shlib_wrap.sh ../../apps/openssl verify -auth_level 1 -purpose sslserver -trusted ../../../test/certs/root-cert.pem -untrusted ../../../test/certs/ca-cert.pem ../../../test/certs/ee-pathlen.pem => 0 ok 84 - accept non-ca with pathlen:0 by default CN = server.example error 41 at 0 depth lookup: invalid or inconsistent certificate extension error ../../../test/certs/ee-pathlen.pem: verification failed ../../util/shlib_wrap.sh ../../apps/openssl verify -auth_level 1 -purpose sslserver -x509_strict -trusted ../../../test/certs/root-cert.
[Touch-packages] [Bug 1888016] Re: Slow wifi, buggy bluethooth, slow startup.
** Summary changed: - Slow wifi, buggy bluethooth, slow startup. SEND HELP + Slow wifi, buggy bluethooth, slow startup. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1888016 Title: Slow wifi, buggy bluethooth, slow startup. Status in network-manager package in Ubuntu: Confirmed Bug description: new to ubuntu and linux in general. installed it two days ago. get repeated errors thoughout the day. it's really bugging me. i hope my system doesn't crash soon. 22:55:57 kernel: rtw_pci :03:00.0: failed to send h2c command 22:50:39 kernel: ACPI Error: Aborting method \_SB.PCI0.LPC0.EC0._Q42 due to previous error (AE_NOT_EXIST) (20190816/psparse-529) 22:50:36 kernel: rtw_pci :03:00.0: failed to send h2c command 22:50:34 bluetoothd: Failed to set mode: Blocked through rfkill (0x12) 22:28:09 kernel: rtw_pci :03:00.0: failed to send h2c command 21:47:54 kernel: ACPI Error: Aborting method \_SB.PCI0.LPC0.EC0._Q42 due to previous error (AE_NOT_EXIST) (20190816/psparse-529) 21:33:57 kernel: rtw_pci :03:00.0: failed to send h2c command 20:48:55 kernel: ACPI Error: Aborting method \_SB.PCI0.LPC0.EC0._Q42 due to previous error (AE_NOT_EXIST) (20190816/psparse-529) 20:48:16 kernel: rtw_pci :03:00.0: failed to send h2c command 20:20:28 kernel: ACPI Error: Aborting method \_SB.PCI0.LPC0.EC0._Q42 due to previous error (AE_NOT_EXIST) (20190816/psparse-529) 20:20:25 kernel: rtw_pci :03:00.0: failed to send h2c command 20:20:23 bluetoothd: Failed to set mode: Blocked through rfkill (0x12) 20:20:23 kernel: rtw_pci :03:00.0: failed to send h2c command 18:50:51 kernel: ACPI Error: Aborting method \_SB.PCI0.LPC0.EC0._Q42 due to previous error (AE_NOT_EXIST) (20190816/psparse-529) 18:35:47 kernel: rtw_pci :03:00.0: failed to send h2c command 17:51:56 kernel: ACPI Error: Aborting method \_SB.PCI0.LPC0.EC0._Q42 due to previous error (AE_NOT_EXIST) (20190816/psparse-529) 17:48:39 kernel: rtw_pci :03:00.0: failed to send h2c command 17:48:37 kernel: debugfs: File 'force_bredr_smp' in directory 'hci0' already present! 17:46:44 kernel: rtw_pci :03:00.0: failed to send h2c command 17:26:22 udev-configure-: no corresponding CUPS device found 17:26:20 hpfax: [17493]: error: Failed to create /var/spool/cups/tmp/.hplip 17:19:56 kernel: rtw_pci :03:00.0: failed to send h2c command 16:53:01 kernel: ACPI Error: Aborting method \_SB.PCI0.LPC0.EC0._Q42 due to previous error (AE_NOT_EXIST) (20190816/psparse-529) 16:46:20 kernel: rtw_pci :03:00.0: failed to send h2c command 16:41:25 kernel: ACPI Error: Aborting method \_SB.PCI0.LPC0.EC0._Q42 due to previous error (AE_NOT_EXIST) (20190816/psparse-529) 16:33:06 kernel: rtw_pci :03:00.0: failed to send h2c command 16:03:52 bluetoothd: Unable to get io data for :1.72/Profile/HSPHSProfile/1108--1000-8000-00805f9b34fb: getpeername: Transport endpoint is not connected (107) 16:02:58 kernel: rtw_pci :03:00.0: failed to send h2c command 16:01:10 kernel: ACPI Error: Aborting method \_SB.PCI0.LPC0.EC0._Q42 due to previous error (AE_NOT_EXIST) (20190816/psparse-529) 16:01:08 kernel: rtw_pci :03:00.0: failed to send h2c command 16:01:06 bluetoothd: Failed to set mode: Blocked through rfkill (0x12) 15:10:21 kernel: rtw_pci :03:00.0: failed to send h2c command 14:55:02 kernel: ACPI Error: Aborting method \_SB.PCI0.LPC0.EC0._Q42 due to previous error (AE_NOT_EXIST) (20190816/psparse-529) 14:54:29 kernel: rtw_pci :03:00.0: failed to send h2c command 13:56:04 kernel: ACPI Error: Aborting method \_SB.PCI0.LPC0.EC0._Q42 due to previous error (AE_NOT_EXIST) (20190816/psparse-529) 13:17:41 kernel: rtw_pci :03:00.0: failed to send h2c command 12:57:06 kernel: ACPI Error: Aborting method \_SB.PCI0.LPC0.EC0._Q42 due to previous error (AE_NOT_EXIST) (20190816/psparse-529) 12:56:45 kernel: rtw_pci :03:00.0: failed to send h2c command 11:58:54 gdm-session-wor: gkr-pam: unable to locate daemon control file 11:58:47 kernel: rtw_pci :03:00.0: failed to send h2c command 11:58:44 bluetoothd: Failed to set mode: Blocked through rfkill (0x12) 11:58:43 kernel: rtw_pci :03:00.0: failed to send h2c command 11:58:39 kernel: ACPI Error: Aborting method \_SB.PCI0.LPC0.EC0._Q42 due to previous error (AE_NOT_EXIST) (20190816/psparse-529) 11:58:39 bluetoothd: Failed to set mode: Blocked through rfkill (0x12) 11:58:36 kernel: ACPI Error: Aborting method \_SB.WLBU._STA due to previous error (AE_NOT_FOUND) (20190816/psparse-529) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-14 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Foss
[Touch-packages] [Bug 1928172] [NEW] Xorg freeze
Public bug reported: If i sometimes missclick and click my Windows button on keyboard, Preview mode show up and sometimes i can't come back to full window mode, my Linux just freezes there. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Jest katalogiem: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Jest katalogiem: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Jest katalogiem: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.73.01 Thu Apr 1 21:40:36 UTC 2021 GCC version: ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 BootLog: Error: [Errno 13] Brak dostępu: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed May 12 08:02:20 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GP106 [GeForce GTX 1060 6GB] [1462:3283] InstallationDate: Installed on 2021-05-03 (8 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: MSI MS-7978 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=08cc25bc-76b2-4d2b-a729-e006642c7cb8 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2016 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: B.90 dmi.board.asset.tag: Default string dmi.board.name: B150 GAMING M3 (MS-7978) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrB.90:bd12/21/2016:br5.12:svnMSI:pnMS-7978:pvr2.0:rvnMSI:rnB150GAMINGM3(MS-7978):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.family: Default string dmi.product.name: MS-7978 dmi.product.sku: Default string dmi.product.version: 2.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug false-gpu-hang freeze hirsute 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/1928172 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: If i sometimes missclick and click my Windows button on keyboard, Preview mode show up and sometimes i can't come back to full window mode, my Linux just freezes there. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Jest katalogiem: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Jest katalogiem: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Jest katalogiem: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.73.01 Thu Apr 1 21:40:36 UTC 2021 GCC version: ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 BootLog: Error: [Errno 13] Brak dostępu: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed May 12 08:02:20 202
[Touch-packages] [Bug 1925742] Re: Recent iCloud versions trigger an issue in IMAP x
Brian, seriously? "Evolution" is broken in your "stable" release for almost a month and you are requesting some meaningless paperwork? People CAN NOT READ THEIR EMAIL for God's sake. Everyone using Apple's email is affected. Is this really the approach in Ubuntu these days? When a house is on fire, do firefighters ask people to (a) explain the effect of fire on the people in the house; (b) justify why the fire should be put out; (c) explain how to notice the raging inferno; (d) how to spot that the fire is gone when it is put out; (e) describe what else can happen when the fire it put out (lots actually - a cat can deliver a litter of kittens, for example)? -- 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/1925742 Title: Recent iCloud versions trigger an issue in IMAP x Status in evolution-data-server package in Ubuntu: Fix Released Bug description: There is a recently introduced bug in evolution-data-server which broke access to email in iCloud. The bug has been fixed yesterday by Evolution's developer: https://gitlab.gnome.org/GNOME/evolution/-/issues/1468 However, the package in Ubuntu (at least in Focal Fosa) still needs to be updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1925742/+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 1928172] Re: Xorg freeze
*** This bug is a duplicate of bug 1922353 *** https://bugs.launchpad.net/bugs/1922353 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1922353, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** This bug has been marked a duplicate of bug 1922353 Overview sometimes fails to appear or disappear in 21.04 -- 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/1928172 Title: Xorg freeze Status in gnome-shell package in Ubuntu: New Bug description: If i sometimes missclick and click my Windows button on keyboard, Preview mode show up and sometimes i can't come back to full window mode, my Linux just freezes there. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Jest katalogiem: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Jest katalogiem: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Jest katalogiem: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.73.01 Thu Apr 1 21:40:36 UTC 2021 GCC version: ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 BootLog: Error: [Errno 13] Brak dostępu: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed May 12 08:02:20 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GP106 [GeForce GTX 1060 6GB] [1462:3283] InstallationDate: Installed on 2021-05-03 (8 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: MSI MS-7978 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=08cc25bc-76b2-4d2b-a729-e006642c7cb8 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2016 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: B.90 dmi.board.asset.tag: Default string dmi.board.name: B150 GAMING M3 (MS-7978) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrB.90:bd12/21/2016:br5.12:svnMSI:pnMS-7978:pvr2.0:rvnMSI:rnB150GAMINGM3(MS-7978):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.family: Default string dmi.product.name: MS-7978 dmi.product.sku: Default string dmi.product.version: 2.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1928172/+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
