[Touch-packages] [Bug 1008217] Re: Package Description needs content.
** Branch linked: lp:~crisdel/whoopsie/whoopsie -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1008217 Title: Package Description needs content. Status in Whoopsie: Confirmed Status in whoopsie package in Ubuntu: Confirmed Bug description: Hello, The description didn't populate: http://packages.ubuntu.com/precise/whoopsie Plus after reading it using apt-cache I find that it's a little too generic. Here is some of the information the description is missing. 1. Where do the reports go, even if it is bugs.launchpad.net. What URL/interface is used for the actual submitting... I.E. what do I need to open up in my firewall or ?http? proxy. 2. How can I view the reports whoopsie is submitting, for my system and for every one else. The two main goals are so that users can get an idea of what whoopsie will do if they install it and what it's done since it's been installed. 3. Who will this benefit and how much will it cost in CPU/bandwidth/ect. How important is it that every box have whoopsie. Include at least two blurbs. Thank you. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: whoopsie 0.1.32 ProcVersionSignature: Ubuntu 3.2.0-23.31-lowlatency-pae 3.2.14 Uname: Linux 3.2.0-23-lowlatency-pae i686 ApportVersion: 2.0.1-0ubuntu8 Architecture: i386 CrashReports: 640:0:112:98174:2012-05-31 18:33:06.18337 -0500:2012-06-03 15:03:58.900679755 -0500:/var/crash/_sbin_alsactl.0.crash 600:110:112:0:2012-06-03 15:05:19.623803615 -0500:2012-06-03 15:05:19.623803615 -0500:/var/crash/_sbin_alsactl.0.uploaded 644:0:0:0:2012-05-31 13:57:04.779285010 -0500:2012-05-31 13:57:04.779285010 -0500:/var/crash/_sbin_alsactl.0.upload Date: Sun Jun 3 15:18:09 2012 SourcePackage: whoopsie-daisy UpgradeStatus: Upgraded to precise on 2012-01-03 (152 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/whoopsie/+bug/1008217/+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 1995157] [NEW] Permission Denied while using lates verions of Openssh client
Public bug reported: Hi, I am having issues in connecting to OpenSSH Server. Error message is Permission Denied (publickey) I am having following versions of OpenSSH Packages : 1) Windows 10 Client : OpenSSH_8.5p1, OpenSSL 1.1.1k 25 Mar 2021 (Installed via Git - older version) 1) Windows 11 Client : OpenSSH_9.0p1, OpenSSL 1.1.1q 5 Jul 2022(Installed via Git 2.38.1 ) 2) Windows 11 Client : OpenSSH_for_Windows_8.6p1 LibreSSL 3.4.3 (Installed via Windows 11 ) 3) Ubuntu 14.04 Server : OpenSSH_6.6.1p1 OpenSSL 1.0.1f 4) Ubuntu 22 Server : OpenSSH_8.9p1 Ubuntu-3, OpenSSL 3.0.2 15 Mar 2022 I have recenty upgraded my WIndows Desktop & installed latest Windows 11 along with latest version of Git. I am having several servers running Ubuntu 14.04 & connecting through git-bash. In my previous windows 10 version of OpenSSH I am able to successfully connect to Ubuntu 14.04 servers. But after upgrading git to ver 9.0p1 I am unable to connect. This latest version I can connect to Ubuntu 22 Servers successfully. I am having single set of public & private keys which are properly installed. Old version of OpenSSH Client (8.5 / 8.6) can connect properly to both servers Ubuntu 14.04 & 22 New version of OpenSSH Client 9.0p1 can connect only to Ubuntu 22 Servers. On 14.04 server getting Permission Denied (publickey) message Thanks Ravi ** Affects: openssh (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1995157 Title: Permission Denied while using lates verions of Openssh client Status in openssh package in Ubuntu: New Bug description: Hi, I am having issues in connecting to OpenSSH Server. Error message is Permission Denied (publickey) I am having following versions of OpenSSH Packages : 1) Windows 10 Client : OpenSSH_8.5p1, OpenSSL 1.1.1k 25 Mar 2021 (Installed via Git - older version) 1) Windows 11 Client : OpenSSH_9.0p1, OpenSSL 1.1.1q 5 Jul 2022(Installed via Git 2.38.1 ) 2) Windows 11 Client : OpenSSH_for_Windows_8.6p1 LibreSSL 3.4.3 (Installed via Windows 11 ) 3) Ubuntu 14.04 Server : OpenSSH_6.6.1p1 OpenSSL 1.0.1f 4) Ubuntu 22 Server : OpenSSH_8.9p1 Ubuntu-3, OpenSSL 3.0.2 15 Mar 2022 I have recenty upgraded my WIndows Desktop & installed latest Windows 11 along with latest version of Git. I am having several servers running Ubuntu 14.04 & connecting through git-bash. In my previous windows 10 version of OpenSSH I am able to successfully connect to Ubuntu 14.04 servers. But after upgrading git to ver 9.0p1 I am unable to connect. This latest version I can connect to Ubuntu 22 Servers successfully. I am having single set of public & private keys which are properly installed. Old version of OpenSSH Client (8.5 / 8.6) can connect properly to both servers Ubuntu 14.04 & 22 New version of OpenSSH Client 9.0p1 can connect only to Ubuntu 22 Servers. On 14.04 server getting Permission Denied (publickey) message Thanks Ravi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1995157/+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 1987126] Re: No audio devices are recognized
[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Expired -- 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/1987126 Title: No audio devices are recognized Status in pulseaudio package in Ubuntu: Expired Bug description: No audio devices are recognized, both in and out. This worked on 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: pulseaudio 1:16.1+dfsg1-1ubuntu1 [modified: usr/share/pulseaudio/alsa-mixer/paths/analog-output-headphones.conf] ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.22.0-0ubuntu4 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC1', '/dev/snd/pcmC1D0c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Aug 19 11:35:58 2022 InstallationDate: Installed on 2022-07-09 (41 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to kinetic on 2022-08-19 (0 days ago) dmi.bios.date: 09/14/2018 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0904 dmi.board.asset.tag: Default string dmi.board.name: PRIME H370M-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Nobilis dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0904:bd09/14/2018:br5.13:svnEquusComputerSystems:pnNobilis:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEH370M-PLUS:rvrRev1.xx:cvnNobilis:ct3:cvrDefaultstring:skuASUS_MB_CNL: dmi.product.family: To be filled by O.E.M. dmi.product.name: Nobilis dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: Equus Computer Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1987126/+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 1987573] Re: /home on btrfs subvolume shared with / stops boot; adding nofail to fstab fixes it
[Expired for systemd (Ubuntu) because there has been no activity for 60 days.] ** Changed in: systemd (Ubuntu) Status: Incomplete => Expired -- 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/1987573 Title: /home on btrfs subvolume shared with / stops boot; adding nofail to fstab fixes it Status in systemd package in Ubuntu: Expired Bug description: After performing `do-release-upgrade` from 20.04 to 22.04.01, the system failed to boot with a message of: Failed to mount /home Dependency failed for Local File Systems. It took some work to figure out, but adding "nofail" to the fstab line allowed boot to proceed, and with that, the system appears to be working without issue. Both /boot and /home are mounted from subvolumes on the same btrfs filesystem. The working fstab is below: # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # LABEL=Root / btrfs defaults,subvol=@ 0 1 LABEL=Root /home btrfs defaults,subvol=@home,nofail 0 2 LABEL=EscherBackup /mnt/EscherBackup btrfs defaults0 2 LABEL=PicassoBackup /mnt/PicassoBackup btrfs defaults0 2 LABEL=scratch /mnt/scratchbtrfs defaults0 2 /dev/mapper/cryptswap1 none swap sw 0 0 /dev/mapper/cryptswap2 none swap sw 0 0 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.13 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu Date: Wed Aug 24 20:16:42 2022 EcryptfsInUse: Yes PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to jammy on 2022-08-24 (0 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1987573/+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 1930914] Re: ubuntu-minimal depends on ubuntu-advantage-tools
ubuntu-minimal should absolutely not force install of ubuntu-advantage- tools. We're being force fed CLI ads via ubuntu-advantage-tools and we HATE it. This package should at best be a 'recommends', and even then, probably not. I have no need of this spammy software, and yet I'm forced to remove the entire meta package if I don't want it?! This is what a mass exodus of users sounds like. -- 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/1930914 Title: ubuntu-minimal depends on ubuntu-advantage-tools Status in ubuntu-meta package in Ubuntu: Won't Fix Bug description: This is counter to #1566183 There is no reason to enforce desktop users who manage machine on their own to install ubuntu-advantage- tools, especially when this is 'minimal' version. This should include only essential packages to make the OS functional ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-minimal 1.450.2 ProcVersionSignature: Ubuntu 5.4.0-73.82-lowlatency 5.4.106 Uname: Linux 5.4.0-73-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Jun 4 18:54:56 2021 InstallationDate: Installed on 2020-01-29 (491 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: ubuntu-meta UpgradeStatus: Upgraded to focal on 2020-06-27 (342 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1930914/+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 1995048] Re: reboot reboots system when --poweroff is passed
Fixed upstream: https://github.com/systemd/systemd/pull/25172. -- 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/1995048 Title: reboot reboots system when --poweroff is passed Status in systemd package in Ubuntu: Triaged Bug description: The feature of passing "--poweroff" to the reboot command to "Power- off the machine, regardless of which one of the three commands is invoked." is broken. Either that or the man page is. This doesn't matter much to me anymore now that I found out that you can also pass "-f" to "poweroff" when debugging, but it confused me a lot at first. $ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 $ apt-cache policy systemd-sysv systemd-sysv: Installed: 249.11-0ubuntu3.6 Candidate: 249.11-0ubuntu3.6 Version table: *** 249.11-0ubuntu3.6 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 249.11-0ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages # Expected behaviour The system to power off. # Actual behaviour The system reboots. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-09-19 (39 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox Package: systemd 249.11-0ubuntu3.6 PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=11e9994e-8b05-42e7-949a-2f635b160285 ro text debug ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Tags: jammy Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1995048/+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 1981385] Re: initrd lacks modules to mount boot image from http boot
Uploaded to Jammy, pending normal SRU processing.
--
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/1981385
Title:
initrd lacks modules to mount boot image from http boot
Status in initramfs-tools package in Ubuntu:
Fix Released
Status in initramfs-tools source package in Jammy:
In Progress
Bug description:
[ Impact ]
* If you use UEFI http boot to boot an image (rather than an EFI
executable) and get all the way to a normal userspace, you can
access the boot image as /dev/pmem0. But this is not accessible in
the initrd; presumably some modules are missing.
* This is desirable because then you can just feed an installer ISO to
a machine via http boot and the installer just works as normal
* Add support for physical pmem devices, and simulation thereof with
the memmap kernel command line parameter
* The initrd is larger
[ Test Plan ]
* unpack an initrd on a Jammy system with the generic kernel
metapackage with unmkinitramfs
* observe that the directories kernel/drivers/{nvdimm,dax,acpi/nfit}
are not present
* install the updated initramfs-tools packages from proposed
* again unpack an initrd on a Jammy system with the generic kernel
metapackage with unmkinitramfs
* observe that the directories kernel/drivers/{nvdimm,dax,acpi/nfit}
are present now
* reboot to confirm that the system still boots
* modify /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT to contain a
memmap entry - memmap=1G!4G seems to work on many systems over 4G of
RAM, or do `dmesg | grep BIOS-e820` to observe the memory regions
and select a usable one.
* update-grub and reboot again
* a /dev/pmem device should now be present on the system
[ Where problems could occur ]
* The growth of the files in /boot will accelerate issues for users
who have a dedicated boot partition that is not large enough
[ Other Info ]
* Details on the memmap kernel command line parameter:
https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt
* PMEM simulation with memmap:
https://docs.pmem.io/persistent-memory/getting-started-guide/creating-development-environments/linux-environments/linux-memmap
[ Original Bug Description ]
If you use UEFI http boot to boot an image (rather than an EFI
executable) and get all the way to a normal userspace, you can access
the boot image as /dev/pmem0. But this is not accessible in the
initrd; presumably some modules are missing. Dimitri added some
modules that are clearly going to be necessary (kernel/drivers/nvdimm)
in 0.140ubuntu14 and I added kernel/drivers/dax too in local
experiments but this appears not to be enough to get it to appear.
This is desirable because then you can just feed an installer ISO to a
machine via http boot and the installer just works as normal (the
speed and, uh, quality, of the implementation of HTTP in a given
machine's firmware may mean this isn't always the best option but it
would be nice if it worked in case someone's machine actually does
this well).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1981385/+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 1994936] Re: initramfs need to mount efivarfs because kernel 6.0 deprecated 'efivars' sysfs interface
** Tags added: foundations-todo -- 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/1994936 Title: initramfs need to mount efivarfs because kernel 6.0 deprecated 'efivars' sysfs interface Status in OEM Priority Project: Confirmed Status in initramfs-tools package in Ubuntu: New Status in initramfs-tools package in Debian: New Bug description: [ Impact ] kernel 6.0 deprecated efivars sysfs interface [1]. For Intel VROC RAID, mdadm needs initramfs to mount efivarfs instead. [1] The commit: commit 0f5b2c69a4cbe4166ca24b76d5ada98ed2867741 Author: Ard Biesheuvel Date: Mon Jun 20 13:34:03 2022 +0200 efi: vars: Remove deprecated 'efivars' sysfs interface [ Test Plan ] 1. Install initramfs-tools 2. update-initramfs -u 3. unmkinitramfs initrd.img-`uname -r` /tmp/extract-initramfs 4. Check if boot script 00_mount_efivarfs exists in directory /tmp/extract-initramfs/main/scripts/init-top/ 5. Check /tmp/extract-initramfs/main/scripts/init-top/ORDER if the boot script 00_mount_efivarfs will be execute before udev. [ Where problems could occur ] Not sure if there any other tools/utilities also need to mount efivarfs as early as mdadm but the probability of file conflict should be very low. Also, there are no impact mounting efivarfs multiple times. mount: /sys/firmware/efi/efivars: efivarfs already mounted on /sys/firmware/efi/efivars. [ Scope ] Jammy, Kinetic [ Other Info ] The private bug link https://bugs.launchpad.net/somerville/+bug/1990231 debian MR: https://salsa.debian.org/kernel-team/initramfs-tools/-/merge_requests/66 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1994936/+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 1994165] Re: CMS_final: do not ignore CMS_dataFinal result
** Tags added: foundations-triage-discuss -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1994165 Title: CMS_final: do not ignore CMS_dataFinal result Status in openssl package in Ubuntu: Triaged Status in openssl source package in Jammy: Triaged Status in openssl source package in Kinetic: Triaged Bug description: https://github.com/openssl/openssl/pull/18876 The CMS_dataFinal result is important as signature may fail, however, it is ignored while returning success from CMS_final. Please add this fix to The openssl 3.0.2 "Jammy Jellyfish (supported)" Thanks Upstream commit: ``` commit 67c0460b89cc1b0644a1a59af78284dfd8d720af Author: Alon Bar-Lev Date: Tue Jul 26 15:17:06 2022 +0300 Handle SMIME_crlf_copy return code Currently the SMIME_crlf_copy result is ignored in all usages. It does return failure when memory allocation fails. This patch handles the SMIME_crlf_copy return code in all occurrences. Signed-off-by: Alon Bar-Lev Reviewed-by: Tomas Mraz Reviewed-by: Paul Dale Reviewed-by: Hugo Landau (Merged from https://github.com/openssl/openssl/pull/18876) ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1994165/+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 1992105] Re: missing httpform plugin for saslauthd
Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1992105 Title: missing httpform plugin for saslauthd Status in cyrus-sasl2 package in Ubuntu: In Progress Status in cyrus-sasl2 source package in Focal: In Progress Status in cyrus-sasl2 source package in Jammy: In Progress Status in cyrus-sasl2 source package in Kinetic: In Progress Status in cyrus-sasl2 source package in Lunar: In Progress Bug description: Hi, we noticed missing httpform plugin for saslauthd. We are migrating from Centos. == On Centos (Notice the httpform at the end) /usr/sbin/saslauthd -v saslauthd 2.1.26 authentication mechanisms: getpwent kerberos5 pam rimap shadow ldap httpform == On Ubuntu jammy /usr/sbin/saslauthd -v saslauthd 2.1.27 authentication mechanisms: sasldb getpwent kerberos5 pam rimap shadow ldap == Potential fix add the "--enable-httpform" flag to the sasl2-bin package build ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: sasl2-bin 2.1.27+dfsg2-3ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic aarch64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: arm64 CasperMD5CheckResult: unknown Date: Thu Oct 6 14:54:13 2022 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: cyrus-sasl2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1992105/+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 1995137] [NEW] "sun4i-drm_dri.so" is missing from libg1-mesa-dri on riscv64
Public bug reported: "sun4i-drm_dri.so" is needed for some RISC-V platforms such as the Allwinner D1. This file is missing from the riscv64 packages, but present on others. This affects (at least) 20.04 and 22.04. itrue@lxc-focal ~/tmp> dpkg -c libgl1-mesa-dri_21.2.6-0ubuntu0.1~20.04.2_arm64.deb | grep _dri.so *snip* hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/aarch64-linux-gnu/dri/sun4i-drm_dri.so link to ./usr/lib/aarch64-linux-gnu/dri/armada-drm_dri.so *snip* itrue@lxc-focal ~/tmp> dpkg -c libgl1-mesa-dri_21.2.6-0ubuntu0.1~20.04.2_riscv64.deb | grep _dri.so -rw-r--r-- root/root 16498024 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/nouveau_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so -rw-r--r-- root/root 4692400 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/nouveau_vieux_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/r200_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/nouveau_vieux_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/r300_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/r600_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/radeon_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/nouveau_vieux_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/radeonsi_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/swrast_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/virtio_gpu_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/zink_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Description changed: "sun4i-drm_dri.so" is needed for some RISC-V platforms such as the Allwinner D1. This file is missing from the riscv64 packages, but present on others. This affects (at least) 20.04 and 22.04. itrue@lxc-focal ~/tmp> dpkg -c libgl1-mesa-dri_21.2.6-0ubuntu0.1~20.04.2_arm64.deb | grep _dri.so - -rw-r--r-- root/root 23619952 2022-03-08 16:37 ./usr/lib/aarch64-linux-gnu/dri/armada-drm_dri.so - hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/aarch64-linux-gnu/dri/d3d12_dri.so link to ./usr/lib/aarch64-linux-gnu/dri/armada-drm_dri.so - hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/aarch64-linux-gnu/dri/etnaviv_dri.so link to ./usr/lib/aarch64-linux-gnu/dri/armada-drm_dri.so - hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/aarch64-linux-gnu/dri/exynos_dri.so link to ./usr/lib/aarch64-linux-gnu/dri/armada-drm_dri.so - hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/aarch64-linux-gnu/dri/hx8357d_dri.so link to ./usr/lib/aarch64-linux-gnu/dri/armada-drm_dri.so - hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/aarch64-linux-gnu/dri/ili9225_dri.so link to ./usr/lib/aarch64-linux-gnu/dri/armada-drm_dri.so - hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/aarch64-linux-gnu/dri/ili9341_dri.so link to ./usr/lib/aarch64-linux-gnu/dri/armada-drm_dri.so - hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/aarch64-linux-gnu/dri/imx-dcss_dri.so link to ./usr/lib/aarch64-linux-gnu/dri/armada-drm_dri.so - hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/aarch64-linux-gnu/dri/imx-drm_dri.so link to ./usr/lib/aarch64-linux-gnu/dri/armada-drm_dri.so - hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/aarch64-linux-gnu/dri/ingenic-drm_dri.so link to ./usr/lib/aarch64-linux-gnu/dri/armada-drm_dri.so - hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/aarch64-linux-gnu/dri/kgsl_dri.so link to ./usr/lib/aarch64-linux-gnu/dri/armada-drm_dri.so - hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/aarch64-linux-gnu/dri/kms_swrast_dri.so link to ./usr/lib/aarch64-linux-gnu/dri/armada-drm_dri.so - hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/aarch64-linux-gnu/dri/lima_dri.so link to ./usr/lib/aarch64-linux-gnu/dri/armada-drm_dri.so - hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/aarch64-linux-gnu/dri/mali-dp_dri.so link to ./usr/lib/aarch64-linux-gnu/dri/armada-drm_dri.so - hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/aarch64-linux-gnu/dri/mcde_dri.so link to ./usr/lib/aarch64-linux-gnu/dri/armada-drm_dri.so - hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/aarch64-linux-gnu/dri/mediatek_dri.so link to
[Touch-packages] [Bug 1992105] Re: missing httpform plugin for saslauthd
Sure, I'll add that in and update the ppa for you. Currently we're waiting on the new development release cycle (23.04) to get started to add it there, then I can officially backport it to kinetic, jammy, and focal. ** Also affects: cyrus-sasl2 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: cyrus-sasl2 (Ubuntu Lunar) Importance: Undecided Assignee: Lena Voytek (lvoytek) Status: In Progress ** Changed in: cyrus-sasl2 (Ubuntu Focal) Status: New => In Progress ** Changed in: cyrus-sasl2 (Ubuntu Focal) Assignee: (unassigned) => Lena Voytek (lvoytek) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1992105 Title: missing httpform plugin for saslauthd Status in cyrus-sasl2 package in Ubuntu: In Progress Status in cyrus-sasl2 source package in Focal: In Progress Status in cyrus-sasl2 source package in Jammy: In Progress Status in cyrus-sasl2 source package in Kinetic: In Progress Status in cyrus-sasl2 source package in Lunar: In Progress Bug description: Hi, we noticed missing httpform plugin for saslauthd. We are migrating from Centos. == On Centos (Notice the httpform at the end) /usr/sbin/saslauthd -v saslauthd 2.1.26 authentication mechanisms: getpwent kerberos5 pam rimap shadow ldap httpform == On Ubuntu jammy /usr/sbin/saslauthd -v saslauthd 2.1.27 authentication mechanisms: sasldb getpwent kerberos5 pam rimap shadow ldap == Potential fix add the "--enable-httpform" flag to the sasl2-bin package build ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: sasl2-bin 2.1.27+dfsg2-3ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic aarch64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: arm64 CasperMD5CheckResult: unknown Date: Thu Oct 6 14:54:13 2022 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: cyrus-sasl2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1992105/+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 1993800]
This is an autogenerated message for OBS integration: This bug (1204267) was mentioned in https://build.opensuse.org/request/show/1031948 Factory / llvm15 -- 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/1993800 Title: LLVM ERROR: Cannot select: 0x2f689c8: v4i32 = ARMISD::VCMPZ 0x2f696b8, Constant:i32<2> Status in LLVM: New Status in llvm-toolchain-15 package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in llvm-toolchain-15 package in openSUSE: Unknown Bug description: LLVM ERROR: Cannot select: 0x2f689c8: v4i32 = ARMISD::VCMPZ 0x2f696b8, Constant:i32<2> 0x2f696b8: v4i32,ch = ARMISD::VLD1DUP<(load (s32) from %ir.212)> 0x2aad434, 0x2f84090:1, Constant:i32<4> 0x2f84090: i32,i32,ch = load<(load (s32) from %ir.209, align 8), > 0x2aad434, 0x2f63a30, Constant:i32<64> 0x2f63a30: i32,ch = CopyFromReg 0x2aad434, Register:i32 %23 0x2f51c10: i32 = Register %23 0x2f82500: i32 = Constant<64> 0x2f81b28: i32 = Constant<4> 0x2f81e40: i32 = Constant<2> In function: fs_variant_partial [https://launchpadlibrarian.net/629171689/buildlog_ubuntu-kinetic- armhf.mutter_43.0-1ubuntu3_BUILDING.txt.gz] Although "LLVM ERROR: Cannot select" seems to be from LLVM, I can't determine what project "fs_variant_partial" is in. Sounds like it might be in some old version of Mesa? The start of the log suggests it's running on focal. To manage notifications about this bug go to: https://bugs.launchpad.net/llvm/+bug/1993800/+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 1992105] Re: missing httpform plugin for saslauthd
Hi Lena, Would it be possible for this to also be enabled on Ubuntu 20.04 (Focal)? We have some servers that need to run on 20.04 because of some unrelated software compatibility issues. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1992105 Title: missing httpform plugin for saslauthd Status in cyrus-sasl2 package in Ubuntu: In Progress Status in cyrus-sasl2 source package in Jammy: In Progress Status in cyrus-sasl2 source package in Kinetic: In Progress Bug description: Hi, we noticed missing httpform plugin for saslauthd. We are migrating from Centos. == On Centos (Notice the httpform at the end) /usr/sbin/saslauthd -v saslauthd 2.1.26 authentication mechanisms: getpwent kerberos5 pam rimap shadow ldap httpform == On Ubuntu jammy /usr/sbin/saslauthd -v saslauthd 2.1.27 authentication mechanisms: sasldb getpwent kerberos5 pam rimap shadow ldap == Potential fix add the "--enable-httpform" flag to the sasl2-bin package build ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: sasl2-bin 2.1.27+dfsg2-3ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic aarch64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: arm64 CasperMD5CheckResult: unknown Date: Thu Oct 6 14:54:13 2022 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: cyrus-sasl2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1992105/+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 1995048] Re: reboot reboots system when --poweroff is passed
Looking at the upstream code, the --poweroff option is intentionally ignored when reboot is invoked [1]. The man page should be fixed to document this exception. [1] https://github.com/systemd/systemd/commit/a042efad57741e90ee78b69c57310858295bf3fc ** Changed in: systemd (Ubuntu) Status: New => Triaged ** Changed in: systemd (Ubuntu) Importance: Undecided => Low -- 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/1995048 Title: reboot reboots system when --poweroff is passed Status in systemd package in Ubuntu: Triaged Bug description: The feature of passing "--poweroff" to the reboot command to "Power- off the machine, regardless of which one of the three commands is invoked." is broken. Either that or the man page is. This doesn't matter much to me anymore now that I found out that you can also pass "-f" to "poweroff" when debugging, but it confused me a lot at first. $ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 $ apt-cache policy systemd-sysv systemd-sysv: Installed: 249.11-0ubuntu3.6 Candidate: 249.11-0ubuntu3.6 Version table: *** 249.11-0ubuntu3.6 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 249.11-0ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages # Expected behaviour The system to power off. # Actual behaviour The system reboots. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-09-19 (39 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox Package: systemd 249.11-0ubuntu3.6 PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=11e9994e-8b05-42e7-949a-2f635b160285 ro text debug ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Tags: jammy Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1995048/+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 1965076] Re: rsync --update incorrectly reports file "is newer" than itself
Assigning this to myself to do the sponsoring. ** Changed in: rsync (Ubuntu Jammy) Assignee: (unassigned) => Paride Legovini (paride) ** Changed in: rsync (Ubuntu Jammy) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1965076 Title: rsync --update incorrectly reports file "is newer" than itself Status in rsync: Fix Released Status in rsync package in Ubuntu: Fix Released Status in rsync source package in Jammy: In Progress Bug description: [Impact] This bug causes rsync 3.2.3 to wrongly report files with an exact same mtime as being "newer" implying they would need to be transfered/sync'ed where in fact they are "uptodate". This breaks users' scripts depending on "is newer" to signal that files need to be sync'ed when in fact, they don't need to be. [Test Plan] Steps to reproduce: 1. Create a local file: $ touch foo 2. Check if rsync would transfer it using the --update option: $ rsync -avv --update foo . If the regression is present, "foo is newer" would be reported: ``` sending incremental file list delta-transmission disabled for local transfer or --whole-file foo is newer total: matches=0 hash_hits=0 false_alarms=0 data=0 sent 61 bytes received 96 bytes 314.00 bytes/sec total size is 0 speedup is 0.00 ``` If the updated package is installed (from -proposed), "foo is uptodate" should be reported: ``` sending incremental file list delta-transmission disabled for local transfer or --whole-file foo is uptodate total: matches=0 hash_hits=0 false_alarms=0 data=0 sent 60 bytes received 106 bytes 332.00 bytes/sec total size is 0 speedup is 0.00 ``` [Regression potential] The patch changes the behavior of --update so if something goes wrong, it could break backup/sync jobs. To mitiate that, manual testing of rsync with and without the --update option was done in addition to the quick [Test Plan] outlined above. Please note the patch restores the behavior from before version 3.2.3 and has been integrated by upstream in September 2021. It also is in Kinetic where no visible regression was observed. [Original description] rsync 3.2.3 has a broken "--update" option.See the examples below. The "--update" option incorrectly makes rsync say a file is newer than itself. Remove the "--update" option, and rsync correctly says the file is "uptodate". The right output should of course be "is uptodate" in all cases. This bug also shows up between machines if the source rsync is 3.1.3 and the destination is 3.2.3. The bug does not show up if the source rsync is 3.2.3 and the destination is 3.1.3. The bug was fixed upstream in June 2020: https://github.com/WayneD/rsync/issues/98 $ touch foo $ rsync --update --info=skip foo foo foo is newer<=== THIS IS NOT CORRECT - A file can't be newer than itself. Obviously a file should not be listed as newer than itself. Another way: $ touch foo $ rsync -avv --update foo . delta-transmission disabled for local transfer or --whole-file foo is newer <=== THIS IS NOT CORRECT - A file can't be newer than itself. total: matches=0 hash_hits=0 false_alarms=0 data=0 sent 38 bytes received 96 bytes 268.00 bytes/sec total size is 0 speedup is 0.00 $ rsync -avv foo . delta-transmission disabled for local transfer or --whole-file foo is uptodate <=== THIS IS CORRECT total: matches=0 hash_hits=0 false_alarms=0 data=0 sent 41 bytes received 106 bytes 294.00 bytes/sec total size is 0 speedup is 0.00 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: rsync 3.2.3-4ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Mar 15 22:47:44 2022 InstallationDate: Installed on 2022-03-16 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: rsync UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/rsync/+bug/1965076/+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 1995105] Re: add-apt-repository fails if it encounters immutable sources.list.d entry
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: software-properties (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1995105 Title: add-apt-repository fails if it encounters immutable sources.list.d entry Status in software-properties package in Ubuntu: Confirmed Bug description: Reason: We're trying to protect an internal APT source from trivial accidental modification by users (who do have sudo as root). Steps to reproduce: echo '# dummy' > /etc/apt/sources.list.d/dummy.list chattr +i /etc/apt/sources.list.d/dummy.list add-apt-repository -y ppa:longsleep/golang-backports Expected behaviour: New sources.list for the PPA gets created. Observed behaviour: Traceback (most recent call last): File "/usr/bin/add-apt-repository", line 364, in sys.exit(0 if addaptrepo.main() else 1) File "/usr/bin/add-apt-repository", line 357, in main shortcut.add() File "/usr/lib/python3/dist-packages/softwareproperties/shortcuthandler.py", line 221, in add self.add_source() File "/usr/lib/python3/dist-packages/softwareproperties/shortcuthandler.py", line 307, in add_source sourceslist.save() File "/usr/lib/python3/dist-packages/softwareproperties/extendedsourceslist.py", line 391, in save with open(filename, "w") as f: PermissionError: [Errno 1] Operation not permitted: '/etc/apt/sources.list.d/dummy.list' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1995105/+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 1956115] Re: ubuntu-advantage-tools ' MOTD is incompatible with Ubuntu Legal's MOTD opt-out directions.
Start here - https://bugs.launchpad.net/ubuntu/+source/base- files/+bug/1803601 Attempts are made which means the policy method doesn't actually opt-out due to a bug. The file is not created by a package so you won't be asked if you want to overwrite the specific value or change it in the future for certain operations. The problem is three fold. One technical in the present, one future and one legal which encompasses both. Then read the actual policy - >How do you disable the collection? >Note that all of the system information may be shared with Canonical. If you >would prefer that Canonical does not receive any item of system information, >please do not consent to it being sent. You can disable this service as >follows: >/etc/default/motd-news has an ENABLED=1 setting that if set to 0 will turn off >this functionality. This implies that without changing the setting that you agree to collection. The file does not exist. The recent ESM servicing hook advertising and communication features are an example of future impact as it relates further into the scope of this policy. >Along with this data, the IP address and other network information is transmitted to facilitate communication on the internet from the Ubuntu machine to Canonical. This information is not stored by Canonical. This is clearly the one way we have to official opt-out for current and future consent. It isn't implemented correctly and cannot explicitly be accomplished in accordance with Canonical Group Limited's own written policy. -- 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/1956115 Title: ubuntu-advantage-tools ' MOTD is incompatible with Ubuntu Legal's MOTD opt-out directions. Status in base-files package in Ubuntu: Incomplete Status in ubuntu-advantage-tools package in Ubuntu: Expired Bug description: https://ubuntu.com/legal/motd This file does not exist in Jammy 22.04. This wouldn't be a problem if it was actually removable without having to build custom metapackages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1956115/+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 1982730] Re: Suspending Lubuntu when the "Lock Screen After" box is checked in XScreenSaver results in an error message about xdg-screensaver
Sorry, I thought xscreensaver-systemd would have been started by systemd, because it was in the name, but I'm certain now it's started by lxqt-session, as correctly determined by the original reporter. ** Package changed: systemd (Ubuntu) => lxqt-session (Ubuntu) -- 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/1982730 Title: Suspending Lubuntu when the "Lock Screen After" box is checked in XScreenSaver results in an error message about xdg-screensaver Status in lxqt-session package in Ubuntu: Confirmed Bug description: Test hardware - HP Elitebook 8570p, 16 GB RAM, 1 TB SSD, 3rd gen i5 CPU. Test was done within a GNOME Boxes VM, 2 GB RAM, 20 GB disk space, SeaBIOS. Steps to reproduce: 1: Install Lubuntu 22.04 into a VM. 2: Run "sudo apt update && sudo apt -y full-upgrade" to get the VM up-to-date. 3: Reboot the VM. 4: Open XScreenSaver, and check the "Lock Screen After" box. 5: Close XScreenSaver. 6: Click the Application Menu, hover over "Leave", and click "Suspend", then click "OK". Expected result: The VM should immediately go into sleep mode without any errors. Actual result: The screen goes black, then the following text appears on the screen: xscreensaver: XX:XX:XX: not launching hack (throttled.) xscreensaver: XX:XX:XX: LOCK CLientMessage received while already locked. If you move the mouse, an XScreenSaver prompt will appear asking for your username and password. If you simply leave the VM for long enough it will eventually go into suspend. If you sign in, the following error message will be present on the screen in a window: Failed to run "xdg-screensaver lock". Ensure you have a locker/screensaver compatible with xdg-screensaver installed and running. Leaving the VM alone at this point will also eventually result in it going into suspend. Clicking the "OK" button on the error window will result in the VM immediately suspending. Notes: I don't actually know what package this should be reported against - I chose lxqt-session because a look at the LXQt source code revealed that it was possible that the "Suspend" button in the LXQt Application Menu was from lxqt-session. Other packages this bug might be in include XScreenSaver, liblxqt, lxqt-powermanagement, systemd, or whatever provides DBus (is that even provided by a package? *shrug*). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: lxqt-session 0.17.1-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Mon Jul 25 02:04:25 2022 InstallationDate: Installed on 2022-07-25 (0 days ago) InstallationMedia: Lubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: lxqt-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxqt-session/+bug/1982730/+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 1995105] Re: add-apt-repository fails if it encounters immutable sources.list.d entry
** Summary changed: - apt-add-repository fails if it encounters immutable sources.list.d entry + add-apt-repository fails if it encounters immutable sources.list.d entry -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1995105 Title: add-apt-repository fails if it encounters immutable sources.list.d entry Status in software-properties package in Ubuntu: New Bug description: Reason: We're trying to protect an internal APT source from trivial accidental modification by users (who do have sudo as root). Steps to reproduce: echo '# dummy' > /etc/apt/sources.list.d/dummy.list chattr +i /etc/apt/sources.list.d/dummy.list add-apt-repository -y ppa:longsleep/golang-backports Expected behaviour: New sources.list for the PPA gets created. Observed behaviour: Traceback (most recent call last): File "/usr/bin/add-apt-repository", line 364, in sys.exit(0 if addaptrepo.main() else 1) File "/usr/bin/add-apt-repository", line 357, in main shortcut.add() File "/usr/lib/python3/dist-packages/softwareproperties/shortcuthandler.py", line 221, in add self.add_source() File "/usr/lib/python3/dist-packages/softwareproperties/shortcuthandler.py", line 307, in add_source sourceslist.save() File "/usr/lib/python3/dist-packages/softwareproperties/extendedsourceslist.py", line 391, in save with open(filename, "w") as f: PermissionError: [Errno 1] Operation not permitted: '/etc/apt/sources.list.d/dummy.list' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1995105/+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 1995105] [NEW] add-apt-repository fails if it encounters immutable sources.list.d entry
Public bug reported: Reason: We're trying to protect an internal APT source from trivial accidental modification by users (who do have sudo as root). Steps to reproduce: echo '# dummy' > /etc/apt/sources.list.d/dummy.list chattr +i /etc/apt/sources.list.d/dummy.list add-apt-repository -y ppa:longsleep/golang-backports Expected behaviour: New sources.list for the PPA gets created. Observed behaviour: Traceback (most recent call last): File "/usr/bin/add-apt-repository", line 364, in sys.exit(0 if addaptrepo.main() else 1) File "/usr/bin/add-apt-repository", line 357, in main shortcut.add() File "/usr/lib/python3/dist-packages/softwareproperties/shortcuthandler.py", line 221, in add self.add_source() File "/usr/lib/python3/dist-packages/softwareproperties/shortcuthandler.py", line 307, in add_source sourceslist.save() File "/usr/lib/python3/dist-packages/softwareproperties/extendedsourceslist.py", line 391, in save with open(filename, "w") as f: PermissionError: [Errno 1] Operation not permitted: '/etc/apt/sources.list.d/dummy.list' ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1995105 Title: add-apt-repository fails if it encounters immutable sources.list.d entry Status in software-properties package in Ubuntu: New Bug description: Reason: We're trying to protect an internal APT source from trivial accidental modification by users (who do have sudo as root). Steps to reproduce: echo '# dummy' > /etc/apt/sources.list.d/dummy.list chattr +i /etc/apt/sources.list.d/dummy.list add-apt-repository -y ppa:longsleep/golang-backports Expected behaviour: New sources.list for the PPA gets created. Observed behaviour: Traceback (most recent call last): File "/usr/bin/add-apt-repository", line 364, in sys.exit(0 if addaptrepo.main() else 1) File "/usr/bin/add-apt-repository", line 357, in main shortcut.add() File "/usr/lib/python3/dist-packages/softwareproperties/shortcuthandler.py", line 221, in add self.add_source() File "/usr/lib/python3/dist-packages/softwareproperties/shortcuthandler.py", line 307, in add_source sourceslist.save() File "/usr/lib/python3/dist-packages/softwareproperties/extendedsourceslist.py", line 391, in save with open(filename, "w") as f: PermissionError: [Errno 1] Operation not permitted: '/etc/apt/sources.list.d/dummy.list' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1995105/+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 1995100] Re: /usr/share/apport/whoopsie-upload-all:ValueError:/usr/share/apport/whoopsie-upload-all@249:main:collect_info:process_report:load
An example .crash files that triggers this bug would be useful. ** Description changed: + ``` + Traceback (most recent call last): + File "/usr/share/apport/whoopsie-upload-all", line 249, in + main() + File "/usr/share/apport/whoopsie-upload-all", line 231, in main + stamps = collect_info() + File "/usr/share/apport/whoopsie-upload-all", line 162, in collect_info + res = process_report(r) + File "/usr/share/apport/whoopsie-upload-all", line 76, in process_report + r.load(f, binary="compressed") + File "/usr/lib/python3/dist-packages/problem_report.py", line 166, in load + (key, value) = line.split(b":", 1) + ValueError: not enough values to unpack (expected 2, got 1) + ``` + The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.23.1-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/134ffbe13e7dd9a7f79ad6a455c6e560669a9928 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1995100 Title: /usr/share/apport/whoopsie-upload- all:ValueError:/usr/share/apport/whoopsie-upload- all@249:main:collect_info:process_report:load Status in apport package in Ubuntu: New Bug description: ``` Traceback (most recent call last): File "/usr/share/apport/whoopsie-upload-all", line 249, in main() File "/usr/share/apport/whoopsie-upload-all", line 231, in main stamps = collect_info() File "/usr/share/apport/whoopsie-upload-all", line 162, in collect_info res = process_report(r) File "/usr/share/apport/whoopsie-upload-all", line 76, in process_report r.load(f, binary="compressed") File "/usr/lib/python3/dist-packages/problem_report.py", line 166, in load (key, value) = line.split(b":", 1) ValueError: not enough values to unpack (expected 2, got 1) ``` The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.23.1-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/134ffbe13e7dd9a7f79ad6a455c6e560669a9928 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1995100/+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 1995100] [NEW] /usr/share/apport/whoopsie-upload-all:ValueError:/usr/share/apport/whoopsie-upload-all@249:main:collect_info:process_report:load
Public bug reported: ``` Traceback (most recent call last): File "/usr/share/apport/whoopsie-upload-all", line 249, in main() File "/usr/share/apport/whoopsie-upload-all", line 231, in main stamps = collect_info() File "/usr/share/apport/whoopsie-upload-all", line 162, in collect_info res = process_report(r) File "/usr/share/apport/whoopsie-upload-all", line 76, in process_report r.load(f, binary="compressed") File "/usr/lib/python3/dist-packages/problem_report.py", line 166, in load (key, value) = line.split(b":", 1) ValueError: not enough values to unpack (expected 2, got 1) ``` The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.23.1-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/134ffbe13e7dd9a7f79ad6a455c6e560669a9928 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: jammy kinetic kylin-22.10 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1995100 Title: /usr/share/apport/whoopsie-upload- all:ValueError:/usr/share/apport/whoopsie-upload- all@249:main:collect_info:process_report:load Status in apport package in Ubuntu: New Bug description: ``` Traceback (most recent call last): File "/usr/share/apport/whoopsie-upload-all", line 249, in main() File "/usr/share/apport/whoopsie-upload-all", line 231, in main stamps = collect_info() File "/usr/share/apport/whoopsie-upload-all", line 162, in collect_info res = process_report(r) File "/usr/share/apport/whoopsie-upload-all", line 76, in process_report r.load(f, binary="compressed") File "/usr/lib/python3/dist-packages/problem_report.py", line 166, in load (key, value) = line.split(b":", 1) ValueError: not enough values to unpack (expected 2, got 1) ``` The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.23.1-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/134ffbe13e7dd9a7f79ad6a455c6e560669a9928 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1995100/+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 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu
If possible, I still expect we can make grub supports to boot from
bigger initramfs.
There will still have users to meet this issue in the future if their
initramfs somehow bigger as long as we don't choose use higher
compression as workaround (for ubuntu desktop / server).
--
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/1842320
Title:
Can't boot: "error: out of memory." immediately after the grub menu
Status in grub:
Unknown
Status in OEM Priority Project:
Triaged
Status in grub2-signed package in Ubuntu:
Triaged
Status in grub2-unsigned package in Ubuntu:
Triaged
Status in initramfs-tools package in Ubuntu:
Won't Fix
Status in linux package in Ubuntu:
Confirmed
Bug description:
[Impact]
* In some cases, if the users’ initramfs grow bigger, then it’ll
likely not be able to be loaded by grub2.
* Some real cases from OEM projects:
In many built-in 4k monitor laptops with nvidia drivers, the u-d-c
puts the nvidia*.ko to initramfs which grows the initramfs to ~120M.
Also the gfxpayload=auto will remain to use 4K resolution since it’s
what EFI POST passed.
In this case, the grub isn't able to load initramfs because the
grub_memalign() won't be able to get suitable memory for the larger
file:
```
#0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376
#1 0x7dd7b074 in grub_malloc (size=592214020) at
../../../grub-core/kern/mm.c:408
#2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076)
at ../../../grub-core/kern/verifiers.c:150
#3 0x7dd801d4 in grub_file_open (name=0x7bc02f00
"/boot/initrd.img-5.17.0-1011-oem",
type=131076) at ../../../grub-core/kern/file.c:121
#4 0x7bcd5a30 in ?? ()
#5 0x7fe21247 in ?? ()
#6 0x7bc030c8 in ?? ()
#7 0x00017fe21238 in ?? ()
#8 0x7bcd5320 in ?? ()
#9 0x7fe21250 in ?? ()
#10 0x in ?? ()
```
Based on grub_mm_dump, we can see the memory fragment (some parts seem
likely be used because of 4K resolution?) and doesn’t have available
contiguous memory for larger file as:
```
grub_real_malloc(...)
...
if (cur->size >= n + extra)
```
Based on UEFI Specification Section 7.2[1] and UEFI driver writers’
guide 4.2.3[2], we can ask 32bits+ on AllocatePages().
As most X86_64 platforms should support 64 bits addressing, we should
extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available
memory.
* When users grown the initramfs, then probably will get initramfs
not found which really annoyed and impact the user experience (system
not able to boot).
[Test Plan]
* detailed instructions how to reproduce the bug:
1. Any method to grow the initramfs, such as install nvidia-driver.
2. If developers would like to reproduce, then could dd if=/dev/random
of=... bs=1M count=500, something like:
```
$ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file
#!/bin/sh
PREREQ=""
prereqs()
{
echo "$PREREQ"
}
case $1 in
# get pre-requisites
prereqs)
prereqs
exit 0
;;
esac
. /usr/share/initramfs-tools/hook-functions
dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500
```
And then update-initramfs
* After applying my patches, the issue is gone.
* I did also test my test grubx64.efi in:
1. X86_64 qemu with
1.1. 60M initramfs + 5.15.0-37-generic kernel
1.2. 565M initramfs + 5.17.0-1011-oem kernel
2. Amd64 HP mobile workstation with
2.1. 65M initramfs + 5.15.0-39-generic kernel
2.2. 771M initramfs + 5.17.0-1011-oem kernel
All working well.
[Where problems could occur]
* The changes almost in i386/efi, thus the impact will be in the i386 /
x86_64 EFI system.
The other change is to modify the “grub-core/kern/efi/mm.c” but I use the
original addressing for “arm/arm64/ia64/riscv32/riscv64”.
Thus it should not impact them.
* There is a “#if defined(__x86_64__)” which intent to limit the >
32bits code in i386 system and also
```
#if defined (__code_model_large__)
-#define GRUB_EFI_MAX_USABLE_ADDRESS 0x
+#define GRUB_EFI_MAX_USABLE_ADDRESS __UINTPTR_MAX__
+#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x7fff
#else
#define GRUB_EFI_MAX_USABLE_ADDRESS 0x7fff
+#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x3fff
#endif
```
If everything works as expected, then i386 should working good.
If not lucky, based on “UEFI writers’ guide”[2], the i386 will get >
4GB memory region and never be able to access.
[Other Info]
* Upstream grub2 bug #61058
https://savannah.gnu.org/bugs/index.php?61058
* Test PPA: https://launchpad.net/~os369510/+archive/ubuntu/lp1842320
* Test grubx64.efi:
https://people.canonical.com/~jeremysu/lp1842320/grubx64.efi.lp1842320
* Test
[Touch-packages] [Bug 1995097] [NEW] systemd
Public bug reported: Processing triggers for libc-bin (2.35-0ubuntu3.1) ... Errors were encountered while processing: systemd systemd-timesyncd libpam-systemd:amd64 systemd-oomd snapd systemd-sysv libnss-systemd:amd64 E: Sub-process /usr/bin/dpkg returned an error code (1) ** 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/1995097 Title: systemd Status in systemd package in Ubuntu: New Bug description: Processing triggers for libc-bin (2.35-0ubuntu3.1) ... Errors were encountered while processing: systemd systemd-timesyncd libpam-systemd:amd64 systemd-oomd snapd systemd-sysv libnss-systemd:amd64 E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1995097/+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 1982730] Re: Suspending Lubuntu when the "Lock Screen After" box is checked in XScreenSaver results in an error message about xdg-screensaver
So I just restarted my system, and I got the bug. BUT, when I killed and reran xscreensaver-systemd, THE BUG DISAPPEARED. This seems to indicate that xscreensaver-systemd is being run too early in the login/startup process. -- 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/1982730 Title: Suspending Lubuntu when the "Lock Screen After" box is checked in XScreenSaver results in an error message about xdg-screensaver Status in systemd package in Ubuntu: Confirmed Bug description: Test hardware - HP Elitebook 8570p, 16 GB RAM, 1 TB SSD, 3rd gen i5 CPU. Test was done within a GNOME Boxes VM, 2 GB RAM, 20 GB disk space, SeaBIOS. Steps to reproduce: 1: Install Lubuntu 22.04 into a VM. 2: Run "sudo apt update && sudo apt -y full-upgrade" to get the VM up-to-date. 3: Reboot the VM. 4: Open XScreenSaver, and check the "Lock Screen After" box. 5: Close XScreenSaver. 6: Click the Application Menu, hover over "Leave", and click "Suspend", then click "OK". Expected result: The VM should immediately go into sleep mode without any errors. Actual result: The screen goes black, then the following text appears on the screen: xscreensaver: XX:XX:XX: not launching hack (throttled.) xscreensaver: XX:XX:XX: LOCK CLientMessage received while already locked. If you move the mouse, an XScreenSaver prompt will appear asking for your username and password. If you simply leave the VM for long enough it will eventually go into suspend. If you sign in, the following error message will be present on the screen in a window: Failed to run "xdg-screensaver lock". Ensure you have a locker/screensaver compatible with xdg-screensaver installed and running. Leaving the VM alone at this point will also eventually result in it going into suspend. Clicking the "OK" button on the error window will result in the VM immediately suspending. Notes: I don't actually know what package this should be reported against - I chose lxqt-session because a look at the LXQt source code revealed that it was possible that the "Suspend" button in the LXQt Application Menu was from lxqt-session. Other packages this bug might be in include XScreenSaver, liblxqt, lxqt-powermanagement, systemd, or whatever provides DBus (is that even provided by a package? *shrug*). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: lxqt-session 0.17.1-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Mon Jul 25 02:04:25 2022 InstallationDate: Installed on 2022-07-25 (0 days ago) InstallationMedia: Lubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: lxqt-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982730/+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 1982730] Re: Suspending Lubuntu when the "Lock Screen After" box is checked in XScreenSaver results in an error message about xdg-screensaver
Okay, here's an EVER WEIRDER UPDATE! The interactions between xscreensaver and systemd are determined by xscreensaver-systemd. So I killed xscreensaver-systemd and then ran xscreensaver-systemd -verbose to look at the terminal output. AND I COULDN'T REPRODUCE THE BUG!!! Having “lock screen after X minutes” enabled led to a normal suspension of the system, and NO MORE ERROR MESSAGES after a while. xscreensaver-systemd: 22:18:44: connected xscreensaver-systemd: 22:18:50: exec: xscreensaver-command -verbose -suspend xscreensaver-command: ClientMessage ignored while authentication dialog is active xscreensaver-systemd: 22:18:51: exec: "xscreensaver-command -verbose -suspend" exited with status 255 xscreensaver-systemd: 22:18:54: exec: xscreensaver-command -verbose -deactivate xscreensaver-command: ClientMessage ignored while authentication dialog is active xscreensaver-systemd: 22:18:54: exec: "xscreensaver-command -verbose -deactivate" exited with status 255 xscreensaver-systemd: 22:19:24: exec: xscreensaver-command -verbose -suspend xscreensaver-command: suspending. xscreensaver-systemd: 22:19:29: exec: xscreensaver-command -verbose -deactivate xscreensaver-command: deactivating. xscreensaver-systemd: 22:19:54: exec: xscreensaver-command -verbose -suspend xscreensaver-command: suspending. xscreensaver-systemd: 22:19:57: exec: xscreensaver-command -verbose -deactivate xscreensaver-command: deactivating. -- 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/1982730 Title: Suspending Lubuntu when the "Lock Screen After" box is checked in XScreenSaver results in an error message about xdg-screensaver Status in systemd package in Ubuntu: Confirmed Bug description: Test hardware - HP Elitebook 8570p, 16 GB RAM, 1 TB SSD, 3rd gen i5 CPU. Test was done within a GNOME Boxes VM, 2 GB RAM, 20 GB disk space, SeaBIOS. Steps to reproduce: 1: Install Lubuntu 22.04 into a VM. 2: Run "sudo apt update && sudo apt -y full-upgrade" to get the VM up-to-date. 3: Reboot the VM. 4: Open XScreenSaver, and check the "Lock Screen After" box. 5: Close XScreenSaver. 6: Click the Application Menu, hover over "Leave", and click "Suspend", then click "OK". Expected result: The VM should immediately go into sleep mode without any errors. Actual result: The screen goes black, then the following text appears on the screen: xscreensaver: XX:XX:XX: not launching hack (throttled.) xscreensaver: XX:XX:XX: LOCK CLientMessage received while already locked. If you move the mouse, an XScreenSaver prompt will appear asking for your username and password. If you simply leave the VM for long enough it will eventually go into suspend. If you sign in, the following error message will be present on the screen in a window: Failed to run "xdg-screensaver lock". Ensure you have a locker/screensaver compatible with xdg-screensaver installed and running. Leaving the VM alone at this point will also eventually result in it going into suspend. Clicking the "OK" button on the error window will result in the VM immediately suspending. Notes: I don't actually know what package this should be reported against - I chose lxqt-session because a look at the LXQt source code revealed that it was possible that the "Suspend" button in the LXQt Application Menu was from lxqt-session. Other packages this bug might be in include XScreenSaver, liblxqt, lxqt-powermanagement, systemd, or whatever provides DBus (is that even provided by a package? *shrug*). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: lxqt-session 0.17.1-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Mon Jul 25 02:04:25 2022 InstallationDate: Installed on 2022-07-25 (0 days ago) InstallationMedia: Lubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: lxqt-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982730/+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 1982730] Re: Suspending Lubuntu when the "Lock Screen After" box is checked in XScreenSaver results in an error message about xdg-screensaver
So here's the problem: if you have “lock screen after X minutes” enabled in xscreensaver, and you run `systemctl suspend`, then for some reason systemd first LOCKS the screen, which stops the suspend; only after unlocking the screen does the system suspend. If you uncheck “lock screen after X minutes”, then systemctl suspend FIRST suspends THEN locks. Very strange behaviour!! ** Package changed: lxqt-session (Ubuntu) => systemd (Ubuntu) -- 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/1982730 Title: Suspending Lubuntu when the "Lock Screen After" box is checked in XScreenSaver results in an error message about xdg-screensaver Status in systemd package in Ubuntu: Confirmed Bug description: Test hardware - HP Elitebook 8570p, 16 GB RAM, 1 TB SSD, 3rd gen i5 CPU. Test was done within a GNOME Boxes VM, 2 GB RAM, 20 GB disk space, SeaBIOS. Steps to reproduce: 1: Install Lubuntu 22.04 into a VM. 2: Run "sudo apt update && sudo apt -y full-upgrade" to get the VM up-to-date. 3: Reboot the VM. 4: Open XScreenSaver, and check the "Lock Screen After" box. 5: Close XScreenSaver. 6: Click the Application Menu, hover over "Leave", and click "Suspend", then click "OK". Expected result: The VM should immediately go into sleep mode without any errors. Actual result: The screen goes black, then the following text appears on the screen: xscreensaver: XX:XX:XX: not launching hack (throttled.) xscreensaver: XX:XX:XX: LOCK CLientMessage received while already locked. If you move the mouse, an XScreenSaver prompt will appear asking for your username and password. If you simply leave the VM for long enough it will eventually go into suspend. If you sign in, the following error message will be present on the screen in a window: Failed to run "xdg-screensaver lock". Ensure you have a locker/screensaver compatible with xdg-screensaver installed and running. Leaving the VM alone at this point will also eventually result in it going into suspend. Clicking the "OK" button on the error window will result in the VM immediately suspending. Notes: I don't actually know what package this should be reported against - I chose lxqt-session because a look at the LXQt source code revealed that it was possible that the "Suspend" button in the LXQt Application Menu was from lxqt-session. Other packages this bug might be in include XScreenSaver, liblxqt, lxqt-powermanagement, systemd, or whatever provides DBus (is that even provided by a package? *shrug*). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: lxqt-session 0.17.1-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Mon Jul 25 02:04:25 2022 InstallationDate: Installed on 2022-07-25 (0 days ago) InstallationMedia: Lubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: lxqt-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982730/+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 1982730] [NEW] Suspending Lubuntu when the "Lock Screen After" box is checked in XScreenSaver results in an error message about xdg-screensaver
You have been subscribed to a public bug: Test hardware - HP Elitebook 8570p, 16 GB RAM, 1 TB SSD, 3rd gen i5 CPU. Test was done within a GNOME Boxes VM, 2 GB RAM, 20 GB disk space, SeaBIOS. Steps to reproduce: 1: Install Lubuntu 22.04 into a VM. 2: Run "sudo apt update && sudo apt -y full-upgrade" to get the VM up-to-date. 3: Reboot the VM. 4: Open XScreenSaver, and check the "Lock Screen After" box. 5: Close XScreenSaver. 6: Click the Application Menu, hover over "Leave", and click "Suspend", then click "OK". Expected result: The VM should immediately go into sleep mode without any errors. Actual result: The screen goes black, then the following text appears on the screen: xscreensaver: XX:XX:XX: not launching hack (throttled.) xscreensaver: XX:XX:XX: LOCK CLientMessage received while already locked. If you move the mouse, an XScreenSaver prompt will appear asking for your username and password. If you simply leave the VM for long enough it will eventually go into suspend. If you sign in, the following error message will be present on the screen in a window: Failed to run "xdg-screensaver lock". Ensure you have a locker/screensaver compatible with xdg-screensaver installed and running. Leaving the VM alone at this point will also eventually result in it going into suspend. Clicking the "OK" button on the error window will result in the VM immediately suspending. Notes: I don't actually know what package this should be reported against - I chose lxqt-session because a look at the LXQt source code revealed that it was possible that the "Suspend" button in the LXQt Application Menu was from lxqt-session. Other packages this bug might be in include XScreenSaver, liblxqt, lxqt-powermanagement, systemd, or whatever provides DBus (is that even provided by a package? *shrug*). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: lxqt-session 0.17.1-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Mon Jul 25 02:04:25 2022 InstallationDate: Installed on 2022-07-25 (0 days ago) InstallationMedia: Lubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: lxqt-session UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: systemd (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug jammy -- Suspending Lubuntu when the "Lock Screen After" box is checked in XScreenSaver results in an error message about xdg-screensaver https://bugs.launchpad.net/bugs/1982730 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1958019]
The Intel based Legion 7i Gen 7 definitely has this problem as I have one. On 10/27/22 09:16, bugzilla-dae...@kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=208555 > > --- Comment #712 from antide...@gmail.com --- > Does anyone know if both the intel and amd versions of legion gen 7 have the > same problem with the DSD tables or just the amd version? > -- 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/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1958019]
Does anyone know if both the intel and amd versions of legion gen 7 have the same problem with the DSD tables or just the amd version? -- 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/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1774632] Re: The symbolic link /etc/resolv.conf points to the wrong file by default
Lukas Märdian (slyon): "NetworkManager should automatically detect sd-
resolved and integrate nicely"
Thank you for this guidance, Lukas. I had disabled NetworkManager on
this system because it wasn't configuring my network connections as I
needed them. I had moved my home LAN onto a separate subnet -
192.168.2.* - as my provider is Verizon FIOS, and it controls
192.168.1.*. Even though I put specific manual settings into
NetworkManager to tell it to use 192.168.2.*, it was still picking DNS
servers on 192.168.1.*.
But your post encouraged me to try again (2 years later) and this time I
got NetworkManager working with Manual configuration. So, I now have
everything configured as default with stub-resolv.conf and
NetworkManager enabled, and it's all working correctly. The only place
I have DNS servers specified is in NetworkManager, separately for each
interface ("Wired connection 1" and "docker0"). I'm providing these
details in case someone finds this report via search.
--
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/1774632
Title:
The symbolic link /etc/resolv.conf points to the wrong file by default
Status in systemd package in Ubuntu:
Invalid
Bug description:
When using nslookup for local machine names, the local DNS was being
ignored (not queried) and none of the local machines could be found.
After much research and digging, it was discovered that the cause was
the incorrect symbolic link /etc/resolv.conf file.
The default install caused systemd-resolve to configure the link to point to
the stub file:
/etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.conf
Reomving that link and pointing it to the correct file solved the DNS lookup
issue. The correct link looks like this:
/etc/resolv.conf -> /run/systemd/resolve/resolv.conf
Steps used to test the bug before fixing the link is to perform an nslookup
on a local (non FQDN) machine that is in your local DNS (my router is my DNS
server for this case) Here is an example of the incorrect output:
$ nslookup web1
Server: 127.0.0.53
Address:127.0.0.53#53
** server can't find web1: SERVFAIL
Switching the symbolic link solves the problem. Here is my solution:
$ sudo rm -f /etc/resolv.conf
$ sudo ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf
After switching the symbolic link, the nslookup functions properly.
$ nslookup web1
Server: 192.168.1.1
Address:192.168.1.1#53
Name: web1
Address: 192.168.1.107
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: systemd 237-3ubuntu10
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Jun 1 05:28:41 2018
InstallationDate: Installed on 2018-01-20 (131 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
MachineType: Dell Inc. Inspiron 5755
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic
root=UUID=7fe151d3-4033-4903-b356-341d9f16e124 ro acpi=force
SourcePackage: systemd
UpgradeStatus: Upgraded to bionic on 2018-04-28 (33 days ago)
dmi.bios.date: 08/27/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A08
dmi.board.name: 0VY15F
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A08
dmi.modalias:
dmi:bvnDellInc.:bvrA08:bd08/27/2015:svnDellInc.:pnInspiron5755:pvrA08:rvnDellInc.:rn0VY15F:rvrA00:cvnDellInc.:ct8:cvrA08:
dmi.product.name: Inspiron 5755
dmi.product.version: A08
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1774632/+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 1995021] Re: Boot and shutdown take several minutes
For further details please see this thread https://forums.linuxmint.com/viewtopic.php?f=46=384285 in the Linux Mint forum where I am the user "stovdal" ** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1995021 Title: Boot and shutdown take several minutes Status in xorg package in Ubuntu: New Bug description: My system has been running smoothly until Kernel 5.15.0-50 (and 5.15.0-52) was installed. Now boot and shutdown take several minutes. I have an Nvidia Gforce 1050 and Nvidia driver 515. Boot and shutdown run witout delay with the Nouveau and Nvidia 390 drivers but the OpenCl is unavailable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1995021/+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 1995021] [NEW] Boot and shutdown take several minutes
You have been subscribed to a public bug: My system has been running smoothly until Kernel 5.15.0-50 (and 5.15.0-52) was installed. Now boot and shutdown take several minutes. I have an Nvidia Gforce 1050 and Nvidia driver 515. Boot and shutdown run witout delay with the Nouveau and Nvidia 390 drivers but the OpenCl is unavailable ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Boot and shutdown take several minutes https://bugs.launchpad.net/bugs/1995021 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1995048] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1995048/+attachment/5627387/+files/UdevDb.txt -- 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/1995048 Title: reboot reboots system when --poweroff is passed Status in systemd package in Ubuntu: New Bug description: The feature of passing "--poweroff" to the reboot command to "Power- off the machine, regardless of which one of the three commands is invoked." is broken. Either that or the man page is. This doesn't matter much to me anymore now that I found out that you can also pass "-f" to "poweroff" when debugging, but it confused me a lot at first. $ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 $ apt-cache policy systemd-sysv systemd-sysv: Installed: 249.11-0ubuntu3.6 Candidate: 249.11-0ubuntu3.6 Version table: *** 249.11-0ubuntu3.6 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 249.11-0ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages # Expected behaviour The system to power off. # Actual behaviour The system reboots. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-09-19 (39 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox Package: systemd 249.11-0ubuntu3.6 PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=11e9994e-8b05-42e7-949a-2f635b160285 ro text debug ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Tags: jammy Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1995048/+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 1995048] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1995048/+attachment/5627388/+files/acpidump.txt -- 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/1995048 Title: reboot reboots system when --poweroff is passed Status in systemd package in Ubuntu: New Bug description: The feature of passing "--poweroff" to the reboot command to "Power- off the machine, regardless of which one of the three commands is invoked." is broken. Either that or the man page is. This doesn't matter much to me anymore now that I found out that you can also pass "-f" to "poweroff" when debugging, but it confused me a lot at first. $ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 $ apt-cache policy systemd-sysv systemd-sysv: Installed: 249.11-0ubuntu3.6 Candidate: 249.11-0ubuntu3.6 Version table: *** 249.11-0ubuntu3.6 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 249.11-0ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages # Expected behaviour The system to power off. # Actual behaviour The system reboots. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-09-19 (39 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox Package: systemd 249.11-0ubuntu3.6 PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=11e9994e-8b05-42e7-949a-2f635b160285 ro text debug ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Tags: jammy Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1995048/+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 1995048] SystemdDelta.txt
apport information ** Attachment added: "SystemdDelta.txt" https://bugs.launchpad.net/bugs/1995048/+attachment/5627386/+files/SystemdDelta.txt -- 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/1995048 Title: reboot reboots system when --poweroff is passed Status in systemd package in Ubuntu: New Bug description: The feature of passing "--poweroff" to the reboot command to "Power- off the machine, regardless of which one of the three commands is invoked." is broken. Either that or the man page is. This doesn't matter much to me anymore now that I found out that you can also pass "-f" to "poweroff" when debugging, but it confused me a lot at first. $ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 $ apt-cache policy systemd-sysv systemd-sysv: Installed: 249.11-0ubuntu3.6 Candidate: 249.11-0ubuntu3.6 Version table: *** 249.11-0ubuntu3.6 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 249.11-0ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages # Expected behaviour The system to power off. # Actual behaviour The system reboots. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-09-19 (39 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox Package: systemd 249.11-0ubuntu3.6 PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=11e9994e-8b05-42e7-949a-2f635b160285 ro text debug ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Tags: jammy Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1995048/+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 1995048] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1995048/+attachment/5627385/+files/ProcModules.txt -- 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/1995048 Title: reboot reboots system when --poweroff is passed Status in systemd package in Ubuntu: New Bug description: The feature of passing "--poweroff" to the reboot command to "Power- off the machine, regardless of which one of the three commands is invoked." is broken. Either that or the man page is. This doesn't matter much to me anymore now that I found out that you can also pass "-f" to "poweroff" when debugging, but it confused me a lot at first. $ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 $ apt-cache policy systemd-sysv systemd-sysv: Installed: 249.11-0ubuntu3.6 Candidate: 249.11-0ubuntu3.6 Version table: *** 249.11-0ubuntu3.6 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 249.11-0ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages # Expected behaviour The system to power off. # Actual behaviour The system reboots. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-09-19 (39 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox Package: systemd 249.11-0ubuntu3.6 PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=11e9994e-8b05-42e7-949a-2f635b160285 ro text debug ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Tags: jammy Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1995048/+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 1995048] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1995048/+attachment/5627378/+files/Dependencies.txt -- 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/1995048 Title: reboot reboots system when --poweroff is passed Status in systemd package in Ubuntu: New Bug description: The feature of passing "--poweroff" to the reboot command to "Power- off the machine, regardless of which one of the three commands is invoked." is broken. Either that or the man page is. This doesn't matter much to me anymore now that I found out that you can also pass "-f" to "poweroff" when debugging, but it confused me a lot at first. $ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 $ apt-cache policy systemd-sysv systemd-sysv: Installed: 249.11-0ubuntu3.6 Candidate: 249.11-0ubuntu3.6 Version table: *** 249.11-0ubuntu3.6 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 249.11-0ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages # Expected behaviour The system to power off. # Actual behaviour The system reboots. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-09-19 (39 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox Package: systemd 249.11-0ubuntu3.6 PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=11e9994e-8b05-42e7-949a-2f635b160285 ro text debug ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Tags: jammy Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1995048/+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 1995048] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1995048/+attachment/5627377/+files/CurrentDmesg.txt -- 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/1995048 Title: reboot reboots system when --poweroff is passed Status in systemd package in Ubuntu: New Bug description: The feature of passing "--poweroff" to the reboot command to "Power- off the machine, regardless of which one of the three commands is invoked." is broken. Either that or the man page is. This doesn't matter much to me anymore now that I found out that you can also pass "-f" to "poweroff" when debugging, but it confused me a lot at first. $ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 $ apt-cache policy systemd-sysv systemd-sysv: Installed: 249.11-0ubuntu3.6 Candidate: 249.11-0ubuntu3.6 Version table: *** 249.11-0ubuntu3.6 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 249.11-0ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages # Expected behaviour The system to power off. # Actual behaviour The system reboots. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-09-19 (39 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox Package: systemd 249.11-0ubuntu3.6 PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=11e9994e-8b05-42e7-949a-2f635b160285 ro text debug ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Tags: jammy Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1995048/+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 1995048] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1995048/+attachment/5627383/+files/ProcCpuinfoMinimal.txt -- 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/1995048 Title: reboot reboots system when --poweroff is passed Status in systemd package in Ubuntu: New Bug description: The feature of passing "--poweroff" to the reboot command to "Power- off the machine, regardless of which one of the three commands is invoked." is broken. Either that or the man page is. This doesn't matter much to me anymore now that I found out that you can also pass "-f" to "poweroff" when debugging, but it confused me a lot at first. $ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 $ apt-cache policy systemd-sysv systemd-sysv: Installed: 249.11-0ubuntu3.6 Candidate: 249.11-0ubuntu3.6 Version table: *** 249.11-0ubuntu3.6 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 249.11-0ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages # Expected behaviour The system to power off. # Actual behaviour The system reboots. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-09-19 (39 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox Package: systemd 249.11-0ubuntu3.6 PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=11e9994e-8b05-42e7-949a-2f635b160285 ro text debug ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Tags: jammy Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1995048/+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 1995048] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1995048/+attachment/5627380/+files/Lspci-vt.txt -- 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/1995048 Title: reboot reboots system when --poweroff is passed Status in systemd package in Ubuntu: New Bug description: The feature of passing "--poweroff" to the reboot command to "Power- off the machine, regardless of which one of the three commands is invoked." is broken. Either that or the man page is. This doesn't matter much to me anymore now that I found out that you can also pass "-f" to "poweroff" when debugging, but it confused me a lot at first. $ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 $ apt-cache policy systemd-sysv systemd-sysv: Installed: 249.11-0ubuntu3.6 Candidate: 249.11-0ubuntu3.6 Version table: *** 249.11-0ubuntu3.6 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 249.11-0ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages # Expected behaviour The system to power off. # Actual behaviour The system reboots. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-09-19 (39 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox Package: systemd 249.11-0ubuntu3.6 PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=11e9994e-8b05-42e7-949a-2f635b160285 ro text debug ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Tags: jammy Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1995048/+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 1995048] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1995048/+attachment/5627382/+files/ProcCpuinfo.txt -- 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/1995048 Title: reboot reboots system when --poweroff is passed Status in systemd package in Ubuntu: New Bug description: The feature of passing "--poweroff" to the reboot command to "Power- off the machine, regardless of which one of the three commands is invoked." is broken. Either that or the man page is. This doesn't matter much to me anymore now that I found out that you can also pass "-f" to "poweroff" when debugging, but it confused me a lot at first. $ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 $ apt-cache policy systemd-sysv systemd-sysv: Installed: 249.11-0ubuntu3.6 Candidate: 249.11-0ubuntu3.6 Version table: *** 249.11-0ubuntu3.6 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 249.11-0ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages # Expected behaviour The system to power off. # Actual behaviour The system reboots. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-09-19 (39 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox Package: systemd 249.11-0ubuntu3.6 PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=11e9994e-8b05-42e7-949a-2f635b160285 ro text debug ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Tags: jammy Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1995048/+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 1995048] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1995048/+attachment/5627384/+files/ProcInterrupts.txt -- 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/1995048 Title: reboot reboots system when --poweroff is passed Status in systemd package in Ubuntu: New Bug description: The feature of passing "--poweroff" to the reboot command to "Power- off the machine, regardless of which one of the three commands is invoked." is broken. Either that or the man page is. This doesn't matter much to me anymore now that I found out that you can also pass "-f" to "poweroff" when debugging, but it confused me a lot at first. $ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 $ apt-cache policy systemd-sysv systemd-sysv: Installed: 249.11-0ubuntu3.6 Candidate: 249.11-0ubuntu3.6 Version table: *** 249.11-0ubuntu3.6 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 249.11-0ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages # Expected behaviour The system to power off. # Actual behaviour The system reboots. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-09-19 (39 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox Package: systemd 249.11-0ubuntu3.6 PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=11e9994e-8b05-42e7-949a-2f635b160285 ro text debug ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Tags: jammy Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1995048/+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 1995048] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1995048/+attachment/5627379/+files/Lspci.txt -- 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/1995048 Title: reboot reboots system when --poweroff is passed Status in systemd package in Ubuntu: New Bug description: The feature of passing "--poweroff" to the reboot command to "Power- off the machine, regardless of which one of the three commands is invoked." is broken. Either that or the man page is. This doesn't matter much to me anymore now that I found out that you can also pass "-f" to "poweroff" when debugging, but it confused me a lot at first. $ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 $ apt-cache policy systemd-sysv systemd-sysv: Installed: 249.11-0ubuntu3.6 Candidate: 249.11-0ubuntu3.6 Version table: *** 249.11-0ubuntu3.6 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 249.11-0ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages # Expected behaviour The system to power off. # Actual behaviour The system reboots. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-09-19 (39 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox Package: systemd 249.11-0ubuntu3.6 PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=11e9994e-8b05-42e7-949a-2f635b160285 ro text debug ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Tags: jammy Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1995048/+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 1995048] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1995048/+attachment/5627381/+files/Lsusb-v.txt -- 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/1995048 Title: reboot reboots system when --poweroff is passed Status in systemd package in Ubuntu: New Bug description: The feature of passing "--poweroff" to the reboot command to "Power- off the machine, regardless of which one of the three commands is invoked." is broken. Either that or the man page is. This doesn't matter much to me anymore now that I found out that you can also pass "-f" to "poweroff" when debugging, but it confused me a lot at first. $ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 $ apt-cache policy systemd-sysv systemd-sysv: Installed: 249.11-0ubuntu3.6 Candidate: 249.11-0ubuntu3.6 Version table: *** 249.11-0ubuntu3.6 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 249.11-0ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages # Expected behaviour The system to power off. # Actual behaviour The system reboots. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-09-19 (39 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox Package: systemd 249.11-0ubuntu3.6 PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=11e9994e-8b05-42e7-949a-2f635b160285 ro text debug ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Tags: jammy Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1995048/+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 1995048] [NEW] reboot reboots system when --poweroff is passed
Public bug reported: The feature of passing "--poweroff" to the reboot command to "Power-off the machine, regardless of which one of the three commands is invoked." is broken. Either that or the man page is. This doesn't matter much to me anymore now that I found out that you can also pass "-f" to "poweroff" when debugging, but it confused me a lot at first. $ lsb_release -rd Description:Ubuntu 22.04.1 LTS Release:22.04 $ apt-cache policy systemd-sysv systemd-sysv: Installed: 249.11-0ubuntu3.6 Candidate: 249.11-0ubuntu3.6 Version table: *** 249.11-0ubuntu3.6 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 249.11-0ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages # Expected behaviour The system to power off. # Actual behaviour The system reboots. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-09-19 (39 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox Package: systemd 249.11-0ubuntu3.6 PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=11e9994e-8b05-42e7-949a-2f635b160285 ro text debug ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Tags: jammy Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected jammy ** Tags added: apport-collected jammy ** Description changed: The feature of passing "--poweroff" to the reboot command to "Power-off the machine, regardless of which one of the three commands is invoked." is broken. Either that or the man page is. This doesn't matter much to me anymore now that I found out that you can also pass "-f" to "poweroff" when debugging, but it confused me a lot at first. $ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 $ apt-cache policy systemd-sysv systemd-sysv: Installed: 249.11-0ubuntu3.6 Candidate: 249.11-0ubuntu3.6 Version table: *** 249.11-0ubuntu3.6 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 249.11-0ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages # Expected behaviour The system to power off. # Actual behaviour The system reboots. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82.1 + Architecture: amd64 + CasperMD5CheckResult: pass + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2022-09-19 (39 days ago) + InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) + Lsusb: + Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet + Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + Lsusb-t: + /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M + |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M + MachineType: innotek GmbH VirtualBox + Package: systemd 249.11-0ubuntu3.6 + PackageArchitecture: amd64 + ProcEnviron: + TERM=linux + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=11e9994e-8b05-42e7-949a-2f635b160285 ro text debug + ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 + Tags: jammy + Uname: Linux 5.15.0-52-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 12/01/2006 + dmi.bios.vendor: innotek GmbH + dmi.bios.version: VirtualBox + dmi.board.name: VirtualBox + dmi.board.vendor: Oracle
