[Touch-packages] [Bug 1939625] Re: DNS setting in network-manager is ignored
** Changed in: network-manager (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1939625 Title: DNS setting in network-manager is ignored Status in network-manager package in Ubuntu: Fix Released Bug description: DNS setting is network-manager is ignored. Instead, /etc/resolv.conf nameserver is used by programs. see screenshot ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu2.2 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 12 02:36:06 2021 EcryptfsInUse: Yes InstallationDate: Installed on 2021-08-10 (1 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) InterestingModules: b44 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected (site only) started limited enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1939625/+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 1916250] Re: gir1.2-signon-2.0 needs to declare replace on older releases (Groovy2Hirsute and Focal2Jammy)
This bug was fixed in the package libsignon-glib - 2.1-3ubuntu1 --- libsignon-glib (2.1-3ubuntu1) jammy; urgency=medium * add replaces relationship to gir1.2-signon-2.0 package. LP: #1916250 -- Rolf Leggewie Fri, 19 Feb 2021 16:52:20 +0100 ** Changed in: libsignon-glib (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 libsignon-glib in Ubuntu. https://bugs.launchpad.net/bugs/1916250 Title: gir1.2-signon-2.0 needs to declare replace on older releases (Groovy2Hirsute and Focal2Jammy) Status in libsignon-glib package in Ubuntu: Fix Released Bug description: gir1.2-signon-1.0 from groovy gir1.2-signon-2.0 from hirsute above two packages ship the same file /usr/lib/python3/dist- packages/gi/overrides/Signon.py without specifying how to resolve the conflict. Unpacking gir1.2-signon-2.0:amd64 (2.1-3) ... dpkg: error processing archive /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb (--unpack): trying to overwrite '/usr/lib/python3/dist-packages/gi/overrides/Signon.py', which is also in package gir1.2-signon-1.0 1.14+17.04.20161117-0ubuntu5 Errors were encountered while processing: /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Probably needs a conflicts/replaces dependency added to the newer hirsute package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsignon-glib/+bug/1916250/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1948511] [NEW] Very low volume output: Realtek ALC1222 in Omen 30L desktop
Public bug reported: Volume at 100% + Speaker knob at 100% and I get barely audio than can be barely heard. Alsa Info link: http://alsa- project.org/db/?f=5bf0f297f3700c75db822f78d563962f563f355c ``` lspci 00:00.0 Host bridge: Intel Corporation Device 9b33 (rev 05) 00:01.0 PCI bridge: Intel Corporation 6th-10th Gen Core Processor PCIe Controller (x16) (rev 05) 00:12.0 Signal processing controller: Intel Corporation Comet Lake PCH Thermal Controller 00:14.0 USB controller: Intel Corporation Comet Lake USB 3.1 xHCI Host Controller 00:14.2 RAM memory: Intel Corporation Comet Lake PCH Shared SRAM 00:14.3 Network controller: Intel Corporation Comet Lake PCH CNVi WiFi 00:16.0 Communication controller: Intel Corporation Comet Lake HECI Controller 00:17.0 SATA controller: Intel Corporation Comet Lake SATA AHCI Controller 00:1c.0 PCI bridge: Intel Corporation Device 06bc (rev f0) 00:1d.0 PCI bridge: Intel Corporation Comet Lake PCI Express Root Port #9 (rev f0) 00:1f.0 ISA bridge: Intel Corporation Device 0685 00:1f.3 Audio device: Intel Corporation Comet Lake PCH cAVS 00:1f.4 SMBus: Intel Corporation Comet Lake PCH SMBus Controller 00:1f.5 Serial bus controller [0c80]: Intel Corporation Comet Lake PCH SPI Controller 01:00.0 VGA compatible controller: NVIDIA Corporation GA102 [GeForce RTX 3090] (rev a1) 01:00.1 Audio device: NVIDIA Corporation GA102 High Definition Audio Controller (rev a1) 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 16) 03:00.0 Non-Volatile memory controller: Sandisk Corp WD Black SN750 / PC SN730 NVMe SSD ``` ``` sudo dmesg | grep snd [6.624036] snd_hda_intel :00:1f.3: enabling device (0100 -> 0102) [6.624372] snd_hda_intel :01:00.1: enabling device (0100 -> 0102) [6.624423] snd_hda_intel :01:00.1: Disabling MSI [6.624426] snd_hda_intel :01:00.1: Handle vga_switcheroo audio client [6.776175] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC1220: line_outs=1 (0x1b/0x0/0x0/0x0/0x0) type:line [6.776179] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [6.776181] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x14/0x0/0x0/0x0/0x0) [6.776182] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [6.776183] snd_hda_codec_realtek hdaudioC0D0:inputs: [6.776184] snd_hda_codec_realtek hdaudioC0D0: Rear Mic=0x18 [6.776186] snd_hda_codec_realtek hdaudioC0D0: Front Mic=0x19 [6.776187] snd_hda_codec_realtek hdaudioC0D0: Mic=0x1a [6.776188] snd_hda_codec_realtek hdaudioC0D0: Line=0x15 ``` ``` cat /proc/asound/car*/co* | grep Codec Codec: Realtek ALC1220 Codec: Nvidia GPU 9a HDMI/DP ``` ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: 30l alc1222 omen realtek -- 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/1948511 Title: Very low volume output: Realtek ALC1222 in Omen 30L desktop Status in alsa-driver package in Ubuntu: New Bug description: Volume at 100% + Speaker knob at 100% and I get barely audio than can be barely heard. Alsa Info link: http://alsa- project.org/db/?f=5bf0f297f3700c75db822f78d563962f563f355c ``` lspci 00:00.0 Host bridge: Intel Corporation Device 9b33 (rev 05) 00:01.0 PCI bridge: Intel Corporation 6th-10th Gen Core Processor PCIe Controller (x16) (rev 05) 00:12.0 Signal processing controller: Intel Corporation Comet Lake PCH Thermal Controller 00:14.0 USB controller: Intel Corporation Comet Lake USB 3.1 xHCI Host Controller 00:14.2 RAM memory: Intel Corporation Comet Lake PCH Shared SRAM 00:14.3 Network controller: Intel Corporation Comet Lake PCH CNVi WiFi 00:16.0 Communication controller: Intel Corporation Comet Lake HECI Controller 00:17.0 SATA controller: Intel Corporation Comet Lake SATA AHCI Controller 00:1c.0 PCI bridge: Intel Corporation Device 06bc (rev f0) 00:1d.0 PCI bridge: Intel Corporation Comet Lake PCI Express Root Port #9 (rev f0) 00:1f.0 ISA bridge: Intel Corporation Device 0685 00:1f.3 Audio device: Intel Corporation Comet Lake PCH cAVS 00:1f.4 SMBus: Intel Corporation Comet Lake PCH SMBus Controller 00:1f.5 Serial bus controller [0c80]: Intel Corporation Comet Lake PCH SPI Controller 01:00.0 VGA compatible controller: NVIDIA Corporation GA102 [GeForce RTX 3090] (rev a1) 01:00.1 Audio device: NVIDIA Corporation GA102 High Definition Audio Controller (rev a1) 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 16) 03:00.0 Non-Volatile memory controller: Sandisk Corp WD Black SN750 / PC SN730 NVMe SSD ``` ``` sudo dmesg | grep snd [6.624036] snd_hda_intel :00:1f.3: enabling device (0100 -> 0102) [6.624372] snd_hda_intel
[Touch-packages] [Bug 1922414] Re: ssh-agent fails to start (has_option: command not found)
This is still broken on impish when running i3 under X11. Oct 22 15:23:39 operations /usr/libexec/gdm-x-session[5615]: /etc/X11/Xsession.d/30x11-common_xresources: line 16: has_option: command not found Oct 22 15:23:39 operations /usr/libexec/gdm-x-session[5646]: /etc/X11/Xsession.d/75dbus_dbus-launch: line 9: has_option: command not found Oct 22 15:23:39 operations /usr/libexec/gdm-x-session[5658]: /etc/X11/Xsession.d/90x11-common_ssh-agent: line 9: has_option: command not found -- 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/1922414 Title: ssh-agent fails to start (has_option: command not found) Status in gdm3 package in Ubuntu: Fix Released Status in xorg package in Ubuntu: Invalid Bug description: Hi, I have been using ssh-agent for years and since I upgraded my system to Ubuntu 21.04/groovy, ssh-agent fails to start. Here is the error message: # journalctl | grep ssh-agent [...] Apr 02 20:16:32 vougeot /usr/libexec/gdm-x-session[3752]: /etc/X11/Xsession.d/90x11-common_ssh-agent: line 9: has_option: command not found ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: x11-common 1:7.7+22ubuntu1 Uname: Linux 5.11.11-05-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Sat Apr 3 09:02:46 2021 Dependencies: lsb-base 11.1.0ubuntu2 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: tuxedo-keyboard, 3.0.4, 5.11.0-13-generic, x86_64: installed tuxedo-keyboard, 3.0.4, 5.11.0-13-lowlatency, x86_64: installed tuxedo-keyboard, 3.0.4, 5.11.11-05-lowlatency, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Iris Xe Graphics [1558:51a1] MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6 PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.11-05-lowlatency root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2020 dmi.bios.release: 7.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.03RTR dmi.board.name: NS50MU dmi.board.vendor: TUXEDO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.03RTR:bd09/07/2020:br7.3:efr7.2:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50MU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: TUXEDO InfinityBook S 15 Gen6 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: TUXEDO version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4 version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.10-3ubuntu5 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 N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1922414/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1946096] Re: Support manual firmware upgrading for Foxconn and Quectel modems.
Is there a risk that applying these changes will regress the behavior of these modems on systems which have NOT applied the firmware updates? Can the testcase include a check for this? ** Changed in: modemmanager (Ubuntu) Status: Fix Committed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1946096 Title: Support manual firmware upgrading for Foxconn and Quectel modems. Status in OEM Priority Project: In Progress Status in modemmanager package in Ubuntu: Incomplete Bug description: [Impact] The modem certification requires that different modem firmware is used for different network carrier. This needs the firmware upgrading capability during the modem certification process. The modem manufacture vendors (Foxconn and Quectel) provided utilities to do modem's firmware upgrading manually.(LP#1943774, LP#1943780) These utilities are verified to be working when the recent versions(> v 1.18.2) of ModemManager are used with. To support manual firmware upgrading on the current Focal release which is using ModemManager v 1.16.6, we need to apply some patches from v 1.18.2. The requested upstream patches are listed as below: * for Quectel EM160 4G ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/83ac82470589a3672092a0ba0be855093b1cf5e2 * for Foxconn T99W175 ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/21ae558fe3600c84b3ca7dcd9bf50a3ba576c7c9 **https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/76e700f4fd703f952208993330ab098305c13d6b ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/52bf2c641171ded9e617022f40497c8984520371 ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/33e2b023ef01bea9da37ae2beb192f7d92bce47a ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/f72046701659073fbfa97516e155865647acb154 The firmware upgrading was verified using the patched ModemManager v 1.16.6 with the following 2 modems: * Foxconn SDX55 T99W175 5G sub6 PCIE Modem * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem [Test Plan] 1. Install the Ubuntu image. 2. Boot and login the system. 3. Prepare the modem’s firmware and install the firmware upgrading application provided by Foxconn and Quectel 4. Using the firmware upgrading application to upgrade the modem’s firmware 5. Verify if the modem’s firmware upgrading is successful 6. Reboot 7. Verify if the upgraded modem firmware is still working [Where problems could occur] The requested upstream patches are for these 2 specific modems. This should not affect existing generic functions and other modems. [Other Info] The firmware and the upgrading utilities can be downloaded from the following link: * LP#1943774 for Quectel modems * LP#1943780 for Foxconn modems To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946096/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1827958] Re: [Acer Swift 5 SF514-53T] No sound at all from the inbuilt microphone - since installation of system
I am using Acer Swift SF514-52T. This issue disappeared after I upgraded to Ubuntu 21.10. -- 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/1827958 Title: [Acer Swift 5 SF514-53T] No sound at all from the inbuilt microphone - since installation of system Status in alsa-driver package in Ubuntu: Confirmed Bug description: The inbuilt microphone has never worked on the version of ubuntu on this computer. The hardware works completely fine on other operating systems (Windows). Distribution: Ubuntu 18.04.2 LTS alsa-base: Installed: 1.0.25+dfsg-0ubuntu5 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.19.21-041921-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lune 1908 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon May 6 23:54:58 2019 InstallationDate: Installed on 2019-01-06 (120 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_AlsaRecordingTestStderr: a r e c o r d : p c m _ r e a d : 2 1 0 3 : r e a d e r r o r : I n p u t / o u t p u t e r r o r Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1273 F pulseaudio lune 1908 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/17/2018 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.03 dmi.board.name: Carlsberg_WL dmi.board.vendor: WL dmi.board.version: V1.03 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.03 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.03:bd12/17/2018:svnAcer:pnSwiftSF514-53T:pvrV1.03:rvnWL:rnCarlsberg_WL:rvrV1.03:cvnAcer:ct10:cvrV1.03: dmi.product.family: Swift 5 dmi.product.name: Swift SF514-53T dmi.product.sku: dmi.product.version: V1.03 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1827958/+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 1948498] [NEW] Bluetooth Headset not working when Lenovo P14s AMD Gen1 is connected to Lenovo USB Dock 40AY0090EU
Public bug reported: When the Laptop is not connected to it's dock, the bluethooth headset works. As soon as it is connected to a Lenovo 40AY0090EU Dock, sound stops on the headsets and plays via the display connected via DisplayPort. The headset is still available in sound settings, but even if selected, no sound plays on the headset. If I change the configuration (HSP/A2DP), a short "click" sound can be heard on the headset, so apparently there's still something going on between the laptop and the headsets. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.11 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Oct 22 22:04:27 2021 InstallationDate: Installed on 2021-09-29 (23 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/30/2021 dmi.bios.release: 1.35 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET66W(1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20Y1000MGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.35 dmi.modalias: dmi:bvnLENOVO:bvrR1BET66W(1.35):bd07/30/2021:br1.35:efr1.35:svnLENOVO:pn20Y1000MGE:pvrThinkPadP14sGen1:skuLENOVO_MT_20Y1_BU_Think_FM_ThinkPadP14sGen1:rvnLENOVO:rn20Y1000MGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P14s Gen 1 dmi.product.name: 20Y1000MGE dmi.product.sku: LENOVO_MT_20Y1_BU_Think_FM_ThinkPad P14s Gen 1 dmi.product.version: ThinkPad P14s Gen 1 dmi.sys.vendor: LENOVO ** Affects: pulseaudio (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 pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1948498 Title: Bluetooth Headset not working when Lenovo P14s AMD Gen1 is connected to Lenovo USB Dock 40AY0090EU Status in pulseaudio package in Ubuntu: New Bug description: When the Laptop is not connected to it's dock, the bluethooth headset works. As soon as it is connected to a Lenovo 40AY0090EU Dock, sound stops on the headsets and plays via the display connected via DisplayPort. The headset is still available in sound settings, but even if selected, no sound plays on the headset. If I change the configuration (HSP/A2DP), a short "click" sound can be heard on the headset, so apparently there's still something going on between the laptop and the headsets. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.11 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Oct 22 22:04:27 2021 InstallationDate: Installed on 2021-09-29 (23 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/30/2021 dmi.bios.release: 1.35 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET66W(1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20Y1000MGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.35 dmi.modalias: dmi:bvnLENOVO:bvrR1BET66W(1.35):bd07/30/2021:br1.35:efr1.35:svnLENOVO:pn20Y1000MGE:pvrThinkPadP14sGen1:skuLENOVO_MT_20Y1_BU_Think_FM_ThinkPadP14sGen1:rvnLENOVO:rn20Y1000MGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P14s Gen 1 dmi.product.name: 20Y1000MGE dmi.product.sku: LENOVO_MT_20Y1_BU_Think_FM_ThinkPad P14s Gen 1 dmi.product.version: ThinkPad P14s Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1948498/+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 1916250] Re: gir1.2-signon-2.0 needs to declare replace on older releases (Groovy2Hirsute and Focal2Jammy)
Given that hirsute and impish are both stable releases and focal2impish will be a supported upgrade path when hirsute becomes end of life there is need for an SRU. So could you please add the SRU template information to the bug report? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libsignon-glib in Ubuntu. https://bugs.launchpad.net/bugs/1916250 Title: gir1.2-signon-2.0 needs to declare replace on older releases (Groovy2Hirsute and Focal2Jammy) Status in libsignon-glib package in Ubuntu: In Progress Bug description: gir1.2-signon-1.0 from groovy gir1.2-signon-2.0 from hirsute above two packages ship the same file /usr/lib/python3/dist- packages/gi/overrides/Signon.py without specifying how to resolve the conflict. Unpacking gir1.2-signon-2.0:amd64 (2.1-3) ... dpkg: error processing archive /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb (--unpack): trying to overwrite '/usr/lib/python3/dist-packages/gi/overrides/Signon.py', which is also in package gir1.2-signon-1.0 1.14+17.04.20161117-0ubuntu5 Errors were encountered while processing: /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Probably needs a conflicts/replaces dependency added to the newer hirsute package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsignon-glib/+bug/1916250/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1946499] Re: installation of deb-packages with gdebi-gtk shows "dpkg: error: unable to read filedescriptor flags for : Bad file descr
I'm unsubscribing the ubuntu-sponsors team as this has already been sponsored albeit rejected by Robie. However, the package can still be accepted from the rejected queue once the bug description has been squared away. I've subscribed to the bug and will accept the package once the SRU information has been added. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1946499 Title: installation of deb-packages with gdebi-gtk shows "dpkg: error: unable to read filedescriptor flags for : Bad file descriptor" in gdebi terminal, package is not installed Status in Ubuntu MATE: Invalid Status in gdebi package in Ubuntu: Fix Released Status in vte2.91 package in Ubuntu: Confirmed Status in gdebi source package in Impish: Triaged Bug description: Steps to reproduce: 1. Install Ubuntu MATE 21.10 2. Open Firefox, navigate to discord.com 3. Download deb-file. At time of writing from the https://dl.discordapp.net/apps/linux/0.0.16/discord-0.0.16.deb link 4. Open Caja in ~/Downloads folder and use GDebi to install the discord-0.0.16.deb file 5. In the GDebi window click Install button Expected results: * Gdebi quietly install discord package, there are no error messages in its terminal Actual results: * Gdebi terminal shows the error in the last line ``` Selecting previously unselected package gconf2-common. (Reading database ... 457178 files and directories currently installed.) Preparing to unpack .../0-gconf2-common_3.2.6-7ubuntu2_all.deb ... Unpacking gconf2-common (3.2.6-7ubuntu2) ... Selecting previously unselected package libgconf-2-4:amd64. Preparing to unpack .../1-libgconf-2-4_3.2.6-7ubuntu2_amd64.deb ... Unpacking libgconf-2-4:amd64 (3.2.6-7ubuntu2) ... Selecting previously unselected package gconf-service-backend. Preparing to unpack .../2-gconf-service-backend_3.2.6-7ubuntu2_amd64.deb ... Unpacking gconf-service-backend (3.2.6-7ubuntu2) ... Selecting previously unselected package gconf-service. Preparing to unpack .../3-gconf-service_3.2.6-7ubuntu2_amd64.deb ... Unpacking gconf-service (3.2.6-7ubuntu2) ... Selecting previously unselected package libappindicator1. Preparing to unpack .../4-libappindicator1_12.10.1+20.10.20200706.1-0ubuntu1_amd64.deb ... Unpacking libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ... Selecting previously unselected package libunwind-13:amd64. Preparing to unpack .../5-libunwind-13_1%3a13.0.0-2_amd64.deb ... Unpacking libunwind-13:amd64 (1:13.0.0-2) ... Selecting previously unselected package libc++abi1-13:amd64. Preparing to unpack .../6-libc++abi1-13_1%3a13.0.0-2_amd64.deb ... Unpacking libc++abi1-13:amd64 (1:13.0.0-2) ... Selecting previously unselected package libc++1-13:amd64. Preparing to unpack .../7-libc++1-13_1%3a13.0.0-2_amd64.deb ... Unpacking libc++1-13:amd64 (1:13.0.0-2) ... Selecting previously unselected package libc++1:amd64. Preparing to unpack .../8-libc++1_1%3a13.0-53~exp1_amd64.deb ... Unpacking libc++1:amd64 (1:13.0-53~exp1) ... Setting up libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ... Setting up gconf2-common (3.2.6-7ubuntu2) ... Creating config file /etc/gconf/2/path with new version Setting up libunwind-13:amd64 (1:13.0.0-2) ... Setting up libc++abi1-13:amd64 (1:13.0.0-2) ... Setting up libc++1-13:amd64 (1:13.0.0-2) ... Setting up libc++1:amd64 (1:13.0-53~exp1) ... Setting up gconf-service (3.2.6-7ubuntu2) ... Processing triggers for libc-bin (2.34-0ubuntu2) ... Processing triggers for sgml-base (1.30) ... Setting up libgconf-2-4:amd64 (3.2.6-7ubuntu2) ... Setting up gconf-service-backend (3.2.6-7ubuntu2) ... Processing triggers for libc-bin (2.34-0ubuntu2) ... dpkg: error: unable to read filedescriptor flags for : Bad file descriptor ``` and as the result Discord package is not installed . ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gdebi 0.9.5.7+nmu5ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Fri Oct 8 18:17:36 2021 InstallationDate: Installed on 2021-10-08 (0 days ago) InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Daily amd64 (20211008) PackageArchitecture: all SourcePackage: gdebi UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2021-10-08T15:41:41.001986 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1946499/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages
[Touch-packages] [Bug 1941962] Re: pulseaudio crashed with SIGSEGV in XFreeGC() from XCloseDisplay() from pa_x11_wrapper_unref()
Just a heads-up, fix for libx11 issue 139 is now merged upstream https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/84 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1941962 Title: pulseaudio crashed with SIGSEGV in XFreeGC() from XCloseDisplay() from pa_x11_wrapper_unref() Status in X.Org X server: Unknown Status in pulseaudio package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/52094416ad4b4132ebf639ec8530fed1fdbac584 crash ProblemType: Crash DistroRelease: Ubuntu 21.10 Package: pulseaudio 1:15.0+dfsg1-1ubuntu2 Uname: Linux 5.13.13-xanmod1-cacule x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anasc 1719 F pulseaudio /dev/snd/pcmC0D0p: anasc 1719 F...m pulseaudio CasperMD5CheckResult: pass Date: Sat Aug 28 21:00:59 2021 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2021-08-26 (2 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210824) ProcCmdline: /usr/bin/pulseaudio --daemonize=no --log-target=journal SegvAnalysis: Segfault happened at: 0x7fbcc9d6a8a4 : mov%edx,0x4(%rax) PC (0x7fbcc9d6a8a4) ok source "%edx" ok destination "0x4(%rax)" (0x0004) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: pulseaudio StacktraceTop: XFreeGC () from /lib/x86_64-linux-gnu/libX11.so.6 XCloseDisplay () from /lib/x86_64-linux-gnu/libX11.so.6 pa_x11_wrapper_unref () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-15.0.so module_x11_publish_LTX_pa__done () from /usr/lib/pulse-15.0+dfsg1/modules/module-x11-publish.so ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-15.0.so Title: pulseaudio crashed with SIGSEGV in XFreeGC() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo dmi.bios.date: 02/05/2021 dmi.bios.release: 15.14 dmi.bios.vendor: Insyde dmi.bios.version: F.14 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 86E2 dmi.board.vendor: HP dmi.board.version: 95.36 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 95.36 dmi.modalias: dmi:bvnInsyde:bvrF.14:bd02/05/2021:br15.14:efr95.36:svnHP:pnHPPavilionLaptop15-cs3xxx:pvrType1ProductConfigId:sku5SU52EA#BH4:rvnHP:rn86E2:rvr95.36:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-cs3xxx dmi.product.sku: 5SU52EA#BH4 dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP separator: To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1941962/+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 1679346] Re: Missing dep8 tests
** Merge proposal linked: https://code.launchpad.net/~lvoytek/ubuntu/+source/net-tools/+git/net-tools/+merge/410677 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to net-tools in Ubuntu. https://bugs.launchpad.net/bugs/1679346 Title: Missing dep8 tests Status in net-tools package in Ubuntu: In Progress Bug description: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 As of April 3, 2017, this source package did not contain package tests in the current development release of Ubuntu, named Zesty. This was determined by running `pull-lp-source net-tools zesty` and then checking for the existence of 'debian/tests/' and 'debian/tests/control'. The package was also checked for 1) a test suite declaration in the debian/control file, 2) any 'test', 'tests', 'testsuite', or 'test-suite' directories, 3) go tests (if applicable), and 4) a test suite declared in a setup.py (if applicable). If you feel this report is incorrect (e.g. this is a library or a source only package) or the check above missed some other package level test please reply explaining why and mark this bug as 'invalid'. Test automation is essential to higher levels of quality and confidence in updates to packages. dep8 tests [1] specify how automatic testing can be integrated into packages and then run by package maintainers before new uploads. This defect is to report the absence of these tests and to report the opportunity as a potential item for development by both new and experienced contributors. Thanks! [1] http://packaging.ubuntu.com/html/auto-pkg-test.html affects ubuntu/net-tools status new importance wishlist tag needs-dep8 - --- Joshua Powers Ubuntu Server Canonical Ltd -BEGIN PGP SIGNATURE- iQIcBAEBCAAGBQJY4siLAAoJEIP8BxPaZgwlKlgP/1tp7NP3mLPZyukvkknbekpa 0Cd02/t3Jy9JNJK/hnH50b0JUQ3HMFAvOIPb6SZgUH7NOlrE2Hgprcyo/OFZ5rRB fX3qc5PRX83VUM2D7IQtaQZqBU+y0vHDZ5DjWWfhke6E9SZsUHybVCAP+yBQXorQ DiEffoTUGkOfi+5S7V57FWw3rBxjeNRBxeoerfq/a0GS4YvTanQgFOMC1weOz/8J I64olcq3EMrUpClxKF2LQ6H0xDdpbF0i3SZfhi5h294p1qF8l4PS0rLT2sqr85Pr 1yz0jORhribXZy3M7thUMz/aLDmimL9+7nPL2lz40JjbNjNTVPZ+s8RguKWYYBx3 DBDJBfdG5JoLhsDDon7PKOILKj40S14KtmdbBY0VGNGuVSz3+m0WiTnTdJQzWWHR FNsfGjD+mdARcXqr11xgp/zY6VEVhG0AFIaZZgs1PbqvqL3FtGPgEGwXetgIU5bS J2suTN+WEEf8nI8kMi6PsUFfGsMogZTRHy04PCfPem0MBB3Olrmulm9bXcfbZ1Le 0eep3OVn06fm43x7YQaI/hzGl959pdppAahlFWTKvF0vfq7mJcSb6n1QpeWhvqeB tBAaV1redyI5ovDGAAVuFzrxJ7rWRKw4PVYln/C2Mayzb1S2dTwpjLtA9kcfQZJQ ZY8eSrPyf6eh2z8LVlR+ =WKVW -END PGP SIGNATURE- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-tools/+bug/1679346/+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 1948476] [NEW] [SRU] Allow target units to fail
Public bug reported: [Impact] A systemd regression in focal made it think that target units cannot fail, which produced warnings like: emergency.target: Requested dependency OnFailure=reboot.target ignored (target units cannot fail). So the OnFailure settings are ignored for targets (see https://github.com/snapcore/core-initrd/issues/33 for details). Upstream fixed the issue in v246: https://github.com/systemd/systemd/commit/94d1ddbd7cd15b1073757eb5ae0645c83f0b414c [Test Plan] Test on a UC system and check that the above warnings are not shown anymore. Check that when a target service type fails, the OnFailure setting is used and the mentioned service is run. [Where problems could occur] Issues might happen if some target has an OnFailure setting that was never run in the past because of this bug, and the behavior is not really right because it was never tested. However, OnFailure is not used that much on 20.04 in target services: /lib/systemd $ find . -name \*.target | xargs grep OnFailure /lib/systemd $ /etc/systemd $ find . -name \*.target | xargs grep OnFailure /etc/systemd $ I've seen it only in emergency.target for UC20. [Other Info] None ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Attachment added: "target-units-can-fail.patch" https://bugs.launchpad.net/bugs/1948476/+attachment/5535284/+files/target-units-can-fail.patch -- 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/1948476 Title: [SRU] Allow target units to fail Status in systemd package in Ubuntu: New Bug description: [Impact] A systemd regression in focal made it think that target units cannot fail, which produced warnings like: emergency.target: Requested dependency OnFailure=reboot.target ignored (target units cannot fail). So the OnFailure settings are ignored for targets (see https://github.com/snapcore/core-initrd/issues/33 for details). Upstream fixed the issue in v246: https://github.com/systemd/systemd/commit/94d1ddbd7cd15b1073757eb5ae0645c83f0b414c [Test Plan] Test on a UC system and check that the above warnings are not shown anymore. Check that when a target service type fails, the OnFailure setting is used and the mentioned service is run. [Where problems could occur] Issues might happen if some target has an OnFailure setting that was never run in the past because of this bug, and the behavior is not really right because it was never tested. However, OnFailure is not used that much on 20.04 in target services: /lib/systemd $ find . -name \*.target | xargs grep OnFailure /lib/systemd $ /etc/systemd $ find . -name \*.target | xargs grep OnFailure /etc/systemd $ I've seen it only in emergency.target for UC20. [Other Info] None To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1948476/+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 1689461] Re: bluetoothd crashed with SIGSEGV from g_io_channel_shutdown from attio_cleanup from browse_request_cancel from device_remove from btd_adapter_remove_device
I experience what might be a similar crash, albeit on Linux Mint. I have put a crash dump here: https://termbin.com/b726b. Also, I reported the issue against Mint, here: https://github.com/linuxmint/cinnamon/issues/10412#issuecomment-949710193. I am unsure whether this the current page is the right place to report this problem (even if it _is_ closely related to the problem that this page mentions). ** Bug watch added: github.com/linuxmint/cinnamon/issues #10412 https://github.com/linuxmint/cinnamon/issues/10412 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1689461 Title: bluetoothd crashed with SIGSEGV from g_io_channel_shutdown from attio_cleanup from browse_request_cancel from device_remove from btd_adapter_remove_device Status in bluez package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.37-0ubuntu5, the problem page at https://errors.ubuntu.com/problem/732cce930e4db100b0ec943638e1029f4655fbf9 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689461/+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 1948357] Re: sshd have no USER_LOGOUT audit event
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: openssh (Ubuntu) Status: New => Confirmed -- 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/1948357 Title: sshd have no USER_LOGOUT audit event Status in openssh package in Ubuntu: Confirmed Bug description: ubuntu 18.04 lizj@FNSTPC:~$ sudo aureport -e -i --summary | grep USER 43241 USER_END 16946 USER_START 16718 USER_ACCT 658 USER_AUTH 543 USER_CMD 255 USER_LOGIN 9 USER_ROLE_CHANGE 5 USER_ERR 2 USER_CHAUTHTOK 1 ADD_USER lizj@FNSTPC:~/.local/bin$ dpkg -l | grep openssh ii openssh-client1:7.6p1-4ubuntu0.5 amd64secure shell (SSH) client, for secure access to remote machines ii openssh-server1:7.6p1-4ubuntu0.5 amd64secure shell (SSH) server, for secure access from remote machines ii openssh-sftp-server 1:7.6p1-4ubuntu0.5 amd64secure shell (SSH) sftp server module, for SFTP access from remote machines lizj@FNSTPC:~/.local/bin$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.6 LTS Release: 18.04 Codename: bionic while in my fedora 33 host, it includes USER_LOGOUT as below fedora 33 [root@iaas-rpma linux]# aureport -e -i --summary | grep USER 7356 CRYPTO_KEY_USER 2103 USER_START 1649 USER_END 1268 USER_ACCT 1108 USER_ROLE_CHANGE 1029 USER_AUTH 895 USER_LOGIN 789 USER_LOGOUT 60 USER_CMD 14 USER_ERR 3 USER_MGMT 3 USER_CHAUTHTOK 1 ADD_USER [root@iaas-rpma ~]# rpm -qa | grep openssh openssh-8.4p1-1.1.fc33.x86_64 openssh-clients-8.4p1-1.1.fc33.x86_64 openssh-server-8.4p1-1.1.fc33.x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1948357/+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 1948339] Re: Logon screen can be bypassed using various shortcuts
Thanks :) I haven't registered a CVE yet and I'm waiting for final confirmation which components are causing the described issue. Happy to contribute to the ArcticaProject issue tracker directly. As you also mentioned I can confirm that the affected arctica-greeter version is present in the following versions of Ubuntu Mate: Ubuntu Mate 20.10 - Groovy Gorilla Ubuntu Mate 21.04 - Hirsute Hippo Ubuntu Mate 21.10 - Impish Indri It doesn't seem to work for 20.04 - Focal Fossa. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1948339 Title: Logon screen can be bypassed using various shortcuts Status in Ubuntu MATE: New Status in arctica-greeter package in Ubuntu: New Status in lightdm package in Ubuntu: New Status in mate-settings-daemon package in Ubuntu: New Bug description: Hi, my little daughter discovered a logon screen bypass in Ubuntu Mate 21.10 after hitting the keyboard for a while. It turns out that several keyboard shortcuts are allowed while Ubuntu Mate is locked (arctica-greeter): - Mod4 + S (mate-search-tool) - Mod4 + E (Open Caja / File Explorer) - CTRL + Shift + Esc (mate-system-monitor) - PRNT (Screenshot) All of the mentioned shortcuts could be used to spawn a file explorer (Caja) or various other binaries as user "lightdm", who owns the logon screen. Although an interactive terminal like mate-terminal, xterm, lxterm etc. could not be opened directly, there are various options to run commands as the lightdm user, for example by creating a shell script using "caja", and execute it directly using the GUI. I've attached Proof-of-Concept GIFs for all shortcuts mentioned above. There might be additional shortcuts that could be used to achieve the same, however I'm not aware about every shortcut that is configured, but I suppose that the root cause is located somewhere in arctica- greeter, rather than within every single binary launched by shortcuts. The bug was reproduced on a fresh installation of Ubuntu Mate 21.10. I haven't tested other versions of Ubuntu Mate yet. Please find additional version details below: $ apt-cache policy lightdm lightdm: Installed: 1.30.0-0ubuntu4 Candidate: 1.30.0-0ubuntu4 Version table: *** 1.30.0-0ubuntu4 500 500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy arctica-greeter arctica-greeter: Installed: 0.99.1.5-2nmu1 Candidate: 0.99.1.5-2nmu1 Version table: *** 0.99.1.5-2nmu1 500 500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status Thanks, Basti To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1948339/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1942685] Re: pulseaudio crashed with SIGSEGV in _IceTransClose()
Could someone having the issue set log-level=debug in /etc/pulse/daemon.conf , restart and add the journalctl log after getting the bug? ** Changed in: pulseaudio (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1942685 Title: pulseaudio crashed with SIGSEGV in _IceTransClose() Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Fix Committed Bug description: https://errors.ubuntu.com/problem/877172e07ed9f86b0674cd458a5aaf24b37fb01e --- Installing Xubuntu Impish daily ISO 04092021 After install I rebooted - applied updates and then rebooted again- the errors (pulseaudio crashed with SIGSEGV in _IceTransClose() ) occurred after logging in. ProblemType: Crash DistroRelease: Ubuntu 21.10 Package: pulseaudio 1:15.0+dfsg1-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1 Uname: Linux 5.13.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kx 847 F pulseaudio CasperMD5CheckResult: pass Date: Sat Sep 4 16:43:45 2021 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2021-09-04 (0 days ago) InstallationMedia: Xubuntu 21.10 "Impish Indri" - Alpha amd64 (20210904) ProcCmdline: /usr/bin/pulseaudio --daemonize=no --log-target=journal Signal: 11 SourcePackage: pulseaudio StacktraceTop: _IceTransClose () from /lib/x86_64-linux-gnu/libICE.so.6 _IceFreeConnection () from /lib/x86_64-linux-gnu/libICE.so.6 IceCloseConnection () from /lib/x86_64-linux-gnu/libICE.so.6 SmcCloseConnection () from /lib/x86_64-linux-gnu/libSM.so.6 ?? () from /usr/lib/pulse-15.0+dfsg1/modules/module-x11-xsmp.so Title: pulseaudio crashed with SIGSEGV in _IceTransClose() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo dmi.bios.date: 12/23/2020 dmi.bios.release: 1.51 dmi.bios.vendor: LENOVO dmi.bios.version: DKCN51WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V14-IIL dmi.ec.firmware.release: 1.51 dmi.modalias: dmi:bvnLENOVO:bvrDKCN51WW:bd12/23/2020:br1.51:efr1.51:svnLENOVO:pn82C4:pvrLenovoV14-IIL:skuLENOVO_MT_82C4_BU_idea_FM_V14-IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoV14-IIL: dmi.product.family: V14-IIL dmi.product.name: 82C4 dmi.product.sku: LENOVO_MT_82C4_BU_idea_FM_V14-IIL dmi.product.version: Lenovo V14-IIL dmi.sys.vendor: LENOVO separator: To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1942685/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1896772] Re: systemd-resolved configures no Current Scopes on start
I have the same issue: systemd-resolved: Failed to save link data /run/systemd/resolve/netif/3: Permission denied The netif folder is indeed owned by root. If I change the ownership to systemd-resolved and restart the service, there is no error but as soon as I reboot the system, the ownership is reverted to root and the error is back. Also, I searched the log for other resolved messages and found the error below as well: nm-dispatcher[4641]: /etc/network/if-up.d/resolved: 12: mystatedir: not found -- 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/1896772 Title: systemd-resolved configures no Current Scopes on start Status in systemd package in Ubuntu: Confirmed Bug description: Running groovy on the desktop, with the systemd packages that migrated today(/overnight EDT). # Steps to reproduce: 1) `systemctl restart systemd-resolved.service` (This is a minimal reproducer, but I first saw this after an apt upgrade of systemd.) # Expected behaviour: DNS continues to work, status looks like this: Link 2 (enp5s0) Current Scopes: DNS DefaultRoute setting: yes LLMNR setting: yes MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no Current DNS Server: 192.168.1.1 DNS Servers: 192.168.1.1 DNS Domain: ~. lan # Actual behaviour: DNS is unconfigured: Link 2 (enp5s0) Current Scopes: none DefaultRoute setting: no LLMNR setting: yes MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no # Workaround Disconnecting and reconnecting my network connection restored DNS functionality. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: systemd 246.5-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: i3 CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Wed Sep 23 09:05:42 2020 InstallationDate: Installed on 2019-05-07 (504 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Gigabyte Technology Co., Ltd. B450M DS3H ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-18-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash resume=UUID=73909634-a75d-42c9-8f66-a69138690756 pcie_aspm=off vt.handoff=7 RebootRequiredPkgs: gnome-shell SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. -- Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. UpgradeStatus: Upgraded to groovy on 2020-06-22 (92 days ago) dmi.bios.date: 01/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: Default string dmi.board.name: B450M DS3H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd01/25/2019:br5.13:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B450M DS3H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1896772/+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 1948438] [NEW] Printer kan niet worden gestart. Controleer de configuratie van uw printer
Public bug reported: My Canon MP499 printer is recognized, but if i try to use it in LibreOffice Writer, a message appears (see above). Using translate, it shows this message: Printer cannot be started. Check your printer's configuration fred@fred-Latitude-E6430:~$ lpstat fred@fred-Latitude-E6430:~$ lpstat -t scheduler is running no system default destination device for DCP-L3550CDW: dnssd://Brother%20DCP-L3550CDW%20series._ipp._tcp.local/?uuid=e3248000-80ce-11db-8000-3c2af4dc9c43 device for MP495-series: usb://Canon/MP495%20series?serial=24F65A=1 DCP-L3550CDW accepting requests since vr 23 jul 2021 12:55:49 CEST MP495-series accepting requests since vr 22 okt 2021 10:58:01 CEST printer DCP-L3550CDW is idle. enabled since vr 23 jul 2021 12:55:49 CEST printer MP495-series is idle. enabled since vr 22 okt 2021 10:58:01 CEST fred@fred-Latitude-E6430:~$ sudo service cups status [sudo] wachtwoord voor fred: ● cups.service - CUPS Scheduler Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: > Active: active (running) since Fri 2021-10-22 10:56:11 CEST; 8min ago TriggeredBy: ● cups.path ● cups.socket Docs: man:cupsd(8) Main PID: 977 (cupsd) Tasks: 3 (limit: 9421) Memory: 24.9M CGroup: /system.slice/cups.service ├─ 977 /usr/sbin/cupsd -l ├─2129 /usr/lib/cups/notifier/dbus dbus:// └─4449 /usr/lib/cups/notifier/dbus dbus:// okt 22 10:56:11 fred-Latitude-E6430 systemd[1]: Started CUPS Scheduler. okt 22 10:57:39 fred-Latitude-E6430 /hpfax[2022]: [2022]: error: Failed to crea> lines 1-16/16 (END)...skipping... ● cups.service - CUPS Scheduler Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: > Active: active (running) since Fri 2021-10-22 10:56:11 CEST; 8min ago TriggeredBy: ● cups.path ● cups.socket Docs: man:cupsd(8) Main PID: 977 (cupsd) Tasks: 3 (limit: 9421) Memory: 24.9M CGroup: /system.slice/cups.service ├─ 977 /usr/sbin/cupsd -l ├─2129 /usr/lib/cups/notifier/dbus dbus:// └─4449 /usr/lib/cups/notifier/dbus dbus:// okt 22 10:56:11 fred-Latitude-E6430 systemd[1]: Started CUPS Scheduler. okt 22 10:57:39 fred-Latitude-E6430 /hpfax[2022]: [2022]: error: Failed to crea> ~ ~ ~ ~ ~ ~ ~ ~ lines 1-16/16 (END)...skipping... ● cups.service - CUPS Scheduler Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: > Active: active (running) since Fri 2021-10-22 10:56:11 CEST; 8min ago TriggeredBy: ● cups.path ● cups.socket Docs: man:cupsd(8) Main PID: 977 (cupsd) Tasks: 3 (limit: 9421) Memory: 24.9M CGroup: /system.slice/cups.service ├─ 977 /usr/sbin/cupsd -l ├─2129 /usr/lib/cups/notifier/dbus dbus:// └─4449 /usr/lib/cups/notifier/dbus dbus:// okt 22 10:56:11 fred-Latitude-E6430 systemd[1]: Started CUPS Scheduler. okt 22 10:57:39 fred-Latitude-E6430 /hpfax[2022]: [2022]: error: Failed to crea> ~ ~ ~ ~ ~ ~ ~ ~ ~ lines 1-16/16 (END)...skipping... ● cups.service - CUPS Scheduler Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: > Active: active (running) since Fri 2021-10-22 10:56:11 CEST; 8min ago TriggeredBy: ● cups.path ● cups.socket Docs: man:cupsd(8) Main PID: 977 (cupsd) Tasks: 3 (limit: 9421) Memory: 24.9M CGroup: /system.slice/cups.service ├─ 977 /usr/sbin/cupsd -l ├─2129 /usr/lib/cups/notifier/dbus dbus:// └─4449 /usr/lib/cups/notifier/dbus dbus:// okt 22 10:56:11 fred-Latitude-E6430 systemd[1]: Started CUPS Scheduler. okt 22 10:57:39 fred-Latitude-E6430 /hpfax[2022]: [2022]: error: Failed to crea> ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ lines 1-16/16 (END)...skipping... ● cups.service - CUPS Scheduler Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: > Active: active (running) since Fri 2021-10-22 10:56:11 CEST; 8min ago TriggeredBy: ● cups.path ● cups.socket Docs: man:cupsd(8) Main PID: 977 (cupsd) Tasks: 3 (limit: 9421) Memory: 24.9M CGroup: /system.slice/cups.service ├─ 977 /usr/sbin/cupsd -l ├─2129 /usr/lib/cups/notifier/dbus dbus:// └─4449 /usr/lib/cups/notifier/dbus dbus:// okt 22 10:56:11 fred-Latitude-E6430 systemd[1]: Started CUPS Scheduler. okt 22 10:57:39 fred-Latitude-E6430 /hpfax[2022]: [2022]: error: Failed to crea> ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ lines 1-16/16 (END)...skipping... ● cups.service - CUPS Scheduler Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: > Active: active (running) since Fri 2021-10-22 10:56:11 CEST; 8min ago TriggeredBy: ● cups.path ● cups.socket Docs: man:cupsd(8) Main PID: 977 (cupsd) Tasks: 3 (limit: 9421) Memory: 24.9M CGroup: /system.slice/cups.service ├─ 977
[Touch-packages] [Bug 1926547] Re: Add Dell Privacy Mic Mute Key mapping
** Changed in: oem-priority/focal Status: New => Fix Released -- 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/1926547 Title: Add Dell Privacy Mic Mute Key mapping Status in OEM Priority Project: Fix Released Status in OEM Priority Project focal series: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Released Status in systemd source package in Groovy: Fix Released Status in systemd source package in Hirsute: Fix Released Bug description: [Impact] * Dell introduces new function called Dell Privacy, it utilizes hardware mute to control audio and camera. The commit map the reported key event to mic mute for making userspace can work as before, "Mic Mute" dialog pop-up while the mic mute button is pressed. [Test Plan] * Use a Dell machine, which has Dell privacy function, and press mic mute key. GUI will pop up "Mic Mute" icon. [Where problems could occur] * This change adds key event mapping in hwdb, which won't impact other hardware. any regression would likely cause problems with key(s) from the specific dell kb matching the modified listing in the hw db. [Other Info] * The change can only work with kernel commit on some specific hardware, ex. Latitude 9520. The commit series is "hardware-privacy-implementation-for-dell-laptop" in alsa-devel kernel tree. https://patchwork.kernel.org/project/alsa-devel/list/?series=465445 * This change has been verified on Dell machine. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1926547/+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 1948339] Re: Logon screen can be bypassed using various shortcuts
Lightdm - https://github.com/canonical/lightdm/issues/214 . -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1948339 Title: Logon screen can be bypassed using various shortcuts Status in Ubuntu MATE: New Status in arctica-greeter package in Ubuntu: New Status in lightdm package in Ubuntu: New Status in mate-settings-daemon package in Ubuntu: New Bug description: Hi, my little daughter discovered a logon screen bypass in Ubuntu Mate 21.10 after hitting the keyboard for a while. It turns out that several keyboard shortcuts are allowed while Ubuntu Mate is locked (arctica-greeter): - Mod4 + S (mate-search-tool) - Mod4 + E (Open Caja / File Explorer) - CTRL + Shift + Esc (mate-system-monitor) - PRNT (Screenshot) All of the mentioned shortcuts could be used to spawn a file explorer (Caja) or various other binaries as user "lightdm", who owns the logon screen. Although an interactive terminal like mate-terminal, xterm, lxterm etc. could not be opened directly, there are various options to run commands as the lightdm user, for example by creating a shell script using "caja", and execute it directly using the GUI. I've attached Proof-of-Concept GIFs for all shortcuts mentioned above. There might be additional shortcuts that could be used to achieve the same, however I'm not aware about every shortcut that is configured, but I suppose that the root cause is located somewhere in arctica- greeter, rather than within every single binary launched by shortcuts. The bug was reproduced on a fresh installation of Ubuntu Mate 21.10. I haven't tested other versions of Ubuntu Mate yet. Please find additional version details below: $ apt-cache policy lightdm lightdm: Installed: 1.30.0-0ubuntu4 Candidate: 1.30.0-0ubuntu4 Version table: *** 1.30.0-0ubuntu4 500 500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy arctica-greeter arctica-greeter: Installed: 0.99.1.5-2nmu1 Candidate: 0.99.1.5-2nmu1 Version table: *** 0.99.1.5-2nmu1 500 500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status Thanks, Basti To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1948339/+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 1948339] Re: Logon screen can be bypassed using various shortcuts
Upstream is now informed via https://github.com/ArcticaProject/arctica-greeter/issues/28 . I cited this bug there. Bastian Kanbach (bkanbach), you are welcome to add more comments there. ** Bug watch added: github.com/ArcticaProject/arctica-greeter/issues #28 https://github.com/ArcticaProject/arctica-greeter/issues/28 ** Bug watch added: github.com/canonical/lightdm/issues #214 https://github.com/canonical/lightdm/issues/214 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1948339 Title: Logon screen can be bypassed using various shortcuts Status in Ubuntu MATE: New Status in arctica-greeter package in Ubuntu: New Status in lightdm package in Ubuntu: New Status in mate-settings-daemon package in Ubuntu: New Bug description: Hi, my little daughter discovered a logon screen bypass in Ubuntu Mate 21.10 after hitting the keyboard for a while. It turns out that several keyboard shortcuts are allowed while Ubuntu Mate is locked (arctica-greeter): - Mod4 + S (mate-search-tool) - Mod4 + E (Open Caja / File Explorer) - CTRL + Shift + Esc (mate-system-monitor) - PRNT (Screenshot) All of the mentioned shortcuts could be used to spawn a file explorer (Caja) or various other binaries as user "lightdm", who owns the logon screen. Although an interactive terminal like mate-terminal, xterm, lxterm etc. could not be opened directly, there are various options to run commands as the lightdm user, for example by creating a shell script using "caja", and execute it directly using the GUI. I've attached Proof-of-Concept GIFs for all shortcuts mentioned above. There might be additional shortcuts that could be used to achieve the same, however I'm not aware about every shortcut that is configured, but I suppose that the root cause is located somewhere in arctica- greeter, rather than within every single binary launched by shortcuts. The bug was reproduced on a fresh installation of Ubuntu Mate 21.10. I haven't tested other versions of Ubuntu Mate yet. Please find additional version details below: $ apt-cache policy lightdm lightdm: Installed: 1.30.0-0ubuntu4 Candidate: 1.30.0-0ubuntu4 Version table: *** 1.30.0-0ubuntu4 500 500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy arctica-greeter arctica-greeter: Installed: 0.99.1.5-2nmu1 Candidate: 0.99.1.5-2nmu1 Version table: *** 0.99.1.5-2nmu1 500 500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status Thanks, Basti To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1948339/+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 313149] Re: deluge produces zombie browser process when launched through about window
** Changed in: python Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-defaults in Ubuntu. https://bugs.launchpad.net/bugs/313149 Title: deluge produces zombie browser process when launched through about window Status in Deluge: Won't Fix Status in Python: Incomplete Status in deluge package in Ubuntu: Invalid Status in python-defaults package in Ubuntu: Triaged Bug description: Binary package hint: deluge-torrent when a new browser process is started by clicking on the link in the about window, it is not harvested after it exits. it is remaining in the process list as zombie/defunct until deluge exits too. deluge-torrent 0.5.9.3-1 ubuntu 8.10 To manage notifications about this bug go to: https://bugs.launchpad.net/deluge/+bug/313149/+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