[Bug 2061313] Re: New Kubuntu icon's transparent background looks broken in some areas
Can we please use the white gear? It's a blessed variation of the logo per the design guide, and it will not clash with any background. I can create the image if needed. The dark blue will never look as good. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061313 Title: New Kubuntu icon's transparent background looks broken in some areas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-settings/+bug/2061313/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969984] Re: [SRU] Kubuntu Plymouth Theme Shows Badly on Multi-Screen
Hi Everyone: VERFIFIED: I tested this and the expected results are now present. That is, the Plymouth theme shows as centered on all monitors along with password entry box. I think we should also take comfort in this is just a re-skin of the Ubuntu Studio Plymouth which has been distributed for over 18 months. Again, thank you Erich, Chris, and Rik. Attention to first-touch experience I feel is very important to users, especially those moving from proprietary systems. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969984 Title: [SRU] Kubuntu Plymouth Theme Shows Badly on Multi-Screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-settings/+bug/1969984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969984] Re: [SRU] Kubuntu Plymouth Theme Shows Badly on Multi-Screen
Thank you Chris and Erich. I will test tomorrow. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969984 Title: [SRU] Kubuntu Plymouth Theme Shows Badly on Multi-Screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-settings/+bug/1969984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969984] Re: Kubuntu Plymouth Shows Badly on Multi-Screen
** Attachment added: "Ubuntu Studio Plymouth Theme (scaling)" https://bugs.launchpad.net/ubuntu/+source/kubuntu-settings/+bug/1969984/+attachment/5583592/+files/IMG_20220424_135612.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969984 Title: Kubuntu Plymouth Shows Badly on Multi-Screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-settings/+bug/1969984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969984] Re: Plymouth Login Shows Badly on Multi-Screen Setup
Here is the Ubuntu Studio Plymouth theme in use which is has scaling implemented. This looks great across all attached screens. We can likely create an updated Kubuntu Plymouth theme that is also scaling to replace the existing one if there is interest. ** Summary changed: - Plymouth Login Shows Badly on Multi-Screen Setup + Kubuntu Plymouth Shows Badly on Multi-Screen ** Description changed: Summary: - The plymouth theme for startup and disk decryption is off-center on - multi-monitor setups with varying resolutions. + The Kubuntu Plymouth theme for startup and disk decryption is off-center + on multi-monitor setups with varying resolutions. Steps to Reproduce: - Connect a 4k external display to a 1080p system. - Start Kubuntu 22.04 LTS Actual Results The Plymouth startup and disk encryption graphic are shifted down and to the right. This do NOT occur when using a single screen. Expected Results: The theme and disk encryption graphic should either be centered on all screens, or, as in Focal, should only be shown on the laptop screen. TODO - Test with more monitor resolutions See the attached images. Assessment: This is likely due to a non-responsive (old-style) Plymouth theme. We could likely create a responsive if it is acceptable. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: plymouth-theme-kubuntu-logo 1:22.04.9 ProcVersionSignature: Ubuntu 5.17.0-1003.3-oem 5.17.0 Uname: Linux 5.17.0-1003-oem x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Fri Apr 22 11:46:12 2022 InstallationDate: Installed on 2022-03-29 (24 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220328.1) PackageArchitecture: all SourcePackage: kubuntu-settings UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969984 Title: Kubuntu Plymouth Shows Badly on Multi-Screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-settings/+bug/1969984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969984] [NEW] Plymouth Login Shows Badly on Multi-Screen Setup
Public bug reported: Summary: The plymouth theme for startup and disk decryption is off-center on multi-monitor setups with varying resolutions. Steps to Reproduce: - Connect a 4k external display to a 1080p system. - Start Kubuntu 22.04 LTS Actual Results The Plymouth startup and disk encryption graphic are shifted down and to the right. This do NOT occur when using a single screen. Expected Results: The theme and disk encryption graphic should either be centered on all screens, or, as in Focal, should only be shown on the laptop screen. TODO - Test with more monitor resolutions See the attached images. Assessment: This is likely due to a non-responsive (old-style) Plymouth theme. We could likely create a responsive if it is acceptable. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: plymouth-theme-kubuntu-logo 1:22.04.9 ProcVersionSignature: Ubuntu 5.17.0-1003.3-oem 5.17.0 Uname: Linux 5.17.0-1003-oem x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Fri Apr 22 11:46:12 2022 InstallationDate: Installed on 2022-03-29 (24 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220328.1) PackageArchitecture: all SourcePackage: kubuntu-settings UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: kubuntu-settings (Ubuntu) Importance: Undecided Status: New ** Affects: kubuntu-settings (Ubuntu Jammy) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy kubuntu ** Attachment added: "Plymouth Incorrectly Placed Grpahics" https://bugs.launchpad.net/bugs/1969984/+attachment/5582587/+files/IMG_20220322_111642.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969984 Title: Plymouth Login Shows Badly on Multi-Screen Setup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-settings/+bug/1969984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960089] Re: Request 2.0 GiB Boot Partition for 22.04LTS FDE
@phd The /boot/efi partition size of 512MiB is far larger than most people need, but it does cover almost all potential use cases included dual boot. If that partition gets corrupted or filled, it could prevent boot of any OS on that disk. For this reason, I believe the team went with the sensible choice and kept that size to prevent this catastrophic, and for many people, unrecoverable error. There are certainly other reasons why /boot/efi is separate. As you mentioned, symlinks are lost, and I speculate that might necessitate full copies of initrd.img, for example, which would completely negate any space savings from combining the two. And of course, if you do that and load up too many kernels, the /boot/efi partition can get corrupted, which is even worse than an overfull boot partition. It seems to your suggestion of providing the user the opportunity to specify the /boot partition size on install is an excellent choice, and IMO is a great resolution to the issue. Customers who run development, AI, and content-creation workstations definitely need a larger boot allocation, whereas Raspberry Pi hobbyists are probably fine with the default, although I wonder how many of the latter actually need or use LVM or LVM+LUKS (FDE). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960089 Title: Request 2.0 GiB Boot Partition for 22.04LTS FDE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/partman-auto/+bug/1960089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962621] Re: Kwin-X11 Windows Resize, Position, and Move Erratically
At present, the windows appear to behaving well with the latest point update (5.24.2 => 5.24.3). ** Changed in: kwin (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962621 Title: Kwin-X11 Windows Resize, Position, and Move Erratically To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1962621/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962621] Re: Kwin-X11 Windows Resize, Position, and Move Erratically
** Description changed: + Upstream bug: https://bugs.kde.org/show_bug.cgi?id=451056 + Summary: Kwin is showing the following anomalies. These are not constant, but occur frequently (10-20 times) per day. They all appear to be associated with a scaling issue, so I have grouped them here. I will work to provide a better guide to reproduce as I find out more. Driver package is nvidia-driver-470. 1. When moving windows, the window will not move with the cursor but will continue to move the window further downwards on the screen even as the cursor is pushed further up. In fact, the speed at which a window moves down appears proportional to the upward movement of the cursor. 2. Windows that are moved as in (1) will often "slide off screen" and are inaccessible using the cursor although they still exist in the panel. Windows include IntelliJ Pro, Google Chrome, Konsole. 3. Windows that have been tiled (e.g. press meta + arrow key) when moved by dragging the title bar, will vertically collapse to only the height of the title bar. After dropping this title bar, one cannot select or move it again from the screen. Windows include IntelliJ Pro, Google Chrome, Konsole 4. Windows spawned by dragging a tab from one window onto an empty space (e.g. dragging a tab from a firefox browser or konsole session onto an empty space on the desktop) are placed badly - usually far away from the intended location, and sometimes off-screen as in (2). Steps to Reproduce: - Run Jammy with multiple 4K monitors attached. I've tried this with a high font DPI setting (System Settings > Fonts > Force DPI = 144) and fractional scaling (System Settings > Displays > Global Scale = 150%). These symptoms occur in either setting. I have not confirmed if this works without either. - Launch an app such as konsole or google-chrome (the latter seems highly susceptible). - Tile and drag windows. This results in issues (1), (2), and (3), above. - Drag a tab from konsole or firefox into an empty space. The window will be placed incorrectly even if the area dragged to is completely open. Potential Solutions: This appears may be a flaw with cursor position scaling in Kwin. In contrast, this bug does NOT exist in the prior KDE LTS found in Kubuntu 20.04.4. TODO: - Test on Intel-X11 - Test on Wayland once it becomes workable on Nvidia hardware ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: kwin-x11 4:5.24.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-lowlatency 5.15.12 Uname: Linux 5.15.0-18-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Tue Mar 1 12:43:47 2022 InstallationDate: Installed on 2022-02-21 (8 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220218) SourcePackage: kwin UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962621 Title: Kwin-X11 Windows Resize, Position, and Move Erratically To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1962621/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962621] Re: Kwin-X11 Windows Resize, Position, and Move Erratically
** Description changed: Summary: Kwin is showing the following anomalies. These are not constant, but occur a number of times per day. They all appear to be associated with a scaling issue, so I have grouped them here. I will work to provide a - better guide to reproduce as I find out more. + better guide to reproduce as I find out more. Driver package is nvidia- + driver-470. 1. When moving windows, the window will not move with the cursor but will continue to move the window further downwards on the screen even as the cursor is pushed further up. In fact, the speed at which a window moves down appears proportional to the upward movement of the cursor. - 2. Windows that are moved as in (1) will often "slide off screen" and are inaccessible using the cursor although they still exist in the panel. - 3. Windows that have been tiled (e.g. press meta + arrow key) when moved by dragging the title bar, will vertically collapse to only the height of the title bar. After dropping this title bar, one cannot select or move it again from the screen. + 2. Windows that are moved as in (1) will often "slide off screen" and are inaccessible using the cursor although they still exist in the panel. Windows include IntelliJ Pro, Google Chrome, Konsole. + 3. Windows that have been tiled (e.g. press meta + arrow key) when moved by dragging the title bar, will vertically collapse to only the height of the title bar. After dropping this title bar, one cannot select or move it again from the screen. Windows include IntelliJ Pro, Google Chrome, Konsole 4. Windows spawned by dragging a tab from one window onto an empty space (e.g. dragging a tab from a firefox browser or konsole session onto an empty space on the desktop) are placed badly - usually far away from the intended location, and sometimes off-screen as in (2). Steps to Reproduce: - Run Jammy with multiple 4K monitors attached. I've tried this with a high font DPI setting (System Settings > Fonts > Force DPI = 144) and fractional scaling (System Settings > Displays > Global Scale = 150%). These symptoms occur in either setting. I have not confirmed if this works without either. - Launch an app such as konsole or google-chrome (the latter seems highly susceptible). - Tile and drag windows. This results in issues (1), (2), and (3), above. - Drag a tab from konsole or firefox into an empty space. The window will be placed incorrectly even if the area dragged to is completely open. Potential Solutions: This appears may be a flaw with cursor position scaling in Kwin. In contrast, this bug does NOT exist in the prior KDE LTS found in Kubuntu 20.04.4. + + TODO: + - Test on Intel-X11 + - Test on Wayland once it becomes workable on Nvidia hardware ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: kwin-x11 4:5.24.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-lowlatency 5.15.12 Uname: Linux 5.15.0-18-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Tue Mar 1 12:43:47 2022 InstallationDate: Installed on 2022-02-21 (8 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220218) SourcePackage: kwin UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: Summary: Kwin is showing the following anomalies. These are not constant, but - occur a number of times per day. They all appear to be associated with a - scaling issue, so I have grouped them here. I will work to provide a - better guide to reproduce as I find out more. Driver package is nvidia- - driver-470. + occur frequently (10-20 times) per day. They all appear to be associated + with a scaling issue, so I have grouped them here. I will work to + provide a better guide to reproduce as I find out more. Driver package + is nvidia-driver-470. 1. When moving windows, the window will not move with the cursor but will continue to move the window further downwards on the screen even as the cursor is pushed further up. In fact, the speed at which a window moves down appears proportional to the upward movement of the cursor. 2. Windows that are moved as in (1) will often "slide off screen" and are inaccessible using the cursor although they still exist in the panel. Windows include IntelliJ Pro, Google Chrome, Konsole. 3. Windows that have been tiled (e.g. press meta + arrow key) when moved by dragging the title bar, will vertically collapse to only the height of the title bar. After dropping this title bar, one cannot select or move it again from the screen. Windows include IntelliJ Pro, Google Chrome, Konsole 4. Windows spawned by dragging a tab from one window onto an empty space (e.g. dragging a tab from a firefox browser or konsole session onto an empty space on the desktop) are placed badly - usually far away from the
[Bug 1962621] [NEW] Kwin-X11 Windows Resize, Position, and Move Erratically
Public bug reported: Summary: Kwin is showing the following anomalies. These are not constant, but occur a number of times per day. They all appear to be associated with a scaling issue, so I have grouped them here. I will work to provide a better guide to reproduce as I find out more. 1. When moving windows, the window will not move with the cursor but will continue to move the window further downwards on the screen even as the cursor is pushed further up. In fact, the speed at which a window moves down appears proportional to the upward movement of the cursor. 2. Windows that are moved as in (1) will often "slide off screen" and are inaccessible using the cursor although they still exist in the panel. 3. Windows that have been tiled (e.g. press meta + arrow key) when moved by dragging the title bar, will vertically collapse to only the height of the title bar. After dropping this title bar, one cannot select or move it again from the screen. 4. Windows spawned by dragging a tab from one window onto an empty space (e.g. dragging a tab from a firefox browser or konsole session onto an empty space on the desktop) are placed badly - usually far away from the intended location, and sometimes off-screen as in (2). Steps to Reproduce: - Run Jammy with multiple 4K monitors attached. I've tried this with a high font DPI setting (System Settings > Fonts > Force DPI = 144) and fractional scaling (System Settings > Displays > Global Scale = 150%). These symptoms occur in either setting. I have not confirmed if this works without either. - Launch an app such as konsole or google-chrome (the latter seems highly susceptible). - Tile and drag windows. This results in issues (1), (2), and (3), above. - Drag a tab from konsole or firefox into an empty space. The window will be placed incorrectly even if the area dragged to is completely open. Potential Solutions: This appears may be a flaw with cursor position scaling in Kwin. In contrast, this bug does NOT exist in the prior KDE LTS found in Kubuntu 20.04.4. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: kwin-x11 4:5.24.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-lowlatency 5.15.12 Uname: Linux 5.15.0-18-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Tue Mar 1 12:43:47 2022 InstallationDate: Installed on 2022-02-21 (8 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220218) SourcePackage: kwin UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: kwin (Ubuntu) Importance: High Status: Confirmed ** Tags: amd64 apport-bug jammy third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962621 Title: Kwin-X11 Windows Resize, Position, and Move Erratically To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1962621/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961631] Re: Static Launch Feedback not consistent with convention
Hi Rik, of course this is opinion. The prior decision to override the KDE default was also driven by an opinion. However, I feel the team at KDE have excellent UX designers these days, and as professional UX designer as well, I agree with their assessment. This appears to be the only adjustment of substance in /usr/share/kubuntu-default-settings/klaunchrc. Deleting this file reverts to the KDE default behavior with the animated launch feedback. If you decide to go this route, I hope you find this useful. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961631 Title: Static Launch Feedback not consistent with convention To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-settings/+bug/1961631/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960089] Re: Request 2.0 GiB Boot Partition for 22.04LTS FDE
** Description changed: Summary: We propose to increase the LVM /boot partition to 2.0 GiB. This provides the space needed so advanced users can use best practice to manage up to 3 kernel flavors. The current /boot partition on 20.04 and 22.04 is limited to just 705MiB, which allows only 3 concurrent kernels before filling and sometimes locking the system (each image set takes 180MiB total; 4 x 180 = 720MiB > 705MiB). Reasoning: Best practice recommends users keep at least two version of each kernel flavor in the /boot directory. If a user has 3 kernel flavors installed (e.g. oem, generic-hwe, and lowlatency-hwe), then one needs to reserve room for 2 x 3 = 6 kernels. The system needs the headroom of at least two additional kernels during any automated clean-up process due to package removal scheduling. I propose to also reserve room for 2 additional kernels as a safety measure. Thus the total recommend available space should accommodate 10 kernels. Each kernel file set takes up 180MiB in the /boot partition when used with Nvidia driver modules. These files include initrd.img, system.map, and vmlinuz. With future kernel and module growth, this may surpass 200MiB soon. Therefore, we suggest planning for 200M for each kernel. We therefore request a total LVM /boot partition size of 10 image x - 200MiB = 2.0 GiB. + 200MiB = 2.0GiB. Other Considerations: When unattended-upgrades works correctly (which does not yet employ best practice), we have seen users with just a single kernel flavor over-fill their /boot partitions. This is because unattended-upgrades can retain up to 4 kernels, while the /boot partition is only large enough for 3. I am currently working with others to improve the unattended-upgrades algorithm to use best practice. The installer could allow users to resize the /boot partition during - installation. In this case, we highly recommend a 2.0 GB default for the + installation. In this case, we highly recommend a 2.0GiB default for the reasons outlined above. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.14.0-1011.11-oem 5.14.17 Uname: Linux 5.14.0-1011-oem x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Fri Feb 4 14:53:36 2022 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed only-ubiquity quiet splash oem-config/enable=true --- InstallationDate: Installed on 2020-06-10 (604 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960089 Title: Request 2.0 GiB Boot Partition for 22.04LTS FDE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/partman-auto/+bug/1960089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960089] Re: Request 2.0 GiB Boot Partition for 22.04LTS FDE
** Summary changed: - Request 2.0 GB Boot Partition for 22.04LTS FDE + Request 2.0 GiB Boot Partition for 22.04LTS FDE -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960089 Title: Request 2.0 GiB Boot Partition for 22.04LTS FDE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/partman-auto/+bug/1960089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960089] Re: Request 2.0 GB Boot Partition for 22.04LTS FDE
** Description changed: Summary: - We propose to increase the LVM /boot partition to 2.0 GB. This provides + We propose to increase the LVM /boot partition to 2.0 GiB. This provides the space needed so advanced users can use best practice to manage up to 3 kernel flavors. The current /boot partition on 20.04 and 22.04 is - limited to just 705M, which allows only 3 concurrent kernels before - filling and sometimes locking the system (each image set takes 180M - total; 4 x 180 = 720M > 705M). + limited to just 705MiB, which allows only 3 concurrent kernels before + filling and sometimes locking the system (each image set takes 180MiB + total; 4 x 180 = 720MiB > 705MiB). Reasoning: Best practice recommends users keep at least two version of each kernel flavor in the /boot directory. If a user has 3 kernel flavors installed (e.g. oem, generic-hwe, and lowlatency-hwe), then one needs to reserve room for 2 x 3 = 6 kernels. The system needs the headroom of at least two additional kernels during any automated clean-up process due to package removal scheduling. I propose to also reserve room for 2 additional kernels as a safety measure. Thus the total recommend available space should accommodate 10 kernels. - Each kernel file set takes up 180M in the /boot partition when used with - Nvidia driver modules. These files include initrd.img, system.map, and - vmlinuz. With future kernel and module growth, this may surpass 200M - soon. Therefore, we suggest planning for 200M for each kernel. + Each kernel file set takes up 180MiB in the /boot partition when used + with Nvidia driver modules. These files include initrd.img, system.map, + and vmlinuz. With future kernel and module growth, this may surpass + 200MiB soon. Therefore, we suggest planning for 200M for each kernel. - We therefore request a total LVM /boot partition size of 10 image x 200M - = 2.0 GB. + We therefore request a total LVM /boot partition size of 10 image x + 200MiB = 2.0 GiB. Other Considerations: When unattended-upgrades works correctly (which does not yet employ best practice), we have seen users with just a single kernel flavor over-fill their /boot partitions. This is because unattended-upgrades can retain up to 4 kernels, while the /boot partition is only large enough for 3. I am currently working with others to improve the unattended-upgrades algorithm to use best practice. The installer could allow users to resize the /boot partition during installation. In this case, we highly recommend a 2.0 GB default for the reasons outlined above. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.14.0-1011.11-oem 5.14.17 Uname: Linux 5.14.0-1011-oem x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Fri Feb 4 14:53:36 2022 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed only-ubiquity quiet splash oem-config/enable=true --- InstallationDate: Installed on 2020-06-10 (604 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960089 Title: Request 2.0 GiB Boot Partition for 22.04LTS FDE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/partman-auto/+bug/1960089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960089] Re: Request 2.0 GB Boot Partition for 22.04LTS FDE
** Summary changed: - Ubiquity Boot Partition for LVM needs to be 2.0 GB for 22.04LTS + Request 2.0 GB Boot Partition for 22.04LTS FDE -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960089 Title: Request 2.0 GB Boot Partition for 22.04LTS FDE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/partman-auto/+bug/1960089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914278] Re: Kernel updates marked as "manually installed", prevents old kernels cleanup
@ximion thanks for this substantial work. The list of enhancements looks impressive. In testing on Jammy where I compare this to the prior versions, manual and automatic marks are as before which is good. We haven't confirmed meta package upgrades that pull in new dependencies (as with kernel packages) because we haven't seen an upgrade yet. However, we may build a package to test this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914278 Title: Kernel updates marked as "manually installed", prevents old kernels cleanup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1914278/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959971] Re: increase /boot partition size
@sil2100 @brian-murray: Thank you for your work and consideration on this. We addressed this issue Kubuntu Focus OEM ISO (https://kfocus.org/try) by increasing the /boot partition size and providing an app that monitors and removes unused kernels (https://kfocus.org/wf/tools#kclean). We want to share our findings upstream for the benefit of everyone that uses client Ubuntu with FDE. In summary, an additional 1.2G of disk space is a very small price to pay to avoid the expense of guiding non-expert users to recover from an over-full partition. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959971 Title: increase /boot partition size To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/partman-auto/+bug/1959971/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956393] Re: Bluetooth no longer recognized after update to 5.14.0-1013
@tjaalton: This kernel has been tested on 6 laptop types and passes on all of them. Tested subsystems included USB, Bluetooth, Wi-Fi, Ethernet and many others. We can get you a full report if you like. Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956393 Title: Bluetooth no longer recognized after update to 5.14.0-1013 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.14/+bug/1956393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959971] Re: increase /boot partition size
Design Failure Mode Effects Analysis System: Boot Potential Failure Mode: /boot partition overfills Effects of Failure: To return the system to a usable state, the user must have advanced knowledge and an available system recovery disk. The procedure involves disk mounting, chroot, package management, and deep file system knowledge. This is outside the range of most target users. Severity: 10 (system is completely unusable until recovery, and recovery is very expensive) Causes of Failure: 1. Multiple kernel updates between reboots will overfill the standard 705M /boot partition with over 3 kernels. 2. User installing generic and lowlatency hwe kernels. They may also have transient kernels when switching to another kernel like oem. Preventative Activities: 1. There does not appear to be any tool to guide kernel selection for users or ensure the latest and penultimate versions are reserved for the kernels. 2. There does not appear to be any testing which prevents installation of a kernel that would over-fill the disk. 3. unattended-upgrades tries to clean images that fill up the /boot disk, but it does not consider disk space, and even when it work (which is a whole other issue), the /boot disk is required to hold 4 images at times which is not feasible with the current 705M and 180M file set size. Occurrence: 5 (even users with a singe Kernel flavor encounter this) Detection Rating: 9 Risk Priority Number: Severity * Occurrence * Detection = 450 Take Away Points: * The DFMEA indicates this is a severe issue that should be considered critical. * When an overfull /boot disk occurs, the effect is catastrophic to the the average user, and for many is simple unrecoverable. This can and does drive users to abandon the OS when this occurs. * Existing controls to prevent occurrence are inadequate (automated upgrades still allows disk to over fill when using a single kernel flavor, and does not consider disk space) or completely missing (users are not guided on the issue of kernel management). The popularity of forum posts over the years about this issue illustrates this is a substantial problem. * This issue goes beyond /boot partition size, but the increasing it to handle all possible transient states is required for a complete solution. * Disk space is cheap these days. On consumer desktop solutions, 2.0GB is a small price to pay to avoid a catastrophic failure which is otherwise unrecoverable for many users. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959971 Title: increase /boot partition size To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/partman-auto/+bug/1959971/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959971] Re: increase /boot partition size
Hi Łukasz and Brian: I have been doing quite a bit of research in this area recently, and also am advocating to get kernel management and cleanup improved, especially for users who must have separate /boot partitions. This means professional users who are required to have full disk encryption according to company IT policies. Using best practice to manage 3 kernel packages (e.g. oem, lowlatency- hwe, generic-hwe) results in the need to maintain 6 kernel file sets (latest and penultimate version for each kernel). Because of the way kernel cleaning is scheduled, additional space is also required for at least 2 additional images. You can see the entire reasoning and details at LP: #1960089. Our conclusion is that 2.0 GB is the preferred target /boot partition size for professional systems. This is reinforced by my research which shows many pros recommend this same size when discussing partitioning (Just one example: https://adventures-in- tech.blogspot.com/2018/10/encrypted-ubuntu-installation-with.html) Given disk space these days, this seems like a small price to pay to support best practice and (hopefully) a future unattended upgrades algorithm that honors them as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959971 Title: increase /boot partition size To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/partman-auto/+bug/1959971/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960089] [NEW] Ubiquity Boot Partition for LVM needs to be 2.0 GB for 22.04LTS
Public bug reported: Summary: We propose to increase the LVM /boot partition to 2.0 GB. This provides the space needed so advanced users can use best practice to manage up to 3 kernel flavors. The current /boot partition on 20.04 and 22.04 is limited to just 705M, which allows only 3 concurrent kernels before filling and sometimes locking the system (each image set takes 180M total; 4 x 180 = 720M > 705M). Reasoning: Best practice recommends users keep at least two version of each kernel flavor in the /boot directory. If a user has 3 kernel flavors installed (e.g. oem, generic-hwe, and lowlatency-hwe), then one needs to reserve room for 2 x 3 = 6 kernels. The system needs the headroom of at least two additional kernels during any automated clean-up process due to package removal scheduling. I propose to also reserve room for 2 additional kernels as a safety measure. Thus the total recommend available space should accommodate 10 kernels. Each kernel file set takes up 180M in the /boot partition when used with Nvidia driver modules. These files include initrd.img, system.map, and vmlinuz. With future kernel and module growth, this may surpass 200M soon. Therefore, we suggest planning for 200M for each kernel. We therefore request a total LVM /boot partition size of 10 image x 200M = 2.0 GB. Other Considerations: When unattended-upgrades works correctly (which does not yet employ best practice), we have seen users with just a single kernel flavor over-fill their /boot partitions. This is because unattended-upgrades can retain up to 4 kernels, while the /boot partition is only large enough for 3. I am currently working with others to improve the unattended-upgrades algorithm to use best practice. The installer could allow users to resize the /boot partition during installation. In this case, we highly recommend a 2.0 GB default for the reasons outlined above. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.14.0-1011.11-oem 5.14.17 Uname: Linux 5.14.0-1011-oem x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Fri Feb 4 14:53:36 2022 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed only-ubiquity quiet splash oem-config/enable=true --- InstallationDate: Installed on 2020-06-10 (604 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal oem-config ubiquity-20.04.15 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960089 Title: Ubiquity Boot Partition for LVM needs to be 2.0 GB for 22.04LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1960089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
