[Touch-packages] [Bug 1775392] Re: at-spi-bus-launcher makes Xorg crash when resuming from suspend
bugzilla is deprecated, if that's still happening it would be better to open a new report on https://gitlab.gnome.org/GNOME/at- spi2-core/-/issues -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1775392 Title: at-spi-bus-launcher makes Xorg crash when resuming from suspend Status in at-spi2-core package in Ubuntu: Confirmed Bug description: If at-spi2-core is installed, when resuming from suspend messages like these are logged in systemd journal: at-spi-bus-launcher[31720]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0" at-spi-bus-launcher[31720]: after 8065 requests (8065 known processed) with 0 events remaining. The number of requests vary, it can reach more than 15000. Depending on the number of requests, the Xorg server crashes with SIGBUS. Depending on the exact moment Xorg crashes, when lightdm manages to recover, it shows a login greeter, or worst case scenario, it can't recover, a black screen is shown and the desptop session doesn't start. It took me a long time to discover the cause. The visible symptom was: once in a while when resuming from suspend, I got a login greeter instead of an unlock greeter, or a black screen which forced me to power down. Investigating, I found out that whenever that happened, there was a Xorg core left behind. Looking at the journal messages before the crash, there was always that flood of at-spi2-core requests. So I uninstalled at-spi2-core and Xorg never crashed anymore. This is a quite severe bug, which makes it impossible to use at- spi2-core. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: at-spi2-core (not installed) ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Jun 6 09:10:12 2018 InstallationDate: Installed on 2018-04-28 (38 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: at-spi2-core UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1775392/+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 1903048] Re: [SRU] Bluetooth won't activate on the pi 400
Could you open a new report about the regression using 'ubuntu-bug bluez'? -- 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/1903048 Title: [SRU] Bluetooth won't activate on the pi 400 Status in bluez package in Ubuntu: Triaged Status in bluez source package in Groovy: Fix Released Status in bluez source package in Hirsute: Triaged Bug description: [Impact] Without these patches, Bluetooth is inoperable on the recently released Raspberry Pi 400. [Test Case] * Boot the Ubuntu Desktop for Pi image on a Pi 400. * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is not enabled and attempting to activate it fails * Enable the -proposed repository for the release (groovy) * sudo apt update * sudo apt install bluez * sudo reboot * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is active and that Bluetooth devices (e.g. mice, mobile phones, headphones, etc.) can connect and operate correctly [Regression Potential] Extremely low (on groovy in particular, this has the same version of bluez as hirsute). The only significant risk is to non-Pi platforms or dongles which also use the Broadcom 43xx (or Cypress 305) chips for Bluetooth which might be inadvertently affected by these patches. [Original Description] The new Pi 400 has a slightly different Wifi/BT chip to the Pi4. Whilst wifi works happily, Bluetooth fails to operate. This doesn't appear to be an issue with either the firmware (the latest versions from upstream Raspbian have been tried), or the kernel (a known-good raspi kernel has been tested under Ubuntu), but with Bluez itself. Specifically, tracing the initialization with btmon on Raspbian and Ubuntu, the stack consistently fails when attempting to "Set Default PHY" on the latter. Curiously, under Ubuntu the adapter also appears to lack a MAC address. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903048/+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 1905539] [NEW] package light-themes 16.10+18.04.20181005-0ubuntu1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
Public bug reported: crash occuring ProblemType: Package DistroRelease: Ubuntu 20.04 Package: light-themes 16.10+18.04.20181005-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Nov 25 12:23:19 2020 ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 InstallationDate: Installed on 2020-06-03 (174 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: ubuntu-themes Title: package light-themes 16.10+18.04.20181005-0ubuntu1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 UpgradeStatus: Upgraded to focal on 2020-11-25 (0 days ago) ** Affects: ubuntu-themes (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1905539 Title: package light-themes 16.10+18.04.20181005-0ubuntu1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 Status in ubuntu-themes package in Ubuntu: New Bug description: crash occuring ProblemType: Package DistroRelease: Ubuntu 20.04 Package: light-themes 16.10+18.04.20181005-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Nov 25 12:23:19 2020 ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 InstallationDate: Installed on 2020-06-03 (174 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: ubuntu-themes Title: package light-themes 16.10+18.04.20181005-0ubuntu1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 UpgradeStatus: Upgraded to focal on 2020-11-25 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1905539/+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 1905539] Re: package light-themes 16.10+18.04.20181005-0ubuntu1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1905539 Title: package light-themes 16.10+18.04.20181005-0ubuntu1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 Status in ubuntu-themes package in Ubuntu: New Bug description: crash occuring ProblemType: Package DistroRelease: Ubuntu 20.04 Package: light-themes 16.10+18.04.20181005-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Nov 25 12:23:19 2020 ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 InstallationDate: Installed on 2020-06-03 (174 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: ubuntu-themes Title: package light-themes 16.10+18.04.20181005-0ubuntu1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 UpgradeStatus: Upgraded to focal on 2020-11-25 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1905539/+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 1905482] Re: Xorg freeze after dragin icon from desktop to nautilus
*** This bug is a duplicate of bug 1898462 *** https://bugs.launchpad.net/bugs/1898462 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 1898462, 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. ** Changed in: xorg (Ubuntu) Importance: Undecided => High ** This bug has been marked a duplicate of bug 1898462 [groovy] Drag and drop files from Desktop to Nautilus freezes gnome-shell -- 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/1905482 Title: Xorg freeze after dragin icon from desktop to nautilus Status in xorg package in Ubuntu: New Bug description: 100% reproducible by dragging an icon from the desktop to an open nautilus window. X then freezes, I have to switch to another tty, login and reboot to recover ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .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 455.38 Thu Oct 22 06:06:59 UTC 2020 GCC version: gcc version 10.2.0 (Ubuntu 10.2.0-13ubuntu1) ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Nov 25 09:51:13 2020 DistUpgraded: 2020-10-24 22:46:08,965 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: nvidia, 455.38, 5.8.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Once a week GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Since a couple weeks or more GraphicsCard: NVIDIA Corporation GK107GL [Quadro K600] [10de:0ffa] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GK107GL [Quadro K600] [10de:094b] InstallationDate: Installed on 2020-04-24 (214 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Precision T1700 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-29-generic root=UUID=c1eecc57-1357-4347-a0a6-cf3c563a52fd ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to groovy on 2020-10-24 (31 days ago) dmi.bios.date: 05/30/2019 dmi.bios.release: 65.28 dmi.bios.vendor: Dell Inc. dmi.bios.version: A28 dmi.board.name: 04JGCK dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA28:bd05/30/2019:br65.28:svnDellInc.:pnPrecisionT1700:pvr00:rvnDellInc.:rn04JGCK:rvrA01:cvnDellInc.:ct15:cvr: dmi.product.name: Precision T1700 dmi.product.sku: 05A6 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1905482/+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 1903048] Re: [SRU] Bluetooth won't activate on the pi 400
@hujq is there anything unusual about your bluetooth setup? miniuart-bt overlay or anything like that? I'm unable to replicate the failure here on a Pi 4 8GB -- 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/1903048 Title: [SRU] Bluetooth won't activate on the pi 400 Status in bluez package in Ubuntu: Triaged Status in bluez source package in Groovy: Fix Released Status in bluez source package in Hirsute: Triaged Bug description: [Impact] Without these patches, Bluetooth is inoperable on the recently released Raspberry Pi 400. [Test Case] * Boot the Ubuntu Desktop for Pi image on a Pi 400. * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is not enabled and attempting to activate it fails * Enable the -proposed repository for the release (groovy) * sudo apt update * sudo apt install bluez * sudo reboot * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is active and that Bluetooth devices (e.g. mice, mobile phones, headphones, etc.) can connect and operate correctly [Regression Potential] Extremely low (on groovy in particular, this has the same version of bluez as hirsute). The only significant risk is to non-Pi platforms or dongles which also use the Broadcom 43xx (or Cypress 305) chips for Bluetooth which might be inadvertently affected by these patches. [Original Description] The new Pi 400 has a slightly different Wifi/BT chip to the Pi4. Whilst wifi works happily, Bluetooth fails to operate. This doesn't appear to be an issue with either the firmware (the latest versions from upstream Raspbian have been tried), or the kernel (a known-good raspi kernel has been tested under Ubuntu), but with Bluez itself. Specifically, tracing the initialization with btmon on Raspbian and Ubuntu, the stack consistently fails when attempting to "Set Default PHY" on the latter. Curiously, under Ubuntu the adapter also appears to lack a MAC address. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903048/+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 1905555] [NEW] Xserver crash at start , black screen , 20.04 , Intel HD620
Public bug reported: Xserver crash at start , black screen , 20.04 , Intel HD630 Just happened since yesterday updates ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Wed Nov 25 12:48:16 2020 DistUpgraded: 2020-09-19 18:32:29,160 DEBUG pid is: 29157 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer UHD Graphics 620 (Whiskey Lake) [1558:1325] InstallationDate: Installed on 2019-03-04 (632 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b685 Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 002: ID 06cb:00a8 Synaptics, Inc. Bus 001 Device 004: ID 8087:0025 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N150ZU ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic root=UUID=5b433ea6-7902-4568-9ee0-36a15ff2f274 ro quiet splash i8042.reset vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-09-19 (66 days ago) dmi.bios.date: 10/19/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.01 dmi.board.asset.tag: Tag 12345 dmi.board.name: N150ZU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.01:bd10/19/2018:svnNotebook:pnN150ZU:pvrNotApplicable:rvnNotebook:rnN150ZU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N150ZU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook 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.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 ** Summary changed: - Xserver crash at start , black screen , 20.04 , Intel HD630 + Xserver crash at start , black screen , 20.04 , Intel HD620 -- 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/190 Title: Xserver crash at start , black screen , 20.04 , Intel HD620 Status in xorg package in Ubuntu: New Bug description: Xserver crash at start , black screen , 20.04 , Intel HD630 Just happened since yesterday updates ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Wed Nov 25 12:48:16 2020 DistUpgraded: 2020-09-19 18:32:29,160 DEBUG pid is: 29157 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer UHD Graphics 620 (Whiskey Lake) [1558:1325] InstallationDate: Installed on 2019-03-04 (632 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b685 Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 002: ID 06cb:00a8 Synaptics, Inc. Bus 001 Device 004: ID 8087:0025 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N150ZU ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic root=UUID=5b433ea6-7902-4568-9ee0-36a15ff2f274 ro quiet splash i8042.reset vt.handoff=7 Sourc
[Touch-packages] [Bug 1905555] Re: Xserver crash at start , black screen , 20.04 , Intel HD620
the crash dump ** Attachment added: "_usr_lib_xorg_Xorg.121.crash" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/190/+attachment/5437868/+files/_usr_lib_xorg_Xorg.121.crash -- 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/190 Title: Xserver crash at start , black screen , 20.04 , Intel HD620 Status in xorg package in Ubuntu: New Bug description: Xserver crash at start , black screen , 20.04 , Intel HD630 Just happened since yesterday updates ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Wed Nov 25 12:48:16 2020 DistUpgraded: 2020-09-19 18:32:29,160 DEBUG pid is: 29157 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer UHD Graphics 620 (Whiskey Lake) [1558:1325] InstallationDate: Installed on 2019-03-04 (632 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b685 Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 002: ID 06cb:00a8 Synaptics, Inc. Bus 001 Device 004: ID 8087:0025 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N150ZU ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic root=UUID=5b433ea6-7902-4568-9ee0-36a15ff2f274 ro quiet splash i8042.reset vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-09-19 (66 days ago) dmi.bios.date: 10/19/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.01 dmi.board.asset.tag: Tag 12345 dmi.board.name: N150ZU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.01:bd10/19/2018:svnNotebook:pnN150ZU:pvrNotApplicable:rvnNotebook:rnN150ZU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N150ZU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook 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.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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/190/+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 1905539] Re: package light-themes 16.10+18.04.20181005-0ubuntu1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that there was an error on your system when trying to install a particular package. Please execute the following command, as it will clear your package cache, in a terminal: sudo apt-get clean Then try performing the update again. This will likely resolve your issue, but the failure could be caused by filesystem or memory corruption. So please also run a fsck on your filesystem(s) and a memory test. Thanks in advance! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: corrupted-package ** Changed in: ubuntu-themes (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1905539 Title: package light-themes 16.10+18.04.20181005-0ubuntu1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 Status in ubuntu-themes package in Ubuntu: Invalid Bug description: crash occuring ProblemType: Package DistroRelease: Ubuntu 20.04 Package: light-themes 16.10+18.04.20181005-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Nov 25 12:23:19 2020 ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 InstallationDate: Installed on 2020-06-03 (174 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: ubuntu-themes Title: package light-themes 16.10+18.04.20181005-0ubuntu1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 UpgradeStatus: Upgraded to focal on 2020-11-25 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1905539/+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 1905560] [NEW] XServer Crashes with atk_component_scroll_to_point if NVIDIA Driver 340 is Used
Public bug reported: System: - Lenovo ThinkPad T61 with - Intel Core 2 Duo T7500 @ 2,2 GHz - NVIDIA G86M (Quadro NVS 140M) graphics chipset. - Samsung SSD 750, 250GByte - 4Gbyte Hauptspeicher OS: Ubuntu from 14.4 LTS, continuously upgraded to 18.04 LTS. NVIDIA third-party free driver installed via ubuntu-drivers. Notebook runs fine with 18.04. After upgrade to 20.04 LTS there is no GUI any longer. startx called from command-line reveals a crash of xserver due to an undefined symbol (atk_component_scroll_to_point) in libatk-bridge2.0-0. In the course of upgrading to 20.04 LTS, this lib has been updated from 2.26.2-1 to 2.34.2. I found this workaround: uninstall libatk-bridge2.0-0 (Purge). It has only 5 dependencies (some Python and Gnome-Orca) which are of no use to me. Downloaded 2.26.2-1 out of 18.04-repo and installed it via dpkg. Install runs smooth without any error message. After restart, GUI is back again. There is no doubt, the problem is caused by libatk-bridge2.0-0 > 2.26.2 due to the missing export of atk_component_scroll_to_point. Please restore this (and possibly other) exports, that have been dropped between 2.26.2 and 2.34.2, even if the corresponding functions are left empty. One must not drop any function from ABI without increasing library version. You can never tell, what relies on the existence of these functions. Regards, Klaus ** Affects: at-spi2-atk (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to at-spi2-atk in Ubuntu. https://bugs.launchpad.net/bugs/1905560 Title: XServer Crashes with atk_component_scroll_to_point if NVIDIA Driver 340 is Used Status in at-spi2-atk package in Ubuntu: New Bug description: System: - Lenovo ThinkPad T61 with - Intel Core 2 Duo T7500 @ 2,2 GHz - NVIDIA G86M (Quadro NVS 140M) graphics chipset. - Samsung SSD 750, 250GByte - 4Gbyte Hauptspeicher OS: Ubuntu from 14.4 LTS, continuously upgraded to 18.04 LTS. NVIDIA third-party free driver installed via ubuntu-drivers. Notebook runs fine with 18.04. After upgrade to 20.04 LTS there is no GUI any longer. startx called from command-line reveals a crash of xserver due to an undefined symbol (atk_component_scroll_to_point) in libatk-bridge2.0-0. In the course of upgrading to 20.04 LTS, this lib has been updated from 2.26.2-1 to 2.34.2. I found this workaround: uninstall libatk-bridge2.0-0 (Purge). It has only 5 dependencies (some Python and Gnome-Orca) which are of no use to me. Downloaded 2.26.2-1 out of 18.04-repo and installed it via dpkg. Install runs smooth without any error message. After restart, GUI is back again. There is no doubt, the problem is caused by libatk-bridge2.0-0 > 2.26.2 due to the missing export of atk_component_scroll_to_point. Please restore this (and possibly other) exports, that have been dropped between 2.26.2 and 2.34.2, even if the corresponding functions are left empty. One must not drop any function from ABI without increasing library version. You can never tell, what relies on the existence of these functions. Regards, Klaus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-atk/+bug/1905560/+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 1901609] Re: signond causes qprocess crash
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: signon (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to signon in Ubuntu. https://bugs.launchpad.net/bugs/1901609 Title: signond causes qprocess crash Status in signon package in Ubuntu: Confirmed Status in signon source package in Focal: Confirmed Status in signon source package in Groovy: Confirmed Status in signon source package in Hirsute: Confirmed Bug description: [Impact] Without the patch users are unable to add google accounts because signond crashes. This prevents users from using KDE's online accounts feature for google. The fix for this is to drop the no-rtti compile flag as qprocess relies on type info. This has no real downside for the user as it simply brings in type info. [Test Case] - in a plasma session - install kio-gdrive - run `systemsettings5 kcm_kaccounts` - add a new account - click on google - wait for login window to appear - signond shouldn't be crashing [Where problems could occur] Cannot think of any. It simply adds type info to the objects. Also upstream has rtti disabled for months and I'm not aware of any problems. [Other Info] This is a fairly grave issue as far as user experience is concerned. I'm reporting this bug upstream from where I found it, since I've learned that the signond package in KDE Neon is sourced from Ubuntu focal. This was found in signon (signond_8.59+17.10.20170606-0ubuntu2_amd64) from Focal Fossa Steps to reproduce: 1. Install KDE Plasma and qt 5.15.0 on Ubuntu focal base (IE: KDE Neon) 2. Install the kaccounts integration and kio-gdrive packages. 3. Open System settings and navigate to "Online Accounts" 4. Press "+ Add New Account" 5. Select "Google" Observed behaviour: - Window that would ask for authentication fails to load, and Online Accounts goes back to overview - system logs show a segfault in libqt5core.so which can be traced to a failure in qporcess, casued by signond (see links for further details) Expected behaviour: - New window opens with a webview where Google authentication credentials can be posted. - When qprocess runs it does not crash. Further reference information at the following links: 1. Bug in KDE Neon: https://bugs.kde.org/show_bug.cgi?id=426034 3. Relevant MR (Since merged) in signond: https://gitlab.com/accounts- sso/signond/-/merge_requests/27 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/signon/+bug/1901609/+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 1901609] Re: signond causes qprocess crash
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: signon (Ubuntu Focal) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to signon in Ubuntu. https://bugs.launchpad.net/bugs/1901609 Title: signond causes qprocess crash Status in signon package in Ubuntu: Confirmed Status in signon source package in Focal: Confirmed Status in signon source package in Groovy: Confirmed Status in signon source package in Hirsute: Confirmed Bug description: [Impact] Without the patch users are unable to add google accounts because signond crashes. This prevents users from using KDE's online accounts feature for google. The fix for this is to drop the no-rtti compile flag as qprocess relies on type info. This has no real downside for the user as it simply brings in type info. [Test Case] - in a plasma session - install kio-gdrive - run `systemsettings5 kcm_kaccounts` - add a new account - click on google - wait for login window to appear - signond shouldn't be crashing [Where problems could occur] Cannot think of any. It simply adds type info to the objects. Also upstream has rtti disabled for months and I'm not aware of any problems. [Other Info] This is a fairly grave issue as far as user experience is concerned. I'm reporting this bug upstream from where I found it, since I've learned that the signond package in KDE Neon is sourced from Ubuntu focal. This was found in signon (signond_8.59+17.10.20170606-0ubuntu2_amd64) from Focal Fossa Steps to reproduce: 1. Install KDE Plasma and qt 5.15.0 on Ubuntu focal base (IE: KDE Neon) 2. Install the kaccounts integration and kio-gdrive packages. 3. Open System settings and navigate to "Online Accounts" 4. Press "+ Add New Account" 5. Select "Google" Observed behaviour: - Window that would ask for authentication fails to load, and Online Accounts goes back to overview - system logs show a segfault in libqt5core.so which can be traced to a failure in qporcess, casued by signond (see links for further details) Expected behaviour: - New window opens with a webview where Google authentication credentials can be posted. - When qprocess runs it does not crash. Further reference information at the following links: 1. Bug in KDE Neon: https://bugs.kde.org/show_bug.cgi?id=426034 3. Relevant MR (Since merged) in signond: https://gitlab.com/accounts- sso/signond/-/merge_requests/27 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/signon/+bug/1901609/+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 1901609] Re: signond causes qprocess crash
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: signon (Ubuntu Groovy) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to signon in Ubuntu. https://bugs.launchpad.net/bugs/1901609 Title: signond causes qprocess crash Status in signon package in Ubuntu: Confirmed Status in signon source package in Focal: Confirmed Status in signon source package in Groovy: Confirmed Status in signon source package in Hirsute: Confirmed Bug description: [Impact] Without the patch users are unable to add google accounts because signond crashes. This prevents users from using KDE's online accounts feature for google. The fix for this is to drop the no-rtti compile flag as qprocess relies on type info. This has no real downside for the user as it simply brings in type info. [Test Case] - in a plasma session - install kio-gdrive - run `systemsettings5 kcm_kaccounts` - add a new account - click on google - wait for login window to appear - signond shouldn't be crashing [Where problems could occur] Cannot think of any. It simply adds type info to the objects. Also upstream has rtti disabled for months and I'm not aware of any problems. [Other Info] This is a fairly grave issue as far as user experience is concerned. I'm reporting this bug upstream from where I found it, since I've learned that the signond package in KDE Neon is sourced from Ubuntu focal. This was found in signon (signond_8.59+17.10.20170606-0ubuntu2_amd64) from Focal Fossa Steps to reproduce: 1. Install KDE Plasma and qt 5.15.0 on Ubuntu focal base (IE: KDE Neon) 2. Install the kaccounts integration and kio-gdrive packages. 3. Open System settings and navigate to "Online Accounts" 4. Press "+ Add New Account" 5. Select "Google" Observed behaviour: - Window that would ask for authentication fails to load, and Online Accounts goes back to overview - system logs show a segfault in libqt5core.so which can be traced to a failure in qporcess, casued by signond (see links for further details) Expected behaviour: - New window opens with a webview where Google authentication credentials can be posted. - When qprocess runs it does not crash. Further reference information at the following links: 1. Bug in KDE Neon: https://bugs.kde.org/show_bug.cgi?id=426034 3. Relevant MR (Since merged) in signond: https://gitlab.com/accounts- sso/signond/-/merge_requests/27 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/signon/+bug/1901609/+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 1465183] Re: ubuntu 15.04 dhcp: option routers and option rfc3442-classless-static-routes
In fact, RedHat, Windows, MacOS don't ignore an default routes with classless-static_route option. What about to add an some tunable to have same behavior in Ubuntu? It should be not a hard -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1465183 Title: ubuntu 15.04 dhcp: option routers and option rfc3442-classless-static- routes Status in isc-dhcp package in Ubuntu: Confirmed Bug description: Hi. Sorry for my bad english. Iam using option rfc3442-classless-static-routes in my dhcp-server. # cat /var/lib/dhcp/dhclient.eth0.leases lease { interface "eth0"; fixed-address 192.168.120.170; option subnet-mask 255.255.255.0; option routers 192.168.120.1; option dhcp-lease-time 86400; option dhcp-message-type 5; option domain-name-servers 192.168.120.1; option dhcp-server-identifier 192.168.120.1; option ntp-servers 192.168.120.1; option rfc3442-classless-static-routes 24,10,125,0,192,168,120,110; option broadcast-address 192.168.120.255; option domain-name "home.xmu"; renew 1 2015/06/15 05:45:48; rebind 1 2015/06/15 17:04:48; expire 1 2015/06/15 20:04:48; } In other operation system: # route -n Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 0.0.0.0 192.168.120.1 0.0.0.0 UG0 00 eth0 10.125.0.0 192.168.120.110 255.255.255.0 UG0 00 eth0 192.168.120.0 0.0.0.0 255.255.255.0 U 0 00 eth0 In ubuntu 15.04: # route -n Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 10.125.0.0 192.168.120.110 255.255.255.0 UG0 00 eth0 192.168.120.0 0.0.0.0 255.255.255.0 U 0 00 eth0 No default gateway!!! # cat /var/lib/dhcp/dhclient.leases lease { interface "eth0"; fixed-address 192.168.120.169; option subnet-mask 255.255.255.0; option routers 192.168.120.1; option dhcp-lease-time 86400; option dhcp-message-type 5; option domain-name-servers 192.168.120.1; option dhcp-server-identifier 192.168.120.1; option ntp-servers 192.168.120.1; option rfc3442-classless-static-routes 24,10,125,0,192,168,120,110; option broadcast-address 192.168.120.255; option domain-name "home.xmu"; renew 1 2015/06/15 07:41:11; rebind 1 2015/06/15 16:57:38; expire 1 2015/06/15 19:57:38; } If i comment option rfc3442-classless-static-routes in my dhcp-server. Default gateway works fine: # route -n Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 0.0.0.0 192.168.120.1 0.0.0.0 UG0 00 eth0 192.168.120.0 0.0.0.0 255.255.255.0 U 0 00 eth0 # cat /etc/issue Ubuntu 15.04 \n \l # uname -a Linux wp01 3.19.0-20-generic #20-Ubuntu SMP Fri May 29 10:10:47 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux # aptitude show isc-dhcp-client Package: isc-dhcp-client State: installed Automatically installed: no Version: 4.3.1-5ubuntu2.2 Priority: important Section: net Maintainer: Ubuntu Developers Architecture: amd64 Uncompressed Size: 698 k Depends: libc6 (>= 2.15), libdns-export100, libirs-export91, libisc-export95, debianutils (>= 2.8.2), isc-dhcp-common (= 4.3.1-5ubuntu2.2), iproute2 Suggests: resolvconf, avahi-autoipd, apparmor Provides: dhcp-client # aptitude show isc-dhcp-common Package: isc-dhcp-common State: installed Automatically installed: no Version: 4.3.1-5ubuntu2.2 Priority: important Section: net Maintainer: Ubuntu Developers Architecture: amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1465183/+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 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
@Hui Wang sudo apt install rtl8821ce-dkms didn't the magic in my case. hsp/hfp is still not working. I disabled Secure Boot on my laptop, I hope is not a problem. -- 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/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+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 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
@smurf, after you change to hsp/hfp mode and it fails, please run hciconfig -a > hcilog.txt and upload it. -- 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/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+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 1775392] Re: at-spi-bus-launcher makes Xorg crash when resuming from suspend
Ok, thank you for the info, I'll move the bug over there -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1775392 Title: at-spi-bus-launcher makes Xorg crash when resuming from suspend Status in at-spi2-core package in Ubuntu: Confirmed Bug description: If at-spi2-core is installed, when resuming from suspend messages like these are logged in systemd journal: at-spi-bus-launcher[31720]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0" at-spi-bus-launcher[31720]: after 8065 requests (8065 known processed) with 0 events remaining. The number of requests vary, it can reach more than 15000. Depending on the number of requests, the Xorg server crashes with SIGBUS. Depending on the exact moment Xorg crashes, when lightdm manages to recover, it shows a login greeter, or worst case scenario, it can't recover, a black screen is shown and the desptop session doesn't start. It took me a long time to discover the cause. The visible symptom was: once in a while when resuming from suspend, I got a login greeter instead of an unlock greeter, or a black screen which forced me to power down. Investigating, I found out that whenever that happened, there was a Xorg core left behind. Looking at the journal messages before the crash, there was always that flood of at-spi2-core requests. So I uninstalled at-spi2-core and Xorg never crashed anymore. This is a quite severe bug, which makes it impossible to use at- spi2-core. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: at-spi2-core (not installed) ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Jun 6 09:10:12 2018 InstallationDate: Installed on 2018-04-28 (38 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: at-spi2-core UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1775392/+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 1775392] Re: at-spi-bus-launcher makes Xorg crash when resuming from suspend
https://gitlab.gnome.org/GNOME/at-spi2-core/-/issues/27 ** Bug watch added: gitlab.gnome.org/GNOME/at-spi2-core/-/issues #27 https://gitlab.gnome.org/GNOME/at-spi2-core/-/issues/27 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1775392 Title: at-spi-bus-launcher makes Xorg crash when resuming from suspend Status in at-spi2-core package in Ubuntu: Confirmed Bug description: If at-spi2-core is installed, when resuming from suspend messages like these are logged in systemd journal: at-spi-bus-launcher[31720]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0" at-spi-bus-launcher[31720]: after 8065 requests (8065 known processed) with 0 events remaining. The number of requests vary, it can reach more than 15000. Depending on the number of requests, the Xorg server crashes with SIGBUS. Depending on the exact moment Xorg crashes, when lightdm manages to recover, it shows a login greeter, or worst case scenario, it can't recover, a black screen is shown and the desptop session doesn't start. It took me a long time to discover the cause. The visible symptom was: once in a while when resuming from suspend, I got a login greeter instead of an unlock greeter, or a black screen which forced me to power down. Investigating, I found out that whenever that happened, there was a Xorg core left behind. Looking at the journal messages before the crash, there was always that flood of at-spi2-core requests. So I uninstalled at-spi2-core and Xorg never crashed anymore. This is a quite severe bug, which makes it impossible to use at- spi2-core. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: at-spi2-core (not installed) ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Jun 6 09:10:12 2018 InstallationDate: Installed on 2018-04-28 (38 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: at-spi2-core UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1775392/+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 1835660] Re: initramfs unpacking failed
So lz4 compressed initrd looks like this with hexdump 568f580 0523 00ac 54bf 4152 4c49 5245 2121 0021 568f590 0001 1cff 0050 568f59a I do wonder what ram is initialized too, and how those things look when kernel reads initrd from memory as loaded by the bootloader / qemu. -- 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/1835660 Title: initramfs unpacking failed Status in OEM Priority Project: New Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. --- However, we currently believe that the decoding error reported in dmesg is actually harmless and has no impact on usability on the system. Switching from lz4 to gzip compression, simply papers over the warning, without any benefits, and slows down boot. Kernel should be fixed to correctly parse lz4 compressed initrds, or at least lower the warning, to not be user visible as an error. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1835660/+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 1905580] [NEW] package linux-image-5.4.0-54-generic 5.4.0-54.60 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: Probably a partition /var full ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-54-generic 5.4.0-54.60 ProcVersionSignature: Ubuntu 4.15.0-124.127-generic 4.15.18 Uname: Linux 4.15.0-124-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 25 15:28 seq crw-rw 1 root audio 116, 33 Nov 25 15:28 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Date: Wed Nov 25 15:48:52 2020 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=bd9c94cd-f9a0-43e5-85ad-f2af4b8c6389 InstallationDate: Installed on 2017-04-12 (1322 days ago) InstallationMedia: Ubuntu-Server 16.10 "Yakkety Yak" - Release amd64 (20161012.1) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-124-generic root=UUID=c25cdc36-f388-482a-acd1-bbd1abbc77c6 ro net.ifnames=0 biosdevname=0 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: grub-pc 2.04-1ubuntu26.7 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: initramfs-tools Title: package linux-image-5.4.0-54-generic 5.4.0-54.60 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to focal on 2020-11-25 (0 days ago) WifiSyslog: dmi.bios.date: 09/17/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd09/17/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- 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/1905580 Title: package linux-image-5.4.0-54-generic 5.4.0-54.60 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: Probably a partition /var full ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-54-generic 5.4.0-54.60 ProcVersionSignature: Ubuntu 4.15.0-124.127-generic 4.15.18 Uname: Linux 4.15.0-124-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 25 15:28 seq crw-rw 1 root audio 116, 33 Nov 25 15:28 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Date: Wed Nov 25 15:48:52 2020 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=bd9c94cd-f9a0-43e5-85ad-f2af4b8c6389 InstallationDate: Installed on 2017-04-12 (1322 days ago) InstallationMedia: Ubuntu-Server 16.10 "Yakkety Yak" - Release amd64 (20161012.1) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-124-generic root=UUID=c25cdc36-f388-482a-acd1-bbd1abbc77c6 ro net.ifnames=0 biosdevname=0 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: grub-pc 2.04-1ubuntu26.7 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: initramfs-tools Title: package linux-im
[Touch-packages] [Bug 1880198] Re: Ubuntu as bluetooth speaker - volume on bluetooth client ignored
Is this bug filed against the correct package? -- 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/1880198 Title: Ubuntu as bluetooth speaker - volume on bluetooth client ignored Status in pulseaudio package in Ubuntu: New Bug description: I'm using my 20.04 system as a media center. It's got a bluetooth adapter plugged into a USB port. I can connect to the system with my phone and ipad as an A2DP source and play music. The problem is that the volume on the source device is not respected When the volume on the source device goes to 0, the sound is muted as expected, but any other volume on the source device leads to the same volume on the Ubuntu server. The only way to adjust the volume is from the server. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.2 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kodi 1455 F pulseaudio /dev/snd/controlC0: kodi 1455 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri May 22 16:42:57 2020 InstallationDate: Installed on 2015-09-30 (1695 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/04/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2404 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H97M-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2404:bd03/04/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH97M-PLUS:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1880198/+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 1880198] Re: Ubuntu as bluetooth speaker - volume on bluetooth client ignored
Would anyone have an idea as to a workaround, or an idea of how I could debug this problem? -- 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/1880198 Title: Ubuntu as bluetooth speaker - volume on bluetooth client ignored Status in pulseaudio package in Ubuntu: New Bug description: I'm using my 20.04 system as a media center. It's got a bluetooth adapter plugged into a USB port. I can connect to the system with my phone and ipad as an A2DP source and play music. The problem is that the volume on the source device is not respected When the volume on the source device goes to 0, the sound is muted as expected, but any other volume on the source device leads to the same volume on the Ubuntu server. The only way to adjust the volume is from the server. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.2 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kodi 1455 F pulseaudio /dev/snd/controlC0: kodi 1455 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri May 22 16:42:57 2020 InstallationDate: Installed on 2015-09-30 (1695 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/04/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2404 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H97M-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2404:bd03/04/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH97M-PLUS:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1880198/+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 1905580] Re: package linux-image-5.4.0-54-generic 5.4.0-54.60 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
** Tags removed: need-duplicate-check -- 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/1905580 Title: package linux-image-5.4.0-54-generic 5.4.0-54.60 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: Probably a partition /var full ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-54-generic 5.4.0-54.60 ProcVersionSignature: Ubuntu 4.15.0-124.127-generic 4.15.18 Uname: Linux 4.15.0-124-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 25 15:28 seq crw-rw 1 root audio 116, 33 Nov 25 15:28 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Date: Wed Nov 25 15:48:52 2020 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=bd9c94cd-f9a0-43e5-85ad-f2af4b8c6389 InstallationDate: Installed on 2017-04-12 (1322 days ago) InstallationMedia: Ubuntu-Server 16.10 "Yakkety Yak" - Release amd64 (20161012.1) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-124-generic root=UUID=c25cdc36-f388-482a-acd1-bbd1abbc77c6 ro net.ifnames=0 biosdevname=0 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: grub-pc 2.04-1ubuntu26.7 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: initramfs-tools Title: package linux-image-5.4.0-54-generic 5.4.0-54.60 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to focal on 2020-11-25 (0 days ago) WifiSyslog: dmi.bios.date: 09/17/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd09/17/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1905580/+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 1905576] [NEW] I cannot drag icons above to a particular region of my desktop
You have been subscribed to a public bug: I have two monitors set up, and one is vertical. Here is a video: https://cdn.discordapp.com/attachments/653633559206166541/781166447174352936/20201121_133143_1_1.mp4 1. Ubuntu 18.04.5 LTS 2. Not sure what package this is 3. I expected the icon to go where I dragged it 4. The x-axis position was the same, but the y-axis position always gets set to a certain height whenever I drag above that height (I think this has to do with the top of my other display). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.4.0-54.60~18.04.1-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .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 450.80.02 Wed Sep 23 01:13:39 UTC 2020 GCC version: gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04) ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Nov 25 09:20:33 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 450.80.02, 5.4.0-53-generic, x86_64: installed nvidia, 450.80.02, 5.4.0-54-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation Device [10de:1e81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8738] InstallationDate: Installed on 2020-10-12 (44 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) MachineType: Micro-Star International Co., Ltd. MS-7B12 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-54-generic root=UUID=321ae9a5-66cd-481d-b940-0f3c32a130c4 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.71 dmi.board.asset.tag: Default string dmi.board.name: MEG Z390 ACE (MS-7B12) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.71:bd10/30/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B12:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMEGZ390ACE(MS-7B12):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7B12 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- I cannot drag icons above to a particular region of my desktop https://bugs.launchpad.net/bugs/1905576 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 1905576] Re: I cannot drag icons above to a particular region of my desktop
** 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/1905576 Title: I cannot drag icons above to a particular region of my desktop Status in xorg package in Ubuntu: New Bug description: I have two monitors set up, and one is vertical. Here is a video: https://cdn.discordapp.com/attachments/653633559206166541/781166447174352936/20201121_133143_1_1.mp4 1. Ubuntu 18.04.5 LTS 2. Not sure what package this is 3. I expected the icon to go where I dragged it 4. The x-axis position was the same, but the y-axis position always gets set to a certain height whenever I drag above that height (I think this has to do with the top of my other display). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.4.0-54.60~18.04.1-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .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 450.80.02 Wed Sep 23 01:13:39 UTC 2020 GCC version: gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04) ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Nov 25 09:20:33 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 450.80.02, 5.4.0-53-generic, x86_64: installed nvidia, 450.80.02, 5.4.0-54-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation Device [10de:1e81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8738] InstallationDate: Installed on 2020-10-12 (44 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) MachineType: Micro-Star International Co., Ltd. MS-7B12 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-54-generic root=UUID=321ae9a5-66cd-481d-b940-0f3c32a130c4 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.71 dmi.board.asset.tag: Default string dmi.board.name: MEG Z390 ACE (MS-7B12) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.71:bd10/30/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B12:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMEGZ390ACE(MS-7B12):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7B12 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1905576/+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 1905594] [NEW] upgrade disables all serial devices and consoles
Public bug reported: [impact] when upgrading, all serial devices are changed to 'dead' and thus all serial consoles are stopped [test case] on a system configured with a serial console, upgrade from focal to the latest systemd package from upstream, and check the serial console. the state of the serial port and/or serial console can also be checked with systemctl status, e.g.: $ systemctl status dev-ttyS0.device [regression potential] and regression would likely involve incorrectly detected or operational devices after a systemd version upgrade, or after a systemd pid1 reexec or reload. [scope] TBD ** 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/1905594 Title: upgrade disables all serial devices and consoles Status in systemd package in Ubuntu: New Bug description: [impact] when upgrading, all serial devices are changed to 'dead' and thus all serial consoles are stopped [test case] on a system configured with a serial console, upgrade from focal to the latest systemd package from upstream, and check the serial console. the state of the serial port and/or serial console can also be checked with systemctl status, e.g.: $ systemctl status dev-ttyS0.device [regression potential] and regression would likely involve incorrectly detected or operational devices after a systemd version upgrade, or after a systemd pid1 reexec or reload. [scope] TBD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1905594/+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 1905044] Re: systemd 245.4-4ubuntu3.3 ADT test failure with linux-hwe-5.8
@ddstreet thanks for pointing to that other bug report. After applying the fix from https://github.com/systemd/systemd/pull/16424 to systemd_245.4-4ubuntu3.3, 'systemd show' does work: $ ./systemctl show -p CapabilityBoundingSet apparmor CapabilityBoundingSet=cap_chown cap_dac_override cap_dac_read_search cap_fowner cap_fsetid cap_kill But the testcase fails a little bit down the line: $ ./test-cap-list cap_chown = 0 cap_dac_override = 1 cap_dac_read_search = 2 [...] cap_block_suspend vs. cap_block_suspend cap_audit_read vs. cap_audit_read Assertion 'streq(t1, t)' failed at src/test/test-cap-list.c:61, function test_capability_set_one(). Aborting. Aborted (core dumped) -- 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/1905044 Title: systemd 245.4-4ubuntu3.3 ADT test failure with linux-hwe-5.8 Status in systemd package in Ubuntu: Invalid Status in systemd source package in Focal: Confirmed Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/s/systemd/20201117_174614_4ece6@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/s/systemd/20201117_221555_48b91@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/ppc64el/s/systemd/20201117_175806_e779f@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/s/systemd/20201117_153051_90e7e@/log.gz The failing testcases are: - root-unittests Assertion 'capability_set_to_string_alloc(c, &t1) == 0' failed at src/test/test-cap-list.c:60, funct ion test_capability_set_one(). Aborting. FAIL: test-cap-list (code: 134) - upstream TEST-24-UNIT-TESTS: --- test-cap-list begin --- Assertion 'capability_set_to_string_alloc(c, &t1) == 0' failed at src/test/test-cap-list.c:60, funct ion test_capability_set_one(). Aborting. --- test-cap-list end --- Both seem to be failing with the same assertion. These tests are successful on Focal with linux 5.4, therefore they would regress when upgrading the kernel from 5.4 to 5.8. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1905044/+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 1905044] Re: systemd 245.4-4ubuntu3.3 ADT test failure with linux-hwe-5.8
So I'm wondering if some other fixes are needed as well do fix the testcase. -- 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/1905044 Title: systemd 245.4-4ubuntu3.3 ADT test failure with linux-hwe-5.8 Status in systemd package in Ubuntu: Invalid Status in systemd source package in Focal: Confirmed Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/s/systemd/20201117_174614_4ece6@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/s/systemd/20201117_221555_48b91@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/ppc64el/s/systemd/20201117_175806_e779f@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/s/systemd/20201117_153051_90e7e@/log.gz The failing testcases are: - root-unittests Assertion 'capability_set_to_string_alloc(c, &t1) == 0' failed at src/test/test-cap-list.c:60, funct ion test_capability_set_one(). Aborting. FAIL: test-cap-list (code: 134) - upstream TEST-24-UNIT-TESTS: --- test-cap-list begin --- Assertion 'capability_set_to_string_alloc(c, &t1) == 0' failed at src/test/test-cap-list.c:60, funct ion test_capability_set_one(). Aborting. --- test-cap-list end --- Both seem to be failing with the same assertion. These tests are successful on Focal with linux 5.4, therefore they would regress when upgrading the kernel from 5.4 to 5.8. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1905044/+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 1905594] Re: upgrade disables all serial devices and consoles
as this is needed only for the debian experimental branch (with v247-rc2), marking this as invalid for ubuntu. ** Description changed: [impact] when upgrading, all serial devices are changed to 'dead' and thus all serial consoles are stopped [test case] on a system configured with a serial console, upgrade from focal to the latest systemd package from upstream, and check the serial console. the state of the serial port and/or serial console can also be checked with systemctl status, e.g.: $ systemctl status dev-ttyS0.device [regression potential] and regression would likely involve incorrectly detected or operational devices after a systemd version upgrade, or after a systemd pid1 reexec or reload. [scope] - TBD + both upstream commits (ids below) are first included upstream in + v247-rc1 + + [other info] + + Upstream commit e77b146f825ef1bb63c297cc713962b94422d2c6 slightly + altered the meaning of the 'G' sd-device db tag, to 'any' tag, and added + a new 'Q' tag, meaning 'current' tag. When upgrading from udev before + that commit to after the commit, the existing udev db is not updated, so + the 'Q' tag is not present in the /run/udev/data/ db file for any + previously-existing devices. + + However, upstream commit 242c1c075aa284c8a8657c5aca36147f528146ba then + changes the 'device_is_ready()' check in src/core/device.c to also check + for the 'current' tag of 'systemd'. That tag will not be present for any + devices in the system since udev just now was changed to know about the + 'Q' type 'current' tags, and has not updated its /run/udev/data db + files. + + This leads to the systemd daemon-reexec ignoring all devices tagged with + 'systemd', but only the older 'G' tag and not the new 'Q' tag, and + marking them all as 'dead'. ** Changed in: systemd (Ubuntu) Status: New => Invalid -- 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/1905594 Title: upgrade disables all serial devices and consoles Status in systemd package in Ubuntu: Invalid Bug description: [impact] when upgrading, all serial devices are changed to 'dead' and thus all serial consoles are stopped [test case] on a system configured with a serial console, upgrade from focal to the latest systemd package from upstream, and check the serial console. the state of the serial port and/or serial console can also be checked with systemctl status, e.g.: $ systemctl status dev-ttyS0.device [regression potential] and regression would likely involve incorrectly detected or operational devices after a systemd version upgrade, or after a systemd pid1 reexec or reload. [scope] both upstream commits (ids below) are first included upstream in v247-rc1 [other info] Upstream commit e77b146f825ef1bb63c297cc713962b94422d2c6 slightly altered the meaning of the 'G' sd-device db tag, to 'any' tag, and added a new 'Q' tag, meaning 'current' tag. When upgrading from udev before that commit to after the commit, the existing udev db is not updated, so the 'Q' tag is not present in the /run/udev/data/ db file for any previously-existing devices. However, upstream commit 242c1c075aa284c8a8657c5aca36147f528146ba then changes the 'device_is_ready()' check in src/core/device.c to also check for the 'current' tag of 'systemd'. That tag will not be present for any devices in the system since udev just now was changed to know about the 'Q' type 'current' tags, and has not updated its /run/udev/data db files. This leads to the systemd daemon-reexec ignoring all devices tagged with 'systemd', but only the older 'G' tag and not the new 'Q' tag, and marking them all as 'dead'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1905594/+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 1905167] Re: htop shows 100% usage of systemd-udevd
I should also note that attaching my Android phone isn't detected/showed in Nautilus, but not sure if this has anything to do with systemd-udevd. -- 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/1905167 Title: htop shows 100% usage of systemd-udevd Status in nvidia-graphics-drivers-455 package in Ubuntu: New Status in systemd package in Ubuntu: Invalid Bug description: I'm attaching a perf profile. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.3 ProcVersionSignature: Ubuntu 5.4.0-54.60-lowlatency 5.4.65 Uname: Linux 5.4.0-54-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Nov 22 13:57:47 2020 InstallationDate: Installed on 2020-02-08 (287 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Acer Aspire A515-51G ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-lowlatency root=/dev/mapper/vgubuntu-root ro quiet splash resume=UUID=f0e63db4-d3af-4977-a82a-5a46a3c677ae lockdown=confidentiality intel_iommu=on iommu=pt vfio-pci.ids=10de:1d10 vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/dnscrypt-proxy.service → /etc/systemd/system/dnscrypt-proxy.service.d/override.conf [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. UpgradeStatus: Upgraded to focal on 2020-10-23 (29 days ago) dmi.bios.date: 01/03/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.02 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Charmander_KL dmi.board.vendor: KBL dmi.board.version: V2.02 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.02 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.02:bd01/03/2019:svnAcer:pnAspireA515-51G:pvrV2.02:rvnKBL:rnCharmander_KL:rvrV2.02:cvnAcer:ct10:cvrV2.02: dmi.product.family: Aspire 5 dmi.product.name: Aspire A515-51G dmi.product.sku: dmi.product.version: V2.02 dmi.sys.vendor: Acer mtime.conffile..etc.apport.crashdb.conf: 2020-05-15T09:41:35.683742 mtime.conffile..etc.systemd.sleep.conf: 2020-09-26T18:33:31.018002 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-455/+bug/1905167/+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 1899288] Re: Python3 can't co-exist with Oracle's VirtualBox on 20.10
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: dh-python (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/1899288 Title: Python3 can't co-exist with Oracle's VirtualBox on 20.10 Status in dh-python package in Ubuntu: Confirmed Status in what-is-python package in Ubuntu: Confirmed Bug description: Sorry I couldn't file this bug against the correct packages. The form told me there are no such packages as python-is-python3 and dh-python in Ubuntu... Release: Groovy Gorilla (Ubuntu 20.10). Package versions: python-is-python3 3.8.2-4 dh-python 4.20200925 The release of Ubuntu 20.10 is less than two weeks out, so I'd like to draw attention to a problem I've run into. It seems that 20.10 defaults to python3 and wants to install python-is-python3, which pulls in the latest version of dh-python, which in turn can't co-exist with Oracle's Virtualbox-6.1 and wants to uninstall it. I don't mind having _both_ python2 (apparently a requirement of VirtualBox) and python3 installed. But as of right now I can have either python-is-python3, and not be able to do a complete upgrade since virtualbox-6.1 will be uninstalled, or python-is-python2, in which case I cripple 20.10's python3 install, since I won't get dh- python and python-six. Ia there something the python packagers do about this? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/1899288/+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 1899288] Re: Python3 can't co-exist with Oracle's VirtualBox on 20.10
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: what-is-python (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/1899288 Title: Python3 can't co-exist with Oracle's VirtualBox on 20.10 Status in dh-python package in Ubuntu: Confirmed Status in what-is-python package in Ubuntu: Confirmed Bug description: Sorry I couldn't file this bug against the correct packages. The form told me there are no such packages as python-is-python3 and dh-python in Ubuntu... Release: Groovy Gorilla (Ubuntu 20.10). Package versions: python-is-python3 3.8.2-4 dh-python 4.20200925 The release of Ubuntu 20.10 is less than two weeks out, so I'd like to draw attention to a problem I've run into. It seems that 20.10 defaults to python3 and wants to install python-is-python3, which pulls in the latest version of dh-python, which in turn can't co-exist with Oracle's Virtualbox-6.1 and wants to uninstall it. I don't mind having _both_ python2 (apparently a requirement of VirtualBox) and python3 installed. But as of right now I can have either python-is-python3, and not be able to do a complete upgrade since virtualbox-6.1 will be uninstalled, or python-is-python2, in which case I cripple 20.10's python3 install, since I won't get dh- python and python-six. Ia there something the python packagers do about this? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/1899288/+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 1905627] [NEW] Bluetooth stops working on Raspberry Pi 4 with bluez 5.55-0ubuntu1.1
Public bug reported: Bluetooth stops working after updating to bluez version 5.55-0ubuntu1.1. /usr/bin/btuart returns "bcm43xx_init Initialization timed out". Bluetooth is working again if bluez is reverted to version 5.55-0ubuntu1. I don't have any unusual setup like miniuart-bt. Release:20.10 bluez: Installed: 5.55-0ubuntu1.1 Candidate: 5.55-0ubuntu1.1 Version table: *** 5.55-0ubuntu1.1 500 500 http://ports.ubuntu.com/ubuntu-ports groovy-updates/main arm64 Packages 100 /var/lib/dpkg/status 5.55-0ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports groovy/main arm64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: bluez 5.55-0ubuntu1.1 ProcVersionSignature: Ubuntu 5.8.0-1007.10-raspi 5.8.14 Uname: Linux 5.8.0-1007-raspi aarch64 ApportVersion: 2.20.11-0ubuntu50.2 Architecture: arm64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Nov 25 16:09:03 2020 ImageMediaBuild: 20200423.1 InterestingModules: bnep bluetooth Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805 USB 3.0 Host Controller Lsusb: Bus 002 Device 002: ID 1058:25ee Western Digital Technologies, Inc. My Book 25EE Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M |__ Port 2: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_headphones=1 video=HDMI-A-1:1920x1080M@60 smsc95xx.macaddr=DC:A6:32:B9:18:CC vc_mem.mem_base=0x3eb0 vc_mem.mem_size=0x3ff0 dwc_otg.lpm_enable=0 console=tty1 root=PARTUUID=5f9d0997-1b4e-423b-ad5e-8bce1a7e1ae4 rootfstype=ext4 elevator=deadline rootwait fixrtc SourcePackage: bluez UpgradeStatus: Upgraded to groovy on 2020-10-23 (33 days ago) acpidump: hciconfig: rfkill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 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/1905627 Title: Bluetooth stops working on Raspberry Pi 4 with bluez 5.55-0ubuntu1.1 Status in bluez package in Ubuntu: New Bug description: Bluetooth stops working after updating to bluez version 5.55-0ubuntu1.1. /usr/bin/btuart returns "bcm43xx_init Initialization timed out". Bluetooth is working again if bluez is reverted to version 5.55-0ubuntu1. I don't have any unusual setup like miniuart-bt. Release: 20.10 bluez: Installed: 5.55-0ubuntu1.1 Candidate: 5.55-0ubuntu1.1 Version table: *** 5.55-0ubuntu1.1 500 500 http://ports.ubuntu.com/ubuntu-ports groovy-updates/main arm64 Packages 100 /var/lib/dpkg/status 5.55-0ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports groovy/main arm64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: bluez 5.55-0ubuntu1.1 ProcVersionSignature: Ubuntu 5.8.0-1007.10-raspi 5.8.14 Uname: Linux 5.8.0-1007-raspi aarch64 ApportVersion: 2.20.11-0ubuntu50.2 Architecture: arm64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Nov 25 16:09:03 2020 ImageMediaBuild: 20200423.1 InterestingModules: bnep bluetooth Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805 USB 3.0 Host Controller Lsusb: Bus 002 Device 002: ID 1058:25ee Western Digital Technologies, Inc. My Book 25EE Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M |__ Port 2: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_headphones=1 video=HDMI-A-1:1920x1080M@60 smsc95xx.macaddr=DC:A6:32:B9:18:CC vc_mem.mem_base=0x3eb0 vc_mem.mem_size=0x3ff0 dwc_otg.lpm_enable=0 console=tty1 root=PARTUUID=5f9d0997-1b4e-423b-ad5e-8bce1a7e1ae4 rootfstype=ext4 elevator=deadline rootwait fixrtc SourcePackage: bluez UpgradeStatus: Upgraded to groovy on 2020-10-23 (33 days ago) acpidump: hciconfig: rfkill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no To man
[Touch-packages] [Bug 1903048] Re: [SRU] Bluetooth won't activate on the pi 400
I opened a new bug #1905627. And I didn't change anything regarding Bluetooth from Ubuntu 20.10 default configuration. There is no miniuart- bt in /boot/firmware/config.txt. -- 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/1903048 Title: [SRU] Bluetooth won't activate on the pi 400 Status in bluez package in Ubuntu: Triaged Status in bluez source package in Groovy: Fix Released Status in bluez source package in Hirsute: Triaged Bug description: [Impact] Without these patches, Bluetooth is inoperable on the recently released Raspberry Pi 400. [Test Case] * Boot the Ubuntu Desktop for Pi image on a Pi 400. * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is not enabled and attempting to activate it fails * Enable the -proposed repository for the release (groovy) * sudo apt update * sudo apt install bluez * sudo reboot * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is active and that Bluetooth devices (e.g. mice, mobile phones, headphones, etc.) can connect and operate correctly [Regression Potential] Extremely low (on groovy in particular, this has the same version of bluez as hirsute). The only significant risk is to non-Pi platforms or dongles which also use the Broadcom 43xx (or Cypress 305) chips for Bluetooth which might be inadvertently affected by these patches. [Original Description] The new Pi 400 has a slightly different Wifi/BT chip to the Pi4. Whilst wifi works happily, Bluetooth fails to operate. This doesn't appear to be an issue with either the firmware (the latest versions from upstream Raspbian have been tried), or the kernel (a known-good raspi kernel has been tested under Ubuntu), but with Bluez itself. Specifically, tracing the initialization with btmon on Raspbian and Ubuntu, the stack consistently fails when attempting to "Set Default PHY" on the latter. Curiously, under Ubuntu the adapter also appears to lack a MAC address. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903048/+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 1905044] Re: systemd 245.4-4ubuntu3.3 ADT test failure with linux-hwe-5.8
yeah, the testcase will need to be fixed with something like https://github.com/ddstreet/systemd/commits/test_cap_list -- 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/1905044 Title: systemd 245.4-4ubuntu3.3 ADT test failure with linux-hwe-5.8 Status in systemd package in Ubuntu: Invalid Status in systemd source package in Focal: Confirmed Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/s/systemd/20201117_174614_4ece6@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/s/systemd/20201117_221555_48b91@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/ppc64el/s/systemd/20201117_175806_e779f@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/s/systemd/20201117_153051_90e7e@/log.gz The failing testcases are: - root-unittests Assertion 'capability_set_to_string_alloc(c, &t1) == 0' failed at src/test/test-cap-list.c:60, funct ion test_capability_set_one(). Aborting. FAIL: test-cap-list (code: 134) - upstream TEST-24-UNIT-TESTS: --- test-cap-list begin --- Assertion 'capability_set_to_string_alloc(c, &t1) == 0' failed at src/test/test-cap-list.c:60, funct ion test_capability_set_one(). Aborting. --- test-cap-list end --- Both seem to be failing with the same assertion. These tests are successful on Focal with linux 5.4, therefore they would regress when upgrading the kernel from 5.4 to 5.8. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1905044/+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 1905628] [NEW] /usr/share/doc/udhcpd/changelog.Debian.gz links to a nonexistent file
Public bug reported: In package: https://packages.ubuntu.com/focal-updates/udhcpc changelog file is linked to nonexistent file: ls -l /usr/share/doc/udhcpd/changelog.Debian.gz lrwxrwxrwx 1 root root 30 lis 11 13:15 /usr/share/doc/udhcpd/changelog.Debian.gz -> ../busybox/changelog.Debian.gz ls: cannot access '/usr/share/doc/busybox/changelog.Debian.gz': No such file or directory It should be linked to: /usr/share/doc/busybox-static/changelog.Debian.gz Description:Ubuntu 20.04.1 LTS Release:20.04 Codename: focal ** Affects: busybox (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/1905628 Title: /usr/share/doc/udhcpd/changelog.Debian.gz links to a nonexistent file Status in busybox package in Ubuntu: New Bug description: In package: https://packages.ubuntu.com/focal-updates/udhcpc changelog file is linked to nonexistent file: ls -l /usr/share/doc/udhcpd/changelog.Debian.gz lrwxrwxrwx 1 root root 30 lis 11 13:15 /usr/share/doc/udhcpd/changelog.Debian.gz -> ../busybox/changelog.Debian.gz ls: cannot access '/usr/share/doc/busybox/changelog.Debian.gz': No such file or directory It should be linked to: /usr/share/doc/busybox-static/changelog.Debian.gz Description:Ubuntu 20.04.1 LTS Release:20.04 Codename: focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1905628/+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 1833174] Re: Shadowing the vim-window results in vim-gtk3 crash
** Changed in: vim (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1833174 Title: Shadowing the vim-window results in vim-gtk3 crash Status in vim: Unknown Status in vim package in Ubuntu: Fix Committed Status in vim source package in Focal: Triaged Status in vim source package in Groovy: Triaged Bug description: With XFCE when I try to "shadow" the vim-gtk3 window (just to show only the title bar) it results in a vim crash and the window just disappears without any core dump neither .swp files on. The only message I get on the terminal is BadMatch (invalid parameter attributes) Vim: Got X error Vim: Finished. This behaviour started from Xubuntu 18.04. The vim-gtk package is not suffering from this problem. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: vim-gtk3 2:8.1.0320-1ubuntu3.1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Jun 18 09:10:38 2019 InstallationDate: Installed on 2019-04-23 (55 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: vim UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/vim/+bug/1833174/+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 1902760] Re: Please merge linker bugfix into Ubuntu 20.04 LTS
blocked on this being in the 2.34 branch upstream ** Changed in: binutils (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1902760 Title: Please merge linker bugfix into Ubuntu 20.04 LTS Status in binutils: Fix Released Status in intel: New Status in binutils package in Ubuntu: Incomplete Bug description: Binutils bug https://sourceware.org/bugzilla/show_bug.cgi?id=26262 fixes a problem that Intel Fortran is running into when using the -ipo option to request link time optimization. Please merge the fix into Ubuntu 20.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/1902760/+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 1905635] [NEW] package linux-image-5.8.0-29-generic 5.8.0-29.31 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: when i install this package, there is this error. ProblemType: Package DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-29-generic 5.8.0-29.31 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: frank 1599 F pulseaudio CasperMD5CheckResult: skip Date: Thu Nov 26 07:52:20 2020 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2020-11-11 (14 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: Dell Inc. OptiPlex 3010 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-25-generic root=UUID=01cc6221-9ec9-491d-bbc6-867edc2eba4a ro quiet splash vt.handoff=7 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.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: /usr/bin/python3.8, Python 3.8.6, unpackaged RelatedPackageVersions: grub-pc 2.04-1ubuntu35 RfKill: SourcePackage: initramfs-tools Title: package linux-image-5.8.0-29-generic 5.8.0-29.31 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2013 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 042P49 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd01/31/2013:br4.6:svnDellInc.:pnOptiPlex3010:pvr01:rvnDellInc.:rn042P49:rvrA01:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 3010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package groovy -- 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/1905635 Title: package linux-image-5.8.0-29-generic 5.8.0-29.31 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: when i install this package, there is this error. ProblemType: Package DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-29-generic 5.8.0-29.31 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: frank 1599 F pulseaudio CasperMD5CheckResult: skip Date: Thu Nov 26 07:52:20 2020 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2020-11-11 (14 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: Dell Inc. OptiPlex 3010 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-25-generic root=UUID=01cc6221-9ec9-491d-bbc6-867edc2eba4a ro quiet splash vt.handoff=7 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.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: /usr/bin/python3.8, Python 3.8.6, unpackaged RelatedPackageVersions: grub-pc 2.04-1ubuntu35 RfKill: SourcePackage: initramfs-tools Title: package linux-image-5.8.0-29-generic 5.8.0-29.31 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2013 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 042P49 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd01/31/2013:br4.6:svnDellInc.:pnOptiPlex3010:pvr01:rvnDellInc.:rn042P49:rvrA01:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 3010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1905635/+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 1904765] Re: Resolution not set or inappropriate
*** This bug is a duplicate of bug 1833855 *** https://bugs.launchpad.net/bugs/1833855 ** This bug is no longer a duplicate of bug 1899152 [i915] VGA resolution limited to 1024x768, EDID ignored or missing? ** This bug has been marked a duplicate of bug 1833855 i915: EDID not detected on VGA resulting in low resolution -- 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/1904765 Title: Resolution not set or inappropriate Status in xorg package in Ubuntu: New Bug description: The resolution is stuck at 1024x768. My screen can display 1440x900. I added the needed resolution to the settings. Even then it is not changing to the new. It is reverting back again and again to 1024x768. This is the second time I am reporting this issue to you. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Nov 18 22:43:44 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 82G33/G31 Express Integrated Graphics Controller [8086:29c2] (rev 10) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation 82G33/G31 Express Integrated Graphics Controller [8086:29c2] InstallationDate: Installed on 2020-10-21 (28 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: OEM OEM ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic root=UUID=ddc3d754-e174-4bc9-8cb7-7d4c277bb4e9 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/24/2018 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.chassis.type: 3 dmi.chassis.vendor: OEM dmi.chassis.version: OEM dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd08/24/2018:svnOEM:pnOEM:pvrOEM:rvn:rn:rvr:cvnOEM:ct3:cvrOEM: dmi.product.name: OEM dmi.product.version: OEM dmi.sys.vendor: OEM 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 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1904765/+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 1904671] Re: After a certain amount of time after the session is launched, mouse clicks are no longer accepted
It sounds like gnome-shell is frozen/crashed and Xorg is still running. Please: 1. Remove any gnome-shell extensions you may have installed and log out and in again. 2. If the problem still happens, check the Extensions app and disable all extensions. Then log out and in again. 2. If the problem still happens, please follow these steps: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment -- 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/1904671 Title: After a certain amount of time after the session is launched, mouse clicks are no longer accepted Status in gnome-shell package in Ubuntu: Incomplete Bug description: X11, Wayland, the Gnome Desktop does not recognize mouse clicks and drags after several tens of minutes after launching. However, it does recognize the movement of the mouse cursor. [How To Reploduce] 1. login in a Gnome session. 2. launch some applications. 3. use it for a few dozen minutes. 4. attempt to click and drag with a mouse or other pointing device. [Actual Result] I can no longer select mouse click application windows, activity buttons, dashes, etc. [Expect Result] I will accept mouse clicks until the end of the session, and possibly hope that the event is executed when the click is made. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-release-upgrader-core 1:20.10.13 ProcVersionSignature: Ubuntu 5.8.0-28.30-lowlatency 5.8.14 Uname: Linux 5.8.0-28-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Wed Nov 18 13:29:28 2020 InstallationDate: Installed on 2018-05-20 (913 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ja_JP.UTF-8 SHELL=/usr/bin/fish RebootRequiredPkgs: gnome-shell linux-image-5.8.0-29-lowlatency linux-base linux-image-5.8.0-29-generic linux-base SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to groovy on 2020-10-25 (23 days ago) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 126: Error executing command as another user: Request dismissed VarLogDistupgradeApttermlog: Error: [Errno 13] 許可がありません: '/var/log/dist-upgrade/apt-term.log' VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1904671/+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 1904671] Re: After a certain amount of time after the session is launched, mouse clicks are no longer accepted
It sounds like gnome-shell is frozen/crashed and Xorg is still running. Please: 1. Remove any gnome-shell extensions you may have installed and log out and in again. 2. If the problem still happens, check the Extensions app and disable all extensions. Then log out and in again. 3. If the problem still happens, please follow these steps: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1904671 Title: After a certain amount of time after the session is launched, mouse clicks are no longer accepted Status in gnome-shell package in Ubuntu: Incomplete Bug description: X11, Wayland, the Gnome Desktop does not recognize mouse clicks and drags after several tens of minutes after launching. However, it does recognize the movement of the mouse cursor. [How To Reploduce] 1. login in a Gnome session. 2. launch some applications. 3. use it for a few dozen minutes. 4. attempt to click and drag with a mouse or other pointing device. [Actual Result] I can no longer select mouse click application windows, activity buttons, dashes, etc. [Expect Result] I will accept mouse clicks until the end of the session, and possibly hope that the event is executed when the click is made. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-release-upgrader-core 1:20.10.13 ProcVersionSignature: Ubuntu 5.8.0-28.30-lowlatency 5.8.14 Uname: Linux 5.8.0-28-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Wed Nov 18 13:29:28 2020 InstallationDate: Installed on 2018-05-20 (913 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ja_JP.UTF-8 SHELL=/usr/bin/fish RebootRequiredPkgs: gnome-shell linux-image-5.8.0-29-lowlatency linux-base linux-image-5.8.0-29-generic linux-base SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to groovy on 2020-10-25 (23 days ago) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 126: Error executing command as another user: Request dismissed VarLogDistupgradeApttermlog: Error: [Errno 13] 許可がありません: '/var/log/dist-upgrade/apt-term.log' VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1904671/+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 1905655] [NEW] PulseAudio release 14.0
Public bug reported: PulseAudio release 14.0 is now out. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: focal groovy hirsute ** Tags added: focal hirsute ** Tags added: groovy -- 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/1905655 Title: PulseAudio release 14.0 Status in pulseaudio package in Ubuntu: New Bug description: PulseAudio release 14.0 is now out. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1905655/+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 1900404] Re: pulseaudio[2032]: No UCM verb is valid for hw:0
This also happens on 20.04.1 LTS. Please fix it there also. May be same as https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1056 ** Bug watch added: gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues #1056 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1056 -- 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/1900404 Title: pulseaudio[2032]: No UCM verb is valid for hw:0 Status in pulseaudio package in Ubuntu: Fix Released Bug description: pulseaudio[2032]: No UCM verb is valid for hw:1 pulseaudio[2032]: No UCM verb is valid for hw:0 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-23.24-generic 5.8.14 Uname: Linux 5.8.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: navycat2032 F pulseaudio /dev/snd/controlC0: navycat2032 F pulseaudio /dev/snd/pcmC0D0p: navycat2032 F...m pulseaudio /dev/snd/controlC1: navycat2032 F pulseaudio CasperMD5CheckResult: skip Date: Mon Oct 19 11:57:52 2020 InstallationDate: Installed on 2020-10-07 (11 days ago) InstallationMedia: Ubuntu-MATE 20.10 "Groovy Gorilla" - Beta amd64 (20201007) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2018 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 150-SE-E789 dmi.board.vendor: EVGA dmi.board.version: Patsburg dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/09/2018:br4.6:svnBASE_BOARD_MANUFACTURER:pnMODEL_NAME:pvrBASE_BOARD_VERSION:rvnEVGA:rn150-SE-E789:rvrPatsburg: dmi.product.family: X86 AT dmi.product.name: MODEL_NAME dmi.product.sku: PROJECT_SUB_TAG dmi.product.version: BASE_BOARD_VERSION dmi.sys.vendor: BASE_BOARD_MANUFACTURER To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1900404/+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 1900404] Re: pulseaudio[2032]: No UCM verb is valid for hw:0
We can't consider a fix unless someone can identify what package, or specifically what change, actually fixed it. -- 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/1900404 Title: pulseaudio[2032]: No UCM verb is valid for hw:0 Status in pulseaudio package in Ubuntu: Fix Released Bug description: pulseaudio[2032]: No UCM verb is valid for hw:1 pulseaudio[2032]: No UCM verb is valid for hw:0 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-23.24-generic 5.8.14 Uname: Linux 5.8.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: navycat2032 F pulseaudio /dev/snd/controlC0: navycat2032 F pulseaudio /dev/snd/pcmC0D0p: navycat2032 F...m pulseaudio /dev/snd/controlC1: navycat2032 F pulseaudio CasperMD5CheckResult: skip Date: Mon Oct 19 11:57:52 2020 InstallationDate: Installed on 2020-10-07 (11 days ago) InstallationMedia: Ubuntu-MATE 20.10 "Groovy Gorilla" - Beta amd64 (20201007) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2018 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 150-SE-E789 dmi.board.vendor: EVGA dmi.board.version: Patsburg dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/09/2018:br4.6:svnBASE_BOARD_MANUFACTURER:pnMODEL_NAME:pvrBASE_BOARD_VERSION:rvnEVGA:rn150-SE-E789:rvrPatsburg: dmi.product.family: X86 AT dmi.product.name: MODEL_NAME dmi.product.sku: PROJECT_SUB_TAG dmi.product.version: BASE_BOARD_VERSION dmi.sys.vendor: BASE_BOARD_MANUFACTURER To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1900404/+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 1905576] Re: I cannot drag icons above to a particular region of my desktop
This is a bug in nautilus-desktop. Unfortunately nautilus-desktop is no longer shipped and no longer supported in newer versions so this is unlikely to ever be fixed. ** Package changed: xorg (Ubuntu) => nautilus (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/1905576 Title: I cannot drag icons above to a particular region of my desktop Status in nautilus package in Ubuntu: New Bug description: I have two monitors set up, and one is vertical. Here is a video: https://cdn.discordapp.com/attachments/653633559206166541/781166447174352936/20201121_133143_1_1.mp4 1. Ubuntu 18.04.5 LTS 2. Not sure what package this is 3. I expected the icon to go where I dragged it 4. The x-axis position was the same, but the y-axis position always gets set to a certain height whenever I drag above that height (I think this has to do with the top of my other display). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.4.0-54.60~18.04.1-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .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 450.80.02 Wed Sep 23 01:13:39 UTC 2020 GCC version: gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04) ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Nov 25 09:20:33 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 450.80.02, 5.4.0-53-generic, x86_64: installed nvidia, 450.80.02, 5.4.0-54-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation Device [10de:1e81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8738] InstallationDate: Installed on 2020-10-12 (44 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) MachineType: Micro-Star International Co., Ltd. MS-7B12 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-54-generic root=UUID=321ae9a5-66cd-481d-b940-0f3c32a130c4 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.71 dmi.board.asset.tag: Default string dmi.board.name: MEG Z390 ACE (MS-7B12) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.71:bd10/30/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B12:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMEGZ390ACE(MS-7B12):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7B12 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1905576/+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 1905555] Re: Xserver crash at start , black screen , 20.04 , Intel HD620
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/190 Title: Xserver crash at start , black screen , 20.04 , Intel HD620 Status in xorg-server package in Ubuntu: Incomplete Bug description: Xserver crash at start , black screen , 20.04 , Intel HD630 Just happened since yesterday updates ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Wed Nov 25 12:48:16 2020 DistUpgraded: 2020-09-19 18:32:29,160 DEBUG pid is: 29157 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer UHD Graphics 620 (Whiskey Lake) [1558:1325] InstallationDate: Installed on 2019-03-04 (632 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b685 Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 002: ID 06cb:00a8 Synaptics, Inc. Bus 001 Device 004: ID 8087:0025 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N150ZU ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic root=UUID=5b433ea6-7902-4568-9ee0-36a15ff2f274 ro quiet splash i8042.reset vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-09-19 (66 days ago) dmi.bios.date: 10/19/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.01 dmi.board.asset.tag: Tag 12345 dmi.board.name: N150ZU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.01:bd10/19/2018:svnNotebook:pnN150ZU:pvrNotApplicable:rvnNotebook:rnN150ZU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N150ZU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook 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.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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/190/+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 1905648] [NEW] fractional display scale cannot work properly
You have been subscribed to a public bug: When I switch on fractional scaling, and choose 125%/150%/175%, everything gets very large. The screen can only display part of the whole desktop. It is even larger than the 200%-scale. P.S. As I remember, the fractional scaling works well in May. But after a update in May (forgot the exact date), fractional scaling cannot work properly anymore. After that update, I can just use 200% scale setting. I'm so sorry to report this bug so late. Also, I tested both with only the builtin screen and with an external monitor in 'Join Display' mode. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:02: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 450.80.02 Wed Sep 23 01:13:39 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Nov 26 09:54:20 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 450.80.02, 5.4.0-53-generic, x86_64: installed nvidia, 450.80.02, 5.4.0-54-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Huawei Technologies Co., Ltd. UHD Graphics 620 (Whiskey Lake) [19e5:3e0c] Subsystem: Huawei Technologies Co., Ltd. GP108M [GeForce MX250] [19e5:3e0c] InstallationDate: Installed on 2020-05-02 (207 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 003: ID 13d3:56db IMC Networks ov9734_azurewave_camera Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HUAWEI HBL-WX9 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic root=UUID=b1d9a025-3f1d-4fad-844f-c4e836944847 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2019 dmi.bios.vendor: HUAWEI dmi.bios.version: 1.09 dmi.board.asset.tag: NULL dmi.board.name: HBL-WX9-PCB dmi.board.vendor: HUAWEI dmi.board.version: M1130 dmi.chassis.asset.tag: NULL dmi.chassis.type: 10 dmi.chassis.vendor: HUAWEI dmi.chassis.version: M1130 dmi.modalias: dmi:bvnHUAWEI:bvr1.09:bd08/12/2019:svnHUAWEI:pnHBL-WX9:pvrM1130:rvnHUAWEI:rnHBL-WX9-PCB:rvrM1130:cvnHUAWEI:ct10:cvrM1130: dmi.product.family: MagicBook dmi.product.name: HBL-WX9 dmi.product.sku: C233 dmi.product.version: M1130 dmi.sys.vendor: HUAWEI 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 N/A 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 resolution ubuntu -- fractional display scale cannot work properly https://bugs.launchpad.net/bugs/1905648 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 1905648] Re: fractional display scale cannot work properly
** 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/1905648 Title: [nvidia] fractional display scale cannot work properly Status in mutter package in Ubuntu: Incomplete Bug description: When I switch on fractional scaling, and choose 125%/150%/175%, everything gets very large. The screen can only display part of the whole desktop. It is even larger than the 200%-scale. P.S. As I remember, the fractional scaling works well in May. But after a update in May (forgot the exact date), fractional scaling cannot work properly anymore. After that update, I can just use 200% scale setting. I'm so sorry to report this bug so late. Also, I tested both with only the builtin screen and with an external monitor in 'Join Display' mode. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:02: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 450.80.02 Wed Sep 23 01:13:39 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Nov 26 09:54:20 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 450.80.02, 5.4.0-53-generic, x86_64: installed nvidia, 450.80.02, 5.4.0-54-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Huawei Technologies Co., Ltd. UHD Graphics 620 (Whiskey Lake) [19e5:3e0c] Subsystem: Huawei Technologies Co., Ltd. GP108M [GeForce MX250] [19e5:3e0c] InstallationDate: Installed on 2020-05-02 (207 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 003: ID 13d3:56db IMC Networks ov9734_azurewave_camera Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HUAWEI HBL-WX9 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic root=UUID=b1d9a025-3f1d-4fad-844f-c4e836944847 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2019 dmi.bios.vendor: HUAWEI dmi.bios.version: 1.09 dmi.board.asset.tag: NULL dmi.board.name: HBL-WX9-PCB dmi.board.vendor: HUAWEI dmi.board.version: M1130 dmi.chassis.asset.tag: NULL dmi.chassis.type: 10 dmi.chassis.vendor: HUAWEI dmi.chassis.version: M1130 dmi.modalias: dmi:bvnHUAWEI:bvr1.09:bd08/12/2019:svnHUAWEI:pnHBL-WX9:pvrM1130:rvnHUAWEI:rnHBL-WX9-PCB:rvrM1130:cvnHUAWEI:ct10:cvrM1130: dmi.product.family: MagicBook dmi.product.name: HBL-WX9 dmi.product.sku: C233 dmi.product.version: M1130 dmi.sys.vendor: HUAWEI 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 N/A 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1905648/+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 1905648] Re: fractional display scale cannot work properly
Please reproduce the problem again, and while it is happening run this command in a terminal: xrandr --verbose > xrandr2.txt and attach the resulting text file. ** Tags added: nvidia regression-update xrandr-scaling ** Summary changed: - fractional display scale cannot work properly + [nvidia] fractional display scale cannot work properly ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** Changed in: mutter (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1905648 Title: [nvidia] fractional display scale cannot work properly Status in mutter package in Ubuntu: Incomplete Bug description: When I switch on fractional scaling, and choose 125%/150%/175%, everything gets very large. The screen can only display part of the whole desktop. It is even larger than the 200%-scale. P.S. As I remember, the fractional scaling works well in May. But after a update in May (forgot the exact date), fractional scaling cannot work properly anymore. After that update, I can just use 200% scale setting. I'm so sorry to report this bug so late. Also, I tested both with only the builtin screen and with an external monitor in 'Join Display' mode. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:02: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 450.80.02 Wed Sep 23 01:13:39 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Nov 26 09:54:20 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 450.80.02, 5.4.0-53-generic, x86_64: installed nvidia, 450.80.02, 5.4.0-54-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Huawei Technologies Co., Ltd. UHD Graphics 620 (Whiskey Lake) [19e5:3e0c] Subsystem: Huawei Technologies Co., Ltd. GP108M [GeForce MX250] [19e5:3e0c] InstallationDate: Installed on 2020-05-02 (207 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 003: ID 13d3:56db IMC Networks ov9734_azurewave_camera Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HUAWEI HBL-WX9 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic root=UUID=b1d9a025-3f1d-4fad-844f-c4e836944847 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2019 dmi.bios.vendor: HUAWEI dmi.bios.version: 1.09 dmi.board.asset.tag: NULL dmi.board.name: HBL-WX9-PCB dmi.board.vendor: HUAWEI dmi.board.version: M1130 dmi.chassis.asset.tag: NULL dmi.chassis.type: 10 dmi.chassis.vendor: HUAWEI dmi.chassis.version: M1130 dmi.modalias: dmi:bvnHUAWEI:bvr1.09:bd08/12/2019:svnHUAWEI:pnHBL-WX9:pvrM1130:rvnHUAWEI:rnHBL-WX9-PCB:rvrM1130:cvnHUAWEI:ct10:cvrM1130: dmi.product.family: MagicBook dmi.product.name: HBL-WX9 dmi.product.sku: C233 dmi.product.version: M1130 dmi.sys.vendor: HUAWEI 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 N/A 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 To mana