[Touch-packages] [Bug 1961561] Re: [radeon] Blinking screen
As told, the file was send from the computer but it doesn't show any new bug-number, crash file should be somewhere in the bug queue. I send it twice. Will restart the procedure. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1961561 Title: [radeon] Blinking screen Status in compiz package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: Binking screen with radeon after upgrade 18.04 to 20.04 - Console OK ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Feb 21 10:13:34 2022 DistUpgraded: 2021-03-08 13:38:14,332 DEBUG package 'libcpanel-json-xs-perl' produces an unwanted removal 'gnome-software-plugin-snap', skipping DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS482/RS485 [Radeon Xpress 1100/1150] [1002:5974] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company DC5750 Microtower [103c:280a] Subsystem: Hewlett-Packard Company RS480 [Radeon Xpress 1150] (Secondary) [103c:280b] InstallationDate: Installed on 2015-11-26 (2278 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Hewlett-Packard HP Compaq dc5750 Small Form Factor ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic root=UUID=681c938b-c95d-48de-886f-bc784bb57787 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2021-03-08 (349 days ago) dmi.bios.date: 01/25/2007 dmi.bios.release: 2.10 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786E3 v02.10 dmi.board.name: 0A64h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC8061JND dmi.chassis.type: 4 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786E3v02.10:bd01/25/2007:br2.10:svnHewlett-Packard:pnHPCompaqdc5750SmallFormFactor:pvr:rvnHewlett-Packard:rn0A64h:rvr:cvnHewlett-Packard:ct4:cvr:skuEW318AV: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq dc5750 Small Form Factor dmi.product.sku: EW318AV dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Mon Feb 21 10:00:44 2022 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.13-1ubuntu1~20.04.2 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1961561/+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 1961743] [NEW] ss
Private bug reported: sss ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: python3 3.8.2-0ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Feb 22 17:01:33 2022 InstallationDate: Installed on 2022-01-04 (49 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: python3-defaults UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: python3-defaults (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Information type changed from Public to Private -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1961743 Title: ss Status in python3-defaults package in Ubuntu: New Bug description: sss ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: python3 3.8.2-0ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Feb 22 17:01:33 2022 InstallationDate: Installed on 2022-01-04 (49 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: python3-defaults UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1961743/+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 1961561] Re: [radeon] Blinking screen
That's just step 1, so try step 2. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1961561 Title: [radeon] Blinking screen Status in compiz package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: Binking screen with radeon after upgrade 18.04 to 20.04 - Console OK ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Feb 21 10:13:34 2022 DistUpgraded: 2021-03-08 13:38:14,332 DEBUG package 'libcpanel-json-xs-perl' produces an unwanted removal 'gnome-software-plugin-snap', skipping DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS482/RS485 [Radeon Xpress 1100/1150] [1002:5974] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company DC5750 Microtower [103c:280a] Subsystem: Hewlett-Packard Company RS480 [Radeon Xpress 1150] (Secondary) [103c:280b] InstallationDate: Installed on 2015-11-26 (2278 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Hewlett-Packard HP Compaq dc5750 Small Form Factor ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic root=UUID=681c938b-c95d-48de-886f-bc784bb57787 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2021-03-08 (349 days ago) dmi.bios.date: 01/25/2007 dmi.bios.release: 2.10 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786E3 v02.10 dmi.board.name: 0A64h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC8061JND dmi.chassis.type: 4 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786E3v02.10:bd01/25/2007:br2.10:svnHewlett-Packard:pnHPCompaqdc5750SmallFormFactor:pvr:rvnHewlett-Packard:rn0A64h:rvr:cvnHewlett-Packard:ct4:cvr:skuEW318AV: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq dc5750 Small Form Factor dmi.product.sku: EW318AV dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Mon Feb 21 10:00:44 2022 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.13-1ubuntu1~20.04.2 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1961561/+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 1953052] Re: In Jammy sound level reset after reboot
** Changed in: alsa-utils (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: pipewire (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: pulseaudio (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) -- 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/1953052 Title: In Jammy sound level reset after reboot Status in pipewire package in Ubuntu: In Progress Bug description: After reboot sound level is reset ignoring the level set in previous session. I manually set the sound output level at next boot the sound is set at a different level (about 70%) Expected: the sound level is persistent across power off/on What happens : sound level is set at a different level (about 70%) Note: this problem does not occur on different partitions of same PC running Ubuntu 20.04 or 21.10 corrado@corrado-p3-jj-1130:~$ apt policy gnome-control-center gnome-control-center: Installed: 1:41.1-1ubuntu1 Candidate: 1:41.1-1ubuntu1 Version table: *** 1:41.1-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status corrado@corrado-p3-jj-1130:~$ inxi -Fx System:Host: corrado-p3-jj-1130 Kernel: 5.13.0-19-generic x86_64 bits: 64 compiler: gcc v: 11.2.0 Desktop: GNOME 40.5 Distro: Ubuntu 22.04 (Jammy Jellyfish) Machine: Type: Laptop System: Dell product: Inspiron 3793 v: N/A serial: Mobo: Dell model: 0C1PF2 v: A00 serial: UEFI: Dell v: 1.5.0 date: 12/17/2019 Battery: ID-1: BAT0 charge: 13.9 Wh (42.1%) condition: 33.0/42.0 Wh (78.7%) volts: 11.3 min: 11.4 model: SWD-ATL3.618 DELL WJPC403 status: Discharging CPU: Info: Quad Core model: Intel Core i5-1035G1 bits: 64 type: MT MCP arch: Ice Lake rev: 5 cache: L2: 6 MiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19046 Speed: 968 MHz min/max: 400/1000 MHz Core speeds (MHz): 1: 968 2: 710 3: 706 4: 714 5: 966 6: 712 7: 724 8: 821 Graphics: Device-1: Intel Iris Plus Graphics G1 vendor: Dell driver: i915 v: kernel bus-ID: 00:02.0 Device-2: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo bus-ID: 1-6:3 Display: wayland server: X.Org 1.21.1.2 compositor: gnome-shell driver: loaded: i915 note: n/a (using device driver) resolution: 1920x1080~60Hz OpenGL: renderer: Mesa Intel UHD Graphics (ICL GT1) v: 4.6 Mesa 21.2.2 direct render: Yes Audio: Device-1: Intel Ice Lake-LP Smart Sound Audio vendor: Dell driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 Sound Server-1: ALSA v: k5.13.0-19-generic running: yes Sound Server-2: PulseAudio v: 15.0 running: yes Sound Server-3: PipeWire v: 0.3.40 running: yes Network: Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Dell driver: r8169 v: kernel port: 3000 bus-ID: 01:00.0 IF: enp1s0 state: down mac: 98:e7:43:59:19:19 Device-2: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter vendor: Dell driver: ath10k_pci v: kernel bus-ID: 02:00.0 IF: wlp2s0 state: up mac: d8:12:65:b8:21:b9 Bluetooth: Device-1: Qualcomm Atheros type: USB driver: btusb v: 0.8 bus-ID: 1-10:4 Report: hciconfig ID: hci0 rfk-id: 0 state: down bt-service: enabled,running rfk-block: hardware: no software: yes address: D8:12:65:B8:21:BA Drives:Local Storage: total: 942.7 GiB used: 11.77 GiB (1.2%) ID-1: /dev/nvme0n1 vendor: Toshiba model: KBG40ZNS512G NVMe KIOXIA 512GB size: 476.94 GiB temp: 24.9 C ID-2: /dev/sda vendor: Crucial model: CT500MX500SSD1 size: 465.76 GiB Partition: ID-1: / size: 46.95 GiB used: 11.73 GiB (25.0%) fs: ext4 dev: /dev/nvme0n1p3 ID-2: /boot/efi size: 246 MiB used: 46.4 MiB (18.9%) fs: vfat dev: /dev/nvme0n1p1 Swap: Alert: No swap data was found. Sensors: System Temperatures: cpu: 27.8 C mobo: N/A Fan Speeds (RPM): cpu: 0 Info: Processes: 263 Uptime: 31m Memory: 15.4 GiB used: 2.45 GiB (15.9%) Init: systemd runlevel: 5 Compilers: gcc: N/A Packages: 1785 Shell: Bash v: 5.1.12 inxi: 3.3.07 corrado@corrado-p3-jj-1130:~$ --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-11-30 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130) Package: gnome-control-center 1:41.1-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Tags: wayland-session jammy
[Touch-packages] [Bug 1953052] Re: In Jammy sound level reset after reboot
The offending package seems to be coming via: ubuntu-meta > gnome-remote-desktop > pipewire-media-session | wireplumber So it's a dependency we probably can't drop. Maybe a config change is the only real option. ** No longer affects: alsa-utils (Ubuntu) ** No longer affects: pulseaudio (Ubuntu) ** Changed in: pipewire (Ubuntu) Status: Confirmed => In Progress -- 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/1953052 Title: In Jammy sound level reset after reboot Status in pipewire package in Ubuntu: In Progress Bug description: After reboot sound level is reset ignoring the level set in previous session. I manually set the sound output level at next boot the sound is set at a different level (about 70%) Expected: the sound level is persistent across power off/on What happens : sound level is set at a different level (about 70%) Note: this problem does not occur on different partitions of same PC running Ubuntu 20.04 or 21.10 corrado@corrado-p3-jj-1130:~$ apt policy gnome-control-center gnome-control-center: Installed: 1:41.1-1ubuntu1 Candidate: 1:41.1-1ubuntu1 Version table: *** 1:41.1-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status corrado@corrado-p3-jj-1130:~$ inxi -Fx System:Host: corrado-p3-jj-1130 Kernel: 5.13.0-19-generic x86_64 bits: 64 compiler: gcc v: 11.2.0 Desktop: GNOME 40.5 Distro: Ubuntu 22.04 (Jammy Jellyfish) Machine: Type: Laptop System: Dell product: Inspiron 3793 v: N/A serial: Mobo: Dell model: 0C1PF2 v: A00 serial: UEFI: Dell v: 1.5.0 date: 12/17/2019 Battery: ID-1: BAT0 charge: 13.9 Wh (42.1%) condition: 33.0/42.0 Wh (78.7%) volts: 11.3 min: 11.4 model: SWD-ATL3.618 DELL WJPC403 status: Discharging CPU: Info: Quad Core model: Intel Core i5-1035G1 bits: 64 type: MT MCP arch: Ice Lake rev: 5 cache: L2: 6 MiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19046 Speed: 968 MHz min/max: 400/1000 MHz Core speeds (MHz): 1: 968 2: 710 3: 706 4: 714 5: 966 6: 712 7: 724 8: 821 Graphics: Device-1: Intel Iris Plus Graphics G1 vendor: Dell driver: i915 v: kernel bus-ID: 00:02.0 Device-2: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo bus-ID: 1-6:3 Display: wayland server: X.Org 1.21.1.2 compositor: gnome-shell driver: loaded: i915 note: n/a (using device driver) resolution: 1920x1080~60Hz OpenGL: renderer: Mesa Intel UHD Graphics (ICL GT1) v: 4.6 Mesa 21.2.2 direct render: Yes Audio: Device-1: Intel Ice Lake-LP Smart Sound Audio vendor: Dell driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 Sound Server-1: ALSA v: k5.13.0-19-generic running: yes Sound Server-2: PulseAudio v: 15.0 running: yes Sound Server-3: PipeWire v: 0.3.40 running: yes Network: Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Dell driver: r8169 v: kernel port: 3000 bus-ID: 01:00.0 IF: enp1s0 state: down mac: 98:e7:43:59:19:19 Device-2: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter vendor: Dell driver: ath10k_pci v: kernel bus-ID: 02:00.0 IF: wlp2s0 state: up mac: d8:12:65:b8:21:b9 Bluetooth: Device-1: Qualcomm Atheros type: USB driver: btusb v: 0.8 bus-ID: 1-10:4 Report: hciconfig ID: hci0 rfk-id: 0 state: down bt-service: enabled,running rfk-block: hardware: no software: yes address: D8:12:65:B8:21:BA Drives:Local Storage: total: 942.7 GiB used: 11.77 GiB (1.2%) ID-1: /dev/nvme0n1 vendor: Toshiba model: KBG40ZNS512G NVMe KIOXIA 512GB size: 476.94 GiB temp: 24.9 C ID-2: /dev/sda vendor: Crucial model: CT500MX500SSD1 size: 465.76 GiB Partition: ID-1: / size: 46.95 GiB used: 11.73 GiB (25.0%) fs: ext4 dev: /dev/nvme0n1p3 ID-2: /boot/efi size: 246 MiB used: 46.4 MiB (18.9%) fs: vfat dev: /dev/nvme0n1p1 Swap: Alert: No swap data was found. Sensors: System Temperatures: cpu: 27.8 C mobo: N/A Fan Speeds (RPM): cpu: 0 Info: Processes: 263 Uptime: 31m Memory: 15.4 GiB used: 2.45 GiB (15.9%) Init: systemd runlevel: 5 Compilers: gcc: N/A Packages: 1785 Shell: Bash v: 5.1.12 inxi: 3.3.07 corrado@corrado-p3-jj-1130:~$ --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-11-30 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130) Package: gnome-control-center 1:41.1-1ubuntu1 PackageArchitecture: a
[Touch-packages] [Bug 1961769] [NEW] Pulse audio doesn't switch to headset-input when microphone requested
Public bug reported: I've recently upgraded 2 versions - from Ubuntu 18.04 LTS to 20.04 LTS and then to 21.10. Before I was able to both listen quality audio and speak over my headset. Right now after some time of struggling with why I can't use bluetooth microphone anymore I've realised it's because it used A2DP profile which doesn't support mic input. I can't check it now but pretty sure microphone usage was seamless in past - I didn't need to manually switch to HFP/HSP and then back to A2DP to listen music. Can we reintroduce this functionality ? "nusch@xps13:~$ LANG="en" pactl list | grep -iA 100 jabra Description: Jabra Evolve 65 Driver: module-bluez5-device.c Sample Specification: s16le 2ch 44100Hz Channel Map: front-left,front-right Owner Module: 26 Mute: no Volume: front-left: 56763 / 87%, front-right: 0 / 0% balance -1.00 Base Volume: 65536 / 100% Monitor Source: bluez_sink.30_50_75_07_11_8C.a2dp_sink.monitor Latency: 0 usec, configured 0 usec Flags: HARDWARE HW_VOLUME_CTRL LATENCY Properties: bluetooth.protocol = "a2dp_sink" bluetooth.codec = "sbc" device.description = "Jabra Evolve 65" device.string = "30:50:75:07:11:8C" device.api = "bluez" device.class = "sound" device.bus = "bluetooth" device.form_factor = "headset" bluez.path = "/org/bluez/hci0/dev_30_50_75_07_11_8C" bluez.class = "0x240404" bluez.alias = "Jabra Evolve 65" device.icon_name = "audio-headset-bluetooth" device.intended_roles = "phone" Ports: headset-output: Słuchawki z mikrofonem (type: Headset, priority: 0, availability unknown) Active Port: headset-output Formats: pcm Source #1 State: SUSPENDED Name: alsa_output.pci-_00_1f.3.analog-stereo.monitor Description: Monitor of Wbudowany dźwięk Analogowe stereo Driver: module-alsa-card.c Sample Specification: s16le 2ch 48000Hz Channel Map: front-left,front-right Owner Module: 22 Mute: no Volume: front-left: 65536 / 100% / 0.00 dB, front-right: 65536 / 100% / 0.00 dB balance 0.00 Base Volume: 65536 / 100% / 0.00 dB Monitor of Sink: alsa_output.pci-_00_1f.3.analog-stereo Latency: 0 usec, configured 0 usec Flags: DECIBEL_VOLUME LATENCY Properties: device.description = "Monitor of Wbudowany dźwięk Analogowe stereo" device.class = "monitor" alsa.card = "0" alsa.card_name = "HDA Intel PCH" alsa.long_card_name = "HDA Intel PCH at 0x60531d8000 irq 188" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-:00:1f.3" sysfs.path = "/devices/pci:00/:00:1f.3/sound/card0" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "a0c8" device.product.name = "Tiger Lake-LP Smart Sound Technology Audio Controller" device.form_factor = "internal" device.string = "0" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" Formats: pcm Source #20 State: SUSPENDED Name: bluez_sink.30_50_75_07_11_8C.a2dp_sink.monitor Description: Monitor of Jabra Evolve 65 Driver: module-bluez5-device.c Sample Specification: s16le 2ch 44100Hz Channel Map: front-left,front-right Owner Module: 26 Mute: no Volume: front-left: 65536 / 100% / 0.00 dB, front-right: 65536 / 100% / 0.00 dB balance 0.00 Base Volume: 65536 / 100% / 0.00 dB Monitor of Sink: bluez_sink.30_50_75_07_11_8C.a2dp_sink Latency: 0 usec, configured 0 usec Flags: DECIBEL_VOLUME LATENCY Properties: device.description = "Monitor of Jabra Evolve 65" device.class = "monitor" device.string = "30:50:75:07:11:8C" device.api = "bluez" device.bus = "bluetooth" device.form_factor = "headset" bluez.path = "/org/bluez/hci0/dev_30_50_75_07_11_8C" bluez.class = "0x240404" bluez.alias = "Jabra Evolve 65" device.icon_name = "audio-headset-bluetooth" device.intended_roles = "phone" Formats: pcm Sink Input #58 Driver: protocol-native.c Owner Module: 10 Client: 106 Sink: 14 Sample Specification: s16le 2ch 44100Hz C
[Touch-packages] [Bug 1961561] Re: [radeon] Blinking screen
How can I connect to https://errors.ubuntu.com/user/ID if I have no access to the web browser *FROM* the machine ? I only have console which is usable. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1961561 Title: [radeon] Blinking screen Status in compiz package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: Binking screen with radeon after upgrade 18.04 to 20.04 - Console OK ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Feb 21 10:13:34 2022 DistUpgraded: 2021-03-08 13:38:14,332 DEBUG package 'libcpanel-json-xs-perl' produces an unwanted removal 'gnome-software-plugin-snap', skipping DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS482/RS485 [Radeon Xpress 1100/1150] [1002:5974] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company DC5750 Microtower [103c:280a] Subsystem: Hewlett-Packard Company RS480 [Radeon Xpress 1150] (Secondary) [103c:280b] InstallationDate: Installed on 2015-11-26 (2278 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Hewlett-Packard HP Compaq dc5750 Small Form Factor ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic root=UUID=681c938b-c95d-48de-886f-bc784bb57787 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2021-03-08 (349 days ago) dmi.bios.date: 01/25/2007 dmi.bios.release: 2.10 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786E3 v02.10 dmi.board.name: 0A64h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC8061JND dmi.chassis.type: 4 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786E3v02.10:bd01/25/2007:br2.10:svnHewlett-Packard:pnHPCompaqdc5750SmallFormFactor:pvr:rvnHewlett-Packard:rn0A64h:rvr:cvnHewlett-Packard:ct4:cvr:skuEW318AV: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq dc5750 Small Form Factor dmi.product.sku: EW318AV dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Mon Feb 21 10:00:44 2022 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.13-1ubuntu1~20.04.2 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1961561/+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 1961561] Re: [radeon] Blinking screen
Finally I could manage something, step #2 https://errors.ubuntu.com/user/9578793ceeb5644eebbc93a1c623f77177c6ec9f84bf04c4e4060e749cd18f2fe3e6806ff52ecc9de8fb1a7176ea8a61204188cebea751c0feba4e7c9ebd1a5a -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1961561 Title: [radeon] Blinking screen Status in compiz package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: Binking screen with radeon after upgrade 18.04 to 20.04 - Console OK ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Feb 21 10:13:34 2022 DistUpgraded: 2021-03-08 13:38:14,332 DEBUG package 'libcpanel-json-xs-perl' produces an unwanted removal 'gnome-software-plugin-snap', skipping DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS482/RS485 [Radeon Xpress 1100/1150] [1002:5974] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company DC5750 Microtower [103c:280a] Subsystem: Hewlett-Packard Company RS480 [Radeon Xpress 1150] (Secondary) [103c:280b] InstallationDate: Installed on 2015-11-26 (2278 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Hewlett-Packard HP Compaq dc5750 Small Form Factor ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic root=UUID=681c938b-c95d-48de-886f-bc784bb57787 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2021-03-08 (349 days ago) dmi.bios.date: 01/25/2007 dmi.bios.release: 2.10 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786E3 v02.10 dmi.board.name: 0A64h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC8061JND dmi.chassis.type: 4 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786E3v02.10:bd01/25/2007:br2.10:svnHewlett-Packard:pnHPCompaqdc5750SmallFormFactor:pvr:rvnHewlett-Packard:rn0A64h:rvr:cvnHewlett-Packard:ct4:cvr:skuEW318AV: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq dc5750 Small Form Factor dmi.product.sku: EW318AV dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Mon Feb 21 10:00:44 2022 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.13-1ubuntu1~20.04.2 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1961561/+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 1961800] [NEW] Seeing out of memory errors after upgrade to 2.2.5-3ubuntu0.4
Public bug reported: I started seeing errors parsing XML files today (Feb 22, 2022) after my system was updated to 2.2.5-3ubuntu0.4. This is on a bionic server. The parsing is being done by python3's xmltodict module, which uses python3 expat as the actual parser. This is the error it raises: xml.parsers.expat.ExpatError: out of memory: line 1, column 0 So far this is happening on multiple xml files, although they all come from the same source (these are jenkins config.xml files). I'm working on coming up with a minimal test case which I'll provide once I have it cleaned up of any private data. [System info] $ lsb_release -rd Description:Ubuntu 18.04.6 LTS Release:18.04 $ apt-cache policy libexpat1 libexpat1: Installed: 2.2.5-3ubuntu0.4 Candidate: 2.2.5-3ubuntu0.4 Version table: *** 2.2.5-3ubuntu0.4 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 2.2.5-3 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages ** Affects: expat (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to expat in Ubuntu. https://bugs.launchpad.net/bugs/1961800 Title: Seeing out of memory errors after upgrade to 2.2.5-3ubuntu0.4 Status in expat package in Ubuntu: New Bug description: I started seeing errors parsing XML files today (Feb 22, 2022) after my system was updated to 2.2.5-3ubuntu0.4. This is on a bionic server. The parsing is being done by python3's xmltodict module, which uses python3 expat as the actual parser. This is the error it raises: xml.parsers.expat.ExpatError: out of memory: line 1, column 0 So far this is happening on multiple xml files, although they all come from the same source (these are jenkins config.xml files). I'm working on coming up with a minimal test case which I'll provide once I have it cleaned up of any private data. [System info] $ lsb_release -rd Description:Ubuntu 18.04.6 LTS Release:18.04 $ apt-cache policy libexpat1 libexpat1: Installed: 2.2.5-3ubuntu0.4 Candidate: 2.2.5-3ubuntu0.4 Version table: *** 2.2.5-3ubuntu0.4 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 2.2.5-3 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/expat/+bug/1961800/+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 1960458] Re: patch git_socket_dir.patch causing FTBFS in gspell
** Changed in: at-spi2-core (Ubuntu) Importance: Undecided => Low ** Changed in: at-spi2-core (Ubuntu) Assignee: (unassigned) => Sebastien Bacher (seb128) ** Changed in: at-spi2-core (Ubuntu) Importance: Low => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1960458 Title: patch git_socket_dir.patch causing FTBFS in gspell Status in at-spi2-core package in Ubuntu: New Bug description: With this patch applied gspell is FTBFS with the following errors: Bail out! dbind-FATAL-WARNING: Couldn't connect to accessibility bus: Failed to connect to socket debian/home/.cache/at-spi/bus: No such file or directory I removed the patch and rebuilt this package in a PPA. When built against this PPA, gpsell is able to build again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1960458/+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 1960387] Re: fprintd crashed with SIGSEGV in log_v() from usbi_log() from libusb_unref_device()
** Bug watch added: github.com/libusb/libusb/issues #1079 https://github.com/libusb/libusb/issues/1079 ** Also affects: libfprint via https://github.com/libusb/libusb/issues/1079 Importance: Unknown Status: Unknown ** Project changed: libfprint => libusb ** Changed in: fprintd (Ubuntu) Status: Confirmed => Won't Fix ** Also affects: libusb (Ubuntu) Importance: Undecided Status: New ** Changed in: libusb (Ubuntu) Importance: Undecided => High ** Changed in: libusb (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libusb in Ubuntu. https://bugs.launchpad.net/bugs/1960387 Title: fprintd crashed with SIGSEGV in log_v() from usbi_log() from libusb_unref_device() Status in libusb: Unknown Status in fprintd package in Ubuntu: Won't Fix Status in libusb package in Ubuntu: Confirmed Bug description: + ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: fprintd 1.94.1-1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Feb 7 21:58:32 2022 ExecutablePath: /usr/libexec/fprintd InstallationDate: Installed on 2021-12-21 (50 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcCmdline: /usr/libexec/fprintd ProcEnviron: LANG=ru_RU.UTF-8 PATH=(custom, no user) SegvAnalysis: Segfault happened at: 0x7fd8a7a3855f:call *%rax PC (0x7fd8a7a3855f) ok source "*%rax" (0xd86d54af5d1db0f9) not located in a known VMA region (needed readable region)! destination "(%rsp)" (0x7ffdceacc590) ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: fprintd StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libusb-1.0.so.0 ?? () from /lib/x86_64-linux-gnu/libusb-1.0.so.0 libusb_unref_device () from /lib/x86_64-linux-gnu/libusb-1.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgusb.so.2 g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: fprintd crashed with SIGSEGV in libusb_unref_device() UpgradeStatus: Upgraded to jammy on 2022-01-16 (23 days ago) UserGroups: N/A separator: To manage notifications about this bug go to: https://bugs.launchpad.net/libusb/+bug/1960387/+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 1961805] [NEW] Please merge procps 2:3.3.17-6 (main) from Debian unstable (main)
Public bug reported: This requires a merge because there are changes in the Ubuntu version not present in the Debian version. ** Affects: procps (Ubuntu) Importance: Undecided Assignee: Nick Rosbrook (enr0n) Status: In Progress ** Changed in: procps (Ubuntu) Assignee: (unassigned) => Nick Rosbrook (enr0n) ** Changed in: procps (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1961805 Title: Please merge procps 2:3.3.17-6 (main) from Debian unstable (main) Status in procps package in Ubuntu: In Progress Bug description: This requires a merge because there are changes in the Ubuntu version not present in the Debian version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1961805/+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 1961800] Re: Seeing out of memory errors after upgrade to 2.2.5-3ubuntu0.4
I was able to workaround the issue by downgrading to the release version of the package: $ sudo apt-get install libexpat1=2.2.5-3 libexpat1-dev=2.2.5-3 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to expat in Ubuntu. https://bugs.launchpad.net/bugs/1961800 Title: Seeing out of memory errors after upgrade to 2.2.5-3ubuntu0.4 Status in expat package in Ubuntu: New Bug description: I started seeing errors parsing XML files today (Feb 22, 2022) after my system was updated to 2.2.5-3ubuntu0.4. This is on a bionic server. The parsing is being done by python3's xmltodict module, which uses python3 expat as the actual parser. This is the error it raises: xml.parsers.expat.ExpatError: out of memory: line 1, column 0 So far this is happening on multiple xml files, although they all come from the same source (these are jenkins config.xml files). I'm working on coming up with a minimal test case which I'll provide once I have it cleaned up of any private data. [System info] $ lsb_release -rd Description:Ubuntu 18.04.6 LTS Release:18.04 $ apt-cache policy libexpat1 libexpat1: Installed: 2.2.5-3ubuntu0.4 Candidate: 2.2.5-3ubuntu0.4 Version table: *** 2.2.5-3ubuntu0.4 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 2.2.5-3 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/expat/+bug/1961800/+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 1961418] Re: snap failed to run with '/usr/bin/snap wait system seed.loaded'
@gsunipipeline it looks like systemd does not operate correctly in your
system. This is a prerequisite for even accessing the snapd daemon,
since we rely on systemd to provide the socket, then activate snapd
daemon, and the snapd daemon directly interacts with systemd to set up
snaps.
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1961418
Title:
snap failed to run with '/usr/bin/snap wait system seed.loaded'
Status in snapd package in Ubuntu:
Incomplete
Status in systemd package in Ubuntu:
New
Bug description:
I tried to enable livepatch without any success. ([Bug 1960689] )
support suggested me report a bug for snapd.
root@plis231v:~# sudo ua enable livepatch
One moment, checking your subscription first
Unexpected error(s) occurred.
For more details, see the log: /var/log/ubuntu-advantage.log
To file a bug run: ubuntu-bug ubuntu-advantage-tools
>> logs
22-02-11 22:27:00,410 - util.py:(429) [DEBUG]: Reading file:
/var/lib/ubuntu-advantage/notices.json
2022-02-11 22:27:00,410 - util.py:(700) [DEBUG]: Writing file:
/var/lib/ubuntu-advantage/notices.json
2022-02-11 22:27:00,411 - cli.py:(1499) [ERROR]: Unhandled exception,
please file a bug
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 1458, in
wrapper
return func(*args, **kwargs)
File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 1544, in main
return args.action(args, cfg=cfg)
File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 166, in new_f
return f(*args, **kwargs)
File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 189, in new_f
return f(args, cfg=cfg, **kwargs)
File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 147, in new_f
retval = f(*args, cfg=cfg, **kwargs)
File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 888, in
action_enable
ent_ret, reason = entitlement.enable()
File "/usr/lib/python3/dist-packages/uaclient/entitlements/base.py", line
197, in enable
ret = self._perform_enable(silent=silent)
File "/usr/lib/python3/dist-packages/uaclient/entitlements/livepatch.py",
line 160, in _perform_ena
[snap.SNAP_CMD, "wait", "system", "seed.loaded"], capture=True
File "/usr/lib/python3/dist-packages/uaclient/util.py", line 662, in subp
out, err = _subp(args, rcs, capture, timeout, env=env)
File "/usr/lib/python3/dist-packages/uaclient/util.py", line 619, in _subp
stderr=err.decode("utf-8"),
uaclient.util.ProcessExecutionError: Failed running command '/usr/bin/snap
wait system seed.loaded' [sage: error: cannot communicate with server: Get
http://localhost/v2/snaps/system/conf?keys=seed.load /run/snapd.socket:
connect: no such file or directory
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubuntu-advantage-tools 27.4.1~16.04.1
ProcVersionSignature: Ubuntu 4.15.0-167.175~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-167-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.30+esm3
Architecture: amd64
Date: Fri Feb 11 23:01:08 2022
InstallationDate: Installed on 2010-12-02 (4089 days ago)
InstallationMedia: Ubuntu-Server 10.04.1 LTS "Lucid Lynx" - Release amd64
(20100816.2)
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: ubuntu-advantage-tools
UpgradeStatus: Upgraded to xenial on 2017-01-21 (1847 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1961418/+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 1961800] Re: Seeing out of memory errors after upgrade to 2.2.5-3ubuntu0.4
Attached is an example config file and python script which demonstrates the parsing error. This was reproduced on focal with: $ apt-cache policy libexpat1 libexpat1: Installed: 2.2.9-1ubuntu0.2 Candidate: 2.2.9-1ubuntu0.2 Version table: *** 2.2.9-1ubuntu0.2 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 2.2.9-1build1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages This example worked with 2.2.9-1build1 but not 2.2.9-1ubuntu0.2. To run the example: $ ./parser_example.py ./sample-config.xml The sample-config.xml was generated by jenkins (version 2.303.2) of a freestyle project with only the job name and description set. ** Attachment added: "sample-config-and-parser.tgz" https://bugs.launchpad.net/ubuntu/+source/expat/+bug/1961800/+attachment/5562745/+files/sample-config-and-parser.tgz ** Summary changed: - Seeing out of memory errors after upgrade to 2.2.5-3ubuntu0.4 + Seeing out of memory errors after upgrade to 2.2.5-3ubuntu0.4 (bionic) or 2.2.9-1ubuntu0.2 (focal) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to expat in Ubuntu. https://bugs.launchpad.net/bugs/1961800 Title: Seeing out of memory errors after upgrade to 2.2.5-3ubuntu0.4 (bionic) or 2.2.9-1ubuntu0.2 (focal) Status in expat package in Ubuntu: New Bug description: I started seeing errors parsing XML files today (Feb 22, 2022) after my system was updated to 2.2.5-3ubuntu0.4. This is on a bionic server. The parsing is being done by python3's xmltodict module, which uses python3 expat as the actual parser. This is the error it raises: xml.parsers.expat.ExpatError: out of memory: line 1, column 0 So far this is happening on multiple xml files, although they all come from the same source (these are jenkins config.xml files). I'm working on coming up with a minimal test case which I'll provide once I have it cleaned up of any private data. [System info] $ lsb_release -rd Description:Ubuntu 18.04.6 LTS Release:18.04 $ apt-cache policy libexpat1 libexpat1: Installed: 2.2.5-3ubuntu0.4 Candidate: 2.2.5-3ubuntu0.4 Version table: *** 2.2.5-3ubuntu0.4 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 2.2.5-3 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/expat/+bug/1961800/+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 1961418] Re: snap failed to run with '/usr/bin/snap wait system seed.loaded'
any suggestion to fix this?
I had tried below command.
root@plis231v:~# sudo dpkg -l | grep systemd
ii libpam-systemd:amd64 229-4ubuntu21.31+esm1
amd64system and service manager - PAM mod
ii libsystemd0:amd64 229-4ubuntu21.31+esm1
amd64systemd utility library
ii python3-systemd231-2build1
amd64Python 3 bindings for systemd
ii systemd229-4ubuntu21.31+esm1
amd64system and service manager
rc systemd-services 204-5ubuntu20.31
amd64systemd runtime services
ii systemd-shim 9-1bzr4ubuntu1
amd64shim for systemd
root@plis231v:~#
root@plis231v:~#
root@plis231v:~#
root@plis231v:~# apt-get install --reinstall systemd
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
Need to get 0 B/3,659 kB of archives.
After this operation, 0 B of additional disk space will be used.
(Reading database ... 77423 files and directories currently installed.)
Preparing to unpack .../systemd_229-4ubuntu21.31+esm1_amd64.deb ...
Unpacking systemd (229-4ubuntu21.31+esm1) over (229-4ubuntu21.31+esm1) ...
Processing triggers for man-db (2.7.5-1) ...
Processing triggers for dbus (1.10.6-1ubuntu3.6+esm1) ...
Processing triggers for ureadahead (0.100.0-19.1) ...
ureadahead will be reprofiled on next reboot
Setting up systemd (229-4ubuntu21.31+esm1) ...
addgroup: The group `systemd-journal' already exists as a system group. Exiting.
Operation failed: No such file or directory
[/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
root@plis231v:~# systemctl status
Failed to read server status: Invalid argument
root@plis231v:~#
root@plis231v:~#
--
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/1961418
Title:
snap failed to run with '/usr/bin/snap wait system seed.loaded'
Status in snapd package in Ubuntu:
Incomplete
Status in systemd package in Ubuntu:
New
Bug description:
I tried to enable livepatch without any success. ([Bug 1960689] )
support suggested me report a bug for snapd.
root@plis231v:~# sudo ua enable livepatch
One moment, checking your subscription first
Unexpected error(s) occurred.
For more details, see the log: /var/log/ubuntu-advantage.log
To file a bug run: ubuntu-bug ubuntu-advantage-tools
>> logs
22-02-11 22:27:00,410 - util.py:(429) [DEBUG]: Reading file:
/var/lib/ubuntu-advantage/notices.json
2022-02-11 22:27:00,410 - util.py:(700) [DEBUG]: Writing file:
/var/lib/ubuntu-advantage/notices.json
2022-02-11 22:27:00,411 - cli.py:(1499) [ERROR]: Unhandled exception,
please file a bug
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 1458, in
wrapper
return func(*args, **kwargs)
File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 1544, in main
return args.action(args, cfg=cfg)
File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 166, in new_f
return f(*args, **kwargs)
File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 189, in new_f
return f(args, cfg=cfg, **kwargs)
File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 147, in new_f
retval = f(*args, cfg=cfg, **kwargs)
File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 888, in
action_enable
ent_ret, reason = entitlement.enable()
File "/usr/lib/python3/dist-packages/uaclient/entitlements/base.py", line
197, in enable
ret = self._perform_enable(silent=silent)
File "/usr/lib/python3/dist-packages/uaclient/entitlements/livepatch.py",
line 160, in _perform_ena
[snap.SNAP_CMD, "wait", "system", "seed.loaded"], capture=True
File "/usr/lib/python3/dist-packages/uaclient/util.py", line 662, in subp
out, err = _subp(args, rcs, capture, timeout, env=env)
File "/usr/lib/python3/dist-packages/uaclient/util.py", line 619, in _subp
stderr=err.decode("utf-8"),
uaclient.util.ProcessExecutionError: Failed running command '/usr/bin/snap
wait system seed.loaded' [sage: error: cannot communicate with server: Get
http://localhost/v2/snaps/system/conf?keys=seed.load /run/snapd.socket:
connect: no such file or directory
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubuntu-advantage-tools 27.4.1~16.04.1
ProcVersionSignature: Ubuntu 4.15.0-167.175~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-167-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.
[Touch-packages] [Bug 1960387] Re: fprintd crashed with SIGSEGV in log_v() from usbi_log() from libusb_unref_device()
** Changed in: libusb Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libusb in Ubuntu. https://bugs.launchpad.net/bugs/1960387 Title: fprintd crashed with SIGSEGV in log_v() from usbi_log() from libusb_unref_device() Status in libusb: New Status in fprintd package in Ubuntu: Won't Fix Status in libusb package in Ubuntu: Confirmed Bug description: + ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: fprintd 1.94.1-1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Feb 7 21:58:32 2022 ExecutablePath: /usr/libexec/fprintd InstallationDate: Installed on 2021-12-21 (50 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcCmdline: /usr/libexec/fprintd ProcEnviron: LANG=ru_RU.UTF-8 PATH=(custom, no user) SegvAnalysis: Segfault happened at: 0x7fd8a7a3855f:call *%rax PC (0x7fd8a7a3855f) ok source "*%rax" (0xd86d54af5d1db0f9) not located in a known VMA region (needed readable region)! destination "(%rsp)" (0x7ffdceacc590) ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: fprintd StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libusb-1.0.so.0 ?? () from /lib/x86_64-linux-gnu/libusb-1.0.so.0 libusb_unref_device () from /lib/x86_64-linux-gnu/libusb-1.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgusb.so.2 g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: fprintd crashed with SIGSEGV in libusb_unref_device() UpgradeStatus: Upgraded to jammy on 2022-01-16 (23 days ago) UserGroups: N/A separator: To manage notifications about this bug go to: https://bugs.launchpad.net/libusb/+bug/1960387/+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 1961418] Re: snap failed to run with '/usr/bin/snap wait system seed.loaded'
What is the output of these commands:
ps -o cmd fp 1
sudo ls -lah /proc/1/exe
cat /proc/cmdline
--
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/1961418
Title:
snap failed to run with '/usr/bin/snap wait system seed.loaded'
Status in snapd package in Ubuntu:
Incomplete
Status in systemd package in Ubuntu:
New
Bug description:
I tried to enable livepatch without any success. ([Bug 1960689] )
support suggested me report a bug for snapd.
root@plis231v:~# sudo ua enable livepatch
One moment, checking your subscription first
Unexpected error(s) occurred.
For more details, see the log: /var/log/ubuntu-advantage.log
To file a bug run: ubuntu-bug ubuntu-advantage-tools
>> logs
22-02-11 22:27:00,410 - util.py:(429) [DEBUG]: Reading file:
/var/lib/ubuntu-advantage/notices.json
2022-02-11 22:27:00,410 - util.py:(700) [DEBUG]: Writing file:
/var/lib/ubuntu-advantage/notices.json
2022-02-11 22:27:00,411 - cli.py:(1499) [ERROR]: Unhandled exception,
please file a bug
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 1458, in
wrapper
return func(*args, **kwargs)
File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 1544, in main
return args.action(args, cfg=cfg)
File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 166, in new_f
return f(*args, **kwargs)
File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 189, in new_f
return f(args, cfg=cfg, **kwargs)
File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 147, in new_f
retval = f(*args, cfg=cfg, **kwargs)
File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 888, in
action_enable
ent_ret, reason = entitlement.enable()
File "/usr/lib/python3/dist-packages/uaclient/entitlements/base.py", line
197, in enable
ret = self._perform_enable(silent=silent)
File "/usr/lib/python3/dist-packages/uaclient/entitlements/livepatch.py",
line 160, in _perform_ena
[snap.SNAP_CMD, "wait", "system", "seed.loaded"], capture=True
File "/usr/lib/python3/dist-packages/uaclient/util.py", line 662, in subp
out, err = _subp(args, rcs, capture, timeout, env=env)
File "/usr/lib/python3/dist-packages/uaclient/util.py", line 619, in _subp
stderr=err.decode("utf-8"),
uaclient.util.ProcessExecutionError: Failed running command '/usr/bin/snap
wait system seed.loaded' [sage: error: cannot communicate with server: Get
http://localhost/v2/snaps/system/conf?keys=seed.load /run/snapd.socket:
connect: no such file or directory
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubuntu-advantage-tools 27.4.1~16.04.1
ProcVersionSignature: Ubuntu 4.15.0-167.175~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-167-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.30+esm3
Architecture: amd64
Date: Fri Feb 11 23:01:08 2022
InstallationDate: Installed on 2010-12-02 (4089 days ago)
InstallationMedia: Ubuntu-Server 10.04.1 LTS "Lucid Lynx" - Release amd64
(20100816.2)
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: ubuntu-advantage-tools
UpgradeStatus: Upgraded to xenial on 2017-01-21 (1847 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1961418/+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 1961800] Re: Seeing out of memory errors after upgrade to 2.2.5-3ubuntu0.4 (bionic) or 2.2.9-1ubuntu0.2 (focal)
This may be an issue with the python3 xmltodict module. Further testing indicates that parsing a file with just xml.parsers.expat is working just fine. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to expat in Ubuntu. https://bugs.launchpad.net/bugs/1961800 Title: Seeing out of memory errors after upgrade to 2.2.5-3ubuntu0.4 (bionic) or 2.2.9-1ubuntu0.2 (focal) Status in expat package in Ubuntu: New Bug description: I started seeing errors parsing XML files today (Feb 22, 2022) after my system was updated to 2.2.5-3ubuntu0.4. This is on a bionic server. The parsing is being done by python3's xmltodict module, which uses python3 expat as the actual parser. This is the error it raises: xml.parsers.expat.ExpatError: out of memory: line 1, column 0 So far this is happening on multiple xml files, although they all come from the same source (these are jenkins config.xml files). I'm working on coming up with a minimal test case which I'll provide once I have it cleaned up of any private data. [System info] $ lsb_release -rd Description:Ubuntu 18.04.6 LTS Release:18.04 $ apt-cache policy libexpat1 libexpat1: Installed: 2.2.5-3ubuntu0.4 Candidate: 2.2.5-3ubuntu0.4 Version table: *** 2.2.5-3ubuntu0.4 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 2.2.5-3 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/expat/+bug/1961800/+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 1961418] Re: snap failed to run with '/usr/bin/snap wait system seed.loaded'
root@plis231v:~# ps -o cmd fp 1
CMD
/sbin/init
root@plis231v:~# sudo ls -lah /proc/1/exe
lrwxrwxrwx 1 root root 0 Feb 11 22:51 /proc/1/exe -> /sbin/upstart
root@plis231v:~# cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-4.15.0-167-generic root=/dev/mapper/plis231v-root ro quiet
root@plis231v:~#
--
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/1961418
Title:
snap failed to run with '/usr/bin/snap wait system seed.loaded'
Status in snapd package in Ubuntu:
Incomplete
Status in systemd package in Ubuntu:
New
Bug description:
I tried to enable livepatch without any success. ([Bug 1960689] )
support suggested me report a bug for snapd.
root@plis231v:~# sudo ua enable livepatch
One moment, checking your subscription first
Unexpected error(s) occurred.
For more details, see the log: /var/log/ubuntu-advantage.log
To file a bug run: ubuntu-bug ubuntu-advantage-tools
>> logs
22-02-11 22:27:00,410 - util.py:(429) [DEBUG]: Reading file:
/var/lib/ubuntu-advantage/notices.json
2022-02-11 22:27:00,410 - util.py:(700) [DEBUG]: Writing file:
/var/lib/ubuntu-advantage/notices.json
2022-02-11 22:27:00,411 - cli.py:(1499) [ERROR]: Unhandled exception,
please file a bug
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 1458, in
wrapper
return func(*args, **kwargs)
File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 1544, in main
return args.action(args, cfg=cfg)
File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 166, in new_f
return f(*args, **kwargs)
File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 189, in new_f
return f(args, cfg=cfg, **kwargs)
File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 147, in new_f
retval = f(*args, cfg=cfg, **kwargs)
File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 888, in
action_enable
ent_ret, reason = entitlement.enable()
File "/usr/lib/python3/dist-packages/uaclient/entitlements/base.py", line
197, in enable
ret = self._perform_enable(silent=silent)
File "/usr/lib/python3/dist-packages/uaclient/entitlements/livepatch.py",
line 160, in _perform_ena
[snap.SNAP_CMD, "wait", "system", "seed.loaded"], capture=True
File "/usr/lib/python3/dist-packages/uaclient/util.py", line 662, in subp
out, err = _subp(args, rcs, capture, timeout, env=env)
File "/usr/lib/python3/dist-packages/uaclient/util.py", line 619, in _subp
stderr=err.decode("utf-8"),
uaclient.util.ProcessExecutionError: Failed running command '/usr/bin/snap
wait system seed.loaded' [sage: error: cannot communicate with server: Get
http://localhost/v2/snaps/system/conf?keys=seed.load /run/snapd.socket:
connect: no such file or directory
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubuntu-advantage-tools 27.4.1~16.04.1
ProcVersionSignature: Ubuntu 4.15.0-167.175~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-167-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.30+esm3
Architecture: amd64
Date: Fri Feb 11 23:01:08 2022
InstallationDate: Installed on 2010-12-02 (4089 days ago)
InstallationMedia: Ubuntu-Server 10.04.1 LTS "Lucid Lynx" - Release amd64
(20100816.2)
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: ubuntu-advantage-tools
UpgradeStatus: Upgraded to xenial on 2017-01-21 (1847 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1961418/+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 1961805] Re: Please merge procps 2:3.3.17-6 (main) from Debian unstable (main)
** Patch added: "Diff from Ubuntu 3.3.17-5ubuntu3" https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1961805/+attachment/5562752/+files/procps-3.3.17-5ubuntu3-to-3.3.17-6ubuntu1.debdiff ** Description changed: This requires a merge because there are changes in the Ubuntu version not present in the Debian version. + + Dropped changes: + - debian/README.sysctl: Debian has added this information. + - debian/procps.install: debian/protect-links.conf has been re-named to debian/99-protect-links.conf, so it can be safely installed again (see LP: #1938585 for background). ** Changed in: procps (Ubuntu) Status: In Progress => Confirmed ** Changed in: procps (Ubuntu) Assignee: Nick Rosbrook (enr0n) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1961805 Title: Please merge procps 2:3.3.17-6 (main) from Debian unstable (main) Status in procps package in Ubuntu: Confirmed Bug description: This requires a merge because there are changes in the Ubuntu version not present in the Debian version. Dropped changes: - debian/README.sysctl: Debian has added this information. - debian/procps.install: debian/protect-links.conf has been re-named to debian/99-protect-links.conf, so it can be safely installed again (see LP: #1938585 for background). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1961805/+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 1961805] Re: Please merge procps 2:3.3.17-6 (main) from Debian unstable (main)
** Patch added: "Diff from Debian" https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1961805/+attachment/5562751/+files/procps-3.3.17-6-to-3.3.17-6ubuntu1.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1961805 Title: Please merge procps 2:3.3.17-6 (main) from Debian unstable (main) Status in procps package in Ubuntu: Confirmed Bug description: This requires a merge because there are changes in the Ubuntu version not present in the Debian version. Dropped changes: - debian/README.sysctl: Debian has added this information. - debian/procps.install: debian/protect-links.conf has been re-named to debian/99-protect-links.conf, so it can be safely installed again (see LP: #1938585 for background). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1961805/+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 1961800] Re: Seeing out of memory errors after upgrade to 2.2.5-3ubuntu0.4 (bionic) or 2.2.9-1ubuntu0.2 (focal)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: expat (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to expat in Ubuntu. https://bugs.launchpad.net/bugs/1961800 Title: Seeing out of memory errors after upgrade to 2.2.5-3ubuntu0.4 (bionic) or 2.2.9-1ubuntu0.2 (focal) Status in expat package in Ubuntu: Confirmed Status in python-xmltodict package in Ubuntu: New Bug description: I started seeing errors parsing XML files today (Feb 22, 2022) after my system was updated to 2.2.5-3ubuntu0.4. This is on a bionic server. The parsing is being done by python3's xmltodict module, which uses python3 expat as the actual parser. This is the error it raises: xml.parsers.expat.ExpatError: out of memory: line 1, column 0 So far this is happening on multiple xml files, although they all come from the same source (these are jenkins config.xml files). I'm working on coming up with a minimal test case which I'll provide once I have it cleaned up of any private data. [System info] $ lsb_release -rd Description:Ubuntu 18.04.6 LTS Release:18.04 $ apt-cache policy libexpat1 libexpat1: Installed: 2.2.5-3ubuntu0.4 Candidate: 2.2.5-3ubuntu0.4 Version table: *** 2.2.5-3ubuntu0.4 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 2.2.5-3 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/expat/+bug/1961800/+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 1961418] Re: snap failed to run with '/usr/bin/snap wait system seed.loaded'
So indeed your system is still using upstart, in order to use snapd you
will need to switch your system over to use systemd instead. Likely one
of the upgrade scripts from 10.04 to 16.04 did not transition from
upstart to systemd the way a fresh install of 16.04 would default to.
** Changed in: snapd (Ubuntu)
Status: Incomplete => Won't Fix
--
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/1961418
Title:
snap failed to run with '/usr/bin/snap wait system seed.loaded'
Status in snapd package in Ubuntu:
Won't Fix
Status in systemd package in Ubuntu:
New
Bug description:
I tried to enable livepatch without any success. ([Bug 1960689] )
support suggested me report a bug for snapd.
root@plis231v:~# sudo ua enable livepatch
One moment, checking your subscription first
Unexpected error(s) occurred.
For more details, see the log: /var/log/ubuntu-advantage.log
To file a bug run: ubuntu-bug ubuntu-advantage-tools
>> logs
22-02-11 22:27:00,410 - util.py:(429) [DEBUG]: Reading file:
/var/lib/ubuntu-advantage/notices.json
2022-02-11 22:27:00,410 - util.py:(700) [DEBUG]: Writing file:
/var/lib/ubuntu-advantage/notices.json
2022-02-11 22:27:00,411 - cli.py:(1499) [ERROR]: Unhandled exception,
please file a bug
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 1458, in
wrapper
return func(*args, **kwargs)
File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 1544, in main
return args.action(args, cfg=cfg)
File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 166, in new_f
return f(*args, **kwargs)
File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 189, in new_f
return f(args, cfg=cfg, **kwargs)
File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 147, in new_f
retval = f(*args, cfg=cfg, **kwargs)
File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 888, in
action_enable
ent_ret, reason = entitlement.enable()
File "/usr/lib/python3/dist-packages/uaclient/entitlements/base.py", line
197, in enable
ret = self._perform_enable(silent=silent)
File "/usr/lib/python3/dist-packages/uaclient/entitlements/livepatch.py",
line 160, in _perform_ena
[snap.SNAP_CMD, "wait", "system", "seed.loaded"], capture=True
File "/usr/lib/python3/dist-packages/uaclient/util.py", line 662, in subp
out, err = _subp(args, rcs, capture, timeout, env=env)
File "/usr/lib/python3/dist-packages/uaclient/util.py", line 619, in _subp
stderr=err.decode("utf-8"),
uaclient.util.ProcessExecutionError: Failed running command '/usr/bin/snap
wait system seed.loaded' [sage: error: cannot communicate with server: Get
http://localhost/v2/snaps/system/conf?keys=seed.load /run/snapd.socket:
connect: no such file or directory
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubuntu-advantage-tools 27.4.1~16.04.1
ProcVersionSignature: Ubuntu 4.15.0-167.175~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-167-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.30+esm3
Architecture: amd64
Date: Fri Feb 11 23:01:08 2022
InstallationDate: Installed on 2010-12-02 (4089 days ago)
InstallationMedia: Ubuntu-Server 10.04.1 LTS "Lucid Lynx" - Release amd64
(20100816.2)
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: ubuntu-advantage-tools
UpgradeStatus: Upgraded to xenial on 2017-01-21 (1847 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1961418/+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 1961800] Re: Seeing out of memory errors after upgrade to 2.2.5-3ubuntu0.4 (bionic) or 2.2.9-1ubuntu0.2 (focal)
Moving this to xmltodict as I've been able to parse multiple xml files through just python3's xml.parsers.expat without error, but none of them through xmltodict. ** Also affects: python-xmltodict (Ubuntu) Importance: Undecided Status: New ** Changed in: python-xmltodict (Ubuntu) Status: New => Confirmed ** Changed in: expat (Ubuntu) Status: Confirmed => Invalid ** Summary changed: - Seeing out of memory errors after upgrade to 2.2.5-3ubuntu0.4 (bionic) or 2.2.9-1ubuntu0.2 (focal) + Seeing out of memory errors after libexpat1 upgrade to 2.2.5-3ubuntu0.4 (bionic) or 2.2.9-1ubuntu0.2 (focal) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to expat in Ubuntu. https://bugs.launchpad.net/bugs/1961800 Title: Seeing out of memory errors after libexpat1 upgrade to 2.2.5-3ubuntu0.4 (bionic) or 2.2.9-1ubuntu0.2 (focal) Status in expat package in Ubuntu: Invalid Status in python-xmltodict package in Ubuntu: Confirmed Bug description: I started seeing errors parsing XML files today (Feb 22, 2022) after my system was updated to 2.2.5-3ubuntu0.4. This is on a bionic server. The parsing is being done by python3's xmltodict module, which uses python3 expat as the actual parser. This is the error it raises: xml.parsers.expat.ExpatError: out of memory: line 1, column 0 So far this is happening on multiple xml files, although they all come from the same source (these are jenkins config.xml files). I'm working on coming up with a minimal test case which I'll provide once I have it cleaned up of any private data. [System info] $ lsb_release -rd Description:Ubuntu 18.04.6 LTS Release:18.04 $ apt-cache policy libexpat1 libexpat1: Installed: 2.2.5-3ubuntu0.4 Candidate: 2.2.5-3ubuntu0.4 Version table: *** 2.2.5-3ubuntu0.4 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 2.2.5-3 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/expat/+bug/1961800/+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 1870829] Re: AptX and AptX HD unavailable as Bluetooth audio quality options
** Changed in: pulseaudio (Debian) Status: New => Fix Committed -- 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/1870829 Title: AptX and AptX HD unavailable as Bluetooth audio quality options Status in pulseaudio package in Ubuntu: Confirmed Status in pulseaudio package in Debian: Fix Committed Bug description: Current situation: When one connects a Bluetooth audio device, at best one can choose between "Headset Head Unit (HSP/HFP)" and "High Fidelity Playback (A2DP Sink)". That is sad when the audio device supports AptX or AptX HD. Expected situation: One can select AptX or AptX HD as the Bluetooth audio output profile. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870829/+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 1960307] Re: No gstreamer dependency causes high-fidelity codecs to be missing for Bluetooth devices
** Bug watch added: Debian Bug tracker #991597 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991597 ** Also affects: pulseaudio via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991597 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1960307 Title: No gstreamer dependency causes high-fidelity codecs to be missing for Bluetooth devices Status in PulseAudio: Unknown Status in gst-plugins-bad1.0 package in Ubuntu: Confirmed Status in gstreamer1.0 package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After the announcements of PulseAudio 15 and Gstreamer 1.20, which both advertised LDAC and AptX (HD) support, I expected that jammy (22.04) would support those codecs. Though in reality it seems that something is missing, gstreamer reports that those codecs are supported but "pactl [...] list-codec" only lists sbc (and variants). Checking here https://packages.ubuntu.com/jammy/pulseaudio-module- bluetooth it seems that PulseAudio is not built with gstreamer support, is that the current blocker? To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1960307/+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 1961823] [NEW] Bluetooth button off and doesn't work
Public bug reported: Bluetooth button off and doesn't work the massage that show me when i open the setting " No Bluetooth Found plug in a dongle to use Bluetooth " ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth 5.53-0ubuntu3.5 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Feb 22 21:08:36 2022 InstallationDate: Installed on 2022-02-17 (4 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) InterestingModules: bnep bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 05c8:03d2 Cheng Uei Precision Industry Co., Ltd (Foxlink) HP TrueVision HD Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 5: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 5: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M MachineType: HP HP Laptop 15-da1xxx PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic root=UUID=616f1e34-70a5-4b45-82ae-a86b7f795ab2 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2021 dmi.bios.release: 15.38 dmi.bios.vendor: Insyde dmi.bios.version: F.38 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8533 dmi.board.vendor: HP dmi.board.version: 70.38 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 70.38 dmi.modalias: dmi:bvnInsyde:bvrF.38:bd08/31/2021:br15.38:efr70.38:svnHP:pnHPLaptop15-da1xxx:pvrType1ProductConfigId:rvnHP:rn8533:rvr70.38:cvnHP:ct10:cvrChassisVersion:sku6EX79EA#A2N: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-da1xxx dmi.product.sku: 6EX79EA#A2N dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP hciconfig: rfkill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1961823 Title: Bluetooth button off and doesn't work Status in bluez package in Ubuntu: New Bug description: Bluetooth button off and doesn't work the massage that show me when i open the setting " No Bluetooth Found plug in a dongle to use Bluetooth " ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth 5.53-0ubuntu3.5 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Feb 22 21:08:36 2022 InstallationDate: Installed on 2022-02-17 (4 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) InterestingModules: bnep bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 05c8:03d2 Cheng Uei Precision Industry Co., Ltd (Foxlink) HP TrueVision HD Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 5: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 5: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M MachineType: HP HP Laptop 15-da1xxx PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic root=UUID=616f1e34-70a5-4b45-82ae-a86b7f795ab2 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2021 dmi.bios.release: 15.38 dmi.bios.vendor: Insyde dmi.bios.version: F.38 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8533 dmi.board.vendor: HP dmi.board.version: 70.38 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 70.38 dmi.modalias: dmi:bvnInsyde:bvrF.38:bd08/31/2021:br15.38:efr70.38:svnHP:pnHPLaptop15-da1xxx:pvrType1ProductConfigId:rvnHP:rn8533:rvr70.38:cvnHP:ct10:cvrChassisVersion:sku6EX79EA#A2N: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-da1xxx dmi.product.sku: 6EX79EA#A2N dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP hciconfig: rfkill: 0: phy0: Wireless LAN S
[Touch-packages] [Bug 1960307] Re: No gstreamer dependency causes high-fidelity codecs to be missing for Bluetooth devices
** Changed in: pulseaudio Status: Unknown => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1960307 Title: No gstreamer dependency causes high-fidelity codecs to be missing for Bluetooth devices Status in PulseAudio: Fix Committed Status in gst-plugins-bad1.0 package in Ubuntu: Confirmed Status in gstreamer1.0 package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After the announcements of PulseAudio 15 and Gstreamer 1.20, which both advertised LDAC and AptX (HD) support, I expected that jammy (22.04) would support those codecs. Though in reality it seems that something is missing, gstreamer reports that those codecs are supported but "pactl [...] list-codec" only lists sbc (and variants). Checking here https://packages.ubuntu.com/jammy/pulseaudio-module- bluetooth it seems that PulseAudio is not built with gstreamer support, is that the current blocker? To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1960307/+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 1961484] Re: 20.04.3: libva2 fails under Wayland (wl_drm@22: error 0: authenticate failed)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libva (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libva in Ubuntu. https://bugs.launchpad.net/bugs/1961484 Title: 20.04.3: libva2 fails under Wayland (wl_drm@22: error 0: authenticate failed) Status in libva package in Ubuntu: Confirmed Bug description: In current 20.04.3 libva2 fails to authenticate connection to Wayland composer. This may be related to update of Mesa to 21.2.6. Any program using libva2 fails with bor@bor-Latitude-E5450:~$ vainfo wl_drm@7: error 0: authenticate failed VA error: wayland: Wayland roundtrip error: Protocol error (errno 71) libva info: VA-API version 1.7.0 libva error: vaGetDriverNameByIndex() failed with invalid VADisplay, driver_name = (null) vaInitialize failed with error code 3 (invalid VADisplay),exit bor@bor-Latitude-E5450:~$ This is fixed in libva upstream in pull request https://github.com/intel/libva/pull/476 I verified that upstream libva correctly works: bor@bor-Latitude-E5450:~/src/intel/libva-utils$ ./vainfo/vainfo libva info: VA-API version 1.15.0 libva info: Trying to open /home/bor/pkg/lib/dri/iHD_drv_video.so libva info: va_openDriver() returns -1 libva info: Trying to open /home/bor/pkg/lib/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_6 libva info: va_openDriver() returns 0 vainfo: VA-API version: 1.15 (libva 2.15.0.pre1) vainfo: Driver version: Intel i965 driver for Intel(R) Broadwell - 2.4.0 vainfo: Supported profile and entrypoints VAProfileMPEG2Simple : VAEntrypointVLD VAProfileMPEG2Simple : VAEntrypointEncSlice VAProfileMPEG2Main : VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointEncSlice VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileH264MultiviewHigh : VAEntrypointVLD VAProfileH264MultiviewHigh : VAEntrypointEncSlice VAProfileH264StereoHigh : VAEntrypointVLD VAProfileH264StereoHigh : VAEntrypointEncSlice VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main : VAEntrypointVLD VAProfileVC1Advanced : VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc VAProfileJPEGBaseline : VAEntrypointVLD VAProfileVP8Version0_3 : VAEntrypointVLD bor@bor-Latitude-E5450:~/src/intel/libva-utils$ With *only* commit 283f776a9649dcef58b47958c1269499adfa1cd4 reverted bor@bor-Latitude-E5450:~/src/intel/libva-utils$ ./vainfo/vainfo wl_drm@7: error 0: authenticate failed VA error: wayland: Wayland roundtrip error: Protocol error (errno 71) libva info: VA-API version 1.15.0 libva error: vaGetDriverNameByIndex() failed with invalid VADisplay, driver_name = (null) vaInitialize failed with error code 3 (invalid VADisplay),exit bor@bor-Latitude-E5450:~/src/intel/libva-utils$ Please update libva in 20.04.3 to match Mesa. This bug affects any application that is trying to use VAAPI for hardware acceleration. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libva2 2.7.0-2 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-lowlatency 5.13.19 Uname: Linux 5.13.0-30-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Feb 19 19:16:15 2022 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2015-07-02 (2424 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: libva UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libva/+bug/1961484/+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 1945225] Re: udev produces unpredictable net names when PCI device is a bridge
So with regards to MAAS, if you wish to apply the link file, I'd second adding a commissioning script that writes the file and executes early enough in the commissioning process (scripts execute in the order of their names, i.e 40-my-script will execute before 50-my-other-script). You can then also select whether to apply this to all machines or specific machines. Alternatively, you can add custom preseed configuration (https://maas.io/docs/snap/3.1/ui/how-to-customise- machines#heading--about-pre-seeding) to write the link file as well, this way you can explicitly control when the file is written and it'll write the file for all commissions. Though the kernel parameter option is probably the simplest one from a MAAS perspective. -- 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/1945225 Title: udev produces unpredictable net names when PCI device is a bridge Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: In Progress Status in systemd source package in Hirsute: Fix Released Status in systemd source package in Impish: Fix Released Bug description: [Impact] udev can produce unpredictable network interface names by default when multiple devices map to the same slot due to an intermediate bridge. On an Nvidia DGX2 system, I see the following when booting a system with udev 245.4-4ubuntu3.13: ubuntu@akis:~$ ls /sys/class/net enp134s0f0 enp6s0 ens103 ens107 eth3 eth9 enp134s0f1 ens102 ens106 eth1eth7 lo For each ens* device, there is a sibling eth* device that maps to the same slot because both devices are behind the same bridge. Unpredictable names present well known problems, but I'll describe a specific issue I'm having. We currently do automated network testing that MAAS deploys a system and then configures 2 specific NICs on the system. While MAAS does take care to always restore the names used during commissioning (eth3 will always be the same NIC on every deploy), these names can change each time the system is commissioned. So today we need to go in and edit the NIC names manually in MAAS any time the system is re-commissioned. [Test Case] Boot with kernel option net.naming-scheme=v247; verify that all network interfaces receive predictable names. [Fix] This issue was addressed upstream by adding a new v247 naming scheme that detects this scenario and disables usage of slot-based names for these devices. Obviously changing the default naming scheme in a released LTS series could break users. However, we could introduce the v247 scheme in a focal SRU, and keep the default scheme of v245 (via -Ddefault-net-naming-scheme=v245). Users impacted by this could then opt-in to the v247 scheme by passing net.naming-scheme=v247 or net.naming-scheme=latest on the kernel command line. I could add this to DGX2 systems via a kernel_opts MAAS tag to always get predictable names during commissioning. [Regression Risk] This would change the behavior of any users who select net.naming-scheme=latest, since the latest will now be v247 and not v245. I'm not sure why an existing Ubuntu user would be doing that though - AFAICT, Ubuntu currently always defaults to the latest scheme. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1945225/+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 1961833] [NEW] openssh 8.8 breaks login to Canonical servers
Public bug reported: With 8.7p1-4 connecting to wendigo debug1: Next authentication method: publickey debug1: Offering public key: /home/jak/.ssh/id_rsa RSA SHA256:Dj1/l9g5RH00/wO7puC1WVxgpvmhmaQg3wEETwmOFPk agent debug1: Server accepts key: /home/jak/.ssh/id_rsa RSA SHA256:Dj1/l9g5RH00/wO7puC1WVxgpvmhmaQg3wEETwmOFPk agent With 8.8p1-1 debug1: Offering public key: /home/jak/.ssh/id_rsa RSA SHA256:Dj1/l9g5RH00/wO7puC1WVxgpvmhmaQg3wEETwmOFPk agent debug1: send_pubkey_test: no mutual signature algorithm Needs further investigation, but blocks people a bit right now ** Affects: openssh (Ubuntu) Importance: Undecided Status: New -- 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/1961833 Title: openssh 8.8 breaks login to Canonical servers Status in openssh package in Ubuntu: New Bug description: With 8.7p1-4 connecting to wendigo debug1: Next authentication method: publickey debug1: Offering public key: /home/jak/.ssh/id_rsa RSA SHA256:Dj1/l9g5RH00/wO7puC1WVxgpvmhmaQg3wEETwmOFPk agent debug1: Server accepts key: /home/jak/.ssh/id_rsa RSA SHA256:Dj1/l9g5RH00/wO7puC1WVxgpvmhmaQg3wEETwmOFPk agent With 8.8p1-1 debug1: Offering public key: /home/jak/.ssh/id_rsa RSA SHA256:Dj1/l9g5RH00/wO7puC1WVxgpvmhmaQg3wEETwmOFPk agent debug1: send_pubkey_test: no mutual signature algorithm Needs further investigation, but blocks people a bit right now To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1961833/+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 1961833] Re: openssh 8.8 breaks login to canonical servers
It says Incompatibility is more likely when connecting to older SSH implementations that have not been upgraded or have not closely tracked improvements in the SSH protocol. For these cases, it may be necessary to selectively re-enable RSA/SHA1 to allow connection and/or user authentication via the HostkeyAlgorithms and PubkeyAcceptedAlgorithms options. For example, the following stanza in ~/.ssh/config will enable RSA/SHA1 for host and user authentication for a single destination host: Host old-host HostkeyAlgorithms +ssh-rsa PubkeyAcceptedAlgorithms +ssh-rsa So this may be a server too old issue; and we can fix this in internal tooling. -- 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/1961833 Title: openssh 8.8 breaks login to Canonical servers Status in openssh package in Ubuntu: New Bug description: With 8.7p1-4 connecting to wendigo debug1: Next authentication method: publickey debug1: Offering public key: /home/jak/.ssh/id_rsa RSA SHA256:Dj1/l9g5RH00/wO7puC1WVxgpvmhmaQg3wEETwmOFPk agent debug1: Server accepts key: /home/jak/.ssh/id_rsa RSA SHA256:Dj1/l9g5RH00/wO7puC1WVxgpvmhmaQg3wEETwmOFPk agent With 8.8p1-1 debug1: Offering public key: /home/jak/.ssh/id_rsa RSA SHA256:Dj1/l9g5RH00/wO7puC1WVxgpvmhmaQg3wEETwmOFPk agent debug1: send_pubkey_test: no mutual signature algorithm Needs further investigation, but blocks people a bit right now To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1961833/+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 1961833] Re: openssh 8.8 breaks login to canonical servers
Question we have to ask: Is breaking support for old servers without a deprecation notice in the LTS release the best cause of action? ** Summary changed: - openssh 8.8 breaks login to canonical servers + openssh 8.8 breaks login to Canonical servers -- 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/1961833 Title: openssh 8.8 breaks login to Canonical servers Status in openssh package in Ubuntu: New Bug description: With 8.7p1-4 connecting to wendigo debug1: Next authentication method: publickey debug1: Offering public key: /home/jak/.ssh/id_rsa RSA SHA256:Dj1/l9g5RH00/wO7puC1WVxgpvmhmaQg3wEETwmOFPk agent debug1: Server accepts key: /home/jak/.ssh/id_rsa RSA SHA256:Dj1/l9g5RH00/wO7puC1WVxgpvmhmaQg3wEETwmOFPk agent With 8.8p1-1 debug1: Offering public key: /home/jak/.ssh/id_rsa RSA SHA256:Dj1/l9g5RH00/wO7puC1WVxgpvmhmaQg3wEETwmOFPk agent debug1: send_pubkey_test: no mutual signature algorithm Needs further investigation, but blocks people a bit right now To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1961833/+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 1961837] [NEW] PackageKit 1.2.5 unable to perform upgrades
Public bug reported: After being notified of upgrades available in Plasma Discover, I attempted to do an upgrade of all available packages. Unfortunately, it would not but also wouldn't show an error. I attempted to run 'pkcon update' which showed no available upgrades, whereas 'apt update' showed several packages available for upgrade. Expected behavior: 'pkcon update' would have performed the upgrade. Actual behavior: 'pkcon update' did nothing, saying no packages were available to upgrade. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: packagekit 1.2.5-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-lowlatency 5.15.12 Uname: Linux 5.15.0-18-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu77 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Tue Feb 22 11:33:52 2022 InstallationDate: Installed on 2021-03-20 (338 days ago) InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 (20210320) SourcePackage: packagekit UpgradeStatus: Upgraded to jammy on 2021-11-07 (107 days ago) ** Affects: packagekit (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1961837 Title: PackageKit 1.2.5 unable to perform upgrades Status in packagekit package in Ubuntu: New Bug description: After being notified of upgrades available in Plasma Discover, I attempted to do an upgrade of all available packages. Unfortunately, it would not but also wouldn't show an error. I attempted to run 'pkcon update' which showed no available upgrades, whereas 'apt update' showed several packages available for upgrade. Expected behavior: 'pkcon update' would have performed the upgrade. Actual behavior: 'pkcon update' did nothing, saying no packages were available to upgrade. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: packagekit 1.2.5-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-lowlatency 5.15.12 Uname: Linux 5.15.0-18-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu77 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Tue Feb 22 11:33:52 2022 InstallationDate: Installed on 2021-03-20 (338 days ago) InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 (20210320) SourcePackage: packagekit UpgradeStatus: Upgraded to jammy on 2021-11-07 (107 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1961837/+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 1961837] Re: PackageKit 1.2.5 unable to perform upgrades
Matthias, could this be a result of allowing PK to switch versions? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1961837 Title: PackageKit 1.2.5 unable to perform upgrades Status in packagekit package in Ubuntu: New Bug description: After being notified of upgrades available in Plasma Discover, I attempted to do an upgrade of all available packages. Unfortunately, it would not but also wouldn't show an error. I attempted to run 'pkcon update' which showed no available upgrades, whereas 'apt update' showed several packages available for upgrade. Expected behavior: 'pkcon update' would have performed the upgrade. Actual behavior: 'pkcon update' did nothing, saying no packages were available to upgrade. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: packagekit 1.2.5-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-lowlatency 5.15.12 Uname: Linux 5.15.0-18-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu77 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Tue Feb 22 11:33:52 2022 InstallationDate: Installed on 2021-03-20 (338 days ago) InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 (20210320) SourcePackage: packagekit UpgradeStatus: Upgraded to jammy on 2021-11-07 (107 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1961837/+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 1961837] Re: PackageKit 1.2.5 unable to perform upgrades
Julian, we've got some discussion upstream: https://github.com/PackageKit/PackageKit/issues/534 ** Bug watch added: github.com/PackageKit/PackageKit/issues #534 https://github.com/PackageKit/PackageKit/issues/534 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1961837 Title: PackageKit 1.2.5 unable to perform upgrades Status in packagekit package in Ubuntu: New Bug description: After being notified of upgrades available in Plasma Discover, I attempted to do an upgrade of all available packages. Unfortunately, it would not but also wouldn't show an error. I attempted to run 'pkcon update' which showed no available upgrades, whereas 'apt update' showed several packages available for upgrade. Expected behavior: 'pkcon update' would have performed the upgrade. Actual behavior: 'pkcon update' did nothing, saying no packages were available to upgrade. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: packagekit 1.2.5-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-lowlatency 5.15.12 Uname: Linux 5.15.0-18-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu77 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Tue Feb 22 11:33:52 2022 InstallationDate: Installed on 2021-03-20 (338 days ago) InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 (20210320) SourcePackage: packagekit UpgradeStatus: Upgraded to jammy on 2021-11-07 (107 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1961837/+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 1961833] Re: openssh 8.8 breaks login to Canonical servers
** Tags added: rls-jj-incoming -- 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/1961833 Title: openssh 8.8 breaks login to Canonical servers Status in openssh package in Ubuntu: New Bug description: With 8.7p1-4 connecting to wendigo debug1: Next authentication method: publickey debug1: Offering public key: /home/jak/.ssh/id_rsa RSA SHA256:Dj1/l9g5RH00/wO7puC1WVxgpvmhmaQg3wEETwmOFPk agent debug1: Server accepts key: /home/jak/.ssh/id_rsa RSA SHA256:Dj1/l9g5RH00/wO7puC1WVxgpvmhmaQg3wEETwmOFPk agent With 8.8p1-1 debug1: Offering public key: /home/jak/.ssh/id_rsa RSA SHA256:Dj1/l9g5RH00/wO7puC1WVxgpvmhmaQg3wEETwmOFPk agent debug1: send_pubkey_test: no mutual signature algorithm Needs further investigation, but blocks people a bit right now To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1961833/+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 1961837] Re: PackageKit 1.2.5 unable to perform upgrades
Sounded like a daemon crash at first, but the deeper I dig the more nonsensical it gets at the moment... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1961837 Title: PackageKit 1.2.5 unable to perform upgrades Status in packagekit package in Ubuntu: New Bug description: After being notified of upgrades available in Plasma Discover, I attempted to do an upgrade of all available packages. Unfortunately, it would not but also wouldn't show an error. I attempted to run 'pkcon update' which showed no available upgrades, whereas 'apt update' showed several packages available for upgrade. Expected behavior: 'pkcon update' would have performed the upgrade. Actual behavior: 'pkcon update' did nothing, saying no packages were available to upgrade. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: packagekit 1.2.5-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-lowlatency 5.15.12 Uname: Linux 5.15.0-18-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu77 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Tue Feb 22 11:33:52 2022 InstallationDate: Installed on 2021-03-20 (338 days ago) InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 (20210320) SourcePackage: packagekit UpgradeStatus: Upgraded to jammy on 2021-11-07 (107 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1961837/+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 1961833] Re: openssh 8.8 breaks login to Canonical servers
No, I'm not going to undo this. IS shouldn't be running a pre-xenial OpenSSH on xenial machines in the first place, and it's good to fix that; and anything older than that is well out of support anyway. ** Changed in: openssh (Ubuntu) Status: New => Won't Fix -- 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/1961833 Title: openssh 8.8 breaks login to Canonical servers Status in openssh package in Ubuntu: Won't Fix Bug description: With 8.7p1-4 connecting to wendigo debug1: Next authentication method: publickey debug1: Offering public key: /home/jak/.ssh/id_rsa RSA SHA256:Dj1/l9g5RH00/wO7puC1WVxgpvmhmaQg3wEETwmOFPk agent debug1: Server accepts key: /home/jak/.ssh/id_rsa RSA SHA256:Dj1/l9g5RH00/wO7puC1WVxgpvmhmaQg3wEETwmOFPk agent With 8.8p1-1 debug1: Offering public key: /home/jak/.ssh/id_rsa RSA SHA256:Dj1/l9g5RH00/wO7puC1WVxgpvmhmaQg3wEETwmOFPk agent debug1: send_pubkey_test: no mutual signature algorithm Needs further investigation, but blocks people a bit right now To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1961833/+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 1961833] Re: openssh 8.8 breaks login to Canonical servers
Also, regarding the "without a deprecation notice" claim, this has been advertised under "Future deprecation notice" in the OpenSSH release notes since 8.2. -- 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/1961833 Title: openssh 8.8 breaks login to Canonical servers Status in openssh package in Ubuntu: Won't Fix Bug description: With 8.7p1-4 connecting to wendigo debug1: Next authentication method: publickey debug1: Offering public key: /home/jak/.ssh/id_rsa RSA SHA256:Dj1/l9g5RH00/wO7puC1WVxgpvmhmaQg3wEETwmOFPk agent debug1: Server accepts key: /home/jak/.ssh/id_rsa RSA SHA256:Dj1/l9g5RH00/wO7puC1WVxgpvmhmaQg3wEETwmOFPk agent With 8.8p1-1 debug1: Offering public key: /home/jak/.ssh/id_rsa RSA SHA256:Dj1/l9g5RH00/wO7puC1WVxgpvmhmaQg3wEETwmOFPk agent debug1: send_pubkey_test: no mutual signature algorithm Needs further investigation, but blocks people a bit right now To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1961833/+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 1961833] Re: openssh 8.8 breaks login to Canonical servers
We generally expect programs to print a depreciation notice to stderr and not just hide them in release notes, that we, as downstream users don't read :) If it doesn't warn during use, it's not properly deprecated. -- 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/1961833 Title: openssh 8.8 breaks login to Canonical servers Status in openssh package in Ubuntu: Won't Fix Bug description: With 8.7p1-4 connecting to wendigo debug1: Next authentication method: publickey debug1: Offering public key: /home/jak/.ssh/id_rsa RSA SHA256:Dj1/l9g5RH00/wO7puC1WVxgpvmhmaQg3wEETwmOFPk agent debug1: Server accepts key: /home/jak/.ssh/id_rsa RSA SHA256:Dj1/l9g5RH00/wO7puC1WVxgpvmhmaQg3wEETwmOFPk agent With 8.8p1-1 debug1: Offering public key: /home/jak/.ssh/id_rsa RSA SHA256:Dj1/l9g5RH00/wO7puC1WVxgpvmhmaQg3wEETwmOFPk agent debug1: send_pubkey_test: no mutual signature algorithm Needs further investigation, but blocks people a bit right now To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1961833/+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 1961837] Re: PackageKit 1.2.5 unable to perform upgrades
** Changed in: packagekit (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1961837 Title: PackageKit 1.2.5 unable to perform upgrades Status in packagekit package in Ubuntu: New Bug description: After being notified of upgrades available in Plasma Discover, I attempted to do an upgrade of all available packages. Unfortunately, it would not but also wouldn't show an error. I attempted to run 'pkcon update' which showed no available upgrades, whereas 'apt update' showed several packages available for upgrade. Expected behavior: 'pkcon update' would have performed the upgrade. Actual behavior: 'pkcon update' did nothing, saying no packages were available to upgrade. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: packagekit 1.2.5-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-lowlatency 5.15.12 Uname: Linux 5.15.0-18-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu77 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Tue Feb 22 11:33:52 2022 InstallationDate: Installed on 2021-03-20 (338 days ago) InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 (20210320) SourcePackage: packagekit UpgradeStatus: Upgraded to jammy on 2021-11-07 (107 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1961837/+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 1961848] [NEW] gst-play-1.0 crashes when attempting to play a mp4 file
Public bug reported: I am attempting to play a mp4 file using gstreamer's gst-play-1.0. What I see is that a window is opened and a segmentation fault is reported (window closes). I am running Jammy: Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 On an Intel Coffelake core-i7 / integrated (Gen 9) graphics. The machine is updated as of Feb 22, 2022. Package version is: $ apt-cache policy gstreamer1.0-plugins-base-apps gstreamer1.0-plugins-base-apps: Installed: 1.20.0-2 Candidate: 1.20.0-2 Version table: *** 1.20.0-2 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status bms20@lichking:/tmp$ Crash log attached. Any advice on how to fix welcome! ** Affects: gst-plugins-base1.0 (Ubuntu) Importance: Undecided Status: New ** Attachment added: "_usr_bin_gst-play-1.0.1000.crash.gz" https://bugs.launchpad.net/bugs/1961848/+attachment/5562828/+files/_usr_bin_gst-play-1.0.1000.crash.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1961848 Title: gst-play-1.0 crashes when attempting to play a mp4 file Status in gst-plugins-base1.0 package in Ubuntu: New Bug description: I am attempting to play a mp4 file using gstreamer's gst-play-1.0. What I see is that a window is opened and a segmentation fault is reported (window closes). I am running Jammy: Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 On an Intel Coffelake core-i7 / integrated (Gen 9) graphics. The machine is updated as of Feb 22, 2022. Package version is: $ apt-cache policy gstreamer1.0-plugins-base-apps gstreamer1.0-plugins-base-apps: Installed: 1.20.0-2 Candidate: 1.20.0-2 Version table: *** 1.20.0-2 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status bms20@lichking:/tmp$ Crash log attached. Any advice on how to fix welcome! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-base1.0/+bug/1961848/+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 1961849] Re: bluetooth connects with headset, deconects, connects, deconnects
Start-Date: 2022-02-21 01:16:18 Commandline: apt -y upgrade Requested-By: tps (1000) Upgrade: firefox-locale-en:amd64 (97.0+build2-0ubuntu1, 97.0.1+build1-0ubuntu1), dmeventd:amd64 (2:1.02.175-2.1ubuntu3, 2:1.02.175-2.1ubuntu4), udev:amd64 (249.9-0ubuntu2, 249.10-0ubuntu1), libctf-nobfd0:amd64 (2.38-1ubuntu1, 2.38-2ubuntu1), systemd-container:amd64 (249.9-0ubuntu2, 249.10-0ubuntu1), libqmi-proxy:amd64 (1.30.2-1, 1.30.4-1), gir1.2-snapd-1:amd64 (1.58-4ubuntu1, 1.60-0ubuntu1), systemd-timesyncd:amd64 (249.9-0ubuntu2, 249.10-0ubuntu1), libpam-systemd:amd64 (249.9-0ubuntu2, 249.10-0ubuntu1), libarchive13:amd64 (3.5.2-1, 3.5.2-1ubuntu1), openmpi-bin:amd64 (4.1.2-1ubuntu1, 4.1.2-1ubuntu2), libbinutils:amd64 (2.38-1ubuntu1, 2.38-2ubuntu1), libfwupd2:amd64 (1.7.4-1ubuntu1, 1.7.5-3), libsnapd-glib1:amd64 (1.58-4ubuntu1, 1.60-0ubuntu1), openmpi-common:amd64 (4.1.2-1ubuntu1, 4.1.2-1ubuntu2), liblvm2cmd2.03:amd64 (2.03.11-2.1ubuntu3, 2.03.11-2.1ubuntu4), libsystemd0:amd64 (249.9-0ubuntu2, 249.10-0ubuntu1), libsystemd0:i386 (249.9-0ubuntu2, 249.10-0ubuntu1), binutils-x86-64-linux-gnu:amd64 (2.38-1ubuntu1, 2.38-2ubuntu1), libnss-systemd:amd64 (249.9-0ubuntu2, 249.10-0ubuntu1), systemd:amd64 (249.9-0ubuntu2, 249.10-0ubuntu1), libudev1:amd64 (249.9-0ubuntu2, 249.10-0ubuntu1), libudev1:i386 (249.9-0ubuntu2, 249.10-0ubuntu1), lvm2:amd64 (2.03.11-2.1ubuntu3, 2.03.11-2.1ubuntu4), libnss-mymachines:amd64 (249.9-0ubuntu2, 249.10-0ubuntu1), libctf0:amd64 (2.38-1ubuntu1, 2.38-2ubuntu1), dmsetup:amd64 (2:1.02.175-2.1ubuntu3, 2:1.02.175-2.1ubuntu4), python3-pil.imagetk:amd64 (9.0.0-1, 9.0.1-1), libhypre-2.22.1:amd64 (2.22.1-6, 2.22.1-7), libdevmapper-event1.02.1:amd64 (2:1.02.175-2.1ubuntu3, 2:1.02.175-2.1ubuntu4), binutils-common:amd64 (2.38-1ubuntu1, 2.38-2ubuntu1), libqmi-glib5:amd64 (1.30.2-1, 1.30.4-1), python3-pil:amd64 (9.0.0-1, 9.0.1-1), libopenmpi3:amd64 (4.1.2-1ubuntu1, 4.1.2-1ubuntu2), systemd-sysv:amd64 (249.9-0ubuntu2, 249.10-0ubuntu1), libfwupdplugin5:amd64 (1.7.4-1ubuntu1, 1.7.5-3), libdevmapper1.02.1:amd64 (2:1.02.175-2.1ubuntu3, 2:1.02.175-2.1ubuntu4), binutils:amd64 (2.38-1ubuntu1, 2.38-2ubuntu1), fwupd:amd64 (1.7.4-1ubuntu1, 1.7.5-3) End-Date: 2022-02-21 01:18:20 Start-Date: 2022-02-21 01:18:24 Commandline: apt -y dist-upgrade Requested-By: tps (1000) Install: libnfsidmap1:amd64 (1:2.6.1-1~exp1ubuntu1, automatic) Upgrade: nfs-common:amd64 (1:1.3.4-6ubuntu1, 1:2.6.1-1~exp1ubuntu1) Remove: libnfsidmap2:amd64 (0.25-6build1) End-Date: 2022-02-21 01:18:28 Start-Date: 2022-02-22 07:07:20 Commandline: apt -y upgrade Requested-By: tps (1000) Install: polkitd:amd64 (0.105-32, automatic), pkexec:amd64 (0.105-32, automatic) Upgrade: libpolkit-agent-1-0:amd64 (0.105-31.1, 0.105-32), libsmartcols1:amd64 (2.37.2-4ubuntu1, 2.37.2-4ubuntu3), debconf-i18n:amd64 (1.5.79, 1.5.79ubuntu1), apt:amd64 (2.3.15, 2.3.15build1), packagekit-tools:amd64 (1.2.4-1ubuntu2, 1.2.5-1ubuntu1), libxcb-image0:amd64 (0.4.0-1build2, 0.4.0-2), zfs-zed:amd64 (2.1.2-1ubuntu2, 2.1.2-1ubuntu3), libpipewire-0.3-common:amd64 (0.3.45-1, 0.3.47-1ubuntu1), zfs-initramfs:amd64 (2.1.2-1ubuntu2, 2.1.2-1ubuntu3), libaom3:amd64 (3.2.0-2, 3.3.0-1), libjpeg-turbo8:amd64 (2.1.1-0ubuntu1, 2.1.2-0ubuntu1), libjpeg-turbo8:i386 (2.1.1-0ubuntu1, 2.1.2-0ubuntu1), libnvpair3linux:amd64 (2.1.2-1ubuntu2, 2.1.2-1ubuntu3), grub-pc-bin:amd64 (2.06-2ubuntu4, 2.06-2ubuntu5), libapt-pkg6.0:amd64 (2.3.15, 2.3.15build1), libuutil3linux:amd64 (2.1.2-1ubuntu2, 2.1.2-1ubuntu3), debconf:amd64 (1.5.79, 1.5.79ubuntu1), libmount1:amd64 (2.37.2-4ubuntu1, 2.37.2-4ubuntu3), libmount1:i386 (2.37.2-4ubuntu1, 2.37.2-4ubuntu3), libzpool5linux:amd64 (2.1.2-1ubuntu2, 2.1.2-1ubuntu3), system-config-printer-udev:amd64 (1.5.15-2ubuntu1, 1.5.16-0ubuntu3), pipewire:amd64 (0.3.45-1, 0.3.47-1ubuntu1), libqpdf28:amd64 (10.5.0-1, 10.6.2-1), gir1.2-packagekitglib-1.0:amd64 (1.2.4-1ubuntu2, 1.2.5-1ubuntu1), util-linux:amd64 (2.37.2-4ubuntu1, 2.37.2-4ubuntu3), libjpeg-turbo-progs:amd64 (2.1.1-0ubuntu1, 2.1.2-0ubuntu1), fdisk:amd64 (2.37.2-4ubuntu1, 2.37.2-4ubuntu3), libfdisk1:amd64 (2.37.2-4ubuntu1, 2.37.2-4ubuntu3), system-config-printer-common:amd64 (1.5.15-2ubuntu1, 1.5.16-0ubuntu3), eject:amd64 (2.37.2-4ubuntu1, 2.37.2-4ubuntu3), packagekit:amd64 (1.2.4-1ubuntu2, 1.2.5-1ubuntu1), libturbojpeg:amd64 (2.1.1-0ubuntu1, 2.1.2-0ubuntu1), libuuid1:amd64 (2.37.2-4ubuntu1, 2.37.2-4ubuntu3), libuuid1:i386 (2.37.2-4ubuntu1, 2.37.2-4ubuntu3), make:amd64 (4.3-4ubuntu2, 4.3-4.1build1), uuid-runtime:amd64 (2.37.2-4ubuntu1, 2.37.2-4ubuntu3), grub-efi-amd64-signed:amd64 (1.177+2.06-2ubuntu4, 1.178+2.06-2ubuntu5), libjpeg-turbo8-dev:amd64 (2.1.1-0ubuntu1, 2.1.2-0ubuntu1), libpolkit-gobject-1-0:amd64 (0.105-31.1, 0.105-32), gir1.2-polkit-1.0:amd64 (0.105-31.1, 0.105-32), libpackagekit-glib2-18:amd64 (1.2.4-1ubuntu2, 1.2.5-1ubuntu1), pipewire-bin:amd64 (0.3.45-1, 0.3.47-1ubuntu1), system-config-printer:amd64 (1.5.15-2ubuntu1, 1.5.16-0ubuntu3), grub-efi-amd64-bin:a
[Touch-packages] [Bug 1961849] [NEW] bluetooth connects with headset, deconects, connects, deconnects
Public bug reported: bluetooth connects with headset, then times out, deconnects. Forcing it to connect again it does, then times out and deconnects again. Seen this with: - Cyber jack - Phonak Hearing Aids - Sennheiser Headset Since it worked until Feb. 21st, 2022 latest fixes applied at 18:00. And stopped working after Feb. 22nd, 2022 latest fixes applied at 21:00. One of the packages updated produced the problem. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.63-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu77 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Feb 22 23:18:09 2022 InstallationDate: Installed on 2021-12-11 (73 days ago) InstallationMedia: Xubuntu 21.10 "Impish Indri" - Release amd64 (20211012) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20FAS16K00 ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_vwfg3u@/vmlinuz-5.15.0-18-generic root=ZFS=rpool/ROOT/ubuntu_vwfg3u ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2021 dmi.bios.release: 1.52 dmi.bios.vendor: LENOVO dmi.bios.version: N1CET84W (1.52 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FAS16K00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.14 dmi.modalias: dmi:bvnLENOVO:bvrN1CET84W(1.52):bd07/08/2021:br1.52:efr1.14:svnLENOVO:pn20FAS16K00:pvrThinkPadT460s:rvnLENOVO:rn20FAS16K00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20FA_BU_Think_FM_ThinkPadT460s: dmi.product.family: ThinkPad T460s dmi.product.name: 20FAS16K00 dmi.product.sku: LENOVO_MT_20FA_BU_Think_FM_ThinkPad T460s dmi.product.version: ThinkPad T460s dmi.sys.vendor: LENOVO hciconfig: hci0: Type: Primary Bus: USB BD Address: 34:F3:9A:EE:2A:4A ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:18813 acl:14 sco:0 events:2736 errors:0 TX bytes:606658 acl:14 sco:0 commands:2675 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1961849 Title: bluetooth connects with headset, deconects, connects, deconnects Status in bluez package in Ubuntu: New Bug description: bluetooth connects with headset, then times out, deconnects. Forcing it to connect again it does, then times out and deconnects again. Seen this with: - Cyber jack - Phonak Hearing Aids - Sennheiser Headset Since it worked until Feb. 21st, 2022 latest fixes applied at 18:00. And stopped working after Feb. 22nd, 2022 latest fixes applied at 21:00. One of the packages updated produced the problem. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.63-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu77 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Feb 22 23:18:09 2022 InstallationDate: Installed on 2021-12-11 (73 days ago) InstallationMedia: Xubuntu 21.10 "Impish Indri" - Release amd64 (20211012) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20FAS16K00 ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_vwfg3u@/vmlinuz-5.15.0-18-generic root=ZFS=rpool/ROOT/ubuntu_vwfg3u ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2021 dmi.bios.release: 1.52 dmi.bios.vendor: LENOVO dmi.bios.version: N1CET84W (1.52 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FAS16K00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.14 dmi.modalias: dmi:bvnLENOVO:bvrN1CET84W(1.52):bd07/08/2021:br1.52:efr1.14:svnLENOVO:pn20FAS16K00:pvrThinkPadT460s:rvnLENOVO:rn20FAS16K00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20FA_BU_Think_FM_ThinkPadT460s: dmi.product.family: ThinkPad T460s dmi.product.name: 20FAS16K00 dmi.product.sku: LENOVO_MT_20FA_BU_Think_FM_ThinkPad T460s dmi.product.version: ThinkPad T460s dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 34:F3:9A:EE:2A:4A ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:18813 acl:14 sco:0 events:2736 errors:0 TX bytes:606658 acl:14 sco:0 commands:2675 errors:0 To manage notificatio
[Touch-packages] [Bug 1914278] Re: Kernel updates marked as "manually installed", prevents old kernels cleanup
I was unable to reproduce the crash in a VM, so it must've been unrelated to packagekit. Therefore, I guess we're OK, but I'm keeping an eye on it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1914278 Title: Kernel updates marked as "manually installed", prevents old kernels cleanup Status in packagekit package in Ubuntu: Fix Released Status in packagekit source package in Focal: New Status in packagekit source package in Jammy: Fix Released Bug description: With the machines I help administer, we have been finding situations where the /boot directory is filling-up beyond 3 kernels on LUKS encrypted systems. apt autoremove is not removing old kernels as expected. This may also be an issue with unattended-upgrades since I found the following line commented-out by default: // Remove unused automatically installed kernel-related packages // (kernel images, kernel headers and kernel version locked tools). // Unattended-Upgrade::Remove-Unused-Kernel-Packages "true"; We have had a system with as many as 15 kernel packages installed as a result of this not working as expected. The majority of these machines are using Discover to do their package upgrading, which uses PackageKit as its backend. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apt 2.0.4 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Feb 2 09:29:01 2021 InstallationDate: Installed on 2020-11-07 (87 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1914278/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1424768] Re: Consider switching to path based activation
I've sponsored the whoopsie changes, thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1424768 Title: Consider switching to path based activation Status in whoopsie package in Ubuntu: Confirmed Status in whoopsie source package in Bionic: Confirmed Bug description: 1) Ubuntu 15.04 2) 0.2.46 3) Whoopsie to only run when it is needed. 4) Instead it runs constantly, using network activity, l See bug (there are more..): https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/991481 also try: sudo fnotifystat -p whoopsie Instead whoopsie should use path based activation to only run when /var/crash has changed. http://www.freedesktop.org/software/systemd/man/systemd.path.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1424768/+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 1961837] Re: PackageKit 1.2.5 unable to perform upgrades
** Changed in: packagekit (Ubuntu) Assignee: (unassigned) => Matthias Klumpp (ximion) ** Also affects: packagekit (Ubuntu Jammy) Importance: Critical Assignee: Matthias Klumpp (ximion) Status: New ** Changed in: packagekit (Ubuntu Jammy) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1961837 Title: PackageKit 1.2.5 unable to perform upgrades Status in packagekit package in Ubuntu: In Progress Status in packagekit source package in Jammy: In Progress Bug description: After being notified of upgrades available in Plasma Discover, I attempted to do an upgrade of all available packages. Unfortunately, it would not but also wouldn't show an error. I attempted to run 'pkcon update' which showed no available upgrades, whereas 'apt update' showed several packages available for upgrade. Expected behavior: 'pkcon update' would have performed the upgrade. Actual behavior: 'pkcon update' did nothing, saying no packages were available to upgrade. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: packagekit 1.2.5-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-lowlatency 5.15.12 Uname: Linux 5.15.0-18-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu77 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Tue Feb 22 11:33:52 2022 InstallationDate: Installed on 2021-03-20 (338 days ago) InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 (20210320) SourcePackage: packagekit UpgradeStatus: Upgraded to jammy on 2021-11-07 (107 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1961837/+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 1961837] Re: PackageKit 1.2.5 unable to perform upgrades
** Also affects: packagekit via https://github.com/PackageKit/PackageKit/issues/534 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1961837 Title: PackageKit 1.2.5 unable to perform upgrades Status in PackageKit: Unknown Status in packagekit package in Ubuntu: In Progress Status in packagekit source package in Jammy: In Progress Bug description: After being notified of upgrades available in Plasma Discover, I attempted to do an upgrade of all available packages. Unfortunately, it would not but also wouldn't show an error. I attempted to run 'pkcon update' which showed no available upgrades, whereas 'apt update' showed several packages available for upgrade. Expected behavior: 'pkcon update' would have performed the upgrade. Actual behavior: 'pkcon update' did nothing, saying no packages were available to upgrade. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: packagekit 1.2.5-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-lowlatency 5.15.12 Uname: Linux 5.15.0-18-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu77 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Tue Feb 22 11:33:52 2022 InstallationDate: Installed on 2021-03-20 (338 days ago) InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 (20210320) SourcePackage: packagekit UpgradeStatus: Upgraded to jammy on 2021-11-07 (107 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/packagekit/+bug/1961837/+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 1961837] Re: PackageKit 1.2.5 unable to perform upgrades
I patched PackageKit from Matthias's upstream commits, and it works as expected now. Attached said patch, will also attach debdiff. ** Patch added: "Patch containing fix" https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1961837/+attachment/5562850/+files/9422895d4ee53aa31e775ced5d8bda1d7be23df3.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1961837 Title: PackageKit 1.2.5 unable to perform upgrades Status in PackageKit: Unknown Status in packagekit package in Ubuntu: In Progress Status in packagekit source package in Jammy: In Progress Bug description: After being notified of upgrades available in Plasma Discover, I attempted to do an upgrade of all available packages. Unfortunately, it would not but also wouldn't show an error. I attempted to run 'pkcon update' which showed no available upgrades, whereas 'apt update' showed several packages available for upgrade. Expected behavior: 'pkcon update' would have performed the upgrade. Actual behavior: 'pkcon update' did nothing, saying no packages were available to upgrade. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: packagekit 1.2.5-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-lowlatency 5.15.12 Uname: Linux 5.15.0-18-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu77 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Tue Feb 22 11:33:52 2022 InstallationDate: Installed on 2021-03-20 (338 days ago) InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 (20210320) SourcePackage: packagekit UpgradeStatus: Upgraded to jammy on 2021-11-07 (107 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/packagekit/+bug/1961837/+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 1961837] Re: PackageKit 1.2.5 unable to perform upgrades
Debdiff as mentioned above ** Patch added: "packagekit_1.2.5-1ubuntu2.debdiff" https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1961837/+attachment/5562851/+files/packagekit_1.2.5.1ubuntu2.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1961837 Title: PackageKit 1.2.5 unable to perform upgrades Status in PackageKit: Unknown Status in packagekit package in Ubuntu: In Progress Status in packagekit source package in Jammy: In Progress Bug description: After being notified of upgrades available in Plasma Discover, I attempted to do an upgrade of all available packages. Unfortunately, it would not but also wouldn't show an error. I attempted to run 'pkcon update' which showed no available upgrades, whereas 'apt update' showed several packages available for upgrade. Expected behavior: 'pkcon update' would have performed the upgrade. Actual behavior: 'pkcon update' did nothing, saying no packages were available to upgrade. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: packagekit 1.2.5-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-lowlatency 5.15.12 Uname: Linux 5.15.0-18-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu77 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Tue Feb 22 11:33:52 2022 InstallationDate: Installed on 2021-03-20 (338 days ago) InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 (20210320) SourcePackage: packagekit UpgradeStatus: Upgraded to jammy on 2021-11-07 (107 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/packagekit/+bug/1961837/+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 1961805] Re: Please merge procps 2:3.3.17-6 (main) from Debian unstable (main)
Excellent work. Just one comment, it's best practice to add the "please merge" bug number in the changelog. That way this bug will be automatically closed when the package is uploaded. I'll go ahead and add that in before I sponsor it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1961805 Title: Please merge procps 2:3.3.17-6 (main) from Debian unstable (main) Status in procps package in Ubuntu: Confirmed Bug description: This requires a merge because there are changes in the Ubuntu version not present in the Debian version. Dropped changes: - debian/README.sysctl: Debian has added this information. - debian/procps.install: debian/protect-links.conf has been re-named to debian/99-protect-links.conf, so it can be safely installed again (see LP: #1938585 for background). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1961805/+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 1961837] Re: PackageKit 1.2.5 unable to perform upgrades
Debian package is available: https://tracker.debian.org/news/1305719/accepted-packagekit-125-2-source-into-unstable/ I forgot to mark this issue as being explicitly closed in the changelog, but I guess Julian can do that when merging the changes into Ubuntu :-) ** Changed in: packagekit (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1961837 Title: PackageKit 1.2.5 unable to perform upgrades Status in PackageKit: Unknown Status in packagekit package in Ubuntu: Fix Committed Status in packagekit source package in Jammy: Fix Committed Bug description: After being notified of upgrades available in Plasma Discover, I attempted to do an upgrade of all available packages. Unfortunately, it would not but also wouldn't show an error. I attempted to run 'pkcon update' which showed no available upgrades, whereas 'apt update' showed several packages available for upgrade. Expected behavior: 'pkcon update' would have performed the upgrade. Actual behavior: 'pkcon update' did nothing, saying no packages were available to upgrade. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: packagekit 1.2.5-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-lowlatency 5.15.12 Uname: Linux 5.15.0-18-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu77 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Tue Feb 22 11:33:52 2022 InstallationDate: Installed on 2021-03-20 (338 days ago) InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 (20210320) SourcePackage: packagekit UpgradeStatus: Upgraded to jammy on 2021-11-07 (107 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/packagekit/+bug/1961837/+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 1961837] Re: PackageKit 1.2.5 unable to perform upgrades
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1961837 Title: PackageKit 1.2.5 unable to perform upgrades Status in PackageKit: Unknown Status in packagekit package in Ubuntu: Fix Committed Status in packagekit source package in Jammy: Fix Committed Bug description: After being notified of upgrades available in Plasma Discover, I attempted to do an upgrade of all available packages. Unfortunately, it would not but also wouldn't show an error. I attempted to run 'pkcon update' which showed no available upgrades, whereas 'apt update' showed several packages available for upgrade. Expected behavior: 'pkcon update' would have performed the upgrade. Actual behavior: 'pkcon update' did nothing, saying no packages were available to upgrade. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: packagekit 1.2.5-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-lowlatency 5.15.12 Uname: Linux 5.15.0-18-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu77 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Tue Feb 22 11:33:52 2022 InstallationDate: Installed on 2021-03-20 (338 days ago) InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 (20210320) SourcePackage: packagekit UpgradeStatus: Upgraded to jammy on 2021-11-07 (107 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/packagekit/+bug/1961837/+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 1961858] Re: compiz crashed with SIGSEGV in ntt_no_indirects_mask() from nir_to_tgsi() from draw_create_vertex_shader() from r300_draw_init_vertex_shader() from r300_create_vs_st
See also bug 1961857. ** Summary changed: - /usr/bin/compiz:11:ntt_no_indirects_mask:nir_to_tgsi:draw_create_vertex_shader:r300_draw_init_vertex_shader:r300_create_vs_state + compiz crashed with SIGSEGV in ntt_no_indirects_mask() from nir_to_tgsi() from draw_create_vertex_shader() from r300_draw_init_vertex_shader() from r300_create_vs_state() ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags added: radeon -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1961858 Title: compiz crashed with SIGSEGV in ntt_no_indirects_mask() from nir_to_tgsi() from draw_create_vertex_shader() from r300_draw_init_vertex_shader() from r300_create_vs_state() Status in compiz package in Ubuntu: New Status in mesa package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding compiz. This problem was most recently seen with package version 1:0.9.14.1+20.04.20200211-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/e715e808830237b34f47eaf08647380de1916892 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1961858/+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 1961857] Re: compiz crashed with SIGSEGV in nir_lower_uniforms_to_ubo() from draw_create_vs_llvm() from draw_create_vertex_shader() from r300_draw_init_vertex_shader() from r300_
See also bug 1961858. ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New ** Changed in: mesa (Ubuntu) Status: New => Confirmed ** Tags added: radeon -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1961857 Title: compiz crashed with SIGSEGV in nir_lower_uniforms_to_ubo() from draw_create_vs_llvm() from draw_create_vertex_shader() from r300_draw_init_vertex_shader() from r300_create_vs_state() Status in compiz package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding compiz. This problem was most recently seen with package version 1:0.9.14.1+20.04.20200211-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/253612f74aa79d2e52b8f27505f04cb72de285c1 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1961857/+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 1961561] Re: [radeon] Blinking screen
*** This bug is a duplicate of bug 1961857 *** https://bugs.launchpad.net/bugs/1961857 Thanks. The only crash report from your machine that looks like this bug is now in bug 1961857. But that is so rare it's only ever been reported twice. Most likely it will be resolved (or already has been) in a newer version of Mesa. ** This bug has been marked a duplicate of bug 1961857 compiz crashed with SIGSEGV in nir_lower_uniforms_to_ubo() from draw_create_vs_llvm() from draw_create_vertex_shader() from r300_draw_init_vertex_shader() from r300_create_vs_state() -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1961561 Title: [radeon] Blinking screen Status in compiz package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: Binking screen with radeon after upgrade 18.04 to 20.04 - Console OK ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Feb 21 10:13:34 2022 DistUpgraded: 2021-03-08 13:38:14,332 DEBUG package 'libcpanel-json-xs-perl' produces an unwanted removal 'gnome-software-plugin-snap', skipping DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS482/RS485 [Radeon Xpress 1100/1150] [1002:5974] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company DC5750 Microtower [103c:280a] Subsystem: Hewlett-Packard Company RS480 [Radeon Xpress 1150] (Secondary) [103c:280b] InstallationDate: Installed on 2015-11-26 (2278 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Hewlett-Packard HP Compaq dc5750 Small Form Factor ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic root=UUID=681c938b-c95d-48de-886f-bc784bb57787 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2021-03-08 (349 days ago) dmi.bios.date: 01/25/2007 dmi.bios.release: 2.10 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786E3 v02.10 dmi.board.name: 0A64h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC8061JND dmi.chassis.type: 4 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786E3v02.10:bd01/25/2007:br2.10:svnHewlett-Packard:pnHPCompaqdc5750SmallFormFactor:pvr:rvnHewlett-Packard:rn0A64h:rvr:cvnHewlett-Packard:ct4:cvr:skuEW318AV: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq dc5750 Small Form Factor dmi.product.sku: EW318AV dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Mon Feb 21 10:00:44 2022 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.13-1ubuntu1~20.04.2 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1961561/+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 1961823] Re: [RTL8822BE] Bluetooth adapter not found
** Summary changed: - Bluetooth button off and doesn't work + [RTL8822BE] Bluetooth adapter not found ** Package changed: bluez (Ubuntu) => linux-hwe-5.13 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1961823 Title: [RTL8822BE] Bluetooth adapter not found Status in linux-hwe-5.13 package in Ubuntu: New Bug description: Bluetooth button off and doesn't work the massage that show me when i open the setting " No Bluetooth Found plug in a dongle to use Bluetooth " ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth 5.53-0ubuntu3.5 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Feb 22 21:08:36 2022 InstallationDate: Installed on 2022-02-17 (4 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) InterestingModules: bnep bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 05c8:03d2 Cheng Uei Precision Industry Co., Ltd (Foxlink) HP TrueVision HD Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 5: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 5: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M MachineType: HP HP Laptop 15-da1xxx PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic root=UUID=616f1e34-70a5-4b45-82ae-a86b7f795ab2 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2021 dmi.bios.release: 15.38 dmi.bios.vendor: Insyde dmi.bios.version: F.38 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8533 dmi.board.vendor: HP dmi.board.version: 70.38 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 70.38 dmi.modalias: dmi:bvnInsyde:bvrF.38:bd08/31/2021:br15.38:efr70.38:svnHP:pnHPLaptop15-da1xxx:pvrType1ProductConfigId:rvnHP:rn8533:rvr70.38:cvnHP:ct10:cvrChassisVersion:sku6EX79EA#A2N: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-da1xxx dmi.product.sku: 6EX79EA#A2N dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP hciconfig: rfkill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1961823/+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 1961849] Re: bluetooth connects with headset, deconects, connects, deconnects
Thanks for the bug report. bluez has not changed at all since 2022-01-13 so the problem isn't going to be that. Next I would usually blame the kernel but that hasn't changed since 2022-01-27. I don't see anything in comment #2 related to Bluetooth either (maybe pipewire?). Can you provide more of the log? ** Package changed: bluez (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1961849 Title: bluetooth connects with headset, deconects, connects, deconnects Status in Ubuntu: Incomplete Bug description: bluetooth connects with headset, then times out, deconnects. Forcing it to connect again it does, then times out and deconnects again. Seen this with: - Cyber jack - Phonak Hearing Aids - Sennheiser Headset Since it worked until Feb. 21st, 2022 latest fixes applied at 18:00. And stopped working after Feb. 22nd, 2022 latest fixes applied at 21:00. One of the packages updated produced the problem. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.63-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu77 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Feb 22 23:18:09 2022 InstallationDate: Installed on 2021-12-11 (73 days ago) InstallationMedia: Xubuntu 21.10 "Impish Indri" - Release amd64 (20211012) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20FAS16K00 ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_vwfg3u@/vmlinuz-5.15.0-18-generic root=ZFS=rpool/ROOT/ubuntu_vwfg3u ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2021 dmi.bios.release: 1.52 dmi.bios.vendor: LENOVO dmi.bios.version: N1CET84W (1.52 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FAS16K00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.14 dmi.modalias: dmi:bvnLENOVO:bvrN1CET84W(1.52):bd07/08/2021:br1.52:efr1.14:svnLENOVO:pn20FAS16K00:pvrThinkPadT460s:rvnLENOVO:rn20FAS16K00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20FA_BU_Think_FM_ThinkPadT460s: dmi.product.family: ThinkPad T460s dmi.product.name: 20FAS16K00 dmi.product.sku: LENOVO_MT_20FA_BU_Think_FM_ThinkPad T460s dmi.product.version: ThinkPad T460s dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 34:F3:9A:EE:2A:4A ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:18813 acl:14 sco:0 events:2736 errors:0 TX bytes:606658 acl:14 sco:0 commands:2675 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1961849/+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 1961618] Re: Pi server image no longer connects to eth0 after upgrade to jammy
This bug was fixed in the package ubuntu-settings - 22.04.2 --- ubuntu-settings (22.04.2) jammy; urgency=medium * d/ubuntu-raspi-settings.maintscript: Remove the pre-jammy netplan eth0 rules; the newer netplan chokes on the space-separated driver filter (LP: #1961618) * meson.build: Remove incorrect positional param -- Dave Jones Mon, 21 Feb 2022 17:28:05 + ** Changed in: ubuntu-settings (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1961618 Title: Pi server image no longer connects to eth0 after upgrade to jammy Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: The eth0 rename fix introduced in 20.10.1, and removed in 22.04.1 unfortunately causes problems on upgrade from impish to jammy as the file (/etc/netplan/10-rpi-ethernet-eth0.yaml) still remains in place, and the new netplan version on jammy chokes on the space-separated driver filter. This results in the entire netplan configuration failing to apply, with the result that the network doesn't come up. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1961618/+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 1961196] Re: apparmor autotest failure on jammy with linux 5.15
This bug was fixed in the package apparmor - 3.0.4-1ubuntu1 --- apparmor (3.0.4-1ubuntu1) jammy; urgency=medium * Merge from Debian unstable; remaining changes: - Drop the following patches that have been included in the upstream release or which Debian has also included: - d/p/ubuntu/adjust-for-ibus-1.5.22.patch - d/p/ubuntu/0011-add-mctp-network-protocol.patch - Refresh d/p/regression-tests-fix-aa_policy_cache-when-using-syst.patch to the official version from upstream - d/p/u/samba-systemd-interaction.patch: allow smbd to interact with systemd - d/p/u/libnss-systemd.patch: allow accessing the libnss-systemd VarLink sockets and DBus APIs - Disable lto builds - Fix autotest test-aa-notify.py - d/p/ubuntu/fix-test-aa-notify.patch - Drop outdated lintian-overrides apparmor (3.0.4-1) unstable; urgency=medium * New upstream release * apparmor-profiles: install new samba-bgqd profile * Drop backported patches that are now obsolete * debian/allow-access-to-ibus-socket.patch: drop support for pre-Bullseye ibus path * Declare compliance with Policy 4.6.0.1 * Drop XS- prefix for adopted Python-Version control field * Add new symbols apparmor (3.0.3-6) unstable; urgency=medium * debian/rules: let "set -e" take effect (Closes: #998843) * Add support for Python 3.10 (Closes: #998686): - upstream-ab4cfb5e-replace-distutils-with-setuptools.patch: new patch, edited to drop changes to upstream .gitignore. - Add build-dependency on python3-setuptools apparmor (3.0.3-5) unstable; urgency=medium [ Debian Janitor ] * Remove constraints unnecessary since stretch. [ Helmut Grohne ] * Make the package cross-buildable (Closes: #984582): - Multiarchify python Build-Depends - Let dh_auto_build pass cross tools to make - Annotate perl build-dependency with !nocheck [ intrigeri ] * Remove obsolete libapparmor-perl on upgrade apparmor (3.0.3-4) unstable; urgency=medium * Merge apparmor-easyprof into apparmor-utils (Closes: #972880) * Make apparmor-utils and python3-apparmor arch:all (Closes: #972881) apparmor (3.0.3-3) unstable; urgency=medium * Adjust gbp.conf and Vcs-* control fields for 3.0.x now being in sid. * Stop building the libapparmor-perl binary package (Closes: #993565) * Update Lintian overrides * Add B-D on dh-sequence-python3, to workaround #996089 in Lintian * B-D: python3-all → python3-all:any, to appease Lintian apparmor (3.0.3-2) unstable; urgency=medium * Upload to unstable apparmor (3.0.3-1) experimental; urgency=medium * New upstream release * Drop debian/Revert-libapparmor-fixing-setup.py-call-when-crosscompili.patch: obsolete * Refresh patches * Merge changes from sid, up to 2.13.6-10 * upstream-6cfc6eee-python-3.10.patch: new patch, for compatibility with Python 3.10 -- Alex Murray Tue, 22 Feb 2022 10:13:44 +1030 ** Changed in: apparmor (Ubuntu Jammy) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1961196 Title: apparmor autotest failure on jammy with linux 5.15 Status in apparmor package in Ubuntu: Fix Released Status in apparmor source package in Jammy: Fix Released Bug description: [Impact] test-aa-notify is also checking if the output of `aa-notify --help` matches a specific text. However it looks like this output has changed in jammy so the autopkgtest is reporting errors like this: 05:17:31 ERROR| [stderr] === test-aa-notify.py === 05:17:31 ERROR| [stderr] .ssF. 05:17:31 ERROR| [stderr] == 05:17:31 ERROR| [stderr] FAIL: test_help_contents (__main__.AANotifyTest) 05:17:31 ERROR| [stderr] Test output of help text 05:17:31 ERROR| [stderr] -- 05:17:31 ERROR| [stderr] Traceback (most recent call last): 05:17:31 ERROR| [stderr] File "/tmp/testlibmse00lib/source/jammy/apparmor-3.0.3/utils/test/test-aa-notify.py", line 178, in test_help_contents 05:17:31 ERROR| [stderr] self.assertEqual(expected_output_is, output, result + output) 05:17:31 ERROR| [stderr] AssertionError: 'usag[189 chars]ptional arguments:\n -h, --helpsh[746 chars]de\n' != 'usag[189 chars]ptions:\n -h, --helpshow this hel[735 chars]de\n' 05:17:31 ERROR| [stderr] usage: aa-notify [-h] [-p] [--display DISPLAY] [-f FILE] [-l] [-s NUM] [-v] 05:17:31 ERROR| [stderr][-u USER] [-w NUM] [--debug] 05:17:31 ERROR| [stderr] 05:17:31 ERROR| [stderr] Display AppArmor notifications or messages for DENIED entries. 05:17:31 ERROR| [stderr] 05:17:31 ERROR| [stderr] - optional arguments: 05:17:31 ERROR| [stderr] + options: 05:17:31 ERROR| [stderr]
[Touch-packages] [Bug 1961558] Re: 802.1x connection Handshake failure ssl3 error in Jammy Jellyfish
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1961558 Title: 802.1x connection Handshake failure ssl3 error in Jammy Jellyfish Status in network-manager package in Ubuntu: Confirmed Bug description: I had install Jammy (beta) release to test it. I have my network with Radius authentication configured, so we have made a Network Profile enabling 802.1x authentication in Ubuntu. When I tried to connecting to the network it doesn't worked. I saw the logs (see picture) and it says that it was a handshake failure in the connection because there is a SSL3 error. I read that probably it can be a problem with the legacy renegotiation in the handshake, but I'm not sure why happens that and what can I do to fix this problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1961558/+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 1956603] Re: /usr/libexec/gdm-x-session: > Internal error: Could not resolve keysym .....
Also brings a huge help to firefox freezing/crashing: https://gitlab.freedesktop.org/xorg/lib/libx11/-/issues/153 ** Bug watch added: gitlab.freedesktop.org/xorg/lib/libx11/-/issues #153 https://gitlab.freedesktop.org/xorg/lib/libx11/-/issues/153 -- 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/1956603 Title: /usr/libexec/gdm-x-session: > Internal error: Could not resolve keysym . Status in xlibs: Unknown Status in libx11 package in Ubuntu: Fix Committed Status in x11-xkb-utils package in Ubuntu: Confirmed Bug description: Get lot of such warnings into Jammy logged; Actual libx11 is 1.7.2 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86MediaRepeat /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF8610ChannelsUp /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF8610ChannelsDown /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Images /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86NotificationCenter /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86PickupPhone /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86HangupPhone /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Fn /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Fn_Esc /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86FnRightShift /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Numeric0 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Numeric1 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Numeric2 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Numeric3 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Numeric4 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Numeric5 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Numeric6 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Numeric7 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Numeric8 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Numeric9 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86NumericStar /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86NumericPound /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86NumericA /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86NumericB /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86NumericC /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86NumericD /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86CameraFocus /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86WPSButton /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86CameraZoomIn /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86CameraZoomOut /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86CameraUp /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86CameraDown /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86CameraLeft /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86CameraRight /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86AttendantOn /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86AttendantOff /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86AttendantToggle /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86LightsToggle --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: MATE DistUpgraded: Fresh install DistroCodename: jammy DistroRelease: Ubuntu 22.04 DistroVariant: ubuntu DkmsStatus: fwts-efi-runtime-dkms/21.12.00, 5.15.0-13-generic, x86_64: installed (WARNING! Diff between built and installed module!) fwts-efi-runtime-dkms/21.12.00, 5.15.0-14-generic, x86_64: installed (WARNING! Diff bet
[Touch-packages] [Bug 1956603] Re: /usr/libexec/gdm-x-session: > Internal error: Could not resolve keysym .....
I think you mean the new libx11 is useful in solving other bugs. This bug should be about the log messages only, so it's low importance. Although it's prevalent enough that people who read logs all day (me) will really appreciate the fix. -- 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/1956603 Title: /usr/libexec/gdm-x-session: > Internal error: Could not resolve keysym . Status in xlibs: Unknown Status in libx11 package in Ubuntu: Fix Committed Status in x11-xkb-utils package in Ubuntu: Confirmed Bug description: Get lot of such warnings into Jammy logged; Actual libx11 is 1.7.2 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86MediaRepeat /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF8610ChannelsUp /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF8610ChannelsDown /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Images /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86NotificationCenter /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86PickupPhone /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86HangupPhone /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Fn /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Fn_Esc /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86FnRightShift /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Numeric0 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Numeric1 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Numeric2 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Numeric3 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Numeric4 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Numeric5 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Numeric6 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Numeric7 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Numeric8 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Numeric9 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86NumericStar /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86NumericPound /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86NumericA /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86NumericB /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86NumericC /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86NumericD /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86CameraFocus /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86WPSButton /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86CameraZoomIn /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86CameraZoomOut /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86CameraUp /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86CameraDown /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86CameraLeft /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86CameraRight /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86AttendantOn /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86AttendantOff /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86AttendantToggle /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86LightsToggle --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: MATE DistUpgraded: Fresh install DistroCodename: jammy DistroRelease: Ubuntu 22.04 DistroVariant: ubuntu DkmsStatus: fwts-efi-runtime-dkms/21.12.00, 5.15.0-13-generic, x86_64: installed (WARNING! Diff between built and installed module!) fwts-efi-runtime-dkms/21.12.00, 5.15.0-14-generic, x86_64: installed (WARNING! Diff between built a
[Touch-packages] [Bug 1424768] Re: Consider switching to path based activation
This bug was fixed in the package whoopsie - 0.2.77 --- whoopsie (0.2.77) jammy; urgency=medium [ Olivier Gayot ] * Added the --no-polling switch so that whoopsie can process existing files and exit directly (LP: #1424768) * Don't try to process files when we know we're offline. Eventually, we would just be ignoring each report ; which would result in useless CPU and IO usage. * Actually move to path-based activation (LP: #1424768) -- Brian Murray Tue, 22 Feb 2022 14:37:37 -0800 ** Changed in: whoopsie (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1424768 Title: Consider switching to path based activation Status in whoopsie package in Ubuntu: Fix Released Status in whoopsie source package in Bionic: Confirmed Bug description: 1) Ubuntu 15.04 2) 0.2.46 3) Whoopsie to only run when it is needed. 4) Instead it runs constantly, using network activity, l See bug (there are more..): https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/991481 also try: sudo fnotifystat -p whoopsie Instead whoopsie should use path based activation to only run when /var/crash has changed. http://www.freedesktop.org/software/systemd/man/systemd.path.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1424768/+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
