[Touch-packages] [Bug 2055270] Re: Buy Tramadol Online At Lowest Prices
** Package changed: systemd (Ubuntu) => null-and-void -- 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/2055270 Title: Buy Tramadol Online At Lowest Prices Status in NULL Project: Invalid Bug description: Buy Tramadol Online 100mg USA Overnight ➤Order here: https://t.ly/N0hN9 ➤Shop Here: https://t.ly/N0hN9 Tramadol 100mg may interact with other medications, including certain antidepressants, antipsychotics, and medications that affect serotonin levels. It's important to inform your healthcare provider about all medications you are taking, including prescription, over-the-counter, and herbal supplements, to avoid potential interactions. Tramadol should not be used in combination with alcohol or other substances that depress the central nervous system, as this can increase the risk of respiratory depression and other serious side effects. People with a history of substance abuse or addiction should use tramadol with caution, as it has the potential for misuse, dependence, and addiction. Tramadol is not recommended for use in children under the age of 12, as its safety and efficacy in this population have not been established. Older adults may be more sensitive to the side effects of tramadol, particularly dizziness and drowsiness, and may require lower doses or closer monitoring. It's essential to follow your healthcare provider's instructions carefully when taking tramadol 100mg and to report any side effects or concerns promptly. Additionally, do not stop taking tramadol suddenly without consulting your doctor, as this can lead to withdrawal symptoms. If you have any questions or uncertainties about tramadol or its use, don't hesitate to discuss them with your healthcare provider. To manage notifications about this bug go to: https://bugs.launchpad.net/null-and-void/+bug/2055270/+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 1991975] Re: dev file system is mounted without nosuid or noexec
These metadata edits on this bug and a few others look spammy to me. Taking the appropriate action now. -- 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/1991975 Title: dev file system is mounted without nosuid or noexec Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in linux source package in Focal: Fix Released Status in systemd source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in systemd source package in Jammy: Fix Released Bug description: [ SRU TEMPLATE ] [ Impact ] * nosuid, and noexec bits are not set on /dev * This has the potential for nefarious actors to use this as an avenue for attack. see https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 for more discussion around this. * It is not best security practice. [ Test Plan ] 1.Boot a Canonical Supplied EC2 instance 2.Check the mount options for /dev. 3.You will notice the lack of nosuid and noexec on /dev. [ Where problems could occur ] * As of 2022/10/06, I need to test this, but don't know how to build -aws flavored ubuntu kernels. Instructions welcome. I'm holding off on adding SRU tags until I can actually get this tested. * If this is applied to non initramfs-less kernels it could potentially cause a regression for very old hardware that does nefarious things with memory. For a larger discussion about that see: https://lore.kernel.org/lkml/YcMfDOyrg647RCmd@debian-BULLSEYE-live-builder-AMD64/T/ * Low risk if a driver depends on /dev allowing suid or exec this might prevent boot. That being said, all kernels that have been booting with an initramfs have been getting nosuid, and noexec set so hopefully we can consider that risk fairly well tested. [ Other Info ] * Patch is accepted into 5.17, and will drop out quickly * Any server booting with an initramfs already has nosuid, and noexec set, so hopefully <<< ORIGINAL TEXT This is similar to https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 but new. I discovered that my ec2 instances based off of Canonical supplied AMI ami-0a23d90349664c6ee *(us-east-2), have dev mounted mounted without the nosuid option. https://us-east-2.console.aws.amazon.com/ec2/home?region=us- east-2#Images:visibility=public-images;imageId=ami-0a23d90349664c6ee My usb installed 20.04.4 home machine does not have this problem, but it has been installed for quite some time. My 22.04 laptop machine also does not have this issue. Reproduce. Start an ec2 instance based off of ami-0a23d90349664c6ee. $ mount | grep devtmpfs nosuid is not found in the options list. I've checked the initrd, and /etc/init.d/udev script and all places I know of where dev gets mounted set nosuid, so it's non-obvious what boot code-path is being taken that results in nosuid missing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: udev 245.4-4ubuntu3.18 ProcVersionSignature: Ubuntu 5.15.0-1020.24~20.04.1-aws 5.15.53 Uname: Linux 5.15.0-1020-aws x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CustomUdevRuleFiles: 60-cdrom_id.rules 70-snap.snapd.rules Date: Thu Oct 6 17:39:42 2022 Ec2AMI: ami-0a23d90349664c6ee Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-2c Ec2InstanceType: t2.medium Ec2Kernel: unavailable Ec2Ramdisk: unavailable Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Xen HVM domU ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1020-aws root=PARTUUID=5bb90437-9efc-421d-aa94-c512c3b666a3 ro console=tty1 console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/24/2006 dmi.bios.release: 4.2 dmi.bios.vendor: Xen dmi.bios.version: 4.2.amazon dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.2.amazon:bd08/24/2006:br4.2:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:sku: dmi.product.name: HVM domU dmi.product.version: 4.2.amazon dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991975/+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 283115] Re: Gimp: toolbox windows can't be minimized
Fixed the upstream bug URL ** Changed in: gimp Importance: Low => Unknown ** Changed in: gimp Status: Fix Released => Unknown ** Changed in: gimp Remote watch: GNOME Bug Tracker #556896 => bugzilla.gnome.org/ #586664 ** Bug watch added: bugzilla.gnome.org/ #556896 https://bugzilla.gnome.org/show_bug.cgi?id=556896 ** Changed in: gimp Remote watch: bugzilla.gnome.org/ #586664 => bugzilla.gnome.org/ #556896 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/283115 Title: Gimp: toolbox windows can't be minimized Status in The Gimp: Unknown Status in GTK+: Unknown Status in gimp package in Ubuntu: Invalid Status in gtk+2.0 package in Ubuntu: New Bug description: gimp 2.6 in intrepid: it is impossible to minimize toolbar windows; they have only a x-Button to close ideally, these windows should be minimized automatically when the (last) Gimp image window is minimized Update While waiting, I designed some sort of workaround : Gnome>System>Preferences>Windows>Double-click titlebar>Roll up To manage notifications about this bug go to: https://bugs.launchpad.net/gimp/+bug/283115/+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 1900748] Re: update-initramfs fails with an error 'Error 24 : Write error : cannot write compressed block'
Uninstalling the older, unused kernel packages doesn't help because zsys takes snapshots of the boot pool before the removal and still eats up a comparable amount of space, thereby not solving the problem at all. -- 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/1900748 Title: update-initramfs fails with an error 'Error 24 : Write error : cannot write compressed block' Status in initramfs-tools package in Ubuntu: New Bug description: On a VirtualBox 6.1.14 VM with 2 vCPUs and 8 GB RAM and a 10 GiB hard disk space, I installed Ubuntu 20.10 with ZFS enabled on a full disk installation using the latest installer ISO available on the Ubuntu releases site. After installation, I booted into the installed OS and tried to install all the package updates. It went mostly fine till when it tried to run the update-initramfs operation and failed. Below are the relevant messages printed to the console. Setting up initramfs-tools (0.137ubuntu12) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools (0.137ubuntu12) ... update-initramfs: Generating /boot/initrd.img-5.8.0-25-generic Error 24 : Write error : cannot write compressed block E: mkinitramfs failure cpio 141 lz4 -9 -l 24 update-initramfs: failed for /boot/initrd.img-5.8.0-25-generic with 1. dpkg: error processing package initramfs-tools (--configure): installed initramfs-tools package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: initramfs-tools ZSys is adding automatic system snapshot to GRUB menu I checked the free disk space to ensure that there is enough available. guruprasad@groovy:~$ df -h FilesystemSize Used Avail Use% Mounted on tmpfs 796M 1.5M 795M 1% /run /dev/mapper/keystore-rpool453M 748K 419M 1% /run/keystore/rpool rpool/ROOT/ubuntu_slz5nq 6.0G 3.9G 2.1G 66% / tmpfs 3.9G 33M 3.9G 1% /dev/shm tmpfs 5.0M 4.0K 5.0M 1% /run/lock tmpfs 4.0M 0 4.0M 0% /sys/fs/cgroup bpool/BOOT/ubuntu_slz5nq 268M 197M 71M 74% /boot rpool/USERDATA/guruprasad_bdqa1x 2.1G 32M 2.1G 2% /home/guruprasad /dev/sda2 512M 19M 494M 4% /boot/efi rpool/ROOT/ubuntu_slz5nq/var/snap 2.1G 384K 2.1G 1% /var/snap rpool/ROOT/ubuntu_slz5nq/usr/local2.1G 512K 2.1G 1% /usr/local rpool/ROOT/ubuntu_slz5nq/srv 2.1G 256K 2.1G 1% /srv rpool/ROOT/ubuntu_slz5nq/var/lib 3.0G 933M 2.1G 31% /var/lib rpool/ROOT/ubuntu_slz5nq/var/www 2.1G 256K 2.1G 1% /var/www rpool/USERDATA/root_bdqa1x2.1G 256K 2.1G 1% /root rpool/ROOT/ubuntu_slz5nq/var/log 2.1G 25M 2.1G 2% /var/log rpool/ROOT/ubuntu_slz5nq/var/spool2.1G 384K 2.1G 1% /var/spool rpool/ROOT/ubuntu_slz5nq/var/games2.1G 256K 2.1G 1% /var/games rpool/ROOT/ubuntu_slz5nq/var/mail 2.1G 256K 2.1G 1% /var/mail rpool/ROOT/ubuntu_slz5nq/var/lib/AccountsService 2.1G 384K 2.1G 1% /var/lib/AccountsService rpool/ROOT/ubuntu_slz5nq/var/lib/NetworkManager 2.1G 256K 2.1G 1% /var/lib/NetworkManager rpool/ROOT/ubuntu_slz5nq/var/lib/dpkg 2.2G 59M 2.1G 3% /var/lib/dpkg rpool/ROOT/ubuntu_slz5nq/var/lib/apt 2.2G 77M 2.1G 4% /var/lib/apt tmpfs 796M 188K 796M 1% /run/user/1000 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: initramfs-tools 0.137ubuntu12 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Oct 20 23:05:25 2020 InstallationDate: Installed on 2020-10-20 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930) PackageArchitecture: all RebootRequiredPkgs: evolution-data-server gnome-shell SourcePackage: initramfs-tools UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1900748/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-pac
[Touch-packages] [Bug 1900748] Re: update-initramfs fails with an error 'Error 24 : Write error : cannot write compressed block'
This appears to be because of the limited remaining space in the /boot partition but the partition layout and sizes were automatically configured by the Ubuntu installer, which seems to be the culprit here. -- 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/1900748 Title: update-initramfs fails with an error 'Error 24 : Write error : cannot write compressed block' Status in initramfs-tools package in Ubuntu: New Bug description: On a VirtualBox 6.1.14 VM with 2 vCPUs and 8 GB RAM and a 10 GiB hard disk space, I installed Ubuntu 20.10 with ZFS enabled on a full disk installation using the latest installer ISO available on the Ubuntu releases site. After installation, I booted into the installed OS and tried to install all the package updates. It went mostly fine till when it tried to run the update-initramfs operation and failed. Below are the relevant messages printed to the console. Setting up initramfs-tools (0.137ubuntu12) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools (0.137ubuntu12) ... update-initramfs: Generating /boot/initrd.img-5.8.0-25-generic Error 24 : Write error : cannot write compressed block E: mkinitramfs failure cpio 141 lz4 -9 -l 24 update-initramfs: failed for /boot/initrd.img-5.8.0-25-generic with 1. dpkg: error processing package initramfs-tools (--configure): installed initramfs-tools package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: initramfs-tools ZSys is adding automatic system snapshot to GRUB menu I checked the free disk space to ensure that there is enough available. guruprasad@groovy:~$ df -h FilesystemSize Used Avail Use% Mounted on tmpfs 796M 1.5M 795M 1% /run /dev/mapper/keystore-rpool453M 748K 419M 1% /run/keystore/rpool rpool/ROOT/ubuntu_slz5nq 6.0G 3.9G 2.1G 66% / tmpfs 3.9G 33M 3.9G 1% /dev/shm tmpfs 5.0M 4.0K 5.0M 1% /run/lock tmpfs 4.0M 0 4.0M 0% /sys/fs/cgroup bpool/BOOT/ubuntu_slz5nq 268M 197M 71M 74% /boot rpool/USERDATA/guruprasad_bdqa1x 2.1G 32M 2.1G 2% /home/guruprasad /dev/sda2 512M 19M 494M 4% /boot/efi rpool/ROOT/ubuntu_slz5nq/var/snap 2.1G 384K 2.1G 1% /var/snap rpool/ROOT/ubuntu_slz5nq/usr/local2.1G 512K 2.1G 1% /usr/local rpool/ROOT/ubuntu_slz5nq/srv 2.1G 256K 2.1G 1% /srv rpool/ROOT/ubuntu_slz5nq/var/lib 3.0G 933M 2.1G 31% /var/lib rpool/ROOT/ubuntu_slz5nq/var/www 2.1G 256K 2.1G 1% /var/www rpool/USERDATA/root_bdqa1x2.1G 256K 2.1G 1% /root rpool/ROOT/ubuntu_slz5nq/var/log 2.1G 25M 2.1G 2% /var/log rpool/ROOT/ubuntu_slz5nq/var/spool2.1G 384K 2.1G 1% /var/spool rpool/ROOT/ubuntu_slz5nq/var/games2.1G 256K 2.1G 1% /var/games rpool/ROOT/ubuntu_slz5nq/var/mail 2.1G 256K 2.1G 1% /var/mail rpool/ROOT/ubuntu_slz5nq/var/lib/AccountsService 2.1G 384K 2.1G 1% /var/lib/AccountsService rpool/ROOT/ubuntu_slz5nq/var/lib/NetworkManager 2.1G 256K 2.1G 1% /var/lib/NetworkManager rpool/ROOT/ubuntu_slz5nq/var/lib/dpkg 2.2G 59M 2.1G 3% /var/lib/dpkg rpool/ROOT/ubuntu_slz5nq/var/lib/apt 2.2G 77M 2.1G 4% /var/lib/apt tmpfs 796M 188K 796M 1% /run/user/1000 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: initramfs-tools 0.137ubuntu12 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Oct 20 23:05:25 2020 InstallationDate: Installed on 2020-10-20 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930) PackageArchitecture: all RebootRequiredPkgs: evolution-data-server gnome-shell SourcePackage: initramfs-tools UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1900748/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launc
[Touch-packages] [Bug 1900748] [NEW] update-initramfs fails with an error 'Error 24 : Write error : cannot write compressed block'
Public bug reported: On a VirtualBox 6.1.14 VM with 2 vCPUs and 8 GB RAM and a 10 GiB hard disk space, I installed Ubuntu 20.10 with ZFS enabled on a full disk installation using the latest installer ISO available on the Ubuntu releases site. After installation, I booted into the installed OS and tried to install all the package updates. It went mostly fine till when it tried to run the update-initramfs operation and failed. Below are the relevant messages printed to the console. Setting up initramfs-tools (0.137ubuntu12) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools (0.137ubuntu12) ... update-initramfs: Generating /boot/initrd.img-5.8.0-25-generic Error 24 : Write error : cannot write compressed block E: mkinitramfs failure cpio 141 lz4 -9 -l 24 update-initramfs: failed for /boot/initrd.img-5.8.0-25-generic with 1. dpkg: error processing package initramfs-tools (--configure): installed initramfs-tools package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: initramfs-tools ZSys is adding automatic system snapshot to GRUB menu I checked the free disk space to ensure that there is enough available. guruprasad@groovy:~$ df -h FilesystemSize Used Avail Use% Mounted on tmpfs 796M 1.5M 795M 1% /run /dev/mapper/keystore-rpool453M 748K 419M 1% /run/keystore/rpool rpool/ROOT/ubuntu_slz5nq 6.0G 3.9G 2.1G 66% / tmpfs 3.9G 33M 3.9G 1% /dev/shm tmpfs 5.0M 4.0K 5.0M 1% /run/lock tmpfs 4.0M 0 4.0M 0% /sys/fs/cgroup bpool/BOOT/ubuntu_slz5nq 268M 197M 71M 74% /boot rpool/USERDATA/guruprasad_bdqa1x 2.1G 32M 2.1G 2% /home/guruprasad /dev/sda2 512M 19M 494M 4% /boot/efi rpool/ROOT/ubuntu_slz5nq/var/snap 2.1G 384K 2.1G 1% /var/snap rpool/ROOT/ubuntu_slz5nq/usr/local2.1G 512K 2.1G 1% /usr/local rpool/ROOT/ubuntu_slz5nq/srv 2.1G 256K 2.1G 1% /srv rpool/ROOT/ubuntu_slz5nq/var/lib 3.0G 933M 2.1G 31% /var/lib rpool/ROOT/ubuntu_slz5nq/var/www 2.1G 256K 2.1G 1% /var/www rpool/USERDATA/root_bdqa1x2.1G 256K 2.1G 1% /root rpool/ROOT/ubuntu_slz5nq/var/log 2.1G 25M 2.1G 2% /var/log rpool/ROOT/ubuntu_slz5nq/var/spool2.1G 384K 2.1G 1% /var/spool rpool/ROOT/ubuntu_slz5nq/var/games2.1G 256K 2.1G 1% /var/games rpool/ROOT/ubuntu_slz5nq/var/mail 2.1G 256K 2.1G 1% /var/mail rpool/ROOT/ubuntu_slz5nq/var/lib/AccountsService 2.1G 384K 2.1G 1% /var/lib/AccountsService rpool/ROOT/ubuntu_slz5nq/var/lib/NetworkManager 2.1G 256K 2.1G 1% /var/lib/NetworkManager rpool/ROOT/ubuntu_slz5nq/var/lib/dpkg 2.2G 59M 2.1G 3% /var/lib/dpkg rpool/ROOT/ubuntu_slz5nq/var/lib/apt 2.2G 77M 2.1G 4% /var/lib/apt tmpfs 796M 188K 796M 1% /run/user/1000 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: initramfs-tools 0.137ubuntu12 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Oct 20 23:05:25 2020 InstallationDate: Installed on 2020-10-20 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930) PackageArchitecture: all RebootRequiredPkgs: evolution-data-server gnome-shell SourcePackage: initramfs-tools UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- 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/1900748 Title: update-initramfs fails with an error 'Error 24 : Write error : cannot write compressed block' Status in initramfs-tools package in Ubuntu: New Bug description: On a VirtualBox 6.1.14 VM with 2 vCPUs and 8 GB RAM and a 10 GiB hard disk space, I installed Ubuntu 20.10 with ZFS enabled on a full disk installation using the latest installer ISO available on the Ubuntu releases site. After installation, I booted into the installed OS and tried to install all the package updates. It went mostly fine till when it tried to run the update-initramfs operation and failed. Below are the
