[Touch-packages] [Bug 1944409] Re: Systemd uses CPU after wakeup due to power_supply BAT0 (battery) continued polling
For Latitude 7520, BIOS 1.7.1 should fix this issue. -- 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/1944409 Title: Systemd uses CPU after wakeup due to power_supply BAT0 (battery) continued polling Status in OEM Priority Project: New Status in systemd package in Ubuntu: Confirmed Bug description: My setup: - Dell Latitude 7520 - Dell WD15 USB C docking station - Ubuntu 20.04.3 - systemd 245.4-4ubuntu3.13 - uname -a: Linux CLIFMI085 5.13.0-1012-oem #16-Ubuntu SMP Tue Sep 7 09:23:08 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux I leave my laptop docked and, after waking it up from sleep, the fans start blowing. After a quick inspection with top/htop, I always see /usr/lib/systemd/systemd-udev consuming 50+% of my CPU. After a quick search, I discover that I can use `udevadm monitor` to check what device is making all this fuss, and this is the output: UDEV [92591.827159] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92591.873819] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92591.920022] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92591.967005] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.018200] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.068351] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.115100] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.166201] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.213318] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.261046] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.308824] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.356577] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.403766] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.451164] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) As you can see, the battery status is being polled every 0.05s. To fix this, I just need to restart the service with: sudo systemctl restart systemd-udevd systemd-udevd-kernel.socket systemd-udevd-control.socket Afterwards, this is the output of `udevadm monitor`: KERNEL[92739.612371] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92739.646888] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) KERNEL[92741.076823] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92741.099370] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) KERNEL[92742.539438] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92742.573812] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) As you can see, the battery is now being polled every ~1.5s, which is fine. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1944409/+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 1954843] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1954843 Title: amdgpu_bl0: Failed to write system 'brightness' attribute: Invalid argument Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: Ubuntu 21.10 does not succeed at setting the display brightness after booting (either to the GNOME login screen or to a logged-in user's desktop). The brightness is at its highest level until I adjust it with keyboard shortcuts or a GUI tool. The systemd-backlight@backlight:amdgpu_bl0 service seems to fail during startup, but I can subsequently run it after startup and it succeeds (and restores brightness): mdmower@T14S ~ $ sudo systemctl status systemd-backlight@backlight:amdgpu_bl0 [sudo] password for mdmower: × systemd-backlight@backlight:amdgpu_bl0.service - Load/Save Screen Backlight Brightness of backlight:amdgpu_bl0 Loaded: loaded (/lib/systemd/system/systemd-backlight@.service; static) Active: failed (Result: exit-code) since Tue 2021-12-14 13:26:05 PST; 30s ago Docs: man:systemd-backlight@.service(8) Process: 962 ExecStart=/lib/systemd/systemd-backlight load backlight:amdgpu_bl0 (code=exited, status=1/FAILURE) Main PID: 962 (code=exited, status=1/FAILURE) CPU: 3ms Dec 14 13:26:05 T14S systemd[1]: Starting Load/Save Screen Backlight Brightness of backlight:amdgpu_bl0... Dec 14 13:26:05 T14S systemd-backlight[962]: amdgpu_bl0: Failed to write system 'brightness' attribute: Invalid argument Dec 14 13:26:05 T14S systemd[1]: systemd-backlight@backlight:amdgpu_bl0.service: Main process exited, code=exited, status=1/FAILURE Dec 14 13:26:05 T14S systemd[1]: systemd-backlight@backlight:amdgpu_bl0.service: Failed with result 'exit-code'. Dec 14 13:26:05 T14S systemd[1]: Failed to start Load/Save Screen Backlight Brightness of backlight:amdgpu_bl0. mdmower@T14S ~ $ sudo systemctl start systemd- backlight@backlight:amdgpu_bl0 mdmower@T14S ~ $ sudo systemctl status systemd-backlight@backlight:amdgpu_bl0 ● systemd-backlight@backlight:amdgpu_bl0.service - Load/Save Screen Backlight Brightness of backlight:amdgpu_bl0 Loaded: loaded (/lib/systemd/system/systemd-backlight@.service; static) Active: active (exited) since Tue 2021-12-14 13:26:45 PST; 1s ago Docs: man:systemd-backlight@.service(8) Process: 5119 ExecStart=/lib/systemd/systemd-backlight load backlight:amdgpu_bl0 (code=exited, status=0/SUCCESS) Main PID: 5119 (code=exited, status=0/SUCCESS) CPU: 5ms Dec 14 13:26:45 T14S systemd[1]: Starting Load/Save Screen Backlight Brightness of backlight:amdgpu_bl0... Dec 14 13:26:45 T14S systemd[1]: Finished Load/Save Screen Backlight Brightness of backlight:amdgpu_bl0. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Dec 14 13:29:38 2021 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev d1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Cezanne [17aa:5095] InstallationDate: Installed on 2021-12-12 (2 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 20XF004WUS ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=859a72cc-a3fe-470f-b525-37b151408289 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.14 dmi.bios.vendor: LENOVO dmi.bios.version: R1NET44W (1.14) dmi.board.asset.tag: Not Available dmi.board.name: 20XF004WUS 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:bvrR1NET44W(1.14):bd11/08/2021:br1.14:efr1.14:svnLENOVO:pn20XF004WUS:pvrThinkPadT14sGen2a:rvnLENOVO:rn20XF004WUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XF_BU_Think_FM_ThinkPadT14sGen2a: dmi.product.family: ThinkPad T14s Gen 2a dmi.product.name: 20XF004WUS dmi.product.sku:
[Touch-packages] [Bug 1954843] Re: amdgpu_bl0: Failed to write system 'brightness' attribute: Invalid argument
** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** 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 xorg in Ubuntu. https://bugs.launchpad.net/bugs/1954843 Title: amdgpu_bl0: Failed to write system 'brightness' attribute: Invalid argument Status in linux package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Ubuntu 21.10 does not succeed at setting the display brightness after booting (either to the GNOME login screen or to a logged-in user's desktop). The brightness is at its highest level until I adjust it with keyboard shortcuts or a GUI tool. The systemd-backlight@backlight:amdgpu_bl0 service seems to fail during startup, but I can subsequently run it after startup and it succeeds (and restores brightness): mdmower@T14S ~ $ sudo systemctl status systemd-backlight@backlight:amdgpu_bl0 [sudo] password for mdmower: × systemd-backlight@backlight:amdgpu_bl0.service - Load/Save Screen Backlight Brightness of backlight:amdgpu_bl0 Loaded: loaded (/lib/systemd/system/systemd-backlight@.service; static) Active: failed (Result: exit-code) since Tue 2021-12-14 13:26:05 PST; 30s ago Docs: man:systemd-backlight@.service(8) Process: 962 ExecStart=/lib/systemd/systemd-backlight load backlight:amdgpu_bl0 (code=exited, status=1/FAILURE) Main PID: 962 (code=exited, status=1/FAILURE) CPU: 3ms Dec 14 13:26:05 T14S systemd[1]: Starting Load/Save Screen Backlight Brightness of backlight:amdgpu_bl0... Dec 14 13:26:05 T14S systemd-backlight[962]: amdgpu_bl0: Failed to write system 'brightness' attribute: Invalid argument Dec 14 13:26:05 T14S systemd[1]: systemd-backlight@backlight:amdgpu_bl0.service: Main process exited, code=exited, status=1/FAILURE Dec 14 13:26:05 T14S systemd[1]: systemd-backlight@backlight:amdgpu_bl0.service: Failed with result 'exit-code'. Dec 14 13:26:05 T14S systemd[1]: Failed to start Load/Save Screen Backlight Brightness of backlight:amdgpu_bl0. mdmower@T14S ~ $ sudo systemctl start systemd- backlight@backlight:amdgpu_bl0 mdmower@T14S ~ $ sudo systemctl status systemd-backlight@backlight:amdgpu_bl0 ● systemd-backlight@backlight:amdgpu_bl0.service - Load/Save Screen Backlight Brightness of backlight:amdgpu_bl0 Loaded: loaded (/lib/systemd/system/systemd-backlight@.service; static) Active: active (exited) since Tue 2021-12-14 13:26:45 PST; 1s ago Docs: man:systemd-backlight@.service(8) Process: 5119 ExecStart=/lib/systemd/systemd-backlight load backlight:amdgpu_bl0 (code=exited, status=0/SUCCESS) Main PID: 5119 (code=exited, status=0/SUCCESS) CPU: 5ms Dec 14 13:26:45 T14S systemd[1]: Starting Load/Save Screen Backlight Brightness of backlight:amdgpu_bl0... Dec 14 13:26:45 T14S systemd[1]: Finished Load/Save Screen Backlight Brightness of backlight:amdgpu_bl0. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Dec 14 13:29:38 2021 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev d1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Cezanne [17aa:5095] InstallationDate: Installed on 2021-12-12 (2 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 20XF004WUS ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=859a72cc-a3fe-470f-b525-37b151408289 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.14 dmi.bios.vendor: LENOVO dmi.bios.version: R1NET44W (1.14) dmi.board.asset.tag: Not Available dmi.board.name: 20XF004WUS 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:bvrR1NET44W(1.14):bd11/08/2021:br1.14:efr1.14:svnLENOVO:pn20XF004WUS:pvrThinkPadT14sGen2a:rvnLENOVO:rn20XF004WUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XF_BU_Think_FM_ThinkPadT14sGen2a: dmi.product.family: ThinkPad T14s Gen 2a dmi.product.name: 20XF004WUS
[Touch-packages] [Bug 1954840] Re: Unabke to set Display to max resolution supported by Monitor and laptop
*** This bug is a duplicate of bug 1901470 *** https://bugs.launchpad.net/bugs/1901470 The EDID data reported by the monitor (decoded from XorgLog.txt) mentions the correct resolution: EDID version: 1.3 Manufacturer: DEL Model 16619 Serial Number 842152019 Made in week 32 of 2017 Digital display Maximum image size: 60 cm x 34 cm Gamma: 2.20 DPMS levels: Off RGB color display First detailed timing is preferred timing Color Characteristics Red: 0.6396, 0.3300 Green: 0.2998, 0.5996 Blue: 0.1503, 0.0595 White: 0.3134, 0.3291 Established Timings I & II 720x40070.082 Hz 9:531.467 kHz 28.320 MHz (IBM) 640x48059.940 Hz 4:331.469 kHz 25.175 MHz (DMT) 640x48075.000 Hz 4:337.500 kHz 31.500 MHz (DMT) 800x60060.317 Hz 4:337.879 kHz 40.000 MHz (DMT) 800x60075.000 Hz 4:346.875 kHz 49.500 MHz (DMT) 1024x76860.004 Hz 4:348.363 kHz 65.000 MHz (DMT) 1024x76875.029 Hz 4:360.023 kHz 78.750 MHz (DMT) 1280x1024 75.025 Hz 5:479.976 kHz 135.000 MHz (DMT) Standard Timings 1152x86475.000 Hz 4:367.500 kHz 108.000 MHz (DMT) 1600x1200 60.000 Hz 4:375.000 kHz 162.000 MHz (DMT) 1280x1024 60.020 Hz 5:463.981 kHz 108.000 MHz (DMT) 1920x1080 60.000 Hz 16:967.500 kHz 148.500 MHz (DMT) Detailed mode: Clock 241.500 MHz, 597 mm x 336 mm 2560 2608 2640 2720 ( 48 32 80) 1440 1443 1448 1481 ( 3 5 33) +hsync -vsync VertFreq: 59.951 Hz, HorFreq: 88.787 kHz Display Product Serial Number: J0XYN78B228S Display Product Name: DELL U2717D Display Range Limits Monitor ranges (GTF): 50-75 Hz V, 30-88 kHz H, max dotclock 250 MHz Has 1 extension block Checksum: 0xcd ** Summary changed: - Unabke to set Display to max resolution supported by Monitor and laptop + [i915] Unable to set Display to max resolution supported by Monitor and laptop ** Package changed: xorg (Ubuntu) => linux-hwe-5.11 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1954840 Title: [i915] Unable to set Display to max resolution supported by Monitor and laptop Status in linux-hwe-5.11 package in Ubuntu: New Bug description: Hi, my secondary display support 2560*1440 but 'Display' in Ubuntu is presenting a max resolution of 2048*1080. The max resolution was working yesterday, I think I performed a update today and it has stopped working after that. Thanks, Jerry, ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Dec 14 19:52:57 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:504a] InstallationDate: Installed on 2021-04-16 (242 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20F5S2BL00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-41-generic root=UUID=5cb08771-ead9-4f2c-9550-4125931d1f4a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/09/2019 dmi.bios.release: 1.45 dmi.bios.vendor: LENOVO dmi.bios.version: R02ET72W (1.45 ) dmi.board.asset.tag: Not Available dmi.board.name: 20F5S2BL00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 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.15 dmi.modalias: dmi:bvnLENOVO:bvrR02ET72W(1.45):bd10/09/2019:br1.45:efr1.15:svnLENOVO:pn20F5S2BL00:pvrThinkPadX260:skuLENOVO_MT_20F5_BU_Think_FM_ThinkPadX260:rvnLENOVO:rn20F5S2BL00:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X260 dmi.product.name: 20F5S2BL00 dmi.product.sku: LENOVO_MT_20F5_BU_Think_FM_ThinkPad X260 dmi.product.version: ThinkPad X260 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati
[Touch-packages] [Bug 1954762] Re: When selecting or navigating text with CTRL + LEFT ARROW or RIGHT, or even just mouse clicking within text, the cursor jumps backwards and forwards erratically
Thanks for the bug report. Which apps are affected? ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete ** Tags added: impish -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1954762 Title: When selecting or navigating text with CTRL + LEFT ARROW or RIGHT, or even just mouse clicking within text, the cursor jumps backwards and forwards erratically Status in Ubuntu: Incomplete Bug description: This started happening recently. Perhaps after a kernel update. I'm now on Ubuntu 21.10, running kernel Linux 5.13.0-22-generic, on a Huawei Matebook Pro X (2020). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1954762/+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 288964] Re: sudo does not work with unbinding usb interface from usbhid driver
ALinuxUser, Xiaofan Chen's example was unbinding the usbhid driver via the /sys/bus/usb/drivers/usbhid/unbind control file -- yours is using /sys/bus/usb/drivers/usb/unbind instead. You probably have to use the control file that corresponds to the driver your device is using. (Check lsusb -t output.) Thanks -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/288964 Title: sudo does not work with unbinding usb interface from usbhid driver Status in sudo package in Ubuntu: Invalid Bug description: I was looking for a way to dump the HID report descriptor under Linux. For that purpose, I need to detach the kernel usbhid driver from the HID interfaces. More detail in libusb mailing list archive. http://www.nabble.com/How-to-dump-HID-report-descriptor-under-Linux-td19609562.html mcuee@Ubuntu804:~$ uname -a Linux Ubuntu804 2.6.24-21-generic #1 SMP Mon Aug 25 17:32:09 UTC 2008 i686 GNU/Linux mcuee@Ubuntu804:/sys/bus/usb/drivers/usbhid$ lsusb Bus 001 Device 007: ID 04f2:0760 Chicony Electronics Co., Ltd Bus 001 Device 006: ID :0005 Bus 001 Device 005: ID 046d:c054 Logitech, Inc. Bus 001 Device 004: ID 14c0:0008 Bus 001 Device 003: ID 1947:0033 Bus 001 Device 002: ID 058f:9360 Alcor Micro Corp. 8-in-1 Media Card Reader Bus 001 Device 001: ID : Bus 002 Device 001: ID : mcuee@Ubuntu804:/sys/bus/usb/drivers/usbhid$ ls 1-3:1.0 1-5:1.0 1-7:1.0 1-7:1.1 bind module new_id uevent unbind So far so good. But then there is error thereafter. Maybe this is a Ubuntu specific problem. mcuee@Ubuntu804:/sys/bus/usb/drivers/usbhid$ sudo echo -n 1-7:1.0 >unbind bash: unbind: Permission denied mcuee@Ubuntu804:/sys/bus/usb/drivers/usbhid$ sudo echo -n 1-7:1.1 >unbind bash: unbind: Permission denied It turns out that I need to enable root to be able to do the job. mcuee@Ubuntu804:/sys/bus/usb/drivers/usbhid$ sudo passwd root [sudo] password for mcuee: Enter new UNIX password: Retype new UNIX password: passwd: password updated successfully mcuee@Ubuntu804:/sys/bus/usb/drivers/usbhid$ ls 1-3:1.0 1-5:1.0 1-7:1.0 1-7:1.1 bind module new_id uevent unbind mcuee@Ubuntu804:/sys/bus/usb/drivers/usbhid$ su - Password: root@Ubuntu804:~# cd /sys/bus/usb/drivers/usbhid/ root@Ubuntu804:/sys/bus/usb/drivers/usbhid# ls 1-3:1.0 1-5:1.0 1-7:1.0 1-7:1.1 bind module new_id uevent unbind root@Ubuntu804:/sys/bus/usb/drivers/usbhid# echo -n 1-7:1.0 >unbind root@Ubuntu804:/sys/bus/usb/drivers/usbhid# echo -n 1-7:1.1 >unbind To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/288964/+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 1954843] Re: amdgpu_bl0: Failed to write system 'brightness' attribute: Invalid argument
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1954843 Title: amdgpu_bl0: Failed to write system 'brightness' attribute: Invalid argument Status in xorg package in Ubuntu: New Bug description: Ubuntu 21.10 does not succeed at setting the display brightness after booting (either to the GNOME login screen or to a logged-in user's desktop). The brightness is at its highest level until I adjust it with keyboard shortcuts or a GUI tool. The systemd-backlight@backlight:amdgpu_bl0 service seems to fail during startup, but I can subsequently run it after startup and it succeeds (and restores brightness): mdmower@T14S ~ $ sudo systemctl status systemd-backlight@backlight:amdgpu_bl0 [sudo] password for mdmower: × systemd-backlight@backlight:amdgpu_bl0.service - Load/Save Screen Backlight Brightness of backlight:amdgpu_bl0 Loaded: loaded (/lib/systemd/system/systemd-backlight@.service; static) Active: failed (Result: exit-code) since Tue 2021-12-14 13:26:05 PST; 30s ago Docs: man:systemd-backlight@.service(8) Process: 962 ExecStart=/lib/systemd/systemd-backlight load backlight:amdgpu_bl0 (code=exited, status=1/FAILURE) Main PID: 962 (code=exited, status=1/FAILURE) CPU: 3ms Dec 14 13:26:05 T14S systemd[1]: Starting Load/Save Screen Backlight Brightness of backlight:amdgpu_bl0... Dec 14 13:26:05 T14S systemd-backlight[962]: amdgpu_bl0: Failed to write system 'brightness' attribute: Invalid argument Dec 14 13:26:05 T14S systemd[1]: systemd-backlight@backlight:amdgpu_bl0.service: Main process exited, code=exited, status=1/FAILURE Dec 14 13:26:05 T14S systemd[1]: systemd-backlight@backlight:amdgpu_bl0.service: Failed with result 'exit-code'. Dec 14 13:26:05 T14S systemd[1]: Failed to start Load/Save Screen Backlight Brightness of backlight:amdgpu_bl0. mdmower@T14S ~ $ sudo systemctl start systemd- backlight@backlight:amdgpu_bl0 mdmower@T14S ~ $ sudo systemctl status systemd-backlight@backlight:amdgpu_bl0 ● systemd-backlight@backlight:amdgpu_bl0.service - Load/Save Screen Backlight Brightness of backlight:amdgpu_bl0 Loaded: loaded (/lib/systemd/system/systemd-backlight@.service; static) Active: active (exited) since Tue 2021-12-14 13:26:45 PST; 1s ago Docs: man:systemd-backlight@.service(8) Process: 5119 ExecStart=/lib/systemd/systemd-backlight load backlight:amdgpu_bl0 (code=exited, status=0/SUCCESS) Main PID: 5119 (code=exited, status=0/SUCCESS) CPU: 5ms Dec 14 13:26:45 T14S systemd[1]: Starting Load/Save Screen Backlight Brightness of backlight:amdgpu_bl0... Dec 14 13:26:45 T14S systemd[1]: Finished Load/Save Screen Backlight Brightness of backlight:amdgpu_bl0. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Dec 14 13:29:38 2021 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev d1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Cezanne [17aa:5095] InstallationDate: Installed on 2021-12-12 (2 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 20XF004WUS ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=859a72cc-a3fe-470f-b525-37b151408289 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.14 dmi.bios.vendor: LENOVO dmi.bios.version: R1NET44W (1.14) dmi.board.asset.tag: Not Available dmi.board.name: 20XF004WUS 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:bvrR1NET44W(1.14):bd11/08/2021:br1.14:efr1.14:svnLENOVO:pn20XF004WUS:pvrThinkPadT14sGen2a:rvnLENOVO:rn20XF004WUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XF_BU_Think_FM_ThinkPadT14sGen2a: dmi.product.family: ThinkPad T14s Gen 2a dmi.product.name: 20XF004WUS dmi.product.sku: LENOVO_MT_20XF_BU_Think_FM_ThinkPad T14s Gen 2a dmi.product.version: ThinkPad T14s Gen 2a dmi.sys.vendor: LENOVO
[Touch-packages] [Bug 1954843] [NEW] amdgpu_bl0: Failed to write system 'brightness' attribute: Invalid argument
You have been subscribed to a public bug: Ubuntu 21.10 does not succeed at setting the display brightness after booting (either to the GNOME login screen or to a logged-in user's desktop). The brightness is at its highest level until I adjust it with keyboard shortcuts or a GUI tool. The systemd-backlight@backlight:amdgpu_bl0 service seems to fail during startup, but I can subsequently run it after startup and it succeeds (and restores brightness): mdmower@T14S ~ $ sudo systemctl status systemd-backlight@backlight:amdgpu_bl0 [sudo] password for mdmower: × systemd-backlight@backlight:amdgpu_bl0.service - Load/Save Screen Backlight Brightness of backlight:amdgpu_bl0 Loaded: loaded (/lib/systemd/system/systemd-backlight@.service; static) Active: failed (Result: exit-code) since Tue 2021-12-14 13:26:05 PST; 30s ago Docs: man:systemd-backlight@.service(8) Process: 962 ExecStart=/lib/systemd/systemd-backlight load backlight:amdgpu_bl0 (code=exited, status=1/FAILURE) Main PID: 962 (code=exited, status=1/FAILURE) CPU: 3ms Dec 14 13:26:05 T14S systemd[1]: Starting Load/Save Screen Backlight Brightness of backlight:amdgpu_bl0... Dec 14 13:26:05 T14S systemd-backlight[962]: amdgpu_bl0: Failed to write system 'brightness' attribute: Invalid argument Dec 14 13:26:05 T14S systemd[1]: systemd-backlight@backlight:amdgpu_bl0.service: Main process exited, code=exited, status=1/FAILURE Dec 14 13:26:05 T14S systemd[1]: systemd-backlight@backlight:amdgpu_bl0.service: Failed with result 'exit-code'. Dec 14 13:26:05 T14S systemd[1]: Failed to start Load/Save Screen Backlight Brightness of backlight:amdgpu_bl0. mdmower@T14S ~ $ sudo systemctl start systemd- backlight@backlight:amdgpu_bl0 mdmower@T14S ~ $ sudo systemctl status systemd-backlight@backlight:amdgpu_bl0 ● systemd-backlight@backlight:amdgpu_bl0.service - Load/Save Screen Backlight Brightness of backlight:amdgpu_bl0 Loaded: loaded (/lib/systemd/system/systemd-backlight@.service; static) Active: active (exited) since Tue 2021-12-14 13:26:45 PST; 1s ago Docs: man:systemd-backlight@.service(8) Process: 5119 ExecStart=/lib/systemd/systemd-backlight load backlight:amdgpu_bl0 (code=exited, status=0/SUCCESS) Main PID: 5119 (code=exited, status=0/SUCCESS) CPU: 5ms Dec 14 13:26:45 T14S systemd[1]: Starting Load/Save Screen Backlight Brightness of backlight:amdgpu_bl0... Dec 14 13:26:45 T14S systemd[1]: Finished Load/Save Screen Backlight Brightness of backlight:amdgpu_bl0. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Dec 14 13:29:38 2021 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev d1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Cezanne [17aa:5095] InstallationDate: Installed on 2021-12-12 (2 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 20XF004WUS ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=859a72cc-a3fe-470f-b525-37b151408289 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.14 dmi.bios.vendor: LENOVO dmi.bios.version: R1NET44W (1.14) dmi.board.asset.tag: Not Available dmi.board.name: 20XF004WUS 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:bvrR1NET44W(1.14):bd11/08/2021:br1.14:efr1.14:svnLENOVO:pn20XF004WUS:pvrThinkPadT14sGen2a:rvnLENOVO:rn20XF004WUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XF_BU_Think_FM_ThinkPadT14sGen2a: dmi.product.family: ThinkPad T14s Gen 2a dmi.product.name: 20XF004WUS dmi.product.sku: LENOVO_MT_20XF_BU_Think_FM_ThinkPad T14s Gen 2a dmi.product.version: ThinkPad T14s Gen 2a dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2
[Touch-packages] [Bug 1954742] Re: Sound starts delayed (4sec) when using HDMI audio
Thank you (especially for the direct link)! https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1305 (btw: Would be nice, if ubuntu-bug or launchpad could propose upstream reporting when trying to create an issue.) ** Bug watch added: gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues #1305 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1305 -- 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/1954742 Title: Sound starts delayed (4sec) when using HDMI audio Status in pulseaudio package in Ubuntu: New Bug description: Reproduce: - Connect notebook to external monitor via HDMI - Start random video in youtube / vlc player Actual: - Sound starts with about 4secs of delay Reproducible: always Misc: The package is just a guess. lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 apt-cache policy pulseaudio pulseaudio: Installed: 1:15.0+dfsg1-1ubuntu2.2 Candidate: 1:15.0+dfsg1-1ubuntu2.2 Version table: *** 1:15.0+dfsg1-1ubuntu2.2 1 (phased 20%) 500 http://archive.ubuntu.com/ubuntu impish-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu impish-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1:15.0+dfsg1-1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu impish/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2 ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19 Uname: Linux 5.13.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nimono 2373 F pulseaudio /dev/snd/pcmC0D3p: nimono 2373 F...m pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Tue Dec 14 15:20:56 2021 SourcePackage: pulseaudio UpgradeStatus: Upgraded to impish on 2021-12-08 (6 days ago) dmi.bios.date: 01/23/2018 dmi.bios.release: 1.7 dmi.bios.vendor: FUJITSU // Insyde Software Corp. dmi.bios.version: Version 1.07 dmi.board.name: FJNB2BB dmi.board.vendor: FUJITSU dmi.board.version: A2 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//InsydeSoftwareCorp.:bvrVersion1.07:bd01/23/2018:br1.7:svnFUJITSU:pnFMVWB3U27:pvr:rvnFUJITSU:rnFJNB2BB:rvrA2:cvnFUJITSU:ct10:cvr:sku: dmi.product.family: LIFEBOOK-JR dmi.product.name: FMVWB3U27 dmi.sys.vendor: FUJITSU modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2021-12-08T10:02:48.239277 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1954742/+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 1927192] Re: gdb ftbfs on armhf, testsuite timeouts
The gdb upload looks fine; I presume it wants to be marked block- proposed, though? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1927192 Title: gdb ftbfs on armhf, testsuite timeouts Status in gdb: Incomplete Status in gdb package in Ubuntu: Fix Released Status in glibc package in Ubuntu: Fix Released Status in gdb source package in Focal: Fix Committed Status in glibc source package in Focal: Fix Committed Status in gdb source package in Groovy: Won't Fix Status in glibc source package in Groovy: Won't Fix Status in gdb source package in Hirsute: Won't Fix Status in glibc source package in Hirsute: Won't Fix Status in gdb source package in Impish: Fix Released Status in glibc source package in Impish: Fix Released Bug description: [Impact] * Gdb can't set some breakpoints in ld.so on armhf when libc6-dbg is not installed. [Test Plan] * Check that ld.so is not stripped on armhf: $ /lib/*/ld-2.31.so libc6/lib/arm-linux-gnueabihf/ld-2.31.so: ELF 32-bit LSB shared object, ARM, EABI5 version 1 (SYSV), dynamically linked, BuildID[sha1]=e20a43bff0c4d2aa7f508c93eadad973ea0c0af9, with debug_info, not stripped * Check that ld.so is stripped on amd64: $ file /lib/x86_64-linux-gnu/ld-2.31.so /lib/x86_64-linux-gnu/ld-2.31.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=ea85fcb25ee4c4c9e7b180924ab4a44257a9547a, stripped [Where problems could occur] * The fix is not stripping ld.so on armhf. Not stripping it comes with a notable increase in file size and it may be performance critical 109K stripped vs 1.3M unstripped. Accidentally ld.so could be left unstripped on other architectures, but the test plan covers checking that, at least on amd64. Other than those not stripping ld.so should not cause any issue. [Original Bug Text] see https://launchpad.net/ubuntu/+source/gdb/10.2-0ubuntu3 $ zcat buildlog_ubuntu-impish-armhf.gdb_10.2-0ubuntu3_BUILDING.txt.gz | fgrep '(timeout)'|wc -l 10451 To manage notifications about this bug go to: https://bugs.launchpad.net/gdb/+bug/1927192/+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 1927192] Re: gdb ftbfs on armhf, testsuite timeouts
Hello Matthias, or anyone else affected, Accepted gdb into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gdb/9.2-0ubuntu1~20.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gdb (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1927192 Title: gdb ftbfs on armhf, testsuite timeouts Status in gdb: Incomplete Status in gdb package in Ubuntu: Fix Released Status in glibc package in Ubuntu: Fix Released Status in gdb source package in Focal: Fix Committed Status in glibc source package in Focal: Fix Committed Status in gdb source package in Groovy: Won't Fix Status in glibc source package in Groovy: Won't Fix Status in gdb source package in Hirsute: Won't Fix Status in glibc source package in Hirsute: Won't Fix Status in gdb source package in Impish: Fix Released Status in glibc source package in Impish: Fix Released Bug description: [Impact] * Gdb can't set some breakpoints in ld.so on armhf when libc6-dbg is not installed. [Test Plan] * Check that ld.so is not stripped on armhf: $ /lib/*/ld-2.31.so libc6/lib/arm-linux-gnueabihf/ld-2.31.so: ELF 32-bit LSB shared object, ARM, EABI5 version 1 (SYSV), dynamically linked, BuildID[sha1]=e20a43bff0c4d2aa7f508c93eadad973ea0c0af9, with debug_info, not stripped * Check that ld.so is stripped on amd64: $ file /lib/x86_64-linux-gnu/ld-2.31.so /lib/x86_64-linux-gnu/ld-2.31.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=ea85fcb25ee4c4c9e7b180924ab4a44257a9547a, stripped [Where problems could occur] * The fix is not stripping ld.so on armhf. Not stripping it comes with a notable increase in file size and it may be performance critical 109K stripped vs 1.3M unstripped. Accidentally ld.so could be left unstripped on other architectures, but the test plan covers checking that, at least on amd64. Other than those not stripping ld.so should not cause any issue. [Original Bug Text] see https://launchpad.net/ubuntu/+source/gdb/10.2-0ubuntu3 $ zcat buildlog_ubuntu-impish-armhf.gdb_10.2-0ubuntu3_BUILDING.txt.gz | fgrep '(timeout)'|wc -l 10451 To manage notifications about this bug go to: https://bugs.launchpad.net/gdb/+bug/1927192/+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 1954348] Re: sed 4.8-1 needs patch disabling non-portable tests
I uploaded this after modifying the debian/changelog to reference the bug number and running update-maintainer. $ dput sed_4.8-1ubuntu1_source.changes Trying to upload package to ubuntu Checking signature on .changes gpg: /tmp/pkgs/jammy/sed_4.8-1ubuntu1_source.changes: Valid signature from 1E918B66765B3E31 Checking signature on .dsc gpg: /tmp/pkgs/jammy/sed_4.8-1ubuntu1.dsc: Valid signature from 1E918B66765B3E31 Uploading to ubuntu (via ftp to upload.ubuntu.com): Uploading sed_4.8-1ubuntu1.dsc: done. Uploading sed_4.8-1ubuntu1.debian.tar.xz: done. Uploading sed_4.8-1ubuntu1_source.buildinfo: done. Uploading sed_4.8-1ubuntu1_source.changes: done. Successfully uploaded packages. ** Changed in: sed (Ubuntu) Status: New => In Progress ** Changed in: sed (Ubuntu) Assignee: (unassigned) => Dave Jones (waveform) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sed in Ubuntu. https://bugs.launchpad.net/bugs/1954348 Title: sed 4.8-1 needs patch disabling non-portable tests Status in sed package in Ubuntu: In Progress Bug description: The sed 4.8-1 package currently in proposed is failing to migrate due to a failing test on armhf. The patch added in 4.7-1ubuntu1 is still required to work around this, and the attached debdiff restores this. The patch has been applied upstream to gnulib (https://git.savannah.gnu.org/cgit/gnulib.git/commit/?id=175e0bc72808d564074c4adcc72aeadb74adfcc6) but sed upstream has not yet bumped the version of gnulib that it vendors in (or more precisely has not made a release since bumping its version of gnulib; 4.8 predates that). The patch itself simply disables the non-portable tests which is not exactly ideal, but given it's what upstream's gone with we ought to follow suit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sed/+bug/1954348/+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 1949075] Re: Bluetooth headset not autoconnecting on power-on on 21.10
** Tags added: champagne rls-ii-incoming -- 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/1949075 Title: Bluetooth headset not autoconnecting on power-on on 21.10 Status in bluez package in Ubuntu: New Bug description: After moving to Impish, my bluetooth headset doesn't automatically connect when I power it on (it was working fine on hirsute). When I go to the bluetooth settings, select it and click connect, the first time it disconnects immediately and I see this line in bluetoothd log: Oct 28 13:57:11 arrakis bluetoothd[1106]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down After that, clicking the connect button again makes it work. I'm not sure where to find info to debug this furhter ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Oct 28 13:57:34 2021 InstallationDate: Installed on 2021-10-16 (11 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20F6CTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-19-generic root=/dev/mapper/ubuntu-root ro rootflags=subvol=@ quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2019 dmi.bios.release: 1.44 dmi.bios.vendor: LENOVO dmi.bios.version: R02ET71W (1.44 ) dmi.board.asset.tag: Not Available dmi.board.name: 20F6CTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.12 dmi.modalias: dmi:bvnLENOVO:bvrR02ET71W(1.44):bd05/08/2019:br1.44:efr1.12:svnLENOVO:pn20F6CTO1WW:pvrThinkPadX260:skuLENOVO_MT_20F6_BU_Think_FM_ThinkPadX260:rvnLENOVO:rn20F6CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X260 dmi.product.name: 20F6CTO1WW dmi.product.sku: LENOVO_MT_20F6_BU_Think_FM_ThinkPad X260 dmi.product.version: ThinkPad X260 dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: E4:A7:A0:01:19:D5 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:56756 acl:285 sco:0 events:6453 errors:0 TX bytes:3721263 acl:3477 sco:0 commands:2751 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1949075/+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 1954840] [NEW] Unabke to set Display to max resolution supported by Monitor and laptop
Public bug reported: Hi, my secondary display support 2560*1440 but 'Display' in Ubuntu is presenting a max resolution of 2048*1080. The max resolution was working yesterday, I think I performed a update today and it has stopped working after that. Thanks, Jerry, ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Dec 14 19:52:57 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:504a] InstallationDate: Installed on 2021-04-16 (242 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20F5S2BL00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-41-generic root=UUID=5cb08771-ead9-4f2c-9550-4125931d1f4a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/09/2019 dmi.bios.release: 1.45 dmi.bios.vendor: LENOVO dmi.bios.version: R02ET72W (1.45 ) dmi.board.asset.tag: Not Available dmi.board.name: 20F5S2BL00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 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.15 dmi.modalias: dmi:bvnLENOVO:bvrR02ET72W(1.45):bd10/09/2019:br1.45:efr1.15:svnLENOVO:pn20F5S2BL00:pvrThinkPadX260:skuLENOVO_MT_20F5_BU_Think_FM_ThinkPadX260:rvnLENOVO:rn20F5S2BL00:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X260 dmi.product.name: 20F5S2BL00 dmi.product.sku: LENOVO_MT_20F5_BU_Think_FM_ThinkPad X260 dmi.product.version: ThinkPad X260 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1954840 Title: Unabke to set Display to max resolution supported by Monitor and laptop Status in xorg package in Ubuntu: New Bug description: Hi, my secondary display support 2560*1440 but 'Display' in Ubuntu is presenting a max resolution of 2048*1080. The max resolution was working yesterday, I think I performed a update today and it has stopped working after that. Thanks, Jerry, ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Dec 14 19:52:57 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:504a] InstallationDate: Installed on 2021-04-16 (242 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20F5S2BL00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-41-generic root=UUID=5cb08771-ead9-4f2c-9550-4125931d1f4a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/09/2019 dmi.bios.release: 1.45 dmi.bios.vendor: LENOVO dmi.bios.version: R02ET72W (1.45 ) dmi.board.asset.tag: Not Available dmi.board.name: 20F5S2BL00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None
[Touch-packages] [Bug 1950193] Please test proposed package
Hello Robert, or anyone else affected, Accepted qtbase-opensource-src into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/qtbase-opensource- src/5.12.8+dfsg-0ubuntu2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1950193 Title: libqt5svg5 affected by CVE-2021-38593 Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in qtbase-opensource-src source package in Focal: Fix Committed Status in qtbase-opensource-src source package in Impish: Fix Committed Bug description: [Impact] libqt5svg5 5.12.8-0ubuntu1 in Ubuntu 20.04 is affected by CVE-2021-38593: https://nvd.nist.gov/vuln/detail/CVE-2021-38593 Trying to open the attached svg file will block one core at 100% and occupy much memory. Depending on the configuration, it might even run out of memory and crash. This is fixed upstream by: https://codereview.qt-project.org/c/qt/qtbase/+/377942 The original issue is public since July 29th. [Test Plan] 1. Install libqt5svg5-dev, qtbase5-dev and their dependencies. 2. Build the attached project with the system's version of Qt: /usr/lib/qt5/bin/qmake test-2021-38593.pro && make 3. Start the resulting binary and pass the path to the included input file as first parameter: ./test-2021-38593 ./input.svg The binary should return immediately and without error messages. If it doesn't, you might be affected. [Where problems could occur] The fix tries to skip drawing dashes that would be invisible anyway. So a potential problem may that it skips too much. In fact, this has already happened, and upstream had to adjust the fix. [Other Info] The patch is a combination of the following upstream commits: - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=7f345f2a1c8d9f60 - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=9378ba2ae857df7e - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=81998f50d039a631 - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=cca8ed0547405b1c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1950193/+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 1950193] Re: libqt5svg5 affected by CVE-2021-38593
Hello Robert, or anyone else affected, Accepted qtbase-opensource-src into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/qtbase-opensource- src/5.15.2+dfsg-12ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- impish to verification-done-impish. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-impish. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: qtbase-opensource-src (Ubuntu Impish) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-impish ** Changed in: qtbase-opensource-src (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1950193 Title: libqt5svg5 affected by CVE-2021-38593 Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in qtbase-opensource-src source package in Focal: Fix Committed Status in qtbase-opensource-src source package in Impish: Fix Committed Bug description: [Impact] libqt5svg5 5.12.8-0ubuntu1 in Ubuntu 20.04 is affected by CVE-2021-38593: https://nvd.nist.gov/vuln/detail/CVE-2021-38593 Trying to open the attached svg file will block one core at 100% and occupy much memory. Depending on the configuration, it might even run out of memory and crash. This is fixed upstream by: https://codereview.qt-project.org/c/qt/qtbase/+/377942 The original issue is public since July 29th. [Test Plan] 1. Install libqt5svg5-dev, qtbase5-dev and their dependencies. 2. Build the attached project with the system's version of Qt: /usr/lib/qt5/bin/qmake test-2021-38593.pro && make 3. Start the resulting binary and pass the path to the included input file as first parameter: ./test-2021-38593 ./input.svg The binary should return immediately and without error messages. If it doesn't, you might be affected. [Where problems could occur] The fix tries to skip drawing dashes that would be invisible anyway. So a potential problem may that it skips too much. In fact, this has already happened, and upstream had to adjust the fix. [Other Info] The patch is a combination of the following upstream commits: - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=7f345f2a1c8d9f60 - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=9378ba2ae857df7e - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=81998f50d039a631 - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=cca8ed0547405b1c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1950193/+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 1950193] Re: libqt5svg5 affected by CVE-2021-38593
** Also affects: qtbase-opensource-src (Ubuntu Impish) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1950193 Title: libqt5svg5 affected by CVE-2021-38593 Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in qtbase-opensource-src source package in Focal: New Status in qtbase-opensource-src source package in Impish: New Bug description: [Impact] libqt5svg5 5.12.8-0ubuntu1 in Ubuntu 20.04 is affected by CVE-2021-38593: https://nvd.nist.gov/vuln/detail/CVE-2021-38593 Trying to open the attached svg file will block one core at 100% and occupy much memory. Depending on the configuration, it might even run out of memory and crash. This is fixed upstream by: https://codereview.qt-project.org/c/qt/qtbase/+/377942 The original issue is public since July 29th. [Test Plan] 1. Install libqt5svg5-dev, qtbase5-dev and their dependencies. 2. Build the attached project with the system's version of Qt: /usr/lib/qt5/bin/qmake test-2021-38593.pro && make 3. Start the resulting binary and pass the path to the included input file as first parameter: ./test-2021-38593 ./input.svg The binary should return immediately and without error messages. If it doesn't, you might be affected. [Where problems could occur] The fix tries to skip drawing dashes that would be invisible anyway. So a potential problem may that it skips too much. In fact, this has already happened, and upstream had to adjust the fix. [Other Info] The patch is a combination of the following upstream commits: - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=7f345f2a1c8d9f60 - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=9378ba2ae857df7e - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=81998f50d039a631 - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=cca8ed0547405b1c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1950193/+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 1949553] Re: Backport packages for 20.04.4 HWE stack
This bug was fixed in the package xorg-server - 2:1.20.13-1ubuntu1~20.04.2 --- xorg-server (2:1.20.13-1ubuntu1~20.04.2) focal-security; urgency=medium * SECURITY UPDATE: SProcRenderCompositeGlyphs out-of-bounds access - debian/patches/CVE-2021-4008.patch: check lengths in render/render.c. - CVE-2021-4008 * SECURITY UPDATE: SProcXFixesCreatePointerBarrier out-of-bounds access - debian/patches/CVE-2021-4009.patch: use sizes in xfixes/cursor.c. - CVE-2021-4009 * SECURITY UPDATE: SProcScreenSaverSuspend out-of-bounds access - debian/patches/CVE-2021-4010.patch: fix logic in Xext/saver.c. - CVE-2021-4010 * SECURITY UPDATE: SwapCreateRegister out-of-bounds access - debian/patches/CVE-2021-4011.patch: fix length in record/record.c. - CVE-2021-4011 -- Marc Deslauriers Tue, 14 Dec 2021 09:14:13 -0500 ** Changed in: xorg-server (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-4008 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-4009 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-4010 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-4011 -- 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/1949553 Title: Backport packages for 20.04.4 HWE stack Status in libdrm package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in libdrm source package in Focal: Fix Committed Status in mesa source package in Focal: In Progress Status in xorg-server source package in Focal: Fix Released Bug description: [Impact] These are needed for 20.04.4 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. [What could go wrong] libdrm: adds some new api, no changes to old stuff llvm-13: a new package, no regression potential on it's own mesa: a new major release, but we'll pull the final stable release of 21.2.x series, so there shouldn't be any regressions left at that point xserver: a new point-release, 1.20.x series is in deep maintenance mode, so there should be little chance of breakage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1949553/+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 1650688] Re: timedatectl set-timezone fails on UC16
Test result on Focal (245.4-4ubuntu3.14): - Normal environment: Tested on my desktop. timedatectl output is correct. Setting the timezone works, and doesn't put the link inside /etc/writable/. - System-image environment (UBports image): timedatectl output is correct. Setting timezone works; readlink -f /etc/localtime points to an existing file. - Ubuntu Core environment: test with snapcore/core20 commit 2d970050. focal-proposed is enabled and src:systemd is pinned in overlay. timedatectl output is correct. Setting timezone works; readlink -f /etc/localtime points to an existing file. Test result on Bionic (237-3ubuntu10.53): - Normal environment: Tested in an LXD container. timedatectl output is correct. Setting the timezone works, and doesn't put the link inside /etc/writable/. - Ubuntu Core environment: test with snapcore/core18 commit b8ad5ed4. bionic-proposed is enabled and src:systemd is pinned in overlay. timedatectl output is correct. Setting timezone works; readlink -f /etc/localtime points to an existing file. - System-image enviroment: We at UBports doesn't have a port of Ubuntu Touch based on Bionic, and as such I cannot test in this environment. Note: in Ubuntu Core environments, timedatectl.real is used to test timedated instead of the wrapper. Note: according to [1], seems like verification-needed* has to be left as-is until another positive testimony appears or the test is done by an SRU verification team member. [1] https://wiki.ubuntu.com/QATeam/PerformingSRUVerification#Updating_the_bug_report -- Oh, BTW, I looked at the autopkgtests failure earlier. One of the failure (can't remember which) was because of an out-of-space error. It seems to be gone by now though. -- 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/1650688 Title: timedatectl set-timezone fails on UC16 Status in Snappy: Triaged Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Focal: Fix Committed Status in systemd source package in Hirsute: Won't Fix Status in systemd source package in Impish: Won't Fix Status in systemd source package in Jammy: Fix Released Bug description: SRU === [Impact] * The bug prevents timedated from recognizing and correctly set the system's timezone when running Ubuntu Core 16, 18 and 20. * This causes by timedated fails to take Ubuntu Core's /etc/writable redirection into account. * The recognizing part is fixed by making the code take writable redirection into account. * The set part is fixed by making the code link to the absolute path instead of a relative one. * Currently core snaps worked around the set part by providing a wrapper script which re-create /etc/writable/localtime afterward. However this does not cover DBus users. [Test Plan] * On classics systems: ensure the proposed systemd package is installed. On Ubuntu Core systems: build a new core snap including proposed package, and install it. Replaces timedatectl with timedatectl.real to test skipping the wrapper. (Note that one can simulate core snap's /etc/writable redirection by running this image creation hook [1] on the system.) [1] https://git.launchpad.net/livecd-rootfs/tree/live-build/ubuntu- core/hooks/08-etc-writable.chroot?h=ubuntu/focal * On freshly boot system: query the timezone using `timedatectl`. The timezone should corresponds to `readlink -f /etc/localtime` and does not show `n/a`. * Set a new timezone: `sudo timedatectl set-timezone Asia/Bangkok`. `readlink -f /etc/localtime` should points to an existing file. * Run `sudo systemctl restart systemd-timedated.service`. Then, query the timezone again: `timedatectl`. It should show the previously set timezone and not `n/a`. * Run `sudo systemctl status systemd-timedated.service`. This should show no sign of timedated crashing. [Where problems could occur] * It's possible that the redirection handling code will be sub-par and causes crash. However, it's not likely because the similar pieces of code is in the previous patch since Ubuntu 16.04. * If it does: the patched `get_timezone()` function is used in 2 places: the networkd's DHCP server [3] and the timedated itself. - Networkd is used primarily on servers where NetworkManage is absent. It's possible that this patch causes the user to loss access to the server due to networkd crash when setting up network interfaces, and requires physical access to fix. However, the code path is executed when DHCP is enabled only. I think it's not common for users to have networkd's DHCP server enabled: the feature seems to gear towards desktop users wanting to share internet connection, and in those cases they're more likely to use NetworkManager. -
[Touch-packages] [Bug 1950193] Re: libqt5svg5 affected by CVE-2021-38593
Does this also need fixing in impish? I'm not very concerned about hirsute given it will be EoL in January. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1950193 Title: libqt5svg5 affected by CVE-2021-38593 Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in qtbase-opensource-src source package in Focal: New Bug description: [Impact] libqt5svg5 5.12.8-0ubuntu1 in Ubuntu 20.04 is affected by CVE-2021-38593: https://nvd.nist.gov/vuln/detail/CVE-2021-38593 Trying to open the attached svg file will block one core at 100% and occupy much memory. Depending on the configuration, it might even run out of memory and crash. This is fixed upstream by: https://codereview.qt-project.org/c/qt/qtbase/+/377942 The original issue is public since July 29th. [Test Plan] 1. Install libqt5svg5-dev, qtbase5-dev and their dependencies. 2. Build the attached project with the system's version of Qt: /usr/lib/qt5/bin/qmake test-2021-38593.pro && make 3. Start the resulting binary and pass the path to the included input file as first parameter: ./test-2021-38593 ./input.svg The binary should return immediately and without error messages. If it doesn't, you might be affected. [Where problems could occur] The fix tries to skip drawing dashes that would be invisible anyway. So a potential problem may that it skips too much. In fact, this has already happened, and upstream had to adjust the fix. [Other Info] The patch is a combination of the following upstream commits: - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=7f345f2a1c8d9f60 - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=9378ba2ae857df7e - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=81998f50d039a631 - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=cca8ed0547405b1c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1950193/+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 1954762] Re: When selecting or navigating text with CTRL + LEFT ARROW or RIGHT, or even just mouse clicking within text, the cursor jumps backwards and forwards erratically
On 100% scaling it is certainly less noticeable, though the cursor sometimes appears slightly moved to the right of where it actually is. The screen resolution I am using is (and always has been) 3000x2000. Maybe it has something to do with this less common screen ratio. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1954762 Title: When selecting or navigating text with CTRL + LEFT ARROW or RIGHT, or even just mouse clicking within text, the cursor jumps backwards and forwards erratically Status in xorg package in Ubuntu: New Bug description: This started happening recently. Perhaps after a kernel update. I'm now on Ubuntu 21.10, running kernel Linux 5.13.0-22-generic, on a Huawei Matebook Pro X (2020). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1954762/+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 1954814] [NEW] systemd.resolved with split domains sends DNS requests to the wrong interface
Public bug reported: When connected simultaneously to two different networks with overlapping domains $ resolvectl domain Global: Link 3 (wlp0s20f3): ~. mit.edu Link 2 (enp0s31f6): ~. psfc.mit.edu $ resolvectl dns Global: Link 3 (wlp0s20f3): 18.0.70.160 18.0.72.3 18.0.71.151 Link 2 (enp0s31f6): 198.125.177.103 198.125.179.203, a DNS request for resolution of a name such as LIBPROXY.GLB.MIT.EDU is by default sent to the nameservers of Link 3 (e.g. 18.0.70.160) but via Link 2 (enp0s31f6) This request is refused, presumably because it is seen by those nameservers as coming from an external network, which ought not to be asking for name resolution from them. It seems that it ought to be the default behavior that requests for name resolution are sent only over the interface whose nameservers are being queried, or else that queries go only to the nameservers that are associated with the interface over which the query will go out. lsb_release -rd Description:Ubuntu 20.04.3 LTS Release:20.04 $ resolvectl --version systemd 245 (245.4-4ubuntu3.13) +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=hybrid $ systemd --version systemd 245 (245.4-4ubuntu3.13) +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=hybrid $ apt-cache policy systemd systemd: Installed: 245.4-4ubuntu3.13 Candidate: 245.4-4ubuntu3.13 Version table: *** 245.4-4ubuntu3.13 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 245.4-4ubuntu3.11 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 245.4-4ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages ** 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/1954814 Title: systemd.resolved with split domains sends DNS requests to the wrong interface Status in systemd package in Ubuntu: New Bug description: When connected simultaneously to two different networks with overlapping domains $ resolvectl domain Global: Link 3 (wlp0s20f3): ~. mit.edu Link 2 (enp0s31f6): ~. psfc.mit.edu $ resolvectl dns Global: Link 3 (wlp0s20f3): 18.0.70.160 18.0.72.3 18.0.71.151 Link 2 (enp0s31f6): 198.125.177.103 198.125.179.203, a DNS request for resolution of a name such as LIBPROXY.GLB.MIT.EDU is by default sent to the nameservers of Link 3 (e.g. 18.0.70.160) but via Link 2 (enp0s31f6) This request is refused, presumably because it is seen by those nameservers as coming from an external network, which ought not to be asking for name resolution from them. It seems that it ought to be the default behavior that requests for name resolution are sent only over the interface whose nameservers are being queried, or else that queries go only to the nameservers that are associated with the interface over which the query will go out. lsb_release -rd Description:Ubuntu 20.04.3 LTS Release:20.04 $ resolvectl --version systemd 245 (245.4-4ubuntu3.13) +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=hybrid $ systemd --version systemd 245 (245.4-4ubuntu3.13) +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=hybrid $ apt-cache policy systemd systemd: Installed: 245.4-4ubuntu3.13 Candidate: 245.4-4ubuntu3.13 Version table: *** 245.4-4ubuntu3.13 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 245.4-4ubuntu3.11 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 245.4-4ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1954814/+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 1954762] Re: When selecting or navigating text with CTRL + LEFT ARROW or RIGHT, or even just mouse clicking within text, the cursor jumps backwards and forwards erratically
With fractional scaling at 150%, it occurs only after some time. On a fresh reboot it isn't apparent, but it gradually gets worse when manipulating text. It's as if some error accumulates with time. After a while it becomes really annoying when working with text. The cursor position is correct, but often isn't where you see it. The cursor may appear at the end of a word while you are actually editing the beginning of the word. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1954762 Title: When selecting or navigating text with CTRL + LEFT ARROW or RIGHT, or even just mouse clicking within text, the cursor jumps backwards and forwards erratically Status in xorg package in Ubuntu: New Bug description: This started happening recently. Perhaps after a kernel update. I'm now on Ubuntu 21.10, running kernel Linux 5.13.0-22-generic, on a Huawei Matebook Pro X (2020). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1954762/+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 1954762] Re: When selecting or navigating text with CTRL + LEFT ARROW or RIGHT, or even just mouse clicking within text, the cursor jumps backwards and forwards erratically
Have been testing at 100% and 200% scaling - so far the problem hasn't appeared at these scalings, which makes me suspect it is a problem with fractional scaling. It's a new problem, as, about a month ago, there was no such problem with the same fractional scaling - I have always preferred 150% on this system. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1954762 Title: When selecting or navigating text with CTRL + LEFT ARROW or RIGHT, or even just mouse clicking within text, the cursor jumps backwards and forwards erratically Status in xorg package in Ubuntu: New Bug description: This started happening recently. Perhaps after a kernel update. I'm now on Ubuntu 21.10, running kernel Linux 5.13.0-22-generic, on a Huawei Matebook Pro X (2020). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1954762/+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 1954762] Re: When selecting or navigating text with CTRL + LEFT ARROW or RIGHT, or even just mouse clicking within text, the cursor jumps backwards and forwards erratically
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1954762 Title: When selecting or navigating text with CTRL + LEFT ARROW or RIGHT, or even just mouse clicking within text, the cursor jumps backwards and forwards erratically Status in xorg package in Ubuntu: New Bug description: This started happening recently. Perhaps after a kernel update. I'm now on Ubuntu 21.10, running kernel Linux 5.13.0-22-generic, on a Huawei Matebook Pro X (2020). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1954762/+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 1954762] [NEW] When selecting or navigating text with CTRL + LEFT ARROW or RIGHT, or even just mouse clicking within text, the cursor jumps backwards and forwards erratically
You have been subscribed to a public bug: This started happening recently. Perhaps after a kernel update. I'm now on Ubuntu 21.10, running kernel Linux 5.13.0-22-generic, on a Huawei Matebook Pro X (2020). ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment selection text -- When selecting or navigating text with CTRL + LEFT ARROW or RIGHT, or even just mouse clicking within text, the cursor jumps backwards and forwards erratically https://bugs.launchpad.net/bugs/1954762 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- 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 1950214] Re: raspi 64 bit Impish image fails update-initramfs with OOM on zstd
Just to clarify, while gzip may be preferable this shouldn't prevent the lz4 fix from landing. It's a "good enough" workaround for a bug that prevents people from running apt-upgrade (which is far more important than "choice of compression algorithm"). -- 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/1950214 Title: raspi 64 bit Impish image fails update-initramfs with OOM on zstd Status in ubuntu-settings package in Ubuntu: Confirmed Status in ubuntu-settings source package in Impish: Confirmed Status in ubuntu-settings source package in Jammy: Confirmed Bug description: When attempting to 'apt upgrade' on the pi zero 2 with the 64 bit Impish image and nothing new installed to it, update-initramfs fails like so: Setting up linux-firmware (1.201.1) ... update-initramfs: Generating /boot/initrd.img-5.13.0-1008-raspi Killed E: mkinitramfs failure zstd -q -19 -T0 137 A simple workaround for now is to switch to the old lz4 default: $ sudo apt install lz4 $ sudo sed -i -e '/^COMPRESS=/ c COMPRESS=lz4' /etc/initramfs-tools/initramfs.conf Original Workaround === Adding a swap file to the setup allowed 'apt -f install' to run successfully. How the device was setup 1) xzcat | dd the sdcard with the impish 64 bit server image 2) setup for serial over USB (dtoverlay=dwc2, modules-load=dwc2,g_serial, link getty@ttyGS0.service ) as suggested in https://www.tal.org/tutorials/raspberry-pi-zero-usb-serial-console 3) resize partition 2 - fdisk delete partition 2 and recreate to use the rest of the 16GB flash, e2fsck, resize2fs 4) cp bcm2710-rpi-3-b.dtb bcm2710-rpi-zero-2.dtb per https://waldorf.waveform.org.uk/2021/the-pi-zero-2.html 5) boot, connect to wireless, ssh in 6) apt update && apt upgrade 7) observe above issue ProblemType: Package DistroRelease: Ubuntu 21.10 Package: linux-firmware 1.201.1 ProcVersionSignature: Ubuntu 5.13.0-1009.10-raspi 5.13.14 Uname: Linux 5.13.0-1009-raspi aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 8 19:47 seq crw-rw 1 root audio 116, 33 Nov 8 19:47 timer AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.13.0-1009-raspi. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu71 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: unknown Date: Mon Nov 8 21:00:59 2021 Dependencies: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 ImageMediaBuild: 20211013 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lspci-vt: -[:00]- Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc2/1p, 480M PackageArchitecture: all PciMultimedia: ProcFB: 0 BCM2708 FB ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=720 bcm2708_fb.fbheight=480 bcm2708_fb.fbswap=1 smsc95xx.macaddr=B8:27:EB:5C:DA:C8 vc_mem.mem_base=0x1ec0 vc_mem.mem_size=0x2000 dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash modules-load=dwc2,g_serial Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1build1 PythonDetails: N/A RelatedPackageVersions: grub-pc N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux-firmware StagingDrivers: bcm2835_mmal_vchiq snd_bcm2835 bcm2835_isp bcm2835_v4l2 bcm2835_codec vc_sm_cma Title: package linux-firmware 1.201.1 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1950214/+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 1950214] Re: raspi 64 bit Impish image fails update-initramfs with OOM on zstd
Some further research on this [1] suggests gzip may be a preferable choice on the smaller platforms (lower memory usage, and better compression anyway), plus this would alleviate the need for including lz4 in the images. I need to do some further analysis of the decompression to see if it is still suitable there too. [1] https://github.com/waveform80/compression/ -- 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/1950214 Title: raspi 64 bit Impish image fails update-initramfs with OOM on zstd Status in ubuntu-settings package in Ubuntu: Confirmed Status in ubuntu-settings source package in Impish: Confirmed Status in ubuntu-settings source package in Jammy: Confirmed Bug description: When attempting to 'apt upgrade' on the pi zero 2 with the 64 bit Impish image and nothing new installed to it, update-initramfs fails like so: Setting up linux-firmware (1.201.1) ... update-initramfs: Generating /boot/initrd.img-5.13.0-1008-raspi Killed E: mkinitramfs failure zstd -q -19 -T0 137 A simple workaround for now is to switch to the old lz4 default: $ sudo apt install lz4 $ sudo sed -i -e '/^COMPRESS=/ c COMPRESS=lz4' /etc/initramfs-tools/initramfs.conf Original Workaround === Adding a swap file to the setup allowed 'apt -f install' to run successfully. How the device was setup 1) xzcat | dd the sdcard with the impish 64 bit server image 2) setup for serial over USB (dtoverlay=dwc2, modules-load=dwc2,g_serial, link getty@ttyGS0.service ) as suggested in https://www.tal.org/tutorials/raspberry-pi-zero-usb-serial-console 3) resize partition 2 - fdisk delete partition 2 and recreate to use the rest of the 16GB flash, e2fsck, resize2fs 4) cp bcm2710-rpi-3-b.dtb bcm2710-rpi-zero-2.dtb per https://waldorf.waveform.org.uk/2021/the-pi-zero-2.html 5) boot, connect to wireless, ssh in 6) apt update && apt upgrade 7) observe above issue ProblemType: Package DistroRelease: Ubuntu 21.10 Package: linux-firmware 1.201.1 ProcVersionSignature: Ubuntu 5.13.0-1009.10-raspi 5.13.14 Uname: Linux 5.13.0-1009-raspi aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 8 19:47 seq crw-rw 1 root audio 116, 33 Nov 8 19:47 timer AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.13.0-1009-raspi. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu71 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: unknown Date: Mon Nov 8 21:00:59 2021 Dependencies: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 ImageMediaBuild: 20211013 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lspci-vt: -[:00]- Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc2/1p, 480M PackageArchitecture: all PciMultimedia: ProcFB: 0 BCM2708 FB ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=720 bcm2708_fb.fbheight=480 bcm2708_fb.fbswap=1 smsc95xx.macaddr=B8:27:EB:5C:DA:C8 vc_mem.mem_base=0x1ec0 vc_mem.mem_size=0x2000 dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash modules-load=dwc2,g_serial Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1build1 PythonDetails: N/A RelatedPackageVersions: grub-pc N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux-firmware StagingDrivers: bcm2835_mmal_vchiq snd_bcm2835 bcm2835_isp bcm2835_v4l2 bcm2835_codec vc_sm_cma Title: package linux-firmware 1.201.1 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1950214/+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 1952107] Re: Google Contacts API Deprecated
the armhf tests worked after a retry -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1952107 Title: Google Contacts API Deprecated Status in evolution-data-server: Unknown Status in evolution package in Ubuntu: Fix Released Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution source package in Focal: Fix Committed Status in evolution-data-server source package in Focal: Fix Committed Status in evolution source package in Impish: Fix Committed Status in evolution-data-server source package in Impish: Fix Committed Bug description: * Impact The google contacts integration with the GNOME component will stop working since it relies on an API which is going to be shutdown * Testcase - use evolution - add a google account - go the contacts section The contacts stored on the google account should be listed, no error should be displayed * Regression potential The patch changes the google contact backend so any potential issue is likely to be with contacts integration. I opened Evolution today and a red banner appeared on top with the following message: > Failed to connect address book “ : Contacts” > Invalid request URI or header, or unsupported nonstandard parameter: Contacts API is being deprecated. Migrate to People API to retain programmatic access to Google Contacts. See https://developers.google.com/people/contacts-api-migration. I found the upstream bug report for this[0], which references the commit[1] that fixes it. However, that commit is in release 3.42.0, whereas Ubuntu 21.10 currently has 3.40.4-1. Is it possible to backport this commit so that Evolution will continue to work properly? [0]: https://gitlab.gnome.org/GNOME/evolution/-/issues/1658 [1]: https://gitlab.gnome.org/GNOME/evolution-data-server/-/commit/d63a1ce3921a6a6c573a6a To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-data-server/+bug/1952107/+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 1944409] Re: Systemd uses CPU after wakeup due to power_supply BAT0 (battery) continued polling
The issue is first found on other platform during enablement, and the fix is landed in BIOS. Latitude 7520 has no problem with the BIOS version we certified, however, the regression should be caused by BIOS upgrade. Therefore, I assume the latest BIOS should contain fix for it. As I know, the issue should be observed whenever adapter is attached, if you can't see it, the issue should be fixed in the latest BIOS. You can still monitor few days or do whatever experiment you'd like to do, until you think the issue is indeed fixed. Again, thanks for reporting the issue. -- 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/1944409 Title: Systemd uses CPU after wakeup due to power_supply BAT0 (battery) continued polling Status in OEM Priority Project: New Status in systemd package in Ubuntu: Confirmed Bug description: My setup: - Dell Latitude 7520 - Dell WD15 USB C docking station - Ubuntu 20.04.3 - systemd 245.4-4ubuntu3.13 - uname -a: Linux CLIFMI085 5.13.0-1012-oem #16-Ubuntu SMP Tue Sep 7 09:23:08 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux I leave my laptop docked and, after waking it up from sleep, the fans start blowing. After a quick inspection with top/htop, I always see /usr/lib/systemd/systemd-udev consuming 50+% of my CPU. After a quick search, I discover that I can use `udevadm monitor` to check what device is making all this fuss, and this is the output: UDEV [92591.827159] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92591.873819] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92591.920022] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92591.967005] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.018200] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.068351] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.115100] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.166201] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.213318] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.261046] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.308824] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.356577] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.403766] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.451164] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) As you can see, the battery status is being polled every 0.05s. To fix this, I just need to restart the service with: sudo systemctl restart systemd-udevd systemd-udevd-kernel.socket systemd-udevd-control.socket Afterwards, this is the output of `udevadm monitor`: KERNEL[92739.612371] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92739.646888] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) KERNEL[92741.076823] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92741.099370] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) KERNEL[92742.539438] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92742.573812] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) As you can see, the battery is now being polled every ~1.5s, which is fine. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1944409/+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 1913775] Re: Copy from Firefox Wayland fails to be pasted anywhere else
** Changed in: gtk+3.0 (Ubuntu) Assignee: (unassigned) => Sebastien Bacher (seb128) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1913775 Title: Copy from Firefox Wayland fails to be pasted anywhere else Status in GTK+: Unknown Status in firefox package in Ubuntu: Invalid Status in gtk+3.0 package in Ubuntu: Fix Committed Bug description: Running Firefox 84.0.2 for Ubuntu Canonical-1.0 on Ubuntu 20.04.1 LTS, on Wayland native Version 84.0.2 Build ID 20210105180113 Window Protocol wayland Desktop Environment gnome DESCRIPTION OF THE PROBLEM: If I copy text from a web page and try to paste it into another Firefox page, the text is pasted correctly. If I copy text from a web page and try to paste it in [gedit, libreoffice, thunderbird, terminal, slack (electron)] nothing happens. The Gnome Clipboard extension stays empty when content is copied from Firefox Wayland. Pasting *from* another app *to* Firefox works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1913775/+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) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-utils in Ubuntu. https://bugs.launchpad.net/bugs/1953052 Title: In Jammy sound level reset after reboot Status in alsa-utils package in Ubuntu: Confirmed 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 Uname: Linux 5.13.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage
[Touch-packages] [Bug 1913775] Re: Copy from Firefox Wayland fails to be pasted anywhere else
The git change is https://gitlab.gnome.org/GNOME/gtk/-/commit/e23b4dd2 ** Changed in: gtk+3.0 (Ubuntu) Importance: Undecided => High ** Changed in: gtk+3.0 (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1913775 Title: Copy from Firefox Wayland fails to be pasted anywhere else Status in GTK+: Unknown Status in firefox package in Ubuntu: Invalid Status in gtk+3.0 package in Ubuntu: Fix Committed Bug description: Running Firefox 84.0.2 for Ubuntu Canonical-1.0 on Ubuntu 20.04.1 LTS, on Wayland native Version 84.0.2 Build ID 20210105180113 Window Protocol wayland Desktop Environment gnome DESCRIPTION OF THE PROBLEM: If I copy text from a web page and try to paste it into another Firefox page, the text is pasted correctly. If I copy text from a web page and try to paste it in [gedit, libreoffice, thunderbird, terminal, slack (electron)] nothing happens. The Gnome Clipboard extension stays empty when content is copied from Firefox Wayland. Pasting *from* another app *to* Firefox works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1913775/+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 1954742] Re: Sound starts delayed (4sec) when using HDMI audio
Thank you for your bug report, could you perhaps report it directly upstream as well on https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues ? ** Changed in: pulseaudio (Ubuntu) Importance: Undecided => Low -- 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/1954742 Title: Sound starts delayed (4sec) when using HDMI audio Status in pulseaudio package in Ubuntu: New Bug description: Reproduce: - Connect notebook to external monitor via HDMI - Start random video in youtube / vlc player Actual: - Sound starts with about 4secs of delay Reproducible: always Misc: The package is just a guess. lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 apt-cache policy pulseaudio pulseaudio: Installed: 1:15.0+dfsg1-1ubuntu2.2 Candidate: 1:15.0+dfsg1-1ubuntu2.2 Version table: *** 1:15.0+dfsg1-1ubuntu2.2 1 (phased 20%) 500 http://archive.ubuntu.com/ubuntu impish-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu impish-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1:15.0+dfsg1-1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu impish/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2 ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19 Uname: Linux 5.13.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nimono 2373 F pulseaudio /dev/snd/pcmC0D3p: nimono 2373 F...m pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Tue Dec 14 15:20:56 2021 SourcePackage: pulseaudio UpgradeStatus: Upgraded to impish on 2021-12-08 (6 days ago) dmi.bios.date: 01/23/2018 dmi.bios.release: 1.7 dmi.bios.vendor: FUJITSU // Insyde Software Corp. dmi.bios.version: Version 1.07 dmi.board.name: FJNB2BB dmi.board.vendor: FUJITSU dmi.board.version: A2 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//InsydeSoftwareCorp.:bvrVersion1.07:bd01/23/2018:br1.7:svnFUJITSU:pnFMVWB3U27:pvr:rvnFUJITSU:rnFJNB2BB:rvrA2:cvnFUJITSU:ct10:cvr:sku: dmi.product.family: LIFEBOOK-JR dmi.product.name: FMVWB3U27 dmi.sys.vendor: FUJITSU modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2021-12-08T10:02:48.239277 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1954742/+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 1944409] Re: Systemd uses CPU after wakeup due to power_supply BAT0 (battery) continued polling
After first reboot with BIOS 1.12.2 all seems fine, the update seems even to have made the process of hooking up the docking station and activating the external monitors faster. After first sleep and wakeup, no battery pinging that I can see with udevadm monitor, not even at a slow pace (but the battery is more than full). Should I retry during battery recharge? -- 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/1944409 Title: Systemd uses CPU after wakeup due to power_supply BAT0 (battery) continued polling Status in OEM Priority Project: New Status in systemd package in Ubuntu: Confirmed Bug description: My setup: - Dell Latitude 7520 - Dell WD15 USB C docking station - Ubuntu 20.04.3 - systemd 245.4-4ubuntu3.13 - uname -a: Linux CLIFMI085 5.13.0-1012-oem #16-Ubuntu SMP Tue Sep 7 09:23:08 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux I leave my laptop docked and, after waking it up from sleep, the fans start blowing. After a quick inspection with top/htop, I always see /usr/lib/systemd/systemd-udev consuming 50+% of my CPU. After a quick search, I discover that I can use `udevadm monitor` to check what device is making all this fuss, and this is the output: UDEV [92591.827159] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92591.873819] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92591.920022] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92591.967005] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.018200] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.068351] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.115100] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.166201] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.213318] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.261046] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.308824] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.356577] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.403766] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.451164] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) As you can see, the battery status is being polled every 0.05s. To fix this, I just need to restart the service with: sudo systemctl restart systemd-udevd systemd-udevd-kernel.socket systemd-udevd-control.socket Afterwards, this is the output of `udevadm monitor`: KERNEL[92739.612371] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92739.646888] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) KERNEL[92741.076823] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92741.099370] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) KERNEL[92742.539438] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92742.573812] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) As you can see, the battery is now being polled every ~1.5s, which is fine. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1944409/+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 1309404] Re: Hovering mouse over dash-window causes screen-flickering
We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. dash is POSIX-compliant shell similar to bash. Looking at your bug report you probably intended to report your problem against the 'Unity' package. Ubuntu 14.04 (trusty) reached end-of-life on April 25,2019 so I'm closing this bug report as "Invalid". If you are still using Unity as your desktop environment and continue to see this problem then please open a new bug report by running the following command in a terminal: ubuntu-bug unity which will gather relevant information from your current Ubuntu installation. Thank you for helping make Ubuntu better. ** Changed in: dash (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dash in Ubuntu. https://bugs.launchpad.net/bugs/1309404 Title: Hovering mouse over dash-window causes screen-flickering Status in dash package in Ubuntu: Invalid Bug description: Upgrade from 13.10 to 14.04. Open dash and hover with the mouse over the icons => screen flickering and artefacts ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: dash 0.5.7-4ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CurrentDesktop: Unity Date: Fri Apr 18 10:35:11 2014 InstallationDate: Installed on 2012-01-26 (812 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) SourcePackage: dash UpgradeStatus: Upgraded to trusty on 2014-04-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dash/+bug/1309404/+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 1466417] Re: Dash doesn't respect touchpad tap setting
We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. dash is POSIX-compliant shell similar to bash. Looking at your bug report you probably intended to report your problem against the 'Unity' package. Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016 so I'm closing this bug report as "Invalid". If you are still using Unity as your desktop environment and continue to see this problem then please open a new bug report by running the following command in a terminal: ubuntu-bug unity which will gather relevant information from your current Ubuntu installation. Thank you for helping make Ubuntu better. ** Changed in: dash (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dash in Ubuntu. https://bugs.launchpad.net/bugs/1466417 Title: Dash doesn't respect touchpad tap setting Status in dash package in Ubuntu: Invalid Bug description: I prefer clicking to touching and I turn the touch pad tap feature off. But the /dash/ still reacts to multitouch taps. How to reproduce: 1) Turn off the option "Tap to Click" in System Settings -> Mouse and Touchpad (while we're already here: something completely unrelated: there is an option to disable the touchpad even if it is the only pointer input device and it doesn't really work) 2) Open one or two Firefox windows and minimize them 3) Tap onto the Firefox icon with two fingers -> a Firefox window zooms up or shows up again ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: dash 0.5.7-4ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jun 18 11:52:29 2015 InstallationDate: Installed on 2015-06-08 (9 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: dash UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dash/+bug/1466417/+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 1576462] Re: multiple desktops (3x3), hitting super in an empty desktop does not bring up the dash
We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. dash is POSIX-compliant shell similar to bash. Looking at your bug report you probably intended to report your problem against the 'Unity' package. Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021 so I'm closing this bug report as "Invalid". If you are still using Unity as your desktop environment and continue to see this problem then please open a new bug report by running the following command in a terminal: ubuntu-bug unity which will gather relevant information from your current Ubuntu installation. Thank you for helping make Ubuntu better. ** Changed in: dash (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dash in Ubuntu. https://bugs.launchpad.net/bugs/1576462 Title: multiple desktops (3x3), hitting super in an empty desktop does not bring up the dash Status in dash package in Ubuntu: Invalid Bug description: ubuntu 16.04 upgrade install from 15.10 multiple virtual desktops created in a 3x3 matrix In an empty virtual desktop, hitting does not bring up the dash. If another program is already open in a virtual desktop, then hitting dies bring up the dash ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: dash 0.5.8-2.1ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 28 20:58:28 2016 InstallationDate: Installed on 2015-04-26 (368 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: dash UpgradeStatus: Upgraded to xenial on 2016-04-28 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dash/+bug/1576462/+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 1944409] Re: Systemd uses CPU after wakeup due to power_supply BAT0 (battery) continued polling
#7 output was already attached there, just grepped for brevity. The first lines where confusing me though, I've now upgraded the system BIOS from 1.6.1 to 1.12.2. 1.13 seems available on the official site, I'll report back ASAP on the results of the upgrade. -- 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/1944409 Title: Systemd uses CPU after wakeup due to power_supply BAT0 (battery) continued polling Status in OEM Priority Project: New Status in systemd package in Ubuntu: Confirmed Bug description: My setup: - Dell Latitude 7520 - Dell WD15 USB C docking station - Ubuntu 20.04.3 - systemd 245.4-4ubuntu3.13 - uname -a: Linux CLIFMI085 5.13.0-1012-oem #16-Ubuntu SMP Tue Sep 7 09:23:08 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux I leave my laptop docked and, after waking it up from sleep, the fans start blowing. After a quick inspection with top/htop, I always see /usr/lib/systemd/systemd-udev consuming 50+% of my CPU. After a quick search, I discover that I can use `udevadm monitor` to check what device is making all this fuss, and this is the output: UDEV [92591.827159] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92591.873819] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92591.920022] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92591.967005] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.018200] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.068351] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.115100] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.166201] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.213318] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.261046] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.308824] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.356577] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.403766] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.451164] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) As you can see, the battery status is being polled every 0.05s. To fix this, I just need to restart the service with: sudo systemctl restart systemd-udevd systemd-udevd-kernel.socket systemd-udevd-control.socket Afterwards, this is the output of `udevadm monitor`: KERNEL[92739.612371] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92739.646888] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) KERNEL[92741.076823] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92741.099370] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) KERNEL[92742.539438] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92742.573812] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) As you can see, the battery is now being polled every ~1.5s, which is fine. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1944409/+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 1954649] Re: autopkgtest regressions with python3.10 as supported
** Tags added: fr-1927 -- 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/1954649 Title: autopkgtest regressions with python3.10 as supported Status in ipywidgets package in Ubuntu: New Status in pygobject package in Ubuntu: New Status in pytest-twisted package in Ubuntu: New Status in python-b2sdk package in Ubuntu: New Status in python-hypothesis package in Ubuntu: New Status in python-taskflow package in Ubuntu: New Status in python3-defaults package in Ubuntu: New Status in skimage package in Ubuntu: Invalid Status in supysonic package in Ubuntu: New Status in vorta package in Ubuntu: New Status in ipywidgets package in Debian: New Status in pygobject package in Debian: New Status in pytest-twisted package in Debian: New Status in python-b2sdk package in Debian: New Status in python-hypothesis package in Debian: Unknown Status in supysonic package in Debian: New Status in vorta package in Debian: Unknown Bug description: This bug is for tracking the packages having autopkgtest regressions with python3.10 as a supported version, blocking migration of python3-defaults/3.9.7-4. All packages are in universe except pygobject and python-taskflow in main. All packages have RC bugs in Debian except python-taskflow which is based on a newer upstream version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipywidgets/+bug/1954649/+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 1654627] Re: Windows Rearrange and Resize without User Interactions
We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time. Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021. Do you still see a problem related to the one that you reported when using a currently supported version of Ubuntu? Please let us know if you do otherwise this report can be left to expire in approximately 60 days time. Thank you for helping make Ubuntu better. ** Package changed: xorg (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 xorg in Ubuntu. https://bugs.launchpad.net/bugs/1654627 Title: Windows Rearrange and Resize without User Interactions Status in Ubuntu: Incomplete Bug description: !What I expected to happen Windows stay in the same place with the same dimensions !What happenes (happens) instead Open windows will be re-arranged. Some will be resized, others maximized and some hidden. If workspaces are enabled, some windows will be moved to a different workspace. Some of the ways to reproduce this: * with workspaces enabled, merely switching workspaces (often but not always) * with or without workspaces enabled, if the machine goes to sleep/suspend $ lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 Problem reproduced on multiple machines less than a year old: * System76 Lemur with external Dell monitor + * 2016 HP Spectre x360 with a standard install of Ubuntu) with no external display Frequency: very (essentially any time I'm away from a machine for more than about ten minutes). !Attempted Solutions * Disable all hot corners/edges, etc. on both machines * turned off the Lemur's internal display (the psuedo disable in System Settings > Display). * turned off workspaces on Lemur The only noticable difference was that it reduced the places I had to hunt for the windows I need to move and resize to begin work again. e.g. put my Development environment back in working order. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 Uname: Linux 4.4.0-57-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Jan 6 11:03:13 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.24, 4.4.0-51-generic, x86_64: installed virtualbox, 5.0.24, 4.4.0-53-generic, x86_64: installed virtualbox, 5.0.24, 4.4.0-57-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Skylake Integrated Graphics [1558:2425] InstallationDate: Installed on 2016-11-30 (37 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: System76, Inc. Lemur ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic.efi.signed root=UUID=5a96be43-7cc5-4afd-a77c-7269b753bae3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/29/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.06RS76 dmi.board.asset.tag: Tag 12345 dmi.board.name: Lemur dmi.board.vendor: System76, Inc. dmi.board.version: lemu6 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.06RS76:bd11/29/2015:svnSystem76,Inc.:pnLemur:pvrlemu6:rvnSystem76,Inc.:rnLemur:rvrlemu6:cvnSystem76,Inc.:ct10:cvrN/A: dmi.product.name: Lemur dmi.product.version: lemu6 dmi.sys.vendor: System76, Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau:
[Touch-packages] [Bug 1627187] Re: touchpad is not recognized. no two finger scrolling or zoom
We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time. Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021. Do you still see a problem related to the one that you reported when using a currently supported version of Ubuntu? Please let us know if you do otherwise this report can be left to expire in approximately 60 days time. Thank you for helping make Ubuntu better. ** Package changed: xorg (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 xorg in Ubuntu. https://bugs.launchpad.net/bugs/1627187 Title: touchpad is not recognized. no two finger scrolling or zoom Status in Ubuntu: Incomplete Bug description: touchpad is not recognized. no two finger scrolling or zoom ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 Uname: Linux 4.6.0-040600-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Sep 23 13:40:10 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Skylake Integrated Graphics [1043:1080] Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 960M] [1043:1080] InstallationDate: Installed on 2016-06-27 (88 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 04f2:b3fd Chicony Electronics Co., Ltd Bus 001 Device 005: ID 0457:10cc Silicon Integrated Systems Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. N501VW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.6.0-040600-generic root=UUID=8d4bed35-4644-4bea-9928-057c910ef932 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/03/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N501VW.206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N501VW dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN501VW.206:bd02/03/2016:svnASUSTeKCOMPUTERINC.:pnN501VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: N501VW dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri Sep 23 12:32:57 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16971 vendor SDC xserver.version: 2:1.18.3-1ubuntu2.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1627187/+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 1633081] Re: [Touchpad] Mouse moves, but clicks and scrolls not detected
We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time. Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021. Do you still see a problem related to the one that you reported when using a currently supported version of Ubuntu? Please let us know if you do otherwise this report can be left to expire in approximately 60 days time. Thank you for helping make Ubuntu better. ** Package changed: xorg (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 xorg in Ubuntu. https://bugs.launchpad.net/bugs/1633081 Title: [Touchpad] Mouse moves, but clicks and scrolls not detected Status in Ubuntu: Incomplete Bug description: Generated using ubuntu-bug xorg ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21 Uname: Linux 4.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset wl nvidia .proc.driver.nvidia.gpus..08.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:08:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 361.42 Tue Mar 22 18:10:58 PDT 2016 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Oct 14 00:24:20 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Broadwell-U Integrated Graphics [1028:0656] Subsystem: Dell GM108M [GeForce 840M] [1028:0656] InstallationDate: Installed on 2016-07-20 (85 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) LightdmDisplayLog: [dix] couldn't enable device 16 [dix] couldn't enable device 14 MachineType: Dell Inc. Inspiron 3543 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-42-generic.efi.signed root=UUID=f1d76f64-1c52-4d8e-ab12-2aa7dc8d78e2 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/13/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0V162V dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA08:bd05/13/2016:svnDellInc.:pnInspiron3543:pvrA08:rvnDellInc.:rn0V162V:rvr:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3543 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1633081/+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 1671522] Re: display settings randomly reset
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021. Reporter's account suspended by Launchpad admins. Closing as no further information can be asked of reporter. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1671522 Title: display settings randomly reset Status in Ubuntu: Invalid Bug description: I usually connect an external monitor to my laptop. I had it set up (System Settings->Displays) so that the laptop's built-in monitor is turned off, and the external monitor is the only active one (of course, when I unplug the external monitor, the builtin one turns on automatically, and it turns off when I plug in the external monitor again). I have been using this configuration for ages and it usually gets remembered across boots, as expected. Today I booted and the two monitors were both turned on, acting as an extended desktop. Unplugging and plugging the monitor again did not fix the issue. I had to manually edit the settings to put them as they were before. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44 Uname: Linux 4.4.0-64-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.101 Thu Dec 1 15:52:31 PST 2016 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 BootLog: [[0;32m OK [0m] Started LSB: Speech Dispatcher. [[0;32m OK [0m] Started LSB: Set the CPU Frequency Scaling governor to "ondemand". [[0;32m OK [0m] Started LSB: daemon to balance interrupts for SMP systems. CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Mar 9 16:24:03 2017 DistUpgraded: 2016-12-11 22:45:13,519 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process "./xorg_fix_proprietary.py" (No such file or directory) (8)) DistroCodename: xenial DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics Controller [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (1244 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic.efi.signed root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-12-11 (87 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Thu Mar 9 16:21:28 2017
[Touch-packages] [Bug 1669581] Re: no screen turned on after resume from hibernation
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021. Reporter's account suspended by Launchpad admins. Closing as no further information can be asked of reporter. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1669581 Title: no screen turned on after resume from hibernation Status in Ubuntu: Invalid Bug description: Steps to reproduce: - I connected an external monitor to my laptop through the HDMI port - my display settings are set to use only the external monitor when it is connected, so the laptop's builtin screen was turned off - I hibernated - I brought my laptop home, connected it to another external monitor through the VGA port, and resumed from hibernation Expected: the external monitor should turn on. If no external monitor is connected, then the builtin should turn on. Whenever a monitor is available, it must be made sure that at least one monitor is ALWAYS turned on no matter what. Observed: neither the builtin NOR the external monitor turned on. This is SO FUCKING STUPID. Both screens were turned off. Additionally, even unplugging and plugging the monitor (several times) did nothing. Which is even more retarded. I could verify that the system was actually up and running by hitting CTRL+ALT+T (to open a terminal) and blindly typing "sudo suspend" and entering the password: the computer actually suspended. Even after resuming from suspend, no screen turned on. I had no way to recover and I was forced to shut down, losing all my unsaved data. This does NOT always happen, but this is not the first time either. It seems to be random. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44 Uname: Linux 4.4.0-64-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.101 Thu Dec 1 15:52:31 PST 2016 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Mar 2 21:38:20 2017 DistUpgraded: 2016-12-11 22:45:13,519 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process "./xorg_fix_proprietary.py" (No such file or directory) (8)) DistroCodename: xenial DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics Controller [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (1238 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic.efi.signed root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-12-11 (80 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
[Touch-packages] [Bug 1741780] Re: No response from touchpad
We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time. Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021. Do you still see a problem related to the one that you reported when using a currently supported version of Ubuntu? Please let us know if you do otherwise this report can be left to expire in approximately 60 days time. Thank you for helping make Ubuntu better. ** Package changed: xorg (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 xorg in Ubuntu. https://bugs.launchpad.net/bugs/1741780 Title: No response from touchpad Status in Ubuntu: Incomplete Bug description: Toshiba Satellite L50-C20N I have started Ubuntu after some months and the touchpad didn't work. I have also Windows on the same Notebook and there it works well. If I connect a USB Mouse it works well also in Ubuntu. Description: Ubuntu 16.04.3 LTS Release: 16.04 I'm sending this report following https://wiki.ubuntu.com/DebuggingTouchpadDetection ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98 Uname: Linux 4.4.0-104-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Jan 7 19:52:57 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Broadwell-U Integrated Graphics [1179:f840] Subsystem: Toshiba America Info Systems GM108M [GeForce 930M] [1179:f842] InstallationDate: Installed on 2015-12-28 (741 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: TOSHIBA SATELLITE L50-C ProcEnviron: LANGUAGE=it TERM=xterm-256color PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-104-generic.efi.signed root=UUID=7e5d00b9-cfb0-4f69-95f9-b82ccc7f7853 ro i8042.noaux SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/11/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 5.20 dmi.board.name: 06F2 dmi.board.vendor: FF50 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis ManuFacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr5.20:bd01/11/2016:svnTOSHIBA:pnSATELLITEL50-C:pvrPSKWSE-05Q014IT:rvnFF50:rn06F2:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion: dmi.product.name: SATELLITE L50-C dmi.product.version: PSKWSE-05Q014IT dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sun Jan 7 19:46:10 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1136 vendor LGD xserver.version: 2:1.18.4-0ubuntu0.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1741780/+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 1743097] Re: keyboard/mouse dont work after update
We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time. Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021. Do you still see a problem related to the one that you reported when using a currently supported version of Ubuntu? Please let us know if you do otherwise this report can be left to expire in approximately 60 days time. Thank you for helping make Ubuntu better. ** Package changed: xorg (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 xorg in Ubuntu. https://bugs.launchpad.net/bugs/1743097 Title: keyboard/mouse dont work after update Status in Ubuntu: Incomplete Bug description: since last kernel update: my normal keyboard and mouse on thinkpad lenovo l570 dont work after startx command or logging in. they work on virtual shell (strgaltF1). external usb keyboard/mouse work. system is 4.13.0-26-generic on ubuntu 16.04.3LTS with normally plasma. after that no more updates. "apt install xserver-xorg-input-all" (as possible strategie in past bugs) failed due to dependencies. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13 Uname: Linux 4.13.0-26-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Sat Jan 13 12:21:54 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: kubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2249] InstallationDate: Installed on 2017-07-04 (192 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: LENOVO 20J8001BGE ProcEnviron: LANGUAGE= PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-26-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/19/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1XET27W (1.05 ) dmi.board.asset.tag: Not Available dmi.board.name: 20J8001BGE 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.modalias: dmi:bvnLENOVO:bvrN1XET27W(1.05):bd01/19/2017:svnLENOVO:pn20J8001BGE:pvrThinkPadL570:rvnLENOVO:rn20J8001BGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L570 dmi.product.name: 20J8001BGE dmi.product.version: ThinkPad L570 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sat Jan 13 11:56:42 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1743097/+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 1653540] Re: Using Processor microcode firmware for intel CPUs from intel-microcode(proprietary)
We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time. Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021. Do you still see a problem related to the one that you reported when using a currently supported version of Ubuntu? Please let us know if you do otherwise this report can be left to expire in approximately 60 days time. Thank you for helping make Ubuntu better. ** Package changed: xorg (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 xorg in Ubuntu. https://bugs.launchpad.net/bugs/1653540 Title: Using Processor microcode firmware for intel CPUs from intel- microcode(proprietary) Status in Ubuntu: Incomplete Bug description: I have installed Ubuntu 16-04-1 update it many times on Hp Compaq Elite 8100 SFF. On a details setting, on overview, I have this configuration: The device name, memory, Processor Intel i5 cpu 650 @ 3,5 GHz X 4 Graphics intel Ironlake desktop Os type 64. I have an issue with my display monitor: I have Unknown display Cannot change the resolution of my screen 1024:768(4:3) to higher. Under Software & update I have these messages: Unknown: Unknown (this device is using an alternative driver) Using Processor microcode firmware for intel CPUs from intel-microcode(proprietary) my product hp machine is: AY032AV: HP Compaq 8100 SFF mohamed@HP-Cpq-PC:~$ lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 mohamed@HP-Cpq-PC:~$ apt-cache policy pkgname N: Unable to locate package pkgname Of course I have tried most of answer in every website. Thank you for your help ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-58.79-generic 4.4.35 Uname: Linux 4.4.0-58-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 BootLog: [[0;32m OK [0m] Started LSB: Speech Dispatcher. [[0;32m OK [0m] Started LSB: Set the CPU Frequency Scaling governor to "ondemand". [[0;32m OK [0m] Started LSB: daemon to balance interrupts for SMP systems. [[0;32m OK [0m] Started Raise network interfaces. [[0;32m OK [0m] Reached target Network. CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Jan 2 18:19:21 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0042] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Core Processor Integrated Graphics Controller [103c:304a] InstallationDate: Installed on 2017-01-01 (1 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Hewlett-Packard HP Compaq 8100 Elite SFF PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-58-generic root=UUID=e4b57f22-d72d-441a-9f95-637a0d130be8 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: Section "Device" Identifier "Card0" Driver "intel" Option "AccelMethod" "sna" EndSection dmi.bios.date: 06/09/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786H1 v01.05 dmi.board.asset.tag: CZC1326QPX dmi.board.name: 304Ah dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC1326QPX dmi.chassis.type: 4 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786H1v01.05:bd06/09/2010:svnHewlett-Packard:pnHPCompaq8100EliteSFFPC:pvr:rvnHewlett-Packard:rn304Ah:rvr:cvnHewlett-Packard:ct4:cvr: dmi.product.name: HP Compaq 8100 Elite SFF PC dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Mon Jan 2 18:05:38 2017 xserver.configfile: /etc/X11/xorg.conf xserver.errors:
[Touch-packages] [Bug 1318406] Re: SystemSettings doesn't enable nouveau but says it does
We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time. Ubuntu 14.04 (trusty) reached end-of-life on April 25,2019. Do you still see a problem related to the one that you reported when using a currently supported version of Ubuntu? Please let us know if you do otherwise this report can be left to expire in approximately 60 days time. Thank you for helping make Ubuntu better. ** Package changed: xorg (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 xorg in Ubuntu. https://bugs.launchpad.net/bugs/1318406 Title: SystemSettings doesn't enable nouveau but says it does Status in Ubuntu: Incomplete Bug description: This is a system that has been upgraded to new versions of ubuntu many times. Recently I switched display drivers to nouveau from nvidia-331. Upon rebooting, I'm stuck in 640x480. SystemSettings says I'm using nouveau, but actually, I'm using VESA. This is because there are some leftover files in modprobe.d/ that are blacklisting nouveau. I think systemsettings should probably check if nouveau is in use before saying it is, and remove blacklists against nouveau when it is installing it! grep nouveau /etc/modprobe.d/* --> http://paste.ubuntu.com/7448926/ ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,imgpng,grid,snap,gnomecompat,move,resize,compiztoolbox,unitymtgrabhandles,regex,mousepoll,vpswitch,wall,animation,expo,workarounds,fade,place,session,ezoom,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun May 11 15:51:56 2014 DistUpgraded: 2014-04-20 21:00:38,849 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.11.0-12-generic, x86_64: installed bbswitch, 0.7, 3.13.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT215 [GeForce GT 240] [10de:0ca3] (rev a2) (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:3001] Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 045e:0040 Microsoft Corp. Wheel Mouse Optical Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic root=UUID=99006791-f6dd-4126-ba56-919e97e1a791 ro quiet splash vt.handoff=7 Renderer: Software SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to trusty on 2014-04-21 (20 days ago) dmi.bios.date: 07/09/2007 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: EPoX MCP61 Series dmi.board.vendor: EPoX COMPUTER CO., LTD dmi.board.version: 1.x dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd07/09/2007:svn:pn:pvr:rvnEPoXCOMPUTERCO.,LTD:rnEPoXMCP61Series:rvr1.x:cvn:ct3:cvr: version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sun May 11 15:04:16 2014 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputMicrosoft Microsoft 3-Button Mouse with IntelliEye(TM) MOUSE, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.15.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1318406/+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 1581700] Re: Always a problem with Linux and this PC. B575
We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time. Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021. Do you still see a problem related to the one that you reported when using a currently supported version of Ubuntu? Please let us know if you do otherwise this report can be left to expire in approximately 60 days time. Thank you for helping make Ubuntu better. ** Package changed: xorg (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 xorg in Ubuntu. https://bugs.launchpad.net/bugs/1581700 Title: Always a problem with Linux and this PC. B575 Status in Ubuntu: Incomplete Bug description: I have Windows 7 and ran this install of 16.04 along side of Win 7 ? What happened ? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri May 13 16:51:16 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6310] [1002:9802] (prog-if 00 [VGA controller]) Subsystem: Lenovo Wrestler [Radeon HD 6310] [17aa:397b] InstallationDate: Installed on 2016-05-13 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 1450A7U ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=610ec27d-0fce-43fd-bc7f-cd183f095039 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 52CN11WW dmi.board.asset.tag: Base Board Asset Tag Unknown dmi.board.name: Inagua dmi.board.vendor: LENOVO dmi.board.version: 109-B78210-00A dmi.chassis.asset.tag: Chassis Asset Tag Unknown dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Chassis Version Unknown dmi.modalias: dmi:bvnLENOVO:bvr52CN11WW:bd05/12/2011:svnLENOVO:pn1450A7U:pvrLenovoB575:rvnLENOVO:rnInagua:rvr109-B78210-00A:cvnLENOVO:ct10:cvrChassisVersionUnknown: dmi.product.name: 1450A7U dmi.product.version: Lenovo B575 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri May 13 16:26:30 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.3-1ubuntu2 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1581700/+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 1643946] Re: Ubuntu 4.14 kernel 4.2.0-42 after update does not detect projector via VGA
We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time. Ubuntu 14.04 (trusty) reached end-of-life on April 25,2019. Do you still see a problem related to the one that you reported when using a currently supported version of Ubuntu? Please let us know if you do otherwise this report can be left to expire in approximately 60 days time. Thank you for helping make Ubuntu better. ** Package changed: xorg (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 xorg in Ubuntu. https://bugs.launchpad.net/bugs/1643946 Title: Ubuntu 4.14 kernel 4.2.0-42 after update does not detect projector via VGA Status in Ubuntu: Incomplete Bug description: Ubuntu 4.14 kernel 4.2.0-42 saw perfectly the VGA port and transmitted to projector or TV. Now after update does not detect VGA port and then it does not send images or video projector on it on TV ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.4.0-47.68~14.04.1-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue Nov 22 17:13:46 2016 DistUpgraded: 2016-11-21 18:10:40,873 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:246a] Subsystem: ASUSTeK Computer Inc. Device [1043:246a] InstallationDate: Installed on 2016-04-16 (220 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) MachineType: ASUSTeK COMPUTER INC. X556UB ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic.efi.signed root=UUID=02a822cd-807e-41e3-932b-14503a6a5ee4 ro quiet splash acpi_osi= pci=nomsi vt.handoff=7 SourcePackage: xorg SystemImageInfo: Error: [Errno 2] File o directory non esistente: 'system-image-cli' UpgradeStatus: Upgraded to trusty on 2016-11-21 (0 days ago) dmi.bios.date: 12/09/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X556UB.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X556UB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX556UB.302:bd12/09/2015:svnASUSTeKCOMPUTERINC.:pnX556UB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX556UB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X556UB dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Tue Nov 22 15:56:23 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 14573 vendor AUO xserver.version: 2:1.18.3-1ubuntu2.2~trusty3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1643946/+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 1952599] Re: virt: Support detection for ARM64 Hyper-V guests (fixed upstream)
Hi there,
I used this[0] script to test the different series. The most relevant
parts of it are those parameters for qemu:
-smbios type=0,vendor='Hyper-V test',version=1.2.3 \
-smbios
type=1,manufacturer=t1manufacturer,product=t1product,version=t1version,serial=t1serial,uuid=----,sku=t1sku,family=t1family
\
You can read more about them here[1]. In short, it configures the DMI
table as follows:
ubuntu@impish:~$ cat /sys/class/dmi/id/product_name
t1product
ubuntu@impish:~$ cat /sys/class/dmi/id/sys_vendor
t1manufacturer
ubuntu@impish:~$ cat /sys/class/dmi/id/bios_vendor
Hyper-V test
ubuntu@impish:~$ cat /sys/class/dmi/id/product_version
t1version
Thus, the old systemd should not detect any virt ("none") and the new
one should detect "microsoft"[2].
Test results:
Bionic
==
ubuntu@bionic:~$ dpkg -l systemd ; systemd-detect-virt
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version
Architecture Description
+++-==---=
ii systemd237-3ubuntu10.52
arm64system and service manager
none
ubuntu@bionic:~$ sudo apt-get install -y systemd
...
ubuntu@bionic:~$ dpkg -l systemd ; systemd-detect-virt
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version
Architecture Description
+++-==---=
ii systemd237-3ubuntu10.53
arm64system and service manager
microsoft
Focal
=
ubuntu@focal:~$ dpkg -l systemd ; systemd-detect-virt
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==-=--=
ii systemd245.4-4ubuntu3.13 arm64system and service manager
none
ubuntu@focal:~$ sudo apt-get install -y systemd
...
ubuntu@focal:~$ dpkg -l systemd ; systemd-detect-virt
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==-=--=
ii systemd245.4-4ubuntu3.14 arm64system and service manager
microsoft
Impish
==
ubuntu@impish:~$ dpkg -l systemd ; systemd-detect-virt
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name VersionArchitecture Description
+++-==-==--=
ii systemd248.3-1ubuntu8 arm64system and service manager
none
ubuntu@impish:~$ sudo apt-get install -y systemd
...
ubuntu@impish:~$ dpkg -l systemd ; systemd-detect-virt
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==---=
ii systemd248.3-1ubuntu8.1 arm64system and service manager
microsoft
[0] https://pastebin.canonical.com/p/WCqqyCK7Qj/
[1] https://gist.github.com/smoser/290f74c256c89cb3f3bd434a27b9f64c
[2] https://github.com/systemd/systemd/blob/main/src/basic/virt.c#L144-L193
** Tags removed: verification-needed-bionic verification-needed-focal
verification-needed-impish
** Tags added: verification-done-bionic verification-done-focal
verification-done-impish
--
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/1952599
Title:
virt: Support
[Touch-packages] [Bug 1944409] Re: Systemd uses CPU after wakeup due to power_supply BAT0 (battery) continued polling
reply #5 Can you try $ fwupdmgr get-updates to see if you can see the latest firmware in LVFS? or attach your output here. Also, you can always get latest BIOS here https://www.dell.com/support/home/en-in/product- support/product/latitude-15-7520-laptop/drivers, sometimes it is newer than BIOS in LVFS. -- 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/1944409 Title: Systemd uses CPU after wakeup due to power_supply BAT0 (battery) continued polling Status in OEM Priority Project: New Status in systemd package in Ubuntu: Confirmed Bug description: My setup: - Dell Latitude 7520 - Dell WD15 USB C docking station - Ubuntu 20.04.3 - systemd 245.4-4ubuntu3.13 - uname -a: Linux CLIFMI085 5.13.0-1012-oem #16-Ubuntu SMP Tue Sep 7 09:23:08 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux I leave my laptop docked and, after waking it up from sleep, the fans start blowing. After a quick inspection with top/htop, I always see /usr/lib/systemd/systemd-udev consuming 50+% of my CPU. After a quick search, I discover that I can use `udevadm monitor` to check what device is making all this fuss, and this is the output: UDEV [92591.827159] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92591.873819] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92591.920022] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92591.967005] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.018200] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.068351] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.115100] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.166201] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.213318] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.261046] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.308824] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.356577] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.403766] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.451164] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) As you can see, the battery status is being polled every 0.05s. To fix this, I just need to restart the service with: sudo systemctl restart systemd-udevd systemd-udevd-kernel.socket systemd-udevd-control.socket Afterwards, this is the output of `udevadm monitor`: KERNEL[92739.612371] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92739.646888] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) KERNEL[92741.076823] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92741.099370] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) KERNEL[92742.539438] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92742.573812] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) As you can see, the battery is now being polled every ~1.5s, which is fine. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1944409/+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
