[Touch-packages] [Bug 1870213] Re: "Switching to another layout" shortcut was not set by oem-config for end-user
** Tags added: hirsute -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1870213 Title: "Switching to another layout" shortcut was not set by oem-config for end-user Status in console-setup package in Ubuntu: New Status in oem-config package in Ubuntu: New Status in ubiquity package in Ubuntu: New Bug description: Steps to reproduce: 1. Launch Ubuntu MATE 20.04 LTS installer in OEM mode 2. Confirm using English locale 3. While setting OS for end user specify Russian language, confirm system configuration 4. Login to the configured system Expected result: * the keyboard layout switcher shows two layouts - *en* and *ru*, reacts on + hotkey Actual result: * the keyboard layout switcher shows two layouts - *en* and *ru*, but does not react on + hotkey Note: the contents of keyboard configuration files is the following: ``` $ cat /etc/default/keyboard # KEYBOARD CONFIGURATION FILE # Consult the keyboard(5) manual page. XKBMODEL="pc105" XKBLAYOUT="us,ru" XKBVARIANT="," XKBOPTIONS="grp_led:scroll" BACKSPACE="guess" ``` so keyboard layout switcher is not defined here. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: keyboard-configuration 1.194ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: MATE Date: Thu Apr 2 00:43:16 2020 InstallationDate: Installed on 2020-04-01 (0 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) PackageArchitecture: all SourcePackage: console-setup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1870213/+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 1922331] Re: Gdebi quitting on installing deb files
Please run apport-collect 1922331 and specify steps to reproduce. Do you use Firefox do download these deb-files? ** Tags added: hirsute ** Also affects: gdebi (Ubuntu) Importance: Undecided Status: New -- 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/1922331 Title: Gdebi quitting on installing deb files Status in Ubuntu MATE: New Status in gdebi package in Ubuntu: New Bug description: Gdebi quitting on installing .deb files. Double clicking on a .deb file caused gdebi to open and check the file for installation. Then when you click on install the program terminates. Have tried it on multiple .deb files and it does the same thing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1922331/+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 1922340] Re: GNOME lock screen wallpaper turns black on main display
** Also affects: wayland (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1922340 Title: GNOME lock screen wallpaper turns black on main display Status in gnome-shell package in Ubuntu: New Status in wayland package in Ubuntu: New Bug description: 1) Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 2) gnome-shell: Installed: 3.38.4-1ubuntu1 Candidate: 3.38.4-1ubuntu1 Version table: *** 3.38.4-1ubuntu1 500 500 http://pl.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status 3) This bug only appears on Gnome with Wayland. It does not affect Gnome on xorg. After the screen stays off and locked for some time the wallpaper on the main display turns black. It never happens on the secondary display. The issue is also reported, here on gitlab: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3206 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 2 11:50:15 2021 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-04-02 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1922340/+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 1922331] Re: Gdebi quitting on installing deb files
apport information ** Tags added: apport-collected ** Description changed: Gdebi quitting on installing .deb files. Double clicking on a .deb file caused gdebi to open and check the file for installation. Then when you click on install the program terminates. Have tried it on multiple .deb files and it does the same thing. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu61 + Architecture: amd64 + CurrentDesktop: MATE + DistroRelease: Ubuntu 21.04 + InstallationDate: Installed on 2021-04-02 (0 days ago) + InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Beta amd64 (20210331.1) + NonfreeKernelModules: nvidia_modeset nvidia + Package: gdebi 0.9.5.7+nmu4 + PackageArchitecture: all + ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 + Tags: hirsute + Uname: Linux 5.11.0-13-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1922331/+attachment/5483385/+files/Dependencies.txt -- 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/1922331 Title: Gdebi quitting on installing deb files Status in Ubuntu MATE: New Status in gdebi package in Ubuntu: New Bug description: Gdebi quitting on installing .deb files. Double clicking on a .deb file caused gdebi to open and check the file for installation. Then when you click on install the program terminates. Have tried it on multiple .deb files and it does the same thing. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CurrentDesktop: MATE DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-02 (0 days ago) InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Beta amd64 (20210331.1) NonfreeKernelModules: nvidia_modeset nvidia Package: gdebi 0.9.5.7+nmu4 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Tags: hirsute Uname: Linux 5.11.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1922331/+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 1922331] HookError_ubuntu.txt
apport information ** Attachment added: "HookError_ubuntu.txt" https://bugs.launchpad.net/bugs/1922331/+attachment/5483386/+files/HookError_ubuntu.txt -- 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/1922331 Title: Gdebi quitting on installing deb files Status in Ubuntu MATE: New Status in gdebi package in Ubuntu: New Bug description: Gdebi quitting on installing .deb files. Double clicking on a .deb file caused gdebi to open and check the file for installation. Then when you click on install the program terminates. Have tried it on multiple .deb files and it does the same thing. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CurrentDesktop: MATE DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-02 (0 days ago) InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Beta amd64 (20210331.1) NonfreeKernelModules: nvidia_modeset nvidia Package: gdebi 0.9.5.7+nmu4 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Tags: hirsute Uname: Linux 5.11.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1922331/+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 1922331] Re: Gdebi quitting on installing deb files
Yes I do use Firefox to download .deb files. I also used Chrome as well -- 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/1922331 Title: Gdebi quitting on installing deb files Status in Ubuntu MATE: New Status in gdebi package in Ubuntu: New Bug description: Gdebi quitting on installing .deb files. Double clicking on a .deb file caused gdebi to open and check the file for installation. Then when you click on install the program terminates. Have tried it on multiple .deb files and it does the same thing. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CurrentDesktop: MATE DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-02 (0 days ago) InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Beta amd64 (20210331.1) NonfreeKernelModules: nvidia_modeset nvidia Package: gdebi 0.9.5.7+nmu4 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Tags: hirsute Uname: Linux 5.11.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1922331/+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 1922331] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1922331/+attachment/5483387/+files/ProcCpuinfoMinimal.txt -- 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/1922331 Title: Gdebi quitting on installing deb files Status in Ubuntu MATE: New Status in gdebi package in Ubuntu: New Bug description: Gdebi quitting on installing .deb files. Double clicking on a .deb file caused gdebi to open and check the file for installation. Then when you click on install the program terminates. Have tried it on multiple .deb files and it does the same thing. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CurrentDesktop: MATE DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-02 (0 days ago) InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Beta amd64 (20210331.1) NonfreeKernelModules: nvidia_modeset nvidia Package: gdebi 0.9.5.7+nmu4 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Tags: hirsute Uname: Linux 5.11.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1922331/+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 1922331] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1922331/+attachment/5483388/+files/ProcEnviron.txt -- 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/1922331 Title: Gdebi quitting on installing deb files Status in Ubuntu MATE: New Status in gdebi package in Ubuntu: New Bug description: Gdebi quitting on installing .deb files. Double clicking on a .deb file caused gdebi to open and check the file for installation. Then when you click on install the program terminates. Have tried it on multiple .deb files and it does the same thing. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CurrentDesktop: MATE DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-02 (0 days ago) InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Beta amd64 (20210331.1) NonfreeKernelModules: nvidia_modeset nvidia Package: gdebi 0.9.5.7+nmu4 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Tags: hirsute Uname: Linux 5.11.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1922331/+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 1922331] Re: Gdebi quitting on installing deb files
I just double clicked on the .deb file to open it in Gdebi. Gdebi opened and checked the file. I clicked on install and then the program terminates. I tried it again and the same thing. -- 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/1922331 Title: Gdebi quitting on installing deb files Status in Ubuntu MATE: New Status in gdebi package in Ubuntu: New Bug description: Gdebi quitting on installing .deb files. Double clicking on a .deb file caused gdebi to open and check the file for installation. Then when you click on install the program terminates. Have tried it on multiple .deb files and it does the same thing. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CurrentDesktop: MATE DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-02 (0 days ago) InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Beta amd64 (20210331.1) NonfreeKernelModules: nvidia_modeset nvidia Package: gdebi 0.9.5.7+nmu4 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Tags: hirsute Uname: Linux 5.11.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1922331/+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 1922338] [NEW] Bluetooth not working after reboot after upgrade to 21.04
Public bug reported: 1) Description:Ubuntu Hirsute Hippo (development branch) Release:21.04 2) bluez: Installed: 5.56-0ubuntu3 Candidate: 5.56-0ubuntu3 Version table: *** 5.56-0ubuntu3 500 500 http://pl.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status After every reboot bluetooth doesn't work. The GNOME bluetooth on/off switch can be changed but doesn't have any effect - no devices are shown. Output from systemctl after reboot: karol@toronto:~$ systemctl status bluetooth.service ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2021-04-02 11:26:31 CEST; 2min 6s ago Docs: man:bluetoothd(8) Main PID: 811 (bluetoothd) Status: "Running" Tasks: 1 (limit: 14115) Memory: 3.2M CGroup: /system.slice/bluetooth.service └─811 /usr/lib/bluetooth/bluetoothd Apr 02 11:26:24 toronto systemd[1]: Starting Bluetooth service... Apr 02 11:26:25 toronto bluetoothd[811]: Bluetooth daemon 5.56 Apr 02 11:26:31 toronto systemd[1]: Started Bluetooth service. Apr 02 11:26:31 toronto bluetoothd[811]: Starting SDP server Apr 02 11:26:32 toronto bluetoothd[811]: Bluetooth management interface 1.19 initialized Apr 02 11:26:37 toronto bluetoothd[811]: Failed to set mode: Blocked through rfkill (0x12) Apr 02 11:27:21 toronto bluetoothd[811]: Failed to set mode: Blocked through rfkill (0x12) Apr 02 11:27:48 toronto bluetoothd[811]: Endpoint registered: sender=:1.72 path=/MediaEndpoint/A2DPSink/sbc Apr 02 11:27:48 toronto bluetoothd[811]: Endpoint registered: sender=:1.72 path=/MediaEndpoint/A2DPSource/sbc Then after running `sudo systemctl restart bluetooth` everything seems to be fine: karol@toronto:~$ sudo systemctl restart bluetooth [sudo] password for karol: karol@toronto:~$ systemctl status bluetooth.service ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2021-04-02 11:30:13 CEST; 3s ago Docs: man:bluetoothd(8) Main PID: 3152 (bluetoothd) Status: "Running" Tasks: 1 (limit: 14115) Memory: 760.0K CGroup: /system.slice/bluetooth.service └─3152 /usr/lib/bluetooth/bluetoothd Apr 02 11:30:13 toronto systemd[1]: Starting Bluetooth service... Apr 02 11:30:13 toronto bluetoothd[3152]: Bluetooth daemon 5.56 Apr 02 11:30:13 toronto systemd[1]: Started Bluetooth service. Apr 02 11:30:13 toronto bluetoothd[3152]: Starting SDP server Apr 02 11:30:13 toronto bluetoothd[3152]: Bluetooth management interface 1.19 initialized Apr 02 11:30:15 toronto bluetoothd[3152]: Endpoint registered: sender=:1.72 path=/MediaEndpoint/A2DPSink/sbc Apr 02 11:30:15 toronto bluetoothd[3152]: Endpoint registered: sender=:1.72 path=/MediaEndpoint/A2DPSource/sbc karol@toronto:~$ ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 2 11:31:48 2021 InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80Q7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-13-generic root=UUID=9996d76c-d95e-4d4c-8902-0a583a091e93 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-02 (0 days ago) dmi.bios.date: 12/16/2015 dmi.bios.release: 1.43 dmi.bios.vendor: LENOVO dmi.bios.version: D5CN43WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Paris 5A8 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 300-15ISK dmi.ec.firmware.release: 1.43 dmi.modalias: dmi:bvnLENOVO:bvrD5CN43WW:bd12/16/2015:br1.43:efr1.43:svnLENOVO:pn80Q7:pvrLenovoideapad300-15ISK:rvnLENOVO:rnParis5A8:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad300-15ISK: dmi.product.family: IDEAPAD dmi.product.name: 80Q7 dmi.product.sku: LENOVO_MT_80Q7_BU_idea_FM_Lenovo ideapad 300-15ISK dmi.product.version: Lenovo ideapad 300-15ISK dmi.sys.vendor: LENOVO hciconfig: hci0: Type: Primary Bus: USB BD Address: 08:D4:0C:C4:D1:2C ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:14133 acl:230 sco:0 events:330 errors:0 TX bytes:5930 acl:17 sco:0 commands:164 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute wayland-session ** Description changed: 1) Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 2) bluez: - Installed: 5.56-0ubuntu3 - Candidate: 5.56-0ubuntu3 - Version table: - *** 5.56-0ubuntu3 500 - 500 http://pl.archive.ubuntu.com/ubuntu hirsute/main amd64
[Touch-packages] [Bug 1922331] Re: Gdebi quitting on installing deb files
Can't reproduce with local deb-file opened by Gdebi from Caja. About Firefox check the following bug 1854588 . -- 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/1922331 Title: Gdebi quitting on installing deb files Status in Ubuntu MATE: New Status in gdebi package in Ubuntu: New Bug description: Gdebi quitting on installing .deb files. Double clicking on a .deb file caused gdebi to open and check the file for installation. Then when you click on install the program terminates. Have tried it on multiple .deb files and it does the same thing. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CurrentDesktop: MATE DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-02 (0 days ago) InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Beta amd64 (20210331.1) NonfreeKernelModules: nvidia_modeset nvidia Package: gdebi 0.9.5.7+nmu4 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Tags: hirsute Uname: Linux 5.11.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1922331/+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 1803391] Re: Systemd update installation hangs in unattended-upgrades InstallOnShutdown mode
When i do upgrade form 18.04 to 20.04 with do-release-upgrade my system reboots on systemctl daemon-reexec from /var/lib/dpkg/info/systemd.postinst code: ``` # skip daemon-reexec and try-restarts during shutdown to avoid hitting LP: #1803391 if [ -n "$2" ] && [ "$(systemctl is-system-running)" != "stopping" ]; then _systemctl daemon-reexec || true # don't restart logind; this can be done again once this gets implemented: # https://github.com/systemd/systemd/issues/1163 _systemctl try-restart systemd-networkd.service || true _systemctl try-restart systemd-resolved.service || true _systemctl try-restart systemd-journald.service || true fi ``` command systemctl is-system-running return degradated. If i execute systemctl daemon-reexec from hand while do-release-upgrade waiting for accept changes on journald.conf, my system hangs. There is strace -ff systemctl daemon-reexec: https://pastebin.ubuntu.com/p/SkYnx8fdts/ ** Bug watch added: github.com/systemd/systemd/issues #1163 https://github.com/systemd/systemd/issues/1163 -- 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/1803391 Title: Systemd update installation hangs in unattended-upgrades InstallOnShutdown mode Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Status in systemd source package in Bionic: Fix Released Status in systemd source package in Cosmic: Fix Released Status in systemd source package in Disco: Fix Released Bug description: [Impact] * Installation of latest systemd update in -security hangs with current versions of unattended-upgrades in supported releases. The u-u-side fix is tracked in LP: #1778219. [Regression Potential] * The daemons, shipped in deb:systemd, are not attempted to be restarted because despite package installation the system is in the middle of shutting down. This means that currently running daemons may be helding up open files on the filesystem, however all process are being stopped and killed as part of shutdown. Hence the worst possible regression from this, is an unclean shutdown, but even that shouldn't happen with this update. [Test Case] Reproduction: rbalint@yogi:~$ lxc launch ubuntu:18.04 uu-systemd-onshutdown Creating uu-systemd-onshutdown Starting uu-systemd-onshutdown rbalint@yogi:~$ lxc shell uu-systemd-onshutdown mesg: ttyname failed: No such device root@uu-systemd-onshutdown:~# apt update -qq 23 packages can be upgraded. Run 'apt list --upgradable' to see them. root@uu-systemd-onshutdown:~# echo 'Unattended-Upgrade::InstallOnShutdown "true";' > /etc/apt/apt.conf.d/51unattended-upgrades-on-shutdown root@uu-systemd-onshutdown:~# apt list --upgradable Listing... Done apport/bionic-updates 2.20.9-0ubuntu7.5 all [upgradable from: 2.20.9-0ubuntu7.4] gettext-base/bionic-updates,bionic-security 0.19.8.1-6ubuntu0.1 amd64 [upgradable from: 0.19.8.1-6] kmod/bionic-updates 24-1ubuntu3.1 amd64 [upgradable from: 24-1ubuntu3] libglib2.0-0/bionic-updates 2.56.3-0ubuntu0.18.04.1 amd64 [upgradable from: 2.56.2-0ubuntu0.18.04.2] libglib2.0-data/bionic-updates 2.56.3-0ubuntu0.18.04.1 all [upgradable from: 2.56.2-0ubuntu0.18.04.2] libkmod2/bionic-updates 24-1ubuntu3.1 amd64 [upgradable from: 24-1ubuntu3] libmspack0/bionic-updates,bionic-security 0.6-3ubuntu0.2 amd64 [upgradable from: 0.6-3ubuntu0.1] libnss-systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] libpam-systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] libsystemd0/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] libudev1/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] lxd/bionic-updates 3.0.2-0ubuntu1~18.04.1 amd64 [upgradable from: 3.0.1-0ubuntu1~18.04.1] lxd-client/bionic-updates 3.0.2-0ubuntu1~18.04.1 amd64 [upgradable from: 3.0.1-0ubuntu1~18.04.1] openssh-client/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 [upgradable from: 1:7.6p1-4] openssh-server/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 [upgradable from: 1:7.6p1-4] openssh-sftp-server/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 [upgradable from: 1:7.6p1-4] python3-apport/bionic-updates 2.20.9-0ubuntu7.5 all [upgradable from: 2.20.9-0ubuntu7.4] python3-distupgrade/bionic-updates 1:18.04.28 all [upgradable from: 1:18.04.27] python3-problem-report/bionic-updates 2.20.9-0ubuntu7.5 all [upgradable from: 2.20.9-0ubuntu7.4] systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] systemd-sysv/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] ubuntu-release-upgrader-core/bionic-updates
[Touch-packages] [Bug 1912331] Re: Many interfaces lead to "kernel receive buffer overrun"
I have 4 servers with Ubuntu 20.04.2 with more than 5 physical ethernets interfaces each (one of then has 18 ethernets) and I had the problem with 2 of them. I can give you access to one of the servers with bug if needed. It's not in production yet and I can cleanup everything after debug. I tried to emulate the problem using KVM. I saw errors too (apparently non directly related with this issue) when use a lot of interfaces with bridges and vlans. Maybe this script can help to debug: wget https://releases.ubuntu.com/20.04/ubuntu-20.04.2-live-server- amd64.iso qemu-img create -f qcow2 disk1.qcow2 20G sudo -E kvm -m 4096 -netdev user,id=user.0 -device e1000,netdev=user.0 -device e1000,id=n1,mac=00:e0:4c:f6:02:3d -net tap,script=no,id=n1 -device e1000,id=n2,mac=00:e0:4c:f6:03:3d -net tap,id=n2 -device e1000,id=n3,mac=00:e0:4c:f6:04:3d -net tap,id=n3 -device e1000,id=n4,mac=00:e0:4c:f6:05:3d -net tap,id=n4 -device e1000,id=n5,mac=00:e0:4c:f6:06:3d -net tap,id=n5 -device e1000,id=n6,mac=00:e0:4c:f6:07:3d -net tap,id=n6 -device e1000,id=n7,mac=00:e0:4c:f6:08:3d -net tap,id=n7 -device e1000,id=n8,mac=00:e0:4c:f6:09:3d -net tap,id=n8 -device e1000,id=n9,mac=00:e0:4c:f6:10:3d -net tap,id=n9 -device e1000,id=n10,mac=00:e0:4c:f6:11:3d -net tap,id=n10 -device e1000,id=n11,mac=00:e0:4c:f6:12:3d -net tap,id=n11 -device e1000,id=n12,mac=00:e0:4c:f6:13:3d -net tap,id=n12 -device e1000,id=n13,mac=00:e0:4c:f6:14:3d -net tap,id=n13 -device e1000,id=n14,mac=00:e0:4c:f6:15:3d -net tap,id=n14 -device e1000,id=n15,mac=00:e0:4c:f6:16:3d -net tap,id=n15 -device e1000,id=n16,mac=00:e0:4c:f6:17:3d -net tap,id=n16 -vga virtio -display gtk -hda disk1.qcow2 -cdrom ubuntu-20.04.2-live-server-amd64.iso -boot c -smp 8 # Proceed with installation # Poweroff the machine # Power on with sudo -E kvm -m 4096 -netdev user,id=user.0 -device e1000,netdev=user.0 -device e1000,id=n1,mac=00:e0:4c:f6:02:3d -net tap,script=no,id=n1 -device e1000,id=n2,mac=00:e0:4c:f6:03:3d -net tap,id=n2 -device e1000,id=n3,mac=00:e0:4c:f6:04:3d -net tap,id=n3 -device e1000,id=n4,mac=00:e0:4c:f6:05:3d -net tap,id=n4 -device e1000,id=n5,mac=00:e0:4c:f6:06:3d -net tap,id=n5 -device e1000,id=n6,mac=00:e0:4c:f6:07:3d -net tap,id=n6 -device e1000,id=n7,mac=00:e0:4c:f6:08:3d -net tap,id=n7 -device e1000,id=n8,mac=00:e0:4c:f6:09:3d -net tap,id=n8 -device e1000,id=n9,mac=00:e0:4c:f6:10:3d -net tap,id=n9 -device e1000,id=n10,mac=00:e0:4c:f6:11:3d -net tap,id=n10 -device e1000,id=n11,mac=00:e0:4c:f6:12:3d -net tap,id=n11 -device e1000,id=n12,mac=00:e0:4c:f6:13:3d -net tap,id=n12 -device e1000,id=n13,mac=00:e0:4c:f6:14:3d -net tap,id=n13 -device e1000,id=n14,mac=00:e0:4c:f6:15:3d -net tap,id=n14 -device e1000,id=n15,mac=00:e0:4c:f6:16:3d -net tap,id=n15 -device e1000,id=n16,mac=00:e0:4c:f6:17:3d -net tap,id=n16 -vga virtio -display gtk -hda disk1.qcow2 -smp 8 # Login and… sudo apt-get update sudo apt-get install ansible magic-wormhole sshpass ansible-galaxy install mrlesmithjr.netplan #Copy the unzipped attached files debug-systemd.yml and hosts to vm #at host wormhole send debug-systemd.yml wormhole send hosts #receive files at vm wormhole receive ... wormhole receive ... # Configure the hosts file properly with ssh credentials (an example is attached) ansible-playbook -i hosts debug-systemd.yml reboot #login and... networkctl -a # you will see a lot of failing/degraded/pending interfaces ip -br a # You will see a log of interfaces without ip ** Attachment added: "debug-systemd.yml.zip" https://bugs.launchpad.net/ubuntu/focal/+source/systemd/+bug/1912331/+attachment/5483521/+files/debug-systemd.yml.zip -- 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/1912331 Title: Many interfaces lead to "kernel receive buffer overrun" Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Confirmed Status in systemd source package in Groovy: Fix Released Bug description: This is about a systemd-networkd bug, described here: https://github.com/systemd/systemd/issues/14417 There's a patch available: https://github.com/systemd/systemd/pull/16982 Can this be backported to Focal? To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1912331/+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 1660121] Re: LightDM can't use the user background on Mate
** Tags added: hirsute -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1660121 Title: LightDM can't use the user background on Mate Status in Ubuntu MATE: New Status in lightdm package in Ubuntu: Confirmed Bug description: Using Ubuntu Mate 16.10 (the issue appears too on 16.04 and 17.04 alpha 2). On Mate, the LightDM Gtk Greeter can't use the user background. It works fine on other DEs like Xfce. From what I understand, LightDM and/or the Gkt greeter (not sure which one handles the background) gets the background path from Gsettings, so I assume it can't find the one from Mate, which stores it in "org.mate.background picture-filename". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1660121/+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 1913855] Re: [radeon] Failure to pass system check and present login screen
[Expired for unity-greeter (Ubuntu) because there has been no activity for 60 days.] ** Changed in: unity-greeter (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1913855 Title: [radeon] Failure to pass system check and present login screen Status in lightdm package in Ubuntu: Expired Status in unity-greeter package in Ubuntu: Expired Status in xorg-server package in Ubuntu: Expired Bug description: I'm reporting this against xorg, because of where the problem occurs, as indicated below, I can't tell if the problem is with xorg, lightdm or light-locker. The system is a Dell Optiplex 745 single-booting to Xubuntu 20.04 up-to-date as of today. I replaced one of 2 monitors, the one rotated to portrait orientation, with a higher resolution monitor. Started the system, logged in as another user and changed the desktop background however, when I then logged out and restarted the system, it behaved normally until it displayed the usual /dev/sda1: clean, x/x files, /x blocks on both monitors. The prompt remained for a few seconds, slowly blinked off and on 6 times, and then remained with no further activity. The system works fine if I boot from a Xubuntu 18.04 DVD (I didn't have a 20.04 DVD, and this is the only machine with a burner). On another machine, I determined that the system was booting, because the machine was visible on the network, and its shared folders were accessible. I could get to a login prompt and log on using Alt+F1 to F6. Alt-F7 returned me to the file system check prompt. I was able to start xorg after logging on with startx, and changing all settings for the new monitor, everything worked normally until logging out, which of course returned me to the command line where I had given the command startx. If I log out requesting a restart, the system reboots, but still stops at the same place every time. That behavior hadn't changed the next day. I can use the machine, but only by selecting a terminal, logging as myself or the other user and giving the startx command. I have been unable to find anything on the Internet that corrects the problem. Since the problem first started, two crashes have occurred and I allowed them to be reported; however, they were light-locker crashes. I reinstalled lightdm and light-locker, but that made no difference. I installed gdm3, which works fine, but switching back to lightdm with: sudo dpkg-reconfigure gdm3 sudo dpkg --configure lightdm resulted in: dpkg: error processing package lightdm (--configure): package lightdm is already installed and configured Errors were encountered while processing: lightdm So I can't really be sure if the problem is with xorg, lightdm or light-locker, but since there are no error messages and everything else works fine, it's clearly a bug, if a strange one. I do not relish the idea of having to reinstall Xubuntu; so for the time being, I'll use gdm3, though I prefer lightdm's ability to properly display backdrops and use the two monitors properly extended (with gdm3, the mouse moves down the left portrait monitor before moving onto the right monitor where gdm3 sees fit to put the logon dialog). The next thing I'll try is autoremoving lightdm rebooting a few times and then reinstalling it... Because of the absence of error messages and information even suggesting why X isn't starting, I have no idea what other information about my system might be useful to you, but if you need something additional, I'll try to provide it. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE Date: Fri Jan 29 22:12:37 2021 DistUpgraded: 2020-10-20 06:56:14,405 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.4.0-62-generic, x86_64: installed virtualbox, 6.1.16, 5.4.0-65-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV620 LE [Radeon HD 3450] [1002:95c5] (prog-if 00 [VGA controller]) Subsystem: Dell OptiPlex 980 [1028:0342] InstallationDate: Installed on 2019-11-29 (427 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. OptiPlex 780 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine:
[Touch-packages] [Bug 1913855] Re: [radeon] Failure to pass system check and present login screen
[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1913855 Title: [radeon] Failure to pass system check and present login screen Status in lightdm package in Ubuntu: Expired Status in unity-greeter package in Ubuntu: Expired Status in xorg-server package in Ubuntu: Expired Bug description: I'm reporting this against xorg, because of where the problem occurs, as indicated below, I can't tell if the problem is with xorg, lightdm or light-locker. The system is a Dell Optiplex 745 single-booting to Xubuntu 20.04 up-to-date as of today. I replaced one of 2 monitors, the one rotated to portrait orientation, with a higher resolution monitor. Started the system, logged in as another user and changed the desktop background however, when I then logged out and restarted the system, it behaved normally until it displayed the usual /dev/sda1: clean, x/x files, /x blocks on both monitors. The prompt remained for a few seconds, slowly blinked off and on 6 times, and then remained with no further activity. The system works fine if I boot from a Xubuntu 18.04 DVD (I didn't have a 20.04 DVD, and this is the only machine with a burner). On another machine, I determined that the system was booting, because the machine was visible on the network, and its shared folders were accessible. I could get to a login prompt and log on using Alt+F1 to F6. Alt-F7 returned me to the file system check prompt. I was able to start xorg after logging on with startx, and changing all settings for the new monitor, everything worked normally until logging out, which of course returned me to the command line where I had given the command startx. If I log out requesting a restart, the system reboots, but still stops at the same place every time. That behavior hadn't changed the next day. I can use the machine, but only by selecting a terminal, logging as myself or the other user and giving the startx command. I have been unable to find anything on the Internet that corrects the problem. Since the problem first started, two crashes have occurred and I allowed them to be reported; however, they were light-locker crashes. I reinstalled lightdm and light-locker, but that made no difference. I installed gdm3, which works fine, but switching back to lightdm with: sudo dpkg-reconfigure gdm3 sudo dpkg --configure lightdm resulted in: dpkg: error processing package lightdm (--configure): package lightdm is already installed and configured Errors were encountered while processing: lightdm So I can't really be sure if the problem is with xorg, lightdm or light-locker, but since there are no error messages and everything else works fine, it's clearly a bug, if a strange one. I do not relish the idea of having to reinstall Xubuntu; so for the time being, I'll use gdm3, though I prefer lightdm's ability to properly display backdrops and use the two monitors properly extended (with gdm3, the mouse moves down the left portrait monitor before moving onto the right monitor where gdm3 sees fit to put the logon dialog). The next thing I'll try is autoremoving lightdm rebooting a few times and then reinstalling it... Because of the absence of error messages and information even suggesting why X isn't starting, I have no idea what other information about my system might be useful to you, but if you need something additional, I'll try to provide it. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE Date: Fri Jan 29 22:12:37 2021 DistUpgraded: 2020-10-20 06:56:14,405 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.4.0-62-generic, x86_64: installed virtualbox, 6.1.16, 5.4.0-65-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV620 LE [Radeon HD 3450] [1002:95c5] (prog-if 00 [VGA controller]) Subsystem: Dell OptiPlex 980 [1028:0342] InstallationDate: Installed on 2019-11-29 (427 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. OptiPlex 780 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine:
[Touch-packages] [Bug 1913855] Re: [radeon] Failure to pass system check and present login screen
[Expired for lightdm (Ubuntu) because there has been no activity for 60 days.] ** Changed in: lightdm (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1913855 Title: [radeon] Failure to pass system check and present login screen Status in lightdm package in Ubuntu: Expired Status in unity-greeter package in Ubuntu: Expired Status in xorg-server package in Ubuntu: Expired Bug description: I'm reporting this against xorg, because of where the problem occurs, as indicated below, I can't tell if the problem is with xorg, lightdm or light-locker. The system is a Dell Optiplex 745 single-booting to Xubuntu 20.04 up-to-date as of today. I replaced one of 2 monitors, the one rotated to portrait orientation, with a higher resolution monitor. Started the system, logged in as another user and changed the desktop background however, when I then logged out and restarted the system, it behaved normally until it displayed the usual /dev/sda1: clean, x/x files, /x blocks on both monitors. The prompt remained for a few seconds, slowly blinked off and on 6 times, and then remained with no further activity. The system works fine if I boot from a Xubuntu 18.04 DVD (I didn't have a 20.04 DVD, and this is the only machine with a burner). On another machine, I determined that the system was booting, because the machine was visible on the network, and its shared folders were accessible. I could get to a login prompt and log on using Alt+F1 to F6. Alt-F7 returned me to the file system check prompt. I was able to start xorg after logging on with startx, and changing all settings for the new monitor, everything worked normally until logging out, which of course returned me to the command line where I had given the command startx. If I log out requesting a restart, the system reboots, but still stops at the same place every time. That behavior hadn't changed the next day. I can use the machine, but only by selecting a terminal, logging as myself or the other user and giving the startx command. I have been unable to find anything on the Internet that corrects the problem. Since the problem first started, two crashes have occurred and I allowed them to be reported; however, they were light-locker crashes. I reinstalled lightdm and light-locker, but that made no difference. I installed gdm3, which works fine, but switching back to lightdm with: sudo dpkg-reconfigure gdm3 sudo dpkg --configure lightdm resulted in: dpkg: error processing package lightdm (--configure): package lightdm is already installed and configured Errors were encountered while processing: lightdm So I can't really be sure if the problem is with xorg, lightdm or light-locker, but since there are no error messages and everything else works fine, it's clearly a bug, if a strange one. I do not relish the idea of having to reinstall Xubuntu; so for the time being, I'll use gdm3, though I prefer lightdm's ability to properly display backdrops and use the two monitors properly extended (with gdm3, the mouse moves down the left portrait monitor before moving onto the right monitor where gdm3 sees fit to put the logon dialog). The next thing I'll try is autoremoving lightdm rebooting a few times and then reinstalling it... Because of the absence of error messages and information even suggesting why X isn't starting, I have no idea what other information about my system might be useful to you, but if you need something additional, I'll try to provide it. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE Date: Fri Jan 29 22:12:37 2021 DistUpgraded: 2020-10-20 06:56:14,405 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.4.0-62-generic, x86_64: installed virtualbox, 6.1.16, 5.4.0-65-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV620 LE [Radeon HD 3450] [1002:95c5] (prog-if 00 [VGA controller]) Subsystem: Dell OptiPlex 980 [1028:0342] InstallationDate: Installed on 2019-11-29 (427 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. OptiPlex 780 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine:
[Touch-packages] [Bug 1913763] Autopkgtest regression report (systemd/229-4ubuntu21.31)
All autopkgtests for the newly accepted systemd (229-4ubuntu21.31) for xenial
have finished running.
The following regressions have been reported in tests triggered by the package:
conntrack-tools/unknown (armhf)
pyudev/unknown (armhf)
linux-aws-hwe/unknown (arm64)
kwin/unknown (armhf)
nplan/0.32~16.04.7 (amd64, ppc64el)
Please visit the excuses page listed below and investigate the failures,
proceeding afterwards as per the StableReleaseUpdates policy regarding
autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/xenial/update_excuses.html#systemd
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
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/1913763
Title:
hyperv: unable to distinguish PTP devices
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Xenial:
Fix Committed
Status in systemd source package in Bionic:
Fix Released
Status in systemd source package in Focal:
Fix Released
Status in systemd source package in Groovy:
Fix Released
Bug description:
[impact]
the /dev/ptp0 device for a hyperv instance may not be the correct,
hyperv-provided, ptp device.
[test case]
on some hyperv instance types, particularly those that might contain
passthrough network card(s) that also provide ptp, the first ptp
device may not be the correct one to use for ptp, e.g. there may be
multiple ones:
$ ls /dev/ptp*
/dev/ptp0 /dev/ptp1
$ cat /sys/class/ptp/ptp0/clock_name
hyperv
$ cat /sys/class/ptp/ptp1/clock_name
mlx5_p2p
the order can change across boots, so a consistent way of addressing
the hyperv-provided one is needed
[regression potential]
any regression would involve failure to properly create the ptp
symlink, or other failure while udev is processing newly detected ptp
device(s)
[scope]
this is needed in all releases
this was fixed upstream with the commit
32e868f058da8b90add00b2958c516241c532b70 which is not yet included in
any release
[original description]
Hyperv provides a PTP device. On system with multiple PTP devices,
services like Chrony don't have a way to know which one is which.
We would like to have a udev rule to create a symlink to the hyperv
clock. This way, services could be configured to always use this clock
no matter if it is ptp0, ptp1, etc..
For example:
```
SUBSYSTEM=="ptp", ATTR{clock_name}=="hyperv", SYMLINK += "ptp_hyperv"
```
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1913763/+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 1922380] [NEW] remove shim-signed very difficult
You have been subscribed to a public bug:
Hello
I don't want the shim-signed anymore, but I need an additional password to
remove it.
This error is for all version of ubuntu.
I am sure I am entering the correct one because I entered it using a
copy paste technique.
Have pity on those who do not know English well !!
apt purge shim-signed
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances
Lecture des informations d'état... Fait
Les paquets suivants ont été installés automatiquement et ne sont plus
nécessaires :
mokutil shim
Veuillez utiliser « apt autoremove » pour les supprimer.
Les paquets suivants seront ENLEVÉS :
shim-signed*
ATTENTION : Les paquets essentiels suivants vont être enlevés.
Vous NE devez PAS faire ceci, à moins de savoir exactement ce
que vous êtes en train de faire.
shim-signed
0 mis à jour, 0 nouvellement installés, 1 à enlever et 0 non mis à jour.
Après cette opération, 2 734 ko d'espace disque seront libérés.
Vous êtes sur le point de faire quelque chose de potentiellement dangereux
Pour continuer, tapez la phrase « Oui, faites ce que je vous dis ! »
?]Oui, faites ce que je vous dis !
Annulation.
root@a:~# export LANG=us
root@a:~# apt purge shim-signed
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
mokutil shim
Use 'apt autoremove' to remove them.
The following packages will be REMOVED:
shim-signed*
WARNING: The following essential packages will be removed.
This should NOT be done unless you know exactly what you are doing!
shim-signed
0 upgraded, 0 newly installed, 1 to remove and 171 not upgraded.
After this operation, 2734 kB disk space will be freed.
You are about to do something potentially harmful.
To continue type in the phrase 'Yes, do as I say!'
?] Yes, do as I say!
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = "fr_FR:fr_CA",
LC_ALL = (unset),
LC_TIME = "fr_FR.UTF-8",
LC_MONETARY = "fr_FR.UTF-8",
LC_ADDRESS = "fr_FR.UTF-8",
LC_TELEPHONE = "fr_FR.UTF-8",
LC_NAME = "fr_FR.UTF-8",
LC_MEASUREMENT = "fr_FR.UTF-8",
LC_IDENTIFICATION = "fr_FR.UTF-8",
LC_NUMERIC = "fr_FR.UTF-8",
LC_PAPER = "fr_FR.UTF-8",
LANG = "us"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
dpkg: warning: overriding problem because --force enabled:
dpkg: warning: this is a protected package; it should not be removed
(Reading database ... 211327 files and directories currently installed.)
Removing shim-signed (1.45+15+1552672080.a4a1fbe-0ubuntu2) ...
(Reading database ... 211314 files and directories currently installed.)
Purging configuration files for shim-signed
(1.45+15+1552672080.a4a1fbe-0ubuntu2) ...
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
root@a:~#
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: evince 3.38.0-1
ProcVersionSignature: Ubuntu 5.8.0-34.37-generic 5.8.18
Uname: Linux 5.8.0-34-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 2 15:07:48 2021
InstallationDate: Installed on 2020-10-25 (159 days ago)
InstallationMedia: Ubuntu-Server 20.10 "Groovy Gorilla" - Release amd64
(20201022)
KernLog:
SourcePackage: evince
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: apt (Ubuntu)
Importance: Undecided
Status: Incomplete
** Tags: amd64 apport-bug groovy uec-images
--
remove shim-signed very difficult
https://bugs.launchpad.net/bugs/1922380
You received this bug notification because you are a member of Ubuntu Touch
seeded packages, which is subscribed to apt in Ubuntu.
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1922396] [NEW] package initramfs-tools 0.136ubuntu6.4 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status
Public bug reported: Hello I'm trying to do apt-get upgrade and I get the following errors: Setting up initramfs-tools (0.136ubuntu6.4) ... update-initramfs: deferring update (trigger activated) Setting up flash-kernel (3.103ubuntu1~20.04.1) ... flash-kernel: deferring update (trigger activated) Processing triggers for initramfs-tools (0.136ubuntu6.4) ... update-initramfs: Generating /boot/initrd.img-5.4.0-70-generic Unsupported platform. run-parts: /etc/initramfs/post-update.d//flash-kernel exited with return code 1 dpkg: error processing package initramfs-tools (--configure): installed initramfs-tools package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: initramfs-tools Version of Ubuntu: Description:Ubuntu 20.04.2 LTS Release:20.04 version Unable to locate package pkgname Expected: Successful upgrade ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.4 Uname: Linux 4.9.93-mainline-rev1 armv7l ApportVersion: 2.20.11-0ubuntu27.16 Architecture: armhf CasperMD5CheckResult: skip Date: Fri Apr 2 21:45:54 2021 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.4 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2021-04-02 (0 days ago) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package armhf focal uec-images -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1922396 Title: package initramfs-tools 0.136ubuntu6.4 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: Hello I'm trying to do apt-get upgrade and I get the following errors: Setting up initramfs-tools (0.136ubuntu6.4) ... update-initramfs: deferring update (trigger activated) Setting up flash-kernel (3.103ubuntu1~20.04.1) ... flash-kernel: deferring update (trigger activated) Processing triggers for initramfs-tools (0.136ubuntu6.4) ... update-initramfs: Generating /boot/initrd.img-5.4.0-70-generic Unsupported platform. run-parts: /etc/initramfs/post-update.d//flash-kernel exited with return code 1 dpkg: error processing package initramfs-tools (--configure): installed initramfs-tools package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: initramfs-tools Version of Ubuntu: Description: Ubuntu 20.04.2 LTS Release: 20.04 version Unable to locate package pkgname Expected: Successful upgrade ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.4 Uname: Linux 4.9.93-mainline-rev1 armv7l ApportVersion: 2.20.11-0ubuntu27.16 Architecture: armhf CasperMD5CheckResult: skip Date: Fri Apr 2 21:45:54 2021 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.4 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2021-04-02 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1922396/+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 1922396] Re: package initramfs-tools 0.136ubuntu6.4 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1922396 Title: package initramfs-tools 0.136ubuntu6.4 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: Hello I'm trying to do apt-get upgrade and I get the following errors: Setting up initramfs-tools (0.136ubuntu6.4) ... update-initramfs: deferring update (trigger activated) Setting up flash-kernel (3.103ubuntu1~20.04.1) ... flash-kernel: deferring update (trigger activated) Processing triggers for initramfs-tools (0.136ubuntu6.4) ... update-initramfs: Generating /boot/initrd.img-5.4.0-70-generic Unsupported platform. run-parts: /etc/initramfs/post-update.d//flash-kernel exited with return code 1 dpkg: error processing package initramfs-tools (--configure): installed initramfs-tools package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: initramfs-tools Version of Ubuntu: Description: Ubuntu 20.04.2 LTS Release: 20.04 version Unable to locate package pkgname Expected: Successful upgrade ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.4 Uname: Linux 4.9.93-mainline-rev1 armv7l ApportVersion: 2.20.11-0ubuntu27.16 Architecture: armhf CasperMD5CheckResult: skip Date: Fri Apr 2 21:45:54 2021 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.4 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2021-04-02 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1922396/+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 1922380] Re: remove shim-signed very difficult
OK it seems you were actually complaining that French did not work for
you. Have you tried entering it manually? Chances are copying messes
things up.
** Changed in: shim-signed (Ubuntu)
Status: Invalid => Incomplete
** Package changed: shim-signed (Ubuntu) => apt (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1922380
Title:
remove shim-signed very difficult
Status in apt package in Ubuntu:
Incomplete
Bug description:
Hello
I don't want the shim-signed anymore, but I need an additional password to
remove it.
This error is for all version of ubuntu.
I am sure I am entering the correct one because I entered it using a
copy paste technique.
Have pity on those who do not know English well !!
apt purge shim-signed
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances
Lecture des informations d'état... Fait
Les paquets suivants ont été installés automatiquement et ne sont plus
nécessaires :
mokutil shim
Veuillez utiliser « apt autoremove » pour les supprimer.
Les paquets suivants seront ENLEVÉS :
shim-signed*
ATTENTION : Les paquets essentiels suivants vont être enlevés.
Vous NE devez PAS faire ceci, à moins de savoir exactement ce
que vous êtes en train de faire.
shim-signed
0 mis à jour, 0 nouvellement installés, 1 à enlever et 0 non mis à jour.
Après cette opération, 2 734 ko d'espace disque seront libérés.
Vous êtes sur le point de faire quelque chose de potentiellement dangereux
Pour continuer, tapez la phrase « Oui, faites ce que je vous dis ! »
?]Oui, faites ce que je vous dis !
Annulation.
root@a:~# export LANG=us
root@a:~# apt purge shim-signed
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer
required:
mokutil shim
Use 'apt autoremove' to remove them.
The following packages will be REMOVED:
shim-signed*
WARNING: The following essential packages will be removed.
This should NOT be done unless you know exactly what you are doing!
shim-signed
0 upgraded, 0 newly installed, 1 to remove and 171 not upgraded.
After this operation, 2734 kB disk space will be freed.
You are about to do something potentially harmful.
To continue type in the phrase 'Yes, do as I say!'
?] Yes, do as I say!
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = "fr_FR:fr_CA",
LC_ALL = (unset),
LC_TIME = "fr_FR.UTF-8",
LC_MONETARY = "fr_FR.UTF-8",
LC_ADDRESS = "fr_FR.UTF-8",
LC_TELEPHONE = "fr_FR.UTF-8",
LC_NAME = "fr_FR.UTF-8",
LC_MEASUREMENT = "fr_FR.UTF-8",
LC_IDENTIFICATION = "fr_FR.UTF-8",
LC_NUMERIC = "fr_FR.UTF-8",
LC_PAPER = "fr_FR.UTF-8",
LANG = "us"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
dpkg: warning: overriding problem because --force enabled:
dpkg: warning: this is a protected package; it should not be removed
(Reading database ... 211327 files and directories currently installed.)
Removing shim-signed (1.45+15+1552672080.a4a1fbe-0ubuntu2) ...
(Reading database ... 211314 files and directories currently installed.)
Purging configuration files for shim-signed
(1.45+15+1552672080.a4a1fbe-0ubuntu2) ...
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
root@a:~#
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: evince 3.38.0-1
ProcVersionSignature: Ubuntu 5.8.0-34.37-generic 5.8.18
Uname: Linux 5.8.0-34-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 2 15:07:48 2021
InstallationDate: Installed on 2020-10-25 (159 days ago)
InstallationMedia: Ubuntu-Server 20.10 "Groovy Gorilla" - Release amd64
(20201022)
KernLog:
SourcePackage: evince
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1922380/+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 1922212] Re: SSHD does not honor configuration files
Hello Jerrey, Thank you for taking out time to file a bug and making the Ubuntu server better. It's a bit upsetting that you're hitting this bug. Can you share your entire conf, please? This would help me better analyze the problem and help me reproduce it. While at it, could you also help me provide steps to reproduce this easily? I can make out the issue but having straightforward steps written will help me debug this fast enough. That said, I found a link to stack exchange that might help: https://unix.stackexchange.com/questions/218034/disabling-ssh-password-authentication-does-not-work-on-my-debian-vps Let me know if it helps? Also, does restarting sshd help? I am marking this bug as "Incomplete" for now. Once you provide the necessary details, please mark it back to "New" and then we can take a look and help debug further. Thanks! :) ** Changed in: openssh (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1922212 Title: SSHD does not honor configuration files Status in openssh package in Ubuntu: Incomplete Bug description: I'm working on Ubuntu 20, x86_64, fully patched. # lsb_release -a Distributor ID:Ubuntu Description: Ubuntu 20.04.2 LTS ... We are seeing reports of failed password-based logins using root: jounralctl -xe ... Apr 01 09:08:21 localhost sshd[239302]: Failed password for root from 49.88.112.77 port 36206 ssh2 Apr 01 09:08:21 localhost sshd[239302]: Failed password for root from 49.88.112.77 port 36206 ssh2 ... There are three attempts every second or two (literally): # journalctl -xe | grep -i -c 'Failed password for root' 324 Our OpenSSH server is configured with both no-password based logins and no-root logins. # ls /etc/ssh/sshd_config.d/ 10_pubkey_auth.conf 20_disable_root_login.conf # cat /etc/ssh/sshd_config.d/10_pubkey_auth.conf # Disable passwords PasswordAuthentication no ChallengeResponseAuthentication no UsePAM no # Enable public key PubkeyAuthentication yes # cat /etc/ssh/sshd_config.d/20_disable_root_login.conf PermitRootLogin no The config files are included last in our /etc/ssh/sshd_config file: # tail -n 3 /etc/ssh/sshd_config # For some reason OpenSSH does not include additional conf files by default. Include /etc/ssh/sshd_config.d/*.conf I dislike modifying /etc/ssh/sshd_config since it will be overwritten by the distro. With that said, I modified it without success. It really annoys me that we can't secure this service. Something looks very broken here. - # apt-cache show openssh-server Package: openssh-server Architecture: amd64 Version: 1:8.2p1-4ubuntu0.2 Multi-Arch: foreign Priority: optional Section: net Source: openssh Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Debian OpenSSH Maintainers Bugs: https://bugs.launchpad.net/ubuntu/+filebug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1922212/+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 1878969] Autopkgtest regression report (systemd/229-4ubuntu21.31)
All autopkgtests for the newly accepted systemd (229-4ubuntu21.31) for xenial
have finished running.
The following regressions have been reported in tests triggered by the package:
conntrack-tools/unknown (armhf)
pyudev/unknown (armhf)
linux-aws-hwe/unknown (arm64)
kwin/unknown (armhf)
nplan/0.32~16.04.7 (amd64, ppc64el)
Please visit the excuses page listed below and investigate the failures,
proceeding afterwards as per the StableReleaseUpdates policy regarding
autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/xenial/update_excuses.html#systemd
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
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/1878969
Title:
time-epoch never changes in SRUs
Status in ubuntu-core-initramfs:
Fix Released
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Xenial:
Fix Committed
Status in systemd source package in Bionic:
Fix Released
Status in systemd source package in Focal:
Fix Released
Bug description:
[Impact]
* Systems without hwclock come up with a fixed time epoch which is not
updated in SRUs
* Ideally booting with a newer built of systemd should move time epoch to be
at least when systemd was last built. For example to the value of
SOURCE_DATE_EPOCH.
[Test Case]
* Boot without network NTP or hwclock
* Observe that the epoch is the same as the time when NEWS entry in the
systemd source code was last touched.
* Boot newer update of systemd, observe that the time epoch is at least 2020
[Regression Potential]
* Bad epoch, may result in unable to perform TLS connections,
validated GPG signatures, and snapd assertions. Changing epoch to be
more recent is desired. Some machines may rely on the fact that
"bionic" without hwclock always comes up in year 2018. But in practice
that is incorrect thing to do.
[Other Info]
* By default
option('time-epoch', type : 'integer', value : '-1',
description : 'time epoch for time clients')
in systemd is set to the modification time of the NEW entry
time_epoch = run_command(stat, '-c', '%Y', NEWS).stdout().to_int()
If available, it should be set to SOURCE_DATE_EPOCH=1585051767 value
to be compliant with the https://reproducible-
builds.org/docs/timestamps/ specification.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-core-initramfs/+bug/1878969/+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 1878969] Re: time-epoch never changes in SRUs
Hello Dimitri, or anyone else affected,
Accepted systemd into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu21.31 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
xenial to verification-done-xenial. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-xenial. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Tags removed: verification-failed-xenial
** Tags added: verification-needed-xenial
--
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/1878969
Title:
time-epoch never changes in SRUs
Status in ubuntu-core-initramfs:
Fix Released
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Xenial:
Fix Committed
Status in systemd source package in Bionic:
Fix Released
Status in systemd source package in Focal:
Fix Released
Bug description:
[Impact]
* Systems without hwclock come up with a fixed time epoch which is not
updated in SRUs
* Ideally booting with a newer built of systemd should move time epoch to be
at least when systemd was last built. For example to the value of
SOURCE_DATE_EPOCH.
[Test Case]
* Boot without network NTP or hwclock
* Observe that the epoch is the same as the time when NEWS entry in the
systemd source code was last touched.
* Boot newer update of systemd, observe that the time epoch is at least 2020
[Regression Potential]
* Bad epoch, may result in unable to perform TLS connections,
validated GPG signatures, and snapd assertions. Changing epoch to be
more recent is desired. Some machines may rely on the fact that
"bionic" without hwclock always comes up in year 2018. But in practice
that is incorrect thing to do.
[Other Info]
* By default
option('time-epoch', type : 'integer', value : '-1',
description : 'time epoch for time clients')
in systemd is set to the modification time of the NEW entry
time_epoch = run_command(stat, '-c', '%Y', NEWS).stdout().to_int()
If available, it should be set to SOURCE_DATE_EPOCH=1585051767 value
to be compliant with the https://reproducible-
builds.org/docs/timestamps/ specification.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-core-initramfs/+bug/1878969/+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 1913763] Re: hyperv: unable to distinguish PTP devices
Hello Gauthier, or anyone else affected,
Accepted systemd into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu21.31 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
xenial to verification-done-xenial. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-xenial. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Tags removed: verification-done verification-done-xenial
** Tags added: verification-needed verification-needed-xenial
--
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/1913763
Title:
hyperv: unable to distinguish PTP devices
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Xenial:
Fix Committed
Status in systemd source package in Bionic:
Fix Released
Status in systemd source package in Focal:
Fix Released
Status in systemd source package in Groovy:
Fix Released
Bug description:
[impact]
the /dev/ptp0 device for a hyperv instance may not be the correct,
hyperv-provided, ptp device.
[test case]
on some hyperv instance types, particularly those that might contain
passthrough network card(s) that also provide ptp, the first ptp
device may not be the correct one to use for ptp, e.g. there may be
multiple ones:
$ ls /dev/ptp*
/dev/ptp0 /dev/ptp1
$ cat /sys/class/ptp/ptp0/clock_name
hyperv
$ cat /sys/class/ptp/ptp1/clock_name
mlx5_p2p
the order can change across boots, so a consistent way of addressing
the hyperv-provided one is needed
[regression potential]
any regression would involve failure to properly create the ptp
symlink, or other failure while udev is processing newly detected ptp
device(s)
[scope]
this is needed in all releases
this was fixed upstream with the commit
32e868f058da8b90add00b2958c516241c532b70 which is not yet included in
any release
[original description]
Hyperv provides a PTP device. On system with multiple PTP devices,
services like Chrony don't have a way to know which one is which.
We would like to have a udev rule to create a symlink to the hyperv
clock. This way, services could be configured to always use this clock
no matter if it is ptp0, ptp1, etc..
For example:
```
SUBSYSTEM=="ptp", ATTR{clock_name}=="hyperv", SYMLINK += "ptp_hyperv"
```
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1913763/+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 1878969] Autopkgtest regression report (systemd/229-4ubuntu21.30)
All autopkgtests for the newly accepted systemd (229-4ubuntu21.30) for xenial
have finished running.
The following regressions have been reported in tests triggered by the package:
linux-aws-hwe/unknown (arm64)
Please visit the excuses page listed below and investigate the failures,
proceeding afterwards as per the StableReleaseUpdates policy regarding
autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/xenial/update_excuses.html#systemd
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
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/1878969
Title:
time-epoch never changes in SRUs
Status in ubuntu-core-initramfs:
Fix Released
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Xenial:
Fix Committed
Status in systemd source package in Bionic:
Fix Released
Status in systemd source package in Focal:
Fix Released
Bug description:
[Impact]
* Systems without hwclock come up with a fixed time epoch which is not
updated in SRUs
* Ideally booting with a newer built of systemd should move time epoch to be
at least when systemd was last built. For example to the value of
SOURCE_DATE_EPOCH.
[Test Case]
* Boot without network NTP or hwclock
* Observe that the epoch is the same as the time when NEWS entry in the
systemd source code was last touched.
* Boot newer update of systemd, observe that the time epoch is at least 2020
[Regression Potential]
* Bad epoch, may result in unable to perform TLS connections,
validated GPG signatures, and snapd assertions. Changing epoch to be
more recent is desired. Some machines may rely on the fact that
"bionic" without hwclock always comes up in year 2018. But in practice
that is incorrect thing to do.
[Other Info]
* By default
option('time-epoch', type : 'integer', value : '-1',
description : 'time epoch for time clients')
in systemd is set to the modification time of the NEW entry
time_epoch = run_command(stat, '-c', '%Y', NEWS).stdout().to_int()
If available, it should be set to SOURCE_DATE_EPOCH=1585051767 value
to be compliant with the https://reproducible-
builds.org/docs/timestamps/ specification.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-core-initramfs/+bug/1878969/+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 1913763] Autopkgtest regression report (systemd/229-4ubuntu21.30)
All autopkgtests for the newly accepted systemd (229-4ubuntu21.30) for xenial
have finished running.
The following regressions have been reported in tests triggered by the package:
linux-aws-hwe/unknown (arm64)
Please visit the excuses page listed below and investigate the failures,
proceeding afterwards as per the StableReleaseUpdates policy regarding
autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/xenial/update_excuses.html#systemd
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
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/1913763
Title:
hyperv: unable to distinguish PTP devices
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Xenial:
Fix Committed
Status in systemd source package in Bionic:
Fix Released
Status in systemd source package in Focal:
Fix Released
Status in systemd source package in Groovy:
Fix Released
Bug description:
[impact]
the /dev/ptp0 device for a hyperv instance may not be the correct,
hyperv-provided, ptp device.
[test case]
on some hyperv instance types, particularly those that might contain
passthrough network card(s) that also provide ptp, the first ptp
device may not be the correct one to use for ptp, e.g. there may be
multiple ones:
$ ls /dev/ptp*
/dev/ptp0 /dev/ptp1
$ cat /sys/class/ptp/ptp0/clock_name
hyperv
$ cat /sys/class/ptp/ptp1/clock_name
mlx5_p2p
the order can change across boots, so a consistent way of addressing
the hyperv-provided one is needed
[regression potential]
any regression would involve failure to properly create the ptp
symlink, or other failure while udev is processing newly detected ptp
device(s)
[scope]
this is needed in all releases
this was fixed upstream with the commit
32e868f058da8b90add00b2958c516241c532b70 which is not yet included in
any release
[original description]
Hyperv provides a PTP device. On system with multiple PTP devices,
services like Chrony don't have a way to know which one is which.
We would like to have a udev rule to create a symlink to the hyperv
clock. This way, services could be configured to always use this clock
no matter if it is ptp0, ptp1, etc..
For example:
```
SUBSYSTEM=="ptp", ATTR{clock_name}=="hyperv", SYMLINK += "ptp_hyperv"
```
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1913763/+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 1916931] Re: omshell returns inconsistent results or segfaults
** Tags added: focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1916931 Title: omshell returns inconsistent results or segfaults Status in isc-dhcp package in Ubuntu: Confirmed Bug description: I have just built a Ubuntu 20.04 server and installed isc-dhcp-server 4.4.1 on it and I am seeing inconsistent returns from omshell. Initially omshell returns data as expected, but when I exit and re-enter omshell connections fail. Here is the initial, working, session: # omshell > server localhost > port 7911 > key omapi_key > connect obj: > new failover-state obj: failover-state > set name = "dhcp-failover" obj: failover-state name = "dhcp-failover" > open obj: failover-state name = "dhcp-failover" partner-address = c0:9d:e9:76:e9:55:00:00 partner-port = 00:00:02:07 local-address = 10:9d:e9:76:e9:55:00:00 local-port = 00:00:02:07 max-outstanding-updates = 00:00:00:0a mclt = 00:00:01:2c load-balance-max-secs = 00:00:00:03 load-balance-hba = ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00 partner-state = 00:00:00:02 local-state = 00:00:00:02 partner-stos = 60:36:d0:68 local-stos = 60:36:8b:3b hierarchy = 00:00:00:01 last-packet-sent = 00:00:00:00 last-timestamp-received = 00:00:00:00 skew = 00:00:00:00 max-response-delay = 00:00:00:3c cur-unacked-updates = 00:00:00:00 Here is what I see when the connect fails. Well, just hangs really. # omshell > server localhost > port 7911 > key omapi_key > connect And then I hit ctrl-c to break out and tried again: # omshell > server localhost > port 7911 > key omapi_key > connect Segmentation fault (core dumped) Note, the peer to this server is still running Ubuntu 18.04 with isc-dhcp-server 4.3.5. Running the exact same commands on the peer works reliably. (They are using the same python script to drive omshell.) The DHCP server on the new system appears to be working just fine as reported by omshell on the peer and systemctl. I was curious if the problem could be with the mis-matched versions of isc-dhcp-server so I shutdown isc-dhcp-server on the 18.04 system and get the same results. I also tried using a python script with the pypureomapi module to try and determine if the problem was in omshell or the server. I got very similar results when I attempted to get information about the failover state of the server. Interestingly interrogating the server about host information seems to work just fine. This is a critical bug since I don't see how to fail over a DHCP that is running the isc-dhcp-server on 20.04 without being able to issue omapi commands. I am attaching apport output to this bug report. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1916931/+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 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
** Tags removed: rls-hh-incoming -- 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/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Status in mesa source package in Hirsute: Confirmed Status in ubiquity source package in Hirsute: Confirmed Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Cases where the crash can be triggered: - Using a Virtualbox VM, where graphics acceleration is handled by mesa with LLVMPIPE - Start the ISO on real hardware in 'safe graphics mode' Cases where the crash is not encountered: - Start the ISO on real intel (HD graphics) hardware with full acceleration. NOTE: The crash can be avoided by downgrading MESA 21.0.x packages to the previous 20.3.4 in hirsute. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+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 1918410] Re: isc-dhcp-client denied by apparmor
** Tags added: focal
** Changed in: isc-dhcp (Ubuntu)
Status: Confirmed => Triaged
** Changed in: isc-dhcp (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1918410
Title:
isc-dhcp-client denied by apparmor
Status in isc-dhcp package in Ubuntu:
Triaged
Bug description:
Hi, I get weird errors in the audit log, seeing dhclient is being
denied reading its comm or the comm of one of its tasks:
[1383307.827378] audit: type=1400 audit(1615367094.054:162):
apparmor="DENIED" operation="open" profile="/{,usr/}sbin/dhclient"
name="/proc/1095210/task/1095213/comm" pid=1095210 comm="dhclient"
requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
This might or might not be linked with the fact that I can't get an
IPv4 on this interface. Note that it happened to other, see this
comment:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1413232/comments/8
Or even an article recommending disabling apparmor for dhclient(!):
https://blog.anthony-jacob.com/perte-dip-v4-sous-ubuntu-20-04-apparmor-et-dhclient/
As I said, I'm not sure this is the root cause of the lack of IPv4 renewal,
because running it manually *does* succeed in getting an IP. And running it in
strace shows the EACCES failure:
[pid 1095210] openat(AT_FDCWD, "/proc/self/task/1095211/comm", O_RDWRstrace:
Process 1095211 attached
) = -1 EACCES (Permission non accordée)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1918410/+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 1880775] Re: HP Envy 4524 All In One - Device communication error - code 5012;
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cups (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1880775 Title: HP Envy 4524 All In One - Device communication error - code 5012; Status in cups package in Ubuntu: Confirmed Bug description: Situation: Ubuntu 20.04 LTS after fresh install, NOT upgrade on desktop (had 16.04 LTS before). Printer was attached during fresh install of 20.04 LTS and internet connection, third party downloads ticked. Bug description: USB connected HP Envy 4524 All In One is recognized multiple times as printer but does not print, scans occasionally but unreliable in getting recognized by 20.04 LTS. Additional Information: HP Envy 4524 All In One works flawless with Ubuntu 18.04 LTS on Laptop. Worked flawless with Ubuntu 16.04 LTS on the desktop used above. Steps taken so far: De-installed/purged hplip 3.20.3 as sudo hp-check -i showed multiple errors and missing dependencies. Installed hplip 3.20.5 from the HPLIP site and ran the script which resulted in compiling and installing the printer with nil errors running sudo hp-check -i. However, after reboot Device communication error - code 5012 re-occured (current hp-check log attached). Log ___ administrator@office-server:~$ sudo hp-check -i [sudo] password for administrator: /usr/bin/hp-check:685: SyntaxWarning: "is not" with a literal. Did you mean "!="? if 'getfacl' not in g and '' is not g and 'file' not in g: Saving output in log file: /home/administrator/hp-check.log HP Linux Imaging and Printing System (ver. 3.20.5) Dependency/Version Check Utility ver. 15.1 Copyright (c) 2001-18 HP Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. Note: hp-check can be run in three modes: 1. Compile-time check mode (-c or --compile): Use this mode before compiling the HPLIP supplied tarball (.tar.gz or .run) to determine if the proper dependencies are installed to successfully compile HPLIP. 2. Run-time check mode (-r or --run): Use this mode to determine if a distro supplied package (.deb, .rpm, etc) or an already built HPLIP supplied tarball has the proper dependencies installed to successfully run. 3. Both compile- and run-time check mode (-b or --both) (Default): This mode will check both of the above cases (both compile- and run-time dependencies). Check types: a. EXTERNALDEP - External Dependencies b. GENERALDEP - General Dependencies (required both at compile and run time) c. COMPILEDEP - Compile time Dependencies d. [All are run-time checks] PYEXT SCANCONF QUEUES PERMISSION Status Types: OK MISSING - Missing Dependency or Permission or Plug-in INCOMPAT - Incompatible dependency-version or Plugin-version |Gtk-Message: 09:51:18.656: Failed to load module "canberra-gtk-module" --- | SYSTEM INFO | --- Kernel: 5.4.0-31-generic #35-Ubuntu SMP Thu May 7 20:20:34 UTC 2020 GNU/Linux Host: office-server Proc: 5.4.0-31-generic #35-Ubuntu SMP Thu May 7 20:20:34 UTC 2020 GNU/Linux Distribution: 12 20.04 Bitness: 64 bit --- | HPLIP CONFIGURATION | --- HPLIP-Version: HPLIP 3.20.5 HPLIP-Home: /usr/share/hplip HPLIP-Installation: Auto installation is supported for ubuntu distro 20.04 version
[Touch-packages] [Bug 1878969] Re: time-epoch never changes in SRUs
$ sudo date -s '1990-01-01'
Mon Jan 1 00:00:00 UTC 1990
$ lxc start ubuntu
$ lxc console ubuntu
ubuntu@ubuntu:~$ dpkg -l systemd|grep systemd
ii systemd229-4ubuntu21.29 amd64system and service manager
ubuntu@ubuntu:~$ date
Thu Feb 11 16:28:20 UTC 2016
>From https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu21.31
" -- Dan Streetman Thu, 01 Apr 2021 22:51:58 -0400"
$ sudo date -s '1990-01-01'
Mon Jan 1 00:00:00 UTC 1990
$ lxc start ubuntu
$ lxc console ubuntu
ubuntu@ubuntu:~$ dpkg -l systemd|grep systemd
ii systemd229-4ubuntu21.31 amd64system and service manager
ubuntu@ubuntu:~$ date
Fri Apr 2 02:52:11 UTC 2021
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial
--
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/1878969
Title:
time-epoch never changes in SRUs
Status in ubuntu-core-initramfs:
Fix Released
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Xenial:
Fix Committed
Status in systemd source package in Bionic:
Fix Released
Status in systemd source package in Focal:
Fix Released
Bug description:
[Impact]
* Systems without hwclock come up with a fixed time epoch which is not
updated in SRUs
* Ideally booting with a newer built of systemd should move time epoch to be
at least when systemd was last built. For example to the value of
SOURCE_DATE_EPOCH.
[Test Case]
* Boot without network NTP or hwclock
* Observe that the epoch is the same as the time when NEWS entry in the
systemd source code was last touched.
* Boot newer update of systemd, observe that the time epoch is at least 2020
[Regression Potential]
* Bad epoch, may result in unable to perform TLS connections,
validated GPG signatures, and snapd assertions. Changing epoch to be
more recent is desired. Some machines may rely on the fact that
"bionic" without hwclock always comes up in year 2018. But in practice
that is incorrect thing to do.
[Other Info]
* By default
option('time-epoch', type : 'integer', value : '-1',
description : 'time epoch for time clients')
in systemd is set to the modification time of the NEW entry
time_epoch = run_command(stat, '-c', '%Y', NEWS).stdout().to_int()
If available, it should be set to SOURCE_DATE_EPOCH=1585051767 value
to be compliant with the https://reproducible-
builds.org/docs/timestamps/ specification.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-core-initramfs/+bug/1878969/+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 1916418] Re: Custom properties set with ENV{WHATEVER} in parent no longer imported with IMPORT{parent} in udev rule
** Changed in: systemd (Ubuntu)
Milestone: None => hirsute-updates
--
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/1916418
Title:
Custom properties set with ENV{WHATEVER} in parent no longer imported
with IMPORT{parent} in udev rule
Status in systemd package in Ubuntu:
New
Status in systemd source package in Focal:
Invalid
Status in systemd source package in Groovy:
New
Bug description:
DisplayLink uses these udev rules to start the displaylink service
when a displaylink device is plugged in:
ACTION=="add", SUBSYSTEM=="usb", DRIVERS=="usb",
ATTR{idVendor}=="17e9", IMPORT{builtin}="usb_id",
ENV{DISPLAYLINK_DEVNAME}="$env{DEVNAME}",
ENV{DISPLAYLINK_DEVICE_ID}="$env{ID_BUS}-$env{BUSNUM}-$env{DEVNUM}-$env{ID_SERIAL}",
ENV{REMOVE_CMD}="/opt/displaylink/udev.sh $root
$env{DISPLAYLINK_DEVICE_ID} $env{DISPLAYLINK_DEVNAME}"
ACTION=="add", SUBSYSTEM=="usb", DRIVERS=="usb",
ATTRS{idVendor}=="17e9", ATTR{bInterfaceClass}=="ff",
ATTR{bInterfaceProtocol}=="03", IMPORT{parent}="DISPLAYLINK*",
RUN+="/opt/displaylink/udev.sh $root $env{DISPLAYLINK_DEVICE_ID}
$env{DISPLAYLINK_DEVNAME}"
The important thing to note here is that the first rule is for the
device that is the parent of the device triggers the second rule, and
the first rule sets ENV{DISPLAYLINK_DEVNAME} and
ENV{DISPLAYLINK_DEVICE_ID}, and the second rule attempts to import
them with IMPORT{parent} and then use them.
This worked fine in 20.04.
It does not work in 21.04.
When the second rule is triggered, DISPLAYLINK_DEVICE_ID and
DISPLAYLINK_DEVNAME are not set.
I have confirmed via udevadm monitor that the variables are getting
set on the parent.
I have confirmed via udevadm info --attribute-walk that the device
triggering the second rule is the child of the device triggering the
first one.
I have tried to import the variables explicitly instead of using a
glob pattern and that doesn't work either.
When I modify the rule to import DEVNAME, ID_BUS, BUSNUM, DEVNUM, and
ID_SERIAL directly, that works. The problem appears to be that these
custom properties we are setting in the parent can't be imported in
the child.
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: udev 247.3-1ubuntu2
ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
Uname: Linux 5.10.0-14-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu59
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
CustomUdevRuleFiles: 60-brother-libsane-type1.rules 99-displaylink.rules~
70-snap.core.rules 70-snap.snap-store.rules 99-x10.rules
60-brother-brscan4-libsane-type1.rules 50-yubikey.rules
70-snap.canonical-livepatch.rules 70-snap.gnome-system-monitor.rules
70-snap.chromium.rules 99-displaylink.rules
Date: Sun Feb 21 19:21:20 2021
InstallationDate: Installed on 2019-01-02 (781 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64
(20181017.3)
MachineType: Acer Predator G6-710
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.10.0-14-generic
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: systemd
UpgradeStatus: Upgraded to hirsute on 2021-02-21 (0 days ago)
dmi.bios.date: 05/18/2016
dmi.bios.release: 5.11
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: R01-A4
dmi.board.name: Predator G6-710
dmi.board.vendor: Acer
dmi.chassis.type: 3
dmi.chassis.vendor: Acer
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:
dmi.product.family: Acer Desktop
dmi.product.name: Predator G6-710
dmi.sys.vendor: Acer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1916418/+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 1920130] Re: System icons missing in kubuntu 21.04
I Experienced this problem and "sudo apt remove libqt5quick5-gles" followed by a reboot corrected the problem completely. Attached are the requested logs. ** Attachment added: "Requested upgrade logs" https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1920130/+attachment/5483583/+files/upgrade-logs.tgz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1920130 Title: System icons missing in kubuntu 21.04 Status in qtdeclarative-opensource-src package in Ubuntu: Won't Fix Status in qtdeclarative-opensource-src-gles package in Debian: New Bug description: Hi, just testing Kubuntu 21.04 on a spare machine. The upgrade initially was fine, but I then install kdenlive and krita which has messed up the system icons and window decorations (corners of windows are showing black squares). I have been through all the normal checks and even created a new user, but the bug still persists. The system Icons are broken in the system and nothing to do with the user account. lsb_release -rd Description:Ubuntu Hirsute Hippo (development branch) Release:21.04 Looking at the following may shed some light on the problem... Thanks, Paul. more .xsession-errors property "maximumWidth" file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "maximumWidth" file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "maximumWidth" libpng warning: iCCP: profile 'ICC profile': 'RGB ': RGB color space not permitted on grayscale PNG libpng warning: iCCP: profile 'ICC profile': 'RGB ': RGB color space not permitted on grayscale PNG QSGTextureAtlas: texture atlas allocation failed, code=501 file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/AbstractApplicationItem.qml:94: TypeError: Cannot read pro perty 'position' of null file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/AbstractApplicationItem.qml:93: TypeError: Cannot read pro perty 'background' of null file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/newstuff/qml/Page.qml:130: TypeError: Cannot read property 'useLabel' of null file:///usr/share/kpackage/kcms/kcm_splashscreen/contents/ui/main.qml:42:13: QML ColumnLayout: Cannot anchor to an ite m that isn't a parent or sibling. qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 55182, resource id: 69206064, major code: 18 (ChangePr operty), minor code: 0 qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 64351, resource id: 69206065, major code: 18 (ChangePr operty), minor code: 0 QQmlEngine::setContextForObject(): Object already has a QQmlContext file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "maximumWidth" file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "maximumWidth" file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "maximumWidth" QSGTextureAtlas: texture atlas allocation failed, code=501 file:///usr/share/kpackage/kcms/kcm_style/contents/ui/main.qml:52:13: QML ColumnLayout: Cannot anchor to an item that isn't a parent or sibling. xsettingsd: Reloading configuration xsettingsd: Loaded 11 settings from /home/paul/.config/xsettingsd/xsettingsd.conf kdeinit5: Got SETENV 'GTK_RC_FILES=/etc/gtk/gtkrc:/home/paul/.gtkrc:/home/paul/.config/gtkrc' from launcher. kdeinit5: Got SETENV 'GTK2_RC_FILES=/etc/gtk-2.0/gtkrc:/home/paul/.gtkrc-2.0:/home/paul/.config/gtkrc-2.0' from launch er. QDBusConnection: error: could not send signal to service "" path "//home/paul/.kde/share/config/kdeglobals" interface "org.kde.kconfig.notify" member "ConfigChanged": Invalid object path: //home/paul/.kde/share/config/kdeglobals QQmlEngine::setContextForObject(): Object already has a QQmlContext file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls.2/org.kde.desktop/ScrollView.qml:86:25: QML ScrollBar: Bindi ng loop detected for property "visible" file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kcm/GridViewKCM.qml:65:5: QML GridView: Binding loop detected for pro perty "rightPadding"
[Touch-packages] [Bug 1913763] Re: hyperv: unable to distinguish PTP devices
ddstreet@ddstreet-test:~$ dpkg -l systemd|grep systemd
ii systemd229-4ubuntu21.29 amd64system and service manager
ddstreet@ddstreet-test:~$ ls -l /dev/ptp*
crw--- 1 root root 247, 0 Apr 2 17:12 /dev/ptp0
crw--- 1 root root 247, 1 Apr 2 17:12 /dev/ptp1
ddstreet@ddstreet-test:~$ grep . /sys/class/ptp/*/clock_name
/sys/class/ptp/ptp0/clock_name:hyperv
/sys/class/ptp/ptp1/clock_name:mlx5_p2p
ddstreet@ddstreet-test:~$ dpkg -l systemd|grep systemd
ii systemd229-4ubuntu21.31 amd64system and service manager
ddstreet@ddstreet-test:~$ ls -l /dev/ptp*
crw--- 1 root root 247, 0 Apr 2 17:20 /dev/ptp0
crw--- 1 root root 247, 1 Apr 2 17:20 /dev/ptp1
lrwxrwxrwx 1 root root 4 Apr 2 17:20 /dev/ptp_hyperv -> ptp0
ddstreet@ddstreet-test:~$ grep . /sys/class/ptp/*/clock_name
/sys/class/ptp/ptp0/clock_name:hyperv
/sys/class/ptp/ptp1/clock_name:mlx5_p2p
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial
--
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/1913763
Title:
hyperv: unable to distinguish PTP devices
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Xenial:
Fix Committed
Status in systemd source package in Bionic:
Fix Released
Status in systemd source package in Focal:
Fix Released
Status in systemd source package in Groovy:
Fix Released
Bug description:
[impact]
the /dev/ptp0 device for a hyperv instance may not be the correct,
hyperv-provided, ptp device.
[test case]
on some hyperv instance types, particularly those that might contain
passthrough network card(s) that also provide ptp, the first ptp
device may not be the correct one to use for ptp, e.g. there may be
multiple ones:
$ ls /dev/ptp*
/dev/ptp0 /dev/ptp1
$ cat /sys/class/ptp/ptp0/clock_name
hyperv
$ cat /sys/class/ptp/ptp1/clock_name
mlx5_p2p
the order can change across boots, so a consistent way of addressing
the hyperv-provided one is needed
[regression potential]
any regression would involve failure to properly create the ptp
symlink, or other failure while udev is processing newly detected ptp
device(s)
[scope]
this is needed in all releases
this was fixed upstream with the commit
32e868f058da8b90add00b2958c516241c532b70 which is not yet included in
any release
[original description]
Hyperv provides a PTP device. On system with multiple PTP devices,
services like Chrony don't have a way to know which one is which.
We would like to have a udev rule to create a symlink to the hyperv
clock. This way, services could be configured to always use this clock
no matter if it is ptp0, ptp1, etc..
For example:
```
SUBSYSTEM=="ptp", ATTR{clock_name}=="hyperv", SYMLINK += "ptp_hyperv"
```
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1913763/+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 1920130] Re: System icons missing in kubuntu 21.04
@poet_imp Thanks for the logs! Unfortunately, these are only the latest logs and they don't explain what happened when you upgraded Ubuntu. Maybe you can attach the historical logs from /var/log/apt too? They have names like history.log.*.gz and term.log.*.gz. If you upgraded recently, then I guess it would be *.1.gz. Otherwise you can look at modification dates. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1920130 Title: System icons missing in kubuntu 21.04 Status in qtdeclarative-opensource-src package in Ubuntu: Won't Fix Status in qtdeclarative-opensource-src-gles package in Debian: New Bug description: Hi, just testing Kubuntu 21.04 on a spare machine. The upgrade initially was fine, but I then install kdenlive and krita which has messed up the system icons and window decorations (corners of windows are showing black squares). I have been through all the normal checks and even created a new user, but the bug still persists. The system Icons are broken in the system and nothing to do with the user account. lsb_release -rd Description:Ubuntu Hirsute Hippo (development branch) Release:21.04 Looking at the following may shed some light on the problem... Thanks, Paul. more .xsession-errors property "maximumWidth" file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "maximumWidth" file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "maximumWidth" libpng warning: iCCP: profile 'ICC profile': 'RGB ': RGB color space not permitted on grayscale PNG libpng warning: iCCP: profile 'ICC profile': 'RGB ': RGB color space not permitted on grayscale PNG QSGTextureAtlas: texture atlas allocation failed, code=501 file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/AbstractApplicationItem.qml:94: TypeError: Cannot read pro perty 'position' of null file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/AbstractApplicationItem.qml:93: TypeError: Cannot read pro perty 'background' of null file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/newstuff/qml/Page.qml:130: TypeError: Cannot read property 'useLabel' of null file:///usr/share/kpackage/kcms/kcm_splashscreen/contents/ui/main.qml:42:13: QML ColumnLayout: Cannot anchor to an ite m that isn't a parent or sibling. qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 55182, resource id: 69206064, major code: 18 (ChangePr operty), minor code: 0 qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 64351, resource id: 69206065, major code: 18 (ChangePr operty), minor code: 0 QQmlEngine::setContextForObject(): Object already has a QQmlContext file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "maximumWidth" file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "maximumWidth" file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "maximumWidth" QSGTextureAtlas: texture atlas allocation failed, code=501 file:///usr/share/kpackage/kcms/kcm_style/contents/ui/main.qml:52:13: QML ColumnLayout: Cannot anchor to an item that isn't a parent or sibling. xsettingsd: Reloading configuration xsettingsd: Loaded 11 settings from /home/paul/.config/xsettingsd/xsettingsd.conf kdeinit5: Got SETENV 'GTK_RC_FILES=/etc/gtk/gtkrc:/home/paul/.gtkrc:/home/paul/.config/gtkrc' from launcher. kdeinit5: Got SETENV 'GTK2_RC_FILES=/etc/gtk-2.0/gtkrc:/home/paul/.gtkrc-2.0:/home/paul/.config/gtkrc-2.0' from launch er. QDBusConnection: error: could not send signal to service "" path "//home/paul/.kde/share/config/kdeglobals" interface "org.kde.kconfig.notify" member "ConfigChanged": Invalid object path: //home/paul/.kde/share/config/kdeglobals QQmlEngine::setContextForObject(): Object already has a QQmlContext file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls.2/org.kde.desktop/ScrollView.qml:86:25: QML ScrollBar: Bindi ng loop detected for property "visible" file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kcm/GridViewKCM.qml:65:5: QML GridView: Binding loop detected for pro
