[Touch-packages] [Bug 1944741] Re: HiFive Unmatched partitions are named "Unleashed"
** Changed in: util-linux (Debian) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1944741 Title: HiFive Unmatched partitions are named "Unleashed" Status in util-linux package in Ubuntu: New Status in util-linux source package in Impish: Fix Committed Status in util-linux source package in Jammy: New Status in util-linux package in Debian: Fix Released Bug description: [Impact] Both HiFive Unleashed and HiFive Unmatched bootloaders seek for the same UUIDs to load the next stage bootloader: the current name makes partitions on Unmatched board appear as 'Unleashed'. This issue gives the feeling that the Ubuntu RISC-V images made specifically for those 2 boards were assembled in a rushed manner. The attached patch fixes this by removing the 'Unleashed' part of the current name so that it fits both, it was build againt all architectures here: https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+sourcepub/12783067/+listing-archive-extra [Test Plan] 1. Download the SiFive Unmatched image here: https://cdimage.ubuntu.com/ubuntu-server/daily-preinstalled/pending/impish-preinstalled-server-riscv64+unmatched.img.xz 2. Follow instructions here to launch a riscv64 VM: https://wiki.ubuntu.com/RISC-V 3. Execute the following command: ubuntu@ubuntu:~$ sudo fdisk -l Disk /dev/vda: 40 GiB, 42949672960 bytes, 83886080 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 0F66C0C3-A5E4-439B-907E-ABAD106FE4A7 Device Start End Sectors Size Type /dev/vda1 235554 83886046 83650493 39.9G Linux filesystem /dev/vda12 227362 235553 81924M Linux filesystem /dev/vda13 34 2081 20481M HiFive Unleashed FSBL /dev/vda14 208210273 81924M HiFive Unleashed BBL /dev/vda15 10274 227361 217088 106M EFI System Partition table entries are not in disk order. 4. Download and install the new packages that contain the fix here: https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+files/libfdisk1_2.36.1-8ubuntu4_riscv64.deb https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+files/libfdisk-dev_2.36.1-8ubuntu4_riscv64.deb https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+files/fdisk_2.36.1-8ubuntu4_riscv64.deb 5. Re-execute the same command as above: ubuntu@ubuntu:~$ sudo fdisk -l Disk /dev/vda: 40 GiB, 42949672960 bytes, 83886080 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 0F66C0C3-A5E4-439B-907E-ABAD106FE4A7 Device Start End Sectors Size Type /dev/vda1 235554 83886046 83650493 39.9G Linux filesystem /dev/vda12 227362 235553 81924M Linux filesystem /dev/vda
[Touch-packages] [Bug 1946096] Re: Apply upstream patches to fix problems for Foxconn and Quectel modems.
Hi SRU team, Please help to check the status of this case which looks stuck at some steps. Thanks -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1946096 Title: Apply upstream patches to fix problems for Foxconn and Quectel modems. Status in OEM Priority Project: In Progress Status in modemmanager package in Ubuntu: Fix Committed Bug description: [Impact] The following 2 modems need the ModemManager v1.16.6 suite to be patched from v1.18.2 to fix some problems(LP#1943774, LP#1943780): * Foxconn SDX55 T99W175 5G sub6 PCIE Modem * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem The requested upstream patches are listed as below: * for Quectel EM160 4G ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/83ac82470589a3672092a0ba0be855093b1cf5e2 * for Foxconn T99W175 ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/21ae558fe3600c84b3ca7dcd9bf50a3ba576c7c9 **https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/76e700f4fd703f952208993330ab098305c13d6b ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/52bf2c641171ded9e617022f40497c8984520371 ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/33e2b023ef01bea9da37ae2beb192f7d92bce47a ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/f72046701659073fbfa97516e155865647acb154 [Test Plan] 1. Install the Ubuntu image. 2. Boot and login the system. 3. Prepare the modem’s firmware and install the firmware upgrading application provided by Foxconn and Quectel 4. Using the firmware upgrading application to upgrade the modem’s firmware 5. Verify if the modem’s firmware upgrading is successful 6. Reboot 7. Verify if the upgraded modem firmware is still working [Where problems could occur] The requested upstream patches are for these 2 specific modems and the status information. This should not affect existing generic functions and other modems. [Other Info] The firmware and the upgrading application can be downloaded from the following link: * LP#1943774 for Quectel modems * LP#1943780 for Foxconn modems To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946096/+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 1930188] Re: Acer Aspire 5 sound driver issues
All 7 packages were not yet available from software updater in focal but I managed to upgrade them using apt-get upgrade and seems to work fine. Thanks all again. -- 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/1930188 Title: Acer Aspire 5 sound driver issues Status in alsa-ucm-conf package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Released Status in linux source package in Focal: Fix Released Status in pulseaudio source package in Focal: Fix Released Status in alsa-ucm-conf source package in Hirsute: Fix Released Status in linux source package in Hirsute: Fix Released Status in pulseaudio source package in Hirsute: Fix Released Status in alsa-ucm-conf source package in Impish: Fix Committed Status in linux source package in Impish: Fix Released Status in pulseaudio source package in Impish: Fix Released Bug description: SRU Justification for alsa-ucm-conf: [Impact] On the machines with the sof audio driver, users could adjust the input volume from UI, but this only adjusts the "Capture Volume", the "Mic Boost" can't be changed, if "Mic Boost" is 0, even we adjust the "Capture Volume" to max, the recorded volume is still very low. [Fix] Backport a upstream patch, the patch adds the "Mic Boost" into the ucm [Test] plug a headset, make sure the headset-mic is the active input device, adjust the input volume to %20, open a terminal and run alsamixer, check the "Capture Volume" and "Mic Boost" value, then adjust the input volume to 80%, check those values and we could see both values are changed. [Where problems could occur] This patch could make the parse of input volume control fail, then the input volume can't be changed anymore when users adjust the volume from UI. But this possibility is very low, I tested this patch on many lenovo and dell machines with sof audio driver, all worked well. SRU Justification for pulseaudio: [Impact] On the machines with the sof audio driver, after booting up, the active output device is speaker by default, we adjust the output volume to 100%, then we plug a headphone, and adjust the output volume from 100% to 20%, now in theory, the speaker's volume is 100%, the headphone's volume is 20%. We plugout the headphone, the active output device becomes speaker and we expect the volume changes to 100%, but the output volume for speaker is 20%. [Fix] Backport a upstream patch, this patch is already in the pulseaudio-15.0, so impish already has this fix. Only hirsute and focal need to backport this patch. [Test] adjust speaker's volume to 80%, then plug headphone and adjust headphone's volume to 20%, unplug the headphone, the speaker's volume becomes to 80%, plug the headphone, the headphone's volume becomes to 20%. [Where problems could occur] The patch writes the output volume to hardware immediately when switching output device on the machines with sof audio driver, this could introduce pop noise when changing the output device, but this possibility is very low, I tested the patch on many lenovo and dell machines with sof audio driver, all worked as expected and have no pop noise when switching output device. The patch was merged to ubuntu 5.13.0 and 5.11.0 generic kernels with stable update already, but it is not merged to ubuntu 5.4.0 kernel yet, so I sent this SRU for the focal kernel. [Impact] Users plug headphone and Mic to the audio jacks, but the system can't detect them, and couldn't output sound through headphone and record sound through Mic. [Fix] Backport a upstream patch, this will set the Mic to auto-detection mode and set the headphone to left location. [Test] Plug a headset to the headset audio jack, both headphone and mic could be detected. And output the sound to headphone, could hear the sound, record the sound through Mic, the sound could be recorded. [Where problems could occur] The patch is specific to Acer Aspire 5 machine, if it could introduce regression, it will make the audio like internal mic and internal spk stop working. But this possibility is very low. Hello, There seems to be lots of issues in sound driver for Acer Aspire A515-56-57XR with ALC255. I will list all of them below and what I have tried so far. 1. Headphones appears always plugged in even if they are physically not 2. When actually plugging in headset/earphones it does not auto switch from speakers/internal mic to headphones/headset microphone automatically and vice versa, have to manually switch everyti
[Touch-packages] [Bug 1662620] Re: "ip addr add" permits illegal labels
Hm. It's not clear what the actual user impact of this is? Reading from the original description, it seems that if a user uses an invalid label to set one address and *also* uses a valid label to set another address *then* tools can be confused? “Our parser is actually more lenient than the manpage states” on its own is definitely not SRU-worthy, but if it breaks other tools then maybe? On the other hand, from the bug it looks like if you *don't* mix valid and invalid labels then everything actually works? So this would potentially be breaking currently working setups? I think we need more information before determining whether this should be accepted as an SRU. ** Changed in: iproute2 (Ubuntu Bionic) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1662620 Title: "ip addr add" permits illegal labels Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Bionic: Incomplete Bug description: [Impact] * The filter on label names does not match the intention by upstream nor the description in the man page * Fix by backporting upstream fix that strengthens the check [Test Plan] Bad case: root@b:~# ip addr add 1.1.1.1 label test1 dev eth0 "dev" (eth0) must match "label" (test1). root@b:~# ip addr add 1.1.1.1 label eth0-test dev eth0 root@b:~# ip addr show dev eth0 | grep test inet 1.1.1.1/32 scope global eth0-test With the fix it should look like: root@i:~# ip addr add 1.1.1.1 label test1 dev eth0 "label" (test1) must match "dev" (eth0) or be prefixed by "dev" with a colon. root@i:~# ip addr add 1.1.1.1 label eth0-test dev eth0 "label" (eth0-test) must match "dev" (eth0) or be prefixed by "dev" with a colon. root@i:~# ip addr show dev eth0 | grep test [Where problems could occur] * While the fix indeed "corrects" behavior I must say that if someone relied on the non-intended behavior it would now break e.g. his scripting or automation. [Other Info] * It was too easy to fix and too long dormant to ignore it further, but if the SRU team says this is too much regression risk relative to the gain we will mark it Won't Fix based on that decision. --- ip-address(8) manpage states: label NAME Each address may be tagged with a label string. In order to preserve compatibility with Linux-2.0 net aliases, this string must coincide with the name of the device or must be prefixed with the device name followed by colon. But you can omit the colon, "ip addr add" is ONLY checking the label is prefixed with the device: # ip addr add 1.1.1.1 label test1 dev eth0 "dev" (eth0) must match "label" (test1). # ip addr add 1.1.1.2 label eth0-test2 dev eth0 # ip addr add 1.1.1.3 label eth0:test3 dev eth0 Now ifconfig becomes confused about eth0-test2: # ifconfig eth0-test2 eth0-test2: error fetching interface information: Device not found # ifconfig eth0:test3 eth0:test3 Link encap:Ethernet HWaddr b0:d5:cc:fe:1d:7c inet addr:1.1.1.3 Bcast:0.0.0.0 Mask:255.255.255.255 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:171 And daemons like ntpd also log errors about the interface with the illegal label: ntpd[7570]: eth0-test3: getting interface flags: No such device ## => many of this error per minute until: ntpd[7570]: Too many errors. Shutting up. So, I think ip addr show disallow adding address with illegal (as stated by his own documentation) labels, it must also check for the colon following the dev name. Version: 4.3.0-1ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1662620/+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 1389283] Re: dh-python 1.20141026-1ubuntu1 incorrectly handles gi package names
I'd argue that the issue here is that "Requires: gi.repository.GLib" is incorrect. There is no such package on PyPI, so the requirement will never be satisfied. Using pydist overrides, as you've done in pasaffe, seems reasonable. ** Changed in: dh-python (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/1389283 Title: dh-python 1.20141026-1ubuntu1 incorrectly handles gi package names Status in dh-python package in Ubuntu: Invalid Bug description: 1.20141026-1ubuntu1 introduced support for guessing dependencies from the egginfo file: * Add support for guessing dependencies from egg-info files (closes: 756378) But this is mishandling gi.introspection dependencies. The pasaffe package, which compiles fine on Utopic, is now adding bogus dependencies to the vivid package: From the egg-info file: Requires: gi.repository.GLib Requires: gi.repository.GObject Requires: gi.repository.Gdk Requires: gi.repository.Gio Requires: gi.repository.Gtk Requires: gi.repository.Pango From the build log: dh_python3 -O--buildsystem=pybuild I: dh_python3 pydist:183: Cannot find installed package that provides gi.repository.glib. Using python3-gi.repository.glib as package name. Please add "gi.repository.glib correct_package_name" line to debian/py3dist-overrides to override it IF this is incorrect. I: dh_python3 pydist:183: Cannot find installed package that provides gi.repository.gobject. Using python3-gi.repository.gobject as package name. Please add "gi.repository.gobject correct_package_name" line to debian/py3dist-overrides to override it IF this is incorrect. I: dh_python3 pydist:183: Cannot find installed package that provides gi.repository.gdk. Using python3-gi.repository.gdk as package name. Please add "gi.repository.gdk correct_package_name" line to debian/py3dist-overrides to override it IF this is incorrect. I: dh_python3 pydist:183: Cannot find installed package that provides gi.repository.gio. Using python3-gi.repository.gio as package name. Please add "gi.repository.gio correct_package_name" line to debian/py3dist-overrides to override it IF this is incorrect. I: dh_python3 pydist:183: Cannot find installed package that provides gi.repository.gtk. Using python3-gi.repository.gtk as package name. Please add "gi.repository.gtk correct_package_name" line to debian/py3dist-overrides to override it IF this is incorrect. I: dh_python3 pydist:183: Cannot find installed package that provides gi.repository.pango. Using python3-gi.repository.pango as package name. Please add "gi.repository.pango correct_package_name" line to debian/py3dist-overrides to override it IF this is incorrect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/1389283/+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 1794229] Re: python packages should not ship colliding /usr/lib/python3/dist-packages/.pytest_cache
Fixed in dh-python in 3.20180927. ** Changed in: dh-python (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/1794229 Title: python packages should not ship colliding /usr/lib/python3/dist- packages/.pytest_cache Status in alembic package in Ubuntu: Fix Released Status in astroid package in Ubuntu: Invalid Status in dh-python package in Ubuntu: Fix Released Status in Debian: Fix Released Status in alembic package in Debian: Fix Released Bug description: Python packages should not ship /usr/lib/python3/dist- packages/.pytest_cache Recently, two packages python3-alembic and python3-astroid both shipped these files which collided on package install dh-python has been improved upstream to stream all hidden "dot" directories in Debian #907871 This change should be imported and both alembic and astroid should be rebuilt (plus any other packages shipping this file) Preparing to unpack .../178-python3-astroid_2.0.4-1_all.deb ... Unpacking python3-astroid (2.0.4-1) over (1.6.5-1ubuntu4) ... dpkg: error processing archive /tmp/apt-dpkg-install-rbF4wE/178-python3-astroid_2.0.4-1_all.deb (--unpack): trying to overwrite '/usr/lib/python3/dist-packages/.pytest_cache/v/cache/nodeids', which is also in package python3-alembic 1.0.0-1ubuntu1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alembic/+bug/1794229/+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 1941708] Re: BlueZ 5.62 release
** Changed in: bluez (Ubuntu) Importance: Undecided => Wishlist ** Tags added: upgrade-software-version -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1941708 Title: BlueZ 5.62 release Status in bluez package in Ubuntu: In Progress Bug description: BlueZ 5.62 release is out: https://mirrors.edge.kernel.org/pub/linux/bluetooth/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1941708/+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 413278]
https://www.ремонты-квартир.com/ https://www.дизайн-квартиры.com/ https://www.о-ремонте.com/ https://www.о-заборах.com/ https://www.bsegypt.com/ https://www.buyingrealty.net/ https://www.khersonnews.com/ https://www.kontrolstroy.info/ https://www.sama-mama.com/ https://www.secretovnet.org/ https://www.teleriko.com/ https://www.us-best-store.com/ https://www.віктор.com/ https://www.accord-hotel.ru/ https://releazer.ru/ https://www.a-n-e-k-d-o-t.ru/ https://www.adhan.ru/ http://www.al-aures.ru/ https://www.apriori-design.ru/ http://artdoski.ru/ https://www.bombusmod.net.ru/ https://www.canadianahealthandcaremallreviews.ru/ https://www.celestiaproject.ru/ https://www.cryptogu.ru/ https://www.downloadskypefree.ru/ https://www.encyclopedia-flowers.ru/ https://www.factura.net.ru/ http://freewizards.ru/ http://futurefactory.ru/ https://glina-med.ru/ http://google-dmoz.ru/ http://iix.su/ https://www.imperia51.ru/ https://www.info-tehnologii.ru/ https://www.kvartira-v-bolgarii.ru/ https://ljubi-i-pozdravljaj.ru/ https://www.majesticarticles.ru/ https://www.onlinecredit247.ru/ https://www.orfey.net.ru/ https://www.pgpk.net.ru/ https://www.rainbow.net.ru/ http://www.rainbowbaby.ru/ http://www.respublika-okon.ru/ https://ribku-lovim.ru/ http://rusorchestra.ru/ http://shmoscow.ru/ https://www.skifspb.ru/ https://www.spare.net.ru/ https://www.stranainform.ru/ https://www.taxi-smile.ru/ https://www.tkanishik.ru/ http://www.tremulous.net.ru/ https://trust-women.ru/ http://uralbel.ru/ https://www.yar-art-union.ru/ https://www.xn7sbcngq4awkg0k.xn--p1ai/ https://www.xn7sbbmgbytlh3a0ll.xn--p1ai/ https://www.xn--35-mlcuxidl.xn--p1ai/ https://www.xn--f1addf1alkk1d.xn--p1ai/ https://www.history-of-great-discoveries.com/ https://www.it-business-trends.com https://www.interesting-history-of-art.com https://www.interesting-news-about-cars.com https://www.architecture-and-design-news.com https://history-of-great-discoveries.blogspot.com/ https://it-business-trends.blogspot.com/ https://interesting-history-of-art.blogspot.com/ https://interesting-news-about-cars.blogspot.com/ https://architecture-and-design-news.blogspot.com/ https://www.secretovnet.org/archives/18806 https://www.secretovnet.org/archives/17685 https://www.secretovnet.org/archives/17683 https://www.secretovnet.org/archives / 17681 https://www.secretovnet.org/archives/13740 https://www.secretovnet.org/archives/13737 https://www.secretovnet.org/archives/13734 https://www.secretovnet.org / archives / 13732 https://www.secretovnet.org/archives/13729 https://www.secretovnet.org/archives/17679 https://www.secretovnet.org/archives/17677 https://www.secretovnet .org / archives / 17675 https://www.secretovnet.org/archives/17670 https://www.secretovnet.org/archives/17667 https://www.secretovnet.org/archives/18686 https://www.secretovnet.org/archives/18684 https://www.secretovnet.org/archives/18682 https://www.secretovnet.org/archives/17665 https://www.secretovnet.org/archives / 17663 https://www.secretovnet.org/archives/17661 https://www.secretovnet.org/archives/17659 https://www.secretovnet.org/archives/17657 https://www.secretovnet.org / archives / 13723 https://www.secretovnet.org/archives/13717 https://www.secretovnet.org/archives/13714 https://www.secretovnet.org/archives/13711 https://www.secretovnet .org / archives / 13708 https://www.secretovnet.org/archives/17655 https://www.secretovnet.org/archives/13702 https://www.secretovnet.org/archives/17647 https://www.secretovnet.org/archives/17645 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to eglibc in Ubuntu. https://bugs.launchpad.net/bugs/413278 Title: stack protector guard value does not lead with a NULL byte Status in GLibC: Fix Released Status in eglibc package in Ubuntu: Fix Released Status in glibc package in Ubuntu: Invalid Status in eglibc source package in Jaunty: Invalid Status in glibc source package in Jaunty: Fix Released Status in eglibc source package in Karmic: Fix Released Status in glibc source package in Karmic: Invalid Bug description: IMPACT: stack protections are weakened due to strcpy function being able to write the stack guard (since it does not start with a zero byte). ADDRESSED: correctly implement leading zero, as done in Karmic. DISCUSSION: regression potential is low, since the patch is isolated and well tested. TEST CASE: $ bzr branch lp:~ubuntu-bugcontrol/qa-regression-testing/master qa-regression-testing $ cd qa-regression-testing/scripts $ ./test-glibc-security.py -v Build helper tools ... (9.10) ok glibc heap protection ... ok sprintf not pre-truncated with -D_FORTIFY_SOURCE=2 ... ok glibc pointer obfuscation ... ok Password hashes ... (sha512) ok Stack guard exists ... ok Stack guard leads with zero byte ... FAIL Stack guard is randomized ... ok == FAIL: S
[Touch-packages] [Bug 1782984] Re: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications
Has anyone tried PCManFM or Inkscape on focal? It seems that this update doesn't fix GNOME Shell on focal, but *maybe* that's because Shell is hitting a different bug? If this can be verified to fix PCManFM, Inkscape, or something on focal we can release it and open a new bug for GNOME Shell on Focal. If this *doesn't* fix something on focal, we need to work out why - maybe it needs more changes backported, like bionic did? If FCManFM & Inkscape don't hang on focal *without* this update then I think we can release the bionic update and close the focal task. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1782984 Title: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications Status in libx11 package in Ubuntu: Fix Released Status in libx11 source package in Bionic: Fix Committed Status in libx11 source package in Focal: Fix Committed Status in libx11 source package in Groovy: Won't Fix Bug description: [Impact] There is a race in libx11 causing applications to randomly abort. It's not trivial to reproduce, but there are enough duplicates that this deserves an SRU to bionic & focal. [Fix] Backport a commit from upstream: From dbb55e1a5e82870466b095097d9e46046680ec25 Mon Sep 17 00:00:00 2001 From: Frediano Ziglio Date: Wed, 29 Jan 2020 09:06:54 + Subject: [PATCH] Fix poll_for_response race condition In poll_for_response is it possible that event replies are skipped and a more up to date message reply is returned. This will cause next poll_for_event call to fail aborting the program. This was proved using some slow ssh tunnel or using some program to slow down server replies (I used a combination of xtrace and strace). How the race happens: - program enters into poll_for_response; - poll_for_event is called but the server didn't still send the reply; - pending_requests is not NULL because we send a request (see call to append_pending_request in _XSend); - xcb_poll_for_reply64 is called from poll_for_response; - xcb_poll_for_reply64 will read from server, at this point server reply with an event (say sequence N) and the reply to our last request (say sequence N+1); - xcb_poll_for_reply64 returns the reply for the request we asked; - last_request_read is set to N+1 sequence in poll_for_response; - poll_for_response returns the response to the request; - poll_for_event is called (for instance from another poll_for_response); - event with sequence N is retrieved; - the N sequence is widen, however, as the "new" number computed from last_request_read is less than N the number is widened to N + 2^32 (assuming last_request_read is still contained in 32 bit); - poll_for_event enters the nested if statement as req is NULL; - we compare the widen N (which now does not fit into 32 bit) with request (which fits into 32 bit) hitting the throw_thread_fail_assert. To avoid the race condition and to avoid the sequence to go back I check again for new events after getting the response and return this last event if present saving the reply to return it later. To test the race and the fix it's helpful to add a delay (I used a "usleep(5000)") before calling xcb_poll_for_reply64. Original patch written by Frediano Ziglio, see https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/34 Reworked primarily for readability by Peter Hutterer, see https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/53 Signed-off-by: Peter Hutterer bionic needs another commit so that the real fix applies. [Test case] It's a race condition, the SRU sponsor (tjaalton) does not have a test case for this, but the bug subscribers seem to. [Where things could go wrong] In theory there might be a case where a race still happens, but since this has been upstream for a year now with no follow-up commits, it's safe to assume that there are no regressions. -- STEPS TO REPRODUCE == The bug seems to occur when clicking on a file or folder. It is random and difficult to provide clear steps to reproduce. It is, however, a common situation. EXPECTED RESULTS pcmanfm works without problem. ACTUAL RESULTS == All pcmanfm windows become unresponsive, though background processes (e.g. copying) may continue without problem. with the same error message in ~/.cache/lxsession/LXDE/run.log: [xcb] Unknown sequence number while processing queue [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called [xcb] Aborting, sorry about that. pcmanfm: xcb_io.c:259: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed. ** Message: 19:58:49.267: app.vala:130: pcmanfm exit with this type of exit: 6 ** Message: 19:58:49.268: app.vala:148: E
[Touch-packages] [Bug 1892825] Re: update-locale not perform correctly sanity checks
Fwiw I reported this as a pam bug too https://github.com/linux- pam/linux-pam/issues/395 ** Bug watch added: github.com/linux-pam/linux-pam/issues #395 https://github.com/linux-pam/linux-pam/issues/395 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1892825 Title: update-locale not perform correctly sanity checks Status in glibc package in Ubuntu: In Progress Status in pam package in Ubuntu: New Status in glibc source package in Bionic: New Status in pam source package in Bionic: New Status in glibc source package in Focal: New Status in pam source package in Focal: New Status in glibc source package in Hirsute: New Status in pam source package in Hirsute: New Status in glibc source package in Impish: New Status in pam source package in Impish: New Bug description: By passing wrong input as following: sudo update-locale LANGUAGE = en_US.UTF-8 result is: ... #LANGUAGE=en = This "equal" sign that was added makes system completely unusable(can't run sudo anymore): bentzy@bentzy-nb:~$ sudo vim /etc/default/locale sudo: pam_open_session: Bad item passed to pam_*_item() sudo: policy plugin failed session initialization Fixed it booting from installation disk and fixing corrupted /etc/default/locale ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: locales 2.31-0ubuntu9 Uname: Linux 5.5.4-050504-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Aug 25 09:36:03 2020 InstallationDate: Installed on 2020-08-17 (7 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: glibc UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1892825/+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 1947800] Re: /usr/share/apport/whoopsie-upload-all:zlib.error:/usr/share/apport/whoopsie-upload-all@196:collect_info:process_report:add_gdb_info:gdb_command:write:read:readinto:r
** Tags added: rls-ii-incoming -- 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/1947800 Title: /usr/share/apport/whoopsie-upload- all:zlib.error:/usr/share/apport/whoopsie-upload- all@196:collect_info:process_report:add_gdb_info:gdb_command:write:read:readinto:read Status in apport package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.11-0ubuntu70, the problem page at https://errors.ubuntu.com/problem/7120f8aebdf09e9dca39196d035eec234071e800 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/1947800/+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 1947800] [NEW] /usr/share/apport/whoopsie-upload-all:zlib.error:/usr/share/apport/whoopsie-upload-all@196:collect_info:process_report:add_gdb_info:gdb_command:write:read:readinto
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.11-0ubuntu70, the problem page at https://errors.ubuntu.com/problem/7120f8aebdf09e9dca39196d035eec234071e800 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: groovy hirsute impish kylin-21.04 rls-ii-incoming -- 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/1947800 Title: /usr/share/apport/whoopsie-upload- all:zlib.error:/usr/share/apport/whoopsie-upload- all@196:collect_info:process_report:add_gdb_info:gdb_command:write:read:readinto:read Status in apport package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.11-0ubuntu70, the problem page at https://errors.ubuntu.com/problem/7120f8aebdf09e9dca39196d035eec234071e800 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/1947800/+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 1933828] Re: NTP servers from DHCP are not propagated to timesyncd
Here is a networkd-dispatcher fix: https://launchpad.net/~hellsworth/+archive/ubuntu/networkd-dispatcher/+build/22316215 And here is a network-manager fix: https://launchpad.net/~hellsworth/+archive/ubuntu/network-manager/+build/22316944 Both should work, so please test the networkd-dispatcher fix first and network-manager if needbe. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1933828 Title: NTP servers from DHCP are not propagated to timesyncd Status in OEM Priority Project: New Status in network-manager package in Ubuntu: New Status in network-manager source package in Focal: New Bug description: Network manager gets NTP servers from DHCP but do not update timesyncd to use it which keeps using ntp.ubuntu.com. This is a problem on private networks which do not have access to public internet. On this type of network the configuration of timesyncd must be updated manually instead of inheriting the conf from the dhcp servers. This can be integrated with a NM dispatcher script such as below: etc/NetworkManager/dispatcher.d/10-update-timesyncd for example: ==8<=8<=8<=8<=8<== #! /usr/bin/bash [ -n "$CONNECTION_UUID" ] || exit INTERFACE=$1 ACTION=$2 case $ACTION in up | dhcp4-change | dhcp6-change) [ -n "$DHCP4_NTP_SERVERS" ] || exit mkdir -p /etc/systemd/timesyncd.conf.d/ cat< /etc/systemd/timesyncd.conf.d/$CONNECTION_UUID.conf [Time] NTP=$DHCP4_NTP_SERVERS RootDistanceMaxSec=15 EOF systemctl restart systemd-timesyncd ;; down) rm -f /etc/systemd/timesyncd.conf.d/$CONNECTION_UUID.conf systemctl restart systemd-timesyncd ;; esac ==8<=8<=8<=8<=8<== ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: network-manager 1.30.0-1ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-18.19+21.10.1-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jun 28 14:08:52 2021 InstallationDate: Installed on 2020-05-31 (393 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527) RebootRequiredPkgs: linux-image-5.11.0-20-generic linux-base SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.30.0 connected started full enabled enabled disabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1933828/+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 1925468] Re: stack-buffer-overflow of import.c in function _import_bin
** Changed in: libcaca
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libcaca in Ubuntu.
https://bugs.launchpad.net/bugs/1925468
Title:
stack-buffer-overflow of import.c in function _import_bin
Status in libcaca:
Fix Released
Status in libcaca package in Ubuntu:
Triaged
Bug description:
Hello ubuntu security team
issues：https://github.com/cacalabs/libcaca/issues/56
System info：
Ubuntu 20.04 : clang 10.0.0 , gcc 9.3.0
Fedora 33: clang 11.0.0 , gcc 10.2.1
libcaca version e4968ba
Verification steps：
1.Get the source code of libcaca
2.Compile the libcaca.so library
$ cd libcaca
$ ./bootstrap
$ ./configure
$ make
or
$ cd libcaca
$ ./bootstrap
$ ../configure CC="clang -O2 -fno-omit-frame-pointer -g
-fsanitize=address,fuzzer-no-link -fsanitize-coverage=bb" CXX="clang++ -O2
-fno-omit-frame-pointer -g -fsanitize=address,fuzzer-no-link
-fsanitize-coverage=bb"
$ make
3.Create the poc_bin.cc && build
#include "config.h"
#include "caca.h"
//#include "common-image.h"
#include
#include
#include
#include
#include
#include
using namespace std;
void crash(const uint8_t *Data, size_t Size) {
if(Size<8) return ;
size_t len=0;
caca_canvas_t *cv;
cv = caca_create_canvas(0,0);
caca_create_frame(cv,0);
caca_set_frame(cv,0);
caca_import_canvas_from_memory(cv,Data,Size,"bin");
caca_free_canvas(cv);
cv=NULL;
}
int main(int args,char* argv[]){
size_t len = 0;
unsigned char buffer[] =
{0x0a,0x20,0x0a,0x0a,0x20,0x20,0x20,0x20,0x20,0x20,0x47,0x47,0x47};
len = sizeof(buffer)/sizeof(unsigned char);
printf("%d\n",sizeof(buffer)/sizeof(unsigned char));
crash((const uint8_t*)buffer,len);
return 0;
}
4.compile poc_bin.cc
clang++ -g poc_bin.cc -O2 -fno-omit-frame-pointer -fsanitize=address
-I./caca/ -lcaca -L./caca/.libs/ -Wl,-rpath,./caca/.libs/ -o poc_bin
5.Run poc_bin
asan info:
=
==3817476==ERROR: AddressSanitizer: stack-buffer-overflow on address
0x7ffe7cd3774d at pc 0x7f8c6314acfd bp 0x7ffe7cd376c0 sp 0x7ffe7cd376b8
READ of size 1 at 0x7ffe7cd3774d thread T0
#0 0x7f8c6314acfc in _import_bin
/home/hh/Downloads/libcaca/caca/codec/import.c:425:33
#1 0x4c6c72 in crash(unsigned char const*, unsigned long)
/home/hh/Downloads/libcaca/poc_bin.cc:21:3
#2 0x4c6c72 in main /home/hh/Downloads/libcaca/poc_bin.cc:34:9
#3 0x7f8c62ba00b2 in __libc_start_main
/build/glibc-eX1tMB/glibc-2.31/csu/../csu/libc-start.c:308:16
#4 0x41c38d in _start (/home/hh/Downloads/libcaca/poc_bin+0x41c38d)
Address 0x7ffe7cd3774d is located in stack of thread T0 at offset 45 in frame
#0 0x4c6b9f in main /home/hh/Downloads/libcaca/poc_bin.cc:28
This frame has 1 object(s):
[32, 45) 'buffer' (line 31) <== Memory access at offset 45 overflows this
variable
HINT: this may be a false positive if your program uses some custom stack
unwind mechanism, swapcontext or vfork
(longjmp and C++ exceptions *are* supported)
SUMMARY: AddressSanitizer: stack-buffer-overflow
/home/hh/Downloads/libcaca/caca/codec/import.c:425:33 in _import_bin
Shadow bytes around the buggy address:
0x10004f99ee90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x10004f99eea0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x10004f99eeb0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x10004f99eec0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x10004f99eed0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
=>0x10004f99eee0: 00 00 00 00 f1 f1 f1 f1 00[05]f3 f3 00 00 00 00
0x10004f99eef0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x10004f99ef00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x10004f99ef10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x10004f99ef20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x10004f99ef30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Shadow byte legend (one shadow byte represents 8 application bytes):
Addressable: 00
Partially addressable: 01 02 03 04 05 06 07
Heap left redzone: fa
Freed heap region: fd
Stack left redzone: f1
Stack mid redzone: f2
Stack right redzone: f3
Stack after return: f5
Stack use after scope: f8
Global redzone: f9
Global init order: f6
Poisoned by user:f7
Container overflow: fc
Array cookie:ac
Intra object redzone:bb
ASan internal: fe
Left alloca redzone: ca
Right alloca redzone:cb
Shadow gap: cc
==3817476==ABORTING
Thanks
To manage notifications about this bug go to:
https://bugs.launchpad.net/libcaca/+bug/1925468/+subscriptions
--
M
[Touch-packages] [Bug 1925467] Re: stack-buffer-overflow of text.c in function _import_ansi
** Changed in: libcaca
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libcaca in Ubuntu.
https://bugs.launchpad.net/bugs/1925467
Title:
stack-buffer-overflow of text.c in function _import_ansi
Status in libcaca:
Fix Released
Status in libcaca package in Ubuntu:
Triaged
Bug description:
Hello ubuntu security team
issues: https://github.com/cacalabs/libcaca/issues/55
System info：
Ubuntu 20.04 : clang 10.0.0 , gcc 9.3.0
Fedora 33: clang 11.0.0 , gcc 10.2.1
libcaca version e4968ba
Verification steps：
1.Get the source code of libcaca
2.Compile the libcaca.so library
$ cd libcaca
$ ./bootstrap
$ ./configure
$ make
or
$ cd libcaca
$ ./bootstrap
$ ../configure CC="clang -O2 -fno-omit-frame-pointer -g
-fsanitize=address,fuzzer-no-link -fsanitize-coverage=bb" CXX="clang++ -O2
-fno-omit-frame-pointer -g -fsanitize=address,fuzzer-no-link
-fsanitize-coverage=bb"
$ make
3.Create the poc_ansi.cc && build
#include "config.h"
#include "caca.h"
//#include "common-image.h"
#include
#include
#include
#include
#include
#include
using namespace std;
void crash(const uint8_t *Data, size_t Size) {
if(Size<8) return ;
size_t len=0;
caca_canvas_t *cv;
cv = caca_create_canvas(0,0);
caca_create_frame(cv,0);
caca_set_frame(cv,0);
caca_import_canvas_from_memory(cv,Data,Size,"ansi");
caca_free_canvas(cv);
cv=NULL;
}
int main(int args,char* argv[]){
size_t len = 0;
unsigned char buffer[] =
{0x20,0x4a,0x0c,0x0a,0x20,0x0a,0x20,0x0c,0xc,0xc};
len = sizeof(buffer)/sizeof(unsigned char);
printf("%d\n",sizeof(buffer)/sizeof(unsigned char));
crash((const uint8_t*)buffer,len);
return 0;
}
4.compile poc_ansi.cc
clang++ -g poc_ansi.cc -O2 -fno-omit-frame-pointer -fsanitize=address
-I./caca/ -lcaca -L./caca/.libs/ -Wl,-rpath,./caca/.libs/ -o poc_ansi
5.Run poc_ansi
asan info:
=
==3763372==ERROR: AddressSanitizer: stack-buffer-overflow on address
0x7ffda0164bea at pc 0x7f098d82c310 bp 0x7ffda01647b0 sp 0x7ffda01647a8
READ of size 1 at 0x7ffda0164bea thread T0
#0 0x7f098d82c30f in _import_ansi
/home/hh/Downloads/libcaca/caca/codec/text.c:391:38
#1 0x4c6c72 in crash(unsigned char const*, unsigned long)
/home/hh/Downloads/libcaca/poc_bin.cc:21:3
#2 0x4c6c72 in main /home/hh/Downloads/libcaca/poc_bin.cc:34:9
#3 0x7f098d2780b2 in __libc_start_main
/build/glibc-eX1tMB/glibc-2.31/csu/../csu/libc-start.c:308:16
#4 0x41c38d in _start (/home/hh/Downloads/libcaca/poc_mbay+0x41c38d)
Address 0x7ffda0164bea is located in stack of thread T0 at offset 42 in frame
#0 0x4c6b9f in main /home/hh/Downloads/libcaca/poc_bin.cc:28
This frame has 1 object(s):
[32, 42) 'buffer' (line 31) <== Memory access at offset 42 overflows this
variable
HINT: this may be a false positive if your program uses some custom stack
unwind mechanism, swapcontext or vfork
(longjmp and C++ exceptions *are* supported)
SUMMARY: AddressSanitizer: stack-buffer-overflow
/home/hh/Downloads/libcaca/caca/codec/text.c:391:38 in _import_ansi
Shadow bytes around the buggy address:
0x100034024920: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8
0x100034024930: f8 f8 f8 f8 f8 f8 f8 f8 f8 f2 f2 f2 f2 f2 f2 f2
0x100034024940: f2 f2 f8 f2 f2 f2 f8 f3 f3 f3 f3 f3 00 00 00 00
0x100034024950: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x100034024960: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
=>0x100034024970: 00 00 00 00 00 00 00 00 f1 f1 f1 f1 00[02]f3 f3
0x100034024980: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x100034024990: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x1000340249a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x1000340249b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x1000340249c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Shadow byte legend (one shadow byte represents 8 application bytes):
Addressable: 00
Partially addressable: 01 02 03 04 05 06 07
Heap left redzone: fa
Freed heap region: fd
Stack left redzone: f1
Stack mid redzone: f2
Stack right redzone: f3
Stack after return: f5
Stack use after scope: f8
Global redzone: f9
Global init order: f6
Poisoned by user:f7
Container overflow: fc
Array cookie:ac
Intra object redzone:bb
ASan internal: fe
Left alloca redzone: ca
Right alloca redzone:cb
Shadow gap: cc
==3763372==ABORTING
Thanks
To manage notifications about this bug go to:
https://bugs.launchpad.net/libcaca/+bug/1925467/+subscriptions
--
Mailing list: h
[Touch-packages] [Bug 1946847] Re: Merge bridge-utils from Debian unstable for 22.04
** Description changed: - Upstream: tbd + Upstream: 1.7.1 Debian: 1.7-1 Ubuntu: 1.7-1ubuntu2 Debian typically updates bridge-utils every 4 months on average, but it was last updated 21.02 and looks overdue. Check back in on this monthly. - - No release expected for bridge-utils this cycle ### New Debian Changes ### bridge-utils (1.7-1) unstable; urgency=medium * New upstream version. Only messages related changes and compilation fixes. * Remove preserve_gcc_flags patch (in upstream now). * Bump standards, no change needed. * Clarify portprio and fix example. * Update upstream url. * Fix NEWS versioning of last entry :-? -- Santiago Garcia Mantinan Wed, 24 Feb 2021 12:34:03 +0100 bridge-utils (1.6-6) unstable; urgency=medium * Fix IPv6 address getting assigned on hotplug devices. Closes: #980752. * Fix waiting so that DAD works again. Closes: #982943. * Move mac setting before brctl addif to ensure mac setting. Closes: #980856. * Update documentation and add examples. Closes: #765098. * Update manpages. Closes: #981253. * Add a note on MTU settings. Closes: #292088. * Hook also on down to recreate the bridge so that multiple stanzas work Ok on ifdown. Closes: #319832. -- Santiago Garcia Mantinan Tue, 16 Feb 2021 13:29:04 +0100 bridge-utils (1.6-5) unstable; urgency=low * Overload bridge_hw to allow do specify an interface as well as the MAC address. Closes: #966244. * Change man page for bridge-utils-interfaces and news fileto document this overloading. -- Santiago Garcia Mantinan Fri, 22 Jan 2021 11:08:47 +0100 bridge-utils (1.6-4) unstable; urgency=low * Add en* to the device regex so that all catches them. Closes: #966319. * Document MAC address changes on news. Closes: #980505. -- Santiago Garcia Mantinan Thu, 21 Jan 2021 10:51:31 +0100 bridge-utils (1.6-3) unstable; urgency=medium * Support VLAN aware setups where we need vlan filtering. Thanks Benedikt Spranger for the patch. Closes: #950879. * Clarify on manual page that stp will get IPv6 lost. Closes: #736336. * Add a 1 second sleep if hw address needs to be changed. Closes: #945466. -- Santiago Garcia Mantinan Thu, 30 Apr 2020 10:06:38 +0200 bridge-utils (1.6-2) unstable; urgency=medium * Bump Standards-Version. * Preserve gcc flags set when building the lib. -- Santiago Garcia Mantinan Mon, 28 Jan 2019 00:25:14 +0100 bridge-utils (1.6-1) unstable; urgency=low * New upstream version. * Change default back to not hotplug. Closes: #892277. * Allow mtu to be set on the bridge by propagating it to the bridged interfaces. Closes: #661711. * Remove kernel headers from the package. -- Santiago Garcia Mantinan Tue, 15 Jan 2019 13:18:33 +0100 bridge-utils (1.5-16) unstable; urgency=medium * Don't set dev globally at bridge-utils.sh. Closes: #873086. -- Santiago Garcia Mantinan Sun, 08 Apr 2018 23:06:30 +0200 bridge-utils (1.5-15) unstable; urgency=medium * Fix substrings on interfaces. Closes: #873087. * Make it lintian clean sticking to 1.0 source format for now. No time to properly comment all the patches right now. -- Santiago Garcia Mantinan Fri, 02 Mar 2018 22:08:20 +0100 bridge-utils (1.5-14) unstable; urgency=low * Fix a problem with some vlan interfaces not being created. -- Santiago Garcia Mantinan Mon, 26 Jun 2017 17:48:37 +0200 bridge-utils (1.5-13) unstable; urgency=low * Fix a hardcoded interface name on bridge-utils.sh. Closes: #854841. -- Santiago Garcia Mantinan Sat, 11 Feb 2017 00:16:45 +0100 bridge-utils (1.5-12) unstable; urgency=medium * Add vlan support so that old setups using vlans as ports don't break. -- Santiago Garcia Mantinan Sun, 22 Jan 2017 00:23:50 +0100 ### Old Ubuntu Delta ### bridge-utils (1.7-1ubuntu2) impish; urgency=medium * No-change rebuild to build packages with zstd compression. -- Matthias Klose Thu, 07 Oct 2021 12:09:41 +0200 bridge-utils (1.7-1ubuntu1) impish; urgency=low * Merge from Debian unstable. Remaining changes: - Don't call ifup from bridge-network-interface, instead just call brctl and let udev/upstart bring the interface up. - debian/ifupdown.sh: Handle bridge params which use port and value - debian/bridge-utils-interface.5: + Update max, default value for path cost + Update unsettable gcint value for newer kernels -- Steve Langasek Wed, 17 Mar 2021 12:32:22 -0700 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bridge-utils in Ubuntu. https://bugs.launchpad.net/bugs/1946847 Title: Merge bridge-utils from Debian unstable for
[Touch-packages] [Bug 1931725] Re: initramfs-tools & kernel: use zstd as the default compression method
How to revert to old compression method for initramfs? Generating image with zstd is extremely slow and takes long time on slow CPU. -- 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/1931725 Title: initramfs-tools & kernel: use zstd as the default compression method Status in Ubuntu on IBM z Systems: Fix Released Status in initramfs-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oracle package in Ubuntu: Fix Released Bug description: Turns out that loading is always the slow part in loading initramfs into memory and decompressing it since decompression is always the final 10-20% or so of the task. It therefore makes sense to use a good compressor that shrinks the initramfs as much as possible with little decompression overhead. Benchmarking zstd vs lz4 shows that while zstd can be ~5x slower in decompression, the image size is much smaller with zstd than lz4, and since ~80-90% of the boot time is loading the image it makes sense to use zstd. Attached is a libreoffice spread sheet showing typical load and decompression times for a fairly standard 3.4 GHZ intel box with data for load times for a 5400 RPM, 7200 RPM and SATA SSD drives. The conclusions from the test results (attached) show: 1. Loading time is always significantly slower than decompression time. 2. ZSTD is 5x slower than LZ4 in decompression speed but produces far better compressed images 3. Given that loading time is the major factor in loading + decompression, ZSTD is best for kernel and initramfs boot timings. (Also refer to https://kernel.ubuntu.com/~cking/boot-speed- eoan-5.3/kernel-compression-method.txt for some raw data on drive load speeds for the same UEFI box I did a couple of years ago). amd64 supports zstd, but s390x does not. Will use this bug to enable zstd support on s390x. Upstream submitted patch https://lore.kernel.org/linux-s390/20210615114150.325080-1-dimitri.led...@canonical.com/T/#u To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1931725/+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 1946898] Re: Merge rsync from Debian unstable for 22.04
** Description changed: - Scheduled-For: 23.01 - Upstream: tbd - Debian: 3.2.3-8 + Upstream: 3.2.3 + Debian: 3.2.3-8 Ubuntu: 3.2.3-4ubuntu1 - Debian does new releases regularly, so it's likely there will be newer versions available before FF that we can pick up if this merge is done later in the cycle. - ### New Debian Changes ### rsync (3.2.3-8) unstable; urgency=medium - * debian/patches: - - manpage_upstream_fixes.patch: Import multiple upstream patches to fix - manpage. - - copy-devices.diff: Add missing manpage changes to patch - - CVE-2020-14387.patch: Add Forwarded DEP3 field to point to upstream patch - - fix_delay_updates.patch: Refresh patch - - fix_mkpath.patch: New upstream patch to fix an edge case on --mkpath - - fix_rsync-ssl_RSYNC_SSL_CERT_feature.patch: New upstream patch - - fix_sparse_inplace.patch: New upstream patch to fix --sparse + --inplace - options - - update_rrsync_options.patch: New upstream patch to update rrsync options + * debian/patches: + - manpage_upstream_fixes.patch: Import multiple upstream patches to fix + manpage. + - copy-devices.diff: Add missing manpage changes to patch + - CVE-2020-14387.patch: Add Forwarded DEP3 field to point to upstream patch + - fix_delay_updates.patch: Refresh patch + - fix_mkpath.patch: New upstream patch to fix an edge case on --mkpath + - fix_rsync-ssl_RSYNC_SSL_CERT_feature.patch: New upstream patch + - fix_sparse_inplace.patch: New upstream patch to fix --sparse + --inplace + options + - update_rrsync_options.patch: New upstream patch to update rrsync options - -- Samuel Henrique Sat, 25 Sep 2021 17:38:16 + -- Samuel Henrique Sat, 25 Sep 2021 17:38:16 +0100 rsync (3.2.3-7) unstable; urgency=medium - * Bump Standards-Version to 4.6.0 - * d/p/workaround_glibc_lchmod_regression.patch: New patch from upstream - (closes: #994543) - * debian/rsync.NEWS: Fix typo in last entry + * Bump Standards-Version to 4.6.0 + * d/p/workaround_glibc_lchmod_regression.patch: New patch from upstream + (closes: #994543) + * debian/rsync.NEWS: Fix typo in last entry - -- Samuel Henrique Sat, 18 Sep 2021 00:25:13 + -- Samuel Henrique Sat, 18 Sep 2021 00:25:13 +0100 rsync (3.2.3-6) unstable; urgency=medium - * d/t/upstream-tests: Suppress stderr warnings from the build process + * d/t/upstream-tests: Suppress stderr warnings from the build process - -- Samuel Henrique Sun, 12 Sep 2021 18:22:57 + -- Samuel Henrique Sun, 12 Sep 2021 18:22:57 +0100 rsync (3.2.3-5) unstable; urgency=medium - [ 刘建强 ] - * Set the rsync.service not to start automatically after installation, - the rsyncd.conf configuration file needs to be configured by the user - before the service can start + [ 刘建强 ] + * Set the rsync.service not to start automatically after installation, + the rsyncd.conf configuration file needs to be configured by the user + before the service can start - [ Samuel Henrique ] - * Re-add upstream patch for --copy-devices, the --write-devices option is - not fully equivalent (closes: #992215) - * d/rsync.docs: Add NEWS.md file (previously named NEWS) (closes: #993697) - * d/p/fix_delay_updates.patch: New patch from upstream (closes: #992231) + [ Samuel Henrique ] + * Re-add upstream patch for --copy-devices, the --write-devices option is + not fully equivalent (closes: #992215) + * d/rsync.docs: Add NEWS.md file (previously named NEWS) (closes: #993697) + * d/p/fix_delay_updates.patch: New patch from upstream (closes: #992231) - -- Samuel Henrique Sun, 12 Sep 2021 17:25:37 + -- Samuel Henrique Sun, 12 Sep 2021 17:25:37 +0100 rsync (3.2.3-4) unstable; urgency=medium - [ Helmut Grohne ] - * d/p/fix_ftcbfs_configure.patch: New patch to fix FTCBFS (closes: #971285) + [ Helmut Grohne ] + * d/p/fix_ftcbfs_configure.patch: New patch to fix FTCBFS (closes: #971285) - [ Samuel Henrique ] - * Bump Standards-Version to 4.5.1 + [ Samuel Henrique ] + * Bump Standards-Version to 4.5.1 - -- Samuel Henrique Tue, 02 Feb 2021 23:08:54 + -- Samuel Henrique Tue, 02 Feb 2021 23:08:54 + rsync (3.2.3-3) unstable; urgency=high - * d/p/CVE-2020-14387.patch: New patch to fix an openssl related CVE - (closes: #969530, CVE-2020-14387) + * d/p/CVE-2020-14387.patch: New patch to fix an openssl related CVE + (closes: #969530, CVE-2020-14387) - -- Samuel Henrique Sat, 19 Dec 2020 12:48:33 + -- Samuel Henrique Sat, 19 Dec 2020 12:48:33 + rsync (3.2.3-2) unstable; urgency=medium - [ Sergio Durigan Junior ] - * Make the autopkgtests cross-friendly. - Thanks to Steve Langasek + [ Sergio Durigan Junior ] + * Make the autopkgtests cross-friendly. + Thanks to Steve Langasek - -- Samuel Henrique Wed, 26 Aug 2020 21:23:57 + -- Samue
[Touch-packages] [Bug 1902022] Re: package dh-python 4.20191017ubuntu7 failed to install/upgrade: installed dh-python package pre-removal script subprocess returned error exit status 127
Hrm, not sure how that happened, the prerm script says: if which py3clean >/dev/null 2>&1; then py3clean -p dh-python else dpkg -L dh-python | perl -ne 's,/([^/]*)\.py$,/__pycache__/\1.*, or next; unlink $_ or die $! foreach glob($_)' find /usr/lib/python3/dist-packages/ -type d -name __pycache__ -empty -print0 | xargs --null --no-run-if-empty rmdir fi So, if py3clean isn't on PATH it should have used the second branch. Maybe /usr/bin/python3 was broken? ** Changed in: dh-python (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/1902022 Title: package dh-python 4.20191017ubuntu7 failed to install/upgrade: installed dh-python package pre-removal script subprocess returned error exit status 127 Status in dh-python package in Ubuntu: Incomplete Bug description: This error occured after my attempts to correct the inability to import pygame into PyCharm-Environment (it works in Python2.7 and Python3.6 and 3.8). A package distutils.utils is requested, which I cannot find anywhere and should be superseeded by setuptools. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: dh-python 4.20191017ubuntu7 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Oct 28 20:55:00 2020 DuplicateSignature: package:dh-python:4.20191017ubuntu7 Removing dh-python (4.20191017ubuntu7) ... /var/lib/dpkg/info/dh-python.prerm: 7: py3clean: not found dpkg: error processing package dh-python (--remove): installed dh-python package pre-removal script subprocess returned error exit status 127 ErrorMessage: installed dh-python package pre-removal script subprocess returned error exit status 127 InstallationDate: Installed on 2020-04-07 (205 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all Python3Details: /usr/bin/python3, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python3.8, Python 3.8.5, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: dh-python Title: package dh-python 4.20191017ubuntu7 failed to install/upgrade: installed dh-python package pre-removal script subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/1902022/+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 1863195] Re: py3compile should not emit python runtime warnings during dist-upgrade
> Or maybe set PYTHONWARNINGS=ignore in the environment during the upgrade? That sounds more like it. Wouldn't we want to see these in other situations? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/1863195 Title: py3compile should not emit python runtime warnings during dist-upgrade Status in dh-python package in Ubuntu: Confirmed Status in dh-python source package in Focal: Confirmed Bug description: py3compile should compile without emitting python runtime warnings on dist-upgrade from bionic to focal a tonne of RuntimeWarnings are emitted during apt upgrade, due to buffering=1 being deprecated. We will not fix all the packages, and these warnings are not helpful to the users, as they cannot and shouldn't need to do anything about them, as they come from packages that are maintained by the distro. Imho py3compile should execute python interpreter with -W ignore Or maybe set PYTHONWARNINGS=ignore in the environment during the upgrade? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/1863195/+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 1648820] Re: package dh-python 1.20140128-1ubuntu8.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Sounds like python3.4 was uninstalled. ** Changed in: dh-python (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/1648820 Title: package dh-python 1.20140128-1ubuntu8.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in dh-python package in Ubuntu: Incomplete Bug description: I have wrongly delete the dependence python2.7, and then the softwarecenter dose not work. Any of the software could not be installed. How should i re-install the software. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: dh-python 1.20140128-1ubuntu8.2 ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 Date: Fri Dec 9 21:37:56 2016 Dependencies: DuplicateSignature: package:dh-python:1.20140128-1ubuntu8.2:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-12-25 (350 days ago) InstallationMedia: Ubuntu-Kylin 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150806) PackageArchitecture: all RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.11 SourcePackage: dh-python Title: package dh-python 1.20140128-1ubuntu8.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/1648820/+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 1758142] Re: Recursive follow of symlinks
Please can you describe how to reproduce this bug?
** Changed in: dh-python (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dh-python in Ubuntu.
https://bugs.launchpad.net/bugs/1758142
Title:
Recursive follow of symlinks
Status in dh-python package in Ubuntu:
Incomplete
Bug description:
This was not a problem with the previous dh-python, this is what we see with
the version reported here:
E: pybuild pybuild:330: test: plugin distutils failed with:
[('/<>/snapcraft-2.40+18.04.2/tests/integration/snaps/old-part-src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src',
'/<>/snapcraft-2.40+18.04.2/.pybuild/cpython3_3.6/build/tests/integration/snaps/old-part-src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src',
"[Errno 40] Too many levels of symbolic links:
'/<>/snapcraft-2.40+18.04.2/tests/integration/snaps/old-part-src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src/parts/part-name/src'")]
dh_auto_test: pybuild --test -i python{version} -p 3.6 returned exit code 13
Looks like there is new copy logic in
https://launchpadlibrarian.net/361622412/dh-
python_2.20170125_3.20180318.diff.gz (not mentioned on the changelog)
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: dh-python 3.20180318
ProcVersionSignature: User Name 4.15.0-10.11-generic 4.15.2
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
Date: Thu Mar 22 19:29:00 2018
PackageArchitecture: all
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=C.UTF-8
SHELL=/bin/bash
SourcePackage: dh-python
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/1758142/+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 1899288] Re: Python3 can't co-exist with Oracle's VirtualBox on 20.10
This is resolved in dh-python 5.20211016. ** Changed in: dh-python (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/1899288 Title: Python3 can't co-exist with Oracle's VirtualBox on 20.10 Status in dh-python package in Ubuntu: Fix Released Status in what-is-python package in Ubuntu: Incomplete Bug description: Sorry I couldn't file this bug against the correct packages. The form told me there are no such packages as python-is-python3 and dh-python in Ubuntu... Release: Groovy Gorilla (Ubuntu 20.10). Package versions: python-is-python3 3.8.2-4 dh-python 4.20200925 The release of Ubuntu 20.10 is less than two weeks out, so I'd like to draw attention to a problem I've run into. It seems that 20.10 defaults to python3 and wants to install python-is-python3, which pulls in the latest version of dh-python, which in turn can't co-exist with Oracle's Virtualbox-6.1 and wants to uninstall it. I don't mind having _both_ python2 (apparently a requirement of VirtualBox) and python3 installed. But as of right now I can have either python-is-python3, and not be able to do a complete upgrade since virtualbox-6.1 will be uninstalled, or python-is-python2, in which case I cripple 20.10's python3 install, since I won't get dh- python and python-six. Ia there something the python packagers do about this? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/1899288/+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 1877626] Re: new upstream version
** Changed in: dh-python (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/1877626 Title: new upstream version Status in dh-python package in Ubuntu: Fix Released Bug description: Debian's dh-python is now in version 4.20200315, which fixed a number of bugs, as can be seen on its changelog[1]. Please sync with the latest version. [1] https://metadata.ftp-master.debian.org/changelogs//main/d/dh- python/dh-python_4.20200315_changelog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/1877626/+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 1608030] Re: package dh-python 2.20151103ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuratio
I can't tell what happened from this bug, but let's assume it was resolved. ** Changed in: dh-python (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/1608030 Title: package dh-python 2.20151103ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in dh-python package in Ubuntu: Incomplete Bug description: after fresh install, I'm having problems to install updates. First I tried using Software Center, but updates couldn't be installed (no error was shown, but updates remained uninstall). After rebooting, I tried upgrading from console ($ sudo apt-get update; sudo apt-get upgrade), and then I got dh-python error. ... Removing obsolete conffile /etc/ld.so.conf.d/snappy.conf ... Setting up thermald (1.5-2ubuntu2) ... Setting up upower (0.99.4-2ubuntu0.3) ... Setting up xinit (1.3.4-3ubuntu0.1) ... Setting up libruby2.3:amd64 (2.3.1-2~16.04) ... Setting up ruby2.3 (2.3.1-2~16.04) ... Processing triggers for libc-bin (2.23-0ubuntu3) ... Errors were encountered while processing: dh-python E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: dh-python 2.20151103ubuntu1.1 ProcVersionSignature: Ubuntu 4.4.0-31.50-lowlatency 4.4.13 Uname: Linux 4.4.0-31-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Sat Jul 30 10:59:32 2016 Dependencies: ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2016-07-24 (5 days ago) InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: dh-python Title: package dh-python 2.20151103ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/1608030/+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 1940405] Re: Sync dh-python 4.20201102+nmu1 (universe) from Debian unstable (main)
** Changed in: dh-python (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/1940405 Title: Sync dh-python 4.20201102+nmu1 (universe) from Debian unstable (main) Status in dh-python package in Ubuntu: Fix Released Bug description: Please sync dh-python 4.20201102+nmu1 (universe) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * Disable the nosetests autopkg test. Unmaintained. * Disable the nosetests autopkg test. Unmaintained. * Fix DocTest. -> Those have been fixed by the NMU * Don't run test t301. -> I don't really understand the rationale for disabling this test. While the test case specifies a python version << 3.9 which wouldn't make it fit for current versions of Ubuntu, I believe what is being tested is the ability to specify the version bounds properly, which shouldn't be affected by the default version on the system. Changelog entries since current impish version 4.20201102ubuntu4: dh-python (4.20201102+nmu1) unstable; urgency=medium * Non-maintainer upload * Don't fail tests just because the default python gets hardcoded (Closes: #975536) -- Paul Gevers Sat, 27 Feb 2021 19:51:37 +0100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/1940405/+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 1946286] Re: Merge openssh from Debian unstable for 22.04
Thanks Colin, we'll leave it to you and close this tracking bug out.
** Changed in: openssh (Ubuntu)
Status: New => Invalid
--
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/1946286
Title:
Merge openssh from Debian unstable for 22.04
Status in openssh package in Ubuntu:
Invalid
Bug description:
Scheduled-For: 22.12
Upstream: tbd
Debian: 1:8.4p1-6
Ubuntu: 1:8.4p1-6ubuntu2
Debian typically updates openssh every 1 months on average, but it was
last updated 21.08 and looks overdue. Check back in on this monthly.
### New Debian Changes ###
openssh
openssh (1:8.4p1-6) unstable; urgency=medium
[ Colin Watson ]
* Rename ssh group to _ssh (closes: #990456). It's only used by
ssh-agent.
* debian/tests/regress: Don't fail cleanup if haveged isn't running.
* Backport from upstream:
- Add includes.h to compat tests (closes: #992134, LP: #1939751).
* Use 'command -v' in maintainer scripts rather than 'which'.
[ Athos Ribeiro ]
* d/systemd/ssh@.service: preserve the systemd managed runtime directory to
ensure parallel processes will not disrupt one another when halting
(LP: #1905285) (closes: #934663)
-- Colin Watson Thu, 19 Aug 2021 11:04:01
+0100
openssh (1:8.4p1-5) unstable; urgency=high
* CVE-2021-28041: Fix double free in ssh-agent(1) (closes: #984940).
-- Colin Watson Sat, 13 Mar 2021 09:59:40
+
openssh (1:8.4p1-4) unstable; urgency=medium
* Avoid using libmd's even if it's installed (closes:
#982705).
-- Colin Watson Mon, 15 Feb 2021 10:25:17
+
openssh (1:8.4p1-3) unstable; urgency=medium
* Backport from upstream:
- Fix `EOF: command not found` error in ssh-copy-id (closes: #975540).
-- Colin Watson Wed, 02 Dec 2020 10:32:23
+
openssh (1:8.4p1-2) unstable; urgency=medium
* Revert incorrect upstream patch that claimed to fix the seccomp sandbox
on x32 but in fact broke it instead.
-- Colin Watson Mon, 26 Oct 2020 17:41:13
+
openssh (1:8.4p1-1) unstable; urgency=medium
* New upstream release (https://www.openssh.com/txt/release-8.4):
- [SECURITY] ssh-agent(1): restrict ssh-agent from signing web
challenges for FIDO/U2F keys.
- [SECURITY] ssh-keygen(1): Enable FIDO 2.1 credProtect extension when
generating a FIDO resident key.
- ssh-keygen(1): the format of the attestation information optionally
recorded when a FIDO key is generated has changed. It now includes the
authenticator data needed to validate attestation signatures.
- The API between OpenSSH and the FIDO token middleware has changed and
the SSH_SK_VERSION_MAJOR version has been incremented as a result.
Third-party middleware libraries must support the current API version
(7) to work with OpenSSH 8.4.
- ssh(1), ssh-keygen(1): support for FIDO keys that require a PIN for
each use. These keys may be generated using ssh-keygen using a new
'verify-required' option. When a PIN-required key is used, the user
will be prompted for a PIN to complete the signature operation.
- sshd(8): authorized_keys now supports a new 'verify-required' option
to require FIDO signatures assert that the token verified that the
user was present before making the signature. The FIDO protocol
supports multiple methods for user-verification, but currently OpenSSH
only supports PIN verification.
- sshd(8), ssh-keygen(1): add support for verifying FIDO webauthn
signatures. Webauthn is a standard for using FIDO keys in web
browsers. These signatures are a slightly different format to plain
FIDO signatures and thus require explicit support.
- ssh(1): allow some keywords to expand shell-style ${ENV} environment
variables. The supported keywords are CertificateFile, ControlPath,
IdentityAgent and IdentityFile, plus LocalForward and RemoteForward
when used for Unix domain socket paths.
- ssh(1), ssh-agent(1): allow some additional control over the use of
ssh-askpass via a new $SSH_ASKPASS_REQUIRE environment variable,
including forcibly enabling and disabling its use (closes: #368657).
- ssh(1): allow ssh_config(5)'s AddKeysToAgent keyword accept a time
limit for keys in addition to its current flag options. Time-limited
keys will automatically be removed from ssh-agent after their expiry
time has passed.
- scp(1), sftp(1): allow the -A flag to explicitly enable agent
forwarding in scp and sftp. The default remains to not forward an
agent, even when ssh_config enables it.
- ssh(1): add a '%k' TOKEN that expands to the effective HostKey of the
destination. This allows, e.g.,
[Touch-packages] [Bug 1930188] Re: Acer Aspire 5 sound driver issues
This bug was fixed in the package alsa-ucm-conf - 1.2.2-1ubuntu0.11 --- alsa-ucm-conf (1.2.2-1ubuntu0.11) focal; urgency=medium * d/p/0033-HDA-Intel-add-Boost-volume-control-for-Headset-Mic.patch Add Mic Boost in the HDA Intel ucm, after this change, when users adjust input volume, the Mic Boost could be adjusted as well as Capture Volume. (LP: #1930188) -- Hui Wang Tue, 14 Sep 2021 15:11:12 +0800 -- 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/1930188 Title: Acer Aspire 5 sound driver issues Status in alsa-ucm-conf package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Released Status in linux source package in Focal: Fix Released Status in pulseaudio source package in Focal: Fix Released Status in alsa-ucm-conf source package in Hirsute: Fix Released Status in linux source package in Hirsute: Fix Released Status in pulseaudio source package in Hirsute: Fix Released Status in alsa-ucm-conf source package in Impish: Fix Committed Status in linux source package in Impish: Fix Released Status in pulseaudio source package in Impish: Fix Released Bug description: SRU Justification for alsa-ucm-conf: [Impact] On the machines with the sof audio driver, users could adjust the input volume from UI, but this only adjusts the "Capture Volume", the "Mic Boost" can't be changed, if "Mic Boost" is 0, even we adjust the "Capture Volume" to max, the recorded volume is still very low. [Fix] Backport a upstream patch, the patch adds the "Mic Boost" into the ucm [Test] plug a headset, make sure the headset-mic is the active input device, adjust the input volume to %20, open a terminal and run alsamixer, check the "Capture Volume" and "Mic Boost" value, then adjust the input volume to 80%, check those values and we could see both values are changed. [Where problems could occur] This patch could make the parse of input volume control fail, then the input volume can't be changed anymore when users adjust the volume from UI. But this possibility is very low, I tested this patch on many lenovo and dell machines with sof audio driver, all worked well. SRU Justification for pulseaudio: [Impact] On the machines with the sof audio driver, after booting up, the active output device is speaker by default, we adjust the output volume to 100%, then we plug a headphone, and adjust the output volume from 100% to 20%, now in theory, the speaker's volume is 100%, the headphone's volume is 20%. We plugout the headphone, the active output device becomes speaker and we expect the volume changes to 100%, but the output volume for speaker is 20%. [Fix] Backport a upstream patch, this patch is already in the pulseaudio-15.0, so impish already has this fix. Only hirsute and focal need to backport this patch. [Test] adjust speaker's volume to 80%, then plug headphone and adjust headphone's volume to 20%, unplug the headphone, the speaker's volume becomes to 80%, plug the headphone, the headphone's volume becomes to 20%. [Where problems could occur] The patch writes the output volume to hardware immediately when switching output device on the machines with sof audio driver, this could introduce pop noise when changing the output device, but this possibility is very low, I tested the patch on many lenovo and dell machines with sof audio driver, all worked as expected and have no pop noise when switching output device. The patch was merged to ubuntu 5.13.0 and 5.11.0 generic kernels with stable update already, but it is not merged to ubuntu 5.4.0 kernel yet, so I sent this SRU for the focal kernel. [Impact] Users plug headphone and Mic to the audio jacks, but the system can't detect them, and couldn't output sound through headphone and record sound through Mic. [Fix] Backport a upstream patch, this will set the Mic to auto-detection mode and set the headphone to left location. [Test] Plug a headset to the headset audio jack, both headphone and mic could be detected. And output the sound to headphone, could hear the sound, record the sound through Mic, the sound could be recorded. [Where problems could occur] The patch is specific to Acer Aspire 5 machine, if it could introduce regression, it will make the audio like internal mic and internal spk stop working. But this possibility is very low. Hello, There seems to be lots of issues in sound driver for Acer Aspire A515-56-57XR with ALC255. I will list all of them below and what I have tried so far.
[Touch-packages] [Bug 1930188] Re: Acer Aspire 5 sound driver issues
This bug was fixed in the package pulseaudio - 1:13.99.1-1ubuntu3.12 --- pulseaudio (1:13.99.1-1ubuntu3.12) focal; urgency=medium * d/p/0001-alsa-sink-source-set-volume-to-hw-immediately-if-ucm.patch Fix the output volume issue for machines with sof audio driver, if a machine uses sof audio driver, the headphone and speaker will share the output volume from UI, this patch will fix this issue, after applying this patch, the speaker and headphone will have independent volume. (LP: #1930188) -- Hui Wang Mon, 13 Sep 2021 12:11:14 +0800 ** Changed in: pulseaudio (Ubuntu Focal) Status: Fix Committed => Fix Released ** Changed in: alsa-ucm-conf (Ubuntu Focal) Status: Fix Committed => Fix Released -- 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/1930188 Title: Acer Aspire 5 sound driver issues Status in alsa-ucm-conf package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Released Status in linux source package in Focal: Fix Released Status in pulseaudio source package in Focal: Fix Released Status in alsa-ucm-conf source package in Hirsute: Fix Released Status in linux source package in Hirsute: Fix Released Status in pulseaudio source package in Hirsute: Fix Released Status in alsa-ucm-conf source package in Impish: Fix Committed Status in linux source package in Impish: Fix Released Status in pulseaudio source package in Impish: Fix Released Bug description: SRU Justification for alsa-ucm-conf: [Impact] On the machines with the sof audio driver, users could adjust the input volume from UI, but this only adjusts the "Capture Volume", the "Mic Boost" can't be changed, if "Mic Boost" is 0, even we adjust the "Capture Volume" to max, the recorded volume is still very low. [Fix] Backport a upstream patch, the patch adds the "Mic Boost" into the ucm [Test] plug a headset, make sure the headset-mic is the active input device, adjust the input volume to %20, open a terminal and run alsamixer, check the "Capture Volume" and "Mic Boost" value, then adjust the input volume to 80%, check those values and we could see both values are changed. [Where problems could occur] This patch could make the parse of input volume control fail, then the input volume can't be changed anymore when users adjust the volume from UI. But this possibility is very low, I tested this patch on many lenovo and dell machines with sof audio driver, all worked well. SRU Justification for pulseaudio: [Impact] On the machines with the sof audio driver, after booting up, the active output device is speaker by default, we adjust the output volume to 100%, then we plug a headphone, and adjust the output volume from 100% to 20%, now in theory, the speaker's volume is 100%, the headphone's volume is 20%. We plugout the headphone, the active output device becomes speaker and we expect the volume changes to 100%, but the output volume for speaker is 20%. [Fix] Backport a upstream patch, this patch is already in the pulseaudio-15.0, so impish already has this fix. Only hirsute and focal need to backport this patch. [Test] adjust speaker's volume to 80%, then plug headphone and adjust headphone's volume to 20%, unplug the headphone, the speaker's volume becomes to 80%, plug the headphone, the headphone's volume becomes to 20%. [Where problems could occur] The patch writes the output volume to hardware immediately when switching output device on the machines with sof audio driver, this could introduce pop noise when changing the output device, but this possibility is very low, I tested the patch on many lenovo and dell machines with sof audio driver, all worked as expected and have no pop noise when switching output device. The patch was merged to ubuntu 5.13.0 and 5.11.0 generic kernels with stable update already, but it is not merged to ubuntu 5.4.0 kernel yet, so I sent this SRU for the focal kernel. [Impact] Users plug headphone and Mic to the audio jacks, but the system can't detect them, and couldn't output sound through headphone and record sound through Mic. [Fix] Backport a upstream patch, this will set the Mic to auto-detection mode and set the headphone to left location. [Test] Plug a headset to the headset audio jack, both headphone and mic could be detected. And output the sound to headphone, could hear the sound, record the sound through Mic, the sound could be recorded. [Where problems could occur] The patch is specific to Acer Aspire 5
[Touch-packages] [Bug 1947769] [NEW] package libgdk-pixbuf-2.0-0:amd64 2.42.6+dfsg-1build2 failed to install/upgrade: triggers looping, abandoned
Public bug reported: After updating to 20.10 this error started to show every 5 min ProblemType: Package DistroRelease: Ubuntu 21.10 Package: libgdk-pixbuf-2.0-0:amd64 2.42.6+dfsg-1build2 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Oct 19 17:04:11 2021 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2021-07-21 (90 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1build1 PythonDetails: /usr/bin/python3.9, Python 3.9.7, python-is-python3, 3.9.2-1 RelatedPackageVersions: dpkg 1.20.9ubuntu2 apt 2.3.9 SourcePackage: gdk-pixbuf Title: package libgdk-pixbuf-2.0-0:amd64 2.42.6+dfsg-1build2 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to impish on 2021-10-19 (0 days ago) ** Affects: gdk-pixbuf (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package impish need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1947769 Title: package libgdk-pixbuf-2.0-0:amd64 2.42.6+dfsg-1build2 failed to install/upgrade: triggers looping, abandoned Status in gdk-pixbuf package in Ubuntu: New Bug description: After updating to 20.10 this error started to show every 5 min ProblemType: Package DistroRelease: Ubuntu 21.10 Package: libgdk-pixbuf-2.0-0:amd64 2.42.6+dfsg-1build2 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Oct 19 17:04:11 2021 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2021-07-21 (90 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1build1 PythonDetails: /usr/bin/python3.9, Python 3.9.7, python-is-python3, 3.9.2-1 RelatedPackageVersions: dpkg 1.20.9ubuntu2 apt 2.3.9 SourcePackage: gdk-pixbuf Title: package libgdk-pixbuf-2.0-0:amd64 2.42.6+dfsg-1build2 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to impish on 2021-10-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1947769/+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 1930188] Re: Acer Aspire 5 sound driver issues
This bug was fixed in the package alsa-ucm-conf - 1.2.4-2ubuntu1.4 --- alsa-ucm-conf (1.2.4-2ubuntu1.4) hirsute; urgency=medium * d/p/0007-HDA-Intel-add-Boost-volume-control-for-Headset-Mic.patch Add Mic Boost in the HDA Intel ucm, after this change, when users adjust input volume, the Mic Boost could be adjusted as well as Capture Volume. (LP: #1930188) -- Hui Wang Tue, 14 Sep 2021 11:08:28 +0800 -- 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/1930188 Title: Acer Aspire 5 sound driver issues Status in alsa-ucm-conf package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Committed Status in linux source package in Focal: Fix Released Status in pulseaudio source package in Focal: Fix Committed Status in alsa-ucm-conf source package in Hirsute: Fix Released Status in linux source package in Hirsute: Fix Released Status in pulseaudio source package in Hirsute: Fix Released Status in alsa-ucm-conf source package in Impish: Fix Committed Status in linux source package in Impish: Fix Released Status in pulseaudio source package in Impish: Fix Released Bug description: SRU Justification for alsa-ucm-conf: [Impact] On the machines with the sof audio driver, users could adjust the input volume from UI, but this only adjusts the "Capture Volume", the "Mic Boost" can't be changed, if "Mic Boost" is 0, even we adjust the "Capture Volume" to max, the recorded volume is still very low. [Fix] Backport a upstream patch, the patch adds the "Mic Boost" into the ucm [Test] plug a headset, make sure the headset-mic is the active input device, adjust the input volume to %20, open a terminal and run alsamixer, check the "Capture Volume" and "Mic Boost" value, then adjust the input volume to 80%, check those values and we could see both values are changed. [Where problems could occur] This patch could make the parse of input volume control fail, then the input volume can't be changed anymore when users adjust the volume from UI. But this possibility is very low, I tested this patch on many lenovo and dell machines with sof audio driver, all worked well. SRU Justification for pulseaudio: [Impact] On the machines with the sof audio driver, after booting up, the active output device is speaker by default, we adjust the output volume to 100%, then we plug a headphone, and adjust the output volume from 100% to 20%, now in theory, the speaker's volume is 100%, the headphone's volume is 20%. We plugout the headphone, the active output device becomes speaker and we expect the volume changes to 100%, but the output volume for speaker is 20%. [Fix] Backport a upstream patch, this patch is already in the pulseaudio-15.0, so impish already has this fix. Only hirsute and focal need to backport this patch. [Test] adjust speaker's volume to 80%, then plug headphone and adjust headphone's volume to 20%, unplug the headphone, the speaker's volume becomes to 80%, plug the headphone, the headphone's volume becomes to 20%. [Where problems could occur] The patch writes the output volume to hardware immediately when switching output device on the machines with sof audio driver, this could introduce pop noise when changing the output device, but this possibility is very low, I tested the patch on many lenovo and dell machines with sof audio driver, all worked as expected and have no pop noise when switching output device. The patch was merged to ubuntu 5.13.0 and 5.11.0 generic kernels with stable update already, but it is not merged to ubuntu 5.4.0 kernel yet, so I sent this SRU for the focal kernel. [Impact] Users plug headphone and Mic to the audio jacks, but the system can't detect them, and couldn't output sound through headphone and record sound through Mic. [Fix] Backport a upstream patch, this will set the Mic to auto-detection mode and set the headphone to left location. [Test] Plug a headset to the headset audio jack, both headphone and mic could be detected. And output the sound to headphone, could hear the sound, record the sound through Mic, the sound could be recorded. [Where problems could occur] The patch is specific to Acer Aspire 5 machine, if it could introduce regression, it will make the audio like internal mic and internal spk stop working. But this possibility is very low. Hello, There seems to be lots of issues in sound driver for Acer Aspire A515-56-57XR with ALC255. I will list all of them below and what I have tried so far.
[Touch-packages] [Bug 1930188] Re: Acer Aspire 5 sound driver issues
This bug was fixed in the package pulseaudio - 1:14.2-1ubuntu1.2 --- pulseaudio (1:14.2-1ubuntu1.2) hirsute; urgency=medium * d/p/0001-alsa-sink-source-set-volume-to-hw-immediately-if-ucm.patch Fix the output volume issue for machines with sof audio driver, if a machine uses sof audio driver, the headphone and speaker will share the output volume from UI, this patch will fix this issue, after applying this patch, the speaker and headphone will have independent volume. (LP: #1930188) -- Hui Wang Mon, 13 Sep 2021 11:28:16 +0800 ** Changed in: pulseaudio (Ubuntu Hirsute) Status: Fix Committed => Fix Released ** Changed in: alsa-ucm-conf (Ubuntu Hirsute) Status: Fix Committed => Fix Released -- 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/1930188 Title: Acer Aspire 5 sound driver issues Status in alsa-ucm-conf package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Committed Status in linux source package in Focal: Fix Released Status in pulseaudio source package in Focal: Fix Committed Status in alsa-ucm-conf source package in Hirsute: Fix Released Status in linux source package in Hirsute: Fix Released Status in pulseaudio source package in Hirsute: Fix Released Status in alsa-ucm-conf source package in Impish: Fix Committed Status in linux source package in Impish: Fix Released Status in pulseaudio source package in Impish: Fix Released Bug description: SRU Justification for alsa-ucm-conf: [Impact] On the machines with the sof audio driver, users could adjust the input volume from UI, but this only adjusts the "Capture Volume", the "Mic Boost" can't be changed, if "Mic Boost" is 0, even we adjust the "Capture Volume" to max, the recorded volume is still very low. [Fix] Backport a upstream patch, the patch adds the "Mic Boost" into the ucm [Test] plug a headset, make sure the headset-mic is the active input device, adjust the input volume to %20, open a terminal and run alsamixer, check the "Capture Volume" and "Mic Boost" value, then adjust the input volume to 80%, check those values and we could see both values are changed. [Where problems could occur] This patch could make the parse of input volume control fail, then the input volume can't be changed anymore when users adjust the volume from UI. But this possibility is very low, I tested this patch on many lenovo and dell machines with sof audio driver, all worked well. SRU Justification for pulseaudio: [Impact] On the machines with the sof audio driver, after booting up, the active output device is speaker by default, we adjust the output volume to 100%, then we plug a headphone, and adjust the output volume from 100% to 20%, now in theory, the speaker's volume is 100%, the headphone's volume is 20%. We plugout the headphone, the active output device becomes speaker and we expect the volume changes to 100%, but the output volume for speaker is 20%. [Fix] Backport a upstream patch, this patch is already in the pulseaudio-15.0, so impish already has this fix. Only hirsute and focal need to backport this patch. [Test] adjust speaker's volume to 80%, then plug headphone and adjust headphone's volume to 20%, unplug the headphone, the speaker's volume becomes to 80%, plug the headphone, the headphone's volume becomes to 20%. [Where problems could occur] The patch writes the output volume to hardware immediately when switching output device on the machines with sof audio driver, this could introduce pop noise when changing the output device, but this possibility is very low, I tested the patch on many lenovo and dell machines with sof audio driver, all worked as expected and have no pop noise when switching output device. The patch was merged to ubuntu 5.13.0 and 5.11.0 generic kernels with stable update already, but it is not merged to ubuntu 5.4.0 kernel yet, so I sent this SRU for the focal kernel. [Impact] Users plug headphone and Mic to the audio jacks, but the system can't detect them, and couldn't output sound through headphone and record sound through Mic. [Fix] Backport a upstream patch, this will set the Mic to auto-detection mode and set the headphone to left location. [Test] Plug a headset to the headset audio jack, both headphone and mic could be detected. And output the sound to headphone, could hear the sound, record the sound through Mic, the sound could be recorded. [Where problems could occur] The patch is specific to Acer Aspire 5
[Touch-packages] [Bug 1930188] Update Released
The verification of the Stable Release Update for pulseaudio has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1930188 Title: Acer Aspire 5 sound driver issues Status in alsa-ucm-conf package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Committed Status in linux source package in Focal: Fix Released Status in pulseaudio source package in Focal: Fix Committed Status in alsa-ucm-conf source package in Hirsute: Fix Released Status in linux source package in Hirsute: Fix Released Status in pulseaudio source package in Hirsute: Fix Released Status in alsa-ucm-conf source package in Impish: Fix Committed Status in linux source package in Impish: Fix Released Status in pulseaudio source package in Impish: Fix Released Bug description: SRU Justification for alsa-ucm-conf: [Impact] On the machines with the sof audio driver, users could adjust the input volume from UI, but this only adjusts the "Capture Volume", the "Mic Boost" can't be changed, if "Mic Boost" is 0, even we adjust the "Capture Volume" to max, the recorded volume is still very low. [Fix] Backport a upstream patch, the patch adds the "Mic Boost" into the ucm [Test] plug a headset, make sure the headset-mic is the active input device, adjust the input volume to %20, open a terminal and run alsamixer, check the "Capture Volume" and "Mic Boost" value, then adjust the input volume to 80%, check those values and we could see both values are changed. [Where problems could occur] This patch could make the parse of input volume control fail, then the input volume can't be changed anymore when users adjust the volume from UI. But this possibility is very low, I tested this patch on many lenovo and dell machines with sof audio driver, all worked well. SRU Justification for pulseaudio: [Impact] On the machines with the sof audio driver, after booting up, the active output device is speaker by default, we adjust the output volume to 100%, then we plug a headphone, and adjust the output volume from 100% to 20%, now in theory, the speaker's volume is 100%, the headphone's volume is 20%. We plugout the headphone, the active output device becomes speaker and we expect the volume changes to 100%, but the output volume for speaker is 20%. [Fix] Backport a upstream patch, this patch is already in the pulseaudio-15.0, so impish already has this fix. Only hirsute and focal need to backport this patch. [Test] adjust speaker's volume to 80%, then plug headphone and adjust headphone's volume to 20%, unplug the headphone, the speaker's volume becomes to 80%, plug the headphone, the headphone's volume becomes to 20%. [Where problems could occur] The patch writes the output volume to hardware immediately when switching output device on the machines with sof audio driver, this could introduce pop noise when changing the output device, but this possibility is very low, I tested the patch on many lenovo and dell machines with sof audio driver, all worked as expected and have no pop noise when switching output device. The patch was merged to ubuntu 5.13.0 and 5.11.0 generic kernels with stable update already, but it is not merged to ubuntu 5.4.0 kernel yet, so I sent this SRU for the focal kernel. [Impact] Users plug headphone and Mic to the audio jacks, but the system can't detect them, and couldn't output sound through headphone and record sound through Mic. [Fix] Backport a upstream patch, this will set the Mic to auto-detection mode and set the headphone to left location. [Test] Plug a headset to the headset audio jack, both headphone and mic could be detected. And output the sound to headphone, could hear the sound, record the sound through Mic, the sound could be recorded. [Where problems could occur] The patch is specific to Acer Aspire 5 machine, if it could introduce regression, it will make the audio like internal mic and internal spk stop working. But this possibility is very low. Hello, There seems to be lots of issues in sound driver for Acer Aspire A515-56-57XR with ALC255. I will list all of them bel
[Touch-packages] [Bug 1946965] Re: python3-defaults: py3versions -i does not list python3.10 when it is installed
Hello Graham, or anyone else affected, Accepted python3-defaults into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/python3-defaults/3.9.4-1ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- impish to verification-done-impish. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-impish. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: python3-defaults (Ubuntu Impish) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-impish -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1946965 Title: python3-defaults: py3versions -i does not list python3.10 when it is installed Status in python3-defaults package in Ubuntu: New Status in python3-defaults source package in Impish: Fix Committed Bug description: Test case: $ sudo apt install python3.9 python3.10 ... $ py3versions -i python3.9 Expected output: $ py3versions -i python3.10 python3.9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1946965/+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 1930188] Re: Acer Aspire 5 sound driver issues
Hello Bijay, or anyone else affected, Accepted alsa-ucm-conf into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/alsa-ucm- conf/1.2.4-2ubuntu5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- impish to verification-done-impish. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-impish. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags removed: verification-done ** Tags added: verification-needed verification-needed-impish -- 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/1930188 Title: Acer Aspire 5 sound driver issues Status in alsa-ucm-conf package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Committed Status in linux source package in Focal: Fix Released Status in pulseaudio source package in Focal: Fix Committed Status in alsa-ucm-conf source package in Hirsute: Fix Committed Status in linux source package in Hirsute: Fix Released Status in pulseaudio source package in Hirsute: Fix Committed Status in alsa-ucm-conf source package in Impish: Fix Committed Status in linux source package in Impish: Fix Released Status in pulseaudio source package in Impish: Fix Released Bug description: SRU Justification for alsa-ucm-conf: [Impact] On the machines with the sof audio driver, users could adjust the input volume from UI, but this only adjusts the "Capture Volume", the "Mic Boost" can't be changed, if "Mic Boost" is 0, even we adjust the "Capture Volume" to max, the recorded volume is still very low. [Fix] Backport a upstream patch, the patch adds the "Mic Boost" into the ucm [Test] plug a headset, make sure the headset-mic is the active input device, adjust the input volume to %20, open a terminal and run alsamixer, check the "Capture Volume" and "Mic Boost" value, then adjust the input volume to 80%, check those values and we could see both values are changed. [Where problems could occur] This patch could make the parse of input volume control fail, then the input volume can't be changed anymore when users adjust the volume from UI. But this possibility is very low, I tested this patch on many lenovo and dell machines with sof audio driver, all worked well. SRU Justification for pulseaudio: [Impact] On the machines with the sof audio driver, after booting up, the active output device is speaker by default, we adjust the output volume to 100%, then we plug a headphone, and adjust the output volume from 100% to 20%, now in theory, the speaker's volume is 100%, the headphone's volume is 20%. We plugout the headphone, the active output device becomes speaker and we expect the volume changes to 100%, but the output volume for speaker is 20%. [Fix] Backport a upstream patch, this patch is already in the pulseaudio-15.0, so impish already has this fix. Only hirsute and focal need to backport this patch. [Test] adjust speaker's volume to 80%, then plug headphone and adjust headphone's volume to 20%, unplug the headphone, the speaker's volume becomes to 80%, plug the headphone, the headphone's volume becomes to 20%. [Where problems could occur] The patch writes the output volume to hardware immediately when switching output device on the machines with sof audio driver, this could introduce pop noise when changing the output device, but this possibility is very low, I tested the patch on many lenovo and dell machines with sof audio driver, all worked as expected and have no pop noise when switching output device. The patch was merged to ubuntu 5.13.0 and 5.11.0 generic kernels with stable update already, but it is not merged to ubuntu 5.4.0 kernel yet, so I sent
[Touch-packages] [Bug 1946499] Re: installation of deb-packages with gdebi-gtk shows "dpkg: error: unable to read filedescriptor flags for : Bad file descr
@Nikola: If that issue happened also in 21.04, it's not the same issue as the one dealt with in this bug report. The latter is about a regression due to an upgrade of vte2.91. So you may want to submit a new bug report (with more details, exact error messages, etc.). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1946499 Title: installation of deb-packages with gdebi-gtk shows "dpkg: error: unable to read filedescriptor flags for : Bad file descriptor" in gdebi terminal, package is not installed Status in Ubuntu MATE: Invalid Status in gdebi package in Ubuntu: Fix Released Status in vte2.91 package in Ubuntu: Confirmed Status in gdebi source package in Impish: Triaged Bug description: Steps to reproduce: 1. Install Ubuntu MATE 21.10 2. Open Firefox, navigate to discord.com 3. Download deb-file. At time of writing from the https://dl.discordapp.net/apps/linux/0.0.16/discord-0.0.16.deb link 4. Open Caja in ~/Downloads folder and use GDebi to install the discord-0.0.16.deb file 5. In the GDebi window click Install button Expected results: * Gdebi quietly install discord package, there are no error messages in its terminal Actual results: * Gdebi terminal shows the error in the last line ``` Selecting previously unselected package gconf2-common. (Reading database ... 457178 files and directories currently installed.) Preparing to unpack .../0-gconf2-common_3.2.6-7ubuntu2_all.deb ... Unpacking gconf2-common (3.2.6-7ubuntu2) ... Selecting previously unselected package libgconf-2-4:amd64. Preparing to unpack .../1-libgconf-2-4_3.2.6-7ubuntu2_amd64.deb ... Unpacking libgconf-2-4:amd64 (3.2.6-7ubuntu2) ... Selecting previously unselected package gconf-service-backend. Preparing to unpack .../2-gconf-service-backend_3.2.6-7ubuntu2_amd64.deb ... Unpacking gconf-service-backend (3.2.6-7ubuntu2) ... Selecting previously unselected package gconf-service. Preparing to unpack .../3-gconf-service_3.2.6-7ubuntu2_amd64.deb ... Unpacking gconf-service (3.2.6-7ubuntu2) ... Selecting previously unselected package libappindicator1. Preparing to unpack .../4-libappindicator1_12.10.1+20.10.20200706.1-0ubuntu1_amd64.deb ... Unpacking libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ... Selecting previously unselected package libunwind-13:amd64. Preparing to unpack .../5-libunwind-13_1%3a13.0.0-2_amd64.deb ... Unpacking libunwind-13:amd64 (1:13.0.0-2) ... Selecting previously unselected package libc++abi1-13:amd64. Preparing to unpack .../6-libc++abi1-13_1%3a13.0.0-2_amd64.deb ... Unpacking libc++abi1-13:amd64 (1:13.0.0-2) ... Selecting previously unselected package libc++1-13:amd64. Preparing to unpack .../7-libc++1-13_1%3a13.0.0-2_amd64.deb ... Unpacking libc++1-13:amd64 (1:13.0.0-2) ... Selecting previously unselected package libc++1:amd64. Preparing to unpack .../8-libc++1_1%3a13.0-53~exp1_amd64.deb ... Unpacking libc++1:amd64 (1:13.0-53~exp1) ... Setting up libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ... Setting up gconf2-common (3.2.6-7ubuntu2) ... Creating config file /etc/gconf/2/path with new version Setting up libunwind-13:amd64 (1:13.0.0-2) ... Setting up libc++abi1-13:amd64 (1:13.0.0-2) ... Setting up libc++1-13:amd64 (1:13.0.0-2) ... Setting up libc++1:amd64 (1:13.0-53~exp1) ... Setting up gconf-service (3.2.6-7ubuntu2) ... Processing triggers for libc-bin (2.34-0ubuntu2) ... Processing triggers for sgml-base (1.30) ... Setting up libgconf-2-4:amd64 (3.2.6-7ubuntu2) ... Setting up gconf-service-backend (3.2.6-7ubuntu2) ... Processing triggers for libc-bin (2.34-0ubuntu2) ... dpkg: error: unable to read filedescriptor flags for : Bad file descriptor ``` and as the result Discord package is not installed . ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gdebi 0.9.5.7+nmu5ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Fri Oct 8 18:17:36 2021 InstallationDate: Installed on 2021-10-08 (0 days ago) InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Daily amd64 (20211008) PackageArchitecture: all SourcePackage: gdebi UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2021-10-08T15:41:41.001986 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1946499/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net
[Touch-packages] [Bug 1946499] Re: installation of deb-packages with gdebi-gtk shows "dpkg: error: unable to read filedescriptor flags for : Bad file descr
When I do right-click on .deb package and open it with Gdebi-gtk, and try to install a package on 21.10 (also used to happen od 21.04) program closes. I have downloaded 0.9.5.7+nmu6 and I think I have built it with dpkg- buildpackage - us -uc and still happens the same. 0.9.5.7+nmu6 works of gdebi-gtk is called from Terminal and .deb opened via File>Open , but it does not when on right-click and install in Thunar. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1946499 Title: installation of deb-packages with gdebi-gtk shows "dpkg: error: unable to read filedescriptor flags for : Bad file descriptor" in gdebi terminal, package is not installed Status in Ubuntu MATE: Invalid Status in gdebi package in Ubuntu: Fix Released Status in vte2.91 package in Ubuntu: Confirmed Status in gdebi source package in Impish: Triaged Bug description: Steps to reproduce: 1. Install Ubuntu MATE 21.10 2. Open Firefox, navigate to discord.com 3. Download deb-file. At time of writing from the https://dl.discordapp.net/apps/linux/0.0.16/discord-0.0.16.deb link 4. Open Caja in ~/Downloads folder and use GDebi to install the discord-0.0.16.deb file 5. In the GDebi window click Install button Expected results: * Gdebi quietly install discord package, there are no error messages in its terminal Actual results: * Gdebi terminal shows the error in the last line ``` Selecting previously unselected package gconf2-common. (Reading database ... 457178 files and directories currently installed.) Preparing to unpack .../0-gconf2-common_3.2.6-7ubuntu2_all.deb ... Unpacking gconf2-common (3.2.6-7ubuntu2) ... Selecting previously unselected package libgconf-2-4:amd64. Preparing to unpack .../1-libgconf-2-4_3.2.6-7ubuntu2_amd64.deb ... Unpacking libgconf-2-4:amd64 (3.2.6-7ubuntu2) ... Selecting previously unselected package gconf-service-backend. Preparing to unpack .../2-gconf-service-backend_3.2.6-7ubuntu2_amd64.deb ... Unpacking gconf-service-backend (3.2.6-7ubuntu2) ... Selecting previously unselected package gconf-service. Preparing to unpack .../3-gconf-service_3.2.6-7ubuntu2_amd64.deb ... Unpacking gconf-service (3.2.6-7ubuntu2) ... Selecting previously unselected package libappindicator1. Preparing to unpack .../4-libappindicator1_12.10.1+20.10.20200706.1-0ubuntu1_amd64.deb ... Unpacking libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ... Selecting previously unselected package libunwind-13:amd64. Preparing to unpack .../5-libunwind-13_1%3a13.0.0-2_amd64.deb ... Unpacking libunwind-13:amd64 (1:13.0.0-2) ... Selecting previously unselected package libc++abi1-13:amd64. Preparing to unpack .../6-libc++abi1-13_1%3a13.0.0-2_amd64.deb ... Unpacking libc++abi1-13:amd64 (1:13.0.0-2) ... Selecting previously unselected package libc++1-13:amd64. Preparing to unpack .../7-libc++1-13_1%3a13.0.0-2_amd64.deb ... Unpacking libc++1-13:amd64 (1:13.0.0-2) ... Selecting previously unselected package libc++1:amd64. Preparing to unpack .../8-libc++1_1%3a13.0-53~exp1_amd64.deb ... Unpacking libc++1:amd64 (1:13.0-53~exp1) ... Setting up libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ... Setting up gconf2-common (3.2.6-7ubuntu2) ... Creating config file /etc/gconf/2/path with new version Setting up libunwind-13:amd64 (1:13.0.0-2) ... Setting up libc++abi1-13:amd64 (1:13.0.0-2) ... Setting up libc++1-13:amd64 (1:13.0.0-2) ... Setting up libc++1:amd64 (1:13.0-53~exp1) ... Setting up gconf-service (3.2.6-7ubuntu2) ... Processing triggers for libc-bin (2.34-0ubuntu2) ... Processing triggers for sgml-base (1.30) ... Setting up libgconf-2-4:amd64 (3.2.6-7ubuntu2) ... Setting up gconf-service-backend (3.2.6-7ubuntu2) ... Processing triggers for libc-bin (2.34-0ubuntu2) ... dpkg: error: unable to read filedescriptor flags for : Bad file descriptor ``` and as the result Discord package is not installed . ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gdebi 0.9.5.7+nmu5ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Fri Oct 8 18:17:36 2021 InstallationDate: Installed on 2021-10-08 (0 days ago) InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Daily amd64 (20211008) PackageArchitecture: all SourcePackage: gdebi UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2021-10-08T15:41:41.001986 To manage notifications about this bug go to: https://bugs.laun
[Touch-packages] [Bug 1947708] Re: Cannot configure suspend-then-hibernate
> [ 82.230208] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 you're using UEFI secure boot, which puts the system into 'lockdown', which disallows (unencrypted) hibernation. So this isn't a problem with systemd, this requires the kernel to handle encrypted hibernation. I *think* that functionality isn't yet in the upstream kernel, as I think this thread was the last discussion about adding it: https://lore.kernel.org/lkml/20210220013255.1083202-1-matthewgarr...@google.com/ ** Package changed: systemd (Ubuntu) => linux (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/1947708 Title: Cannot configure suspend-then-hibernate Status in linux package in Ubuntu: New Bug description: Previous bug 1947617 was closed because my swap space was insufficient. Swap was increased to 24G and the problem remains. Configuring login to suspend-then-hiberrnate when the lid is off and configuring sleep so that hibernate happens 10 seconds after suspend, when trying to test with: sudo systemctl suspend-then-hibernate I get: Failed to suspend system, hibernate later via logind: Sleep verb "suspend-then-hibernate" not supported This could be a security vulnerability. If the user expects the system to suspend (and then lock) when the lid is off and it does not work, somebody could then just reopen the lid and get access. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: systemd 248.3-1ubuntu8 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: i3 Date: Tue Oct 19 11:51:50 2021 InstallationDate: Installed on 2021-10-14 (4 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: HP HP ENVY x360 Convertible 13-ay0xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic root=UUID=e85d08c2-ae82-4f0f-a625-a5012616c934 ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/systemd-localed.service → /usr/lib/systemd/system/systemd-localed.service.d/locale-gen.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. -- Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/30/2021 dmi.bios.release: 15.20 dmi.bios.vendor: Insyde dmi.bios.version: F.20 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 876E dmi.board.vendor: HP dmi.board.version: 12.52 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 12.52 dmi.modalias: dmi:bvnInsyde:bvrF.20:bd07/30/2021:br15.20:efr12.52:svnHP:pnHPENVYx360Convertible13-ay0xxx:pvrType1ProductConfigId:sku3V693EA#ABF:rvnHP:rn876E:rvr12.52:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY x360 Convertible 13-ay0xxx dmi.product.sku: 3V693EA#ABF dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP mtime.conffile..etc.systemd.logind.conf: 2021-10-18T18:51:43.976989 mtime.conffile..etc.systemd.sleep.conf: 2021-10-18T18:52:04.283409 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947708/+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 1944741] Re: HiFive Unmatched partitions are named "Unleashed"
I tested the new packages [1] on a fresh RISC-V image following the test plan in the bug description and validated that the bug was fixed in Impish. [1] https://launchpad.net/ubuntu/+source/util-linux/2.36.1-8ubuntu2/+build/22279841/+files/libfdisk-dev_2.36.1-8ubuntu2_riscv64.deb https://launchpad.net/ubuntu/+source/util-linux/2.36.1-8ubuntu2/+build/22279841/+files/libfdisk1_2.36.1-8ubuntu2_riscv64.deb https://launchpad.net/ubuntu/+source/util-linux/2.36.1-8ubuntu2/+build/22279841/+files/fdisk_2.36.1-8ubuntu2_riscv64.deb ** Tags added: verification-done-impish -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1944741 Title: HiFive Unmatched partitions are named "Unleashed" Status in util-linux package in Ubuntu: New Status in util-linux source package in Impish: Fix Committed Status in util-linux source package in Jammy: New Status in util-linux package in Debian: Confirmed Bug description: [Impact] Both HiFive Unleashed and HiFive Unmatched bootloaders seek for the same UUIDs to load the next stage bootloader: the current name makes partitions on Unmatched board appear as 'Unleashed'. This issue gives the feeling that the Ubuntu RISC-V images made specifically for those 2 boards were assembled in a rushed manner. The attached patch fixes this by removing the 'Unleashed' part of the current name so that it fits both, it was build againt all architectures here: https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+sourcepub/12783067/+listing-archive-extra [Test Plan] 1. Download the SiFive Unmatched image here: https://cdimage.ubuntu.com/ubuntu-server/daily-preinstalled/pending/impish-preinstalled-server-riscv64+unmatched.img.xz 2. Follow instructions here to launch a riscv64 VM: https://wiki.ubuntu.com/RISC-V 3. Execute the following command: ubuntu@ubuntu:~$ sudo fdisk -l Disk /dev/vda: 40 GiB, 42949672960 bytes, 83886080 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 0F66C0C3-A5E4-439B-907E-ABAD106FE4A7 Device Start End Sectors Size Type /dev/vda1 235554 83886046 83650493 39.9G Linux filesystem /dev/vda12 227362 235553 81924M Linux filesystem /dev/vda13 34 2081 20481M HiFive Unleashed FSBL /dev/vda14 208210273 81924M HiFive Unleashed BBL /dev/vda15 10274 227361 217088 106M EFI System Partition table entries are not in disk order. 4. Download and install the new packages that contain the fix here: https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+files/libfdisk1_2.36.1-8ubuntu4_riscv64.deb https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+files/libfdisk-dev_2.36.1-8ubuntu4_riscv64.deb https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+files/fdisk_2.36.1-8ubuntu4_riscv64.deb 5. Re-execute the same command as above: ubuntu@ubuntu:~$ sudo fdisk -l Disk /dev/vda: 40 GiB, 42949672960 bytes, 83886080 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt
Re: [Touch-packages] [Bug 1947466] Re: [CREATIVE MUVO 1c, playback] volume slider does not change sound volume
i just noticed, this slider also doesn't work on my ps5 headset https://www.playstation.com/en-us/accessories/pulse-3d-wireless-headset/ niedz., 17 paź 2021 o 17:50 Hui Wang <1947...@bugs.launchpad.net> napisał(a): > bluetooth adapter is CSR8510 A10 > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1947466 > > Title: > [CREATIVE MUVO 1c, playback] volume slider does not change sound > volume > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1947466/+subscriptions > > -- Paweł Bogaczewicz http://bogaczew.blip.pl/ if (statusIsNotValid.compareTo( Boolean.FALSE ) != 0) skipValidation = false; -- 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/1947466 Title: [CREATIVE MUVO 1c, playback] volume slider does not change sound volume Status in alsa-driver package in Ubuntu: New Bug description: changing the volume of system volume does not affect the sound volume at all. i have to change volume of each program separetly. i.e to change volume of spotify i have to adjust the 'spotify' slider in settings, etc. i'm on fresh install of ubuntu 21.10 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pawel 1425 F pulseaudio /dev/snd/controlC1: pawel 1425 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Oct 16 20:58:59 2021 InstallationDate: Installed on 2021-10-16 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: all ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: CREATIVE MUVO 1c Symptom_Type: Volume slider, or mixer problems Title: [CREATIVE MUVO 1c, playback] volume slider problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/27/2016 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.80 dmi.board.asset.tag: Default string dmi.board.name: H110M PRO-VD (MS-7996) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.80:bd07/27/2016:br5.11:svnMSI:pnMS-7996:pvr1.0:skuDefaultstring:rvnMSI:rnH110MPRO-VD(MS-7996):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7996 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1947466/+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 1947578] Re: broken RTL support in VTE-based terminal emulators.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: newt (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to newt in Ubuntu. https://bugs.launchpad.net/bugs/1947578 Title: broken RTL support in VTE-based terminal emulators. Status in newt package in Ubuntu: Confirmed Bug description: AFAIK Whiptail has a built-in RTL script support, which is awesome on many environment with no RTL support such as text-based Debian installer or TTYs. But recently VTE added support for RTL languages and now, Whiptail is broken on GNOME Terminal, etc. --- I reported this upstream too: https://pagure.io/newt/issue/20 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: whiptail 0.52.21-4ubuntu7 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Oct 18 15:09:03 2021 InstallationDate: Installed on 2021-07-13 (97 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fa_IR SHELL=/bin/bash SourcePackage: newt UpgradeStatus: Upgraded to impish on 2021-10-16 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/newt/+bug/1947578/+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 1947558] Re: rfkill fails to turn on wifi card on Dell Latitude 5490
Found a fix : Get into Bios (F2 At boot) Go to : Power Management -> Wireless Radio Control -> Turn everything OFF This prevents hardware lock of wifi card when going into suspend and undocking from Dell dock. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1947558 Title: rfkill fails to turn on wifi card on Dell Latitude 5490 Status in util-linux package in Ubuntu: New Bug description: Laptop is a Dell Latitude 5490 Was using Windows 10 and installed Ubuntu 20.04 All updates are installed, all firmwares are up to date. Machine was crashing on sleep : would go into sleep, then waking the machine up would do a full system restart. Edited the file /etc/systemd/sleep.conf to have a line "SuspendState=mem" The machine now suspends and wakes properly. But... Once the machine comes back from sleep, the wifi card is dead. Rebooting does not fix the issue, only a full shutdown then restart brings the wifi card back. When doing a tail -f on the /var/log/syslog I can see that rfkill is used to bring the Wifi card back. Here is what happens when laptop goes into sleep : Oct 18 09:53:29 alpha systemd[1]: Starting Suspend... Oct 18 09:53:29 alpha systemd-sleep[3046]: Suspending system... Oct 18 09:53:29 alpha kernel: [ 136.204296] PM: suspend entry (deep) Oct 18 09:53:29 alpha systemd[1]: Starting GRUB failed boot detection... Oct 18 09:53:29 alpha kernel: [ 136.228964] Filesystems sync: 0.024 seconds Oct 18 09:53:29 alpha systemd[1]: grub-initrd-fallback.service: Succeeded. Oct 18 09:53:29 alpha systemd[1]: Finished GRUB failed boot detection. Oct 18 09:55:40 alpha kernel: [ 136.495878] Freezing user space processes ... (elapsed 0.003 seconds) done. Oct 18 09:55:40 alpha kernel: [ 136.499361] OOM killer disabled. Oct 18 09:55:40 alpha kernel: [ 136.499363] Freezing remaining freezable tasks ... (elapsed 0.000 seconds) done. Oct 18 09:55:40 alpha kernel: [ 136.500427] printk: Suspending console(s) (use no_console_suspend to debug) Oct 18 09:55:40 alpha kernel: [ 136.529343] sd 2:0:0:0: [sda] Synchronizing SCSI cache Oct 18 09:55:40 alpha kernel: [ 136.534871] sd 2:0:0:0: [sda] Stopping disk Oct 18 09:55:40 alpha kernel: [ 136.580654] ACPI: EC: interrupt blocked Oct 18 09:55:40 alpha kernel: [ 136.624750] ACPI: Preparing to enter system sleep state S3 Oct 18 09:55:40 alpha kernel: [ 136.635044] ACPI: EC: event blocked Oct 18 09:55:40 alpha kernel: [ 136.635046] ACPI: EC: EC stopped Oct 18 09:55:40 alpha kernel: [ 136.635047] PM: Saving platform NVS memory Oct 18 09:55:40 alpha kernel: [ 136.635149] Disabling non-boot CPUs ... Oct 18 09:55:40 alpha kernel: [ 136.636740] smpboot: CPU 1 is now offline Oct 18 09:55:40 alpha kernel: [ 136.639254] smpboot: CPU 2 is now offline Oct 18 09:55:40 alpha kernel: [ 136.641610] smpboot: CPU 3 is now offline Oct 18 09:55:40 alpha kernel: [ 136.643970] smpboot: CPU 4 is now offline Oct 18 09:55:40 alpha kernel: [ 136.645806] IRQ 122: no longer affine to CPU5 Oct 18 09:55:40 alpha kernel: [ 136.645815] IRQ 128: no longer affine to CPU5 Oct 18 09:55:40 alpha kernel: [ 136.646820] smpboot: CPU 5 is now offline Oct 18 09:55:40 alpha kernel: [ 136.647982] IRQ 124: no longer affine to CPU6 Oct 18 09:55:40 alpha kernel: [ 136.649021] smpboot: CPU 6 is now offline Oct 18 09:55:40 alpha kernel: [ 136.650373] IRQ 126: no longer affine to CPU7 Oct 18 09:55:40 alpha kernel: [ 136.650382] IRQ 129: no longer affine to CPU7 Oct 18 09:55:40 alpha kernel: [ 136.651394] smpboot: CPU 7 is now offline Oct 18 09:55:40 alpha kernel: [ 136.654659] ACPI: Low-level resume complete Oct 18 09:55:40 alpha kernel: [ 136.654749] ACPI: EC: EC started Oct 18 09:55:40 alpha kernel: [ 136.654750] PM: Restoring platform NVS memory Oct 18 09:55:40 alpha kernel: [ 136.655504] Enabling non-boot CPUs ... Oct 18 09:55:40 alpha kernel: [ 136.655548] x86: Booting SMP configuration: Oct 18 09:55:40 alpha kernel: [ 136.655549] smpboot: Booting Node 0 Processor 1 APIC 0x2 Oct 18 09:55:40 alpha kernel: [ 136.656533] CPU1 is up Oct 18 09:55:40 alpha kernel: [ 136.656552] smpboot: Booting Node 0 Processor 2 APIC 0x4 Oct 18 09:55:40 alpha kernel: [ 136.657153] CPU2 is up Oct 18 09:55:40 alpha kernel: [ 136.657171] smpboot: Booting Node 0 Processor 3 APIC 0x6 Oct 18 09:55:40 alpha kernel: [ 136.657774] CPU3 is up Oct 18 09:55:40 alpha kernel: [ 136.657792] smpboot: Booting Node 0 Processor 4 APIC 0x1 Oct 18 09:55:40 alpha kernel: [ 136.658525] CPU4 is up Oct 18 09:55:40 alpha kernel: [ 136.658547] smpboot: Booting Node 0 Processor 5 APIC 0x3 Oct 18 09:55:40 alpha kernel: [ 136.659182] CPU5 is up Oct 18 09:55:40 alpha kernel: [ 136.659201] smpboot: Booting Node 0 Processor 6 APIC 0x5 Oct 18 09:55:40 alpha kernel: [ 136.6598
[Touch-packages] [Bug 1942260] Re: compress firmware in /lib/firmware
** Also affects: linux-firmware-raspi2 (Ubuntu) Importance: Undecided Status: New -- 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/1942260 Title: compress firmware in /lib/firmware Status in initramfs-tools package in Ubuntu: New Status in linux-firmware package in Ubuntu: New Status in linux-firmware-raspi2 package in Ubuntu: New Bug description: Some facts: - The linux kernel has supported loading xz compressed firmware since 5.3 - The size of /lib/firmware in impish is ~650Mb (and growing) - The compressed size of firmware could be ~230Mb It would be nice to install compressed firmware to save space. Here are the plans from the Fedora project: https://fedoraproject.org/wiki/Changes/CompressKernelFirmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1942260/+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 1932329] Re: Benchmark if we can compress kernel modules
** Also affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New -- 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/1932329 Title: Benchmark if we can compress kernel modules Status in initramfs-tools package in Ubuntu: New Status in linux package in Ubuntu: In Progress Bug description: Symbol: MODULE_COMPRESS_ZSTD [=n] Type : bool = Impacts to measure and observe = == Disk space == * Inspect linux-modules-* and linux-modules-extra* deb package Installed-Size and Download-Size changes, i.e. $ apt show linux-modules-5.8.0-53-generic linux-modules- extra-5.8.0-53-generic | grep -e Package: -e Size: Package: linux-modules-5.8.0-53-generic Installed-Size: 81.5 MB Download-Size: 15.5 MB Package: linux-modules-extra-5.8.0-53-generic Installed-Size: 215 MB Download-Size: 41.5 MB In theory, there should not be a significant change in the Download- size. It is desired that there is a significant reduction in Installed-Size. Modules take up about 300MB and normally one has upto three kernel version installed, resulting in about of 1GB of disk space that one constantly pays for. == Boot Speed == In theory, boot speed may either improve or regress. It depends if disk IO is slower than decompression speed, meaning loading compressed modules is faster. Also one has to observe the changes in the initrd size. zstd(zstd) compression may result in slight growth, which shouldn't impact boot speed too much. = Outcomes = If installed size savings can be achieved without regressing bootspeed we should enable CONFIG_MODULE_COMPRESS_ZSTD=y by default. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1932329/+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 1942260] Re: compress firmware in /lib/firmware
** Also affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New -- 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/1942260 Title: compress firmware in /lib/firmware Status in initramfs-tools package in Ubuntu: New Status in linux-firmware package in Ubuntu: New Bug description: Some facts: - The linux kernel has supported loading xz compressed firmware since 5.3 - The size of /lib/firmware in impish is ~650Mb (and growing) - The compressed size of firmware could be ~230Mb It would be nice to install compressed firmware to save space. Here are the plans from the Fedora project: https://fedoraproject.org/wiki/Changes/CompressKernelFirmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1942260/+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 1947708] [NEW] Cannot configure suspend-then-hibernate
Public bug reported: Previous bug 1947617 was closed because my swap space was insufficient. Swap was increased to 24G and the problem remains. Configuring login to suspend-then-hiberrnate when the lid is off and configuring sleep so that hibernate happens 10 seconds after suspend, when trying to test with: sudo systemctl suspend-then-hibernate I get: Failed to suspend system, hibernate later via logind: Sleep verb "suspend-then-hibernate" not supported This could be a security vulnerability. If the user expects the system to suspend (and then lock) when the lid is off and it does not work, somebody could then just reopen the lid and get access. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: systemd 248.3-1ubuntu8 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: i3 Date: Tue Oct 19 11:51:50 2021 InstallationDate: Installed on 2021-10-14 (4 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: HP HP ENVY x360 Convertible 13-ay0xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic root=UUID=e85d08c2-ae82-4f0f-a625-a5012616c934 ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/systemd-localed.service → /usr/lib/systemd/system/systemd-localed.service.d/locale-gen.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. -- Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/30/2021 dmi.bios.release: 15.20 dmi.bios.vendor: Insyde dmi.bios.version: F.20 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 876E dmi.board.vendor: HP dmi.board.version: 12.52 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 12.52 dmi.modalias: dmi:bvnInsyde:bvrF.20:bd07/30/2021:br15.20:efr12.52:svnHP:pnHPENVYx360Convertible13-ay0xxx:pvrType1ProductConfigId:sku3V693EA#ABF:rvnHP:rn876E:rvr12.52:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY x360 Convertible 13-ay0xxx dmi.product.sku: 3V693EA#ABF dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP mtime.conffile..etc.systemd.logind.conf: 2021-10-18T18:51:43.976989 mtime.conffile..etc.systemd.sleep.conf: 2021-10-18T18:52:04.283409 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish -- 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/1947708 Title: Cannot configure suspend-then-hibernate Status in systemd package in Ubuntu: New Bug description: Previous bug 1947617 was closed because my swap space was insufficient. Swap was increased to 24G and the problem remains. Configuring login to suspend-then-hiberrnate when the lid is off and configuring sleep so that hibernate happens 10 seconds after suspend, when trying to test with: sudo systemctl suspend-then-hibernate I get: Failed to suspend system, hibernate later via logind: Sleep verb "suspend-then-hibernate" not supported This could be a security vulnerability. If the user expects the system to suspend (and then lock) when the lid is off and it does not work, somebody could then just reopen the lid and get access. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: systemd 248.3-1ubuntu8 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: i3 Date: Tue Oct 19 11:51:50 2021 InstallationDate: Installed on 2021-10-14 (4 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: HP HP ENVY x360 Convertible 13-ay0xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic root=UUID=e85d08c2-ae82-4f0f-a625-a5012616c934 ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTE
[Touch-packages] [Bug 1947578] Re: broken RTL support in VTE-based terminal emulators.
Found out the problem is in this debian patch for Bidi: https://git.launchpad.net/ubuntu/+source/newt/tree/debian/patches/bidi.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to newt in Ubuntu. https://bugs.launchpad.net/bugs/1947578 Title: broken RTL support in VTE-based terminal emulators. Status in newt package in Ubuntu: New Bug description: AFAIK Whiptail has a built-in RTL script support, which is awesome on many environment with no RTL support such as text-based Debian installer or TTYs. But recently VTE added support for RTL languages and now, Whiptail is broken on GNOME Terminal, etc. --- I reported this upstream too: https://pagure.io/newt/issue/20 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: whiptail 0.52.21-4ubuntu7 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Oct 18 15:09:03 2021 InstallationDate: Installed on 2021-07-13 (97 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fa_IR SHELL=/bin/bash SourcePackage: newt UpgradeStatus: Upgraded to impish on 2021-10-16 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/newt/+bug/1947578/+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 1947677] [NEW] Colemak keyboard layout's left-hand backspace is also acting as Caps Lock
Public bug reported: I have installed Ubuntu with the default English (US) Qwerty keyboard layout and I added the English (Australia) Colemak keyboard layout through the Settings app (as per the screenshot attached). This is for the in-built laptop keyboard on the Lenovo ThinkPad X1 Yoga Touch. The bug is that the CapsLock key, which is meant to be remapped to a Backspace key on the Colemak keyboard layout, acts as both the CapsLock AND the Backspace, when the Colemak keyboard layout is active. This means that backspacing a single time deletes a single character AND also toggles Caps Lock. The expected behaviour is that the key acts only as Backspace when the Colemak keyboard layout is active. The output of 𝚡𝚙𝚛𝚘𝚙 -𝚛𝚘𝚘𝚝 | 𝚐𝚛𝚎𝚙 𝚇𝙺𝙱 is _𝚇𝙺𝙱_𝚁𝚄𝙻𝙴𝚂_𝙽𝙰𝙼𝙴𝚂(𝚂𝚃𝚁𝙸𝙽𝙶) = "𝚎𝚟𝚍𝚎𝚟", "𝚙𝚌𝟷𝟶𝟻", "𝚞𝚜,𝚞𝚜,𝚞𝚜", ",𝚌𝚘𝚕𝚎𝚖𝚊𝚔,", "" I hope a fix can be found soon :) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Oct 19 17:34:44 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:224e] InstallationDate: Installed on 2021-10-09 (9 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: LENOVO 20JDA00CAU ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-38-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2021 dmi.bios.release: 1.41 dmi.bios.vendor: LENOVO dmi.bios.version: N1NET54W (1.41 ) dmi.board.asset.tag: Not Available dmi.board.name: 20JDA00CAU dmi.board.vendor: LENOVO dmi.board.version: SDK0K17763 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnLENOVO:bvrN1NET54W(1.41):bd08/17/2021:br1.41:efr1.19:svnLENOVO:pn20JDA00CAU:pvrThinkPadX1Yoga2nd:skuLENOVO_MT_20JD_BU_Think_FM_ThinkPad:rvnLENOVO:rn20JDA00CAU:rvrSDK0K17763WIN:cvnLENOVO:ct31:cvrNone: dmi.product.family: ThinkPad dmi.product.name: 20JDA00CAU dmi.product.sku: LENOVO_MT_20JD_BU_Think_FM_ThinkPad dmi.product.version: ThinkPad X1 Yoga 2nd dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu ** Attachment added: "Screenshot of keyboard layouts installed on this laptop" https://bugs.launchpad.net/bugs/1947677/+attachment/5534082/+files/Screenshot%20from%202021-10-19%2017-39-51.png -- 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/1947677 Title: Colemak keyboard layout's left-hand backspace is also acting as Caps Lock Status in xorg package in Ubuntu: New Bug description: I have installed Ubuntu with the default English (US) Qwerty keyboard layout and I added the English (Australia) Colemak keyboard layout through the Settings app (as per the screenshot attached). This is for the in-built laptop keyboard on the Lenovo ThinkPad X1 Yoga Touch. The bug is that the CapsLock key, which is meant to be remapped to a Backspace key on the Colemak keyboard layout, acts as both the CapsLock AND the Backspace, when the Colemak keyboard layout is active. This means that backspacing a single time deletes a single character AND also toggles Caps Lock. The expected behaviour is that the key acts only as Backspace when the Colemak keyboard layout is active. The output of 𝚡𝚙𝚛𝚘𝚙 -𝚛𝚘𝚘𝚝 | 𝚐𝚛𝚎𝚙 𝚇𝙺𝙱 is _𝚇𝙺𝙱_𝚁𝚄𝙻𝙴𝚂_𝙽𝙰𝙼𝙴𝚂(𝚂𝚃𝚁𝙸𝙽𝙶) = "𝚎𝚟𝚍𝚎𝚟", "𝚙𝚌𝟷𝟶𝟻", "𝚞𝚜,𝚞𝚜,𝚞𝚜", ",𝚌𝚘𝚕𝚎𝚖𝚊𝚔,", "" I hope a fix can be found soon :) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 Uname: Lin
[Touch-packages] [Bug 1934501] Re: CVE-2018-15473 patch introduce user enumeration vulnerability
Thanks, Kazza. That certainly helped. I also had a word with Marc and we
reached to the conclusion that Stretch isn't affected with this
backporting problem.
Thanks, again! \o/
--
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/1934501
Title:
CVE-2018-15473 patch introduce user enumeration vulnerability
Status in openssh package in Ubuntu:
Fix Released
Bug description:
I was recently using a 18.04 machine and noticed that the result of
connecting to ssh with an arbitrary public key varied depending if the
user was valid.
After some investigation, it appears to only be present when
CVE-2018-15473.patch has been applied.
Directly pulling a 18.04 docker image and installing openssh server
(currently 1:7.6p1-4ubuntu0.3) results in a trivial user enumeration
vulnerability in the default config.
Below shows the setup of environment:
$ docker pull ubuntu:18.04
18.04: Pulling from library/ubuntu
Digest:
sha256:139b3846cee2e63de9ced83cee7023a2d95763ee2573e5b0ab6dea9dfbd4db8f
Status: Image is up to date for ubuntu:18.04
docker.io/library/ubuntu:18.04
$ docker run -t -i --rm -e TERM=${TERM} ubuntu:18.04
root@75569fbf0b03:/# apt update
...snip...
root@75569fbf0b03:/# apt install openssh-server
...snip...
root@75569fbf0b03:/# dpkg-query -l openssh\*
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version
Architecture Description
+++--=-=-=
ii openssh-client 1:7.6p1-4ubuntu0.3amd64
secure shell (SSH) client, for secure access to remote
machines
ii openssh-server 1:7.6p1-4ubuntu0.3amd64
secure shell (SSH) server, for secure access from remote
machines
ii openssh-sftp-server 1:7.6p1-4ubuntu0.3amd64
secure shell (SSH) sftp server module, for SFTP access from
remote machines
root@75569fbf0b03:/# mkdir /run/sshd
root@75569fbf0b03:/# /usr/sbin/sshd -D
Then to perform user enumeration, connecting with a public key results in
user enumeration:
* in the following id_rsa-dummy.pub is removed as it slightly changes message
flow
* I have not checked different versions of the ssh client
$ ssh -V
OpenSSH_8.2p1 Ubuntu-4ubuntu0.2, OpenSSL 1.1.1f 31 Mar 2020
$ ssh-keygen -t rsa -C dummy -P '' -f id_rsa-dummy
$ rm id_rsa-dummy.pub
$ ssh -i id_rsa-dummy invalid@172.17.0.2
Connection closed by 172.17.0.2 port 22
$ ssh -i id_rsa-dummy root@172.17.0.2
root@172.17.0.2's password:
That is, when invalid users are provided to public key auth the
connection is closed by the server. Otherwise, it will move onto the
next auth method. This can be improved by adding "ssh -o
PasswordAuthentication=no" when connecting to avoid password prompt
and get an easy to script error message.
I have verified that this behaviour is present after starting with
original source and only applying CVE-2018-15473.patch from the
openssh_7.6p1-4ubuntu0.3.debian.tar.xz archive. Without this patch
this behaviour is not present.
$ md5sum openssh-7.6p1.tar.gz debian/patches/CVE-2018-15473.patch
06a88699018e5fef13d4655abfed1f63 openssh-7.6p1.tar.gz
6101d47f542690b0c5e354ec8b8a70a1 debian/patches/CVE-2018-15473.patch
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1934501/+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 1947617] Re: Cannot configure suspend-then-hibernate
I do not think that this bug report is invalid for multiple reasons (in order of importance): 1. The error message is not related to the root you identified. If the root cause is effectively a swap partition that is not big enough, maybe the error should say so. 2. The swap size was configured by the ubuntu installer. I would expect that the automatic installer configure the partition so that all the features are available, especially hibernate on a laptop. 3. Why would swap size have anything to do with hibernate? The system can dump memory in a regular file on the regular filesystem. Swapping is, as far as I understand, a way to extend memory when RAM is insufficient, not a way to store the whole volatile memory on disk. Anyway, thanks for your time and effort. -- 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/1947617 Title: Cannot configure suspend-then-hibernate Status in systemd package in Ubuntu: Invalid Bug description: Configuring login to suspend-then-hiberrnate when the lid is off and configuring sleep so that hibernate happens 10 seconds after suspend, when trying to test with: sudo systemctl suspend-then-hibernate I get: Failed to suspend system, hibernate later via logind: Sleep verb "suspend-then-hibernate" not supported This could be a security vulnerability. If the user expects the system to suspend (and then lock) when the lid is off and it does not work, somebody could then just reopen the lid and get access. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: systemd 248.3-1ubuntu8 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: i3 Date: Mon Oct 18 18:57:35 2021 InstallationDate: Installed on 2021-10-14 (3 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: HP HP ENVY x360 Convertible 13-ay0xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic root=UUID=e85d08c2-ae82-4f0f-a625-a5012616c934 ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/systemd-localed.service → /usr/lib/systemd/system/systemd-localed.service.d/locale-gen.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. -- Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/30/2021 dmi.bios.release: 15.20 dmi.bios.vendor: Insyde dmi.bios.version: F.20 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 876E dmi.board.vendor: HP dmi.board.version: 12.52 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 12.52 dmi.modalias: dmi:bvnInsyde:bvrF.20:bd07/30/2021:br15.20:efr12.52:svnHP:pnHPENVYx360Convertible13-ay0xxx:pvrType1ProductConfigId:sku3V693EA#ABF:rvnHP:rn876E:rvr12.52:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY x360 Convertible 13-ay0xxx dmi.product.sku: 3V693EA#ABF dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP mtime.conffile..etc.systemd.logind.conf: 2021-10-18T18:51:43.976989 mtime.conffile..etc.systemd.sleep.conf: 2021-10-18T18:52:04.283409 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1947617/+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
