[Touch-packages] [Bug 1960742] Re: System freeze
Thanks for the bug report. Next time the freeze happens please: 1. Wait 10 seconds. 2. Reboot. 3. Run: journalctl -b-1 > prevboot.txt 4. Attach the resulting text file here. ** Summary changed: - Xorg freeze + System freeze ** Package changed: xorg (Ubuntu) => linux-hwe-5.13 (Ubuntu) ** Changed in: linux-hwe-5.13 (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/1960742 Title: System freeze Status in linux-hwe-5.13 package in Ubuntu: Incomplete Bug description: before it crashes, 3 LEDs (Power, mayus,block number) turn on and turn off about 3 times.. And all will be freeze it needs to shutdown keeping pressed the I/O button ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Feb 13 11:03:30 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Device [8086:4e55] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:2212] InstallationDate: Installed on 2022-02-09 (4 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: INTEL V14 ProcEnviron: LANGUAGE=es_EC:es PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_EC.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic root=UUID=31ee87c2-d9b1-413d-bc93-15224f6ba1ec ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/25/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: WZ362D.fBNAPLL02.2105061 dmi.board.asset.tag: Default string dmi.board.name: V14 dmi.board.vendor: INET dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.ec.firmware.release: 1.2 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrWZ362D.fBNAPLL02.2105061:bd05/25/2021:br5.19:efr1.2:svnINTEL:pnV14:pvrDefaultstring:rvnINET:rnV14:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:sku2105061: dmi.product.family: Jasper lake dmi.product.name: V14 dmi.product.sku: 2105061 dmi.product.version: Default string dmi.sys.vendor: INTEL version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1960742/+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 1960747] Re: Autorotation of screen does not work on wayland, but on X
** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** Summary changed: - Autorotation of screen does not work on wayland, but on X + [Lenovo Yoga 7] Autorotation of screen does not work on wayland, but on X -- 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/1960747 Title: [Lenovo Yoga 7] Autorotation of screen does not work on wayland, but on X Status in mutter package in Ubuntu: New Bug description: When physically rotating my 2-in-1 laptop Lenovo Yoga 7 Gen 6 AMD - 14ACN6, screen rotates properly under X, but not under Wayland. Also the lock screen rotation option is missing in the top-right menu under Wayland. It exists in X. iio-sensor-proxy is being loaded correctly: --- $ systemctl status iio-sensor-proxy.service ● iio-sensor-proxy.service - IIO Sensor Proxy service Loaded: loaded (/lib/systemd/system/iio-sensor-proxy.service; static) Active: active (running) since Sun 2022-02-13 15:43:37 CET; 2h 12min ago Main PID: 787 (iio-sensor-prox) Tasks: 3 (limit: 16544) Memory: 1.4M CPU: 5.688s CGroup: /system.slice/iio-sensor-proxy.service └─787 /usr/libexec/iio-sensor-proxy Feb 13 15:43:36 michaels-yoga systemd[1]: Starting IIO Sensor Proxy service... Feb 13 15:43:37 michaels-yoga systemd[1]: Started IIO Sensor Proxy service. --- monitor-sensor detects the physical rotation: --- $ monitor-sensor Waiting for iio-sensor-proxy to appear +++ iio-sensor-proxy appeared === Has accelerometer (orientation: normal) === Has ambient light sensor (value: 70,29, unit: lux) === No proximity sensor Light changed: 65,27 (lux) Light changed: 160,66 (lux) Accelerometer orientation changed: right-up Light changed: 40,16 (lux) Light changed: 45,18 (lux) Light changed: 40,16 (lux) Light changed: 25,10 (lux) Accelerometer orientation changed: left-up Light changed: 20,08 (lux) Light changed: 25,10 (lux) Light changed: 35,14 (lux) Accelerometer orientation changed: normal Light changed: 155,64 (lux) Accelerometer orientation changed: bottom-up Light changed: 30,12 (lux) Light changed: 40,16 (lux) Light changed: 30,12 (lux) Light changed: 145,60 (lux) Accelerometer orientation changed: normal --- Putting the laptop in tablet mode disables keyboard and touchpad correctly both under Wayland and X. So obviously the sensors are working correctly, but signals are not being interpreted correctly in Wayland? --- ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 Uname: Linux 5.15.0-051500-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Feb 13 17:46:51 2022 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Cezanne [17aa:3813] InstallationDate: Installed on 2022-02-11 (1 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 82N7 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.15.0-051500-generic root=UUID=d1796991-349c-4784-b8c3-e0a2eb2fc132 ro rootflags=subvol=@ quiet splash mem_sleep_default=deep vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/12/2021 dmi.bios.release: 1.25 dmi.bios.vendor: LENOVO dmi.bios.version: H9CN25WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76463 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga 7 14ACN6 dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnLENOVO:bvrH9CN25WW:bd11/12/2021:br1.25:efr1.25:svnLENOVO:pn82N7:pvrYoga714ACN6:rvnLENOVO:rnLNVNB161216:rvrSDK0T76463WIN:cvnLENOVO:ct31:cvrYoga714ACN6:skuLENOVO_MT_82N7_BU_idea_FM_Yoga714ACN6: dmi.product.family: Yoga 7 14ACN6 dmi.product.name: 82N7 dmi.product.sku: LENOVO_MT_82N7_BU_idea_FM_Yoga 7 14ACN6 dmi.product.version: Yoga 7 14ACN6 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.6-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.
[Touch-packages] [Bug 1960709] Re: Recent bluez update broke Bluetooth for setups using a BT dongle
BTW, "ConditionPathIsDirectory" is not new. It's been there for two years already in Ubuntu 20.04. If you have experienced a regression then more often that would come from a kernel update so please try some different kernel versions. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1960709 Title: Recent bluez update broke Bluetooth for setups using a BT dongle Status in bluez package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: A recent upgrade (seemingly 5.53-0ubuntu3.5) broke Bluetooth functionality for certain setups. Specifically, the `ConditionPathIsDirectory=` parameter has been added to the `bluetooth` Systemd unit. This breaks setups where users use a Bluetooth dongle, since when the system starts, the BT device may not be connected, and due to the condition, the `bluetooth` unit won't start at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1960709/+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 1960709] Re: Recent bluez update broke Bluetooth for setups using a BT dongle
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1960709 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Tags added: focal regression-update ** Changed in: bluez (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1960709 Title: Recent bluez update broke Bluetooth for setups using a BT dongle Status in bluez package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: A recent upgrade (seemingly 5.53-0ubuntu3.5) broke Bluetooth functionality for certain setups. Specifically, the `ConditionPathIsDirectory=` parameter has been added to the `bluetooth` Systemd unit. This breaks setups where users use a Bluetooth dongle, since when the system starts, the BT device may not be connected, and due to the condition, the `bluetooth` unit won't start at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1960709/+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 1960448] Re: Sony WF-XB700 Bluetooth headset not detected
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- 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/1960448 Title: Sony WF-XB700 Bluetooth headset not detected Status in bluez package in Ubuntu: New Status in gnome-bluetooth package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Gnome-bluetooth does not detect Sony WF-XB700 bluetooth headset. Installed blueman to try to figure out if this is related to gnome- bluetooth - the results are the same. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-bluetooth 3.34.5-4 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Feb 9 22:01:56 2022 InstallationDate: Installed on 2021-09-09 (153 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: gnome-bluetooth UpgradeStatus: Upgraded to jammy on 2022-01-13 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1960448/+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 1960605] Re: Xorg freeze
Thanks for the bug report. I can see two problems here, though am not sure if either is the main issue: * Timeout, server 21.0.0.52 not responding. Whatever that is, if it's a server the machine depends on then it might cause a startup failure. * CurrentDmesg.txt seems to suggest file system corruption on /dev/sdb1. If that's something the machine depends on then it might cause a startup failure. ** Summary changed: - Xorg freeze + System freeze ** Package changed: xorg (Ubuntu) => 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/1960605 Title: System freeze Status in Ubuntu: New Bug description: When booting the system, sometimes the system freezes (HP logo, Ubuntu logo and stopped rotating symbol), and can't do anything not even ping the system. After zero or a few re-try's I get to the login screen. It is then possible to log in via ssh from another system. Everything looks OK. Then I can select the user give her password and then one of two things happens. one: Ubuntu starts and works OK. two: the system freezes (black screen) and nothing works not even the ssh session. I've tried looking at syslog and other files, but can't make any sense of it. I also attached the last lines of the syslog wich ended in a crash/hangup. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.86 Tue Oct 26 21:55:45 UTC 2021 GCC version: ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Toegang geweigerd: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Feb 11 10:29:20 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Since a couple weeks or more GraphicsCard: Intel Corporation UHD Graphics [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:8745] NVIDIA Corporation Device [10de:1f95] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:8745] InstallationDate: Installed on 2021-12-04 (69 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: HP HP Pavilion Gaming Laptop 17-cd1xxx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic root=UUID=84ab800e-9239-453f-8f4a-dc7e4377e5ad ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2021 dmi.bios.release: 15.21 dmi.bios.vendor: Insyde dmi.bios.version: F.21 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8745 dmi.board.vendor: HP dmi.board.version: 03.34 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 3.34 dmi.modalias: dmi:bvnInsyde:bvrF.21:bd01/08/2021:br15.21:efr3.34:svnHP:pnHPPavilionGamingLaptop17-cd1xxx:pvrType1ProductConfigId:rvnHP:rn8745:rvr03.34:cvnHP:ct10:cvrChassisVersion:sku1C4U6EA#ABH: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Gaming Laptop 17-cd1xxx dmi.product.sku: 1C4U6EA#ABH dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP 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 21.0.3-0ubuntu0.3~20.04.5 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubu
[Touch-packages] [Bug 1960602] Re: Ubuntu 20.04 shows blank upon resuming from resume. Requires hard shutdown using the h/w power button
Thanks for the bug report. The final entry in your kernel log shows that the Intel GPU tried and failed to update the screen: [ 1216.206745] i915 :00:02.0: [drm] *ERROR* Atomic update failure on pipe A (start=73567 end=73568) time 940 us, min 1073, max 1079, scanline start 1033, end 1097 So maybe that's the issue... Please try (separately): 1. Selecting 'Ubuntu on Wayland' on the login screen just before logging in. 2. Edit /etc/environment and add a line: MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 Then reboot and select 'Ubuntu on Wayland' again. ** Tags added: resume suspend-resume ** Package changed: xorg (Ubuntu) => linux-hwe-5.13 (Ubuntu) ** Changed in: linux-hwe-5.13 (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/1960602 Title: Ubuntu 20.04 shows blank upon resuming from resume. Requires hard shutdown using the h/w power button Status in linux-hwe-5.13 package in Ubuntu: Incomplete Bug description: After installing Ubuntu 20.04 on my laptop, if the laptop suspends due to closing the lid or not using the laptop for some time and once I press any key to resume from the suspend, the laptop shows a blank screen and is unresponsive to any button presses. This problem happens sometimes though. There have been times that I resume from suspend successfully. But more often it will fail to resume from suspend completely and I will need to use the hardware power button to hard shutdown and restart. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-28-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: Fri Feb 11 14:23:17 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 620 (Whiskey Lake) [103c:84c1] Subsystem: Hewlett-Packard Company GM108M [GeForce MX130] [103c:84c1] InstallationDate: Installed on 2021-09-10 (153 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05c8:03bc Cheng Uei Precision Industry Co., Ltd (Foxlink) HP Wide Vision HD Camera Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Pavilion Laptop 15-cs1xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic root=UUID=a6c8900d-2dd5-4390-a3c8-c0865429d620 ro nouveau.blacklist=1 quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2020 dmi.bios.release: 15.23 dmi.bios.vendor: Insyde dmi.bios.version: F.23 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84C1 dmi.board.vendor: HP dmi.board.version: 15.32 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 15.32 dmi.modalias: dmi:bvnInsyde:bvrF.23:bd12/25/2020:br15.23:efr15.32:svnHP:pnHPPavilionLaptop15-cs1xxx:pvrType1ProductConfigId:rvnHP:rn84C1:rvr15.32:cvnHP:ct10:cvrChassisVersion:sku5FP53PA#ACJ: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-cs1xxx dmi.product.sku: 5FP53PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP 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 21.0.3-0ubuntu0.3~20.04.5 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1960602/+subscriptions -- Mailing list: https
[Touch-packages] [Bug 1960768] Re: fwupd crash on stop
** Also affects: libusb (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libusb in Ubuntu. https://bugs.launchpad.net/bugs/1960768 Title: fwupd crash on stop Status in OEM Priority Project: In Progress Status in fwupd package in Ubuntu: New Status in libusb package in Ubuntu: New Bug description: I can reproduce crash with a similar stack as below as I stop fwupd service. https://errors.ubuntu.com/problem/4bfcf571c017010afe4775687ff2a9ca7ff79661 also test fwupd 1.7.5 (https://launchpad.net/~ycheng-twn/+archive/ubuntu/fwupd175) still can reproduce this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1960768/+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] 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 bluez in Ubuntu. https://bugs.launchpad.net/bugs/1949075 Title: [Sony WI-C310] [Intel Wireless 8260] Bluetooth headset not autoconnecting on power-on on 21.10 Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Confirmed 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 1960403] Re: Kubuntu constantly freezing on ThinkPad T510
Jonas, In comment #5 do you mean the fix was released to Ubuntu, or the fix is only in the Mesa PPA from comment #3? ** No longer affects: xserver-xorg-video-intel (Ubuntu) ** No longer affects: linux (Ubuntu) ** No longer affects: kubuntu-meta (Ubuntu) ** No longer affects: xorg (Ubuntu) ** Tags added: arrandale i915 ** Changed in: mesa (Ubuntu) Status: New => Incomplete -- 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/1960403 Title: Kubuntu constantly freezing on ThinkPad T510 Status in mesa package in Ubuntu: Incomplete Bug description: This happens either during SDDM, or on the desktop, but Kubuntu's constantly freezing up. I tried disabling the compositor, but it doesn't seem to help. Also, I removed the external monitor, but that doesn't seem to help. I've installed Lubuntu, and so far it's been fine. However, when I tried to change the SDDM theme via KDE's System Settings, the laptop locked up. I'll keep Kubuntu on it for now, but I'm gonna have to switch this to Lubuntu in the meantime. Specs: * Core i7-640M * 8GB RAM ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: kubuntu-desktop 1.416 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Feb 9 05:58:18 2022 InstallationDate: Installed on 2021-08-07 (186 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: kubuntu-meta UpgradeStatus: Upgraded to jammy on 2022-02-09 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1960403/+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 1960448] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1960448 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1960448 Title: Sony WF-XB700 Bluetooth headset not detected Status in bluez package in Ubuntu: New Status in gnome-bluetooth package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Gnome-bluetooth does not detect Sony WF-XB700 bluetooth headset. Installed blueman to try to figure out if this is related to gnome- bluetooth - the results are the same. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-bluetooth 3.34.5-4 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Feb 9 22:01:56 2022 InstallationDate: Installed on 2021-09-09 (153 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: gnome-bluetooth UpgradeStatus: Upgraded to jammy on 2022-01-13 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1960448/+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: Sony WI-C310 Bluetooth headset not autoconnecting on power-on on 21.10
Given the message in your kernel log: Bluetooth: hci0: Ignoring error of Inquiry Cancel command A similar problem with the same message was a kernel regression: https://bbs.archlinux.org/viewtopic.php?id=259954 Maybe not related to this bug, but still a reminder that it might be a kernel regression. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Sony WI-C310 Bluetooth headset not autoconnecting on power-on on 21.10 + [Sony WI-C310] [Intel Wireless 8260] Bluetooth headset not autoconnecting on power-on on 21.10 -- 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: [Sony WI-C310] [Intel Wireless 8260] Bluetooth headset not autoconnecting on power-on on 21.10 Status in bluez package in Ubuntu: New Status in linux 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 1960448] Re: Sony WF-XB700 Bluetooth headset not detected
** Changed in: bluez (Ubuntu) Status: Incomplete => New ** Changed in: gnome-bluetooth (Ubuntu) Status: Incomplete => New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- 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/1960448 Title: Sony WF-XB700 Bluetooth headset not detected Status in bluez package in Ubuntu: New Status in gnome-bluetooth package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: Gnome-bluetooth does not detect Sony WF-XB700 bluetooth headset. Installed blueman to try to figure out if this is related to gnome- bluetooth - the results are the same. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-bluetooth 3.34.5-4 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Feb 9 22:01:56 2022 InstallationDate: Installed on 2021-09-09 (153 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: gnome-bluetooth UpgradeStatus: Upgraded to jammy on 2022-01-13 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1960448/+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
This is still on my TODO list but low priority. The reason being this kind of bug has been observed with every release on a variety of hardware. I think it fails in more cases than it succeeds, and has always done so. If by chance a developer has access to the same specific headset then the problem could be bisected and a specific cause identified. ** Summary changed: - Bluetooth headset not autoconnecting on power-on on 21.10 + Sony WI-C310 Bluetooth headset not autoconnecting on power-on on 21.10 -- 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: Sony WI-C310 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 1676203] Re: Strange pixels after wakeup
*** This bug is a duplicate of bug 1876632 *** https://bugs.launchpad.net/bugs/1876632 This is an ongoing problem with the Nvidia drivers. Now tracking in bug 1876632. ** This bug has been marked a duplicate of bug 1876632 [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend -- 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/1676203 Title: Strange pixels after wakeup Status in xorg package in Ubuntu: Invalid Bug description: After ubuntu wakeup I experience a lot of pixels on desktop and on every context menu (after right click). You can see the problem in the attached screenshoot. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-67.88-generic 4.4.49 Uname: Linux 4.4.0-67-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] Jest katalogiem: '/proc/driver/nvidia/gpus/:04:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 375.39 Tue Jan 31 20:47:00 PST 2017 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: Sun Mar 26 19:55:41 2017 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: ASUSTeK Computer Inc. Broadwell-U Integrated Graphics [1043:1a6d] Subsystem: ASUSTeK Computer Inc. GK208M [GeForce 920M] [1043:1a6d] InstallationDate: Installed on 2016-10-06 (170 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) LightdmLog: [+17450.89s] DEBUG: User /org/freedesktop/Accounts/User126 added Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 007: ID 13d3:3423 IMC Networks Bus 001 Device 002: ID 0bda:57b5 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X555LJ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-67-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/04/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555LJ.504 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555LJ 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.:bvrX555LJ.504:bd08/04/2015:svnASUSTeKCOMPUTERINC.:pnX555LJ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LJ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X555LJ 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.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: Sun Mar 26 07:58:24 2017 xserver.configfile: /etc/X11/xorg.conf xserver.errors: evdev: BluetoothMouse3600: Unable to open evdev device "/dev/input/event13". xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1676203/+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 980519] Re: Random log off in Ubuntu 12.04 LTS
Sorry, this bug is very old and this version of Ubuntu isn't supported any more. If you think you have a similar issue, please file a new bug. ** Package changed: fedora => libgweather4 (Ubuntu) ** No longer affects: libgweather4 (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/980519 Title: Random log off in Ubuntu 12.04 LTS Status in Unity: Fix Released Status in gnome-desktop package in Ubuntu: Invalid Status in nvidia-graphics-drivers package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Status in xorg package in Ubuntu: Fix Released Bug description: I get logged off from Ubuntu sometimes. There is no error message or any indication that it is going to log off. The screen goes black, and after 2-4 seconds, i get presented with the Ubuntu Log On Screen. There is no clear pattern (or at least if have not noticed any). One time i am working with Netbeans, another time i am using firefox. This also means that at present i can not clearly say what package might be causing this behaviour. I am fairly sure the problem lies in 12.04 (or more precise - the combination of 12.04 and the hardware i am using). I do not have the same problem running 11.04 or 11.10. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/980519/+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 980519] Re: Random log off in Ubuntu 12.04 LTS
** Changed in: gnome-desktop (Ubuntu) Status: Confirmed => Fix Released ** Changed in: gnome-desktop (Ubuntu) Status: Fix Released => 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/980519 Title: Random log off in Ubuntu 12.04 LTS Status in Unity: Fix Released Status in gnome-desktop package in Ubuntu: Invalid Status in nvidia-graphics-drivers package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Status in xorg package in Ubuntu: Fix Released Bug description: I get logged off from Ubuntu sometimes. There is no error message or any indication that it is going to log off. The screen goes black, and after 2-4 seconds, i get presented with the Ubuntu Log On Screen. There is no clear pattern (or at least if have not noticed any). One time i am working with Netbeans, another time i am using firefox. This also means that at present i can not clearly say what package might be causing this behaviour. I am fairly sure the problem lies in 12.04 (or more precise - the combination of 12.04 and the hardware i am using). I do not have the same problem running 11.04 or 11.10. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/980519/+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 980519] Re: Random log off in Ubuntu 12.04 LTS
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libgweather4 (Ubuntu) Status: New => Confirmed -- 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/980519 Title: Random log off in Ubuntu 12.04 LTS Status in Unity: Fix Released Status in gnome-desktop package in Ubuntu: Invalid Status in nvidia-graphics-drivers package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Status in xorg package in Ubuntu: Fix Released Bug description: I get logged off from Ubuntu sometimes. There is no error message or any indication that it is going to log off. The screen goes black, and after 2-4 seconds, i get presented with the Ubuntu Log On Screen. There is no clear pattern (or at least if have not noticed any). One time i am working with Netbeans, another time i am using firefox. This also means that at present i can not clearly say what package might be causing this behaviour. I am fairly sure the problem lies in 12.04 (or more precise - the combination of 12.04 and the hardware i am using). I do not have the same problem running 11.04 or 11.10. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/980519/+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 1960264] Re: 503 errors for Jammy PPAs
Julian - correct I was using apt-cacher-ng as per sbuild instructions here https://wiki.ubuntu.com/SimpleSbuild Sorry - I've no idea how to configure squid-deb-proxy with sbuild. So I've deleted my sbuild chroots & disabled using the .mk-sbuildrc proxy. Installing from a ppa no longer shows 503 errors. ** Changed in: apt (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1960264 Title: 503 errors for Jammy PPAs Status in apt package in Ubuntu: New Bug description: For Jammy - all PPAs seem to fail - the main archive is ok 503 Connection closed, check DlMaxRetries [IP: 127.0.0.1 3142] Err:12 http://ppa.launchpad.net/ubuntubudgie-dev/budgie-extras-daily/ubuntu jammy/main amd64 budgie-window-shuffler amd64 1.3.0+202202062047~ubuntu22.04.1 503 Connection closed, check DlMaxRetries [IP: 127.0.0.1 3142] Err:6 http://ppa.launchpad.net/ubuntubudgie-dev/budgie-extras-daily/ubuntu jammy/main amd64 budgie-rotation-lock-applet all 1.3.0+202202062047~ubuntu22.04.1 503 Connection closed, check DlMaxRetries [IP: 127.0.0.1 3142] Fetched 114 kB in 7s (15.8 kB/s) E: Failed to fetch http://ppa.launchpad.net/ubuntubudgie-dev/budgie-extras-daily/ubuntu/pool/main/b/budgie-extras/budgie-quicknote-applet_1.3.0%2b202202062047%7eubuntu22.04.1_amd64.deb 503 Connection closed, check DlMaxRetries [IP: 127.0.0.1 3142] E: Failed to fetch http://ppa.launchpad.net/ubuntubudgie-dev/budgie-extras-daily/ubuntu/pool/main/b/budgie-extras/budgie-recentlyused-applet_1.3.0%2b202202062047%7eubuntu22.04.1_amd64.deb 503 Connection closed, check DlMaxRetries [IP: 127.0.0.1 3142] ppa:ubuntubudgie-dev/budgie-extras-daily The same PPA for impish & focal work just fine Thoughts? Continually running repeatedly sudo apt update && sudo apt dist- upgrade -y eventually forces the downloads to occur ok and the upgrades can then be installed ok ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apt 2.3.15 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Budgie:GNOME Date: Mon Feb 7 18:47:47 2022 InstallationDate: Installed on 2022-01-29 (8 days ago) InstallationMedia: Ubuntu-Budgie 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220129) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1960264/+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 1960727] Re: When apt holds back updates, it fails to inform the user of the reason
For over a decade now, at least, users have continually been puzzled by this silent refusal. Again, in most contexts, that indicates a failure of the interface. Viewed 1.1M times https://askubuntu.com/questions/601/the-following-packages-have-been-kept-back-why-and-how-do-i-solve-it Viewed 62k times https://unix.stackexchange.com/questions/38837/what-does-the-following-packages-have-been-kept-back-mean Viewed 87k times https://superuser.com/questions/1107334/apt-says-packages-have-been-kept-back-what-to-do/1108268 etc. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1960727 Title: When apt holds back updates, it fails to inform the user of the reason Status in apt package in Ubuntu: Opinion Bug description: In the case where apt refuses to install and holds back certain packages, only the following output is produced: root@system:/home/admin# apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages have been kept back: [ List of packages ] 0 upgraded, 0 newly installed, 0 to remove and 24 not upgraded. Missing is any explanation about which package is responsible for apt refusing to perform its job, or even what is the reason for that package being uninstallable. This bug leads users to believe that official Ubuntu packages are routinely misconstructed, corrupt, or otherwise junk. Fix: Instead of apt simply responding "No Dave, I'm Afraid I Can't Do that", correct the output to include the specific package that has a missing or unresolved dependency, so the user a) has confidence that the process works correctly and b) can proceed with fixing the problem. This bug is longstanding, so I don't think version details are required, but they follow anyway: 1) Distributor ID: Ubuntu Description:Ubuntu 20.04.3 LTS Release:20.04 Codename: focal 2) # apt --version apt 2.0.6 (amd64) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1960727/+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 1377338] Re: apparmor may fail to load some profiles if one is corrupted
It should be fixed as of the AppArmor 3.0 release. With 3.0 the handling
of jobs doesn't stop with an error unless --abort-on-error is specified.
Instead the parser will keep track of the last error and return that
there was an error, but it will keep processing the rest of the jobs.
We did not close this for 3.0 as we wanted more time, to make sure we
have it fixed. But we are considering it fixed on the dev branch. Though
christian did turn up another corner case the other day
https://gitlab.com/apparmor/apparmor/-/issues/215 that we need to finish
fixing.
** Bug watch added: gitlab.com/apparmor/apparmor/-/issues #215
https://gitlab.com/apparmor/apparmor/-/issues/215
** Changed in: apparmor
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1377338
Title:
apparmor may fail to load some profiles if one is corrupted
Status in AppArmor:
Fix Committed
Status in apparmor package in Ubuntu:
Fix Released
Status in click-apparmor package in Ubuntu:
Fix Released
Status in apparmor package in Ubuntu RTM:
Fix Released
Status in click-apparmor package in Ubuntu RTM:
Fix Released
Bug description:
Steps to reproduce (on the emulator):
1. sudo sh -c 'echo foo >
/var/lib/apparmor/profiles/click_com.ubuntu.music_music_1.3.638'
2. sudo start apparmor ACTION=teardown
3. sudo start apparmor
start: Job failed to start
4. sudo aa-status|egrep '^ '|grep -v '('| sort -u > /tmp/aa-status.music_bad
5. sudo rm -f /var/lib/apparmor/profiles/click_com.ubuntu.music_music_1.3.638
6. sudo aa-clickhook # regenerates the missing profile to had a good one
7. sudo start apparmor ACTION=teardown
8. sudo start apparmor
9. sudo aa-status|egrep '^ '|grep -v '('| sort -u > /tmp/aa-status.music_good
10. diff -Naur /tmp/aa-status.music_bad /tmp/aa-status.music_good
--- /tmp/aa-status.music_bad 2014-10-03 22:47:52.890906744 +
+++ /tmp/aa-status.music_good 2014-10-03 22:49:54.372739381 +
@@ -13,6 +13,10 @@
com.ubuntu.developer.webapps.webapp-twitter_webapp-twitter_1.0.18//oxide_helper
com.ubuntu.developer.webapps.webapp-twitter_webapp-twitter-helper_1.0.18
com.ubuntu.dropping-letters_dropping-letters_0.1.2.2.66
+ com.ubuntu.music_music_1.3.638
+ com.ubuntu.shorts_shorts_0.2.330
+ com.ubuntu.sudoku_sudoku_1.1.292
+ com.ubuntu.weather_weather_1.1.374
lxc-container-default
lxc-container-default-with-mounting
lxc-container-default-with-nesting
Expected results: only com.ubuntu.music_music_1.3.638 should be
missing.
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1377338/+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 1960727] Re: When apt holds back updates, it fails to inform the user of the reason
Nearly anything would be better than the current state of silent failure. At present, probably many thousands of Ubuntu systems are reporting the following: root@system:/home# apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages have been kept back: libnvidia-cfg1-470 libnvidia-compute-470 libnvidia-compute-470:i386 libnvidia-decode-470 libnvidia-decode-470:i386 libnvidia-encode-470 libnvidia-encode-470:i386 libnvidia-extra-470 libnvidia-fbc1-470 libnvidia-fbc1-470:i386 libnvidia-gl-470 libnvidia-gl-470:i386 libnvidia-ifr1-470 libnvidia-ifr1-470:i386 linux-modules-nvidia-470-5.13.0-28-generic linux-modules-nvidia-470-generic-hwe-20.04 linux-objects-nvidia-470-5.13.0-28-generic linux-signatures-nvidia-5.13.0-28-generic nvidia-compute-utils-470 nvidia-driver-470 nvidia-kernel-common-470 nvidia-kernel-source-470 nvidia-utils-470 xserver-xorg-video-nvidia-470 0 upgraded, 0 newly installed, 0 to remove and 24 not upgraded. Providing not even a hint as to which of those packages is uninstallable, or why, would be unacceptable in most development contexts. In this case, with preceding versions of most or all of those packages already installed, it is far from clear to end-users why their system refuses to install official upgrades. Not many software tools respond to user instructions with a simple "No", and that's generally considered bad practice. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1960727 Title: When apt holds back updates, it fails to inform the user of the reason Status in apt package in Ubuntu: Opinion Bug description: In the case where apt refuses to install and holds back certain packages, only the following output is produced: root@system:/home/admin# apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages have been kept back: [ List of packages ] 0 upgraded, 0 newly installed, 0 to remove and 24 not upgraded. Missing is any explanation about which package is responsible for apt refusing to perform its job, or even what is the reason for that package being uninstallable. This bug leads users to believe that official Ubuntu packages are routinely misconstructed, corrupt, or otherwise junk. Fix: Instead of apt simply responding "No Dave, I'm Afraid I Can't Do that", correct the output to include the specific package that has a missing or unresolved dependency, so the user a) has confidence that the process works correctly and b) can proceed with fixing the problem. This bug is longstanding, so I don't think version details are required, but they follow anyway: 1) Distributor ID: Ubuntu Description:Ubuntu 20.04.3 LTS Release:20.04 Codename: focal 2) # apt --version apt 2.0.6 (amd64) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1960727/+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 1960264] Re: 503 errors for Jammy PPAs
It seems you use apt-cacher-ng, please try if the issue reproduces without it, and if so, if it happens with a known good proxy like squid (e.g. using deb-squid-proxy). ** Changed in: apt (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1960264 Title: 503 errors for Jammy PPAs Status in apt package in Ubuntu: Incomplete Bug description: For Jammy - all PPAs seem to fail - the main archive is ok 503 Connection closed, check DlMaxRetries [IP: 127.0.0.1 3142] Err:12 http://ppa.launchpad.net/ubuntubudgie-dev/budgie-extras-daily/ubuntu jammy/main amd64 budgie-window-shuffler amd64 1.3.0+202202062047~ubuntu22.04.1 503 Connection closed, check DlMaxRetries [IP: 127.0.0.1 3142] Err:6 http://ppa.launchpad.net/ubuntubudgie-dev/budgie-extras-daily/ubuntu jammy/main amd64 budgie-rotation-lock-applet all 1.3.0+202202062047~ubuntu22.04.1 503 Connection closed, check DlMaxRetries [IP: 127.0.0.1 3142] Fetched 114 kB in 7s (15.8 kB/s) E: Failed to fetch http://ppa.launchpad.net/ubuntubudgie-dev/budgie-extras-daily/ubuntu/pool/main/b/budgie-extras/budgie-quicknote-applet_1.3.0%2b202202062047%7eubuntu22.04.1_amd64.deb 503 Connection closed, check DlMaxRetries [IP: 127.0.0.1 3142] E: Failed to fetch http://ppa.launchpad.net/ubuntubudgie-dev/budgie-extras-daily/ubuntu/pool/main/b/budgie-extras/budgie-recentlyused-applet_1.3.0%2b202202062047%7eubuntu22.04.1_amd64.deb 503 Connection closed, check DlMaxRetries [IP: 127.0.0.1 3142] ppa:ubuntubudgie-dev/budgie-extras-daily The same PPA for impish & focal work just fine Thoughts? Continually running repeatedly sudo apt update && sudo apt dist- upgrade -y eventually forces the downloads to occur ok and the upgrades can then be installed ok ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apt 2.3.15 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Budgie:GNOME Date: Mon Feb 7 18:47:47 2022 InstallationDate: Installed on 2022-01-29 (8 days ago) InstallationMedia: Ubuntu-Budgie 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220129) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1960264/+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 1960727] Re: When apt holds back updates, it fails to inform the user of the reason
Marking as Opinion as David explained why that is not a thing we can reasonably determine. ** Changed in: apt (Ubuntu) Status: New => Opinion -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1960727 Title: When apt holds back updates, it fails to inform the user of the reason Status in apt package in Ubuntu: Opinion Bug description: In the case where apt refuses to install and holds back certain packages, only the following output is produced: root@system:/home/admin# apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages have been kept back: [ List of packages ] 0 upgraded, 0 newly installed, 0 to remove and 24 not upgraded. Missing is any explanation about which package is responsible for apt refusing to perform its job, or even what is the reason for that package being uninstallable. This bug leads users to believe that official Ubuntu packages are routinely misconstructed, corrupt, or otherwise junk. Fix: Instead of apt simply responding "No Dave, I'm Afraid I Can't Do that", correct the output to include the specific package that has a missing or unresolved dependency, so the user a) has confidence that the process works correctly and b) can proceed with fixing the problem. This bug is longstanding, so I don't think version details are required, but they follow anyway: 1) Distributor ID: Ubuntu Description:Ubuntu 20.04.3 LTS Release:20.04 Codename: focal 2) # apt --version apt 2.0.6 (amd64) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1960727/+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 1960751] Re: upower hogs CPU (50%, 27% etc, laptop lags)
capture of top output, such CPU use seems suspicious ** Attachment added: "Peek 2022-02-13 18-50.gif" https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1960751/+attachment/5560703/+files/Peek%202022-02-13%2018-50.gif -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1960751 Title: upower hogs CPU (50%, 27% etc, laptop lags) Status in upower package in Ubuntu: New Bug description: `upower --monitor-detail` has shown noninsane battery info twice and is silent otherwise, `upowerd` appears in `top` as eating 27%, 50% CPU (not all the time, but most of the time it is somehow top user of CPU) Computer become noticeably laggy recently, `upowerd` is so far sole abnormal symptom I was advised to file bug by people from Lubuntu Telegram channel. I would be happy to provide more info, but plan to reinstall OS soon due to macabre lagginess. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: upower 0.99.11-1build2 ProcVersionSignature: Ubuntu 5.4.0-99.112-lowlatency 5.4.162 Uname: Linux 5.4.0-99-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Sun Feb 13 18:42:10 2022 InstallationDate: Installed on 2021-01-06 (403 days ago) InstallationMedia: Lubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: upower UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1960751/+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 1960751] [NEW] upower hogs CPU (50%, 27% etc, laptop lags)
Public bug reported: `upower --monitor-detail` has shown noninsane battery info twice and is silent otherwise, `upowerd` appears in `top` as eating 27%, 50% CPU (not all the time, but most of the time it is somehow top user of CPU) Computer become noticeably laggy recently, `upowerd` is so far sole abnormal symptom I was advised to file bug by people from Lubuntu Telegram channel. I would be happy to provide more info, but plan to reinstall OS soon due to macabre lagginess. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: upower 0.99.11-1build2 ProcVersionSignature: Ubuntu 5.4.0-99.112-lowlatency 5.4.162 Uname: Linux 5.4.0-99-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Sun Feb 13 18:42:10 2022 InstallationDate: Installed on 2021-01-06 (403 days ago) InstallationMedia: Lubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: upower UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: upower (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1960751 Title: upower hogs CPU (50%, 27% etc, laptop lags) Status in upower package in Ubuntu: New Bug description: `upower --monitor-detail` has shown noninsane battery info twice and is silent otherwise, `upowerd` appears in `top` as eating 27%, 50% CPU (not all the time, but most of the time it is somehow top user of CPU) Computer become noticeably laggy recently, `upowerd` is so far sole abnormal symptom I was advised to file bug by people from Lubuntu Telegram channel. I would be happy to provide more info, but plan to reinstall OS soon due to macabre lagginess. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: upower 0.99.11-1build2 ProcVersionSignature: Ubuntu 5.4.0-99.112-lowlatency 5.4.162 Uname: Linux 5.4.0-99-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Sun Feb 13 18:42:10 2022 InstallationDate: Installed on 2021-01-06 (403 days ago) InstallationMedia: Lubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: upower UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1960751/+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 1960751] Re: upower hogs CPU (50%, 27% etc, laptop lags)
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1420395 is similar but with distinct symptoms - here too many updates appear to be not the cause of insane CPU use -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1960751 Title: upower hogs CPU (50%, 27% etc, laptop lags) Status in upower package in Ubuntu: New Bug description: `upower --monitor-detail` has shown noninsane battery info twice and is silent otherwise, `upowerd` appears in `top` as eating 27%, 50% CPU (not all the time, but most of the time it is somehow top user of CPU) Computer become noticeably laggy recently, `upowerd` is so far sole abnormal symptom I was advised to file bug by people from Lubuntu Telegram channel. I would be happy to provide more info, but plan to reinstall OS soon due to macabre lagginess. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: upower 0.99.11-1build2 ProcVersionSignature: Ubuntu 5.4.0-99.112-lowlatency 5.4.162 Uname: Linux 5.4.0-99-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Sun Feb 13 18:42:10 2022 InstallationDate: Installed on 2021-01-06 (403 days ago) InstallationMedia: Lubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: upower UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1960751/+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 1574154] Re: xorg.conf changed on start of lightdm service
Wow, a reply on a bug report after 6 years! I did not mean this to be negative, just surprised that I got a response this late. I forgot all about it, but this brings a lot back. Back then, I was mostly wondering what was in the mind of someone to change a user-modifiable config file.. But anyway, the T540 is running 20.04 now, and I dont see that problem anymore; maybe because I dont use a xorg.conf currently. And, the T540 is currently retiring ;-) Anyway, No problem for me anymore. Status can be changed to 'Time made us forget this' ;-) Btw: I'm still proud of my quick fix: 'chattr +i xorg.conf' ;-) -- 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/1574154 Title: xorg.conf changed on start of lightdm service Status in xorg package in Ubuntu: Incomplete Bug description: After upgrading from 15.10 (Wily) to 16.04 (Xenial), X wont start. It appears that my xorg.conf is modified such that I get a non-working way (I get a coredump in the video driver I think). I have a Thinkpad T530 with dual video cards, so I change the from the nvidia that is somewere(?) auto selected back to intel. Alas, restarting of lightdm service does not work: xorg.conf is re-modified. Manually starting a X session with 'startx' (after correcting xorg.conf) works as expected. Alas, nobody logs about this; that would have helped me find the culprit.. Who modifies my xorg.conf? Why? This never happened before, and should IMHO not be done. Temporary solution: 'chattr +i /etc/X11/xorg.conf'. This makes auto- changing impossible. But this is a hack. I should be allowed to change my system such that it works the way I want. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: MATE Date: Sun Apr 24 05:45:17 2016 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to xenial on 2016-04-21 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1574154/+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 1960747] Re: Autorotation of screen does not work on wayland, but on X
** Description changed: When physically rotating my 2-in-1 laptop Lenovo Yoga 7 Gen 6 AMD - 14ACN6, screen rotates properly under X, but not under Wayland. Also the lock screen rotation option is missing in the top-right menu under Wayland. It exists in X. - `iio-sensor-proxy` is loaded correctly: - ``` - systemctl status iio-sensor-proxy.service + + iio-sensor-proxy is being loaded correctly: + + --- + $ systemctl status iio-sensor-proxy.service ● iio-sensor-proxy.service - IIO Sensor Proxy service - Loaded: loaded (/lib/systemd/system/iio-sensor-proxy.service; static) - Active: active (running) since Sun 2022-02-13 15:43:37 CET; 2h 12min ago -Main PID: 787 (iio-sensor-prox) - Tasks: 3 (limit: 16544) - Memory: 1.4M - CPU: 5.688s - CGroup: /system.slice/iio-sensor-proxy.service - └─787 /usr/libexec/iio-sensor-proxy + Loaded: loaded (/lib/systemd/system/iio-sensor-proxy.service; static) + Active: active (running) since Sun 2022-02-13 15:43:37 CET; 2h 12min ago + Main PID: 787 (iio-sensor-prox) + Tasks: 3 (limit: 16544) + Memory: 1.4M + CPU: 5.688s + CGroup: /system.slice/iio-sensor-proxy.service + └─787 /usr/libexec/iio-sensor-proxy Feb 13 15:43:36 michaels-yoga systemd[1]: Starting IIO Sensor Proxy service... Feb 13 15:43:37 michaels-yoga systemd[1]: Started IIO Sensor Proxy service. - ``` - and `monitor-sensor` detects the physical rotation: - ``` - monitor-sensor - Waiting for iio-sensor-proxy to appear + --- + + monitor-sensor detects the physical rotation: + + --- + $ monitor-sensor + Waiting for iio-sensor-proxy to appear +++ iio-sensor-proxy appeared === Has accelerometer (orientation: normal) === Has ambient light sensor (value: 70,29, unit: lux) === No proximity sensor - Light changed: 65,27 (lux) - Light changed: 160,66 (lux) - Accelerometer orientation changed: right-up - Light changed: 40,16 (lux) - Light changed: 45,18 (lux) - Light changed: 40,16 (lux) - Light changed: 25,10 (lux) - Accelerometer orientation changed: left-up - Light changed: 20,08 (lux) - Light changed: 25,10 (lux) - Light changed: 35,14 (lux) - Accelerometer orientation changed: normal - Light changed: 155,64 (lux) - Accelerometer orientation changed: bottom-up - Light changed: 30,12 (lux) - Light changed: 40,16 (lux) - Light changed: 30,12 (lux) - Light changed: 145,60 (lux) - Accelerometer orientation changed: normal - ``` - Putting the laptop in tablet mode disables keyboard and touchpad correctly both under Wayland and X. - So obviously the sensors are working correctly, but signals are not being interpreted correctly in Wayland? + Light changed: 65,27 (lux) + Light changed: 160,66 (lux) + Accelerometer orientation changed: right-up + Light changed: 40,16 (lux) + Light changed: 45,18 (lux) + Light changed: 40,16 (lux) + Light changed: 25,10 (lux) + Accelerometer orientation changed: left-up + Light changed: 20,08 (lux) + Light changed: 25,10 (lux) + Light changed: 35,14 (lux) + Accelerometer orientation changed: normal + Light changed: 155,64 (lux) + Accelerometer orientation changed: bottom-up + Light changed: 30,12 (lux) + Light changed: 40,16 (lux) + Light changed: 30,12 (lux) + Light changed: 145,60 (lux) + Accelerometer orientation changed: normal + --- + + Putting the laptop in tablet mode disables keyboard and touchpad + correctly both under Wayland and X. + + So obviously the sensors are working correctly, but signals are not + being interpreted correctly in Wayland? + + --- ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 Uname: Linux 5.15.0-051500-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Feb 13 17:46:51 2022 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: - Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev c1) (prog-if 00 [VGA controller]) -Subsystem: Lenovo Cezanne [17aa:3813] + Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev c1) (prog-if 00 [VGA controller]) + Subsystem: Lenovo Cezanne [17aa:3813] InstallationDate: Installed on 2022-02-11 (1 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 82N7 ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=de_DE.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=de_DE.U
[Touch-packages] [Bug 1960747] [NEW] Autorotation of screen does not work on wayland, but on X
Public bug reported: When physically rotating my 2-in-1 laptop Lenovo Yoga 7 Gen 6 AMD - 14ACN6, screen rotates properly under X, but not under Wayland. Also the lock screen rotation option is missing in the top-right menu under Wayland. It exists in X. `iio-sensor-proxy` is loaded correctly: ``` systemctl status iio-sensor-proxy.service ● iio-sensor-proxy.service - IIO Sensor Proxy service Loaded: loaded (/lib/systemd/system/iio-sensor-proxy.service; static) Active: active (running) since Sun 2022-02-13 15:43:37 CET; 2h 12min ago Main PID: 787 (iio-sensor-prox) Tasks: 3 (limit: 16544) Memory: 1.4M CPU: 5.688s CGroup: /system.slice/iio-sensor-proxy.service └─787 /usr/libexec/iio-sensor-proxy Feb 13 15:43:36 michaels-yoga systemd[1]: Starting IIO Sensor Proxy service... Feb 13 15:43:37 michaels-yoga systemd[1]: Started IIO Sensor Proxy service. ``` and `monitor-sensor` detects the physical rotation: ``` monitor-sensor Waiting for iio-sensor-proxy to appear +++ iio-sensor-proxy appeared === Has accelerometer (orientation: normal) === Has ambient light sensor (value: 70,29, unit: lux) === No proximity sensor Light changed: 65,27 (lux) Light changed: 160,66 (lux) Accelerometer orientation changed: right-up Light changed: 40,16 (lux) Light changed: 45,18 (lux) Light changed: 40,16 (lux) Light changed: 25,10 (lux) Accelerometer orientation changed: left-up Light changed: 20,08 (lux) Light changed: 25,10 (lux) Light changed: 35,14 (lux) Accelerometer orientation changed: normal Light changed: 155,64 (lux) Accelerometer orientation changed: bottom-up Light changed: 30,12 (lux) Light changed: 40,16 (lux) Light changed: 30,12 (lux) Light changed: 145,60 (lux) Accelerometer orientation changed: normal ``` Putting the laptop in tablet mode disables keyboard and touchpad correctly both under Wayland and X. So obviously the sensors are working correctly, but signals are not being interpreted correctly in Wayland? ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 Uname: Linux 5.15.0-051500-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Feb 13 17:46:51 2022 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Cezanne [17aa:3813] InstallationDate: Installed on 2022-02-11 (1 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 82N7 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.15.0-051500-generic root=UUID=d1796991-349c-4784-b8c3-e0a2eb2fc132 ro rootflags=subvol=@ quiet splash mem_sleep_default=deep vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/12/2021 dmi.bios.release: 1.25 dmi.bios.vendor: LENOVO dmi.bios.version: H9CN25WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76463 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga 7 14ACN6 dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnLENOVO:bvrH9CN25WW:bd11/12/2021:br1.25:efr1.25:svnLENOVO:pn82N7:pvrYoga714ACN6:rvnLENOVO:rnLNVNB161216:rvrSDK0T76463WIN:cvnLENOVO:ct31:cvrYoga714ACN6:skuLENOVO_MT_82N7_BU_idea_FM_Yoga714ACN6: dmi.product.family: Yoga 7 14ACN6 dmi.product.name: 82N7 dmi.product.sku: LENOVO_MT_82N7_BU_idea_FM_Yoga 7 14ACN6 dmi.product.version: Yoga 7 14ACN6 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.6-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.1 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 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish ubuntu wayland-session ** Summary changed: - Autorotation of screen does not work on wayland, but on xorg + Autorotation of screen does not work on wayland, but on X -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in
[Touch-packages] [Bug 1960742] [NEW] Xorg freeze
Public bug reported: before it crashes, 3 LEDs (Power, mayus,block number) turn on and turn off about 3 times.. And all will be freeze it needs to shutdown keeping pressed the I/O button ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Feb 13 11:03:30 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Device [8086:4e55] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:2212] InstallationDate: Installed on 2022-02-09 (4 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: INTEL V14 ProcEnviron: LANGUAGE=es_EC:es PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_EC.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic root=UUID=31ee87c2-d9b1-413d-bc93-15224f6ba1ec ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/25/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: WZ362D.fBNAPLL02.2105061 dmi.board.asset.tag: Default string dmi.board.name: V14 dmi.board.vendor: INET dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.ec.firmware.release: 1.2 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrWZ362D.fBNAPLL02.2105061:bd05/25/2021:br5.19:efr1.2:svnINTEL:pnV14:pvrDefaultstring:rvnINET:rnV14:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:sku2105061: dmi.product.family: Jasper lake dmi.product.name: V14 dmi.product.sku: 2105061 dmi.product.version: Default string dmi.sys.vendor: INTEL version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 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 freeze 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/1960742 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: before it crashes, 3 LEDs (Power, mayus,block number) turn on and turn off about 3 times.. And all will be freeze it needs to shutdown keeping pressed the I/O button ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Feb 13 11:03:30 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Device [8086:4e55] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:2212] InstallationDate: Installed on 2022-02-09 (4 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: INTEL V14 ProcEnviron: LANGUAGE=es_EC:es PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_EC.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic root=UUID=31ee87c2-d9b1-413d-bc93-15224f6ba1ec ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/25/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: WZ362D.fBNAPLL02.2105061 dmi.board.asset.
[Touch-packages] [Bug 1960737] [NEW] /usr/lib/x86_64-linux-gnu/libgtk-3-0/gtk-query-immodules-3.0: symbol lookup error: /usr/lib/x86_64-linux-gnu/libgdk-3.so.0: undefined symbol: wl_proxy_marshal_flag
Public bug reported: /usr/lib/x86_64-linux-gnu/libgtk-3-0/gtk-query-immodules-3.0: symbol lookup error: /usr/lib/x86_64-linux-gnu/libgdk-3.so.0: undefined symbol: wl_proxy_marshal_flags ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New -- 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/1960737 Title: /usr/lib/x86_64-linux-gnu/libgtk-3-0/gtk-query-immodules-3.0: symbol lookup error: /usr/lib/x86_64-linux-gnu/libgdk-3.so.0: undefined symbol: wl_proxy_marshal_flags Status in gtk+3.0 package in Ubuntu: New Bug description: /usr/lib/x86_64-linux-gnu/libgtk-3-0/gtk-query-immodules-3.0: symbol lookup error: /usr/lib/x86_64-linux-gnu/libgdk-3.so.0: undefined symbol: wl_proxy_marshal_flags To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1960737/+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 1960727] Re: When apt holds back updates, it fails to inform the user of the reason
Can you provide a complete (preferably real) example of what output you would expect? Honestly, I don't see this working as in the general case the reason is not simple – its at least my experience from staring at debug output for hours to figure such things out in the development branches of a distribution. That is because a package is seldomly held back because it is itself "misconstructed" (and never because its "corrupt, or otherwise junk"), it is usually the state of the universe at large (so to speak) who is at 'fault'. Happy to be proven wrong through. Ideally with a tool who can deduce these things which could be used in apt & elsewhere. Also, but that comes down to user attitude I guess, is that as a user I am trusting the tools I am using. So it justifying all its decisions in detail for me to review feels way too micro-managing to me. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1960727 Title: When apt holds back updates, it fails to inform the user of the reason Status in apt package in Ubuntu: New Bug description: In the case where apt refuses to install and holds back certain packages, only the following output is produced: root@system:/home/admin# apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages have been kept back: [ List of packages ] 0 upgraded, 0 newly installed, 0 to remove and 24 not upgraded. Missing is any explanation about which package is responsible for apt refusing to perform its job, or even what is the reason for that package being uninstallable. This bug leads users to believe that official Ubuntu packages are routinely misconstructed, corrupt, or otherwise junk. Fix: Instead of apt simply responding "No Dave, I'm Afraid I Can't Do that", correct the output to include the specific package that has a missing or unresolved dependency, so the user a) has confidence that the process works correctly and b) can proceed with fixing the problem. This bug is longstanding, so I don't think version details are required, but they follow anyway: 1) Distributor ID: Ubuntu Description:Ubuntu 20.04.3 LTS Release:20.04 Codename: focal 2) # apt --version apt 2.0.6 (amd64) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1960727/+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 1377338] Re: apparmor may fail to load some profiles if one is corrupted
I'm a bit confused:
* On the one hand, this bug is *not* marked is fixed in AppArmor
upstream; the only reason it was marked as "Fix Released" for Ubuntu is
the pile of kludges added in /lib/apparmor/functions, that I migrated to
rc.apparmor.functions upstream a few years back.
* On the other hand, the aforementioned pile of kludges was removed by
https://gitlab.com/apparmor/apparmor/-/commit/0b8ea047e88b250862da73a968b1cd1f8b7f6b91
because "LP:1377338 has been fixed for quite awhile".
So, it seems to me that:
* Either the parser bug was actually fixed upstream, and then the status this
bug is incorrect: it should be "Fix Released".
* Or the parser bug is still there, and then
0b8ea047e88b250862da73a968b1cd1f8b7f6b91 was done based on a misunderstanding.
Which is it?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1377338
Title:
apparmor may fail to load some profiles if one is corrupted
Status in AppArmor:
Triaged
Status in apparmor package in Ubuntu:
Fix Released
Status in click-apparmor package in Ubuntu:
Fix Released
Status in apparmor package in Ubuntu RTM:
Fix Released
Status in click-apparmor package in Ubuntu RTM:
Fix Released
Bug description:
Steps to reproduce (on the emulator):
1. sudo sh -c 'echo foo >
/var/lib/apparmor/profiles/click_com.ubuntu.music_music_1.3.638'
2. sudo start apparmor ACTION=teardown
3. sudo start apparmor
start: Job failed to start
4. sudo aa-status|egrep '^ '|grep -v '('| sort -u > /tmp/aa-status.music_bad
5. sudo rm -f /var/lib/apparmor/profiles/click_com.ubuntu.music_music_1.3.638
6. sudo aa-clickhook # regenerates the missing profile to had a good one
7. sudo start apparmor ACTION=teardown
8. sudo start apparmor
9. sudo aa-status|egrep '^ '|grep -v '('| sort -u > /tmp/aa-status.music_good
10. diff -Naur /tmp/aa-status.music_bad /tmp/aa-status.music_good
--- /tmp/aa-status.music_bad 2014-10-03 22:47:52.890906744 +
+++ /tmp/aa-status.music_good 2014-10-03 22:49:54.372739381 +
@@ -13,6 +13,10 @@
com.ubuntu.developer.webapps.webapp-twitter_webapp-twitter_1.0.18//oxide_helper
com.ubuntu.developer.webapps.webapp-twitter_webapp-twitter-helper_1.0.18
com.ubuntu.dropping-letters_dropping-letters_0.1.2.2.66
+ com.ubuntu.music_music_1.3.638
+ com.ubuntu.shorts_shorts_0.2.330
+ com.ubuntu.sudoku_sudoku_1.1.292
+ com.ubuntu.weather_weather_1.1.374
lxc-container-default
lxc-container-default-with-mounting
lxc-container-default-with-nesting
Expected results: only com.ubuntu.music_music_1.3.638 should be
missing.
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1377338/+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 1528921] Re: rsync hangs on select(5, [], [4], [], {60, 0}
All tests passed already.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
https://bugs.launchpad.net/bugs/1528921
Title:
rsync hangs on select(5, [], [4], [], {60, 0}
Status in rsync:
Unknown
Status in rsync package in Ubuntu:
Fix Released
Status in rsync source package in Bionic:
Fix Committed
Status in rsync source package in Focal:
Fix Committed
Bug description:
[Impact]
What the user suffering from this bug experiences is that the big
amount of informative messages related to the copy process with the
three spawned processes(sender, receiver and generator) exhaust the
I/O buffer and the sync gets stuck, either because there are too many
files to synchronise and/or because too many detail messages (levels
of verbose mode) have been requested in the output.
The fix, that comes from upstream and is applied there since version
3.2.0., increments the size of the receiver's I/O buffer.
[Test Plan]
This test plan is for Focal, but it's the same for Bionic.
0.Preparing the test environment:
#Preparing the container
lxc launch images:ubuntu/focal rsync-iobuffer-focal
lxc shell rsync-iobuffer-focal
apt update -y
apt upgrade -y
#Installing necessary tools
apt install rsync
#Get test cases from comments #16 and #19 on this LP bug: As test case
#16 covers both aspects (a lot of files and upper verbosity) and test
#19 uses a huge tarball (120 Mb), I'm removing from this SRU the #19
scenario (but, please, feel to reach me it if you consider it
necessary and I'll provide the steps and bad/good scenarios).
cd /tmp/
#16
Paste the contents of https://pastebin.com/raw/ctzJJGwt:
#!/bin/bash
mkdir source_dir
pushd source_dir
dd if=/dev/zero of=source bs=600K count=1
for i in `seq 1 11500`;
do
cp -v source file_$i;
done
rm source
for i in `seq 1 10`;
do
dd if=/dev/zero of=file_large_$i bs=200M count=1
done
popd
echo "Created 11500 files with size 600K and 10 files with size 200M, try the
following command:"
echo "rsync -avvvz --delete source_dir target_dir"
in a new file script_comment16.sh
chmod +x script_comment16.sh
./script_comment16.sh
1. Bad cases (without and with using strace):
# Scenario from comment 16
$ rsync -avvvz --delete source_dir target_dir
sending incremental file list
[sender] make_file(source_dir,*,0)
send_file_list done
[sender] pushing local filters for /root/source_dir/
[sender] make_file(source_dir/file_3048,*,2)
[sender] make_file(source_dir/file_11358,*,2)
[sender] make_file(source_dir/file_5914,*,2)
[sender] make_file(source_dir/file_5880,*,2)
[sender] make_file(source_dir/file_9318,*,2)
[sender] make_file(source_dir/file_5539,*,2)
[...]
sending file_sum
false_alarms=0 hash_hits=0 matches=0
sender finished source_dir/file_10807
send_files(903, source_dir/file_10808)
send_files mapped source_dir/file_10808 of size 614400
calling match_sums source_dir/file_10808
source_dir/file_10808
It hangs here, where using strace we can see:
$ strace rsync -avvvz --delete source_dir target_dir
source_dir/file_11280
read(3,
"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 262144)
= 262144
read(3,
"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 262144)
= 262144
read(3,
"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 90112) =
90112
select(6, [5], [4], [5], {tv_sec=60, tv_usec=0}) = 1 (in [5], left
{tv_sec=59, tv_usec=96})
read(5,
"\0\0\0\0\0\0\0\1\0\240\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\240\0\0\0"...,
1900) = 1900
select(5, [], [4], [], {tv_sec=60, tv_usec=0}) = 0 (Timeout)
select(5, [], [4], [], {tv_sec=60, tv_usec=0}) = 0 (Timeout)
select(5, [], [4], [], {tv_sec=60, tv_usec=0}
1. Good cases:
# Scenario from comment 16
$ rsync -avvvz --delete source_dir target_dir
sending incremental file list
[sender] make_file(source_dir,*,0)
send_file_list done
[sender] pushing local filters for /tmp/source_dir/
[sender] make_file(source_dir/file_3052,*,2)
[sender] make_file(source_dir/file_1766,*,2)
[sender] make_file(source_dir/file_10466,*,2)
[sender] make_file(source_dir/file_9375,*,2)
[sender] make_file(source_dir/file_7260,*,2)
[sender] make_file(source_dir/file_5554,*,2)
[sender] make_file(source_dir/file_5523,*,2)
[sender] make_file(source_dir/file_1685,*,2)
[sender] make_file(source_dir/file_7217,*,2)
[sender] make_file(source_dir/file_10411,*,2)
[...]
generate_files finished
sent 9,555,678 bytes received 3,599,560 bytes 124,694.20 bytes/sec
total size is 9,162,752,000 speedup is 696.51
[Where problems could occur]
Perhaps the buffer size may not be sufficient for an operation
involving a very huge amount of data, as reported upstream here (
https://bugzilla.samba.org/show_bug.cgi?id=11166#c9 )
[Touch-packages] [Bug 1960582] Re: [critical] dpkg error while processing - can't install nor upgrade
** Also affects: apt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1960582 Title: [critical] dpkg error while processing - can't install nor upgrade Status in apt package in Ubuntu: New Status in dpkg package in Ubuntu: New Bug description: My current ubuntu version : No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 Codename: jammy Issue : when `sudo apt update` is ok, all newest package is downloaded but `sudo apt ugprade` show current error : ] sudo apt upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following packages have been kept back: librygel-renderer-2.6-2 librygel-server-2.6-2 rygel The following packages will be upgraded: bolt code deja-dup enchant-2 fwupd gdm3 gir1.2-gdm-1.0 gir1.2-gst-plugins-base-1.0 gir1.2-nm-1.0 gir1.2-nma-1.0 gir1.2-upowerglib-1.0 gjs gstreamer1.0-alsa gstreamer1.0-gl gstreamer1.0-gtk3 gstreamer1.0-plugins-base gstreamer1.0-plugins-base-apps gstreamer1.0-plugins-good gstreamer1.0-pulseaudio gstreamer1.0-x initramfs-tools initramfs-tools-bin initramfs-tools-core iputils-ping iputils-tracepath language-pack-en language-pack-gnome-en libenchant-2-2 libfwupd2 libfwupdplugin5 libgdm1 libgjs0g libgstreamer-gl1.0-0 libgstreamer-plugins-base1.0-0 libgstreamer-plugins-good1.0-0 libnl-3-200 libnl-genl-3-200 libnl-route-3-200 libnm0 libnma-common libnma0 libpkcs11-helper1 libseccomp2 libunistring2 libunistring2:i386 libupower-glib3 media-types nano network-manager network-manager-config-connectivity-ubuntu python3-paramiko python3-software-properties simple-scan software-properties-common software-properties-gtk upower 56 upgraded, 0 newly installed, 0 to remove and 3 not upgraded. 10 not fully installed or removed. Need to get 0 B/94,6 MB of archives. After this operation, 1.928 kB of additional disk space will be used. Do you want to continue? [Y/n] Y Extracting templates from packages: 100% Preconfiguring packages ... Setting up dpkg (1.21.1ubuntu1) ... head: error reading 'dpkg': Is a directory dpkg: error processing package dpkg (--configure): installed dpkg package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: dpkg E: Sub-process /usr/bin/dpkg returned an error code (1) i have to resintall all of the package in cache with `sudo dpkg -i /var/cache/apt/archives/*.deb `, but the cache sometimes is not the newest packages and when i rerun `sudo apt upgrade`, there is still not the newest package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1960582/+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 1892825] Autopkgtest regression report (glibc/2.31-0ubuntu9.5)
All autopkgtests for the newly accepted glibc (2.31-0ubuntu9.5) for focal have finished running. The following regressions have been reported in tests triggered by the package: garli/2.1-3build1 (armhf) fpc/3.0.4+dfsg-23 (armhf) lazarus/2.0.6+dfsg-3 (armhf) libuv1/1.34.2-1ubuntu1.3 (i386) ikiwiki-hosting/0.20180719-2 (armhf) rtags/2.37-1 (amd64) mercurial/5.3.1-1ubuntu1 (amd64, ppc64el) foo2zjs/20171202dfsg0-4 (armhf) frameworkintegration/5.68.0-0ubuntu1 (armhf) hilive/2.0a-3build2 (arm64) ruby-libxml/3.1.0-2 (s390x) plasma-framework/5.68.0-0ubuntu1 (armhf) feersum/1.407-2 (s390x) r-bioc-delayedarray/0.12.2+dfsg-1 (armhf) php-luasandbox/3.0.3-2build2 (ppc64el) snapd-glib/1.58-0ubuntu0.20.04.0 (armhf) bolt/0.8-4ubuntu1 (ppc64el) threadweaver/5.68.0-0ubuntu1 (armhf) python3.8/3.8.10-0ubuntu1~20.04.2 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#glibc [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1892825 Title: update-locale not perform correctly sanity checks Status in glibc package in Ubuntu: In Progress Status in pam package in Ubuntu: New Status in glibc source package in Bionic: New Status in pam source package in Bionic: New Status in glibc source package in Focal: Fix Committed Status in pam source package in Focal: New Status in glibc source package in Hirsute: New Status in pam source package in Hirsute: New Status in glibc source package in Impish: New Status in pam source package in Impish: New Bug description: [impact] A simple typo using the update-locale script can render a system inoperable without booting into single user mode or similar: $ sudo update-locale LANGUAGE = en_US.UTF-8 $ sudo -s sudo: pam_open_session: Bad item passed to pam_*_item() sudo: policy plugin failed session initialization [test case] $ cp /etc/default/locale /tmp/locale $ update-locale --locale-file /tmp/locale LANGUAGE = en_US.UTF-8 "diff -u /etc/default/locale /tmp/locale" should be empty. [original description] By passing wrong input as following: sudo update-locale LANGUAGE = en_US.UTF-8 result is: ... #LANGUAGE=en = This "equal" sign that was added makes system completely unusable(can't run sudo anymore): bentzy@bentzy-nb:~$ sudo vim /etc/default/locale sudo: pam_open_session: Bad item passed to pam_*_item() sudo: policy plugin failed session initialization Fixed it booting from installation disk and fixing corrupted /etc/default/locale ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: locales 2.31-0ubuntu9 Uname: Linux 5.5.4-050504-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Aug 25 09:36:03 2020 InstallationDate: Installed on 2020-08-17 (7 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: glibc UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1892825/+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] Autopkgtest regression report (glibc/2.31-0ubuntu9.5)
All autopkgtests for the newly accepted glibc (2.31-0ubuntu9.5) for focal have finished running. The following regressions have been reported in tests triggered by the package: garli/2.1-3build1 (armhf) fpc/3.0.4+dfsg-23 (armhf) lazarus/2.0.6+dfsg-3 (armhf) libuv1/1.34.2-1ubuntu1.3 (i386) ikiwiki-hosting/0.20180719-2 (armhf) rtags/2.37-1 (amd64) mercurial/5.3.1-1ubuntu1 (amd64, ppc64el) foo2zjs/20171202dfsg0-4 (armhf) frameworkintegration/5.68.0-0ubuntu1 (armhf) hilive/2.0a-3build2 (arm64) ruby-libxml/3.1.0-2 (s390x) plasma-framework/5.68.0-0ubuntu1 (armhf) feersum/1.407-2 (s390x) r-bioc-delayedarray/0.12.2+dfsg-1 (armhf) php-luasandbox/3.0.3-2build2 (ppc64el) snapd-glib/1.58-0ubuntu0.20.04.0 (armhf) bolt/0.8-4ubuntu1 (ppc64el) threadweaver/5.68.0-0ubuntu1 (armhf) python3.8/3.8.10-0ubuntu1~20.04.2 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#glibc [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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 Released 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
