[Touch-packages] [Bug 1810316] Re: gnome-control-center SIGABRT when network-manager is not working [Assertion failure "G_IS_OBJECT (object)" in cc_object_storage_add_object]
** Changed in: gnome-control-center Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1810316 Title: gnome-control-center SIGABRT when network-manager is not working [Assertion failure "G_IS_OBJECT (object)" in cc_object_storage_add_object] Status in gnome-control-center: Fix Released Status in NetworkManager: Fix Released Status in gnome-control-center package in Ubuntu: Triaged Status in network-manager package in Ubuntu: Incomplete Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:3.30.0-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/b90090b3330514b0e5d6f1ed58c2260a77b8e5e8 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. --- https://gitlab.gnome.org/GNOME/gnome-control-center/issues/342 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/143 --- [Impact] gnome-control-center goes crash when I try to work with two USB WiFi cards. [Test Case] I have a wireless card connected and then I connect 'another' wireless card and the network module starts to malfunction in the gnome-control-center. [Potential Regression] I think it's not a potential regression. Original Description * I was trying to open wifi settings * I'm connecting 2 WiFi USB in ubuntu disk ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: gnome-control-center 1:3.30.2-1ubuntu0.18.10.1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 2 09:54:42 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2018-09-27 (97 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: gnome-control-center wifi ProcEnviron: LC_COLLATE=C PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: gnome-control-center StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 cc_object_storage_add_object () cc_wifi_panel_static_init_func () cc_panel_loader_fill_model () Title: gnome-control-center crashed with SIGABRT UpgradeStatus: Upgraded to cosmic on 2018-11-08 (54 days ago) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo vboxusers wireshark modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2018-10-04T06:36:50.792292 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1810316/+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 2039371] Re: package network-manager 1.44.2-1ubuntu1 failed to install/upgrade: installed network-manager package post-installation script subprocess was killed by signal (Termin
(note : NetworkManager works quite well, service NetworkManager status is happy, but nm-online never returns) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2039371 Title: package network-manager 1.44.2-1ubuntu1 failed to install/upgrade: installed network-manager package post-installation script subprocess was killed by signal (Terminated) Status in network-manager package in Ubuntu: New Bug description: With do-release-upgrade -d, Setting up network-manager hanged indefinitely with [...] Setting up network-manager (1.44.2-1ubuntu1) ... SKIP: NetworkManager is not ready ... SKIP: NetworkManager is not ready ... SKIP: NetworkManager is not ready ... SKIP: NetworkManager is not ready ... SKIP: NetworkManager is not ready ... ^[[CSKIP: NetworkManager is not ready ... SKIP: NetworkManager is not ready ... SKIP: NetworkManager is not ready ... SKIP: NetworkManager is not ready ... SKIP: NetworkManager is not ready ... SKIP: NetworkManager is not ready ... SKIP: NetworkManager is not ready ... [...] Killing it resulted in Terminated SKIP: NetworkManager is not ready ... dpkg: error processing package network-manager (--configure): installed network-manager package post-installation script subprocess was killed by signal (Terminated) ProblemType: Package DistroRelease: Ubuntu 23.10 Package: network-manager 1.44.2-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-34.34-generic 6.2.16 Uname: Linux 6.2.0-34-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass Date: Sun Oct 15 00:40:40 2023 ErrorMessage: installed network-manager package post-installation script subprocess was killed by signal (Terminated) InstallationDate: Installed on 2023-01-13 (274 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) IpRoute: default via 192.168.0.254 dev wlp2s0 proto dhcp src 192.168.0.29 metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.29 metric 600 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5 PythonDetails: /usr/bin/python3.11, Python 3.11.6, python-is-python3, 3.11.4-1 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.22.0ubuntu1 apt 2.7.3 SourcePackage: network-manager Title: package network-manager 1.44.2-1ubuntu1 failed to install/upgrade: installed network-manager package post-installation script subprocess was killed by signal (Terminated) UpgradeStatus: Upgraded to mantic on 2023-10-14 (0 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.44.2 connected starting full enabled enabled enabled missing enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2039371/+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 2039371] [NEW] package network-manager 1.44.2-1ubuntu1 failed to install/upgrade: installed network-manager package post-installation script subprocess was killed by signal (Term
Public bug reported: With do-release-upgrade -d, Setting up network-manager hanged indefinitely with [...] Setting up network-manager (1.44.2-1ubuntu1) ... SKIP: NetworkManager is not ready ... SKIP: NetworkManager is not ready ... SKIP: NetworkManager is not ready ... SKIP: NetworkManager is not ready ... SKIP: NetworkManager is not ready ... ^[[CSKIP: NetworkManager is not ready ... SKIP: NetworkManager is not ready ... SKIP: NetworkManager is not ready ... SKIP: NetworkManager is not ready ... SKIP: NetworkManager is not ready ... SKIP: NetworkManager is not ready ... SKIP: NetworkManager is not ready ... [...] Killing it resulted in Terminated SKIP: NetworkManager is not ready ... dpkg: error processing package network-manager (--configure): installed network-manager package post-installation script subprocess was killed by signal (Terminated) ProblemType: Package DistroRelease: Ubuntu 23.10 Package: network-manager 1.44.2-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-34.34-generic 6.2.16 Uname: Linux 6.2.0-34-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass Date: Sun Oct 15 00:40:40 2023 ErrorMessage: installed network-manager package post-installation script subprocess was killed by signal (Terminated) InstallationDate: Installed on 2023-01-13 (274 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) IpRoute: default via 192.168.0.254 dev wlp2s0 proto dhcp src 192.168.0.29 metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.29 metric 600 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5 PythonDetails: /usr/bin/python3.11, Python 3.11.6, python-is-python3, 3.11.4-1 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.22.0ubuntu1 apt 2.7.3 SourcePackage: network-manager Title: package network-manager 1.44.2-1ubuntu1 failed to install/upgrade: installed network-manager package post-installation script subprocess was killed by signal (Terminated) UpgradeStatus: Upgraded to mantic on 2023-10-14 (0 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.44.2 connected starting full enabled enabled enabled missing enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package mantic need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2039371 Title: package network-manager 1.44.2-1ubuntu1 failed to install/upgrade: installed network-manager package post-installation script subprocess was killed by signal (Terminated) Status in network-manager package in Ubuntu: New Bug description: With do-release-upgrade -d, Setting up network-manager hanged indefinitely with [...] Setting up network-manager (1.44.2-1ubuntu1) ... SKIP: NetworkManager is not ready ... SKIP: NetworkManager is not ready ... SKIP: NetworkManager is not ready ... SKIP: NetworkManager is not ready ... SKIP: NetworkManager is not ready ... ^[[CSKIP: NetworkManager is not ready ... SKIP: NetworkManager is not ready ... SKIP: NetworkManager is not ready ... SKIP: NetworkManager is not ready ... SKIP: NetworkManager is not ready ... SKIP: NetworkManager is not ready ... SKIP: NetworkManager is not ready ... [...] Killing it resulted in Terminated SKIP: NetworkManager is not ready ... dpkg: error processing package network-manager (--configure): installed network-manager package post-installation script subprocess was killed by signal (Terminated) ProblemType: Package DistroRelease: Ubuntu 23.10 Package: network-manager 1.44.2-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-34.34-generic 6.2.16 Uname: Linux 6.2.0-34-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass Date: Sun Oct 15 00:40:40 2023 ErrorMessage: installed network-manager package post-installation script subprocess was killed by signal (Terminated) InstallationDate: Installed on 2023-01-13 (274 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) IpRoute: default via 192.168.0.254 dev wlp2s0 proto dhcp src 192.168.0.29 metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.0.0/24 dev wlp2s0 proto kernel scope link src
[Touch-packages] [Bug 2039371] Re: package network-manager 1.44.2-1ubuntu1 failed to install/upgrade: installed network-manager package post-installation script subprocess was killed by signal (Termin
also hangs at the end when retrying [...] └─ /usr/bin/dpkg --configure -a └─ /bin/sh /var/lib/dpkg/info/network-manager.postinst configure 1.42.4-1ubuntu2 └─ nm-online -qs ├─ nm-online -qs ├─ nm-online -qs └─ nm-online -qs -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2039371 Title: package network-manager 1.44.2-1ubuntu1 failed to install/upgrade: installed network-manager package post-installation script subprocess was killed by signal (Terminated) Status in network-manager package in Ubuntu: New Bug description: With do-release-upgrade -d, Setting up network-manager hanged indefinitely with [...] Setting up network-manager (1.44.2-1ubuntu1) ... SKIP: NetworkManager is not ready ... SKIP: NetworkManager is not ready ... SKIP: NetworkManager is not ready ... SKIP: NetworkManager is not ready ... SKIP: NetworkManager is not ready ... ^[[CSKIP: NetworkManager is not ready ... SKIP: NetworkManager is not ready ... SKIP: NetworkManager is not ready ... SKIP: NetworkManager is not ready ... SKIP: NetworkManager is not ready ... SKIP: NetworkManager is not ready ... SKIP: NetworkManager is not ready ... [...] Killing it resulted in Terminated SKIP: NetworkManager is not ready ... dpkg: error processing package network-manager (--configure): installed network-manager package post-installation script subprocess was killed by signal (Terminated) ProblemType: Package DistroRelease: Ubuntu 23.10 Package: network-manager 1.44.2-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-34.34-generic 6.2.16 Uname: Linux 6.2.0-34-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass Date: Sun Oct 15 00:40:40 2023 ErrorMessage: installed network-manager package post-installation script subprocess was killed by signal (Terminated) InstallationDate: Installed on 2023-01-13 (274 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) IpRoute: default via 192.168.0.254 dev wlp2s0 proto dhcp src 192.168.0.29 metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.29 metric 600 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5 PythonDetails: /usr/bin/python3.11, Python 3.11.6, python-is-python3, 3.11.4-1 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.22.0ubuntu1 apt 2.7.3 SourcePackage: network-manager Title: package network-manager 1.44.2-1ubuntu1 failed to install/upgrade: installed network-manager package post-installation script subprocess was killed by signal (Terminated) UpgradeStatus: Upgraded to mantic on 2023-10-14 (0 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.44.2 connected starting full enabled enabled enabled missing enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2039371/+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 2039352] Re: OpenGL applications don't run on AMD FirePro S7150 and fill dmesg with: *ERROR* Not enough memory for command submission!
@oibaf thanks, I reported it:
- https://gitlab.freedesktop.org/mesa/mesa/-/issues/1
(nice issue number by the way ☺️)
** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #1
https://gitlab.freedesktop.org/mesa/mesa/-/issues/1
--
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/2039352
Title:
OpenGL applications don't run on AMD FirePro S7150 and fill dmesg
with: *ERROR* Not enough memory for command submission!
Status in mesa package in Ubuntu:
New
Bug description:
I first thought the Radeon PRO W7600 was affected, in fact the
affected GPU is the AMD FirePro S7150.
See comment 3 and below:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2039352/comments/3
__
When I run Unigine Superposition 1.1, it doesn't open any window and
dmesg is filled with:
```
[36881.961064] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
[36881.962579] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
[36881.963946] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
[36881.965556] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
[36881.967138] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
[36881.968522] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
```
printing new error log lines many time per second.
Killing the Unigine Superposition process stops the log printing.
There are more than one GPU in that system but the one used for
rendering is a Radeon PRO W7600:
```
Slot: 47:00.0
Class:VGA compatible controller [0300]
Vendor: Advanced Micro Devices, Inc. [AMD/ATI] [1002]
Device: Navi 33 [Radeon RX 7700S/7600/7600S/7600M XT/PRO W7600] [7480]
SVendor: Advanced Micro Devices, Inc. [AMD/ATI] [1002]
SDevice: Device [0e0d]
ProgIf: 00
Driver: amdgpu
Module: amdgpu
IOMMUGroup: 58
```
```
name of display: :1
display: :1 screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
Vendor: AMD (0x1002)
Device: AMD Radeon PRO W7600 (gfx1102, LLVM 15.0.7, DRM 3.54,
6.5.0-9-generic) (0x7480)
Version: 23.2.1
Accelerated: yes
Video memory: 8192MB
Unified memory: no
Preferred profile: core (0x1)
Max core profile version: 4.6
Max compat profile version: 4.6
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.2
```
Other games like Unvanquished or Quake II RTX are working correctly.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: libglapi-mesa 23.2.1-1ubuntu3
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompizPlugins:
[core,bailer,detection,composite,opengl,imgjpeg,compiztoolbox,copytex,decor,regex,snap,vpswitch,mousepoll,gnomecompat,titleinfo,imgpng,resize,animation,expo,ezoom,grid,place,move,imgsvg,workarounds,wall,session,thumbnail,staticswitcher,fade,scale]
CompositorRunning: None
CurrentDesktop: GNOME
Date: Sat Oct 14 14:58:23 2023
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
v4l2loopback/0.12.7, 6.5.0-9-generic, x86_64: installed (WARNING! Diff
between built and installed module!)
vhba/20211218, 6.2.0-33-generic, x86_64: installed
vhba/20211218, 6.5.0-9-generic, x86_64: installed
ExtraDebuggingInterest: Yes
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.5.0-9-generic
root=UUID=f35ecf77-511e-4dde-ac11-c1d848e97315 ro rootflags=subvol=@
amdgpu.si_support=1 radeon.si_support=0 amdgpu.cik_support=1
radeon.cik_support=0 amdgpu.exp_hw_support=1 amdgpu.gpu_recovery=1
amdgpu.ppfeaturemask=0x delayacct zswap.enabled=1
SourcePackage: mesa
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/08/2023
dmi.bios.release: 5.23
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: WRX80SU8-F6
dmi.board.asset.tag: Default string
dmi.board.name: Default string
dmi.board.vendor: Default string
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrWRX80SU8-F6:bd06/08/2023:br5.23:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family:
[Touch-packages] [Bug 2039352] Re: OpenGL applications don't run on AMD FirePro S7150 and fill dmesg with: *ERROR* Not enough memory for command submission!
@illwieckz: please report the bug at:
https://gitlab.freedesktop.org/mesa/mesa/-/issues
--
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/2039352
Title:
OpenGL applications don't run on AMD FirePro S7150 and fill dmesg
with: *ERROR* Not enough memory for command submission!
Status in mesa package in Ubuntu:
New
Bug description:
I first thought the Radeon PRO W7600 was affected, in fact the
affected GPU is the AMD FirePro S7150.
See comment 3 and below:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2039352/comments/3
__
When I run Unigine Superposition 1.1, it doesn't open any window and
dmesg is filled with:
```
[36881.961064] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
[36881.962579] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
[36881.963946] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
[36881.965556] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
[36881.967138] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
[36881.968522] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
```
printing new error log lines many time per second.
Killing the Unigine Superposition process stops the log printing.
There are more than one GPU in that system but the one used for
rendering is a Radeon PRO W7600:
```
Slot: 47:00.0
Class:VGA compatible controller [0300]
Vendor: Advanced Micro Devices, Inc. [AMD/ATI] [1002]
Device: Navi 33 [Radeon RX 7700S/7600/7600S/7600M XT/PRO W7600] [7480]
SVendor: Advanced Micro Devices, Inc. [AMD/ATI] [1002]
SDevice: Device [0e0d]
ProgIf: 00
Driver: amdgpu
Module: amdgpu
IOMMUGroup: 58
```
```
name of display: :1
display: :1 screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
Vendor: AMD (0x1002)
Device: AMD Radeon PRO W7600 (gfx1102, LLVM 15.0.7, DRM 3.54,
6.5.0-9-generic) (0x7480)
Version: 23.2.1
Accelerated: yes
Video memory: 8192MB
Unified memory: no
Preferred profile: core (0x1)
Max core profile version: 4.6
Max compat profile version: 4.6
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.2
```
Other games like Unvanquished or Quake II RTX are working correctly.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: libglapi-mesa 23.2.1-1ubuntu3
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompizPlugins:
[core,bailer,detection,composite,opengl,imgjpeg,compiztoolbox,copytex,decor,regex,snap,vpswitch,mousepoll,gnomecompat,titleinfo,imgpng,resize,animation,expo,ezoom,grid,place,move,imgsvg,workarounds,wall,session,thumbnail,staticswitcher,fade,scale]
CompositorRunning: None
CurrentDesktop: GNOME
Date: Sat Oct 14 14:58:23 2023
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
v4l2loopback/0.12.7, 6.5.0-9-generic, x86_64: installed (WARNING! Diff
between built and installed module!)
vhba/20211218, 6.2.0-33-generic, x86_64: installed
vhba/20211218, 6.5.0-9-generic, x86_64: installed
ExtraDebuggingInterest: Yes
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.5.0-9-generic
root=UUID=f35ecf77-511e-4dde-ac11-c1d848e97315 ro rootflags=subvol=@
amdgpu.si_support=1 radeon.si_support=0 amdgpu.cik_support=1
radeon.cik_support=0 amdgpu.exp_hw_support=1 amdgpu.gpu_recovery=1
amdgpu.ppfeaturemask=0x delayacct zswap.enabled=1
SourcePackage: mesa
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/08/2023
dmi.bios.release: 5.23
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: WRX80SU8-F6
dmi.board.asset.tag: Default string
dmi.board.name: Default string
dmi.board.vendor: Default string
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrWRX80SU8-F6:bd06/08/2023:br5.23:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: Default string
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Default string
[Touch-packages] [Bug 2039352] Re: OpenGL applications don't run on AMD FirePro S7150 and fill dmesg with: *ERROR* Not enough memory for command submission!
I reproduce the bug with current Mesa
(d97427f41c1603db2f657b5d9c3f91a97f74b1c0) and LLVM 16.0.6. I don't know
if the bug is on drm side or on Mesa side.
--
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/2039352
Title:
OpenGL applications don't run on AMD FirePro S7150 and fill dmesg
with: *ERROR* Not enough memory for command submission!
Status in mesa package in Ubuntu:
New
Bug description:
I first thought the Radeon PRO W7600 was affected, in fact the
affected GPU is the AMD FirePro S7150.
See comment 3 and below:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2039352/comments/3
__
When I run Unigine Superposition 1.1, it doesn't open any window and
dmesg is filled with:
```
[36881.961064] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
[36881.962579] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
[36881.963946] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
[36881.965556] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
[36881.967138] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
[36881.968522] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
```
printing new error log lines many time per second.
Killing the Unigine Superposition process stops the log printing.
There are more than one GPU in that system but the one used for
rendering is a Radeon PRO W7600:
```
Slot: 47:00.0
Class:VGA compatible controller [0300]
Vendor: Advanced Micro Devices, Inc. [AMD/ATI] [1002]
Device: Navi 33 [Radeon RX 7700S/7600/7600S/7600M XT/PRO W7600] [7480]
SVendor: Advanced Micro Devices, Inc. [AMD/ATI] [1002]
SDevice: Device [0e0d]
ProgIf: 00
Driver: amdgpu
Module: amdgpu
IOMMUGroup: 58
```
```
name of display: :1
display: :1 screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
Vendor: AMD (0x1002)
Device: AMD Radeon PRO W7600 (gfx1102, LLVM 15.0.7, DRM 3.54,
6.5.0-9-generic) (0x7480)
Version: 23.2.1
Accelerated: yes
Video memory: 8192MB
Unified memory: no
Preferred profile: core (0x1)
Max core profile version: 4.6
Max compat profile version: 4.6
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.2
```
Other games like Unvanquished or Quake II RTX are working correctly.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: libglapi-mesa 23.2.1-1ubuntu3
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompizPlugins:
[core,bailer,detection,composite,opengl,imgjpeg,compiztoolbox,copytex,decor,regex,snap,vpswitch,mousepoll,gnomecompat,titleinfo,imgpng,resize,animation,expo,ezoom,grid,place,move,imgsvg,workarounds,wall,session,thumbnail,staticswitcher,fade,scale]
CompositorRunning: None
CurrentDesktop: GNOME
Date: Sat Oct 14 14:58:23 2023
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
v4l2loopback/0.12.7, 6.5.0-9-generic, x86_64: installed (WARNING! Diff
between built and installed module!)
vhba/20211218, 6.2.0-33-generic, x86_64: installed
vhba/20211218, 6.5.0-9-generic, x86_64: installed
ExtraDebuggingInterest: Yes
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.5.0-9-generic
root=UUID=f35ecf77-511e-4dde-ac11-c1d848e97315 ro rootflags=subvol=@
amdgpu.si_support=1 radeon.si_support=0 amdgpu.cik_support=1
radeon.cik_support=0 amdgpu.exp_hw_support=1 amdgpu.gpu_recovery=1
amdgpu.ppfeaturemask=0x delayacct zswap.enabled=1
SourcePackage: mesa
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/08/2023
dmi.bios.release: 5.23
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: WRX80SU8-F6
dmi.board.asset.tag: Default string
dmi.board.name: Default string
dmi.board.vendor: Default string
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrWRX80SU8-F6:bd06/08/2023:br5.23:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: Default string
dmi.product.sku: Default string
[Touch-packages] [Bug 2037906] Re: [Intel AX201] Bluetooth LE not working after upgrade from 22.04 to 23.10
** Also affects: linux-firmware
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2037906
Title:
[Intel AX201] Bluetooth LE not working after upgrade from 22.04 to
23.10
Status in Linux Firmware:
New
Status in bluez package in Ubuntu:
New
Status in linux package in Ubuntu:
Incomplete
Bug description:
syslog:
2023-09-20T09:32:54.138852+02:00 zaionc kernel: [ 13.539860] Bluetooth:
hci0: Waiting for firmware download to complete
2023-09-20T09:32:54.138857+02:00 zaionc kernel: [ 13.540223] Bluetooth:
hci0: Firmware loaded in 1706498 usecs
2023-09-20T09:32:54.138858+02:00 zaionc kernel: [ 13.540278] Bluetooth:
hci0: Waiting for device to boot
2023-09-20T09:32:54.154894+02:00 zaionc kernel: [ 13.555430] Bluetooth:
hci0: Malformed MSFT vendor event: 0x02
2023-09-20T09:32:54.154908+02:00 zaionc kernel: [ 13.555482] Bluetooth:
hci0: Device booted in 14872 usecs
2023-09-20T09:32:54.154910+02:00 zaionc kernel: [ 13.555913] Bluetooth:
hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc
2023-09-20T09:32:54.158856+02:00 zaionc kernel: [ 13.558300] Bluetooth:
hci0: Applying Intel DDC parameters completed
2023-09-20T09:32:54.158859+02:00 zaionc kernel: [ 13.559326] Bluetooth:
hci0: Firmware revision 0.4 build 249 week 27 2023
lshw:
*-usb:5
description: Bluetooth wireless interface
product: AX201 Bluetooth
vendor: Intel Corp.
physical id: a
bus info: usb@3:a
version: 0.02
capabilities: bluetooth usb-2.01
configuration: driver=btusb maxpower=100mA speed=12Mbit/s
root@zaionc:~# hcitool lescan
Set scan parameters failed: Input/output error
At first bluetooth stopped working at all due to Ubuntu bug = missing
firmware. It was fixed recently and now the bluetooth module seems
fine, but the whole BTLE part is not available. Particularly I cannot
detect/pair Logitech M720 mouse.
Platform: ThinkPad T14 Gen 2i
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu4
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2022-05-28 (494 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64
(20220419)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
Package: linux
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic
root=UUID=d0002130-adf6-4f18-93b1-fda536d8b499 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
RebootRequiredPkgs: Error: path contained symlinks.
Tags: mantic
Uname: Linux 6.5.0-5-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-09-03 (30 days ago)
UserGroups: adm cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 05/10/2023
dmi.bios.release: 1.56
dmi.bios.vendor: LENOVO
dmi.bios.version: N34ET56W (1.56 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20W000AMPB
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.42
dmi.modalias:
dmi:bvnLENOVO:bvrN34ET56W(1.56):bd05/10/2023:br1.56:efr1.42:svnLENOVO:pn20W000AMPB:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W000AMPB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20W0_BU_Think_FM_ThinkPadT14Gen2i:
dmi.product.family: ThinkPad T14 Gen 2i
dmi.product.name: 20W000AMPB
dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i
dmi.product.version: ThinkPad T14 Gen 2i
dmi.sys.vendor: LENOVO
hciconfig:
hci0:Type: Primary Bus: USB
BD Address: A0:E7:0B:23:70:E8 ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING
RX bytes:22183 acl:0 sco:0 events:3531 errors:0
TX bytes:821193 acl:0 sco:0 commands:3510 errors:0
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux-firmware/+bug/2037906/+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 2039218] Re: NetworkManager doesn't connect to Wi-Fi after suspend
This bug can be closed. I know, what caused the problem. It is system76-driver package from System76 PPA, or its dependencies. When I uninstalled it, autoremoved dependencies and installed power-profiles- daemon, Wi-Fi wakes up after suspend. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2039218 Title: NetworkManager doesn't connect to Wi-Fi after suspend Status in network-manager package in Ubuntu: New Bug description: After upgrading to Mantic Minotaur, when I suspend and resume the system, NetworkManager doesn't see any Wi-Fi networks and i can't connect to Wi-Fi, unless I log out and log in. I don't know exactly in which package there is a problem, I can only guess, that it is network-manager or plasma-nm. My Wi-Fi adapter is Intel AX201 (Wi-Fi 6), operating under iwlwifi driver. Plasma Network Manager applet doesn't see any connections, unless I log out and log in. Or I can modprobe -r iwlwifi, modprobe iwlwifi. Then I can use nmcli to connect, but graphical interface doesn't work anymore. System info: Operating System: Kubuntu 23.10 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 Kernel Version: 6.5.0-9-generic (64-bit) Graphics Platform: Wayland Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz Memory: 31.2 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics Manufacturer: System76 Product Name: Darter Pro System Version: darp7 ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: network-manager 1.44.2-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Oct 12 21:31:21 2023 InstallationDate: Installed on 2021-07-23 (811 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: network-manager UpgradeStatus: Upgraded to mantic on 2023-10-12 (0 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.44.2 connected started full enabled enabled enabled missing enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2039218/+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 2037595] Autopkgtest regression report (gpgme1.0/1.13.1-7ubuntu2.2)
All autopkgtests for the newly accepted gpgme1.0 (1.13.1-7ubuntu2.2) for focal
have finished running.
The following regressions have been reported in tests triggered by the package:
samba/2:4.15.13+dfsg-0ubuntu0.20.04.7 (ppc64el)
Please visit the excuses page listed below and investigate the failures,
proceeding afterwards as per the StableReleaseUpdates policy regarding
autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#gpgme1.0
[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 gpgme1.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2037595
Title:
_gpgme_io_select breaks when more than 1024 file descriptors are open
Status in gpgme1.0 package in Ubuntu:
Fix Released
Status in gpgme1.0 source package in Focal:
Fix Committed
Status in gpgme1.0 source package in Jammy:
Fix Committed
Bug description:
[Impact]
Launchpad's buildd-manager is a complex event-driven daemon that
manages several hundred builders on production. As such, it can often
end up with more than 1024 file descriptors open. It also uses gpgme
from time to time to fetch signing keys for PPAs when dispatching
builds that involve PPAs.
On focal (and also on jammy), this breaks because `_gpgme_io_select`
is implemented using select(2), whose manual page says: "WARNING:
select() can monitor only file descriptors numbers that are less than
FD_SETSIZE (1024)—an unreasonably low limit for many modern
applications—and this limitation will not change. All modern
applications should instead use poll(2) or epoll(7), which do not
suffer this limitation." This is exactly the limitation we're running
into, resulting in mysterious "Too many open files" errors despite
resource limits being set to more than comfortable values.
Fortunately, this was fixed upstream in https://git.gnupg.org/cgi-
bin/gitweb.cgi?p=gpgme.git;a=commitdiff;h=8148237cb4ae20755c06a44d71761c7030973c3d,
and lunar has that fix. focal and jammy do not (there may be a
similar problem with older LTSes too, but I only care about it back to
focal). buildd-manager currently runs on focal.
We've been running buildd-manager with a cherry-picked fix from
upstream for a few weeks now, and I'd like to get that SRUed back into
Ubuntu so that we don't accidentally lose this patch in the event of a
security update or similar.
[Test Plan]
William Grant provided this minimal reproducer:
```
root@tmp:~# python3
Python 3.8.10 (default, May 26 2023, 14:05:08)
[GCC 9.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import gpg
>>> c = gpg.Context()
>>> list(c.keylist())
[]
>>> fs = []
>>> for i in range(1024):
... fs.append(open('/dev/null'))
...
>>> list(c.keylist())
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/gpg/core.py", line 751, in keylist
key = self.op_keylist_next()
File "/usr/lib/python3/dist-packages/gpg/core.py", line 1195, in
op_keylist_next
raise excp
File "/usr/lib/python3/dist-packages/gpg/core.py", line 1190, in
op_keylist_next
errorcheck(gpgme.gpgme_op_keylist_next(self.wrapped, ptr))
File "/usr/lib/python3/dist-packages/gpg/errors.py", line 129, in errorcheck
raise GPGMEError(retval, extradata)
gpg.errors.GPGMEError: GPGME: Too many open files
```
[Where problems could occur]
`_gpgme_io_select` is pretty central to gpgme, so if something is
wrong the package will be pretty broken. On the other hand, that also
means any glaring problems are likely to be caught by the package's
test suite.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/2037595/+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 2039352] Re: Unigine Superposition 1.1 doesn't run and fills dmesg with: *ERROR* Not enough memory for command submission!
I reproduce the same issue if I just do:
```
DRI_PRIME=1 glxinfo -B
name of display: :1
```
Which means the fault happens when using the AMD FirePro S7150, NOT the
AMD Radeon PRO W7600.
Maybe for some reasons Unigine Superposition tries to use all GPUs
available?
So, the bug is now easier to reproduce, it is affecting the AMD FirePro
S7150, and a glxinfo is enough.
** Summary changed:
- Unigine Superposition 1.1 doesn't run and fills dmesg with: *ERROR* Not
enough memory for command submission!
+ OpenGL applications don't run on AMD FirePro S7150 and fills dmesg with:
*ERROR* Not enough memory for command submission!
** Description changed:
+ I first thought the Radeon PRO W7600 was affected, in fact the affected
+ GPU is the AMD FirePro S7150.
+
+ See comment 3 and below:
+ https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2039352/comments/3
+
+ __
+
When I run Unigine Superposition 1.1, it doesn't open any window and
dmesg is filled with:
```
[36881.961064] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
[36881.962579] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
[36881.963946] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
[36881.965556] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
[36881.967138] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
[36881.968522] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
```
printing new error log lines many time per second.
Killing the Unigine Superposition process stops the log printing.
There are more than one GPU in that system but the one used for
rendering is a Radeon PRO W7600:
```
Slot: 47:00.0
Class:VGA compatible controller [0300]
Vendor: Advanced Micro Devices, Inc. [AMD/ATI] [1002]
Device: Navi 33 [Radeon RX 7700S/7600/7600S/7600M XT/PRO W7600] [7480]
SVendor: Advanced Micro Devices, Inc. [AMD/ATI] [1002]
SDevice: Device [0e0d]
ProgIf: 00
Driver: amdgpu
Module: amdgpu
IOMMUGroup: 58
```
```
name of display: :1
display: :1 screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
Vendor: AMD (0x1002)
Device: AMD Radeon PRO W7600 (gfx1102, LLVM 15.0.7, DRM 3.54,
6.5.0-9-generic) (0x7480)
Version: 23.2.1
Accelerated: yes
Video memory: 8192MB
Unified memory: no
Preferred profile: core (0x1)
Max core profile version: 4.6
Max compat profile version: 4.6
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.2
```
Other games like Unvanquished or Quake II RTX are working correctly.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: libglapi-mesa 23.2.1-1ubuntu3
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompizPlugins:
[core,bailer,detection,composite,opengl,imgjpeg,compiztoolbox,copytex,decor,regex,snap,vpswitch,mousepoll,gnomecompat,titleinfo,imgpng,resize,animation,expo,ezoom,grid,place,move,imgsvg,workarounds,wall,session,thumbnail,staticswitcher,fade,scale]
CompositorRunning: None
CurrentDesktop: GNOME
Date: Sat Oct 14 14:58:23 2023
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
v4l2loopback/0.12.7, 6.5.0-9-generic, x86_64: installed (WARNING! Diff
between built and installed module!)
vhba/20211218, 6.2.0-33-generic, x86_64: installed
vhba/20211218, 6.5.0-9-generic, x86_64: installed
ExtraDebuggingInterest: Yes
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.5.0-9-generic
root=UUID=f35ecf77-511e-4dde-ac11-c1d848e97315 ro rootflags=subvol=@
amdgpu.si_support=1 radeon.si_support=0 amdgpu.cik_support=1
radeon.cik_support=0 amdgpu.exp_hw_support=1 amdgpu.gpu_recovery=1
amdgpu.ppfeaturemask=0x delayacct zswap.enabled=1
SourcePackage: mesa
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/08/2023
dmi.bios.release: 5.23
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: WRX80SU8-F6
dmi.board.asset.tag: Default string
dmi.board.name: Default string
dmi.board.vendor: Default string
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
[Touch-packages] [Bug 2039358] Re: Audio via bluetooth gets intermitent when a browser is started
worse with snap based browser -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2039358 Title: Audio via bluetooth gets intermitent when a browser is started Status in alsa-driver package in Ubuntu: New Bug description: listening to a fresh boot of mantic install .. sound works properly and bluetooh headphones/speaker connection is flawless.. starting a browser .. audio becomes choppy via bluetooth .. laptop speaker suffer no degradation.. occurs with kernels above 6.5.0-5 see bug 2038539 also.. (reported from a 6.5.0-5 kernel instance This report was added so a report from a 6.5.0-9 kernel instance is made ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: derk 1707 F wireplumber /dev/snd/controlC1: derk 1707 F wireplumber /dev/snd/seq:derk 1704 F pipewire CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Sat Oct 14 10:39:35 2023 InstallationDate: Installed on 2023-10-04 (10 days ago) InstallationMedia: Xubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20231004) PackageArchitecture: all PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: alsa-driver Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2023 dmi.bios.release: 1.21 dmi.bios.vendor: LENOVO dmi.bios.version: L9CN21WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76463 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad Slim 5 16ABR8 dmi.ec.firmware.release: 1.21 dmi.modalias: dmi:bvnLENOVO:bvrL9CN21WW:bd06/13/2023:br1.21:efr1.21:svnLENOVO:pn82XG:pvrIdeaPadSlim516ABR8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76463WIN:cvnLENOVO:ct10:cvrIdeaPadSlim516ABR8:skuLENOVO_MT_82XG_BU_idea_FM_IdeaPadSlim516ABR8: dmi.product.family: IdeaPad Slim 5 16ABR8 dmi.product.name: 82XG dmi.product.sku: LENOVO_MT_82XG_BU_idea_FM_IdeaPad Slim 5 16ABR8 dmi.product.version: IdeaPad Slim 5 16ABR8 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2039358/+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 2039358] [NEW] Audio via bluetooth gets intermitent when a browser is started
Public bug reported: listening to a fresh boot of mantic install .. sound works properly and bluetooh headphones/speaker connection is flawless.. starting a browser .. audio becomes choppy via bluetooth .. laptop speaker suffer no degradation.. occurs with kernels above 6.5.0-5 see bug 2038539 also.. (reported from a 6.5.0-5 kernel instance This report was added so a report from a 6.5.0-9 kernel instance is made ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: derk 1707 F wireplumber /dev/snd/controlC1: derk 1707 F wireplumber /dev/snd/seq:derk 1704 F pipewire CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Sat Oct 14 10:39:35 2023 InstallationDate: Installed on 2023-10-04 (10 days ago) InstallationMedia: Xubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20231004) PackageArchitecture: all PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: alsa-driver Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2023 dmi.bios.release: 1.21 dmi.bios.vendor: LENOVO dmi.bios.version: L9CN21WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76463 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad Slim 5 16ABR8 dmi.ec.firmware.release: 1.21 dmi.modalias: dmi:bvnLENOVO:bvrL9CN21WW:bd06/13/2023:br1.21:efr1.21:svnLENOVO:pn82XG:pvrIdeaPadSlim516ABR8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76463WIN:cvnLENOVO:ct10:cvrIdeaPadSlim516ABR8:skuLENOVO_MT_82XG_BU_idea_FM_IdeaPadSlim516ABR8: dmi.product.family: IdeaPad Slim 5 16ABR8 dmi.product.name: 82XG dmi.product.sku: LENOVO_MT_82XG_BU_idea_FM_IdeaPad Slim 5 16ABR8 dmi.product.version: IdeaPad Slim 5 16ABR8 dmi.sys.vendor: LENOVO ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2039358 Title: Audio via bluetooth gets intermitent when a browser is started Status in alsa-driver package in Ubuntu: New Bug description: listening to a fresh boot of mantic install .. sound works properly and bluetooh headphones/speaker connection is flawless.. starting a browser .. audio becomes choppy via bluetooth .. laptop speaker suffer no degradation.. occurs with kernels above 6.5.0-5 see bug 2038539 also.. (reported from a 6.5.0-5 kernel instance This report was added so a report from a 6.5.0-9 kernel instance is made ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: derk 1707 F wireplumber /dev/snd/controlC1: derk 1707 F wireplumber /dev/snd/seq:derk 1704 F pipewire CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Sat Oct 14 10:39:35 2023 InstallationDate: Installed on 2023-10-04 (10 days ago) InstallationMedia: Xubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20231004) PackageArchitecture: all PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: alsa-driver Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2023 dmi.bios.release: 1.21 dmi.bios.vendor: LENOVO dmi.bios.version: L9CN21WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76463 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad Slim 5 16ABR8 dmi.ec.firmware.release: 1.21 dmi.modalias: dmi:bvnLENOVO:bvrL9CN21WW:bd06/13/2023:br1.21:efr1.21:svnLENOVO:pn82XG:pvrIdeaPadSlim516ABR8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76463WIN:cvnLENOVO:ct10:cvrIdeaPadSlim516ABR8:skuLENOVO_MT_82XG_BU_idea_FM_IdeaPadSlim516ABR8: dmi.product.family: IdeaPad Slim 5 16ABR8 dmi.product.name: 82XG dmi.product.sku: LENOVO_MT_82XG_BU_idea_FM_IdeaPad Slim 5 16ABR8 dmi.product.version: IdeaPad Slim 5 16ABR8 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2039358/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to
[Touch-packages] [Bug 2039357] [NEW] Bluetooth headphones not detected properly
Public bug reported: On a fresh system boot, stereo Bluetooth headphones with a microphone that identify as WH-CH710N connect but provide no sound until Settings is used to pick the only microphone option, the headphones, whereupon sound immediately works. Thereafter, doing a sound Test reveals the headphones are considered mono, not stereo. Sound works, but periodically the Bluetooth connection halts the browser that's playing the sound and in about 10 seconds, Bluetooth disconnects then reconnects a short time later but with the original sound problem. The issue is with the Bluetooth detection. The symptom is no sound. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-86.96-generic 5.15.122 Uname: Linux 5.15.0-86-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bill 1876 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sat Oct 14 08:38:00 2023 InstallationDate: Installed on 2019-11-18 (1425 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: Upgraded to jammy on 2022-11-01 (346 days ago) dmi.bios.date: 09/21/2018 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0805 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX Z390-I GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0805:bd09/21/2018:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXZ390-IGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuASUS_MB_CNL: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2039357 Title: Bluetooth headphones not detected properly Status in alsa-driver package in Ubuntu: New Bug description: On a fresh system boot, stereo Bluetooth headphones with a microphone that identify as WH-CH710N connect but provide no sound until Settings is used to pick the only microphone option, the headphones, whereupon sound immediately works. Thereafter, doing a sound Test reveals the headphones are considered mono, not stereo. Sound works, but periodically the Bluetooth connection halts the browser that's playing the sound and in about 10 seconds, Bluetooth disconnects then reconnects a short time later but with the original sound problem. The issue is with the Bluetooth detection. The symptom is no sound. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-86.96-generic 5.15.122 Uname: Linux 5.15.0-86-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bill 1876 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sat Oct 14 08:38:00 2023 InstallationDate: Installed on 2019-11-18 (1425 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: Upgraded to jammy on 2022-11-01 (346 days ago) dmi.bios.date: 09/21/2018 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0805 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX Z390-I GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0805:bd09/21/2018:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXZ390-IGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuASUS_MB_CNL: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2039357/+subscriptions --
[Touch-packages] [Bug 2037595] Autopkgtest regression report (gpgme1.0/1.16.0-1.2ubuntu4.2)
All autopkgtests for the newly accepted gpgme1.0 (1.16.0-1.2ubuntu4.2) for
jammy have finished running.
The following regressions have been reported in tests triggered by the package:
samba/2:4.15.13+dfsg-0ubuntu1.5 (ppc64el)
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/jammy/update_excuses.html#gpgme1.0
[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 gpgme1.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2037595
Title:
_gpgme_io_select breaks when more than 1024 file descriptors are open
Status in gpgme1.0 package in Ubuntu:
Fix Released
Status in gpgme1.0 source package in Focal:
Fix Committed
Status in gpgme1.0 source package in Jammy:
Fix Committed
Bug description:
[Impact]
Launchpad's buildd-manager is a complex event-driven daemon that
manages several hundred builders on production. As such, it can often
end up with more than 1024 file descriptors open. It also uses gpgme
from time to time to fetch signing keys for PPAs when dispatching
builds that involve PPAs.
On focal (and also on jammy), this breaks because `_gpgme_io_select`
is implemented using select(2), whose manual page says: "WARNING:
select() can monitor only file descriptors numbers that are less than
FD_SETSIZE (1024)—an unreasonably low limit for many modern
applications—and this limitation will not change. All modern
applications should instead use poll(2) or epoll(7), which do not
suffer this limitation." This is exactly the limitation we're running
into, resulting in mysterious "Too many open files" errors despite
resource limits being set to more than comfortable values.
Fortunately, this was fixed upstream in https://git.gnupg.org/cgi-
bin/gitweb.cgi?p=gpgme.git;a=commitdiff;h=8148237cb4ae20755c06a44d71761c7030973c3d,
and lunar has that fix. focal and jammy do not (there may be a
similar problem with older LTSes too, but I only care about it back to
focal). buildd-manager currently runs on focal.
We've been running buildd-manager with a cherry-picked fix from
upstream for a few weeks now, and I'd like to get that SRUed back into
Ubuntu so that we don't accidentally lose this patch in the event of a
security update or similar.
[Test Plan]
William Grant provided this minimal reproducer:
```
root@tmp:~# python3
Python 3.8.10 (default, May 26 2023, 14:05:08)
[GCC 9.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import gpg
>>> c = gpg.Context()
>>> list(c.keylist())
[]
>>> fs = []
>>> for i in range(1024):
... fs.append(open('/dev/null'))
...
>>> list(c.keylist())
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/gpg/core.py", line 751, in keylist
key = self.op_keylist_next()
File "/usr/lib/python3/dist-packages/gpg/core.py", line 1195, in
op_keylist_next
raise excp
File "/usr/lib/python3/dist-packages/gpg/core.py", line 1190, in
op_keylist_next
errorcheck(gpgme.gpgme_op_keylist_next(self.wrapped, ptr))
File "/usr/lib/python3/dist-packages/gpg/errors.py", line 129, in errorcheck
raise GPGMEError(retval, extradata)
gpg.errors.GPGMEError: GPGME: Too many open files
```
[Where problems could occur]
`_gpgme_io_select` is pretty central to gpgme, so if something is
wrong the package will be pretty broken. On the other hand, that also
means any glaring problems are likely to be caught by the package's
test suite.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/2037595/+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 2034986] Re: some text became unreadable during a distribution upgrade
Since I propose yet another SRU, I created bug #2039356. This bug report is quite noisy already... My examination of the flavors with respect to this issue focused on two questions: 1. Does the u-r-u model effectively prevent 'the unreadable text issue' when the desktop font in use — whether default or set by the user — has changed during the cycle? After the changes proposed via bug #2039356 I would say "yes" for: Ubuntu Desktop Ubunu Budgie Ubuntu Cinnamon Ubuntu Kylin Ubuntu MATE Ubuntu Unity while the model (i.e. temporarily changing a dconf value which represents the desktop font) is not effective for: Kubuntu Lubuntu Xubuntu In case of Kubuntu and Lubuntu the Qt way of dealing with fonts seems to require something else, and the Xfce way applied in Xubuntu means similar difficulties. Fortunately all those flavors use a desktop font by default (Noto Sans) which was not changed during the cycle, so this does not need to be addressed for mantic. But if you like, you can trigger the 23.04 -> 23.10 upgrade issue in for instance Xubuntu: Go to Settings -> Appearance -> Fonts and change the "Default Font" from Noto Sans to Ubuntu. Doing so will be reflected both in the ~/.config/xfce4/xfconf/xfce-perchannel-xml/xsettings.xml file and in dconf (gsettings get org.gnome.desktop.interface font-name), but changing the font-name dconf value only to something else during upgrade (as we do) won't change the effective desktop font in Xubuntu, which results in 'the unreadable text issue'. 2. Is the temporary desktop font dconf value properly reset at next login after reboot? Yes it is, after the changes proposed via bug #2039356. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2034986 Title: some text became unreadable during a distribution upgrade Status in Cinnamon: New Status in Ubuntu MATE: New Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Fix Committed Status in ubuntu-release-upgrader source package in Jammy: Fix Committed Status in ubuntu-release-upgrader source package in Lunar: Fix Committed Status in ubuntu-meta source package in Mantic: Fix Released Status in ubuntu-release-upgrader source package in Mantic: Fix Committed Bug description: [ Impact ] * On Ubuntu Mate with the Lunar series, when running ubuntu-release-upgrader, the displayed font of running applications (including the upgrader) becomes very corrupted. * This is not just a display problem, it is also a functional one. The release upgrader will have text corrupted to the point where a dialog asks a decision, and displays two buttons, but the text is unreadable and one has to guess which button is the one that carries out their desired action. * In the early parts of the upgrader tool, users are told in bold: "To prevent data loss close all open applications and documents." This is just before the "Start Upgrade" button is available. But they may not do so. Many applications may have a corrupted font. * To address this, an additional environment variable is being passed along to pkexec, XDG_CURRENT_DESKTOP, as this is the critical criteria for making the Mate version of the fix work. * Also in the change are * an update to tests * from pre-build.sh * an update of the mirrors.cfg, adding and removing several mirrors * a refresh of the po files [ Test Plan ] * acquire an Ubuntu Mate environment running Ubuntu Lunar on amd64 * as user, run "update-manager -d" * monitor the "Distribution Upgrade" screen. During the "Installing the upgrades" step (and mind that this step will be long), observe the text of the "Distribution Upgrade" screen and verify that the font does not corrupt. * Repeat the above for Ubuntu Desktop [ Where problems could occur ] * We are changing, at release time, ubuntu-release upgrader. If we are careless, we could regress upgrades for a wider group of users than just Ubuntu Mate. That said, it is believed that passing the additional XDG_CURRENT_DESKTOP variable is relatively low risk. [ Other Info ] * TBD --- Original description: I was upgrading from Lunar to Mantic the other day and left a couple of applications open during the upgrade process. During the upgrade the text in audacious became unreadable (I'll attach a screenshot) and I seem to recall the title bar of Firefox being unreadable but the contents of web pages still being readable. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-release-upgrader-core 1:23.10.5 ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0 Uname: Linux 6.5.0-4-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion:
[Touch-packages] [Bug 2039352] Re: Unigine Superposition 1.1 doesn't run and fills dmesg with: *ERROR* Not enough memory for command submission!
** Description changed:
When I run Unigine Superposition 1.1, it doesn't open any window and
dmesg is filled with:
```
[36881.961064] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
[36881.962579] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
[36881.963946] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
[36881.965556] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
[36881.967138] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
[36881.968522] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
```
printing new error log lines many time per second.
Killing the Unigine Superposition process stops the log printing.
- There are more then one GPU in that system but the one used for
+ There are more than one GPU in that system but the one used for
rendering is a Radeon PRO W7600:
```
Slot: 47:00.0
Class:VGA compatible controller [0300]
Vendor: Advanced Micro Devices, Inc. [AMD/ATI] [1002]
Device: Navi 33 [Radeon RX 7700S/7600/7600S/7600M XT/PRO W7600] [7480]
SVendor: Advanced Micro Devices, Inc. [AMD/ATI] [1002]
SDevice: Device [0e0d]
ProgIf: 00
Driver: amdgpu
Module: amdgpu
IOMMUGroup: 58
```
```
name of display: :1
display: :1 screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
Vendor: AMD (0x1002)
Device: AMD Radeon PRO W7600 (gfx1102, LLVM 15.0.7, DRM 3.54,
6.5.0-9-generic) (0x7480)
Version: 23.2.1
Accelerated: yes
Video memory: 8192MB
Unified memory: no
Preferred profile: core (0x1)
Max core profile version: 4.6
Max compat profile version: 4.6
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.2
```
Other games like Unvanquished or Quake II RTX are working correctly.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: libglapi-mesa 23.2.1-1ubuntu3
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompizPlugins:
[core,bailer,detection,composite,opengl,imgjpeg,compiztoolbox,copytex,decor,regex,snap,vpswitch,mousepoll,gnomecompat,titleinfo,imgpng,resize,animation,expo,ezoom,grid,place,move,imgsvg,workarounds,wall,session,thumbnail,staticswitcher,fade,scale]
CompositorRunning: None
CurrentDesktop: GNOME
Date: Sat Oct 14 14:58:23 2023
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
v4l2loopback/0.12.7, 6.5.0-9-generic, x86_64: installed (WARNING! Diff
between built and installed module!)
vhba/20211218, 6.2.0-33-generic, x86_64: installed
vhba/20211218, 6.5.0-9-generic, x86_64: installed
ExtraDebuggingInterest: Yes
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.5.0-9-generic
root=UUID=f35ecf77-511e-4dde-ac11-c1d848e97315 ro rootflags=subvol=@
amdgpu.si_support=1 radeon.si_support=0 amdgpu.cik_support=1
radeon.cik_support=0 amdgpu.exp_hw_support=1 amdgpu.gpu_recovery=1
amdgpu.ppfeaturemask=0x delayacct zswap.enabled=1
SourcePackage: mesa
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/08/2023
dmi.bios.release: 5.23
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: WRX80SU8-F6
dmi.board.asset.tag: Default string
dmi.board.name: Default string
dmi.board.vendor: Default string
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrWRX80SU8-F6:bd06/08/2023:br5.23:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: Default string
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Default string
modified.conffile..etc.default.apport: [modified]
mtime.conffile..etc.default.apport: 2018-06-16T17:39:00.798346
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
[Touch-packages] [Bug 2039352] Re: Unigine Superposition 1.1 doesn't run and fill dmesg with: *ERROR* Not enough memory for command submission!
In the log file you may see notice of some amdgpu-pro OpenCL components
like ROCm ROCr OpenCL or Legacy Orca OpenCL, there is no amdgpu-pro
OpenGL or dkms module installed though. Removing entirely the amdgpu-pro
OpenCL packages produce the same bug anyway. The contrary would have
been surprising since I assume Superposition to be an OpenGL benchmark
and to not make use of OpenCL, but to be 100% sure I removed all those
amdgpu-pro packages and I get the same bug with stock Ubuntu anyway.
** Summary changed:
- Unigine Superposition 1.1 doesn't run and fill dmesg with: *ERROR* Not enough
memory for command submission!
+ Unigine Superposition 1.1 doesn't run and fills dmesg with: *ERROR* Not
enough memory for command submission!
** Description changed:
When I run Unigine Superposition 1.1, it doesn't open any window and
dmesg is filled with:
```
[36881.961064] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
[36881.962579] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
[36881.963946] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
[36881.965556] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
[36881.967138] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
[36881.968522] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
```
printing new error log lines many time per second.
Killing the Unigine Superposition process stops the log printing.
- There is multiple GPU in that system but the one used for rendering is a
- Radeon PRO W7600:
-
+ There are more then one GPU in that system but the one used for
+ rendering is a Radeon PRO W7600:
```
Slot: 47:00.0
Class:VGA compatible controller [0300]
Vendor: Advanced Micro Devices, Inc. [AMD/ATI] [1002]
Device: Navi 33 [Radeon RX 7700S/7600/7600S/7600M XT/PRO W7600] [7480]
SVendor: Advanced Micro Devices, Inc. [AMD/ATI] [1002]
SDevice: Device [0e0d]
ProgIf: 00
Driver: amdgpu
Module: amdgpu
IOMMUGroup: 58
```
```
name of display: :1
display: :1 screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
- Vendor: AMD (0x1002)
- Device: AMD Radeon PRO W7600 (gfx1102, LLVM 15.0.7, DRM 3.54,
6.5.0-9-generic) (0x7480)
- Version: 23.2.1
- Accelerated: yes
- Video memory: 8192MB
- Unified memory: no
- Preferred profile: core (0x1)
- Max core profile version: 4.6
- Max compat profile version: 4.6
- Max GLES1 profile version: 1.1
- Max GLES[23] profile version: 3.2
+ Vendor: AMD (0x1002)
+ Device: AMD Radeon PRO W7600 (gfx1102, LLVM 15.0.7, DRM 3.54,
6.5.0-9-generic) (0x7480)
+ Version: 23.2.1
+ Accelerated: yes
+ Video memory: 8192MB
+ Unified memory: no
+ Preferred profile: core (0x1)
+ Max core profile version: 4.6
+ Max compat profile version: 4.6
+ Max GLES1 profile version: 1.1
+ Max GLES[23] profile version: 3.2
```
Other games like Unvanquished or Quake II RTX are working correctly.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: libglapi-mesa 23.2.1-1ubuntu3
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompizPlugins:
[core,bailer,detection,composite,opengl,imgjpeg,compiztoolbox,copytex,decor,regex,snap,vpswitch,mousepoll,gnomecompat,titleinfo,imgpng,resize,animation,expo,ezoom,grid,place,move,imgsvg,workarounds,wall,session,thumbnail,staticswitcher,fade,scale]
CompositorRunning: None
CurrentDesktop: GNOME
Date: Sat Oct 14 14:58:23 2023
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
- v4l2loopback/0.12.7, 6.5.0-9-generic, x86_64: installed (WARNING! Diff
between built and installed module!)
- vhba/20211218, 6.2.0-33-generic, x86_64: installed
- vhba/20211218, 6.5.0-9-generic, x86_64: installed
+ v4l2loopback/0.12.7, 6.5.0-9-generic, x86_64: installed (WARNING! Diff
between built and installed module!)
+ vhba/20211218, 6.2.0-33-generic, x86_64: installed
+ vhba/20211218, 6.5.0-9-generic, x86_64: installed
ExtraDebuggingInterest: Yes
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.5.0-9-generic
root=UUID=f35ecf77-511e-4dde-ac11-c1d848e97315 ro rootflags=subvol=@
amdgpu.si_support=1 radeon.si_support=0 amdgpu.cik_support=1
radeon.cik_support=0 amdgpu.exp_hw_support=1 amdgpu.gpu_recovery=1
amdgpu.ppfeaturemask=0x delayacct zswap.enabled=1
SourcePackage: mesa
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/08/2023
[Touch-packages] [Bug 2039352] [NEW] Unigine Superposition 1.1 doesn't run and fill dmesg with: *ERROR* Not enough memory for command submission!
Public bug reported:
When I run Unigine Superposition 1.1, it doesn't open any window and
dmesg is filled with:
```
[36881.961064] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
[36881.962579] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
[36881.963946] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
[36881.965556] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
[36881.967138] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
[36881.968522] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
```
printing new error log lines many time per second.
Killing the Unigine Superposition process stops the log printing.
There is multiple GPU in that system but the one used for rendering is a
Radeon PRO W7600:
```
Slot: 47:00.0
Class: VGA compatible controller [0300]
Vendor: Advanced Micro Devices, Inc. [AMD/ATI] [1002]
Device: Navi 33 [Radeon RX 7700S/7600/7600S/7600M XT/PRO W7600] [7480]
SVendor:Advanced Micro Devices, Inc. [AMD/ATI] [1002]
SDevice:Device [0e0d]
ProgIf: 00
Driver: amdgpu
Module: amdgpu
IOMMUGroup: 58
```
```
name of display: :1
display: :1 screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
Vendor: AMD (0x1002)
Device: AMD Radeon PRO W7600 (gfx1102, LLVM 15.0.7, DRM 3.54,
6.5.0-9-generic) (0x7480)
Version: 23.2.1
Accelerated: yes
Video memory: 8192MB
Unified memory: no
Preferred profile: core (0x1)
Max core profile version: 4.6
Max compat profile version: 4.6
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.2
```
Other games like Unvanquished or Quake II RTX are working correctly.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: libglapi-mesa 23.2.1-1ubuntu3
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompizPlugins:
[core,bailer,detection,composite,opengl,imgjpeg,compiztoolbox,copytex,decor,regex,snap,vpswitch,mousepoll,gnomecompat,titleinfo,imgpng,resize,animation,expo,ezoom,grid,place,move,imgsvg,workarounds,wall,session,thumbnail,staticswitcher,fade,scale]
CompositorRunning: None
CurrentDesktop: GNOME
Date: Sat Oct 14 14:58:23 2023
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
v4l2loopback/0.12.7, 6.5.0-9-generic, x86_64: installed (WARNING! Diff between
built and installed module!)
vhba/20211218, 6.2.0-33-generic, x86_64: installed
vhba/20211218, 6.5.0-9-generic, x86_64: installed
ExtraDebuggingInterest: Yes
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.5.0-9-generic
root=UUID=f35ecf77-511e-4dde-ac11-c1d848e97315 ro rootflags=subvol=@
amdgpu.si_support=1 radeon.si_support=0 amdgpu.cik_support=1
radeon.cik_support=0 amdgpu.exp_hw_support=1 amdgpu.gpu_recovery=1
amdgpu.ppfeaturemask=0x delayacct zswap.enabled=1
SourcePackage: mesa
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/08/2023
dmi.bios.release: 5.23
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: WRX80SU8-F6
dmi.board.asset.tag: Default string
dmi.board.name: Default string
dmi.board.vendor: Default string
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrWRX80SU8-F6:bd06/08/2023:br5.23:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: Default string
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Default string
modified.conffile..etc.default.apport: [modified]
mtime.conffile..etc.default.apport: 2018-06-16T17:39:00.798346
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1
** Affects: mesa (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug mantic ubuntu
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa
[Touch-packages] [Bug 1451103] Re: ubuntu-standard depends on cron
systemd-cron 2;x with it's C++ rewrite in pretty good shape, could be Ubuntu default cron even for 24.04 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1451103 Title: ubuntu-standard depends on cron Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: ubuntu-standard have a hardcoded dependency on cron package. Instead it should depend on systemd-cron to decrease learning curve for new users and simplify system maintenance: it's much easier if periodic tasks are administered the same way as all other tasks - via standard units. People who need legacy software for some reason could easily install it from the repository. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1451103/+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 2038453] Autopkgtest regression report (apt/2.4.11)
All autopkgtests for the newly accepted apt (2.4.11) for jammy have finished running. The following regressions have been reported in tests triggered by the package: apt/2.4.11 (armhf) sbuild/0.81.2ubuntu6 (arm64, ppc64el, s390x) 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/jammy/update_excuses.html#apt [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 apt in Ubuntu. https://bugs.launchpad.net/bugs/2038453 Title: [SRU] apt snapshot integration backport Status in Ubuntu Pro: Triaged Status in Ubuntu Pro 18.04 series: Triaged Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: Won't Fix Status in apt source package in Focal: Fix Committed Status in apt source package in Jammy: Fix Committed Status in apt source package in Lunar: Won't Fix Status in apt source package in Mantic: Fix Released Bug description: [Impact] The snapshot service provides users access to older states of the archive with ease of use, and enables a consistent user experience across all supported releases, as otherwise users would have to rewrite their sources.list to make use of snapshots and set up pinning; hence partners requested the feature be SRUed to older releases as well. [Test plan] The complete regression test suite in autopkgtests includes an automatic test case for this and the known limitations that have been fixed. Aside from that, it is also worthwhile to do an end-to-end test: Configure snapshot=yes for Ubuntu sources in your sources.list and 1. run apt update - it should not use snapshot 2. run apt update --snapshot 20231001T00Z, it should download the snapshot 3. run apt policy --snapshot 20231001T00Z hello, it should show hello in the snapshot 4. run apt install --snapshot 20231001T00Z hello, it should install hello from the snapshot 5. Run apt update; observe snapshot not being downloaded 6. Observe snapshots are gone from /var/lib/apt/lists again [Where problems could occur] The integration has been purposefully limited in how it works to reduce the impact it has on the APT code; hence it was possible to cherry-pick this into 22.04, 20.04, and even 18.04, with only a minor editorial change. This significantly limits the risk. This feature is only enabled for sources with snapshot=yes (.list) or Snapshot: yes (.sources) or other truthy values apt recognizes. Most users will not have such entries as they did not have an APT supporting it. This combined should ensure that users do not experience any regressions. However the feature may be lacking in some ways that we may want to address in follow up SRUs; it has not been used in the wild a lot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-pro/+bug/2038453/+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 2039342] [NEW] package linux-image-6.5.0-1005-raspi 6.5.0-1005.7 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: This happened during the upgrade. ProblemType: Package DistroRelease: Ubuntu 23.10 Package: linux-image-6.5.0-1005-raspi 6.5.0-1005.7 ProcVersionSignature: Ubuntu 6.2.0-1014.16-raspi 6.2.16 Uname: Linux 6.2.0-1014-raspi aarch64 ApportVersion: 2.27.0-0ubuntu5 Architecture: arm64 CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: CloudSubPlatform: config-disk (/dev/sdb1) Date: Sat Oct 14 09:07:02 2023 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 ImageMediaBuild: 20210201.1 Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.22.0ubuntu1 apt 2.7.3 SourcePackage: initramfs-tools Title: package linux-image-6.5.0-1005-raspi 6.5.0-1005.7 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to mantic on 2023-10-14 (0 days ago) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package arm64 arm64-image cloud-image mantic need-duplicate-check raspi-image -- 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/2039342 Title: package linux-image-6.5.0-1005-raspi 6.5.0-1005.7 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: This happened during the upgrade. ProblemType: Package DistroRelease: Ubuntu 23.10 Package: linux-image-6.5.0-1005-raspi 6.5.0-1005.7 ProcVersionSignature: Ubuntu 6.2.0-1014.16-raspi 6.2.16 Uname: Linux 6.2.0-1014-raspi aarch64 ApportVersion: 2.27.0-0ubuntu5 Architecture: arm64 CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: CloudSubPlatform: config-disk (/dev/sdb1) Date: Sat Oct 14 09:07:02 2023 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 ImageMediaBuild: 20210201.1 Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.22.0ubuntu1 apt 2.7.3 SourcePackage: initramfs-tools Title: package linux-image-6.5.0-1005-raspi 6.5.0-1005.7 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to mantic on 2023-10-14 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2039342/+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 2039340] Re: On upgrade from 23.04 to 23.10, cannot login using Gnome or Ubuntu WM entries
2023-10-14T01:44:00.468542-04:00 anadon gdm-password]: pam_unix(gdm-password:session): session opened for user anadon(uid=1000) by (uid=0) 2023-10-14T01:44:00.473683-04:00 anadon systemd-logind[1169]: New session 6 of user anadon. 2023-10-14T01:44:00.522860-04:00 anadon (systemd): pam_unix(systemd-user:session): session opened for user anadon(uid=1000) by (uid=0) 2023-10-14T01:44:00.658692-04:00 anadon gdm-password]: gkr-pam: unlocked login keyring 2023-10-14T01:44:01.673108-04:00 anadon gnome-keyring-daemon[3237]: The PKCS#11 component was already initialized 2023-10-14T01:44:01.673392-04:00 anadon gnome-keyring-daemon[3560]: discover_other_daemon: 1 2023-10-14T01:44:01.674538-04:00 anadon gnome-keyring-daemon[3237]: The Secret Service was already initialized 2023-10-14T01:44:01.674742-04:00 anadon gnome-keyring-daemon[3562]: discover_other_daemon: 1 2023-10-14T01:44:01.677463-04:00 anadon gnome-keyring-daemon[3563]: discover_other_daemon: 1 2023-10-14T01:44:09.242277-04:00 anadon PackageKit: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0) 2023-10-14T01:44:09.243637-04:00 anadon PackageKit: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh 2023-10-14T01:44:10.632860-04:00 anadon gdm-password]: pam_unix(gdm-password:session): session closed for user anadon 2023-10-14T01:44:10.643754-04:00 anadon systemd-logind[1169]: Session 6 logged out. Waiting for processes to exit. 2023-10-14T01:44:10.644366-04:00 anadon systemd-logind[1169]: Removed session 6. This appears to show a successful login with gdm. So if launching the graphical session fails afterwards, that must be an issue with gdm or some other downstream component. Reassigning. ** Package changed: pam (Ubuntu) => gdm3 (Ubuntu) ** Changed in: gdm3 (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2039340 Title: On upgrade from 23.04 to 23.10, cannot login using Gnome or Ubuntu WM entries Status in Ubuntu: New Status in apparmor package in Ubuntu: New Status in gdm3 package in Ubuntu: New Bug description: Last time I hacked around a bug like this, it had portions in PAM, apparmor, Seahorse, and Gnome so this time I'd like someone more focused on broad stability to look at things. The problem is simple. Before the upgrade to 23.10, I could log in using the "Ubuntu", "Ubuntu on X.org". "Gnome", and "Gnome on X.org" WMs. Now I can't. I can still login using XFCE and TTY. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2039340/+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 2039340] Re: On upgrade from 23.04 to 23.10, cannot login using Gnome or Ubuntu WM entries
There is some funky stuff going on in auth.log. I go to log in, enter my password, it starts the process, then lands me back at the gdm login screen after a second. ** Attachment added: "auth.log" https://bugs.launchpad.net/ubuntu/+source/pam/+bug/2039340/+attachment/5709366/+files/auth.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/2039340 Title: On upgrade from 23.04 to 23.10, cannot login using Gnome or Ubuntu WM entries Status in Ubuntu: New Status in apparmor package in Ubuntu: New Status in pam package in Ubuntu: Incomplete Bug description: Last time I hacked around a bug like this, it had portions in PAM, apparmor, Seahorse, and Gnome so this time I'd like someone more focused on broad stability to look at things. The problem is simple. Before the upgrade to 23.10, I could log in using the "Ubuntu", "Ubuntu on X.org". "Gnome", and "Gnome on X.org" WMs. Now I can't. I can still login using XFCE and TTY. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2039340/+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 2038453] Please test proposed package
Hello Julian, or anyone else affected, Accepted apt into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/2.0.10 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/2038453 Title: [SRU] apt snapshot integration backport Status in Ubuntu Pro: Triaged Status in Ubuntu Pro 18.04 series: Triaged Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: Won't Fix Status in apt source package in Focal: Fix Committed Status in apt source package in Jammy: Fix Committed Status in apt source package in Lunar: Won't Fix Status in apt source package in Mantic: Fix Released Bug description: [Impact] The snapshot service provides users access to older states of the archive with ease of use, and enables a consistent user experience across all supported releases, as otherwise users would have to rewrite their sources.list to make use of snapshots and set up pinning; hence partners requested the feature be SRUed to older releases as well. [Test plan] The complete regression test suite in autopkgtests includes an automatic test case for this and the known limitations that have been fixed. Aside from that, it is also worthwhile to do an end-to-end test: Configure snapshot=yes for Ubuntu sources in your sources.list and 1. run apt update - it should not use snapshot 2. run apt update --snapshot 20231001T00Z, it should download the snapshot 3. run apt policy --snapshot 20231001T00Z hello, it should show hello in the snapshot 4. run apt install --snapshot 20231001T00Z hello, it should install hello from the snapshot 5. Run apt update; observe snapshot not being downloaded 6. Observe snapshots are gone from /var/lib/apt/lists again [Where problems could occur] The integration has been purposefully limited in how it works to reduce the impact it has on the APT code; hence it was possible to cherry-pick this into 22.04, 20.04, and even 18.04, with only a minor editorial change. This significantly limits the risk. This feature is only enabled for sources with snapshot=yes (.list) or Snapshot: yes (.sources) or other truthy values apt recognizes. Most users will not have such entries as they did not have an APT supporting it. This combined should ensure that users do not experience any regressions. However the feature may be lacking in some ways that we may want to address in follow up SRUs; it has not been used in the wild a lot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-pro/+bug/2038453/+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 2038453] Re: [SRU] apt snapshot integration backport
Hello Julian, or anyone else affected, Accepted apt into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/2.4.11 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: apt (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-jammy ** Changed in: apt (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/2038453 Title: [SRU] apt snapshot integration backport Status in Ubuntu Pro: Triaged Status in Ubuntu Pro 18.04 series: Triaged Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: Won't Fix Status in apt source package in Focal: Fix Committed Status in apt source package in Jammy: Fix Committed Status in apt source package in Lunar: Won't Fix Status in apt source package in Mantic: Fix Released Bug description: [Impact] The snapshot service provides users access to older states of the archive with ease of use, and enables a consistent user experience across all supported releases, as otherwise users would have to rewrite their sources.list to make use of snapshots and set up pinning; hence partners requested the feature be SRUed to older releases as well. [Test plan] The complete regression test suite in autopkgtests includes an automatic test case for this and the known limitations that have been fixed. Aside from that, it is also worthwhile to do an end-to-end test: Configure snapshot=yes for Ubuntu sources in your sources.list and 1. run apt update - it should not use snapshot 2. run apt update --snapshot 20231001T00Z, it should download the snapshot 3. run apt policy --snapshot 20231001T00Z hello, it should show hello in the snapshot 4. run apt install --snapshot 20231001T00Z hello, it should install hello from the snapshot 5. Run apt update; observe snapshot not being downloaded 6. Observe snapshots are gone from /var/lib/apt/lists again [Where problems could occur] The integration has been purposefully limited in how it works to reduce the impact it has on the APT code; hence it was possible to cherry-pick this into 22.04, 20.04, and even 18.04, with only a minor editorial change. This significantly limits the risk. This feature is only enabled for sources with snapshot=yes (.list) or Snapshot: yes (.sources) or other truthy values apt recognizes. Most users will not have such entries as they did not have an APT supporting it. This combined should ensure that users do not experience any regressions. However the feature may be lacking in some ways that we may want to address in follow up SRUs; it has not been used in the wild a lot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-pro/+bug/2038453/+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 2039340] Re: On upgrade from 23.04 to 23.10, cannot login using Gnome or Ubuntu WM entries
What is the behavior when you try to log in? Do you get an authentication failure message, or does it appear there is a successful login followed by a screen flicker and a return to the login screen? Are there failure messages in /var/log/auth.log? ** Changed in: pam (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/2039340 Title: On upgrade from 23.04 to 23.10, cannot login using Gnome or Ubuntu WM entries Status in Ubuntu: New Status in apparmor package in Ubuntu: New Status in pam package in Ubuntu: Incomplete Bug description: Last time I hacked around a bug like this, it had portions in PAM, apparmor, Seahorse, and Gnome so this time I'd like someone more focused on broad stability to look at things. The problem is simple. Before the upgrade to 23.10, I could log in using the "Ubuntu", "Ubuntu on X.org". "Gnome", and "Gnome on X.org" WMs. Now I can't. I can still login using XFCE and TTY. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2039340/+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 2037595] Please test proposed package
Hello Colin, or anyone else affected,
Accepted gpgme1.0 into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/gpgme1.0/1.13.1-7ubuntu2.2 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gpgme1.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2037595
Title:
_gpgme_io_select breaks when more than 1024 file descriptors are open
Status in gpgme1.0 package in Ubuntu:
Fix Released
Status in gpgme1.0 source package in Focal:
Fix Committed
Status in gpgme1.0 source package in Jammy:
Fix Committed
Bug description:
[Impact]
Launchpad's buildd-manager is a complex event-driven daemon that
manages several hundred builders on production. As such, it can often
end up with more than 1024 file descriptors open. It also uses gpgme
from time to time to fetch signing keys for PPAs when dispatching
builds that involve PPAs.
On focal (and also on jammy), this breaks because `_gpgme_io_select`
is implemented using select(2), whose manual page says: "WARNING:
select() can monitor only file descriptors numbers that are less than
FD_SETSIZE (1024)—an unreasonably low limit for many modern
applications—and this limitation will not change. All modern
applications should instead use poll(2) or epoll(7), which do not
suffer this limitation." This is exactly the limitation we're running
into, resulting in mysterious "Too many open files" errors despite
resource limits being set to more than comfortable values.
Fortunately, this was fixed upstream in https://git.gnupg.org/cgi-
bin/gitweb.cgi?p=gpgme.git;a=commitdiff;h=8148237cb4ae20755c06a44d71761c7030973c3d,
and lunar has that fix. focal and jammy do not (there may be a
similar problem with older LTSes too, but I only care about it back to
focal). buildd-manager currently runs on focal.
We've been running buildd-manager with a cherry-picked fix from
upstream for a few weeks now, and I'd like to get that SRUed back into
Ubuntu so that we don't accidentally lose this patch in the event of a
security update or similar.
[Test Plan]
William Grant provided this minimal reproducer:
```
root@tmp:~# python3
Python 3.8.10 (default, May 26 2023, 14:05:08)
[GCC 9.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import gpg
>>> c = gpg.Context()
>>> list(c.keylist())
[]
>>> fs = []
>>> for i in range(1024):
... fs.append(open('/dev/null'))
...
>>> list(c.keylist())
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/gpg/core.py", line 751, in keylist
key = self.op_keylist_next()
File "/usr/lib/python3/dist-packages/gpg/core.py", line 1195, in
op_keylist_next
raise excp
File "/usr/lib/python3/dist-packages/gpg/core.py", line 1190, in
op_keylist_next
errorcheck(gpgme.gpgme_op_keylist_next(self.wrapped, ptr))
File "/usr/lib/python3/dist-packages/gpg/errors.py", line 129, in errorcheck
raise GPGMEError(retval, extradata)
gpg.errors.GPGMEError: GPGME: Too many open files
```
[Where problems could occur]
`_gpgme_io_select` is pretty central to gpgme, so if something is
wrong the package will be pretty broken. On the other hand, that also
means any glaring problems are likely to be caught by the package's
test suite.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/2037595/+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 2037595] Re: _gpgme_io_select breaks when more than 1024 file descriptors are open
Hello Colin, or anyone else affected,
Accepted gpgme1.0 into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/gpgme1.0/1.16.0-1.2ubuntu4.2 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: gpgme1.0 (Ubuntu Jammy)
Status: In Progress => Fix Committed
** Tags added: verification-needed verification-needed-jammy
** Changed in: gpgme1.0 (Ubuntu Focal)
Status: In Progress => Fix Committed
** Tags added: verification-needed-focal
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gpgme1.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2037595
Title:
_gpgme_io_select breaks when more than 1024 file descriptors are open
Status in gpgme1.0 package in Ubuntu:
Fix Released
Status in gpgme1.0 source package in Focal:
Fix Committed
Status in gpgme1.0 source package in Jammy:
Fix Committed
Bug description:
[Impact]
Launchpad's buildd-manager is a complex event-driven daemon that
manages several hundred builders on production. As such, it can often
end up with more than 1024 file descriptors open. It also uses gpgme
from time to time to fetch signing keys for PPAs when dispatching
builds that involve PPAs.
On focal (and also on jammy), this breaks because `_gpgme_io_select`
is implemented using select(2), whose manual page says: "WARNING:
select() can monitor only file descriptors numbers that are less than
FD_SETSIZE (1024)—an unreasonably low limit for many modern
applications—and this limitation will not change. All modern
applications should instead use poll(2) or epoll(7), which do not
suffer this limitation." This is exactly the limitation we're running
into, resulting in mysterious "Too many open files" errors despite
resource limits being set to more than comfortable values.
Fortunately, this was fixed upstream in https://git.gnupg.org/cgi-
bin/gitweb.cgi?p=gpgme.git;a=commitdiff;h=8148237cb4ae20755c06a44d71761c7030973c3d,
and lunar has that fix. focal and jammy do not (there may be a
similar problem with older LTSes too, but I only care about it back to
focal). buildd-manager currently runs on focal.
We've been running buildd-manager with a cherry-picked fix from
upstream for a few weeks now, and I'd like to get that SRUed back into
Ubuntu so that we don't accidentally lose this patch in the event of a
security update or similar.
[Test Plan]
William Grant provided this minimal reproducer:
```
root@tmp:~# python3
Python 3.8.10 (default, May 26 2023, 14:05:08)
[GCC 9.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import gpg
>>> c = gpg.Context()
>>> list(c.keylist())
[]
>>> fs = []
>>> for i in range(1024):
... fs.append(open('/dev/null'))
...
>>> list(c.keylist())
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/gpg/core.py", line 751, in keylist
key = self.op_keylist_next()
File "/usr/lib/python3/dist-packages/gpg/core.py", line 1195, in
op_keylist_next
raise excp
File "/usr/lib/python3/dist-packages/gpg/core.py", line 1190, in
op_keylist_next
errorcheck(gpgme.gpgme_op_keylist_next(self.wrapped, ptr))
File "/usr/lib/python3/dist-packages/gpg/errors.py", line 129, in errorcheck
raise GPGMEError(retval, extradata)
gpg.errors.GPGMEError: GPGME: Too many open files
```
[Where problems could occur]
`_gpgme_io_select` is pretty central to gpgme, so if something is
wrong the package will be pretty broken. On the other hand, that also
means any glaring problems are likely to be caught by the package's
test suite.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/2037595/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to :
[Touch-packages] [Bug 2039340] Re: On upgrade from 23.04 to 23.10, cannot login using Gnome or Ubuntu WM entries
** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+bug/2039340/+attachment/5709363/+files/dmesg.txt ** Also affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Also affects: pam (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2039340 Title: On upgrade from 23.04 to 23.10, cannot login using Gnome or Ubuntu WM entries Status in Ubuntu: New Status in apparmor package in Ubuntu: New Status in pam package in Ubuntu: New Bug description: Last time I hacked around a bug like this, it had portions in PAM, apparmor, Seahorse, and Gnome so this time I'd like someone more focused on broad stability to look at things. The problem is simple. Before the upgrade to 23.10, I could log in using the "Ubuntu", "Ubuntu on X.org". "Gnome", and "Gnome on X.org" WMs. Now I can't. I can still login using XFCE and TTY. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2039340/+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
