[Touch-packages] [Bug 2039235] Re: gnome-online-accounts -> when signing into google account, infinite loading after entering password
** Attachment added: "ProcCPUinfoFull.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/2039235/+attachment/5712189/+files/ProcCPUinfoFull.txt -- 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 2039235] Re: gnome-online-accounts -> when signing into google account, infinite loading after entering password
I am facing this issue on Ubuntu 22.04 LTS as well so I suspect that this is not related to the operating system per se but more of the package and how it interacts with google. I have attached my dependencies as well as my full cpuinfo. ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/2039235/+attachment/5712188/+files/Dependencies.txt -- 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 2040076] [NEW] Something is holding a lock on unmounted partition
Public bug reported: Following instructions from https://discourse.maas.io/t/deploying- servers-with-full-disk-encryption-luks2/3286 to get full disk encryption with ubuntu-22.04-server # mount -o remount,ro /boot # install -m0600 /dev/null /tmp/boot.tar # tar -C /boot --acls --xattrs --one-file-system -cf /tmp/boot.tar . # umount -v /boot/efi umount: /boot/efi unmounted # umount -v /boot umount: /boot unmounted # cryptsetup -y luksFormat --type luks1 /dev/nvme0n1p3 WARNING: Device /dev/nvme0n1p3 already contains a 'ext4' superblock signature. WARNING! This will overwrite data on /dev/nvme0n1p3 irrevocably. Are you sure? (Type 'yes' in capital letters); YES Enter Passphrase for /dev/nvme0n1p3: Verify Passphrase: Device /dev/nvme0n1p3 is in use. Cannot proceed with format operation. Uh, not what I expected. So i start to investigate: # grep nvme0n1p3 /proc/mounts # lsof | grep nvme0n1p3 # lsof nvme0n1p3 # fuser nvme0n1p3 So: - umount succeeded - /proc/mounts, lsof, fuser don's show any sign that the partition is in use BUT: strace cryptsetup luksFormat --type luks1 /dev/nvme0n1p3 2>&1 | egrep '(nvme0n1p3|close)' shows openat(AT_FDCWD, "/dev/nvme0n1p3", O_RDONLY|ODIRECT) = 3 close(3) openat(AT_FDCWD, "/dev/nvme0n1p3", O_RDONLY|O_NONBLOCK|OCLOEXEC) = 3 close(3) openat(AT_FDCWD, "/dev/nvme0n1p3", O_RDWR|OEXCL) = -1 EBUSY (Device or resource busy) So there must be something holding a hand on the partition. But there's no trace of what it might be === Another try (after fresh boot): # mount -o remount,ro /boot # install -m0600 /dev/null /tmp/boot.tar # tar -C /boot --acls --xattrs --one-file-system -cf /tmp/boot.tar . # umount /boot/efi # umount /boot # mount /boot mount: /boot: /dev/nvme0n1p3 already mounted or mount point busy and again: no sign that the partition is in use: # grep nvme0n1p3 /proc/mounts # lsof | grep nvme0n1p3 # lsof nvme0n1p3 # fuser nvme0n1p3 === So another try (reboot again): # mount -o remount,ro /boot # install -m0600 /dev/null /tmp/boot.tar # tar -C /boot --acls --xattrs --one-file-system -cf /tmp/boot.tar . # umount /boot/efi # mount -o remount,rw /boot# --- notice this one! # umount /boot # mount /boot # --- Now it succeeds! Now do the same, but without the "mount -oremount,rw /boot" # mount -o remount,ro /boot # install -m0600 /dev/null /tmp/boot.tar # tar -C /boot --acls --xattrs --one-file-system -cf /tmp/boot.tar . # umount /boot # mount /boot mount: /boot: /dev/nvme0n1p3 already mounted or mount point busy Oooops! Now system is messed up again. No way to "clean up the mess. Getting closer? Partition originally was mounted read-write. umount while remounted read-only seems to mess up things and mount looses track of was is going on.. Thus, another try: = Again freshly booted. Omit the "mount -oremount,ro /boot" this time: # install -m0600 /dev/null /tmp/boot.tar # tar -C /boot --acls --xattrs --one-file-system -cf /tmp/boot.tar . # umount -v /boot/efi umount: /boot/efi unmounted # umount -v /boot umount: /boot unmounted # cryptsetup -y luksFormat --type luks1 /dev/nvme0n1p3 WARNING: Device /dev/nvme0n1p3 already contains a 'ext4' superblock signature. WARNING! This will overwrite data on /dev/nvme0n1p3 irrevocably. Are you sure? (Type 'yes' in capital letters); YES Enter Passphrase for /dev/nvme0n1p3: Verify Passphrase: Device /dev/nvme0n1p3 is in use. Cannot proceed with format operation. failed again, but # mount /boot # --- Now it succeeds! # umount /boot # --- Now it succeeds! # mount /boot # --- Now it succeeds! So, how can I track this one down further? ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New ** Tags: cryptsetup mount umount ** Description changed: Following instructions from https://discourse.maas.io/t/deploying- servers-with-full-disk-encryption-luks2/3286 to get full disk encryption with ubuntu-22.04-server -# mount -o remount,ro /boot -# install -m0600 /dev/null /tmp/boot.tar -# tar -C /boot --acls --xattrs --one-file-system -cf /tmp/boot.tar . -# umount -v /boot/efi -umount: /boot/efi unmounted -# umount -v /boot -umount: /boot unmounted -# cryptsetup -y luksFormat --type luks1 /dev/nvme0n1p3 -WARNING: Device /dev/nvme0n1p3 already contains a 'ext4' superblock signature. + # mount -o remount,ro /boot + # install -m0600 /dev/null /tmp/boot.tar + # tar -C /boot --acls --xattrs --one-file-system -cf /tmp/boot.tar . + # umount -v /boot/efi +
[Touch-packages] [Bug 2029019] Re: PulseAudio doesn't start by logging in after a standby
Logs entries related to PulseAudio:
03:14:20 PM systemd: pulseaudio.socket: Failed with result
'service-start-limit-hit'.
03:14:13 PM dbus-daemon: [system] Activating via systemd: service
name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.189' (uid=1000
pid=3142 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo"
label="unconfined")
03:14:13 PM systemd: pulseaudio.service: Succeeded.
03:08:45 PM sudo: luca : TTY=pts/0 ; PWD=/home/luca ; USER=root ;
COMMAND=/usr/bin/apt purge pulseaudio
03:07:18 PM pulseaudio: GetManagedObjects() failed:
org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez':
timed out (service_start_timeout=25000ms)
03:07:14 PM systemd: pulseaudio.service: Succeeded.
03:06:53 PM dbus-daemon: [system] Activating via systemd: service
name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.161' (uid=1000
pid=2849 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo"
label="unconfined")
03:06:52 PM systemd: pulseaudio.service: Succeeded.
03:05:24 PM pulseaudio: Error opening PCM device front:0: File or directory
does not exist
4 oct 03:31:04 PM systemd: pulseaudio.socket: Succeeded.
4 oct 03:30:49 PM pulseaudio: GetManagedObjects() failed:
org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez':
timed out (service_start_timeout=25000ms)
4 oct 03:30:35 PM systemd: gnome-launched-pulseaudio.desktop-1603.scope:
Succeeded.
4 oct 03:30:26 PM dbus-daemon: [system] Activating via systemd: service
name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.71' (uid=1000
pid=1383 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo"
label="unconfined")
4 oct 03:29:12 PM system76-schedu: (Assignment(CpuPriority(-11),
Realtime(PriorityLevel(0))), {"pipewire", "pipewire-pulse", "wireplumber"})
--
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/2029019
Title:
PulseAudio doesn't start by logging in after a standby
Status in pulseaudio package in Ubuntu:
New
Bug description:
Often when I log in after a standby PulseAudio doesn't play any audio, the
service is working but no audio is heard. I noticed that when this happens, if
I adjust volume the system shows Dummy Output instead of the usual speaker
small window. Also, one day when I was having right this issue I simply took a
screenshot to a game that I was playing and audio was played 廊.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.27
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: luca 1456 F pulseaudio
/dev/snd/pcmC0D0p: luca 1456 F...m pulseaudio
/dev/snd/controlC1: luca 1456 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: zorin:GNOME
DistroRelease: Zorin OS 16
InstallationDate: Installed on 2022-10-01 (325 days ago)
InstallationMedia: Zorin-OS 16.1 Core 64bit
Package: pulseaudio 1:13.99.1-1ubuntu3.13 [origin: Ubuntu]
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.15.0-78.85~20.04.1-generic 5.15.99
Tags: focal third-party-packages
Uname: Linux 5.15.0-78-generic x86_64
UnreportableReason: Questo non è un pacchetto ufficiale di Zorin. Rimuovere
tutti i pacchetti di terze parti, quindi riprovare.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 01/28/2011
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: K52N.218
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: K52N
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrK52N.218:bd01/28/2011:br4.6:svnASUSTeKComputerInc.:pnK52N:pvr1.0:rvnASUSTeKComputerInc.:rnK52N:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:sku:
dmi.product.name: K52N
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2029019/+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 1759014] Re: Netplan has no way to control DHCP client
I can confirm that on an up-to-date Ubuntu 22.04 use-dns doesn't work
with the NetworkManager renderer. It does work with networkd.
network:
ethernets:
enp2s0:
dhcp4: true
dhcp4-overrides:
use-dns: false
nameservers:
addresses: [9.9.9.9, 149.112.112.112]
search: []
renderer: NetworkManager
version: 2
$ resolvectl status
Global
Protocols: -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
resolv.conf mode: uplink
DNS Servers: 9.9.9.9
Link 2 (enp2s0)
Current Scopes: DNS
Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
DNS Servers: 9.9.9.9 149.112.112.112 192.168.0.1
DNS Domain: Home
(With option "use-dns: false" 192.168.0.1 shouldn't be added to the list of DNS
servers.)
With "renderer: networkd" it looks alright:
$ resolvectl status
Global
Protocols: -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
resolv.conf mode: uplink
DNS Servers: 9.9.9.9
Link 2 (enp2s0)
Current Scopes: DNS
Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
DNS Servers: 9.9.9.9 149.112.112.112
DNS Domain: Home
--
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/1759014
Title:
Netplan has no way to control DHCP client
Status in Default settings and artwork for Baltix OS:
New
Status in netplan:
Fix Released
Status in netplan.io package in Ubuntu:
Fix Released
Status in systemd package in Ubuntu:
Fix Released
Status in netplan.io source package in Bionic:
Fix Released
Status in systemd source package in Bionic:
Fix Released
Status in netplan.io source package in Cosmic:
Fix Released
Status in systemd source package in Cosmic:
Fix Released
Status in netplan.io source package in Disco:
Fix Released
Status in systemd source package in Disco:
Fix Released
Bug description:
[Impact]
DHCP configurations where custom settings (routes, nameservers, etc.) need to
be applied.
[Test case]
1) Configure netplan for the particulars of the network by configuring an
appropriate dhcp{4,6}-override stanza:
network:
version: 2
ethernets:
engreen:
dhcp4: true
dhcp4-overrides:
use-dns: false
use-routes: false
route-metric:
Additionally, if so required, add a custom DNS / routes to the
configuration. e.g.
nameservers:
search: [lab, kitchen]
addresses: [8.8.8.8]
(See https://netplan.io/reference#dhcp-overrides for the available
options)
2) Run 'netplan apply' or reboot to have the configuration applied.
3) Validate that the routes / DNS are properly ignored and/or replaced by the
defined values.
[Regression potential]
Minimal; this adds new values to the configuration generated for networkd or
NetworkManager. Existing configurations will remain unchanged, but new
configurations using the dhcp{4,6}-overrides fields will benefit from
additional flexibility.
---
Currently DHCP appears to be an all or nothing boolean, which is insufficient
for many network configurations.
Ideally all of the DHCP configuration options supported by systemd would also
be supported in netplan:
https://www.freedesktop.org/software/systemd/man/systemd.network.html#%5BDHCP%5D%20Section%20Options
As an example, consider the following netplan configuration:
network:
version: 2
renderer: networkd
ethernets:
enp0s3:
dhcp4: yes
nameservers: [8.8.8.8,8.8.4.4]
After running netplan apply I check the nameservers with systemd-
resolve --status and it shows:
DNS Servers: 8.8.8.8
8.8.4.4
192.168.1.1
Here, "192.168.1.1" was provided by my DHCP server. On this
particular node, I only want the manually configured DNS servers, but
netplan has no way to indicate this.
To manage notifications about this bug go to:
https://bugs.launchpad.net/baltix-default-settings/+bug/1759014/+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 2025982] Re: Warning 'failed to get driver name for fd 0' fails gtk tests
** Changed in: mesa (Debian) Status: Confirmed => Fix Released -- 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/2025982 Title: Warning 'failed to get driver name for fd 0' fails gtk tests Status in Mesa: Fix Released Status in mesa package in Ubuntu: Fix Released Status in mesa package in Debian: Fix Released Bug description: The new version displays that warning which makes the gtk autopkgtest red Upstream https://gitlab.freedesktop.org/mesa/mesa/-/issues/9199 Debian https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039922 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2025982/+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 2039868]
Hello, I'm having this same issue with my thinkpad z16 laptop, Ryzen
6850H and Radeon RX 6500M graphics card.
I do not use the laptop for gaming but for audio and video editing. I
have not had trouble with any video editing software but I can easily
reproduce the issue by loading up Ardour or Mixbus32C and either leaving
it alone or working. After 15 minutes the screen freezes although audio
will continue for a time. At this point Ardour or Mixbus will close and
I can continue using the machine. If I load up either program again it
will fail again, usually within a couple minutes and the whole laptop
will freeze up until I ctrl-alt-F2 to get to a terminal prompt.
The issue always happens when Im recording audio with an HDMI device
attached and 90% of the time without HDMI
I will attempt to set this kernel parameter amdgpu.mcbp=0 and report
back.
--
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/2039868
Title:
amdgpu reset during usage of firefox
Status in Linux:
Unknown
Status in linux package in Ubuntu:
Confirmed
Status in mesa package in Ubuntu:
New
Bug description:
Running nightly on 23.10 (since monday), I have been experiencing a
few amdgpu resets in the past hours
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-9-generic 6.5.0-9.9
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: ubuntu:GNOME
Date: Thu Oct 19 18:26:43 2023
HibernationDevice: RESUME=/dev/mapper/vg--ubuntu-lv--ubuntu--swap
InstallationDate: Installed on 2022-07-04 (472 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64
(20220419)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=fr_FR.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic
root=/dev/mapper/vg--ubuntu-lv--ubuntu--root ro rootflags=subvol=@ quiet splash
resume=/dev/mapper/vg--ubuntu-lv--ubuntu--swap vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9-generic N/A
linux-backports-modules-6.5.0-9-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-10-16 (3 days ago)
dmi.bios.date: 05/15/2023
dmi.bios.release: 1.24
dmi.bios.vendor: LENOVO
dmi.bios.version: R1MET54W (1.24 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21A0CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.24
dmi.modalias:
dmi:bvnLENOVO:bvrR1MET54W(1.24):bd05/15/2023:br1.24:efr1.24:svnLENOVO:pn21A0CTO1WW:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A0CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a:
dmi.product.family: ThinkPad P14s Gen 2a
dmi.product.name: 21A0CTO1WW
dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a
dmi.product.version: ThinkPad P14s Gen 2a
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2039868/+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 2039873] Re: liblxc-dev was built with LXC_DEVEL=1 in Ubuntu Jammy/Kinetic
The attachment "set LXC_DEVEL to 0" seems to be a debdiff. The ubuntu- sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/2039873 Title: liblxc-dev was built with LXC_DEVEL=1 in Ubuntu Jammy/Kinetic Status in lxc package in Ubuntu: New Bug description: Dear colleagues, As I can see from: - https://git.launchpad.net/ubuntu/+source/lxc/tree/configure?h=applied/ubuntu/jammy - https://git.launchpad.net/ubuntu/+source/lxc/tree/configure?h=applied/ubuntu/kinetic LXC 5.0.0 was built with LXC_DEVEL=1 set. But for release build we should have LXC_DEVEL=0. LXC_DEVEL is a variable that appears in the /usr/include/lxc/version.h and then can be (and actually it is) used by other projects to detect if liblxc-dev is a development build or stable. Having LXC_DEVEL=1 makes problems for the users who want to build projects those are depend on liblxc from source (for example, LXD, go-lxc: https://github.com/canonical/lxd/pull/12420). Q: Why it was not a problem for so long? A: Because LXC API was stable for a long time, but recently we have extended liblxc API (https://github.com/lxc/lxc/pull/4260) and dependant package go-lxc was updated too (https://github.com/lxc/go-lxc/pull/166). This change was developed properly to be backward compatible with the old versions of liblxc. But, there is a problem. If LXC_DEVEL=1 then the macro check VERSION_AT_LEAST (https://github.com/lxc/go-lxc/blob/ccae595aa49e779f7ecc9250329967aa546acd31/lxc-binding.h#L7) is disabled. That's why we should *not* have LXC_DEVEL=1 for *any* release build of LXC. And also, as I can see the source code that was used to build LXC 5.0.0 in Jammy/Kinetic is not precisely the same as in the official LXC 5.0.0 tag (https://github.com/lxc/lxc/tree/lxc-5.0.0). I understand that Jammy is a LTS release and making any changes is a problem and we should go through the SRU process. But I believe that we have to do something at least with LXC_DEVEL to make things work properly. Kind regards, Alex To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2039873/+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 2037205] Re: setuptools: FTBFS in mantic
** Changed in: setuptools (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/2037205 Title: setuptools: FTBFS in mantic Status in dh-python package in Ubuntu: New Status in setuptools package in Ubuntu: Fix Released Status in dh-python package in Debian: New Status in setuptools package in Debian: Fix Released Bug description: As seen in the mantic test rebuild [1], setuptools 68.1.2-1 currently FTBFS: Traceback (most recent call last): File "/<>/setuptools/config/setupcfg.py", line 284, in __setitem__ current_value = getattr(target_obj, option_name) AttributeError: 'MinimalDistribution' object has no attribute 'entry_points' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/<>/setup.py", line 92, in dist = setuptools.setup(**setup_params) File "/<>/setuptools/__init__.py", line 106, in setup _install_setup_requires(attrs) File "/<>/setuptools/__init__.py", line 77, in _install_setup_requires dist.parse_config_files(ignore_option_errors=True) File "/<>/setuptools/dist.py", line 895, in parse_config_files setupcfg.parse_configuration( File "/<>/setuptools/config/setupcfg.py", line 177, in parse_configuration options.parse() File "/<>/setuptools/config/setupcfg.py", line 500, in parse section_parser_method(section_options) File "/<>/setuptools/config/setupcfg.py", line 727, in parse_section_entry_points self['entry_points'] = parsed File "/<>/setuptools/config/setupcfg.py", line 286, in __setitem__ raise KeyError(option_name) KeyError: 'entry_points' E: pybuild pybuild:395: clean: plugin distutils failed with: exit code=1: python3.11 setup.py clean [1] https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20230830-mantic-mantic.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/2037205/+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 2039798] Re: please merge from debian instable 8.4 to address vulnerability
** Summary changed: - please upgrade to 8.4 to address vulnerability + please merge from debian instable 8.4 to address vulnerability -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/2039798 Title: please merge from debian instable 8.4 to address vulnerability Status in curl package in Ubuntu: Confirmed Bug description: Actually Mantic has 8.2.1 version A huge security issue is fixed with 8.4 : https://linuxsecurity.com/news/security-vulnerabilities/curl-8-4-released-for-addressing-a-big-security-vulnerability changelog: https://curl.se/changes.html Available on Debian Sid: https://packages.debian.org/sid/curl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/2039798/+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 2040055] [NEW] systemd-resolved stops resolving host names
Public bug reported: # lsb_release -rd No LSB modules are available. Description:Ubuntu 23.10 Release:23.10 # aptitude show 'systemd-resolved' Package: systemd-resolved Version: 253.5-1ubuntu6 State: installed The system is unable to resolve any DNS names. Whenever a DNS name shall be resolved the following error appears in the journal Oct 21 15:50:32 my-host.my-domain.tld systemd-resolved[114]: Failed to start query: Invalid argument If one manually tries to resolve a DNS name from the local stub resolver via dig @127.0.0.53 A www.google.com. another error message is added to the journal. However, resolving a DNS name from the configured upstream DNS server works perfectly dig @81.169.163.106 A www.google.com. Returns a proper response. (Note, 81.169.163.106 is the internal DNS server from my hoster.) Some more infos # resolvectl Global Protocols: -LLMNR mDNS=resolve -DNSOverTLS DNSSEC=no/unsupported resolv.conf mode: stub Current DNS Server: 81.169.163.106 DNS Servers: 81.169.163.106 85.214.7.22 DNS Domain: my-domain.tld Link 2 (venet0) Current Scopes: none Protocols: -DefaultRoute -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported # cat /etc/systemd/resolved.conf [Resolve] DNS=81.169.163.106 85.214.7.22 Domains=my-domain.tld # aptitude search '~i resolv' i libnss-resolve - nss module to resolve names via systemd-resolved i A systemd-resolved- systemd DNS resolver ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2040055 Title: systemd-resolved stops resolving host names Status in systemd package in Ubuntu: New Bug description: # lsb_release -rd No LSB modules are available. Description:Ubuntu 23.10 Release:23.10 # aptitude show 'systemd-resolved' Package: systemd-resolved Version: 253.5-1ubuntu6 State: installed The system is unable to resolve any DNS names. Whenever a DNS name shall be resolved the following error appears in the journal Oct 21 15:50:32 my-host.my-domain.tld systemd-resolved[114]: Failed to start query: Invalid argument If one manually tries to resolve a DNS name from the local stub resolver via dig @127.0.0.53 A www.google.com. another error message is added to the journal. However, resolving a DNS name from the configured upstream DNS server works perfectly dig @81.169.163.106 A www.google.com. Returns a proper response. (Note, 81.169.163.106 is the internal DNS server from my hoster.) Some more infos # resolvectl Global Protocols: -LLMNR mDNS=resolve -DNSOverTLS DNSSEC=no/unsupported resolv.conf mode: stub Current DNS Server: 81.169.163.106 DNS Servers: 81.169.163.106 85.214.7.22 DNS Domain: my-domain.tld Link 2 (venet0) Current Scopes: none Protocols: -DefaultRoute -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported # cat /etc/systemd/resolved.conf [Resolve] DNS=81.169.163.106 85.214.7.22 Domains=my-domain.tld # aptitude search '~i resolv' i libnss-resolve - nss module to resolve names via systemd-resolved i A systemd-resolved- systemd DNS resolver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2040055/+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 2040051] [NEW] systemd-networkd-wait-online terminates with "Could not create manager: Invalid argument"
Public bug reported: # lsb_release -rd No LSB modules are available. Description:Ubuntu 23.10 Release:23.10 # aptitude show systemd Package: systemd Version: 253.5-1ubuntu6 State: installed systemd-networkd-wait-online terminates with "Could not create manager: Invalid argument". This lets the corresponding service (systemd-networkd-wait- online.service) fail as well. The error also appears when one directly invokes /lib/systemd/systemd-networkd-wait-online from a shell. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2040051 Title: systemd-networkd-wait-online terminates with "Could not create manager: Invalid argument" Status in systemd package in Ubuntu: New Bug description: # lsb_release -rd No LSB modules are available. Description:Ubuntu 23.10 Release:23.10 # aptitude show systemd Package: systemd Version: 253.5-1ubuntu6 State: installed systemd-networkd-wait-online terminates with "Could not create manager: Invalid argument". This lets the corresponding service (systemd-networkd-wait- online.service) fail as well. The error also appears when one directly invokes /lib/systemd/systemd-networkd-wait-online from a shell. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2040051/+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 2040047] [NEW] Removing Python modules causes the removal of Xorg
Public bug reported: I tried to remove python3-keyring and was surprised to see that this would cause the removal of xorg and sddm. The dependency chain is something like: python3-keyring <- python3-launchpadlib <- python3-apport <- xserver-xorg <- sddm. It is completely unexpected and potentially embarrassing to end up with no graphical desktop after removing a random Python library. python3-apport should not be a hard dependency of xserver-xorg. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xserver-xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-35-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: KDE Date: Sat Oct 21 12:40:20 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] VanGogh [1002:163f] (rev ae) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] VanGogh [1002:0123] InstallationDate: Installed on 2023-10-15 (5 days ago) InstallationMedia: Kubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.1) MachineType: Valve Jupiter ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-35-generic root=UUID=84e67fd7-6fb5-4d82-9d36-7bb084af0af5 ro rootflags=subvol=@ mitigations=off zswap.enabled=1 zswap.compressor=lz4 zswap.zpool=z3fold zswap.max_pool_percent=30 amd_iommu=off amdgpu.gttsize=8128 spi_amd.speed_dev=1 audit=0 fbcon=vc:2-6 quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2023 dmi.bios.release: 1.16 dmi.bios.vendor: Valve dmi.bios.version: F7A0116 dmi.board.name: Jupiter dmi.board.vendor: Valve dmi.chassis.type: 8 dmi.chassis.vendor: Valve dmi.chassis.version: 1 dmi.ec.firmware.release: 1.14 dmi.modalias: dmi:bvnValve:bvrF7A0116:bd05/12/2023:br1.16:efr1.14:svnValve:pnJupiter:pvr1:rvnValve:rnJupiter:rvr:cvnValve:ct8:cvr1:sku: dmi.product.family: Aerith dmi.product.name: Jupiter dmi.product.version: 1 dmi.sys.vendor: Valve version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 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 jammy ubuntu wayland-session -- 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/2040047 Title: Removing Python modules causes the removal of Xorg Status in xorg package in Ubuntu: New Bug description: I tried to remove python3-keyring and was surprised to see that this would cause the removal of xorg and sddm. The dependency chain is something like: python3-keyring <- python3-launchpadlib <- python3-apport <- xserver-xorg <- sddm. It is completely unexpected and potentially embarrassing to end up with no graphical desktop after removing a random Python library. python3-apport should not be a hard dependency of xserver-xorg. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xserver-xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-35-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: KDE Date: Sat Oct 21 12:40:20 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] VanGogh [1002:163f] (rev ae) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] VanGogh [1002:0123] InstallationDate: Installed on 2023-10-15 (5 days ago) InstallationMedia: Kubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.1) MachineType: Valve Jupiter ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-35-generic root=UUID=84e67fd7-6fb5-4d82-9d36-7bb084af0af5 ro rootflags=subvol=@ mitigations=off zswap.enabled=1 zswap.compressor=lz4 zswap.zpool=z3fold zswap.max_pool_percent=30 amd_iommu=off amdgpu.gttsize=8128 spi_amd.speed_dev=1 audit=0 fbcon=vc:2-6 quiet splash
[Touch-packages] [Bug 1577599] Re: [CM1855, Realtek ALC892, Green Line Out, Rear] Sound is distorted / Audio Notification unstable (Popping in/out)
This bug report provides detailed information about an audio issue on Ubuntu 16.04, including system specifications and relevant diagnostic data. The inclusion of video and forum posts for further context is commendable, making it easier for others to understand and assist in resolving the problem. Also read it :https://kqsolicitors.com/immigration-attorney/healthcare- visa/invitation-letter-for-visa-uk/ -- 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/1577599 Title: [CM1855, Realtek ALC892, Green Line Out, Rear] Sound is distorted / Audio Notification unstable (Popping in/out) Status in alsa-driver package in Ubuntu: Confirmed Bug description: For a better explanation, here is a video I've made. https://youtu.be/8q092XpLT-Y For further diagnostics, here is a ubuntu forum post I've made. http://ubuntuforums.org/showthread.php?t=2322708 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC2D0c: deviantxs 1672 F...m pulseaudio /dev/snd/controlC2: deviantxs 1672 F pulseaudio /dev/snd/controlC0: deviantxs 1672 F pulseaudio /dev/snd/controlC1: deviantxs 1672 F pulseaudio CurrentDesktop: Unity Date: Mon May 2 16:35:54 2016 InstallationDate: Installed on 2016-04-30 (2 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:SB failed Symptom_Card: Built-in Audio - HDA ATI SB Symptom_Jack: Green Line Out, Rear Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [CM1855, Realtek ALC892, Green Line Out, Rear] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/20/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: CM1855 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1501:bd08/20/2013:svnASUSTeKCOMPUTERINC.:pnCM1855:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnCM1855:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: CM1855 dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1577599/+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
Install VNC on a remote box (or VM), connect using VNC client, try to run firefox. Stop telling users it's their fault for having mis-configured machines or using "non-standard logins" (whatever one of those is). Jeez, I've been a fan of Ubuntu over the years, but this piece of functionality is simply broken for certain use-cases. -- 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
