[Touch-packages] [Bug 1943561] Re: Add ACCEL_LOCATION=base property for 6 Dell clamshell models
** Changed in: systemd (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1943561 Title: Add ACCEL_LOCATION=base property for 6 Dell clamshell models Status in OEM Priority Project: New Status in systemd package in Ubuntu: New Bug description: This hwdb update is to avoid unwanted screen rotation when tilting the laptop. This is the update to the previously rolled back SRU LP: #1938259 [Impact] * This fixes unwanted rotations on certain Dell clamshell laptop models with accelerometer. [Test Plan] * On Dell laptops with model SKU 0A36, 0A3E, 0B09, 0B0B, 0B0D, 0B11, install this package and ensure the kernel is updated to the latest. * Screen should be correct side up in login screen and desktop. * Tilt the laptop and the screen should not be rotated. [Where problems could occur] * This is to add parameters for certain models in hwdb, and does not affect any other part of systemd. * Only models with the same Dell SKU would be affected. [scope] this is needed for all releases this is being added to upstream by https://github.com/systemd/systemd/pull/20314 and https://github.com/systemd/systemd/pull/20661 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1943561/+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 1943859] Re: The development package does not include static libraries
** Also affects: pango1.0 (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994752 Importance: Unknown Status: Unknown ** Changed in: pango1.0 (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1943859 Title: The development package does not include static libraries Status in pango1.0 package in Ubuntu: New Status in pango1.0 package in Debian: Unknown Bug description: The development package for pango (libpango1.0-dev) does not include static libraries so it is not possible to link these libraries statically. See attached patch with the fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1943859/+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 1944404] [NEW] [HDA-Intel - HDA NVidia, playback] No sound at all
Public bug reported: Hi...my problem is that I am using the nVidia GTX card connected by HDMI cable to a widescreen Samsung monitor that doesn't have speakers. Ubuntu assumes I can use that to play audio. In reality I'm using stereo speakers connected to the "center" output from the rear of the computer. This works fine in windows, but not in Ubuntu 20.04. I've tried several fixes to similar looking issues on line, but still I don't get sound. The only option I have under settings is for the HDMI/DisplayPort 2 - GM107 High Definition audio controller [GE Force 940 MX]. I've tried an old solution by adding hdajackretask and I've tried adjusting volume levels using alsamixer, but those solutions didn't help. Anyone have any other ideas? Thanks in advance. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: larry 11338 F pulseaudio /dev/snd/controlC2: larry 11338 F pulseaudio /dev/snd/controlC1: larry 11338 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Sep 20 23:05:52 2021 PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed Symptom_Card: GM107 High Definition Audio Controller [GeForce 940MX] - HDA NVidia Symptom_Type: No sound at all Title: [HDA-Intel - HDA NVidia, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/31/2019 dmi.bios.release: 64.14 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0KWVT8 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd05/31/2019:br64.14:svnDellInc.:pnXPS8700:pvr:sku0x05B7:rvnDellInc.:rn0KWVT8:rvrA03:cvnDellInc.:ct3:cvr: dmi.product.family: To be filled by O.E.M. dmi.product.name: XPS 8700 dmi.product.sku: 0x05B7 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1944404 Title: [HDA-Intel - HDA NVidia, playback] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Hi...my problem is that I am using the nVidia GTX card connected by HDMI cable to a widescreen Samsung monitor that doesn't have speakers. Ubuntu assumes I can use that to play audio. In reality I'm using stereo speakers connected to the "center" output from the rear of the computer. This works fine in windows, but not in Ubuntu 20.04. I've tried several fixes to similar looking issues on line, but still I don't get sound. The only option I have under settings is for the HDMI/DisplayPort 2 - GM107 High Definition audio controller [GE Force 940 MX]. I've tried an old solution by adding hdajackretask and I've tried adjusting volume levels using alsamixer, but those solutions didn't help. Anyone have any other ideas? Thanks in advance. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: larry 11338 F pulseaudio /dev/snd/controlC2: larry 11338 F pulseaudio /dev/snd/controlC1: larry 11338 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Sep 20 23:05:52 2021 PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed Symptom_Card: GM107 High Definition Audio Controller [GeForce 940MX] - HDA NVidia Symptom_Type: No sound at all Title: [HDA-Intel - HDA NVidia, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/31/2019 dmi.bios.release: 64.14 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0KWVT8 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd05/31/2019:br64.14:svnDellInc.:pnXPS8700:pvr:sku0x05B7:rvnDellInc.:rn0KWVT8:rv
[Touch-packages] [Bug 1937178] Re: package util-linux 2.27.1-6ubuntu3.10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
[Expired for util-linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: util-linux (Ubuntu) Status: Incomplete => Expired -- 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/1937178 Title: package util-linux 2.27.1-6ubuntu3.10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in util-linux package in Ubuntu: Expired Bug description: while updating using software update show this error. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: util-linux 2.27.1-6ubuntu3.10 ProcVersionSignature: Ubuntu 4.15.0-142.146~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-142-generic i686 ApportVersion: 2.20.1-0ubuntu2.30 Architecture: i386 Date: Thu Jul 22 12:54:08 2021 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2019-01-26 (907 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release i386 (20180731) RelatedPackageVersions: dpkg 1.18.4ubuntu1.7 apt 1.2.32ubuntu0.2 SourcePackage: util-linux Title: package util-linux 2.27.1-6ubuntu3.10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1937178/+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 1940505] Re: monero FTBFS on riscv64
This bug was fixed in the package monero - 0.17.2.0+~0+20200826-1ubuntu2 --- monero (0.17.2.0+~0+20200826-1ubuntu2) impish; urgency=medium * Build with -O1 on riscv64 to avoid link error (LP: #1940505) * Limit parallelism only on certain architectures -- Graham Inggs Mon, 20 Sep 2021 16:11:23 + ** Changed in: monero (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1940505 Title: monero FTBFS on riscv64 Status in binutils: Fix Released Status in binutils package in Ubuntu: New Status in monero package in Ubuntu: Fix Released Bug description: monero FTBFS on riscv64 due to toolchain issues: [ 64%] Linking CXX executable signature_fuzz_tests cd "/<>/obj-riscv64-linux-gnu/tests/fuzz" && /usr/bin/cmake -E cmake_link_script CMakeFiles/signature_fuzz_tests.dir/link.txt --verbose=1 /usr/bin/c++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -DNO_AES -fno-strict-aliasing -std=c++11 -D_GNU_SOURCE -Wall -Wextra -Wpointer-arith -Wundef -Wvla -Wwrite-strings -Wno-error=extra -Wno-error=deprecated-declarations -Wno-unused-parameter -Wno-unused-variable -Wno-error=unused-variable -Wno-error=undef -Wno-error=uninitialized -Wlogical-op -Wno-error=maybe-uninitialized -Wno-error=cpp -Wno-reorder -Wno-missing-field-initializers -fPIC -Wformat -Wformat-security -fstack-protector -fstack-protector-strong -fstack-clash-protection -fno-strict-aliasing -ftemplate-depth=900 -Wl,-Bsymbolic-functions -Wl,-z,relro -pie -Wl,-z,relro -Wl,-z,now -Wl,-z,noexecstack -rdynamic CMakeFiles/signature_fuzz_tests.dir/signature.cpp.o CMakeFiles/signature_fuzz_tests.dir/fuzzer.cpp.o -o signature_fuzz_tests ../../lib/libwallet.a ../../src/cryptonote_core/libcryptonote_core.a ../../src/p2p/libp2p.a ../../contrib/epee/src/libepee.a ../../src/device/libdevice.a -Wl,-Bstatic -lrt -Wl,-Bdynamic -ldl ../../src/rpc/librpc_base.a ../../src/mnemonics/libmnemonics.a ../../src/device_trezor/libdevice_trezor.a ../../src/cryptonote_core/libcryptonote_core.a ../../src/multisig/libmultisig.a ../../src/blockchain_db/libblockchain_db.a ../../external/db_drivers/liblmdb/liblmdb.a ../../src/ringct/libringct.a ../../src/cryptonote_basic/libcryptonote_basic.a ../../src/device/libdevice.a -lhidapi-libusb ../../src/ringct/libringct_basic.a ../../src/blocks/libblocks.a ../../src/checkpoints/libcheckpoints.a ../../src/hardforks/libhardforks.a ../../src/net/libnet.a ../../src/common/libcommon.a ../../src/crypto/libcncrypto.a ../../contrib/epee/src/libepee.a ../../external/easylogging++/libeasylogging.a -lrandomx -lunbound -lboost_regex -lboost_date_time -lssl -lcrypto -lzmq -lpgm -lnorm -lgssapi_krb5 -lsodium ../../src/libversion.a -lminiupnpc -lboost_chrono -lboost_serialization -lboost_filesystem -lboost_system -lboost_thread -lboost_program_options -Wl,-Bstatic -lrt -Wl,-Bdynamic -ldl -latomic ../../external/db_drivers/liblmdb/liblmdb.a(mdb.c.o): in function `mdb_node_add': ./obj-riscv64-linux-gnu/external/db_drivers/liblmdb/./external/db_drivers/liblmdb/mdb.c:8245:(.text+0x44e6): relocation truncated to fit: R_RISCV_JAL against `mdb_assert_fail.constprop.0' collect2: error: ld returned 1 exit status make[3]: *** [tests/fuzz/CMakeFiles/signature_fuzz_tests.dir/build.make:166: tests/fuzz/signature_fuzz_tests] Error 1 make[3]: Leaving directory '/<>/obj-riscv64-linux-gnu' make[2]: *** [CMakeFiles/Makefile2:4165: tests/fuzz/CMakeFiles/signature_fuzz_tests.dir/all] Error 2 make[2]: Leaving directory '/<>/obj-riscv64-linux-gnu' make[1]: *** [Makefile:163: all] Error 2 make[1]: Leaving directory '/<>/obj-riscv64-linux-gnu' dh_auto_build: error: cd obj-riscv64-linux-gnu && make -j1 "INSTALL=install --strip-program=true" VERBOSE=1 returned exit code 2 make: *** [debian/rules:47: binary-arch] Error 25 dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/1940505/+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 1944122] Re: GUI crash
*** This bug is a duplicate of bug 1939417 *** https://bugs.launchpad.net/bugs/1939417 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1939417, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Summary changed: - Xorg crash + GUI crash ** This bug has been marked a duplicate of bug 1939417 Ubuntu GUI crashes (w and w/o Wayland), VM_L2_PROTECTION_FAULT, amdgpu :09:00.0: [gfxhub0] retry page fault -- 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/1944122 Title: GUI crash Status in xorg package in Ubuntu: New Bug description: in the middle of working the GUI crashed (mouse movements yes, no klicks possible) came back, crashed again, login screen appeared. Clearly an issue with AMD-GPU as dmesg states. This report was only possible via ssh from a different machine. Distributor ID: Ubuntu Description: Ubuntu 21.04 Release: 21.04 Codename: hirsute Linux peter 5.14.0-051400drmtip20210904-generic #202109040225 SMP Sat Sep 4 02:34:06 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 Uname: Linux 5.14.0-051400drmtip20210904-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.11-0ubuntu65.3 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Sep 20 14:26:27 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: vhba, 20210418, 5.11.0-34-generic, x86_64: installed vhba, 20210418, 5.11.0-35-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] InstallationDate: Installed on 2020-12-16 (278 days ago) InstallationMedia: Ubuntu 16.04.7 LTS "Xenial Xerus" - Release amd64 (20200806) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.14.0-051400drmtip20210904-generic root=UUID=54c9f67c-180d-4545-8531-aef138dc5e0a ro SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: Section "InputClass" Identifier "middle button emulation class" MatchIsPointer "on" Option "Emulate3Buttons" "on" EndSection dmi.bios.date: 06/18/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.20 dmi.board.name: B450 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.20:bd06/18/2020:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:rvnASRock:rnB450Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. mtime.conffile..etc.apport.crashdb.conf: 2021-08-13T12:52:00.669929 version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4 version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 xserver.bootTime: Mon Sep 20 14:25:30 2021 xserver.configfile: /etc/X11/xorg.conf xserver.errors: AMDGPU(0): Failed to make import prime FD as pixmap: 22 xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.11-1ubuntu1.1 xserver.video_driver: amdgpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1944122/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchp
[Touch-packages] [Bug 1944398] [NEW] [Bluetooth Headset, playback] auto_switch=2 doesn't work with Discord
Public bug reported: I am having a problem connecting a bluetooth headset as HSP/HFP (headset_head_unit). It seems that the only way to use my headset as an HSP/HFP device is to set module-bluetooth-policy auto_switch=2, as A2DP is the hard-coded default. It's hard to find information because of the overwhelming number of issues people have had getting HSP/HFP to work in the first place. auto_switch=2 does switch the protocol to HSP/HFP, but in such a way that Discord does not recognize that the device is connected any longer. If I manually switch my headset to HSP/HFP before joining a voicechat channel, everything works as expected, but I can find no way to default my headset to HSP/HFP. Steps to reproduce: Open Discord, having previously set input/output to Bluetooth device Connect Bluetooth headset Join Voice Chat Expected result: Bluetooth unit sets profile to HSP/HFP Discord outputs and inputs via the headset Actual result: Bluetooth unit sets profile to "off" No output or input through Discord ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-84.94-lowlatency 5.4.133 Uname: Linux 5.4.0-84-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: hukt 2399 F pulseaudio /dev/snd/controlC0: hukt 2399 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Mon Sep 20 21:36:10 2021 InstallationDate: Installed on 2020-04-27 (511 days ago) InstallationMedia: Ubuntu-Studio 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: M98 Symptom_Type: None of the above Title: [M98, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/18/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0910 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V LE PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0910:bd03/18/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLEPLUS:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1944398 Title: [Bluetooth Headset, playback] auto_switch=2 doesn't work with Discord Status in alsa-driver package in Ubuntu: New Bug description: I am having a problem connecting a bluetooth headset as HSP/HFP (headset_head_unit). It seems that the only way to use my headset as an HSP/HFP device is to set module-bluetooth-policy auto_switch=2, as A2DP is the hard-coded default. It's hard to find information because of the overwhelming number of issues people have had getting HSP/HFP to work in the first place. auto_switch=2 does switch the protocol to HSP/HFP, but in such a way that Discord does not recognize that the device is connected any longer. If I manually switch my headset to HSP/HFP before joining a voicechat channel, everything works as expected, but I can find no way to default my headset to HSP/HFP. Steps to reproduce: Open Discord, having previously set input/output to Bluetooth device Connect Bluetooth headset Join Voice Chat Expected result: Bluetooth unit sets profile to HSP/HFP Discord outputs and inputs via the headset Actual result: Bluetooth unit sets profile to "off" No output or input through Discord ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-84.94-lowlatency 5.4.133 Uname: Linux 5.4.0-84-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: hukt 2399 F pulseaudio /dev/snd/controlC0: hukt 2399 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Mon Sep 20 21:36:10 2021 InstallationDate: Installed on 2020-04-27 (511 days ago) InstallationMedia: Ubuntu-Studio 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: M98 Symptom_Type: None of the above Title: [M98,
[Touch-packages] [Bug 304393] Re: rpcbind grabs ports used by other daemons such as cupsd
** Changed in: fedora Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/304393 Title: rpcbind grabs ports used by other daemons such as cupsd Status in cups package in Ubuntu: Invalid Status in rpcbind package in Ubuntu: Fix Released Status in rpcbind source package in Xenial: Fix Released Status in rpcbind source package in Bionic: Fix Released Status in rpcbind package in Debian: Fix Released Status in Fedora: Won't Fix Bug description: [impact] rpcbind binds to a 'random' reserved port at startup, which can conflict with the reserved port number for other applications that actually 'own' the reserved port number. One example is cups, which uses the reserved port 631. This prevents the actual 'owner' of the reserved port from starting, since it can't bind to its reserved port. Additionally, this can raise alarms from security monitoring software that does not expect programs to be listening on random reserved ports. [test case] start rpcbind and check which ports it is listening on, e.g.: $ sudo netstat --inet -p -l | grep rpcbind | grep -v sunrpc udp0 0 0.0.0.0:614 0.0.0.0:* 4678/rpcbind each time rpcbind is restarted, it will be listening to a different 'random' port. [regression potential] this adds a way to disable rpcbind from listening to the 'random' port. any regression would likely prevent rpcbind from starting, or may cause problems with the interaction between rpcinfo and rpcbind, as rpcinfo may use the random reserved port in some cases, as detailed in the Debian bug. [scope] This is needed only for Bionic and earlier. In Focal and later, and in Debian, rpcbind defaults to not opening the random reserved port. The admin can use the -r parameter to cause rpcbind to restore the old behavior of opening the random reserved port. [other info] Note that the -r parameter is a Debian addition, and the upstream rpcbind has disabled the random port functionality at build time; there is no runtime parameter to allow the admin to choose the behavior. Also, as discussed in the Debian bug, disabling this rpcbind 'feature' is known to cause problems for the rpcinfo program, which is why Debian introduced the -r parameter. So, when this -r parameter is backported to Bionic and earlier, we must retain the default behavior for those releases, which is for rpcbind to open the random reserved port. Thus, the patch for this will first backport the upstream patch that adds functionality to be able to disable the 'remote calls' function, and also backports the debian patch to change that from a compile-time to run-time option. Then, another patch is added, which changes the default back to the behavior of x/b, which is for remote calls to be enabled by default, and also adds a check for the existence of an environment variable "RPCBIND_RMTCALL_DEFAULT_DISABLED" which, if defined (to anything), will change the default to disabled. This allows 1) retaining the existing default behavior of rpcbind in x and b, while also 2) providing a mechanism to change that default for anyone who does *not* want remote calls to be enabled, and 3) allowing the mechanism to change the default to remain in place after an upgrade to Focal. Using the environment variable allows anyone to disable the remote calls in x and/or b, and then upgrade to Focal without breaking rpcbind or needing to remove the env var. After the upgrade to Focal, the environment variable (defined in /etc/default/rpcbind and/or /etc/rpcbind.conf) will simply be ignored without any change needed to the rpcbind package in Focal or later. [original description] Binary package hint: cups cups 1.3.9-2ubuntu4 From /var/log/cups/error_log: cups: unable to bind socket for address 127.0.0.1:631 - Address already in use. Nothing actually looks wrong. 127.0.0.1:631 is only in use by cupsd when started. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/304393/+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 304393]
We are tracking this upstream. It is unclear whether bindresvport will remain as a public API in glibc. So far, it has not been subject to the Sun RPC transition in glibc, although libtirpc implements the symbol as well. It may therefore be possible to turn the glibc symbol in to a compat symbol, effectively removing it from the glibc API. In this case, it is unlikely that upstream will implement a denylist, similar to what is available in libtirpc today. Applications built on Red Hat Enterprise Linux 8 can already use the libtirpc denylist functionality for bindresvport by linking against libtirpc. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/304393 Title: rpcbind grabs ports used by other daemons such as cupsd Status in cups package in Ubuntu: Invalid Status in rpcbind package in Ubuntu: Fix Released Status in rpcbind source package in Xenial: Fix Released Status in rpcbind source package in Bionic: Fix Released Status in rpcbind package in Debian: Fix Released Status in Fedora: Won't Fix Bug description: [impact] rpcbind binds to a 'random' reserved port at startup, which can conflict with the reserved port number for other applications that actually 'own' the reserved port number. One example is cups, which uses the reserved port 631. This prevents the actual 'owner' of the reserved port from starting, since it can't bind to its reserved port. Additionally, this can raise alarms from security monitoring software that does not expect programs to be listening on random reserved ports. [test case] start rpcbind and check which ports it is listening on, e.g.: $ sudo netstat --inet -p -l | grep rpcbind | grep -v sunrpc udp0 0 0.0.0.0:614 0.0.0.0:* 4678/rpcbind each time rpcbind is restarted, it will be listening to a different 'random' port. [regression potential] this adds a way to disable rpcbind from listening to the 'random' port. any regression would likely prevent rpcbind from starting, or may cause problems with the interaction between rpcinfo and rpcbind, as rpcinfo may use the random reserved port in some cases, as detailed in the Debian bug. [scope] This is needed only for Bionic and earlier. In Focal and later, and in Debian, rpcbind defaults to not opening the random reserved port. The admin can use the -r parameter to cause rpcbind to restore the old behavior of opening the random reserved port. [other info] Note that the -r parameter is a Debian addition, and the upstream rpcbind has disabled the random port functionality at build time; there is no runtime parameter to allow the admin to choose the behavior. Also, as discussed in the Debian bug, disabling this rpcbind 'feature' is known to cause problems for the rpcinfo program, which is why Debian introduced the -r parameter. So, when this -r parameter is backported to Bionic and earlier, we must retain the default behavior for those releases, which is for rpcbind to open the random reserved port. Thus, the patch for this will first backport the upstream patch that adds functionality to be able to disable the 'remote calls' function, and also backports the debian patch to change that from a compile-time to run-time option. Then, another patch is added, which changes the default back to the behavior of x/b, which is for remote calls to be enabled by default, and also adds a check for the existence of an environment variable "RPCBIND_RMTCALL_DEFAULT_DISABLED" which, if defined (to anything), will change the default to disabled. This allows 1) retaining the existing default behavior of rpcbind in x and b, while also 2) providing a mechanism to change that default for anyone who does *not* want remote calls to be enabled, and 3) allowing the mechanism to change the default to remain in place after an upgrade to Focal. Using the environment variable allows anyone to disable the remote calls in x and/or b, and then upgrade to Focal without breaking rpcbind or needing to remove the env var. After the upgrade to Focal, the environment variable (defined in /etc/default/rpcbind and/or /etc/rpcbind.conf) will simply be ignored without any change needed to the rpcbind package in Focal or later. [original description] Binary package hint: cups cups 1.3.9-2ubuntu4 From /var/log/cups/error_log: cups: unable to bind socket for address 127.0.0.1:631 - Address already in use. Nothing actually looks wrong. 127.0.0.1:631 is only in use by cupsd when started. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/304393/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packa
[Touch-packages] [Bug 304393]
I filed bug 1854147 against libtirpc with the denylist additions suggested in comment 0. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/304393 Title: rpcbind grabs ports used by other daemons such as cupsd Status in cups package in Ubuntu: Invalid Status in rpcbind package in Ubuntu: Fix Released Status in rpcbind source package in Xenial: Fix Released Status in rpcbind source package in Bionic: Fix Released Status in rpcbind package in Debian: Fix Released Status in Fedora: Won't Fix Bug description: [impact] rpcbind binds to a 'random' reserved port at startup, which can conflict with the reserved port number for other applications that actually 'own' the reserved port number. One example is cups, which uses the reserved port 631. This prevents the actual 'owner' of the reserved port from starting, since it can't bind to its reserved port. Additionally, this can raise alarms from security monitoring software that does not expect programs to be listening on random reserved ports. [test case] start rpcbind and check which ports it is listening on, e.g.: $ sudo netstat --inet -p -l | grep rpcbind | grep -v sunrpc udp0 0 0.0.0.0:614 0.0.0.0:* 4678/rpcbind each time rpcbind is restarted, it will be listening to a different 'random' port. [regression potential] this adds a way to disable rpcbind from listening to the 'random' port. any regression would likely prevent rpcbind from starting, or may cause problems with the interaction between rpcinfo and rpcbind, as rpcinfo may use the random reserved port in some cases, as detailed in the Debian bug. [scope] This is needed only for Bionic and earlier. In Focal and later, and in Debian, rpcbind defaults to not opening the random reserved port. The admin can use the -r parameter to cause rpcbind to restore the old behavior of opening the random reserved port. [other info] Note that the -r parameter is a Debian addition, and the upstream rpcbind has disabled the random port functionality at build time; there is no runtime parameter to allow the admin to choose the behavior. Also, as discussed in the Debian bug, disabling this rpcbind 'feature' is known to cause problems for the rpcinfo program, which is why Debian introduced the -r parameter. So, when this -r parameter is backported to Bionic and earlier, we must retain the default behavior for those releases, which is for rpcbind to open the random reserved port. Thus, the patch for this will first backport the upstream patch that adds functionality to be able to disable the 'remote calls' function, and also backports the debian patch to change that from a compile-time to run-time option. Then, another patch is added, which changes the default back to the behavior of x/b, which is for remote calls to be enabled by default, and also adds a check for the existence of an environment variable "RPCBIND_RMTCALL_DEFAULT_DISABLED" which, if defined (to anything), will change the default to disabled. This allows 1) retaining the existing default behavior of rpcbind in x and b, while also 2) providing a mechanism to change that default for anyone who does *not* want remote calls to be enabled, and 3) allowing the mechanism to change the default to remain in place after an upgrade to Focal. Using the environment variable allows anyone to disable the remote calls in x and/or b, and then upgrade to Focal without breaking rpcbind or needing to remove the env var. After the upgrade to Focal, the environment variable (defined in /etc/default/rpcbind and/or /etc/rpcbind.conf) will simply be ignored without any change needed to the rpcbind package in Focal or later. [original description] Binary package hint: cups cups 1.3.9-2ubuntu4 From /var/log/cups/error_log: cups: unable to bind socket for address 127.0.0.1:631 - Address already in use. Nothing actually looks wrong. 127.0.0.1:631 is only in use by cupsd when started. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/304393/+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 1941799] Re: Please merge openssh 1:8.4p1-6 from Debian unstable
Actually, a feature of openssh is being able to use a chroot that doesn't look like a root filesystem, so we'll have to consider how to move forward on this. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1941799 Title: Please merge openssh 1:8.4p1-6 from Debian unstable Status in openssh package in Ubuntu: In Progress Bug description: This merge is needed because there are changes in Ubuntu that are not present in Debian. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1941799/+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 1941799] Re: Please merge openssh 1:8.4p1-6 from Debian unstable
Mounting /proc in the chroot fixed the test. I'll prepare a patch and an upstream bug report. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1941799 Title: Please merge openssh 1:8.4p1-6 from Debian unstable Status in openssh package in Ubuntu: In Progress Bug description: This merge is needed because there are changes in Ubuntu that are not present in Debian. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1941799/+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 1917148] Update Released
The verification of the Stable Release Update for procps 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 procps in Ubuntu. https://bugs.launchpad.net/bugs/1917148 Title: ps version is UNKNOWN in procps 2:3.3.16-1ubuntu2 Status in procps package in Ubuntu: Fix Released Status in procps source package in Bionic: Fix Released Status in procps source package in Focal: Fix Released Status in procps source package in Hirsute: Fix Released Status in procps source package in Impish: Fix Released Bug description: [Impact] * Breakage of tools expecting the version number or the number to substantially match the Debian package version. * May confuse users expecting the version to substantially match the Debian package version. * Restores behavior to that provided in Groovy/Hirsute+ and Bionic and prior releases. - Focal is the only release affected. * Backported Debian fix to restore ".tarball-version" file to provide version information during build. - Also included the autopkgtests for versioning from the same Debian fix. [Test Plan] 1) Create a Focal (or derived from Focal) system. 2) Execute "ps --version" or any of the binaries provided by the package with their respective version flags. 3) Instead of desired output of the version, the output is: the invoked binary name followed by "from procps-ng UNKNOWN" Example: "ps from procps-ng UNKNOWN" [Where problems could occur] * This fix could cause issues if applications have come to depend on the incorrect behavior. IE, an application that uses a version string of "UNKNOWN" as part of a heuristic for identifying a Focal system. * If the version of procps-ng is incremented, this patch would need to be updated or removed if it is no longer relevant. Otherwise, an incorrect version would be reported by the binaries. [Other Info] * This change is in Groovy+ and Debian packaging with the same version of procps-ng. - Introduced in procps (2:3.3.16-5) unstable in Debian. [Original Description] From Linux Lint 20.1, so Focal Fossa 20.04.1 Package procps 2:3.3.16-1ubuntu2 $ LANG=C ps --version ps from procps-ng UNKNOWN I don't know if it comes from Ubuntu or upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1917148/+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 1917148] Re: ps version is UNKNOWN in procps 2:3.3.16-1ubuntu2
This bug was fixed in the package procps - 2:3.3.16-1ubuntu2.3 --- procps (2:3.3.16-1ubuntu2.3) focal; urgency=medium * Fixes version output of utilities (LP: #1917148) - d/p/fix_version.patch -- Kellen Renshaw Thu, 09 Sep 2021 08:59:24 -0400 ** Changed in: procps (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1917148 Title: ps version is UNKNOWN in procps 2:3.3.16-1ubuntu2 Status in procps package in Ubuntu: Fix Released Status in procps source package in Bionic: Fix Released Status in procps source package in Focal: Fix Released Status in procps source package in Hirsute: Fix Released Status in procps source package in Impish: Fix Released Bug description: [Impact] * Breakage of tools expecting the version number or the number to substantially match the Debian package version. * May confuse users expecting the version to substantially match the Debian package version. * Restores behavior to that provided in Groovy/Hirsute+ and Bionic and prior releases. - Focal is the only release affected. * Backported Debian fix to restore ".tarball-version" file to provide version information during build. - Also included the autopkgtests for versioning from the same Debian fix. [Test Plan] 1) Create a Focal (or derived from Focal) system. 2) Execute "ps --version" or any of the binaries provided by the package with their respective version flags. 3) Instead of desired output of the version, the output is: the invoked binary name followed by "from procps-ng UNKNOWN" Example: "ps from procps-ng UNKNOWN" [Where problems could occur] * This fix could cause issues if applications have come to depend on the incorrect behavior. IE, an application that uses a version string of "UNKNOWN" as part of a heuristic for identifying a Focal system. * If the version of procps-ng is incremented, this patch would need to be updated or removed if it is no longer relevant. Otherwise, an incorrect version would be reported by the binaries. [Other Info] * This change is in Groovy+ and Debian packaging with the same version of procps-ng. - Introduced in procps (2:3.3.16-5) unstable in Debian. [Original Description] From Linux Lint 20.1, so Focal Fossa 20.04.1 Package procps 2:3.3.16-1ubuntu2 $ LANG=C ps --version ps from procps-ng UNKNOWN I don't know if it comes from Ubuntu or upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1917148/+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 1932579] Re: snap pt_BR locale shows warning every time
@anonymouse67 and @miguelpires1, sorry for the delay, I was not at the office today. @miguelpires1, you're right a simple `sudo snap refresh snapd --edge` did it. @anonymouse67, the correction seems to work: ``` $ snap version snap2.52+git869.g363f829 snapd 2.52+git869.g363f829 series 16 ubuntu 20.04 kernel 5.11.0-34-generic $ snap list NomeVersão RevA seguir EditorNotas core16-2.51.4 11606 latest/stable canonical✓core core18 202107222128 latest/stable canonical✓base core20 202107021081 latest/stable canonical✓base gnome-3-28-1804 3.28.0-19-g98f9e67.98f9e67 161latest/stable canonical✓- gnome-3-34-1804 0+git.3556cb3 72 latest/stable/… canonical✓- gtk-common-themes 0.1-52-gb92ac40 1515 latest/stable/… canonical✓- intellij-idea-ultimate 2021.2.2319latest/stable jetbrains✓classic skype 8.75.0.140 183latest/stable skype✓- snap-store 3.38.0-64-g23c4c77 547latest/stable/… canonical✓- snapd 2.52+git869.g363f82913449 latest/edge canonical✓snapd telegram-desktop3.1.0 3119 latest/stable telegram.desktop - $ snap --help O comando snap permite instalar, configurar, atualizar e remover snaps. Os Snaps são pacotes que funcionam em muitas distribuições Linux diferentes, permitindo a entrega e operação seguras das aplicações e utilitários mais recentes. Uso: snap [...] ... ``` -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to language-pack-pt-base in Ubuntu. https://bugs.launchpad.net/bugs/1932579 Title: snap pt_BR locale shows warning every time Status in snapd: Fix Committed Status in language-pack-pt-base package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Fix Committed Bug description: The following warning appears every time I type a snap command, and thus breaks auto-completion. 2021/06/18 13:15:24.372374 main.go:176: description of prepare-image's "" is lowercase in locale "pt_BR": "o directório de destino" The problem seems locale dependent, since "LANG=C snap" doesn't show this warning. I'm currently using Ubuntu 21.04, and this bug happens since I upgraded from 20.10. (I don't know if this is off-topic or where I can help, but "directório" is more pt_PT than pt_BR, which could be "pasta/diretório") echo $LANG output: pt_BR.UTF-8 lsb_release -rb output: Description: Ubuntu 21.04 Release: 21.04 apt-cache policy snapd output: snapd: Instalado: 2.49.2+21.04ubuntu1 Candidato: 2.49.2+21.04ubuntu1 Tabela de versão: *** 2.49.2+21.04ubuntu1 500 500 http://br.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status snap list output: ...[other packages]... snap-store 3.38.0-64-g23c4c77 547latest/stable canonical✓ - snapd 2.5112159 latest/stable canonical✓ snapd To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1932579/+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 1822156] Re: Cannot parse m3u8 playlist
Just noticed that VLC opens and plays the "radio.m3u8" stream just fine. (It is the "YLE Puhe" radio channel from Finland) $ sudo apt install vlc $ vlc Download/radio.m3u8 Ref: https://www.radio-browser.info/#/search?page=1&name=YLE -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to totem-pl-parser in Ubuntu. https://bugs.launchpad.net/bugs/1822156 Title: Cannot parse m3u8 playlist Status in totem-pl-parser package in Ubuntu: Fix Released Bug description: Hello, I have a m3u8 (utf8 format) playlist, but many players do not understand that file. Neither does totem-pl-parser. Ref: https://developer.gnome.org/totem-pl-parser/stable/ radio.m3u8 attached. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: libtotem-plparser-dev 3.26.3-1ubuntu1 Uname: Linux 5.0.1-050001-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 28 16:06:11 2019 InstallationDate: Installed on 2019-03-06 (21 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) SourcePackage: totem-pl-parser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem-pl-parser/+bug/1822156/+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 1932579] Re: snap pt_BR locale shows warning every time
Ah Miguel, thanks for realizing my error, I should have probably just said something like sudo snap install snapd --edge; sudo snap refresh snapd --edge which will ensure that it's always installed and gets refreshed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to language-pack-pt-base in Ubuntu. https://bugs.launchpad.net/bugs/1932579 Title: snap pt_BR locale shows warning every time Status in snapd: Fix Committed Status in language-pack-pt-base package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Fix Committed Bug description: The following warning appears every time I type a snap command, and thus breaks auto-completion. 2021/06/18 13:15:24.372374 main.go:176: description of prepare-image's "" is lowercase in locale "pt_BR": "o directório de destino" The problem seems locale dependent, since "LANG=C snap" doesn't show this warning. I'm currently using Ubuntu 21.04, and this bug happens since I upgraded from 20.10. (I don't know if this is off-topic or where I can help, but "directório" is more pt_PT than pt_BR, which could be "pasta/diretório") echo $LANG output: pt_BR.UTF-8 lsb_release -rb output: Description: Ubuntu 21.04 Release: 21.04 apt-cache policy snapd output: snapd: Instalado: 2.49.2+21.04ubuntu1 Candidato: 2.49.2+21.04ubuntu1 Tabela de versão: *** 2.49.2+21.04ubuntu1 500 500 http://br.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status snap list output: ...[other packages]... snap-store 3.38.0-64-g23c4c77 547latest/stable canonical✓ - snapd 2.5112159 latest/stable canonical✓ snapd To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1932579/+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 1822156] Re: Cannot parse m3u8 playlist
Hello, Yes, it is long time since I filed this report. I am now using Ubuntu 21.10 (daily version). I tried to play the file in Totem, but it does not understand the format (or Gstreamer is missing a plugin for it). I have installed the ubuntu-restricted-extras package. I attached a video of my test. Please tell me if you need additional tests or information. ** Attachment added: "Screencast from 20-09-2021 20:25:22.webm" https://bugs.launchpad.net/ubuntu/+source/totem-pl-parser/+bug/1822156/+attachment/5526556/+files/Screencast%20from%2020-09-2021%2020%3A25%3A22.webm -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to totem-pl-parser in Ubuntu. https://bugs.launchpad.net/bugs/1822156 Title: Cannot parse m3u8 playlist Status in totem-pl-parser package in Ubuntu: Fix Released Bug description: Hello, I have a m3u8 (utf8 format) playlist, but many players do not understand that file. Neither does totem-pl-parser. Ref: https://developer.gnome.org/totem-pl-parser/stable/ radio.m3u8 attached. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: libtotem-plparser-dev 3.26.3-1ubuntu1 Uname: Linux 5.0.1-050001-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 28 16:06:11 2019 InstallationDate: Installed on 2019-03-06 (21 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) SourcePackage: totem-pl-parser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem-pl-parser/+bug/1822156/+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 1941799] Re: Please merge openssh 1:8.4p1-6 from Debian unstable
So this is fun, the upstream openssh actually has the same test failure when running `make tests`. So it doesn't appear to be something we introduced here, but it is definitely a problem that needs solving. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1941799 Title: Please merge openssh 1:8.4p1-6 from Debian unstable Status in openssh package in Ubuntu: In Progress Bug description: This merge is needed because there are changes in Ubuntu that are not present in Debian. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1941799/+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 1932579] Re: snap pt_BR locale shows warning every time
Hi (or Olá for the PT crowd). I think snapd just wasn't refreshed, @ioguis' output doesn't show it: ``` $ sudo snap install snapd --edge || sudo snap refresh snapd --edge [sudo] senha para my-user: 2021/09/18 12:54:59.334587 main.go:176: description of prepare-image's "" is lowercase in locale "pt_BR": "o directório de destino" snap "snapd" já está instalado, consulte 'snap help refresh' ``` `snap install ` (when run on an already installed snap) returns 0. So the right-side of the `||` didn't run and snapd wasn't refreshed to edge. @iogui, can you run `sudo snap refresh snapd --edge` and let us know if `snap list` logs the warning? I've just tested with edge and the fix seems to be working. If you still see the warning, then could you please run `snap version` and post the output? Thanks for your help -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to language-pack-pt-base in Ubuntu. https://bugs.launchpad.net/bugs/1932579 Title: snap pt_BR locale shows warning every time Status in snapd: Fix Committed Status in language-pack-pt-base package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Fix Committed Bug description: The following warning appears every time I type a snap command, and thus breaks auto-completion. 2021/06/18 13:15:24.372374 main.go:176: description of prepare-image's "" is lowercase in locale "pt_BR": "o directório de destino" The problem seems locale dependent, since "LANG=C snap" doesn't show this warning. I'm currently using Ubuntu 21.04, and this bug happens since I upgraded from 20.10. (I don't know if this is off-topic or where I can help, but "directório" is more pt_PT than pt_BR, which could be "pasta/diretório") echo $LANG output: pt_BR.UTF-8 lsb_release -rb output: Description: Ubuntu 21.04 Release: 21.04 apt-cache policy snapd output: snapd: Instalado: 2.49.2+21.04ubuntu1 Candidato: 2.49.2+21.04ubuntu1 Tabela de versão: *** 2.49.2+21.04ubuntu1 500 500 http://br.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status snap list output: ...[other packages]... snap-store 3.38.0-64-g23c4c77 547latest/stable canonical✓ - snapd 2.5112159 latest/stable canonical✓ snapd To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1932579/+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 1822156] Re: Cannot parse m3u8 playlist
> I verified your sample file works with totem-pl-parser 3.26.5-5ubuntu1 Hi, How exactly did you verify the sample m3u8 file ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to totem-pl-parser in Ubuntu. https://bugs.launchpad.net/bugs/1822156 Title: Cannot parse m3u8 playlist Status in totem-pl-parser package in Ubuntu: Fix Released Bug description: Hello, I have a m3u8 (utf8 format) playlist, but many players do not understand that file. Neither does totem-pl-parser. Ref: https://developer.gnome.org/totem-pl-parser/stable/ radio.m3u8 attached. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: libtotem-plparser-dev 3.26.3-1ubuntu1 Uname: Linux 5.0.1-050001-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 28 16:06:11 2019 InstallationDate: Installed on 2019-03-06 (21 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) SourcePackage: totem-pl-parser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem-pl-parser/+bug/1822156/+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 1933117] Re: ufw delete can confuse protocol-specific rule with otherwise matching 'proto any' rule
This bug was fixed in the package ufw - 0.36.1-1 --- ufw (0.36.1-1) unstable; urgency=medium * New upstream release (LP: #1808463, LP: #1831186, LP: #1838764, LP: #1556419, LP: #1933117). Drop the following (included upstream): - 0002-fix-check-requirements.patch - 0003-lp1838764.patch - 0004-make-root-tests-chain-order-agnostic.patch - 0005-use-only-python3.patch - 0006-bug921680.patch - 0007-bug921680-pt2.patch - 0008-fix-check-requirements-again.patch - 0009-empty-non-functioning-ipt-modules.patch - 0010-add-other-firewall-checks.patch - 0011-suppress-legacy-warnings-in-tests.patch - 0012-pyflakes3.patch - 0013-add-prepend-to-help.patch * Remaining changes: - 0001-optimize-boot.patch - python3-versions.diff [ Jamie Strandboge ] * ufw.lintian-overrides: - remove init.d-script-possible-missing-stop override - adjust "allow to" override - override spare-manual-page for ufw-framework as it gives additional details for the ufw command * 0002-fix-copyright.patch: src/ufw: update copyright year * debian/*: use my jdstr...@ubuntu.com email address [ Debian Janitor ] * Use secure copyright file specification URI. * Use set -e rather than passing -e on the shebang-line. * Set upstream metadata fields: Repository, Repository-Browse. * Update watch file format version to 4. [ Bastian Triller ] * debian/ufw.logrotate: use rsyslog-rotate instead of invoke-rc.d (Closes: 993525) -- Jamie Strandboge Sun, 19 Sep 2021 05:46:12 + ** Changed in: ufw (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1933117 Title: ufw delete can confuse protocol-specific rule with otherwise matching 'proto any' rule Status in ufw: Fix Released Status in ufw package in Ubuntu: Fix Released Bug description: UFW versions 0.35 (on Ubuntu 16.04 LTS) and 0.36 (on Ubuntu 20.04 LTS) If a rule is inserted without specifying the protocol, it will default to both udp and tcp. If a second rule is inserted earlier in the order that specifies the protocol but is otherwise identical, UFW will delete the wrong rule if the first rule is deleted. This is repeatable with the following script: ufw insert 1 allow from 1.1.1.1/26 to any port 22 ufw insert 2 allow from 1.2.3.4/26 to any port 22 ufw insert 1 allow from 1.2.3.4/26 to any port 22 proto tcp iptables -L -n | grep -A 6 "Chain ufw-user-input" yes | ufw delete 3 iptables -L -n | grep -A 4 "Chain ufw-user-input" The output is as follows: Chain ufw-user-input (1 references) target prot opt source destination ACCEPT tcp -- 1.2.3.0/26 0.0.0.0/0tcp dpt:22 ACCEPT tcp -- 1.1.1.0/26 0.0.0.0/0tcp dpt:22 ACCEPT udp -- 1.1.1.0/26 0.0.0.0/0udp dpt:22 ACCEPT tcp -- 1.2.3.0/26 0.0.0.0/0tcp dpt:22 ACCEPT udp -- 1.2.3.0/26 0.0.0.0/0udp dpt:22 Chain ufw-user-input (1 references) target prot opt source destination ACCEPT tcp -- 1.1.1.0/26 0.0.0.0/0tcp dpt:22 ACCEPT udp -- 1.1.1.0/26 0.0.0.0/0udp dpt:22 ACCEPT tcp -- 1.2.3.0/26 0.0.0.0/0tcp dpt:22 UFW deleted the first rule for 1.2.3.0 and then the last rule for 1.2.3.0, leaving the wrong rule remaining. Here is the ufw status: To Action From -- -- 22/tcp ALLOW 1.2.3.0/26 22 ALLOW 1.1.1.0/26 Mixing ALLOW and REJECT/DENY rules can further result in incorrect behavior due to this incorrect reordering. On port 22, this could render SSH remotely inaccessible. For example, if one had initially set up the following rule to port 22 (TCP and UDP)... ufw insert 1 allow from 1.2.3.4 to any port 22 ...and later wanted to further restrict it to only TCP, while explicitly rejecting any other port 22 connections... ufw insert 1 allow from 1.2.3.4 to any port 22 proto tcp ufw insert 2 reject from any to any port 22 yes | ufw delete 3 ...this would result in SSH becoming inaccessible. Instead if one had the initial configuration... ufw insert 1 reject from 1.0.0.0/8 to any port 22 ufw insert 2 allow from any to any port 22 ...which was later updated to be... ufw insert 1 reject from 1.0.0.0/8 to any port 22 proto tcp ufw insert 2 allow from any to any port 22 proto tcp yes | ufw delete 3 ...this would result in 1.0.0.0/8 incorrectly being allowed to access port 22. While this is a contrived scenario, it is possible and reproducible. A reboot is required to fix the issue, as it re
[Touch-packages] [Bug 1943441] Re: lxc: lxc-test-parse-config-file failure
Found on impish/linux-oracle/5.13.0-1005.7 ** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Tags added: 5.13 amd64 impish linux-kvm oracle sru-20210906 ubuntu- lxc ** Tags added: hinted -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1943441 Title: lxc: lxc-test-parse-config-file failure Status in ubuntu-kernel-tests: New Status in lxc package in Ubuntu: In Progress Bug description: I'm getting the following error with the lxc kernel autotest on impish: 08:46:04 DEBUG| parse_config_file.c: 60: set_get_compare_clear_save_load: expected value "system_u:system_r:lxc_t:s0:c22" and retrieved value "" for config key "lxc.selinux.context" do not match 08:46:04 DEBUG| 08:46:04 DEBUG| parse_config_file.c: 382: main: lxc.selinux.context 08:46:06 INFO | ERRORubuntu_lxc.lxc-test-parse-config-file ubuntu_lxc.lxc-test-parse-config-filetimestamp=1631090766localtime=Sep 08 08:46:06Command failed, rc=1, Command returned non-zero exit status * Command: /tmp/lxc-pkg-ubuntu/src/tests/lxc-test-parse-config-file Exit status: 1 Duration: 0.0550210475922 stderr: parse_config_file.c: 60: set_get_compare_clear_save_load: expected value "system_u:system_r:lxc_t:s0:c22" and retrieved value "" for config key "lxc.selinux.context" do not match parse_config_file.c: 382: main: lxc.selinux.context I haven't investigated very much, but it looks like a (mis)configuration change / issue. Does it ring any bell? Otherwise I'll investigate more. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1943441/+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 1932579] Re: snap pt_BR locale shows warning every time
@iogui, hmm it could be that our fix isn't working, can you show the output of these commands: snap version snap list -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to language-pack-pt-base in Ubuntu. https://bugs.launchpad.net/bugs/1932579 Title: snap pt_BR locale shows warning every time Status in snapd: Fix Committed Status in language-pack-pt-base package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Fix Committed Bug description: The following warning appears every time I type a snap command, and thus breaks auto-completion. 2021/06/18 13:15:24.372374 main.go:176: description of prepare-image's "" is lowercase in locale "pt_BR": "o directório de destino" The problem seems locale dependent, since "LANG=C snap" doesn't show this warning. I'm currently using Ubuntu 21.04, and this bug happens since I upgraded from 20.10. (I don't know if this is off-topic or where I can help, but "directório" is more pt_PT than pt_BR, which could be "pasta/diretório") echo $LANG output: pt_BR.UTF-8 lsb_release -rb output: Description: Ubuntu 21.04 Release: 21.04 apt-cache policy snapd output: snapd: Instalado: 2.49.2+21.04ubuntu1 Candidato: 2.49.2+21.04ubuntu1 Tabela de versão: *** 2.49.2+21.04ubuntu1 500 500 http://br.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status snap list output: ...[other packages]... snap-store 3.38.0-64-g23c4c77 547latest/stable canonical✓ - snapd 2.5112159 latest/stable canonical✓ snapd To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1932579/+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 1944060] Re: Black Screen after Session Unlock from Suspend
** Package changed: ubuntu => ubuntu-meta (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1944060 Title: Black Screen after Session Unlock from Suspend Status in ubuntu-meta package in Ubuntu: New Bug description: Ubuntu Release: Ubuntu 20.04.3 LTS Installation Style: Minimal (selected during GUI install) (Untested against full installation style) Patient System Hardware Information: Lenovo ThinkPad P50 (Xenon) - Intel HD Graphics + NVIDIA Quadro M2000M (NVIDIA Prime enabled w/proprietary drivers) (GPU is not suspected to be the issue) Expected Behavior: 1) Suspend the system into sleep mode. 2) Awake the system to be greeted by lock screen. 3) Type in password, press enter. 4)GNOME validates password successfully. 5) Resume user desktop session. Actual Behavior: 1) Suspend the system into sleep mode. 2) Awake the system to be greeted by lock screen. 3) Type in password, press enter. 4)GNOME validates password successfully. 5) GNOME lock screen freezes - spinner stops moving but mouse cursor and keyboard are responsive (can switch TTYs). After GNOME lock screen freeze, if you switch out of TTY2 (default for GUI), and back into it, a black screen is shown. If you attempt to login via TTY1, you are switched to the black screen session in TTY2. Solution / Workaround: This behavior can be avoided by installing the "gnome-scrensaver" package. Something in this package is required by GNOME in order to successfully resume this system from suspend, even though no screen saver settings were configured after installing it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1944060/+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 1860826] Re: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory
** Description changed: - Hello, after upgrading to focal I found the following in my journalctl - output: + [Impact] + Removal of the /etc/securetty file from the system results in useless log messages whenever pam_unix is invoked, which for some systems is quite a lot of logging. /etc/securetty is not coming back, and this is not an error. + + [Test Plan] + 1. Run 'sudo -s'. Confirm that 'journalctl | grep sudo.*securetty' returns a line 'sudo[...]: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory'. + 2. Install libpam-modules update from -proposed. + 3. Confirm that 'grep nullok_secure' /etc/pam.d/common-auth returns no lines. + 4. Run 'sudo -k'. + 5. Run 'sudo -s' again. + 6. Confirm that sudo succeeds and gives you a root shell. + 7. Confirm that 'journalctl | grep sudo.*securetty' does not show any new lines. + + [Where problems could occur] + PAM is a sensitive package because it's used in all authentication operations on the system. A bug here could render a user unable to log in to their system. + + Risks are mitigated by: + - including a patch that treats the obsolete 'nullok_secure' as an alias for 'nullok' to ensure any user-edited configurations continue to work rather than throwing errors about unknown options + - editing the system-managed /etc/pam.d/common-auth config to use 'nullok' instead of 'nullok_secure' for future compatibility. + + Because we are editing the system config, this could also cause issues + on future upgrades with undesirable prompts to the user. However, the + maintainer scripts are not meant to prompt on changes to the pam-config, + and this code has been in Debian for a while with no reports of + problems. + + + [Original description] + Hello, after upgrading to focal I found the following in my journalctl output: Jan 24 23:07:00 millbarge sudo[32120]: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory Jan 24 23:07:01 millbarge sudo[32120]: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory - The login package stopped packaging this file: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731656 and now forcibly removes the file: https://paste.ubuntu.com/p/myh9cGWrHD/ However, the pam package's pam_unix.so module has not yet been adapted to ignore this file: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674857#25 Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libpam-modules 1.3.1-5ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 Date: Fri Jan 24 23:35:33 2020 ProcEnviron: - TERM=rxvt-unicode-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=rxvt-unicode-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: pam UpgradeStatus: Upgraded to focal on 2020-01-24 (0 days ago) -- 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/1860826 Title: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory Status in pam package in Ubuntu: Fix Released Status in pam source package in Focal: In Progress Status in pam source package in Groovy: Won't Fix Status in pam package in Debian: Fix Released Bug description: [Impact] Removal of the /etc/securetty file from the system results in useless log messages whenever pam_unix is invoked, which for some systems is quite a lot of logging. /etc/securetty is not coming back, and this is not an error. [Test Plan] 1. Run 'sudo -s'. Confirm that 'journalctl | grep sudo.*securetty' returns a line 'sudo[...]: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory'. 2. Install libpam-modules update from -proposed. 3. Confirm that 'grep nullok_secure' /etc/pam.d/common-auth returns no lines. 4. Run 'sudo -k'. 5. Run 'sudo -s' again. 6. Confirm that sudo succeeds and gives you a root shell. 7. Confirm that 'journalctl | grep sudo.*securetty' does not show any new lines. [Where problems could occur] PAM is a sensitive package because it's used in all authentication operations on the system. A bug here could render a user unable to log in to their system. Risks are mitigated by: - including a patch that treats the obsolete 'nullok_secure' as an alias for 'nullok' to ensure any user-edited configurations continue to work rather than throwing errors about unknown options - editing the system-managed /etc/pam.d/common-auth config to use 'nullok' instead of 'nullok_secure' for future compatibility. Because we are editing the system config, this could also cause issues on future upgrades with undesira
[Touch-packages] [Bug 1944060] [NEW] Black Screen after Session Unlock from Suspend
You have been subscribed to a public bug: Ubuntu Release: Ubuntu 20.04.3 LTS Installation Style: Minimal (selected during GUI install) (Untested against full installation style) Patient System Hardware Information: Lenovo ThinkPad P50 (Xenon) - Intel HD Graphics + NVIDIA Quadro M2000M (NVIDIA Prime enabled w/proprietary drivers) (GPU is not suspected to be the issue) Expected Behavior: 1) Suspend the system into sleep mode. 2) Awake the system to be greeted by lock screen. 3) Type in password, press enter. 4)GNOME validates password successfully. 5) Resume user desktop session. Actual Behavior: 1) Suspend the system into sleep mode. 2) Awake the system to be greeted by lock screen. 3) Type in password, press enter. 4)GNOME validates password successfully. 5) GNOME lock screen freezes - spinner stops moving but mouse cursor and keyboard are responsive (can switch TTYs). After GNOME lock screen freeze, if you switch out of TTY2 (default for GUI), and back into it, a black screen is shown. If you attempt to login via TTY1, you are switched to the black screen session in TTY2. Solution / Workaround: This behavior can be avoided by installing the "gnome-scrensaver" package. Something in this package is required by GNOME in order to successfully resume this system from suspend, even though no screen saver settings were configured after installing it. ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment unmetdeps -- Black Screen after Session Unlock from Suspend https://bugs.launchpad.net/bugs/1944060 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1860826] Re: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory
** Changed in: pam (Ubuntu Focal) Status: Confirmed => In Progress -- 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/1860826 Title: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory Status in pam package in Ubuntu: Fix Released Status in pam source package in Focal: In Progress Status in pam source package in Groovy: Won't Fix Status in pam package in Debian: Fix Released Bug description: Hello, after upgrading to focal I found the following in my journalctl output: Jan 24 23:07:00 millbarge sudo[32120]: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory Jan 24 23:07:01 millbarge sudo[32120]: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory The login package stopped packaging this file: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731656 and now forcibly removes the file: https://paste.ubuntu.com/p/myh9cGWrHD/ However, the pam package's pam_unix.so module has not yet been adapted to ignore this file: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674857#25 Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libpam-modules 1.3.1-5ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 Date: Fri Jan 24 23:35:33 2020 ProcEnviron: TERM=rxvt-unicode-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pam UpgradeStatus: Upgraded to focal on 2020-01-24 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1860826/+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 1932579] Re: snap pt_BR locale shows warning every time
@anonymouse67, tested just now and the result is the same. I don't know much about snap commands but maybe the parameter "--edge" is not working as you expect it to... shouldn't the command be with a parameter "-- channel=latest/edge" to select the channel?... Because I don't know, I've not tried something different as I'm afraid to mess with my system. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to language-pack-pt-base in Ubuntu. https://bugs.launchpad.net/bugs/1932579 Title: snap pt_BR locale shows warning every time Status in snapd: Fix Committed Status in language-pack-pt-base package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Fix Committed Bug description: The following warning appears every time I type a snap command, and thus breaks auto-completion. 2021/06/18 13:15:24.372374 main.go:176: description of prepare-image's "" is lowercase in locale "pt_BR": "o directório de destino" The problem seems locale dependent, since "LANG=C snap" doesn't show this warning. I'm currently using Ubuntu 21.04, and this bug happens since I upgraded from 20.10. (I don't know if this is off-topic or where I can help, but "directório" is more pt_PT than pt_BR, which could be "pasta/diretório") echo $LANG output: pt_BR.UTF-8 lsb_release -rb output: Description: Ubuntu 21.04 Release: 21.04 apt-cache policy snapd output: snapd: Instalado: 2.49.2+21.04ubuntu1 Candidato: 2.49.2+21.04ubuntu1 Tabela de versão: *** 2.49.2+21.04ubuntu1 500 500 http://br.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status snap list output: ...[other packages]... snap-store 3.38.0-64-g23c4c77 547latest/stable canonical✓ - snapd 2.5112159 latest/stable canonical✓ snapd To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1932579/+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 1932579] Re: snap pt_BR locale shows warning every time
@iogui could you try again? snapd on the edge channel may not have finished building by the time you tried, but I see that there was an update pushed out this morning. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to language-pack-pt-base in Ubuntu. https://bugs.launchpad.net/bugs/1932579 Title: snap pt_BR locale shows warning every time Status in snapd: Fix Committed Status in language-pack-pt-base package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Fix Committed Bug description: The following warning appears every time I type a snap command, and thus breaks auto-completion. 2021/06/18 13:15:24.372374 main.go:176: description of prepare-image's "" is lowercase in locale "pt_BR": "o directório de destino" The problem seems locale dependent, since "LANG=C snap" doesn't show this warning. I'm currently using Ubuntu 21.04, and this bug happens since I upgraded from 20.10. (I don't know if this is off-topic or where I can help, but "directório" is more pt_PT than pt_BR, which could be "pasta/diretório") echo $LANG output: pt_BR.UTF-8 lsb_release -rb output: Description: Ubuntu 21.04 Release: 21.04 apt-cache policy snapd output: snapd: Instalado: 2.49.2+21.04ubuntu1 Candidato: 2.49.2+21.04ubuntu1 Tabela de versão: *** 2.49.2+21.04ubuntu1 500 500 http://br.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status snap list output: ...[other packages]... snap-store 3.38.0-64-g23c4c77 547latest/stable canonical✓ - snapd 2.5112159 latest/stable canonical✓ snapd To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1932579/+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 1943984] Re: No archive files for static compilation are included in the -dev package
Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994757 ** Bug watch added: Debian Bug tracker #994757 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994757 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to graphite2 in Ubuntu. https://bugs.launchpad.net/bugs/1943984 Title: No archive files for static compilation are included in the -dev package Status in graphite2 package in Ubuntu: New Bug description: There is no libgraphite2.a file, so it is not possible to compile statically against this library. See attached patch to solve this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/graphite2/+bug/1943984/+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 1938144] Re: monitor_read: unpermitted request 48 on server while attempting GSSAPI key exchange
Thanks, Niklas! Utkarsh, Paride: Since this seems to be a low priority issue, I am waiting to see if we get a couple more eyes into https://github.com/openssh-gsskex/openssh-gsskex/pull/21 before adding this one in our delta (this could even go into Debian first and then we can start preparing SRUs). Therefore, I am also removing the server-next tag from this one. ** Tags removed: server-next -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1938144 Title: monitor_read: unpermitted request 48 on server while attempting GSSAPI key exchange Status in portable OpenSSH: Unknown Status in openssh package in Ubuntu: Triaged Status in openssh source package in Focal: Triaged Status in openssh source package in Hirsute: Triaged Bug description: I'm using openssh 1:8.2p1-4ubuntu0.2 on Ubuntu 20.04.2 LTS (client and server) with the option "GSSAPIKeyExchange=yes", and this causes the connection to fail. The server has GSSAPI (Kerberos authentication) enabled, but is is only used for non-root users (root uses SSH keys). Client command: ssh -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex root@server -v -p -o GSSAPIKeyExchange=yes Client log: OpenSSH_8.2p1 Ubuntu-4ubuntu0.2, OpenSSL 1.1.1f 31 Mar 2020 debug1: Reading configuration data /home/user/.ssh/config debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/*.conf matched no files debug1: /etc/ssh/ssh_config line 21: Applying options for * debug1: Connecting to compute-test [130.75.80.46] port . debug1: Connection established. debug1: identity file /home/rother/.ssh/id_rsa type 0 debug1: identity file /home/rother/.ssh/id_rsa-cert type -1 debug1: identity file /home/rother/.ssh/id_dsa type -1 debug1: identity file /home/rother/.ssh/id_dsa-cert type -1 debug1: identity file /home/rother/.ssh/id_ecdsa type -1 debug1: identity file /home/rother/.ssh/id_ecdsa-cert type -1 debug1: identity file /home/rother/.ssh/id_ecdsa_sk type -1 debug1: identity file /home/rother/.ssh/id_ecdsa_sk-cert type -1 debug1: identity file /home/rother/.ssh/id_ed25519 type -1 debug1: identity file /home/rother/.ssh/id_ed25519-cert type -1 debug1: identity file /home/rother/.ssh/id_ed25519_sk type -1 debug1: identity file /home/rother/.ssh/id_ed25519_sk-cert type -1 debug1: identity file /home/rother/.ssh/id_xmss type -1 debug1: identity file /home/rother/.ssh/id_xmss-cert type -1 debug1: Local version string SSH-2.0-OpenSSH_8.2p1 Ubuntu-4ubuntu0.2 debug1: Remote protocol version 2.0, remote software version OpenSSH_8.2p1 Ubuntu-4ubuntu0.2 debug1: match: OpenSSH_8.2p1 Ubuntu-4ubuntu0.2 pat OpenSSH* compat 0x0400 debug1: Authenticating to server: as 'root' debug1: Offering GSSAPI proposal: gss-gex-sha1-toWM5Slw5Ew8Mqkay+al2g==,gss-group14-sha1-toWM5Slw5Ew8Mqkay+al2g==,gss-gex-sha1-eipGX3TCiQSrx573bT1o1Q==,gss-group14-sha1-eipGX3TCiQSrx573bT1o1Q== debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: algorithm: gss-gex-sha1-toWM5Slw5Ew8Mqkay+al2g== debug1: kex: host key algorithm: ecdsa-sha2-nistp256 debug1: kex: server->client cipher: chacha20-poly1...@openssh.com MAC: compression: none debug1: kex: client->server cipher: chacha20-poly1...@openssh.com MAC: compression: none debug1: Doing group exchange debug1: Calling gss_init_sec_context debug1: Delegating credentials debug1: Received GSSAPI_COMPLETE debug1: Calling gss_init_sec_context debug1: Delegating credentials debug1: Rekey has happened - updating saved versions debug1: rekey out after 134217728 blocks debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: rekey in after 134217728 blocks debug1: Will attempt key: /home/rother/.ssh/id_rsa RSA SHA256:n/EY/cGjgd/r+7JpuqODxIotHHLsYptGXYx9GlKCWSM agent debug1: Will attempt key: /home/rother/.ssh/root_id_rsa RSA SHA256:yCLAID9FMILharHmDpCB8wW8eiA+iHa4oQKLODbbzKw agent debug1: Will attempt key: /home/user/.ssh/id_dsa debug1: Will attempt key: /home/user/.ssh/id_ecdsa debug1: Will attempt key: /home/user/.ssh/id_ecdsa_sk debug1: Will attempt key: /home/user/.ssh/id_ed25519 debug1: Will attempt key: /home/user/.ssh/id_ed25519_sk debug1: Will attempt key: /home/user/.ssh/id_xmss debug1: SSH2_MSG_EXT_INFO received debug1: kex_input_ext_info: server-sig-algs= debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password debug1: Next authentication method: gssapi-with-mic debug1: Delegating credentials debug1: Delegating credentials debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password debug1: Authentications that can continue: publi
[Touch-packages] [Bug 1943859] Re: The development package does not include static libraries
Debian bug report: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=994752 ** Bug watch added: Debian Bug tracker #994752 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994752 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1943859 Title: The development package does not include static libraries Status in pango1.0 package in Ubuntu: New Bug description: The development package for pango (libpango1.0-dev) does not include static libraries so it is not possible to link these libraries statically. See attached patch with the fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1943859/+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 1943984] Re: No archive files for static compilation are included in the -dev package
Thank for your bug report, the package is in sync with Debian so could you report the issue there? ** Changed in: graphite2 (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to graphite2 in Ubuntu. https://bugs.launchpad.net/bugs/1943984 Title: No archive files for static compilation are included in the -dev package Status in graphite2 package in Ubuntu: New Bug description: There is no libgraphite2.a file, so it is not possible to compile statically against this library. See attached patch to solve this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/graphite2/+bug/1943984/+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 1872145] Re: explicit key offered after all agent keys, auth can fail before explicit key used
I have again updated the upstream case, but if they are not willing/convinced this won't happen as Ubuntu delta or we will have too many small scratches by being slightly different on this. So anyone affected/requesting this please chime in on the upstream bug. Dropping server-next as it can't be acted on as-is. ** Tags removed: server-next -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1872145 Title: explicit key offered after all agent keys, auth can fail before explicit key used Status in portable OpenSSH: Unknown Status in openssh package in Ubuntu: Triaged Status in openssh package in Debian: New Bug description: A user creates an ssh key and specifies it on the cmdline with 'ssh -i new_key user@host'. The connection fails with the message "Too many authentication failures" displayed to the user. This would lead the user to believe that they failed to put the public portion of the new key on the destination and it will probably be hard for the average user to debug this. The root of this issue is that the user has a number of keys in ~/.ssh/ registered with their ssh agent. The ssh command is offering each of these keys from the agent to the remote system before trying the explicit key from the command line. There are enough agent keys to reach the failure limit (usually 5 keys) with the remote before they get to the explicit key. The solution today for the user is to head down into the ssh_config man page to find '-o IdentitiesOnly=yes' to skip the agent keys and only use the specified key. But they're unlikely to do this because '-i' in the ssh man page doesn't suggest this and they'd only look for this if they actually understood the root cause of the problem, which is a bit cruel. We should consider changing the order of the keys offered to the remote to use explicit keys first followed by agent keys. It would seem to me that this would honor the users intent of explicitly specifying a key to use. The current order makes this difficult for anyone fielding a user's authentication failure report as they must double check that ssh managed to actually try the key the user specified before it raised an error message about authentication failures. To manage notifications about this bug go to: https://bugs.launchpad.net/openssh/+bug/1872145/+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 1934221] Re: systemd-resolve segfault
Thanks for confirming Denys, that's unfortunate... Would you mind giving the version from this PPA a try https://launchpad.net/~slyon/+archive/ubuntu/lp1934221 (for Hirsute)? And maybe also for Focal once the build is ready? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1934221 Title: systemd-resolve segfault Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Confirmed Status in systemd source package in Hirsute: Confirmed Status in systemd source package in Impish: Fix Released Bug description: [Impact] * systemd-resolved stops replying to clients on the local LAN. * logging segfault crashes in dmesg: [836786.046514] systemd-resolve[872009]: segfault at 399 ip 0399 sp 7ffd7959a6d8 error 14 in systemd-resolved[556398695000+9000] [836786.046524] Code: Bad RIP value. [840887.303994] traps: systemd-resolve[877019] general protection fault ip:55ba402e2594 sp:7ffe8cb6bbb0 error:0 in systemd-resolved[55ba402b5000+4] [844395.313421] systemd-resolve[878503]: segfault at 208 ip 5557a249f5fa sp 7ffe686f5a90 error 6 in systemd-resolved[5557a2472000+4] [844395.313431] Code: 48 85 c0 74 0e 48 8b 8d 00 01 00 00 48 89 88 00 01 00 00 48 8b 85 00 01 00 00 48 85 c0 0f 84 1d 01 00 00 48 8b 95 f8 00 00 00 <48> 89 90 f8 00 00 00 48 c7 85 00 01 00 00 00 00 00 00 48 c7 85 f8 * The upload backports the upstream fix (https://github.com/systemd/systemd/pull/18832) to Focal & Hirsute. [Test Plan] * Setup /etc/systemd/resolved.conf: [Resolve] DNS=46.182.19.48#dns2.digitalcourage.de 1.1.1.1#cloudflare-dns.com 9.9.9.9#dns.quad9.net DNSSEC=yes DNSOverTLS=opportunistic MulticastDNS=no LLMNR=no Cache=yes DNSStubListener=yes Domains=~. * wait for ~24-48 hours and observe if any crash happens [Where problems could occur] * Any regression would likely cause crashes in systemd-resolved, making it unresponsive to DNS network name requests to local applications. [Other Info] * Reported upstream: https://github.com/systemd/systemd/issues/18427 * Fixed upstream in v248: https://github.com/systemd/systemd/pull/18832 === Original description === systemd-resolve keep crashing and it is very annoying as sometimes it severely interrupt normal dns resolving. Last uploaded report is 2d9e7378-d89b-11eb-9e14-fa163ee63de6 Typical error in dmesg: systemd-resolve[1792202]: segfault at 564ff982f3e0 ip 564ff982f3e0 sp 7ffe2fd0b758 error 15 apport hints me that problem is related to mdns #3 0x7f3e903c2f11 in sd_event_dispatch () from /lib/systemd/libsystemd-shared-245.so It might be (or not) related that some hosts with mdns in my network have ipv6 enabled. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.7 ProcVersionSignature: Ubuntu 5.4.0-75.84-generic 5.4.119 Uname: Linux 5.4.0-75-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jul 1 08:22:51 2021 InstallationDate: Installed on 2018-12-05 (938 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-75-generic root=UUID=54b80d5c-3d61-4919-873f-0d308083e3b9 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2020-05-22 (405 days ago) dmi.bios.date: 05/12/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1205 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX X399-E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1205:bd05/12/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXX399-EGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1934221/+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 1934221] Re: systemd-resolve segfault
** Merge proposal linked: https://code.launchpad.net/~slyon/ubuntu/+source/systemd/+git/systemd/+merge/408886 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1934221 Title: systemd-resolve segfault Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Confirmed Status in systemd source package in Hirsute: Confirmed Status in systemd source package in Impish: Fix Released Bug description: [Impact] * systemd-resolved stops replying to clients on the local LAN. * logging segfault crashes in dmesg: [836786.046514] systemd-resolve[872009]: segfault at 399 ip 0399 sp 7ffd7959a6d8 error 14 in systemd-resolved[556398695000+9000] [836786.046524] Code: Bad RIP value. [840887.303994] traps: systemd-resolve[877019] general protection fault ip:55ba402e2594 sp:7ffe8cb6bbb0 error:0 in systemd-resolved[55ba402b5000+4] [844395.313421] systemd-resolve[878503]: segfault at 208 ip 5557a249f5fa sp 7ffe686f5a90 error 6 in systemd-resolved[5557a2472000+4] [844395.313431] Code: 48 85 c0 74 0e 48 8b 8d 00 01 00 00 48 89 88 00 01 00 00 48 8b 85 00 01 00 00 48 85 c0 0f 84 1d 01 00 00 48 8b 95 f8 00 00 00 <48> 89 90 f8 00 00 00 48 c7 85 00 01 00 00 00 00 00 00 48 c7 85 f8 * The upload backports the upstream fix (https://github.com/systemd/systemd/pull/18832) to Focal & Hirsute. [Test Plan] * Setup /etc/systemd/resolved.conf: [Resolve] DNS=46.182.19.48#dns2.digitalcourage.de 1.1.1.1#cloudflare-dns.com 9.9.9.9#dns.quad9.net DNSSEC=yes DNSOverTLS=opportunistic MulticastDNS=no LLMNR=no Cache=yes DNSStubListener=yes Domains=~. * wait for ~24-48 hours and observe if any crash happens [Where problems could occur] * Any regression would likely cause crashes in systemd-resolved, making it unresponsive to DNS network name requests to local applications. [Other Info] * Reported upstream: https://github.com/systemd/systemd/issues/18427 * Fixed upstream in v248: https://github.com/systemd/systemd/pull/18832 === Original description === systemd-resolve keep crashing and it is very annoying as sometimes it severely interrupt normal dns resolving. Last uploaded report is 2d9e7378-d89b-11eb-9e14-fa163ee63de6 Typical error in dmesg: systemd-resolve[1792202]: segfault at 564ff982f3e0 ip 564ff982f3e0 sp 7ffe2fd0b758 error 15 apport hints me that problem is related to mdns #3 0x7f3e903c2f11 in sd_event_dispatch () from /lib/systemd/libsystemd-shared-245.so It might be (or not) related that some hosts with mdns in my network have ipv6 enabled. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.7 ProcVersionSignature: Ubuntu 5.4.0-75.84-generic 5.4.119 Uname: Linux 5.4.0-75-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jul 1 08:22:51 2021 InstallationDate: Installed on 2018-12-05 (938 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-75-generic root=UUID=54b80d5c-3d61-4919-873f-0d308083e3b9 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2020-05-22 (405 days ago) dmi.bios.date: 05/12/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1205 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX X399-E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1205:bd05/12/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXX399-EGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1934221/+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 1941799] Re: Please merge openssh 1:8.4p1-6 from Debian unstable
Bryceh: I've been looking into this a bit. Removing the --oknodo had no effect on the tests, and neither did removing the diff that we carry from Debian. I've also noticed that the issue only occurs on kernel <= 5.8. The tests all pass when run in a test environment with kernel 5.11 or 5.13, which is how I missed this in my initial testing. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1941799 Title: Please merge openssh 1:8.4p1-6 from Debian unstable Status in openssh package in Ubuntu: In Progress Bug description: This merge is needed because there are changes in Ubuntu that are not present in Debian. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1941799/+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 1944122] [NEW] Xorg crash
Public bug reported: in the middle of working the GUI crashed (mouse movements yes, no klicks possible) came back, crashed again, login screen appeared. Clearly an issue with AMD-GPU as dmesg states. This report was only possible via ssh from a different machine. Distributor ID: Ubuntu Description:Ubuntu 21.04 Release:21.04 Codename: hirsute Linux peter 5.14.0-051400drmtip20210904-generic #202109040225 SMP Sat Sep 4 02:34:06 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 Uname: Linux 5.14.0-051400drmtip20210904-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.11-0ubuntu65.3 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Sep 20 14:26:27 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: vhba, 20210418, 5.11.0-34-generic, x86_64: installed vhba, 20210418, 5.11.0-35-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] InstallationDate: Installed on 2020-12-16 (278 days ago) InstallationMedia: Ubuntu 16.04.7 LTS "Xenial Xerus" - Release amd64 (20200806) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.14.0-051400drmtip20210904-generic root=UUID=54c9f67c-180d-4545-8531-aef138dc5e0a ro SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: Section "InputClass" Identifier "middle button emulation class" MatchIsPointer "on" Option "Emulate3Buttons" "on" EndSection dmi.bios.date: 06/18/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.20 dmi.board.name: B450 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.20:bd06/18/2020:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:rvnASRock:rnB450Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. mtime.conffile..etc.apport.crashdb.conf: 2021-08-13T12:52:00.669929 version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4 version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 xserver.bootTime: Mon Sep 20 14:25:30 2021 xserver.configfile: /etc/X11/xorg.conf xserver.errors: AMDGPU(0): Failed to make import prime FD as pixmap: 22 xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.11-1ubuntu1.1 xserver.video_driver: amdgpu ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug crash hirsute third-party-packages ubuntu ** Attachment added: "dmesg_20sep2021crasing_APU.txt" https://bugs.launchpad.net/bugs/1944122/+attachment/5526448/+files/dmesg_20sep2021crasing_APU.txt -- 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/1944122 Title: Xorg crash Status in xorg package in Ubuntu: New Bug description: in the middle of working the GUI crashed (mouse movements yes, no klicks possible) came back, crashed again, login screen appeared. Clearly an issue with AMD-GPU as dmesg states. This report was only possible via ssh from a different machine. Distributor ID: Ubuntu Description: Ubuntu 21.04 Release: 21.04 Codename: hirsute Linux peter 5.14.0-051400drmtip20210904-generic #202109040225 SMP Sat Sep 4 02:34:06 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 Uname: Linux 5.14.0-051400drmtip20210904-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.11-0ubuntu65.3 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Co
[Touch-packages] [Bug 1944120] [NEW] Regression in USN-5079-1
*** This bug is a security vulnerability *** Public security bug reported: USN-5079-1 introduced a regression in bionic: https://ubuntuforums.org/showthread.php?t=2467177 Focal+ appear to work as intended. ** Affects: curl (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1944120 Title: Regression in USN-5079-1 Status in curl package in Ubuntu: New Bug description: USN-5079-1 introduced a regression in bionic: https://ubuntuforums.org/showthread.php?t=2467177 Focal+ appear to work as intended. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1944120/+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 1944117] Re: package linux-image-5.4.0-84-generic 5.4.0-84.94 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
** Tags removed: 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/1944117 Title: package linux-image-5.4.0-84-generic 5.4.0-84.94 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: the kernel has failed to load on several tries. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-84-generic 5.4.0-84.94 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.20 AptOrdering: python3-problem-report:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Sep 17 06:38:08 2021 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2020-05-10 (497 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Hewlett-Packard HP EliteDesk 800 G1 TWR ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_sy4czr@/vmlinuz-5.11.0-34-generic root=ZFS=rpool/ROOT/ubuntu_sy4czr ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: grub-pc N/A RfKill: SourcePackage: initramfs-tools Title: package linux-image-5.4.0-84-generic 5.4.0-84.94 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) dmi.bios.date: 12/17/2013 dmi.bios.release: 2.21 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L01 v02.21 dmi.board.asset.tag: 2UA41526RG dmi.board.name: 18E4 dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: 2UA41526RG dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL01v02.21:bd12/17/2013:br2.21:svnHewlett-Packard:pnHPEliteDesk800G1TWR:pvr:skuC8N27AV:rvnHewlett-Packard:rn18E4:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP EliteDesk 800 G1 TWR dmi.product.sku: C8N27AV dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1944117/+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 1944117] [NEW] package linux-image-5.4.0-84-generic 5.4.0-84.94 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: the kernel has failed to load on several tries. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-84-generic 5.4.0-84.94 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.20 AptOrdering: python3-problem-report:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Sep 17 06:38:08 2021 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2020-05-10 (497 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Hewlett-Packard HP EliteDesk 800 G1 TWR ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_sy4czr@/vmlinuz-5.11.0-34-generic root=ZFS=rpool/ROOT/ubuntu_sy4czr ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: grub-pc N/A RfKill: SourcePackage: initramfs-tools Title: package linux-image-5.4.0-84-generic 5.4.0-84.94 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) dmi.bios.date: 12/17/2013 dmi.bios.release: 2.21 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L01 v02.21 dmi.board.asset.tag: 2UA41526RG dmi.board.name: 18E4 dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: 2UA41526RG dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL01v02.21:bd12/17/2013:br2.21:svnHewlett-Packard:pnHPEliteDesk800G1TWR:pvr:skuC8N27AV:rvnHewlett-Packard:rn18E4:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP EliteDesk 800 G1 TWR dmi.product.sku: C8N27AV dmi.sys.vendor: Hewlett-Packard ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- 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/1944117 Title: package linux-image-5.4.0-84-generic 5.4.0-84.94 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: the kernel has failed to load on several tries. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-84-generic 5.4.0-84.94 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.20 AptOrdering: python3-problem-report:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Sep 17 06:38:08 2021 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2020-05-10 (497 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Hewlett-Packard HP EliteDesk 800 G1 TWR ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_sy4czr@/vmlinuz-5.11.0-34-generic root=ZFS=rpool/ROOT/ubuntu_sy4czr ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: grub-pc N/A RfKill: SourcePackage: initramfs-tools Title: package linux-image-5.4.0-84-generic 5.4.0-84.94 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) dmi.bios.date: 12/17/2013 dmi.bios.release: 2.21 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L01 v02.21 dmi.board.asset.tag: 2UA41526RG dmi.board.name: 18E4 dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: 2UA41526RG dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL01v02.21:bd12/17/2013:br2.21:svnHewlett-Packard:pnHPEliteDesk800G1TWR:pvr:skuC8N27AV:rvnHewlett-Packard:rn18E4:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP EliteDesk 800 G1 TWR dmi.product.sku: C8N27AV dmi.sys.vendor: Hewlett-Packard To man
[Touch-packages] [Bug 1944107] [NEW] No archive files for static compilation are included in the -dev package
Public bug reported: There are no libdrm.a, libdrm_amdgpu.a, etc. files, so it is not possible to compile statically against this library. See attached debdiff to solve this. ** Affects: libdrm (Ubuntu) Importance: Undecided Status: New ** Attachment added: "debdiff.patch" https://bugs.launchpad.net/bugs/1944107/+attachment/5526398/+files/debdiff.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1944107 Title: No archive files for static compilation are included in the -dev package Status in libdrm package in Ubuntu: New Bug description: There are no libdrm.a, libdrm_amdgpu.a, etc. files, so it is not possible to compile statically against this library. See attached debdiff to solve this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1944107/+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
