[Touch-packages] [Bug 2027847] Re: Bump minimum /boot size in ubuntu-release-upgrader
$ cat /var/log/installer/media-info Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) -- 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/2027847 Title: Bump minimum /boot size in ubuntu-release-upgrader Status in apt package in Ubuntu: Won't Fix Status in dpkg package in Ubuntu: Invalid Status in kernel-package package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in linux-firmware package in Ubuntu: Invalid Status in linux-kernel-headers package in Ubuntu: Invalid Status in linux-restricted-modules package in Ubuntu: Invalid Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: System information: ubuntu 23.04 x86_64 6.2.0-24-generic Upgrading the system: $ sudo dpkg --configure -a Setting up linux-firmware (20230323.gitbcdcfbcf-0ubuntu1.2) ... update-initramfs: Generating /boot/initrd.img-6.2.0-24-generic I: The initramfs will attempt to resume from /dev/dm-2 I: (/dev/mapper/ubuntu--vg-swap_1) I: Set the RESUME variable to override this. zstd: error 70 : Write error : cannot write block : No space left on device E: mkinitramfs failure zstd -q -1 -T0 70 Check space left (none): $ df -h /boot Filesystem Size Used Avail Use% Mounted on /dev/sdb2 707M 693M 0 100% /boot What is required is to remove older kernels (and purge them most likely). List all the installed kernels except the current one: $ dpkg -l 'linux-*' | sed '/^ii/!d;/'"$(uname -r | sed "s/\(.*\)-\([^0-9]\+\)/\1/")"'/d;s/^[^ ]* [^ ]* \([^ ]*\).*/\1/;/[0-9]/!d' linux-headers-6.2.0-23 linux-headers-6.2.0-23-generic linux-headers-6.2.0-25 linux-headers-6.2.0-25-generic linux-image-6.2.0-23-generic linux-libc-dev:amd64 linux-libc-dev:i386 linux-modules-6.2.0-23-generic linux-modules-6.2.0-25-generic linux-modules-extra-6.2.0-23-generic linux-modules-extra-6.2.0-25-generic Is not possible to uninstall any kernel because fails: $ sudo apt purge linux-headers-6.2.0-23 E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. Reconfigure fails again so some kernel have to be manually removed to free up space: $ sudo rm /boot/initrd.img-6.2.0-23-generic $ sudo rm -rf /boot/initrd.img-6.2.0-25-generic.new Now you can reconfigure: $ Remove kernels: $ sudo apt purge linux-headers-6.2.0-23 linux-headers-6.2.0-23-generic linux-headers-6.2.0-25 linux-headers-6.2.0-25-generic linux-image-6.2.0-23-generic linux-modules-6.2.0-23-generic linux-modules-6.2.0-25-generic linux-modules-extra-6.2.0-23-generic linux-modules-extra-6.2.0-25-generic Reboot: $ sudo reboot Upgrade as usual: $ sudo apt update && sudo apt upgrade Before upgrading new kernels I need to check for free space and remove older kernels manually. Fix this so there's only one kernel left. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2027847/+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 2027847] Re: Bump minimum /boot size in ubuntu-release-upgrader
art_msdos.mod 4096 part_apple.mod 4096 blocklist.mod 4096 bufio.mod 4096 keystatus.mod 4096 password.mod 4096 lsmmap.mod 4096 cmp.mod 4096 usbserial_common.mod 4096 dm_nv.mod 4096 mdraid09_be.mod 4096 mdraid09.mod 4096 ctz_test.mod 4096 part_dfly.mod 4096 mdraid1x.mod 4096 part_amiga.mod 4096 setjmp_test.mod 4096 cpuid.mod 4096 part_plan.mod 4096 backtrace.mod 4096 part_sunpc.mod 4096 modinfo.sh 4096 mul_test.mod 4096 wrmsr.mod 4096 gcry_arcfour.mod 4096 time.mod 4096 usbserial_usbdebug.mod 4096 part_acorn.mod 4096 priority_queue.mod 4096 read.mod 4096 exfctest.mod 4096 offsetio.mod 4096 part_sun.mod 4096 part_dvh.mod 4096 eval.mod 4096 efifwsetup.mod 4096 crc64.mod 4096 afsplitter.mod 4096 test_blockarg.mod 4096 trig.mod 4096 raid5rec.mod 4096 adler32.mod 4096 pbkdf2.mod 4096 true.mod 4096 hello.mod 4096 reboot.mod 4096 cbtable.mod 4096 aout.mod 4096 div.mod 4096 crypto.lst 4096 setjmp.mod 4096 all_video.mod 4096 fs.lst 4096 terminal.lst 4096 partmap.lst 4096 load.cfg 4096 video.lst 4096 parttool.lst /boot/grub/fonts: total 2396160 2396160 unicode.pf2 /boot/grub/locale: total 131072 118784 e...@quot.mo 4096 en_GB.mo 4096 en_AU.mo 4096 en_CA.mo -- 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/2027847 Title: Bump minimum /boot size in ubuntu-release-upgrader Status in apt package in Ubuntu: Won't Fix Status in dpkg package in Ubuntu: Invalid Status in kernel-package package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in linux-firmware package in Ubuntu: Invalid Status in linux-kernel-headers package in Ubuntu: Invalid Status in linux-restricted-modules package in Ubuntu: Invalid Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: System information: ubuntu 23.04 x86_64 6.2.0-24-generic Upgrading the system: $ sudo dpkg --configure -a Setting up linux-firmware (20230323.gitbcdcfbcf-0ubuntu1.2) ... update-initramfs: Generating /boot/initrd.img-6.2.0-24-generic I: The initramfs will attempt to resume from /dev/dm-2 I: (/dev/mapper/ubuntu--vg-swap_1) I: Set the RESUME variable to override this. zstd: error 70 : Write error : cannot write block : No space left on device E: mkinitramfs failure zstd -q -1 -T0 70 Check space left (none): $ df -h /boot Filesystem Size Used Avail Use% Mounted on /dev/sdb2 707M 693M 0 100% /boot What is required is to remove older kernels (and purge them most likely). List all the installed kernels except the current one: $ dpkg -l 'linux-*' | sed '/^ii/!d;/'"$(uname -r | sed "s/\(.*\)-\([^0-9]\+\)/\1/")"'/d;s/^[^ ]* [^ ]* \([^ ]*\).*/\1/;/[0-9]/!d' linux-headers-6.2.0-23 linux-headers-6.2.0-23-generic linux-headers-6.2.0-25 linux-headers-6.2.0-25-generic linux-image-6.2.0-23-generic linux-libc-dev:amd64 linux-libc-dev:i386 linux-modules-6.2.0-23-generic linux-modules-6.2.0-25-generic linux-modules-extra-6.2.0-23-generic linux-modules-extra-6.2.0-25-generic Is not possible to uninstall any kernel because fails: $ sudo apt purge linux-headers-6.2.0-23 E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. Reconfigure fails again so some kernel have to be manually removed to free up space: $ sudo rm /boot/initrd.img-6.2.0-23-generic $ sudo rm -rf /boot/initrd.img-6.2.0-25-generic.new Now you can reconfigure: $ Remove kernels: $ sudo apt purge linux-headers-6.2.0-23 linux-headers-6.2.0-23-generic linux-headers-6.2.0-25 linux-headers-6.2.0-25-generic linux-image-6.2.0-23-generic linux-modules-6.2.0-23-generic linux-modules-6.2.0-25-generic linux-modules-extra-6.2.0-23-generic linux-modules-extra-6.2.0-25-generic Reboot: $ sudo reboot Upgrade as usual: $ sudo apt update && sudo apt upgrade Before upgrading new kernels I need to check for free space and remove older kernels manually. Fix this so there's only one kernel left. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2027847/+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 2027847] Re: Bump minimum /boot size in ubuntu-release-upgrader
I'm using nvidia drivers. According to stat, /boot was birth in 2018-11 sudo fdisk -l /dev/sdb2 (/boot mount point) Disk /dev/sdb2: 735,99 MiB, 771740160 bytes, 1507305 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 33553920 bytes df -h /boot Filesystem Size Used Avail Use% Mounted on /dev/sdb2 707M 252M 405M 39% /boot -- 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/2027847 Title: Bump minimum /boot size in ubuntu-release-upgrader Status in apt package in Ubuntu: Won't Fix Status in dpkg package in Ubuntu: Invalid Status in kernel-package package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in linux-firmware package in Ubuntu: Invalid Status in linux-kernel-headers package in Ubuntu: Invalid Status in linux-restricted-modules package in Ubuntu: Invalid Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: System information: ubuntu 23.04 x86_64 6.2.0-24-generic Upgrading the system: $ sudo dpkg --configure -a Setting up linux-firmware (20230323.gitbcdcfbcf-0ubuntu1.2) ... update-initramfs: Generating /boot/initrd.img-6.2.0-24-generic I: The initramfs will attempt to resume from /dev/dm-2 I: (/dev/mapper/ubuntu--vg-swap_1) I: Set the RESUME variable to override this. zstd: error 70 : Write error : cannot write block : No space left on device E: mkinitramfs failure zstd -q -1 -T0 70 Check space left (none): $ df -h /boot Filesystem Size Used Avail Use% Mounted on /dev/sdb2 707M 693M 0 100% /boot What is required is to remove older kernels (and purge them most likely). List all the installed kernels except the current one: $ dpkg -l 'linux-*' | sed '/^ii/!d;/'"$(uname -r | sed "s/\(.*\)-\([^0-9]\+\)/\1/")"'/d;s/^[^ ]* [^ ]* \([^ ]*\).*/\1/;/[0-9]/!d' linux-headers-6.2.0-23 linux-headers-6.2.0-23-generic linux-headers-6.2.0-25 linux-headers-6.2.0-25-generic linux-image-6.2.0-23-generic linux-libc-dev:amd64 linux-libc-dev:i386 linux-modules-6.2.0-23-generic linux-modules-6.2.0-25-generic linux-modules-extra-6.2.0-23-generic linux-modules-extra-6.2.0-25-generic Is not possible to uninstall any kernel because fails: $ sudo apt purge linux-headers-6.2.0-23 E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. Reconfigure fails again so some kernel have to be manually removed to free up space: $ sudo rm /boot/initrd.img-6.2.0-23-generic $ sudo rm -rf /boot/initrd.img-6.2.0-25-generic.new Now you can reconfigure: $ Remove kernels: $ sudo apt purge linux-headers-6.2.0-23 linux-headers-6.2.0-23-generic linux-headers-6.2.0-25 linux-headers-6.2.0-25-generic linux-image-6.2.0-23-generic linux-modules-6.2.0-23-generic linux-modules-6.2.0-25-generic linux-modules-extra-6.2.0-23-generic linux-modules-extra-6.2.0-25-generic Reboot: $ sudo reboot Upgrade as usual: $ sudo apt update && sudo apt upgrade Before upgrading new kernels I need to check for free space and remove older kernels manually. Fix this so there's only one kernel left. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2027847/+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 2027847] Re: Bump minimum /boot size in ubuntu-release-upgrader
These are the 'linux-' packages which I have installed: binutils-x86-64-linux-gnu/lunar-updates,lunar-security,now 2.40-2ubuntu4.1 amd64 [installed,automatic] linux-base/lunar,lunar,lunar,lunar,lunar,lunar,now 4.5ubuntu9 all [installed,automatic] linux-firmware/lunar-updates,lunar-updates,lunar-security,lunar-security,now 20230323.gitbcdcfbcf-0ubuntu1.2 all [installed,automatic] linux-headers-6.2.0-24-generic/lunar-updates,lunar-security,now 6.2.0-24.24 amd64 [installed,automatic] linux-headers-6.2.0-24/lunar-updates,lunar-updates,lunar-security,lunar-security,now 6.2.0-24.24 all [installed,automatic] linux-image-6.2.0-24-generic/lunar-updates,lunar-security,now 6.2.0-24.24 amd64 [installed,automatic] linux-libc-dev/lunar-updates,lunar-security,now 6.2.0-25.25 amd64 [installed,automatic] linux-libc-dev/lunar-updates,lunar-security,now 6.2.0-25.25 i386 [installed,automatic] linux-modules-6.2.0-24-generic/lunar-updates,lunar-security,now 6.2.0-24.24 amd64 [installed,automatic] linux-modules-extra-6.2.0-24-generic/lunar-updates,lunar-security,now 6.2.0-24.24 amd64 [installed,automatic] linux-sound-base/lunar,lunar,lunar,lunar,lunar,lunar,now 1.0.25+dfsg-0ubuntu7 all [installed,automatic] selinux-utils/lunar,lunar,lunar,now 3.4-1build4 amd64 [installed,automatic] syslinux-common/lunar,lunar,lunar,lunar,lunar,lunar,now 3:6.04~git20190206.bf6db5b4+dfsg1-3ubuntu1 all [installed,automatic] util-linux-extra/lunar,lunar,lunar,now 2.38.1-4ubuntu1 amd64 [installed,automatic] -- 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/2027847 Title: Bump minimum /boot size in ubuntu-release-upgrader Status in apt package in Ubuntu: Won't Fix Status in dpkg package in Ubuntu: Invalid Status in kernel-package package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in linux-firmware package in Ubuntu: Invalid Status in linux-kernel-headers package in Ubuntu: Invalid Status in linux-restricted-modules package in Ubuntu: Invalid Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: System information: ubuntu 23.04 x86_64 6.2.0-24-generic Upgrading the system: $ sudo dpkg --configure -a Setting up linux-firmware (20230323.gitbcdcfbcf-0ubuntu1.2) ... update-initramfs: Generating /boot/initrd.img-6.2.0-24-generic I: The initramfs will attempt to resume from /dev/dm-2 I: (/dev/mapper/ubuntu--vg-swap_1) I: Set the RESUME variable to override this. zstd: error 70 : Write error : cannot write block : No space left on device E: mkinitramfs failure zstd -q -1 -T0 70 Check space left (none): $ df -h /boot Filesystem Size Used Avail Use% Mounted on /dev/sdb2 707M 693M 0 100% /boot What is required is to remove older kernels (and purge them most likely). List all the installed kernels except the current one: $ dpkg -l 'linux-*' | sed '/^ii/!d;/'"$(uname -r | sed "s/\(.*\)-\([^0-9]\+\)/\1/")"'/d;s/^[^ ]* [^ ]* \([^ ]*\).*/\1/;/[0-9]/!d' linux-headers-6.2.0-23 linux-headers-6.2.0-23-generic linux-headers-6.2.0-25 linux-headers-6.2.0-25-generic linux-image-6.2.0-23-generic linux-libc-dev:amd64 linux-libc-dev:i386 linux-modules-6.2.0-23-generic linux-modules-6.2.0-25-generic linux-modules-extra-6.2.0-23-generic linux-modules-extra-6.2.0-25-generic Is not possible to uninstall any kernel because fails: $ sudo apt purge linux-headers-6.2.0-23 E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. Reconfigure fails again so some kernel have to be manually removed to free up space: $ sudo rm /boot/initrd.img-6.2.0-23-generic $ sudo rm -rf /boot/initrd.img-6.2.0-25-generic.new Now you can reconfigure: $ Remove kernels: $ sudo apt purge linux-headers-6.2.0-23 linux-headers-6.2.0-23-generic linux-headers-6.2.0-25 linux-headers-6.2.0-25-generic linux-image-6.2.0-23-generic linux-modules-6.2.0-23-generic linux-modules-6.2.0-25-generic linux-modules-extra-6.2.0-23-generic linux-modules-extra-6.2.0-25-generic Reboot: $ sudo reboot Upgrade as usual: $ sudo apt update && sudo apt upgrade Before upgrading new kernels I need to check for free space and remove older kernels manually. Fix this so there's only one kernel left. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2027847/+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 2027847] Re: Bump minimum /boot size in ubuntu-release-upgrader
I was able to upgrade because left only 1 installed kernel just before "update-manager -d". Probably I should have opened the issue by then... -- 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/2027847 Title: Bump minimum /boot size in ubuntu-release-upgrader Status in apt package in Ubuntu: Won't Fix Status in dpkg package in Ubuntu: Invalid Status in kernel-package package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in linux-firmware package in Ubuntu: Invalid Status in linux-kernel-headers package in Ubuntu: Invalid Status in linux-restricted-modules package in Ubuntu: Invalid Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: System information: ubuntu 23.04 x86_64 6.2.0-24-generic Upgrading the system: $ sudo dpkg --configure -a Setting up linux-firmware (20230323.gitbcdcfbcf-0ubuntu1.2) ... update-initramfs: Generating /boot/initrd.img-6.2.0-24-generic I: The initramfs will attempt to resume from /dev/dm-2 I: (/dev/mapper/ubuntu--vg-swap_1) I: Set the RESUME variable to override this. zstd: error 70 : Write error : cannot write block : No space left on device E: mkinitramfs failure zstd -q -1 -T0 70 Check space left (none): $ df -h /boot Filesystem Size Used Avail Use% Mounted on /dev/sdb2 707M 693M 0 100% /boot What is required is to remove older kernels (and purge them most likely). List all the installed kernels except the current one: $ dpkg -l 'linux-*' | sed '/^ii/!d;/'"$(uname -r | sed "s/\(.*\)-\([^0-9]\+\)/\1/")"'/d;s/^[^ ]* [^ ]* \([^ ]*\).*/\1/;/[0-9]/!d' linux-headers-6.2.0-23 linux-headers-6.2.0-23-generic linux-headers-6.2.0-25 linux-headers-6.2.0-25-generic linux-image-6.2.0-23-generic linux-libc-dev:amd64 linux-libc-dev:i386 linux-modules-6.2.0-23-generic linux-modules-6.2.0-25-generic linux-modules-extra-6.2.0-23-generic linux-modules-extra-6.2.0-25-generic Is not possible to uninstall any kernel because fails: $ sudo apt purge linux-headers-6.2.0-23 E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. Reconfigure fails again so some kernel have to be manually removed to free up space: $ sudo rm /boot/initrd.img-6.2.0-23-generic $ sudo rm -rf /boot/initrd.img-6.2.0-25-generic.new Now you can reconfigure: $ Remove kernels: $ sudo apt purge linux-headers-6.2.0-23 linux-headers-6.2.0-23-generic linux-headers-6.2.0-25 linux-headers-6.2.0-25-generic linux-image-6.2.0-23-generic linux-modules-6.2.0-23-generic linux-modules-6.2.0-25-generic linux-modules-extra-6.2.0-23-generic linux-modules-extra-6.2.0-25-generic Reboot: $ sudo reboot Upgrade as usual: $ sudo apt update && sudo apt upgrade Before upgrading new kernels I need to check for free space and remove older kernels manually. Fix this so there's only one kernel left. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2027847/+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 2027847] Re: Bump minimum /boot size in ubuntu-release-upgrader
I think this install was performed mid-2018, judging by my bug report: https://bugs.launchpad.net/ubuntu/+bug/1773633 -- 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/2027847 Title: Bump minimum /boot size in ubuntu-release-upgrader Status in apt package in Ubuntu: Won't Fix Status in dpkg package in Ubuntu: Invalid Status in kernel-package package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in linux-firmware package in Ubuntu: Invalid Status in linux-kernel-headers package in Ubuntu: Invalid Status in linux-restricted-modules package in Ubuntu: Invalid Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: System information: ubuntu 23.04 x86_64 6.2.0-24-generic Upgrading the system: $ sudo dpkg --configure -a Setting up linux-firmware (20230323.gitbcdcfbcf-0ubuntu1.2) ... update-initramfs: Generating /boot/initrd.img-6.2.0-24-generic I: The initramfs will attempt to resume from /dev/dm-2 I: (/dev/mapper/ubuntu--vg-swap_1) I: Set the RESUME variable to override this. zstd: error 70 : Write error : cannot write block : No space left on device E: mkinitramfs failure zstd -q -1 -T0 70 Check space left (none): $ df -h /boot Filesystem Size Used Avail Use% Mounted on /dev/sdb2 707M 693M 0 100% /boot What is required is to remove older kernels (and purge them most likely). List all the installed kernels except the current one: $ dpkg -l 'linux-*' | sed '/^ii/!d;/'"$(uname -r | sed "s/\(.*\)-\([^0-9]\+\)/\1/")"'/d;s/^[^ ]* [^ ]* \([^ ]*\).*/\1/;/[0-9]/!d' linux-headers-6.2.0-23 linux-headers-6.2.0-23-generic linux-headers-6.2.0-25 linux-headers-6.2.0-25-generic linux-image-6.2.0-23-generic linux-libc-dev:amd64 linux-libc-dev:i386 linux-modules-6.2.0-23-generic linux-modules-6.2.0-25-generic linux-modules-extra-6.2.0-23-generic linux-modules-extra-6.2.0-25-generic Is not possible to uninstall any kernel because fails: $ sudo apt purge linux-headers-6.2.0-23 E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. Reconfigure fails again so some kernel have to be manually removed to free up space: $ sudo rm /boot/initrd.img-6.2.0-23-generic $ sudo rm -rf /boot/initrd.img-6.2.0-25-generic.new Now you can reconfigure: $ Remove kernels: $ sudo apt purge linux-headers-6.2.0-23 linux-headers-6.2.0-23-generic linux-headers-6.2.0-25 linux-headers-6.2.0-25-generic linux-image-6.2.0-23-generic linux-modules-6.2.0-23-generic linux-modules-6.2.0-25-generic linux-modules-extra-6.2.0-23-generic linux-modules-extra-6.2.0-25-generic Reboot: $ sudo reboot Upgrade as usual: $ sudo apt update && sudo apt upgrade Before upgrading new kernels I need to check for free space and remove older kernels manually. Fix this so there's only one kernel left. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2027847/+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 2027847] Re: Updating kernel does not check for free space left on device beforehand
> APT only keeps 2 kernel versions around Yes, but when installing a new kernel, it does not remove beforehand the oldest kernel, so there's a situation where there are 3 kernels installed at the same time, until you reboot and run upgrade again. ** Summary changed: - Updating kernel does not check for free space left on device beforehand + APT installs 3 kernels at once so /boot runs out of free space left and partition size does not increase alongside with newer ubuntu versions -- 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/2027847 Title: APT installs 3 kernels at once so /boot runs out of free space left and partition size does not increase alongside with newer ubuntu versions Status in apt package in Ubuntu: Won't Fix Status in dpkg package in Ubuntu: Invalid Status in kernel-package package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in linux-firmware package in Ubuntu: Invalid Status in linux-kernel-headers package in Ubuntu: Invalid Status in linux-restricted-modules package in Ubuntu: Invalid Bug description: System information: ubuntu 23.04 x86_64 6.2.0-24-generic Upgrading the system: $ sudo dpkg --configure -a Setting up linux-firmware (20230323.gitbcdcfbcf-0ubuntu1.2) ... update-initramfs: Generating /boot/initrd.img-6.2.0-24-generic I: The initramfs will attempt to resume from /dev/dm-2 I: (/dev/mapper/ubuntu--vg-swap_1) I: Set the RESUME variable to override this. zstd: error 70 : Write error : cannot write block : No space left on device E: mkinitramfs failure zstd -q -1 -T0 70 Check space left (none): $ df -h /boot Filesystem Size Used Avail Use% Mounted on /dev/sdb2 707M 693M 0 100% /boot What is required is to remove older kernels (and purge them most likely). List all the installed kernels except the current one: $ dpkg -l 'linux-*' | sed '/^ii/!d;/'"$(uname -r | sed "s/\(.*\)-\([^0-9]\+\)/\1/")"'/d;s/^[^ ]* [^ ]* \([^ ]*\).*/\1/;/[0-9]/!d' linux-headers-6.2.0-23 linux-headers-6.2.0-23-generic linux-headers-6.2.0-25 linux-headers-6.2.0-25-generic linux-image-6.2.0-23-generic linux-libc-dev:amd64 linux-libc-dev:i386 linux-modules-6.2.0-23-generic linux-modules-6.2.0-25-generic linux-modules-extra-6.2.0-23-generic linux-modules-extra-6.2.0-25-generic Is not possible to uninstall any kernel because fails: $ sudo apt purge linux-headers-6.2.0-23 E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. Reconfigure fails again so some kernel have to be manually removed to free up space: $ sudo rm /boot/initrd.img-6.2.0-23-generic $ sudo rm -rf /boot/initrd.img-6.2.0-25-generic.new Now you can reconfigure: $ Remove kernels: $ sudo apt purge linux-headers-6.2.0-23 linux-headers-6.2.0-23-generic linux-headers-6.2.0-25 linux-headers-6.2.0-25-generic linux-image-6.2.0-23-generic linux-modules-6.2.0-23-generic linux-modules-6.2.0-25-generic linux-modules-extra-6.2.0-23-generic linux-modules-extra-6.2.0-25-generic Reboot: $ sudo reboot Upgrade as usual: $ sudo apt update && sudo apt upgrade Before upgrading new kernels I need to check for free space and remove older kernels manually. Fix this so there's only one kernel left. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2027847/+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 2027847] Re: Updating kernel does not check for free space left on device beforehand
There are 3 kernels installed: 6.2.0-24-generic (running) linux-image-6.2.0-23-generic /boot/initrd.img-6.2.0-25-generic.new (file 225MB placed by apt upgrade but remember the upgrade broke). The /boot partition is sized for 3, but maybe today in 2023. This ubuntu system has been being upgraded for several years, so maybe back in the day a kernel image didn't weight 200+ MB but 100MB. So now I have the problem that I must resize the partition, because kernels are only getting bigger. With time, my 707M /boot partition will only be fit for one kernel, maybe ubuntu 26.10 or whatever it be. -- 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/2027847 Title: APT installs 3 kernels at once so /boot runs out of free space left and partition size does not increase alongside with newer ubuntu versions Status in apt package in Ubuntu: Won't Fix Status in dpkg package in Ubuntu: Invalid Status in kernel-package package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in linux-firmware package in Ubuntu: Invalid Status in linux-kernel-headers package in Ubuntu: Invalid Status in linux-restricted-modules package in Ubuntu: Invalid Bug description: System information: ubuntu 23.04 x86_64 6.2.0-24-generic Upgrading the system: $ sudo dpkg --configure -a Setting up linux-firmware (20230323.gitbcdcfbcf-0ubuntu1.2) ... update-initramfs: Generating /boot/initrd.img-6.2.0-24-generic I: The initramfs will attempt to resume from /dev/dm-2 I: (/dev/mapper/ubuntu--vg-swap_1) I: Set the RESUME variable to override this. zstd: error 70 : Write error : cannot write block : No space left on device E: mkinitramfs failure zstd -q -1 -T0 70 Check space left (none): $ df -h /boot Filesystem Size Used Avail Use% Mounted on /dev/sdb2 707M 693M 0 100% /boot What is required is to remove older kernels (and purge them most likely). List all the installed kernels except the current one: $ dpkg -l 'linux-*' | sed '/^ii/!d;/'"$(uname -r | sed "s/\(.*\)-\([^0-9]\+\)/\1/")"'/d;s/^[^ ]* [^ ]* \([^ ]*\).*/\1/;/[0-9]/!d' linux-headers-6.2.0-23 linux-headers-6.2.0-23-generic linux-headers-6.2.0-25 linux-headers-6.2.0-25-generic linux-image-6.2.0-23-generic linux-libc-dev:amd64 linux-libc-dev:i386 linux-modules-6.2.0-23-generic linux-modules-6.2.0-25-generic linux-modules-extra-6.2.0-23-generic linux-modules-extra-6.2.0-25-generic Is not possible to uninstall any kernel because fails: $ sudo apt purge linux-headers-6.2.0-23 E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. Reconfigure fails again so some kernel have to be manually removed to free up space: $ sudo rm /boot/initrd.img-6.2.0-23-generic $ sudo rm -rf /boot/initrd.img-6.2.0-25-generic.new Now you can reconfigure: $ Remove kernels: $ sudo apt purge linux-headers-6.2.0-23 linux-headers-6.2.0-23-generic linux-headers-6.2.0-25 linux-headers-6.2.0-25-generic linux-image-6.2.0-23-generic linux-modules-6.2.0-23-generic linux-modules-6.2.0-25-generic linux-modules-extra-6.2.0-23-generic linux-modules-extra-6.2.0-25-generic Reboot: $ sudo reboot Upgrade as usual: $ sudo apt update && sudo apt upgrade Before upgrading new kernels I need to check for free space and remove older kernels manually. Fix this so there's only one kernel left. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2027847/+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 2027847] [NEW] Updating kernel does not check for free space left on device beforehand
Public bug reported: System information: ubuntu 23.04 x86_64 6.2.0-24-generic Upgrading the system: $ sudo dpkg --configure -a Setting up linux-firmware (20230323.gitbcdcfbcf-0ubuntu1.2) ... update-initramfs: Generating /boot/initrd.img-6.2.0-24-generic I: The initramfs will attempt to resume from /dev/dm-2 I: (/dev/mapper/ubuntu--vg-swap_1) I: Set the RESUME variable to override this. zstd: error 70 : Write error : cannot write block : No space left on device E: mkinitramfs failure zstd -q -1 -T0 70 Check space left (none): $ df -h /boot Filesystem Size Used Avail Use% Mounted on /dev/sdb2 707M 693M 0 100% /boot What is required is to remove older kernels (and purge them most likely). List all the installed kernels except the current one: $ dpkg -l 'linux-*' | sed '/^ii/!d;/'"$(uname -r | sed "s/\(.*\)-\([^0-9]\+\)/\1/")"'/d;s/^[^ ]* [^ ]* \([^ ]*\).*/\1/;/[0-9]/!d' linux-headers-6.2.0-23 linux-headers-6.2.0-23-generic linux-headers-6.2.0-25 linux-headers-6.2.0-25-generic linux-image-6.2.0-23-generic linux-libc-dev:amd64 linux-libc-dev:i386 linux-modules-6.2.0-23-generic linux-modules-6.2.0-25-generic linux-modules-extra-6.2.0-23-generic linux-modules-extra-6.2.0-25-generic Is not possible to uninstall any kernel because fails: $ sudo apt purge linux-headers-6.2.0-23 E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. Reconfigure fails again so some kernel have to be manually removed to free up space: $ sudo rm /boot/initrd.img-6.2.0-23-generic $ sudo rm -rf /boot/initrd.img-6.2.0-25-generic.new Now you can reconfigure: $ Remove kernels: $ sudo apt purge linux-headers-6.2.0-23 linux-headers-6.2.0-23-generic linux-headers-6.2.0-25 linux-headers-6.2.0-25-generic linux-image-6.2.0-23-generic linux-modules-6.2.0-23-generic linux-modules-6.2.0-25-generic linux-modules-extra-6.2.0-23-generic linux-modules-extra-6.2.0-25-generic Reboot: $ sudo reboot Upgrade as usual: $ sudo apt update && sudo apt upgrade Before upgrading new kernels I need to check for free space and remove older kernels manually. Fix this so there's only one kernel left. ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Affects: dpkg (Ubuntu) Importance: Undecided Status: New ** Affects: kernel-package (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Affects: linux-kernel-headers (Ubuntu) Importance: Undecided Status: New ** Affects: linux-restricted-modules (Ubuntu) Importance: Undecided Status: New ** Tags: 23.04 apt dpkg linux-headers linux-image linux-modules ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-kernel-headers (Ubuntu) Importance: Undecided Status: New ** Also affects: kernel-package (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-restricted-modules (Ubuntu) Importance: Undecided Status: New ** Also affects: dpkg (Ubuntu) Importance: Undecided Status: New ** Also affects: apt (Ubuntu) Importance: Undecided Status: New ** Tags added: 23.04 ** Tags added: linux-headers linux-image linux-modules ** Tags added: apt dpkg -- 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/2027847 Title: Updating kernel does not check for free space left on device beforehand Status in apt package in Ubuntu: New Status in dpkg package in Ubuntu: New Status in kernel-package package in Ubuntu: New Status in linux package in Ubuntu: New Status in linux-firmware package in Ubuntu: New Status in linux-kernel-headers package in Ubuntu: New Status in linux-restricted-modules package in Ubuntu: New Bug description: System information: ubuntu 23.04 x86_64 6.2.0-24-generic Upgrading the system: $ sudo dpkg --configure -a Setting up linux-firmware (20230323.gitbcdcfbcf-0ubuntu1.2) ... update-initramfs: Generating /boot/initrd.img-6.2.0-24-generic I: The initramfs will attempt to resume from /dev/dm-2 I: (/dev/mapper/ubuntu--vg-swap_1) I: Set the RESUME variable to override this. zstd: error 70 : Write error : cannot write block : No space left on device E: mkinitramfs failure zstd -q -1 -T0 70 Check space left (none): $ df -h /boot Filesystem Size Used Avail Use% Mounted on /dev/sdb2 707M 693M 0 100% /boot What is required is to remove older kernels (and purge them most likely). List all the installed kernels except the current one: $ dpkg -l 'linux-*' | sed '/^ii/!d;/'"$(uname -r | sed "s/\(.*\)-\([^0-9]\+\)/\1/")"'/d;s/^[^ ]* [^ ]* \([^ ]*\).*/\1/;/[0-9]/!d' linux-headers-6.2.0-23 linux-headers-6.2.0-23-generic
[Touch-packages] [Bug 1840592] Re: systemd-backlight does not save and restore brightness for nvidia display
@ayush-akarsh try this command to get and set backlight. Works for me on nvidia. xbacklight -get xbacklight -set 40 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1840592 Title: systemd-backlight does not save and restore brightness for nvidia display Status in nvidia-graphics-drivers package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Status in nvidia-settings package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: Running nvidia gtx 1080 graphics card, with proprietary nvidia drivers on ubuntu 19.04. I can change screen brightness from 0% to 100% in 5% steps. However, after a reboot or after a shutdown, brightness level reverts to 100%. Please fix to is "remembers" the current brightness value at shutdown time, like in does Windows. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1840592/+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 1840592] Re: systemd-backlight does not save and restore brightness for nvidia display
Has anybody checked how other distros operate this? Maybe Debian/Kali? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1840592 Title: systemd-backlight does not save and restore brightness for nvidia display Status in nvidia-graphics-drivers package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Status in nvidia-settings package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: Running nvidia gtx 1080 graphics card, with proprietary nvidia drivers on ubuntu 19.04. I can change screen brightness from 0% to 100% in 5% steps. However, after a reboot or after a shutdown, brightness level reverts to 100%. Please fix to is "remembers" the current brightness value at shutdown time, like in does Windows. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1840592/+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 1840592] Re: systemd-backlight does not save and restore brightness for nvidia display
Well, apparently Nvidia driver doesn't do that. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1840592 Title: systemd-backlight does not save and restore brightness for nvidia display Status in nvidia-graphics-drivers package in Ubuntu: New Status in nvidia-graphics-drivers-418 package in Ubuntu: New Status in nvidia-settings package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Running nvidia gtx 1080 graphics card, with proprietary nvidia drivers on ubuntu 19.04. I can change screen brightness from 0% to 100% in 5% steps. However, after a reboot or after a shutdown, brightness level reverts to 100%. Please fix to is "remembers" the current brightness value at shutdown time, like in does Windows. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1840592/+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 1840592] Re: systemd-backlight does not save and restore brightness for nvidia display
systemctl list-units --no-pager |grep "systemd-backlight" systemd-backlight@backlight:acpi_video0.service loaded active exitedLoad/Save Screen Backlight Brightness of backlight:acpi_video0 systemd-backlight@backlight:nvidia_0.service loaded active exitedLoad/Save Screen Backlight Brightness of backlight:nvidia_0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1840592 Title: systemd-backlight does not save and restore brightness for nvidia display Status in nvidia-graphics-drivers package in Ubuntu: New Status in nvidia-graphics-drivers-418 package in Ubuntu: New Status in nvidia-settings package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Running nvidia gtx 1080 graphics card, with proprietary nvidia drivers on ubuntu 19.04. I can change screen brightness from 0% to 100% in 5% steps. However, after a reboot or after a shutdown, brightness level reverts to 100%. Please fix to is "remembers" the current brightness value at shutdown time, like in does Windows. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1840592/+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 1840592] Re: systemd-backlight does not save and restore brightness for nvidia display
The notebook has 2 gpus, one is from the intel cpu and another is nvidia which can be enabled or disable on bios on section "MSI VGA MODE" and choose "MSI IGPU MODE" or "MSI DGPU MODE" -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1840592 Title: systemd-backlight does not save and restore brightness for nvidia display Status in nvidia-graphics-drivers package in Ubuntu: New Status in nvidia-graphics-drivers-418 package in Ubuntu: New Status in nvidia-settings package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Running nvidia gtx 1080 graphics card, with proprietary nvidia drivers on ubuntu 19.04. I can change screen brightness from 0% to 100% in 5% steps. However, after a reboot or after a shutdown, brightness level reverts to 100%. Please fix to is "remembers" the current brightness value at shutdown time, like in does Windows. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1840592/+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 1840592] Re: systemd-backlight does not save and restore brightness for nvidia display
** Summary changed: - systemd-backlight does not save&restore brightness for nvidia display + systemd-backlight does not save and restore brightness for nvidia display -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1840592 Title: systemd-backlight does not save and restore brightness for nvidia display Status in nvidia-graphics-drivers package in Ubuntu: New Status in nvidia-graphics-drivers-418 package in Ubuntu: New Status in nvidia-settings package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Running nvidia gtx 1080 graphics card, with proprietary nvidia drivers on ubuntu 19.04. I can change screen brightness from 0% to 100% in 5% steps. However, after a reboot or after a shutdown, brightness level reverts to 100%. Please fix to is "remembers" the current brightness value at shutdown time, like in does Windows. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1840592/+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 1840592] Re: systemd-backlight does not save&restore brightness for nvidia display
** Summary changed: - display brightness not restored on next boot resets to 100 + systemd-backlight does not save&restore brightness for nvidia display -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1840592 Title: systemd-backlight does not save and restore brightness for nvidia display Status in nvidia-graphics-drivers package in Ubuntu: New Status in nvidia-graphics-drivers-418 package in Ubuntu: New Status in nvidia-settings package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Running nvidia gtx 1080 graphics card, with proprietary nvidia drivers on ubuntu 19.04. I can change screen brightness from 0% to 100% in 5% steps. However, after a reboot or after a shutdown, brightness level reverts to 100%. Please fix to is "remembers" the current brightness value at shutdown time, like in does Windows. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1840592/+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 1840592] Re: display brightness not restored on next boot resets to 100
/lib/systemd/system/systemd-backlight@.service NOT working properly with nvidia cards. ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1840592 Title: display brightness not restored on next boot resets to 100 Status in nvidia-graphics-drivers package in Ubuntu: New Status in nvidia-graphics-drivers-418 package in Ubuntu: New Status in nvidia-settings package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Running nvidia gtx 1080 graphics card, with proprietary nvidia drivers on ubuntu 19.04. I can change screen brightness from 0% to 100% in 5% steps. However, after a reboot or after a shutdown, brightness level reverts to 100%. Please fix to is "remembers" the current brightness value at shutdown time, like in does Windows. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1840592/+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 1833532] Re: systemd-backlight does not restore screen brightness after reboot
Still affected. https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1840592 ** Changed in: systemd (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1833532 Title: systemd-backlight does not restore screen brightness after reboot Status in systemd package in Ubuntu: Confirmed Bug description: As the title says, on this laptop the brightness controls are NOT saved after reboot. What is saved instead, is only the keyboard brightness. I have tested two distros, Ubuntu 18.04.2 LTS and 19.04, happens on both systems. But there is a difference On 19.04, "systemctl status systemd-backlight@:*intel_screen_backlight_*" shows: "Saved brightness 20 too low, increasing to 75" On 18.04.2 does not show anything rather than the service starting normally The laptop is a Dell XPS 15 9550, the screen backlight driver is the intel one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1833532/+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 1773651] Re: xserver-xorg-video-nouveau is required with nouveau driver to display properly gnome apps
It happens with Gnome and Plasma, for gnome apps like synaptics, etc. I can't even login to Wayland, the screen goes black just after entering my user's password and clicking enter. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1773651 Title: xserver-xorg-video-nouveau is required with nouveau driver to display properly gnome apps Status in gnome-desktop package in Ubuntu: Incomplete Status in nautilus package in Ubuntu: Incomplete Status in software-properties package in Ubuntu: Incomplete Status in xserver-xorg-video-nouveau package in Ubuntu: Incomplete Bug description: When I switch from nvidia to nouveau from software-properties-gtk and reboot, with the nouveau driver already running, I experience graphic glitches on gnome apps. This is due to "xserver-xorg-video-nouveau" missing. See bugs here: https://bugs.freedesktop.org/show_bug.cgi?id=106657 https://gitlab.gnome.org/GNOME/nautilus/issues/426 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop/+bug/1773651/+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 1773651] Re: xserver-xorg-video-nouveau is required with nouveau driver to display properly gnome apps
What information do you need to know exactly? It's a nvidia gtx 10 series -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1773651 Title: xserver-xorg-video-nouveau is required with nouveau driver to display properly gnome apps Status in gnome-desktop package in Ubuntu: Incomplete Status in nautilus package in Ubuntu: Incomplete Status in software-properties package in Ubuntu: Incomplete Status in xserver-xorg-video-nouveau package in Ubuntu: Incomplete Bug description: When I switch from nvidia to nouveau from software-properties-gtk and reboot, with the nouveau driver already running, I experience graphic glitches on gnome apps. This is due to "xserver-xorg-video-nouveau" missing. See bugs here: https://bugs.freedesktop.org/show_bug.cgi?id=106657 https://gitlab.gnome.org/GNOME/nautilus/issues/426 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop/+bug/1773651/+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 1773693] [NEW] xserver-xorg-video-nouveau requires reboot to apply changes
Public bug reported: Using update-manager to install or update xserver-xorg-video-nouveau should prompt to reboot ** Affects: plasma-discover (Ubuntu) Importance: Undecided Status: New ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Affects: synaptic (Ubuntu) Importance: Undecided Status: New ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New ** Also affects: update-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1773693 Title: xserver-xorg-video-nouveau requires reboot to apply changes Status in plasma-discover package in Ubuntu: New Status in software-properties package in Ubuntu: New Status in synaptic package in Ubuntu: New Status in update-manager package in Ubuntu: New Bug description: Using update-manager to install or update xserver-xorg-video-nouveau should prompt to reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-discover/+bug/1773693/+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 1773693] Re: xserver-xorg-video-nouveau requires reboot to apply changes
Also with plasma-discover ** Also affects: plasma-discover (Ubuntu) Importance: Undecided Status: New ** Also affects: synaptic (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1773693 Title: xserver-xorg-video-nouveau requires reboot to apply changes Status in plasma-discover package in Ubuntu: New Status in software-properties package in Ubuntu: New Status in synaptic package in Ubuntu: New Status in update-manager package in Ubuntu: New Bug description: Using update-manager to install or update xserver-xorg-video-nouveau should prompt to reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-discover/+bug/1773693/+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 1773651] Re: xserver-xorg-video-nouveau is required with nouveau driver to display properly gnome apps
It should be installed somehow. When I installed ubuntu I was running the discrete graphics card so nvidia proprietary drivers installed automatically. Then I wanted to switch to nouveau and that package is missing. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1773651 Title: xserver-xorg-video-nouveau is required with nouveau driver to display properly gnome apps Status in gnome-desktop package in Ubuntu: New Status in nautilus package in Ubuntu: New Status in software-properties package in Ubuntu: New Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description: When I switch from nvidia to nouveau from software-properties-gtk and reboot, with the nouveau driver already running, I experience graphic glitches on gnome apps. This is due to "xserver-xorg-video-nouveau" missing. See bugs here: https://bugs.freedesktop.org/show_bug.cgi?id=106657 https://gitlab.gnome.org/GNOME/nautilus/issues/426 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop/+bug/1773651/+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 1773651] [NEW] xserver-xorg-video-nouveau is required with nouveau driver to display properly gnome apps
Public bug reported: When I switch from nvidia to nouveau from software-properties-gtk and reboot, with the nouveau driver already running, I experience graphic glitches on gnome apps. This is due to "xserver-xorg-video-nouveau" missing. See bugs here: https://bugs.freedesktop.org/show_bug.cgi?id=106657 https://gitlab.gnome.org/GNOME/nautilus/issues/426 ** Affects: gnome-desktop (Ubuntu) Importance: Undecided Status: New ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Affects: xserver-xorg-video-nouveau (Ubuntu) Importance: Undecided Status: New ** Also affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Also affects: xserver-xorg-video-nouveau (Ubuntu) Importance: Undecided Status: New ** Also affects: gnome-desktop (Ubuntu) Importance: Undecided Status: New ** Summary changed: - xserver-xorg-video-nouveau is required to display properly gnome graphics with nouveau driver + xserver-xorg-video-nouveau is required with nouveau driver to display properly gnome apps -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1773651 Title: xserver-xorg-video-nouveau is required with nouveau driver to display properly gnome apps Status in gnome-desktop package in Ubuntu: New Status in nautilus package in Ubuntu: New Status in software-properties package in Ubuntu: New Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description: When I switch from nvidia to nouveau from software-properties-gtk and reboot, with the nouveau driver already running, I experience graphic glitches on gnome apps. This is due to "xserver-xorg-video-nouveau" missing. See bugs here: https://bugs.freedesktop.org/show_bug.cgi?id=106657 https://gitlab.gnome.org/GNOME/nautilus/issues/426 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop/+bug/1773651/+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 1769338] Re: software-properties-gtk gets stuck when switching from nvidia to nouveau and vice-versa
Ok waiting for update, already on bionic-proposal. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1769338 Title: software-properties-gtk gets stuck when switching from nvidia to nouveau and vice-versa Status in software-properties package in Ubuntu: New Bug description: Switching from nvidia to nouveau makes the gui to get stuck at "Applying changes..." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1769338/+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 1753333] Re: Using "Software and Updates -> Additional Drivers" to Switch Fails
Running bionic-proposed here and still can't see software-properties (0.96.24.33): root@ubuntu:~# dpkg -l | grep software-properties ii python3-software-properties 0.96.24.32.2 all manage the repositories that you install software from ii software-properties-common 0.96.24.32.2 all manage the repositories that you install software from (common) ii software-properties-gtk 0.96.24.32.2 all manage the repositories that you install software from (gtk) ii software-properties-kde 0.96.24.32.2 all manage the repositories that you install software from (qt) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/175 Title: Using "Software and Updates -> Additional Drivers" to Switch Fails Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Bionic: Fix Committed Bug description: SRU Request: [Impact] Currently, the Additional Drivers tool uninstalls only the driver package that ships the modaliases. When it comes to the NVIDIA drivers (>=390), that package is only a meta-package. Removing the meta-package will not uninstall the driver. We should make sure to uninstall all its nvidia related dependencies, not only the meta-package. [Test Case] 1) Open the "Software & Updates" app, and select the "Additional Drivers" tab 2) Uninstall the NVIDIA 390 driver 3) Check that, for example, the nvidia-dkms-390 package was uninstalled: apt-cache policy nvidia-dkms-390 The package will be reported as installed, because the current code didn't remove it. [Regression Potential] Relatively low, as the change in behaviour only affects the nvidia driver, and it only causes the Additional Drivers tool to remove dependencies of the meta-package that have the "nvidia" string in their name. __ When you are in the initial install state, you can easily switch from the Nouvea drivers to the Nvidia drivers by choosing the option in "Software and Updates -> Additional Drivers". However, when you attempt to switch back (by selecting the nouveau option and clicking Apply), and subsequently reboot, your system will still come up using the Nvidia drivers, and you will WTF. And then, if you visit Additional Drivers, you will be presented with grayed out options for both nvidia and nouvea, and the only selectable option will be "continue using manually installed driver". The reason for this is that the tool, when reselecting nvidia in the GUI, uninstalls the nvidia-drivers-390 package, but because it's a metapackage (or at least I presume this is the reason), it doesn't uninstall its dependencies, which causes the Additional Drivers tool to believe it's in a non-automanaged state, and the nvidia drivers never actually get uninstalled. You can fix it by doing an apt autoremove and rerunning the Additional Drivers tool. But obviously there is no real way for inexperienced users to know this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/175/+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 1753333] Re: Using "Software and Updates -> Additional Drivers" to Switch Fails
I'm also affected: https://bugs.launchpad.net/ubuntu/+source/software- properties/+bug/1769338 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/175 Title: Using "Software and Updates -> Additional Drivers" to Switch Fails Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Bionic: Fix Committed Bug description: SRU Request: [Impact] Currently, the Additional Drivers tool uninstalls only the driver package that ships the modaliases. When it comes to the NVIDIA drivers (>=390), that package is only a meta-package. Removing the meta-package will not uninstall the driver. We should make sure to uninstall all its nvidia related dependencies, not only the meta-package. [Test Case] 1) Open the "Software & Updates" app, and select the "Additional Drivers" tab 2) Uninstall the NVIDIA 390 driver 3) Check that, for example, the nvidia-dkms-390 package was uninstalled: apt-cache policy nvidia-dkms-390 The package will be reported as installed, because the current code didn't remove it. [Regression Potential] Relatively low, as the change in behaviour only affects the nvidia driver, and it only causes the Additional Drivers tool to remove dependencies of the meta-package that have the "nvidia" string in their name. __ When you are in the initial install state, you can easily switch from the Nouvea drivers to the Nvidia drivers by choosing the option in "Software and Updates -> Additional Drivers". However, when you attempt to switch back (by selecting the nouveau option and clicking Apply), and subsequently reboot, your system will still come up using the Nvidia drivers, and you will WTF. And then, if you visit Additional Drivers, you will be presented with grayed out options for both nvidia and nouvea, and the only selectable option will be "continue using manually installed driver". The reason for this is that the tool, when reselecting nvidia in the GUI, uninstalls the nvidia-drivers-390 package, but because it's a metapackage (or at least I presume this is the reason), it doesn't uninstall its dependencies, which causes the Additional Drivers tool to believe it's in a non-automanaged state, and the nvidia drivers never actually get uninstalled. You can fix it by doing an apt autoremove and rerunning the Additional Drivers tool. But obviously there is no real way for inexperienced users to know this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/175/+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 1769338] Re: software-properties-gtk gets stuck when switching from nvidia to nouveau and vice-versa
Ok waiting for update, already on bionic-proposal. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1769338 Title: software-properties-gtk gets stuck when switching from nvidia to nouveau and vice-versa Status in software-properties package in Ubuntu: New Bug description: Switching from nvidia to nouveau makes the gui to get stuck at "Applying changes..." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1769338/+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 1769338] Re: software-properties-gtk gets stuck when switching from nvidia to nouveau
root@ubuntu:~# ubuntu-drivers list nvidia-driver-390 root@ubuntu:~# -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1769338 Title: software-properties-gtk gets stuck when switching from nvidia to nouveau and vice-versa Status in software-properties package in Ubuntu: New Bug description: Switching from nvidia to nouveau makes the gui to get stuck at "Applying changes..." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1769338/+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 1769338] Re: software-properties-gtk gets stuck when switching from nvidia to nouveau
** Attachment added: "software-properties-gtk_halts-when-changing.png" https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1769338/+attachment/5134299/+files/software-properties-gtk_halts-when-changing.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1769338 Title: software-properties-gtk gets stuck when switching from nvidia to nouveau and vice-versa Status in software-properties package in Ubuntu: New Bug description: Switching from nvidia to nouveau makes the gui to get stuck at "Applying changes..." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1769338/+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 1769338] Re: software-properties-gtk gets stuck when switching from nvidia to nouveau
If I click Cancel and select nvidia and apply same problem, stays there forever. ** Summary changed: - software-properties-gtk gets stuck when switching from nvidia to nouveau + software-properties-gtk gets stuck when switching from nvidia to nouveau and vice-versa -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1769338 Title: software-properties-gtk gets stuck when switching from nvidia to nouveau and vice-versa Status in software-properties package in Ubuntu: New Bug description: Switching from nvidia to nouveau makes the gui to get stuck at "Applying changes..." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1769338/+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 1769338] [NEW] software-properties-gtk gets stuck when switching from nvidia to nouveau and vice-versa
Public bug reported: Switching from nvidia to nouveau makes the gui to get stuck at "Applying changes..." ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1769338 Title: software-properties-gtk gets stuck when switching from nvidia to nouveau and vice-versa Status in software-properties package in Ubuntu: New Bug description: Switching from nvidia to nouveau makes the gui to get stuck at "Applying changes..." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1769338/+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 1768764] Re: disable wayland by default - nvidia proprietary drivers backlight
Don't mess the system until it's 100% functional. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1768764 Title: disable wayland by default - nvidia proprietary drivers backlight Status in wayland package in Ubuntu: New Bug description: With wayland can't control screen brightness using nvidia proprietary drivers. The screen brightness is always at 100%. Please DON'T enable wayland by default on fresh installations or updates because it's not 100% compatible with nvidia proprietary drivers. Nouveau still doesn't support backlight control on Pascal cards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1768764/+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 1768764] [NEW] disable wayland by default - nvidia proprietary drivers backlight
Public bug reported: With wayland can't control screen brightness using nvidia proprietary drivers. The screen brightness is always at 100%. Please DON'T enable wayland by default on fresh installations or updates because it's not 100% compatible with nvidia proprietary drivers. Nouveau still doesn't support backlight control on Pascal cards. ** Affects: wayland (Ubuntu) Importance: Undecided Status: New ** Summary changed: - disable wayland by default because nvidia backlight doesn't work + disable wayland by default - nvidia proprietary drivers backlight -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1768764 Title: disable wayland by default - nvidia proprietary drivers backlight Status in wayland package in Ubuntu: New Bug description: With wayland can't control screen brightness using nvidia proprietary drivers. The screen brightness is always at 100%. Please DON'T enable wayland by default on fresh installations or updates because it's not 100% compatible with nvidia proprietary drivers. Nouveau still doesn't support backlight control on Pascal cards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1768764/+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 1762010] [NEW] auto-recognize bitlocker partitions and drives
Public bug reported: I would like that ubuntu detects when a drive or partition is protected by bitlocker, so prompts for password after clicking on the unit icon, from any filesystem manager like nautilus or dolphin. Basically, replicate the Windows behavior would be the ideal. The automatic recognition helps prevent users from wiping the drive or partition in case they think it's unformatted. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Bitlocker prompt to enter decrypt password." https://bugs.launchpad.net/bugs/1762010/+attachment/5105771/+files/bitlocker-preboot-password-entry.png ** Package changed: apt (Ubuntu) => nautilus (Ubuntu) -- 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/1762010 Title: auto-recognize bitlocker partitions and drives Status in nautilus package in Ubuntu: New Bug description: I would like that ubuntu detects when a drive or partition is protected by bitlocker, so prompts for password after clicking on the unit icon, from any filesystem manager like nautilus or dolphin. Basically, replicate the Windows behavior would be the ideal. The automatic recognition helps prevent users from wiping the drive or partition in case they think it's unformatted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1762010/+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 1649086] Re: W: Invalid 'Date' entry in Release file /var/lib/apt/lists/developer.download.nvidia.com_compute_cuda_repos_ubuntu1604_x86%5f64_Release
Ok who is the developer of that repository? -- 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/1649086 Title: W: Invalid 'Date' entry in Release file /var/lib/apt/lists/developer.download.nvidia.com_compute_cuda_repos_ubuntu1604_x86%5f64_Release Status in apt package in Ubuntu: Invalid Bug description: root@ubuntu:/var/lib/apt/lists# apt-get update Hit:1 http://ppa.launchpad.net/stefansundin/truecrypt/ubuntu yakkety InRelease Hit:3 http://ppa.launchpad.net/unit193/encryption/ubuntu yakkety InRelease Hit:4 http://es.archive.ubuntu.com/ubuntu yakkety InRelease Hit:5 http://repository.spotify.com stable InRelease Hit:6 http://ppa.launchpad.net/wine/wine-builds/ubuntu yakkety InRelease Get:7 http://es.archive.ubuntu.com/ubuntu yakkety-updates InRelease [102 kB] Get:8 http://security.ubuntu.com/ubuntu yakkety-security InRelease [102 kB] Get:9 http://es.archive.ubuntu.com/ubuntu yakkety-backports InRelease [102 kB] Hit:2 http://screenshots.getdeb.net yakkety-getdeb InRelease Ign:10 http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1604/x86_64 InRelease Hit:11 http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1604/x86_64 Release Fetched 306 kB in 1s (242 kB/s) Reading package lists... Done W: Invalid 'Date' entry in Release file /var/lib/apt/lists/developer.download.nvidia.com_compute_cuda_repos_ubuntu1604_x86%5f64_Release root@ubuntu:/var/lib/apt/lists# The file is as 'developer.download.nvidia.com_compute_cuda_repos_ubuntu1604_x86%5f64_Release' follows: Origin: NVIDIA Label: NVIDIA CUDA Architecture: x86_64 Date: Fri, 23 Sep 2016 18:52:52 -0700 MD5Sum: 3213a453e90b070bc10f329d2fe7f1a384080 Packages c1660fe24223ec9b07b04de1dfb3777122493 Packages.gz SHA1: 60f8bd97333efb0bce147702712aab654ba3469b84080 Packages 04e6ceaf9bcbcd3b36a9cc390b58110da138b7cd22493 Packages.gz SHA256: 44a4473829b9403e7e2d36c43757b4d4ce8334b5804d90d920bd92edaf346241 84080 Packages f179e19b7c5b47d5c7247b5d6f37eb2ab2fba168ac70531dd02a0a1cda756038 22493 Packages.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1649086/+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 1649086] [NEW] W: Invalid 'Date' entry in Release file /var/lib/apt/lists/developer.download.nvidia.com_compute_cuda_repos_ubuntu1604_x86%5f64_Release
Public bug reported: root@ubuntu:/var/lib/apt/lists# apt-get update Hit:1 http://ppa.launchpad.net/stefansundin/truecrypt/ubuntu yakkety InRelease Hit:3 http://ppa.launchpad.net/unit193/encryption/ubuntu yakkety InRelease Hit:4 http://es.archive.ubuntu.com/ubuntu yakkety InRelease Hit:5 http://repository.spotify.com stable InRelease Hit:6 http://ppa.launchpad.net/wine/wine-builds/ubuntu yakkety InRelease Get:7 http://es.archive.ubuntu.com/ubuntu yakkety-updates InRelease [102 kB] Get:8 http://security.ubuntu.com/ubuntu yakkety-security InRelease [102 kB] Get:9 http://es.archive.ubuntu.com/ubuntu yakkety-backports InRelease [102 kB] Hit:2 http://screenshots.getdeb.net yakkety-getdeb InRelease Ign:10 http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1604/x86_64 InRelease Hit:11 http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1604/x86_64 Release Fetched 306 kB in 1s (242 kB/s) Reading package lists... Done W: Invalid 'Date' entry in Release file /var/lib/apt/lists/developer.download.nvidia.com_compute_cuda_repos_ubuntu1604_x86%5f64_Release root@ubuntu:/var/lib/apt/lists# The file is as 'developer.download.nvidia.com_compute_cuda_repos_ubuntu1604_x86%5f64_Release' follows: Origin: NVIDIA Label: NVIDIA CUDA Architecture: x86_64 Date: Fri, 23 Sep 2016 18:52:52 -0700 MD5Sum: 3213a453e90b070bc10f329d2fe7f1a384080 Packages c1660fe24223ec9b07b04de1dfb3777122493 Packages.gz SHA1: 60f8bd97333efb0bce147702712aab654ba3469b84080 Packages 04e6ceaf9bcbcd3b36a9cc390b58110da138b7cd22493 Packages.gz SHA256: 44a4473829b9403e7e2d36c43757b4d4ce8334b5804d90d920bd92edaf346241 84080 Packages f179e19b7c5b47d5c7247b5d6f37eb2ab2fba168ac70531dd02a0a1cda756038 22493 Packages.gz ** 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/1649086 Title: W: Invalid 'Date' entry in Release file /var/lib/apt/lists/developer.download.nvidia.com_compute_cuda_repos_ubuntu1604_x86%5f64_Release Status in apt package in Ubuntu: New Bug description: root@ubuntu:/var/lib/apt/lists# apt-get update Hit:1 http://ppa.launchpad.net/stefansundin/truecrypt/ubuntu yakkety InRelease Hit:3 http://ppa.launchpad.net/unit193/encryption/ubuntu yakkety InRelease Hit:4 http://es.archive.ubuntu.com/ubuntu yakkety InRelease Hit:5 http://repository.spotify.com stable InRelease Hit:6 http://ppa.launchpad.net/wine/wine-builds/ubuntu yakkety InRelease Get:7 http://es.archive.ubuntu.com/ubuntu yakkety-updates InRelease [102 kB] Get:8 http://security.ubuntu.com/ubuntu yakkety-security InRelease [102 kB] Get:9 http://es.archive.ubuntu.com/ubuntu yakkety-backports InRelease [102 kB] Hit:2 http://screenshots.getdeb.net yakkety-getdeb InRelease Ign:10 http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1604/x86_64 InRelease Hit:11 http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1604/x86_64 Release Fetched 306 kB in 1s (242 kB/s) Reading package lists... Done W: Invalid 'Date' entry in Release file /var/lib/apt/lists/developer.download.nvidia.com_compute_cuda_repos_ubuntu1604_x86%5f64_Release root@ubuntu:/var/lib/apt/lists# The file is as 'developer.download.nvidia.com_compute_cuda_repos_ubuntu1604_x86%5f64_Release' follows: Origin: NVIDIA Label: NVIDIA CUDA Architecture: x86_64 Date: Fri, 23 Sep 2016 18:52:52 -0700 MD5Sum: 3213a453e90b070bc10f329d2fe7f1a384080 Packages c1660fe24223ec9b07b04de1dfb3777122493 Pa
