[Touch-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
Set to priority Low since you need to be using both the Nvidia proprietary driver and automatic logins to hit this bug. ** No longer affects: gnome-shell (Ubuntu) ** No longer affects: gnome-shell (Ubuntu Eoan) ** Also affects: nvidia-graphics-drivers-430 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-430 (Ubuntu) Status: New => Confirmed ** Changed in: nvidia-graphics-drivers-430 (Ubuntu) Importance: Undecided => Low ** Also affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: New => Confirmed ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided => Low ** Changed in: gdm3 (Ubuntu Eoan) Status: Incomplete => Confirmed ** Changed in: gnome-session (Ubuntu) Status: Incomplete => Confirmed ** Changed in: gnome-session (Ubuntu Eoan) Status: Incomplete => Confirmed ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu) Status: New => Confirmed ** Changed in: systemd (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in gdm3 source package in Eoan: Confirmed Status in gnome-session source package in Eoan: Confirmed Status in nvidia-graphics-drivers-435 source package in Eoan: Confirmed Bug description: I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0:
[Touch-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
Sorry about the noise. I have shotgunned a more appropriate set of packages related to this bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in gdm3 source package in Eoan: Confirmed Status in gnome-session source package in Eoan: Confirmed Status in nvidia-graphics-drivers-435 source package in Eoan: Confirmed Bug description: I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+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 1577197] Re: Pulseaudio bluez5-util.c: TryAcquire() failed - Operation Not Authorized
** Changed in: bluez (Ubuntu) Importance: High => Medium ** Changed in: pulseaudio (Ubuntu) Importance: High => Undecided ** Changed in: bluez (Ubuntu) Importance: Medium => Undecided -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1577197 Title: Pulseaudio bluez5-util.c: TryAcquire() failed - Operation Not Authorized Status in bluez package in Ubuntu: Confirmed Status in indicator-sound package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Confirmed Bug description: Pulseaudio outright stops audio via Bluetooth after sleep or prolonged period of time. Only restart fixes the issue. This started early 2016 in 15.10. Issue is discussed here as well http://askubuntu.com/questions/763539/bluetooth-speaker-no-sound-in-ubuntu-16-04 and mentioned in other unrelated bugs. Ubuntu Xenial 16.04 LTS The log below: May 1 17:18:07 jalexoidmobile pulseaudio[2884]: [pulseaudio] module-bluez5-device.c: Default profile not connected, selecting off profile May 1 17:18:07 jalexoidmobile bluetoothd[7349]: /org/bluez/hci0/dev_00_02_3C_05_99_F2/fd4: fd(35) ready May 1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Supervising 3 threads of 1 processes of 1 users. May 1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Successfully made thread 10967 of process 2884 (n/a) owned by '1000' RT at priority 5. May 1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Supervising 4 threads of 1 processes of 1 users. May 1 17:18:07 jalexoidmobile pulseaudio[2884]: [pulseaudio] bluez5-util.c: Transport TryAcquire() failed for transport /org/bluez/hci0/dev_00_02_3C_05_99_F2/fd4 (Operation Not Authorized) May 1 17:18:07 jalexoidmobile kernel: [20583.032442] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input24 May 1 17:18:19 jalexoidmobile pulseaudio[2884]: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 006: ID 04f2:b2da Chicony Electronics Co., Ltd thinkpad t430s camera Bus 001 Device 008: ID 0a5c:21e6 Broadcom Corp. BCM20702 Bluetooth 4.0 [ThinkPad] Bus 001 Device 004: ID 147e:2020 Upek TouchChip Fingerprint Coprocessor (WBF advanced mode) Bus 001 Device 003: ID 17ef:1003 Lenovo Integrated Smart Card Reader Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub [20388.983474] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [20389.070114] usb 1-1.4: New USB device found, idVendor=0a5c, idProduct=21e6 [20389.070120] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [20389.070122] usb 1-1.4: Product: BCM20702A0 [20389.070124] usb 1-1.4: Manufacturer: Broadcom Corp [20389.070126] usb 1-1.4: SerialNumber: 446D578686DD [20389.076232] Bluetooth: hci0: BCM: chip id 63 [20389.092220] Bluetooth: hci0: BCM20702A [20389.093225] Bluetooth: hci0: BCM20702A1 (001.002.014) build [20389.551476] wlan0: authenticate with a0:63:91:2f:3f:ed [20389.554391] wlan0: send auth to a0:63:91:2f:3f:ed (try 1/3) [20389.557790] wlan0: authenticated [20389.558339] wlan0: associate with a0:63:91:2f:3f:ed (try 1/3) [20389.562209] wlan0: RX AssocResp from a0:63:91:2f:3f:ed (capab=0x1411 status=0 aid=2) [20389.581260] wlan0: associated [20389.581369] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [20389.830185] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1669 [20389.846186] Bluetooth: hci0: Broadcom Bluetooth Device [20418.269466] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input23 [20583.032442] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input24 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1577197/+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 1856428] Re: Disable TLS1.0, TLS 1.1
** Also affects: golang-1.13 (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Disable TLS1.0, TLS 1.1 + Disable TLS below 1.2 by default -- 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/1856428 Title: Disable TLS below 1.2 by default Status in gnutls28 package in Ubuntu: Fix Committed Status in golang-1.13 package in Ubuntu: New Status in nss package in Ubuntu: Fix Committed Status in openssl package in Ubuntu: Fix Committed Bug description: Disable TLS 1.0, TLS1.1, DTLS1.0 As part of focal commitment, we shall disable obsolete protocols by default. Users can override this behaviour with a config file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnutls28/+bug/1856428/+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 1859096] Re: No sound or Crazy sound on Display port since kernel change to 5.4 (but 5.3.0-24 works)
** Summary changed: - No sound or Crazy sound on Display port since kernel change to 5.4 + No sound or Crazy sound on Display port since kernel change to 5.4 (but 5.3.0-24 works) ** Package changed: xorg (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1859096 Title: No sound or Crazy sound on Display port since kernel change to 5.4 (but 5.3.0-24 works) Status in linux package in Ubuntu: New Bug description: I use Nvidia driver 440. The sound became crazy on DisplayPort. Volume is not adjustable. I have either full volume or nothing. sound is crazy on my GTX1650 video card. If I use Nouveau driver I have no sound on my Display port. If I boot with 5.3.0-24 kernel sound is OK with Nivdia driver. But no sound with nouveau driver. Same things append on Focal and on Ubuntu 19.10. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] est un dossier: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.44 Sun Dec 8 03:38:56 UTC 2019 GCC version: gcc version 9.2.1 20191130 (Ubuntu 9.2.1-21ubuntu1) ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: MATE Date: Fri Jan 10 00:26:20 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.44, 5.4.0-9-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd TU117 [GeForce GTX 1650] [1458:3fcb] InstallationDate: Installed on 2020-01-05 (4 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Alpha amd64 (20200104) MachineType: Micro-Star International Co., Ltd. MS-7B51 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-9-generic root=UUID=0b5d6829-5bb4-40e3-9fee-0fdec99e5f5a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/21/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.50 dmi.board.asset.tag: Default string dmi.board.name: MPG Z390 GAMING PLUS (MS-7B51) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.50:bd02/21/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B51:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMPGZ390GAMINGPLUS(MS-7B51):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7B51 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859096/+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 1859101] Re: stuck on 800x600
Thanks for the bug report. The first thing I notice is that the kernel doesn't have a driver for your GPU because it seems to be QEMU's "-vga std" option. So Xorg defaults to 800x600 and does not support any other modes besides the default one... [27.274] (==) FBDEV(0): Depth 24, (==) framebuffer bpp 24 [27.274] (==) FBDEV(0): RGB weight 888 [27.274] (==) FBDEV(0): Default visual is TrueColor [27.274] (==) FBDEV(0): Using gamma correction (1.0, 1.0, 1.0) [27.275] (II) FBDEV(0): hardware: EFI VGA (video memory: 1408kB) [27.275] (II) FBDEV(0): checking modes against framebuffer device... [27.275] (II) FBDEV(0): checking modes against monitor... [27.275] (--) FBDEV(0): Virtual size is 800x600 (pitch 800) [27.275] (**) FBDEV(0): Built-in mode "current": 48.0 MHz, 46.9 kHz, 75.1 Hz [27.275] (II) FBDEV(0): Modeline "current"x0.0 48.00 800 832 928 1024 600 604 608 624 -hsync -vsync -csync (46.9 kHz b) [27.275] (==) FBDEV(0): DPI set to (96, 96) This is understandably annoying, but your only other options are to: * Get SeaBIOS/QEMU to support other modes; or * Get QEMU to emulate a different GPU type using "-vga ..." ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Invalid -- 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/1859101 Title: stuck on 800x600 Status in xorg-server package in Ubuntu: Invalid Bug description: Intel integrated graphics, HPE DL360 Gen6 server VM running Ubuntu 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jan 10 00:22:23 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Device [1234:] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc. Device [1af4:1100] InstallationDate: Installed on 2020-01-06 (3 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lsusb: Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-74-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro maybe-ubiquity Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.12.1-0-ga5cab58e9a3f-prebuilt.qemu.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.1 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.12.1-0-ga5cab58e9a3f-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.1:cvnQEMU:ct1:cvrpc-i440fx-4.1: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.1 dmi.sys.vendor: QEMU version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git1912100730.f66d39~oibaf~b version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1859101/+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 1856428] Re: Disable TLS1.0, TLS 1.1
** Changed in: gnutls28 (Ubuntu) Status: In Progress => Fix Committed ** Changed in: nss (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nss in Ubuntu. https://bugs.launchpad.net/bugs/1856428 Title: Disable TLS1.0, TLS 1.1 Status in gnutls28 package in Ubuntu: Fix Committed Status in nss package in Ubuntu: Fix Committed Status in openssl package in Ubuntu: Fix Committed Bug description: Disable TLS 1.0, TLS1.1, DTLS1.0 As part of focal commitment, we shall disable obsolete protocols by default. Users can override this behaviour with a config file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnutls28/+bug/1856428/+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 1859101] [NEW] stuck on 800x600
Public bug reported: Intel integrated graphics, HPE DL360 Gen6 server VM running Ubuntu 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jan 10 00:22:23 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Device [1234:] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc. Device [1af4:1100] InstallationDate: Installed on 2020-01-06 (3 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lsusb: Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-74-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro maybe-ubiquity Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.12.1-0-ga5cab58e9a3f-prebuilt.qemu.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.1 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.12.1-0-ga5cab58e9a3f-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.1:cvnQEMU:ct1:cvrpc-i440fx-4.1: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.1 dmi.sys.vendor: QEMU version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git1912100730.f66d39~oibaf~b version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages ubuntu uec-images -- 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/1859101 Title: stuck on 800x600 Status in xorg package in Ubuntu: New Bug description: Intel integrated graphics, HPE DL360 Gen6 server VM running Ubuntu 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jan 10 00:22:23 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Device [1234:] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc. Device [1af4:1100] InstallationDate: Installed on 2020-01-06 (3 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lsusb: Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-74-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro maybe-ubiquity Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.12.1-0-ga5cab58e9a3f-prebuilt.qemu.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.1 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.12.1-0-ga5cab58e9a3f-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.1:cvnQEMU:ct1:cvrpc-i440fx-4.1: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.1 dmi.sys.vendor: QEMU version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
[Touch-packages] [Bug 1859013] Re: openssh tests use "not valid yet" certificate from 2020, which is now valid
** Tags added: block-proposed-bionic block-proposed-disco block-
proposed-eoan block-proposed-xenial
** Description changed:
- openssh tests use "not valid yet" certificate from 2020, which is now
- valid
+ [Impact]
-
https://anongit.mindrot.org/openssh.git/commit/?id=ff31f15773ee173502eec4d7861ec56f26bba381
+ * regression testsuite uses 1st of January 2020 as the date in the
+ future, however that is now in the past making autpkgtests fail.
- this causes autopkgtest regression suite fail in 2020
+ [Test Case]
- grep 20200101 -r .
- ./openssh-7.6p1/regress/cert-hostkey.sh:test_one "cert not yet valid" failure
"-h -V20200101:20300101"
- ./openssh-7.6p1/regress/cert-userkey.sh:test_one "cert not yet valid" failure
"-n ${USER} -V20200101:20300101"
- ./openssh-7.2p2/regress/cert-hostkey.sh:test_one "cert not yet valid" failure
"-h -V20200101:20300101"
- ./openssh-7.2p2/regress/cert-userkey.sh:test_one "cert not yet valid" failure
"-n ${USER} -V20200101:20300101"
- ./openssh-6.6p1/regress/cert-hostkey.sh:test_one "cert not yet valid" failure
"-h -V20200101:20300101"
- ./openssh-6.6p1/regress/cert-userkey.sh:test_one "cert not yet valid" failure
"-n ${USER} -V20200101:20300101"
- ./openssh-5.9p1/regress/cert-hostkey.sh:test_one "cert not yet valid" failure
"-h -V20200101:20300101"
- ./openssh-5.9p1/regress/cert-userkey.sh:test_one "cert not yet valid" failure
"-n ${USER} -V20200101:20300101"
+ * Autopkgtest must pass
+
+ [Regression Potential]
+
+ * Testsuite assertion update only
+
+ [Other Info]
+
+ This is a staged update to be rolled up with any other openssh update in
+ the future.
fixed in debian https://tracker.debian.org/news/1092767/accepted-
openssh-181p1-4-source-into-unstable/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1859013
Title:
openssh tests use "not valid yet" certificate from 2020, which is now
valid
Status in openssh package in Ubuntu:
New
Status in openssh source package in Precise:
New
Status in openssh source package in Trusty:
New
Status in openssh source package in Xenial:
New
Status in openssh source package in Bionic:
New
Status in openssh source package in Disco:
New
Status in openssh source package in Eoan:
New
Status in openssh source package in Focal:
New
Bug description:
[Impact]
* regression testsuite uses 1st of January 2020 as the date in the
future, however that is now in the past making autpkgtests fail.
[Test Case]
* Autopkgtest must pass
[Regression Potential]
* Testsuite assertion update only
[Other Info]
This is a staged update to be rolled up with any other openssh update
in the future.
fixed in debian https://tracker.debian.org/news/1092767/accepted-
openssh-181p1-4-source-into-unstable/
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1859013/+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 1859096] [NEW] No sound or Crazy sound on Display port since kernel change to 5.4
Public bug reported: I use Nvidia driver 440. The sound became crazy on DisplayPort. Volume is not adjustable. I have either full volume or nothing. sound is crazy on my GTX1650 video card. If I use Nouveau driver I have no sound on my Display port. If I boot with 5.3.0-24 kernel sound is OK with Nivdia driver. But no sound with nouveau driver. Same things append on Focal and on Ubuntu 19.10. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] est un dossier: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.44 Sun Dec 8 03:38:56 UTC 2019 GCC version: gcc version 9.2.1 20191130 (Ubuntu 9.2.1-21ubuntu1) ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: MATE Date: Fri Jan 10 00:26:20 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.44, 5.4.0-9-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd TU117 [GeForce GTX 1650] [1458:3fcb] InstallationDate: Installed on 2020-01-05 (4 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Alpha amd64 (20200104) MachineType: Micro-Star International Co., Ltd. MS-7B51 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-9-generic root=UUID=0b5d6829-5bb4-40e3-9fee-0fdec99e5f5a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/21/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.50 dmi.board.asset.tag: Default string dmi.board.name: MPG Z390 GAMING PLUS (MS-7B51) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.50:bd02/21/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B51:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMPGZ390GAMINGPLUS(MS-7B51):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7B51 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal reproducible single-occurrence ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1859096 Title: No sound or Crazy sound on Display port since kernel change to 5.4 Status in xorg package in Ubuntu: New Bug description: I use Nvidia driver 440. The sound became crazy on DisplayPort. Volume is not adjustable. I have either full volume or nothing. sound is crazy on my GTX1650 video card. If I use Nouveau driver I have no sound on my Display port. If I boot with 5.3.0-24 kernel sound is OK with Nivdia driver. But no sound with nouveau driver. Same things append on Focal and on Ubuntu 19.10. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] est un dossier: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.44 Sun Dec 8 03:38:56 UTC 2019 GCC version: gcc version 9.2.1 20191130 (Ubuntu 9.2.1-21ubuntu1) ApportVersion:
[Touch-packages] [Bug 1838253] Re: Gigabyte X570 Aorus Elite: whine/beep when recording sound, not present under Windows
** Summary changed: - whine/beep when recording sound, not present under Windows + Gigabyte X570 Aorus Elite: whine/beep when recording sound, not present under Windows -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1838253 Title: Gigabyte X570 Aorus Elite: whine/beep when recording sound, not present under Windows Status in alsa-driver package in Ubuntu: New Bug description: When recording sound under Ubuntu 18.04 there is a whine/beep present. This is not the case under Windows 10, as such I suspect missing driver/software bits. See attachments for audio samples of both cases. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-20.21~18.04.1-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: az 1795 F pulseaudio /dev/snd/controlC2: az 1795 F pulseaudio /dev/snd/pcmC2D0p: az 1795 F...m pulseaudio /dev/snd/controlC0: az 1795 F pulseaudio CurrentDesktop: XFCE Date: Mon Jul 29 12:44:43 2019 InstallationDate: Installed on 2019-07-17 (11 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/12/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4g dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS ELITE dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4g:bd07/12/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSELITE:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSELITE:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X570 AORUS ELITE dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1838253/+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 1858802] Re: libblkid: no bcache UUID due to ambivalent detection of bcache and xfs_external_log for regular xfs in bcache backing device
Autopkgtests triggered against the PPA. Results/Exit-codes (all zero) focal $ curl -s 'https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal-mfo-lp1858802-sru/focal/amd64/u/util-linux/20200109_132227_94cc9@/result.tar' | tar x --to-stdout exitcode 0 eoan $ curl -s 'https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-mfo-lp1858802-sru/eoan/amd64/u/util-linux/20200109_132218_4d6ee@/result.tar' | tar x --to-stdout exitcode 0 disco curl -s 'https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco-mfo-lp1858802-sru/disco/amd64/u/util-linux/20200109_212330_3dad1@/result.tar' | tar x --to-stdout exitcode 0 bionic $ curl -s 'https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-mfo-lp1858802-sru/bionic/amd64/u/util-linux/20200109_132056_9828a@/result.tar' | tar x --to-stdout exitcode 0 xenial $ curl -s 'https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial-mfo-lp1858802-sru/xenial/amd64/u/util-linux/20200109_132002_7346b@/result.tar' | tar x --to-stdout exitcode 0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1858802 Title: libblkid: no bcache UUID due to ambivalent detection of bcache and xfs_external_log for regular xfs in bcache backing device Status in util-linux package in Ubuntu: In Progress Status in util-linux source package in Xenial: In Progress Status in util-linux source package in Bionic: In Progress Status in util-linux source package in Disco: In Progress Status in util-linux source package in Eoan: In Progress Status in util-linux source package in Focal: In Progress Status in util-linux package in Debian: Unknown Bug description: [Impact] * Users with an XFS filesystem on top of bcache (this is seen on some ceph, cloud deployments) might fail to reference the bcache device by UUID or other udev properties. * The journal of the regular XFS filesystem in the bcache device is incorrectly detected as an XFS external log; so two superblocks are detected (bcache and xfs_external_log). * Thus blkid fails with ambivalent superblocks detected then doesn't provide the usual udev properties (UUID, etc.) * The fix improves the probe function for XFS external log so it detects it's regular XFS and bails out. [Test Case] * See test steps detailed in comment #7 and later. - Create an XFS filesystem with the journal/log in the beginning of the bcache device (< 256K). - Stop the bcache device. - Run '$ blkid -o udev -p $BCACHE_BACKING_DEVICE'. $ sudo make-bcache -B $BACKING_DEV $ sudo mkfs.xfs -d agsize=16m -l agnum=0 -f $BCACHE_DEV $ echo 1 | sudo tee /sys/block/$(basename $BCACHE_DEV)/bcache/stop $ sudo blkid -o udev -p $BACKING_DEV [Regression Potential] * The patch only changes the detection function for XFS external log to be more general about the sector where the magic of regular XFS may be found (which is shifted inside the bcache.) * It still checks at sector zero (the only one checked previously), so this behavior didn't change. * Possible regressions are actual XFS external log devices that are not anymore detected as such. (Although that would probably indicate a different bug in libblkid.) [Other Info] * upstream commit: https://git.kernel.org/pub/scm/utils/util-linux/util-linux.git/commit/?id=d756af7d640c51ce8d1414607bd3f17eeecf2424 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1858802/+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 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
I get this error on a new minimal VM install with all LVM disks except '/boot': -- root@img-ults18:/var/log# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT loop0 7:00 89.1M 1 loop /snap/core/8268 loop1 7:10 88.5M 1 loop /snap/core/7270 sda 8:001G 0 disk ├─sda1 8:101M 0 part └─sda2 8:20 1021M 0 part /boot sdb 8:16 0 32G 0 disk ├─VGroot-LVroot 253:007G 0 lvm / ├─VGroot-LVtmp253:103G 0 lvm /tmp ├─VGroot-LVvar253:204G 0 lvm /var ├─VGroot-LVvartmp 253:303G 0 lvm /var/tmp ├─VGroot-VGlog253:404G 0 lvm /var/log ├─VGroot-LVaudit 253:502G 0 lvm /var/log/audit ├─VGroot-LVswap 253:604G 0 lvm [SWAP] └─VGroot-LVhome 253:705G 0 lvm /home sr011:01 1024M 0 rom root@img-ults18:/var/log# pvs PV VG Fmt Attr PSize PFree /dev/sdb VGroot lvm2 a-- <32.00g0 root@img-ults18:/var/log# vgs VG #PV #LV #SN Attr VSize VFree VGroot 1 8 0 wz--n- <32.00g0 root@img-ults18:/var/log# lvs -a LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert LVaudit VGroot -wi-ao 2.00g LVhome VGroot -wi-ao <5.00g LVroot VGroot -wi-ao 7.00g LVswap VGroot -wi-ao 4.00g LVtmpVGroot -wi-ao 3.00g LVvarVGroot -wi-ao 4.00g LVvartmp VGroot -wi-ao 3.00g VGlogVGroot -wi-ao 4.00g -- ... 0 packages can be updated. 0 updates are security updates. No mail. Last login: Thu Jan 9 21:09:04 2020 from 137.82.124.99 root@img-ults18:~# root@img-ults18:~# apt-get install selinux Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: policycoreutils selinux-policy-dummy selinux-utils The following packages will be REMOVED: apparmor snapd The following NEW packages will be installed: policycoreutils selinux selinux-policy-dummy selinux-utils 0 upgraded, 4 newly installed, 2 to remove and 0 not upgraded. Need to get 544 kB of archives. After this operation, 62.7 MB disk space will be freed. Do you want to continue? [Y/n] Get:1 http://mirror.it.ubc.ca/ubuntu bionic/universe amd64 selinux-utils amd64 2.7-2build2 [81.7 kB] Get:2 http://mirror.it.ubc.ca/ubuntu bionic/universe amd64 policycoreutils amd64 2.7-1 [450 kB] Get:3 http://mirror.it.ubc.ca/ubuntu bionic/universe amd64 selinux all 1:0.11 [11.2 kB] Get:4 http://mirror.it.ubc.ca/ubuntu bionic/universe amd64 selinux-policy-dummy all 0.1 [1,730 B] Fetched 544 kB in 0s (7,670 kB/s) Preconfiguring packages ... ... (Reading database ... 102901 files and directories currently installed.) Removing snapd (2.42.1+18.04) ... Removing apparmor (2.12-4ubuntu5.1) ... Selecting previously unselected package selinux-utils. (Reading database ... 102812 files and directories currently installed.) Preparing to unpack .../selinux-utils_2.7-2build2_amd64.deb ... Unpacking selinux-utils (2.7-2build2) ... Selecting previously unselected package policycoreutils. Preparing to unpack .../policycoreutils_2.7-1_amd64.deb ... Unpacking policycoreutils (2.7-1) ... Selecting previously unselected package selinux. Preparing to unpack .../selinux_1%3a0.11_all.deb ... Unpacking selinux (1:0.11) ... Selecting previously unselected package selinux-policy-dummy. Preparing to unpack .../selinux-policy-dummy_0.1_all.deb ... Unpacking selinux-policy-dummy (0.1) ... Setting up selinux-utils (2.7-2build2) ... Setting up selinux-policy-dummy (0.1) ... Setting up policycoreutils (2.7-1) ... selinux-autorelabel-mark.service is a disabled or a static unit, not starting it. Setting up selinux (1:0.11) ... Sourcing file `/etc/default/grub' Generating grub configuration file ... File descriptor 3 (pipe:[34729]) leaked on vgs invocation. Parent PID 2167: /usr/sbin/grub-probe File descriptor 3 (pipe:[34729]) leaked on vgs invocation. Parent PID 2167: /usr/sbin/grub-probe File descriptor 3 (pipe:[34729]) leaked on vgs invocation. Parent PID 2172: /usr/sbin/grub-probe File descriptor 3 (pipe:[34729]) leaked on vgs invocation. Parent PID 2172: /usr/sbin/grub-probe File descriptor 3 (pipe:[34729]) leaked on vgs invocation. Parent PID 2177: /usr/sbin/grub-probe File descriptor 3 (pipe:[34729]) leaked on vgs invocation. Parent PID 2177: /usr/sbin/grub-probe File descriptor 3 (pipe:[34729]) leaked on vgs invocation. Parent PID 2182: /usr/sbin/grub-probe File descriptor 3
[Touch-packages] [Bug 1859080] [NEW] NetworkMonitor.get_default() hangs consuming 100% of a core, blocking unattended-upgrades
Public bug reported: On an Ubuntu Server operating as a BGP router with over 800k routes, the call to NetworkMonitor.get_default() invoked by unattended-upgrades will hang indefinitely consuming a cpu core. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: python3-gi 3.20.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-72.81~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 Date: Thu Jan 9 16:03:20 2020 ProcEnviron: SHELL=/bin/bash TERM=xterm-kitty PATH=(custom, no user) LANG=en_US LANGUAGE=en_US: SourcePackage: pygobject UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: pygobject (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/1859080 Title: NetworkMonitor.get_default() hangs consuming 100% of a core, blocking unattended-upgrades Status in pygobject package in Ubuntu: New Bug description: On an Ubuntu Server operating as a BGP router with over 800k routes, the call to NetworkMonitor.get_default() invoked by unattended- upgrades will hang indefinitely consuming a cpu core. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: python3-gi 3.20.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-72.81~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 Date: Thu Jan 9 16:03:20 2020 ProcEnviron: SHELL=/bin/bash TERM=xterm-kitty PATH=(custom, no user) LANG=en_US LANGUAGE=en_US: SourcePackage: pygobject UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/1859080/+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 1311056] Re: apt-add-repository adds duplicate commented/disabled source lines
This bug was fixed in the package python-apt - 1.9.3ubuntu2 --- python-apt (1.9.3ubuntu2) focal; urgency=medium * Revert "apt.Cache: cache apt.package.Origin objects by id" -- Julian Andres Klode Tue, 17 Dec 2019 19:24:36 +0100 ** Changed in: python-apt (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1311056 Title: apt-add-repository adds duplicate commented/disabled source lines Status in python-apt package in Ubuntu: Fix Released Status in software-properties package in Ubuntu: Triaged Bug description: Trusty Tahr 14.04 0 root@osprey:/etc/apt/sources.list.d#cat aims-aims-desktop-trusty.list deb http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main 0 root@osprey:/etc/apt/sources.list.d#apt-add-repository -y ppa:aims/aims-desktop gpg: keyring `/tmp/tmp0ufdhnmv/secring.gpg' created gpg: keyring `/tmp/tmp0ufdhnmv/pubring.gpg' created gpg: requesting key BE796FF2 from hkp server keyserver.ubuntu.com gpg: /tmp/tmp0ufdhnmv/trustdb.gpg: trustdb created gpg: key BE796FF2: public key "Launchpad PPA for AIMS" imported gpg: Total number processed: 1 gpg: imported: 1 (RSA: 1) OK 0 root@osprey:/etc/apt/sources.list.d#cat aims-aims-desktop-trusty.list deb http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main 0 root@osprey:/etc/apt/sources.list.d# That deb-src line should have stayed commented out, and not been duplicated. (Commented deb lines should of course be uncommented, as already fixed per https://bugs.launchpad.net/ubuntu/+source/python- apt/+bug/1042916 .) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1311056/+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 1856560] Re: ds-identify - stuck in uninterruptible sleep state
Moved back to New, because this is happening in normal cloud-init operation. ** Changed in: util-linux (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1856560 Title: ds-identify - stuck in uninterruptible sleep state Status in cloud-init: Invalid Status in util-linux package in Ubuntu: New Bug description: We got recurring issues with the cloud-init/ds-identify process. It spawns sub-processes "blkid -c /dev/null -o export" which gets stuck in the "D" uninterruptible sleep state. The processes cannot be killed, so the only solution is to reboot the affected server. root 3839 0.0 0.0 4760 1840 ? S Dec05 0:00 /bin/sh /usr/lib/cloud-init/ds-identify root 3844 0.0 0.0 11212 2836 ? D Dec05 0:00 \_ blkid -c /dev/null -o export root 6943 0.0 0.0 4760 1880 ? S Dec05 0:00 /bin/sh /usr/lib/cloud-init/ds-identify root 6948 0.0 0.0 11212 2844 ? D Dec05 0:00 \_ blkid -c /dev/null -o export root 6111 0.0 0.0 4760 1916 ? S Dec12 0:00 /bin/sh /usr/lib/cloud-init/ds-identify root 6149 0.0 0.0 11212 2940 ? D Dec12 0:00 \_ blkid -c /dev/null -o export root 8765 0.0 0.3 926528 24968 ? Ssl Dec12 0:12 /usr/lib/snapd/snapd root 9179 0.0 0.0 4760 1892 ? S Dec12 0:00 /bin/sh /usr/lib/cloud-init/ds-identify root 9185 0.0 0.0 11980 3552 ? D Dec12 0:00 \_ blkid -c /dev/null -o export Distributor ID: Ubuntu Description: Ubuntu 18.04.3 LTS Release: 18.04 Codename: bionic 5.0.0-36-generic #39~18.04.1-Ubuntu SMP Tue Nov 12 11:09:50 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1856560/+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 1858802] Re: libblkid: no bcache UUID due to ambivalent detection of bcache and xfs_external_log for regular xfs in bcache backing device
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1858802 Title: libblkid: no bcache UUID due to ambivalent detection of bcache and xfs_external_log for regular xfs in bcache backing device Status in util-linux package in Ubuntu: In Progress Status in util-linux source package in Xenial: In Progress Status in util-linux source package in Bionic: In Progress Status in util-linux source package in Disco: In Progress Status in util-linux source package in Eoan: In Progress Status in util-linux source package in Focal: In Progress Status in util-linux package in Debian: Unknown Bug description: [Impact] * Users with an XFS filesystem on top of bcache (this is seen on some ceph, cloud deployments) might fail to reference the bcache device by UUID or other udev properties. * The journal of the regular XFS filesystem in the bcache device is incorrectly detected as an XFS external log; so two superblocks are detected (bcache and xfs_external_log). * Thus blkid fails with ambivalent superblocks detected then doesn't provide the usual udev properties (UUID, etc.) * The fix improves the probe function for XFS external log so it detects it's regular XFS and bails out. [Test Case] * See test steps detailed in comment #7 and later. - Create an XFS filesystem with the journal/log in the beginning of the bcache device (< 256K). - Stop the bcache device. - Run '$ blkid -o udev -p $BCACHE_BACKING_DEVICE'. $ sudo make-bcache -B $BACKING_DEV $ sudo mkfs.xfs -d agsize=16m -l agnum=0 -f $BCACHE_DEV $ echo 1 | sudo tee /sys/block/$(basename $BCACHE_DEV)/bcache/stop $ sudo blkid -o udev -p $BACKING_DEV [Regression Potential] * The patch only changes the detection function for XFS external log to be more general about the sector where the magic of regular XFS may be found (which is shifted inside the bcache.) * It still checks at sector zero (the only one checked previously), so this behavior didn't change. * Possible regressions are actual XFS external log devices that are not anymore detected as such. (Although that would probably indicate a different bug in libblkid.) [Other Info] * upstream commit: https://git.kernel.org/pub/scm/utils/util-linux/util-linux.git/commit/?id=d756af7d640c51ce8d1414607bd3f17eeecf2424 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1858802/+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 1858802] Re: libblkid: no bcache UUID due to ambivalent detection of bcache and xfs_external_log for regular xfs in bcache backing device
Test :: bionic $ lsb_release -cs bionic $ uname -rv 4.15.0-72-generic #81-Ubuntu SMP Tue Nov 26 12:20:02 UTC 2019 $ dpkg -s bcache-tools xfsprogs | grep -i version Version: 1.0.8-2build1 Version: 4.9.0+nmu1ubuntu2 $ sudo hexdump -C $BACKING_DEV | grep -m2 -e XFSB -e 'fe ed ba be' 2000 58 46 53 42 00 00 10 00 00 00 00 00 00 03 f0 00 |XFSB| 7000 fe ed ba be 00 00 00 01 00 00 00 02 00 00 02 00 || Before: $ dpkg -s libblkid1 | grep -i version Version: 2.31.1-0.4ubuntu3.4 $ sudo blkid -o udev -p $BACKING_DEV ID_FS_AMBIVALENT=other:bcache other:xfs_external_log After: $ dpkg -s libblkid1 | grep -i version Version: 2.31.1-0.4ubuntu3.5 $ sudo blkid -o udev -p $BACKING_DEV ID_FS_UUID=46a3afa8-2c87-41b0-9c35-b766e06c ID_FS_UUID_ENC=46a3afa8-2c87-41b0-9c35-b766e06c ID_FS_TYPE=bcache ID_FS_USAGE=other -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1858802 Title: libblkid: no bcache UUID due to ambivalent detection of bcache and xfs_external_log for regular xfs in bcache backing device Status in util-linux package in Ubuntu: In Progress Status in util-linux source package in Xenial: In Progress Status in util-linux source package in Bionic: In Progress Status in util-linux source package in Disco: In Progress Status in util-linux source package in Eoan: In Progress Status in util-linux source package in Focal: In Progress Status in util-linux package in Debian: Unknown Bug description: [Impact] * Users with an XFS filesystem on top of bcache (this is seen on some ceph, cloud deployments) might fail to reference the bcache device by UUID or other udev properties. * The journal of the regular XFS filesystem in the bcache device is incorrectly detected as an XFS external log; so two superblocks are detected (bcache and xfs_external_log). * Thus blkid fails with ambivalent superblocks detected then doesn't provide the usual udev properties (UUID, etc.) * The fix improves the probe function for XFS external log so it detects it's regular XFS and bails out. [Test Case] * See test steps detailed in comment #7 and later. - Create an XFS filesystem with the journal/log in the beginning of the bcache device (< 256K). - Stop the bcache device. - Run '$ blkid -o udev -p $BCACHE_BACKING_DEVICE'. $ sudo make-bcache -B $BACKING_DEV $ sudo mkfs.xfs -d agsize=16m -l agnum=0 -f $BCACHE_DEV $ echo 1 | sudo tee /sys/block/$(basename $BCACHE_DEV)/bcache/stop $ sudo blkid -o udev -p $BACKING_DEV [Regression Potential] * The patch only changes the detection function for XFS external log to be more general about the sector where the magic of regular XFS may be found (which is shifted inside the bcache.) * It still checks at sector zero (the only one checked previously), so this behavior didn't change. * Possible regressions are actual XFS external log devices that are not anymore detected as such. (Although that would probably indicate a different bug in libblkid.) [Other Info] * upstream commit: https://git.kernel.org/pub/scm/utils/util-linux/util-linux.git/commit/?id=d756af7d640c51ce8d1414607bd3f17eeecf2424 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1858802/+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 1858802] Re: libblkid: no bcache UUID due to ambivalent detection of bcache and xfs_external_log for regular xfs in bcache backing device
Test :: xenial $ lsb_release -cs xenial $ uname -rv 4.4.0-171-generic #200-Ubuntu SMP Tue Dec 3 11:04:55 UTC 2019 $ dpkg -s bcache-tools xfsprogs | grep -i version Version: 1.0.8-2 Version: 4.3.0+nmu1ubuntu1.1 $ sudo hexdump -C $BACKING_DEV | grep -m2 -e XFSB -e 'fe ed ba be' 2000 58 46 53 42 00 00 10 00 00 00 00 00 00 03 f0 00 |XFSB| 7000 fe ed ba be 00 00 00 01 00 00 00 02 00 00 00 14 || Before: $ dpkg -s libblkid1 | grep -i version Version: 2.27.1-6ubuntu3.9 $ sudo blkid -o udev -p $BACKING_DEV ID_FS_AMBIVALENT=other:bcache other:xfs_external_log After: $ dpkg -s libblkid1 | grep -i version Version: 2.27.1-6ubuntu3.10 $ sudo blkid -o udev -p $BACKING_DEV ID_FS_UUID=9dd54115-df08-4e6d-99eb-fb322fcfc04e ID_FS_UUID_ENC=9dd54115-df08-4e6d-99eb-fb322fcfc04e ID_FS_TYPE=bcache ID_FS_USAGE=other ** Description changed: [Impact] - * Users with an XFS filesystem on top of bcache -(this is seen on some ceph, cloud deployments) -might fail to reference the bcache device by -UUID or other udev properties. + * Users with an XFS filesystem on top of bcache + (this is seen on some ceph, cloud deployments) + might fail to reference the bcache device by + UUID or other udev properties. - * The journal of the regular XFS filesystem in -the bcache device is incorrectly detected as -an XFS external log; so two superblocks are -detected (bcache and xfs_external_log). + * The journal of the regular XFS filesystem in + the bcache device is incorrectly detected as + an XFS external log; so two superblocks are + detected (bcache and xfs_external_log). - * Thus blkid fails with ambivalent superblocks -detected then doesn't provide the usual udev -properties (UUID, etc.) + * Thus blkid fails with ambivalent superblocks + detected then doesn't provide the usual udev + properties (UUID, etc.) - * The fix improves the probe function for XFS -external log so it detects it's regular XFS -and bails out. + * The fix improves the probe function for XFS + external log so it detects it's regular XFS + and bails out. [Test Case] - * See test steps detailed in comment #. -- Create an XFS filesystem with the journal/log - in the beginning of the bcache device (< 256K). -- Stop the bcache device. -- Run '$ blkid -o udev -p $BCACHE_BACKING_DEVICE'. + * See test steps detailed in comment #7 and later. + - Create an XFS filesystem with the journal/log + in the beginning of the bcache device (< 256K). + - Stop the bcache device. + - Run '$ blkid -o udev -p $BCACHE_BACKING_DEVICE'. -$ sudo make-bcache -B $BACKING_DEV -$ sudo mkfs.xfs -d agsize=16m -l agnum=0 -f $BCACHE_DEV -$ echo 1 | sudo tee /sys/block/$(basename $BCACHE_DEV)/bcache/stop -$ sudo blkid -o udev -p $BACKING_DEV + $ sudo make-bcache -B $BACKING_DEV + $ sudo mkfs.xfs -d agsize=16m -l agnum=0 -f $BCACHE_DEV + $ echo 1 | sudo tee /sys/block/$(basename $BCACHE_DEV)/bcache/stop + $ sudo blkid -o udev -p $BACKING_DEV [Regression Potential] - * The patch only changes the detection function -for XFS external log to be more general about -the sector where the magic of regular XFS may -be found (which is shifted inside the bcache.) + * The patch only changes the detection function + for XFS external log to be more general about + the sector where the magic of regular XFS may + be found (which is shifted inside the bcache.) - * It still checks at sector zero (the only one -checked previously), so this behavior didn't -change. + * It still checks at sector zero (the only one + checked previously), so this behavior didn't + change. - * Possible regressions are actual XFS external -log devices that are not anymore detected as -such. (Although that would probably indicate -a different bug in libblkid.) + * Possible regressions are actual XFS external + log devices that are not anymore detected as + such. (Although that would probably indicate + a different bug in libblkid.) [Other Info] - * upstream commit: - https://git.kernel.org/pub/scm/utils/util-linux/util-linux.git/commit/?id=d756af7d640c51ce8d1414607bd3f17eeecf2424 + * upstream commit: + https://git.kernel.org/pub/scm/utils/util-linux/util-linux.git/commit/?id=d756af7d640c51ce8d1414607bd3f17eeecf2424 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1858802 Title: libblkid: no bcache UUID due to ambivalent detection of bcache and xfs_external_log for regular xfs in bcache backing device Status in util-linux package in Ubuntu: In Progress Status in util-linux source package in Xenial: In Progress Status in util-linux source package in Bionic: In Progress Status in util-linux source package in Disco:
[Touch-packages] [Bug 1858802] Re: libblkid: no bcache UUID due to ambivalent detection of bcache and xfs_external_log for regular xfs in bcache backing device
Test :: disco $ lsb_release -cs disco $ uname -rv 5.0.0-37-generic #40-Ubuntu SMP Thu Nov 14 00:14:01 UTC 2019 $ dpkg -s bcache-tools xfsprogs | grep -i version Version: 1.0.8-3 Version: 4.15.1-1ubuntu1 $ sudo hexdump -C $BACKING_DEV | grep -m2 -e XFSB -e 'fe ed ba be' 2000 58 46 53 42 00 00 10 00 00 00 00 00 00 03 f0 00 |XFSB| 7000 fe ed ba be 00 00 00 01 00 00 00 02 00 00 02 00 || Before: $ dpkg -s libblkid1 | grep -i version Version: 2.33.1-0.1ubuntu3 $ sudo blkid -o udev -p $BACKING_DEV ID_FS_AMBIVALENT=other:bcache other:xfs_external_log After: $ dpkg -s libblkid1 | grep -i version Version: 2.33.1-0.1ubuntu4 $ sudo blkid -o udev -p $BACKING_DEV ID_FS_UUID=c3c22fe2-cb68-4966-8cde-aba13a079201 ID_FS_UUID_ENC=c3c22fe2-cb68-4966-8cde-aba13a079201 ID_FS_TYPE=bcache ID_FS_USAGE=other -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1858802 Title: libblkid: no bcache UUID due to ambivalent detection of bcache and xfs_external_log for regular xfs in bcache backing device Status in util-linux package in Ubuntu: In Progress Status in util-linux source package in Xenial: In Progress Status in util-linux source package in Bionic: In Progress Status in util-linux source package in Disco: In Progress Status in util-linux source package in Eoan: In Progress Status in util-linux source package in Focal: In Progress Status in util-linux package in Debian: Unknown Bug description: [Impact] * Users with an XFS filesystem on top of bcache (this is seen on some ceph, cloud deployments) might fail to reference the bcache device by UUID or other udev properties. * The journal of the regular XFS filesystem in the bcache device is incorrectly detected as an XFS external log; so two superblocks are detected (bcache and xfs_external_log). * Thus blkid fails with ambivalent superblocks detected then doesn't provide the usual udev properties (UUID, etc.) * The fix improves the probe function for XFS external log so it detects it's regular XFS and bails out. [Test Case] * See test steps detailed in comment #7 and later. - Create an XFS filesystem with the journal/log in the beginning of the bcache device (< 256K). - Stop the bcache device. - Run '$ blkid -o udev -p $BCACHE_BACKING_DEVICE'. $ sudo make-bcache -B $BACKING_DEV $ sudo mkfs.xfs -d agsize=16m -l agnum=0 -f $BCACHE_DEV $ echo 1 | sudo tee /sys/block/$(basename $BCACHE_DEV)/bcache/stop $ sudo blkid -o udev -p $BACKING_DEV [Regression Potential] * The patch only changes the detection function for XFS external log to be more general about the sector where the magic of regular XFS may be found (which is shifted inside the bcache.) * It still checks at sector zero (the only one checked previously), so this behavior didn't change. * Possible regressions are actual XFS external log devices that are not anymore detected as such. (Although that would probably indicate a different bug in libblkid.) [Other Info] * upstream commit: https://git.kernel.org/pub/scm/utils/util-linux/util-linux.git/commit/?id=d756af7d640c51ce8d1414607bd3f17eeecf2424 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1858802/+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 1858802] Re: libblkid: no bcache UUID due to ambivalent detection of bcache and xfs_external_log for regular xfs in bcache backing device
Test :: focal $ lsb_release -cs focal $ uname -rv 5.4.0-9-generic #12-Ubuntu SMP Mon Dec 16 22:34:19 UTC 2019 $ dpkg -s bcache-tools xfsprogs | grep -i version Version: 1.0.8-3 Version: 5.2.1-1ubuntu1 $ sudo hexdump -C $BACKING_DEV | grep -m2 -e XFSB -e 'fe ed ba be' 2000 58 46 53 42 00 00 10 00 00 00 00 00 00 03 f0 00 |XFSB| 8000 fe ed ba be 00 00 00 01 00 00 00 02 00 00 02 00 || Before: $ dpkg -s libblkid1 | grep -i version Version: 2.34-0.1ubuntu4 $ sudo blkid -o udev -p $BACKING_DEV ID_FS_AMBIVALENT=other:bcache other:xfs_external_log After: $ dpkg -s libblkid1 | grep -i version Version: 2.34-0.1ubuntu5 $ sudo blkid -o udev -p $BACKING_DEV ID_FS_UUID=dc12092f-0bf6-48f7-913c-6249c8506dab ID_FS_UUID_ENC=dc12092f-0bf6-48f7-913c-6249c8506dab ID_FS_TYPE=bcache ID_FS_USAGE=other -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1858802 Title: libblkid: no bcache UUID due to ambivalent detection of bcache and xfs_external_log for regular xfs in bcache backing device Status in util-linux package in Ubuntu: In Progress Status in util-linux source package in Xenial: In Progress Status in util-linux source package in Bionic: In Progress Status in util-linux source package in Disco: In Progress Status in util-linux source package in Eoan: In Progress Status in util-linux source package in Focal: In Progress Status in util-linux package in Debian: Unknown Bug description: [Impact] * Users with an XFS filesystem on top of bcache (this is seen on some ceph, cloud deployments) might fail to reference the bcache device by UUID or other udev properties. * The journal of the regular XFS filesystem in the bcache device is incorrectly detected as an XFS external log; so two superblocks are detected (bcache and xfs_external_log). * Thus blkid fails with ambivalent superblocks detected then doesn't provide the usual udev properties (UUID, etc.) * The fix improves the probe function for XFS external log so it detects it's regular XFS and bails out. [Test Case] * See test steps detailed in comment #7 and later. - Create an XFS filesystem with the journal/log in the beginning of the bcache device (< 256K). - Stop the bcache device. - Run '$ blkid -o udev -p $BCACHE_BACKING_DEVICE'. $ sudo make-bcache -B $BACKING_DEV $ sudo mkfs.xfs -d agsize=16m -l agnum=0 -f $BCACHE_DEV $ echo 1 | sudo tee /sys/block/$(basename $BCACHE_DEV)/bcache/stop $ sudo blkid -o udev -p $BACKING_DEV [Regression Potential] * The patch only changes the detection function for XFS external log to be more general about the sector where the magic of regular XFS may be found (which is shifted inside the bcache.) * It still checks at sector zero (the only one checked previously), so this behavior didn't change. * Possible regressions are actual XFS external log devices that are not anymore detected as such. (Although that would probably indicate a different bug in libblkid.) [Other Info] * upstream commit: https://git.kernel.org/pub/scm/utils/util-linux/util-linux.git/commit/?id=d756af7d640c51ce8d1414607bd3f17eeecf2424 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1858802/+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 1858802] Re: libblkid: no bcache UUID due to ambivalent detection of bcache and xfs_external_log for regular xfs in bcache backing device
** Patch added: "lp1858802_xenial.debdiff" https://bugs.launchpad.net/debian/+source/util-linux/+bug/1858802/+attachment/5318919/+files/lp1858802_xenial.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1858802 Title: libblkid: no bcache UUID due to ambivalent detection of bcache and xfs_external_log for regular xfs in bcache backing device Status in util-linux package in Ubuntu: In Progress Status in util-linux source package in Xenial: In Progress Status in util-linux source package in Bionic: In Progress Status in util-linux source package in Disco: In Progress Status in util-linux source package in Eoan: In Progress Status in util-linux source package in Focal: In Progress Status in util-linux package in Debian: Unknown Bug description: [Impact] * Users with an XFS filesystem on top of bcache (this is seen on some ceph, cloud deployments) might fail to reference the bcache device by UUID or other udev properties. * The journal of the regular XFS filesystem in the bcache device is incorrectly detected as an XFS external log; so two superblocks are detected (bcache and xfs_external_log). * Thus blkid fails with ambivalent superblocks detected then doesn't provide the usual udev properties (UUID, etc.) * The fix improves the probe function for XFS external log so it detects it's regular XFS and bails out. [Test Case] * See test steps detailed in comment #7 and later. - Create an XFS filesystem with the journal/log in the beginning of the bcache device (< 256K). - Stop the bcache device. - Run '$ blkid -o udev -p $BCACHE_BACKING_DEVICE'. $ sudo make-bcache -B $BACKING_DEV $ sudo mkfs.xfs -d agsize=16m -l agnum=0 -f $BCACHE_DEV $ echo 1 | sudo tee /sys/block/$(basename $BCACHE_DEV)/bcache/stop $ sudo blkid -o udev -p $BACKING_DEV [Regression Potential] * The patch only changes the detection function for XFS external log to be more general about the sector where the magic of regular XFS may be found (which is shifted inside the bcache.) * It still checks at sector zero (the only one checked previously), so this behavior didn't change. * Possible regressions are actual XFS external log devices that are not anymore detected as such. (Although that would probably indicate a different bug in libblkid.) [Other Info] * upstream commit: https://git.kernel.org/pub/scm/utils/util-linux/util-linux.git/commit/?id=d756af7d640c51ce8d1414607bd3f17eeecf2424 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1858802/+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 1858802] Re: libblkid: no bcache UUID due to ambivalent detection of bcache and xfs_external_log for regular xfs in bcache backing device
Test :: eoan $ lsb_release -cs eoan $ uname -rv 5.3.0-26-generic #28-Ubuntu SMP Wed Dec 18 05:37:46 UTC 2019 $ dpkg -s bcache-tools xfsprogs | grep -i version Version: 1.0.8-3 Version: 5.0.0-1ubuntu1 $ sudo hexdump -C $BACKING_DEV | grep -m2 -e XFSB -e 'fe ed ba be' 2000 58 46 53 42 00 00 10 00 00 00 00 00 00 03 f0 00 |XFSB| 7000 fe ed ba be 00 00 00 01 00 00 00 02 00 00 02 00 || Before: $ dpkg -s libblkid1 | grep -i version Version: 2.34-0.1ubuntu2.1 $ sudo blkid -o udev -p $BACKING_DEV ID_FS_AMBIVALENT=other:bcache other:xfs_external_log After: $ dpkg -s libblkid1 | grep -i version Version: 2.34-0.1ubuntu2.2 $ sudo blkid -o udev -p $BACKING_DEV ID_FS_UUID=b42bee00-cc30-4966-8f09-6cddf2ebddf8 ID_FS_UUID_ENC=b42bee00-cc30-4966-8f09-6cddf2ebddf8 ID_FS_TYPE=bcache ID_FS_USAGE=other -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1858802 Title: libblkid: no bcache UUID due to ambivalent detection of bcache and xfs_external_log for regular xfs in bcache backing device Status in util-linux package in Ubuntu: In Progress Status in util-linux source package in Xenial: In Progress Status in util-linux source package in Bionic: In Progress Status in util-linux source package in Disco: In Progress Status in util-linux source package in Eoan: In Progress Status in util-linux source package in Focal: In Progress Status in util-linux package in Debian: Unknown Bug description: [Impact] * Users with an XFS filesystem on top of bcache (this is seen on some ceph, cloud deployments) might fail to reference the bcache device by UUID or other udev properties. * The journal of the regular XFS filesystem in the bcache device is incorrectly detected as an XFS external log; so two superblocks are detected (bcache and xfs_external_log). * Thus blkid fails with ambivalent superblocks detected then doesn't provide the usual udev properties (UUID, etc.) * The fix improves the probe function for XFS external log so it detects it's regular XFS and bails out. [Test Case] * See test steps detailed in comment #7 and later. - Create an XFS filesystem with the journal/log in the beginning of the bcache device (< 256K). - Stop the bcache device. - Run '$ blkid -o udev -p $BCACHE_BACKING_DEVICE'. $ sudo make-bcache -B $BACKING_DEV $ sudo mkfs.xfs -d agsize=16m -l agnum=0 -f $BCACHE_DEV $ echo 1 | sudo tee /sys/block/$(basename $BCACHE_DEV)/bcache/stop $ sudo blkid -o udev -p $BACKING_DEV [Regression Potential] * The patch only changes the detection function for XFS external log to be more general about the sector where the magic of regular XFS may be found (which is shifted inside the bcache.) * It still checks at sector zero (the only one checked previously), so this behavior didn't change. * Possible regressions are actual XFS external log devices that are not anymore detected as such. (Although that would probably indicate a different bug in libblkid.) [Other Info] * upstream commit: https://git.kernel.org/pub/scm/utils/util-linux/util-linux.git/commit/?id=d756af7d640c51ce8d1414607bd3f17eeecf2424 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1858802/+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 1858802] Re: libblkid: no bcache UUID due to ambivalent detection of bcache and xfs_external_log for regular xfs in bcache backing device
** Patch added: "lp1858802_disco.debdiff" https://bugs.launchpad.net/debian/+source/util-linux/+bug/1858802/+attachment/5318917/+files/lp1858802_disco.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1858802 Title: libblkid: no bcache UUID due to ambivalent detection of bcache and xfs_external_log for regular xfs in bcache backing device Status in util-linux package in Ubuntu: In Progress Status in util-linux source package in Xenial: In Progress Status in util-linux source package in Bionic: In Progress Status in util-linux source package in Disco: In Progress Status in util-linux source package in Eoan: In Progress Status in util-linux source package in Focal: In Progress Status in util-linux package in Debian: Unknown Bug description: [Impact] * Users with an XFS filesystem on top of bcache (this is seen on some ceph, cloud deployments) might fail to reference the bcache device by UUID or other udev properties. * The journal of the regular XFS filesystem in the bcache device is incorrectly detected as an XFS external log; so two superblocks are detected (bcache and xfs_external_log). * Thus blkid fails with ambivalent superblocks detected then doesn't provide the usual udev properties (UUID, etc.) * The fix improves the probe function for XFS external log so it detects it's regular XFS and bails out. [Test Case] * See test steps detailed in comment #7 and later. - Create an XFS filesystem with the journal/log in the beginning of the bcache device (< 256K). - Stop the bcache device. - Run '$ blkid -o udev -p $BCACHE_BACKING_DEVICE'. $ sudo make-bcache -B $BACKING_DEV $ sudo mkfs.xfs -d agsize=16m -l agnum=0 -f $BCACHE_DEV $ echo 1 | sudo tee /sys/block/$(basename $BCACHE_DEV)/bcache/stop $ sudo blkid -o udev -p $BACKING_DEV [Regression Potential] * The patch only changes the detection function for XFS external log to be more general about the sector where the magic of regular XFS may be found (which is shifted inside the bcache.) * It still checks at sector zero (the only one checked previously), so this behavior didn't change. * Possible regressions are actual XFS external log devices that are not anymore detected as such. (Although that would probably indicate a different bug in libblkid.) [Other Info] * upstream commit: https://git.kernel.org/pub/scm/utils/util-linux/util-linux.git/commit/?id=d756af7d640c51ce8d1414607bd3f17eeecf2424 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1858802/+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 1858802] Re: libblkid: no bcache UUID due to ambivalent detection of bcache and xfs_external_log for regular xfs in bcache backing device
** Patch added: "lp1858802_focal.debdiff" https://bugs.launchpad.net/debian/+source/util-linux/+bug/1858802/+attachment/5318915/+files/lp1858802_focal.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1858802 Title: libblkid: no bcache UUID due to ambivalent detection of bcache and xfs_external_log for regular xfs in bcache backing device Status in util-linux package in Ubuntu: In Progress Status in util-linux source package in Xenial: In Progress Status in util-linux source package in Bionic: In Progress Status in util-linux source package in Disco: In Progress Status in util-linux source package in Eoan: In Progress Status in util-linux source package in Focal: In Progress Status in util-linux package in Debian: Unknown Bug description: [Impact] * Users with an XFS filesystem on top of bcache (this is seen on some ceph, cloud deployments) might fail to reference the bcache device by UUID or other udev properties. * The journal of the regular XFS filesystem in the bcache device is incorrectly detected as an XFS external log; so two superblocks are detected (bcache and xfs_external_log). * Thus blkid fails with ambivalent superblocks detected then doesn't provide the usual udev properties (UUID, etc.) * The fix improves the probe function for XFS external log so it detects it's regular XFS and bails out. [Test Case] * See test steps detailed in comment #7 and later. - Create an XFS filesystem with the journal/log in the beginning of the bcache device (< 256K). - Stop the bcache device. - Run '$ blkid -o udev -p $BCACHE_BACKING_DEVICE'. $ sudo make-bcache -B $BACKING_DEV $ sudo mkfs.xfs -d agsize=16m -l agnum=0 -f $BCACHE_DEV $ echo 1 | sudo tee /sys/block/$(basename $BCACHE_DEV)/bcache/stop $ sudo blkid -o udev -p $BACKING_DEV [Regression Potential] * The patch only changes the detection function for XFS external log to be more general about the sector where the magic of regular XFS may be found (which is shifted inside the bcache.) * It still checks at sector zero (the only one checked previously), so this behavior didn't change. * Possible regressions are actual XFS external log devices that are not anymore detected as such. (Although that would probably indicate a different bug in libblkid.) [Other Info] * upstream commit: https://git.kernel.org/pub/scm/utils/util-linux/util-linux.git/commit/?id=d756af7d640c51ce8d1414607bd3f17eeecf2424 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1858802/+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 1858802] Re: libblkid: no bcache UUID due to ambivalent detection of bcache and xfs_external_log for regular xfs in bcache backing device
** Patch added: "lp1858802_eoan.debdiff" https://bugs.launchpad.net/debian/+source/util-linux/+bug/1858802/+attachment/5318916/+files/lp1858802_eoan.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1858802 Title: libblkid: no bcache UUID due to ambivalent detection of bcache and xfs_external_log for regular xfs in bcache backing device Status in util-linux package in Ubuntu: In Progress Status in util-linux source package in Xenial: In Progress Status in util-linux source package in Bionic: In Progress Status in util-linux source package in Disco: In Progress Status in util-linux source package in Eoan: In Progress Status in util-linux source package in Focal: In Progress Status in util-linux package in Debian: Unknown Bug description: [Impact] * Users with an XFS filesystem on top of bcache (this is seen on some ceph, cloud deployments) might fail to reference the bcache device by UUID or other udev properties. * The journal of the regular XFS filesystem in the bcache device is incorrectly detected as an XFS external log; so two superblocks are detected (bcache and xfs_external_log). * Thus blkid fails with ambivalent superblocks detected then doesn't provide the usual udev properties (UUID, etc.) * The fix improves the probe function for XFS external log so it detects it's regular XFS and bails out. [Test Case] * See test steps detailed in comment #7 and later. - Create an XFS filesystem with the journal/log in the beginning of the bcache device (< 256K). - Stop the bcache device. - Run '$ blkid -o udev -p $BCACHE_BACKING_DEVICE'. $ sudo make-bcache -B $BACKING_DEV $ sudo mkfs.xfs -d agsize=16m -l agnum=0 -f $BCACHE_DEV $ echo 1 | sudo tee /sys/block/$(basename $BCACHE_DEV)/bcache/stop $ sudo blkid -o udev -p $BACKING_DEV [Regression Potential] * The patch only changes the detection function for XFS external log to be more general about the sector where the magic of regular XFS may be found (which is shifted inside the bcache.) * It still checks at sector zero (the only one checked previously), so this behavior didn't change. * Possible regressions are actual XFS external log devices that are not anymore detected as such. (Although that would probably indicate a different bug in libblkid.) [Other Info] * upstream commit: https://git.kernel.org/pub/scm/utils/util-linux/util-linux.git/commit/?id=d756af7d640c51ce8d1414607bd3f17eeecf2424 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1858802/+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 1858802] Re: libblkid: no bcache UUID due to ambivalent detection of bcache and xfs_external_log for regular xfs in bcache backing device
** Patch added: "lp1858802_bionic.debdiff" https://bugs.launchpad.net/debian/+source/util-linux/+bug/1858802/+attachment/5318918/+files/lp1858802_bionic.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1858802 Title: libblkid: no bcache UUID due to ambivalent detection of bcache and xfs_external_log for regular xfs in bcache backing device Status in util-linux package in Ubuntu: In Progress Status in util-linux source package in Xenial: In Progress Status in util-linux source package in Bionic: In Progress Status in util-linux source package in Disco: In Progress Status in util-linux source package in Eoan: In Progress Status in util-linux source package in Focal: In Progress Status in util-linux package in Debian: Unknown Bug description: [Impact] * Users with an XFS filesystem on top of bcache (this is seen on some ceph, cloud deployments) might fail to reference the bcache device by UUID or other udev properties. * The journal of the regular XFS filesystem in the bcache device is incorrectly detected as an XFS external log; so two superblocks are detected (bcache and xfs_external_log). * Thus blkid fails with ambivalent superblocks detected then doesn't provide the usual udev properties (UUID, etc.) * The fix improves the probe function for XFS external log so it detects it's regular XFS and bails out. [Test Case] * See test steps detailed in comment #7 and later. - Create an XFS filesystem with the journal/log in the beginning of the bcache device (< 256K). - Stop the bcache device. - Run '$ blkid -o udev -p $BCACHE_BACKING_DEVICE'. $ sudo make-bcache -B $BACKING_DEV $ sudo mkfs.xfs -d agsize=16m -l agnum=0 -f $BCACHE_DEV $ echo 1 | sudo tee /sys/block/$(basename $BCACHE_DEV)/bcache/stop $ sudo blkid -o udev -p $BACKING_DEV [Regression Potential] * The patch only changes the detection function for XFS external log to be more general about the sector where the magic of regular XFS may be found (which is shifted inside the bcache.) * It still checks at sector zero (the only one checked previously), so this behavior didn't change. * Possible regressions are actual XFS external log devices that are not anymore detected as such. (Although that would probably indicate a different bug in libblkid.) [Other Info] * upstream commit: https://git.kernel.org/pub/scm/utils/util-linux/util-linux.git/commit/?id=d756af7d640c51ce8d1414607bd3f17eeecf2424 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1858802/+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 1858802] Re: libblkid: no bcache UUID due to ambivalent detection of bcache and xfs_external_log for regular xfs in bcache backing device
Test Steps: --- # Document versions lsb_release -cs uname -rv dpkg -s bcache-tools xfsprogs | grep -i version # Create disk image DISK_IMG=disk.img rm -f $DISK_IMG dd if=/dev/zero of=$DISK_IMG bs=1G count=0 seek=1 # Create bcache backing device from disk image BACKING_DEV=$(sudo losetup --find --show $DISK_IMG) sudo make-bcache -B $BACKING_DEV echo $BACKING_DEV | sudo tee /sys/fs/bcache/register # for Disco only. sleep 1 # Create xfs on its bcache device BCACHE_DEV="$(readlink -e /sys/block/$(basename $BACKING_DEV)/bcache/dev)" BCACHE_DEV="/dev/$(basename $BCACHE_DEV)" sudo mkfs.xfs -d agsize=16m -l agnum=0 -f $BCACHE_DEV sleep 1 # Stop bcache device to flush (needed) echo 1 | sudo tee /sys/block/$(basename $BCACHE_DEV)/bcache/stop sleep 1 # Check signatures for XFS and XFS journal (both before 0x4 / 256K) sudo hexdump -C $BACKING_DEV | grep -m2 -e XFSB -e 'fe ed ba be' # Test old version dpkg -s libblkid1 | grep -i version sudo blkid -o udev -p $BACKING_DEV # Install new version sudo add-apt-repository ppa:mfo/lp1858802-sru sudo apt update sudo apt install -y libblkid1 # Test new version dpkg -s libblkid1 | grep -i version sudo blkid -o udev -p $BACKING_DEV # Stop loop/backing device sudo losetup -d $BACKING_DEV -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1858802 Title: libblkid: no bcache UUID due to ambivalent detection of bcache and xfs_external_log for regular xfs in bcache backing device Status in util-linux package in Ubuntu: In Progress Status in util-linux source package in Xenial: In Progress Status in util-linux source package in Bionic: In Progress Status in util-linux source package in Disco: In Progress Status in util-linux source package in Eoan: In Progress Status in util-linux source package in Focal: In Progress Status in util-linux package in Debian: Unknown Bug description: [Impact] * Users with an XFS filesystem on top of bcache (this is seen on some ceph, cloud deployments) might fail to reference the bcache device by UUID or other udev properties. * The journal of the regular XFS filesystem in the bcache device is incorrectly detected as an XFS external log; so two superblocks are detected (bcache and xfs_external_log). * Thus blkid fails with ambivalent superblocks detected then doesn't provide the usual udev properties (UUID, etc.) * The fix improves the probe function for XFS external log so it detects it's regular XFS and bails out. [Test Case] * See test steps detailed in comment #7 and later. - Create an XFS filesystem with the journal/log in the beginning of the bcache device (< 256K). - Stop the bcache device. - Run '$ blkid -o udev -p $BCACHE_BACKING_DEVICE'. $ sudo make-bcache -B $BACKING_DEV $ sudo mkfs.xfs -d agsize=16m -l agnum=0 -f $BCACHE_DEV $ echo 1 | sudo tee /sys/block/$(basename $BCACHE_DEV)/bcache/stop $ sudo blkid -o udev -p $BACKING_DEV [Regression Potential] * The patch only changes the detection function for XFS external log to be more general about the sector where the magic of regular XFS may be found (which is shifted inside the bcache.) * It still checks at sector zero (the only one checked previously), so this behavior didn't change. * Possible regressions are actual XFS external log devices that are not anymore detected as such. (Although that would probably indicate a different bug in libblkid.) [Other Info] * upstream commit: https://git.kernel.org/pub/scm/utils/util-linux/util-linux.git/commit/?id=d756af7d640c51ce8d1414607bd3f17eeecf2424 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1858802/+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 1858802] Re: libblkid: no bcache UUID due to ambivalent detection of bcache and xfs_external_log for regular xfs in bcache backing device
Attaching the debdiffs for X/B/D/E/F for reference. The package built successfully on all architectures for all releases considered (X/B/D/E/F) in PPA [1]. The test results are positive: (see next comments) - the latest version in -updates (X/B/D/F) or -proposed (E) fails with ambivalent results detected (bcache + xfs external log) and no UUID/other variables are printed. - the version with the patch/from the PPA [1] succeeds with only bcache detected, and prints the UUID/other variables. The autopkgtest results ran against the PPA are positive. All of them have a 'exitcode' of zero. (see next comments) (Note: there's an util-linux in eoan-proposed that needs work on its autopkgtest failures before this is uploaded, which will be worked first. Eoan debdiff is on top of it.) [1] https://launchpad.net/~mfo/+archive/ubuntu/lp1858802-sru/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1858802 Title: libblkid: no bcache UUID due to ambivalent detection of bcache and xfs_external_log for regular xfs in bcache backing device Status in util-linux package in Ubuntu: In Progress Status in util-linux source package in Xenial: In Progress Status in util-linux source package in Bionic: In Progress Status in util-linux source package in Disco: In Progress Status in util-linux source package in Eoan: In Progress Status in util-linux source package in Focal: In Progress Status in util-linux package in Debian: Unknown Bug description: [Impact] * Users with an XFS filesystem on top of bcache (this is seen on some ceph, cloud deployments) might fail to reference the bcache device by UUID or other udev properties. * The journal of the regular XFS filesystem in the bcache device is incorrectly detected as an XFS external log; so two superblocks are detected (bcache and xfs_external_log). * Thus blkid fails with ambivalent superblocks detected then doesn't provide the usual udev properties (UUID, etc.) * The fix improves the probe function for XFS external log so it detects it's regular XFS and bails out. [Test Case] * See test steps detailed in comment #7 and later. - Create an XFS filesystem with the journal/log in the beginning of the bcache device (< 256K). - Stop the bcache device. - Run '$ blkid -o udev -p $BCACHE_BACKING_DEVICE'. $ sudo make-bcache -B $BACKING_DEV $ sudo mkfs.xfs -d agsize=16m -l agnum=0 -f $BCACHE_DEV $ echo 1 | sudo tee /sys/block/$(basename $BCACHE_DEV)/bcache/stop $ sudo blkid -o udev -p $BACKING_DEV [Regression Potential] * The patch only changes the detection function for XFS external log to be more general about the sector where the magic of regular XFS may be found (which is shifted inside the bcache.) * It still checks at sector zero (the only one checked previously), so this behavior didn't change. * Possible regressions are actual XFS external log devices that are not anymore detected as such. (Although that would probably indicate a different bug in libblkid.) [Other Info] * upstream commit: https://git.kernel.org/pub/scm/utils/util-linux/util-linux.git/commit/?id=d756af7d640c51ce8d1414607bd3f17eeecf2424 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1858802/+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 1856560] Re: ds-identify - stuck in uninterruptible sleep state
> If someone manually installs Ubuntu Desktop / Server using an installer, > one should not be installing or using cloud-init as clearly, it will never > complete without a correct metadata source present. And when it fails to > complete, it re-attempts to reprovision the machine on every boot. I'd just like to clarify something. The above statement is neither true nor helpful. cloud-init (since 18.04) does not run unless it is on a cloud or has cloud platform metadata. It is perfectly fine to have cloud-init installed on a desktop or a server that is not running "on a cloud". In order to accomplish this, cloud-init is only enabled via a generator. That generator ran 'blkid', and 'blkid' blocked indefinitely. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1856560 Title: ds-identify - stuck in uninterruptible sleep state Status in cloud-init: Invalid Status in util-linux package in Ubuntu: Incomplete Bug description: We got recurring issues with the cloud-init/ds-identify process. It spawns sub-processes "blkid -c /dev/null -o export" which gets stuck in the "D" uninterruptible sleep state. The processes cannot be killed, so the only solution is to reboot the affected server. root 3839 0.0 0.0 4760 1840 ? S Dec05 0:00 /bin/sh /usr/lib/cloud-init/ds-identify root 3844 0.0 0.0 11212 2836 ? D Dec05 0:00 \_ blkid -c /dev/null -o export root 6943 0.0 0.0 4760 1880 ? S Dec05 0:00 /bin/sh /usr/lib/cloud-init/ds-identify root 6948 0.0 0.0 11212 2844 ? D Dec05 0:00 \_ blkid -c /dev/null -o export root 6111 0.0 0.0 4760 1916 ? S Dec12 0:00 /bin/sh /usr/lib/cloud-init/ds-identify root 6149 0.0 0.0 11212 2940 ? D Dec12 0:00 \_ blkid -c /dev/null -o export root 8765 0.0 0.3 926528 24968 ? Ssl Dec12 0:12 /usr/lib/snapd/snapd root 9179 0.0 0.0 4760 1892 ? S Dec12 0:00 /bin/sh /usr/lib/cloud-init/ds-identify root 9185 0.0 0.0 11980 3552 ? D Dec12 0:00 \_ blkid -c /dev/null -o export Distributor ID: Ubuntu Description: Ubuntu 18.04.3 LTS Release: 18.04 Codename: bionic 5.0.0-36-generic #39~18.04.1-Ubuntu SMP Tue Nov 12 11:09:50 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1856560/+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 1858802] Re: libblkid: no bcache UUID due to ambivalent detection of bcache and xfs_external_log for regular xfs in bcache backing device
** Description changed: - description/debdiffs to be provided. + [Impact] - upstream commit: - https://git.kernel.org/pub/scm/utils/util-linux/util-linux.git/commit/?id=d756af7d640c51ce8d1414607bd3f17eeecf2424 + * Users with an XFS filesystem on top of bcache +(this is seen on some ceph, cloud deployments) +might fail to reference the bcache device by +UUID or other udev properties. + + * The journal of the regular XFS filesystem in +the bcache device is incorrectly detected as +an XFS external log; so two superblocks are +detected (bcache and xfs_external_log). + + * Thus blkid fails with ambivalent superblocks +detected then doesn't provide the usual udev +properties (UUID, etc.) + + * The fix improves the probe function for XFS +external log so it detects it's regular XFS +and bails out. + + [Test Case] + + * See test steps detailed in comment #. +- Create an XFS filesystem with the journal/log + in the beginning of the bcache device (< 256K). +- Stop the bcache device. +- Run '$ blkid -o udev -p $BCACHE_BACKING_DEVICE'. + +$ sudo make-bcache -B $BACKING_DEV +$ sudo mkfs.xfs -d agsize=16m -l agnum=0 -f $BCACHE_DEV +$ echo 1 | sudo tee /sys/block/$(basename $BCACHE_DEV)/bcache/stop +$ sudo blkid -o udev -p $BACKING_DEV + + [Regression Potential] + + * The patch only changes the detection function +for XFS external log to be more general about +the sector where the magic of regular XFS may +be found (which is shifted inside the bcache.) + + * It still checks at sector zero (the only one +checked previously), so this behavior didn't +change. + + * Possible regressions are actual XFS external +log devices that are not anymore detected as +such. (Although that would probably indicate +a different bug in libblkid.) + + [Other Info] + * upstream commit: + https://git.kernel.org/pub/scm/utils/util-linux/util-linux.git/commit/?id=d756af7d640c51ce8d1414607bd3f17eeecf2424 ** Bug watch added: Debian Bug tracker #948444 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948444 ** Also affects: util-linux (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948444 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1858802 Title: libblkid: no bcache UUID due to ambivalent detection of bcache and xfs_external_log for regular xfs in bcache backing device Status in util-linux package in Ubuntu: In Progress Status in util-linux source package in Xenial: In Progress Status in util-linux source package in Bionic: In Progress Status in util-linux source package in Disco: In Progress Status in util-linux source package in Eoan: In Progress Status in util-linux source package in Focal: In Progress Status in util-linux package in Debian: Unknown Bug description: [Impact] * Users with an XFS filesystem on top of bcache (this is seen on some ceph, cloud deployments) might fail to reference the bcache device by UUID or other udev properties. * The journal of the regular XFS filesystem in the bcache device is incorrectly detected as an XFS external log; so two superblocks are detected (bcache and xfs_external_log). * Thus blkid fails with ambivalent superblocks detected then doesn't provide the usual udev properties (UUID, etc.) * The fix improves the probe function for XFS external log so it detects it's regular XFS and bails out. [Test Case] * See test steps detailed in comment #. - Create an XFS filesystem with the journal/log in the beginning of the bcache device (< 256K). - Stop the bcache device. - Run '$ blkid -o udev -p $BCACHE_BACKING_DEVICE'. $ sudo make-bcache -B $BACKING_DEV $ sudo mkfs.xfs -d agsize=16m -l agnum=0 -f $BCACHE_DEV $ echo 1 | sudo tee /sys/block/$(basename $BCACHE_DEV)/bcache/stop $ sudo blkid -o udev -p $BACKING_DEV [Regression Potential] * The patch only changes the detection function for XFS external log to be more general about the sector where the magic of regular XFS may be found (which is shifted inside the bcache.) * It still checks at sector zero (the only one checked previously), so this behavior didn't change. * Possible regressions are actual XFS external log devices that are not anymore detected as such. (Although that would probably indicate a different bug in libblkid.) [Other Info] * upstream commit: https://git.kernel.org/pub/scm/utils/util-linux/util-linux.git/commit/?id=d756af7d640c51ce8d1414607bd3f17eeecf2424 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1858802/+subscriptions -- Mailing list:
[Touch-packages] [Bug 1856045] Re: capabilities set with setcap are not honoured
** Tags removed: rls-ee-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libcap2 in Ubuntu. https://bugs.launchpad.net/bugs/1856045 Title: capabilities set with setcap are not honoured Status in libcap2 package in Ubuntu: New Status in libcap2 source package in Eoan: Confirmed Bug description: Hi, In Ubuntu 19.10 I set capabilities as; setcap cap_net_admin,cap_sys_admin+ep /bin/ip getcap /bin/ip /bin/ip = cap_net_admin,cap_sys_admin+ep but; > ip addr add 20.20.20.20/32 dev lo RTNETLINK answers: Operation not permitted *exactly* the same works perfect on 18.04.3 LTS. BTW the set of a silly address on "lo" is just an example. Nothing works on Ubuntu 19.10 Regards, ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: libcap2-bin 1:2.25-2 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Wed Dec 11 15:27:00 2019 InstallationDate: Installed on 2019-12-09 (2 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: libcap2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcap2/+bug/1856045/+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 1859030] Re: libcairo2 does not install on Bionic (18.04)
I have now enabled bionic-updates, it must have been disabled in error. Thank you for your help, apologies for the unnecessary report. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cairo in Ubuntu. https://bugs.launchpad.net/bugs/1859030 Title: libcairo2 does not install on Bionic (18.04) Status in cairo package in Ubuntu: Invalid Bug description: Attempt at installing libcairo2-dev on a clean Bionic install fails as follows: $ sudo apt install libcairo2-dev Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies. libcairo2-dev : Depends: libcairo2 (= 1.15.10-2) but 1.15.10-2ubuntu0.1 is to be installed Depends: libcairo-gobject2 (= 1.15.10-2) but 1.15.10-2ubuntu0.1 is to be installed Depends: libxcb-shm0-dev but it is not going to be installed E: Unable to correct problems, you have held broken packages. Similar issues reported previously on Launchpad are: https://answers.launchpad.net/ubuntu/+source/cairo/+question/262830 and most recently on StackOverflow (just over a week ago) here: https://stackoverflow.com/questions/9437246/unable-to-install-cairo-package-under-linux $ lsb_release -a; uname -a; apt-cache policy libcairo2-dev No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.3 LTS Release: 18.04 Codename: bionic Linux gnuradio 5.0.0-37-generic #40~18.04.1-Ubuntu SMP Thu Nov 14 12:06:39 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux libcairo2-dev: Installed: (none) Candidate: 1.15.10-2 Version table: 1.15.10-2 500 500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1859030/+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 1858802] Re: libblkid: no bcache UUID due to ambivalent detection of bcache and xfs_external_log for regular xfs in bcache backing device
** Changed in: util-linux (Ubuntu Disco) Status: Invalid => In Progress ** Changed in: util-linux (Ubuntu Disco) Importance: Undecided => Medium ** Changed in: util-linux (Ubuntu Disco) Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1858802 Title: libblkid: no bcache UUID due to ambivalent detection of bcache and xfs_external_log for regular xfs in bcache backing device Status in util-linux package in Ubuntu: In Progress Status in util-linux source package in Xenial: In Progress Status in util-linux source package in Bionic: In Progress Status in util-linux source package in Disco: In Progress Status in util-linux source package in Eoan: In Progress Status in util-linux source package in Focal: In Progress Bug description: description/debdiffs to be provided. upstream commit: https://git.kernel.org/pub/scm/utils/util-linux/util-linux.git/commit/?id=d756af7d640c51ce8d1414607bd3f17eeecf2424 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1858802/+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 1859030] Re: libcairo2 does not install on Bionic (18.04)
If there is a simple way to downgrade packages from 18.04.1 to 18.04 I would be greatly appreciative if somebody could help me with this. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cairo in Ubuntu. https://bugs.launchpad.net/bugs/1859030 Title: libcairo2 does not install on Bionic (18.04) Status in cairo package in Ubuntu: Invalid Bug description: Attempt at installing libcairo2-dev on a clean Bionic install fails as follows: $ sudo apt install libcairo2-dev Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies. libcairo2-dev : Depends: libcairo2 (= 1.15.10-2) but 1.15.10-2ubuntu0.1 is to be installed Depends: libcairo-gobject2 (= 1.15.10-2) but 1.15.10-2ubuntu0.1 is to be installed Depends: libxcb-shm0-dev but it is not going to be installed E: Unable to correct problems, you have held broken packages. Similar issues reported previously on Launchpad are: https://answers.launchpad.net/ubuntu/+source/cairo/+question/262830 and most recently on StackOverflow (just over a week ago) here: https://stackoverflow.com/questions/9437246/unable-to-install-cairo-package-under-linux $ lsb_release -a; uname -a; apt-cache policy libcairo2-dev No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.3 LTS Release: 18.04 Codename: bionic Linux gnuradio 5.0.0-37-generic #40~18.04.1-Ubuntu SMP Thu Nov 14 12:06:39 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux libcairo2-dev: Installed: (none) Candidate: 1.15.10-2 Version table: 1.15.10-2 500 500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1859030/+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 1859030] Re: libcairo2 does not install on Bionic (18.04)
Thanks for the update, closing the bug then since it was a local system configuration error and not an issue with the Ubuntu source ** Changed in: cairo (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cairo in Ubuntu. https://bugs.launchpad.net/bugs/1859030 Title: libcairo2 does not install on Bionic (18.04) Status in cairo package in Ubuntu: Invalid Bug description: Attempt at installing libcairo2-dev on a clean Bionic install fails as follows: $ sudo apt install libcairo2-dev Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies. libcairo2-dev : Depends: libcairo2 (= 1.15.10-2) but 1.15.10-2ubuntu0.1 is to be installed Depends: libcairo-gobject2 (= 1.15.10-2) but 1.15.10-2ubuntu0.1 is to be installed Depends: libxcb-shm0-dev but it is not going to be installed E: Unable to correct problems, you have held broken packages. Similar issues reported previously on Launchpad are: https://answers.launchpad.net/ubuntu/+source/cairo/+question/262830 and most recently on StackOverflow (just over a week ago) here: https://stackoverflow.com/questions/9437246/unable-to-install-cairo-package-under-linux $ lsb_release -a; uname -a; apt-cache policy libcairo2-dev No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.3 LTS Release: 18.04 Codename: bionic Linux gnuradio 5.0.0-37-generic #40~18.04.1-Ubuntu SMP Thu Nov 14 12:06:39 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux libcairo2-dev: Installed: (none) Candidate: 1.15.10-2 Version table: 1.15.10-2 500 500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1859030/+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 1859030] Re: libcairo2 does not install on Bionic (18.04)
I'm not certain whether I have bionic-updates enabled, although I have realised the issue has been caused by the versions of packages (namely 1.15.10-2ubuntu0.1) being more recent than 1.15.10-2, I guess this means that the system on which I am installing has indeed had some updates to the original Bionic package list. Apologies for the bug if this means it was filed in error, as this is my first time using Ubuntu in a while I did not expect these two versions to be different. I have manually downgraded all of the dependencies e.g.: $sudo apt install libcairo-gobject2=1.15.10-2 Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be DOWNGRADED: libcairo-gobject2 0 to upgrade, 0 to newly install, 1 to downgrade, 0 to remove and 0 not to upgrade. Need to get 17.2 kB of archives. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] y Get:1 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 libcairo-gobject2 amd64 1.15.10-2 [17.2 kB] Fetched 17.2 kB in 0s (506 kB/s) Which has allowed me to correctly install libcairo2-dev as required. One perhaps useful update to come from this would be adjusting libcairo2-dev's dependencies to include those packages from the Bionic updates. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cairo in Ubuntu. https://bugs.launchpad.net/bugs/1859030 Title: libcairo2 does not install on Bionic (18.04) Status in cairo package in Ubuntu: Incomplete Bug description: Attempt at installing libcairo2-dev on a clean Bionic install fails as follows: $ sudo apt install libcairo2-dev Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies. libcairo2-dev : Depends: libcairo2 (= 1.15.10-2) but 1.15.10-2ubuntu0.1 is to be installed Depends: libcairo-gobject2 (= 1.15.10-2) but 1.15.10-2ubuntu0.1 is to be installed Depends: libxcb-shm0-dev but it is not going to be installed E: Unable to correct problems, you have held broken packages. Similar issues reported previously on Launchpad are: https://answers.launchpad.net/ubuntu/+source/cairo/+question/262830 and most recently on StackOverflow (just over a week ago) here: https://stackoverflow.com/questions/9437246/unable-to-install-cairo-package-under-linux $ lsb_release -a; uname -a; apt-cache policy libcairo2-dev No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.3 LTS Release: 18.04 Codename: bionic Linux gnuradio 5.0.0-37-generic #40~18.04.1-Ubuntu SMP Thu Nov 14 12:06:39 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux libcairo2-dev: Installed: (none) Candidate: 1.15.10-2 Version table: 1.15.10-2 500 500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1859030/+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 1856560] Re: ds-identify - stuck in uninterruptible sleep state
cloud-init is used to perform first time configuration of cloud-images using a cloud metadata source. I.e. a generic image is launched by openstack and provisions per-user keys / packages / etc. If someone manually installs Ubuntu Desktop / Server using an installer, one should not be installing or using cloud-init as clearly, it will never complete without a correct metadata source present. And when it fails to complete, it re-attempts to reprovision the machine on every boot. If you don't know whether or not there is a cloud metadata source, and whether or not cloud-init should be provisioning the instances on first boot, or whether a desktop/server installers were used - you need to sort that out first. Please escalate to your IT/devops team to understand whether or not it is intentional that cloud-init is installed and attempted on every boot, and where the metadata for it is suppoed to come from. Then fix cloud-init/metadata such that it completes, or remove/disable/uninstall cloud-init. This is not a bug, but effectively a support issue at this point. The logs are inconsistent with normal cloud-init usage, and there is no reproducer. ** Changed in: util-linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1856560 Title: ds-identify - stuck in uninterruptible sleep state Status in cloud-init: Invalid Status in util-linux package in Ubuntu: Incomplete Bug description: We got recurring issues with the cloud-init/ds-identify process. It spawns sub-processes "blkid -c /dev/null -o export" which gets stuck in the "D" uninterruptible sleep state. The processes cannot be killed, so the only solution is to reboot the affected server. root 3839 0.0 0.0 4760 1840 ? S Dec05 0:00 /bin/sh /usr/lib/cloud-init/ds-identify root 3844 0.0 0.0 11212 2836 ? D Dec05 0:00 \_ blkid -c /dev/null -o export root 6943 0.0 0.0 4760 1880 ? S Dec05 0:00 /bin/sh /usr/lib/cloud-init/ds-identify root 6948 0.0 0.0 11212 2844 ? D Dec05 0:00 \_ blkid -c /dev/null -o export root 6111 0.0 0.0 4760 1916 ? S Dec12 0:00 /bin/sh /usr/lib/cloud-init/ds-identify root 6149 0.0 0.0 11212 2940 ? D Dec12 0:00 \_ blkid -c /dev/null -o export root 8765 0.0 0.3 926528 24968 ? Ssl Dec12 0:12 /usr/lib/snapd/snapd root 9179 0.0 0.0 4760 1892 ? S Dec12 0:00 /bin/sh /usr/lib/cloud-init/ds-identify root 9185 0.0 0.0 11980 3552 ? D Dec12 0:00 \_ blkid -c /dev/null -o export Distributor ID: Ubuntu Description: Ubuntu 18.04.3 LTS Release: 18.04 Codename: bionic 5.0.0-36-generic #39~18.04.1-Ubuntu SMP Tue Nov 12 11:09:50 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1856560/+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 1749562] Re: openvpn tls-crypt not working
I'm not a programmer but I'll be happy to do whatever I can to facilitate getting this resolved. -- 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/1749562 Title: openvpn tls-crypt not working Status in network-manager package in Ubuntu: Confirmed Bug description: Hi, if i try to connect to my openvpn 2.4 server i got this error on serverside: Feb 14 18:42:22 fenrir openvpn[58665]: tls-crypt unwrap error: packet too short Feb 14 18:42:22 fenrir openvpn[58665]: TLS Error: tls-crypt unwrapping failed from [AF_INET6]:::91.33.41.15:51754 (via :::192.168.2.2%igb0) my server conf: dev ovpns1 verb 1 dev-type tun dev-node /dev/tun1 writepid /var/run/openvpn_server1.pid #user nobody #group nobody script-security 3 daemon keepalive 10 60 ping-timer-rem persist-tun persist-key proto udp cipher AES-256-CBC auth SHA512 up /usr/local/sbin/ovpn-linkup down /usr/local/sbin/ovpn-linkdown client-connect /usr/local/sbin/openvpn.attributes.sh client-disconnect /usr/local/sbin/openvpn.attributes.sh multihome engine cryptodev tls-server server 10.4.0.0 255.255.0.0 client-config-dir /var/etc/openvpn-csc/server1 username-as-common-name auth-user-pass-verify "/usr/local/sbin/ovpn_auth_verify user ZmVucmly false server1 1194" via-env tls-verify "/usr/local/sbin/ovpn_auth_verify tls 'domain.local' 1" lport 1194 management /var/etc/openvpn/server1.sock unix ca /var/etc/openvpn/server1.ca cert /var/etc/openvpn/server1.cert key /var/etc/openvpn/server1.key dh /etc/dh-parameters.4096 tls-crypt /var/etc/openvpn/server1.tls-crypt ncp-ciphers AES-256-CBC persist-remote-ip float topology subnet my client config: dev tun persist-tun persist-key cipher AES-256-CBC ncp-ciphers AES-256-CBC auth SHA512 tls-client client resolv-retry infinite remote tuxist.ddns.net 1194 udp verify-x509-name "domain.local" name auth-user-pass remote-cert-tls server ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.8.4-1ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 CurrentDesktop: KDE Date: Wed Feb 14 18:46:29 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-08-13 (550 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: default via 10.3.0.1 dev wlp3s0 proto static metric 600 10.3.0.0/16 dev wlp3s0 proto kernel scope link src 10.3.141.174 metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=false SourcePackage: network-manager UpgradeStatus: Upgraded to bionic on 2018-02-12 (1 days ago) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp3s0 wifi connected/org/freedesktop/NetworkManager/Devices/3 gameofgods 404f7dfd-a05c-4271-9a7f-6e18bc31e0cf /org/freedesktop/NetworkManager/ActiveConnection/2 eno1ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.8.4connected started full enabled enabled enabled enabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1749562/+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 1859030] Re: libcairo2 does not install on Bionic (18.04)
Thank you for your bug report, it looks like the SRU from https://launchpad.net/ubuntu/+source/cairo/1.15.10-2ubuntu0.1 is not correctly available, do you have bionic-updates enabled for universe? ** Changed in: cairo (Ubuntu) Importance: Undecided => Low ** Changed in: cairo (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cairo in Ubuntu. https://bugs.launchpad.net/bugs/1859030 Title: libcairo2 does not install on Bionic (18.04) Status in cairo package in Ubuntu: Incomplete Bug description: Attempt at installing libcairo2-dev on a clean Bionic install fails as follows: $ sudo apt install libcairo2-dev Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies. libcairo2-dev : Depends: libcairo2 (= 1.15.10-2) but 1.15.10-2ubuntu0.1 is to be installed Depends: libcairo-gobject2 (= 1.15.10-2) but 1.15.10-2ubuntu0.1 is to be installed Depends: libxcb-shm0-dev but it is not going to be installed E: Unable to correct problems, you have held broken packages. Similar issues reported previously on Launchpad are: https://answers.launchpad.net/ubuntu/+source/cairo/+question/262830 and most recently on StackOverflow (just over a week ago) here: https://stackoverflow.com/questions/9437246/unable-to-install-cairo-package-under-linux $ lsb_release -a; uname -a; apt-cache policy libcairo2-dev No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.3 LTS Release: 18.04 Codename: bionic Linux gnuradio 5.0.0-37-generic #40~18.04.1-Ubuntu SMP Thu Nov 14 12:06:39 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux libcairo2-dev: Installed: (none) Candidate: 1.15.10-2 Version table: 1.15.10-2 500 500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1859030/+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 1859031] [NEW] Cursor freezes with synergy software kvm
Public bug reported: I'm using the synergy software KVM to share a mouse and keyboard between two machines, with my Ubuntu workstation as the client. When attempting to drag-and-drop within Qt apps, the mouse cursor will freeze for several seconds. Cursor freezes also occur intermittently as well. I have an issue report for synergy as well: https://github.com/symless /synergy-core/issues/6487 This issue seems to be a regression related to update 1.6.4-3ubuntu0.2. The current workaround is to pin all libx11 packages to the previous (0.1) versions. Release Version: Ubuntu 18.04.3 LTS Package Version: libx11-6:amd64 2:1.6.4-3ubuntu0.2 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libx11-6 2:1.6.4-3ubuntu0.1 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.33.01 Wed Nov 13 00:00:22 UTC 2019 GCC version: gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Thu Jan 9 09:13:29 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GP104GLM [Quadro P5200 Mobile] [10de:1bb5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GP104GLM [Quadro P5200 Mobile] [1028:1832] InstallationDate: Installed on 2018-07-30 (527 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Precision 7730 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-37-generic root=UUID=6599bc95-d2cf-4bb0-b32d-653b78ae0fe9 ro quiet splash acpi=force vt.handoff=1 SourcePackage: libx11 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/11/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 0MG0JR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd11/11/2019:svnDellInc.:pnPrecision7730:pvr:rvnDellInc.:rn0MG0JR:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 7730 dmi.product.sku: 0832 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: libx11 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic possible-manual-nvidia-install ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1859031 Title: Cursor freezes with synergy software kvm Status in libx11 package in Ubuntu: New Bug description: I'm using the synergy software KVM to share a mouse and keyboard between two machines, with my Ubuntu workstation as the client. When attempting to drag-and-drop within Qt apps, the mouse cursor will freeze for several seconds. Cursor freezes also occur intermittently as well. I have an issue report for synergy as well: https://github.com/symless/synergy-core/issues/6487 This issue seems to be a regression related to update 1.6.4-3ubuntu0.2. The current workaround is to pin all libx11 packages to the previous (0.1) versions. Release Version: Ubuntu 18.04.3 LTS Package Version: libx11-6:amd64 2:1.6.4-3ubuntu0.2 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libx11-6 2:1.6.4-3ubuntu0.1 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.33.01 Wed Nov 13
[Touch-packages] [Bug 1859030] [NEW] libcairo2 does not install on Bionic (18.04)
Public bug reported: Attempt at installing libcairo2-dev on a clean Bionic install fails as follows: $ sudo apt install libcairo2-dev Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies. libcairo2-dev : Depends: libcairo2 (= 1.15.10-2) but 1.15.10-2ubuntu0.1 is to be installed Depends: libcairo-gobject2 (= 1.15.10-2) but 1.15.10-2ubuntu0.1 is to be installed Depends: libxcb-shm0-dev but it is not going to be installed E: Unable to correct problems, you have held broken packages. Similar issues reported previously on Launchpad are: https://answers.launchpad.net/ubuntu/+source/cairo/+question/262830 and most recently on StackOverflow (just over a week ago) here: https://stackoverflow.com/questions/9437246/unable-to-install-cairo-package-under-linux $ lsb_release -a; uname -a; apt-cache policy libcairo2-dev No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.3 LTS Release:18.04 Codename: bionic Linux gnuradio 5.0.0-37-generic #40~18.04.1-Ubuntu SMP Thu Nov 14 12:06:39 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux libcairo2-dev: Installed: (none) Candidate: 1.15.10-2 Version table: 1.15.10-2 500 500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ** Affects: cairo (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cairo in Ubuntu. https://bugs.launchpad.net/bugs/1859030 Title: libcairo2 does not install on Bionic (18.04) Status in cairo package in Ubuntu: New Bug description: Attempt at installing libcairo2-dev on a clean Bionic install fails as follows: $ sudo apt install libcairo2-dev Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies. libcairo2-dev : Depends: libcairo2 (= 1.15.10-2) but 1.15.10-2ubuntu0.1 is to be installed Depends: libcairo-gobject2 (= 1.15.10-2) but 1.15.10-2ubuntu0.1 is to be installed Depends: libxcb-shm0-dev but it is not going to be installed E: Unable to correct problems, you have held broken packages. Similar issues reported previously on Launchpad are: https://answers.launchpad.net/ubuntu/+source/cairo/+question/262830 and most recently on StackOverflow (just over a week ago) here: https://stackoverflow.com/questions/9437246/unable-to-install-cairo-package-under-linux $ lsb_release -a; uname -a; apt-cache policy libcairo2-dev No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.3 LTS Release: 18.04 Codename: bionic Linux gnuradio 5.0.0-37-generic #40~18.04.1-Ubuntu SMP Thu Nov 14 12:06:39 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux libcairo2-dev: Installed: (none) Candidate: 1.15.10-2 Version table: 1.15.10-2 500 500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1859030/+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 1858802] Re: libblkid: no bcache UUID due to ambivalent detection of bcache and xfs_external_log for regular xfs in bcache backing device
** Also affects: util-linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: util-linux (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: util-linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: util-linux (Ubuntu Focal) Importance: Undecided Assignee: Mauricio Faria de Oliveira (mfo) Status: In Progress ** Also affects: util-linux (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: util-linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: util-linux (Ubuntu Eoan) Status: New => In Progress ** Changed in: util-linux (Ubuntu Eoan) Importance: Undecided => Medium ** Changed in: util-linux (Ubuntu Eoan) Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo) ** Changed in: util-linux (Ubuntu Disco) Status: New => Invalid ** Changed in: util-linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: util-linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: util-linux (Ubuntu Bionic) Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo) ** Changed in: util-linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: util-linux (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: util-linux (Ubuntu Xenial) Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo) ** Tags added: sts sts-sponsor-mfo -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1858802 Title: libblkid: no bcache UUID due to ambivalent detection of bcache and xfs_external_log for regular xfs in bcache backing device Status in util-linux package in Ubuntu: In Progress Status in util-linux source package in Xenial: In Progress Status in util-linux source package in Bionic: In Progress Status in util-linux source package in Disco: Invalid Status in util-linux source package in Eoan: In Progress Status in util-linux source package in Focal: In Progress Bug description: description/debdiffs to be provided. upstream commit: https://git.kernel.org/pub/scm/utils/util-linux/util-linux.git/commit/?id=d756af7d640c51ce8d1414607bd3f17eeecf2424 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1858802/+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 1858496] Re: Uninstallable build-deps
need to depend on python2, uploaded. ** Changed in: krb5 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1858496 Title: Uninstallable build-deps Status in krb5 package in Ubuntu: Fix Released Bug description: $ sudo apt-get build-dep ./ sudo: setrlimit(RLIMIT_CORE): Operation not permitted Note, using directory './' to get the build dependencies Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: builddeps:./ : Depends: python-sphinx but it is not going to be installed Depends: doxygen-latex but it is not going to be installed E: Unable to correct problems, you have held broken packages. Chasing it down a bit: doxygen-latex : Depends: texlive-latex-extra but it is not going to be installed python-sphinx : Depends: python-docutils but it is not going to be installed Depends: python-packaging but it is not going to be installed python-docutils : Depends: python:any (< 2.8) Depends: python:any (>= 2.7~) python-packaging : Depends: python:any (< 2.8) Depends: python:any (>= 2.7~) texlive-latex-extra : Depends: texlive-pictures (>= 2019.20191112) but it is not going to be installed texlive-pictures : Depends: python but it is not going to be installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1858496/+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 1858971] Re: SECLEVEL=2 & tls1.2-min by default are causing ftbfs / autopkgtest failures
** No longer affects: openssh (Ubuntu) ** Also affects: nodejs (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/1858971 Title: SECLEVEL=2 & tls1.2-min by default are causing ftbfs / autopkgtest failures Status in nodejs package in Ubuntu: New Status in openssl package in Ubuntu: New Status in python2.7 package in Ubuntu: New Status in ruby-openssl package in Ubuntu: New Status in ruby2.5 package in Ubuntu: New Bug description: SECLEVEL=2 by default is causing ftbfs / autopkgtest failure openssl switched to SECLEVEL=2 by default Causes: SSL_CTX_use_certificate: ca md too weak in ruby2.5 ruby-openssl openssl uses tls1.2-min: test_ssl failing in python2.7 ERROR: test_protocol_sslv23 (test.test_ssl.ThreadedTests) Connecting to an SSLv23 server with various client options ERROR: test_protocol_tlsv1_1 (test.test_ssl.ThreadedTests) Connecting to a TLSv1.1 server with various client options. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nodejs/+bug/1858971/+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 1859013] [NEW] openssh tests use "not valid yet" certificate from 2020, which is now valid
Public bug reported:
openssh tests use "not valid yet" certificate from 2020, which is now
valid
https://anongit.mindrot.org/openssh.git/commit/?id=ff31f15773ee173502eec4d7861ec56f26bba381
this causes autopkgtest regression suite fail in 2020
grep 20200101 -r .
./openssh-7.6p1/regress/cert-hostkey.sh:test_one "cert not yet valid" failure
"-h -V20200101:20300101"
./openssh-7.6p1/regress/cert-userkey.sh:test_one "cert not yet valid" failure
"-n ${USER} -V20200101:20300101"
./openssh-7.2p2/regress/cert-hostkey.sh:test_one "cert not yet valid" failure
"-h -V20200101:20300101"
./openssh-7.2p2/regress/cert-userkey.sh:test_one "cert not yet valid" failure
"-n ${USER} -V20200101:20300101"
./openssh-6.6p1/regress/cert-hostkey.sh:test_one "cert not yet valid" failure
"-h -V20200101:20300101"
./openssh-6.6p1/regress/cert-userkey.sh:test_one "cert not yet valid" failure
"-n ${USER} -V20200101:20300101"
./openssh-5.9p1/regress/cert-hostkey.sh:test_one "cert not yet valid" failure
"-h -V20200101:20300101"
./openssh-5.9p1/regress/cert-userkey.sh:test_one "cert not yet valid" failure
"-n ${USER} -V20200101:20300101"
fixed in debian https://tracker.debian.org/news/1092767/accepted-
openssh-181p1-4-source-into-unstable/
** Affects: openssh (Ubuntu)
Importance: Undecided
Status: New
** Affects: openssh (Ubuntu Precise)
Importance: Undecided
Status: New
** Affects: openssh (Ubuntu Trusty)
Importance: Undecided
Status: New
** Affects: openssh (Ubuntu Xenial)
Importance: Undecided
Status: New
** Affects: openssh (Ubuntu Bionic)
Importance: Undecided
Status: New
** Affects: openssh (Ubuntu Disco)
Importance: Undecided
Status: New
** Affects: openssh (Ubuntu Eoan)
Importance: Undecided
Status: New
** Affects: openssh (Ubuntu Focal)
Importance: Undecided
Status: New
** Tags: update-excuse
** Tags added: update-excuse
** Description changed:
openssh tests use "not valid yet" certificate from 2020, which is now
valid
https://anongit.mindrot.org/openssh.git/commit/?id=ff31f15773ee173502eec4d7861ec56f26bba381
this causes autopkgtest regression suite fail in 2020
+
+ grep 20200101 -r .
+ ./openssh-7.6p1/regress/cert-hostkey.sh:test_one "cert not yet valid" failure
"-h -V20200101:20300101"
+ ./openssh-7.6p1/regress/cert-userkey.sh:test_one "cert not yet valid" failure
"-n ${USER} -V20200101:20300101"
+ ./openssh-7.2p2/regress/cert-hostkey.sh:test_one "cert not yet valid" failure
"-h -V20200101:20300101"
+ ./openssh-7.2p2/regress/cert-userkey.sh:test_one "cert not yet valid" failure
"-n ${USER} -V20200101:20300101"
+ ./openssh-6.6p1/regress/cert-hostkey.sh:test_one "cert not yet valid" failure
"-h -V20200101:20300101"
+ ./openssh-6.6p1/regress/cert-userkey.sh:test_one "cert not yet valid" failure
"-n ${USER} -V20200101:20300101"
+ ./openssh-5.9p1/regress/cert-hostkey.sh:test_one "cert not yet valid" failure
"-h -V20200101:20300101"
+ ./openssh-5.9p1/regress/cert-userkey.sh:test_one "cert not yet valid" failure
"-n ${USER} -V20200101:20300101"
** Also affects: openssh (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: openssh (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: openssh (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: openssh (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: openssh (Ubuntu Eoan)
Importance: Undecided
Status: New
** Also affects: openssh (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: openssh (Ubuntu Disco)
Importance: Undecided
Status: New
** Description changed:
openssh tests use "not valid yet" certificate from 2020, which is now
valid
https://anongit.mindrot.org/openssh.git/commit/?id=ff31f15773ee173502eec4d7861ec56f26bba381
this causes autopkgtest regression suite fail in 2020
- grep 20200101 -r .
+ grep 20200101 -r .
./openssh-7.6p1/regress/cert-hostkey.sh:test_one "cert not yet valid" failure
"-h -V20200101:20300101"
./openssh-7.6p1/regress/cert-userkey.sh:test_one "cert not yet valid" failure
"-n ${USER} -V20200101:20300101"
./openssh-7.2p2/regress/cert-hostkey.sh:test_one "cert not yet valid" failure
"-h -V20200101:20300101"
./openssh-7.2p2/regress/cert-userkey.sh:test_one "cert not yet valid" failure
"-n ${USER} -V20200101:20300101"
./openssh-6.6p1/regress/cert-hostkey.sh:test_one "cert not yet valid" failure
"-h -V20200101:20300101"
./openssh-6.6p1/regress/cert-userkey.sh:test_one "cert not yet valid" failure
"-n ${USER} -V20200101:20300101"
./openssh-5.9p1/regress/cert-hostkey.sh:test_one "cert not yet valid" failure
"-h -V20200101:20300101"
./openssh-5.9p1/regress/cert-userkey.sh:test_one "cert not yet valid" failure
"-n ${USER} -V20200101:20300101"
+
+ fixed in debian
[Touch-packages] [Bug 1857123] Re: IPv4 addresses are not assigned in LXC with systemd 244.1
244.1 was removed from proposed. ** Tags removed: block-proposed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1857123 Title: IPv4 addresses are not assigned in LXC with systemd 244.1 Status in systemd package in Ubuntu: New Bug description: triaging To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1857123/+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 1847570] Re: PulseAudio automatically switches to HDMI sound output on login
I can confirm that hdmi is not selected when monitor returns from sleep (I did something and the correct sound device would be selected at startup before updating from proposed). However, closing and reopening the monitor manually causes HDMI to be selected. I don't think that used to happen previously. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1847570 Title: PulseAudio automatically switches to HDMI sound output on login Status in PulseAudio: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Eoan: Fix Committed Status in pulseaudio source package in Focal: Fix Released Bug description: [Impact] On my freshly installed eoan system I have two output devices: - HDMI/DisplayPort 2 - GK208 ... - Line Out - Family 17h ... When I login into the system pulseaudio always select the "wrong" one (HDMI) and I need to go to gnome-settings/Sound/Output Device and switch to "line out". This applies to every login/logout not just reboots. [Test Case] 0. Plug in a monitor that supports HDMI audio (one that appears in your Settings>Sound) 1. Log out and in again. Verify the default audio device in Settings is still speakers or headphones. Not the monitor's HDMI audio device. [Regression Potential] The behaviour is changed back to what it was before 19.10, some users might find it inconvenient and prefer the auto switch but the feedback we got shows it's unreliable and an annoying for the majority of our users so we will got back to default to safest behaviour. The fix proposed just reverts to the same code used in PulseAudio 12 and earlier. It has also been released and verified on focal already. [Workaround] Comment out: load-module module-switch-on-port-available load-module module-switch-on-connect from /etc/pulse/default.pa To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1847570/+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 1847570] Re: PulseAudio automatically switches to HDMI sound output on login
Never mind the however part, it is fixed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1847570 Title: PulseAudio automatically switches to HDMI sound output on login Status in PulseAudio: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Eoan: Fix Committed Status in pulseaudio source package in Focal: Fix Released Bug description: [Impact] On my freshly installed eoan system I have two output devices: - HDMI/DisplayPort 2 - GK208 ... - Line Out - Family 17h ... When I login into the system pulseaudio always select the "wrong" one (HDMI) and I need to go to gnome-settings/Sound/Output Device and switch to "line out". This applies to every login/logout not just reboots. [Test Case] 0. Plug in a monitor that supports HDMI audio (one that appears in your Settings>Sound) 1. Log out and in again. Verify the default audio device in Settings is still speakers or headphones. Not the monitor's HDMI audio device. [Regression Potential] The behaviour is changed back to what it was before 19.10, some users might find it inconvenient and prefer the auto switch but the feedback we got shows it's unreliable and an annoying for the majority of our users so we will got back to default to safest behaviour. The fix proposed just reverts to the same code used in PulseAudio 12 and earlier. It has also been released and verified on focal already. [Workaround] Comment out: load-module module-switch-on-port-available load-module module-switch-on-connect from /etc/pulse/default.pa To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1847570/+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 1788608] Re: wget doesn't support compression, it needs zlib1g-dev
** Changed in: wget (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wget in Ubuntu. https://bugs.launchpad.net/bugs/1788608 Title: wget doesn't support compression, it needs zlib1g-dev Status in wget package in Ubuntu: Fix Released Status in wget package in Debian: Fix Released Bug description: wget can use zlib1g for a few features, notably --compression support. The Debian package doesn't explicitly build-depend on zlib1g-dev, it gets it via libgnutls28-dev; since the Ubuntu package drops the latter, compression support is lost too. Please consider adding zlib1g-dev. (I've also asked the Debian maintainer to do so, see the linked bug; however the libgnutls28-dev removal in Ubuntu should take this into account IMO.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wget/+bug/1788608/+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 1838838] Re: username is not saved in openconnect connection dialog
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/328 ** Bug watch added: gitlab.freedesktop.org/NetworkManager/NetworkManager/issues #328 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/328 -- 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/1838838 Title: username is not saved in openconnect connection dialog Status in network-manager package in Ubuntu: Confirmed Status in network-manager-openconnect package in Ubuntu: Confirmed Bug description: Same issue as https://bugs.launchpad.net/ubuntu/+source/network- manager-openconnect/+bug/1609700 This was marked resolved. The report of its reappearance in Ubuntu 19.04 and 19.10 has not been acknowledged. This was working for me in 18.10, but a fresh install of 19.04 and 19.10 show that it is back. The password is saved when the option to save passwords is selected, but the username must be entered manually upon connection. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1838838/+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 1851806] Re: 'module' object has no attribute 'O_PATH'
** Changed in: apport (Ubuntu)
Assignee: (unassigned) => Tiago Stürmer Daitx (tdaitx)
** Changed in: apport (Ubuntu)
Importance: Undecided => High
** Changed in: apport (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1851806
Title:
'module' object has no attribute 'O_PATH'
Status in apport package in Ubuntu:
In Progress
Bug description:
I encountered the following exception in python-apport while
encountering an exception `bup` which uses `python-apport`. I'm sure
that the exception lies in the responsibility of `python-apport` (the
`AttributeError` stacktrace is relevant):
```
Traceback (most recent call last):
File "/usr/lib/bup/cmd/bup-index", line 269, in
update_index(rp, excluded_paths, exclude_rxs, xdev_exceptions=xexcept)
File "/usr/lib/bup/cmd/bup-index", line 191, in update_index
mi.close()
File "/usr/lib/bup/bup/index.py", line 528, in close
os.rename(self.tmpname, self.filename)
OSError: [Errno 13] Permission denied
Error in sys.excepthook:
Traceback (most recent call last):
File "/usr/lib/bup/bup/helpers.py", line 916, in newhook
return oldhook(exctype, value, traceback)
File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 109, in
apport_excepthook
pr.add_proc_info(extraenv=['PYTHONPATH', 'PYTHONHOME'])
File "/usr/lib/python2.7/dist-packages/apport/report.py", line 544, in
add_proc_info
proc_pid_fd = os.open('/proc/%s' % pid, os.O_RDONLY | os.O_PATH |
os.O_DIRECTORY)
AttributeError: 'module' object has no attribute 'O_PATH'
Original exception was:
Traceback (most recent call last):
File "/usr/lib/bup/cmd/bup-index", line 269, in
update_index(rp, excluded_paths, exclude_rxs, xdev_exceptions=xexcept)
File "/usr/lib/bup/cmd/bup-index", line 191, in update_index
mi.close()
File "/usr/lib/bup/bup/index.py", line 528, in close
os.rename(self.tmpname, self.filename)
OSError: [Errno 13] Permission denied
```
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: python-apport 2.20.11-0ubuntu8.2
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportLog: Error: [Errno 13] Keine Berechtigung: '/var/log/apport.log'
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Nov 8 10:43:02 2019
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: Upgraded to eoan on 2019-10-25 (13 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1851806/+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 1847967] Re: oem kernel packages treated differently from generic kernel ones
@Francis, anything I can help here? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1847967 Title: oem kernel packages treated differently from generic kernel ones Status in OEM Priority Project: New Status in apport package in Ubuntu: Fix Released Status in apport source package in Bionic: In Progress Status in apport source package in Disco: In Progress Status in apport source package in Eoan: In Progress Status in apport source package in Focal: Fix Released Bug description: [SRU Justification] [Impact] When `apport-bug linux` was executed on systems with linux-oem, linux-oem-osp1 kernels, many details are not included as generic linux kernel does. Alsa info, dmesg, lspci, lsusb, DMI, etc. are missing. [Fix] Fix already merged in Focal: https://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu/focal/apport/ubuntu/revision/2724 . SRU merge proposals in: * https://code.launchpad.net/~vicamo/ubuntu/bionic/apport/bug-1847967/+merge/376380 * https://code.launchpad.net/~vicamo/ubuntu/disco/apport/bug-1847967/+merge/376381 * https://code.launchpad.net/~vicamo/ubuntu/eoan/apport/bug-1847967/+merge/374263 [Test Case] 1. Boot with linux-oem or linux-oem-osp1 kernel and try to collect apport logs with: $ apport-cli --save saved.apport linux-oem-osp1 2. Make sure the report contains PCI/ALSA/DMI/Sysfs info. [Regression Potential] Low. original bug description When `apport-bug linux` was executed on systems with linux-oem, linux- oem-osp1 kernels, many details are not included as generic linux kernel does. Alsa info, dmesg, lspci, lsusb, DMI, etc. are missing. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1847967/+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 1856501] Re: xgettext cannot deal with jsx self-closing tags
thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/1856501 Title: xgettext cannot deal with jsx self-closing tags Status in gettext package in Ubuntu: In Progress Bug description: Bug in xgettext: https://savannah.gnu.org/bugs/?56848 Fixed through https://git.savannah.gnu.org/gitweb/?p=gettext.git;a=commitdiff;h=8f8b910322f5905045a8731df7aca5e601c9b082 Can you apply this patch? It really needed. ProblemType: Bug Architecture: x86_64 Date: Mon Dec 16 09:30:05 +07 2019 DistroRelease: Ubuntu 18.04 Package: gettext 0.19.8.1-6ubuntu0.3 PackageArchitecture: amd64 SourcePackage: gettext Uname: Linux 5.0.0-36-generic #39~18.04.1-Ubuntu SMP Tue Nov 12 11:09:50 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gettext/+bug/1856501/+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 1856501] Re: xgettext cannot deal with jsx self-closing tags
xgettext --from-code=utf-8 --language=JavaScript --keyword=translate Documentation.jsx ** Attachment added: "Documentation.jsx" https://bugs.launchpad.net/ubuntu/+source/gettext/+bug/1856501/+attachment/5318792/+files/Documentation.jsx -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/1856501 Title: xgettext cannot deal with jsx self-closing tags Status in gettext package in Ubuntu: In Progress Bug description: Bug in xgettext: https://savannah.gnu.org/bugs/?56848 Fixed through https://git.savannah.gnu.org/gitweb/?p=gettext.git;a=commitdiff;h=8f8b910322f5905045a8731df7aca5e601c9b082 Can you apply this patch? It really needed. ProblemType: Bug Architecture: x86_64 Date: Mon Dec 16 09:30:05 +07 2019 DistroRelease: Ubuntu 18.04 Package: gettext 0.19.8.1-6ubuntu0.3 PackageArchitecture: amd64 SourcePackage: gettext Uname: Linux 5.0.0-36-generic #39~18.04.1-Ubuntu SMP Tue Nov 12 11:09:50 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gettext/+bug/1856501/+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 1856501] Re: xgettext cannot deal with jsx self-closing tags
Thanks for the detail, could you add a jsx example to the bug that could be used as testcase? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/1856501 Title: xgettext cannot deal with jsx self-closing tags Status in gettext package in Ubuntu: In Progress Bug description: Bug in xgettext: https://savannah.gnu.org/bugs/?56848 Fixed through https://git.savannah.gnu.org/gitweb/?p=gettext.git;a=commitdiff;h=8f8b910322f5905045a8731df7aca5e601c9b082 Can you apply this patch? It really needed. ProblemType: Bug Architecture: x86_64 Date: Mon Dec 16 09:30:05 +07 2019 DistroRelease: Ubuntu 18.04 Package: gettext 0.19.8.1-6ubuntu0.3 PackageArchitecture: amd64 SourcePackage: gettext Uname: Linux 5.0.0-36-generic #39~18.04.1-Ubuntu SMP Tue Nov 12 11:09:50 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gettext/+bug/1856501/+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 1838838] Re: username is not saved in openconnect connection dialog
Could someone having the issue report it upstream on https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues ? -- 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/1838838 Title: username is not saved in openconnect connection dialog Status in network-manager package in Ubuntu: Confirmed Status in network-manager-openconnect package in Ubuntu: Confirmed Bug description: Same issue as https://bugs.launchpad.net/ubuntu/+source/network- manager-openconnect/+bug/1609700 This was marked resolved. The report of its reappearance in Ubuntu 19.04 and 19.10 has not been acknowledged. This was working for me in 18.10, but a fresh install of 19.04 and 19.10 show that it is back. The password is saved when the option to save passwords is selected, but the username must be entered manually upon connection. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1838838/+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 1848476] Re: [ZenBook UX534FT_UX534FT, Realtek ALC294, Black Headphone Out, Left] No sound at all
*** This bug is a duplicate of bug 1850439 *** https://bugs.launchpad.net/bugs/1850439 ** This bug has been marked a duplicate of bug 1850439 No sound on ASUS UX534FT -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1848476 Title: [ZenBook UX534FT_UX534FT, Realtek ALC294, Black Headphone Out, Left] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: Ubuntu 18.04.3 LTS The sound works until I plug the headphones and then it never works again, even without them. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.3.6-050306-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daniela2692 F pulseaudio /dev/snd/pcmC0D0c: daniela2692 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Oct 17 11:03:37 2019 InstallationDate: Installed on 2019-09-18 (28 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1426 F pulseaudio daniela2692 F pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [ZenBook UX534FT_UX534FT, Realtek ALC294, Black Headphone Out, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/10/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX534FT.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX534FT dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX534FT.204:bd06/10/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX534FT_UX534FT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX534FT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX534FT_UX534FT dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1848476/+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
