[Touch-packages] [Bug 1873895] Re: Regression: block staircase display with side-by-side monitors of different pixel widths
Same issue with Ubuntu Mate HWE 20.04 with kernel 5.8 and latest AMD driver from oibaf PPA. $ inxi -SMG System:Host: ACER-xk2308 Kernel: 5.8.0-38-generic x86_64 bits: 64 Desktop: MATE 1.24.0 Distro: Ubuntu 20.04.1 LTS (Focal Fossa) Machine: Type: Desktop System: MSI product: MS-7798 v: 1.0 serial: Mobo: MSI model: B75MA-P45 (MS-7798) v: 1.0 serial: BIOS: American Megatrends v: 1.9 date: 09/30/2013 Graphics: Device-1: Advanced Micro Devices [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] driver: amdgpu v: kernel Display: x11 server: X.Org 1.20.9 driver: amdgpu,ati unloaded: fbdev,modesetting,radeon,vesa resolution: 1366x768~60Hz OpenGL: renderer: AMD Radeon RX 5600 XT (NAVI10 DRM 3.38.0 5.8.0-38-generic LLVM 11.0.1) v: 4.6 Mesa 21.1.0-devel (git-7b48d5d 2021-01-16 focal-oibaf-ppa) $ hwe-support-status --verbose Your Hardware Enablement Stack (HWE) is supported until avril 2025 Please, let me know what to do, for testing what you want. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxcb in Ubuntu. https://bugs.launchpad.net/bugs/1873895 Title: Regression: block staircase display with side-by-side monitors of different pixel widths Status in Linux: Unknown Status in libxcb package in Ubuntu: Confirmed Status in xfwm4 package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: Update based on further research. This only happens when the secondary external display is operating at a different pixel width to the internal. In this case eDP is 1920x1080 whereas the external HDMI-A-0 is natively 1680x1050. It is caused by xfwm4's recent switch from using glx to xpresent for AMD GPUs. The underlying bug is in the AMD driver. I was able to reproduce on an external 1920x1200 display only when it was set to a non-native 1680x1050 resolution. --- Two identical Lenovo E495 laptops with 20.04 installed. The problem occurred initially on the laptop that is having package upgrades applied regularly. With dual monitors and the external monitor placed left or right the display has a blocked staircase effect shown in the attached photograph, and seems related to https://gitlab.freedesktop.org/xorg/driver/xf86-video- amdgpu/-/issues/10 More detailed investigation suggests it only happens when the X coordinate of the two monitors is different. The symptom looks like an off-by-one error because it appears as if the display is divided into, say, 10 rows and 15 columns but the first row has 16 'columns' worth of blocks on it and so wraps to the beginning of the 2nd row, and so on. On the laptop without package upgrades being applied this didn't happen. So I upgraded it (314 packages) and restarted and it too sees the same problem. I suspected libxcomposite1 and downgraded it to 1:0.4.5-0ubuntu1 but that didn't solve it. I now suspect libxcb but so far haven't been able to prove it. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkPad E595 [17aa:5124] InstallationDate: Installed on 2020-04-08 (11 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408) MachineType: LENOVO 20NECTO1WW Package: xserver-xorg-video-amdgpu 19.1.0-1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/ELLOE000-rootfs ro acpi_osi=! "acpi_osi=Windows 2016" quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Tags: focal ubuntu ubuntu Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sudo users _MarkForUpload: True dmi.bios.date: 12/23/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R11ET32W (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NECTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR11ET32W(1.12):bd12/23/2019:svnLENOVO:pn20NECTO1WW:pvrThinkPadE495:rvnLENOVO:rn20NECTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E495 dmi.product.name: 20NECTO1WW dmi.product.sku: LENOVO_MT_20NE_BU_Think_FM_ThinkPad E495 dmi.product.version:
[Touch-packages] [Bug 1875944] Re: Lenovo Ideapad 130-15AST 20.04 distorted and unusable
*** This bug is a duplicate of bug 1873895 *** https://bugs.launchpad.net/bugs/1873895 Same issue with Ubuntu Mate HWE 20.04 with kernel 5.8 and latest AMD driver from oibaf PPA. $ inxi -SMG System:Host: ACER-xk2308 Kernel: 5.8.0-38-generic x86_64 bits: 64 Desktop: MATE 1.24.0 Distro: Ubuntu 20.04.1 LTS (Focal Fossa) Machine: Type: Desktop System: MSI product: MS-7798 v: 1.0 serial: Mobo: MSI model: B75MA-P45 (MS-7798) v: 1.0 serial: BIOS: American Megatrends v: 1.9 date: 09/30/2013 Graphics: Device-1: Advanced Micro Devices [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] driver: amdgpu v: kernel Display: x11 server: X.Org 1.20.9 driver: amdgpu,ati unloaded: fbdev,modesetting,radeon,vesa resolution: 1366x768~60Hz OpenGL: renderer: AMD Radeon RX 5600 XT (NAVI10 DRM 3.38.0 5.8.0-38-generic LLVM 11.0.1) v: 4.6 Mesa 21.1.0-devel (git-7b48d5d 2021-01-16 focal-oibaf-ppa) $ hwe-support-status --verbose Your Hardware Enablement Stack (HWE) is supported until avril 2025 Please, let me know what to do, for testing what you want. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1875944 Title: Lenovo Ideapad 130-15AST 20.04 distorted and unusable Status in Ubuntu MATE: Confirmed Status in libdrm package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Output of lshw here: https://pastebin.com/NMBigV4G Screenshot of the desktop here in the community forum: https://ubuntu-mate.community/t/lenovo-ideapad-20-04-upgrade-distorted-and-unusable/21617 I'm not all that experienced at filing bug reports here so I have included the attachment of the photo found at the forum link. The picture in the community forum link is what the MATE 20.04 live USB boots to. I first upgraded from 18.04 using do-release-upgrade. The result looked like the photo as well. Then I reinstalled 18.04, upgraded to 19.10, which looked and performed normally. I then upgraded the 19.10 install to 20.04 with the same result as the photo. I also tried with a different flash drive just to rule that out. Then I made the live USB of the 20.04 image and booted it to what you see in the forum post. I made a live USB of both Stock Ubuntu and Kubuntu 20.04 and both worked just fine. Until I tried the other two flavors I was thinking it was system specific, but after they worked normally it seems to be a MATE specific issue with this system. It appears to be only a display problem. The DE is completely unusable with the mouse, but I can launch a terminal and run commands, although the terminal is just as distorted as the photo above, so you can't see what you are typing or the resulting output. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: clay 1524 F pulseaudio /dev/snd/controlC0: clay 1524 F pulseaudio BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: MATE DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu DkmsStatus: rtl8821ce, v5.5.2_34066.20200325, 5.3.0-46-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98e4] (rev ea) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:39f5] InstallationDate: Installed on 2020-04-27 (11 days ago) InstallationMedia: Ubuntu-MATE 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: LENOVO 81H5 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic root=UUID=bec09cbc-83af-49f6-8aeb-f02059977f4a ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-46-generic N/A linux-backports-modules-5.3.0-46-generic N/A linux-firmware1.173.17 Tags: bionic ubuntu Uname: Linux 5.3.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/27/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 8ZCN15WW(V1.04) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 130-15AST dmi.modalias:
[Touch-packages] [Bug 1903484] Re: package python-six 1.14.0-2 failed to install/upgrade: installed python-six package post-installation script subprocess returned error exit status 127
[Expired for six (Ubuntu) because there has been no activity for 60 days.] ** Changed in: six (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to six in Ubuntu. https://bugs.launchpad.net/bugs/1903484 Title: package python-six 1.14.0-2 failed to install/upgrade: installed python-six package post-installation script subprocess returned error exit status 127 Status in six package in Ubuntu: Expired Bug description: Plz fix this bug ProblemType: Package DistroRelease: Ubuntu 20.04 Package: python-six 1.14.0-2 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Nov 5 21:00:52 2020 Dependencies: DuplicateSignature: package:python-six:1.14.0-2 Setting up python-six (1.14.0-2) ... /var/lib/dpkg/info/python-six.postinst: 6: pycompile: not found dpkg: error processing package python-six (--configure): installed python-six package post-installation script subprocess returned error exit status 127 ErrorMessage: installed python-six package post-installation script subprocess returned error exit status 127 InstallationDate: Installed on 2020-10-22 (17 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: six Title: package python-six 1.14.0-2 failed to install/upgrade: installed python-six package post-installation script subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/six/+bug/1903484/+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 1912083] [NEW] the icons are longer
Public bug reported: the icons are longer than they should be ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 BootLog: Error: [Errno 13] 拒絕不符權限的操作: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jan 17 11:12:46 2021 DistUpgraded: 2021-01-17 10:47:32,279 DEBUG openCache() DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.8.0-36-generic, x86_64: installed virtualbox, 6.1.16, 5.8.0-38-generic, x86_64: installed GraphicsCard: Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics [103c:86cd] ImageMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:56c9 IMC Networks HP TrueVision HD Camera Bus 001 Device 002: ID 145f:021f Trust 2.4G Mouse Bus 001 Device 004: ID 8087:0026 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP 348 G7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=aea93e03-8fb8-49c7-8081-a18a438e7864 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to groovy on 2021-01-17 (0 days ago) dmi.bios.date: 06/11/2020 dmi.bios.release: 15.21 dmi.bios.vendor: Insyde dmi.bios.version: F.21 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 86CD dmi.board.vendor: HP dmi.board.version: 98.08 dmi.chassis.asset.tag: 5CG0351KMK dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 98.8 dmi.modalias: dmi:bvnInsyde:bvrF.21:bd06/11/2020:br15.21:efr98.8:svnHP:pnHP348G7:pvrType1ProductConfigId:rvnHP:rn86CD:rvr98.08:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5336AN HP Notebook dmi.product.name: HP 348 G7 dmi.product.sku: 7HC08AV dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy third-party-packages ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1912083 Title: the icons are longer Status in xorg package in Ubuntu: New Bug description: the icons are longer than they should be ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 BootLog: Error: [Errno 13] 拒絕不符權限的操作: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jan 17 11:12:46 2021 DistUpgraded: 2021-01-17 10:47:32,279 DEBUG openCache() DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.8.0-36-generic, x86_64: installed virtualbox, 6.1.16, 5.8.0-38-generic, x86_64: installed GraphicsCard: Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics [103c:86cd] ImageMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:56c9 IMC Networks HP TrueVision HD Camera Bus 001 Device 002: ID 145f:021f Trust 2.4G Mouse Bus 001 Device 004: ID 8087:0026 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP 348 G7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=aea93e03-8fb8-49c7-8081-a18a438e7864 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to groovy on 2021-01-17 (0 days ago) dmi.bios.date: 06/11/2020 dmi.bios.release: 15.21 dmi.bios.vendor: Insyde dmi.bios.version: F.21 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 86CD dmi.board.vendor: HP dmi.board.version: 98.08 dmi.chassis.asset.tag: 5CG0351KMK dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version
[Touch-packages] [Bug 1891479] Re: pycurl ftbfs in focal (missing python-sphinx)
The builds in proposed succeeded https://launchpad.net/ubuntu/+source/pycurl/7.43.0.2-1ubuntu6 ** Tags removed: removal-candidate verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pycurl in Ubuntu. https://bugs.launchpad.net/bugs/1891479 Title: pycurl ftbfs in focal (missing python-sphinx) Status in pycurl package in Ubuntu: Fix Released Status in pycurl source package in Focal: Fix Committed Bug description: [SRU Justification] This package is unbuildable due to unsatisfiable build-dependencies, as seen in a focal test rebuild: https://launchpad.net/ubuntu/+archive/test-rebuild-20200810-focal/+build/19799602 Missing build dependencies: python-sphinx This makes the package unsupportable in the event a security update needs to be applied. [Test case] 1. let the package attempt to build in focal 2. check if it succeeds. [Regression potential] Because the missing build-dependency is python-sphinx, which is only used for building the package documentation, the risk of regression is confined to a misbuild of the documentation. Regardless, this package will be held in -proposed because the runtime impact of a FTBFS is non-existent. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pycurl/+bug/1891479/+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 1891479] Re: pycurl ftbfs in focal (wait-deps)
Already fix in Groovy and later. --- pycurl (7.43.0.2-3) unstable; urgency=medium * Drop python2 support; Closes: #937415 * debian/control - annotate flaky as nocheck, patch by Helmut Grohne; Closes: #929194 -- Sandro Tosi Wed, 01 Apr 2020 23:22:15 -0400 ** Changed in: pycurl (Ubuntu) Status: Confirmed => Fix Released ** Summary changed: - pycurl ftbfs in focal (wait-deps) + pycurl ftbfs in focal (missing python-sphinx) ** Tags removed: verification-needed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pycurl in Ubuntu. https://bugs.launchpad.net/bugs/1891479 Title: pycurl ftbfs in focal (missing python-sphinx) Status in pycurl package in Ubuntu: Fix Released Status in pycurl source package in Focal: Fix Committed Bug description: [SRU Justification] This package is unbuildable due to unsatisfiable build-dependencies, as seen in a focal test rebuild: https://launchpad.net/ubuntu/+archive/test-rebuild-20200810-focal/+build/19799602 Missing build dependencies: python-sphinx This makes the package unsupportable in the event a security update needs to be applied. [Test case] 1. let the package attempt to build in focal 2. check if it succeeds. [Regression potential] Because the missing build-dependency is python-sphinx, which is only used for building the package documentation, the risk of regression is confined to a misbuild of the documentation. Regardless, this package will be held in -proposed because the runtime impact of a FTBFS is non-existent. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pycurl/+bug/1891479/+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 1891479] Re: pycurl ftbfs in focal (wait-deps)
** Changed in: pycurl (Ubuntu Focal) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pycurl in Ubuntu. https://bugs.launchpad.net/bugs/1891479 Title: pycurl ftbfs in focal (wait-deps) Status in pycurl package in Ubuntu: Fix Released Status in pycurl source package in Focal: Fix Committed Bug description: [SRU Justification] This package is unbuildable due to unsatisfiable build-dependencies, as seen in a focal test rebuild: https://launchpad.net/ubuntu/+archive/test-rebuild-20200810-focal/+build/19799602 Missing build dependencies: python-sphinx This makes the package unsupportable in the event a security update needs to be applied. [Test case] 1. let the package attempt to build in focal 2. check if it succeeds. [Regression potential] Because the missing build-dependency is python-sphinx, which is only used for building the package documentation, the risk of regression is confined to a misbuild of the documentation. Regardless, this package will be held in -proposed because the runtime impact of a FTBFS is non-existent. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pycurl/+bug/1891479/+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 1840375] Re: groupdel doesn't support extrausers
** Tags removed: verification-needed verification-needed-disco
** Changed in: shadow (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: shadow (Ubuntu Xenial)
Importance: Undecided => Wishlist
** Changed in: shadow (Ubuntu Bionic)
Importance: Undecided => Wishlist
** Changed in: shadow (Ubuntu Disco)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shadow in Ubuntu.
https://bugs.launchpad.net/bugs/1840375
Title:
groupdel doesn't support extrausers
Status in snapd:
Triaged
Status in shadow package in Ubuntu:
Fix Released
Status in shadow source package in Xenial:
Fix Committed
Status in shadow source package in Bionic:
Fix Committed
Status in shadow source package in Disco:
Won't Fix
Bug description:
snapd needs the ability to call 'groupdel --extrausers foo' to clean
up after itself, but --extrausers is currently unsupported.
[Impact]
On ubuntu-core systems we want to be able to manage "extrausers" in the same
way as regular users. This requires updates to the various
{user,group}{add,del} tools. Right now "groupdel" cannot handle extrausers.
This is an important feature for Ubuntu Core
[Test Case]
0. upgrade the "passwd" to the version in {xenial,bionic}-proposed
1. install the libnss-extrausers and add "extrauers" to the passwd and shadow
line (see /usr/share/doc/libnss-extrausers/README for the modifications in
sswitch.conf)
2. run "groupadd --extrausers foo" and verify "grep foo
/var/lib/extrausers/group"
3 check /var/lib/extrausers/group for the new "foo" group
4. run "groupdel --extrausers foo"
5. check /var/lib/extrausers/group and ensure the "foo" group is removed
[Regression Potential]
* low: this adds a new (optional) option which is off by default
To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1840375/+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 1906701] Re: Please merge logrotate 3.17.0-1 (main) from Debian unstable (main)
logrotate (3.17.0-1ubuntu1) hirsute; urgency=medium * Merge from Debian unstable. Remaining changes: - debian/control: Drop mailx to Suggests for Ubuntu; it's only used on request, and we don't configure an MTA by default. - debian/logrotate.conf: use group 'syslog' by default when rotating logs. * Dropped changes, included upstream: - Chery-pick upstream patch to fix FTBFS with GCC 10 logrotate (3.17.0-1) unstable; urgency=medium * New upstream version 3.17.0 (Closes: #945097, #966016) * debian: - bump to debhelper compat level 13 - wrap-and-sort * d/rules: - drop custom cleanup * d/patches: - rebase and drop applied ones - drop patch disabling test 70 - move debian specific patch to subdir - cherry-pick upstream commits: + use getenv() on macOS and BSD + logrotate.service: harden with ProtectHostname + tests: always run logrotate in verbose mode + test-0070: set log modification time to current date + make `delaycompress` not to fail with `rotate 0` * d/logrotate.preinst: drop ancient maintainer script about old state file paths * d/control: add acl package to build-dependencies to run ACL unit tests on Linux * d/copyright: update years logrotate (3.16.0-3) unstable; urgency=medium * d/patches: cherry-pick upstream switch-user fixes - When using configuration directive su, accept staying as user root. In particular restore mailman's usage of 'su root list'. - Reset user/group when error returning early in rotateLogSet(). logrotate (3.16.0-2) unstable; urgency=medium * d/patches: - add upstream commit to silence unused parameter warning in acl disabled build Should fix FTBFS on architectures without acl - add upstream commit to enable systemd hardening option ProtectClock logrotate (3.16.0-1) unstable; urgency=medium [ Debian Janitor ] * Drop no longer supported add-log-mailing-address setting from debian/changelog. * Add missing colon in closes line. * Remove obsolete fields Name from debian/upstream/metadata. [ Christian Göttsche ] * New upstream version 3.16.0 (Closes: #915301) * d/patches: rebase and drop upstream applied ones - add new directive ProtectKernelLogs - drop NoNewPrivileges, which is actually not implied and might be needed for third party rotate scripts * d/copyright: add extra sections - add section for queue.h licensed under BSD-3-Clause - add section for build-aux/git-version-gen licensed under GPL-3+ * d/control: bump to std version 4.5.0 (no further changes) * d/rules: fail on compiler warnings logrotate (3.15.1-2) unstable; urgency=medium * d/control: drop postgresql-common break * d/copyright: update for 2019 * d/salsa-ci.yml: add standard salsa-ci configuration * d/tests: add additional small test script * d/patches: add testsuite patches to pass reprotest on salsa-ci * d/patches: tighten systemd service hardening * d/control: bump to std version 4.4.1 (no further changes) * d/source/lintian-overrides: ignore package-does-not-install-examples logrotate (3.15.1-1) unstable; urgency=medium [ Ondřej Nový ] * d/changelog: Remove trailing whitespaces [ Christian Göttsche ] * New upstream version 3.15.1 * d/patches: rebase and drop upstream applied ones * d/patches: add spelling fix * d/control: bump to std version 4.4.0 (no further changes) * debian: Switch to debhelper compat level 12 (no further changes) -- Balint Reczey Mon, 26 Oct 2020 18:24:33 +0100 ** Changed in: logrotate (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1906701 Title: Please merge logrotate 3.17.0-1 (main) from Debian unstable (main) Status in logrotate package in Ubuntu: Fix Released Bug description: Please merge logrotate 3.17.0-1 (main) from Debian unstable (main) At the time of filling this bug, the target debian unstable version is 3.17.0-2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1906701/+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 1879927] Re: Please merge wpa 2:2.9.0-13 (main) from Debian unstable (main)
** Summary changed: - Merge wpa 2:2.9.0-13 (main) from Debian unstable (main) + Please merge wpa 2:2.9.0-13 (main) from Debian unstable (main) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1879927 Title: Please merge wpa 2:2.9.0-13 (main) from Debian unstable (main) Status in wpa package in Ubuntu: New Bug description: Please merge wpa 2:2.9.0-13 (main) from Debian unstable (main) The Debian package carries some upstream cherry-picks that are nice to have in Ubuntu, plus the packaging updates. Sorry, I can't work on this merge myself. These Ubuntu changes can be dropped because they are already in Debian: * debian/patches/git_realtek_macrand.patch: - backport an upstream patch to fix issues with some realtek cards when MAC address randomization is enabled (lp: #1867908) * SECURITY UPDATE: Incorrect indication of disconnection in certain situations - debian/patches/CVE-2019-16275.patch: silently ignore management frame from unexpected source address in src/ap/drv_callbacks.c, src/ap/ieee882_11.c. - CVE-2019-16275 Remaining changes specific to Ubuntu: * debian/patches/wpa_service_ignore-on-isolate.patch: add IgnoreOnIsolate=yes so that when switching "runlevels" in oem-config will not kill off wpa and cause wireless to be unavailable on first boot. * debian/patches/session-ticket.patch: disable the TLS Session Ticket extension to fix auth with 802.1x PEAP on some hardware. Changelog entries since current groovy version 2:2.9-1ubuntu7: wpa (2:2.9.0-13) unstable; urgency=medium * Apply upstream patches: - Avoid sending invalid mgmt frames at startup - Increase introspection buffer size for D-Bus -- Andrej Shadura Tue, 19 May 2020 14:29:29 +0200 wpa (2:2.9.0-12) unstable; urgency=medium * Add an upstream patch to fix the MAC randomisation issue with some cards (LP: #1867908). -- Andrej Shadura Tue, 24 Mar 2020 11:13:16 +0100 wpa (2:2.9.0-11) unstable; urgency=medium * Actually add autopkgtest for libwpa-client-dev and libwpa_test.c. -- Andrej Shadura Sat, 07 Mar 2020 13:18:19 +0100 wpa (2:2.9.0-10) unstable; urgency=medium * Rename the package with the client library to libwpa-client-dev. -- Andrej Shadura Tue, 25 Feb 2020 20:19:52 +0100 wpa (2:2.9.0-9) unstable; urgency=medium [ Terry Burton ] * Build and install eapol_test in eapoltest package (Closes: #700870) [ Didier Raboud ] * Backport upstream patch to fix build with Debian's VERSION_STR. [ Andrew Lee (李健秋) ] * Build libwpa-dev binary package which contains a static libwpa_client library and the wpa_ctrl header with an example program. [ Andrej Shadura ] * Add a patch to provide the BIT() macro locally in wpa_ctrl.h. * Patch the example to use stddef.h and wpa_ctrl.h from the global location. * Add an autopkgtest for libwpa-dev and libwpa_test.c. -- Andrej Shadura Tue, 25 Feb 2020 18:21:35 +0100 wpa (2:2.9.0-8) unstable; urgency=medium * Reupload as 2.9.0 to undo an accidental experimental upload to unstable. -- Andrej Shadura Sat, 22 Feb 2020 11:25:29 +0300 wpa (2:2.9-7) unstable; urgency=medium * Apply upstream patches: - trace: handle binutils bfd.h breakage - Check for FT support when selecting FT suites (Closes: #942164) -- Andrej Shadura Sat, 15 Feb 2020 16:42:04 +0100 wpa (2:2.9-6) unstable; urgency=medium [ Debian Janitor ] * Use secure URI in Homepage field. * Move source package lintian overrides to debian/source. * Use canonical URL in Vcs-Browser. * Rely on pre-initialized dpkg-architecture variables. * Update standards version to 4.4.1, no changes needed. [ Andrej Shadura ] * Disable CONFIG_DRIVER_MACSEC_QCA on kfreebsd. -- Andrej Shadura Mon, 13 Jan 2020 16:28:58 +0100 wpa (2:2.9-5) unstable; urgency=medium * Fix erroneously inverted logic in postinst. -- Andrej Shadura Mon, 13 Jan 2020 10:48:26 +0100 wpa (2:2.9-4) unstable; urgency=medium [ Helmut Grohne ] * Fix FTCBFS: Don’t export CC=cc (Closes: #921998). [ Andrej Shadura ] * Don’t act in hostapd.postinst if we’re running in a chrootless root. * Apply an upstream patch: - wpa_supplicant: Do not try to detect PSK mismatch during PTK rekeying. -- Andrej Shadura Mon, 13 Jan 2020 10:37:10 +0100 wpa (2:2.9-3) unstable; urgency=medium * Add pkg.wpa.nogui and noudeb build profiles. -- Andrej Shadura Fri, 04 Oct 2019 11:47:15 +0200 wpa (2:2.9-2) unstable; urgency=medium * SECURITY UPDATE: - AP mode PMF disconnection protection bypass. More details: + https://w1.fi/security/2019-7/ Closes: #940080
[Touch-packages] [Bug 1639531] Re: GCC compiles programs to shared object instead of executable, preventing GUI file managers from executing programs
20.10 bug still not fixed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shared-mime-info in
Ubuntu.
https://bugs.launchpad.net/bugs/1639531
Title:
GCC compiles programs to shared object instead of executable,
preventing GUI file managers from executing programs
Status in gcc-defaults:
Unknown
Status in shared-mime-info:
Unknown
Status in shared-mime-info package in Ubuntu:
Triaged
Bug description:
Release of Ubuntu being used
Description:Ubuntu 16.10
Release:16.10
Version of the package being used
=
gcc:
Installed: 4:6.1.1-1ubuntu2
Candidate: 4:6.1.1-1ubuntu2
Version table:
*** 4:6.1.1-1ubuntu2 500
500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages
100 /var/lib/dpkg/status
What was expected
=
Programs compiled using `gcc -o program program.c` should be runnable
by double-clicking them from a GUI file manager.
Compiling a simple program (`void main() { }`) using Xubuntu 16.04's
current version of `gcc` (`gcc version 5.4.0 20160609 (Ubuntu
5.4.0-6ubuntu1~16.04.2)`) produces the following output from
`/usr/bin/file program`:
program: ELF 64-bit LSB executable, x86-64, version 1 (SYSV),
dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for
GNU/Linux 2.6.32, BuildID[sha1]=signature_here, not stripped
This is correct behavior, allowing the executables to run from
Nautilus and Thunar.
What happened instead
=
Programs compiled using `gcc -o program program.c` are not runnable by
double-clicking them from a GUI file manager, even though they are
runnable from the terminal.
Compiling a simple program (`void main() { }`) using the current
version of `gcc` (`6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12)`) produces
the following output from `/usr/bin/file program`:
program: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV),
dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for
GNU/Linux 2.6.32, BuildID[sha1]=signature_here, not stripped
The program is also identified as a "shared library" instead of an
"executable" in Thunar, causing it to not be runnable from the GUI.
Others are unable to run such programs from Nautilus.
To manage notifications about this bug go to:
https://bugs.launchpad.net/gcc-defaults/+bug/1639531/+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 1912069] [NEW] app-notification style class does not appear correctly
Public bug reported: app-notification style class show without transparency like in attachment. ** Affects: ubuntu-themes (Ubuntu) Importance: Undecided Status: New ** Tags: visual-quality ** Attachment added: "incorect.png" https://bugs.launchpad.net/bugs/1912069/+attachment/5453791/+files/incorect.png ** Tags added: visual-quality -- 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/1912069 Title: app-notification style class does not appear correctly Status in ubuntu-themes package in Ubuntu: New Bug description: app-notification style class show without transparency like in attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1912069/+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 1848330] Re: Installing auditd sometimes fails in post-inst
All regressions have been resolved after some retries.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to audit in Ubuntu.
https://bugs.launchpad.net/bugs/1848330
Title:
Installing auditd sometimes fails in post-inst
Status in audit package in Ubuntu:
Fix Released
Status in audit source package in Bionic:
Fix Committed
Status in audit package in Debian:
New
Bug description:
[Impact]
Sometimes, auditd will get stuck when starting up, causing systemd to
kill it after a while since it (systemd) never got the start
notification.
Upstream troubleshooted this to be caused by calling a syslog()
function inside a signal handler.
[Test Case]
There is no reliable test case to reproduce the bug, other than trying the
fixed packages on an affected system where the hang occurs more frequently.
Basically:
sudo systemctl stop auditd
sudo systemctl start auditd
should work reliably. Do not run that in a tight loop, however, as
that will trigger a it's-restarting-too-frequently failure.
[Where problems could occur]
- if auditd fails to start, then the first fallback is syslog, and if that is
not picking up the audit messages, the last resort is the kernel buffer, which
can fill up. In the case it fills up, audit logs will be lost.
- it's possible to configure the audit system to panic() the machine
if audit messages are lost or otherwise not able to be recorded
(auditctl -f 2; default is 1 which is printk())
- the update restarts auditd as expected. Misconfiguration on very
very busy systems could mean that audit logs would be lost during the
brief moment the service is restarted. If that's the case, this update
would just be one more way to trigger it, but not be the root cause of
the problem
- similarly, as is usual with updates that restart services, it's
possible than an incorrect configuration for auditd is present, but
was never loaded before. The restart will load the config, and will
fail in such a case.
- this update removes a logging statement that occurs during startup:
("dispatcher %d reaped", pid)
It's unlikely, but possible, that some monitoring software could be
looking for that message in the logs. It won't be there anymore after
this update.
[Other Info]
The patch is committed upstream and part of the 2.8.5 release, which is
present in Focal and later.
The real fix for this bug is just dropping the audit_msg() call in the signal
handler code. But the original reporter of the bug, who is also who came up
with the fix (see https://bugzilla.redhat.com/show_bug.cgi?id=1587995#c4)
stated that with the 3 changes in the patch the startup hang didn't happen to
him anymore. Since this bug is difficult to reproduce elsewhere (either you
have it, or you don't), I chose to keep the 3 changes instead of just the
removal of the audit_msg() call.
[Original Description]
This happens sometimes when installing auditd on Ubuntu 18.04.2, most
installations work successfully, though. Re-running the install also
fixes the issue, but the failure breaks our automation. The log from
the failure looks like this:
# apt install auditd
...
Setting up auditd (1:2.8.2-1ubuntu1) ...
Created symlink /etc/systemd/system/multi-user.target.wants/auditd.service →
/lib/systemd/system/auditd.service.
Job for auditd.service failed because a timeout was exceeded.
See "systemctl status auditd.service" and "journalctl -xe" for details.
invoke-rc.d: initscript auditd, action "start" failed.
● auditd.service - Security Auditing Service
Loaded: loaded (/lib/systemd/system/auditd.service; enabled; vendor
preset: enabled)
Active: failed (Result: timeout) since Tue 2019-09-17 18:43:06 UTC; 11ms
ago
Docs: man:auditd(8)
https://github.com/linux-audit/audit-documentation
Process: 9702 ExecStart=/sbin/auditd (code=killed, signal=KILL)
Sep 17 18:40:06 compute-node21 systemd[1]: Starting Security Auditing
Service...
Sep 17 18:40:06 compute-node21 auditd[9703]: Started dispatcher:
/sbin/audispd pid: 9705
Sep 17 18:40:06 compute-node21 audispd[9705]: No plugins found, exiting
Sep 17 18:41:36 compute-node21 systemd[1]: auditd.service: Start operation
timed out. Terminating.
Sep 17 18:43:06 compute-node21 systemd[1]: auditd.service: State
'stop-sigterm' timed out. Killing.
Sep 17 18:43:06 compute-node21 systemd[1]: auditd.service: Killing process
9702 (auditd) with signal SIGKILL.
Sep 17 18:43:06 compute-node21 systemd[1]: auditd.service: Killing process
9703 (auditd) with signal SIGKILL.
Sep 17 18:43:06 compute-node21 systemd[1]: auditd.service: Control process
exited, code=killed status=9
Sep 17 18:43:06 compute-node21 systemd[1]: auditd.service: Failed with result
'timeout'.
Sep 17 18:43:06 compute-node21 systemd[1]: Failed to start Security Auditing
Service.
dpkg: error processing package
[Touch-packages] [Bug 1912052] [NEW] external headset microphone not working on Ubuntu 20.10 (not even wired, cable headset)
Public bug reported: Recently, external microphone has stopped working while using classic wired audio combo jack headset. Basics: 1) Headset's microphone works fine both in MS Windows on the same machine and on older Xubuntu on another machine. 2) Internal laptop mic works normally. 3) Yes, I have mic unmuted in settings. I've followed whole step1 from this troubleshoot guide: https://help.ubuntu.com/community/SoundTroubleshootingProcedure Did not help. There are more information with screenshots here: https://askubuntu.com/questions/1305942/external-headset-microphone-not- working-on-ubuntu-20-10-not-even-wired-cable-h: ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crysman2301 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 16 13:31:13 2021 InstallationDate: Installed on 2020-06-19 (210 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-12-08 (38 days ago) dmi.bios.date: 07/17/2020 dmi.bios.release: 1.5 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.05 dmi.board.name: Caboom_IL dmi.board.vendor: IL dmi.board.version: V1.05 dmi.chassis.type: 31 dmi.chassis.vendor: Acer dmi.chassis.version: V1.05 dmi.ec.firmware.release: 1.2 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.05:bd07/17/2020:br1.5:efr1.2:svnAcer:pnSpinSP513-54N:pvrV1.05:rvnIL:rnCaboom_IL:rvrV1.05:cvnAcer:ct31:cvrV1.05: dmi.product.family: Spin 5 dmi.product.name: Spin SP513-54N dmi.product.sku: dmi.product.version: V1.05 dmi.sys.vendor: Acer ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy ** Description changed: Recently, external microphone has stopped working while using classic wired audio combo jack headset. Basics: 1) Headset's microphone works fine both in MS Windows on the same machine and on older Xubuntu on another machine. 2) Internal laptop mic works normally. 3) Yes, I have mic unmuted in settings. I've followed whole step1 from this troubleshoot guide: https://help.ubuntu.com/community/SoundTroubleshootingProcedure Did not help. - There are more informationhttps://askubuntu.com/questions/1305942 - /external-headset-microphone-not-working-on-ubuntu-20-10-not-even-wired- - cable-h with screenshot here: + There are more information with screenshots here: + https://askubuntu.com/questions/1305942/external-headset-microphone-not- + working-on-ubuntu-20-10-not-even-wired-cable-h: ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: crysman2301 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: crysman2301 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 16 13:31:13 2021 InstallationDate: Installed on 2020-06-19 (210 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-12-08 (38 days ago) dmi.bios.date: 07/17/2020 dmi.bios.release: 1.5 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.05 dmi.board.name: Caboom_IL dmi.board.vendor: IL dmi.board.version: V1.05 dmi.chassis.type: 31 dmi.chassis.vendor: Acer dmi.chassis.version: V1.05 dmi.ec.firmware.release: 1.2 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.05:bd07/17/2020:br1.5:efr1.2:svnAcer:pnSpinSP513-54N:pvrV1.05:rvnIL:rnCaboom_IL:rvrV1.05:cvnAcer:ct31:cvrV1.05: dmi.product.family: Spin 5 dmi.product.name: Spin SP513-54N dmi.product.sku: dmi.product.version: V1.05 dmi.sys.vendor: Acer -- 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/1912052 Title: external headset microphone not working on Ubuntu 20.10 (not even wired, cable headset) Status in pulseaudio package in Ubuntu: New Bug description: Recently, external microphone has stopped working while using classic wired audio combo jack headset. Basics: 1) Headset's microphone works fine both in MS Windows on the same machine and on older Xubuntu on another machine. 2) Internal laptop mic works normally. 3) Yes, I have mic unmuted in settings. I've followed whole step1 from this troubleshoot guide: https://help.ubuntu.com/community/SoundTroubleshootingProcedure
[Touch-packages] [Bug 1911133] Re: [Regression] RS482M [Mobility Radeon Xpress 200]
I can also confirm issues with the same graphics card on two Dell Inspirion 1501 laptops that occurred around the same time after a recent update. [AMD/ATI] RS482M [Mobility Radeon Xpress 200] - Ubuntu Mate 20.04 Issues include:- > Message of error occurred with "mate-session-check-accelerated-gl-helper" > after boot. > Reports of r300 module missing then segfault when playing video in VLC > Segfault when you run glxinfo > WebGL items not working in Firefox. ** Attachment added: "vlc.crash" https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1911133/+attachment/5453666/+files/vlc.crash -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1911133 Title: [Regression] RS482M [Mobility Radeon Xpress 200] Status in mesa package in Ubuntu: Confirmed Bug description: RS482M [Mobility Radeon Xpress 200] crash gnome desktop at startup with Oh no! Something has gone wrong after latest updates It works fine before them System: Hp Nx6325 Video: Advanced Micro Deviceº Inc. [AMD/ATI] RS482M [Mobility Radeon Xpress 200] (prog-if 00 [VGA controller]) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1911133/+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 48734] Re: Home permissions too open
Probably, behind the original decision there were also issues of home
access, required by some unprivileged services, like apache (userdir).
Today, letting all users accessing any ~/Doc,~/Pic,~/Video look like a
huge security hole (MS Windows deny this).
But anyway, today 'user' access should support user namespaces
(subuid/subgid)
This is required for rootless container development (podman, docker).
Another point is "sandbox model" by snap/flatpak.
In particular in "partial" supported scenarios: Snap+SeLinux (fedora)
and Flatpak+AppArmor (ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to adduser in Ubuntu.
https://bugs.launchpad.net/bugs/48734
Title:
Home permissions too open
Status in adduser package in Ubuntu:
Fix Committed
Status in shadow package in Ubuntu:
Fix Released
Status in adduser source package in Hirsute:
Fix Committed
Status in shadow source package in Hirsute:
Fix Released
Status in Ubuntu RTM:
Opinion
Bug description:
Binary package hint: debian-installer
On a fresh dapper install i noticed that the file permissons for the
home directory for the user created by the installer is set to 755,
giving read access to everyone on the system.
Surely this is a bad idea? If your set on the idea can we atleast have
a option during the boot proccess?
Also new files that are created via the console ('touch' etc.) are
done so with '644' permissons, is there anything that can be done
here? nautlius seems to create files at '600', which is a better
setting.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/48734/+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 1911133] Re: [Regression] RS482M [Mobility Radeon Xpress 200]
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mesa (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1911133 Title: [Regression] RS482M [Mobility Radeon Xpress 200] Status in mesa package in Ubuntu: Confirmed Bug description: RS482M [Mobility Radeon Xpress 200] crash gnome desktop at startup with Oh no! Something has gone wrong after latest updates It works fine before them System: Hp Nx6325 Video: Advanced Micro Deviceº Inc. [AMD/ATI] RS482M [Mobility Radeon Xpress 200] (prog-if 00 [VGA controller]) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1911133/+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 1908167] Autopkgtest regression report (pulseaudio/1:13.99.2-1ubuntu2.3)
All autopkgtests for the newly accepted pulseaudio (1:13.99.2-1ubuntu2.3) for groovy have finished running. The following regressions have been reported in tests triggered by the package: openjdk-8/8u275-b01-0ubuntu1~20.10 (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/groovy/update_excuses.html#pulseaudio [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1908167 Title: [SRU] pulseaudio: the headset-mic or heapdhone-mic could not be selected automatically if there is no internal mic Status in HWE Next: New Status in OEM Priority Project: New Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Focal: Fix Committed Status in pulseaudio source package in Groovy: Fix Committed Status in pulseaudio source package in Hirsute: Fix Released Bug description: [Impact] On the Dell AIO machines, there is no internal mic, after plugging a headset, users expect the headset-mic or headphone-mic could be selected automatically. But with the current rule, the headset-mic/headphone-mic will not be selected automatically and even users manually select them, they will not show up in the gnome sound setting, and users could not record sound by headset-mic/headphone-mic. [Fix] backport a patch from pulseaudio mergerequest, the patch is going to be merged to pulseaudio 14.1. This patch could be backported to hirsute without any change, but need to be changed if backport it to groovy and focal. [Test] With the old pulseaudio (prior to 1:13.99.1-1ubuntu3.10), plugging in a headset to the problematic Dell AIO machine will not automatically select headset-mic/headphone-mic, and they also do not show up in Gnome sound settings, leading to failure to record any sound. With the new proposed package, on those Dell AIO, plug a headset, open the gnome sound setting, the headset-mic is selected automatically, use the headset-mic to record the sound, the sound could be recorded and the sound quality is good. [Where problems could occur] This patch could change the policy of audio device switching, it will not affect all audio devices, but only the devices which has AVAIL_UNKNOWN available status, that means it has possibility to introduce the regression on headphone-mic ,headset-mic, internal mic and internal speaker's switching since they all has AVAIL_UNKNOWN status. For example, after unpluging the headset, the input device will not switch to internal mic automatically or after unplug the headphone, the output device will not switch to internal speaker automatically. But this possibility is very low, we have tested the patch on many Dell and Lenovo machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1908167/+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 1763100] Re: FONT="x/y/z" is not applied due to setupcon script bug
I confirm the bug also on Ubuntu 20.04.1
Patch on post #3 resolve the problem.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to console-setup in Ubuntu.
https://bugs.launchpad.net/bugs/1763100
Title:
FONT="x/y/z" is not applied due to setupcon script bug
Status in console-setup package in Ubuntu:
Confirmed
Bug description:
apt-cache policy console-setup
console-setup:
Installed: 1.178ubuntu1
Candidate: 1.178ubuntu1
Version table:
*** 1.178ubuntu1 500
500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
500 http://gb.archive.ubuntu.com/ubuntu bionic/main i386 Packages
100 /var/lib/dpkg/status
On 18.04 I wanted to set the TTY font to use a Powerline font. Despite
being able to set the font manually it wasn't being set at boot-time.
/etc/default/console-setup contains:
FONT="/usr/local/share/fonts/ter-powerline-v22n.psf.gz"
"setupcon -v -f" reported an error:
putfont: KDFONTOP: Invalid argument
due to passing the font filename twice:
executing setfont -C /dev/tty1 /usr/local/share/fonts/ter-powerline-
v22n.psf.gz /usr/local/share/fonts/ter-powerline-v22n.psf.gz.
The problem is in /bin/setupcon where the collecting variable
FONTFILES has the font added twice, once at the top of the for loop
FONTFILES="$FONTFILES `findfile $fontdir $f`"
and again at the bottom
FONTFILES="$FONTFILES $RES"
Removing the first assignment fixes it.
FONTFILES=''
echo "DEBUG: FONT=$FONT"
if [ "$FONT" ]; then
for f in $FONT; do
echo "DEBUG: for loop"
FONTFILES="$FONTFILES `findfile $fontdir $f`"
RES=`findfile $fontdir $f`
if [ -z "$RES" ]; then
fdec="${f%.gz}"
RES=`findfile $fontdir $fdec`
fi
FONTFILES="$FONTFILES $RES"
done
fi
FONTFILES=`echo $FONTFILES` # remove extra spaces
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1763100/+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
Re: [Touch-packages] [Bug 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected
I don't believe that this is fixed. I am still getting errors: [ 88.448840] [ cut here ] [ 88.448842] nouveau :01:00.0: timeout [ 88.448887] WARNING: CPU: 3 PID: 1177 at /build/linux-hwe-5.4-hNUtrM/linux-hwe-5.4-5.4.0/drivers/gpu/drm/nouveau/nvkm/falcon/v1.c:313 nvkm_falcon_v1_clear_interrupt+0xe6/0x100 [nouveau] [ 88.448887] Modules linked in: cmac bnep snd_hda_codec_hdmi snd_soc_hdac_hdmi snd_hda_codec_realtek snd_hda_codec_generic snd_soc_dmic snd_sof_pci snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda snd_sof_intel_byt snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi ledtrig_audio snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine nls_iso8859_1 joydev hid_multitouch 8250_dw mei_hdcp intel_rapl_msr x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_hda_intel snd_intel_dspcfg uvcvideo kvm iwlmvm snd_seq_midi snd_seq_midi_event snd_hda_codec videobuf2_vmalloc rapl input_leds snd_hda_core snd_rawmidi mac80211 videobuf2_memops btusb snd_hwdep videobuf2_v4l2 btrtl videobuf2_common asus_nb_wmi btbcm asus_wmi btintel intel_cstate libarc4 serio_raw sparse_keymap wmi_bmof videodev snd_seq snd_pcm bluetooth iwlwifi mc snd_seq_device snd_timer snd processor_thermal_device mei_me ecdh_generic intel_rapl_common intel_lpss_pci ecc [ 88.448901] cfg80211 intel_lpss idma64 mei virt_dma soundcore intel_soc_dts_iosf intel_pch_thermal int3403_thermal int340x_thermal_zone mac_hid int3400_thermal acpi_pad asus_wireless acpi_thermal_rel sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 algif_skcipher af_alg dm_crypt hid_generic usbhid nouveau i915 crct10dif_pclmul crc32_pclmul mxm_wmi ghash_clmulni_intel ttm i2c_algo_bit aesni_intel drm_kms_helper crypto_simd syscopyarea sysfillrect nvme sysimgblt cryptd fb_sys_fops glue_helper drm r8169 ahci nvme_core realtek libahci i2c_hid wmi video hid pinctrl_cannonlake pinctrl_intel [ 88.448913] CPU: 3 PID: 1177 Comm: gnome-shell Not tainted 5.4.0-62-generic #70~18.04.1-Ubuntu [ 88.448914] Hardware name: ASUSTeK COMPUTER INC. TUF Gaming FX705GE_FX705GE/FX705GE, BIOS FX705GE.302 11/16/2018 [ 88.448929] RIP: 0010:nvkm_falcon_v1_clear_interrupt+0xe6/0x100 [nouveau] [ 88.448930] Code: 45 b0 48 8b 40 10 48 8b 78 10 48 8b 5f 50 48 85 db 74 1b e8 3c 35 d6 c7 48 89 da 48 89 c6 48 c7 c7 ba c7 af c0 e8 2a 7f 70 c7 <0f> 0b eb a8 48 8b 1f eb e0 e8 fc 81 70 c7 66 90 66 2e 0f 1f 84 00 [ 88.448930] RSP: 0018:b912c1447a08 EFLAGS: 00010282 [ 88.448931] RAX: RBX: 9b3ad8cfdb70 RCX: 0006 [ 88.448931] RDX: 0007 RSI: 0096 RDI: 9b3add8d78c0 [ 88.448932] RBP: b912c1447a58 R08: 03e9 R09: 0004 [ 88.448932] R10: 002c R11: 0001 R12: 9b3aca5aab00 [ 88.448933] R13: 0010 R14: ff92 R15: [ 88.448933] FS: 7ff79ae03ac0() GS:9b3add8c() knlGS: [ 88.448934] CS: 0010 DS: ES: CR0: 80050033 [ 88.448934] CR2: 00c42085b000 CR3: 000850710002 CR4: 003606e0 [ 88.448935] Call Trace: [ 88.448950] nvkm_falcon_clear_interrupt+0x15/0x20 [nouveau] [ 88.448972] acr_r352_bootstrap+0x9f/0x290 [nouveau] [ 88.448993] acr_r352_reset+0x39/0x250 [nouveau] [ 88.449014] nvkm_secboot_reset+0x31/0x70 [nouveau] [ 88.449037] gf100_gr_init_ctxctl+0x268/0x700 [nouveau] [ 88.449060] gf100_gr_init+0x563/0x590 [nouveau] [ 88.449082] gf100_gr_init_+0x90/0x120 [nouveau] [ 88.449104] nvkm_gr_init+0x1d/0x20 [nouveau] [ 88.449117] nvkm_engine_init+0x6b/0x1d0 [nouveau] [ 88.449131] nvkm_subdev_init+0xb3/0x1d0 [nouveau] [ 88.449133] ? _cond_resched+0x19/0x40 [ 88.449146] nvkm_engine_ref.part.0+0x4a/0x70 [nouveau] [ 88.449159] nvkm_engine_ref+0x13/0x20 [nouveau] [ 88.449171] nvkm_ioctl_new+0x277/0x2c0 [nouveau] [ 88.449194] ? nvkm_fifo_chan_child_del+0xa0/0xa0 [nouveau] [ 88.449216] ? gf100_gr_dtor+0xe0/0xe0 [nouveau] [ 88.449229] nvkm_ioctl+0x11d/0x280 [nouveau] [ 88.449252] nvkm_client_ioctl+0x12/0x20 [nouveau] [ 88.449264] nvif_client_ioctl+0x2c/0x30 [nouveau] [ 88.449286] usif_ioctl+0x657/0x760 [nouveau] [ 88.449307] nouveau_drm_ioctl+0xac/0xc0 [nouveau] [ 88.449309] do_vfs_ioctl+0xa9/0x640 [ 88.449310] ? handle_mm_fault+0xcb/0x210 [ 88.449311] ksys_ioctl+0x75/0x80 [ 88.449312] __x64_sys_ioctl+0x1a/0x20 [ 88.449313] do_syscall_64+0x57/0x190 [ 88.449315] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 88.449316] RIP: 0033:0x7ff797ec0317 [ 88.449317] Code: b3 66 90 48 8b 05 71 4b 2d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 41 4b 2d 00 f7 d8 64 89 01 48 [ 88.449317] RSP: 002b:7ffe9a44a418 EFLAGS: 0246 ORIG_RAX: 0010 [ 88.449318] RAX: ffda RBX: 0038 RCX:
Re: [Touch-packages] [Bug 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected
There definitely seems to be an issue here: [ 88.448840] [ cut here ] [ 88.448842] nouveau :01:00.0: timeout [ 88.448887] WARNING: CPU: 3 PID: 1177 at /build/linux-hwe-5.4-hNUtrM/linux-hwe-5.4-5.4.0/drivers/gpu/drm/nouveau/nvkm/falcon/v1.c:313 nvkm_falcon_v1_clear_interrupt+0xe6/0x100 [nouveau] [ 88.448887] Modules linked in: cmac bnep snd_hda_codec_hdmi snd_soc_hdac_hdmi snd_hda_codec_realtek snd_hda_codec_generic snd_soc_dmic snd_sof_pci snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda snd_sof_intel_byt snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi ledtrig_audio snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine nls_iso8859_1 joydev hid_multitouch 8250_dw mei_hdcp intel_rapl_msr x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_hda_intel snd_intel_dspcfg uvcvideo kvm iwlmvm snd_seq_midi snd_seq_midi_event snd_hda_codec videobuf2_vmalloc rapl input_leds snd_hda_core snd_rawmidi mac80211 videobuf2_memops btusb snd_hwdep videobuf2_v4l2 btrtl videobuf2_common asus_nb_wmi btbcm asus_wmi btintel intel_cstate libarc4 serio_raw sparse_keymap wmi_bmof videodev snd_seq snd_pcm bluetooth iwlwifi mc snd_seq_device snd_timer snd processor_thermal_device mei_me ecdh_generic intel_rapl_common intel_lpss_pci ecc [ 88.448901] cfg80211 intel_lpss idma64 mei virt_dma soundcore intel_soc_dts_iosf intel_pch_thermal int3403_thermal int340x_thermal_zone mac_hid int3400_thermal acpi_pad asus_wireless acpi_thermal_rel sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 algif_skcipher af_alg dm_crypt hid_generic usbhid nouveau i915 crct10dif_pclmul crc32_pclmul mxm_wmi ghash_clmulni_intel ttm i2c_algo_bit aesni_intel drm_kms_helper crypto_simd syscopyarea sysfillrect nvme sysimgblt cryptd fb_sys_fops glue_helper drm r8169 ahci nvme_core realtek libahci i2c_hid wmi video hid pinctrl_cannonlake pinctrl_intel [ 88.448913] CPU: 3 PID: 1177 Comm: gnome-shell Not tainted 5.4.0-62-generic #70~18.04.1-Ubuntu [ 88.448914] Hardware name: ASUSTeK COMPUTER INC. TUF Gaming FX705GE_FX705GE/FX705GE, BIOS FX705GE.302 11/16/2018 [ 88.448929] RIP: 0010:nvkm_falcon_v1_clear_interrupt+0xe6/0x100 [nouveau] [ 88.448930] Code: 45 b0 48 8b 40 10 48 8b 78 10 48 8b 5f 50 48 85 db 74 1b e8 3c 35 d6 c7 48 89 da 48 89 c6 48 c7 c7 ba c7 af c0 e8 2a 7f 70 c7 <0f> 0b eb a8 48 8b 1f eb e0 e8 fc 81 70 c7 66 90 66 2e 0f 1f 84 00 [ 88.448930] RSP: 0018:b912c1447a08 EFLAGS: 00010282 [ 88.448931] RAX: RBX: 9b3ad8cfdb70 RCX: 0006 [ 88.448931] RDX: 0007 RSI: 0096 RDI: 9b3add8d78c0 [ 88.448932] RBP: b912c1447a58 R08: 03e9 R09: 0004 [ 88.448932] R10: 002c R11: 0001 R12: 9b3aca5aab00 [ 88.448933] R13: 0010 R14: ff92 R15: [ 88.448933] FS: 7ff79ae03ac0() GS:9b3add8c() knlGS: [ 88.448934] CS: 0010 DS: ES: CR0: 80050033 [ 88.448934] CR2: 00c42085b000 CR3: 000850710002 CR4: 003606e0 [ 88.448935] Call Trace: [ 88.448950] nvkm_falcon_clear_interrupt+0x15/0x20 [nouveau] [ 88.448972] acr_r352_bootstrap+0x9f/0x290 [nouveau] [ 88.448993] acr_r352_reset+0x39/0x250 [nouveau] [ 88.449014] nvkm_secboot_reset+0x31/0x70 [nouveau] [ 88.449037] gf100_gr_init_ctxctl+0x268/0x700 [nouveau] [ 88.449060] gf100_gr_init+0x563/0x590 [nouveau] [ 88.449082] gf100_gr_init_+0x90/0x120 [nouveau] [ 88.449104] nvkm_gr_init+0x1d/0x20 [nouveau] [ 88.449117] nvkm_engine_init+0x6b/0x1d0 [nouveau] [ 88.449131] nvkm_subdev_init+0xb3/0x1d0 [nouveau] [ 88.449133] ? _cond_resched+0x19/0x40 [ 88.449146] nvkm_engine_ref.part.0+0x4a/0x70 [nouveau] [ 88.449159] nvkm_engine_ref+0x13/0x20 [nouveau] [ 88.449171] nvkm_ioctl_new+0x277/0x2c0 [nouveau] [ 88.449194] ? nvkm_fifo_chan_child_del+0xa0/0xa0 [nouveau] [ 88.449216] ? gf100_gr_dtor+0xe0/0xe0 [nouveau] [ 88.449229] nvkm_ioctl+0x11d/0x280 [nouveau] [ 88.449252] nvkm_client_ioctl+0x12/0x20 [nouveau] [ 88.449264] nvif_client_ioctl+0x2c/0x30 [nouveau] [ 88.449286] usif_ioctl+0x657/0x760 [nouveau] [ 88.449307] nouveau_drm_ioctl+0xac/0xc0 [nouveau] [ 88.449309] do_vfs_ioctl+0xa9/0x640 [ 88.449310] ? handle_mm_fault+0xcb/0x210 [ 88.449311] ksys_ioctl+0x75/0x80 [ 88.449312] __x64_sys_ioctl+0x1a/0x20 [ 88.449313] do_syscall_64+0x57/0x190 [ 88.449315] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 88.449316] RIP: 0033:0x7ff797ec0317 [ 88.449317] Code: b3 66 90 48 8b 05 71 4b 2d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 41 4b 2d 00 f7 d8 64 89 01 48 [ 88.449317] RSP: 002b:7ffe9a44a418 EFLAGS: 0246 ORIG_RAX: 0010 [ 88.449318] RAX: ffda RBX: 0038 RCX: 7ff797ec0317 [
