[Touch-packages] [Bug 2063503] Re: NVidia drivers won't install completely
This appears to be the issue. DRM_UNLOCKED does not exist for nvidia- drm-drv.c to compile. Missing ot changed kernel header? # CC [M] /var/lib/dkms/nvidia/545.29.06/build/nvidia-drm/nvidia-drm-gem-nvkms-memory.o cc -Wp,-MMD,/var/lib/dkms/nvidia/545.29.06/build/nvidia-drm/.nvidia-drm-gem-nvkms-memory.o.d -nostdinc -I./arch/x86/include -I./arch/x86/include/generated -I./include -I./arch/x86/include/uapi -I./arch/x86/include/generated/uapi -I./include/uapi -I./include/generated/uapi -include ./include/linux/compiler-version.h -include ./include/linux/kconfig.h -I./ubuntu/include -include ./include/linux/compiler_types.h -D__KERNEL__ -fmacro-prefix-map=./= -std=gnu11 -fshort-wchar -funsigned-char -fno-common -fno-PIE -fno-strict-aliasing -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -fcf-protection=none -m64 -falign-jumps=1 -falign-loops=1 -mno-80387 -mno-fp-ret-in-387 -mpreferred-stack-boundary=3 -mskip-rax-setup -mtune=generic -mno-red-zone -mcmodel=kernel -Wno-sign-compare -fno-asynchronous-unwind-tables -mindirect-branch=thunk-extern -mindirect-branch-register -mindirect-branch-cs-prefix -mfunction-return=thunk-extern -fno-jump-tables -mharden-sls=all -fpatchable-function-entry=16,16 -fno-delete-null-pointer-checks -O2 -fno-allow-store-data-races -fstack-protector-strong -fno-omit-frame-pointer -fno-optimize-sibling-calls -ftrivial-auto-var-init=zero -fno-stack-clash-protection -fzero-call-used-regs=used-gpr -pg -mrecord-mcount -mfentry -DCC_USING_FENTRY -falign-functions=16 -fstrict-flex-arrays=3 -fno-strict-overflow -fno-stack-check -fconserve-stack -Wall -Wundef -Werror=implicit-function-declaration -Werror=implicit-int -Werror=return-type -Werror=strict-prototypes -Wno-format-security -Wno-trigraphs -Wno-frame-address -Wno-address-of-packed-member -Wmissing-declarations -Wmissing-prototypes -Wframe-larger-than=1024 -Wno-main -Wno-unused-but-set-variable -Wno-unused-const-variable -Wno-dangling-pointer -Wvla -Wno-pointer-sign -Wcast-function-type -Wno-stringop-overflow -Wno-array-bounds -Wno-alloc-size-larger-than -Wimplicit-fallthrough=5 -Werror=date-time -Werror=incompatible-pointer-types -Werror=designated-init -Wenum-conversion -Wno-unused-but-set-variable -Wno-unused-const-variable -Wno-restrict -Wno-packed-not-aligned -Wno-format-overflow -Wno-format-truncation -Wno-stringop-truncation -Wno-missing-field-initializers -Wno-type-limits -Wno-shift-negative-value -Wno-maybe-uninitialized -Wno-sign-compare -g -gdwarf-5 -I/var/lib/dkms/nvidia/545.29.06/build/common/inc -I/var/lib/dkms/nvidia/545.29.06/build -Wall -Wno-cast-qual -Wno-error -Wno-format-extra-args -D__KERNEL__ -DMODULE -DNVRM -DNV_VERSION_STRING=\"545.29.06\" -DNV_FILESYSTEM_ACCESS_AVAILABLE=1 -Wno-unused-function -Wuninitialized -fno-strict-aliasing -ffreestanding -mno-red-zone -mcmodel=kernel -DNV_UVM_ENABLE -Werror=undef -DNV_SPECTRE_V2=0 -DNV_KERNEL_INTERFACE_LAYER -I/var/lib/dkms/nvidia/545.29.06/build/nvidia-drm -UDEBUG -U_DEBUG -DNDEBUG -DNV_BUILD_MODULE_INSTANCES=0 -fsanitize=bounds-strict -fsanitize=shift -fsanitize=bool -fsanitize=enum -DMODULE -DKBUILD_BASENAME='"nvidia_drm_gem_nvkms_memory"' -DKBUILD_MODNAME='"nvidia_drm"' -D__KBUILD_MODNAME=kmod_nvidia_drm -c -o /var/lib/dkms/nvidia/545.29.06/build/nvidia-drm/nvidia-drm-gem-nvkms-memory.o /var/lib/dkms/nvidia/545.29.06/build/nvidia-drm/nvidia-drm-gem-nvkms-memory.c ; ./tools/objtool/objtool --hacks=jump_label --hacks=noinstr --hacks=skylake --retpoline --rethunk --sls --stackval --static-call --uaccess --prefix=16 --module /var/lib/dkms/nvidia/545.29.06/build/nvidia-drm/nvidia-drm-gem-nvkms-memory.o In file included from /var/lib/dkms/nvidia/545.29.06/build/nvidia-drm/nvidia-drm-drv.c:64: /var/lib/dkms/nvidia/545.29.06/build/nvidia-drm/nvidia-drm-drv.c:1489:40: error: ‘DRM_UNLOCKED’ undeclared here (not in a function); did you mean ‘VM_LOCKED’? 1489 | DRM_RENDER_ALLOW|DRM_UNLOCKED), |^~~~ ./include/drm/drm_ioctl.h:155:26: note: in definition of macro ‘DRM_IOCTL_DEF_DRV’ 155 | .flags = _flags, \ | ^~ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2063503 Title: NVidia drivers won't install completely Status in xorg package in Ubuntu: New Bug description: ll versions of the nvidia driver fail to install no matter what. Including the one downloaded from Nvidia. It doesn't matter the version. :~$ sudo apt install nvidia-driver-550 [sudo] password for jim: Reading package lists... Done Building dependency tree... Done Reading state information... Done The following package was automatically installed and is no longer required: nvidia-firmware-545-545.29.06 Use 'sudo apt autoremove' to remove
[Touch-packages] [Bug 2063503] Re: NVidia drivers won't install completely
** Attachment added: "The make.log referred to in my comment above" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2063503/+attachment/5770654/+files/make.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2063503 Title: NVidia drivers won't install completely Status in xorg package in Ubuntu: New Bug description: ll versions of the nvidia driver fail to install no matter what. Including the one downloaded from Nvidia. It doesn't matter the version. :~$ sudo apt install nvidia-driver-550 [sudo] password for jim: Reading package lists... Done Building dependency tree... Done Reading state information... Done The following package was automatically installed and is no longer required: nvidia-firmware-545-545.29.06 Use 'sudo apt autoremove' to remove it. The following additional packages will be installed: libnvidia-cfg1-550 libnvidia-common-550 libnvidia-compute-550 libnvidia-compute-550:i386 libnvidia-decode-550 libnvidia-decode-550:i386 libnvidia-encode-550 libnvidia-encode-550:i386 libnvidia-extra-550 libnvidia-fbc1-550 libnvidia-fbc1-550:i386 libnvidia-gl-550 libnvidia-gl-550:i386 nvidia-compute-utils-550 nvidia-dkms-550 nvidia-firmware-550-550.67 nvidia-kernel-common-550 nvidia-kernel-source-550 nvidia-utils-550 xserver-xorg-video-nvidia-550 The following packages will be REMOVED: libnvidia-cfg1-545 libnvidia-common-545 libnvidia-compute-545 libnvidia-compute-545:i386 libnvidia-decode-545 libnvidia-decode-545:i386 libnvidia-encode-545 libnvidia-encode-545:i386 libnvidia-extra-545 libnvidia-fbc1-545 libnvidia-fbc1-545:i386 libnvidia-gl-545 libnvidia-gl-545:i386 nvidia-compute-utils-545 nvidia-dkms-545 nvidia-driver-545 nvidia-kernel-common-545 nvidia-kernel-source-545 nvidia-utils-545 xserver-xorg-video-nvidia-545 The following NEW packages will be installed: libnvidia-cfg1-550 libnvidia-common-550 libnvidia-compute-550 libnvidia-compute-550:i386 libnvidia-decode-550 libnvidia-decode-550:i386 libnvidia-encode-550 libnvidia-encode-550:i386 libnvidia-extra-550 libnvidia-fbc1-550 libnvidia-fbc1-550:i386 libnvidia-gl-550 libnvidia-gl-550:i386 nvidia-compute-utils-550 nvidia-dkms-550 nvidia-driver-550 nvidia-firmware-550-550.67 nvidia-kernel-common-550 nvidia-kernel-source-550 nvidia-utils-550 xserver-xorg-video-nvidia-550 0 upgraded, 21 newly installed, 20 to remove and 15 not upgraded. 2 not fully installed or removed. Need to get 360 MB of archives. After this operation, 14.7 MB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://archive.ubuntu.com/ubuntu noble/multiverse amd64 nvidia-dkms-550 amd64 550.67-0ubuntu3 [35.8 kB] Get:2 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 libnvidia-cfg1-550 amd64 550.67-0ubuntu3 [155 kB] Get:3 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 libnvidia-common-550 all 550.67-0ubuntu3 [14.8 kB] Get:4 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 libnvidia-compute-550 amd64 550.67-0ubuntu3 [41.3 MB] Get:5 http://ca.archive.ubuntu.com/ubuntu noble/restricted i386 libnvidia-compute-550 i386 550.67-0ubuntu3 [41.2 MB] Get:6 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 libnvidia-decode-550 amd64 550.67-0ubuntu3 [2,028 kB] Get:7 http://ca.archive.ubuntu.com/ubuntu noble/restricted i386 libnvidia-decode-550 i386 550.67-0ubuntu3 [2,470 kB] Get:8 http://ca.archive.ubuntu.com/ubuntu noble/restricted i386 libnvidia-encode-550 i386 550.67-0ubuntu3 [115 kB] Get:9 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 libnvidia-encode-550 amd64 550.67-0ubuntu3 [105 kB] Get:10 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 libnvidia-extra-550 amd64 550.67-0ubuntu3 [72.9 kB] Get:11 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 libnvidia-fbc1-550 amd64 550.67-0ubuntu3 [56.4 kB] Get:12 http://ca.archive.ubuntu.com/ubuntu noble/restricted i386 libnvidia-fbc1-550 i386 550.67-0ubuntu3 [61.9 kB] Get:13 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 libnvidia-gl-550 amd64 550.67-0ubuntu3 [155 MB] Get:14 http://ca.archive.ubuntu.com/ubuntu noble/restricted i386 libnvidia-gl-550 i386 550.67-0ubuntu3 [33.8 MB] Get:15 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 nvidia-compute-utils-550 amd64 550.67-0ubuntu3 [123 kB] Get:16 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 nvidia-kernel-source-550 amd64 550.67-0ubuntu3 [41.7 MB] Get:17 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 nvidia-firmware-550-550.67 amd64 550.67-0ubuntu3 [38.1 MB] Get:18 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 nvidia-kernel-common-550 amd64 550.67-0ubuntu3 [120 kB] Get:19 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64
[Touch-packages] [Bug 2063503] Re: NVidia drivers won't install completely
Tried again after purging all things NVidia and rebooting. :~$ sudo ubuntu-drivers install --recommended udevadm hwdb is deprecated. Use systemd-hwdb instead. udevadm hwdb is deprecated. Use systemd-hwdb instead. udevadm hwdb is deprecated. Use systemd-hwdb instead. udevadm hwdb is deprecated. Use systemd-hwdb instead. udevadm hwdb is deprecated. Use systemd-hwdb instead. udevadm hwdb is deprecated. Use systemd-hwdb instead. Reading package lists... Done Building dependency tree... Done Reading state information... Done The following additional packages will be installed: libnvidia-cfg1-545 libnvidia-common-545 libnvidia-compute-545 libnvidia-decode-545 libnvidia-encode-545 libnvidia-extra-545 libnvidia-fbc1-545 libnvidia-gl-545 libnvidia-gl-545:i386 nvidia-compute-utils-545 nvidia-firmware-545-545.29.06 nvidia-kernel-common-545 nvidia-kernel-source-545 nvidia-prime nvidia-settings nvidia-utils-545 xserver-xorg-video-nvidia-545 The following NEW packages will be installed: libnvidia-cfg1-545 libnvidia-common-545 libnvidia-compute-545 libnvidia-decode-545 libnvidia-encode-545 libnvidia-extra-545 libnvidia-fbc1-545 libnvidia-gl-545 libnvidia-gl-545:i386 nvidia-compute-utils-545 nvidia-dkms-545 nvidia-driver-545 nvidia-firmware-545-545.29.06 nvidia-kernel-common-545 nvidia-kernel-source-545 nvidia-prime nvidia-settings nvidia-utils-545 xserver-xorg-video-nvidia-545 0 upgraded, 19 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/338 MB of archives. After this operation, 908 MB of additional disk space will be used. Selecting previously unselected package libnvidia-cfg1-545:amd64. (Reading database ... 339019 files and directories currently installed.) Preparing to unpack .../00-libnvidia-cfg1-545_545.29.06-0ubuntu0~gpu24.04.1_amd64.deb ... Unpacking libnvidia-cfg1-545:amd64 (545.29.06-0ubuntu0~gpu24.04.1) ... Selecting previously unselected package libnvidia-common-545. Preparing to unpack .../01-libnvidia-common-545_545.29.06-0ubuntu0~gpu24.04.1_all.deb ... Unpacking libnvidia-common-545 (545.29.06-0ubuntu0~gpu24.04.1) ... Selecting previously unselected package libnvidia-compute-545:amd64. Preparing to unpack .../02-libnvidia-compute-545_545.29.06-0ubuntu0~gpu24.04.1_amd64.deb ... Unpacking libnvidia-compute-545:amd64 (545.29.06-0ubuntu0~gpu24.04.1) ... Selecting previously unselected package libnvidia-decode-545:amd64. Preparing to unpack .../03-libnvidia-decode-545_545.29.06-0ubuntu0~gpu24.04.1_amd64.deb ... Unpacking libnvidia-decode-545:amd64 (545.29.06-0ubuntu0~gpu24.04.1) ... Selecting previously unselected package libnvidia-encode-545:amd64. Preparing to unpack .../04-libnvidia-encode-545_545.29.06-0ubuntu0~gpu24.04.1_amd64.deb ... Unpacking libnvidia-encode-545:amd64 (545.29.06-0ubuntu0~gpu24.04.1) ... Selecting previously unselected package libnvidia-extra-545:amd64. Preparing to unpack .../05-libnvidia-extra-545_545.29.06-0ubuntu0~gpu24.04.1_amd64.deb ... Unpacking libnvidia-extra-545:amd64 (545.29.06-0ubuntu0~gpu24.04.1) ... Selecting previously unselected package libnvidia-fbc1-545:amd64. Preparing to unpack .../06-libnvidia-fbc1-545_545.29.06-0ubuntu0~gpu24.04.1_amd64.deb ... Unpacking libnvidia-fbc1-545:amd64 (545.29.06-0ubuntu0~gpu24.04.1) ... Selecting previously unselected package libnvidia-gl-545:i386. Preparing to unpack .../07-libnvidia-gl-545_545.29.06-0ubuntu0~gpu24.04.1_i386.deb ... dpkg-query: no packages found matching libnvidia-gl-535 Unpacking libnvidia-gl-545:i386 (545.29.06-0ubuntu0~gpu24.04.1) ... Selecting previously unselected package libnvidia-gl-545:amd64. Preparing to unpack .../08-libnvidia-gl-545_545.29.06-0ubuntu0~gpu24.04.1_amd64.deb ... dpkg-query: no packages found matching libnvidia-gl-535 Unpacking libnvidia-gl-545:amd64 (545.29.06-0ubuntu0~gpu24.04.1) ... Selecting previously unselected package nvidia-compute-utils-545. Preparing to unpack .../09-nvidia-compute-utils-545_545.29.06-0ubuntu0~gpu24.04.1_amd64.deb ... Unpacking nvidia-compute-utils-545 (545.29.06-0ubuntu0~gpu24.04.1) ... Selecting previously unselected package nvidia-kernel-source-545. Preparing to unpack .../10-nvidia-kernel-source-545_545.29.06-0ubuntu0~gpu24.04.1_amd64.deb ... Unpacking nvidia-kernel-source-545 (545.29.06-0ubuntu0~gpu24.04.1) ... Selecting previously unselected package nvidia-firmware-545-545.29.06. Preparing to unpack .../11-nvidia-firmware-545-545.29.06_545.29.06-0ubuntu0~gpu24.04.1_amd64.deb ... Unpacking nvidia-firmware-545-545.29.06 (545.29.06-0ubuntu0~gpu24.04.1) ... Selecting previously unselected package nvidia-kernel-common-545. Preparing to unpack .../12-nvidia-kernel-common-545_545.29.06-0ubuntu0~gpu24.04.1_amd64.deb ... Unpacking nvidia-kernel-common-545 (545.29.06-0ubuntu0~gpu24.04.1) ... Selecting previously unselected package nvidia-dkms-545. Preparing to unpack .../13-nvidia-dkms-545_545.29.06-0ubuntu0~gpu24.04.1_amd64.deb ... Unpacking nvidia-dkms-545 (545.29.06-0ubuntu0~gpu24.04.1) ... Selecting previously
[Touch-packages] [Bug 2063503] [NEW] NVidia drivers won't install completely
Public bug reported: ll versions of the nvidia driver fail to install no matter what. Including the one downloaded from Nvidia. It doesn't matter the version. :~$ sudo apt install nvidia-driver-550 [sudo] password for jim: Reading package lists... Done Building dependency tree... Done Reading state information... Done The following package was automatically installed and is no longer required: nvidia-firmware-545-545.29.06 Use 'sudo apt autoremove' to remove it. The following additional packages will be installed: libnvidia-cfg1-550 libnvidia-common-550 libnvidia-compute-550 libnvidia-compute-550:i386 libnvidia-decode-550 libnvidia-decode-550:i386 libnvidia-encode-550 libnvidia-encode-550:i386 libnvidia-extra-550 libnvidia-fbc1-550 libnvidia-fbc1-550:i386 libnvidia-gl-550 libnvidia-gl-550:i386 nvidia-compute-utils-550 nvidia-dkms-550 nvidia-firmware-550-550.67 nvidia-kernel-common-550 nvidia-kernel-source-550 nvidia-utils-550 xserver-xorg-video-nvidia-550 The following packages will be REMOVED: libnvidia-cfg1-545 libnvidia-common-545 libnvidia-compute-545 libnvidia-compute-545:i386 libnvidia-decode-545 libnvidia-decode-545:i386 libnvidia-encode-545 libnvidia-encode-545:i386 libnvidia-extra-545 libnvidia-fbc1-545 libnvidia-fbc1-545:i386 libnvidia-gl-545 libnvidia-gl-545:i386 nvidia-compute-utils-545 nvidia-dkms-545 nvidia-driver-545 nvidia-kernel-common-545 nvidia-kernel-source-545 nvidia-utils-545 xserver-xorg-video-nvidia-545 The following NEW packages will be installed: libnvidia-cfg1-550 libnvidia-common-550 libnvidia-compute-550 libnvidia-compute-550:i386 libnvidia-decode-550 libnvidia-decode-550:i386 libnvidia-encode-550 libnvidia-encode-550:i386 libnvidia-extra-550 libnvidia-fbc1-550 libnvidia-fbc1-550:i386 libnvidia-gl-550 libnvidia-gl-550:i386 nvidia-compute-utils-550 nvidia-dkms-550 nvidia-driver-550 nvidia-firmware-550-550.67 nvidia-kernel-common-550 nvidia-kernel-source-550 nvidia-utils-550 xserver-xorg-video-nvidia-550 0 upgraded, 21 newly installed, 20 to remove and 15 not upgraded. 2 not fully installed or removed. Need to get 360 MB of archives. After this operation, 14.7 MB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://archive.ubuntu.com/ubuntu noble/multiverse amd64 nvidia-dkms-550 amd64 550.67-0ubuntu3 [35.8 kB] Get:2 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 libnvidia-cfg1-550 amd64 550.67-0ubuntu3 [155 kB] Get:3 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 libnvidia-common-550 all 550.67-0ubuntu3 [14.8 kB] Get:4 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 libnvidia-compute-550 amd64 550.67-0ubuntu3 [41.3 MB] Get:5 http://ca.archive.ubuntu.com/ubuntu noble/restricted i386 libnvidia-compute-550 i386 550.67-0ubuntu3 [41.2 MB] Get:6 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 libnvidia-decode-550 amd64 550.67-0ubuntu3 [2,028 kB] Get:7 http://ca.archive.ubuntu.com/ubuntu noble/restricted i386 libnvidia-decode-550 i386 550.67-0ubuntu3 [2,470 kB] Get:8 http://ca.archive.ubuntu.com/ubuntu noble/restricted i386 libnvidia-encode-550 i386 550.67-0ubuntu3 [115 kB] Get:9 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 libnvidia-encode-550 amd64 550.67-0ubuntu3 [105 kB] Get:10 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 libnvidia-extra-550 amd64 550.67-0ubuntu3 [72.9 kB] Get:11 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 libnvidia-fbc1-550 amd64 550.67-0ubuntu3 [56.4 kB] Get:12 http://ca.archive.ubuntu.com/ubuntu noble/restricted i386 libnvidia-fbc1-550 i386 550.67-0ubuntu3 [61.9 kB] Get:13 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 libnvidia-gl-550 amd64 550.67-0ubuntu3 [155 MB] Get:14 http://ca.archive.ubuntu.com/ubuntu noble/restricted i386 libnvidia-gl-550 i386 550.67-0ubuntu3 [33.8 MB] Get:15 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 nvidia-compute-utils-550 amd64 550.67-0ubuntu3 [123 kB] Get:16 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 nvidia-kernel-source-550 amd64 550.67-0ubuntu3 [41.7 MB] Get:17 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 nvidia-firmware-550-550.67 amd64 550.67-0ubuntu3 [38.1 MB] Get:18 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 nvidia-kernel-common-550 amd64 550.67-0ubuntu3 [120 kB] Get:19 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 nvidia-utils-550 amd64 550.67-0ubuntu3 [521 kB] Get:20 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 xserver-xorg-video-nvidia-550 amd64 550.67-0ubuntu3 [1,616 kB] Get:21 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 nvidia-driver-550 amd64 550.67-0ubuntu3 [486 kB] Fetched 360 MB in 30s (11.8 MB/s) (Reading database ... 339762 files and directories currently installed.) Removing nvidia-driver-545 (545.29.06-0ubuntu0~gpu24.04.1) ... Removing nvidia-dkms-545
[Touch-packages] [Bug 2029120] Re: /usr/bin/unattended-upgrade leaking and saturating RAM in 30 seconds
Hello, I notice the same problem as reported by Aurélien. It happens daily at the time the unattended upgrades are scheduled. Sometimes it lasts only a minute, sometimes longer. But when it occurs at a moment that an unresponsive system is not acceptable, this causes problems. It consumes 90% memory (32 Gb RAM - swapfile is twice that size)! Until now I didn't notice an out of memory for that process, but it seems that it keeps growing until it fills the whole memory available. Ubuntu 22.04.3 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/2029120 Title: /usr/bin/unattended-upgrade leaking and saturating RAM in 30 seconds Status in unattended-upgrades package in Ubuntu: New Bug description: Hello, We are facing a huge memory leak with unattended-upgrade binary. It appears that in around 20s, 2.9Go (80%) of RAM is consumed by the process making the system unresponsive (even a basic 'ps' command remains stuck). The swap was voluntarily disabled, but anyway I do not expect such a process to consume up to 3Go of RAM in nominal operation. Note: the logs were captured on a system configured in French. I manually translated some words below, which could explain it is not exactly what you would have on an english based system. Ubuntu release: Description:Ubuntu 22.04 LTS Release:22.04 Package version: unattended-upgrades: Installed : 2.8ubuntu1 Candidate : 2.8ubuntu1 Version table : *** 2.8ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://fr.archive.ubuntu.com/ubuntu jammy/main i386 Packages 100 /var/lib/dpkg/status In attachment you will find 2 files: - periodic monitoring of available memory (with free -m) - periodic monitoring of highest memory consumer processes (with ps + sort on memory column) - screenshot of syslog (from a distinct run) showing that unattended-upgr went out of memory and was killed by OOM. You can also see that the run occured as part of the apt-daily service. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/2029120/+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 2034986] Re: some text became unreadable during a distribution upgrade
Just now upgrading ubuntu-mate 23.04 to 23.10 and encountered the corrupt text issues. Screenshot attached. ** Attachment added: "corruption.png" https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2034986/+attachment/5710737/+files/corruption.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2034986 Title: some text became unreadable during a distribution upgrade Status in Cinnamon: New Status in Ubuntu MATE: New Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: In Progress Status in ubuntu-release-upgrader source package in Jammy: Fix Committed Status in ubuntu-release-upgrader source package in Lunar: Fix Committed Status in ubuntu-meta source package in Mantic: Fix Released Status in ubuntu-release-upgrader source package in Mantic: In Progress Bug description: [ Impact ] * On Ubuntu Mate with the Lunar series, when running ubuntu-release-upgrader, the displayed font of running applications (including the upgrader) becomes very corrupted. * This is not just a display problem, it is also a functional one. The release upgrader will have text corrupted to the point where a dialog asks a decision, and displays two buttons, but the text is unreadable and one has to guess which button is the one that carries out their desired action. * In the early parts of the upgrader tool, users are told in bold: "To prevent data loss close all open applications and documents." This is just before the "Start Upgrade" button is available. But they may not do so. Many applications may have a corrupted font. * To address this, an additional environment variable is being passed along to pkexec, XDG_CURRENT_DESKTOP, as this is the critical criteria for making the Mate version of the fix work. * Also in the change are * an update to tests * from pre-build.sh * an update of the mirrors.cfg, adding and removing several mirrors * a refresh of the po files [ Test Plan ] * acquire an Ubuntu Mate environment running Ubuntu Lunar on amd64 * as user, run "update-manager -d" * monitor the "Distribution Upgrade" screen. During the "Installing the upgrades" step (and mind that this step will be long), observe the text of the "Distribution Upgrade" screen and verify that the font does not corrupt. * Repeat the above for Ubuntu Desktop [ Where problems could occur ] * We are changing, at release time, ubuntu-release upgrader. If we are careless, we could regress upgrades for a wider group of users than just Ubuntu Mate. That said, it is believed that passing the additional XDG_CURRENT_DESKTOP variable is relatively low risk. [ Other Info ] * TBD --- Original description: I was upgrading from Lunar to Mantic the other day and left a couple of applications open during the upgrade process. During the upgrade the text in audacious became unreadable (I'll attach a screenshot) and I seem to recall the title bar of Firefox being unreadable but the contents of web pages still being readable. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-release-upgrader-core 1:23.10.5 ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0 Uname: Linux 6.5.0-4-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Sep 8 15:39:27 2023 InstallationDate: Installed on 2018-08-10 (1855 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 126: Error executing command as another user: Request dismissed VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490 To manage notifications about this bug go to: https://bugs.launchpad.net/cinnamon-project/+bug/2034986/+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 2034986] Re: some text became unreadable during a distribution upgrade
Am in the process of an Ubuntu-Mate 23.04 to 23.10 upgrade and have the corrupted text issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2034986 Title: some text became unreadable during a distribution upgrade Status in Cinnamon: New Status in Ubuntu MATE: New Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: In Progress Status in ubuntu-release-upgrader source package in Jammy: Fix Committed Status in ubuntu-release-upgrader source package in Lunar: Fix Committed Status in ubuntu-meta source package in Mantic: Fix Released Status in ubuntu-release-upgrader source package in Mantic: In Progress Bug description: [ Impact ] * On Ubuntu Mate with the Lunar series, when running ubuntu-release-upgrader, the displayed font of running applications (including the upgrader) becomes very corrupted. * This is not just a display problem, it is also a functional one. The release upgrader will have text corrupted to the point where a dialog asks a decision, and displays two buttons, but the text is unreadable and one has to guess which button is the one that carries out their desired action. * In the early parts of the upgrader tool, users are told in bold: "To prevent data loss close all open applications and documents." This is just before the "Start Upgrade" button is available. But they may not do so. Many applications may have a corrupted font. * To address this, an additional environment variable is being passed along to pkexec, XDG_CURRENT_DESKTOP, as this is the critical criteria for making the Mate version of the fix work. * Also in the change are * an update to tests * from pre-build.sh * an update of the mirrors.cfg, adding and removing several mirrors * a refresh of the po files [ Test Plan ] * acquire an Ubuntu Mate environment running Ubuntu Lunar on amd64 * as user, run "update-manager -d" * monitor the "Distribution Upgrade" screen. During the "Installing the upgrades" step (and mind that this step will be long), observe the text of the "Distribution Upgrade" screen and verify that the font does not corrupt. * Repeat the above for Ubuntu Desktop [ Where problems could occur ] * We are changing, at release time, ubuntu-release upgrader. If we are careless, we could regress upgrades for a wider group of users than just Ubuntu Mate. That said, it is believed that passing the additional XDG_CURRENT_DESKTOP variable is relatively low risk. [ Other Info ] * TBD --- Original description: I was upgrading from Lunar to Mantic the other day and left a couple of applications open during the upgrade process. During the upgrade the text in audacious became unreadable (I'll attach a screenshot) and I seem to recall the title bar of Firefox being unreadable but the contents of web pages still being readable. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-release-upgrader-core 1:23.10.5 ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0 Uname: Linux 6.5.0-4-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Sep 8 15:39:27 2023 InstallationDate: Installed on 2018-08-10 (1855 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 126: Error executing command as another user: Request dismissed VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490 To manage notifications about this bug go to: https://bugs.launchpad.net/cinnamon-project/+bug/2034986/+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 1993571] Re: After 5.19.0-15, intel wifi 6 no longer available
The 'unavailability' of the wifi interface is apparently a path- dependent bug in network manager or a related component. I was not able to fix it in place, but a scratch reinstall of Kinetic fixed it. So it can't be the kernel. ** Package changed: linux (Ubuntu) => network-manager (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1993571 Title: After 5.19.0-15, intel wifi 6 no longer available Status in network-manager package in Ubuntu: Confirmed Bug description: Since 5.19.0-16, which is also the kernel that broke booting on 11/12-gen Intel graphics, my Intel wifi is no longer working. This continues with the present release candidate kernel package -21. The wifi status reports simply that it is "unavailable" and no means to make it "available" is evident to me. On all prior kernels and Jammy it worked fine. % sudo iwconfig wlo1 wlo1 IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=-2147483648 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on % sudo nmcli device show wlo1 GENERAL.DEVICE: wlo1 GENERAL.TYPE: wifi GENERAL.HWADDR: 38:87:D5:13:C1:30 GENERAL.MTU:1500 GENERAL.STATE: 20 (unavailable) GENERAL.CONNECTION: -- GENERAL.CON-PATH: -- IP4.GATEWAY:-- IP6.GATEWAY:-- ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-21-generic 5.19.0-21.21 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jwb1179 F wireplumber /dev/snd/seq:jwb1176 F pipewire CRDA: N/A CasperMD5CheckResult: unknown Date: Wed Oct 19 10:24:26 2022 InstallationDate: Installed on 2021-12-31 (292 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: ASUS System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-21-generic root=UUID=74e4f833-7902-4b06-9e40-e5b191272e08 ro quiet splash irqaffinity=0-15 isolcpus=16-19 vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-21-generic N/A linux-backports-modules-5.19.0-21-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to kinetic on 2022-06-07 (133 days ago) dmi.bios.date: 08/25/2022 dmi.bios.release: 20.3 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2003 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z690-P WIFI D4 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2003:bd08/25/2022:br20.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ690-PWIFID4:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1993571/+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 1972790] Re: Can't connect to hotspot created on ubuntu
My machine can't connect with the ubuntu software, when wpa_supplicant version is 2.10. On the version 2.9 of wpa_supplicant, the machine can connect with that. But, the internet does not work. After the firewall of the ubuntu software is disable, my machine can connect the internet. But the internet is not available if I enable the firewall, again. Even if only the hotspot is handled as an exception in the firewall, the result is the same. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1972790 Title: Can't connect to hotspot created on ubuntu Status in wpa package in Ubuntu: Confirmed Bug description: We currently have older systems (18.04) with hotspot's and we will migrate to 22.04. Anything work's fine, expect the hotspot. The Hotspot will be created and is visible in the WLAN-List, but if the security is set to "WPA & WPA2 Personal" we get the error message "Failed to connect to the network". If we change the Security to "WPA3 Personal" we get the error message "Invalid Password", even if the password is correct. As soon we remove the security (change it to "none"), we can connect with out any problems. We can reproduce it with a fresh installtion of the Ubuntu Server 22.04 and the following two commands: apt install network-manager nmcli c add type wifi ifname wlp3s0 con-name Hotspot autoconnect yes ssid test-ap 802-11-wireless.mode ap 802-11-wireless.band bg 802-11-wireless.mac-address "80:45:dd:f0:27:ba" wifi-sec.group ccmp wifi-sec.key-mgmt wpa-psk wifi-sec.pairwise ccmp wifi-sec.proto rsn wifi-sec.psk "test12345" ipv4.addresses 192.168.60.1/24 ipv4.method shared && nmcli connection up Hotspot We thought it could be similar to this issue: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267 Because if we test it with 20.04 it worked fine, because 20.04 uses the Version 2:2.9.0-21build1 as described in the Ticket. As @Sebastian Bacher suggested (https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/comments/58), i created a own report. In the attachment is the requested log file. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-6 [modified: lib/systemd/system/wpa_supplicant.service] ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue May 10 07:24:15 2022 InstallationDate: Installed on 2022-05-10 (0 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1972790/+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 1972790] Re: Can't connect to hotspot created on ubuntu
my wpa_supplicant version is 2.9 but, it is not working for me. iphone se3, ios 15.7 it is not connected. infinite loading. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1972790 Title: Can't connect to hotspot created on ubuntu Status in wpa package in Ubuntu: Confirmed Bug description: We currently have older systems (18.04) with hotspot's and we will migrate to 22.04. Anything work's fine, expect the hotspot. The Hotspot will be created and is visible in the WLAN-List, but if the security is set to "WPA & WPA2 Personal" we get the error message "Failed to connect to the network". If we change the Security to "WPA3 Personal" we get the error message "Invalid Password", even if the password is correct. As soon we remove the security (change it to "none"), we can connect with out any problems. We can reproduce it with a fresh installtion of the Ubuntu Server 22.04 and the following two commands: apt install network-manager nmcli c add type wifi ifname wlp3s0 con-name Hotspot autoconnect yes ssid test-ap 802-11-wireless.mode ap 802-11-wireless.band bg 802-11-wireless.mac-address "80:45:dd:f0:27:ba" wifi-sec.group ccmp wifi-sec.key-mgmt wpa-psk wifi-sec.pairwise ccmp wifi-sec.proto rsn wifi-sec.psk "test12345" ipv4.addresses 192.168.60.1/24 ipv4.method shared && nmcli connection up Hotspot We thought it could be similar to this issue: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267 Because if we test it with 20.04 it worked fine, because 20.04 uses the Version 2:2.9.0-21build1 as described in the Ticket. As @Sebastian Bacher suggested (https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/comments/58), i created a own report. In the attachment is the requested log file. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-6 [modified: lib/systemd/system/wpa_supplicant.service] ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue May 10 07:24:15 2022 InstallationDate: Installed on 2022-05-10 (0 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1972790/+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 1851504] Re: encrypted root fails to cryptsetup on disco
It looks like this issue might be resolved in a recent update. At least for me, /lib is now a softlink to /usr/lib and the original cryptroot script will now find libgcc_s.so.1 and add it to the initramfs. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1851504 Title: encrypted root fails to cryptsetup on disco Status in cryptsetup: New Status in initramfs-tools package in Ubuntu: Confirmed Bug description: There is a subtle error message during update-initramfs: find: '': No such file or directory I could trace this to /usr/share/initramfs-tools/hooks/cryptroot line 430: # libargon2 uses pthread_cancel LIBC_DIR="$(ldd /sbin/cryptsetup | sed -nr 's#.* => (/lib.*)/libc\.so\.[0-9.-]+ \(0x[[:xdigit:]]+\)$#\1#p')" > find -L "$LIBC_DIR" -maxdepth 1 -name 'libgcc_s.*' -type f | while read so; do copy_exec "$so" done ldd output shows: libc.so.6 => /usr/lib/x86_64-linux-gnu/libc.so.6 (0x7f41aa8c4000) so the library is not in /lib anymore but /usr/lib The root cause of this may be an update to libc, however the script may need adjusting anyway. cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=19.04 DISTRIB_CODENAME=disco DISTRIB_DESCRIPTION="Ubuntu 19.04" To manage notifications about this bug go to: https://bugs.launchpad.net/cryptsetup/+bug/1851504/+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 1851504] Re: encrypted root fails to cryptsetup on disco
This bug is affecting me on Kubuntu 19.04. I rebooted my computer this morning and typed my password into cryptsetup during boot only to get the message "libgcc_s.so.1 must be installed for pthread_cancel to work". There are a few factors that I believe should cause the priority of this issue to be increased: 1. Advanced boot options cannot be used to recover Selecting recovery mode from grub menu or older kernel/initramfs versions doesn't help. All of my old initramfs images have been updated to no longer include libgcc_s.so.1. 2. The initramfs scripts do not recover gracefully It has taken me at least 4 hours to recover from this issue because copying libgcc_s.so.1 from a usb stick into the initramfs isn't enough to recover. Upon exiting the recovery shell, it simply indicated that the root couldn't be mounted and dumped me back to the shell again. I manually ran cryptsetup to open the LUKS volume and this still resulted in getting dumped back to the initramfs shell. The problem, I think, is that the cryptsetup fails several times (in local-top and in local-premount or local-block) before the mount is considered failed and the initial recovery console is presented. So, when exiting the shell, it tries to resume at a point well past the initial mounting attempt. I finally got the computer to boot by copying libgcc_s.so.1 from another computer into the recovery initramfs. I then had to source scripts/functions and run_scripts local-top. After that I was able to boot, but I don't remember if I also did a run_scripts local-premount. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1851504 Title: encrypted root fails to cryptsetup on disco Status in cryptsetup: New Status in initramfs-tools package in Ubuntu: Confirmed Bug description: There is a subtle error message during update-initramfs: find: '': No such file or directory I could trace this to /usr/share/initramfs-tools/hooks/cryptroot line 430: # libargon2 uses pthread_cancel LIBC_DIR="$(ldd /sbin/cryptsetup | sed -nr 's#.* => (/lib.*)/libc\.so\.[0-9.-]+ \(0x[[:xdigit:]]+\)$#\1#p')" > find -L "$LIBC_DIR" -maxdepth 1 -name 'libgcc_s.*' -type f | while read so; do copy_exec "$so" done ldd output shows: libc.so.6 => /usr/lib/x86_64-linux-gnu/libc.so.6 (0x7f41aa8c4000) so the library is not in /lib anymore but /usr/lib The root cause of this may be an update to libc, however the script may need adjusting anyway. cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=19.04 DISTRIB_CODENAME=disco DISTRIB_DESCRIPTION="Ubuntu 19.04" To manage notifications about this bug go to: https://bugs.launchpad.net/cryptsetup/+bug/1851504/+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 1815889]
I'm removing this from the 19.0 blocking tracker. Generally we don't add bugs to block a release if they were present in the previous release, additionally there doesn't seem to be any consensus on a solution, at this moment. If there is a fix implemented I'd be happy to pull that into a later 19.0 release. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1815889 Title: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new() Status in Mesa: Confirmed Status in QEMU: New Status in mesa package in Ubuntu: Triaged Status in qemu package in Ubuntu: Triaged Status in mesa source package in Disco: Triaged Bug description: Unable to launch Default Fedora 29 images in gnome-boxes ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: qemu-system-x86 1:3.1+dfsg-2ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18 Uname: Linux 4.19.0-12-generic x86_64 ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64 Date: Thu Feb 14 11:00:45 2019 ExecutablePath: /usr/bin/qemu-system-x86_64 KvmCmdLine: COMMAND STAT EUID RUID PID PPID %CPU COMMAND MachineType: Dell Inc. Precision T3610 ProcEnviron: PATH=(custom, user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.19.0-12-generic root=UUID=939b509b-d627-4642-a655-979b44972d17 ro splash quiet vt.handoff=1 Signal: 31 SourcePackage: qemu StacktraceTop: __pthread_setaffinity_new (th=, cpusetsize=128, cpuset=0x7f5771fbf680) at ../sysdeps/unix/sysv/linux/pthread_setaffinity.c:34 () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so start_thread (arg=) at pthread_create.c:486 clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Title: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new() UpgradeStatus: Upgraded to disco on 2018-11-14 (91 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video dmi.bios.date: 11/14/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A18 dmi.board.name: 09M8Y8 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA18:bd11/14/2018:svnDellInc.:pnPrecisionT3610:pvr00:rvnDellInc.:rn09M8Y8:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision T3610 dmi.product.sku: 05D2 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1815889/+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 1815889]
We're getting down to just a few bugs blocking 19.0, so I'm pinging those bugs to see what the progress is? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1815889 Title: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new() Status in Mesa: Confirmed Status in QEMU: New Status in mesa package in Ubuntu: Triaged Status in qemu package in Ubuntu: Triaged Status in mesa source package in Disco: Triaged Bug description: Unable to launch Default Fedora 29 images in gnome-boxes ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: qemu-system-x86 1:3.1+dfsg-2ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18 Uname: Linux 4.19.0-12-generic x86_64 ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64 Date: Thu Feb 14 11:00:45 2019 ExecutablePath: /usr/bin/qemu-system-x86_64 KvmCmdLine: COMMAND STAT EUID RUID PID PPID %CPU COMMAND MachineType: Dell Inc. Precision T3610 ProcEnviron: PATH=(custom, user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.19.0-12-generic root=UUID=939b509b-d627-4642-a655-979b44972d17 ro splash quiet vt.handoff=1 Signal: 31 SourcePackage: qemu StacktraceTop: __pthread_setaffinity_new (th=, cpusetsize=128, cpuset=0x7f5771fbf680) at ../sysdeps/unix/sysv/linux/pthread_setaffinity.c:34 () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so start_thread (arg=) at pthread_create.c:486 clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Title: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new() UpgradeStatus: Upgraded to disco on 2018-11-14 (91 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video dmi.bios.date: 11/14/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A18 dmi.board.name: 09M8Y8 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA18:bd11/14/2018:svnDellInc.:pnPrecisionT3610:pvr00:rvnDellInc.:rn09M8Y8:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision T3610 dmi.product.sku: 05D2 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1815889/+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 1815236]
The mentioned patch has landed in master and 19.0 (presumably it is or will be in 18.3 shortly), is this okay to close? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1815236 Title: totem assert failure: totem: src/intel/genxml/gen9_pack.h:72: __gen_uint: La declaración `v <= max' no se cumple. Status in Mesa: Fix Released Status in mesa package in Ubuntu: Confirmed Status in totem package in Ubuntu: Invalid Bug description: https://gitlab.gnome.org/GNOME/totem/issues/297 (Not GNOME) --- I'm not sure, but this happened after updating to gstreamer 1.15.1, I have problems when I maximize totem. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: totem 3.30.0-4ubuntu1 Uname: Linux 4.20.7-042007-generic x86_64 ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64 AssertionMessage: totem: src/intel/genxml/gen9_pack.h:72: __gen_uint: La declaración `v <= max' no se cumple. CurrentDesktop: ubuntu:GNOME Date: Thu Feb 7 18:40:29 2019 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2018-12-02 (68 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/totem --gapplication-service Signal: 6 SourcePackage: totem StacktraceTop: __assert_fail_base (fmt=0x7ff31939be23 , assertion=0x7ff312a5416c "v <= max", file=0x7ff312a5644c "src/intel/genxml/gen9_pack.h", line=72, function=) at assert.c:92 __GI___assert_fail (assertion=0x7ff312a5416c "v <= max", file=0x7ff312a5644c "src/intel/genxml/gen9_pack.h", line=72, function=0x7ff312a56938 "__gen_uint") at assert.c:101 ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so Title: totem assert failure: totem: src/intel/genxml/gen9_pack.h:72: __gen_uint: La declaración `v <= max' no se cumple. UpgradeStatus: Upgraded to disco on 2018-12-02 (67 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1815236/+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 1813434] [NEW] package libpolkit-agent-1-0 0.105-20ubuntu0.18.04.4 failed to install/upgrade: unable to sync directory '/var/lib/dpkg/tmp.ci/': Input/output error
Public bug reported: this shows up on startup ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libpolkit-agent-1-0 0.105-20ubuntu0.18.04.4 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Sat Jan 26 18:30:41 2019 DuplicateSignature: package:libpolkit-agent-1-0:0.105-20ubuntu0.18.04.4 Unpacking gir1.2-polkit-1.0 (0.105-20ubuntu0.18.04.4) over (0.105-20ubuntu0.18.04.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-STjm8e/008-libpolkit-agent-1-0_0.105-20ubuntu0.18.04.4_amd64.deb (--unpack): unable to sync directory '/var/lib/dpkg/tmp.ci/': Input/output error ErrorMessage: unable to sync directory '/var/lib/dpkg/tmp.ci/': Input/output error InstallationDate: Installed on 2013-11-13 (1900 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6ubuntu0.1 SourcePackage: policykit-1 Title: package libpolkit-agent-1-0 0.105-20ubuntu0.18.04.4 failed to install/upgrade: unable to sync directory '/var/lib/dpkg/tmp.ci/': Input/output error UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: policykit-1 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1813434 Title: package libpolkit-agent-1-0 0.105-20ubuntu0.18.04.4 failed to install/upgrade: unable to sync directory '/var/lib/dpkg/tmp.ci/': Input/output error Status in policykit-1 package in Ubuntu: New Bug description: this shows up on startup ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libpolkit-agent-1-0 0.105-20ubuntu0.18.04.4 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Sat Jan 26 18:30:41 2019 DuplicateSignature: package:libpolkit-agent-1-0:0.105-20ubuntu0.18.04.4 Unpacking gir1.2-polkit-1.0 (0.105-20ubuntu0.18.04.4) over (0.105-20ubuntu0.18.04.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-STjm8e/008-libpolkit-agent-1-0_0.105-20ubuntu0.18.04.4_amd64.deb (--unpack): unable to sync directory '/var/lib/dpkg/tmp.ci/': Input/output error ErrorMessage: unable to sync directory '/var/lib/dpkg/tmp.ci/': Input/output error InstallationDate: Installed on 2013-11-13 (1900 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6ubuntu0.1 SourcePackage: policykit-1 Title: package libpolkit-agent-1-0 0.105-20ubuntu0.18.04.4 failed to install/upgrade: unable to sync directory '/var/lib/dpkg/tmp.ci/': Input/output error UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1813434/+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 1699293] [NEW] package tzdata 2017b-2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
Public bug reported: came up on main screen ProblemType: Package DistroRelease: Ubuntu 17.10 Package: tzdata 2017b-2 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 Date: Tue Jun 20 12:58:39 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-06-20 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170613) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.4.5 SourcePackage: tzdata Title: package tzdata 2017b-2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: tzdata (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package artful -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1699293 Title: package tzdata 2017b-2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in tzdata package in Ubuntu: New Bug description: came up on main screen ProblemType: Package DistroRelease: Ubuntu 17.10 Package: tzdata 2017b-2 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 Date: Tue Jun 20 12:58:39 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-06-20 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170613) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.4.5 SourcePackage: tzdata Title: package tzdata 2017b-2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1699293/+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 798414] Re: update-initramfs should produce a more helpful error when there isn't enough free space
On booting I am told that a system program has encountered an error and asked if I want to send a report. On saying yes I'm told that the bug has already been reported and that it is "update-initramfs should produce a more helpful error when there isn't enough free space". This is so far from what is happening that it is infuriating. The basis of the problem is that /boot is not being cleaned up automatically. This was a bug which was supposedly fixed in 16.04 UTS, but apparently not. As a retired software engineer I know that I can clean up /boot manually, and have done so many times. However I shouldn't have to. Please stop classifying the /boot partition being full as "update-initramfs should produce a more helpful error when there isn't enough free space". This bug (/boot not being cleaned up automatically) should be given the highest possible importance. It must be a complete turn of to any ubuntu user who does not have computer science skills (and to many who do). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/798414 Title: update-initramfs should produce a more helpful error when there isn't enough free space Status in initramfs-tools: Confirmed Status in Software Updater: New Status in dpkg package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: In Progress Bug description: Binary package hint: initramfs-tools When generating a new initramfs there is no check for available free space, subsequently its possible for update-initramfs to fail due to a lack of free space. This is resulting in package installation failures for initramfs-tools. For example: Setting up initramfs-tools (0.98.8ubuntu3) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic gzip: stdout: No space left on device E: mkinitramfs failure cpio 141 gzip 1 update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic dpkg: error processing initramfs-tools (--configure): subprocess installed post-installation script returned error exit status 1 WORKAROUND: Remove unused kernels using computer janitor (not in repositories for 14.04 or later) or manually free space on your partition containing the /boot file system. See instructions here https://help.ubuntu.com/community/RemoveOldKernels To manage notifications about this bug go to: https://bugs.launchpad.net/initramfs-tools/+bug/798414/+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 1661406] [NEW] apparmor failing to be purged on trusty
Public bug reported: Version: 2.10.95-0ubuntu2.5~14.04.1 When executing apt -y purge apparmor. The purge run but has errors as files do not exist and the rmdir fails to execute. rmdir: failed to remove '/var/lib/apparmor/profiles': No such file or directory Steps to reproduce: apt-get update apt-get -y install apparmor apt -y purge apparmor I will put workarounds in place for now in puppet but this is making puppet not like it.. ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1661406 Title: apparmor failing to be purged on trusty Status in apparmor package in Ubuntu: New Bug description: Version: 2.10.95-0ubuntu2.5~14.04.1 When executing apt -y purge apparmor. The purge run but has errors as files do not exist and the rmdir fails to execute. rmdir: failed to remove '/var/lib/apparmor/profiles': No such file or directory Steps to reproduce: apt-get update apt-get -y install apparmor apt -y purge apparmor I will put workarounds in place for now in puppet but this is making puppet not like it.. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1661406/+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 1591411] Re: systemd-logind must be restarted every ~1000 SSH logins to prevent a ~25 second delay
Are there any updates on fixing this in xenial/16.04? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1591411 Title: systemd-logind must be restarted every ~1000 SSH logins to prevent a ~25 second delay Status in D-Bus: Unknown Status in systemd: Unknown Status in dbus package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Fix Released Status in dbus source package in Xenial: Confirmed Status in systemd source package in Xenial: Invalid Bug description: I noticed on a system that accepts large numbers of SSH connections that after awhile, SSH sessions were taking ~25 seconds to complete. Looking in /var/log/auth.log, systemd-logind starts failing with the following: Jun 10 23:55:28 test sshd[3666]: pam_unix(sshd:session): session opened for user ubuntu by (uid=0) Jun 10 23:55:28 test systemd-logind[105]: New session c1052 of user ubuntu. Jun 10 23:55:28 test systemd-logind[105]: Failed to abandon session scope: Transport endpoint is not connected Jun 10 23:55:28 test sshd[3666]: pam_systemd(sshd:session): Failed to create session: Message recipient disconnected from message bus without replying I reproduced this in an LXD container by doing something like: lxc launch ubuntu:x test lxc exec test -- login -f ubuntu ssh-import-id Then ran a script as follows (passing in ubuntu@): while [ 1 ]; do (time ssh $1 "echo OK > /dev/null") 2>&1 | grep ^real >> log done In my case, after 1052 logins, the 1053rd and thereafter were taking 25+ seconds to complete. Here are some snippets from the log file: $ cat log | grep 0m0 | wc -l 1052 $ cat log | grep 0m25 | wc -l 4 $ tail -5 log real 0m0.222s real 0m25.232s real 0m25.235s real 0m25.236s real 0m25.239s ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sat Jun 11 00:09:34 2016 MachineType: Notebook W230SS ProcEnviron: TERM=xterm-256color PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W230SS dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/15/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.name: W230SS dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1591411/+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 1591797] Re: Only run FIPS self tests when FIPS is enabled
Chris, I can confirm that 1.0.2g-1ubuntu4.3 in xenial-proposed on armhf
works as expected.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1591797
Title:
Only run FIPS self tests when FIPS is enabled
Status in openssl package in Ubuntu:
Fix Released
Bug description:
The FIPS changes added in 1.0.2g-1ubuntu3/1.0.2g-1ubuntu4 as discussed
in https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1553309
always run the FIPS self tests independent of FIPS being enabled (via
/proc/sys/crypto/fips_enabled).
The performance impact of running these FIPS tests on armhf
(beaglebone and raspberry pi 2&3) is significant (~ 700ms). On amd64
it is measurable but far less significant (~ 10ms). On a long running
process this may be insignificant, but for command line tools this is
problematic. I've seen performance differences with wget, dig,
nslookup, and host. I am sure there are others. The specific numbers
above are from the sample code below.
The relevant initialization can be found in crypto/o_init.c:
static void init_fips_mode(void)
{
char buf[2] = "0";
int fd;
/* Ensure the selftests always run */
FIPS_mode_set(1);
/* For now, do not enforce fips mode via env var
if (getenv("OPENSSL_FORCE_FIPS_MODE") != NULL) {
buf[0] = '1';
} else if ((fd = open(FIPS_MODE_SWITCH_FILE, O_RDONLY)) >= 0) { */
if ((fd = open(FIPS_MODE_SWITCH_FILE, O_RDONLY)) >= 0) {
while (read(fd, buf, sizeof(buf)) < 0 && errno == EINTR) ; close(fd);
}
/* Failure reading the fips mode switch file means just not
* switching into FIPS mode. We would break too many things
* otherwise..
*/
if (buf[0] != '1') {
/* drop down to non-FIPS mode if it is not requested */
FIPS_mode_set(0);
} else {
/* abort if selftest failed */
FIPS_selftest_check();
}
}
I would like to see these tests only run if /proc/sys/crypto/fips_enabled
exists, and is 1. This still meets the original proposal as written in the
1553309 thread:
1. openssl must read a 1 from /proc/sys/crypto/fips_enabled.
2. The selftests must pass
3. The integrity check must pass
To see the performance differences you can build and time the following
program:
#include
#include
int main() {
OpenSSL_add_ssl_algorithms();
}
To measure the system performance without FIPS I installed 1.0.2g-
1ubuntu2 from: https://launchpad.net/ubuntu/+source/openssl/1.0.2g-
1ubuntu2 on both armhf and amd64. I have also recompiled 1.0.2g-
1ubuntu4.1 with the call to FIPS_mode_set(1) commented out.
When I run the original 1.0.2g-1ubuntu4.1 on my Raspberry Pi I see the
following times:
real0m0.690s
real0m0.683s
real0m0.705s
real0m0.690s
The same system with 1.0.2g-1ubuntu4.1 modified and the call to
FIPS_mode_set(1) commented out:
real0m0.010s
real0m0.010s
real0m0.009s
real0m0.012s
real0m0.010s
The same system with 1.0.2g-1ubuntu2:
real0m0.010s
real0m0.009s
real0m0.009s
real0m0.011s
real0m0.012s
Here is some information about my system:
$ lsb_release -rd
Description:Ubuntu 16.04 LTS
Release:16.04
$ apt-cache policy libssl1.0.0
libssl1.0.0:
Installed: 1.0.2g-1ubuntu4.1
Candidate: 1.0.2g-1ubuntu4.1
Version table:
*** 1.0.2g-1ubuntu4.1 500
500 http://ports.ubuntu.com/ubuntu-ports xenial-security/main armhf
Packages 500 http://ports.ubuntu.com/ubuntu-ports xenial-updates/main armhf
Packages 100 /var/lib/dpkg/status
1.0.2g-1ubuntu4 500
500 http://ports.ubuntu.com/ubuntu-ports xenial/main armhf Packages
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1591797/+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 1614210] Re: Remove incomplete fips in openssl in xenial.
I can confirm that 1.0.2g-1ubuntu4.3 in xenial-proposed on armhf
resolves the bug I described in
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1591797.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1614210
Title:
Remove incomplete fips in openssl in xenial.
Status in openssl package in Ubuntu:
Fix Released
Status in openssl source package in Xenial:
Fix Committed
Status in openssl source package in Yakkety:
Fix Released
Bug description:
Package: openssl-1.0.2g-1ubuntu4.1
Distro: xenial
The openssl contains incomplete fips patches. In light that the fips
is incomplete and will not be completed in the main archive and they
are impacting customers, they should be withdrawn. See lp bugs
1593953, 1591797, 1594748, 1588524, 1613658. Removal of these fips
patches will remove these fips-related issues.
[Test case]
1. Problem in 1594748
Note: this problem was reported in upstream openssl and testcase posted there
also.
https://rt.openssl.org/Ticket/Display.html?id=4559
CRYPTO_set_mem_functions() always returns 0 because library
initialization within fips code already calls CRYPTO_malloc() and
disables it.
This testcase should cause openssl to abort, but instead it returns a
context.
#include
#include
#include
void * my_alloc(size_t n) { abort(); }
void my_free(void *p) { abort(); }
void * my_realloc(void *p, size_t n) { abort(); }
int main(int argc, const char **argv)
{
const SSL_METHOD *method;
SSL_CTX *ctx;
CRYPTO_set_mem_functions(my_alloc, my_realloc, my_free);
SSL_library_init();
method = SSLv23_client_method();
ctx = SSL_CTX_new(method);
printf("Got ctx %p\n", ctx);
return 0;
}
2. Problem in 1593953
EC key generation allows user to generate keys using EC curves that the EC
sign and verify
do not support when OPENSSL_FIPS is defined.
Testcase taken from lp #1593953
openssl ecparam -genkey -name Oakley-EC2N-4
will fail when OPENSSL_FIPS is defined since it causes a fips key-pair
consistency check to be done.
Otherwise, without OPENSSL_FIPS defined, the check is not done.
3. Problem reported in 1588524
Error code being skipped...
Testcase taken from lp #1588524
#include
#include
int main() {
int rc;
unsigned long fips_err;
SSL_library_init();
SSL_load_error_strings();
ERR_load_crypto_strings();
OpenSSL_add_all_algorithms();
rc = FIPS_mode_set(1);
fips_err = ERR_peek_last_error();
// FIPS_mode_set will return 0 on failure, which is expected if
// the FIPS module is not compiled. In this case, we should then
// be able to get the error code
// CRYPTO_R_FIPS_MODE_NOT_SUPPORTED (0xf06d065)
// https://wiki.openssl.org/index.php/FIPS_mode_set%28%29
printf("%d %lu\n", rc, fips_err);
ERR_print_errors_fp(stdout);
ERR_free_strings();
return 0;
}
Should report an error message.
[ Regression potential ]
Removing the fips patches should decrease regression potential of openssl in
the main archive.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1614210/+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 1591797] Re: Only run FIPS self tests when FIPS is enabled
Marc Deslauriers,
Will this change to remove the FIPS patches be backported and released
in Xenial?
-- Ken
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1591797
Title:
Only run FIPS self tests when FIPS is enabled
Status in openssl package in Ubuntu:
Fix Released
Bug description:
The FIPS changes added in 1.0.2g-1ubuntu3/1.0.2g-1ubuntu4 as discussed
in https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1553309
always run the FIPS self tests independent of FIPS being enabled (via
/proc/sys/crypto/fips_enabled).
The performance impact of running these FIPS tests on armhf
(beaglebone and raspberry pi 2&3) is significant (~ 700ms). On amd64
it is measurable but far less significant (~ 10ms). On a long running
process this may be insignificant, but for command line tools this is
problematic. I've seen performance differences with wget, dig,
nslookup, and host. I am sure there are others. The specific numbers
above are from the sample code below.
The relevant initialization can be found in crypto/o_init.c:
static void init_fips_mode(void)
{
char buf[2] = "0";
int fd;
/* Ensure the selftests always run */
FIPS_mode_set(1);
/* For now, do not enforce fips mode via env var
if (getenv("OPENSSL_FORCE_FIPS_MODE") != NULL) {
buf[0] = '1';
} else if ((fd = open(FIPS_MODE_SWITCH_FILE, O_RDONLY)) >= 0) { */
if ((fd = open(FIPS_MODE_SWITCH_FILE, O_RDONLY)) >= 0) {
while (read(fd, buf, sizeof(buf)) < 0 && errno == EINTR) ; close(fd);
}
/* Failure reading the fips mode switch file means just not
* switching into FIPS mode. We would break too many things
* otherwise..
*/
if (buf[0] != '1') {
/* drop down to non-FIPS mode if it is not requested */
FIPS_mode_set(0);
} else {
/* abort if selftest failed */
FIPS_selftest_check();
}
}
I would like to see these tests only run if /proc/sys/crypto/fips_enabled
exists, and is 1. This still meets the original proposal as written in the
1553309 thread:
1. openssl must read a 1 from /proc/sys/crypto/fips_enabled.
2. The selftests must pass
3. The integrity check must pass
To see the performance differences you can build and time the following
program:
#include
#include
int main() {
OpenSSL_add_ssl_algorithms();
}
To measure the system performance without FIPS I installed 1.0.2g-
1ubuntu2 from: https://launchpad.net/ubuntu/+source/openssl/1.0.2g-
1ubuntu2 on both armhf and amd64. I have also recompiled 1.0.2g-
1ubuntu4.1 with the call to FIPS_mode_set(1) commented out.
When I run the original 1.0.2g-1ubuntu4.1 on my Raspberry Pi I see the
following times:
real0m0.690s
real0m0.683s
real0m0.705s
real0m0.690s
The same system with 1.0.2g-1ubuntu4.1 modified and the call to
FIPS_mode_set(1) commented out:
real0m0.010s
real0m0.010s
real0m0.009s
real0m0.012s
real0m0.010s
The same system with 1.0.2g-1ubuntu2:
real0m0.010s
real0m0.009s
real0m0.009s
real0m0.011s
real0m0.012s
Here is some information about my system:
$ lsb_release -rd
Description:Ubuntu 16.04 LTS
Release:16.04
$ apt-cache policy libssl1.0.0
libssl1.0.0:
Installed: 1.0.2g-1ubuntu4.1
Candidate: 1.0.2g-1ubuntu4.1
Version table:
*** 1.0.2g-1ubuntu4.1 500
500 http://ports.ubuntu.com/ubuntu-ports xenial-security/main armhf
Packages 500 http://ports.ubuntu.com/ubuntu-ports xenial-updates/main armhf
Packages 100 /var/lib/dpkg/status
1.0.2g-1ubuntu4 500
500 http://ports.ubuntu.com/ubuntu-ports xenial/main armhf Packages
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1591797/+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 1591797] [NEW] Only run FIPS self tests when FIPS is enabled
Public bug reported:
The FIPS changes added in 1.0.2g-1ubuntu3/1.0.2g-1ubuntu4 as discussed
in https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1553309 always
run the FIPS self tests independent of FIPS being enabled (via
/proc/sys/crypto/fips_enabled).
The performance impact of running these FIPS tests on armhf (beaglebone
and raspberry pi 2&3) is significant (~ 700ms). On amd64 it is
measurable but far less significant (~ 10ms). On a long running process
this may be insignificant, but for command line tools this is
problematic. I've seen performance differences with wget, dig,
nslookup, and host. I am sure there are others. The specific numbers
above are from the sample code below.
The relevant initialization can be found in crypto/o_init.c:
static void init_fips_mode(void)
{
char buf[2] = "0";
int fd;
/* Ensure the selftests always run */
FIPS_mode_set(1);
/* For now, do not enforce fips mode via env var
if (getenv("OPENSSL_FORCE_FIPS_MODE") != NULL) {
buf[0] = '1';
} else if ((fd = open(FIPS_MODE_SWITCH_FILE, O_RDONLY)) >= 0) { */
if ((fd = open(FIPS_MODE_SWITCH_FILE, O_RDONLY)) >= 0) {
while (read(fd, buf, sizeof(buf)) < 0 && errno == EINTR) ; close(fd);
}
/* Failure reading the fips mode switch file means just not
* switching into FIPS mode. We would break too many things
* otherwise..
*/
if (buf[0] != '1') {
/* drop down to non-FIPS mode if it is not requested */
FIPS_mode_set(0);
} else {
/* abort if selftest failed */
FIPS_selftest_check();
}
}
I would like to see these tests only run if /proc/sys/crypto/fips_enabled
exists, and is 1. This still meets the original proposal as written in the
1553309 thread:
1. openssl must read a 1 from /proc/sys/crypto/fips_enabled.
2. The selftests must pass
3. The integrity check must pass
To see the performance differences you can build and time the following program:
#include
#include
int main() {
OpenSSL_add_ssl_algorithms();
}
To measure the system performance without FIPS I installed 1.0.2g-
1ubuntu2 from: https://launchpad.net/ubuntu/+source/openssl/1.0.2g-
1ubuntu2 on both armhf and amd64. I have also recompiled 1.0.2g-
1ubuntu4.1 with the call to FIPS_mode_set(1) commented out.
When I run the original 1.0.2g-1ubuntu4.1 on my Raspberry Pi I see the
following times:
real0m0.690s
real0m0.683s
real0m0.705s
real0m0.690s
The same system with 1.0.2g-1ubuntu4.1 modified and the call to
FIPS_mode_set(1) commented out:
real0m0.010s
real0m0.010s
real0m0.009s
real0m0.012s
real0m0.010s
The same system with 1.0.2g-1ubuntu2:
real0m0.010s
real0m0.009s
real0m0.009s
real0m0.011s
real0m0.012s
Here is some information about my system:
$ lsb_release -rd
Description:Ubuntu 16.04 LTS
Release:16.04
$ apt-cache policy libssl1.0.0
libssl1.0.0:
Installed: 1.0.2g-1ubuntu4.1
Candidate: 1.0.2g-1ubuntu4.1
Version table:
*** 1.0.2g-1ubuntu4.1 500
500 http://ports.ubuntu.com/ubuntu-ports xenial-security/main armhf
Packages 500 http://ports.ubuntu.com/ubuntu-ports xenial-updates/main armhf
Packages 100 /var/lib/dpkg/status
1.0.2g-1ubuntu4 500
500 http://ports.ubuntu.com/ubuntu-ports xenial/main armhf Packages
** Affects: openssl (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1591797
Title:
Only run FIPS self tests when FIPS is enabled
Status in openssl package in Ubuntu:
New
Bug description:
The FIPS changes added in 1.0.2g-1ubuntu3/1.0.2g-1ubuntu4 as discussed
in https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1553309
always run the FIPS self tests independent of FIPS being enabled (via
/proc/sys/crypto/fips_enabled).
The performance impact of running these FIPS tests on armhf
(beaglebone and raspberry pi 2&3) is significant (~ 700ms). On amd64
it is measurable but far less significant (~ 10ms). On a long running
process this may be insignificant, but for command line tools this is
problematic. I've seen performance differences with wget, dig,
nslookup, and host. I am sure there are others. The specific numbers
above are from the sample code below.
The relevant initialization can be found in crypto/o_init.c:
static void init_fips_mode(void)
{
char buf[2] = "0";
int fd;
/* Ensure the selftests always run */
FIPS_mode_set(1);
/* For now, do not enforce fips mode via env var
if (getenv("OPENSSL_FORCE_FIPS_MODE") != NULL) {
buf[0] = '1';
} else if ((fd = open(FIPS_MODE_SWITCH_FILE, O_RDONLY)) >= 0) { */
if ((fd = open(FIPS_MODE_SWITCH_FILE, O_RDONLY)) >= 0) {
while (read(fd, buf, sizeof(buf)) < 0 && errno == EINTR) ; close(fd);
}
/*
[Touch-packages] [Bug 1313513] Re: mountall does not honour _netdev
I seem to be running into this bug on a new build of 14.04.4 when using an LVM on a multipathed ISCSI drive which I am trying to mount at /var/lib/mysql. I'm no upstart guru, so if there is anything I can post to help verify if it is this bug that is causing an issue please let me know. If I just add the 'nobootwait' option to fstab will mysql still wait till the iscsi drive is mounted correctly? Thanks, Steve -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mountall in Ubuntu. https://bugs.launchpad.net/bugs/1313513 Title: mountall does not honour _netdev Status in mountall package in Ubuntu: Confirmed Bug description: Hi, This is a fresh install of Ubuntu 14.04 LTS AMD64. I tried configuring a Ceph Rados Block Device (rbd) to be mounted during boot on /var/lib/one, containing my OpenNebula configuration and database. The idea being that should the machine go belly up, I'll have an up- to-date snapshot of the OpenNebula data on Ceph to mount on the new frontend machine. /etc/ceph/rbdmap is configured, I set up /etc/fstab with an entry: /dev/rbd/pool/rbdname /var/lib/one xfs defaults,_netdev 0 1 then rebooted. According to mount(8), _netdev is supposed to tell mountall to skip mounting this device until the network is up. As seen from the attached snapshot, it doesn't bother to wait, and blindly tries to mount the RBD before connecting to Ceph: this will never work. mountall seems to rely on *knowing* a list of network file systems: this means when someone comes up with a new network file system, or uses a conventional disk file system with a remote block device, mountall's heuristic falls flat on its face as has been demonstrated here. The problem would also exist for iSCSI, AoE, FibreChannel, nbd and drbd devices. Due to bug 1313497, the keyboard is non-functional. Recovery is useless as the keyboard is broken there too, and now the machine is waiting for a keypress it will never see due to that bug. A headless system would similarly have this problem. Two suggestions I would have: 1. mountall should honour _netdev to decide whether to mount a device or not: this gives the user the means to manually tell mountall that the device needs network access to operate even if the filesystem looks to be local. I'd wager that if the user specified _netdev, they probably meant it and likely know better than mountall. 2. mountall should time out after a predefined period and NEVER wait indefinitely: even if the disk is local. If a disk goes missing, then it is better the machine tries to boot in its degraded state so it can be remotely managed and raise an alarm, than to wait for someone to notice the machine being down. Unfortunately since the machine is now effectively bricked, I can only grep proxy server logs to see what packages got installed. mountall_2.53_amd64.deb seems to be the culprit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1313513/+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 1238194] Re: keyboard doesn't work to enter password with encrypted partitions ubuntu 13.10 saucy
I am encountering this same issue running 15.10 as a VM in hyper-v as generation 2 vm. I can't work around it as there is no vm, and disk is encrypted, Sucks as i'll have to reinstall from scratch. Any fix that can be made during install? I tried the update-initramfs -u -k all but it doesn't fix the issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1238194 Title: keyboard doesn't work to enter password with encrypted partitions ubuntu 13.10 saucy Status in initramfs-tools: New Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Precise: Fix Released Status in initramfs-tools source package in Saucy: Fix Released Bug description: [Justification] With the kernel in 13.10, some systems use a different USB host driver than previously. Failing to include this driver in the initramfs causes regressions for users who need to interact with the system in early boot using a USB keyboard, such as users with an encrypted root filesystem. Such systems are not bootable with this host driver missing. [Test case] 1. On an affected system, reboot to a kernel from 13.04. 2. Install the initramfs-tools package from -proposed. 3. Reboot to the kernel from 13.10. 4. Verify that you are able to type your passphrase at the prompt in the initramfs. [Regression potential] Minimal. The update-initramfs script will ignore missing modules (such as the many other modules in the list which are built-ins), and the only change made is to copy the module into the initramfs: it will only be loaded in the initramfs if udev determines it's needed, just as it would load it after switching to the root filesystem. Is the same problem as here but in the new ubuntu 13.10 saucy https://bugs.launchpad.net/bugs/1066376 I just can't use (i can install) a encrypted partition because when is time to introduce the password to unlock partition keyboard is not working. I don't know how to edit a bug to report it afects other version of ubuntu so i created this new bug... To manage notifications about this bug go to: https://bugs.launchpad.net/initramfs-tools/+bug/1238194/+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 1440537] [NEW] Friends app not updating after upgrade to vivid
Public bug reported: Last updates were 192 days ago (last time I used the app). I attached the friends.log file. ** Affects: friends-app (Ubuntu) Importance: Undecided Status: New ** Attachment added: friends.log https://bugs.launchpad.net/bugs/1440537/+attachment/430/+files/friends.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to friends-app in Ubuntu. https://bugs.launchpad.net/bugs/1440537 Title: Friends app not updating after upgrade to vivid Status in friends-app package in Ubuntu: New Bug description: Last updates were 192 days ago (last time I used the app). I attached the friends.log file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/friends-app/+bug/1440537/+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 1373217] Re: package tzdata 2014e-0ubuntu0.12.04 failed to install/upgrade: unable to make backup link of `./usr/share/zoneinfo/ROC' before installing new version: Operation not
This bug now affects me on both 12.04.5 LTS x64 as well as 14.04 LTS x64. Package: /var/cache/apt/archives/tzdata_2014i-0ubuntu0.12.04_all.deb Error: unable to make backup link of `./usr/share/zoneinfo/ROC' before installing new version: Operation not permitted Tried to install time-zone and daylight-saving time data update. Same issue that occurred during 14.04 distribution upgrade. Please investigate this issue immediately, I believe this can become a very serious bug in the entire Ubuntu timezone system, especially if it has anything to do with why my apt package became broken after a bad update. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1373217 Title: package tzdata 2014e-0ubuntu0.12.04 failed to install/upgrade: unable to make backup link of `./usr/share/zoneinfo/ROC' before installing new version: Operation not permitted Status in “tzdata” package in Ubuntu: New Bug description: I posted about this problem on askubuntu.com. Instead of reiterating everything again, please see my post here: http://askubuntu.com/questions/520714/cannot-update-or-install-new- packages-kubuntu-14-04-1-after-upgrade-from-12-04-5 This issue must be a bug, I'm just not sure if it is a situation that is reproduceable or not. The bug seemed to occur at the upgrade process while I still was logged into my Kubuntu 12.04 environment. Version prior to upgrade - Kubuntu 12.04.5 LTS x86_64 Upgraded with Kubuntu 14.04.1 LTS x86_64 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: tzdata 2014e-0ubuntu0.12.04 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 Date: Tue Sep 23 20:38:23 2014 DuplicateSignature: package:tzdata:2014e-0ubuntu0.12.04:unable to make backup link of `./usr/share/zoneinfo/ROC' before installing new version: Operation not permitted ErrorMessage: unable to make backup link of `./usr/share/zoneinfo/ROC' before installing new version: Operation not permitted InstallationDate: Installed on 2014-04-11 (165 days ago) InstallationMedia: Kubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120423) PackageArchitecture: all SourcePackage: tzdata Title: package tzdata 2014e-0ubuntu0.12.04 failed to install/upgrade: unable to make backup link of `./usr/share/zoneinfo/ROC' before installing new version: Operation not permitted UpgradeStatus: Upgraded to trusty on 2014-09-06 (18 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1373217/+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 1373217] [NEW] package tzdata 2014e-0ubuntu0.12.04 failed to install/upgrade: unable to make backup link of `./usr/share/zoneinfo/ROC' before installing new version: Operation no
Public bug reported: I posted about this problem on askubuntu.com. Instead of reiterating everything again, please see my post here: http://askubuntu.com/questions/520714/cannot-update-or-install-new- packages-kubuntu-14-04-1-after-upgrade-from-12-04-5 This issue must be a bug, I'm just not sure if it is a situation that is reproduceable or not. The bug seemed to occur at the upgrade process while I still was logged into my Kubuntu 12.04 environment. Version prior to upgrade - Kubuntu 12.04.5 LTS x86_64 Upgraded with Kubuntu 14.04.1 LTS x86_64 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: tzdata 2014e-0ubuntu0.12.04 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 Date: Tue Sep 23 20:38:23 2014 DuplicateSignature: package:tzdata:2014e-0ubuntu0.12.04:unable to make backup link of `./usr/share/zoneinfo/ROC' before installing new version: Operation not permitted ErrorMessage: unable to make backup link of `./usr/share/zoneinfo/ROC' before installing new version: Operation not permitted InstallationDate: Installed on 2014-04-11 (165 days ago) InstallationMedia: Kubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120423) PackageArchitecture: all SourcePackage: tzdata Title: package tzdata 2014e-0ubuntu0.12.04 failed to install/upgrade: unable to make backup link of `./usr/share/zoneinfo/ROC' before installing new version: Operation not permitted UpgradeStatus: Upgraded to trusty on 2014-09-06 (18 days ago) ** Affects: tzdata (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1373217 Title: package tzdata 2014e-0ubuntu0.12.04 failed to install/upgrade: unable to make backup link of `./usr/share/zoneinfo/ROC' before installing new version: Operation not permitted Status in “tzdata” package in Ubuntu: New Bug description: I posted about this problem on askubuntu.com. Instead of reiterating everything again, please see my post here: http://askubuntu.com/questions/520714/cannot-update-or-install-new- packages-kubuntu-14-04-1-after-upgrade-from-12-04-5 This issue must be a bug, I'm just not sure if it is a situation that is reproduceable or not. The bug seemed to occur at the upgrade process while I still was logged into my Kubuntu 12.04 environment. Version prior to upgrade - Kubuntu 12.04.5 LTS x86_64 Upgraded with Kubuntu 14.04.1 LTS x86_64 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: tzdata 2014e-0ubuntu0.12.04 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 Date: Tue Sep 23 20:38:23 2014 DuplicateSignature: package:tzdata:2014e-0ubuntu0.12.04:unable to make backup link of `./usr/share/zoneinfo/ROC' before installing new version: Operation not permitted ErrorMessage: unable to make backup link of `./usr/share/zoneinfo/ROC' before installing new version: Operation not permitted InstallationDate: Installed on 2014-04-11 (165 days ago) InstallationMedia: Kubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120423) PackageArchitecture: all SourcePackage: tzdata Title: package tzdata 2014e-0ubuntu0.12.04 failed to install/upgrade: unable to make backup link of `./usr/share/zoneinfo/ROC' before installing new version: Operation not permitted UpgradeStatus: Upgraded to trusty on 2014-09-06 (18 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1373217/+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
