[Touch-packages] [Bug 2023289] Re: System permanent freeze via running Qt5 QML + .mesh project on Ubuntu 22.04
Thanks for the bug report. The 'oibaf' PPA you are using is not supported and is known to cause graphics bugs like this. Please uninstall it using the 'ppa-purge' command, reboot, and then open new bugs for any problems that you find. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Invalid -- 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/2023289 Title: System permanent freeze via running Qt5 QML + .mesh project on Ubuntu 22.04 Status in Ubuntu: Invalid Bug description: I'm trying to launch Qt5 project with QML UI with .mesh 3D objects. This project works normally on old, grand-daddy's laptop Asus X555D, with Radeon R6 M340DX 2GB graphics, 8GB RAM and AMD A10 6th gen. But when i try to launch this project on the same Ubuntu version, on my other laptop (it's specs are listed below), i have absolute blacked out window instead of application and system freeze for about 1 minute with project (sometimes even QTCreator) crash. Here is my troubled Asus's specs: Laptop: ASUSTeK VivoBook 15 X513EAN_K513EA Graphics: Mesa Intel® Xe Graphics (TGL GT2) CPU: 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz × 8 RAM: 16,0 GB OS: Ubuntu 22.04.2 LTS, 64 bit Gnome: 42.5 Display server: x11 OpenGl ver: 4.6 (Compatibility Profile) Mesa 22.2.5 I've tried to update xinerama's libs, checked missing libs, tried to update OpenGL, tried this method but for 22.04 and, to be honest, i've lost the count of solutions that i've tried. I will be grateful for any help with information. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.1.0-1013.13-oem 6.1.25 Uname: Linux 6.1.0-1013-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jun 8 14:49:52 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. TigerLake-LP GT2 [Iris Xe Graphics] [1043:1c22] InstallationDate: Installed on 2023-04-19 (50 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0408:30d4 Quanta Computer, Inc. USB2.0 HD UVC WebCam Bus 001 Device 002: ID 09da:2403 A4Tech Co., Ltd. 2.4G Device Bus 001 Device 004: ID 8087:0026 Intel Corp. AX201 Bluetooth Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X513EAN_K513EA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.1.0-1013-oem root=UUID=9fdae802-1912-4c11-b382-7a593209ef38 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2022 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: X513EAN.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X513EAN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrX513EAN.302:bd04/21/2022:br5.19:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX513EAN_K513EA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX513EAN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: VivoBook dmi.product.name: VivoBook_ASUSLaptop X513EAN_K513EA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.115+git2305120500.98e1db~oibaf~j version.libgl1-mesa-dri: libgl1-mesa-dri 23.2~git2306080600.96cf45~oibaf~j version.libgl1-mesa-glx: libgl1-mesa-glx 23.2~git2306080600.96cf45~oibaf~j version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.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-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2023289/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 2020604] Re: After Mesa upgrades, Chrome won't show graphics
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mesa (Ubuntu Lunar) Status: New => Confirmed -- 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/2020604 Title: After Mesa upgrades, Chrome won't show graphics Status in chromium-browser package in Ubuntu: Invalid Status in mesa package in Ubuntu: Triaged Status in chromium-browser source package in Jammy: Invalid Status in mesa source package in Jammy: Fix Committed Status in chromium-browser source package in Lunar: Invalid Status in mesa source package in Lunar: Confirmed Bug description: [Impact] After patching Mesa with some driver updates, Chromium/Brave started seeing corrupt graphics. This was due to GPU acceleration being enabled in the browser by default now, and the old GPU shader cache is invalid in some ways and the browser is not able to recognize that the driver has changed, since the upstream version string hasn't changed. This is shown for instance with 'glxinfo -B' or under 'chrome:gpu' from the browser. The fix is to make the upstream VERSION to have the full packaging version, this will then be used for the core profile version string as well. [Test case] - run stock jammy, install brave-browser from brave.com, launch brave- browser, check that 'brave://gpu' shows things are accelerated, then exit the browser - enable proposed, install libgl1-mesa-dri et al - launch brave-browser again, verify that gfx are not corrupted and brave://gpu is showing acceration being used with the pulled update, graphics would be severely corrupted [Where things could go wrong] There could be apps that expect the Mesa version string to only contain a.b.c, and break in some ways when that's no longer the case. -- After today's Ubuntu 22.04 Mesa upgrades many of our users reported problems viewing graphics when using Google Chrome (Stable). The Mesa upgrades we installed were: [UPGRADE] libegl-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libegl1-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libgl1-mesa-dri:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libgl1-mesa-glx:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libglapi-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libglx-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 We documented the problem in AskUbuntu before we realized it was probably related to Mesa, so wanted to link to that report here: https://askubuntu.com/questions/1469116/since-23-may-2023-ubuntu-22-04-mesa- updates-chrome-wont-display-website-graphi There are several useful pointers and bypasses listed in that AskUbuntu link (one being to remove affected users' GPUCache directories, which does not destroy their profiles and seems to work in many but not all cases). Not sure if this is an issue with Mesa or Chrome or specific machine graphics or an interaction between them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2020604/+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 2020604] Re: After Mesa upgrades, Chrome won't show graphics
Following Timo's instructions, aptitude upgraded those two packages (along with three additional packages aptitude auto-selected) on one test system: [UPGRADE] libegl-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.2 -> 22.2.5-0ubuntu0.1~22.04.3 [UPGRADE] libgbm1:amd64 22.2.5-0ubuntu0.1~22.04.2 -> 22.2.5-0ubuntu0.1~22.04.3 [UPGRADE] libgl1-mesa-dri:amd64 22.2.5-0ubuntu0.1~22.04.2 -> 22.2.5-0ubuntu0.1~22.04.3 [UPGRADE] libglapi-mesa:amd64 22.2.5-0ubuntu0.1~22.04.2 -> 22.2.5-0ubuntu0.1~22.04.3 [UPGRADE] libglx-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.2 -> 22.2.5-0ubuntu0.1~22.04.3 Rebooted and tested Chrome. No immediate issues, graphics work. Will keep testing. -- 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/2020604 Title: After Mesa upgrades, Chrome won't show graphics Status in chromium-browser package in Ubuntu: Invalid Status in mesa package in Ubuntu: Triaged Status in chromium-browser source package in Jammy: Invalid Status in mesa source package in Jammy: Fix Committed Status in chromium-browser source package in Lunar: Invalid Status in mesa source package in Lunar: New Bug description: [Impact] After patching Mesa with some driver updates, Chromium/Brave started seeing corrupt graphics. This was due to GPU acceleration being enabled in the browser by default now, and the old GPU shader cache is invalid in some ways and the browser is not able to recognize that the driver has changed, since the upstream version string hasn't changed. This is shown for instance with 'glxinfo -B' or under 'chrome:gpu' from the browser. The fix is to make the upstream VERSION to have the full packaging version, this will then be used for the core profile version string as well. [Test case] - run stock jammy, install brave-browser from brave.com, launch brave- browser, check that 'brave://gpu' shows things are accelerated, then exit the browser - enable proposed, install libgl1-mesa-dri et al - launch brave-browser again, verify that gfx are not corrupted and brave://gpu is showing acceration being used with the pulled update, graphics would be severely corrupted [Where things could go wrong] There could be apps that expect the Mesa version string to only contain a.b.c, and break in some ways when that's no longer the case. -- After today's Ubuntu 22.04 Mesa upgrades many of our users reported problems viewing graphics when using Google Chrome (Stable). The Mesa upgrades we installed were: [UPGRADE] libegl-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libegl1-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libgl1-mesa-dri:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libgl1-mesa-glx:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libglapi-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libglx-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 We documented the problem in AskUbuntu before we realized it was probably related to Mesa, so wanted to link to that report here: https://askubuntu.com/questions/1469116/since-23-may-2023-ubuntu-22-04-mesa- updates-chrome-wont-display-website-graphi There are several useful pointers and bypasses listed in that AskUbuntu link (one being to remove affected users' GPUCache directories, which does not destroy their profiles and seems to work in many but not all cases). Not sure if this is an issue with Mesa or Chrome or specific machine graphics or an interaction between them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2020604/+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 2023342] [NEW] apparmor needs read access to no-stub-resolv.conf
Public bug reported: Description:Ubuntu 22.04.2 LTS Release:22.04 apt-cache policy apparmor apparmor: Installed: 3.0.4-2ubuntu2.2 Candidate: 3.0.4-2ubuntu2.2 apparmor 3.0.4-2ubuntu2.2 amd64 Due to issues with systemd-resolved failing to resolve hosts after a random amount of time, I have /etc/resolv.conf -> ../run/NetworkManager/no-stub-resolv.conf Unfortunately, /etc/apparmor.d/abstractions/nameservice does not allow read access to the above path, so armored daemons like chrony fail to resolve hostnames when used in their configuration files: type=AVC msg=audit(1685023761.372:15182): apparmor="DENIED" operation="open" profile="/usr/sbin/chronyd" name="/run/NetworkManager/no-stub-resolv.conf" pid=191892 comm="chronyd" requested_mask="r" denied_mask="r" fsuid=118 ouid=0^]FSUID="_chrony" OUID="root" A generalized (non-chrony specific) workaround is: mkdir /etc/apparmor.d/abstractions/nameservice.d echo @{run}/NetworkManager/no-stub-resolv.conf r, > /etc/apparmor.d/abstractions/nameservice.d/no-stub systemctl reload apparmor.service It seems to be an omission to not have '@{run}/NetworkManager/no-stub- resolv.conf r,' in the default abstractions/nameservice file. Thanks for your consideration! ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2023342 Title: apparmor needs read access to no-stub-resolv.conf Status in apparmor package in Ubuntu: New Bug description: Description: Ubuntu 22.04.2 LTS Release: 22.04 apt-cache policy apparmor apparmor: Installed: 3.0.4-2ubuntu2.2 Candidate: 3.0.4-2ubuntu2.2 apparmor 3.0.4-2ubuntu2.2 amd64 Due to issues with systemd-resolved failing to resolve hosts after a random amount of time, I have /etc/resolv.conf -> ../run/NetworkManager/no-stub-resolv.conf Unfortunately, /etc/apparmor.d/abstractions/nameservice does not allow read access to the above path, so armored daemons like chrony fail to resolve hostnames when used in their configuration files: type=AVC msg=audit(1685023761.372:15182): apparmor="DENIED" operation="open" profile="/usr/sbin/chronyd" name="/run/NetworkManager/no-stub-resolv.conf" pid=191892 comm="chronyd" requested_mask="r" denied_mask="r" fsuid=118 ouid=0^]FSUID="_chrony" OUID="root" A generalized (non-chrony specific) workaround is: mkdir /etc/apparmor.d/abstractions/nameservice.d echo @{run}/NetworkManager/no-stub-resolv.conf r, > /etc/apparmor.d/abstractions/nameservice.d/no-stub systemctl reload apparmor.service It seems to be an omission to not have '@{run}/NetworkManager/no-stub- resolv.conf r,' in the default abstractions/nameservice file. Thanks for your consideration! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2023342/+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 2009071] Re: [Blade 16 - RZ09-0483, Realtek ALC298, Speaker, Internal] No sound at all
I just received my Blade 16 and walked into the same problem with Ubuntu 22.04.2 fresh install and everything updated to latest versions. I also tested on Ubuntu 23.04, same problem. -- 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/2009071 Title: [Blade 16 - RZ09-0483, Realtek ALC298, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: New install of Ubuntu 22.04 has no audio. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mblack 1793 F pulseaudio /dev/snd/controlC1: mblack 1793 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 126: Error executing command as another user: Request dismissed Date: Thu Mar 2 13:21:20 2023 InstallationDate: Installed on 2023-03-02 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mblack 1793 F pulseaudio /dev/snd/controlC1: mblack 1793 F pulseaudio mblack 8091 F alsamixer Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [Blade 16 - RZ09-0483, Realtek ALC298, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/27/2023 dmi.bios.release: 1.7 dmi.bios.vendor: Razer dmi.bios.version: 1.07 dmi.board.name: SO690 dmi.board.vendor: Razer dmi.board.version: 4 dmi.chassis.type: 10 dmi.chassis.vendor: Razer dmi.ec.firmware.release: 1.3 dmi.modalias: dmi:bvnRazer:bvr1.07:bd01/27/2023:br1.7:efr1.3:svnRazer:pnBlade16-RZ09-0483:pvr9.04:rvnRazer:rnSO690:rvr4:cvnRazer:ct10:cvr:skuRZ09-0483SEJ3: dmi.product.family: 1A583006 Razer Blade dmi.product.name: Blade 16 - RZ09-0483 dmi.product.sku: RZ09-0483SEJ3 dmi.product.version: 9.04 dmi.sys.vendor: Razer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2009071/+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 2009071] Re: [Blade 16 - RZ09-0483, Realtek ALC298, Speaker, Internal] No sound at all
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- 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/2009071 Title: [Blade 16 - RZ09-0483, Realtek ALC298, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: New install of Ubuntu 22.04 has no audio. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mblack 1793 F pulseaudio /dev/snd/controlC1: mblack 1793 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 126: Error executing command as another user: Request dismissed Date: Thu Mar 2 13:21:20 2023 InstallationDate: Installed on 2023-03-02 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mblack 1793 F pulseaudio /dev/snd/controlC1: mblack 1793 F pulseaudio mblack 8091 F alsamixer Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [Blade 16 - RZ09-0483, Realtek ALC298, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/27/2023 dmi.bios.release: 1.7 dmi.bios.vendor: Razer dmi.bios.version: 1.07 dmi.board.name: SO690 dmi.board.vendor: Razer dmi.board.version: 4 dmi.chassis.type: 10 dmi.chassis.vendor: Razer dmi.ec.firmware.release: 1.3 dmi.modalias: dmi:bvnRazer:bvr1.07:bd01/27/2023:br1.7:efr1.3:svnRazer:pnBlade16-RZ09-0483:pvr9.04:rvnRazer:rnSO690:rvr4:cvnRazer:ct10:cvr:skuRZ09-0483SEJ3: dmi.product.family: 1A583006 Razer Blade dmi.product.name: Blade 16 - RZ09-0483 dmi.product.sku: RZ09-0483SEJ3 dmi.product.version: 9.04 dmi.sys.vendor: Razer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2009071/+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 2023322] Re: Unable to connect Ubuntu with Google Online Accounts
That command brings up the browser and things work fine there. I don't know if it matters but it seems like connecting to Microsoft also uses the same mechanism, but that works fine. It's just connecting to google. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/2023322 Title: Unable to connect Ubuntu with Google Online Accounts Status in gnome-online-accounts package in Ubuntu: New Bug description: When I go into Settings > Online Accounts > Google, I get to the prompt for email address, once in a while it stops accepting input there. But often I can get to the password screen. Once I do, I can't type anything or paste anything. This is a fresh install of Ubuntu 23.04 and I have installed all updates. Nothing in /var/crash Jun 08 11:15:59 CCW-HAL systemd[3523]: vte-spawn-8b4a59a3-a060-4bdd-92e6-285656bdb9a2.scope: Consumed 3.448s CPU time. Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:29 CCW-HAL systemd[3523]: Started app-gnome-org.gnome.Terminal-10924.scope - Application launched by gnome-shell. Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.167' (uid=1000 pid=10927 comm="/usr/bin/gnome-terminal.real" label="unconfined") Jun 08 11:16:29 CCW-HAL systemd[3523]: Starting gnome-terminal-server.service - GNOME Terminal Server... Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] Successfully activated service 'org.gnome.Terminal' Jun 08 11:16:29 CCW-HAL systemd[3523]: Started gnome-terminal-server.service - GNOME Terminal Server. Jun 08 11:16:29 CCW-HAL systemd[3523]: Started vte-spawn-9cee1911-372a-4bb4-8b57-694984e43990.scope - VTE child process 10955 launched by gnome-terminal-server process 10931. Jun 08 11:16:49 CCW-HAL gnome-control-c[8079]: Error showing account: Child process exited with code 1 Jun 08 11:16:53 CCW-HAL gnome-online-accounts-panel.desktop[9764]: GLib-GIO: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3)GLib-GIO: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’GLib: unsetenv() is not thread-safe and should not be used after threads are createdGLib-GIO: _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’GoaBackend: Loading all providers: GoaBackend: - googleGoaBackend: - owncloudGoaBackend: - windows_liveGoaBackend: - exchangeGoaBackend: - lastfmGoaBackend: - imap_smtpGoaBackend: - kerberosGoaBackend: activated kerberos providerGLib-GIO: _g_io_module_get_default: Found default implementation gnutls (GTlsBackendGnutls) for ‘gio-tls-backend’Failed to create account: Dialog was dismissed Jun 08 11:16:53 CCW-HAL xdg-desktop-por[3907]: Realtime error: Could not map pid: Could not determine pid namespace: Could not find instance-id in process's /.flatpak-info Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0) Jun 08 11:17:01 CCW-HAL CRON[11094]: (root) CMD (cd / && run-parts --report /etc/cron.hourly) Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session closed for user root Jun 08 11:17:06 CCW-HAL kernel: WebKitWebProces[11026]: segfault at 55bd22ad9adc ip 55bd22ad9adc sp 7ffd1f6adbe8 error 14 likely on CPU 2 (core 2, socket 0) Jun 08 11:17:06 CCW-HAL kernel: Code: Unable to access opcode bytes at 0x55bd22ad9ab2. Jun 08 11:17:36 CCW-HAL gnome-shell[3803]: Window manager warning: WM_TRANSIENT_FOR window 0x3a02767 for 0x3a02778 window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect window 0x3a006dc. Jun 08 11:17:42 CCW-HAL systemd[1]: Starting systemd-tmpfiles-clean.service - Cleanup of Temporary Directories... Jun 08 11:17:42 CCW-HAL systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully. Jun 08 11:17:42 CCW-HAL systemd[1]: Finished systemd-tmpfiles-clean.service - Cleanup of Temporary Directories. Jun 08 11:17:42 CCW-HAL systemd[1]: run-credentials-systemd\x2dtmpfiles\x2dclean.service.mount: Deactivated successfully. Jun 08 11:18:10 CCW-HAL gnome-shell[3803]: Window manager warning: WM_TRANSIENT_FOR window 0x3a029e2 for 0x3a029f0 window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect
[Touch-packages] [Bug 2023322] Re: Unable to connect Ubuntu with Google Online Accounts
Thank you. The systemd journal entry you included has this line which suggests a crash in webkit2gtk CCW-HAL kernel: WebKitWebProces[11026]: segfault at 55bd22ad9adc ip 55bd22ad9adc sp 7ffd1f6adbe8 error 14 likely on CPU 2 (core 2, socket 0) Do other webkit2gtk apps work for you? Could you run this command in a terminal to try the MiniBrowser? /usr/lib/x86_64-linux-gnu/webkitgtk-6.0/MiniBrowser -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/2023322 Title: Unable to connect Ubuntu with Google Online Accounts Status in gnome-online-accounts package in Ubuntu: New Bug description: When I go into Settings > Online Accounts > Google, I get to the prompt for email address, once in a while it stops accepting input there. But often I can get to the password screen. Once I do, I can't type anything or paste anything. This is a fresh install of Ubuntu 23.04 and I have installed all updates. Nothing in /var/crash Jun 08 11:15:59 CCW-HAL systemd[3523]: vte-spawn-8b4a59a3-a060-4bdd-92e6-285656bdb9a2.scope: Consumed 3.448s CPU time. Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:29 CCW-HAL systemd[3523]: Started app-gnome-org.gnome.Terminal-10924.scope - Application launched by gnome-shell. Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.167' (uid=1000 pid=10927 comm="/usr/bin/gnome-terminal.real" label="unconfined") Jun 08 11:16:29 CCW-HAL systemd[3523]: Starting gnome-terminal-server.service - GNOME Terminal Server... Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] Successfully activated service 'org.gnome.Terminal' Jun 08 11:16:29 CCW-HAL systemd[3523]: Started gnome-terminal-server.service - GNOME Terminal Server. Jun 08 11:16:29 CCW-HAL systemd[3523]: Started vte-spawn-9cee1911-372a-4bb4-8b57-694984e43990.scope - VTE child process 10955 launched by gnome-terminal-server process 10931. Jun 08 11:16:49 CCW-HAL gnome-control-c[8079]: Error showing account: Child process exited with code 1 Jun 08 11:16:53 CCW-HAL gnome-online-accounts-panel.desktop[9764]: GLib-GIO: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3)GLib-GIO: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’GLib: unsetenv() is not thread-safe and should not be used after threads are createdGLib-GIO: _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’GoaBackend: Loading all providers: GoaBackend: - googleGoaBackend: - owncloudGoaBackend: - windows_liveGoaBackend: - exchangeGoaBackend: - lastfmGoaBackend: - imap_smtpGoaBackend: - kerberosGoaBackend: activated kerberos providerGLib-GIO: _g_io_module_get_default: Found default implementation gnutls (GTlsBackendGnutls) for ‘gio-tls-backend’Failed to create account: Dialog was dismissed Jun 08 11:16:53 CCW-HAL xdg-desktop-por[3907]: Realtime error: Could not map pid: Could not determine pid namespace: Could not find instance-id in process's /.flatpak-info Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0) Jun 08 11:17:01 CCW-HAL CRON[11094]: (root) CMD (cd / && run-parts --report /etc/cron.hourly) Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session closed for user root Jun 08 11:17:06 CCW-HAL kernel: WebKitWebProces[11026]: segfault at 55bd22ad9adc ip 55bd22ad9adc sp 7ffd1f6adbe8 error 14 likely on CPU 2 (core 2, socket 0) Jun 08 11:17:06 CCW-HAL kernel: Code: Unable to access opcode bytes at 0x55bd22ad9ab2. Jun 08 11:17:36 CCW-HAL gnome-shell[3803]: Window manager warning: WM_TRANSIENT_FOR window 0x3a02767 for 0x3a02778 window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect window 0x3a006dc. Jun 08 11:17:42 CCW-HAL systemd[1]: Starting systemd-tmpfiles-clean.service - Cleanup of Temporary Directories... Jun 08 11:17:42 CCW-HAL systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully. Jun 08 11:17:42 CCW-HAL systemd[1]: Finished systemd-tmpfiles-clean.service - Cleanup of Temporary Directories. Jun 08 11:17:42 CCW-HAL systemd[1]: run-credentials-systemd\x2dtmpfiles\x2dclean.service.mount: Deactivated successfully. Jun 08 11:18:10 CCW-HAL gnome-shell[3803]: Window manager warning: WM_TRANSIENT_FOR
[Touch-packages] [Bug 1854588] Re: gdebi-gtk calls pkexec inappropriately
Hi Alkis, You are absolutely correct. I just removed the firefox snap and installed it through the mozillateam PPA instead, and indeed, gdebi ends up parented by init when launched through Firefox's downloads, just like what I saw with Chrome, and the same issue is reproducible (my patch fixes it). So snap has been hiding the problem. Thanks for pointing that out! -- 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/1854588 Title: gdebi-gtk calls pkexec inappropriately Status in gdebi package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu with gdebi-gtk installed 2. Open Firefox 3. Visit some site with deb-package download link or use direct link like https://github.com/jgm/pandoc/releases/download/2.9.2.1/pandoc-2.9.2.1-1-amd64.deb 4. Proceed with file downloading 5. In Firefox select Library → Downloads, click on downloaded deb-file Expected results: * gdebi-gtk is opened, the package installs normally after users clicks Install button Actual results: * gdebi-gtk is opened, the package is not installed because of vanishing of gdebi-gtk window just after clicking Install button Before anyone says this bug already exists... it doesn't (at least as far as I can see). It's just that a lot of similar bugs do/did exist where people have also experienced the same symptoms (of gdebi-gtk vanishing upon clicking 'Install'). So yes this is the same symptoms, but it must be a different cause as the circumstances are different and doesn't have the same resolution. The meat of it... Basically on a fresh install of Ubuntu MATE 18.04.3 amd64... with Firefox (or with Chrome if you installed that) go to any site that offers a .deb package and either... a) choose to open it directly from the browser (rather than saving it to 'Downloads' folder) b) or... save the file (e.g. to the 'Downloads' folder), BUT!.. open that file from within the browser itself. You should find that gdebi-gtk appears but vanishes the moment you click 'Install' without a prompt for a password, an explanation or the package actually getting installed. This bug has existed since the beginning of Ubuntu 18.04 however it's been largely confused with other similar bugs. I've had it on half a dozen machines and confirmed it exists with IRC users on #ubuntu-mate of freenode. However with *this* bug (compared to others) gdebi-gtk works perfectly fine if you run it from the terminal or just double click the .deb package from your file manager. It's the kind of bug which if you're a hardened desktop Linux user, you'd just work around it... But if you're a novice and you can't get a simple thing like Teamviewer installed (which is a .deb, and a thing I might ask someone to do over the phone to try to help them) you likely get fed up and re-install Windows :S Any input on this would be brilliant as I can't seem to get any logs/output. ~lantizia To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1854588/+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 2019739] Re: Cannot reauthorize Google account or authorize again. The app crashes
I'm not sure if it's identical or not: https://bugs.launchpad.net/ubuntu/+source/gnome-online- accounts/+bug/2023322 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/2019739 Title: Cannot reauthorize Google account or authorize again. The app crashes Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-online-accounts package in Ubuntu: Confirmed Bug description: As in title I tried to relogin, The window prompt appears and quickly exits and nothing happens. Still cannot not logged in. Have to remove account and sign in again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-online-accounts 3.44.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon May 15 17:45:34 2023 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2019739/+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 1854588] Re: gdebi-gtk calls pkexec inappropriately
> I will point out that Firefox, regardless of how it's launched, seems to not be affected anymore. If you're testing firefox.snap, that might be the cause, i.e. maybe snap does the parenting. While e.g. firefox.deb from the mozillateam PPA (or firefox in Debian) could still have the issue. Thanks for working on this! -- 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/1854588 Title: gdebi-gtk calls pkexec inappropriately Status in gdebi package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu with gdebi-gtk installed 2. Open Firefox 3. Visit some site with deb-package download link or use direct link like https://github.com/jgm/pandoc/releases/download/2.9.2.1/pandoc-2.9.2.1-1-amd64.deb 4. Proceed with file downloading 5. In Firefox select Library → Downloads, click on downloaded deb-file Expected results: * gdebi-gtk is opened, the package installs normally after users clicks Install button Actual results: * gdebi-gtk is opened, the package is not installed because of vanishing of gdebi-gtk window just after clicking Install button Before anyone says this bug already exists... it doesn't (at least as far as I can see). It's just that a lot of similar bugs do/did exist where people have also experienced the same symptoms (of gdebi-gtk vanishing upon clicking 'Install'). So yes this is the same symptoms, but it must be a different cause as the circumstances are different and doesn't have the same resolution. The meat of it... Basically on a fresh install of Ubuntu MATE 18.04.3 amd64... with Firefox (or with Chrome if you installed that) go to any site that offers a .deb package and either... a) choose to open it directly from the browser (rather than saving it to 'Downloads' folder) b) or... save the file (e.g. to the 'Downloads' folder), BUT!.. open that file from within the browser itself. You should find that gdebi-gtk appears but vanishes the moment you click 'Install' without a prompt for a password, an explanation or the package actually getting installed. This bug has existed since the beginning of Ubuntu 18.04 however it's been largely confused with other similar bugs. I've had it on half a dozen machines and confirmed it exists with IRC users on #ubuntu-mate of freenode. However with *this* bug (compared to others) gdebi-gtk works perfectly fine if you run it from the terminal or just double click the .deb package from your file manager. It's the kind of bug which if you're a hardened desktop Linux user, you'd just work around it... But if you're a novice and you can't get a simple thing like Teamviewer installed (which is a .deb, and a thing I might ask someone to do over the phone to try to help them) you likely get fed up and re-install Windows :S Any input on this would be brilliant as I can't seem to get any logs/output. ~lantizia To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1854588/+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 2023322] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2023322/+attachment/5678692/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/2023322 Title: Unable to connect Ubuntu with Google Online Accounts Status in gnome-online-accounts package in Ubuntu: New Bug description: When I go into Settings > Online Accounts > Google, I get to the prompt for email address, once in a while it stops accepting input there. But often I can get to the password screen. Once I do, I can't type anything or paste anything. This is a fresh install of Ubuntu 23.04 and I have installed all updates. Nothing in /var/crash Jun 08 11:15:59 CCW-HAL systemd[3523]: vte-spawn-8b4a59a3-a060-4bdd-92e6-285656bdb9a2.scope: Consumed 3.448s CPU time. Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:29 CCW-HAL systemd[3523]: Started app-gnome-org.gnome.Terminal-10924.scope - Application launched by gnome-shell. Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.167' (uid=1000 pid=10927 comm="/usr/bin/gnome-terminal.real" label="unconfined") Jun 08 11:16:29 CCW-HAL systemd[3523]: Starting gnome-terminal-server.service - GNOME Terminal Server... Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] Successfully activated service 'org.gnome.Terminal' Jun 08 11:16:29 CCW-HAL systemd[3523]: Started gnome-terminal-server.service - GNOME Terminal Server. Jun 08 11:16:29 CCW-HAL systemd[3523]: Started vte-spawn-9cee1911-372a-4bb4-8b57-694984e43990.scope - VTE child process 10955 launched by gnome-terminal-server process 10931. Jun 08 11:16:49 CCW-HAL gnome-control-c[8079]: Error showing account: Child process exited with code 1 Jun 08 11:16:53 CCW-HAL gnome-online-accounts-panel.desktop[9764]: GLib-GIO: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3)GLib-GIO: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’GLib: unsetenv() is not thread-safe and should not be used after threads are createdGLib-GIO: _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’GoaBackend: Loading all providers: GoaBackend: - googleGoaBackend: - owncloudGoaBackend: - windows_liveGoaBackend: - exchangeGoaBackend: - lastfmGoaBackend: - imap_smtpGoaBackend: - kerberosGoaBackend: activated kerberos providerGLib-GIO: _g_io_module_get_default: Found default implementation gnutls (GTlsBackendGnutls) for ‘gio-tls-backend’Failed to create account: Dialog was dismissed Jun 08 11:16:53 CCW-HAL xdg-desktop-por[3907]: Realtime error: Could not map pid: Could not determine pid namespace: Could not find instance-id in process's /.flatpak-info Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0) Jun 08 11:17:01 CCW-HAL CRON[11094]: (root) CMD (cd / && run-parts --report /etc/cron.hourly) Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session closed for user root Jun 08 11:17:06 CCW-HAL kernel: WebKitWebProces[11026]: segfault at 55bd22ad9adc ip 55bd22ad9adc sp 7ffd1f6adbe8 error 14 likely on CPU 2 (core 2, socket 0) Jun 08 11:17:06 CCW-HAL kernel: Code: Unable to access opcode bytes at 0x55bd22ad9ab2. Jun 08 11:17:36 CCW-HAL gnome-shell[3803]: Window manager warning: WM_TRANSIENT_FOR window 0x3a02767 for 0x3a02778 window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect window 0x3a006dc. Jun 08 11:17:42 CCW-HAL systemd[1]: Starting systemd-tmpfiles-clean.service - Cleanup of Temporary Directories... Jun 08 11:17:42 CCW-HAL systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully. Jun 08 11:17:42 CCW-HAL systemd[1]: Finished systemd-tmpfiles-clean.service - Cleanup of Temporary Directories. Jun 08 11:17:42 CCW-HAL systemd[1]: run-credentials-systemd\x2dtmpfiles\x2dclean.service.mount: Deactivated successfully. Jun 08 11:18:10 CCW-HAL gnome-shell[3803]: Window manager warning: WM_TRANSIENT_FOR window 0x3a029e2 for 0x3a029f0 window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect window 0x3a006dc. --- ProblemType: Bug
[Touch-packages] [Bug 2023322] Re: Unable to connect Ubuntu with Google Online Accounts
apport information ** Tags added: apport-collected lunar ** Description changed: When I go into Settings > Online Accounts > Google, I get to the prompt for email address, once in a while it stops accepting input there. But often I can get to the password screen. Once I do, I can't type anything or paste anything. This is a fresh install of Ubuntu 23.04 and I have installed all updates. Nothing in /var/crash Jun 08 11:15:59 CCW-HAL systemd[3523]: vte-spawn-8b4a59a3-a060-4bdd-92e6-285656bdb9a2.scope: Consumed 3.448s CPU time. Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:29 CCW-HAL systemd[3523]: Started app-gnome-org.gnome.Terminal-10924.scope - Application launched by gnome-shell. Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.167' (uid=1000 pid=10927 comm="/usr/bin/gnome-terminal.real" label="unconfined") Jun 08 11:16:29 CCW-HAL systemd[3523]: Starting gnome-terminal-server.service - GNOME Terminal Server... Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] Successfully activated service 'org.gnome.Terminal' Jun 08 11:16:29 CCW-HAL systemd[3523]: Started gnome-terminal-server.service - GNOME Terminal Server. Jun 08 11:16:29 CCW-HAL systemd[3523]: Started vte-spawn-9cee1911-372a-4bb4-8b57-694984e43990.scope - VTE child process 10955 launched by gnome-terminal-server process 10931. Jun 08 11:16:49 CCW-HAL gnome-control-c[8079]: Error showing account: Child process exited with code 1 Jun 08 11:16:53 CCW-HAL gnome-online-accounts-panel.desktop[9764]: GLib-GIO: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3)GLib-GIO: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’GLib: unsetenv() is not thread-safe and should not be used after threads are createdGLib-GIO: _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’GoaBackend: Loading all providers: GoaBackend: - googleGoaBackend: - owncloudGoaBackend: - windows_liveGoaBackend: - exchangeGoaBackend: - lastfmGoaBackend: - imap_smtpGoaBackend: - kerberosGoaBackend: activated kerberos providerGLib-GIO: _g_io_module_get_default: Found default implementation gnutls (GTlsBackendGnutls) for ‘gio-tls-backend’Failed to create account: Dialog was dismissed Jun 08 11:16:53 CCW-HAL xdg-desktop-por[3907]: Realtime error: Could not map pid: Could not determine pid namespace: Could not find instance-id in process's /.flatpak-info Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0) Jun 08 11:17:01 CCW-HAL CRON[11094]: (root) CMD (cd / && run-parts --report /etc/cron.hourly) Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session closed for user root Jun 08 11:17:06 CCW-HAL kernel: WebKitWebProces[11026]: segfault at 55bd22ad9adc ip 55bd22ad9adc sp 7ffd1f6adbe8 error 14 likely on CPU 2 (core 2, socket 0) Jun 08 11:17:06 CCW-HAL kernel: Code: Unable to access opcode bytes at 0x55bd22ad9ab2. Jun 08 11:17:36 CCW-HAL gnome-shell[3803]: Window manager warning: WM_TRANSIENT_FOR window 0x3a02767 for 0x3a02778 window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect window 0x3a006dc. Jun 08 11:17:42 CCW-HAL systemd[1]: Starting systemd-tmpfiles-clean.service - Cleanup of Temporary Directories... Jun 08 11:17:42 CCW-HAL systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully. Jun 08 11:17:42 CCW-HAL systemd[1]: Finished systemd-tmpfiles-clean.service - Cleanup of Temporary Directories. Jun 08 11:17:42 CCW-HAL systemd[1]: run-credentials-systemd\x2dtmpfiles\x2dclean.service.mount: Deactivated successfully. Jun 08 11:18:10 CCW-HAL gnome-shell[3803]: Window manager warning: WM_TRANSIENT_FOR window 0x3a029e2 for 0x3a029f0 window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect window 0x3a006dc. + --- + ProblemType: Bug + ApportVersion: 2.26.1-0ubuntu2 + Architecture: amd64 + CasperMD5CheckResult: unknown + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 23.04 + InstallationDate: Installed on 2023-06-01 (7 days ago) + InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) + NonfreeKernelModules: nvidia_modeset nvidia + Package: gnome-online-accounts 3.48.0-1 + PackageArchitecture: amd64 + ProcEnviron: +
[Touch-packages] [Bug 2023327] [NEW] package ubuntu-standard 1.501 failed to install/upgrade: afhængighedsproblemer - efterlader den ukonfigureret
Public bug reported: Trying to install ubuntu-gnome-desktop ProblemType: Package DistroRelease: Ubuntu 23.04 Package: ubuntu-standard 1.501 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Apr 17 17:53:06 2023 ErrorMessage: afhængighedsproblemer - efterlader den ukonfigureret InstallationDate: Installed on 2016-02-08 (2677 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160208) Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.21ubuntu1 apt 2.6.0 SourcePackage: ubuntu-meta Title: package ubuntu-standard 1.501 failed to install/upgrade: afhængighedsproblemer - efterlader den ukonfigureret UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package lunar -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2023327 Title: package ubuntu-standard 1.501 failed to install/upgrade: afhængighedsproblemer - efterlader den ukonfigureret Status in ubuntu-meta package in Ubuntu: New Bug description: Trying to install ubuntu-gnome-desktop ProblemType: Package DistroRelease: Ubuntu 23.04 Package: ubuntu-standard 1.501 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Apr 17 17:53:06 2023 ErrorMessage: afhængighedsproblemer - efterlader den ukonfigureret InstallationDate: Installed on 2016-02-08 (2677 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160208) Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.21ubuntu1 apt 2.6.0 SourcePackage: ubuntu-meta Title: package ubuntu-standard 1.501 failed to install/upgrade: afhængighedsproblemer - efterlader den ukonfigureret UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2023327/+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 2016908] Re: udev fails to make prctl() syscall with apparmor=0 (as used by maas by default)
This bug is awaiting verification that the linux- hwe-6.2/6.2.0-23.23~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-hwe-6.2 verification-needed-jammy -- 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/2016908 Title: udev fails to make prctl() syscall with apparmor=0 (as used by maas by default) Status in AppArmor: New Status in MAAS: Fix Committed Status in maas-images: Invalid Status in apparmor package in Ubuntu: Confirmed Status in linux package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: Invalid Status in apparmor source package in Lunar: Confirmed Status in linux source package in Lunar: Fix Committed Status in systemd source package in Lunar: Invalid Bug description: I'm assuming the image being used for these deploys is 20230417 or 20230417.1 based on the fact that I saw a 6.2 kernel being used which I don't believe was part of the 20230319 serial. I don't have access to the maas server, so I can't directly check any log files. MAAS Version: 3.3.2 Here's where the serial log indicates it can't download the squashfs. The full log is attached as scobee-lunar-no-squashfs.log (there are some other console message intermixed): no search or nameservers found in /run/net-BOOTIF.conf /run/net-*.conf /run/net6 -*.conf :: root=squash:http://10.229.32.21:5248/images/ubuntu/arm64/ga-23.04/lunar/candi date/squa[ 206.804704] Btrfs loaded, crc32c=crc32c-generic, zoned=yes, fsverity =yes shfs :: mount_squash downloading http://10.229.32.21:5248/images/ubuntu/arm64/ga-23.0 4/lunar/candidate/squashfs to /root.tmp.img Connecting to 10.229.32.21:5248 (10.229.32.21:5248) wget: can't connect to remote host (10.229.32.21): Network is unreachable :: mount -t squashfs -o loop '/root.tmp.img' '/root.tmp' mount: mounting /root.tmp.img on /root.tmp failed: No such file or directory done. Still gathering logs and info and will update as I go. Kernel Bug / Apparmor reproducer $ wget https://images.maas.io/ephemeral-v3/candidate/lunar/amd64/20230419/ga-23.04/generic/boot-kernel $ wget https://images.maas.io/ephemeral-v3/candidate/lunar/amd64/20230419/ga-23.04/generic/boot-initrd $ qemu-system-x86_64 -nographic -m 2G -kernel ./boot-kernel -initrd ./boot-initrd -append 'console=ttyS0 break=modules apparmor=0' #start the VM Starting systemd-udevd version 252.5-2ubuntu3 Spawning shell within the initramfs BusyBox v1.35.0 (Ubuntu 1:1.35.0-4ubuntu1) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) udevadm info --export-db Failed to set death signal: Invalid argument Observe that udevadm fails to setup death signal, with in systemd code is this https://github.com/systemd/systemd/blob/08c2f9c626e0f0052d505b1b7e52f335c0fbfa1d/src/basic/process- util.c#L1252 if (flags & (FORK_DEATHSIG|FORK_DEATHSIG_SIGINT)) if (prctl(PR_SET_PDEATHSIG, (flags & FORK_DEATHSIG_SIGINT) ? SIGINT : SIGTERM) < 0) { log_full_errno(prio, errno, "Failed to set death signal: %m"); _exit(EXIT_FAILURE); } workaround set kernel commandline to `apparmor=1` MAAS bug Why is maas setting `apparmor=0` ? Ubuntu shouldn't be used without apparmor. Even for deployment and commisioning. To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/2016908/+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 2023322] Re: Unable to connect Ubuntu with Google Online Accounts
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 2023322 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/2023322 Title: Unable to connect Ubuntu with Google Online Accounts Status in gnome-online-accounts package in Ubuntu: New Bug description: When I go into Settings > Online Accounts > Google, I get to the prompt for email address, once in a while it stops accepting input there. But often I can get to the password screen. Once I do, I can't type anything or paste anything. This is a fresh install of Ubuntu 23.04 and I have installed all updates. Nothing in /var/crash Jun 08 11:15:59 CCW-HAL systemd[3523]: vte-spawn-8b4a59a3-a060-4bdd-92e6-285656bdb9a2.scope: Consumed 3.448s CPU time. Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:29 CCW-HAL systemd[3523]: Started app-gnome-org.gnome.Terminal-10924.scope - Application launched by gnome-shell. Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.167' (uid=1000 pid=10927 comm="/usr/bin/gnome-terminal.real" label="unconfined") Jun 08 11:16:29 CCW-HAL systemd[3523]: Starting gnome-terminal-server.service - GNOME Terminal Server... Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] Successfully activated service 'org.gnome.Terminal' Jun 08 11:16:29 CCW-HAL systemd[3523]: Started gnome-terminal-server.service - GNOME Terminal Server. Jun 08 11:16:29 CCW-HAL systemd[3523]: Started vte-spawn-9cee1911-372a-4bb4-8b57-694984e43990.scope - VTE child process 10955 launched by gnome-terminal-server process 10931. Jun 08 11:16:49 CCW-HAL gnome-control-c[8079]: Error showing account: Child process exited with code 1 Jun 08 11:16:53 CCW-HAL gnome-online-accounts-panel.desktop[9764]: GLib-GIO: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3)GLib-GIO: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’GLib: unsetenv() is not thread-safe and should not be used after threads are createdGLib-GIO: _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’GoaBackend: Loading all providers: GoaBackend: - googleGoaBackend: - owncloudGoaBackend: - windows_liveGoaBackend: - exchangeGoaBackend: - lastfmGoaBackend: - imap_smtpGoaBackend: - kerberosGoaBackend: activated kerberos providerGLib-GIO: _g_io_module_get_default: Found default implementation gnutls (GTlsBackendGnutls) for ‘gio-tls-backend’Failed to create account: Dialog was dismissed Jun 08 11:16:53 CCW-HAL xdg-desktop-por[3907]: Realtime error: Could not map pid: Could not determine pid namespace: Could not find instance-id in process's /.flatpak-info Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0) Jun 08 11:17:01 CCW-HAL CRON[11094]: (root) CMD (cd / && run-parts --report /etc/cron.hourly) Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session closed for user root Jun 08 11:17:06 CCW-HAL kernel: WebKitWebProces[11026]: segfault at 55bd22ad9adc ip 55bd22ad9adc sp 7ffd1f6adbe8 error 14 likely on CPU 2 (core 2, socket 0) Jun 08 11:17:06 CCW-HAL kernel: Code: Unable to access opcode bytes at 0x55bd22ad9ab2. Jun 08 11:17:36 CCW-HAL gnome-shell[3803]: Window manager warning: WM_TRANSIENT_FOR window 0x3a02767 for 0x3a02778 window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect window 0x3a006dc. Jun 08 11:17:42 CCW-HAL systemd[1]: Starting systemd-tmpfiles-clean.service - Cleanup of Temporary Directories... Jun 08 11:17:42 CCW-HAL systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully. Jun 08 11:17:42 CCW-HAL systemd[1]: Finished systemd-tmpfiles-clean.service - Cleanup of Temporary Directories. Jun 08 11:17:42 CCW-HAL systemd[1]: run-credentials-systemd\x2dtmpfiles\x2dclean.service.mount: Deactivated successfully. Jun 08 11:18:10 CCW-HAL gnome-shell[3803]: Window manager warning:
[Touch-packages] [Bug 1854588] Re: gdebi-gtk calls pkexec inappropriately
Feedback on the patch has been addressed and it has been resubmitted. -- 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/1854588 Title: gdebi-gtk calls pkexec inappropriately Status in gdebi package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu with gdebi-gtk installed 2. Open Firefox 3. Visit some site with deb-package download link or use direct link like https://github.com/jgm/pandoc/releases/download/2.9.2.1/pandoc-2.9.2.1-1-amd64.deb 4. Proceed with file downloading 5. In Firefox select Library → Downloads, click on downloaded deb-file Expected results: * gdebi-gtk is opened, the package installs normally after users clicks Install button Actual results: * gdebi-gtk is opened, the package is not installed because of vanishing of gdebi-gtk window just after clicking Install button Before anyone says this bug already exists... it doesn't (at least as far as I can see). It's just that a lot of similar bugs do/did exist where people have also experienced the same symptoms (of gdebi-gtk vanishing upon clicking 'Install'). So yes this is the same symptoms, but it must be a different cause as the circumstances are different and doesn't have the same resolution. The meat of it... Basically on a fresh install of Ubuntu MATE 18.04.3 amd64... with Firefox (or with Chrome if you installed that) go to any site that offers a .deb package and either... a) choose to open it directly from the browser (rather than saving it to 'Downloads' folder) b) or... save the file (e.g. to the 'Downloads' folder), BUT!.. open that file from within the browser itself. You should find that gdebi-gtk appears but vanishes the moment you click 'Install' without a prompt for a password, an explanation or the package actually getting installed. This bug has existed since the beginning of Ubuntu 18.04 however it's been largely confused with other similar bugs. I've had it on half a dozen machines and confirmed it exists with IRC users on #ubuntu-mate of freenode. However with *this* bug (compared to others) gdebi-gtk works perfectly fine if you run it from the terminal or just double click the .deb package from your file manager. It's the kind of bug which if you're a hardened desktop Linux user, you'd just work around it... But if you're a novice and you can't get a simple thing like Teamviewer installed (which is a .deb, and a thing I might ask someone to do over the phone to try to help them) you likely get fed up and re-install Windows :S Any input on this would be brilliant as I can't seem to get any logs/output. ~lantizia To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1854588/+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 2023322] [NEW] Unable to connect Ubuntu with Google Online Accounts
Public bug reported: When I go into Settings > Online Accounts > Google, I get to the prompt for email address, once in a while it stops accepting input there. But often I can get to the password screen. Once I do, I can't type anything or paste anything. This is a fresh install of Ubuntu 23.04 and I have installed all updates. Nothing in /var/crash Jun 08 11:15:59 CCW-HAL systemd[3523]: vte-spawn-8b4a59a3-a060-4bdd-92e6-285656bdb9a2.scope: Consumed 3.448s CPU time. Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:29 CCW-HAL systemd[3523]: Started app-gnome-org.gnome.Terminal-10924.scope - Application launched by gnome-shell. Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.167' (uid=1000 pid=10927 comm="/usr/bin/gnome-terminal.real" label="unconfined") Jun 08 11:16:29 CCW-HAL systemd[3523]: Starting gnome-terminal-server.service - GNOME Terminal Server... Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] Successfully activated service 'org.gnome.Terminal' Jun 08 11:16:29 CCW-HAL systemd[3523]: Started gnome-terminal-server.service - GNOME Terminal Server. Jun 08 11:16:29 CCW-HAL systemd[3523]: Started vte-spawn-9cee1911-372a-4bb4-8b57-694984e43990.scope - VTE child process 10955 launched by gnome-terminal-server process 10931. Jun 08 11:16:49 CCW-HAL gnome-control-c[8079]: Error showing account: Child process exited with code 1 Jun 08 11:16:53 CCW-HAL gnome-online-accounts-panel.desktop[9764]: GLib-GIO: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3)GLib-GIO: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’GLib: unsetenv() is not thread-safe and should not be used after threads are createdGLib-GIO: _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’GoaBackend: Loading all providers: GoaBackend: - googleGoaBackend: - owncloudGoaBackend: - windows_liveGoaBackend: - exchangeGoaBackend: - lastfmGoaBackend: - imap_smtpGoaBackend: - kerberosGoaBackend: activated kerberos providerGLib-GIO: _g_io_module_get_default: Found default implementation gnutls (GTlsBackendGnutls) for ‘gio-tls-backend’Failed to create account: Dialog was dismissed Jun 08 11:16:53 CCW-HAL xdg-desktop-por[3907]: Realtime error: Could not map pid: Could not determine pid namespace: Could not find instance-id in process's /.flatpak-info Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0) Jun 08 11:17:01 CCW-HAL CRON[11094]: (root) CMD (cd / && run-parts --report /etc/cron.hourly) Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session closed for user root Jun 08 11:17:06 CCW-HAL kernel: WebKitWebProces[11026]: segfault at 55bd22ad9adc ip 55bd22ad9adc sp 7ffd1f6adbe8 error 14 likely on CPU 2 (core 2, socket 0) Jun 08 11:17:06 CCW-HAL kernel: Code: Unable to access opcode bytes at 0x55bd22ad9ab2. Jun 08 11:17:36 CCW-HAL gnome-shell[3803]: Window manager warning: WM_TRANSIENT_FOR window 0x3a02767 for 0x3a02778 window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect window 0x3a006dc. Jun 08 11:17:42 CCW-HAL systemd[1]: Starting systemd-tmpfiles-clean.service - Cleanup of Temporary Directories... Jun 08 11:17:42 CCW-HAL systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully. Jun 08 11:17:42 CCW-HAL systemd[1]: Finished systemd-tmpfiles-clean.service - Cleanup of Temporary Directories. Jun 08 11:17:42 CCW-HAL systemd[1]: run-credentials-systemd\x2dtmpfiles\x2dclean.service.mount: Deactivated successfully. Jun 08 11:18:10 CCW-HAL gnome-shell[3803]: Window manager warning: WM_TRANSIENT_FOR window 0x3a029e2 for 0x3a029f0 window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect window 0x3a006dc. ** Affects: gnome-online-accounts (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/2023322 Title: Unable to connect Ubuntu with Google Online Accounts Status in gnome-online-accounts package in Ubuntu: New Bug description: When I go into Settings > Online Accounts > Google, I get to the prompt for email address, once in a while it stops accepting input there.
[Touch-packages] [Bug 2019739] Re: Cannot reauthorize Google account or authorize again. The app crashes
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-online-accounts (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/2019739 Title: Cannot reauthorize Google account or authorize again. The app crashes Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-online-accounts package in Ubuntu: Confirmed Bug description: As in title I tried to relogin, The window prompt appears and quickly exits and nothing happens. Still cannot not logged in. Have to remove account and sign in again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-online-accounts 3.44.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon May 15 17:45:34 2023 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2019739/+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 2019739] Re: Cannot reauthorize Google account or authorize again. The app crashes
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-control-center (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/2019739 Title: Cannot reauthorize Google account or authorize again. The app crashes Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-online-accounts package in Ubuntu: Confirmed Bug description: As in title I tried to relogin, The window prompt appears and quickly exits and nothing happens. Still cannot not logged in. Have to remove account and sign in again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-online-accounts 3.44.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon May 15 17:45:34 2023 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2019739/+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 2019739] Re: Cannot reauthorize Google account or authorize again. The app crashes
I am having the same issue. How can I help? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/2019739 Title: Cannot reauthorize Google account or authorize again. The app crashes Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-online-accounts package in Ubuntu: Confirmed Bug description: As in title I tried to relogin, The window prompt appears and quickly exits and nothing happens. Still cannot not logged in. Have to remove account and sign in again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-online-accounts 3.44.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon May 15 17:45:34 2023 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2019739/+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 1854588] Re: gdebi-gtk calls pkexec inappropriately
I take back what I said in my previous comment. This does still affect 23.04, at least with Ubuntu MATE and Chrome. It all depends on how the processes are parented, which changes based on how you launch Chrome. If I launch Chrome from the MATE menu, it gets parented to "systemd --user" and this problem doesn't occur. If I launch Chrome by clicking its icon in mate-panel, it gets parented to mate-panel instead, which follows a parenting chain of mate-session -> lightdm -> init. This difference also affects how gdebi ends up being parented when Chrome launches it from its downloads. gdebi ends up parented to init if I try to open a Chrome download from Chrome after I've launched Chrome from the panel, and this problem occurs. The same can be said about the "setsid gdebi-gtk package.deb" command. If I start MATE Terminal from the MATE menu and run that command, it works fine. If I start MATE Terminal from mate-panel and run the same command, it immediately exits and I get the "Refusing to render service to dead parents." message instead. I suspect this difference explains why some people haven't been able to reproduce this problem but others have. I will point out that Firefox, regardless of how it's launched, seems to not be affected anymore. gdebi always ends up parented by systemd when Firefox launches it. Clearly there is still value in fixing this in gdebi. I'll look into addressing Julian's feedback and resubmitting the fix. -- 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/1854588 Title: gdebi-gtk calls pkexec inappropriately Status in gdebi package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu with gdebi-gtk installed 2. Open Firefox 3. Visit some site with deb-package download link or use direct link like https://github.com/jgm/pandoc/releases/download/2.9.2.1/pandoc-2.9.2.1-1-amd64.deb 4. Proceed with file downloading 5. In Firefox select Library → Downloads, click on downloaded deb-file Expected results: * gdebi-gtk is opened, the package installs normally after users clicks Install button Actual results: * gdebi-gtk is opened, the package is not installed because of vanishing of gdebi-gtk window just after clicking Install button Before anyone says this bug already exists... it doesn't (at least as far as I can see). It's just that a lot of similar bugs do/did exist where people have also experienced the same symptoms (of gdebi-gtk vanishing upon clicking 'Install'). So yes this is the same symptoms, but it must be a different cause as the circumstances are different and doesn't have the same resolution. The meat of it... Basically on a fresh install of Ubuntu MATE 18.04.3 amd64... with Firefox (or with Chrome if you installed that) go to any site that offers a .deb package and either... a) choose to open it directly from the browser (rather than saving it to 'Downloads' folder) b) or... save the file (e.g. to the 'Downloads' folder), BUT!.. open that file from within the browser itself. You should find that gdebi-gtk appears but vanishes the moment you click 'Install' without a prompt for a password, an explanation or the package actually getting installed. This bug has existed since the beginning of Ubuntu 18.04 however it's been largely confused with other similar bugs. I've had it on half a dozen machines and confirmed it exists with IRC users on #ubuntu-mate of freenode. However with *this* bug (compared to others) gdebi-gtk works perfectly fine if you run it from the terminal or just double click the .deb package from your file manager. It's the kind of bug which if you're a hardened desktop Linux user, you'd just work around it... But if you're a novice and you can't get a simple thing like Teamviewer installed (which is a .deb, and a thing I might ask someone to do over the phone to try to help them) you likely get fed up and re-install Windows :S Any input on this would be brilliant as I can't seem to get any logs/output. ~lantizia To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1854588/+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 2023301] Re: Please merge dbus 1.14.6-1 (main) from debian unstable (main)
** Description changed: - TODO + Debian has dbus 1.14.6-1 in unstable + Ubuntu has dbus 1.14.4-1ubuntu1 in mantic + + Two changes from @waveform have been merged upstream and the relevant + delta can be dropped in Ubuntu. + + - d/p/u/concrete-dbus-socket.patch: Add the "real" path used by the apparmor +autopkgtest to the apparmor profile in the test +[merged upstream in 1.14.6] + - d/control: Add M-A: foreign to the new dbus-{session,system}-bus-common +packages to permit the resolver to use them to satisfy i386 dependencies +[merged in debian in 1.14.6-1] -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/2023301 Title: Please merge dbus 1.14.6-1 (main) from debian unstable (main) Status in dbus package in Ubuntu: In Progress Bug description: Debian has dbus 1.14.6-1 in unstable Ubuntu has dbus 1.14.4-1ubuntu1 in mantic Two changes from @waveform have been merged upstream and the relevant delta can be dropped in Ubuntu. - d/p/u/concrete-dbus-socket.patch: Add the "real" path used by the apparmor autopkgtest to the apparmor profile in the test [merged upstream in 1.14.6] - d/control: Add M-A: foreign to the new dbus-{session,system}-bus-common packages to permit the resolver to use them to satisfy i386 dependencies [merged in debian in 1.14.6-1] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/2023301/+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 2023016] Re: Merge 13.1-3 into mantic
** Description changed: - The upstream version 13.1-3 should be merged into mantic. The current + The upstream version 13.2-1 should be merged into mantic. The current version is 13.1-2ubuntu2. See the merge conflict report: https://merges.ubuntu.com/g/gdb/REPORT Note: this is a tracking bug ** Summary changed: - Merge 13.1-3 into mantic + Merge 13.2-1 into mantic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/2023016 Title: Merge 13.2-1 into mantic Status in gdb package in Ubuntu: In Progress Bug description: The upstream version 13.2-1 should be merged into mantic. The current version is 13.1-2ubuntu2. See the merge conflict report: https://merges.ubuntu.com/g/gdb/REPORT Note: this is a tracking bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/2023016/+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 2023229] Re: Autopkgtest failure for tests-in-lxd
Here is one sample: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/s/systemd/20230607_231036_1c385@/log.gz -- 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/2023229 Title: Autopkgtest failure for tests-in-lxd Status in systemd package in Ubuntu: Incomplete Status in systemd source package in Jammy: New Bug description: Autopackagetests on multiple Jammy kernels show the same failure on the test-in-lxd test Error: Aliases already exists: autopkgtest/ubuntu/jammy/amd64 autopkgtest [16:33:58]: test tests-in-lxd: ---] autopkgtest [16:33:58]: test tests-in-lxd: - - - - - - - - - - results - - - - - - - - - - tests-in-lxd FAIL non-zero exit status 1 Where the error seems to be triggered by debian/tests/tests-in-lxd lxc publish systemd-lxc --alias $IMAGE To be determined if this a problem in the autopkgtest infrastructure or test bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2023229/+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 2023301] [NEW] Please merge dbus 1.14.6-1 (main) from debian unstable (main)
Public bug reported: TODO ** Affects: dbus (Ubuntu) Importance: Undecided Assignee: Olivier Gayot (ogayot) Status: In Progress ** Changed in: dbus (Ubuntu) Assignee: (unassigned) => Olivier Gayot (ogayot) ** Changed in: dbus (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/2023301 Title: Please merge dbus 1.14.6-1 (main) from debian unstable (main) Status in dbus package in Ubuntu: In Progress Bug description: TODO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/2023301/+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 2016908] Re: udev fails to make prctl() syscall with apparmor=0 (as used by maas by default)
My understanding is that nothing needs to be done for systemd. Please re-open if I am mistaken. ** Changed in: systemd (Ubuntu Lunar) Status: Confirmed => Invalid -- 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/2016908 Title: udev fails to make prctl() syscall with apparmor=0 (as used by maas by default) Status in AppArmor: New Status in MAAS: Fix Committed Status in maas-images: Invalid Status in apparmor package in Ubuntu: Confirmed Status in linux package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: Invalid Status in apparmor source package in Lunar: Confirmed Status in linux source package in Lunar: Fix Committed Status in systemd source package in Lunar: Invalid Bug description: I'm assuming the image being used for these deploys is 20230417 or 20230417.1 based on the fact that I saw a 6.2 kernel being used which I don't believe was part of the 20230319 serial. I don't have access to the maas server, so I can't directly check any log files. MAAS Version: 3.3.2 Here's where the serial log indicates it can't download the squashfs. The full log is attached as scobee-lunar-no-squashfs.log (there are some other console message intermixed): no search or nameservers found in /run/net-BOOTIF.conf /run/net-*.conf /run/net6 -*.conf :: root=squash:http://10.229.32.21:5248/images/ubuntu/arm64/ga-23.04/lunar/candi date/squa[ 206.804704] Btrfs loaded, crc32c=crc32c-generic, zoned=yes, fsverity =yes shfs :: mount_squash downloading http://10.229.32.21:5248/images/ubuntu/arm64/ga-23.0 4/lunar/candidate/squashfs to /root.tmp.img Connecting to 10.229.32.21:5248 (10.229.32.21:5248) wget: can't connect to remote host (10.229.32.21): Network is unreachable :: mount -t squashfs -o loop '/root.tmp.img' '/root.tmp' mount: mounting /root.tmp.img on /root.tmp failed: No such file or directory done. Still gathering logs and info and will update as I go. Kernel Bug / Apparmor reproducer $ wget https://images.maas.io/ephemeral-v3/candidate/lunar/amd64/20230419/ga-23.04/generic/boot-kernel $ wget https://images.maas.io/ephemeral-v3/candidate/lunar/amd64/20230419/ga-23.04/generic/boot-initrd $ qemu-system-x86_64 -nographic -m 2G -kernel ./boot-kernel -initrd ./boot-initrd -append 'console=ttyS0 break=modules apparmor=0' #start the VM Starting systemd-udevd version 252.5-2ubuntu3 Spawning shell within the initramfs BusyBox v1.35.0 (Ubuntu 1:1.35.0-4ubuntu1) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) udevadm info --export-db Failed to set death signal: Invalid argument Observe that udevadm fails to setup death signal, with in systemd code is this https://github.com/systemd/systemd/blob/08c2f9c626e0f0052d505b1b7e52f335c0fbfa1d/src/basic/process- util.c#L1252 if (flags & (FORK_DEATHSIG|FORK_DEATHSIG_SIGINT)) if (prctl(PR_SET_PDEATHSIG, (flags & FORK_DEATHSIG_SIGINT) ? SIGINT : SIGTERM) < 0) { log_full_errno(prio, errno, "Failed to set death signal: %m"); _exit(EXIT_FAILURE); } workaround set kernel commandline to `apparmor=1` MAAS bug Why is maas setting `apparmor=0` ? Ubuntu shouldn't be used without apparmor. Even for deployment and commisioning. To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/2016908/+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 2023229] Re: Autopkgtest failure for tests-in-lxd
Could you please provide some relevant output from the tests-in-lxd failure, or better yet a link to a test log? -- 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/2023229 Title: Autopkgtest failure for tests-in-lxd Status in systemd package in Ubuntu: Incomplete Status in systemd source package in Jammy: New Bug description: Autopackagetests on multiple Jammy kernels show the same failure on the test-in-lxd test Error: Aliases already exists: autopkgtest/ubuntu/jammy/amd64 autopkgtest [16:33:58]: test tests-in-lxd: ---] autopkgtest [16:33:58]: test tests-in-lxd: - - - - - - - - - - results - - - - - - - - - - tests-in-lxd FAIL non-zero exit status 1 Where the error seems to be triggered by debian/tests/tests-in-lxd lxc publish systemd-lxc --alias $IMAGE To be determined if this a problem in the autopkgtest infrastructure or test bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2023229/+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 2009859] Re: systemd: networkd-test.py fails with newer kinetic kernels
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu Kinetic) Status: New => Confirmed -- 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/2009859 Title: systemd: networkd-test.py fails with newer kinetic kernels Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Status in linux source package in Kinetic: Confirmed Status in systemd source package in Kinetic: Confirmed Bug description: systemd autopkgtests are failing in kinetic, and they are not considered regressions. The failing test is one within networkd- test.py: == ERROR: test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest) resolved: domain-restricted DNS servers -- Traceback (most recent call last): File "/tmp/autopkgtest.wTrLDQ/build.Oa5/src/test/networkd-test.py", line 680, in test_resolved_domain_restricted_dns out = subprocess.check_output(['resolvectl', 'query', 'math.lab']) File "/usr/lib/python3.10/subprocess.py", line 420, in check_output return run(*popenargs, stdout=PIPE, timeout=timeout, check=True, File "/usr/lib/python3.10/subprocess.py", line 524, in run raise CalledProcessError(retcode, process.args, subprocess.CalledProcessError: Command '['resolvectl', 'query', 'math.lab']' returned non-zero exit status 1. -- Ran 35 tests in 161.770s FAILED (errors=1, skipped=2) The failures started without any changes to the systemd package, i.e. it was caused by another package upload. In particular, the failures started around 2022-11-17 with linux 5.19.0-24.25. The tests pass fine with linux 5.19.0-21.21, i.e. the version in kinetic-release. This can be demonstrated locally with autopkgtest: $ autopkgtest --shell-fail systemd --test-name networkd-test.py --pin- packages=kinetic=src:linux --setup-commands 'apt update' -- qemu /home/nr/ubuntu/autopkgtest-testbeds/autopkgtest-kinetic-amd64.img Note in the above command I did not pass -U, so no packages in the test bed are upgraded. But, with: $ autopkgtest --shell-fail systemd --test-name networkd-test.py -U -- qemu /home/nr/ubuntu/autopkgtest-testbeds/autopkgtest-kinetic- amd64.img the kernel is upgraded, and the test fails. This can also be done manually by grabbing the systemd source on a kinetic machine (e.g. pull-lp-source systemd kinetic), and running: $ sudo python3 test/networkd-test.py DnsmasqClientTest.test_resolved_domain_restricted_dns The attached journal.txt shows systemd-resolved logs from when the test is run. The failure is caused by the EHOSTUNREACH when trying to resolve math.lab. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 9 11:56 seq crw-rw 1 root audio 116, 33 Mar 9 11:56 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.10 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 bochs-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic root=UUID=7f0aa1bf-59bd-4d77-b092-7244f86e5566 ro console=tty0 console=hvc0 console=ttyS0 ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-35-generic N/A linux-backports-modules-5.19.0-35-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.4 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: kinetic Uname: Linux 5.19.0-35-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.16.0-debian-1.16.0-4 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-kinetic dmi.modalias:
[Touch-packages] [Bug 2023180] Re: Autopkgtest failure for kinetic kernels
*** This bug is a duplicate of bug 2009859 *** https://bugs.launchpad.net/bugs/2009859 I believe this is a duplicate of bug 2009859, so I am marking it as such. ** This bug has been marked a duplicate of bug 2009859 systemd: networkd-test.py fails with newer kinetic kernels -- 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/2023180 Title: Autopkgtest failure for kinetic kernels Status in systemd package in Ubuntu: Incomplete Status in systemd source package in Kinetic: New Bug description: autopkgtest [10:10:45]: test networkd-test.py: [--- systemd-network:x:100:102:systemd Network Management,,,:/run/systemd:/usr/sbin/nologin test_bridge_init (__main__.BridgeTest) ... ok test_bridge_port_priority (__main__.BridgeTest) ... ok test_bridge_port_priority_set_zero (__main__.BridgeTest) It should be possible to set the bridge port priority to 0 ... ok test_bridge_port_property (__main__.BridgeTest) Test the "[Bridge]" section keys ... ok test_coldplug_dhcp_ip4_only (__main__.DnsmasqClientTest) ... ok test_coldplug_dhcp_ip4_only_no_ra (__main__.DnsmasqClientTest) ... ok test_coldplug_dhcp_ip6 (__main__.DnsmasqClientTest) ... ok test_coldplug_dhcp_yes_ip4 (__main__.DnsmasqClientTest) ... ok test_coldplug_dhcp_yes_ip4_no_ra (__main__.DnsmasqClientTest) ... ok test_hotplug_dhcp_ip4 (__main__.DnsmasqClientTest) ... ok test_hotplug_dhcp_ip6 (__main__.DnsmasqClientTest) ... ok test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest) resolved: domain-restricted DNS servers ... ERROR test_resolved_etc_hosts (__main__.DnsmasqClientTest) resolved queries to /etc/hosts ... ok test_route_only_dns (__main__.DnsmasqClientTest) ... ok test_route_only_dns_all_domains (__main__.DnsmasqClientTest) ... ok test_transient_hostname (__main__.DnsmasqClientTest) networkd sets transient hostname from DHCP ... ok test_transient_hostname_with_static (__main__.DnsmasqClientTest) transient hostname is not applied if static hostname exists ... ok test_basic_matching (__main__.MatchClientTest) Verify the Name= line works throughout this class. ... ok test_inverted_matching (__main__.MatchClientTest) Verify that a '!'-prefixed value inverts the match. ... ok test_coldplug_dhcp_ip4_only (__main__.NetworkdClientTest) ... ok test_coldplug_dhcp_ip4_only_no_ra (__main__.NetworkdClientTest) ... ok test_coldplug_dhcp_ip6 (__main__.NetworkdClientTest) ... skipped 'networkd does not have DHCPv6 server support' test_coldplug_dhcp_yes_ip4 (__main__.NetworkdClientTest) ... ok test_coldplug_dhcp_yes_ip4_no_ra (__main__.NetworkdClientTest) ... ok test_dhcp_timezone (__main__.NetworkdClientTest) networkd sets time zone from DHCP ... ok test_dropin (__main__.NetworkdClientTest) ... ok test_hotplug_dhcp_ip4 (__main__.NetworkdClientTest) ... ok test_hotplug_dhcp_ip6 (__main__.NetworkdClientTest) ... skipped 'networkd does not have DHCPv6 server support' test_route_only_dns (__main__.NetworkdClientTest) ... ok test_route_only_dns_all_domains (__main__.NetworkdClientTest) ... ok test_search_domains (__main__.NetworkdClientTest) ... ok test_catchall_config (__main__.UnmanagedClientTest) Verify link states with a catch-all config, hot-plug. ... ok test_catchall_config_coldplug (__main__.UnmanagedClientTest) Verify link states with a catch-all config, cold-plug. ... ok test_unmanaged_setting (__main__.UnmanagedClientTest) Verify link states with Unmanaged= settings, hot-plug. ... ok test_unmanaged_setting_coldplug (__main__.UnmanagedClientTest) Verify link states with Unmanaged= settings, cold-plug. ... ok == ERROR: test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest) resolved: domain-restricted DNS servers -- Traceback (most recent call last): File "/tmp/autopkgtest.W3rkSo/build.Vi6/src/test/networkd-test.py", line 680, in test_resolved_domain_restricted_dns out = subprocess.check_output(['resolvectl', 'query', 'math.lab']) File "/usr/lib/python3.10/subprocess.py", line 420, in check_output return run(*popenargs, stdout=PIPE, timeout=timeout, check=True, File "/usr/lib/python3.10/subprocess.py", line 524, in run raise CalledProcessError(retcode, process.args, subprocess.CalledProcessError: Command '['resolvectl', 'query', 'math.lab']' returned non-zero exit status 1. -- Ran 35 tests in 158.633s FAILED (errors=1, skipped=2) autopkgtest [10:13:25]: test networkd-test.py: ---] autopkgtest [10:13:25]: test networkd-test.py: - - - - - - - - - - results - - - - - - - - - - networkd-test.py FAIL non-zero exit
[Touch-packages] [Bug 1939537] Re: Tests in ubuntu_lxc failed with "ERROR: Couldn't find a matching image." on X-hwe and older releases
All done, updated states and dropped sponsors subscribers ** Changed in: lxc (Ubuntu) Status: Confirmed => Invalid ** Changed in: ubuntu-kernel-tests Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1939537 Title: Tests in ubuntu_lxc failed with "ERROR: Couldn't find a matching image." on X-hwe and older releases Status in ubuntu-kernel-tests: Fix Released Status in lxc package in Ubuntu: Invalid Status in lxc source package in Bionic: Fix Released Bug description: [ Impact ] * The following tests fail as they try to use inexistent LXC images: * lxc-test-apparmor-mount * lxc-test-autostart * lxc-test-unpriv * lxc-test-usernic * Having them fixed for the affected series (for example, Bionic) will allow us to run the LXC test suite without maintaining local changes for these tests. [ Test Plan ] * Run the affected tests on an affected series (e.g. Bionic). * The tests should pass. [ Where problems could occur ] * The regression risk is very low and the changes only affect the tests so the regression scope is minimal. [Other info] Original bug report: Issue found on node onibi 4.15.0-142-generic #146~16.04.1 With bug 1916087 resolved, the following tests: * lxc-test-apparmor-mount * lxc-test-autostart * lxc-test-unpriv * lxc-test-usernic Are now failing with: ERROR: Couldn't find a matching image. This is because with lxc version 2.0.11-0ubuntu1~16.04.3 the default target release is "trusty" or the system release if supported. It will be checked with: ubuntu-distro-info --supported However Xenial is an ESM series now, it won't use xenial as the target release but use trusty instead. The attempt to download trusty image will fail with this error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1939537/+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 1939537] Re: Tests in ubuntu_lxc failed with "ERROR: Couldn't find a matching image." on X-hwe and older releases
Is there anything left to do on this bug? Any further series to target for lxc, and/or anything to do with the ubuntu-kernel-tests? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1939537 Title: Tests in ubuntu_lxc failed with "ERROR: Couldn't find a matching image." on X-hwe and older releases Status in ubuntu-kernel-tests: New Status in lxc package in Ubuntu: Confirmed Status in lxc source package in Bionic: Fix Released Bug description: [ Impact ] * The following tests fail as they try to use inexistent LXC images: * lxc-test-apparmor-mount * lxc-test-autostart * lxc-test-unpriv * lxc-test-usernic * Having them fixed for the affected series (for example, Bionic) will allow us to run the LXC test suite without maintaining local changes for these tests. [ Test Plan ] * Run the affected tests on an affected series (e.g. Bionic). * The tests should pass. [ Where problems could occur ] * The regression risk is very low and the changes only affect the tests so the regression scope is minimal. [Other info] Original bug report: Issue found on node onibi 4.15.0-142-generic #146~16.04.1 With bug 1916087 resolved, the following tests: * lxc-test-apparmor-mount * lxc-test-autostart * lxc-test-unpriv * lxc-test-usernic Are now failing with: ERROR: Couldn't find a matching image. This is because with lxc version 2.0.11-0ubuntu1~16.04.3 the default target release is "trusty" or the system release if supported. It will be checked with: ubuntu-distro-info --supported However Xenial is an ESM series now, it won't use xenial as the target release but use trusty instead. The attempt to download trusty image will fail with this error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1939537/+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 2023289] [NEW] System permanent freeze via running Qt5 QML + .mesh project on Ubuntu 22.04
Public bug reported: I'm trying to launch Qt5 project with QML UI with .mesh 3D objects. This project works normally on old, grand-daddy's laptop Asus X555D, with Radeon R6 M340DX 2GB graphics, 8GB RAM and AMD A10 6th gen. But when i try to launch this project on the same Ubuntu version, on my other laptop (it's specs are listed below), i have absolute blacked out window instead of application and system freeze for about 1 minute with project (sometimes even QTCreator) crash. Here is my troubled Asus's specs: Laptop: ASUSTeK VivoBook 15 X513EAN_K513EA Graphics: Mesa Intel® Xe Graphics (TGL GT2) CPU: 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz × 8 RAM: 16,0 GB OS: Ubuntu 22.04.2 LTS, 64 bit Gnome: 42.5 Display server: x11 OpenGl ver: 4.6 (Compatibility Profile) Mesa 22.2.5 I've tried to update xinerama's libs, checked missing libs, tried to update OpenGL, tried this method but for 22.04 and, to be honest, i've lost the count of solutions that i've tried. I will be grateful for any help with information. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.1.0-1013.13-oem 6.1.25 Uname: Linux 6.1.0-1013-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jun 8 14:49:52 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. TigerLake-LP GT2 [Iris Xe Graphics] [1043:1c22] InstallationDate: Installed on 2023-04-19 (50 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0408:30d4 Quanta Computer, Inc. USB2.0 HD UVC WebCam Bus 001 Device 002: ID 09da:2403 A4Tech Co., Ltd. 2.4G Device Bus 001 Device 004: ID 8087:0026 Intel Corp. AX201 Bluetooth Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X513EAN_K513EA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.1.0-1013-oem root=UUID=9fdae802-1912-4c11-b382-7a593209ef38 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2022 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: X513EAN.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X513EAN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrX513EAN.302:bd04/21/2022:br5.19:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX513EAN_K513EA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX513EAN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: VivoBook dmi.product.name: VivoBook_ASUSLaptop X513EAN_K513EA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.115+git2305120500.98e1db~oibaf~j version.libgl1-mesa-dri: libgl1-mesa-dri 23.2~git2306080600.96cf45~oibaf~j version.libgl1-mesa-glx: libgl1-mesa-glx 23.2~git2306080600.96cf45~oibaf~j version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.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-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2023289 Title: System permanent freeze via running Qt5 QML + .mesh project on Ubuntu 22.04 Status in xorg package in Ubuntu: New Bug description: I'm trying to launch Qt5 project with QML UI with .mesh 3D objects. This project works normally on old, grand-daddy's laptop Asus X555D, with Radeon R6 M340DX 2GB graphics, 8GB RAM and AMD A10 6th gen. But when i try to launch this project on the same Ubuntu version, on my other laptop (it's specs are listed below), i have absolute blacked out window instead of application and system freeze for about 1 minute with project (sometimes even QTCreator) crash. Here is my troubled Asus's specs: Laptop: ASUSTeK VivoBook 15 X513EAN_K513EA
[Touch-packages] [Bug 2023282] [NEW] The module visible providers take 1min, but the UI shows a timeout in the 30s
Public bug reported: 1.Environment Image: pc-stella-jammy-amd64-20230215-269 modem:FM350-GL-02-08 Test SIM Card: Unicom Module IMEI: 863714050025511 NetworkManager:1.36.6 2. Test Steps 1). Insert the SIM card 2). Boot into system 3). Open System Setting->Mobile Network 4). Disable Mobile Data 5). Click Network 6). Disable Automatic 3. Expected Result show visible providers success 4. Actual Result show visible providers timeout I wonder if visible providers on the UI can be adjusted to 90s? Ensure that the success of visible providers is displayed ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- 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/2023282 Title: The module visible providers take 1min, but the UI shows a timeout in the 30s Status in network-manager package in Ubuntu: New Bug description: 1.Environment Image: pc-stella-jammy-amd64-20230215-269 modem:FM350-GL-02-08 Test SIM Card: Unicom Module IMEI: 863714050025511 NetworkManager:1.36.6 2. Test Steps 1). Insert the SIM card 2). Boot into system 3). Open System Setting->Mobile Network 4). Disable Mobile Data 5). Click Network 6). Disable Automatic 3. Expected Result show visible providers success 4. Actual Result show visible providers timeout I wonder if visible providers on the UI can be adjusted to 90s? Ensure that the success of visible providers is displayed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2023282/+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 2015355] Re: Please backport patches for false atari partition detection to Ubuntu 20.04
Thanks for completing the backport, rolling out the proposed .deb now and will comment again once I've confirmed the fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/2015355 Title: Please backport patches for false atari partition detection to Ubuntu 20.04 Status in util-linux package in Ubuntu: Fix Released Status in util-linux source package in Focal: Fix Committed Bug description: [Impact] The partition detection logic in libblkid1 can falsely report the presence of an atari partition. One place where this has a practical impact is in kubernetes where mount-utils will refuse to format the device (https://github.com/kubernetes/mount- utils/blob/732a08ae47571516020ef99c303c70c1fa5b3e6c/mount_linux.go#L437-L441). [Test Plan] * Create a new qcow2 disk image: $ qemu-img create -f qcow2 test.img 20G * Boot a focal ISO with QEMU/KVM as if installing to test.img: $ qemu-system-x86_64 -enable-kvm -m 4096 -name test -drive file=test.img,format=qcow2 -net nic,model=virtio -net user,hostfwd=tcp::1022-:22 -vga virtio -cdrom ubuntu-20.04.6-desktop- amd64.iso * Using the live environment, format the empty disk. These particular commands were given as a reproducer on the upstream bug report (https://github.com/util-linux/util-linux/issues/1116). $ parted -s /dev/sda -- mklabel msdos $ parted -s /dev/sda -- mkpart primary 0% 10% mkpart primary 10% 30% * Run wipefs on /dev/sda to list partitions. On an affected machine, an atari partition will be listed. On a fixed machine, the incorrect atari listing will be gone. $ wipefs /dev/sda DEVICE OFFSET TYPE UUID LABEL sda0x1fe dos sda0x1d2 atari [Where problems could occur] These patches specifically address the atari prober logic in libblkid. Therefore, if we saw regressions it would be related to detecting atari partitions with libblkid. This would potentially impact tools such as wipefs and blkid, or any other tool that uses libblkid1 for this purpose. [Original Description] There are three patches in util-linux upstream that were released in util-linux 2.37 and prevent false detection of the atari partition table with blkid and wipefs. We see this mostly on LUKS devices initialised via luksFormat reporting there is an atari partition table on the device when it is empty. This causes issues in various places, but one key example for us is in kubernetes where mount-utils will refuse to format the device (https://github.com/kubernetes/mount- utils/blob/732a08ae47571516020ef99c303c70c1fa5b3e6c/mount_linux.go#L437-L441) RedHat backported these fixes to RHEL 8 under https://bugzilla.redhat.com/show_bug.cgi?id=2060030 and it would be helpful if Ubuntu also backported them to Ubuntu 20.04 which is still running util-linux 2.34 The request is to backport patches based on the https://github.com/util-linux/util-linux/issues/1159 upstream report. Upstream commits to cherry-pick the changes to libblkid/src/partitions/atari.c from: 2cc76d50d7a14bef8e7b07fab11b26c9e49d36a2 282ceadc3a72fc07dd0388b8880fd751490bb87f c70b4f2a5b99876d230b8f4f413c3bb3ee6647f1 # lsb_release -a Distributor ID: Ubuntu Description:Ubuntu 20.04.6 LTS Release:20.04 Codename: focal # blkid -V blkid from util-linux 2.34 (libblkid 2.34.0, 14-Jun-2019) # blkid -p -s TYPE -s PTTYPE -o export /dev/mapper/pvc-7b331195-cd5a-4ab6-8fdc-552af4b9139d_encrypted DEVNAME=dev/mapper/pvc-7b331195-cd5a-4ab6-8fdc-552af4b9139d_encrypted PTTYPE=atari # lsblk ... sdccrypto_LUKS a79d2982-74f2-44c7-bb29-460768ebfe64 `-3600a09803830474a735d4c63744c4a56crypto_LUKS a79d2982-74f2-44c7-bb29-460768ebfe64 `-pvc-7b331195-cd5a-4ab6-8fdc-552af4b9139d_encrypted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/2015355/+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 1989731] Re: Non-root user unable to change own password if pam_pwhistory is used
This is now released with usg 20.04.17 ** Changed in: usg Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1989731 Title: Non-root user unable to change own password if pam_pwhistory is used Status in Ubuntu Security Guide: Fix Released Status in pam package in Ubuntu: In Progress Bug description: When pam_pwhistory is in use non-root users are unable to change their passwords. In fact, they are able to change it but the system spits out an error even though the password was indeed changed. Reproducer: --- 1. created an Ubuntu/Focal VM 2. added a user 'test' sudo adduser test # used passwd '123' su test 3. changed the password using 'passwd' logged in as the user 'test' passwd test # used passwd '1qaz2wsx' 4. logged out from 'test' and executed echo 'password required pam_pwhistory.so remember=5' | sudo tee -a /etc/pam.d/common-password 5. tried again to follow step 3 as user 'test' but the following happens: passwd test # used passwd '3edc4rfv' (1) Changing password for test. Current password: New password: Retype new password: Password has been already used. Choose another. passwd: Have exhausted maximum number of retries for service passwd: password unchanged However, I'm now able to log in as 'test' using the password in (1) (the one that was supposedly not set up due to having been already used) instead of the old one (the one that should be in place since the change process returned an error). 6. if I comment out 'password required pam_pwhistory.so remember=5' then I can log in as 'test' and change the password without issues This behavior has been verified with the below package versioning: ii libpam-cap:amd641:2.32-1 amd64POSIX 1003.1e capabilities (PAM module) ii libpam-modules:amd641.3.1-5ubuntu4.3 amd64Pluggable Authentication Modules for PAM ii libpam-modules-bin 1.3.1-5ubuntu4.3 amd64Pluggable Authentication Modules for PAM - helper binaries ii libpam-runtime 1.3.1-5ubuntu4.3 all Runtime support for the PAM library ii libpam-systemd:amd64245.4-4ubuntu3.15 amd64system and service manager - PAM module ii libpam0g:amd64 1.3.1-5ubuntu4.3 amd64Pluggable Authentication Modules library To manage notifications about this bug go to: https://bugs.launchpad.net/usg/+bug/1989731/+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 2009859] Re: systemd: networkd-test.py fails with newer kinetic kernels
I have hit this bug in the ADT testing part of the linux-aws 5.19.0-1027.28 release: https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic/kinetic/amd64/s/systemd/20230525_124201_d6c4e@/log.gz https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic/kinetic/arm64/s/systemd/20230525_134055_652ab@/log.gz ** Tags added: sru-20230515 -- 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/2009859 Title: systemd: networkd-test.py fails with newer kinetic kernels Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Status in linux source package in Kinetic: Confirmed Status in systemd source package in Kinetic: New Bug description: systemd autopkgtests are failing in kinetic, and they are not considered regressions. The failing test is one within networkd- test.py: == ERROR: test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest) resolved: domain-restricted DNS servers -- Traceback (most recent call last): File "/tmp/autopkgtest.wTrLDQ/build.Oa5/src/test/networkd-test.py", line 680, in test_resolved_domain_restricted_dns out = subprocess.check_output(['resolvectl', 'query', 'math.lab']) File "/usr/lib/python3.10/subprocess.py", line 420, in check_output return run(*popenargs, stdout=PIPE, timeout=timeout, check=True, File "/usr/lib/python3.10/subprocess.py", line 524, in run raise CalledProcessError(retcode, process.args, subprocess.CalledProcessError: Command '['resolvectl', 'query', 'math.lab']' returned non-zero exit status 1. -- Ran 35 tests in 161.770s FAILED (errors=1, skipped=2) The failures started without any changes to the systemd package, i.e. it was caused by another package upload. In particular, the failures started around 2022-11-17 with linux 5.19.0-24.25. The tests pass fine with linux 5.19.0-21.21, i.e. the version in kinetic-release. This can be demonstrated locally with autopkgtest: $ autopkgtest --shell-fail systemd --test-name networkd-test.py --pin- packages=kinetic=src:linux --setup-commands 'apt update' -- qemu /home/nr/ubuntu/autopkgtest-testbeds/autopkgtest-kinetic-amd64.img Note in the above command I did not pass -U, so no packages in the test bed are upgraded. But, with: $ autopkgtest --shell-fail systemd --test-name networkd-test.py -U -- qemu /home/nr/ubuntu/autopkgtest-testbeds/autopkgtest-kinetic- amd64.img the kernel is upgraded, and the test fails. This can also be done manually by grabbing the systemd source on a kinetic machine (e.g. pull-lp-source systemd kinetic), and running: $ sudo python3 test/networkd-test.py DnsmasqClientTest.test_resolved_domain_restricted_dns The attached journal.txt shows systemd-resolved logs from when the test is run. The failure is caused by the EHOSTUNREACH when trying to resolve math.lab. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 9 11:56 seq crw-rw 1 root audio 116, 33 Mar 9 11:56 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.10 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 bochs-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic root=UUID=7f0aa1bf-59bd-4d77-b092-7244f86e5566 ro console=tty0 console=hvc0 console=ttyS0 ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-35-generic N/A linux-backports-modules-5.19.0-35-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.4 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: kinetic Uname: Linux 5.19.0-35-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.16.0-debian-1.16.0-4 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU
[Touch-packages] [Bug 2023266] [NEW] Please re-add [pm]mnormalize
Public bug reported: The Debian packaging contains these lines: https://salsa.debian.org/debian/rsyslog/-/blob/debian/master/debian/rules#L43 --enable-pmnormalize \ --enable-mmnormalize \ AFAIK these were removed because liblognorm was in universe: - Drop [mm|pm]normalize modules, depending on liblognorm from universe. + d/rules: drop --enable-mmnormalize & --enable-pmnormalize + d/control: drop build dependency on liblognorm-dev -- Steve Langasek Wed, 29 Dec 2021 17:15:17 -0800 But later on liblognorm was re-added: * Re-add build-dependency on liblognorm-dev, also needed for rsyslog-kubernetes. -- Steve Langasek Thu, 30 Dec 2021 07:22:05 + So these very useful modules are now excluded from the build for no reason. Please re-enable them as they're needed in order to receive logs from switches that send non-standard dates, for example: https://github.com/rsyslog/rsyslog/issues/5148#issuecomment-1568687769 ** Affects: rsyslog (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/2023266 Title: Please re-add [pm]mnormalize Status in rsyslog package in Ubuntu: New Bug description: The Debian packaging contains these lines: https://salsa.debian.org/debian/rsyslog/-/blob/debian/master/debian/rules#L43 --enable-pmnormalize \ --enable-mmnormalize \ AFAIK these were removed because liblognorm was in universe: - Drop [mm|pm]normalize modules, depending on liblognorm from universe. + d/rules: drop --enable-mmnormalize & --enable-pmnormalize + d/control: drop build dependency on liblognorm-dev -- Steve Langasek Wed, 29 Dec 2021 17:15:17 -0800 But later on liblognorm was re-added: * Re-add build-dependency on liblognorm-dev, also needed for rsyslog-kubernetes. -- Steve Langasek Thu, 30 Dec 2021 07:22:05 + So these very useful modules are now excluded from the build for no reason. Please re-enable them as they're needed in order to receive logs from switches that send non-standard dates, for example: https://github.com/rsyslog/rsyslog/issues/5148#issuecomment-1568687769 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/2023266/+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 2023180] Re: Autopkgtest failure for kinetic kernels
** Description changed: autopkgtest [10:10:45]: test networkd-test.py: [--- systemd-network:x:100:102:systemd Network Management,,,:/run/systemd:/usr/sbin/nologin test_bridge_init (__main__.BridgeTest) ... ok test_bridge_port_priority (__main__.BridgeTest) ... ok test_bridge_port_priority_set_zero (__main__.BridgeTest) It should be possible to set the bridge port priority to 0 ... ok test_bridge_port_property (__main__.BridgeTest) Test the "[Bridge]" section keys ... ok test_coldplug_dhcp_ip4_only (__main__.DnsmasqClientTest) ... ok test_coldplug_dhcp_ip4_only_no_ra (__main__.DnsmasqClientTest) ... ok test_coldplug_dhcp_ip6 (__main__.DnsmasqClientTest) ... ok test_coldplug_dhcp_yes_ip4 (__main__.DnsmasqClientTest) ... ok test_coldplug_dhcp_yes_ip4_no_ra (__main__.DnsmasqClientTest) ... ok test_hotplug_dhcp_ip4 (__main__.DnsmasqClientTest) ... ok test_hotplug_dhcp_ip6 (__main__.DnsmasqClientTest) ... ok test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest) resolved: domain-restricted DNS servers ... ERROR test_resolved_etc_hosts (__main__.DnsmasqClientTest) resolved queries to /etc/hosts ... ok test_route_only_dns (__main__.DnsmasqClientTest) ... ok test_route_only_dns_all_domains (__main__.DnsmasqClientTest) ... ok test_transient_hostname (__main__.DnsmasqClientTest) networkd sets transient hostname from DHCP ... ok test_transient_hostname_with_static (__main__.DnsmasqClientTest) transient hostname is not applied if static hostname exists ... ok test_basic_matching (__main__.MatchClientTest) Verify the Name= line works throughout this class. ... ok test_inverted_matching (__main__.MatchClientTest) Verify that a '!'-prefixed value inverts the match. ... ok test_coldplug_dhcp_ip4_only (__main__.NetworkdClientTest) ... ok test_coldplug_dhcp_ip4_only_no_ra (__main__.NetworkdClientTest) ... ok test_coldplug_dhcp_ip6 (__main__.NetworkdClientTest) ... skipped 'networkd does not have DHCPv6 server support' test_coldplug_dhcp_yes_ip4 (__main__.NetworkdClientTest) ... ok test_coldplug_dhcp_yes_ip4_no_ra (__main__.NetworkdClientTest) ... ok test_dhcp_timezone (__main__.NetworkdClientTest) networkd sets time zone from DHCP ... ok test_dropin (__main__.NetworkdClientTest) ... ok test_hotplug_dhcp_ip4 (__main__.NetworkdClientTest) ... ok test_hotplug_dhcp_ip6 (__main__.NetworkdClientTest) ... skipped 'networkd does not have DHCPv6 server support' test_route_only_dns (__main__.NetworkdClientTest) ... ok test_route_only_dns_all_domains (__main__.NetworkdClientTest) ... ok test_search_domains (__main__.NetworkdClientTest) ... ok test_catchall_config (__main__.UnmanagedClientTest) Verify link states with a catch-all config, hot-plug. ... ok test_catchall_config_coldplug (__main__.UnmanagedClientTest) Verify link states with a catch-all config, cold-plug. ... ok test_unmanaged_setting (__main__.UnmanagedClientTest) Verify link states with Unmanaged= settings, hot-plug. ... ok test_unmanaged_setting_coldplug (__main__.UnmanagedClientTest) Verify link states with Unmanaged= settings, cold-plug. ... ok == ERROR: test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest) resolved: domain-restricted DNS servers -- Traceback (most recent call last): File "/tmp/autopkgtest.W3rkSo/build.Vi6/src/test/networkd-test.py", line 680, in test_resolved_domain_restricted_dns out = subprocess.check_output(['resolvectl', 'query', 'math.lab']) File "/usr/lib/python3.10/subprocess.py", line 420, in check_output return run(*popenargs, stdout=PIPE, timeout=timeout, check=True, File "/usr/lib/python3.10/subprocess.py", line 524, in run raise CalledProcessError(retcode, process.args, subprocess.CalledProcessError: Command '['resolvectl', 'query', 'math.lab']' returned non-zero exit status 1. -- Ran 35 tests in 158.633s FAILED (errors=1, skipped=2) autopkgtest [10:13:25]: test networkd-test.py: ---] autopkgtest [10:13:25]: test networkd-test.py: - - - - - - - - - - results - - - - - - - - - - networkd-test.py FAIL non-zero exit status 1 To be determined if the issue is in the package or linux kernel + + --- + External link: https://warthogs.atlassian.net/browse/PEL-424 -- 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/2023180 Title: Autopkgtest failure for kinetic kernels Status in systemd package in Ubuntu: Incomplete Status in systemd source package in Kinetic: New Bug description: autopkgtest [10:10:45]: test networkd-test.py: [---