[Touch-packages] [Bug 1895618] Re: ubuntu dock bounces when on bottom and auto-hide is active
*** This bug is a duplicate of bug 1881941 *** https://bugs.launchpad.net/bugs/1881941 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1881941, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Package changed: xorg (Ubuntu) => gnome-shell-extension-ubuntu-dock (Ubuntu) ** This bug has been marked a duplicate of bug 1881941 Ubuntu dock behaves crazy when hidden at the bottom of the screen -- 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/1895618 Title: ubuntu dock bounces when on bottom and auto-hide is active Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: While dock is locked to the bottom of the screen and hidden while not in use, once un-hidden/activated it will bounce back and forth between hidden and un-hidden. This is much more apparent or frequent when there is a window that is either maximized or has a boarder near the bottom of the screen next to where the dock will be activated at (Usually the bottom 10 or 20 pixels of the screen). This is potentially a GNOME issues or an "Ubuntu Dock", issue. However, I don't have the time at the moment to diagnose this further. Attached is a video which shows the bug in action. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.100 Fri May 29 08:45:51 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Sep 14 22:19:54 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 630 [1028:07e1] Subsystem: Dell GP107M [GeForce GTX 1050 Mobile] [1028:07e1] InstallationDate: Installed on 2020-04-25 (143 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 007: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 005: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 1bcf:28b0 Sunplus Innovation Technology Inc. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5577 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=1a7811cb-1019-45cb-97af-94a5bf22c0c3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.3 dmi.board.name: 0MVD5F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.1.3:bd12/02/2018:svnDellInc.:pnInspiron5577:pvr1.1.3:rvnDellInc.:rn0MVD5F:rvrA00:cvnDellInc.:ct10:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 5577 dmi.product.sku: 07E1 dmi.product.version: 1.1.3 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 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
[Touch-packages] [Bug 1895618] [NEW] ubuntu dock bounces when on bottom and auto-hide is active
Public bug reported: While dock is locked to the bottom of the screen and hidden while not in use, once un-hidden/activated it will bounce back and forth between hidden and un-hidden. This is much more apparent or frequent when there is a window that is either maximized or has a boarder near the bottom of the screen next to where the dock will be activated at (Usually the bottom 10 or 20 pixels of the screen). This is potentially a GNOME issues or an "Ubuntu Dock", issue. However, I don't have the time at the moment to diagnose this further. Attached is a video which shows the bug in action. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.100 Fri May 29 08:45:51 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Sep 14 22:19:54 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 630 [1028:07e1] Subsystem: Dell GP107M [GeForce GTX 1050 Mobile] [1028:07e1] InstallationDate: Installed on 2020-04-25 (143 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 007: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 005: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 1bcf:28b0 Sunplus Innovation Technology Inc. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5577 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=1a7811cb-1019-45cb-97af-94a5bf22c0c3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.3 dmi.board.name: 0MVD5F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.1.3:bd12/02/2018:svnDellInc.:pnInspiron5577:pvr1.1.3:rvnDellInc.:rn0MVD5F:rvrA00:cvnDellInc.:ct10:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 5577 dmi.product.sku: 07E1 dmi.product.version: 1.1.3 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 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 ubuntu ** Attachment added: "Video of the bounce that I am talking about." https://bugs.launchpad.net/bugs/1895618/+attachment/5410901/+files/2020-09-14%2022-14-22.mkv -- 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/1895618 Title: ubuntu dock bounces when on bottom and auto-hide is active Status in xorg package in Ubuntu: New Bug description: While dock is locked to the bottom of the screen and hidden while not in use, once un-hidden/activated it will bounce back and forth between hidden and un-hidden. This is much more apparent or frequent when there is a window that is either maximized or has a boarder near the bottom of the screen next to where the dock will be activated at (Usually the bottom 10 or 20 pixels of the screen). This is potentially a GNOME issues or an "Ubuntu Dock", issue. However, I don't have the time at the moment to diagnose this further. Attached is a video which shows the bug in
[Touch-packages] [Bug 1895600] Re: Error in xorg package
That's the wrong driver for your system which is why it doesn't install properly. The best and newest driver for Intel is the one you already have installed: /usr/lib/xorg/modules/drivers/modesetting_drv.so If you really want to experiment with the old driver then the package to install is: xserver-xorg-video-intel-hwe-18.04 but I don't recommend it. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1895600 Title: Error in xorg package Status in xorg-server package in Ubuntu: Invalid Bug description: I want to check if my video graphics card of Intel is installed in the system but am unable to do so. In terminal, I give the following command: ramraj@luna:~$ sudo apt-get install xserver-xorg-video-intel Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: xserver-xorg-video-intel : Depends: xorg-video-abi-23 Depends: xserver-xorg-core (>= 2:1.18.99.901) E: Unable to correct problems, you have held broken packages. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Sep 15 06:44:30 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:0591] InstallationDate: Installed on 2019-07-01 (441 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. Inspiron 3421 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=06ae3a9b-634e-4cdc-95dc-76d422c99559 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/09/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0RDCXP dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA08:bd09/09/2013:svnDellInc.:pnInspiron3421:pvrNotSpecified:rvnDellInc.:rn0RDCXP:rvrA08:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3421 dmi.product.sku: Inspiron 3421 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1895600/+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 1894234] Re: Bluetooth not working with Gnome in Groovy (20.10)
** Changed in: bluez (Ubuntu) Status: Incomplete => Fix Released -- 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/1894234 Title: Bluetooth not working with Gnome in Groovy (20.10) Status in bluez package in Ubuntu: Fix Released Bug description: Having plugged in a USB bluetooth dongle, the gnome-bluetooth settiogs report that I have no bluetooth adapter, and I should plug one in. At the same time, I can see the bluetooth adapter with hciconfig, and in fact, I can pair with remote bluetooth devices using a 3rd party bluetooth manager (blueman). Obviously this is not ideal, as it is not fully integrated with gnome, sound devices are not fully available etc.. I'm not sure what else I can provide, but:- # hciconfig -a hci0: Type: Primary Bus: USB BD Address: 24:4B:FE:3A:21:65 ACL MTU: 1021:6 SCO MTU: 255:12 UP RUNNING PSCAN RX bytes:1117 acl:0 sco:0 events:72 errors:0 TX bytes:4973 acl:0 sco:0 commands:72 errors:0 Features: 0xff 0xff 0xff 0xfe 0xdb 0xfd 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF PARK Link mode: SLAVE ACCEPT Name: 'morpheous' Class: 0x1c0104 Service Classes: Rendering, Capturing, Object Transfer Device Class: Computer, Desktop workstation HCI Version: 5.1 (0xa) Revision: 0xb LMP Version: 5.1 (0xa) Subversion: 0x8761 Manufacturer: Realtek Semiconductor Corporation (93) root@morpheous:~# When I got to settings, it tells me I have no bluetooth devices plugged in! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1894234/+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 1894338] Re: [Samsung Earphones Tuned by AKG] Volume control buttons don't work
OK thanks. Just to confirm, do the volume buttons work in Windows 10 on the *same* laptop? ** Tags added: focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1894338 Title: [Samsung Earphones Tuned by AKG] Volume control buttons don't work Status in pulseaudio package in Ubuntu: Incomplete Bug description: My earphones are the one coming with Samsung Galaxy S8 (here: https://www.samsung.com/us/mobile/mobile-accessories/phones/samsung- earphones-tuned-by-akg--gray-eo-ig955bsegus) and on my Ubuntu 18.04 (dual-boot with Windows 10, Secure Boot enabled) Trying to set the volume from my earphones' controls doesn't work, no modification on the volume, the sound bar on Ubuntu doesn't appear in order to indicate volume change. I would like to change the master volume, or whatever my common laptop controls do when I up/down the volume controls on my earphones, like it happens on Windows 10. Why does the erroneous behavior of being unable to set volume from my earphones happen? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.10 ProcVersionSignature: Ubuntu 4.15.0-115.116-generic 4.15.18 Uname: Linux 4.15.0-115-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jason 3523 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Sep 4 23:29:52 2020 InstallationDate: Installed on 2018-09-28 (706 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=el_GR.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/17/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.16.0 dmi.board.name: 02P5YY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.16.0:bd02/17/2020:svnDellInc.:pnInspiron7570:pvr:rvnDellInc.:rn02P5YY:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7570 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1894338/+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 1574251] Re: Resuming from screen lock with a multimonitor setup causes all windows to migrate to the "primary screen"
*** This bug is a duplicate of bug 1001984 *** https://bugs.launchpad.net/bugs/1001984 ** Package changed: xorg (Ubuntu) => compiz (Ubuntu) ** This bug has been marked a duplicate of bug 1001984 Maximised window changes monitor through lock screen or 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/1574251 Title: Resuming from screen lock with a multimonitor setup causes all windows to migrate to the "primary screen" Status in compiz package in Ubuntu: Confirmed Bug description: Hardware: * Dell M3800; builtin screen is a 15", 1920x1080 screen; * an external display connected via HDMI, brand ASUS, same resolution; * the configuration via settings is that the screen on the laptop is on the left and the ASUS screen on the right. The bug did not appear with 15.10; only starting with 16.04 did this start to happen. This is a laptop with a nVidia chipset, and it doesn't matter whether I use nouveau or the proprietary nVidia driver. When the screen locks after inactivity, or I lock it explicitly, and then some time later (for some definition of "later") log back in, all windows have migrated to the laptop screen. This is annoying since it means I have to move all the windows over again. I am not sure what details I should give. I only noticed that compared to 15.10 which did not exhibit the bug, the ASUS screen takes longer to "wake up" again... My hunch here is that the HDMI port was deactivated. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 .tmp.unity_support_test.0: .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Apr 24 14:43:24 2016 DistUpgraded: 2016-04-23 03:26:23,168 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-21-generic, x86_64: installed nvidia-361, 361.42, 4.4.0-21-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell 4th Gen Core Processor Integrated Graphics Controller [1028:060d] InstallationDate: Installed on 2015-07-16 (282 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. Dell Precision M3800 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-21-generic.efi.signed root=UUID=b8f6e64b-30d4-4621-8885-8079631fbd0e ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UnitySupportTest: Error: command ['/usr/lib/nux/unity_support_test', '-p', '-f'] failed with exit code 1: Error: unable to create the OpenGL context UpgradeStatus: Upgraded to xenial on 2016-04-23 (1 days ago) dmi.bios.date: 01/08/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: Dell Precision M3800 dmi.board.vendor: Dell Inc. dmi.board.version: A09 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA09:bd01/08/2015:svnDellInc.:pnDellPrecisionM3800:pvrA09:rvnDellInc.:rnDellPrecisionM3800:rvrA09:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Dell Precision M3800 dmi.product.version: A09 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sat Apr 23 19:16:20 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4589 vendor AUO xserver.version: 2:1.18.3-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1574251/+subscriptions -- Mailing list:
[Touch-packages] [Bug 1595695] Re: Bluetooth indicator disappears every time bluetooth is being turned off
There is an upstream fix gnome-shell!1174 but it doesn't seem to work. So this bug can stay open. ** Changed in: gnome-bluetooth (Ubuntu) Importance: Undecided => Medium ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Medium ** No longer affects: indicator-bluetooth (Ubuntu) ** No longer affects: gnome-bluetooth (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Triaged ** Tags added: groovy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1595695 Title: Bluetooth indicator disappears every time bluetooth is being turned off Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Triaged Bug description: In Ubuntu 16.04, every time I turn off bluetooth, the indicator icon disappears from the top panel. Each time I have to re-enable it by system setting or via dash. I expect it to behave in a same way as network indicator instead of disappearing. Here is the link with some info which could be helpful https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1126108 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1595695/+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 1895600] [NEW] Error in xorg package
Public bug reported: I want to check if my video graphics card of Intel is installed in the system but am unable to do so. In terminal, I give the following command: ramraj@luna:~$ sudo apt-get install xserver-xorg-video-intel Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: xserver-xorg-video-intel : Depends: xorg-video-abi-23 Depends: xserver-xorg-core (>= 2:1.18.99.901) E: Unable to correct problems, you have held broken packages. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Sep 15 06:44:30 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:0591] InstallationDate: Installed on 2019-07-01 (441 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. Inspiron 3421 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=06ae3a9b-634e-4cdc-95dc-76d422c99559 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/09/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0RDCXP dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA08:bd09/09/2013:svnDellInc.:pnInspiron3421:pvrNotSpecified:rvnDellInc.:rn0RDCXP:rvrA08:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3421 dmi.product.sku: Inspiron 3421 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic 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/1895600 Title: Error in xorg package Status in xorg package in Ubuntu: New Bug description: I want to check if my video graphics card of Intel is installed in the system but am unable to do so. In terminal, I give the following command: ramraj@luna:~$ sudo apt-get install xserver-xorg-video-intel Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: xserver-xorg-video-intel : Depends: xorg-video-abi-23 Depends: xserver-xorg-core (>= 2:1.18.99.901) E: Unable to correct problems, you have held broken packages. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Sep 15 06:44:30 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches
[Touch-packages] [Bug 1882179] Re: package lvm2 2.03.07-1ubuntu1 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lvm2 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1882179 Title: package lvm2 2.03.07-1ubuntu1 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1 Status in lvm2 package in Ubuntu: Confirmed Bug description: I had run "sudo apt install qemu qemu-kvm libvirt-clients libvirt- daemon-system bridge-utils virt-manager", when this system problem detected error came. Please check it if it causes any issue. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: lvm2 2.03.07-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Jun 5 09:40:05 2020 ErrorMessage: installed lvm2 package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2019-08-17 (292 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: lvm2 Title: package lvm2 2.03.07-1ubuntu1 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-05-08 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1882179/+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 1894338] Re: [Samsung Earphones Tuned by AKG] Volume control buttons don't work
Just tried a live USB of 20.04.1 and yes, the same problem persists exactly as it is. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1894338 Title: [Samsung Earphones Tuned by AKG] Volume control buttons don't work Status in pulseaudio package in Ubuntu: Incomplete Bug description: My earphones are the one coming with Samsung Galaxy S8 (here: https://www.samsung.com/us/mobile/mobile-accessories/phones/samsung- earphones-tuned-by-akg--gray-eo-ig955bsegus) and on my Ubuntu 18.04 (dual-boot with Windows 10, Secure Boot enabled) Trying to set the volume from my earphones' controls doesn't work, no modification on the volume, the sound bar on Ubuntu doesn't appear in order to indicate volume change. I would like to change the master volume, or whatever my common laptop controls do when I up/down the volume controls on my earphones, like it happens on Windows 10. Why does the erroneous behavior of being unable to set volume from my earphones happen? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.10 ProcVersionSignature: Ubuntu 4.15.0-115.116-generic 4.15.18 Uname: Linux 4.15.0-115-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jason 3523 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Sep 4 23:29:52 2020 InstallationDate: Installed on 2018-09-28 (706 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=el_GR.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/17/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.16.0 dmi.board.name: 02P5YY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.16.0:bd02/17/2020:svnDellInc.:pnInspiron7570:pvr:rvnDellInc.:rn02P5YY:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7570 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1894338/+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 1895422] Re: Sound card not detected on Dell Latitude 9510 (Realtek ALC711)
I installed linux-oem-20.04 and also turned on focal-proposed updates and did apt-get update && apt-get upgrade. Though -- this was only enough to get it to recognize the speaker. The pitch/video speed is still wrong, so it's not really quite usable. I should correct something I said earlier: video playback is just too fast across the board, e.g. on Youtube it's playing at maybe double the speed and the pitch is high. However, even when I slow the playback speed down to normal (by selecting 0.5x speed) the pitch is *still* too high. I suspect the wrong driver is being used for the sound card. It is still detecting "00:1f.3 Multimedia audio controller: Intel Corporation Device 02c8" instead of the Realtek card. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1895422 Title: Sound card not detected on Dell Latitude 9510 (Realtek ALC711) Status in alsa-driver package in Ubuntu: Confirmed Bug description: I am running Ubuntu 20.04.01 LTS, kernel version 5.6.0-1027-oem (checked via uname -r). I believe my sound card is not being detected by Ubuntu. I checked the serial number and via BIOS (which I've upgraded to the latest version) according to the specs (https://topics-cdn.dell.com/pdf/latitude-15-9510-2-in-1-laptop_owners-manual5_en-us.pdf) the sound controller/speaker should be Realtek ALC711-CG / Realtek ALC1309D. However, when I run lspci only the following device appears: 00:1f.3 Multimedia audio controller [0401]: Intel Corporation Device [8086:02c8] In alsamixer, only the HDMI port appears. alsa-info output: http://alsa- project.org/db/?f=f2b70f6eb1a237378bf563cacb6f192ce0a677c3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1895422/+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 1894234] Re: Bluetooth not working with Gnome in Groovy (20.10)
As of 14 Sep, this is working in groovy... looks like things are progressing with groovy, -- 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/1894234 Title: Bluetooth not working with Gnome in Groovy (20.10) Status in bluez package in Ubuntu: Incomplete Bug description: Having plugged in a USB bluetooth dongle, the gnome-bluetooth settiogs report that I have no bluetooth adapter, and I should plug one in. At the same time, I can see the bluetooth adapter with hciconfig, and in fact, I can pair with remote bluetooth devices using a 3rd party bluetooth manager (blueman). Obviously this is not ideal, as it is not fully integrated with gnome, sound devices are not fully available etc.. I'm not sure what else I can provide, but:- # hciconfig -a hci0: Type: Primary Bus: USB BD Address: 24:4B:FE:3A:21:65 ACL MTU: 1021:6 SCO MTU: 255:12 UP RUNNING PSCAN RX bytes:1117 acl:0 sco:0 events:72 errors:0 TX bytes:4973 acl:0 sco:0 commands:72 errors:0 Features: 0xff 0xff 0xff 0xfe 0xdb 0xfd 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF PARK Link mode: SLAVE ACCEPT Name: 'morpheous' Class: 0x1c0104 Service Classes: Rendering, Capturing, Object Transfer Device Class: Computer, Desktop workstation HCI Version: 5.1 (0xa) Revision: 0xb LMP Version: 5.1 (0xa) Subversion: 0x8761 Manufacturer: Realtek Semiconductor Corporation (93) root@morpheous:~# When I got to settings, it tells me I have no bluetooth devices plugged in! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1894234/+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 1895584] Re: fstab does not schedule fsck
The the server installer (and the respective 20.04 too. https://releases.ubuntu.com/20.04.1/ubuntu-20.04.1-live-server-amd64.iso I will check more installers in 12h or so 18.04.* create(d) proper fstabs -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1895584 Title: fstab does not schedule fsck Status in base-files package in Ubuntu: Incomplete Bug description: Current live server installer (20.04 / 20.04.1) creates fstab which never schedules fsck. when actual power failure occurs half of systems dont boot, other half come up with scary errors in boot log. fstab manual (in "mount" package) says explicitly that / filesystem whould be with fsck preference 1 and other disk-based filesystems with 2, if that is corrected, in cases from external boot media, fsck and good system boot proceeds correctly PS package "mount 2.34-0.1ubuntu9 amd64" cannot be selected in the box above To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1895584/+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 1895422] Re: Sound card not detected on Dell Latitude 9510 (Realtek ALC711)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1895422 Title: Sound card not detected on Dell Latitude 9510 (Realtek ALC711) Status in alsa-driver package in Ubuntu: Confirmed Bug description: I am running Ubuntu 20.04.01 LTS, kernel version 5.6.0-1027-oem (checked via uname -r). I believe my sound card is not being detected by Ubuntu. I checked the serial number and via BIOS (which I've upgraded to the latest version) according to the specs (https://topics-cdn.dell.com/pdf/latitude-15-9510-2-in-1-laptop_owners-manual5_en-us.pdf) the sound controller/speaker should be Realtek ALC711-CG / Realtek ALC1309D. However, when I run lspci only the following device appears: 00:1f.3 Multimedia audio controller [0401]: Intel Corporation Device [8086:02c8] In alsamixer, only the HDMI port appears. alsa-info output: http://alsa- project.org/db/?f=f2b70f6eb1a237378bf563cacb6f192ce0a677c3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1895422/+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 1895422] Re: Sound card not detected on Dell Latitude 9510 (Realtek ALC711)
Same problem, what did you do exactly to let it work? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1895422 Title: Sound card not detected on Dell Latitude 9510 (Realtek ALC711) Status in alsa-driver package in Ubuntu: Confirmed Bug description: I am running Ubuntu 20.04.01 LTS, kernel version 5.6.0-1027-oem (checked via uname -r). I believe my sound card is not being detected by Ubuntu. I checked the serial number and via BIOS (which I've upgraded to the latest version) according to the specs (https://topics-cdn.dell.com/pdf/latitude-15-9510-2-in-1-laptop_owners-manual5_en-us.pdf) the sound controller/speaker should be Realtek ALC711-CG / Realtek ALC1309D. However, when I run lspci only the following device appears: 00:1f.3 Multimedia audio controller [0401]: Intel Corporation Device [8086:02c8] In alsamixer, only the HDMI port appears. alsa-info output: http://alsa- project.org/db/?f=f2b70f6eb1a237378bf563cacb6f192ce0a677c3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1895422/+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 1895382] Re: Ability to install 2 or more versions at once
Why no longer affects flatpak snapd, dpkg? Adolfo Jayme, you're just another moron (The ideal solution should serve as an umbrella for all packaging tools) -- 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/1895382 Title: Ability to install 2 or more versions at once Status in apt package in Ubuntu: Invalid Bug description: 1) do not ask questions with two identical answers in a row 2) ask user every time if multiple versions are present 3) if the same answer was given twice in a row - remember choice The ideal solution should serve as an umbrella for all packaging tools. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1895382/+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 1895584] Re: fstab does not schedule fsck
which live installer: desktop or server? ** Changed in: base-files (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1895584 Title: fstab does not schedule fsck Status in base-files package in Ubuntu: Incomplete Bug description: Current live server installer (20.04 / 20.04.1) creates fstab which never schedules fsck. when actual power failure occurs half of systems dont boot, other half come up with scary errors in boot log. fstab manual (in "mount" package) says explicitly that / filesystem whould be with fsck preference 1 and other disk-based filesystems with 2, if that is corrected, in cases from external boot media, fsck and good system boot proceeds correctly PS package "mount 2.34-0.1ubuntu9 amd64" cannot be selected in the box above To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1895584/+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 1895584] [NEW] fstab does not schedule fsck
Public bug reported: Current live server installer (20.04 / 20.04.1) creates fstab which never schedules fsck. when actual power failure occurs half of systems dont boot, other half come up with scary errors in boot log. fstab manual (in "mount" package) says explicitly that / filesystem whould be with fsck preference 1 and other disk-based filesystems with 2, if that is corrected, in cases from external boot media, fsck and good system boot proceeds correctly PS package "mount 2.34-0.1ubuntu9 amd64" cannot be selected in the box above ** Affects: base-files (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1895584 Title: fstab does not schedule fsck Status in base-files package in Ubuntu: New Bug description: Current live server installer (20.04 / 20.04.1) creates fstab which never schedules fsck. when actual power failure occurs half of systems dont boot, other half come up with scary errors in boot log. fstab manual (in "mount" package) says explicitly that / filesystem whould be with fsck preference 1 and other disk-based filesystems with 2, if that is corrected, in cases from external boot media, fsck and good system boot proceeds correctly PS package "mount 2.34-0.1ubuntu9 amd64" cannot be selected in the box above To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1895584/+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 1887968] Re: Pairing with Bluetooth LE mice fails on a Huawei Matebook 13 AMD laptop with Realtek RTL8822CE Wifi/Bluetooth combo adapter
I'm having this problem too with an Huawei Matebook 13 2020 with
Microsoft 3600 bloetooth mouse.
[CHG] Device D7:1B:68:EE:63:C5 Trusted: yes
Changing D7:1B:68:EE:63:C5 trust succeeded
[bluetooth]# pair D7:1B:68:EE:63:C5
Attempting to pair with D7:1B:68:EE:63:C5
[CHG] Device D7:1B:68:EE:63:C5 Connected: yes
[CHG] Device D7:1B:68:EE:63:C5 Connected: no
Failed to pair: org.bluez.Error.AuthenticationCanceled
--
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/1887968
Title:
Pairing with Bluetooth LE mice fails on a Huawei Matebook 13 AMD
laptop with Realtek RTL8822CE Wifi/Bluetooth combo adapter
Status in bluez package in Ubuntu:
Confirmed
Bug description:
I'm using Ubuntu 20.04 on a Huawei Matebook 13 AMD laptop which seems
to use a Realtek RTL8822CE Wifi/Bluetooth combo adapter.
I've been unsuccessful to pair with 2 different bluetooth mice.
However bluetooth seems to work with other devices. I'm under the
impression that this problem only happens with Bluetooth LE devices.
Trying to pair using bluetoothctl fails with the
org.bluez.Error.AuthenticationCanceled error:
[bluetooth]# pair E5:5B:67:2A:09:76
Attempting to pair with E5:5B:67:2A:09:76
[CHG] Device E5:5B:67:2A:09:76 Connected: yes
[CHG] Device E5:5B:67:2A:09:76 Connected: no
Failed to pair: org.bluez.Error.AuthenticationCanceled
A quick google search for org.bluez.Error.AuthenticationCanceled
reported nothing relevant.
Running btmon while trying to pair with the device gives me the
following:
Bluetooth monitor ver 5.53
= Note: Linux version 5.4.0-40-generic (x86_64)
0.998188
= Note: Bluetooth subsystem version 2.22
0.998193
= New Index: E8:6F:38:9C:2B:3C (Primary,USB,hci0)
[hci0] 0.998194
= Open Index: E8:6F:38:9C:2B:3C
[hci0] 0.998195
= Index Info: E8:6F:38:9C:2B:3C (Realtek Semiconductor Corporation)
[hci0] 0.998197
@ MGMT Open: bluetoothd (privileged) version 1.14
{0x0001} 0.998198
@ MGMT Open: btmon (privileged) version 1.14
{0x0002} 0.998310
@ MGMT Command: Pair Device (0x0019) plen 8
{0x0001} [hci0] 8.162442
LE Address: E5:5B:67:2A:09:76 (Static)
Capability: KeyboardDisplay (0x04)
< HCI Command: LE Set Extended Scan Parameters (0x08|0x0041) plen 8
#1 [hci0] 8.162527
Own address type: Public (0x00)
Filter policy: Ignore not in white list (0x01)
PHYs: 0x01
Entry 0: LE 1M
Type: Passive (0x00)
Interval: 60.000 msec (0x0060)
Window: 30.000 msec (0x0030)
> HCI Event: Command Complete (0x0e) plen 4
#2 [hci0] 8.284618
LE Set Extended Scan Parameters (0x08|0x0041) ncmd 2
Status: Success (0x00)
< HCI Command: LE Set Extended Scan Enable (0x08|0x0042) plen 6
#3 [hci0] 8.284654
Extended scan: Enabled (0x01)
Filter duplicates: Enabled (0x01)
Duration: 0 msec (0x)
Period: 0.00 sec (0x)
> HCI Event: Command Complete (0x0e) plen 4
#4 [hci0] 8.289616
LE Set Extended Scan Enable (0x08|0x0042) ncmd 2
Status: Success (0x00)
> HCI Event: LE Meta Event (0x3e) plen 52
#5 [hci0] 8.343614
LE Extended Advertising Report (0x0d)
Num reports: 1
Entry 0
Event type: 0x0013
Props: 0x0013
Connectable
Scannable
Use legacy advertising PDUs
Data status: Complete
Legacy PDU Type: ADV_IND (0x0013)
Address type: Random (0x01)
Address: E5:5B:67:2A:09:76 (Static)
Primary PHY: LE 1M
Secondary PHY: No packets
SID: no ADI field (0xff)
[Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'
$ journalctl -b -u apport-autoreport Sep 14 13:01:52 rubberducky systemd[1]: Starting Process error reports when automatic reporting is enabled... Sep 14 13:02:07 rubberducky whoopsie-upload-all[145261]: Collecting info for /var/crash/_usr_bin_gnome-shell.1000.crash... Sep 14 13:02:07 rubberducky whoopsie-upload-all[145261]: Marking /var/crash/_usr_bin_gnome-shell.1000.crash for whoopsie upload Sep 14 13:02:07 rubberducky whoopsie-upload-all[145261]: All reports processed Sep 14 13:02:07 rubberducky systemd[1]: apport-autoreport.service: Succeeded. Sep 14 13:02:07 rubberducky systemd[1]: Finished Process error reports when automatic reporting is enabled. Sep 14 13:02:07 rubberducky systemd[1]: Starting Process error reports when automatic reporting is enabled... Sep 14 13:02:07 rubberducky whoopsie-upload-all[147307]: /var/crash/_usr_bin_gnome-shell.1000.crash already marked for upload, skipping Sep 14 13:02:07 rubberducky whoopsie-upload-all[147307]: All reports processed Sep 14 13:02:07 rubberducky systemd[1]: apport-autoreport.service: Succeeded. Sep 14 13:02:07 rubberducky systemd[1]: Finished Process error reports when automatic reporting is enabled. Sep 14 13:02:07 rubberducky systemd[1]: Starting Process error reports when automatic reporting is enabled... Sep 14 13:02:07 rubberducky whoopsie-upload-all[147310]: /var/crash/_usr_bin_gnome-shell.1000.crash already marked for upload, skipping Sep 14 13:02:07 rubberducky whoopsie-upload-all[147310]: All reports processed Sep 14 13:02:07 rubberducky systemd[1]: apport-autoreport.service: Succeeded. Sep 14 13:02:07 rubberducky systemd[1]: Finished Process error reports when automatic reporting is enabled. Sep 14 13:02:07 rubberducky systemd[1]: Starting Process error reports when automatic reporting is enabled... Sep 14 13:02:07 rubberducky whoopsie-upload-all[147313]: /var/crash/_usr_bin_gnome-shell.1000.crash already marked for upload, skipping Sep 14 13:02:07 rubberducky whoopsie-upload-all[147313]: All reports processed Sep 14 13:02:07 rubberducky systemd[1]: apport-autoreport.service: Succeeded. Sep 14 13:02:07 rubberducky systemd[1]: Finished Process error reports when automatic reporting is enabled. Sep 14 13:02:07 rubberducky systemd[1]: Starting Process error reports when automatic reporting is enabled... Sep 14 13:02:07 rubberducky whoopsie-upload-all[147315]: /var/crash/_usr_bin_gnome-shell.1000.crash already marked for upload, skipping Sep 14 13:02:07 rubberducky whoopsie-upload-all[147315]: All reports processed Sep 14 13:02:07 rubberducky systemd[1]: apport-autoreport.service: Succeeded. Sep 14 13:02:07 rubberducky systemd[1]: Finished Process error reports when automatic reporting is enabled. Sep 14 13:02:07 rubberducky systemd[1]: Starting Process error reports when automatic reporting is enabled... Sep 14 13:02:07 rubberducky whoopsie-upload-all[147317]: /var/crash/_usr_bin_gnome-shell.1000.crash already marked for upload, skipping Sep 14 13:02:07 rubberducky whoopsie-upload-all[147317]: All reports processed Sep 14 13:02:07 rubberducky systemd[1]: apport-autoreport.service: Succeeded. Sep 14 13:02:07 rubberducky systemd[1]: Finished Process error reports when automatic reporting is enabled. Sep 14 13:02:07 rubberducky systemd[1]: apport-autoreport.service: Start request repeated too quickly. Sep 14 13:02:07 rubberducky systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Sep 14 13:02:07 rubberducky systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Sep 14 13:02:07 rubberducky systemd[1]: apport-autoreport.service: Start request repeated too quickly. Sep 14 13:02:07 rubberducky systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Sep 14 13:02:07 rubberducky systemd[1]: Failed to start Process error reports when automatic reporting is enabled. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1891657 Title: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit' Status in apport package in Ubuntu: Confirmed Bug description: after upgrade from Ubuntu 20.04 to 20.10 seeing systemd use 100% cpu forever top top - 10:16:19 up 20 min, 1 user, load average: 3.91, 4.28, 3.39 Tasks: 332 total, 2 running, 330 sleeping, 0 stopped, 0 zombie %Cpu(s): 18.7 us, 6.4 sy, 11.9 ni, 62.2 id, 0.0 wa, 0.0 hi, 0.8 si, 0.0 st MiB Mem : 15917.6 total, 8553.4 free, 2604.3 used, 4759.9 buff/cache MiB Swap: 2048.0 total, 2048.0 free, 0.0 used. 12633.7 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1 root 20 0 177316 12252 8684 R 100.0 0.1 15:01.25 systemd
[Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'
The error message (the last 3 lines) keep repeating ad infinitum until I manually remove the crash files in /var/crash as Rocky notes in https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1891657/comments/13. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1891657 Title: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit' Status in apport package in Ubuntu: Confirmed Bug description: after upgrade from Ubuntu 20.04 to 20.10 seeing systemd use 100% cpu forever top top - 10:16:19 up 20 min, 1 user, load average: 3.91, 4.28, 3.39 Tasks: 332 total, 2 running, 330 sleeping, 0 stopped, 0 zombie %Cpu(s): 18.7 us, 6.4 sy, 11.9 ni, 62.2 id, 0.0 wa, 0.0 hi, 0.8 si, 0.0 st MiB Mem : 15917.6 total, 8553.4 free, 2604.3 used, 4759.9 buff/cache MiB Swap: 2048.0 total, 2048.0 free, 0.0 used. 12633.7 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1 root 20 0 177316 12252 8684 R 100.0 0.1 15:01.25 systemd 4636 kush 39 19 633796 176152 16360 S 98.3 1.1 17:51.56 tracker-miner-f 820 message+ 20 0 10740 6452 4212 S 39.8 0.0 6:19.06 dbus-daemon 316 root 19 -1 535916 322896 320824 S 15.3 2.0 3:16.41 systemd-journal 844 syslog20 0 221136 5840 3920 S 13.6 0.0 2:14.52 rsyslogd 858 root 20 0 83708 74124 7568 S 12.7 0.5 2:06.98 systemd-logind 5 root 20 0 0 0 0 I 3.4 0.0 0:05.01 kworker/0:0-events 35566 kush 20 0 3850088 588344 262192 S 2.5 3.6 0:30.48 MainThread 5626 kush 20 0 5004788 260876 93400 S 1.7 1.6 3:05.19 gnome-shell 7033 kush 20 0 869792 66440 44272 S 1.7 0.4 0:06.05 gnome-terminal- 36790 kush 20 0 2525432 156636 98568 S 1.7 1.0 0:04.99 Web Content 957 root 20 0 1556196 45044 24284 S 0.8 0.3 0:02.48 containerd 1038 root 20 0 10460 4412 3300 S 0.8 0.0 0:00.16 fancontrol sudo tail -n 100 /var/log/syslog Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when
[Touch-packages] [Bug 1894369] Re: apport-autoreport.service fails to start in groovy after upgrading from focal
** Changed in: apport (Ubuntu) Assignee: (unassigned) => Brian Murray (brian-murray) ** Tags added: groovy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1894369 Title: apport-autoreport.service fails to start in groovy after upgrading from focal Status in apport package in Ubuntu: Confirmed Bug description: apport-autoreport.service fails to start with that CPU load increases significantly making computer unusable. disabling the service and path and stopping both normalizes CPU load as it was supposed to be. for test purposes i started apport-autoreport.service and after checking its status i get state: degraded and 2 units failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1894369/+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 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'
The output of both of the following commands would help us sort out what is going on. journalctl -b -u whoopsie journalctl -b -u apport-autoreport Thanks! Additionally, if this happening on a release other than Ubuntu 20.10 please let me know. ** Changed in: apport (Ubuntu) Assignee: (unassigned) => Brian Murray (brian-murray) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1891657 Title: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit' Status in apport package in Ubuntu: Confirmed Bug description: after upgrade from Ubuntu 20.04 to 20.10 seeing systemd use 100% cpu forever top top - 10:16:19 up 20 min, 1 user, load average: 3.91, 4.28, 3.39 Tasks: 332 total, 2 running, 330 sleeping, 0 stopped, 0 zombie %Cpu(s): 18.7 us, 6.4 sy, 11.9 ni, 62.2 id, 0.0 wa, 0.0 hi, 0.8 si, 0.0 st MiB Mem : 15917.6 total, 8553.4 free, 2604.3 used, 4759.9 buff/cache MiB Swap: 2048.0 total, 2048.0 free, 0.0 used. 12633.7 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1 root 20 0 177316 12252 8684 R 100.0 0.1 15:01.25 systemd 4636 kush 39 19 633796 176152 16360 S 98.3 1.1 17:51.56 tracker-miner-f 820 message+ 20 0 10740 6452 4212 S 39.8 0.0 6:19.06 dbus-daemon 316 root 19 -1 535916 322896 320824 S 15.3 2.0 3:16.41 systemd-journal 844 syslog20 0 221136 5840 3920 S 13.6 0.0 2:14.52 rsyslogd 858 root 20 0 83708 74124 7568 S 12.7 0.5 2:06.98 systemd-logind 5 root 20 0 0 0 0 I 3.4 0.0 0:05.01 kworker/0:0-events 35566 kush 20 0 3850088 588344 262192 S 2.5 3.6 0:30.48 MainThread 5626 kush 20 0 5004788 260876 93400 S 1.7 1.6 3:05.19 gnome-shell 7033 kush 20 0 869792 66440 44272 S 1.7 0.4 0:06.05 gnome-terminal- 36790 kush 20 0 2525432 156636 98568 S 1.7 1.0 0:04.99 Web Content 957 root 20 0 1556196 45044 24284 S 0.8 0.3 0:02.48 containerd 1038 root 20 0 10460 4412 3300 S 0.8 0.0 0:00.16 fancontrol sudo tail -n 100 /var/log/syslog Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service:
[Touch-packages] [Bug 1894369] Re: apport-autoreport.service fails to start in groovy after upgrading from focal
Which release of Ubuntu are you running? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1894369 Title: apport-autoreport.service fails to start in groovy after upgrading from focal Status in apport package in Ubuntu: Confirmed Bug description: apport-autoreport.service fails to start with that CPU load increases significantly making computer unusable. disabling the service and path and stopping both normalizes CPU load as it was supposed to be. for test purposes i started apport-autoreport.service and after checking its status i get state: degraded and 2 units failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1894369/+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 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration
@paelzer To correct myself this (s390x) regression is not due to the snapd seeding issue, but LP: #1895576 which may have been already fixed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1892358 Title: autopkgtest success rate dropped inhibiting proposed migration Status in build-essential package in Ubuntu: Invalid Status in glib2.0 package in Ubuntu: Invalid Status in iputils package in Ubuntu: Invalid Status in kbd package in Ubuntu: Invalid Status in linux-meta package in Ubuntu: Invalid Status in ntpsec package in Ubuntu: Invalid Status in qemu package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in util-linux package in Ubuntu: Invalid Status in linux-meta source package in Bionic: New Status in systemd source package in Bionic: New Status in build-essential source package in Focal: Confirmed Status in linux-meta source package in Focal: New Status in qemu source package in Focal: Confirmed Status in systemd source package in Focal: Confirmed Status in util-linux source package in Focal: Confirmed Bug description: Hi, we had such cases in the past like bug 1817721 for bionic and maybe bug 1892130 is about the same as well. There were more but I didn't want to search for all of them - what I checked is that there are no open ones clearly pointing out the recent further drop in already flaky subtests. In particular the tests "tests-in-lxd" and "systemd-fsckd" were known to be flaky before, but got even worse. Here stats of the last 40 runs, it might be a coincidences that this is after 246-2ubuntu1 landed. Could as well be any other change groovy amd64 tests-in-lxd (F 42% S 0% B 10% => P 45%/) BFFFBFF.B.F.F...FBF build-login(F 0% S 0% B 10% => P 87%/) B...B...BB. unit-config(F 0% S 0% B 10% => P 87%/) B...B...BB. networkd-testpy(F 0% S 0% B 10% => P 87%/) B...B...BB. boot-and-services (F 0% S 0% B 10% => P 87%/) B...B...BB. boot-smoke (F 0% S 0% B 10% => P 87%/) B...B...BB. logind (F 0% S 0% B 10% => P 87%/) B...B...BB. storage(F 0% S 0% B 10% => P 87%/) B...B...BB. upstream (F 35% S 0% B 10% => P 52%/) ..FFB.FFF.FFBFF.B.F.F..FFBF udev (F 0% S 0% B 10% => P 87%/) B...B...BB. systemd-fsckd (F 37% S 0% B 10% => P 50%/) BFFFB.FF...FB.F..B. root-unittests (F 0% S 0% B 10% => P 87%/) B...B...BB. ppc64el tests-in-lxd (F 25% S 0% B 0% => P 75%/) FFFFF.F. systemd-fsckd (F 35% S 0% B 0% => P 65%/) FFF...FFFFF.F..F root-unittests (F 2% S 0% B 0% => P 97%/) ..F. s390x tests-in-lxd (F 52% S 0% B 0% => P 47%/) FFF.FFF.FF....F. timedated (F 2% S 0% B 0% => P 97%/) ...F upstream (F 17% S 0% B 0% => P 82%/) .F..F.F.FFF...F. systemd-fsckd (F 32% S 0% B 0% => P 67%/) FFF..FF..F.FF..F root-unittests (F 10% S 0% B 0% => P 90%/) FFF...F. arm64 tests-in-lxd (F 40% S 0% B 2% => P 57%/) F.B...FFF.FF..F..F.FFF.F logind (F 2% S 0% B 2% => P 95%/) ..B...F. upstream (F 22% S 0% B 2% => P 75%/) ...F.FB.F.F.F..FFF.F root-unittests (F 12% S 0% B 2% => P 85%/) ..B.F...F.FF...F (I'm sure LP will make this unreadable, but is is nice in monospace) Whatever the root cause is - the success rate of these has reduced so much that the (even formerly questionable) practice of retry-until- success won't work anymore. I have run the two tests in a local VM and systemd-fsckd works there while tests-in-lxd seems to trip over the old flaky fellow being "boot-and-services". We had the discussion in the past, but I think I need to again bring up the suggestion to skip "tests-in-lxd" and "systemd-fsckd" until they are on reasonable success rates. To manage notifications about this bug go to:
[Touch-packages] [Bug 1895576] [NEW] boot-and-services in tests-in-lxd autopkgtest fails in groovy on s390x
Public bug reported: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-groovy/groovy/s390x/s/systemd/20200903_184028_2bbdf@/log.gz ... test_rsyslog (__main__.ServicesTest) ... FAIL test_tmp_cleanup (__main__.ServicesTest) ... ok test_tmp_mount (__main__.ServicesTest) ... ok test_udev (__main__.ServicesTest) ... skipped 'udev does not work in containers' == FAIL: test_rsyslog (__main__.ServicesTest) -- Traceback (most recent call last): File "/tmp/autopkgtest.15TVnz/build.ZVh/real-tree/debian/tests/boot-and-services", line 120, in test_rsyslog self.assertRegex(log, 'systemd.*Reached target Graphical Interface') ... Interestingly it does not fail locally on an s390x Focal VM running boot-and-services in LXD. Kernel: Linux juju-d7a408-generic-21 5.4.0-14-generic Also interestingly it is passing with cryptsetup/2:2.3.3-1ubuntu5 glibc/2.32-0ubuntu2. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: update-excuse -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1895576 Title: boot-and-services in tests-in-lxd autopkgtest fails in groovy on s390x Status in systemd package in Ubuntu: New Bug description: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest- groovy/groovy/s390x/s/systemd/20200903_184028_2bbdf@/log.gz ... test_rsyslog (__main__.ServicesTest) ... FAIL test_tmp_cleanup (__main__.ServicesTest) ... ok test_tmp_mount (__main__.ServicesTest) ... ok test_udev (__main__.ServicesTest) ... skipped 'udev does not work in containers' == FAIL: test_rsyslog (__main__.ServicesTest) -- Traceback (most recent call last): File "/tmp/autopkgtest.15TVnz/build.ZVh/real-tree/debian/tests/boot-and-services", line 120, in test_rsyslog self.assertRegex(log, 'systemd.*Reached target Graphical Interface') ... Interestingly it does not fail locally on an s390x Focal VM running boot-and-services in LXD. Kernel: Linux juju-d7a408-generic-21 5.4.0-14-generic Also interestingly it is passing with cryptsetup/2:2.3.3-1ubuntu5 glibc/2.32-0ubuntu2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1895576/+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 1895573] Re: systemd[1]: Failed to start Process error reports when automatic reporting is enabled.
Forgot the mention that I'm on 20.10, upgraded from 20.04. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1895573 Title: systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Status in apport package in Ubuntu: New Bug description: htop always shows 100% CPU for /sbin/init/splash When I look the journalctl, I have always seen `systemd[1]: Failed to start Process error reports when automatic reporting is enabled.` thing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1895573/+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 1895573] Re: systemd[1]: Failed to start Process error reports when automatic reporting is enabled.
Masking apport-autoreport.service and apport.service solves the issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1895573 Title: systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Status in apport package in Ubuntu: New Bug description: htop always shows 100% CPU for /sbin/init/splash When I look the journalctl, I have always seen `systemd[1]: Failed to start Process error reports when automatic reporting is enabled.` thing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1895573/+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 1895573] [NEW] systemd[1]: Failed to start Process error reports when automatic reporting is enabled.
Public bug reported: htop always shows 100% CPU for /sbin/init/splash When I look the journalctl, I have always seen `systemd[1]: Failed to start Process error reports when automatic reporting is enabled.` thing. ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Attachment added: "journalctl_no_full.txt" https://bugs.launchpad.net/bugs/1895573/+attachment/5410802/+files/journalctl_no_full.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1895573 Title: systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Status in apport package in Ubuntu: New Bug description: htop always shows 100% CPU for /sbin/init/splash When I look the journalctl, I have always seen `systemd[1]: Failed to start Process error reports when automatic reporting is enabled.` thing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1895573/+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 1888726] Re: systemd-udevd regression: some renamed network interfaces stuck in "pending" state
** Merge proposal linked: https://code.launchpad.net/~paride/curtin/+git/curtin/+merge/390692 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1888726 Title: systemd-udevd regression: some renamed network interfaces stuck in "pending" state Status in netplan.io package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Bug description: Summary: In Ubuntu Server 20.04 LTS and newer, using netplan.io and systemd- networkd, in certain network configurations, renamed network interfaces get stuck in "pending" state and are not configured properly. On boot, system is stuck on "Wait for Network to be Configured" for 2 minutes. How to reproduce: 1. Configure a machine (for example, a virtual machine) with two Ethernet network cards. Make note of MAC addresses of these network cards. 2. Set up netplan with a single configuration file, contents are in the attached "00-static.yaml" file. Replace the MAC addresses to match your setup. IP address configuration is omitted and is not necessary to reproduce the bug. 3. Reboot the system. Expected outcome: 1. System boots in a reasonable time 2. First network interface (wan) is brought up, is not renamed, and is marked as configured by networkd 3. Second network interface (lan) is brought up, renamed, configured for MTU=9000, and is marked as configured by networkd 4. VLAN interface (vlan20) is brought up, renamed, configured for MTU=9000, and is marked as configured by networkd Actual outcome: 1. System boot is delayed by 2 minutes 2. First network interface (wan) is configured as expected 3. Second network interface (lan) is configured as expected 4. VLAN interface (vlan20) seems to be configured as expected, but is stuck in "pending" state according to networkctl list Test environment: Hardware: Virtual machine with the following configuration * 4 amd64 CPU cores (also tested with a single core) * 1 GB RAM * 8 GB disk * 2 network cards (vmxnet3 in VMware, virtio in Parallels) Working as expected: * [1] Ubuntu Server 19.10, kernel 5.3.0-62, netplan.io 0.99-0ubuntu3~19.10.2, systemd+udev 242-7ubuntu3.11 Broken: * [2] Ubuntu Server 19.10, kernel 5.3.0-62, netplan.io 0.99-0ubuntu3~19.10.2, systemd 242-7ubuntu3.11, udev 245.4-4ubuntu3.1 * [3] Ubuntu Server 20.04 LTS, kernel 5.4.0-42, netplan.io 0.99-0ubuntu3~20.04.2, systemd+udev 245.4-4ubuntu3.1 * [4] Ubuntu Server 20.04 LTS, kernel 5.4.0-42, netplan.io 0.99-0ubuntu3~20.04.2, systemd+udev vanilla upstream git e9769453 * [5] Ubuntu Server 20.04 LTS, kernel 5.4.0-42, netplan.io 0.99-0ubuntu3~20.04.2, systemd+udev vanilla upstream git v242 * [6] Ubuntu Server 20.10 daily-live, kernel 5.4.0-26, netplan.io 0.99-0ubuntu5, systemd+udev 245.6-3ubuntu3 [2] As noted above, issue was reproduced in 19.10 by upgrading ONLY udev and libudev1 to ones shipped in focal-updates. [4] It was also reproduced in vanilla upstream systemd, git master commit e9769453. Just installed on top of existing systemd using "sudo ninja -C build install". [5] Interestingly enough, issue also seems to exist in vanilla v242. Either that, or the installation didn't replace the packaged systemd properly. This may hint at some distribution-specific patch that got removed before 20.04. This issue was reproduced in VMware ESXi 6.7U3, VMware Fusion 11.5.5 and Parallels Desktop 15.1.4. This leads me to believe that network card drivers or virtualisation engines do not play part in the issue. Extra observations: To make the example configuration (00-static.yaml) not get stuck in "pending" state, any one of the following options helps: * Remove "set-name" parameter for "lan" interface * Remove "mtu" parameter for "lan" interface * Remove "wan" interface entirely I got some data/logs for each of these scenarios for eoan [1] and focal [3], as well as the original broken config, and put them together in the attached "parallels.tar.gz". Note about Apport: Attached apport report was generated for test environment [2] above. Attachments: * 00-static.yaml: minimalistic broken netplan configuration example * parallels.tar.gz: various logs for eoan [1] and focal [3], as described in "Extra observations" above ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: udev 245.4-4ubuntu3.2 ProcVersionSignature: Ubuntu 5.3.0-62.56-generic 5.3.18 Uname: Linux 5.3.0-62-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.9 Architecture: amd64 CustomUdevRuleFiles: 70-snap.core.rules Date: Thu Jul 23 18:54:58 2020 InstallationDate: Installed on 2020-07-22 (1 days ago) InstallationMedia: Ubuntu-Server 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Error: command ['lsusb'] failed with exit code 1:
[Touch-packages] [Bug 1895262] Re: Installer windows do not fit on screen, when live-CD only boots with 800x600 screen resolution
** Package changed: ubuntu-meta (Ubuntu) => ubiquity (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1895262 Title: Installer windows do not fit on screen, when live-CD only boots with 800x600 screen resolution Status in ubiquity package in Ubuntu: New Bug description: I recently got a new laptop, ThinkPad E14 G2 with AMD Ryzen 7 4700U with Radeon Graphics. The live-system boots only with a screen resolution of 800x600, which cannot be increased. The problem is that the windows of the installer do not fit the screen so that the buttons for "cancel", "back" and, most importantly, "continue" are not visible on the screen. Thus any novice trying to install Ubuntu/Linux on a recent laptop with AMD hardware will surely despair and be turned off from using Ubuntu/Linux. I suggest that the windows of the installer get a scroll bar to make it feasible to install Ubuntu in such cases. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-desktop (not installed) ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Sep 11 16:01:52 2020 InstallationDate: Installed on 2015-11-05 (1771 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: ubuntu-meta UpgradeStatus: Upgraded to focal on 2020-09-10 (0 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-03-07T21:28:39.455024 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1895262/+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 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration
@paelzer I agree that the fact, i.e. that systemd autpkgtest is failing in Groovy/s390x, but this is a real regression which is not due to flakiness of tests-in-lxd. Please don't reopen this bug, but file a new one or find one already opened. As I see this is still LP: #1878225. I'm filing a hint for it for now. ** Changed in: systemd (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1892358 Title: autopkgtest success rate dropped inhibiting proposed migration Status in build-essential package in Ubuntu: Invalid Status in glib2.0 package in Ubuntu: Invalid Status in iputils package in Ubuntu: Invalid Status in kbd package in Ubuntu: Invalid Status in linux-meta package in Ubuntu: Invalid Status in ntpsec package in Ubuntu: Invalid Status in qemu package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in util-linux package in Ubuntu: Invalid Status in linux-meta source package in Bionic: New Status in systemd source package in Bionic: New Status in build-essential source package in Focal: Confirmed Status in linux-meta source package in Focal: New Status in qemu source package in Focal: Confirmed Status in systemd source package in Focal: Confirmed Status in util-linux source package in Focal: Confirmed Bug description: Hi, we had such cases in the past like bug 1817721 for bionic and maybe bug 1892130 is about the same as well. There were more but I didn't want to search for all of them - what I checked is that there are no open ones clearly pointing out the recent further drop in already flaky subtests. In particular the tests "tests-in-lxd" and "systemd-fsckd" were known to be flaky before, but got even worse. Here stats of the last 40 runs, it might be a coincidences that this is after 246-2ubuntu1 landed. Could as well be any other change groovy amd64 tests-in-lxd (F 42% S 0% B 10% => P 45%/) BFFFBFF.B.F.F...FBF build-login(F 0% S 0% B 10% => P 87%/) B...B...BB. unit-config(F 0% S 0% B 10% => P 87%/) B...B...BB. networkd-testpy(F 0% S 0% B 10% => P 87%/) B...B...BB. boot-and-services (F 0% S 0% B 10% => P 87%/) B...B...BB. boot-smoke (F 0% S 0% B 10% => P 87%/) B...B...BB. logind (F 0% S 0% B 10% => P 87%/) B...B...BB. storage(F 0% S 0% B 10% => P 87%/) B...B...BB. upstream (F 35% S 0% B 10% => P 52%/) ..FFB.FFF.FFBFF.B.F.F..FFBF udev (F 0% S 0% B 10% => P 87%/) B...B...BB. systemd-fsckd (F 37% S 0% B 10% => P 50%/) BFFFB.FF...FB.F..B. root-unittests (F 0% S 0% B 10% => P 87%/) B...B...BB. ppc64el tests-in-lxd (F 25% S 0% B 0% => P 75%/) FFFFF.F. systemd-fsckd (F 35% S 0% B 0% => P 65%/) FFF...FFFFF.F..F root-unittests (F 2% S 0% B 0% => P 97%/) ..F. s390x tests-in-lxd (F 52% S 0% B 0% => P 47%/) FFF.FFF.FF....F. timedated (F 2% S 0% B 0% => P 97%/) ...F upstream (F 17% S 0% B 0% => P 82%/) .F..F.F.FFF...F. systemd-fsckd (F 32% S 0% B 0% => P 67%/) FFF..FF..F.FF..F root-unittests (F 10% S 0% B 0% => P 90%/) FFF...F. arm64 tests-in-lxd (F 40% S 0% B 2% => P 57%/) F.B...FFF.FF..F..F.FFF.F logind (F 2% S 0% B 2% => P 95%/) ..B...F. upstream (F 22% S 0% B 2% => P 75%/) ...F.FB.F.F.F..FFF.F root-unittests (F 12% S 0% B 2% => P 85%/) ..B.F...F.FF...F (I'm sure LP will make this unreadable, but is is nice in monospace) Whatever the root cause is - the success rate of these has reduced so much that the (even formerly questionable) practice of retry-until- success won't work anymore. I have run the two tests in a local VM and systemd-fsckd works there while tests-in-lxd seems to trip over the old flaky fellow being "boot-and-services". We
[Touch-packages] [Bug 1895382] Re: Ability to install 2 or more versions at once
** No longer affects: flatpak (Ubuntu) ** No longer affects: snapd (Ubuntu) ** No longer affects: dpkg (Ubuntu) -- 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/1895382 Title: Ability to install 2 or more versions at once Status in apt package in Ubuntu: Invalid Bug description: 1) do not ask questions with two identical answers in a row 2) ask user every time if multiple versions are present 3) if the same answer was given twice in a row - remember choice The ideal solution should serve as an umbrella for all packaging tools. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1895382/+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 1887968] Re: Pairing with Bluetooth LE mice fails on a Huawei Matebook 13 AMD laptop with Realtek RTL8822CE Wifi/Bluetooth combo adapter
I'm having the same problem with an Huawei Matebook D14 2020 R5 with their
bluetooth mouse.
What I noticed using bluetoothctl is that the mouse device ID changes:
D9:73:24:7E:1A:0E (random)
I've seen 0E, 0F, 0C, 0B, etc.
I don't know if it's suppose to be like that or not.
--
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/1887968
Title:
Pairing with Bluetooth LE mice fails on a Huawei Matebook 13 AMD
laptop with Realtek RTL8822CE Wifi/Bluetooth combo adapter
Status in bluez package in Ubuntu:
Confirmed
Bug description:
I'm using Ubuntu 20.04 on a Huawei Matebook 13 AMD laptop which seems
to use a Realtek RTL8822CE Wifi/Bluetooth combo adapter.
I've been unsuccessful to pair with 2 different bluetooth mice.
However bluetooth seems to work with other devices. I'm under the
impression that this problem only happens with Bluetooth LE devices.
Trying to pair using bluetoothctl fails with the
org.bluez.Error.AuthenticationCanceled error:
[bluetooth]# pair E5:5B:67:2A:09:76
Attempting to pair with E5:5B:67:2A:09:76
[CHG] Device E5:5B:67:2A:09:76 Connected: yes
[CHG] Device E5:5B:67:2A:09:76 Connected: no
Failed to pair: org.bluez.Error.AuthenticationCanceled
A quick google search for org.bluez.Error.AuthenticationCanceled
reported nothing relevant.
Running btmon while trying to pair with the device gives me the
following:
Bluetooth monitor ver 5.53
= Note: Linux version 5.4.0-40-generic (x86_64)
0.998188
= Note: Bluetooth subsystem version 2.22
0.998193
= New Index: E8:6F:38:9C:2B:3C (Primary,USB,hci0)
[hci0] 0.998194
= Open Index: E8:6F:38:9C:2B:3C
[hci0] 0.998195
= Index Info: E8:6F:38:9C:2B:3C (Realtek Semiconductor Corporation)
[hci0] 0.998197
@ MGMT Open: bluetoothd (privileged) version 1.14
{0x0001} 0.998198
@ MGMT Open: btmon (privileged) version 1.14
{0x0002} 0.998310
@ MGMT Command: Pair Device (0x0019) plen 8
{0x0001} [hci0] 8.162442
LE Address: E5:5B:67:2A:09:76 (Static)
Capability: KeyboardDisplay (0x04)
< HCI Command: LE Set Extended Scan Parameters (0x08|0x0041) plen 8
#1 [hci0] 8.162527
Own address type: Public (0x00)
Filter policy: Ignore not in white list (0x01)
PHYs: 0x01
Entry 0: LE 1M
Type: Passive (0x00)
Interval: 60.000 msec (0x0060)
Window: 30.000 msec (0x0030)
> HCI Event: Command Complete (0x0e) plen 4
#2 [hci0] 8.284618
LE Set Extended Scan Parameters (0x08|0x0041) ncmd 2
Status: Success (0x00)
< HCI Command: LE Set Extended Scan Enable (0x08|0x0042) plen 6
#3 [hci0] 8.284654
Extended scan: Enabled (0x01)
Filter duplicates: Enabled (0x01)
Duration: 0 msec (0x)
Period: 0.00 sec (0x)
> HCI Event: Command Complete (0x0e) plen 4
#4 [hci0] 8.289616
LE Set Extended Scan Enable (0x08|0x0042) ncmd 2
Status: Success (0x00)
> HCI Event: LE Meta Event (0x3e) plen 52
#5 [hci0] 8.343614
LE Extended Advertising Report (0x0d)
Num reports: 1
Entry 0
Event type: 0x0013
Props: 0x0013
Connectable
Scannable
Use legacy advertising PDUs
Data status: Complete
Legacy PDU Type: ADV_IND (0x0013)
Address type: Random (0x01)
Address: E5:5B:67:2A:09:76 (Static)
Primary PHY: LE 1M
Secondary PHY: No packets
SID: no ADI field (0xff)
TX power: 127 dBm
RSSI: -20 dBm (0xec)
Periodic advertising invteral: 0.00 msec (0x)
[Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'
I ran into this and applied the workaround of deleting all the files in /var/crash to stop the journalctl spam and 100% CPU usage. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1891657 Title: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit' Status in apport package in Ubuntu: Confirmed Bug description: after upgrade from Ubuntu 20.04 to 20.10 seeing systemd use 100% cpu forever top top - 10:16:19 up 20 min, 1 user, load average: 3.91, 4.28, 3.39 Tasks: 332 total, 2 running, 330 sleeping, 0 stopped, 0 zombie %Cpu(s): 18.7 us, 6.4 sy, 11.9 ni, 62.2 id, 0.0 wa, 0.0 hi, 0.8 si, 0.0 st MiB Mem : 15917.6 total, 8553.4 free, 2604.3 used, 4759.9 buff/cache MiB Swap: 2048.0 total, 2048.0 free, 0.0 used. 12633.7 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1 root 20 0 177316 12252 8684 R 100.0 0.1 15:01.25 systemd 4636 kush 39 19 633796 176152 16360 S 98.3 1.1 17:51.56 tracker-miner-f 820 message+ 20 0 10740 6452 4212 S 39.8 0.0 6:19.06 dbus-daemon 316 root 19 -1 535916 322896 320824 S 15.3 2.0 3:16.41 systemd-journal 844 syslog20 0 221136 5840 3920 S 13.6 0.0 2:14.52 rsyslogd 858 root 20 0 83708 74124 7568 S 12.7 0.5 2:06.98 systemd-logind 5 root 20 0 0 0 0 I 3.4 0.0 0:05.01 kworker/0:0-events 35566 kush 20 0 3850088 588344 262192 S 2.5 3.6 0:30.48 MainThread 5626 kush 20 0 5004788 260876 93400 S 1.7 1.6 3:05.19 gnome-shell 7033 kush 20 0 869792 66440 44272 S 1.7 0.4 0:06.05 gnome-terminal- 36790 kush 20 0 2525432 156636 98568 S 1.7 1.0 0:04.99 Web Content 957 root 20 0 1556196 45044 24284 S 0.8 0.3 0:02.48 containerd 1038 root 20 0 10460 4412 3300 S 0.8 0.0 0:00.16 fancontrol sudo tail -n 100 /var/log/syslog Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]:
[Touch-packages] [Bug 1895426] Re: package linux-firmware 1.187.3 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1
Looks like a problem generating a new initramfs: update-initramfs: Generating /boot/initrd.img-5.4.0-47-generic mv: cannot stat '/boot/initrd.img-5.4.0-47-generic.new': No such file or directory I don't see any information about what went wrong though. The disk isn't full, so that's not the problem. Adding initramfs-tools. I don't see any reason to think this is a linux- firmware problem right now, so setting that to invalid. ** Also affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-firmware (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1895426 Title: package linux-firmware 1.187.3 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Status in linux-firmware package in Ubuntu: Invalid Bug description: linux-firmware bug ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.3 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tirtha 1397 F pulseaudio CasperMD5CheckResult: skip Date: Sun Sep 13 11:45:12 2020 Dependencies: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-09-13 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox PackageArchitecture: all ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=a24d343d-9753-4460-ac8f-43882d4197c7 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26.3 RfKill: SourcePackage: linux-firmware Title: package linux-firmware 1.187.3 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1895426/+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 1895528] [NEW] Setting in manpage of resolved.conf does not apply
Public bug reported: Hi, it looks like there is an error in the manpage of resolved.conf. Ubuntu 20.04.1 LTS systemd 245.4-4ubuntu3.2 The manpage of resolved.conf says: DNSSEC= ... Defaults to "allow-downgrade" So when I leave the resolved.conf un-edited, the value is [Resolve] ... #DNSSEC=no ... so the default "allow-downgrade" should apply. But instead DNSSEC is not used at all. dig sshfp dnsprivacy.org +dnssec ; <<>> DiG 9.16.1-Ubuntu <<>> sshfp dnsprivacy.org +dnssec ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 24171 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 When I set the value hard-coded to "allow-downgrade" [Resolve] ... DNSSEC=allow-downgrade ... the ad flag is shown. dig sshfp dnsprivacy.org +dnssec ; <<>> DiG 9.16.1-Ubuntu <<>> sshfp dnsprivacy.org +dnssec ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 41701 ;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 Best regards Daniel ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1895528 Title: Setting in manpage of resolved.conf does not apply Status in systemd package in Ubuntu: New Bug description: Hi, it looks like there is an error in the manpage of resolved.conf. Ubuntu 20.04.1 LTS systemd 245.4-4ubuntu3.2 The manpage of resolved.conf says: DNSSEC= ... Defaults to "allow-downgrade" So when I leave the resolved.conf un-edited, the value is [Resolve] ... #DNSSEC=no ... so the default "allow-downgrade" should apply. But instead DNSSEC is not used at all. dig sshfp dnsprivacy.org +dnssec ; <<>> DiG 9.16.1-Ubuntu <<>> sshfp dnsprivacy.org +dnssec ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 24171 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 When I set the value hard-coded to "allow-downgrade" [Resolve] ... DNSSEC=allow-downgrade ... the ad flag is shown. dig sshfp dnsprivacy.org +dnssec ; <<>> DiG 9.16.1-Ubuntu <<>> sshfp dnsprivacy.org +dnssec ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 41701 ;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 Best regards Daniel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1895528/+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 1794478] Re: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it
** Tags added: ssc -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1794478 Title: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it Status in Ubuntu on IBM z Systems: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Bionic: Fix Released Bug description: [Impact] In case creating bond interface, IPv4 address is not automatically assigned when IPv6 has manual setting. [Test Case] 1. create 18.04.4 instance, network-manager version is 1.10.6-2ubuntu.1.2 as original description. 2. ipv6 manual, ipv4 auto ## sudo nmcli con add type bond con-name bond0 ifname bond0 mode active-backup; sudo nmcli con mod bond0 bond.options "downdelay=0, fail_over_mac=none, miimon=100, mode=active-backup,num_grat_arp=0, primary_reselect=always, updelay=0"; sudo nmcli con mod bond0 ipv6.method manual ipv6.addresses fe81::ff:fe97:a27f/64; sudo nmcli con mod bond0 ipv4.method auto; sudo nmcli con add type bond-slave ifname ens34 master bond0; sudo nmcli con add type bond-slave ifname ens35 master bond0; sudo nmcli con mod bond0 +bond.options mii=100 sleep 5 sudo nmcli con up bond-slave-ens34 sudo nmcli con up bond-slave-ens35 sudo nmcli con up bond0; sleep 5; sudo nmcli c s bond0 ## 3. ipv6 auto, ipv4 auto ## sudo nmcli con add type bond con-name bond0 ifname bond0 mode active-backup; sudo nmcli con mod bond0 bond.options "downdelay=0, fail_over_mac=none, miimon=100, mode=active-backup,num_grat_arp=0, primary_reselect=always, updelay=0"; sudo nmcli con mod bond0 ipv6.method auto; sudo nmcli con mod bond0 ipv4.method auto; sudo nmcli con add type bond-slave ifname ens34 master bond0; sudo nmcli con add type bond-slave ifname ens35 master bond0; sudo nmcli con mod bond0 +bond.options mii=100 sleep 5 sudo nmcli con up bond-slave-ens34 sudo nmcli con up bond-slave-ens35 sudo nmcli con up bond0; sleep 5 sudo nmcli c s bond0 ## when run #3, it is working, but with #2, it is not working. [Potential Regression] Actually nothing special. fix just remove if statement. but it needs Network Manager restarted. [Other informations] After upstream fix, it is working fine with #2 and #3 above. * Upstream bug and fix: https://bugzilla.redhat.com/show_bug.cgi?id=1575944 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/f03ae35 * Only affecting Bionic: $ git describe --contains f03ae35 1.10.8~2 $ rmadison network-manager ==> network-manager | 1.10.6-2ubuntu1.2 | bionic-updates network-manager | 1.20.4-2ubuntu2.2 | eoan-updates network-manager | 1.22.4-1ubuntu2 | focal [Original description] ---Problem Description--- Bond interface with automatic ipv4 mode and manual ipv6 mode fails to get automatic ipv4 assigned from dhcp server. ---uname output--- Linux NetworkTest 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = s390x ---Debugger--- A debugger is not configured ---Steps to Reproduce--- When user configures ipv4 as automatic and ipv6 as manual for bond interface automatic ipv4 is not getting assigned. Looks like dhcp client request for ipv4 is not done to dhcp server after maunal ipv6 is assigned quickly to bond interface This issue will not happen in below cases: 1)with ipv4 automatic and ipv6 manual configuration for ethernet or vlan interface. 2)with ipv4 automatic and ipv6 automatic configuration for bond interface 3)with ipv4 automatic and ipv6 disabled configuration for bond interface Configuration: Bond interface, ipv4 automatic mode and ipv6 automatic mode root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond [connection] id=test_bond uuid=63e54542-5135-47ac-a954-b861c3937be2 type=bond interface-name=test_bond permissions= timestamp=1537944121 [ethernet] mac-address-blacklist= [bond] downdelay=0 fail_over_mac=none miimon=100 mode=active-backup num_grat_arp=0 primary_reselect=always updelay=0 [ipv4] dns-search= method=auto [ipv6] addr-gen-mode=stable-privacy dns-search= method=auto From /var/log/syslog, we can see ip got assigned: Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPDISCOVER on test_bond to 255.255.255.255 port 67 interval 3 (xid=0x5e04bf1e) Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPREQUEST of 10.2.3.55 on test_bond to 255.255.255.255 port 67 (xid=0x5e04bf1e) Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPOFFER of 10.2.3.55 from 10.2.3.1 Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPACK of 10.2.3.55 from
[Touch-packages] [Bug 1895502] Re: the screen is hanging frequently and i am unable to perform any typing work on the screen due to the huge delay between my typing and characters appearing on the scr
You seem to be experiencing recurring kernel crashes in the 'nouveau' driver. Rather than waiting for a fix I suggest just installing the proprietary Nvidia driver from the 'Additional Drivers' app. ** Summary changed: - the screen is hanging frequently and i am unable to perform any typing work on the screen due to the huge delay between my typing and characters appearing on the screen + nouveau keeps crashing in nvkm_pmu_init ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Tags added: nouveau -- 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/1895502 Title: nouveau keeps crashing in nvkm_pmu_init Status in linux package in Ubuntu: New Bug description: screen brightness automatically gets full even if I reduce it ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18 Uname: Linux 4.15.0-76-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Sep 14 09:59:45 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:3963] Subsystem: Lenovo GP108M [GeForce MX150] [17aa:3963] InstallationDate: Installed on 2019-01-10 (612 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 174f:241a Syntek Bus 001 Device 003: ID 0cf3:e500 Atheros Communications, Inc. Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81DE ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-76-generic root=UUID=b5321cab-9053-41be-abdd-7ac822fa43b9 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 8TCN44WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55724 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15IKB dmi.modalias: dmi:bvnLENOVO:bvr8TCN44WW:bd06/13/2018:svnLENOVO:pn81DE:pvrLenovoideapad330-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55724WIN:cvnLENOVO:ct10:cvrLenovoideapad330-15IKB: dmi.product.family: ideapad 330-15IKB dmi.product.name: 81DE dmi.product.version: Lenovo ideapad 330-15IKB dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895502/+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 1895502] Re: the screen is hanging frequently and i am unable to perform any typing work on the screen due to the huge delay between my typing and characters appearing on the scr
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1895502 Title: nouveau keeps crashing in nvkm_pmu_init Status in linux package in Ubuntu: New Bug description: screen brightness automatically gets full even if I reduce it ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18 Uname: Linux 4.15.0-76-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Sep 14 09:59:45 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:3963] Subsystem: Lenovo GP108M [GeForce MX150] [17aa:3963] InstallationDate: Installed on 2019-01-10 (612 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 174f:241a Syntek Bus 001 Device 003: ID 0cf3:e500 Atheros Communications, Inc. Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81DE ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-76-generic root=UUID=b5321cab-9053-41be-abdd-7ac822fa43b9 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 8TCN44WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55724 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15IKB dmi.modalias: dmi:bvnLENOVO:bvr8TCN44WW:bd06/13/2018:svnLENOVO:pn81DE:pvrLenovoideapad330-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55724WIN:cvnLENOVO:ct10:cvrLenovoideapad330-15IKB: dmi.product.family: ideapad 330-15IKB dmi.product.name: 81DE dmi.product.version: Lenovo ideapad 330-15IKB dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895502/+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 1788321] Re: swapon failed: invalid argument
Good News! This bug is still here. Same error on Dell Inspiron 13-7353, Ubuntu 20.04.1 (Upgraded from 18.05.5), Kernel: Linux NOMIS-inspiron 5.4.0-47-generic #51-Ubuntu SMP Fri Sep 4 19:50:52 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Filesystem btrfs, Storage: Samsung 650 SSD (1TB). Was working properly on 18.04, and 20.04.1 on earlier kernels. I did not try late kernels. It seems like I have the worst combination of configuration but innocently walked into this . I reduced vm.swapiness to ZERO. in the hope I will encouner fewer crashes. Please advise. Thanx. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1788321 Title: swapon failed: invalid argument Status in linux package in Ubuntu: Confirmed Status in util-linux package in Ubuntu: Invalid Bug description: Environment: - Ubuntu 18.04.1 LTS - Linux 4.15.0-32-generic i686 Description: When I try to mount my swap partition or my swap file, I get "swapon failed: invalid argument" . Steps to reproduce: 1) sudo bash 2) dd if=/dev/zero of=/swapfile bs=1024 count=524288 3) mkswap /swapfile 4) chown root:root /swapfile 5) chmod 0600 /swapfile 6) swapon /swapfile Last execution returns "swapon failed: invalid argument" . I'm almost sure it's a bug because I have no problems using Linux 4.15.0-29-generic instead of Linux 4.15.0-32-generic. Also, no problems using Ubuntu 18.04.1 LTS Live CD. Regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788321/+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 1895502] [NEW] the screen is hanging frequently and i am unable to perform any typing work on the screen due to the huge delay between my typing and characters appearing on the s
You have been subscribed to a public bug: screen brightness automatically gets full even if I reduce it ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18 Uname: Linux 4.15.0-76-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Sep 14 09:59:45 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:3963] Subsystem: Lenovo GP108M [GeForce MX150] [17aa:3963] InstallationDate: Installed on 2019-01-10 (612 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 174f:241a Syntek Bus 001 Device 003: ID 0cf3:e500 Atheros Communications, Inc. Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81DE ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-76-generic root=UUID=b5321cab-9053-41be-abdd-7ac822fa43b9 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 8TCN44WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55724 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15IKB dmi.modalias: dmi:bvnLENOVO:bvr8TCN44WW:bd06/13/2018:svnLENOVO:pn81DE:pvrLenovoideapad330-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55724WIN:cvnLENOVO:ct10:cvrLenovoideapad330-15IKB: dmi.product.family: ideapad 330-15IKB dmi.product.name: 81DE dmi.product.version: Lenovo ideapad 330-15IKB dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- the screen is hanging frequently and i am unable to perform any typing work on the screen due to the huge delay between my typing and characters appearing on the screen https://bugs.launchpad.net/bugs/1895502 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration
Groovy It seems this isn't over for groovy, it was mentioned that the issues in the subtest "tests-in-lxd" would be related to some fstab issues in those issues. But recently all architectures, but s390x recovered. I assume that the fstab issue is fixed but something else surfaces now. groovy s390x tests-in-lxd (F 100% f 0% S 0% B 0% => P 0%/) FF boot-and-services (F 3% f 0% S 0% B 0% => P 96%/) .F systemd-fsckd (F 26% f 73% S 0% B 0% => P 0%/) fFFfFF We see when systemd-fsckd was marked flaky (F->f), but tests-in-lxd continues to perma-stop any migration depending on systemd. Currently this holds back a lot of things in groovy, it seems to be: qemu/1:5.0-5ubuntu7 chiark-tcl/1.3.4ubuntu3 cmake-extras/1.5-1ubuntu1 cstore-fdw/1.7.0-1 dateparser/0.7.4-1 dpdk/19.11.4-1 gem2deb/1.2.1 glibc/2.32-0ubuntu2 gnome-desktop3/3.37.90.1-1ubuntu1 grep/3.4-1 libnss-nis/3.1-0ubuntu3 libnss-nisplus/1.3-0ubuntu3 link-grammar/5.8.0-1 mksh/59b-1 natsort/7.0.1-1 openconnect/8.10-1 orafce/3.13.4-1 pandas/1.0.5+dfsg-3 pango1.0/1.46.1-1 php-nesbot-carbon/2.32.2-1 php-shellcommand/1.6.1-1 php-twig/2.13.0-1 postgresql-12/12.4-1 postgresql-common/216 postgresql-multicorn/1.4.0-2 reprotest/0.7.15 snapd/2.46.1+20.10 symfony/4.4.11+dfsg-1ubuntu1 systemd/246.4-1ubuntu1 tracker/2.3.4-1build1 vis/0.6-3 Therefore re-opening the groovy task, this isn't over yet :-/ @rbalint please let us know if you know more details about it already. ** Changed in: systemd (Ubuntu) Status: Fix Released => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1892358 Title: autopkgtest success rate dropped inhibiting proposed migration Status in build-essential package in Ubuntu: Invalid Status in glib2.0 package in Ubuntu: Invalid Status in iputils package in Ubuntu: Invalid Status in kbd package in Ubuntu: Invalid Status in linux-meta package in Ubuntu: Invalid Status in ntpsec package in Ubuntu: Invalid Status in qemu package in Ubuntu: Invalid Status in systemd package in Ubuntu: New Status in util-linux package in Ubuntu: Invalid Status in linux-meta source package in Bionic: New Status in systemd source package in Bionic: New Status in build-essential source package in Focal: Confirmed Status in linux-meta source package in Focal: New Status in qemu source package in Focal: Confirmed Status in systemd source package in Focal: Confirmed Status in util-linux source package in Focal: Confirmed Bug description: Hi, we had such cases in the past like bug 1817721 for bionic and maybe bug 1892130 is about the same as well. There were more but I didn't want to search for all of them - what I checked is that there are no open ones clearly pointing out the recent further drop in already flaky subtests. In particular the tests "tests-in-lxd" and "systemd-fsckd" were known to be flaky before, but got even worse. Here stats of the last 40 runs, it might be a coincidences that this is after 246-2ubuntu1 landed. Could as well be any other change groovy amd64 tests-in-lxd (F 42% S 0% B 10% => P 45%/) BFFFBFF.B.F.F...FBF build-login(F 0% S 0% B 10% => P 87%/) B...B...BB. unit-config(F 0% S 0% B 10% => P 87%/) B...B...BB. networkd-testpy(F 0% S 0% B 10% => P 87%/) B...B...BB. boot-and-services (F 0% S 0% B 10% => P 87%/) B...B...BB. boot-smoke (F 0% S 0% B 10% => P 87%/) B...B...BB. logind (F 0% S 0% B 10% => P 87%/) B...B...BB. storage(F 0% S 0% B 10% => P 87%/) B...B...BB. upstream (F 35% S 0% B 10% => P 52%/) ..FFB.FFF.FFBFF.B.F.F..FFBF udev (F 0% S 0% B 10% => P 87%/) B...B...BB. systemd-fsckd (F 37% S 0% B 10% => P 50%/) BFFFB.FF...FB.F..B. root-unittests (F 0% S 0% B 10% => P 87%/) B...B...BB. ppc64el tests-in-lxd (F 25% S 0% B 0% => P 75%/) FFFFF.F. systemd-fsckd (F 35% S 0% B 0% => P 65%/) FFF...FFFFF.F..F root-unittests (F 2% S 0% B 0% => P 97%/) ..F. s390x tests-in-lxd (F 52% S 0% B 0% => P 47%/)
