[Touch-packages] [Bug 2042749] Re: apt does not work with given convig files in new format
As the documentation says, the file name must end in .sources ** Changed in: apt (Ubuntu) Status: New => Won't Fix ** Changed in: apt (Ubuntu) Status: Won't Fix => Invalid -- 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/2042749 Title: apt does not work with given convig files in new format Status in apt package in Ubuntu: Invalid Bug description: assume /etc/apt/sources.list.d/somerepo.list: Types: deb URIs: https://repo.vivaldi.com/stable/deb/ Suites: stable Components: main Architectures: amd64 Signed-By: /etc/apt/trusted.gpg.d/33EAAB8E.gpg /etc/apt/trusted.gpg.d/4218647E.gpg Then 'apt update' will produce: # apt update E: Type 'Types:' is not known on line 4 in source list /etc/apt/sources.list.d/vivaldi.list E: The list of sources could not be read. A new apt version is available. Would be nice to upgrade. At the moment "man sources.list" does describe a file format not accepted by apt in sources.list-files. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: apt 2.7.3 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Sat Nov 4 23:51:50 2023 InstallationDate: Installed on 2021-12-11 (693 days ago) InstallationMedia: Xubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcEnviron: LANG=de_DE.UTF-8 LANGUAGE=de_DE PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2042749/+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 2042756] [NEW] package systemd 252.5-2ubuntu3.2 failed to install/upgrade: installed systemd package post-installation script subprocess returned error exit status 1
Public bug reported: I encountered the following while upgrading to lunar, which asked me to file here: ``` /etc/gshadow: Group "nogroup" already exists. dpkg: error processing package systemd (--configure): installed systemd package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: systemd needrestart is being skipped since dpkg has failed packages have been installed but needrestart is suspended ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/systemd.0.crash' packages have been installed but needrestart is suspended Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) ``` ProblemType: Package DistroRelease: Ubuntu 22.04 Package: systemd 252.5-2ubuntu3.2 ProcVersionSignature: Ubuntu 5.15.0-88.98-generic 5.15.126 Uname: Linux 5.15.0-88-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config Date: Sun Nov 5 04:08:26 2023 ErrorMessage: installed systemd package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-10-19 (16 days ago) InstallationMedia: Ubuntu-Server 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230217.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0cf3:3004 Qualcomm Atheros Communications AR3012 Bluetooth 4.0 Bus 001 Device 003: ID 0403:6001 Future Technology Devices International, Ltd FT232 Serial (UART) IC Bus 001 Device 004: ID 413c:2107 Dell Computer Corp. KB212-B Quiet Key Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Protectli VP4650 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-88-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.10 SourcePackage: systemd SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. Title: package systemd 252.5-2ubuntu3.2 failed to install/upgrade: installed systemd package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2023-11-05 (0 days ago) dmi.bios.date: 12/08/2022 dmi.bios.release: 1.0 dmi.bios.vendor: 3mdeb dmi.bios.version: Dasharo (coreboot+UEFI) v1.0.19 dmi.board.name: VP4650 dmi.board.vendor: Protectli dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: Protectli dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvn3mdeb:bvrDasharo(coreboot+UEFI)v1.0.19:bd12/08/2022:br1.0:efr0.0:svnProtectli:pnVP4650:pvr1.0:rvnProtectli:rnVP4650:rvr1.0:cvnProtectli:ct3:cvr:sku: dmi.product.family: Vault Pro dmi.product.name: VP4650 dmi.product.version: 1.0 dmi.sys.vendor: Protectli ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy need-duplicate-check third-party-packages uec-images -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2042756 Title: package systemd 252.5-2ubuntu3.2 failed to install/upgrade: installed systemd package post-installation script subprocess returned error exit status 1 Status in systemd package in Ubuntu: New Bug description: I encountered the following while upgrading to lunar, which asked me to file here: ``` /etc/gshadow: Group "nogroup" already exists. dpkg: error processing package systemd (--configure): installed systemd package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: systemd needrestart is being skipped since dpkg has failed packages have been installed but needrestart is suspended ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/systemd.0.crash' packages have been installed but needrestart is suspended Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) ``` ProblemType: Package DistroRelease: Ubuntu 22.04 Package: systemd 252.5-2ubuntu3.2 ProcVersionSignature: Ubuntu 5.15.0-88.98-generic 5.15.126 Uname: Linux 5.15.0-88-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config Date: Sun Nov 5 04:08:26 2023 ErrorMessage: installed systemd package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-10-19 (16 days ago)
Re: [Touch-packages] [Bug 1951491] Re: Can't run snaps: .slice/session-1.scope is not a snap cgroup
it is more that systemd is not setup properly rather than snaps, but snaps assume systemd cgroup is set up when other applications are not so fussy. systemd-oomd also relies on cgroups and I wonder if it is broken too. Anyway, the root cause of this is not snaps, but rather, snaps expose a bug which has occurred before the graphical session even starts. The DBUS_SESSION_BUS_ADDRESS is supposed to be set in the login process, way before the graphical session starts,,so my own amateur investigations agree with yours. There is a promise relating to the systemd "pam" login steps which do this, and I guess our broken logins skip this, but there are so many scripts involved that it hard to work out. It seems plausible that this is relatively recent change to the login process which old tools with custom login approaches have not been adapted to This is why I concluded that the problem that people are having is related to the way the login is done by their remote access tool, be it nomachine in my case or x2go or the vnc connections that first spawn a login (some types of remote access simply connect to an existing session and these would be immune from our problem). However, I'm just repeating myself, and likewise I will no doubt get more angry replies from people who believe this is a snap bug and are frustrated about the snap developers ignoring it. On Sun, 5 Nov 2023 at 09:55, Richard Brooksby <1951...@bugs.launchpad.net> wrote: > Some clues: > > If I start Ubuntu 22 with kernel argument `systemd.unit=multi- > user.target` (i.e. non-graphical) then start Wayland with > `XDG_SESSION_TYPE=wayland dbus-run-session gnome-session` then > DBUS_SESSION_BUS_ADDRESS gets set to something like > "DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus- > mcSf5L11K8,guid=b86aac9a59f39dddad072fc86546c3f8" and the Firefox snap > errors with "/user.slice/user-1000.slice/session-1.scope is not a snap > cgroup". > > But Firefox launched with > `DBUS_SESSION_BUS_ADDRESS="unix:path=$XDG_RUNTIME_DIR/bus" firefox` from > a Terminal will run. > > Note that DBUS_SESSION_BUS_ADDRESS is already set in the non-graphical > shell before starting the Wayland session. It is overriden by dbus-run- > session (as documented in the man page). > > I don't understand these systems, but it would seem to me that the > Firefox snap is assuming that it's being run from a top-level session. > If a Wayland is started by a user with dbus-run-session then it can't > talk to it because it's assuming the top level D-bus. > > This might also be a clue as to why things don't work for remote > sessions. Perhaps snaps assume (indirectly) that they're only being run > in a top-level local session. A "standard session" if you like. > > Incidentally, the Firefox is happy if I use `startx` to get a session. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1951491 > > Title: > Can't run snaps: .slice/session-1.scope is not a snap cgroup > > To manage notifications about this bug go to: > https://bugs.launchpad.net/x2go/+bug/1951491/+subscriptions > > -- Tim Richardson -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1951491 Title: Can't run snaps: .slice/session-1.scope is not a snap cgroup Status in X2Go: New Status in Xpra Terminal Server: New Status in snapd package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Incomplete Status in x2goserver package in Ubuntu: Confirmed Status in snapd package in Debian: New Status in snapd package in Fedora: New Bug description: I just upgraded from hirsute to impish using do-release-upgrade. On the upgraded system, I can't run either firefox or chromium (both of which worked fine under hirsute). Both fail with: /user.slice/user-NNN.slice/session-1.scope is not a snap cgroup where NNN is my uid With firefox, I was able to fix the problem with: snap remove --purge firefox apt purge firefox apt install firefox Now firefox works. But I tried the same thing substituting chromium- browser for firefox, and it didn't help: chromium fails with the same error message. I guess there must be something left over from the hirsute version of snapd that isn't getting noticed or cleared by the impish version? Someone suggested this might be related to bug 1850667, but that bug is marked fixed as of a couple months ago, and I just did this upgrade today. Also, it doesn't mention the error message I'm seeing. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: snapd 2.53+21.10ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Nov 18 18:12:45 2021 InstallationDate: Installed on 2020-04-29 (568 days ago)
[Touch-packages] [Bug 2042749] [NEW] apt does not work with given convig files in new format
Public bug reported: assume /etc/apt/sources.list.d/somerepo.list: Types: deb URIs: https://repo.vivaldi.com/stable/deb/ Suites: stable Components: main Architectures: amd64 Signed-By: /etc/apt/trusted.gpg.d/33EAAB8E.gpg /etc/apt/trusted.gpg.d/4218647E.gpg Then 'apt update' will produce: # apt update E: Type 'Types:' is not known on line 4 in source list /etc/apt/sources.list.d/vivaldi.list E: The list of sources could not be read. A new apt version is available. Would be nice to upgrade. At the moment "man sources.list" does describe a file format not accepted by apt in sources.list-files. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: apt 2.7.3 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Sat Nov 4 23:51:50 2023 InstallationDate: Installed on 2021-12-11 (693 days ago) InstallationMedia: Xubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcEnviron: LANG=de_DE.UTF-8 LANGUAGE=de_DE PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apt (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 apt in Ubuntu. https://bugs.launchpad.net/bugs/2042749 Title: apt does not work with given convig files in new format Status in apt package in Ubuntu: New Bug description: assume /etc/apt/sources.list.d/somerepo.list: Types: deb URIs: https://repo.vivaldi.com/stable/deb/ Suites: stable Components: main Architectures: amd64 Signed-By: /etc/apt/trusted.gpg.d/33EAAB8E.gpg /etc/apt/trusted.gpg.d/4218647E.gpg Then 'apt update' will produce: # apt update E: Type 'Types:' is not known on line 4 in source list /etc/apt/sources.list.d/vivaldi.list E: The list of sources could not be read. A new apt version is available. Would be nice to upgrade. At the moment "man sources.list" does describe a file format not accepted by apt in sources.list-files. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: apt 2.7.3 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Sat Nov 4 23:51:50 2023 InstallationDate: Installed on 2021-12-11 (693 days ago) InstallationMedia: Xubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcEnviron: LANG=de_DE.UTF-8 LANGUAGE=de_DE PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2042749/+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 1951491] Re: Can't run snaps: .slice/session-1.scope is not a snap cgroup
Some clues: If I start Ubuntu 22 with kernel argument `systemd.unit=multi- user.target` (i.e. non-graphical) then start Wayland with `XDG_SESSION_TYPE=wayland dbus-run-session gnome-session` then DBUS_SESSION_BUS_ADDRESS gets set to something like "DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus- mcSf5L11K8,guid=b86aac9a59f39dddad072fc86546c3f8" and the Firefox snap errors with "/user.slice/user-1000.slice/session-1.scope is not a snap cgroup". But Firefox launched with `DBUS_SESSION_BUS_ADDRESS="unix:path=$XDG_RUNTIME_DIR/bus" firefox` from a Terminal will run. Note that DBUS_SESSION_BUS_ADDRESS is already set in the non-graphical shell before starting the Wayland session. It is overriden by dbus-run- session (as documented in the man page). I don't understand these systems, but it would seem to me that the Firefox snap is assuming that it's being run from a top-level session. If a Wayland is started by a user with dbus-run-session then it can't talk to it because it's assuming the top level D-bus. This might also be a clue as to why things don't work for remote sessions. Perhaps snaps assume (indirectly) that they're only being run in a top-level local session. A "standard session" if you like. Incidentally, the Firefox is happy if I use `startx` to get a session. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1951491 Title: Can't run snaps: .slice/session-1.scope is not a snap cgroup Status in X2Go: New Status in Xpra Terminal Server: New Status in snapd package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Incomplete Status in x2goserver package in Ubuntu: Confirmed Status in snapd package in Debian: New Status in snapd package in Fedora: New Bug description: I just upgraded from hirsute to impish using do-release-upgrade. On the upgraded system, I can't run either firefox or chromium (both of which worked fine under hirsute). Both fail with: /user.slice/user-NNN.slice/session-1.scope is not a snap cgroup where NNN is my uid With firefox, I was able to fix the problem with: snap remove --purge firefox apt purge firefox apt install firefox Now firefox works. But I tried the same thing substituting chromium- browser for firefox, and it didn't help: chromium fails with the same error message. I guess there must be something left over from the hirsute version of snapd that isn't getting noticed or cleared by the impish version? Someone suggested this might be related to bug 1850667, but that bug is marked fixed as of a couple months ago, and I just did this upgrade today. Also, it doesn't mention the error message I'm seeing. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: snapd 2.53+21.10ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Nov 18 18:12:45 2021 InstallationDate: Installed on 2020-04-29 (568 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: snapd UpgradeStatus: Upgraded to impish on 2021-11-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/x2go/+bug/1951491/+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 2039235] Re: gnome-online-accounts -> when signing into google account, infinite loading after entering password
Can confirm that the workaround worked for me as well. I had a yubikey on my google account and that was what caused the issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/2039235 Title: gnome-online-accounts -> when signing into google account, infinite loading after entering password Status in gnome-online-accounts package in Ubuntu: Confirmed Bug description: 1) What you expected to happen - sign in is successful, which will allow google services to populate the appropriate applications (calendar, mail, google drive) 2) What actually happened - sign in hangs infinitely after entering the password - the process is able to detect that the password is correct or incorrect. When entering an incorrect password, it will correctly and quickly complain that the password is incorrect. When entering the correct password, the bug will occur. 3) Steps to reproduce a) start the program b) select online accounts c) select google d) enter email e) enter password f) loads forever ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-online-accounts 3.48.0-2 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Oct 12 22:27:59 2023 InstallationDate: Installed on 2023-10-12 (0 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) Hardware info (not sure if relevant): cpu: intel gpu: nvidia (driver version: "Using NVIDIA driver metapackage from nvidia-driver-535(proprietary, tested)") To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/2039235/+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 2042729] [NEW] Xorg freeze
Public bug reported:
Computer unresponsive after closing laptop screen and reopening. GDM
screen does not appear to login, just see contents of the X session
before i closed the lid. mouse moves and hardware buttons (mute, caps
lock etc) are responsive with LEDs. Have to hard reboot to login and use
computer
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.129.03 Thu Oct 19
18:56:32 UTC 2023
GCC version:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Nov 4 15:33:14 2023
DistUpgraded: 2023-11-02 15:19:38,871 DEBUG 'libkf5itemviews5' scheduled for
remove but not safe to remove, skipping
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GpuHangFrequency: Several times a week
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Within the last few days
GraphicsCard:
Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 00
[VGA controller])
Subsystem: Lenovo CoffeeLake-H GT2 [UHD Graphics 630] [17aa:229f]
NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev
a1) (prog-if 00 [VGA controller])
Subsystem: Lenovo TU117M [GeForce GTX 1650 Mobile / Max-Q] [17aa:229f]
InstallationDate: Installed on 2023-05-24 (164 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230417)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=UUID=45e4e3f8-045a-4651-bd83-6087eca44175 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to mantic on 2023-11-02 (2 days ago)
dmi.bios.date: 09/19/2023
dmi.bios.release: 1.48
dmi.bios.vendor: LENOVO
dmi.bios.version: N2OET61W (1.48 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20QV00BRUK
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.22
dmi.modalias:
dmi:bvnLENOVO:bvrN2OET61W(1.48):bd09/19/2023:br1.48:efr1.22:svnLENOVO:pn20QV00BRUK:pvrThinkPadX1Extreme2nd:rvnLENOVO:rn20QV00BRUK:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QV_BU_Think_FM_ThinkPadX1Extreme2nd:
dmi.product.family: ThinkPad X1 Extreme 2nd
dmi.product.name: 20QV00BRUK
dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme 2nd
dmi.product.version: ThinkPad X1 Extreme 2nd
dmi.sys.vendor: LENOVO
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 23.0.4-0ubuntu1~23.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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: xorg (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug freeze mantic ubuntu
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2042729
Title:
Xorg freeze
Status in xorg package in Ubuntu:
New
Bug description:
Computer unresponsive after closing laptop screen and reopening. GDM
screen does not appear to login, just see contents of the X session
before i closed the lid. mouse moves and hardware buttons (mute, caps
lock etc) are responsive with LEDs. Have to hard reboot to login and
use computer
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
[Touch-packages] [Bug 2039328] Please test proposed package
Hello Dimitri, or anyone else affected, Accepted ubuntu-meta into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu- meta/1.524.1 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- mantic to verification-done-mantic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-mantic. 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 ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2039328 Title: Update ubuntu-meta with promotions done between last ubuntu-meta build & release Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-meta source package in Mantic: Fix Committed Status in ubuntu-meta source package in Noble: Fix Released Bug description: [ Impact ] * ubuntu-seeds were changed since last meta update * to ensure correct upgrades; regenerate ubuntu-meta with contents / changes done before release [ Test Plan ] * Check that arm64 upgrades of ubuntu-desktop-minimal from lunar to mantic install newly recommended packages. [ Where problems could occur ] * This is automatically generated change based on ubuntu-seeds commit [1]. * Theoretically, regressions would occur if new desktop-minimal-recommends dependencies on arm64 (flash-kernel, protection-domain-mapper, qrtr-tools): - have issues on install during release-upgrade; - have issues on regular system usage (after installed). [ Other Info ] * ubuntu-meta was not uploaded during final freeze, to prevent rebuilding all images as changes affect arm64 only, which is a brand new release image * protection-domain-mapper [2] and qrtr [3] moved from universe to main in Mantic. * flash-kernel is/was already in main. [1] https://git.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/+git/ubuntu/commit/?id=afe820cd49514896e96d02303298ed873d8d7f8a [2] https://launchpad.net/ubuntu/+source/protection-domain-mapper/1.0-4ubuntu2/+publishinghistory [3] https://launchpad.net/ubuntu/+source/qrtr/1.0-2ubuntu1/+publishinghistory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2039328/+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 2039328] Re: Update ubuntu-meta with promotions done between last ubuntu-meta build & release
ubuntu-meta sponsored to noble, but no bug ref in changelog, so marking this fix released for noble. ** Changed in: ubuntu-meta (Ubuntu Noble) Status: Fix Committed => Fix Released ** Changed in: ubuntu-meta (Ubuntu Mantic) Status: Confirmed => Fix Committed ** Tags added: verification-needed verification-needed-mantic -- 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/2039328 Title: Update ubuntu-meta with promotions done between last ubuntu-meta build & release Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-meta source package in Mantic: Fix Committed Status in ubuntu-meta source package in Noble: Fix Released Bug description: [ Impact ] * ubuntu-seeds were changed since last meta update * to ensure correct upgrades; regenerate ubuntu-meta with contents / changes done before release [ Test Plan ] * Check that arm64 upgrades of ubuntu-desktop-minimal from lunar to mantic install newly recommended packages. [ Where problems could occur ] * This is automatically generated change based on ubuntu-seeds commit [1]. * Theoretically, regressions would occur if new desktop-minimal-recommends dependencies on arm64 (flash-kernel, protection-domain-mapper, qrtr-tools): - have issues on install during release-upgrade; - have issues on regular system usage (after installed). [ Other Info ] * ubuntu-meta was not uploaded during final freeze, to prevent rebuilding all images as changes affect arm64 only, which is a brand new release image * protection-domain-mapper [2] and qrtr [3] moved from universe to main in Mantic. * flash-kernel is/was already in main. [1] https://git.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/+git/ubuntu/commit/?id=afe820cd49514896e96d02303298ed873d8d7f8a [2] https://launchpad.net/ubuntu/+source/protection-domain-mapper/1.0-4ubuntu2/+publishinghistory [3] https://launchpad.net/ubuntu/+source/qrtr/1.0-2ubuntu1/+publishinghistory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2039328/+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 2025339] Re: FDE image fails to run e2fsck
** Changed in: e2fsprogs (Debian) Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/2025339 Title: FDE image fails to run e2fsck Status in e2fsprogs package in Ubuntu: Fix Released Status in e2fsprogs source package in Lunar: In Progress Status in e2fsprogs package in Debian: Fix Released Bug description: After installation of the FDE image, the system fails to boot due to e2fsck failing with: Jun 21 12:48:19 ubuntu systemd-fsck[268]: /dev/vda2 has unsupported feature(s): FEATURE_C12 this means that Jammy fsck fails against mantic created ext4 which is not great Seems this is orphan_file feature / orphan_present Also need to check if grub2 supports this as it is RO_INCOMPAT feature. [Fix] This SRU is disabling 2 features (orphan_file and metadata_csum_seed) from ext4 to generate filesystems compatible with older series. Fixes come from debian (fixing #1031622, #1030939). This is only disabling the feature by default. One can still generate a filesystem with this feature by explicitly listing them when invoking mkfs.ext4. [Impact] See LP: #2028564. Generating a filesystem on lunar with e2fsprogs will use the orphan_file feature. This will prevent a jammy (or older) based OS from modifying this filesystem (in particular resize it at first boot). [ Test Plan ] On lunar, generate a filesystem and check the orphan_file feature is enabled: $ dd if=/dev/zero of=test.img bs=100M count=1 $ mkfs.ext4 test.img $ # Then check the orphan_file feature is enabled $ dumpe2fs test.img | grep orphan Move this .img file to a jammy based machine, and try using resize2fs on it: $ resize2fs -d -f -M test.img resize2fs 1.46.5 (30-Dec-2021) resize2fs: Filesystem has unsupported feature(s) (test.img) [Where problems could occur] Some users on Lunar may currently rely on this feature to be enabled by default. This can still be enabled explicitly when calling mkfs.ext4 but the default behavior will be changed. The orphan_file feature aims at improving performances when dealing with deleted files or directories. So if we disable this by default, I think it should only impact performances of generated filesystems and probably not break anything else. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/2025339/+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 2042728] [NEW] No sound from speakers. Chip Everest ESSX 8336 (ESSX8336, ES8336).
Public bug reported: Similar to bug #1977685. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: pulseaudio 1:16.1+dfsg1-2ubuntu4 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joel905 F wireplumber /dev/snd/seq:joel902 F pipewire CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Sat Nov 4 15:27:44 2023 InstallationDate: Installed on 2023-11-03 (1 days ago) InstallationMedia: Xubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010) ProcEnviron: LANG=fr_FR.UTF-8 LANGUAGE=fr_FR PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2021 dmi.bios.release: 0.5 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V0.5.0_P8S4M1E0F0L2B0T0P2G00A0U0D605_ENE dmi.board.asset.tag: Default string dmi.board.name: G8316 dmi.board.vendor: THOMSON dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.ec.firmware.release: 1.2 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV0.5.0_P8S4M1E0F0L2B0T0P2G00A0U0D605_ENE:bd04/23/2021:br0.5:efr1.2:svnTHOMSON:pnN14C4WH64:pvrDefaultstring:rvnTHOMSON:rnG8316:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:skuN14C4WH64: dmi.product.family: N14C4WH64 dmi.product.name: N14C4WH64 dmi.product.sku: N14C4WH64 dmi.product.version: Default string dmi.sys.vendor: THOMSON ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic ** Summary changed: - No soud from speakers. Chip ESSX 8336. + No soud from speakers. Chip Everest ESSX 8336 (ESSX8336, ES8336). ** Summary changed: - No soud from speakers. Chip Everest ESSX 8336 (ESSX8336, ES8336). + No sound from speakers. Chip Everest ESSX 8336 (ESSX8336, ES8336). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2042728 Title: No sound from speakers. Chip Everest ESSX 8336 (ESSX8336, ES8336). Status in pulseaudio package in Ubuntu: New Bug description: Similar to bug #1977685. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: pulseaudio 1:16.1+dfsg1-2ubuntu4 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joel905 F wireplumber /dev/snd/seq:joel902 F pipewire CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Sat Nov 4 15:27:44 2023 InstallationDate: Installed on 2023-11-03 (1 days ago) InstallationMedia: Xubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010) ProcEnviron: LANG=fr_FR.UTF-8 LANGUAGE=fr_FR PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2021 dmi.bios.release: 0.5 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V0.5.0_P8S4M1E0F0L2B0T0P2G00A0U0D605_ENE dmi.board.asset.tag: Default string dmi.board.name: G8316 dmi.board.vendor: THOMSON dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.ec.firmware.release: 1.2 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV0.5.0_P8S4M1E0F0L2B0T0P2G00A0U0D605_ENE:bd04/23/2021:br0.5:efr1.2:svnTHOMSON:pnN14C4WH64:pvrDefaultstring:rvnTHOMSON:rnG8316:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:skuN14C4WH64: dmi.product.family: N14C4WH64 dmi.product.name: N14C4WH64 dmi.product.sku: N14C4WH64 dmi.product.version: Default string dmi.sys.vendor: THOMSON To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2042728/+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 1977685] Re: Sound card/chip Everest ESSX 8336 (ESSX8336, ES8336) not supported.
This hack (that I have not tested) for Ubuntu 22.04 may be interesting: https://ubuntuhandbook.org/index.php/2022/07/fix-no-sound-issue- ubuntu-22-04-essx8336/ ** Summary changed: - sound card Everest ESSX8336 not supported + Sound card/chip Everest ESSX 8336 (ESSX8336, ES8336) not supported. ** Tags added: 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/1977685 Title: Sound card/chip Everest ESSX 8336 (ESSX8336, ES8336) not supported. Status in alsa-driver package in Ubuntu: Confirmed Bug description: I work with Ubuntu 22.04 but the Everest semiconductor Co Ltd ESSX8336\1 sound card is not recognized. On the web a lot of people have the same problem. It's an annoying problem. Could you please help us to solve this problem. I have a Huawei Matebook D15 series Matebook D 15 (2021) i3 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: francois852 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jun 5 15:44:25 2022 InstallationDate: Installed on 2022-04-22 (43 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/21/2022 dmi.bios.release: 1.41 dmi.bios.vendor: HUAWEI dmi.bios.version: 1.41 dmi.board.asset.tag: NULL dmi.board.name: BOHB-WAX9-PCB-B2 dmi.board.vendor: HUAWEI dmi.board.version: M1340 dmi.chassis.asset.tag: NULL dmi.chassis.type: 10 dmi.chassis.vendor: HUAWEI dmi.chassis.version: M1340 dmi.ec.firmware.release: 1.41 dmi.modalias: dmi:bvnHUAWEI:bvr1.41:bd02/21/2022:br1.41:efr1.41:svnHUAWEI:pnBOHB-WAX9:pvrM1340:rvnHUAWEI:rnBOHB-WAX9-PCB-B2:rvrM1340:cvnHUAWEI:ct10:cvrM1340:skuC100: dmi.product.family: MateBook D dmi.product.name: BOHB-WAX9 dmi.product.sku: C100 dmi.product.version: M1340 dmi.sys.vendor: HUAWEI mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-06-04T20:59:26.778687 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1977685/+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 1977685] Re: sound card Everest ESSX8336 not supported
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1977685 Title: Sound card/chip Everest ESSX 8336 (ESSX8336, ES8336) not supported. Status in alsa-driver package in Ubuntu: Confirmed Bug description: I work with Ubuntu 22.04 but the Everest semiconductor Co Ltd ESSX8336\1 sound card is not recognized. On the web a lot of people have the same problem. It's an annoying problem. Could you please help us to solve this problem. I have a Huawei Matebook D15 series Matebook D 15 (2021) i3 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: francois852 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jun 5 15:44:25 2022 InstallationDate: Installed on 2022-04-22 (43 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/21/2022 dmi.bios.release: 1.41 dmi.bios.vendor: HUAWEI dmi.bios.version: 1.41 dmi.board.asset.tag: NULL dmi.board.name: BOHB-WAX9-PCB-B2 dmi.board.vendor: HUAWEI dmi.board.version: M1340 dmi.chassis.asset.tag: NULL dmi.chassis.type: 10 dmi.chassis.vendor: HUAWEI dmi.chassis.version: M1340 dmi.ec.firmware.release: 1.41 dmi.modalias: dmi:bvnHUAWEI:bvr1.41:bd02/21/2022:br1.41:efr1.41:svnHUAWEI:pnBOHB-WAX9:pvrM1340:rvnHUAWEI:rnBOHB-WAX9-PCB-B2:rvrM1340:cvnHUAWEI:ct10:cvrM1340:skuC100: dmi.product.family: MateBook D dmi.product.name: BOHB-WAX9 dmi.product.sku: C100 dmi.product.version: M1340 dmi.sys.vendor: HUAWEI mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-06-04T20:59:26.778687 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1977685/+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 1574582] Re: HP lt4120 Snapdragon X5 LTE USB modem not recognized by network-manager
In the kernel 5.15.x and up the modem X5 is working in the MBIM mode, so the updated udev script attached. ** Attachment added: "99-hp-lt4120-test.rules" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1574582/+attachment/5715918/+files/99-hp-lt4120-test.rules -- 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/1574582 Title: HP lt4120 Snapdragon X5 LTE USB modem not recognized by network- manager Status in network-manager package in Ubuntu: Confirmed Bug description: USB modem not recognized by network-manager. Modem information in attached ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CasperVersion: 1.376 Date: Mon Apr 25 11:14:04 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 10.106.36.1 dev wlp2s0 proto static metric 600 1.1.1.1 via 10.106.36.1 dev wlp2s0 proto dhcp metric 600 10.106.36.0/22 dev wlp2s0 proto kernel scope link src 10.106.39.123 metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connected /org/freedesktop/NetworkManager/Devices/1 IQORAMS_REPAIR 3b1e13ff-f9c9-4a49-a576-465bc2713e21 /org/freedesktop/NetworkManager/ActiveConnection/1 enxb2e41f35ffe1 ethernet disconnected /org/freedesktop/NetworkManager/Devices/2 -- -- -- enp0s31f6ethernet unavailable /org/freedesktop/NetworkManager/Devices/3 -- -- -- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- -- -- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1574582/+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 2036253] Re: FTBFS: missing strl* symbols fail the build
** Changed in: heimdal (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/2036253 Title: FTBFS: missing strl* symbols fail the build Status in heimdal package in Ubuntu: New Status in heimdal package in Debian: New Bug description: See ubuntu-devel thread[1] and mantic rebuild report[2]. dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libkafs0-heimdal/DEBIAN/symbols doesn't match completely debian/libkafs0-heimdal.symbols --- debian/libkafs0-heimdal.symbols (libkafs0-heimdal_7.8.git20221117.28daf24+dfsg-3ubuntu1_amd64) +++ dpkg-gensymbolshoPgEa 2023-09-05 02:37:15.654111977 + @@ -12,7 +12,7 @@ _kafs_get_cred@Base 1.4.0+git20110226 _kafs_realm_of_cell@Base 1.4.0+git20110226 _kafs_resolve_debug@Base 1.4.0+git20110226 - _kafs_strlcpy@Base 1.4.0+git20110226 +#MISSING: 7.8.git20221117.28daf24+dfsg-3ubuntu1# _kafs_strlcpy@Base 1.4.0+git20110226 k_afs_cell_of_file@Base 1.4.0+git20110226 k_hasafs@Base 1.4.0+git20110226 k_hasafs_recheck@Base 1.4.0+git20110226 dh_makeshlibs: error: failing due to earlier errors make[1]: *** [debian/rules:18: override_dh_makeshlibs] Error 25 This one might need a fix similar to the krb5 one[3]. 1. https://lists.ubuntu.com/archives/ubuntu-devel/2023-September/042784.html 2. https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20230830-mantic-mantic.html#ubuntu-server-team 3. https://launchpad.net/ubuntu/+source/krb5/1.20.1-3ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/2036253/+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 2031841] Re: initramfs-tools and dracut install different sets of kernel modules
Regression: bug #2042710 -- 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/2031841 Title: initramfs-tools and dracut install different sets of kernel modules Status in initramfs-tools package in Ubuntu: Fix Released Bug description: initramfs-tools and dracut install different sets of kernel modules. Either these modules are not needed for booting or are missing in the other project. dracut-install can filter modules by symbol (--mod-filter-symbol) to select modules more fine-grain. Harmonize the set of modules. Adopt the install rules from dracut to get rid of modules that are shipped in initramfs-tools, but not in dracut. Following kernel modules will be kept since they are mentioned in the initramfs-tools code: * via hidden_dep_add_modules: psmouse mlx5_ib mlx4_ib * via framebuffer hook: =drivers/gpu vga16fb =drivers/char/agp * explicit in auto_add_modules: extcon-usb-gpio extcon-usbc-cros-ec cros_ec_spi * via hw_random in auto_add_modules: =drivers/char/hw_random * via fb in auto_add_modules: pwm-cros-ec pwm_bl * ignored difference for now: =drivers/mmc * via virtual in auto_add_modules: hv_utils * not analyzed yet: mhi_ep mhi mhi_pci_generic i2c-mux i2c-mux-gpio i2c-mux-ltc4306 i2c-mux-mlxcpld i2c-mux-pca9541 i2c-mux-pca954x i2c-mux-reg c67x00 Following modules will be removed from initramfs-tools with this change, but are in dracut (pulled in as dependency): intel_pmc_bxt kempld-core rave-sp retu-mfd nandcore bch If that change removed too much, we need to add it back and also report that to dracut to add it there as well. Test setup: mantic schroot with linux 6.3.0-7-generic and following packages: linux-image-generic,zstd,busybox-initramfs,cryptsetup- initramfs,isc-dhcp-client,kbd,lvm2,mdadm,ntfs-3g,plymouth,plymouth- theme-spinner,initramfs-tools,dracut-core,dracut-config- generic,dcracut-network initramfs generation with dracut: dracut --regenerate-all --force -q --add-drivers "=drivers/char/agp hv_utils =drivers/mmc pwm-cros-ec pwm_bl mlx4_ib extcon-usb-gpio extcon-usbc-cros-ec cros_ec_spi =drivers/gpu vga16fb psmouse mlx5_ib =drivers/char/hw_random" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2031841/+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 2042680] Re: lsb_release shows incorrect Ubuntu version
and screenshot of apt policy base-files ** Attachment added: "Screenshot from 2023-11-04 09-59-44.png" https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2042680/+attachment/5715871/+files/Screenshot%20from%202023-11-04%2009-59-44.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/2042680 Title: lsb_release shows incorrect Ubuntu version Status in base-files package in Ubuntu: Incomplete Bug description: Testing Ubuntu Noble Desktop for Raspberry PI daily ISO dated 03-11-2023 After installing and rebooting running lsb_release -a shows version 23.10 not 24.04 ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: lsb-release 12.0-2 ProcVersionSignature: Ubuntu 6.5.0-1006.8-raspi 6.5.3 Uname: Linux 6.5.0-1006-raspi aarch64 ApportVersion: 2.27.0-0ubuntu5 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Nov 3 16:24:14 2023 Dependencies: PackageArchitecture: all ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: lsb-release-minimal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2042680/+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 2042680] Re: lsb_release shows incorrect Ubuntu version
@vorlon Steve Langasek - Retested with latest ISO dated 04-11-2023 still same results ..see attached screenshot ** Attachment added: "Screenshot from 2023-11-04 09-48-53.png" https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2042680/+attachment/5715870/+files/Screenshot%20from%202023-11-04%2009-48-53.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/2042680 Title: lsb_release shows incorrect Ubuntu version Status in base-files package in Ubuntu: Incomplete Bug description: Testing Ubuntu Noble Desktop for Raspberry PI daily ISO dated 03-11-2023 After installing and rebooting running lsb_release -a shows version 23.10 not 24.04 ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: lsb-release 12.0-2 ProcVersionSignature: Ubuntu 6.5.0-1006.8-raspi 6.5.3 Uname: Linux 6.5.0-1006-raspi aarch64 ApportVersion: 2.27.0-0ubuntu5 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Nov 3 16:24:14 2023 Dependencies: PackageArchitecture: all ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: lsb-release-minimal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2042680/+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 2036253] Re: FTBFS: missing strl* symbols fail the build
** Bug watch added: Debian Bug tracker #1055316 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055316 ** Also affects: heimdal (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055316 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/2036253 Title: FTBFS: missing strl* symbols fail the build Status in heimdal package in Ubuntu: New Status in heimdal package in Debian: Unknown Bug description: See ubuntu-devel thread[1] and mantic rebuild report[2]. dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libkafs0-heimdal/DEBIAN/symbols doesn't match completely debian/libkafs0-heimdal.symbols --- debian/libkafs0-heimdal.symbols (libkafs0-heimdal_7.8.git20221117.28daf24+dfsg-3ubuntu1_amd64) +++ dpkg-gensymbolshoPgEa 2023-09-05 02:37:15.654111977 + @@ -12,7 +12,7 @@ _kafs_get_cred@Base 1.4.0+git20110226 _kafs_realm_of_cell@Base 1.4.0+git20110226 _kafs_resolve_debug@Base 1.4.0+git20110226 - _kafs_strlcpy@Base 1.4.0+git20110226 +#MISSING: 7.8.git20221117.28daf24+dfsg-3ubuntu1# _kafs_strlcpy@Base 1.4.0+git20110226 k_afs_cell_of_file@Base 1.4.0+git20110226 k_hasafs@Base 1.4.0+git20110226 k_hasafs_recheck@Base 1.4.0+git20110226 dh_makeshlibs: error: failing due to earlier errors make[1]: *** [debian/rules:18: override_dh_makeshlibs] Error 25 This one might need a fix similar to the krb5 one[3]. 1. https://lists.ubuntu.com/archives/ubuntu-devel/2023-September/042784.html 2. https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20230830-mantic-mantic.html#ubuntu-server-team 3. https://launchpad.net/ubuntu/+source/krb5/1.20.1-3ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/2036253/+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 2042715] [NEW] gpu-manager service takes 10 seconds during boot
Public bug reported: There is obviously something not right with the gpu-manager service as it's taking more than 10 seconds to run during boot, and this is happening every time. # systemd-analyze blame 13.254s plymouth-quit-wait.service 10.347s gpu-manager.service 3.843s NetworkManager-wait-online.service 1.313s logrotate.service 1.276s fwupd-refresh.service 1.197s snapd.service 1.134s NetworkManager.service 871ms fwupd.service 772ms udisks2.service ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-desktop (not installed) ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Nov 4 10:32:53 2023 InstallationDate: Installed on 2023-10-12 (23 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011) SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic wayland-session -- 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/2042715 Title: gpu-manager service takes 10 seconds during boot Status in ubuntu-meta package in Ubuntu: New Bug description: There is obviously something not right with the gpu-manager service as it's taking more than 10 seconds to run during boot, and this is happening every time. # systemd-analyze blame 13.254s plymouth-quit-wait.service 10.347s gpu-manager.service 3.843s NetworkManager-wait-online.service 1.313s logrotate.service 1.276s fwupd-refresh.service 1.197s snapd.service 1.134s NetworkManager.service 871ms fwupd.service 772ms udisks2.service ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-desktop (not installed) ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Nov 4 10:32:53 2023 InstallationDate: Installed on 2023-10-12 (23 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011) SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2042715/+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 2036358] Re: systemd wait-online now times out after jammy and lunar upgrade
systemd 249.11-0ubuntu3.11 bug still exists root@ubuntu:~# netplan get network: version: 2 renderer: networkd ethernets: eth0: dhcp4: true optional: true dhcp-identifier: "mac" root@ubuntu:~# networkctl list IDX LINK TYPE OPERATIONAL SETUP 1 lo loopback carrier unmanaged 2 eth0 etherroutableconfigured 3 eth1 etheroff unmanaged 3 links listed. root@ubuntu:~# systemctl status systemd-networkd-wait-online.service × systemd-networkd-wait-online.service - Wait for Network to be Configured Loaded: loaded (/lib/systemd/system/systemd-networkd-wait-online.service; enabled-runtime; vendor preset: disabled) Active: failed (Result: exit-code) since Sat 2023-11-04 15:45:37 CST; 50s ago Docs: man:systemd-networkd-wait-online.service(8) Process: 630 ExecStart=/lib/systemd/systemd-networkd-wait-online (code=exited, status=1/FAILURE) Main PID: 630 (code=exited, status=1/FAILURE) CPU: 5ms Nov 04 15:43:37 ubuntu systemd[1]: Starting Wait for Network to be Configured... Nov 04 15:45:37 ubuntu systemd-networkd-wait-online[630]: Timeout occurred while waiting for network connectivity. Nov 04 15:45:37 ubuntu systemd[1]: systemd-networkd-wait-online.service: Main process exited, code=exited, status=1/FAILURE Nov 04 15:45:37 ubuntu systemd[1]: systemd-networkd-wait-online.service: Failed with result 'exit-code'. Nov 04 15:45:37 ubuntu systemd[1]: Failed to start Wait for Network to be Configured. root@ubuntu:~# SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd-wait-online --timeout=10 Found link 3 Found link 2 Found link 1 eth0: link is ignored eth1: link is not managed by networkd (yet?). lo: link is ignored Timeout occurred while waiting for network connectivity. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2036358 Title: systemd wait-online now times out after jammy and lunar upgrade Status in systemd package in Ubuntu: Invalid Status in systemd source package in Jammy: Fix Released Status in systemd source package in Lunar: Fix Released Bug description: [NOTE] If you are running a desktop system and you see this issue, you should run: $ systemctl disable --now systemd-networkd.service This will disable systemd-networkd and associated units, including systemd-networkd-wait-online.service. NetworkManager and systemd- networkd should not be running at the same time. On desktop, NetworkManager is the default network stack. [Impact] When all interfaces are "not required for online", e.g. when they are marked "optional: true" in netplan, systemd-networkd-wait-online will timeout. Or, in other words, systemd-networkd-wait-online will timeout even though all interfaces are ignored, hence none of them will ever be marked as "ready." Depending on what units depend on network- online.target, this can delay boot by 120 seconds (the default timeout for systemd-networkd-wait-online). [Test Plan] 1. Create a new LXD container. These instructions assume jammy is the release, but the same can be done for lunar. $ lxc launch ubuntu-daily:jammy jammy $ lxc exec jammy bash 2. Once in the container, modify the default /etc/netplan/10-lxc.yaml so that eth0 is configured with "optional: true": $ vi /etc/netplan/50-cloud-init.yaml # Use whatever editor you like $ cat /etc/netplan/50-cloud-init.yaml network: version: 2 ethernets: eth0: dhcp4: true dhcp-identifier: mac optional: true 3. Re-generate and apply the netplan configuration. $ netplan generate $ netplan apply 4. Manually run systemd-networkd-wait-online, and observe that all links are ignored, and the command times out: $ SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd-wait-online --timeout=10 Found link lo(1) Found link eth0(19) lo: link is ignored eth0: link is ignored Timeout occurred while waiting for network connectivity. [Where problems could occur] This patch partially re-instates a patch remove in bug 1982218. However, instead of exiting if all links are unmanaged, we exit if all links are ignored in manager_configured(). If the patch was wrong, we may re-introduce bug 1982218, so as part of this SRU verification, that bug should be tested too. Any other regressions would also be related to systemd-networkd-wait-online behavior. [Original Description] On Ubuntu 22.04 desktop system using network-manager and upgrading to systemd 249.11-0ubuntu3.10, wait-online now times out which prevents logins (GDM, ssh, console) until it does time out. This seems to be introduced by the change for https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218. https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218/comments/21 also mentioned the problem on Lunar. To
[Touch-packages] [Bug 2042680] Re: lsb_release shows incorrect Ubuntu version
Image used was created from the zsync ..zsync http://cdimage.ubuntu.com/ubuntu/daily-preinstalled/20231103/noble- preinstalled-desktop-arm64+raspi.img.xz.zsync this taken from the QA testing tracker site.. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/2042680 Title: lsb_release shows incorrect Ubuntu version Status in base-files package in Ubuntu: Incomplete Bug description: Testing Ubuntu Noble Desktop for Raspberry PI daily ISO dated 03-11-2023 After installing and rebooting running lsb_release -a shows version 23.10 not 24.04 ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: lsb-release 12.0-2 ProcVersionSignature: Ubuntu 6.5.0-1006.8-raspi 6.5.3 Uname: Linux 6.5.0-1006-raspi aarch64 ApportVersion: 2.27.0-0ubuntu5 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Nov 3 16:24:14 2023 Dependencies: PackageArchitecture: all ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: lsb-release-minimal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2042680/+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
