[Touch-packages] [Bug 1966418] Re: [jammy regression] Evolution does not display message content anymore
Ubuntu on Xorg is a good work-around for me, no error message from evolution at the command line, and the email displays normaily, thanks for that -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1966418 Title: [jammy regression] Evolution does not display message content anymore Status in evolution package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: Confirmed Bug description: Evolution has suddenly stopped displaying message contents on the last 24h. Starting it up from the command line shows this output: ``` EGLDisplay Initialization failed: EGL_NOT_INITIALIZED Cannot create EGL context: invalid display (last error: EGL_SUCCESS) ``` I don't know if it's related, but googling around shows some webkitgtk hits on this error. The email contents are however clickable. They're just not rendered to screen (see attached file). Deleting the evolution folders from `~/.config`, `~/.cache` and `~/.local/share` does not help. Email accounts are all google, configured through gnome online accounts. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evolution 3.44.0-1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: sway Date: Fri Mar 25 10:55:49 2022 SourcePackage: evolution UpgradeStatus: Upgraded to jammy on 2022-03-01 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1966418/+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 1966418] Re: [jammy regression] Evolution does not display message content anymore
** Also affects: webkit2gtk (Ubuntu) Importance: Undecided Status: New ** Changed in: webkit2gtk (Ubuntu) Importance: Undecided => High ** Changed in: webkit2gtk (Ubuntu) Status: New => Confirmed ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New ** Changed in: mesa (Ubuntu) Status: New => Confirmed ** Changed in: mesa (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1966418 Title: [jammy regression] Evolution does not display message content anymore Status in evolution package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: Confirmed Bug description: Evolution has suddenly stopped displaying message contents on the last 24h. Starting it up from the command line shows this output: ``` EGLDisplay Initialization failed: EGL_NOT_INITIALIZED Cannot create EGL context: invalid display (last error: EGL_SUCCESS) ``` I don't know if it's related, but googling around shows some webkitgtk hits on this error. The email contents are however clickable. They're just not rendered to screen (see attached file). Deleting the evolution folders from `~/.config`, `~/.cache` and `~/.local/share` does not help. Email accounts are all google, configured through gnome online accounts. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evolution 3.44.0-1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: sway Date: Fri Mar 25 10:55:49 2022 SourcePackage: evolution UpgradeStatus: Upgraded to jammy on 2022-03-01 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1966418/+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 1961859] Re: When we install ModemManager1.16.6 and others, this will lead to ubuntu can not enter into GNOME UI.
Hi: We rebuild MM1.16.6 without reinstall glic, it works fine. So we can close this ticket.Tks. -- 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/1961859 Title: When we install ModemManager1.16.6 and others, this will lead to ubuntu can not enter into GNOME UI. Status in modemmanager package in Ubuntu: Incomplete Bug description: 1. We use sourcecode to install ModemManger1.16.6 2. Ubuntu can not enter UI. 3. We capture log and picture and add these on the attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1961859/+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 1965646] Re: pulseaudio missing even though says installed in software center. Have no audio
Is this bug related to https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1963934 ? If doing this solves the issue, then it probably is: sudo touch /usr/share/pipewire/media-session.d/with-pulseaudio -- 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/1965646 Title: pulseaudio missing even though says installed in software center. Have no audio Status in pulseaudio package in Ubuntu: New Bug description: Previously: had SoundHissheadphones https://answers.launchpad.net/ubuntu/+question/700984 Messed with pulseaudio until it's totally gone even though on the software center it still says it is installed but unable to remove it because it says: "PulseAudio System Tray": no packages to remove Sudo apt remove pulseaudio Removing pulseaudio (1:15.99.1+dfsg1-1ubuntu1) ... Setting up pipewire-pulse (0.3.48-1ubuntu1) ... Created symlink /etc/systemd/user/default.target.wants/pipewire-pulse.service → /usr/lib/systemd/user/pipewire-pulse.service. Created symlink /etc/systemd/user/sockets.target.wants/pipewire-pulse.socket → / usr/lib/systemd/user/pipewire-pulse.socket. Processing triggers for man-db (2.10.1-1) ... Processing triggers for libglib2.0-0:amd64 (2.71.3-1) ... sudo apt purge Purging configuration files for pulseaudio (1:15.99.1+dfsg1-1ubuntu1) ... Processing triggers for dbus (1.12.20-2ubuntu3) . ___ No audio symbol, it's gone Software center still says it is installed. Unable to remove "PulseAudio" in software center Unable to remove"PulseAudio Volume Control": no packages to remove Version 0.17.0 ___ mate-volume-control No device to configure under Hardware Input: unchecked Monitor of Dummy Output Output: unchecked Dummy Output Stereo __ sudo apt-get update -y sudo apt-get install -y pulseaudio Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages were automatically installed and are no longer required: libsbc1 libssl1.1 linux-headers-5.13.0-19 Use 'sudo apt autoremove' to remove them. Suggested packages: pavumeter paprefs ubuntu-sounds The following NEW packages will be installed: pulseaudio 0 upgraded, 1 newly installed, 0 to remove and 7 not upgraded. Need to get 0 B/913 kB of archives. After this operation, 4,674 kB of additional disk space will be used. Selecting previously unselected package pulseaudio. (Reading database ... 321785 files and directories currently installed.) Preparing to unpack .../pulseaudio_1%3a15.99.1+dfsg1-1ubuntu1_amd64.deb ... Unpacking pulseaudio (1:15.99.1+dfsg1-1ubuntu1) ... Setting up pulseaudio (1:15.99.1+dfsg1-1ubuntu1) ... Adding user pulse to group audio Created symlink /etc/systemd/user/default.target.wants/pulseaudio.service → /usr/lib/systemd/user/pulseaudio.service. Created symlink /etc/systemd/user/sockets.target.wants/pulseaudio.socket → /usr/lib/systemd/user/pulseaudio.socket. Processing triggers for man-db (2.10.1-1) ... Processing triggers for dbus (1.12.20-2ubuntu3) ...y sudo apt autoremove Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages will be REMOVED: libsbc1 libssl1.1 linux-headers-5.13.0-19 0 upgraded, 0 newly installed, 3 to remove and 7 not upgraded. After this operation, 80.1 MB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 321976 files and directories currently installed.) Removing libsbc1:amd64 (1.5-3build1) ... Removing libssl1.1:amd64 (1.1.1l-1ubuntu1) ... Removing linux-headers-5.13.0-19 (5.13.0-19.19) ... Processing triggers for libc-bin (2.35-0ubuntu3) ... pulseaudio W: [pulseaudio] pid.c: Stale PID file, overwriting. E: [pulseaudio] socket-server.c: bind(): Address already in use E: [pulseaudio] module.c: Failed to load module "module-native-protocol-unix" (argument: ""): initialization failed. E: [pulseaudio] main.c: D-Bus name org.pulseaudio.Server already taken. pulseaudio -k E: [pulseaudio] main.c: Failed to kill daemon: No such process __ ubuntu-bug -s audio Package pulseaudio 1:15:99.1+dgsg1-1ubuntu1 2.20.11-Outbuntu79 __ killall pulseaudio; pulseaudio -k ; rm -r ~/.config/pulse/* ; rm -r ~/.pulse* rm -r ~/.pulse* pulseaudio: no process found E: [pulseaudio] main.c: Failed to kill daemon: No such process rm: cannot remove '/home/ptosis/.pulse*': No such file or directory pulseaudio --start waited 10 seconds, then reboot wget -O alsa-info.sh http://www.alsa-project.org/alsa-info.sh && chmod +x ./alsa-info.sh && ./alsa-info.sh bash alsa-info.sh --stdout AFTER
[Touch-packages] [Bug 1966381] Re: applications crash that never crashed under Ubuntu-20.04
FYI About 6 hours ago I saw a new release of systemd-oom was released (249.11-0ubuntu2). I've upgraded the entire system and rebooted, so I'll report back if there's any change. I was getting these random OOM about every couple of days, so within a week should know if that changed anything -- 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/1966381 Title: applications crash that never crashed under Ubuntu-20.04 Status in systemd package in Ubuntu: New Bug description: Just now I was watching some video in Firefox. I popped over to another virtual workspace for a few minutes, and when I popped back to Firefox it had gone. The same thing had been happening all week (I installed fresh Ubuntu-22.04 last week) with Chrome, Firefox and Thunderbird. This time instead of shrugging it off I looked in the logs, and found this Mar 25 19:45:40 ubuntu systemd-oomd[960]: Killed /user.slice/user-1001.slice/user@1001.service/app.slice/app-gnome-firefox-6607.scope due to memory used (15940579328) / total (16153944064) and swap used (925564928) / total (1023406080) being more than 90.00% Mar 22 08:11:29 ubuntu systemd[5029]: app-gnome-google\x2dchrome-5412.scope: systemd-oomd killed 298 process(es) in this unit. Mar 23 11:09:28 ubuntu systemd-oomd[1055]: Killed /user.slice/user-1001.slice/user@1001.service/app.slice/app-gnome-thunderbird-5418.scope due to memory used (15591993344) / total (16149745664) and swap used (927760384) / total (1023406080) being more than 90.00% Mar 23 11:09:28 ubuntu systemd[5029]: app-gnome-thunderbird-5418.scope: systemd-oomd killed 173 process(es) in this unit. I know it's saying those three entirely unrelated applications had suddenly decided to swallow all the RAM+swap on this laptop of mine - but the very same apps didn't act like that last week under Ubuntu-20.04, so I suspect something else is going on I can't say they hadn't swallowed all the RAM, but there is ZERO sign of a system on the verge of collapsing - everything has been screaming along just nicely - no sign of the "staggering" you normally get when the OS is heavily into swap. However, now that I look I see my 16G laptop only has 1G swap??? I just let the Ubuntu installer do it's defaults - but it used to auto- choose 1xRAM or 2xRAM - what's with this 1G swap? Could that be related? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: systemd-oomd 249.11-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 25 19:47:44 2022 InstallationDate: Installed on 2022-03-13 (11 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1966381/+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 1902748] Re: ubuntu-seed / ubuntu-boot partition detection could be improved
** Changed in: snapd Assignee: Ian Johnson (anonymouse67) => (unassigned) -- 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/1902748 Title: ubuntu-seed / ubuntu-boot partition detection could be improved Status in snapd: Confirmed Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Invalid Bug description: ubuntu-seed / ubuntu-boot partition detection could be improved Currently in the initrd, snapd-bootstrap searches for ubuntu-boot / ubuntu-seed partition by label or by UEFI variable that was set by sd- boot. sdboot uses devicepath UEFI protocol to establish MEDIA_DEVICE_PATH, HARDDRIVE_DEVICEPATH, GUID, Signature aka partuuid that was used to boot. https://github.com/tianocore/edk2/blob/master/MdePkg/Include/Protocol/DevicePath.h This is nice, but not unique enough. It would be nice if we were able to modify sd-boot stub to export something more specific that ideally maps to a sysfs path. For example PCI_DEVICE_PATH, SCSI_DEVICE_PATH, SATA_DEVICE_PATH, USB_DEVICE_PATH, NVME_NAMESPACE_DEVICE_PATH, SD_DEVICE_PATH, UFS_DEVICE_PATH, EMMC_DEVICE_PATH or some such. That way initrd would be able to resolve better which block device to key off. Given that EFI device handle is passed to the kernel, doesn't kernel also know where it came from? or not? To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1902748/+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 1966519] Re: hard shutdown after close laptop lid
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1966519 Title: hard shutdown after close laptop lid Status in xorg package in Ubuntu: New Bug description: shutdown on close screen lid and when i reopen the lid it is completely shutdown and i must press the power button and start boot sequence, i have set in gnome-tweaks action,the after close the lid memory suspend, but evidently it is not working. Sorry for my english. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-37.42-generic 5.13.19 Uname: Linux 5.13.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Operace zamítnuta: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Mar 25 20:59:38 2022 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.32, 5.13.0-37-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev d3) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Cezanne [103c:8895] InstallationDate: Installed on 2022-03-23 (1 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210502) MachineType: HP HP EliteBook 845 G8 Notebook PC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=cs_CZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-37-generic root=UUID=e3adb113-cca4-4316-9c3b-edc124da9ca4 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/11/2022 dmi.bios.release: 8.3 dmi.bios.vendor: HP dmi.bios.version: T82 Ver. 01.08.03 dmi.board.name: 8895 dmi.board.vendor: HP dmi.board.version: KBC Version 43.2A.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 67.42 dmi.modalias: dmi:bvnHP:bvrT82Ver.01.08.03:bd02/11/2022:br8.3:efr67.42:svnHP:pnHPEliteBook845G8NotebookPC:pvr:rvnHP:rn8895:rvrKBCVersion43.2A.00:cvnHP:ct10:cvr:sku48R69EA#BCM: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 845 G8 Notebook PC dmi.product.sku: 48R69EA#BCM dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1966519/+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 1966519] [NEW] hard shutdown after close laptop lid
You have been subscribed to a public bug: shutdown on close screen lid and when i reopen the lid it is completely shutdown and i must press the power button and start boot sequence, i have set in gnome-tweaks action,the after close the lid memory suspend, but evidently it is not working. Sorry for my english. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-37.42-generic 5.13.19 Uname: Linux 5.13.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Operace zamítnuta: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Mar 25 20:59:38 2022 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.32, 5.13.0-37-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev d3) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Cezanne [103c:8895] InstallationDate: Installed on 2022-03-23 (1 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210502) MachineType: HP HP EliteBook 845 G8 Notebook PC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=cs_CZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-37-generic root=UUID=e3adb113-cca4-4316-9c3b-edc124da9ca4 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/11/2022 dmi.bios.release: 8.3 dmi.bios.vendor: HP dmi.bios.version: T82 Ver. 01.08.03 dmi.board.name: 8895 dmi.board.vendor: HP dmi.board.version: KBC Version 43.2A.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 67.42 dmi.modalias: dmi:bvnHP:bvrT82Ver.01.08.03:bd02/11/2022:br8.3:efr67.42:svnHP:pnHPEliteBook845G8NotebookPC:pvr:rvnHP:rn8895:rvrKBCVersion43.2A.00:cvnHP:ct10:cvr:sku48R69EA#BCM: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 845 G8 Notebook PC dmi.product.sku: 48R69EA#BCM dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish ubuntu wayland-session -- hard shutdown after close laptop lid https://bugs.launchpad.net/bugs/1966519 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg 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 1902464] Re: The rear panel of Lenovo P620 doesn't support more than one audio device at the same time
I enabled proposed and upgrade alsa-ucm-conf, then reboot the system. I plugged a microphone to the rear panel, made sure it works, then I plugged a speaker to line-out, and made sure both speaker and mic are working. So the original issue is solved by this SRU. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-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/1902464 Title: The rear panel of Lenovo P620 doesn't support more than one audio device at the same time Status in HWE Next: New Status in OEM Priority Project: Confirmed Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Committed Status in pulseaudio source package in Focal: Fix Released Bug description: == SRU Justification == [Impact] On P620, only single port can work on rear panel. For example, when the Line-Out is plugged, the Mic won't work anymore. [Fix] Use upstream version of UCM to handle port priority correctly, instead of separate ports into different profiles. [Test] Once the UCM is in place, all three ports of rear panel work correctly. [Where problems could occur] UCM is not a static thing - it's actually interpreted differently at higher level. So any change in userspace daemons other than PulseAudio may not like the change and can interpret the UCM in another way. == Original Bug Report == After backporting following patches from PA and alsa-ucm-conf and then it works. https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/290 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/354 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/355 https://github.com/alsa-project/alsa-ucm-conf/tree/master/ucm2/USB- Audio [landed by aa74f4c12eefcc98582572d2fc48982cf7478b51] Here is the test PPA: https://launchpad.net/~os369510/+archive/ubuntu/oem-package-test Since the upstream not yet accepted those patches, the regression potential may quite high. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1902464/+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 1761382] Re: Unable to connect to ibus: Could not connect: Connection refused
I found this bug because I was searching for the message: gnome-shell[PID]: Unable to connect to ibus: Could not connect: Connection refused in my journalctl output from a relatively new Ubuntu 21.10 install. No apparent problems, but I was looking to see if I should be concerned? Summary: Still present in some Ubuntu 21.10 logs. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1761382 Title: Unable to connect to ibus: Could not connect: Connection refused Status in gnome-shell package in Ubuntu: Expired Status in ibus package in Ubuntu: Expired Bug description: Get this logged: oem@ubuntu:~$ journalctl -b | grep ibus dbus-daemon[1074]: [session uid=120 pid=1074] Activating service name='org.freedesktop.portal.IBus' requested by ':1.18' (uid=120 pid=1135 comm="ibus-daemon --xim --panel disable " label="unconfined") gnome-shell[1084]: Unable to connect to ibus: Could not connect: Connection refused /usr/lib/gdm3/gdm-x-session[1281]: dbus-update-activation-environment: setting QT_IM_MODULE=ibus /usr/lib/gdm3/gdm-x-session[1281]: dbus-update-activation-environment: setting XMODIFIERS=@im=ibus /usr/lib/gdm3/gdm-x-session[1281]: dbus-update-activation-environment: setting GTK_IM_MODULE=ibus dbus-daemon[1293]: [session uid=1000 pid=1293] Activating service name='org.freedesktop.portal.IBus' requested by ':1.27' (uid=1000 pid=1458 comm="ibus-daemon --xim --panel disable " label="unconfined") gnome-shell[1435]: Unable to connect to ibus: Could not connect: Connection refused ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Apr 5 07:43:59 2018 DisplayManager: gdm3 EcryptfsInUse: Yes ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1761382/+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 1965993] Re: [UIFe] Remove Ubuntu Pro settings
I approve of this change past UI Freeze. ** Changed in: software-properties (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1965993 Title: [UIFe] Remove Ubuntu Pro settings Status in software-properties package in Ubuntu: Triaged Bug description: Due to backend delay, we want to remove the Ubuntu Pro settings and only show Livepatch settings as were previously shown. This feature will be re-added at a future time. This change will rename the "Ubuntu Pro" page to "Livepatch" and hide various UI elements. This adds the following new strings for translations: "This machine is not covered by an Ubuntu Advantage subscription." "Ubuntu Advantage subscription attached." "Livepatch" All existing strings for the Ubuntu Pro settings remain, so should remain translated when this change is reverted. See below for screenshots of the change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1965993/+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 1965809] Re: 22.04 - Videos ‘cannot find’ any videos (VLC works fine) - totem crashed with SIGSEGV in magazine_chain_pop_head()
After many reboots and log out / log in cycles, I have noticed that this happens 95% of the time in Wayland, but hasn't happened once in Xorg -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1965809 Title: 22.04 - Videos ‘cannot find’ any videos (VLC works fine) - totem crashed with SIGSEGV in magazine_chain_pop_head() Status in gstreamer1.0 package in Ubuntu: New Bug description: Attempting to open videos in multiple formats (tried .webm and .mp4 so far) results in ‘specified movie could not be found’ errors in Videos. I’ve moved them into multiple folders with the same result. If I hit the upper left button ’ < ’ I can see the file just fine ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: libgstreamer1.0-0 1.20.1-1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 21 14:20:08 2022 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2022-02-17 (32 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126) ProcCmdline: /usr/bin/totem --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0x7f023771dd0c :mov 0x8(%r12),%rax PC (0x7f023771dd0c) ok source "0x8(%r12)" (0x55e51814962008) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gstreamer1.0 StacktraceTop: g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 Title: totem crashed with SIGSEGV in g_slice_alloc() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxsf XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1965809/+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 1966381] Re: applications crash that never crashed under Ubuntu-20.04
** Changed in: systemd (Ubuntu) Importance: Undecided => High -- 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/1966381 Title: applications crash that never crashed under Ubuntu-20.04 Status in systemd package in Ubuntu: New Bug description: Just now I was watching some video in Firefox. I popped over to another virtual workspace for a few minutes, and when I popped back to Firefox it had gone. The same thing had been happening all week (I installed fresh Ubuntu-22.04 last week) with Chrome, Firefox and Thunderbird. This time instead of shrugging it off I looked in the logs, and found this Mar 25 19:45:40 ubuntu systemd-oomd[960]: Killed /user.slice/user-1001.slice/user@1001.service/app.slice/app-gnome-firefox-6607.scope due to memory used (15940579328) / total (16153944064) and swap used (925564928) / total (1023406080) being more than 90.00% Mar 22 08:11:29 ubuntu systemd[5029]: app-gnome-google\x2dchrome-5412.scope: systemd-oomd killed 298 process(es) in this unit. Mar 23 11:09:28 ubuntu systemd-oomd[1055]: Killed /user.slice/user-1001.slice/user@1001.service/app.slice/app-gnome-thunderbird-5418.scope due to memory used (15591993344) / total (16149745664) and swap used (927760384) / total (1023406080) being more than 90.00% Mar 23 11:09:28 ubuntu systemd[5029]: app-gnome-thunderbird-5418.scope: systemd-oomd killed 173 process(es) in this unit. I know it's saying those three entirely unrelated applications had suddenly decided to swallow all the RAM+swap on this laptop of mine - but the very same apps didn't act like that last week under Ubuntu-20.04, so I suspect something else is going on I can't say they hadn't swallowed all the RAM, but there is ZERO sign of a system on the verge of collapsing - everything has been screaming along just nicely - no sign of the "staggering" you normally get when the OS is heavily into swap. However, now that I look I see my 16G laptop only has 1G swap??? I just let the Ubuntu installer do it's defaults - but it used to auto- choose 1xRAM or 2xRAM - what's with this 1G swap? Could that be related? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: systemd-oomd 249.11-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 25 19:47:44 2022 InstallationDate: Installed on 2022-03-13 (11 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1966381/+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 1907878] Re: wrong var declaration in if-up.d/resolved (nm-dispatcher[54417]: /etc/network/if-up.d/resolved: 12: mystatedir: not found)
FWIW this is still a problem as of Ubuntu 22.04. I'm aware that using /etc/network is deprecated in favor of netplan, I guess that's why the script can stay in a broken state for so long. I'll be looking at porting my configuration to that. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1907878 Title: wrong var declaration in if-up.d/resolved (nm-dispatcher[54417]: /etc/network/if-up.d/resolved: 12: mystatedir: not found) Status in ifupdown package in Ubuntu: Confirmed Bug description: Syslog error: nm-dispatcher[...]: /etc/network/if-up.d/resolved: 12: mystatedir: not found I think it's because of this line: if systemctl is-enabled systemd-resolved > /dev/null 2>&1; then mystatedir statedir ifindex interface <- this is interpreted as a 'mystatedir' command and fails interface=$IFACE if [ ! "$interface" ]; then Perhaps the intention was to 'export mystatedir statedir ...' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1907878/+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 1966436] Re: Bluetooth fails to connect "br-connection-profile-unavailable"
I found recent bugs but: * this is not the same adapter as #1960448 * not same adapter as #1960377 and I'm running 5.15.0-23-generic which is supposed to have the fix mentioned. -- 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/1966436 Title: Bluetooth fails to connect "br-connection-profile-unavailable" Status in bluez package in Ubuntu: New Bug description: How to reproduce: > bluetoothctl scan on Discovery started ... > bluetoothctl connect 94:DB:56:8E:0B:96 Attempting to connect to 94:DB:56:8E:0B:96 Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable > systemctl status bluetooth bluetooth.service - Bluetooth service Loaded: loaded ... mars 25 12:39:08 ncelrnd2375 bluetoothd[1282]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 94:DB:56:8E:0B:96: Protocol not available Notes: kernel-5.15, bluez-5.64 Bus 003 Device 004: ID 8087:0032 Intel Corp. AX210 Bluetooth Dell Precision 3560 Unfortunately I did not test before upgrade to 22.04. Tried installing pipewire-pulse, blueman, but this is lower-level. There are reports of similar errors popping up in Arch and Manjaro recently: https://bbs.archlinux.org/viewtopic.php?id=270465 https://forum.manjaro.org/t/bluetooth-ko-with-kernel-5-16/99913 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Mar 25 12:56:34 2022 InstallationDate: Installed on 2022-03-04 (21 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Precision 3560 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=/dev/mapper/AmadeUbuntu20-root ro audit=1 acpi_rev_override load_nvme=YES nouveau.modeset=0 dis_ucode_ldr quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to jammy on 2022-03-22 (3 days ago) dmi.bios.date: 09/13/2021 dmi.bios.release: 1.12 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.2 dmi.board.name: 095HH7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.2:bd09/13/2021:br1.12:svnDellInc.:pnPrecision3560:pvr:rvnDellInc.:rn095HH7:rvrA00:cvnDellInc.:ct10:cvr:sku0A22: dmi.product.family: Precision dmi.product.name: Precision 3560 dmi.product.sku: 0A22 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 44:E5:17:BC:00:DD ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:24189 acl:41 sco:0 events:519 errors:0 TX bytes:8252 acl:33 sco:0 commands:239 errors:0 modified.conffile..etc.cron.daily.apport: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1966436/+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 1966436] [NEW] Bluetooth fails to connect "br-connection-profile-unavailable"
Public bug reported: How to reproduce: > bluetoothctl scan on Discovery started ... > bluetoothctl connect 94:DB:56:8E:0B:96 Attempting to connect to 94:DB:56:8E:0B:96 Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable > systemctl status bluetooth bluetooth.service - Bluetooth service Loaded: loaded ... mars 25 12:39:08 ncelrnd2375 bluetoothd[1282]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 94:DB:56:8E:0B:96: Protocol not available Notes: kernel-5.15, bluez-5.64 Bus 003 Device 004: ID 8087:0032 Intel Corp. AX210 Bluetooth Dell Precision 3560 Unfortunately I did not test before upgrade to 22.04. Tried installing pipewire-pulse, blueman, but this is lower-level. There are reports of similar errors popping up in Arch and Manjaro recently: https://bbs.archlinux.org/viewtopic.php?id=270465 https://forum.manjaro.org/t/bluetooth-ko-with-kernel-5-16/99913 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Mar 25 12:56:34 2022 InstallationDate: Installed on 2022-03-04 (21 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Precision 3560 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=/dev/mapper/AmadeUbuntu20-root ro audit=1 acpi_rev_override load_nvme=YES nouveau.modeset=0 dis_ucode_ldr quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to jammy on 2022-03-22 (3 days ago) dmi.bios.date: 09/13/2021 dmi.bios.release: 1.12 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.2 dmi.board.name: 095HH7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.2:bd09/13/2021:br1.12:svnDellInc.:pnPrecision3560:pvr:rvnDellInc.:rn095HH7:rvrA00:cvnDellInc.:ct10:cvr:sku0A22: dmi.product.family: Precision dmi.product.name: Precision 3560 dmi.product.sku: 0A22 dmi.sys.vendor: Dell Inc. hciconfig: hci0: Type: Primary Bus: USB BD Address: 44:E5:17:BC:00:DD ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:24189 acl:41 sco:0 events:519 errors:0 TX bytes:8252 acl:33 sco:0 commands:239 errors:0 modified.conffile..etc.cron.daily.apport: [deleted] ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- 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/1966436 Title: Bluetooth fails to connect "br-connection-profile-unavailable" Status in bluez package in Ubuntu: New Bug description: How to reproduce: > bluetoothctl scan on Discovery started ... > bluetoothctl connect 94:DB:56:8E:0B:96 Attempting to connect to 94:DB:56:8E:0B:96 Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable > systemctl status bluetooth bluetooth.service - Bluetooth service Loaded: loaded ... mars 25 12:39:08 ncelrnd2375 bluetoothd[1282]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 94:DB:56:8E:0B:96: Protocol not available Notes: kernel-5.15, bluez-5.64 Bus 003 Device 004: ID 8087:0032 Intel Corp. AX210 Bluetooth Dell Precision 3560 Unfortunately I did not test before upgrade to 22.04. Tried installing pipewire-pulse, blueman, but this is lower-level. There are reports of similar errors popping up in Arch and Manjaro recently: https://bbs.archlinux.org/viewtopic.php?id=270465 https://forum.manjaro.org/t/bluetooth-ko-with-kernel-5-16/99913 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Mar 25 12:56:34 2022 InstallationDate: Installed on 2022-03-04 (21 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Precision 3560 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=/dev/mapper/AmadeUbuntu20-root ro audit=1 acpi_rev_override load_nvme=YES nouveau.modeset=0 dis_ucode_ldr quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to jammy on 2022-03-22 (3 days ago) dmi.bios.date: 09/13/2021 dmi.bios.release: 1.12 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.2 dmi.board.name: 095HH7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc.
[Touch-packages] [Bug 1966416] [NEW] pam_faillock does not actually deny login after given number of failures
Public bug reported: ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libpam-modules 1.4.0-11ubuntu1 I just noticed that Ubuntu 22.04 changed from the old pam_tally2 module to the more widespread pam_faillock one. \o/ However, locking (denying logins) does not actually seem to work. According to pam_faillock(8) I changed the config like this: # diff -u /etc/pam.d/common-auth{.orig,} --- /etc/pam.d/common-auth.orig 2022-03-25 10:41:29.08800 + +++ /etc/pam.d/common-auth 2022-03-25 10:48:48.913419254 + @@ -17,11 +17,11 @@ auth [success=2 default=ignore] pam_unix.so nullok auth [success=1 default=ignore] pam_sss.so use_first_pass # here's the fallback if no module succeeds -auth requisite pam_deny.so +auth [default=die] pam_faillock.so authfail # prime the stack with a positive return value if there isn't one already; # this avoids us returning an error just because nothing sets a success code # since the modules above will each just jump around -auth requiredpam_permit.so +auth sufficient pam_faillock.so authsucc # and here are more per-package modules (the "Additional" block) auth optionalpam_cap.so # end of pam-auth-update config This config works fine on both Debian 11 and Debian testing, and it agrees with the example in the manpage -- so I don't think it's that broken. Start from a blank slate: # faillock --user admin --reset # faillock --user admin admin: WhenType Source Valid Now I log in as user "admin" with a wrong password four times (one more than the default "deny=3", just to make sure): sshd[3841]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=172.27.0.2 user=admin sshd[3841]: Failed password for admin from 172.27.0.2 port 39446 ssh2 After the third time, I even see this in the journal: sshd[3841]: Failed password for admin from 172.27.0.2 port 39446 ssh2 pam_faillock(sshd:auth): Consecutive login failures for user admin account temporarily locked Failed password for admin from 172.27.0.2 port 39446 ssh2 But if I then log in with the correct password, it succeeds: sshd[4492]: Accepted password for admin from 172.27.0.2 port 39450 ssh2 sshd[4492]: pam_unix(sshd:session): session opened for user admin(uid=1000) by (uid=0) That's buggy -- "admin" should be denied access for ten minutes ("unlock_time = 600" in /etc/security/faillock.conf). It did record the failed logins alright: # faillock --user admin admin: WhenType Source Valid 2022-03-25 10:54:02 RHOST 172.27.0.2 V 2022-03-25 10:54:27 RHOST 172.27.0.2 V 2022-03-25 10:54:30 RHOST 172.27.0.2 V But the actual denial doesn't seem to work. ** Affects: pam (Ubuntu) Importance: Undecided Status: New ** Tags: jammy regression-release -- 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/1966416 Title: pam_faillock does not actually deny login after given number of failures Status in pam package in Ubuntu: New Bug description: ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libpam-modules 1.4.0-11ubuntu1 I just noticed that Ubuntu 22.04 changed from the old pam_tally2 module to the more widespread pam_faillock one. \o/ However, locking (denying logins) does not actually seem to work. According to pam_faillock(8) I changed the config like this: # diff -u /etc/pam.d/common-auth{.orig,} --- /etc/pam.d/common-auth.orig 2022-03-25 10:41:29.08800 + +++ /etc/pam.d/common-auth2022-03-25 10:48:48.913419254 + @@ -17,11 +17,11 @@ auth [success=2 default=ignore] pam_unix.so nullok auth [success=1 default=ignore] pam_sss.so use_first_pass # here's the fallback if no module succeeds -auth requisite pam_deny.so +auth [default=die] pam_faillock.so authfail # prime the stack with a positive return value if there isn't one already; # this avoids us returning an error just because nothing sets a success code # since the modules above will each just jump around -auth requiredpam_permit.so +auth sufficient pam_faillock.so authsucc # and here are more per-package modules (the "Additional" block) auth optionalpam_cap.so # end of pam-auth-update config This config works fine on both Debian 11 and Debian testing, and it agrees with the example in the manpage -- so I don't think it's that broken. Start from a blank slate: # faillock --user admin --reset # faillock --user admin admin: WhenType S
[Touch-packages] [Bug 1962843] Re: Guest OS customization fail for ubuntu 22.04 desktop in vsphere due to adding 'shutdown.target' in file /usr/lib/systemd/system/systemd-networkd.socket
** Tags added: rls-jj-incoming -- 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/1962843 Title: Guest OS customization fail for ubuntu 22.04 desktop in vsphere due to adding 'shutdown.target' in file /usr/lib/systemd/system/systemd- networkd.socket Status in systemd package in Ubuntu: Confirmed Bug description: Problem: Guest OS customization fail for ubuntu 22.04 desktop in vsphere due to adding 'shutdown.target' in file /usr/lib/systemd/system/systemd-networkd.socket Analysis Compared with Ubuntu 21.04 desktop image, there is a difference in /usr/lib/systemd/system/systemd-networkd.socket, "shutdown.target" is added to Before and Conflicts options. Ubuntu 22.04 [Unit] Description=Network Service Netlink Socket Documentation=man:systemd-networkd.service(8) man:rtnetlink(7) ConditionCapability=CAP_NET_ADMIN DefaultDependencies=no Before=sockets.target shutdown.target Conflicts=shutdown.target Ubuntu 21.04 [Unit] Description=Network Service Netlink Socket Documentation=man:systemd-networkd.service(8) man:rtnetlink(7) ConditionCapability=CAP_NET_ADMIN DefaultDependencies=no Before=sockets.target After removed "shutdown.target" from /usr/lib/systemd/system/systemd- networkd.socket in ubuntu 22.04 desktop, this issue did NOT reproduce since systemd-networkd.service starts much earlier So the root cause of the issue is that adding 'shutdown.target' leads systemd-networkd.service starts late which makes customization command '/usr/sbin/netplan apply' fail. Not sure why adding 'shutdown.target' to file /usr/lib/systemd/system/systemd-networkd.socket ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962843/+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 1953200] Re: [jammy] FTBFS, gcc ICE?
mir builds with the recent gcc-11 in jammy, closing ** Changed in: mir (Ubuntu) Status: New => Invalid ** Changed in: gcc-11 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1953200 Title: [jammy] FTBFS, gcc ICE? Status in gcc-11 package in Ubuntu: Invalid Status in mir package in Ubuntu: Invalid Bug description: https://launchpad.net/ubuntu/+source/mir/2.4.1-0ubuntu3 [ 38%] Building CXX object src/client/CMakeFiles/mirclientobjects.dir/event_printer.cpp.o cd /<>/build-amd64/src/client && /usr/bin/c++ -DCLIENT_PLATFORM_VERSION=\"MIR_CLIENT_PLATFORM_5\" -DEGL_NO_X11 -DLOG_NDEBUG=1 -DLTTNG_UST_HAVE_SDT_INTEGRATION -DMESA_EGL_NO_X11_HEADERS -DMIR_CLIENT_PLATFORM_PATH=\"/usr/lib/x86_64-linux-gnu/mir/client-platform/\" -DMIR_DRMMODEADDFB_HAS_CONST_SIGNATURE -DMIR_LOG_COMPONENT_FALLBACK=\"mirclient\" -DMIR_VERSION_MAJOR=2 -DMIR_VERSION_MICRO=1 -DMIR_VERSION_MINOR=4 -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -I/<>/include/core -I/<>/include/common -I/<>/include/cookie -I/<>/src/include/common -I/<>/build-amd64/src/capnproto -I/<>/build-amd64/src/protobuf -I/<>/build-amd64/src/client -I/<>/include/platform -I/<>/include/client -I/<>/src/include/client -I/<>/src/include/cookie -I/usr/include/libdrm -g -O2 -ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -g -std=c++17 -Wall -fno-strict-aliasing -pedantic -Wnon-virtual-dtor -Wextra -fPIC -Werror -Wno-mismatched-tags -Wno-psabi -flto -ffat-lto-objects -std=c++17 -MD -MT src/client/CMakeFiles/mirclientobjects.dir/event_printer.cpp.o -MF CMakeFiles/mirclientobjects.dir/event_printer.cpp.o.d -o CMakeFiles/mirclientobjects.dir/event_printer.cpp.o -c /<>/src/client/event_printer.cpp In file included from /usr/include/boost/bind.hpp:30, from /<>/src/client/rpc/mir_protobuf_rpc_channel.cpp:44: /usr/include/boost/bind.hpp:36:1: note: ‘#pragma message: The practice of declaring the Bind placeholders (_1, _2, ...) in the global namespace is deprecated. Please use + using namespace boost::placeholders, or define BOOST_BIND_GLOBAL_PLACEHOLDERS to retain the current behavior.’ 36 | BOOST_PRAGMA_MESSAGE( | ^~~~ The bug is not reproducible, so it is likely a hardware or OS problem. make[3]: *** [src/client/lttng/CMakeFiles/mirclientlttng-static.dir/build.make:107: src/client/lttng/CMakeFiles/mirclientlttng-static.dir/input_receiver_report.cpp.o] Error 1 make[3]: Leaving directory '/<>/build-amd64' make[2]: *** [CMakeFiles/Makefile2:4657: src/client/lttng/CMakeFiles/mirclientlttng-static.dir/all] Error 2 make[2]: *** Waiting for unfinished jobs Possibly relevant, this seems to be using boost 1.74.0-13ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-11/+bug/1953200/+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 1966179] Re: The airplane hotkey does not work on lots of HP platforms
Install #comment #1 on 202203-30011, 202203-30008, 202203-30005, 202203-30004, 202203-30029, 202203-30030, 202203-30050 and 202203-30054. Will test it. -- 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/1966179 Title: The airplane hotkey does not work on lots of HP platforms Status in OEM Priority Project: In Progress Status in systemd package in Ubuntu: New Bug description: [Impact] The airplane hokey doesn't work on HP new generation machines. [Test Plan] Press airplane hokey. [Where problems could occur] If we don't have whitelist in focal and impish, then the airplane key won't work on new HP platforms. Please refer to Bug #1955997 as well. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1966179/+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 1902464] Re: The rear panel of Lenovo P620 doesn't support more than one audio device at the same time
Hello jeremyszu, or anyone else affected, Accepted alsa-ucm-conf into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/alsa-ucm- conf/1.2.2-1ubuntu0.13 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: alsa-ucm-conf (Ubuntu Focal) Status: Confirmed => Fix Committed ** Tags added: verification-needed verification-needed-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/1902464 Title: The rear panel of Lenovo P620 doesn't support more than one audio device at the same time Status in HWE Next: New Status in OEM Priority Project: Confirmed Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Committed Status in pulseaudio source package in Focal: Fix Released Bug description: == SRU Justification == [Impact] On P620, only single port can work on rear panel. For example, when the Line-Out is plugged, the Mic won't work anymore. [Fix] Use upstream version of UCM to handle port priority correctly, instead of separate ports into different profiles. [Test] Once the UCM is in place, all three ports of rear panel work correctly. [Where problems could occur] UCM is not a static thing - it's actually interpreted differently at higher level. So any change in userspace daemons other than PulseAudio may not like the change and can interpret the UCM in another way. == Original Bug Report == After backporting following patches from PA and alsa-ucm-conf and then it works. https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/290 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/354 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/355 https://github.com/alsa-project/alsa-ucm-conf/tree/master/ucm2/USB- Audio [landed by aa74f4c12eefcc98582572d2fc48982cf7478b51] Here is the test PPA: https://launchpad.net/~os369510/+archive/ubuntu/oem-package-test Since the upstream not yet accepted those patches, the regression potential may quite high. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1902464/+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 1902464] Re: The rear panel of Lenovo P620 doesn't support more than one audio device at the same time
** Description changed: - After backporting following patches from PA and alsa-ucm-conf and then - it works. + == SRU Justification == + [Impact] + On P620, only single port can work on rear panel. For example, when the Line-Out is plugged, the Mic won't work anymore. + + [Fix] + Use upstream version of UCM to handle port priority correctly, instead of separate ports into different profiles. + + [Test] + Once the UCM is in place, all three ports of rear panel work correctly. + + [Where problems could occur] + UCM is not a static thing - it's actually interpreted differently at higher level. So any change in userspace daemons other than PulseAudio may not like the change and can interpret the UCM in another way. + + == Original Bug Report == + After backporting following patches from PA and alsa-ucm-conf and then it works. https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/290 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/354 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/355 https://github.com/alsa-project/alsa-ucm-conf/tree/master/ucm2/USB-Audio [landed by aa74f4c12eefcc98582572d2fc48982cf7478b51] Here is the test PPA: https://launchpad.net/~os369510/+archive/ubuntu/oem-package-test Since the upstream not yet accepted those patches, the regression potential may quite high. -- 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/1902464 Title: The rear panel of Lenovo P620 doesn't support more than one audio device at the same time Status in HWE Next: New Status in OEM Priority Project: Confirmed Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Committed Status in pulseaudio source package in Focal: Fix Released Bug description: == SRU Justification == [Impact] On P620, only single port can work on rear panel. For example, when the Line-Out is plugged, the Mic won't work anymore. [Fix] Use upstream version of UCM to handle port priority correctly, instead of separate ports into different profiles. [Test] Once the UCM is in place, all three ports of rear panel work correctly. [Where problems could occur] UCM is not a static thing - it's actually interpreted differently at higher level. So any change in userspace daemons other than PulseAudio may not like the change and can interpret the UCM in another way. == Original Bug Report == After backporting following patches from PA and alsa-ucm-conf and then it works. https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/290 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/354 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/355 https://github.com/alsa-project/alsa-ucm-conf/tree/master/ucm2/USB- Audio [landed by aa74f4c12eefcc98582572d2fc48982cf7478b51] Here is the test PPA: https://launchpad.net/~os369510/+archive/ubuntu/oem-package-test Since the upstream not yet accepted those patches, the regression potential may quite high. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1902464/+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 1962843] Re: Guest OS customization fail for ubuntu 22.04 desktop in vsphere due to adding 'shutdown.target' in file /usr/lib/systemd/system/systemd-networkd.socket
Hi Christian Ehrhardt, Would you kindly please help ask somebody to take care of this issue ? Thanks very much. -- 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/1962843 Title: Guest OS customization fail for ubuntu 22.04 desktop in vsphere due to adding 'shutdown.target' in file /usr/lib/systemd/system/systemd- networkd.socket Status in systemd package in Ubuntu: Confirmed Bug description: Problem: Guest OS customization fail for ubuntu 22.04 desktop in vsphere due to adding 'shutdown.target' in file /usr/lib/systemd/system/systemd-networkd.socket Analysis Compared with Ubuntu 21.04 desktop image, there is a difference in /usr/lib/systemd/system/systemd-networkd.socket, "shutdown.target" is added to Before and Conflicts options. Ubuntu 22.04 [Unit] Description=Network Service Netlink Socket Documentation=man:systemd-networkd.service(8) man:rtnetlink(7) ConditionCapability=CAP_NET_ADMIN DefaultDependencies=no Before=sockets.target shutdown.target Conflicts=shutdown.target Ubuntu 21.04 [Unit] Description=Network Service Netlink Socket Documentation=man:systemd-networkd.service(8) man:rtnetlink(7) ConditionCapability=CAP_NET_ADMIN DefaultDependencies=no Before=sockets.target After removed "shutdown.target" from /usr/lib/systemd/system/systemd- networkd.socket in ubuntu 22.04 desktop, this issue did NOT reproduce since systemd-networkd.service starts much earlier So the root cause of the issue is that adding 'shutdown.target' leads systemd-networkd.service starts late which makes customization command '/usr/sbin/netplan apply' fail. Not sure why adding 'shutdown.target' to file /usr/lib/systemd/system/systemd-networkd.socket ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962843/+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 1966381] Re: applications crash that never crashed under Ubuntu-20.04
Thank you for the report, tagging as rls incoming because it sounds like we should ensure the systemd-oomd behaviour is what is expected or if it's maybe kicking in more early than it should ** Tags added: rls-jj-incoming -- 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/1966381 Title: applications crash that never crashed under Ubuntu-20.04 Status in systemd package in Ubuntu: New Bug description: Just now I was watching some video in Firefox. I popped over to another virtual workspace for a few minutes, and when I popped back to Firefox it had gone. The same thing had been happening all week (I installed fresh Ubuntu-22.04 last week) with Chrome, Firefox and Thunderbird. This time instead of shrugging it off I looked in the logs, and found this Mar 25 19:45:40 ubuntu systemd-oomd[960]: Killed /user.slice/user-1001.slice/user@1001.service/app.slice/app-gnome-firefox-6607.scope due to memory used (15940579328) / total (16153944064) and swap used (925564928) / total (1023406080) being more than 90.00% Mar 22 08:11:29 ubuntu systemd[5029]: app-gnome-google\x2dchrome-5412.scope: systemd-oomd killed 298 process(es) in this unit. Mar 23 11:09:28 ubuntu systemd-oomd[1055]: Killed /user.slice/user-1001.slice/user@1001.service/app.slice/app-gnome-thunderbird-5418.scope due to memory used (15591993344) / total (16149745664) and swap used (927760384) / total (1023406080) being more than 90.00% Mar 23 11:09:28 ubuntu systemd[5029]: app-gnome-thunderbird-5418.scope: systemd-oomd killed 173 process(es) in this unit. I know it's saying those three entirely unrelated applications had suddenly decided to swallow all the RAM+swap on this laptop of mine - but the very same apps didn't act like that last week under Ubuntu-20.04, so I suspect something else is going on I can't say they hadn't swallowed all the RAM, but there is ZERO sign of a system on the verge of collapsing - everything has been screaming along just nicely - no sign of the "staggering" you normally get when the OS is heavily into swap. However, now that I look I see my 16G laptop only has 1G swap??? I just let the Ubuntu installer do it's defaults - but it used to auto- choose 1xRAM or 2xRAM - what's with this 1G swap? Could that be related? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: systemd-oomd 249.11-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 25 19:47:44 2022 InstallationDate: Installed on 2022-03-13 (11 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1966381/+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 1965993] Re: [UIFe] Remove Ubuntu Pro settings
** Summary changed: - Remove Ubuntu Pro settings + [UIFe] Remove Ubuntu Pro settings -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1965993 Title: [UIFe] Remove Ubuntu Pro settings Status in software-properties package in Ubuntu: New Bug description: Due to backend delay, we want to remove the Ubuntu Pro settings and only show Livepatch settings as were previously shown. This feature will be re-added at a future time. This change will rename the "Ubuntu Pro" page to "Livepatch" and hide various UI elements. This adds the following new strings for translations: "This machine is not covered by an Ubuntu Advantage subscription." "Ubuntu Advantage subscription attached." "Livepatch" All existing strings for the Ubuntu Pro settings remain, so should remain translated when this change is reverted. See below for screenshots of the change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1965993/+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 1966381] [NEW] applications crash that never crashed under Ubuntu-20.04
Public bug reported: Just now I was watching some video in Firefox. I popped over to another virtual workspace for a few minutes, and when I popped back to Firefox it had gone. The same thing had been happening all week (I installed fresh Ubuntu-22.04 last week) with Chrome, Firefox and Thunderbird. This time instead of shrugging it off I looked in the logs, and found this Mar 25 19:45:40 ubuntu systemd-oomd[960]: Killed /user.slice/user-1001.slice/user@1001.service/app.slice/app-gnome-firefox-6607.scope due to memory used (15940579328) / total (16153944064) and swap used (925564928) / total (1023406080) being more than 90.00% Mar 22 08:11:29 ubuntu systemd[5029]: app-gnome-google\x2dchrome-5412.scope: systemd-oomd killed 298 process(es) in this unit. Mar 23 11:09:28 ubuntu systemd-oomd[1055]: Killed /user.slice/user-1001.slice/user@1001.service/app.slice/app-gnome-thunderbird-5418.scope due to memory used (15591993344) / total (16149745664) and swap used (927760384) / total (1023406080) being more than 90.00% Mar 23 11:09:28 ubuntu systemd[5029]: app-gnome-thunderbird-5418.scope: systemd-oomd killed 173 process(es) in this unit. I know it's saying those three entirely unrelated applications had suddenly decided to swallow all the RAM+swap on this laptop of mine - but the very same apps didn't act like that last week under Ubuntu-20.04, so I suspect something else is going on I can't say they hadn't swallowed all the RAM, but there is ZERO sign of a system on the verge of collapsing - everything has been screaming along just nicely - no sign of the "staggering" you normally get when the OS is heavily into swap. However, now that I look I see my 16G laptop only has 1G swap??? I just let the Ubuntu installer do it's defaults - but it used to auto-choose 1xRAM or 2xRAM - what's with this 1G swap? Could that be related? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: systemd-oomd 249.11-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 25 19:47:44 2022 InstallationDate: Installed on 2022-03-13 (11 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- 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/1966381 Title: applications crash that never crashed under Ubuntu-20.04 Status in systemd package in Ubuntu: New Bug description: Just now I was watching some video in Firefox. I popped over to another virtual workspace for a few minutes, and when I popped back to Firefox it had gone. The same thing had been happening all week (I installed fresh Ubuntu-22.04 last week) with Chrome, Firefox and Thunderbird. This time instead of shrugging it off I looked in the logs, and found this Mar 25 19:45:40 ubuntu systemd-oomd[960]: Killed /user.slice/user-1001.slice/user@1001.service/app.slice/app-gnome-firefox-6607.scope due to memory used (15940579328) / total (16153944064) and swap used (925564928) / total (1023406080) being more than 90.00% Mar 22 08:11:29 ubuntu systemd[5029]: app-gnome-google\x2dchrome-5412.scope: systemd-oomd killed 298 process(es) in this unit. Mar 23 11:09:28 ubuntu systemd-oomd[1055]: Killed /user.slice/user-1001.slice/user@1001.service/app.slice/app-gnome-thunderbird-5418.scope due to memory used (15591993344) / total (16149745664) and swap used (927760384) / total (1023406080) being more than 90.00% Mar 23 11:09:28 ubuntu systemd[5029]: app-gnome-thunderbird-5418.scope: systemd-oomd killed 173 process(es) in this unit. I know it's saying those three entirely unrelated applications had suddenly decided to swallow all the RAM+swap on this laptop of mine - but the very same apps didn't act like that last week under Ubuntu-20.04, so I suspect something else is going on I can't say they hadn't swallowed all the RAM, but there is ZERO sign of a system on the verge of collapsing - everything has been screaming along just nicely - no sign of the "staggering" you normally get when the OS is heavily into swap. However, now that I look I see my 16G laptop only has 1G swap??? I just let the Ubuntu installer do it's defaults - but it used to auto- choose 1xRAM or 2xRAM - what's with this 1G swap? Could that be related? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: systemd-oomd 249.11-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: p