[Touch-packages] [Bug 1947854] Re: package linux-image-5.13.0-20-generic 5.13.0-20.20 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: initramfs-tools (Ubuntu) Status: New => Confirmed -- 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/1947854 Title: package linux-image-5.13.0-20-generic 5.13.0-20.20 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: Confirmed Bug description: Installed via Gnome software, hangs on decrypting volume after reboot. ProblemType: Package DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-20-generic 5.13.0-20.20 ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ymirv 12352 F pulseaudio /dev/snd/controlC3: ymirv 12352 F pulseaudio /dev/snd/controlC2: ymirv 12352 F pulseaudio /dev/snd/controlC0: ymirv 12352 F pulseaudio CasperMD5CheckResult: unknown Date: Wed Oct 20 09:28:09 2021 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=none InstallationDate: Installed on 2021-01-16 (276 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 82FN ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_u6oi4d@/vmlinuz-5.11.0-37-generic root=ZFS=rpool/ROOT/ubuntu_u6oi4d ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1build1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu47 SourcePackage: initramfs-tools Title: package linux-image-5.13.0-20-generic 5.13.0-20.20 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to impish on 2021-10-18 (1 days ago) dmi.bios.date: 10/06/2020 dmi.bios.release: 1.15 dmi.bios.vendor: LENOVO dmi.bios.version: FFCN15WW(V1.03) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: 3192 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga 6 13ARE05 dmi.ec.firmware.release: 1.15 dmi.modalias: dmi:bvnLENOVO:bvrFFCN15WW(V1.03):bd10/06/2020:br1.15:efr1.15:svnLENOVO:pn82FN:pvrYoga613ARE05:skuLENOVO_MT_82FN_BU_idea_FM_Yoga613ARE05:rvnLENOVO:rnLNVNB161216:rvr3192WIN:cvnLENOVO:ct31:cvrYoga613ARE05: dmi.product.family: Yoga 6 13ARE05 dmi.product.name: 82FN dmi.product.sku: LENOVO_MT_82FN_BU_idea_FM_Yoga 6 13ARE05 dmi.product.version: Yoga 6 13ARE05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1947854/+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 1946096] Re: Support manual firmware upgrading for Foxconn and Quectel modems.
Yes, (3) is not expected to change existing behavior. -- 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: Support manual firmware upgrading for Foxconn and Quectel modems. Status in OEM Priority Project: In Progress Status in modemmanager package in Ubuntu: New Bug description: [Impact] The modem certification requires that different modem firmware is used for different network carrier. This needs the firmware upgrading capability during the modem certification process. The modem manufacture vendors (Foxconn and Quectel) provided utilities to do modem's firmware upgrading manually.(LP#1943774, LP#1943780) These utilities are verified to be working when the recent versions(> v 1.18.2) of ModemManager are used with. To support manual firmware upgrading on the current Focal release which is using ModemManager v 1.16.6, we need to apply some patches from v 1.18.2. 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 The firmware upgrading was verified using the patched ModemManager v 1.16.6 with the following 2 modems: * Foxconn SDX55 T99W175 5G sub6 PCIE Modem * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem [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. This should not affect existing generic functions and other modems. [Other Info] The firmware and the upgrading utilities 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 1946096] Re: Support manual firmware upgrading for Foxconn and Quectel modems.
Ok. For clarity, my understanding of these patches are that they do the following things: 1) Add a feature to ModemManager to support uploading firmware to these modems 2) Increase a timeout that was found to be insufficient when doing a firmware update 3) Add a bunch of mappings from SIM->Carrier And then in response to potential concerns: (1) is a straight feature addition, and the associated code will only be called if an external component connects to modemmanager requesting a firmware upload. This is not expected to change any existing behaviours. (2) is low-risk It's not clear to me whether (3) is expected to change existing behaviours at all. Is this understanding correct? Assuming (3) is not expected to change existing behaviour this looks like it would be acceptable under the hardware-enablement SRU policy. -- 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: Support manual firmware upgrading for Foxconn and Quectel modems. Status in OEM Priority Project: In Progress Status in modemmanager package in Ubuntu: New Bug description: [Impact] The modem certification requires that different modem firmware is used for different network carrier. This needs the firmware upgrading capability during the modem certification process. The modem manufacture vendors (Foxconn and Quectel) provided utilities to do modem's firmware upgrading manually.(LP#1943774, LP#1943780) These utilities are verified to be working when the recent versions(> v 1.18.2) of ModemManager are used with. To support manual firmware upgrading on the current Focal release which is using ModemManager v 1.16.6, we need to apply some patches from v 1.18.2. 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 The firmware upgrading was verified using the patched ModemManager v 1.16.6 with the following 2 modems: * Foxconn SDX55 T99W175 5G sub6 PCIE Modem * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem [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. This should not affect existing generic functions and other modems. [Other Info] The firmware and the upgrading utilities 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 1948813] Re: cant connect to second monitor
Thanks for the bug report. The problem appears to be that the nvidia-470 kernel driver loaded and then quickly unloaded two seconds later. I don't know why that would happen... Maybe look in the 'Additional Drivers' app and uninstall the 470 driver, try 460 or 465 instead? ** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-470 (Ubuntu) ** Summary changed: - cant connect to second monitor + Nvidia-470 kernel driver loads then unloads during boot on GTX 1050 Mobile. No driver loaded in the end. -- 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/1948813 Title: Nvidia-470 kernel driver loads then unloads during boot on GTX 1050 Mobile. No driver loaded in the end. Status in nvidia-graphics-drivers-470 package in Ubuntu: New Bug description: I lost projecting to my second monitor while updating in ubuntu 20 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-89.100-generic 5.4.143 Uname: Linux 5.4.0-89-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/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 26 07:55:42 2021 DistUpgraded: 2021-10-15 08:30:35,667 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 5.4.0-89-generic, x86_64: installed nvidia, 470.74, 5.4.0-89-generic, x86_64: installed virtualbox, 6.1.26, 5.4.0-88-generic, x86_64: installed virtualbox, 6.1.26, 5.4.0-89-generic, x86_64: installed GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] UHD Graphics 630 (Mobile) [1025:1264] NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] [10de:1c8d] (rev ff) (prog-if ff) InstallationDate: Installed on 2021-09-21 (34 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) MachineType: Acer Nitro AN515-52 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic root=UUID=c4de9279-4774-410d-be28-7e7083e0c939 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2021-10-15 (10 days ago) dmi.bios.date: 08/05/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.28 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Freed_CFS dmi.board.vendor: CFL dmi.board.version: V1.28 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.28 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.28:bd08/05/2019:svnAcer:pnNitroAN515-52:pvrV1.28:rvnCFL:rnFreed_CFS:rvrV1.28:cvnAcer:ct10:cvrV1.28: dmi.product.family: Acer Nitro 5 dmi.product.name: Nitro AN515-52 dmi.product.sku: dmi.product.version: V1.28 dmi.sys.vendor: Acer 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 21.0.3-0ubuntu0.3~20.04.3 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 N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1948813/+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 1921518] Re: OpenSSL "double free" error
Hi,
Sorry for interrupting your thread, this bug has been prioritized on our
end (I work at NVIDIA) so I joined the triaging effort and I believe I
found the root cause for the crash. For the record, I used wget, but it
behaves the same to curl.
First of all, it seems that it isn't that far off from an old case -
https://openssl-dev.openssl.narkive.com/97zf5qT2/what-is-the-really-
proper-way-to-use-an-engine. The reason being that the configuration
file is loaded twice:
#0 0xf7c80304 in CONF_modules_load_file () from
/lib/aarch64-linux-gnu/libcrypto.so.1.1
#1 0xf7c805e8 in ?? () from /lib/aarch64-linux-gnu/libcrypto.so.1.1
#2 0xf7cfa03c in ?? () from /lib/aarch64-linux-gnu/libcrypto.so.1.1
#3 0xf79dadd4 in __pthread_once_slow (once_control=0xf7e44550,
init_routine=0xf7cfa020) at pthread_once.c:116
#4 0xf7d434c4 in CRYPTO_THREAD_run_once () from
/lib/aarch64-linux-gnu/libcrypto.so.1.1
#5 0xf7cfa608 in OPENSSL_init_crypto () from
/lib/aarch64-linux-gnu/libcrypto.so.1.1
#6 0xf7c80578 in OPENSSL_config () from
/lib/aarch64-linux-gnu/libcrypto.so.1.1
#7 0xaaae9e24 in ?? ()
#8 0xaaacfbe0 in ?? ()
#9 0xaaad29cc in ?? ()
#10 0xaaadde5c in ?? ()
#11 0xaaab8874 in ?? ()
And later again (practically in the same function):
#0 0xf7c80304 in CONF_modules_load_file () from
/lib/aarch64-linux-gnu/libcrypto.so.1.1
#1 0xaaae9e68 in ?? ()
#2 0xaaacfbe0 in ?? ()
#3 0xaaad29cc in ?? ()
#4 0xaaadde5c in ?? ()
#5 0xaaab8874 in ?? ()
This means that the engine parsing and creation flow is done twice,
which breaks several assumptions of both OpenSSL and the loaded engines:
1. Parsing the name "pka"
2. Creating a dynamic engine
3. Cloning the dynamic engine inside ENGINE_by_id()
3. Using the dynamic path to call the "bind" method of the loaded .so file
(pka.so)
4. Populating the fields of the cloned dynamic engine on top of what the user
still holds as ("e"):
else if (strcmp(ctrlname, "dynamic_path") == 0) {
e = ENGINE_by_id("dynamic");
5. dynamic_load() will try to once again ENGINE_add() the engine, but it is
already in the engine list
6. The Add will fail, and the reference count won't be incremented, hence will
stay at 1
7. The error will propagate and ENGINE_free() will get called because the load
failed:
if (!ENGINE_ctrl_cmd_string(e, "LOAD", NULL, 0))
goto err;
8. The free()ed engine is actually the PKA engine which got created twice, and
the destruction of the engine (which assumes it only get created/destroyed
once) will free memory pointed by static variables inside of the PKA module.
9. The first PKA engine is still "alive" and when used it will access free()ed
memory pointed by the static variables of PKA
10. We get a BUS error when invoking a function using a garbled fptr which got
overridden because it is stored in a free()ed memory buffer. On ARM, BUS error
is very common because the CPU can't execute commands from misaligned
addresses, and with high probability the garbled value isn't divisible by 4.
It seems that several fixes could resolve this issue:
1. The configuration file shouldn't be loaded twice, this breaks several
assumptions of the engines (as shown in the bug I linked above, which is from
11 years ago)
2. The fact that the dynamic engine starts as "dynamic" and the load replaces
it with the loaded engine is extremely counter intuitive. The caller holds a
single pointer, and it gets transformed into the loaded engine. Seeing there is
already a following call of "e = ENGINE_by_id(name)", this should be the code
line that transforms the user's engine to the one that was loaded, the dynamic
engine shouldn't change it in-memory when the user thinks their pointer points
at a dynamic engine.
3. If engines are to be expected to get added/freed multiple times, it should
be announced clearly, so that engine developers would know they are expected to
maintain their own reference count if using static variables. In general, it
will probably be best if engines would only be loaded once (and point #1 will
be fixed).
I hope my analysis will help resolve this issue. Feel free to reach out
if more information is needed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1921518
Title:
OpenSSL "double free" error
Status in openssl package in Ubuntu:
Incomplete
Status in openssl source package in Focal:
Incomplete
Bug description:
"double free" error is seen when using curl utility. Error is from
libcrypto.so which is part of the OpenSSL package. This happens only
when OpenSSL is configured to use a dynamic engine.
OpenSSL version is 1.1.1f
The issue is not encountered if
http://www.openssl.org/source/openssl-1.1.1f.tar.gz is used
[Touch-packages] [Bug 1916250] Re: gir1.2-signon-2.0 needs to declare replace on older releases (Groovy2Hirsute and Focal2Jammy)
** Description changed: gir1.2-signon-1.0 from groovy gir1.2-signon-2.0 from hirsute above two packages ship the same file /usr/lib/python3/dist- packages/gi/overrides/Signon.py without specifying how to resolve the conflict. + + [Test Case] + This can be simply tested with a focal schroot: + 1) apt-get install vim libsignon-glib-dev + 2) edit /etc/apt/sources.list replacing focal with hirsute + 3) apt-get update + 4) apt-get install libsignon-glib-dev + + With the version of libsignon-glib-dev from -proposed you'll no longer + receive the 'dpkg: error' from below. Unpacking gir1.2-signon-2.0:amd64 (2.1-3) ... dpkg: error processing archive /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb (--unpack): trying to overwrite '/usr/lib/python3/dist-packages/gi/overrides/Signon.py', which is also in package gir1.2-signon-1.0 1.14+17.04.20161117-0ubuntu5 Errors were encountered while processing: /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Probably needs a conflicts/replaces dependency added to the newer hirsute package. + + [Regression Potential] + We are adding a replaces with gir1.2-signon-1.0 so anything that depends on that package would be broken but given that that package is no longer available after focal that seems fine. ** Also affects: libsignon-glib (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: libsignon-glib (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: libsignon-glib (Ubuntu Hirsute) Status: New => In Progress ** Changed in: libsignon-glib (Ubuntu Impish) Status: New => In Progress ** Changed in: libsignon-glib (Ubuntu Hirsute) Assignee: (unassigned) => Brian Murray (brian-murray) ** Changed in: libsignon-glib (Ubuntu Impish) Assignee: (unassigned) => Brian Murray (brian-murray) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libsignon-glib in Ubuntu. https://bugs.launchpad.net/bugs/1916250 Title: gir1.2-signon-2.0 needs to declare replace on older releases (Groovy2Hirsute and Focal2Jammy) Status in libsignon-glib package in Ubuntu: Fix Released Status in libsignon-glib source package in Hirsute: In Progress Status in libsignon-glib source package in Impish: In Progress Bug description: gir1.2-signon-1.0 from groovy gir1.2-signon-2.0 from hirsute above two packages ship the same file /usr/lib/python3/dist- packages/gi/overrides/Signon.py without specifying how to resolve the conflict. [Test Case] This can be simply tested with a focal schroot: 1) apt-get install vim libsignon-glib-dev 2) edit /etc/apt/sources.list replacing focal with hirsute 3) apt-get update 4) apt-get install libsignon-glib-dev With the version of libsignon-glib-dev from -proposed you'll no longer receive the 'dpkg: error' from below. Unpacking gir1.2-signon-2.0:amd64 (2.1-3) ... dpkg: error processing archive /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb (--unpack): trying to overwrite '/usr/lib/python3/dist-packages/gi/overrides/Signon.py', which is also in package gir1.2-signon-1.0 1.14+17.04.20161117-0ubuntu5 Errors were encountered while processing: /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Probably needs a conflicts/replaces dependency added to the newer hirsute package. [Regression Potential] We are adding a replaces with gir1.2-signon-1.0 so anything that depends on that package would be broken but given that that package is no longer available after focal that seems fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsignon-glib/+bug/1916250/+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 1943811] Re: apport-gtk crashed with SIGSEGV in g_callable_info_free_closure()
** Information type changed from Private to Public -- 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/1943811 Title: apport-gtk crashed with SIGSEGV in g_callable_info_free_closure() Status in apport package in Ubuntu: New Bug description: keeps happening on trying to report any other bug. (origin probably #1943809) for once an apport-gtk bug actually seems to be being reported as far as here anyway... ProblemType: Crash DistroRelease: Ubuntu 21.10 Package: apport-gtk 2.20.11-0ubuntu68 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 CasperMD5CheckResult: unknown CrashReports: 640:1000:125:13142670:2021-09-14 10:30:28.342162132 +0100:2021-09-14 10:30:29.342162132 +0100:/var/crash/_usr_bin_update-manager.1000.crash 640:1000:125:8224590:2021-09-14 10:27:22.069457292 +0100:2021-09-14 10:27:23.069457292 +0100:/var/crash/_usr_share_apport_apport-gtk.1000.crash 640:1000:125:1933001:2021-09-14 12:07:52.568973206 +0100:2021-09-14 12:07:52.068972495 +0100:/var/crash/_usr_share_code_code.1000.crash 640:1000:125:6853834:2021-09-14 10:27:21.601451252 +0100:2021-09-14 10:27:20.765447794 +0100:/var/crash/_usr_lib_ubuntu-release-upgrader_check-new-release-gtk.1000.crash 640:1000:125:2851453:2021-09-14 12:06:33.592861389 +0100:2021-09-14 12:06:32.60397 +0100:/var/crash/_usr_bin_gjs-console.1000.crash CurrentDesktop: ubuntu:GNOME Date: Tue Sep 14 10:27:22 2021 ExecutablePath: /usr/share/apport/apport-gtk ExecutableTimestamp: 1629415949 InstallationDate: Installed on 2021-01-17 (241 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) InterpreterPath: /usr/bin/python3.9 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk ProcCwd: /home/rachel ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/usr/bin/zsh Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1 PythonDetails: N/A SegvAnalysis: Segfault happened at: 0x7f52d4d18cec : mov0x8(%rax),%rdi PC (0x7f52d4d18cec) ok source "0x8(%rax)" (0x441f0f66e307) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: apport StacktraceTop: g_callable_info_free_closure () from /lib/x86_64-linux-gnu/libgirepository-1.0.so.1 ?? () from /usr/lib/python3/dist-packages/gi/_gi.cpython-39-x86_64-linux-gnu.so ?? () ?? () ?? () Title: apport-gtk crashed with SIGSEGV in g_callable_info_free_closure() UpgradeStatus: Upgraded to impish on 2021-07-08 (69 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1943811/+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 1942685] Re: pulseaudio crashed with SIGSEGV in _IceTransClose()
Hello Brian (brian-murray) Please see my comment #9 above - i have run numerous tests on Xubuntu Impish and have been unable to reproduce this bug. -- 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/1942685 Title: pulseaudio crashed with SIGSEGV in _IceTransClose() Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Fix Committed Status in pulseaudio source package in Impish: Fix Committed Bug description: * Impact The pulseaudio service sometime segfaults on session closing which trigger a bug report dialog * Test plan Log out of a desktop session and back in, there should be no error prompt The issue isn't triggered only randomly it seems so it might be easier to check that reports stop on https://errors.ubuntu.com/problem/877172e07ed9f86b0674cd458a5aaf24b37fb01e * Where problems could occur The change is in the X session closing handling so shouldn't impact on normal use, if incorrect the fix could lead to increase the chance of hitting the segfault when an Xsession is closed --- Installing Xubuntu Impish daily ISO 04092021 After install I rebooted - applied updates and then rebooted again- the errors (pulseaudio crashed with SIGSEGV in _IceTransClose() ) occurred after logging in. ProblemType: Crash DistroRelease: Ubuntu 21.10 Package: pulseaudio 1:15.0+dfsg1-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1 Uname: Linux 5.13.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kx 847 F pulseaudio CasperMD5CheckResult: pass Date: Sat Sep 4 16:43:45 2021 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2021-09-04 (0 days ago) InstallationMedia: Xubuntu 21.10 "Impish Indri" - Alpha amd64 (20210904) ProcCmdline: /usr/bin/pulseaudio --daemonize=no --log-target=journal Signal: 11 SourcePackage: pulseaudio StacktraceTop: _IceTransClose () from /lib/x86_64-linux-gnu/libICE.so.6 _IceFreeConnection () from /lib/x86_64-linux-gnu/libICE.so.6 IceCloseConnection () from /lib/x86_64-linux-gnu/libICE.so.6 SmcCloseConnection () from /lib/x86_64-linux-gnu/libSM.so.6 ?? () from /usr/lib/pulse-15.0+dfsg1/modules/module-x11-xsmp.so Title: pulseaudio crashed with SIGSEGV in _IceTransClose() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo dmi.bios.date: 12/23/2020 dmi.bios.release: 1.51 dmi.bios.vendor: LENOVO dmi.bios.version: DKCN51WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V14-IIL dmi.ec.firmware.release: 1.51 dmi.modalias: dmi:bvnLENOVO:bvrDKCN51WW:bd12/23/2020:br1.51:efr1.51:svnLENOVO:pn82C4:pvrLenovoV14-IIL:skuLENOVO_MT_82C4_BU_idea_FM_V14-IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoV14-IIL: dmi.product.family: V14-IIL dmi.product.name: 82C4 dmi.product.sku: LENOVO_MT_82C4_BU_idea_FM_V14-IIL dmi.product.version: Lenovo V14-IIL dmi.sys.vendor: LENOVO separator: To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1942685/+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 1896251] Re: rsync --delete-missing-args fails with "error: protocol incompatibility"
** Changed in: rsync (Ubuntu Bionic) Status: Triaged => In Progress ** Changed in: rsync (Ubuntu Focal) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1896251 Title: rsync --delete-missing-args fails with "error: protocol incompatibility" Status in rsync package in Ubuntu: Fix Released Status in rsync source package in Xenial: Won't Fix Status in rsync source package in Bionic: In Progress Status in rsync source package in Focal: In Progress Bug description: Running rsync --delete-missing-args --files-from=... fails with error message like ABORTING due to invalid path from sender: dir1/dir2/dir3 rsync error: protocol incompatibility (code 2) at generator.c(1271) [generator=3.1.2] if the listed directories are trying to delete full subtree of files. According to https://bugzilla.samba.org/show_bug.cgi?id=12569 this has been fixed in version 3.2.2. See also: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863334 Could you update the rsync package or backport the fix? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: rsync 3.1.2-2.1ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-47.51~18.04.1-lowlatency 5.4.55 Uname: Linux 5.4.0-47-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CurrentDesktop: MATE Date: Fri Sep 18 18:27:53 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-05 (621 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: rsync UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1896251/+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 1896251] Re: rsync --delete-missing-args fails with "error: protocol incompatibility"
** Changed in: rsync (Ubuntu Bionic) Assignee: (unassigned) => Lena Voytek (lvoytek) ** Changed in: rsync (Ubuntu Focal) Assignee: (unassigned) => Lena Voytek (lvoytek) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1896251 Title: rsync --delete-missing-args fails with "error: protocol incompatibility" Status in rsync package in Ubuntu: Fix Released Status in rsync source package in Xenial: Won't Fix Status in rsync source package in Bionic: Triaged Status in rsync source package in Focal: Triaged Bug description: Running rsync --delete-missing-args --files-from=... fails with error message like ABORTING due to invalid path from sender: dir1/dir2/dir3 rsync error: protocol incompatibility (code 2) at generator.c(1271) [generator=3.1.2] if the listed directories are trying to delete full subtree of files. According to https://bugzilla.samba.org/show_bug.cgi?id=12569 this has been fixed in version 3.2.2. See also: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863334 Could you update the rsync package or backport the fix? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: rsync 3.1.2-2.1ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-47.51~18.04.1-lowlatency 5.4.55 Uname: Linux 5.4.0-47-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CurrentDesktop: MATE Date: Fri Sep 18 18:27:53 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-05 (621 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: rsync UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1896251/+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 1938983] Re: missing modules after 5.11.0-25-generic update
Similar bugs are also reported here: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1922350 https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1939986 It seems that the 5.11 kernel needs newer versions of i915 firmware than those currently available in linux-firmware package. ** Also affects: linux-firmware (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/1938983 Title: missing modules after 5.11.0-25-generic update Status in initramfs-tools package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: New Bug description: After updating to kernel 5.11.0-25-generic wireless driver failed to recognize WiFi card. Possible reasons/symptoms: $ sudo update-initramfs -u -k all update-initramfs: Generating /boot/initrd.img-5.11.0-25-generic W: Possible missing firmware /lib/firmware/i915/skl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/bxt_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/glk_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/cml_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/icl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/ehl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/ehl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/dg1_dmc_ver2_02.bin for module i915 update-initramfs: Generating /boot/initrd.img-5.8.0-63-generic $ lsb_release -a LSB Version: core-11.1.0ubuntu2-noarch:security-11.1.0ubuntu2-noarch Distributor ID: Ubuntu Description: July2021 Release: 20.04 Codename: focal Workaround: connected Ethernet. (Inconvenient) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1938983/+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 1942685] Re: pulseaudio crashed with SIGSEGV in _IceTransClose()
Hello Leó, or anyone else affected, Accepted pulseaudio into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/pulseaudio/1:15.0+dfsg1-1ubuntu2.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- 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: pulseaudio (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 pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1942685 Title: pulseaudio crashed with SIGSEGV in _IceTransClose() Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Fix Committed Status in pulseaudio source package in Impish: Fix Committed Bug description: * Impact The pulseaudio service sometime segfaults on session closing which trigger a bug report dialog * Test plan Log out of a desktop session and back in, there should be no error prompt The issue isn't triggered only randomly it seems so it might be easier to check that reports stop on https://errors.ubuntu.com/problem/877172e07ed9f86b0674cd458a5aaf24b37fb01e * Where problems could occur The change is in the X session closing handling so shouldn't impact on normal use, if incorrect the fix could lead to increase the chance of hitting the segfault when an Xsession is closed --- Installing Xubuntu Impish daily ISO 04092021 After install I rebooted - applied updates and then rebooted again- the errors (pulseaudio crashed with SIGSEGV in _IceTransClose() ) occurred after logging in. ProblemType: Crash DistroRelease: Ubuntu 21.10 Package: pulseaudio 1:15.0+dfsg1-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1 Uname: Linux 5.13.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kx 847 F pulseaudio CasperMD5CheckResult: pass Date: Sat Sep 4 16:43:45 2021 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2021-09-04 (0 days ago) InstallationMedia: Xubuntu 21.10 "Impish Indri" - Alpha amd64 (20210904) ProcCmdline: /usr/bin/pulseaudio --daemonize=no --log-target=journal Signal: 11 SourcePackage: pulseaudio StacktraceTop: _IceTransClose () from /lib/x86_64-linux-gnu/libICE.so.6 _IceFreeConnection () from /lib/x86_64-linux-gnu/libICE.so.6 IceCloseConnection () from /lib/x86_64-linux-gnu/libICE.so.6 SmcCloseConnection () from /lib/x86_64-linux-gnu/libSM.so.6 ?? () from /usr/lib/pulse-15.0+dfsg1/modules/module-x11-xsmp.so Title: pulseaudio crashed with SIGSEGV in _IceTransClose() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo dmi.bios.date: 12/23/2020 dmi.bios.release: 1.51 dmi.bios.vendor: LENOVO dmi.bios.version: DKCN51WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V14-IIL dmi.ec.firmware.release: 1.51 dmi.modalias: dmi:bvnLENOVO:bvrDKCN51WW:bd12/23/2020:br1.51:efr1.51:svnLENOVO:pn82C4:pvrLenovoV14-IIL:skuLENOVO_MT_82C4_BU_idea_FM_V14-IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoV14-IIL: dmi.product.family: V14-IIL dmi.product.name: 82C4 dmi.product.sku: LENOVO_MT_82C4_BU_idea_FM_V14-IIL dmi.product.version: Lenovo V14-IIL dmi.sys.vendor: LENOVO separator: To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1942685/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 1930188] Re: Acer Aspire 5 sound driver issues
This bug was fixed in the package alsa-ucm-conf - 1.2.4-2ubuntu5 --- alsa-ucm-conf (1.2.4-2ubuntu5) impish; urgency=medium * d/p/0008-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 10:54:28 +0800 ** Changed in: alsa-ucm-conf (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 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 Released 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 Released 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
[Touch-packages] [Bug 1556302] Re: Ubuntu patch to add HOME to env_keep makes custom commands vulnerable by default
@kibitih, please don't change the bug status without at least providing an upload or some kind of explanation ** Changed in: ubuntu-release-notes Status: Fix Committed => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1556302 Title: Ubuntu patch to add HOME to env_keep makes custom commands vulnerable by default Status in Release Notes for Ubuntu: Confirmed Status in sudo package in Ubuntu: Fix Released Status in sudo source package in Xenial: In Progress Status in sudo source package in Bionic: In Progress Status in sudo source package in Cosmic: Won't Fix Status in sudo source package in Disco: Won't Fix Status in sudo source package in Eoan: Fix Released Bug description: [impact] sudo does not set HOME to the target user's HOME [test case] ddstreet@thorin:~$ sudo printenv | grep HOME HOME=/home/ddstreet [regression potential] this is a significant behavior change. As mentioned in comment 11 (and later, and other bugs duped to this, and the mailing list discussion, etc) users of Ubuntu so far have been used to running sudo with their own HOME set, not root's HOME. Therefore, it's inappropriate to change this behavior for existing releases; this should be changed starting in Eoan, and only the sudo and sudoers man pages changed in previous releases to indicate the actual behavior of sudo in those releases. [other info] Shortly after upstream changed the behavior, the patch to keep HOME as the calling (instead of target) user was added in bug 760140. For quick reference to anyone coming to this bug, the pre-19.10 behavior (of sudo keeping the calling user's $HOME) can be disabled by running 'sudo visudo' and adding this line: Defaultsalways_set_home or, run sudo with the -H param. -- original description: -- I wanted to allow certain users to execute a python script as another user, so I created the following sudoers config: Defaults env_reset source_user ALL=(target_user) NOPASSWD: /home/target_user/bin/script.py This results in a highly insecure Python environment because the source user can set HOME and override any Python package by putting files in $HOME/.local/lib/python*/site-packages/. This should be a safe configuration because the default behaviour (as specified in the man page) is that env_reset will replace HOME with the target user's home directory. The "env_reset" option even has special behaviour for bash which has its own potential environment vulnerabilities. However there is an Ubuntu-specific patch in the package (keep_home_by_default.patch) that makes sudo preserve HOME by default, which negates the correct behaviour of "env_reset". It should not be necessary to explicitly specify the "always_set_home" option in order to negate this patch. The patch should be removed and the default /etc/sudoers should explicitly add HOME to "env_keep" for the "allow admins to run any command as root" entries, to get the desired behaviour without creating security issues for other sudoers commands. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1556302/+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 1938983] Re: missing modules after 5.11.0-25-generic update
This has been broken for nearly 3 months. Is a fix planned? -- 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/1938983 Title: missing modules after 5.11.0-25-generic update Status in initramfs-tools package in Ubuntu: Confirmed Bug description: After updating to kernel 5.11.0-25-generic wireless driver failed to recognize WiFi card. Possible reasons/symptoms: $ sudo update-initramfs -u -k all update-initramfs: Generating /boot/initrd.img-5.11.0-25-generic W: Possible missing firmware /lib/firmware/i915/skl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/bxt_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/glk_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/cml_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/icl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/ehl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/ehl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/dg1_dmc_ver2_02.bin for module i915 update-initramfs: Generating /boot/initrd.img-5.8.0-63-generic $ lsb_release -a LSB Version: core-11.1.0ubuntu2-noarch:security-11.1.0ubuntu2-noarch Distributor ID: Ubuntu Description: July2021 Release: 20.04 Codename: focal Workaround: connected Ethernet. (Inconvenient) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1938983/+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 1948698] Re: Update tzdata to version 2021e
Okay from the Ubuntu Security team for these tzdata updates to land in
security pockets. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1948698
Title:
Update tzdata to version 2021e
Status in tzdata package in Ubuntu:
In Progress
Status in tzdata source package in Bionic:
In Progress
Status in tzdata source package in Focal:
In Progress
Status in tzdata source package in Hirsute:
In Progress
Status in tzdata source package in Impish:
In Progress
Bug description:
New upstream version affecting the following timestamp:
$region/$timezone = Asia/Gaza
Verification is done with 'zdump'. The first timezone that gets
changed in the updated package is dumped with 'zdump -v
$region/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is
compared to the same output after the updated package got installed.
If those are different the verification is considered done.
[Test Case for all releases]
1) zdump -v Asia/Gaza 2021
For releases with ICU timezone data verification is done using the following
with dates before and after the change:
[Test Case for releases >= 20.04 LTS]
1) sudo apt-get install python3-icu
2) python3 -c 'from datetime import datetime; from icu import ICUtzinfo,
TimeZone; tz = ICUtzinfo(TimeZone.creat eTimeZone('Pacific/Apia'));
print(str(tz.utcoffset(datetime(2021, 9, 26'
Additionally, an upstream update of tzdata removed the 'old' SystemV
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS
and earlier releases. Subsequently, these should be checked for using
the following:
[Test Case for releases <= 20.04 LTS]
diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 |
cut -d' ' -f2-)
Nothing should be returned by the above command.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1948698/+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 349943] Re: Screen blinks randomly on external monitor
Oh, thanks for all of you reported this issue. I'm using Ubuntu20.04.2 now, and encountered the exactly same issue as you met about 12 years ago on Ubuntu9.04. It seems this is a very old bug in Ubuntu or linux bug on its HDMI driver. And because not so many people using external HDMI monitor, so this issue couldn't be paid attention to for linux/Ubuntu engineering team. -- 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/349943 Title: Screen blinks randomly on external monitor Status in xorg package in Ubuntu: Won't Fix Bug description: Hardware: Asus F8Va laptop (Core 2 Duo P8600, ATI HD3650, 1440x900) OS: Ubuntu 9.04 beta x64 (Wubi installation inside Windows Vista Home Premium x64 SP1) External monitor (Samsung SyncMaster 2493HM, 1920x1200), connected via HDMI, blinks several times a minute, randomly. When there is no user activity, it doesn't seem to blink however. By "blinking" I mean, the monitor goes off and then on, like it usually does when it changes resolution, only resolution doesn't change. Also, when I move windows around, thin horizontal stripes flash in fraction of second from time to time (only on external monitor). Screen configuration: Samsung 24": On Resolution: 1920x1200 Refresh rate: 60 Hz Rotation: Normal Laptop 14": On Resolution: 1440x900 Refresh rate: 67 Hz Rotation: Normal Mirror screens: unchecked Relative position of screens (physical and in Display Preferences) laptop screen below the external screen, centred. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/349943/+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 1694989] Re: apt-mark overwrites existing held package info
This was fixed in dpkg (1.20.6) unstable; urgency=medium [...] * libdpkg: Do not forget not-installed packages that are set on hold. Reported by David Kalnischkies . -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1694989 Title: apt-mark overwrites existing held package info Status in apt package in Ubuntu: Invalid Status in apt package in Debian: New Bug description: Running apt-mark hold commands overwrites / nullifies any existing held package data. Not sure if this is by design, but I assume it's meant to be cumulative. Ubuntu version: 16.04.2 LTS Package version: apt 1.2.19 amd64 Expected behaviour: apt-mark hold 3dchess apt-mark hold 0ad apt-mark showhold 3dchess 0ad Actual behaviour: apt-mark hold 3dchess apt-mark hold 0ad apt-mark showhold 0ad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1694989/+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 1694989] Re: apt-mark overwrites existing held package info
** Changed in: apt (Ubuntu) Status: Triaged => Won't Fix ** Changed in: apt (Ubuntu) Status: Won't Fix => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1694989 Title: apt-mark overwrites existing held package info Status in apt package in Ubuntu: Invalid Status in apt package in Debian: New Bug description: Running apt-mark hold commands overwrites / nullifies any existing held package data. Not sure if this is by design, but I assume it's meant to be cumulative. Ubuntu version: 16.04.2 LTS Package version: apt 1.2.19 amd64 Expected behaviour: apt-mark hold 3dchess apt-mark hold 0ad apt-mark showhold 3dchess 0ad Actual behaviour: apt-mark hold 3dchess apt-mark hold 0ad apt-mark showhold 0ad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1694989/+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 772121] Re: typo in pam_tally manpage
1.4.0-10ubuntu1 has been uploaded to jammy, which fixes this bug, but a wrong upload option prevents this bug from being autoclosed. Related changelog entry: pam (1.4.0-1) unstable; urgency=medium * New upstream release. Closes: #948188. - Stop using obsoleted selinux headers. Closes: #956355. - Continue building pam_cracklib, which is deprecated upstream; the replacement, pam_passwdqc, is packaged separately. - Update symbols file for new symbols. - Refresh lintian overrides for changes to available pam modules. * Drop patches to implement "nullok_secure" option for pam_unix. Closes: #674857, #936071, LP: #1860826. * debian/patches-applied/cve-2010-4708.patch: drop, applied upstream. * debian/patches-applied/nullok_secure-compat.patch: Support nullok_secure as a deprecated alias for nullok. * debian/pam-configs/unix: use nullok, not nullok_secure. * Drop pam_tally and pam_tally2 modules, which have been deprecated upstream in favor of pam_faillock. Closes: #569746, LP: #772121. * Add hardening+=bindnow to build options, per lintian. ** Changed in: pam (Ubuntu) Status: Confirmed => Fix Released -- 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/772121 Title: typo in pam_tally manpage Status in pam package in Ubuntu: Fix Released Status in pam package in Debian: Fix Released Bug description: The pam_tally manpage says "filed" where it should say "field". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/772121/+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 1694989] Re: apt-mark overwrites existing held package info
This is very annoying, I agree that either, apt-mark should not accept 'uninstalled' packages or we should avoid losing packages marked as 'hold' Steps to reproduce (assuming none of these two packages are available) Trying to mark as hold two uninstalled packages... and notice that the second we add the second one we lost the status for the first one.. > apt update > apt-mark hold p0f p0f set on hold. > apt-mark showhold p0f > grep -c p0f /var/lib/dpkg/status 1 > apt-mark hold dovecot-core dovecot-core set on hold. > apt-mark showhold dovecot-core > grep -c p0f /var/lib/dpkg/status 0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1694989 Title: apt-mark overwrites existing held package info Status in apt package in Ubuntu: Triaged Status in apt package in Debian: New Bug description: Running apt-mark hold commands overwrites / nullifies any existing held package data. Not sure if this is by design, but I assume it's meant to be cumulative. Ubuntu version: 16.04.2 LTS Package version: apt 1.2.19 amd64 Expected behaviour: apt-mark hold 3dchess apt-mark hold 0ad apt-mark showhold 3dchess 0ad Actual behaviour: apt-mark hold 3dchess apt-mark hold 0ad apt-mark showhold 0ad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1694989/+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 1563781] Re: Flickering and invisible mouse pointer after wakeup from suspend
** Changed in: lightdm Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1563781 Title: Flickering and invisible mouse pointer after wakeup from suspend Status in Light Display Manager: Invalid Status in lightdm package in Ubuntu: Expired Bug description: Hello, I run Arch linux on a Thinkpad X230 uname -a Linux schwarzbaer 4.4.5-1-ARCH #1 SMP PREEMPT Thu Mar 10 07:38:19 CET 2016 x86_64 GNU/Linux I use xmonad and a custom .xinitrc to start my session. I run `light- locker --lock-on-suspend` there and xmonad. - When I wake up my laptop from suspend, the login screen shows up as expected. - After about 2 second, the screen flickers once and the login screen shows up again. - If I start typing a password before the flickering, the input field will be reset upon flickering. Usually I end up with my password half-typed and a wrong password notice. - After logging back into the session, there is no mouse pointer. - Going to VT1 and back to VT7 restores the pointer. Please find the lightdm and journalctl logs below. I am happy to provide more logs and info. Thanks, Dominik The lightdm log: [+14840.86s] DEBUG: Seat seat0: Creating greeter session [+14840.86s] DEBUG: Seat seat0: Creating display server of type x [+14840.86s] DEBUG: Using VT 8 [+14840.86s] DEBUG: Seat seat0: Starting local X display on VT 8 [+14840.86s] DEBUG: DisplayServer x-1: Logging to /var/log/lightdm/x-1.log [+14840.86s] DEBUG: DisplayServer x-1: Writing X server authority to /run/lightdm/root/:1 [+14840.86s] DEBUG: DisplayServer x-1: Launching X Server [+14840.86s] DEBUG: Launching process 16458: /usr/sbin/X :1 -seat seat0 -auth /run/lightdm/root/:1 -nolisten tcp vt8 -novtswitch [+14840.86s] DEBUG: DisplayServer x-1: Waiting for ready signal from X server :1 [+14841.11s] DEBUG: Seat seat0 changes active session to [+14841.36s] DEBUG: Got signal 10 from process 16458 [+14841.36s] DEBUG: DisplayServer x-1: Got signal from X server :1 [+14841.36s] DEBUG: DisplayServer x-1: Connecting to XServer :1 [+14841.36s] DEBUG: Seat seat0: Display server ready, starting session authentication [+14841.36s] DEBUG: Session pid=16473: Started with service 'lightdm-greeter', username 'lightdm' [+14841.37s] DEBUG: Session pid=16473: Authentication complete with return value 0: Success [+14841.37s] DEBUG: Seat seat0: Session authenticated, running command [+14841.37s] DEBUG: Session pid=16473: Running command /usr/sbin/lightdm-gtk-greeter [+14841.37s] DEBUG: Creating shared data directory /var/lib/lightdm-data/lightdm [+14841.37s] DEBUG: Session pid=16473: Logging to /var/log/lightdm/x-1-greeter.log [+14841.41s] DEBUG: Activating VT 8 [+14841.41s] DEBUG: Locking login1 session c2 [+14841.41s] DEBUG: Activating login1 session c16 [+14841.41s] DEBUG: Seat seat0 changes active session to c16 [+14841.41s] DEBUG: Session c16 is already active [+14841.58s] DEBUG: Session pid=16473: Greeter connected version=1.16.7 resettable=false [+14841.76s] DEBUG: Session pid=16473: Greeter start authentication for dominik [+14841.76s] DEBUG: Session pid=16510: Started with service 'lightdm', username 'dominik' [+14841.77s] DEBUG: Session pid=16510: Got 1 message(s) from PAM [+14841.77s] DEBUG: Session pid=16473: Prompt greeter with 1 message(s) [+14846.18s] DEBUG: Session pid=16473: Continue authentication [+14846.20s] DEBUG: Session pid=16510: Authentication complete with return value 0: Success [+14846.20s] DEBUG: Session pid=16473: Authenticate result for user dominik: Success [+14846.20s] DEBUG: Session pid=16473: User dominik authorized [+14846.20s] DEBUG: Session pid=16473: Greeter sets language en_US.utf8 [+14846.26s] DEBUG: Session pid=16473: Greeter requests session xmonad-dominik [+14846.26s] DEBUG: Seat seat0: Returning to existing user session dominik [+14846.26s] DEBUG: Unlocking login1 session c2 [+14846.26s] DEBUG: Activating VT 7 [+14846.45s] DEBUG: Seat seat0: Stopping greeter [+14846.45s] DEBUG: Session pid=16473: Sending SIGTERM [+14846.45s] DEBUG: Activating login1 session c2 [+14846.46s] DEBUG: Session pid=16510: Exited with return value 0 [+14846.46s] DEBUG: Seat seat0: Session stopped [+14846.46s] DEBUG: Seat seat0 changes active session to c2 [+14846.46s] DEBUG: Session c2 is already active [+14846.50s] DEBUG: Session pid=16473: Greeter closed communication channel [+14846.50s] DEBUG: Session pid=16473: Exited with return value 0 [+14846.50s] DEBUG: Seat seat0: Session stopped [+14846.50s] DEBUG: Seat seat0: Stopping display server, no sessions require it [+14846.50s] DEBUG: Sending signal 15 to process 16458 [+14846.51s] DEBUG: Process 16458 exited with return value 0 [+14846.51s] DEBUG: DisplayServer x-1: X server stopped
[Touch-packages] [Bug 1933828] Re: NTP servers from DHCP are not propagated to timesyncd
was the issue reported and discussed upstream yet? those scripts added to the package sound like downstream workaround we will have to carry and should be a backup plan if the issue can't be properly fixed upstream. And even if a distro hack makes sense it would be better to have it in Debian to reduce or maintainance -- 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 1948813] [NEW] cant connect to second monitor
Public bug reported: I lost projecting to my second monitor while updating in ubuntu 20 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-89.100-generic 5.4.143 Uname: Linux 5.4.0-89-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/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 26 07:55:42 2021 DistUpgraded: 2021-10-15 08:30:35,667 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 5.4.0-89-generic, x86_64: installed nvidia, 470.74, 5.4.0-89-generic, x86_64: installed virtualbox, 6.1.26, 5.4.0-88-generic, x86_64: installed virtualbox, 6.1.26, 5.4.0-89-generic, x86_64: installed GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] UHD Graphics 630 (Mobile) [1025:1264] NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] [10de:1c8d] (rev ff) (prog-if ff) InstallationDate: Installed on 2021-09-21 (34 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) MachineType: Acer Nitro AN515-52 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic root=UUID=c4de9279-4774-410d-be28-7e7083e0c939 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2021-10-15 (10 days ago) dmi.bios.date: 08/05/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.28 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Freed_CFS dmi.board.vendor: CFL dmi.board.version: V1.28 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.28 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.28:bd08/05/2019:svnAcer:pnNitroAN515-52:pvrV1.28:rvnCFL:rnFreed_CFS:rvrV1.28:cvnAcer:ct10:cvrV1.28: dmi.product.family: Acer Nitro 5 dmi.product.name: Nitro AN515-52 dmi.product.sku: dmi.product.version: V1.28 dmi.sys.vendor: Acer 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 21.0.3-0ubuntu0.3~20.04.3 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 N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1948813 Title: cant connect to second monitor Status in xorg package in Ubuntu: New Bug description: I lost projecting to my second monitor while updating in ubuntu 20 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-89.100-generic 5.4.143 Uname: Linux 5.4.0-89-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/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 26 07:55:42 2021 DistUpgraded: 2021-10-15 08:30:35,667 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 5.4.0-89-generic, x86_64: installed nvidia, 470.74, 5.4.0-89-generic, x86_64: installed virtualbox, 6.1.26, 5.4.0-88-generic, x86_64: installed virtualbox, 6.1.26, 5.4.0-89-generic, x86_64: installed GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] UHD Graphics 630 (Mobile) [1025:1264] NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] [10de:1c8d] (rev ff) (prog-if ff) InstallationDate: Installed on 2021-09-21 (34 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) MachineType: Acer Nitro AN515-52 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic root=UUID=c4de9279-4774-410d-be28-7e7083e0c939 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2021-10-15 (10 days ago) dmi.bios.date: 08/05/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.28 dmi.board.asset.tag: Type2 - Board Serial Number
[Touch-packages] [Bug 1948805] Re: package linux-image-5.11.0-38-generic 5.11.0-38.42~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Thank you for taking the time to report this bug and helping to make Ubuntu better. Reviewing your dmesg attachment in this bug report it seems that there is a problem with your hardware. I recommend performing a back up and then investigating the situation. Measures you might take include checking cable connections and using software tools to investigate the health of your hardware. In the event that is is not in fact an error with your hardware please set the bug's status back to New. Thanks and good luck! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: hardware-error ** Changed in: initramfs-tools (Ubuntu) Importance: Undecided => Low ** Changed in: initramfs-tools (Ubuntu) Status: New => Invalid -- 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/1948805 Title: package linux-image-5.11.0-38-generic 5.11.0-38.42~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: Invalid Bug description: O linux não iniciava, o que me deu muita dor de cabeça. De início pensei que fosse um problema no boot, mas apertando as teclas alt + ctrl + 1 o sistema deu sinal de vida ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-38-generic 5.11.0-38.42~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Oct 26 08:59:26 2021 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2021-08-25 (61 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: initramfs-tools Title: package linux-image-5.11.0-38-generic 5.11.0-38.42~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1948805/+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 1948806] [NEW] [SRU] Enable support for Yoga Cloud Archive
Public bug reported: Please add support for: cloud-archive:yoga cloud-archive:yoga-proposed This will also need to be SRU'd back to focal. [Impact] End users have to manually enable the yoga cloud archive pockets. [Test case] sudo add-apt-repository cloud-archive:yoga sudo add-apt-repository cloud-archive:yoga-proposed [Regression potential] Limited - just a data item addition ** Affects: software-properties (Ubuntu) Importance: Medium Status: Triaged ** Affects: software-properties (Ubuntu Focal) Importance: Medium Status: Triaged ** Affects: software-properties (Ubuntu Jammy) Importance: Medium Status: Triaged ** Also affects: software-properties (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: software-properties (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: software-properties (Ubuntu Focal) Status: New => Triaged ** Changed in: software-properties (Ubuntu Jammy) Status: New => Triaged ** Changed in: software-properties (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: software-properties (Ubuntu Jammy) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1948806 Title: [SRU] Enable support for Yoga Cloud Archive Status in software-properties package in Ubuntu: Triaged Status in software-properties source package in Focal: Triaged Status in software-properties source package in Jammy: Triaged Bug description: Please add support for: cloud-archive:yoga cloud-archive:yoga-proposed This will also need to be SRU'd back to focal. [Impact] End users have to manually enable the yoga cloud archive pockets. [Test case] sudo add-apt-repository cloud-archive:yoga sudo add-apt-repository cloud-archive:yoga-proposed [Regression potential] Limited - just a data item addition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1948806/+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 1948805] [NEW] package linux-image-5.11.0-38-generic 5.11.0-38.42~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: O linux não iniciava, o que me deu muita dor de cabeça. De início pensei que fosse um problema no boot, mas apertando as teclas alt + ctrl + 1 o sistema deu sinal de vida ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-38-generic 5.11.0-38.42~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Oct 26 08:59:26 2021 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2021-08-25 (61 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: initramfs-tools Title: package linux-image-5.11.0-38-generic 5.11.0-38.42~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- 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/1948805 Title: package linux-image-5.11.0-38-generic 5.11.0-38.42~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: O linux não iniciava, o que me deu muita dor de cabeça. De início pensei que fosse um problema no boot, mas apertando as teclas alt + ctrl + 1 o sistema deu sinal de vida ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-38-generic 5.11.0-38.42~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Oct 26 08:59:26 2021 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2021-08-25 (61 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: initramfs-tools Title: package linux-image-5.11.0-38-generic 5.11.0-38.42~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1948805/+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"
This bug was fixed in the package util-linux - 2.36.1-8ubuntu2 --- util-linux (2.36.1-8ubuntu2) impish; urgency=medium * Fix HiFive partition names (LP: #1944741) - include: Rename HiFive partition UUIDs - po: Update translations after changes to HiFive partition names -- Alexandre Ghiti Thu, 23 Sep 2021 16:07:01 +0200 ** Changed in: util-linux (Ubuntu Impish) Status: Fix Committed => 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 Released 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
[Touch-packages] [Bug 1944741] Update Released
The verification of the Stable Release Update for util-linux 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 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 Released 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:
[Touch-packages] [Bug 1948752] Re: apparmor is logging too many messages
The /usr/bin/redshift profile needs some additional dbus rules. ** Also affects: redshift Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1948752 Title: apparmor is logging too many messages Status in Redshift: New Status in apparmor package in Ubuntu: New Bug description: Unfortunately, this bug does not seem to be fixed yet. My syslog is flooded with ALLOWED messages regarding redshift. My system is a Kubuntu 21.04. AppArmor is V. 3.0.0-0ubuntu7.1 Attached you'll find an excerpt from /var/log/syslog for the last 5 minutes. To manage notifications about this bug go to: https://bugs.launchpad.net/redshift/+bug/1948752/+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 1941752]
Created attachment 142865 New crash information added by DrKonqi gwenview (21.08.1) using Qt 5.15.2 Gwenview crashed when trying to open a jpg. The images in question were saved by Darktable from Canon Raw images, and ranged in size from 8.2 to 16.4 MiB. -- Backtrace (Reduced): #4 __pthread_kill_implementation (no_tid=0, signo=6, threadid=139626298358848) at pthread_kill.c:44 #5 __pthread_kill_internal (signo=6, threadid=139626298358848) at pthread_kill.c:80 #6 __GI___pthread_kill (threadid=139626298358848, signo=signo@entry=6) at pthread_kill.c:91 #7 0x7efd4d5d6476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x7efd4d5bc7b7 in __GI_abort () at abort.c:79 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1941752 Title: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable Status in Gwenview: Unknown Status in exiv2 package in Ubuntu: Confirmed Status in gwenview package in Ubuntu: Confirmed Bug description: Since the recent security update of exiv2, Gwenview crashes when trying to open image files that got exported by darktable. Steps to reproduce: * Make a test installation of Kubuntu 21.04 in VirtualBox * Install all updates * Install darktable * Copy one of the images in /usr/share/wallpapers (or any other image) to your home directory and open it with darktable * Within darktable, export a copy of the image (no need to do any actual modifications) * Try to open that copy with Gwenview. Gwenview will crash. I'm attaching a crash report hinting that this is related to exiv2. Temporary workaround: If I downgrade libexiv2-27 to 0.27.3-3ubuntu1.4, Gwenview doesn't crash, so it seems the crash is related to changes in 0.27.3-3ubuntu1.5. I don't know if the underlying cause is actually some bug in exiv2, Gwenview or darktable. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: libexiv2-27 0.27.3-3ubuntu1.5 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Aug 26 15:16:47 2021 InstallationDate: Installed on 2021-08-26 (0 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: exiv2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gwenview/+bug/1941752/+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-2ubuntu5 --- alsa-ucm-conf (1.2.4-2ubuntu5) impish; urgency=medium * d/p/0008-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 10:54:28 +0800 ** Changed in: alsa-ucm-conf (Ubuntu Impish) 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 Released 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
[Touch-packages] [Bug 1948729] Re: ubuntu-bug bleeds username into Launchpad comments making it impossible to redact
** Changed in: apport (Ubuntu) Status: Incomplete => New -- 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/1948729 Title: ubuntu-bug bleeds username into Launchpad comments making it impossible to redact Status in apport package in Ubuntu: New Bug description: Reporting a bug using ubuntu-bug invariably seems to attach my system username to the bug description. If I try to edit that description in order to remove the username, it succeeds, but I'm not informed that every version of the description is being saved and published publicly for anyone, making all edits useless for the sake of privacy. I now have only one choice if I want to not disclose my system username: don't use ubuntu-bug anymore for any bug reporting. Also it means I'd have to mark already reported bugs as Private, which more often than not informs me that it will be visible to no one... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1948729/+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
