[Touch-packages] [Bug 2024396] Re: Xorg crash
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: xorg (Ubuntu) => ubuntu ** Summary changed: - Xorg crash + Crash -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2024396 Title: Crash Status in Ubuntu: Incomplete Bug description: bug na tela travou na opção do som e acessar as configurações no Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.15.0-75.82~20.04.1-generic 5.15.99 Uname: Linux 5.15.0-75-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.182.03 Fri Feb 24 03:29:56 UTC 2023 GCC version: gcc version 9.4.0 (Ubuntu 9.4.0-1ubuntu1~20.04.1) ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jun 19 15:26:08 2023 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85 DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 470.182.03, 5.10.0-1014-oem, x86_64: installed nvidia, 470.182.03, 5.15.0-75-generic, x86_64: installed virtualbox, 6.1.38, 5.15.0-75-generic, x86_64: installed GraphicsCard: Intel Corporation Device [8086:9a49] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0b24] Subsystem: Dell Device [1028:0b24] InstallationDate: Installed on 2023-06-08 (11 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. Inspiron 15 5510 ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-75-generic root=UUID=7ca9b39c-6d76-473f-8f4b-d40298565bc7 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/09/2023 dmi.bios.release: 2.19 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.19.1 dmi.board.name: 07MY78 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.19.1:bd05/09/2023:br2.19:svnDellInc.:pnInspiron155510:pvr:rvnDellInc.:rn07MY78:rvrA00:cvnDellInc.:ct10:cvr:sku0B24: dmi.product.family: Inspiron dmi.product.name: Inspiron 15 5510 dmi.product.sku: 0B24 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2024396/+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 2024618] Re: [Compaq Presario 420] In some boots, screen display is totally black possible i915 issue
** Summary changed: - In some boots, screen display is totally black possible i915 issue + [Compaq Presario 420] In some boots, screen display is totally black possible i915 issue ** Package changed: xorg (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2024618 Title: [Compaq Presario 420] In some boots, screen display is totally black possible i915 issue Status in linux package in Ubuntu: New Bug description: Hi, In some boots my laptop's graphic card(Intel Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx) only display a black screen, everything else seems to work, the system is able to produce sounds. Its possible to make the display go back to work after close and open the lid. After some tests and debug, it was seen that the screen wasn't entirely black the brightness seems to be setted to the minimum(almost impossible to see), and with a external monitor the brightness level was checked in `/sys/class/backlight/intel_backlight/actual_brightness` it was set to the default value, so the problem can't be the backlight. I believe is a i915 driver problem. it was tested the following kernel's params: i915.enable_dpcd_backlight=3 i915.enable_dpcd_backlight=1 i915.enable_dpcd_backlight=0 i915.invert_brightness=1 i915.invert_brightness=-1 i915.modeset=0 i915.modeset=1 i915.register_backlight=1 Still no results. Distributor ID: Ubuntu Description: Ubuntu 23.04 Release: 23.04 Codename: lunar xorg: Installed: 1:7.7+23ubuntu2 Candidate: 1:7.7+23ubuntu2 Version table: *** 1:7.7+23ubuntu2 500 500 http://br.archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-23.23-generic 6.2.12 Uname: Linux 6.2.0-23-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jun 21 16:03:20 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] InstallationDate: Installed on 2023-06-21 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:b720 Realtek Semiconductor Corp. RTL8723BU 802.11b/g/n WLAN Adapter Bus 001 Device 002: ID 0bda:5830 Realtek Semiconductor Corp. MTD camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Compaq 420 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-23-generic root=UUID=774e3ecb-1e91-4c0e-8036-66b475c7f433 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 126: Error executing command as another user: Request dismissed dmi.bios.date: 09/27/2021 dmi.bios.release: 5.11 dmi.bios.version: V1.13.X dmi.board.asset.tag: Default string dmi.board.name: N14JP6-V2 dmi.board.vendor: Compaq dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Compaq dmi.chassis.version: Default string dmi.ec.firmware.release: 1.0 dmi.modalias: dmi:bvn:bvrV1.13.X:bd09/27/2021:br5.11:efr1.0:svnCompaq:pn420:pvrDefaultstring:rvnCompaq:rnN14JP6-V2:rvr:cvnCompaq:ct10:cvrDefaultstring:skuDefaultstring: dmi.product.family: Presario dmi.product.name: 420 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Compaq version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to:
[Touch-packages] [Bug 2024603] Re: Selecting an alternate keyboard does not work and keypad is active even when typing
Thanks for the bug report. Please change the bug description to cover only one of those issues and move secondary issues to new bugs. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2024603 Title: Selecting an alternate keyboard does not work and keypad is active even when typing Status in Ubuntu: Incomplete Bug description: Since upgrading to Ubuntu 22.04 I have been having trouble with both Wayland and Xorg. Xorg seems the most stable of the two, so I am attempting to use it, however, I am having two problems that are causing problems. 1) I have added an alternate (Spanish) keyboard. This shows up in both the tray and under the keyboard settings, however, when I select the alternate keyboard it just reverts back to English and does not allow entry via the alternate keyboard. This part does work properly in Wayland allowing me to select either the English or the Spanish keyboard for the current window as I have selected in the settings 2) The touchpad is active full-time even with the "Disable while typing" options selected. This is continually causing problems as I bump the touchpad with my palm while typing. While the second issue is mostly an annoyance, the first makes Xorg unusable as I need to routinely switch to the Spanish character set for documents and web entry. In both cases Xorg is not responding to or acknowledging the selections. Neither of these were problems with Ubuntu 20.04 prior to upgrading. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 Uname: Linux 6.2.6-76060206-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jun 21 09:58:31 2023 DistUpgraded: 2022-12-01 16:49:16,796 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: system76/1.0.14~1684961628~22.04~8c2ff21~dev, 6.2.6-76060206-generic, x86_64: installed system76_acpi/1.0.2~1685480347~22.04~aaf10e3~dev, 6.2.6-76060206-generic, x86_64: installed system76-io/1.0.2~1685984007~22.04~7dc99ca~dev, 6.2.6-76060206-generic, x86_64: installed wireguard/1.0.20210606: added ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer HD Graphics 530 [1558:6509] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 04f2:b5a7 Chicony Electronics Co., Ltd Chicony USB 2.0 Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System76, Inc. Gazelle ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.6-76060206-generic root=UUID=ac9c0a24-9264-4620-9dca-59a3e7976588 ro acpi_backlight=vendor quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-12-02 (201 days ago) dmi.bios.date: 09/09/2016 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.02RSA2-1 dmi.board.asset.tag: Tag 12345 dmi.board.name: Gazelle dmi.board.vendor: System76, Inc. dmi.board.version: gaze11 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.02RSA2-1:bd09/09/2016:br5.11:svnSystem76,Inc.:pnGazelle:pvrgaze11:rvnSystem76,Inc.:rnGazelle:rvrgaze11:cvnSystem76,Inc.:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: Gazelle dmi.product.sku: Not Applicable dmi.product.version: gaze11 dmi.sys.vendor: System76, Inc. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2016-10-20T08:48:37.54 version.compiz: compiz 1:0.9.14.1+22.04.20220820-0ubuntu1 version.libdrm2: libdrm2 2.4.110-1pop0~1648761328~22.04~166056a~dev version.libgl1-mesa-dri: libgl1-mesa-dri 22.3.5-1pop1~1677168864~22.04~8f20e98~dev version.libgl1-mesa-glx: libgl1-mesa-glx 22.3.5-1pop1~1677168864~22.04~8f20e98~dev version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev:
[Touch-packages] [Bug 2024398] Re: wipefs not working as documented
Well, color me baffled. I was all set to try testing before and after applying the update. But now I cannot make the problem happen. I'll apply the updates anyway. Feel free to do what makes sense with this bug report -- mark worksforme, mark as duplicate, whatever. All I can think of is that the original error depended on a timestamp or something similar. But I do not know that. Sorry to "bug" you. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/2024398 Title: wipefs not working as documented Status in util-linux package in Ubuntu: Incomplete Bug description: Working on a new app to do full-disk backup and recovery, I'm having trouble with clearing existing partitions on a target drive. The man page for wipefs says that wipefs -a should wipe all partitions on the drive, but I have a situation where it has a strange result: lsblk reports one partition still remains. Steps to reproduce: - zero the first and last megabytes on the target drive - partition the drive with 'sfdisk /dev/drive is the name of the file attached to this report - wipefs -a - lsblk What I see at this point is a drive with one partition -- oddly 1,3,4,5 and 6 have disappeared, but partition 2 remains. This persists even after doing 'partprobe'. The problem seems to be that something in the label looks like an atari disk label(!!!), and 'wipefs -a' is not clearing it. I can get around the problem by using the --force parameter so: 'wipefs -f -a', and it reports an "atari" signature that was hiding in my DOS MBR somehow. Since I had zeroed the entire disk label area, this has to be a kind of mirage created by a specific configuration of bits. This behavior is a sneaky trap. It took me a very long time to stumble upon the cause and the fix I've just described. It seems best to me if wipefs can detect this issue and clear any odd artifacts like this. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: util-linux 2.34-0.1ubuntu9.3 Uname: Linux 5.18.10-76051810-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Jun 19 11:19:03 2023 SourcePackage: util-linux UpgradeStatus: Upgraded to focal on 2022-05-13 (402 days ago) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2017-05-02T14:12:29.908000 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/2024398/+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 1941938] Re: systemd trying to unmount non-existent file system
** Package changed: systemd (Ubuntu) => finalrd (Ubuntu) ** Changed in: finalrd (Ubuntu) Status: Confirmed => New -- 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/1941938 Title: systemd trying to unmount non-existent file system Status in finalrd package in Ubuntu: New Bug description: This output is copied from here: https://github.com/systemd/systemd/issues/20516 because I have not been able to capture the error messages. However what I am seeing is identical. sd-umoun[2406]: Failed to unmount /oldroot: Device or resource busy sd-umoun[2407]: Failed to unmount /oldroot/dev/pts: Device or resource busy sd-umoun[2408]: Failed to unmount /oldroot/dev: Device or resource busy shutdown[1]: Failed to finalize file systems, ignoring This has happened consistently since I upgraded to Ubuntu 20.04 two weeks ago, and is really annoying. Is there an actual problem or is it just noise that can be safely ignored? The only other thing referencing oldroot in its config was snap, which I have completely uninstalled to isolate the problem. /lib/systemd/systemd-shutdown also contains this string: # strings systemd-shutdown |grep old /oldroot sigprocmask(SIG_BLOCK, , ) == 0 sigprocmask(SIG_SETMASK, , NULL) == 0 I have never had an /oldroot mount and there isn't one now. I gather it is something the upgrade process might create, or it could perhaps be something broken in finalrd. Bin Li, who posted the above error to the systemd bug portal, got short shrift there and was told to contact the distro. So I am, as my version of systemd is 245, same as his. This problem is 100% repeateable and I see it every time I shutdown or restart. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.11 ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128 Uname: Linux 5.4.0-81-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Unity:Unity7:ubuntu Date: Sat Aug 28 14:28:03 2021 InstallationDate: Installed on 2017-05-26 (1554 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 5986:0708 Acer, Inc Integrated Camera Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 3: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 7: Dev 4, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 7: Dev 4, If 1, Class=Video, Driver=uvcvideo, 480M MachineType: LENOVO 20EVCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-81-generic root=UUID=3be3-50c9-41cc-94b5-eab06cff1d17 ro quiet splash SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2021-08-05 (22 days ago) dmi.bios.date: 12/01/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R00ET49W (1.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EVCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR00ET49W(1.24):bd12/01/2016:svnLENOVO:pn20EVCTO1WW:pvrThinkPadE560:rvnLENOVO:rn20EVCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E560 dmi.product.name: 20EVCTO1WW dmi.product.sku: LENOVO_MT_20EV_BU_Think_FM_ThinkPad E560 dmi.product.version: ThinkPad E560 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/finalrd/+bug/1941938/+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 1794516] Re: systemd-logind does not track all user processes
If you believe this is still an issue in 23.04, please open a bug upstream (https://github.com/systemd/ssytemd/issues) and post the link here. ** Changed in: systemd (Ubuntu) Status: Confirmed => Incomplete -- 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/1794516 Title: systemd-logind does not track all user processes Status in systemd package in Ubuntu: Incomplete Bug description: In Ubuntu 16.04(xenial) release all user processes are in session scope for example: └─user.slice └─user-200463.slice ├─user@200463.service │ └─init.scope │ ├─5886 /lib/systemd/systemd --user │ └─5888 (sd-pam) └─session-c2.scope ├─ 419 bash ├─ 471 mc ├─ 473 bash -rcfile .bashrc ├─ 1432 bash ├─ 1455 mc ├─ 1457 bash -rcfile .bashrc ├─ 1915 /usr/sbin/sssd -D -f In Ubuntu 18.04 (bionic) some processes are in session scope and other are in user service for example: ├─user.slice │ ├─user-200463.slice │ │ ├─session-84.scope │ │ │ ├─14992 gdm-session-worker [pam/gdm-password] │ │ │ ├─15013 /usr/bin/gnome-keyring-daemon --daemonize --login │ │ │ ├─15057 /usr/lib/gdm3/gdm-x-session --run-script env GNOME_SHELL_SESSION_MODE=ubuntu gnome-session --session=ubuntu │ │ │ ├─15059 /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth /run/user/200463/gdm/Xauthority -background none -noreset -keeptty -verbose 3 │ │ │ ├─15114 /usr/lib/gnome-session/gnome-session-binary --session=ubuntu │ │ │ ├─15205 /usr/bin/ssh-agent /usr/bin/im-launch env GNOME_SHELL_SESSION_MODE=ubuntu gnome-session --session=ubuntu │ │ │ ├─15317 /usr/bin/gnome-shell │ │ │ ├─15326 /usr/bin/pulseaudio --start --log-target=syslog │ │ │ ├─15345 ibus-daemon --xim --panel disable │ │ │ ├─15349 /usr/lib/ibus/ibus-dconf │ │ │ ├─15353 /usr/lib/ibus/ibus-x11 --kill-daemon │ │ │ ├─15417 /usr/lib/gnome-settings-daemon/gsd-power │ │ │ ├─15419 /usr/lib/gnome-settings-daemon/gsd-print-notifications │ │ │ ├─15420 /usr/lib/gnome-settings-daemon/gsd-rfkill │ │ │ ├─15423 /usr/lib/gnome-settings-daemon/gsd-screensaver-proxy │ │ │ ├─15425 /usr/lib/gnome-settings-daemon/gsd-sharing │ │ │ ├─15431 /usr/lib/gnome-settings-daemon/gsd-smartcard │ │ │ ├─15434 /usr/lib/gnome-settings-daemon/gsd-xsettings │ │ │ ├─15439 /usr/lib/gnome-settings-daemon/gsd-wacom │ │ │ ├─15442 /usr/lib/gnome-settings-daemon/gsd-sound │ │ │ ├─15452 /usr/lib/gnome-settings-daemon/gsd-clipboard │ │ │ ├─15454 /usr/lib/gnome-settings-daemon/gsd-a11y-settings │ │ │ ├─15457 /usr/lib/gnome-settings-daemon/gsd-datetime │ │ │ ├─15461 /usr/lib/gnome-settings-daemon/gsd-color │ │ │ ├─15464 /usr/lib/gnome-settings-daemon/gsd-keyboard │ │ │ ├─15465 /usr/lib/gnome-settings-daemon/gsd-housekeeping │ │ │ ├─15469 /usr/lib/gnome-settings-daemon/gsd-mouse │ │ │ ├─15472 /usr/lib/gnome-settings-daemon/gsd-media-keys │ │ │ ├─15510 diodon │ │ │ ├─15515 /usr/lib/gnome-disk-utility/gsd-disk-utility-notify │ │ │ ├─15516 /usr/lib/i386-linux-gnu/indicator-messages/indicator-messages-service │ │ │ ├─15519 /usr/lib/i386-linux-gnu/indicator-application/indicator-application-service │ │ │ ├─15527 /usr/lib/gnome-settings-daemon/gsd-printer │ │ │ ├─15531 nautilus-desktop │ │ │ ├─15593 /usr/lib/ibus/ibus-engine-simple │ │ │ ├─15711 update-notifier │ │ │ └─16083 /usr/lib/deja-dup/deja-dup-monitor │ │ └─user@200463.service │ │ ├─zeitgeist.service │ │ │ └─15551 /usr/bin/zeitgeist-daemon │ │ ├─gnome-terminal-server.service │ │ │ ├─15661 /usr/lib/gnome-terminal/gnome-terminal-server │ │ │ ├─15671 bash │ │ │ ├─15682 systemd-cgls │ │ │ └─15683 pager │ │ ├─gvfs-gphoto2-volume-monitor.service │ │ │ └─15400 /usr/lib/gvfs/gvfs-gphoto2-volume-monitor │ │ ├─zeitgeist-fts.service │ │ │ └─15557 /usr/lib/zeitgeist/zeitgeist/zeitgeist-fts │ │ ├─at-spi-dbus-bus.service │ │ │ ├─15267 /usr/lib/at-spi2-core/at-spi-bus-launcher │ │ │ ├─15277 /usr/bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork --print-address 3 │ │ │ └─15282 /usr/lib/at-spi2-core/at-spi2-registryd --use-gnome-session │ │ ├─dbus.service │ │ │ ├─15110 /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only │ │ │ ├─15298 /usr/bin/gnome-keyring-daemon --start --foreground --components=secrets │ │ │ ├─15357 /usr/lib/ibus/ibus-portal │ │ │ ├─15364 /usr/lib/gnome-shell/gnome-shell-calendar-server │ │ │ ├─15376 /usr/lib/gnome-online-accounts/goa-daemon │ │ │ ├─15387 /usr/lib/gnome-online-accounts/goa-identity-service │ │ │ └─15602 /usr/lib/dconf/dconf-service │ │ ├─gvfs-udisks2-volume-monitor.service │ │ │ └─15396 /usr/lib/gvfs/gvfs-udisks2-volume-monitor │ │ ├─evolution-calendar-factory.service │ │ │ ├─15567
[Touch-packages] [Bug 1794517] Re: Empty Display property in org.freedesktop.login1.session
If this is still an issue on newer releases, please provide a script or snippet of code that can be used to demonstrate the issue, and please explain why you believe the behavior to be incorrect. ** Changed in: systemd (Ubuntu) Status: Confirmed => Incomplete -- 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/1794517 Title: Empty Display property in org.freedesktop.login1.session Status in systemd package in Ubuntu: Incomplete Bug description: In Ubuntu 18.04 when get property of Display variable using DBus org.freedesktop.login1.session get empty value. In Ubuntu 16.04 release these values isn`t empty and get for example Display = :0. I use: Description: Ubuntu 18.04.1 LTS Release: 18.04 Package info: Package: systemd Version: 237-3ubuntu10.3 Priority: important Section: admin Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Debian systemd Maintainers Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 12,9 MB Pre-Depends: libacl1 (>= 2.2.51-8), libblkid1 (>= 2.19.1), libc6 (>= 2.27), libcap2 (>= 1:2.10), libcryptsetup12 (>= 2:1.4), libgcrypt20 (>= 1.8.0), libidn11 (>= 1.13), libip4tc0 (>= 1.6.0+snapshot20161117), liblz4-1 (>= 0.0~r130), liblzma5 (>= 5.1.1alpha+20120614), libseccomp2 (>= 2.3.1), libselinux1 (>= 2.1.9) Depends: libapparmor1 (>= 2.9.0-3+exp2), libaudit1 (>= 1:2.2.1), libcryptsetup12 (>= 2:1.4.3), libgpg-error0 (>= 1.14), libkmod2 (>= 5~), libmount1 (>= 2.26.2), libpam0g (>= 0.99.7.1), libsystemd0 (= 237-3ubuntu10.3), util-linux (>= 2.27.1), mount (>= 2.26), adduser, procps Recommends: libpam-systemd, dbus, networkd-dispatcher Suggests: systemd-container, policykit-1 Breaks: apparmor (<< 2.9.2-1), ifupdown (<< 0.8.5~), laptop-mode-tools (<< 1.68~), systemd-shim (<< 10-3~), udev (<< 228-5) Replaces: udev (<< 228-5) Homepage: https://www.freedesktop.org/wiki/Software/systemd Task: minimal, ubuntu-core Supported: 5y Download-Size: 2 947 kB APT-Manual-Installed: yes APT-Sources: http://my.repo/ubuntu-current bionic-updates/main i386 Packages Description: system and service manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1794517/+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 1932525] Re: This bug is back on my pc - bug #1722481 Systemd Sync twice at shutdown
Please re-open if this is still an issue on newer, supported releases. ** Changed in: systemd (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1932525 Title: This bug is back on my pc - bug #1722481 Systemd Sync twice at shutdown Status in systemd package in Ubuntu: Invalid Bug description: systemd should sync disks, before killing all processes on shutdown: bug #1722481 has returned. Is it possible this bug returned in ubuntu 21.04 - hirsute? see my systemd-shutdown in the txt file attached. ..or is a workaround possible for this? I notice this behavior when i shutdown and reboot. the laptop needs almost no time to shutdown, and then for 20 maybe 30 seconds the plymouth screen comes back with the rotating sign, waiting to sync probably, then the screen goes black and shutdown. my laptop is a HP elitebook 820 with ssd hdd. - snap of text of original bugreport - [Impact] * systemd-shutdown binary is executed to complete system shutdown. In xenial, it calls sync() after killing all processes, and not before killing them. This means that processes are racing the SIGKILL/TERM timeouts to sync all IO to disk. To mitigate this race condition, and make the shutdown process more reliable the sync() should also happen before process killing spree starts. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1932525/+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 1946667] Re: resolved reports Failed to send hostname reply: Invalid argument
The fix referenced upstream is included in Jammy and newer. At the moment I do not see a need to SRU this to Focal. ** Changed in: systemd (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1946667 Title: resolved reports Failed to send hostname reply: Invalid argument Status in systemd package in Ubuntu: Fix Released Bug description: According to https://github.com/systemd/systemd/issues/11626 this is fixed in version 248 of systemd. Please make that version available to LTS 20.04.3 Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1946667/+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 1992688] Re: firefox deb not installed
I tested an Ubuntu 22.04 daily build today and can confirm that firefox deb is installed and `x-www-browser www.ubuntu.com` works. bdmurray@bdmurray-Standard-PC-Q35-ICH9-2009:~$ cat /var/log/installer/media-info Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230621)bdmurray@bdmurray-Standard-PC-Q35-ICH9-2009:~$ apt-cache policy ubuntu-desktop ubuntu-desktop: Installed: 1.481.1 Candidate: 1.481.1 Version table: *** 1.481.1 500 500 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1.481 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages bdmurray@bdmurray-Standard-PC-Q35-ICH9-2009:~$ which x-www-browser /usr/bin/x-www-browser bdmurray@bdmurray-Standard-PC-Q35-ICH9-2009:~$ apt-cache policy firefox firefox: Installed: 1:1snap1-0ubuntu2 Candidate: 1:1snap1-0ubuntu2 Version table: *** 1:1snap1-0ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status ** Description changed: Impact -- - Applications with x-www-browser to launch Firefox will not work on a freshly installed Ubuntu 22.04 system as the firefox deb is not installed. + Applications with x-www-browser configured to launch Firefox will not work on a freshly installed Ubuntu 22.04 system as the firefox deb is not installed. Test Plan - 1) Install Ubuntu 22.04.2 using an amd64 desktop iso image 2) Open a terminal 3) Run x-www-browser www.ubuntu.com 4) Observe a command not found message which recommends installing firefox Where problems could occur -- Other Info -- I tested an upgrade from Ubuntu 20.04 to Ubuntu 22.04 and the firefox deb was not removed during the upgrade process so upgrades are a non-issue. Original Description Bug 1964036 leads me to believe that the firefox deb provides some important functionality (the firefox favourite icon in the gnome shell dock) but there is nothing that would require the deb to be installed (it is not seeded nor has an rdep) and the package description indicates that it can be safely removed. Is there some important functionality that it provides? ProblemType: BugDistroRelease: Ubuntu 22.10 Package: ubuntu-release-upgrader-core 1:22.10.8 ProcVersionSignature: User Name 5.19.0-19.19-generic 5.19.7 Uname: Linux 5.19.0-19-generic x86_64 ApportVersion: 2.23.1-0ubuntu2 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Wed Oct 12 11:30:46 2022 InstallationDate: Installed on 2022-04-27 (167 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to kinetic on 2022-10-12 (0 days ago) VarLogDistupgradeTermlog: ** Description changed: Impact -- - Applications with x-www-browser configured to launch Firefox will not work on a freshly installed Ubuntu 22.04 system as the firefox deb is not installed. + Applications which use x-www-browser to launch a browser will not work on a freshly installed Ubuntu 22.04 system as the firefox deb (which provides x-www-browser) is not installed. Test Plan - 1) Install Ubuntu 22.04.2 using an amd64 desktop iso image 2) Open a terminal 3) Run x-www-browser www.ubuntu.com 4) Observe a command not found message which recommends installing firefox + + Installing of a daily build of Ubuntu 22.04 with -proposed enabled and + ubuntu-desktop will not exhibit the above problem. Where problems could occur -- Other Info -- I tested an upgrade from Ubuntu 20.04 to Ubuntu 22.04 and the firefox deb was not removed during the upgrade process so upgrades are a non-issue. Original Description Bug 1964036 leads me to believe that the firefox deb provides some important functionality (the firefox favourite icon in the gnome shell dock) but there is nothing that would require the deb to be installed (it is not seeded nor has an rdep) and the package description indicates that it can be safely removed. Is there some important functionality that it provides? ProblemType: BugDistroRelease: Ubuntu 22.10 Package: ubuntu-release-upgrader-core 1:22.10.8 ProcVersionSignature: User Name 5.19.0-19.19-generic 5.19.7 Uname: Linux 5.19.0-19-generic x86_64 ApportVersion: 2.23.1-0ubuntu2 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Wed Oct 12 11:30:46 2022 Install
[Touch-packages] [Bug 1643675] Re: hugepages for non-default pagesize need manual setup
** Changed in: systemd (Ubuntu) Importance: Undecided => Wishlist -- 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/1643675 Title: hugepages for non-default pagesize need manual setup Status in OpenStack Nova Compute Charm: Triaged Status in libvirt package in Ubuntu: Won't Fix Status in systemd package in Ubuntu: Confirmed Status in nova-compute package in Juju Charms Collection: Invalid Bug description: This is a amd64 xenial/mitaka deploy using 1607 charms release where I need to have 1G hugepages available for openstack/kvm. nova-compute charm should provide ways to ease e.g. 1G hugepages setup, currently only exposes a "hugepages" setting that ends setting vm.nr_hugepages for the node, but even after settings kernel cmdline parameters for 1G hugepages (hugepagesz=1G hugepages=128), is not usable by libvirt-bin: #1 systemd: Installs /lib/systemd/system/dev-hugepages.mount with default pagesize => no hugetblfs mount with (e.g.) pagesize=1G #2 libvirt-bin: Installs apparmor profile ("libvirt-qemu") which only allows: # for access to hugepages owner "/run/hugepages/kvm/libvirt/qemu/**" rw, owner "/dev/hugepages/libvirt/qemu/**" rw, => not possible to have other mount points for other pagesizes. I've workaround'd #1,#2 above by overriding systemd's by creating a /etc/systemd/system/dev-hugepages.mount with below extra line at [Mount] section: Options=pagesize=1G -> https://paste.ubuntu.com/23513048/ To manage notifications about this bug go to: https://bugs.launchpad.net/charm-nova-compute/+bug/1643675/+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 1456789] Re: restarting services hangs on systemd-tty-ask-password-agent
** Changed in: systemd (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1456789 Title: restarting services hangs on systemd-tty-ask-password-agent Status in systemd package in Ubuntu: Fix Released Status in systemd package in Debian: Fix Released Bug description: I have a script run as root from cron that tweaks smb.conf and restarts smbd and winbind. Problem is, starting today after working perfectly up till yesterday, this script now hangs on Ubuntu 15.04. When run from cron, the process tree looks like this: service smbd restart \_ systemctl restart smbd.service \_ /bin/systemd-tty-ask-password-agent --watch \_ /usr/bin/pkttyagent --notify-fd 5 --fallback Run from a shell via sudo, same thing except the process tree (obviously) includes the sudo command. It times out after 5 minutes, causing the script to fail. If I manually kill the processes, it fails faster. The simplest possible scripts that reproduce this, run as root or through cron or via sudo, are: #!/bin/sh service smbd restart #!/bin/sh systemctl restart smbd.service Using 'service', this works perfectly on Ubuntu 14.04 and 14.10, and until this morning worked perfectly on 15.04 as well. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Ubuntu 15.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center systemd 219-7ubuntu5 samba 2:4.1.13+dfsg-4ubuntu3 3) What you expected to happen Services to restart 4) What happened instead Services didn't restart, 'systemctl' hung To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1456789/+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 1817627] Re: systemd-analyze verify reports failure
This is fixed in Focal and newer by https://github.com/systemd/systemd/commit/114110cdf1a0ddba8238e0e10c520039281c5d6e. ** Changed in: systemd (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1817627 Title: systemd-analyze verify reports failure Status in Ubuntu Manpage Repository: Invalid Status in systemd package in Ubuntu: Fix Released Bug description: Version 237 and 238 of systemd-analyze have a known issue: https://github.com/systemd/systemd/issues/8592 When will a fix be posted? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-manpage-repository/+bug/1817627/+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 1954843] Re: amdgpu_bl0: Failed to write system 'brightness' attribute: Invalid argument
According to the last comment, this was fixed by upgrading to 22.04. ** Changed in: systemd (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1954843 Title: amdgpu_bl0: Failed to write system 'brightness' attribute: Invalid argument Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Bug description: Ubuntu 21.10 does not succeed at setting the display brightness after booting (either to the GNOME login screen or to a logged-in user's desktop). The brightness is at its highest level until I adjust it with keyboard shortcuts or a GUI tool. The systemd-backlight@backlight:amdgpu_bl0 service seems to fail during startup, but I can subsequently run it after startup and it succeeds (and restores brightness): mdmower@T14S ~ $ sudo systemctl status systemd-backlight@backlight:amdgpu_bl0 [sudo] password for mdmower: × systemd-backlight@backlight:amdgpu_bl0.service - Load/Save Screen Backlight Brightness of backlight:amdgpu_bl0 Loaded: loaded (/lib/systemd/system/systemd-backlight@.service; static) Active: failed (Result: exit-code) since Tue 2021-12-14 13:26:05 PST; 30s ago Docs: man:systemd-backlight@.service(8) Process: 962 ExecStart=/lib/systemd/systemd-backlight load backlight:amdgpu_bl0 (code=exited, status=1/FAILURE) Main PID: 962 (code=exited, status=1/FAILURE) CPU: 3ms Dec 14 13:26:05 T14S systemd[1]: Starting Load/Save Screen Backlight Brightness of backlight:amdgpu_bl0... Dec 14 13:26:05 T14S systemd-backlight[962]: amdgpu_bl0: Failed to write system 'brightness' attribute: Invalid argument Dec 14 13:26:05 T14S systemd[1]: systemd-backlight@backlight:amdgpu_bl0.service: Main process exited, code=exited, status=1/FAILURE Dec 14 13:26:05 T14S systemd[1]: systemd-backlight@backlight:amdgpu_bl0.service: Failed with result 'exit-code'. Dec 14 13:26:05 T14S systemd[1]: Failed to start Load/Save Screen Backlight Brightness of backlight:amdgpu_bl0. mdmower@T14S ~ $ sudo systemctl start systemd- backlight@backlight:amdgpu_bl0 mdmower@T14S ~ $ sudo systemctl status systemd-backlight@backlight:amdgpu_bl0 ● systemd-backlight@backlight:amdgpu_bl0.service - Load/Save Screen Backlight Brightness of backlight:amdgpu_bl0 Loaded: loaded (/lib/systemd/system/systemd-backlight@.service; static) Active: active (exited) since Tue 2021-12-14 13:26:45 PST; 1s ago Docs: man:systemd-backlight@.service(8) Process: 5119 ExecStart=/lib/systemd/systemd-backlight load backlight:amdgpu_bl0 (code=exited, status=0/SUCCESS) Main PID: 5119 (code=exited, status=0/SUCCESS) CPU: 5ms Dec 14 13:26:45 T14S systemd[1]: Starting Load/Save Screen Backlight Brightness of backlight:amdgpu_bl0... Dec 14 13:26:45 T14S systemd[1]: Finished Load/Save Screen Backlight Brightness of backlight:amdgpu_bl0. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Dec 14 13:29:38 2021 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev d1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Cezanne [17aa:5095] InstallationDate: Installed on 2021-12-12 (2 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 20XF004WUS ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=859a72cc-a3fe-470f-b525-37b151408289 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.14 dmi.bios.vendor: LENOVO dmi.bios.version: R1NET44W (1.14) dmi.board.asset.tag: Not Available dmi.board.name: 20XF004WUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.14 dmi.modalias: dmi:bvnLENOVO:bvrR1NET44W(1.14):bd11/08/2021:br1.14:efr1.14:svnLENOVO:pn20XF004WUS:pvrThinkPadT14sGen2a:rvnLENOVO:rn20XF004WUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XF_BU_Think_FM_ThinkPadT14sGen2a: dmi.product.family: ThinkPad T14s Gen 2a
[Touch-packages] [Bug 1973589] Re: Restart loop when using PathExistsGlob
I think this is to be expected since your service just does one thing and exits immediately -- when the service exists, the PathExistsGlob condition is still true, and so the service is activated again by test.path. If you had a long running service, or another condition to say "we already ran test.service, no need to run again", you would avoid this. ** Changed in: systemd (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1973589 Title: Restart loop when using PathExistsGlob Status in systemd package in Ubuntu: Invalid Bug description: When using PathExistsGlob in a path unit, systemd starts the corresponding service unit in an infinite loop. We have observed this problem only under Jammy. -- [Unit] Description=Test [Path] PathExistsGlob=/home/www-data/test/*.so Unit=test.service [Install] WantedBy=multi-user.target -- [Unit] Description=Test [Service] Type=simple ExecStart=echo test StartLimitBurst=1000 [Install] WantedBy=multi-user.target - www-data@josi-test-jammy03:~ $ systemctl --user status test.path × test.path - Test Loaded: loaded (/home/www-data/.config/systemd/user/test.path; disabled; vendor preset: enabled) Active: failed (Result: unit-start-limit-hit) since Mon 2022-05-16 17:08:08 CEST; 121ms ago Triggers: ● test.service May 16 17:08:04 josi-test-jammy03 systemd[24979]: Started Test May 16 17:08:08 josi-test-jammy03 systemd[24979]: test.path: Failed with result 'unit-start-limit-hit'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1973589/+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 1945288] Re: Search domains missing from resolv.conf stub
This restriction was dropped upstream by https://github.com/systemd/systemd/commit/1c7466aa2e5663b5595f9cef5cbece9ec63bcc14, which is included in 22.04 and later releases. ** Changed in: systemd (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1945288 Title: Search domains missing from resolv.conf stub Status in systemd package in Ubuntu: Fix Released Bug description: System is Mint 20.2, with the relevant packages taken from Ubuntu Focal. This is the output of `systemd-resolv --status vpn0`: Link 7 (vpn0) Current Scopes: DNS DefaultRoute setting: yes LLMNR setting: yes MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no Current DNS Server: 10.0.0.53 DNS Servers: 10.0.0.53 DNS Domain: example.com example.com.rpz privatelink.blob.core.windows.net node.prd.lan.example.com node.stg.lan.example.com node.dev.lan.example.com However that last domain is missing from `/etc/resolv.conf` (symlink to `/run/systemd/resolve/stub-resolv.conf`), instead there is a line # Too many search domains configured, remaining ones ignored. According to resolv.conf(5) since glibc 2.26 the number of search domains should be unlimited, and installed is 2.31-0ubuntu9.3 VPN is PaloAlto GlobalProtect through the OpenConnect plugin on NetworkManager. Exact same setup and behaviour for a colleague using Pop!_OS 20.04 -- systemd: Installed: 245.4-4ubuntu3.13 Candidate: 245.4-4ubuntu3.13 Version table: *** 245.4-4ubuntu3.13 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 245.4-4ubuntu3.11 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 245.4-4ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages libc-bin: Installed: 2.31-0ubuntu9.3 Candidate: 2.31-0ubuntu9.3 Version table: *** 2.31-0ubuntu9.3 100 100 /var/lib/dpkg/status 2.31-0ubuntu9.2 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 2.31-0ubuntu9 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1945288/+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 1980679] Re: Suspend on focal takes 30s.
Is this still an issue? If so, what does the output of systemd-inhibit show? Please also attach logs from journalctl from the time between suspend is initiated, to the time it actually takes place. Finally, if you have any changes to logind's config, that would be good to know: $ systemd-analyze cat-config systemd/logind.conf ** Changed in: systemd (Ubuntu) Status: Confirmed => Incomplete ** Changed in: systemd (Ubuntu) Importance: Undecided => Low -- 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/1980679 Title: Suspend on focal takes 30s. Status in systemd package in Ubuntu: Incomplete Bug description: Just upgrades my NUC from Bionic to Focal and suspend went from immediate (within a couple seconds) to taking a whole 30 seconds. While suspend is happening, the machine is still usable, mouse moves, applications respond, all the way until the machine actually goes to sleep. I don't see anything strange in kern.log that would explain the slowness: Jul 4 08:44:55 domi kernel: [342379.045479] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Jul 4 08:44:55 domi kernel: [342379.048878] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Jul 4 08:44:55 domi kernel: [342379.049670] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Jul 4 08:44:56 domi kernel: [342379.966129] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Jul 4 08:44:56 domi kernel: [342379.971410] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Jul 4 08:45:27 domi kernel: [342410.725869] PM: suspend entry (s2idle) Jul 4 08:45:32 domi kernel: [342410.749912] Filesystems sync: 0.024 seconds Jul 4 08:45:32 domi kernel: [342410.751470] Freezing user space processes ... (elapsed 0.002 seconds) done. Jul 4 08:45:32 domi kernel: [342410.753907] OOM killer disabled. Jul 4 08:45:32 domi kernel: [342410.753907] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. Jul 4 08:45:32 domi kernel: [342410.755259] printk: Suspending console(s) (use no_console_suspend to debug) Jul 4 08:45:32 domi kernel: [342410.755948] e1000e: EEE TX LPI TIMER: 0011 Jul 4 08:45:32 domi kernel: [342410.812587] sd 2:0:0:0: [sdb] Synchronizing SCSI cache Jul 4 08:45:32 domi kernel: [342410.812607] sd 1:0:0:0: [sda] Synchronizing SCSI cache Jul 4 08:45:32 domi kernel: [342410.812708] sd 2:0:0:0: [sdb] Stopping disk Jul 4 08:45:32 domi kernel: [342410.816870] sd 1:0:0:0: [sda] Stopping disk Jul 4 08:45:32 domi kernel: [342411.080056] ACPI: EC: interrupt blocked Jul 4 08:45:32 domi kernel: [342415.597918] ACPI: EC: interrupt unblocked There does look to be 30s between the last "Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7" and "PM: suspend entry (s2idle)" This is mostly a frustration, but could be a security issue for some if they suspend the machine and walk away thinking it would be locked but is usable for another 30s. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-121-generic 5.4.0-121.137 ProcVersionSignature: Ubuntu 5.4.0-121.137-generic 5.4.189 Uname: Linux 5.4.0-121-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bbogart1033 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Mon Jul 4 08:43:09 2022 InstallationDate: Installed on 2019-02-09 (1241 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Intel(R) Client Systems NUC8i3BEH ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-121-generic root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-121-generic N/A linux-backports-modules-5.4.0-121-generic N/A linux-firmware 1.187.31 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2022-06-30 (4 days ago) dmi.bios.date: 10/15/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0051.2018.1015.1513 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-304 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0051.2018.1015.1513:bd10/15/2018:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.sku: BOXNUC8i3BEH dmi.product.version: J72753-303 dmi.sys.vendor: Intel(R) Client Systems To
[Touch-packages] [Bug 1983758] Re: systemd-cryptenroll does not support PKCS#11 tokens
p11kit is enabled in Lunar and newer, but I don't think this will be SRU'd to Jammy. ** Changed in: systemd (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1983758 Title: systemd-cryptenroll does not support PKCS#11 tokens Status in systemd package in Ubuntu: Fix Released Bug description: linux 5.19.0-13-generic #13-Ubuntu SMP PREEMPT_DYNAMIC Thu Jul 28 15:28:43 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux systemd 249.11-0ubuntu3.4 ykman piv keys generate --algorithm ECCP256 9a pubkey.pem Enter a management key [blank to use default key]: ykman piv certificates generate --subject "PKCS#11" 9a pubkey.pem Enter a management key [blank to use default key]: Enter PIN: ** systemd-cryptenroll --pkcs11-token-uri=auto /dev/sda5 PKCS#11 tokens not supported on this build. where /dev/sda5 is luks-encrypted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1983758/+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 1934393] Re: systemd-logind network access is blocked, and breaks remote authentication configurations
** Changed in: systemd (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1934393 Title: systemd-logind network access is blocked, and breaks remote authentication configurations Status in systemd: Fix Released Status in nis package in Ubuntu: Confirmed Status in openldap package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Won't Fix Status in nis package in Debian: Fix Released Bug description: [impact] starting in focal, systemd-logind runs sandboxed without any network access, which breaks any configuration that uses remote servers for user data, e.g. ldap, nis, etc A more full discussion is available in the upstream bug report as well as the debian bug report, see other info section below [test case] many possible ways to reproduce this; there are reproducers in some of the bugs reported before that are caused by this, e.g. bug 1915502 or bug 1916235 [regression potential] failure to authenticate when using remote user data, incorrect authentication, security issues due to un-sandboxing of systemd-logind [scope] this is needed in f and later before focal, systemd-logind was not sandboxed so this did not apply [other info] this isn't actually a bug in systemd, this is a by-design security feature; see links below (and/or comment 13 in this bug) to upstream comments about how systemd's position is that no NSS module should ever perform network access, and any NSS module that does needs to also adjust the restrictions of systemd services such as systemd-logind, systemd-userdbd, and possibly others that might need to make NSS calls into glibc. https://github.com/systemd/systemd/issues/7074#issuecomment-338157851 https://github.com/systemd/systemd/issues/15705#issuecomment-624125354 this may also can cause systemd-udevd failures in some cases as well. https://github.com/systemd/systemd/pull/7343#issuecomment-344800313 For reference, upstream discussion around the systemd-logind sandboxing specifically: https://github.com/systemd/systemd/issues/7074 upstream updated doc PR explaining the upstream position: https://github.com/systemd/systemd/pull/7343 Debian bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878625 Note that while this Debian bug is marked as fix released, I don't think it actually fixes the problem, from the final comment it seems like the only change was to add Recommends: nscd, which doesn't really solve things if someone doesn't use nscd. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1934393/+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 2009699] Re: sytemd-udev package upgrade breaks if udev is masked
** Changed in: systemd (Ubuntu) Importance: Undecided => Low -- 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/2009699 Title: sytemd-udev package upgrade breaks if udev is masked Status in systemd package in Ubuntu: Confirmed Bug description: The Anbox Cloud LXD images are based of the standard Ubuntu cloud images for LXD but have the systemd-udevd.service unit masked (`systemctl mask systemd-udevd.service`) as we do not need udev. With the latest security patch on Ubuntu 22.04 upgrading the udev package fails: ... Mar 07 21:33:48 ams-cg3qqttdjmctnqegcqag sh[753]: left to upgrade {'udev', 'libudev1'} Mar 07 21:33:48 ams-cg3qqttdjmctnqegcqag sh[753]: applying set ['udev', 'libudev1'] Mar 07 21:33:48 ams-cg3qqttdjmctnqegcqag sh[753]: Log ended: 2023-03-07 21:33:47 Mar 07 21:33:48 ams-cg3qqttdjmctnqegcqag sh[753]: Log started: 2023-03-07 21:33:48 Mar 07 21:33:48 ams-cg3qqttdjmctnqegcqag sh[753]: [614B blob data] Mar 07 21:33:48 ams-cg3qqttdjmctnqegcqag sh[753]: Preparing to unpack .../udev_249.11-0ubuntu3.7_arm64.deb ... Mar 07 21:33:48 ams-cg3qqttdjmctnqegcqag sh[753]: Unpacking udev (249.11-0ubuntu3.7) over (249.11-0ubuntu3.6) ... Mar 07 21:33:49 ams-cg3qqttdjmctnqegcqag sh[753]: Preparing to unpack .../libudev1_249.11-0ubuntu3.7_arm64.deb ... Mar 07 21:33:49 ams-cg3qqttdjmctnqegcqag sh[753]: Unpacking libudev1:arm64 (249.11-0ubuntu3.7) over (249.11-0ubuntu3.6) ... Mar 07 21:33:49 ams-cg3qqttdjmctnqegcqag sh[753]: Setting up libudev1:arm64 (249.11-0ubuntu3.7) ... Mar 07 21:33:49 ams-cg3qqttdjmctnqegcqag sh[753]: Setting up udev (249.11-0ubuntu3.7) ... Mar 07 21:33:49 ams-cg3qqttdjmctnqegcqag systemd[1]: Reloading. Mar 07 21:33:49 ams-cg3qqttdjmctnqegcqag sh[753]: Failed to restart udev.service: Unit udev.service failed to load properly, please adjust/correct and reload service manager: File exists Mar 07 21:33:49 ams-cg3qqttdjmctnqegcqag sh[753]: See system logs and 'systemctl status udev.service' for details. Mar 07 21:33:49 ams-cg3qqttdjmctnqegcqag sh[753]: invoke-rc.d: initscript udev, action "restart" failed. We can workaround this by doing a patch release to our users next week but it would be a lot better if the package scripts check if the service unit is masked and if it is avoid restarting udev.service The problem isn't introduced with the 249.11-0ubuntu3.7 but should exist for longer already. It just became a problem for us due to the security patch rolling in via unattended-upgrades To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2009699/+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 1933880] Re: systemd-logind crash when suspend with nvidia-suspend.service masked, bringing session down with it
Based on the workaround, it seems that the problem is with nvidia systemd units, and not systemd itself. ** Changed in: systemd (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1933880 Title: systemd-logind crash when suspend with nvidia-suspend.service masked, bringing session down with it Status in nvidia-graphics-drivers-465 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Bug description: Steps to reproduce: 1. Run `sudo apt install nvidia-driver-465`. Then, without a need for a restart, run `sudo apt autoremove nvidia-driver-465`. 2. Leaving the terminal open, suspend the machine. Expected behavior: the machine suspend successfully and can be woken up successfully. Actual behavior: the machine doesn't suspend. It either: - hang with no respond other than SysRq+REISUB (or maybe network, but I didn't test), or - return you back to the login screen. Upon logging in, you'll notice that the terminal you opened is gone. Upon further inspection (on a session that doesn't hang), it's been found that X server died with: Fatal server error: [66.422] (EE) systemd-logind disappeared (stopped/restarted?) And checking journal for systemd-logind log, it said: Error during inhibitor-delayed operation (already returned success to client): Unit nvidia-suspend.service is masked. before the new process takes it place. The system is Ubuntu 20.04, X.org session. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.7 ProcVersionSignature: Ubuntu 5.11.0-22.23~20.04.1-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jun 29 03:34:00 2021 InstallationDate: Installed on 2021-03-15 (105 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=th_TH.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic root=UUID=06f2a676-a62c-443a-8bc8-4e0eda4600f4 ro log_buf_len=2M quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/01/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN31WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55756 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.ec.firmware.release: 1.31 dmi.modalias: dmi:bvnLENOVO:bvrEUCN31WW:bd01/01/2021:br1.31:efr1.31:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55756WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05: dmi.product.family: Legion 5 15ARH05 dmi.product.name: 82B5 dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05 dmi.product.version: Lenovo Legion 5 15ARH05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-465/+bug/1933880/+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 1997124] Re: Netplan/Systemd/Cloud-init/Dbus Race
** Changed in: systemd (Ubuntu) Status: Confirmed => Triaged ** Changed in: systemd (Ubuntu) Importance: Undecided => Wishlist -- 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/1997124 Title: Netplan/Systemd/Cloud-init/Dbus Race Status in cloud-init: Expired Status in netplan: Triaged Status in systemd package in Ubuntu: Triaged Bug description: Cloud-init is seeing intermittent failures while running `netplan apply`, which appears to be caused by a missing resource at the time of call. The symptom in cloud-init logs looks like: Running ['netplan', 'apply'] resulted in stderr output: Failed to connect system bus: No such file or directory I think that this error[1] is likely caused by cloud-init running netplan apply too early in boot process (before dbus is active). Today I stumbled upon this error which was hit in MAAS[2]. We have also hit it intermittently during tests (we didn't have a reproducer). Realizing that this may not be a cloud-init error, but possibly a dependency bug between dbus/systemd we decided to file this bug for broader visibility to other projects. I will follow up this initial report with some comments from our discussion earlier. [1] https://github.com/canonical/netplan/blob/main/src/dbus.c#L801 [2] https://discourse.maas.io/t/latest-ubuntu-20-04-image-causing-netplan-error/5970 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1997124/+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 2007529] Re: package slapd 2.4.49+dfsg-2ubuntu1.9 failed to install/upgrade: installed slapd package post-installation script subprocess returned error exit status 1
Thank you very much for the quick reply, Oleksii. >From what you describe, it really seems like this was a local configuration issue, possibly with some other component from your system. I will close this bug as Invalid based on that observation, but feel free to reopen it if you encounter the problem again. Thanks! ** Changed in: openldap (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/2007529 Title: package slapd 2.4.49+dfsg-2ubuntu1.9 failed to install/upgrade: installed slapd package post-installation script subprocess returned error exit status 1 Status in openldap package in Ubuntu: Invalid Bug description: The system asked me to send a report about a failure. Here it is. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: slapd 2.4.49+dfsg-2ubuntu1.9 ProcVersionSignature: Ubuntu 5.15.0-60.66~20.04.1-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 AptOrdering: gir1.2-webkit2-4.0:amd64: Install gir1.2-javascriptcoregtk-4.0:amd64: Install NULL: ConfigurePending Architecture: amd64 CNConfig: Error: command ['/usr/bin/ldapsearch', '-Q', '-LLL', '-Y EXTERNAL', '-H ldapi:///', '-b cn=config'] failed with exit code 255: ldap_sasl_interactive_bind_s: Can't contact LDAP server (-1) CasperMD5CheckResult: skip Date: Wed Feb 15 06:54:50 2023 ErrorMessage: installed slapd package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-02-20 (360 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-60-generic root=UUID=02b06a5b-7026-48f6-9745-993e04e5aba6 ro quiet splash Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: openldap Title: package slapd 2.4.49+dfsg-2ubuntu1.9 failed to install/upgrade: installed slapd package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.default.slapd: 2022-10-24T00:13:25.321836 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/2007529/+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 2024618] [NEW] In some boots, screen display is totally black possible i915 issue
Public bug reported: Hi, In some boots my laptop's graphic card(Intel Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx) only display a black screen, everything else seems to work, the system is able to produce sounds. Its possible to make the display go back to work after close and open the lid. After some tests and debug, it was seen that the screen wasn't entirely black the brightness seems to be setted to the minimum(almost impossible to see), and with a external monitor the brightness level was checked in `/sys/class/backlight/intel_backlight/actual_brightness` it was set to the default value, so the problem can't be the backlight. I believe is a i915 driver problem. it was tested the following kernel's params: i915.enable_dpcd_backlight=3 i915.enable_dpcd_backlight=1 i915.enable_dpcd_backlight=0 i915.invert_brightness=1 i915.invert_brightness=-1 i915.modeset=0 i915.modeset=1 i915.register_backlight=1 Still no results. Distributor ID: Ubuntu Description: Ubuntu 23.04 Release: 23.04 Codename: lunar xorg: Installed: 1:7.7+23ubuntu2 Candidate: 1:7.7+23ubuntu2 Version table: *** 1:7.7+23ubuntu2 500 500 http://br.archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-23.23-generic 6.2.12 Uname: Linux 6.2.0-23-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jun 21 16:03:20 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] InstallationDate: Installed on 2023-06-21 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:b720 Realtek Semiconductor Corp. RTL8723BU 802.11b/g/n WLAN Adapter Bus 001 Device 002: ID 0bda:5830 Realtek Semiconductor Corp. MTD camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Compaq 420 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-23-generic root=UUID=774e3ecb-1e91-4c0e-8036-66b475c7f433 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 126: Error executing command as another user: Request dismissed dmi.bios.date: 09/27/2021 dmi.bios.release: 5.11 dmi.bios.version: V1.13.X dmi.board.asset.tag: Default string dmi.board.name: N14JP6-V2 dmi.board.vendor: Compaq dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Compaq dmi.chassis.version: Default string dmi.ec.firmware.release: 1.0 dmi.modalias: dmi:bvn:bvrV1.13.X:bd09/27/2021:br5.11:efr1.0:svnCompaq:pn420:pvrDefaultstring:rvnCompaq:rnN14JP6-V2:rvr:cvnCompaq:ct10:cvrDefaultstring:skuDefaultstring: dmi.product.family: Presario dmi.product.name: 420 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Compaq version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar ubuntu wayland-session ** Description changed: - Hi, - In some boots my laptopt graphic card(Intel Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx) only display a black screen, everything else seems to work, the system is able to produce sounds. Its possible to make the display go back to work after close and open the lid. After some tests and debug, it was seen that the screen wasn't entirely black the brightness seems to be setted to the minimum(almost impossible to see), and with a external monitor the brightness level was checked in `/sys/class/backlight/intel_backlight/actual_brightness` it was set to the default value, so the problem can't be the backlight. I believe is a i915 driver
[Touch-packages] [Bug 1992688] Re: firefox deb not installed
** Description changed: - Bug 1964036 leads me to believe that the firefox deb provides some - important functionality (the firefox favourite icon in the gnome shell - dock) but there is nothing that would require the deb to be installed - (it is not seeded nor has an rdep) and the package description indicates - that it can be safely removed. Is there some important functionality - that it provides? + Impact + -- + Applications with x-www-browser to launch Firefox will not work on a freshly installed Ubuntu 22.04 system as the firefox deb is not installed. + + Test Plan + - + 1) Install Ubuntu 22.04.2 using an amd64 desktop iso image + 2) Open a terminal + 3) Run x-www-browser www.ubuntu.com + 4) Observe a command not found message which recommends installing firefox + + Where problems could occur + -- + + Other Info + -- + I tested an upgrade from Ubuntu 20.04 to Ubuntu 22.04 and the firefox deb was not removed during the upgrade process so upgrades are a non-issue. + + Original Description + + Bug 1964036 leads me to believe that the firefox deb provides some important functionality (the firefox favourite icon in the gnome shell dock) but there is nothing that would require the deb to be installed (it is not seeded nor has an rdep) and the package description indicates that it can be safely removed. Is there some important functionality that it provides? ProblemType: BugDistroRelease: Ubuntu 22.10 Package: ubuntu-release-upgrader-core 1:22.10.8 ProcVersionSignature: User Name 5.19.0-19.19-generic 5.19.7 Uname: Linux 5.19.0-19-generic x86_64 ApportVersion: 2.23.1-0ubuntu2 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Wed Oct 12 11:30:46 2022 InstallationDate: Installed on 2022-04-27 (167 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to kinetic on 2022-10-12 (0 days ago) VarLogDistupgradeTermlog: -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1992688 Title: firefox deb not installed Status in firefox package in Ubuntu: Invalid Status in ubuntu-meta package in Ubuntu: Fix Released Status in firefox source package in Jammy: Invalid Status in ubuntu-meta source package in Jammy: Fix Committed Bug description: Impact -- Applications with x-www-browser to launch Firefox will not work on a freshly installed Ubuntu 22.04 system as the firefox deb is not installed. Test Plan - 1) Install Ubuntu 22.04.2 using an amd64 desktop iso image 2) Open a terminal 3) Run x-www-browser www.ubuntu.com 4) Observe a command not found message which recommends installing firefox Where problems could occur -- Other Info -- I tested an upgrade from Ubuntu 20.04 to Ubuntu 22.04 and the firefox deb was not removed during the upgrade process so upgrades are a non-issue. Original Description Bug 1964036 leads me to believe that the firefox deb provides some important functionality (the firefox favourite icon in the gnome shell dock) but there is nothing that would require the deb to be installed (it is not seeded nor has an rdep) and the package description indicates that it can be safely removed. Is there some important functionality that it provides? ProblemType: BugDistroRelease: Ubuntu 22.10 Package: ubuntu-release-upgrader-core 1:22.10.8 ProcVersionSignature: User Name 5.19.0-19.19-generic 5.19.7 Uname: Linux 5.19.0-19-generic x86_64 ApportVersion: 2.23.1-0ubuntu2 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Wed Oct 12 11:30:46 2022 InstallationDate: Installed on 2022-04-27 (167 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to kinetic on 2022-10-12 (0 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1992688/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help
[Touch-packages] [Bug 2007529] Re: package slapd 2.4.49+dfsg-2ubuntu1.9 failed to install/upgrade: installed slapd package post-installation script subprocess returned error exit status 1
Hello Sergio, Thanks a lot for your attention to my ticket, I really appreciate it (I mean it). Unfortunately, the system with the issue is gone: it was a VM inside VirtualBox and after I moved on a new project I has not only remove the VM but reinstall the host system from scratch. So it is impossible to check it anymore. The one thing I remember though, the issue was being reproduced every time I installed new software with apt-get install. The software installed ok, but the error message were persisting. I hope this information couldsomehow help in order someone encounter it in the future. Best regards, Oleksii -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/2007529 Title: package slapd 2.4.49+dfsg-2ubuntu1.9 failed to install/upgrade: installed slapd package post-installation script subprocess returned error exit status 1 Status in openldap package in Ubuntu: Incomplete Bug description: The system asked me to send a report about a failure. Here it is. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: slapd 2.4.49+dfsg-2ubuntu1.9 ProcVersionSignature: Ubuntu 5.15.0-60.66~20.04.1-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 AptOrdering: gir1.2-webkit2-4.0:amd64: Install gir1.2-javascriptcoregtk-4.0:amd64: Install NULL: ConfigurePending Architecture: amd64 CNConfig: Error: command ['/usr/bin/ldapsearch', '-Q', '-LLL', '-Y EXTERNAL', '-H ldapi:///', '-b cn=config'] failed with exit code 255: ldap_sasl_interactive_bind_s: Can't contact LDAP server (-1) CasperMD5CheckResult: skip Date: Wed Feb 15 06:54:50 2023 ErrorMessage: installed slapd package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-02-20 (360 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-60-generic root=UUID=02b06a5b-7026-48f6-9745-993e04e5aba6 ro quiet splash Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: openldap Title: package slapd 2.4.49+dfsg-2ubuntu1.9 failed to install/upgrade: installed slapd package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.default.slapd: 2022-10-24T00:13:25.321836 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/2007529/+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 1869796] Re: vague error during upgrade
** Changed in: systemd Status: Unknown => New -- 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/1869796 Title: vague error during upgrade Status in systemd: New Status in debhelper package in Ubuntu: New Status in libvirt package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Confirmed Status in debhelper package in Debian: Confirmed Bug description: Seen from today's apt upgrade on focal: Setting up libvirt-daemon-driver-qemu (6.0.0-0ubuntu6) ... Setting up libvirt-daemon (6.0.0-0ubuntu6) ... Setting up libvirt-daemon-driver-storage-rbd (6.0.0-0ubuntu6) ... Setting up libvirt-daemon-driver-storage-zfs (6.0.0-0ubuntu6) ... Setting up libvirt-daemon-system (6.0.0-0ubuntu6) ... Job failed. See "journalctl -xe" for details. virtlockd.service is a disabled or a static unit, not starting it. virtlogd.service is a disabled or a static unit, not starting it. Setting up libvirt-daemon dnsmasq configuration. Sadly 'journactl -xe' was useless. (It only showed a thousand unrelated lines.) A raw journalctl took forever to run long enough to let me see it generated two million lines of output, and started about two years ago, that I'm not keen on trying to run that through less or similar. Advice accepted. systemctl status looks good enough though: $ systemctl status 'libvirt*' ● libvirtd.socket - Libvirt local socket Loaded: loaded (/lib/systemd/system/libvirtd.socket; enabled; vendor preset: enabled) Active: active (running) since Mon 2020-03-30 20:44:55 UTC; 6min ago Triggers: ● libvirtd.service Listen: /run/libvirt/libvirt-sock (Stream) Tasks: 0 (limit: 18814) Memory: 0B CGroup: /system.slice/libvirtd.socket Mar 30 20:44:55 millbarge systemd[1]: Listening on Libvirt local socket. ● libvirtd.service - Virtualization daemon Loaded: loaded (/lib/systemd/system/libvirtd.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2020-03-30 20:44:55 UTC; 6min ago TriggeredBy: ● libvirtd-admin.socket ● libvirtd.socket ● libvirtd-ro.socket Docs: man:libvirtd(8) https://libvirt.org Main PID: 3646435 (libvirtd) Tasks: 19 (limit: 32768) Memory: 26.9M CGroup: /system.slice/libvirtd.service ├─ 3054 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper ├─ 3055 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper └─3646435 /usr/sbin/libvirtd Mar 30 20:44:55 millbarge systemd[1]: Starting Virtualization daemon... Mar 30 20:44:55 millbarge systemd[1]: Started Virtualization daemon. Mar 30 20:44:55 millbarge dnsmasq[3054]: read /etc/hosts - 7 addresses Mar 30 20:44:55 millbarge dnsmasq[3054]: read /var/lib/libvirt/dnsmasq/default.addnhosts - 0 addresses Mar 30 20:44:55 millbarge dnsmasq-dhcp[3054]: read /var/lib/libvirt/dnsmasq/default.hostsfile ● libvirtd-admin.socket - Libvirt admin socket Loaded: loaded (/lib/systemd/system/libvirtd-admin.socket; enabled; vendor preset: enabled) Active: active (running) since Mon 2020-03-30 20:44:55 UTC; 6min ago Triggers: ● libvirtd.service Listen: /run/libvirt/libvirt-admin-sock (Stream) Tasks: 0 (limit: 18814) Memory: 0B CGroup: /system.slice/libvirtd-admin.socket Mar 30 20:44:55 millbarge systemd[1]: Listening on Libvirt admin socket. ● libvirt-guests.service - Suspend/Resume Running libvirt Guests Loaded: loaded (/lib/systemd/system/libvirt-guests.service; enabled; vendor preset: enabled) Active: active (exited) since Wed 2020-03-25 00:41:47 UTC; 5 days ago Docs: man:libvirtd(8) https://libvirt.org Main PID: 2808 (code=exited, status=0/SUCCESS) Tasks: 0 (limit: 18814) Memory: 0B CGroup: /system.slice/libvirt-guests.service Mar 25 00:41:47 millbarge systemd[1]: Starting Suspend/Resume Running libvirt Guests... Mar 25 00:41:47 millbarge systemd[1]: Finished Suspend/Resume Running libvirt Guests. ● libvirtd-ro.socket - Libvirt local read-only socket Loaded: loaded (/lib/systemd/system/libvirtd-ro.socket; enabled; vendor preset: enabled) Active: active (running) since Mon 2020-03-30 20:44:55 UTC; 6min ago Triggers: ● libvirtd.service Listen: /run/libvirt/libvirt-sock-ro (Stream) Tasks: 0 (limit: 18814) Memory: 0B CGroup: /system.slice/libvirtd-ro.socket Mar 30 20:44:55 millbarge systemd[1]: Listening on Libvirt local read- only socket. Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package:
[Touch-packages] [Bug 2024617] [NEW] [Latitude E6430, IDT 92HD93BXX, Mic, Internal] No sound at all
Public bug reported: Inbuilt Microphone input is not working at all. Trying to enable through alsamixer has no effect and no sound is recorded. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-45.46~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tsharma8300 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: LXQt Date: Wed Jun 21 23:34:58 2023 InstallationDate: Installed on 2022-07-17 (339 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tsharma8300 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [Latitude E6430, IDT 92HD93BXX, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2018 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A23 dmi.board.name: 0CPWYR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA23:bd11/30/2018:br4.6:svnDellInc.:pnLatitudeE6430:pvr01:rvnDellInc.:rn0CPWYR:rvrA00:cvnDellInc.:ct9:cvr:skuLatitudeE6430: dmi.product.name: Latitude E6430 dmi.product.sku: Latitude E6430 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2024617 Title: [Latitude E6430, IDT 92HD93BXX, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Inbuilt Microphone input is not working at all. Trying to enable through alsamixer has no effect and no sound is recorded. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-45.46~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tsharma8300 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: LXQt Date: Wed Jun 21 23:34:58 2023 InstallationDate: Installed on 2022-07-17 (339 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tsharma8300 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [Latitude E6430, IDT 92HD93BXX, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2018 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A23 dmi.board.name: 0CPWYR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA23:bd11/30/2018:br4.6:svnDellInc.:pnLatitudeE6430:pvr01:rvnDellInc.:rn0CPWYR:rvrA00:cvnDellInc.:ct9:cvr:skuLatitudeE6430: dmi.product.name: Latitude E6430 dmi.product.sku: Latitude E6430 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2024617/+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 1892225] Re: apport-gtk consumes 100% CPU for way too long after something crashes
I have the same issue on Ubuntu 22.04.2, `apport-gtk` version is 2.20.11. There are 4 process of `apport-gtk` running currently and they are running for days already, taking all processing power they can. I have tried to clean up the `/var/crash` directory (simply deleting all files there - crash dump and upload files), but it didn't help, so I have also killed all those four processor-hungry processes. After that, all other apport processes (about 10 to 15 of them) ended themselves and so far nothing has started again. I'll observe the issue further. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1892225 Title: apport-gtk consumes 100% CPU for way too long after something crashes Status in apport package in Ubuntu: Confirmed Bug description: Something (related to Cinnamon) crashes, so the usual popup appears telling me that something crashed, and asking me whether I wanted to send a report. I choose Send. Every time this happens, then a process called apport-gtk starts consuming 100% CPU and it goes on for several minutes, so long that I end up killing it. There's no way there is a good reason for consuming so much CPU for so long. If you need to do such an amount of processing just to generate and send a bug report, something is deeply broken. But if the operation actually had to be that computationally expensive, then you must do it in a less intensive way so that it can go on in the background, for no matter how long, without rendering me unable to use my computer. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apport 2.20.11-0ubuntu27.4 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia ApportLog: ERROR: apport (pid 2908) Wed Aug 19 18:39:29 2020: called for pid 2405, signal 11, core limit 0, dump mode 1 ERROR: apport (pid 2908) Wed Aug 19 18:39:29 2020: executable: /usr/bin/cinnamon (command line "cinnamon --replace") ERROR: apport (pid 2908) Wed Aug 19 18:39:29 2020: debug: session gdbus call: (true,) ERROR: apport (pid 2908) Wed Aug 19 18:39:34 2020: wrote report /var/crash/_usr_bin_cinnamon.1000.crash ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CrashReports: 640:1000:110:69556:2020-08-19 18:39:33.732794284 +0200:2020-08-19 18:39:34.732794284 +0200:/var/crash/_usr_bin_cinnamon-launcher.1000.crash 640:1000:110:15432562:2020-08-19 18:39:34.466977487 +0200:2020-08-19 18:42:42.722667813 +0200:/var/crash/_usr_bin_cinnamon.1000.crash CurrentDesktop: X-Cinnamon Date: Wed Aug 19 18:42:34 2020 InstallationDate: Installed on 2013-10-11 (2503 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to focal on 2020-07-12 (37 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1892225/+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 1627769] Re: limits.conf not applied
Please re-open if this is still an issue in newer releases. ** Changed in: systemd (Ubuntu) Status: Confirmed => Invalid -- 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/1627769 Title: limits.conf not applied Status in jackd2 package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Bug description: Since upgraded to 16.10 Yakkety, modifications in /etc/security/limits.conf are not taken into consideration when logging in the graphical interface. /etc/security/limits.conf: @audio - rtprio 99 @audio - memlockunlimited I tried the same settings in /etc/security/limits.d/audio.conf, to the same results. After logging in Unity, opening a console, the limits are not set: blablack@ideaon:~$ ulimit -l -r max locked memory (kbytes, -l) 64 real-time priority (-r) 0 Reloging to my user via bash DOES apply the limits: blablack@ideaon:~$ ulimit -l -r max locked memory (kbytes, -l) 64 real-time priority (-r) 0 blablack@ideaon:~$ su blablack Password: blablack@ideaon:~$ ulimit -l -r max locked memory (kbytes, -l) unlimited real-time priority (-r) 95 Switching to a console (ctrl+alt+f1) and logging in would apply the limits as well. The exact same setup used to work fine on Xenial 16.04 before upgrade. If you need any more information, please let me know. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: lightdm 1.19.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7 Uname: Linux 4.8.0-16-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Mon Sep 26 17:27:10 2016 SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1627769/+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 1726124] Re: DNS domain search paths not updated when VPN started
** Changed in: systemd (Ubuntu) Importance: High => Low -- 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/1726124 Title: DNS domain search paths not updated when VPN started Status in network-manager package in Ubuntu: Confirmed Status in network-manager-openvpn package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: I connect to work with openvpn through network-manager-openvpn. I'm selecting automatic (DHCP) to get an IP address, and "Use this connection only for resources on its network" to support split tunneling. In the last few versions of Ubuntu I used, this all worked fine. In Ubuntu 17.10 (fresh install, not upgrade) I can access hosts on both my VPN network and the internet, BUT I have to use FQDN for my VPN network hosts: the updates to the DNS search path provided by my VPN DHCP server are never being applied. Investigating the system I see that /etc/resolv.conf is pointing to /run/systemd/resolve/stub-resolv.conf and that resolv.conf does not have any of the VPN's search path settings in it: # This file is managed by man:systemd-resolved(8). Do not edit. # # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 127.0.0.53 search home In previous versions of Ubuntu, where NetworkManager controlled the resolver not systemd, /etc/resolv.conf pointed to /run/NetworkManager/resolv.conf and there was a local dnsmasq instance that managed all the complexity. In Ubuntu 17.10 when I look in /run/NetworkManager/resolv.conf file, I see that the search paths ARE properly updated there: $ cat /run/NetworkManager/resolv.conf # Generated by NetworkManager search internal.mycorp.com other.mycorp.com home nameserver 127.0.1.1 However this file isn't being used, and also there's no dnsmasq running on the system so if I switch my /etc/resolv.conf to point to this file instead, then all lookups fail. Strangely, if I look at the systemd-resolv status I see that in theory systemd-resolve does seem to know about the proper search paths: $ systemd-resolve --status ... Link 3 (tun0) Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6 LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 10.3.0.10 10.8.42.2 DNS Domain: ~internal.mycorp.com ~other.mycorp.com but for whatever reason the search domains are not getting put into the resolv.conf file: $ host mydesk ;; connection timed out; no servers could be reached $ host mydesk.internal.mycorp.com mydesk.internal.mycorp.com has address 10.8.37.74 (BTW, the timeout in the failed attempt above takes 10s: it is SUPER frustrating when all your host lookups are taking that long just to fail). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu12 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Oct 22 15:08:57 2017 InstallationDate: Installed on 2017-10-21 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic root=UUID=4384306c-5fed-4b48-97a6-a6d594c4f72b ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2101 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L-M/USB3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2101:bd12/02/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-M/USB3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System
[Touch-packages] [Bug 1839231] Re: (re)starting networkd removes still-valid RFC 4941 ipv6 addrs
Please re-open if this is still an issue on newer releases. ** Changed in: systemd (Ubuntu) Status: Confirmed => Won't Fix -- 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/1839231 Title: (re)starting networkd removes still-valid RFC 4941 ipv6 addrs Status in systemd package in Ubuntu: Won't Fix Bug description: I updated my Ubuntu 18.04.2 server from systemd 237-3ubuntu10.24 to 237-3ubuntu10.25. This caused a restart of systemd-networkd, breaking all TCP-over-IPv6 connections. apt history entry: Start-Date: 2019-08-06 19:46:21 Commandline: apt-get dist-upgrade -y Requested-By: shivaram (1000) Upgrade: libsystemd0:amd64 (237-3ubuntu10.24, 237-3ubuntu10.25), udev:amd64 (237-3ubuntu10.24, 237-3ubuntu10.25), libudev1:amd64 (237-3ubuntu10.24, 237-3ubuntu10.25), systemd-sysv:amd64 (237-3ubuntu10.24, 237-3ubuntu10.25), libpam-systemd:amd64 (237-3ubuntu10.24, 237-3ubuntu10.25), systemd:amd64 (237-3ubuntu10.24, 237-3ubuntu10.25), libnss-systemd:amd64 (237-3ubuntu10.24, 237-3ubuntu10.25), base-files:amd64 (10.1ubuntu2.5, 10.1ubuntu2.6) End-Date: 2019-08-06 19:54:17 systemd journal output: Aug 06 19:47:40 pentos systemd[1]: Reloading. Aug 06 19:47:57 pentos systemd[1]: Reexecuting. Aug 06 19:47:58 pentos systemd[1]: systemd 237 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hie Aug 06 19:47:58 pentos systemd[1]: Detected architecture x86-64. Aug 06 19:47:58 pentos systemd[1]: Stopping Network Service... Aug 06 19:47:58 pentos systemd[1]: Stopped Network Service. Aug 06 19:47:58 pentos systemd[1]: Starting Network Service... Aug 06 19:47:59 pentos systemd-networkd[11513]: ens5: Gained IPv6LL Aug 06 19:47:59 pentos systemd-networkd[11513]: Enumeration completed Aug 06 19:47:59 pentos systemd[1]: Started Network Service. Aug 06 19:47:59 pentos systemd-networkd[11513]: lo: Link is not managed by us Aug 06 19:47:59 pentos systemd-networkd[11513]: ens5: DHCPv4 address 192.168.1.103/24 via 192.168.1.1 Aug 06 19:47:59 pentos dbus-daemon[947]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.2341' (uid=100 pid=11513 comm="/lib/systemd/systemd-network Aug 06 19:47:59 pentos systemd-networkd[11513]: ens5: Configured To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1839231/+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 1965219] Re: gnome lock screen does not permit reentering password
** Changed in: systemd (Ubuntu) Importance: Undecided => Low -- 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/1965219 Title: gnome lock screen does not permit reentering password Status in gnome-shell package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: Initially, only the mouse works in the gnome lock screen, without any way to get a password prompt. It's likely only happening when returning from suspend with lid open. It's possible to ssh into the machine or to press Fn+Ctrl+Alt+F?? and login without gnome. After this, Fn+Ctrl+Alt+F1 brings up a purple ubuntu login screen, but then after login you simply return to the lock screen with no working keyboard. I never found any method to force unlock from ssh or another vt though, so this always still required a reboot, or killing all of gnome. I've randomly tried some solutions from https://askubuntu.com/questions/1242110/after-upgrading-to- ubuntu-20-04-lockscreen-not-working including reinstalling many gnome components. After this, the behavior initially disappeared by returning from suspend merely took a long time, like 30 seconds or 1 minute. It's possible the delay stems from memory size, but a previous identical lenovo x1 had no such problems. I've now a worse problem just a few hours later where unsuspend went directly to a purple ubuntu login screen, but neither the mouse nor keyboard worked. I've not yet been able to test ssh on this problem. It's possibly all connected to recent firmware upgrades, so I'm happy to try downgrading the firmware, but I've not found any instructions on doing so, or even identifying the firmware upgrade log. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.14.0-1027.30-oem 5.14.21 Uname: Linux 5.14.0-1027-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 17 03:44:49 2022 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20210412-218+sutton-newell-focal-amd64+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Within the last week or two GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:22d5] InstallationDate: Installed on 2021-04-15 (335 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20210412-22:07 MachineType: LENOVO 20XWCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1027-oem root=UUID=6a411137-06bb-4de1-be93-c2fcd4f44a5a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2021 dmi.bios.release: 1.51 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET75W (1.51 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.32:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9: dmi.product.family: ThinkPad X1 Carbon Gen 9 dmi.product.name: 20XWCTO1WW dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9 dmi.product.version: ThinkPad X1 Carbon Gen 9 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages
[Touch-packages] [Bug 2007529] Re: package slapd 2.4.49+dfsg-2ubuntu1.9 failed to install/upgrade: installed slapd package post-installation script subprocess returned error exit status 1
Thank you for taking the time to submit a bug report. I'm afraid we're going to need more information before we can act on it, though. It's not entirely clear to me what happened here. Do you still have access to the logs from when you've experienced the issue? Something that caught my attention is the fact that several dpkg operations seem to be failing on your system (based on DpkgHistoryLog.txt). It seems that slapd did not successfully restart after the upgrade, but it's not possible to determine what caused this problem. Can you reproduce the bug? If yes, could you please provide steps explaining how to do it? Thanks in advance. ** Changed in: openldap (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/2007529 Title: package slapd 2.4.49+dfsg-2ubuntu1.9 failed to install/upgrade: installed slapd package post-installation script subprocess returned error exit status 1 Status in openldap package in Ubuntu: Incomplete Bug description: The system asked me to send a report about a failure. Here it is. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: slapd 2.4.49+dfsg-2ubuntu1.9 ProcVersionSignature: Ubuntu 5.15.0-60.66~20.04.1-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 AptOrdering: gir1.2-webkit2-4.0:amd64: Install gir1.2-javascriptcoregtk-4.0:amd64: Install NULL: ConfigurePending Architecture: amd64 CNConfig: Error: command ['/usr/bin/ldapsearch', '-Q', '-LLL', '-Y EXTERNAL', '-H ldapi:///', '-b cn=config'] failed with exit code 255: ldap_sasl_interactive_bind_s: Can't contact LDAP server (-1) CasperMD5CheckResult: skip Date: Wed Feb 15 06:54:50 2023 ErrorMessage: installed slapd package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-02-20 (360 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-60-generic root=UUID=02b06a5b-7026-48f6-9745-993e04e5aba6 ro quiet splash Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: openldap Title: package slapd 2.4.49+dfsg-2ubuntu1.9 failed to install/upgrade: installed slapd package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.default.slapd: 2022-10-24T00:13:25.321836 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/2007529/+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 1869796] Re: vague error during upgrade
** Bug watch added: github.com/systemd/systemd/issues #8102 https://github.com/systemd/systemd/issues/8102 ** Also affects: systemd via https://github.com/systemd/systemd/issues/8102 Importance: Unknown Status: Unknown -- 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/1869796 Title: vague error during upgrade Status in systemd: Unknown Status in debhelper package in Ubuntu: New Status in libvirt package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Confirmed Status in debhelper package in Debian: Confirmed Bug description: Seen from today's apt upgrade on focal: Setting up libvirt-daemon-driver-qemu (6.0.0-0ubuntu6) ... Setting up libvirt-daemon (6.0.0-0ubuntu6) ... Setting up libvirt-daemon-driver-storage-rbd (6.0.0-0ubuntu6) ... Setting up libvirt-daemon-driver-storage-zfs (6.0.0-0ubuntu6) ... Setting up libvirt-daemon-system (6.0.0-0ubuntu6) ... Job failed. See "journalctl -xe" for details. virtlockd.service is a disabled or a static unit, not starting it. virtlogd.service is a disabled or a static unit, not starting it. Setting up libvirt-daemon dnsmasq configuration. Sadly 'journactl -xe' was useless. (It only showed a thousand unrelated lines.) A raw journalctl took forever to run long enough to let me see it generated two million lines of output, and started about two years ago, that I'm not keen on trying to run that through less or similar. Advice accepted. systemctl status looks good enough though: $ systemctl status 'libvirt*' ● libvirtd.socket - Libvirt local socket Loaded: loaded (/lib/systemd/system/libvirtd.socket; enabled; vendor preset: enabled) Active: active (running) since Mon 2020-03-30 20:44:55 UTC; 6min ago Triggers: ● libvirtd.service Listen: /run/libvirt/libvirt-sock (Stream) Tasks: 0 (limit: 18814) Memory: 0B CGroup: /system.slice/libvirtd.socket Mar 30 20:44:55 millbarge systemd[1]: Listening on Libvirt local socket. ● libvirtd.service - Virtualization daemon Loaded: loaded (/lib/systemd/system/libvirtd.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2020-03-30 20:44:55 UTC; 6min ago TriggeredBy: ● libvirtd-admin.socket ● libvirtd.socket ● libvirtd-ro.socket Docs: man:libvirtd(8) https://libvirt.org Main PID: 3646435 (libvirtd) Tasks: 19 (limit: 32768) Memory: 26.9M CGroup: /system.slice/libvirtd.service ├─ 3054 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper ├─ 3055 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper └─3646435 /usr/sbin/libvirtd Mar 30 20:44:55 millbarge systemd[1]: Starting Virtualization daemon... Mar 30 20:44:55 millbarge systemd[1]: Started Virtualization daemon. Mar 30 20:44:55 millbarge dnsmasq[3054]: read /etc/hosts - 7 addresses Mar 30 20:44:55 millbarge dnsmasq[3054]: read /var/lib/libvirt/dnsmasq/default.addnhosts - 0 addresses Mar 30 20:44:55 millbarge dnsmasq-dhcp[3054]: read /var/lib/libvirt/dnsmasq/default.hostsfile ● libvirtd-admin.socket - Libvirt admin socket Loaded: loaded (/lib/systemd/system/libvirtd-admin.socket; enabled; vendor preset: enabled) Active: active (running) since Mon 2020-03-30 20:44:55 UTC; 6min ago Triggers: ● libvirtd.service Listen: /run/libvirt/libvirt-admin-sock (Stream) Tasks: 0 (limit: 18814) Memory: 0B CGroup: /system.slice/libvirtd-admin.socket Mar 30 20:44:55 millbarge systemd[1]: Listening on Libvirt admin socket. ● libvirt-guests.service - Suspend/Resume Running libvirt Guests Loaded: loaded (/lib/systemd/system/libvirt-guests.service; enabled; vendor preset: enabled) Active: active (exited) since Wed 2020-03-25 00:41:47 UTC; 5 days ago Docs: man:libvirtd(8) https://libvirt.org Main PID: 2808 (code=exited, status=0/SUCCESS) Tasks: 0 (limit: 18814) Memory: 0B CGroup: /system.slice/libvirt-guests.service Mar 25 00:41:47 millbarge systemd[1]: Starting Suspend/Resume Running libvirt Guests... Mar 25 00:41:47 millbarge systemd[1]: Finished Suspend/Resume Running libvirt Guests. ● libvirtd-ro.socket - Libvirt local read-only socket Loaded: loaded (/lib/systemd/system/libvirtd-ro.socket; enabled; vendor preset: enabled) Active: active (running) since Mon 2020-03-30 20:44:55 UTC; 6min ago Triggers: ● libvirtd.service Listen: /run/libvirt/libvirt-sock-ro (Stream) Tasks: 0 (limit: 18814) Memory: 0B CGroup:
[Touch-packages] [Bug 2015380] Re: slapd crash when using pwdMinDelay of ppolicy
Fixed in 2.6.5 (upcoming release) by: https://git.openldap.org/openldap/openldap/-/commit/f12d6c047c31c7b0009f10e3be05ae066bac61ac Fixed in 2.5.15 (upcoming release) by: https://git.openldap.org/openldap/openldap/-/commit/e765972f ** Also affects: openldap (Ubuntu Mantic) Importance: Medium Assignee: Sergio Durigan Junior (sergiodj) Status: New ** Also affects: openldap (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: openldap (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: openldap (Ubuntu Kinetic) Importance: Undecided Status: New ** Changed in: openldap (Ubuntu Jammy) Assignee: (unassigned) => Sergio Durigan Junior (sergiodj) ** Changed in: openldap (Ubuntu Kinetic) Assignee: (unassigned) => Sergio Durigan Junior (sergiodj) ** Changed in: openldap (Ubuntu Lunar) Assignee: (unassigned) => Sergio Durigan Junior (sergiodj) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/2015380 Title: slapd crash when using pwdMinDelay of ppolicy Status in openldap package in Ubuntu: New Status in openldap source package in Jammy: New Status in openldap source package in Kinetic: New Status in openldap source package in Lunar: New Status in openldap source package in Mantic: New Bug description: Bug reported upstream[1], and confirmed in the mailing list[2]. PR at [3]. From the mailing list post[2], we can see that slapd crashes: """ But if I test with a wrong password ( yyy) I got: root@zeus:/usr/lib/python3/dist-packages# ldapsearch -xLLLZZD uid=pauloric,ou=users,dc=contatogs,dc=com,dc=br -w yyy |wc -l ldap_result: Can't contact LDAP server (-1) 0 my openldap stop working.Active: inactive (dead) root@zeus:/usr/lib/python3/dist-packages# systemctl status -l slapd ○ slapd.service - LSB: OpenLDAP standalone server (Lightweight Director> Loaded: loaded (/etc/init.d/slapd; generated) Drop-In: /usr/lib/systemd/system/slapd.service.d └─slapd-remain-after-exit.conf Active: inactive (dead) since Tue 2023-04-04 14:44:49 -03; 20s ago Docs: man:systemd-sysv-generator(8) Process: 986673 ExecStart=/etc/init.d/slapd start (code=exited, sta> Process: 986688 ExecStop=/etc/init.d/slapd stop (code=exited, statu> CPU: 47ms """ 1. https://bugs.openldap.org/show_bug.cgi?id=10028 2. https://lists.openldap.org/hyperkitty/list/openldap-techni...@openldap.org/thread/3LYIPMT6TYJM4C7NUFXVYJS7YMODB5ZH/ 3. https://git.openldap.org/openldap/openldap/-/merge_requests/609 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/2015380/+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 2018093] Re: Merge openldap from Debian unstable for mantic
** Changed in: openldap (Ubuntu) Status: New => In Progress ** Merge proposal linked: https://code.launchpad.net/~sergiodj/ubuntu/+source/openldap/+git/openldap/+merge/445156 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/2018093 Title: Merge openldap from Debian unstable for mantic Status in openldap package in Ubuntu: In Progress Bug description: Upstream: tbd Debian: 2.5.13+dfsg-52.6.4+dfsg-1~exp1 Ubuntu: 2.6.3+dfsg-1~exp1ubuntu2 Debian new has 2.6.4+dfsg-1~exp1, which may be available for merge soon. If it turns out this needs a sync rather than a merge, please change the tag 'needs-merge' to 'needs-sync', and (optionally) update the title as desired. ### New Debian Changes ### openldap (2.5.13+dfsg-5) unstable; urgency=medium * Fix sha2-contrib autopkgtest failure. Call slappasswd using its full path. (Closes: #1030814) * Disable flaky test test069-delta-multiprovider-starttls. -- Ryan Tandy Tue, 07 Feb 2023 17:56:12 -0800 openldap (2.5.13+dfsg-4) unstable; urgency=medium [ Andreas Hasenack ] * d/rules: Fix passwd/sha2 build (Closes: #1030716, LP: #2000817) * d/t/sha2-contrib: add test for sha2 module -- Ryan Tandy Mon, 06 Feb 2023 19:21:05 -0800 openldap (2.5.13+dfsg-3) unstable; urgency=medium [ Ryan Tandy ] * Disable flaky test test063-delta-multiprovider. Mitigates #1010608. [ Gioele Barabucci ] * slapd.scripts-common: Avoid double-UTF8-encoding org name (Closes: #1016185) * d/slapd.scripts-common: Remove outdated `migrate_to_slapd_d_style` * d/slapd.postinst: Remove test for ancient version * slapd.scripts-common: Remove unused `normalize_ldif` * d/slapd.scripts-common: Use sed instead of perl in `release_diagnostics` -- Ryan Tandy Fri, 13 Jan 2023 16:29:59 -0800 openldap (2.5.13+dfsg-2) unstable; urgency=medium * d/tests/smbk5pwd: Grant slapd access to /var/lib/heimdal-kdc. Fixes the autopkgtest failure due to heimdal setting mode 700 on this directory. (Closes: #1020442) * d/source/lintian-overrides: Add wildcards to make overrides compatible with both older and newer versions of lintian. * d/slapd-contrib.lintian-overrides: Remove unused custom-library-search-path override now that krb5-config no longer sets -rpath. -- Ryan Tandy Sat, 24 Sep 2022 12:40:21 -0700 openldap (2.5.13+dfsg-1) unstable; urgency=medium * d/rules: Remove get-orig-source, now unnecessary. * Check PGP signature when running uscan. * d/watch: Modernize watch file; use repacksuffix. * d/copyright: Update according to DEP-5. * d/control: Add myself to Uploaders. * New upstream release. -- Sergio Durigan Junior Sun, 18 Sep 2022 18:29:46 -0400 openldap (2.5.12+dfsg-2) unstable; urgency=medium * Stop slapd explicitly in prerm as a workaround for #1006147, which caused dpkg-reconfigure to not restart the service, so the new configuration was not applied. See also #994204. (Closes: #1010971) -- Ryan Tandy Mon, 23 May 2022 10:14:53 -0700 openldap (2.5.12+dfsg-1) unstable; urgency=medium * New upstream release. - Fixed SQL injection in back-sql (ITS#9815) (CVE-2022-29155) * Update debconf translations: - German, thanks to Helge Kreutzmann. (Closes: #1007728) - Spanish, thanks to Camaleón. (Closes: #1008529) - Dutch, thanks to Frans Spiesschaert. (Closes: #1010034) -- Ryan Tandy Wed, 04 May 2022 18:00:16 -0700 openldap (2.5.11+dfsg-1) unstable; urgency=medium * Upload to unstable. -- Ryan Tandy Fri, 11 Mar 2022 19:38:02 -0800 openldap (2.5.11+dfsg-1~exp1) experimental; urgency=medium * New upstream release. * Add openssl to Build-Depends to enable more checks in test067-tls. * Update slapd-contrib's custom-library-search-path override to work with current Lintian. -- Ryan Tandy Sun, 23 Jan 2022 17:16:05 -0800 openldap (2.5.8+dfsg-1~exp1) experimental; urgency=medium * New upstream release. * Update slapd-contrib's custom-library-search-path override to work with Lintian 2.108.0. -- Ryan Tandy Wed, 13 Oct 2021 18:42:55 -0700 openldap (2.5.7+dfsg-1~exp1) experimental; urgency=medium * New upstream release. * Don't run autoreconf in contrib/ldapc++. We don't build it, and it is not ### Old Ubuntu Delta ### openldap (2.6.3+dfsg-1~exp1ubuntu2) lunar; urgency=medium * Build the passwd/sha2 contrib module with -fno-strict-aliasing to avoid computing an incorrect SHA256 hash with some versions of the compiler (LP: #2000817): - d/t/{control,sha2-contrib}: test to verify the SHA256 hash produced by passwd/sha2 - d/rules: set -fno-strict-aliasing only when building the passwd/sha2 contrib module
[Touch-packages] [Bug 1967014] Re: Lenovo Ideapad 3 screen brightness F keys not working...
Are you still running Focal, or have you tried upgrading to Jammy (or another release)? If this is still an issue on whatever release you are running, can you please run: $ sudo evtest and when prompted, select device number that corresponds to your keyboard. Then, press the key combination that you expect to adjust brightness up, and then the same for brightness down, and attach that output? Please also attach the output of: $ udevadm info /dev/input/eventX where X is the same number selected in the evtest command, and the output of: $ cat /sys/class/dmi/id/modalias ** Changed in: systemd (Ubuntu) Status: Confirmed => Incomplete -- 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/1967014 Title: Lenovo Ideapad 3 screen brightness F keys not working... Status in systemd package in Ubuntu: Incomplete Bug description: As the title says, the F keys the control screen brightness (F11/F12 on the Lenovo Ideapad 3 15ITL05 laptop I have) don't work on Ubuntu 21.10. All other special function keys (volume up/down, lock screen, airplane mode, etc...) and the screen brightness slider in the top right-hand corner work; it's just the brightness keys that are not working. I know I can just use the slider, but it's more convenient to use the F keys. I hope you are working on this for a future 21.10 update. Also, I originally installed 20.04 and upgraded to 21.10, but even on 20.04, those keys weren't working, either. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1967014/+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 1970634] Re: FTBFS: mariadb fails to start due to low MEMLOCK limit
The commit mentioned in https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1970634/comments/3 has been present in systemd since v251 (which is in Kinetic), so I don't think there is anything left to do for systemd. Please correct me if I am wrong. ** Changed in: systemd (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1970634 Title: FTBFS: mariadb fails to start due to low MEMLOCK limit Status in mariadb-10.6 package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in mariadb-10.6 source package in Jammy: Fix Released Status in systemd source package in Jammy: Won't Fix Bug description: [Impact] Jammy's MariaDB will fail to build, and also fail to start, if the underlying kernel is 5.4.x (focal's) and if it's running in an unprivileged container (lxd, docker). It will also fail to build in launchpad builders. Common scenarios where this combination exists is a focal host, running an unprivileged jammy container (lxd or docker), or even a chroot (the launchpad builders). Jammy's MariaDB was built with io_uring support, and it tries to enable it at runtime if it deems it's running on a supported kernel. There is a range of kernel versions it checks, but of interest for this SRU, the Focal (5.4.x) kernel is inside this range and io_uring will be enabled. The jammy kernel (5.15) is not, so io_uring will not be enabled there, and thus the bug is not manifested in that case. If io_uring is enabled, a higher MEMLOCK limit is required than what is set by default in focal or jammy (64Mb is what we get, 256Mb or more is required). The systemd unit file for mariadb tries to raise this limit, but in an unprivileged container this won't work. MariaDB has checks in place to catch when MEMLOCK is too low, in which case it will not use io_uring, but these checks are failing because of the LTO build flags that were used in the jammy build of mariadb. It's unclear if it's a bug in gcc or something else. There is more information in comment #1, comment #5 and later. The suggested fix here is to disable LTO for the jammy build. This has been done for kinetic already, and is also applied to the debian packaging (inside a distro-specific conditional). [Test Plan] The test plan is to launch mariadb in a jammy lxd container running on a focal host. lxc launch ubuntu:focal f --vm lxc shell f lxd init # just hit enter for all questions lxc launch ubuntu:jammy j lxc shell j ulimit -l # confirm it's less than 256 apt update && apt install mariadb-server -y After the installation, mariadb will not be running, and this can be checked with: systemctl status mariadb.service or journalctl -u mariadb.server You will see something like this: Jun 17 18:32:01 jammy-mariadb systemd[1]: Starting MariaDB 10.6.7 database server... Jun 17 18:32:01 jammy-mariadb mariadbd[1864]: 2022-06-17 18:32:01 0 [Note] /usr/sbin/mariadbd (server 10.6.7-MariaDB-2ubuntu1) starting as process 1864 ... Jun 17 18:32:01 jammy-mariadb mariadbd[1864]: 2022-06-17 18:32:01 0 [Note] InnoDB: The first data file './ibdata1' did not exist. A new tablespace will be created! Jun 17 18:32:01 jammy-mariadb mariadbd[1864]: 2022-06-17 18:32:01 0 [Note] InnoDB: Compressed tables use zlib 1.2.11 Jun 17 18:32:01 jammy-mariadb mariadbd[1864]: 2022-06-17 18:32:01 0 [Note] InnoDB: Using transactional memory Jun 17 18:32:01 jammy-mariadb mariadbd[1864]: 2022-06-17 18:32:01 0 [Note] InnoDB: Number of pools: 1 Jun 17 18:32:01 jammy-mariadb mariadbd[1864]: 2022-06-17 18:32:01 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions Jun 17 18:32:01 jammy-mariadb mariadbd[1864]: 2022-06-17 18:32:01 0 [Warning] mariadbd: io_uring_queue_init() failed with ENOMEM: try larger memory locked limit, ulimit -l, or https://mariadb.com/kb/en/systemd/#configuring-limitmemlock under systemd (262144 bytes required) Jun 17 18:32:01 jammy-mariadb mariadbd[1864]: 220617 18:32:01 [ERROR] mysqld got signal 6 ; And a crash dump. With the fixed version, the service will be running normally after installation. [Where problems could occur] The proposed fix is not a surgical strike. It's unfortunate that we didn't get to the bottom of why LTO is causing this behavior. Reverting it is still the quickest and less risky change at the moment, though. This gets us on par with upstream binary builds, and debian builds, and these also have wide test coverage and ample user base. The other regression possibility is that this is a rebuild of mariadb in the current jammy environment, and the package that is currently in jammy was built on March 10th, 2022. Most likely the reverse dependencies were updated in jammy since then. It's unclear how
[Touch-packages] [Bug 2018261] Re: package udev 249.11-0ubuntu3.9 failed to install/upgrade: le sous-processus paquet udev script post-installation installé a renvoyé un état de sortie d'erreur 1
The relevant part of DpkgTerminalLog.txt is: Setting up udev (249.11-0ubuntu3.9)... Installing new version of configuration file /etc/init.d/udev... Installing new version of configuration file /etc/udev/udev.conf... The "kvm" group already exists, without being a system group. End of procedure. dpkg: error processing udev package (--configure): udev script post install package subprocess installed returned error exit status 1 I believe the best resolution is for you to correctly configure the kvm group as a system group. See bug 1880541 for more background. I don't think we should make any changes in systemd to work around this. ** Changed in: systemd (Ubuntu) Status: Confirmed => Won't Fix -- 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/2018261 Title: package udev 249.11-0ubuntu3.9 failed to install/upgrade: le sous- processus paquet udev script post-installation installé a renvoyé un état de sortie d'erreur 1 Status in systemd package in Ubuntu: Won't Fix Bug description: upgrade error from 20.04 to 22.04 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: udev 249.11-0ubuntu3.9 ProcVersionSignature: Ubuntu 5.4.0-148.165-generic 5.4.231 Uname: Linux 5.4.0-148-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: unknown CustomUdevRuleFiles: 70-snap.gnome-characters.rules 95-oem-hotkey-osd.rules 70-snap.ubuntu-frame.rules 70-snap.firefox.rules 70-snap.snap-store.rules 70-snap.snapd.rules 70-snap.cups.rules 70-snap.gnome-calculator.rules 10-ubports.rules 70-snap.multipass.rules 70-snap.gnome-system-monitor.rules 70-snap.xibo-player.rules 70-snap.chromium.rules 70-snap.gnome-logs.rules Date: Mon May 1 21:25:19 2023 ErrorMessage: le sous-processus paquet udev script post-installation installé a renvoyé un état de sortie d'erreur 1 InstallationDate: Installed on 2021-01-22 (829 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20180507-04:30 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 003: ID 0461:4d81 Primax Electronics, Ltd Dell N889 Optical Mouse Bus 001 Device 002: ID 413c:2106 Dell Computer Corp. QuietKey Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel Corporation NUC7i5DNKE ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-148-generic root=UUID=527a0826-742d-45c2-bd7b-cb43d2f0fa5c ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.9 SourcePackage: systemd Title: package udev 249.11-0ubuntu3.9 failed to install/upgrade: le sous-processus paquet udev script post-installation installé a renvoyé un état de sortie d'erreur 1 UpgradeStatus: Upgraded to jammy on 2023-05-01 (0 days ago) dmi.bios.date: 03/04/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: DNKBLi5v.86A.0062.2019.0304.1757 dmi.board.name: NUC7i5DNB dmi.board.vendor: Intel Corporation dmi.board.version: J57626-506 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrDNKBLi5v.86A.0062.2019.0304.1757:bd03/04/2019:svnIntelCorporation:pnNUC7i5DNKE:pvrJ72865-506:rvnIntelCorporation:rnNUC7i5DNB:rvrJ57626-506:cvnIntelCorporation:ct35:cvr2: dmi.product.family: Intel NUC dmi.product.name: NUC7i5DNKE dmi.product.version: J72865-506 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2018261/+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 1938065] Re: systemd 248.3-1ubuntu2 fails to install (when upgrading 21.04->21.10)
This version of systemd is no longer in any supported Ubuntu release. ** Changed in: systemd (Ubuntu) Status: Confirmed => Won't Fix -- 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/1938065 Title: systemd 248.3-1ubuntu2 fails to install (when upgrading 21.04->21.10) Status in systemd package in Ubuntu: Won't Fix Bug description: This happened when trying to upgrade from 21.04 to 21.10. Setting up systemd (248.3-1ubuntu2) ... systemd-machine-id-setup: error while loading shared libraries: libsystemd-shared-247.so: cannot open shared object file: No such file or directory dpkg: error processing package systemd (--configure): installed systemd package post-installation script subprocess returned error exit status 127 Processing triggers for initramfs-tools (0.140ubuntu6) ... update-initramfs: Generating /boot/initrd.img-5.11.0-25-generic Processing triggers for libc-bin (2.33-0ubuntu7) ... Processing triggers for man-db (2.9.4-2) ... Processing triggers for dbus (1.12.20-2ubuntu1) ... Errors were encountered while processing: systemd I reverted to old version by manualing installing the hirsute's debs (from 21.04: libsystemd0_247.3-3ubuntu3.4_i386.deb systemd_247.3-3ubuntu3.4_amd64.deb libnss- systemd_247.3-3ubuntu3.4_amd64.deb libsystemd- dev_247.3-3ubuntu3.4_amd64.deb systemd-sysv_247.3-3ubuntu3.4_amd64.deb libpam-systemd_247.3-3ubuntu3.4_amd64.deb libudev1_247.3-3ubuntu3.4_amd64.deb udev_247.3-3ubuntu3.4_amd64.deb libsystemd0_247.3-3ubuntu3.4_amd64.deb libudev- dev_247.3-3ubuntu3.4_amd64.deb) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1938065/+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 1948904] Re: Installed systemd package post-installation script subprocess returned error exit status 127
This version of systemd is no longer in any supported Ubuntu release. ** Changed in: systemd (Ubuntu) Status: Confirmed => Won't Fix -- 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/1948904 Title: Installed systemd package post-installation script subprocess returned error exit status 127 Status in systemd package in Ubuntu: Won't Fix Bug description: The package systemd started giving error after upgrade to 21.10 from 21.04. Setting up systemd (248.3-1ubuntu8) ... systemd-machine-id-setup: error while loading shared libraries: libsystemd-shared-247.so: cannot open shared object file: No such file or directory dpkg: error processing package systemd (--configure): installed systemd package post-installation script subprocess returned error exit status 127 Errors were encountered while processing: systemd E: Sub-process /usr/bin/dpkg returned an error code (1) When I tried to force reinstall systemd it gives following error. Internal Error, No file name for systemd:amd64 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: systemd 248.3-1ubuntu8 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Oct 27 12:00:49 2021 InstallationDate: Installed on 2018-11-21 (1070 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 27c6:55a4 Shenzhen Goodix Technology Co.,Ltd. Goodix FingerPrint Device Bus 001 Device 002: ID 13d3:5415 IMC Networks Integrated Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 8: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M |__ Port 8: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 9: Dev 3, If 0, Class=Vendor Specific Class, Driver=, 480M MachineType: LENOVO 20RAS0D800 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic root=UUID=b69e3e1e-fa29-46b4-8ec8-c6cee754774b ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/systemd-localed.service → /usr/lib/systemd/system/systemd-localed.service.d/locale-gen.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. UpgradeStatus: Upgraded to impish on 2021-10-19 (7 days ago) dmi.bios.date: 09/14/2020 dmi.bios.release: 1.14 dmi.bios.vendor: LENOVO dmi.bios.version: R16ET28W (1.14 ) dmi.board.asset.tag: Not Available dmi.board.name: 20RAS0D800 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.11 dmi.modalias: dmi:bvnLENOVO:bvrR16ET28W(1.14):bd09/14/2020:br1.14:efr1.11:svnLENOVO:pn20RAS0D800:pvrThinkPadE14:skuLENOVO_MT_20RA_BU_SMB_FM_ThinkPadE14:rvnLENOVO:rn20RAS0D800:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E14 dmi.product.name: 20RAS0D800 dmi.product.sku: LENOVO_MT_20RA_BU_SMB_FM_ThinkPad E14 dmi.product.version: ThinkPad E14 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1948904/+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 2024603] [NEW] Selecting an alternate keyboard does not work and keypad is active even when typing
Public bug reported: Since upgrading to Ubuntu 22.04 I have been having trouble with both Wayland and Xorg. Xorg seems the most stable of the two, so I am attempting to use it, however, I am having two problems that are causing problems. 1) I have added an alternate (Spanish) keyboard. This shows up in both the tray and under the keyboard settings, however, when I select the alternate keyboard it just reverts back to English and does not allow entry via the alternate keyboard. This part does work properly in Wayland allowing me to select either the English or the Spanish keyboard for the current window as I have selected in the settings 2) The touchpad is active full-time even with the "Disable while typing" options selected. This is continually causing problems as I bump the touchpad with my palm while typing. While the second issue is mostly an annoyance, the first makes Xorg unusable as I need to routinely switch to the Spanish character set for documents and web entry. In both cases Xorg is not responding to or acknowledging the selections. Neither of these were problems with Ubuntu 20.04 prior to upgrading. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 Uname: Linux 6.2.6-76060206-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jun 21 09:58:31 2023 DistUpgraded: 2022-12-01 16:49:16,796 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: system76/1.0.14~1684961628~22.04~8c2ff21~dev, 6.2.6-76060206-generic, x86_64: installed system76_acpi/1.0.2~1685480347~22.04~aaf10e3~dev, 6.2.6-76060206-generic, x86_64: installed system76-io/1.0.2~1685984007~22.04~7dc99ca~dev, 6.2.6-76060206-generic, x86_64: installed wireguard/1.0.20210606: added ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer HD Graphics 530 [1558:6509] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 04f2:b5a7 Chicony Electronics Co., Ltd Chicony USB 2.0 Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System76, Inc. Gazelle ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.6-76060206-generic root=UUID=ac9c0a24-9264-4620-9dca-59a3e7976588 ro acpi_backlight=vendor quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-12-02 (201 days ago) dmi.bios.date: 09/09/2016 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.02RSA2-1 dmi.board.asset.tag: Tag 12345 dmi.board.name: Gazelle dmi.board.vendor: System76, Inc. dmi.board.version: gaze11 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.02RSA2-1:bd09/09/2016:br5.11:svnSystem76,Inc.:pnGazelle:pvrgaze11:rvnSystem76,Inc.:rnGazelle:rvrgaze11:cvnSystem76,Inc.:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: Gazelle dmi.product.sku: Not Applicable dmi.product.version: gaze11 dmi.sys.vendor: System76, Inc. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2016-10-20T08:48:37.54 version.compiz: compiz 1:0.9.14.1+22.04.20220820-0ubuntu1 version.libdrm2: libdrm2 2.4.110-1pop0~1648761328~22.04~166056a~dev version.libgl1-mesa-dri: libgl1-mesa-dri 22.3.5-1pop1~1677168864~22.04~8f20e98~dev version.libgl1-mesa-glx: libgl1-mesa-glx 22.3.5-1pop1~1677168864~22.04~8f20e98~dev version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 xserver.bootTime: Sat Jan 19 19:22:02 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1191 vendor LGD xserver.version: 2:1.18.4-0ubuntu0.8 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages ubuntu ** Summary changed: -
[Touch-packages] [Bug 2023437] Re: ppc64el gold linker produces unusable clang-16 binary
** Changed in: binutils Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/2023437 Title: ppc64el gold linker produces unusable clang-16 binary Status in binutils: Fix Released Status in binutils package in Ubuntu: New Bug description: root@Unimatrix08-Jammy:/clang# /usr/bin/g++-12 -O3 -fstack-protector-strong -Wformat -Werror=format-security -Wno-unused-command-line-argument -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -fno-semantic-interposition -fvisibility-inlines-hidden -Werror=date-time -Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wno-missing-field-initializers -pedantic -Wno-long-long -Wimplicit-fallthrough -Wno-maybe-uninitialized -Wno-class-memaccess -Wno-redundant-move -Wno-pessimizing-move -Wno-noexcept-type -Wdelete-non-virtual-dtor -Wsuggest-override -Wno-comment -Wno-misleading-indentation -Wctad-maybe-unsupported -fdiagnostics-color -ffunction-sections -fdata-sections -fdebug-prefix-map=/llvm-toolchain-16-16.0.5/build-llvm=build-llvm -fdebug-prefix-map=/llvm-toolchain-16-16.0.5/= -no-canonical-prefixes -ffile-prefix-map=/llvm-toolchain-16-16.0.5/build-llvm=build-llvm -ffile-prefix-map=/llvm-toolchain-16-16.0.5/= -no-canonical-prefixes -fno-common -Woverloaded-virtual -fno-strict-aliasi ng -O3 -DNDEBUG -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,--build-id -fuse-ld=bfd-Wl,--gc-sections tools/clang/tools/driver/CMakeFiles/clang.dir/driver.cpp.o tools/clang/tools/driver/CMakeFiles/clang.dir/cc1_main.cpp.o tools/clang/tools/driver/CMakeFiles/clang.dir/cc1as_main.cpp.o tools/clang/tools/driver/CMakeFiles/clang.dir/cc1gen_reproducer_main.cpp.o tools/clang/tools/driver/CMakeFiles/clang.dir/clang-driver.cpp.o -o bin/clang-16-bfd -Wl,-rpath,"\$ORIGIN/../lib:" lib/libLLVMPowerPCCodeGen.a lib/libLLVMPowerPCAsmParser.a lib/libLLVMPowerPCDesc.a lib/libLLVMPowerPCDisassembler.a lib/libLLVMPowerPCInfo.a lib/libLLVMAnalysis.a lib/libLLVMCodeGen.a lib/libLLVMCore.a lib/libLLVMipo.a lib/libLLVMAggressiveInstCombine.a lib/libLLVMInstCombine.a lib/libLLVMInstrumentation.a lib/libLLVMMC.a lib/libLLVMMCParser.a lib/libLLVMObjCARCOpts.a lib/libLLVMOption.a lib/libLLVMScalarOpts.a lib/libLLVMSupport.a lib/libLLVMTargetParser.a lib/libLLVMTransformUtils.a lib/libLL VMVectorize.a lib/libclangBasic.a lib/libclangCodeGen.a lib/libclangDriver.a lib/libclangFrontend.a lib/libclangFrontendTool.a lib/libclangSerialization.a lib/libLLVMAsmPrinter.a lib/libLLVMGlobalISel.a lib/libLLVMSelectionDAG.a lib/libLLVMMCDisassembler.a lib/libclangCodeGen.a lib/libLLVMCoverage.a lib/libLLVMLTO.a lib/libLLVMExtensions.a lib/libPolly.a lib/libPollyISL.a lib/libLLVMPasses.a lib/libLLVMCodeGen.a lib/libLLVMObjCARCOpts.a lib/libLLVMTarget.a lib/libLLVMCoroutines.a lib/libLLVMipo.a lib/libLLVMInstrumentation.a lib/libLLVMVectorize.a lib/libLLVMBitWriter.a lib/libLLVMLinker.a lib/libLLVMIRPrinter.a lib/libclangExtractAPI.a lib/libclangRewriteFrontend.a lib/libclangARCMigrate.a lib/libclangStaticAnalyzerFrontend.a lib/libclangStaticAnalyzerCheckers.a lib/libclangStaticAnalyzerCore.a lib/libclangCrossTU.a lib/libclangIndex.a lib/libclangFrontend.a lib/libclangDriver.a lib/libLLVMWindowsDriver.a lib/libLLVMOption.a lib/libclangParse .a lib/libclangSerialization.a lib/libclangSema.a lib/libclangAnalysis.a lib/libclangASTMatchers.a lib/libLLVMFrontendHLSL.a lib/libclangEdit.a lib/libclangSupport.a lib/libclangAST.a lib/libLLVMFrontendOpenMP.a lib/libLLVMScalarOpts.a lib/libLLVMAggressiveInstCombine.a lib/libLLVMInstCombine.a lib/libLLVMTransformUtils.a lib/libLLVMAnalysis.a lib/libLLVMProfileData.a lib/libLLVMSymbolize.a lib/libLLVMDebugInfoDWARF.a lib/libLLVMDebugInfoPDB.a lib/libLLVMObject.a lib/libLLVMMCParser.a lib/libLLVMMC.a lib/libLLVMIRReader.a lib/libLLVMBitReader.a lib/libLLVMAsmParser.a lib/libLLVMTextAPI.a lib/libLLVMDebugInfoCodeView.a lib/libLLVMDebugInfoMSF.a lib/libLLVMCore.a lib/libLLVMBinaryFormat.a lib/libLLVMRemarks.a lib/libLLVMBitstreamReader.a lib/libclangFormat.a lib/libclangToolingInclusions.a lib/libclangToolingCore.a lib/libclangRewrite.a lib/libclangLex.a lib/libclangBasic.a lib/libLLVMTargetParser.a lib/libLLVMSupport.a lib/libLLVMDemangle.a -l rt -ldl -lm /usr/lib/powerpc64le-linux-gnu/libz.so /usr/lib/powerpc64le-linux-gnu/libtinfo.so root@Unimatrix08-Jammy:/clang# /usr/bin/g++-12 -O3 -fstack-protector-strong -Wformat -Werror=format-security -Wno-unused-command-line-argument -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -fno-semantic-interposition -fvisibility-inlines-hidden -Werror=date-time -Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wno-missing-field-initializers -pedantic -Wno-long-long -Wimplicit-fallthrough -Wno-maybe-uninitialized
[Touch-packages] [Bug 2023437]
thanks! I'll test shortly! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/2023437 Title: ppc64el gold linker produces unusable clang-16 binary Status in binutils: Fix Released Status in binutils package in Ubuntu: New Bug description: root@Unimatrix08-Jammy:/clang# /usr/bin/g++-12 -O3 -fstack-protector-strong -Wformat -Werror=format-security -Wno-unused-command-line-argument -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -fno-semantic-interposition -fvisibility-inlines-hidden -Werror=date-time -Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wno-missing-field-initializers -pedantic -Wno-long-long -Wimplicit-fallthrough -Wno-maybe-uninitialized -Wno-class-memaccess -Wno-redundant-move -Wno-pessimizing-move -Wno-noexcept-type -Wdelete-non-virtual-dtor -Wsuggest-override -Wno-comment -Wno-misleading-indentation -Wctad-maybe-unsupported -fdiagnostics-color -ffunction-sections -fdata-sections -fdebug-prefix-map=/llvm-toolchain-16-16.0.5/build-llvm=build-llvm -fdebug-prefix-map=/llvm-toolchain-16-16.0.5/= -no-canonical-prefixes -ffile-prefix-map=/llvm-toolchain-16-16.0.5/build-llvm=build-llvm -ffile-prefix-map=/llvm-toolchain-16-16.0.5/= -no-canonical-prefixes -fno-common -Woverloaded-virtual -fno-strict-aliasi ng -O3 -DNDEBUG -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,--build-id -fuse-ld=bfd-Wl,--gc-sections tools/clang/tools/driver/CMakeFiles/clang.dir/driver.cpp.o tools/clang/tools/driver/CMakeFiles/clang.dir/cc1_main.cpp.o tools/clang/tools/driver/CMakeFiles/clang.dir/cc1as_main.cpp.o tools/clang/tools/driver/CMakeFiles/clang.dir/cc1gen_reproducer_main.cpp.o tools/clang/tools/driver/CMakeFiles/clang.dir/clang-driver.cpp.o -o bin/clang-16-bfd -Wl,-rpath,"\$ORIGIN/../lib:" lib/libLLVMPowerPCCodeGen.a lib/libLLVMPowerPCAsmParser.a lib/libLLVMPowerPCDesc.a lib/libLLVMPowerPCDisassembler.a lib/libLLVMPowerPCInfo.a lib/libLLVMAnalysis.a lib/libLLVMCodeGen.a lib/libLLVMCore.a lib/libLLVMipo.a lib/libLLVMAggressiveInstCombine.a lib/libLLVMInstCombine.a lib/libLLVMInstrumentation.a lib/libLLVMMC.a lib/libLLVMMCParser.a lib/libLLVMObjCARCOpts.a lib/libLLVMOption.a lib/libLLVMScalarOpts.a lib/libLLVMSupport.a lib/libLLVMTargetParser.a lib/libLLVMTransformUtils.a lib/libLL VMVectorize.a lib/libclangBasic.a lib/libclangCodeGen.a lib/libclangDriver.a lib/libclangFrontend.a lib/libclangFrontendTool.a lib/libclangSerialization.a lib/libLLVMAsmPrinter.a lib/libLLVMGlobalISel.a lib/libLLVMSelectionDAG.a lib/libLLVMMCDisassembler.a lib/libclangCodeGen.a lib/libLLVMCoverage.a lib/libLLVMLTO.a lib/libLLVMExtensions.a lib/libPolly.a lib/libPollyISL.a lib/libLLVMPasses.a lib/libLLVMCodeGen.a lib/libLLVMObjCARCOpts.a lib/libLLVMTarget.a lib/libLLVMCoroutines.a lib/libLLVMipo.a lib/libLLVMInstrumentation.a lib/libLLVMVectorize.a lib/libLLVMBitWriter.a lib/libLLVMLinker.a lib/libLLVMIRPrinter.a lib/libclangExtractAPI.a lib/libclangRewriteFrontend.a lib/libclangARCMigrate.a lib/libclangStaticAnalyzerFrontend.a lib/libclangStaticAnalyzerCheckers.a lib/libclangStaticAnalyzerCore.a lib/libclangCrossTU.a lib/libclangIndex.a lib/libclangFrontend.a lib/libclangDriver.a lib/libLLVMWindowsDriver.a lib/libLLVMOption.a lib/libclangParse .a lib/libclangSerialization.a lib/libclangSema.a lib/libclangAnalysis.a lib/libclangASTMatchers.a lib/libLLVMFrontendHLSL.a lib/libclangEdit.a lib/libclangSupport.a lib/libclangAST.a lib/libLLVMFrontendOpenMP.a lib/libLLVMScalarOpts.a lib/libLLVMAggressiveInstCombine.a lib/libLLVMInstCombine.a lib/libLLVMTransformUtils.a lib/libLLVMAnalysis.a lib/libLLVMProfileData.a lib/libLLVMSymbolize.a lib/libLLVMDebugInfoDWARF.a lib/libLLVMDebugInfoPDB.a lib/libLLVMObject.a lib/libLLVMMCParser.a lib/libLLVMMC.a lib/libLLVMIRReader.a lib/libLLVMBitReader.a lib/libLLVMAsmParser.a lib/libLLVMTextAPI.a lib/libLLVMDebugInfoCodeView.a lib/libLLVMDebugInfoMSF.a lib/libLLVMCore.a lib/libLLVMBinaryFormat.a lib/libLLVMRemarks.a lib/libLLVMBitstreamReader.a lib/libclangFormat.a lib/libclangToolingInclusions.a lib/libclangToolingCore.a lib/libclangRewrite.a lib/libclangLex.a lib/libclangBasic.a lib/libLLVMTargetParser.a lib/libLLVMSupport.a lib/libLLVMDemangle.a -l rt -ldl -lm /usr/lib/powerpc64le-linux-gnu/libz.so /usr/lib/powerpc64le-linux-gnu/libtinfo.so root@Unimatrix08-Jammy:/clang# /usr/bin/g++-12 -O3 -fstack-protector-strong -Wformat -Werror=format-security -Wno-unused-command-line-argument -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -fno-semantic-interposition -fvisibility-inlines-hidden -Werror=date-time -Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wno-missing-field-initializers -pedantic -Wno-long-long -Wimplicit-fallthrough -Wno-maybe-uninitialized -Wno-class-memaccess -Wno-redundant-move
[Touch-packages] [Bug 2023437]
Should now be fixed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/2023437 Title: ppc64el gold linker produces unusable clang-16 binary Status in binutils: Fix Released Status in binutils package in Ubuntu: New Bug description: root@Unimatrix08-Jammy:/clang# /usr/bin/g++-12 -O3 -fstack-protector-strong -Wformat -Werror=format-security -Wno-unused-command-line-argument -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -fno-semantic-interposition -fvisibility-inlines-hidden -Werror=date-time -Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wno-missing-field-initializers -pedantic -Wno-long-long -Wimplicit-fallthrough -Wno-maybe-uninitialized -Wno-class-memaccess -Wno-redundant-move -Wno-pessimizing-move -Wno-noexcept-type -Wdelete-non-virtual-dtor -Wsuggest-override -Wno-comment -Wno-misleading-indentation -Wctad-maybe-unsupported -fdiagnostics-color -ffunction-sections -fdata-sections -fdebug-prefix-map=/llvm-toolchain-16-16.0.5/build-llvm=build-llvm -fdebug-prefix-map=/llvm-toolchain-16-16.0.5/= -no-canonical-prefixes -ffile-prefix-map=/llvm-toolchain-16-16.0.5/build-llvm=build-llvm -ffile-prefix-map=/llvm-toolchain-16-16.0.5/= -no-canonical-prefixes -fno-common -Woverloaded-virtual -fno-strict-aliasi ng -O3 -DNDEBUG -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,--build-id -fuse-ld=bfd-Wl,--gc-sections tools/clang/tools/driver/CMakeFiles/clang.dir/driver.cpp.o tools/clang/tools/driver/CMakeFiles/clang.dir/cc1_main.cpp.o tools/clang/tools/driver/CMakeFiles/clang.dir/cc1as_main.cpp.o tools/clang/tools/driver/CMakeFiles/clang.dir/cc1gen_reproducer_main.cpp.o tools/clang/tools/driver/CMakeFiles/clang.dir/clang-driver.cpp.o -o bin/clang-16-bfd -Wl,-rpath,"\$ORIGIN/../lib:" lib/libLLVMPowerPCCodeGen.a lib/libLLVMPowerPCAsmParser.a lib/libLLVMPowerPCDesc.a lib/libLLVMPowerPCDisassembler.a lib/libLLVMPowerPCInfo.a lib/libLLVMAnalysis.a lib/libLLVMCodeGen.a lib/libLLVMCore.a lib/libLLVMipo.a lib/libLLVMAggressiveInstCombine.a lib/libLLVMInstCombine.a lib/libLLVMInstrumentation.a lib/libLLVMMC.a lib/libLLVMMCParser.a lib/libLLVMObjCARCOpts.a lib/libLLVMOption.a lib/libLLVMScalarOpts.a lib/libLLVMSupport.a lib/libLLVMTargetParser.a lib/libLLVMTransformUtils.a lib/libLL VMVectorize.a lib/libclangBasic.a lib/libclangCodeGen.a lib/libclangDriver.a lib/libclangFrontend.a lib/libclangFrontendTool.a lib/libclangSerialization.a lib/libLLVMAsmPrinter.a lib/libLLVMGlobalISel.a lib/libLLVMSelectionDAG.a lib/libLLVMMCDisassembler.a lib/libclangCodeGen.a lib/libLLVMCoverage.a lib/libLLVMLTO.a lib/libLLVMExtensions.a lib/libPolly.a lib/libPollyISL.a lib/libLLVMPasses.a lib/libLLVMCodeGen.a lib/libLLVMObjCARCOpts.a lib/libLLVMTarget.a lib/libLLVMCoroutines.a lib/libLLVMipo.a lib/libLLVMInstrumentation.a lib/libLLVMVectorize.a lib/libLLVMBitWriter.a lib/libLLVMLinker.a lib/libLLVMIRPrinter.a lib/libclangExtractAPI.a lib/libclangRewriteFrontend.a lib/libclangARCMigrate.a lib/libclangStaticAnalyzerFrontend.a lib/libclangStaticAnalyzerCheckers.a lib/libclangStaticAnalyzerCore.a lib/libclangCrossTU.a lib/libclangIndex.a lib/libclangFrontend.a lib/libclangDriver.a lib/libLLVMWindowsDriver.a lib/libLLVMOption.a lib/libclangParse .a lib/libclangSerialization.a lib/libclangSema.a lib/libclangAnalysis.a lib/libclangASTMatchers.a lib/libLLVMFrontendHLSL.a lib/libclangEdit.a lib/libclangSupport.a lib/libclangAST.a lib/libLLVMFrontendOpenMP.a lib/libLLVMScalarOpts.a lib/libLLVMAggressiveInstCombine.a lib/libLLVMInstCombine.a lib/libLLVMTransformUtils.a lib/libLLVMAnalysis.a lib/libLLVMProfileData.a lib/libLLVMSymbolize.a lib/libLLVMDebugInfoDWARF.a lib/libLLVMDebugInfoPDB.a lib/libLLVMObject.a lib/libLLVMMCParser.a lib/libLLVMMC.a lib/libLLVMIRReader.a lib/libLLVMBitReader.a lib/libLLVMAsmParser.a lib/libLLVMTextAPI.a lib/libLLVMDebugInfoCodeView.a lib/libLLVMDebugInfoMSF.a lib/libLLVMCore.a lib/libLLVMBinaryFormat.a lib/libLLVMRemarks.a lib/libLLVMBitstreamReader.a lib/libclangFormat.a lib/libclangToolingInclusions.a lib/libclangToolingCore.a lib/libclangRewrite.a lib/libclangLex.a lib/libclangBasic.a lib/libLLVMTargetParser.a lib/libLLVMSupport.a lib/libLLVMDemangle.a -l rt -ldl -lm /usr/lib/powerpc64le-linux-gnu/libz.so /usr/lib/powerpc64le-linux-gnu/libtinfo.so root@Unimatrix08-Jammy:/clang# /usr/bin/g++-12 -O3 -fstack-protector-strong -Wformat -Werror=format-security -Wno-unused-command-line-argument -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -fno-semantic-interposition -fvisibility-inlines-hidden -Werror=date-time -Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wno-missing-field-initializers -pedantic -Wno-long-long -Wimplicit-fallthrough -Wno-maybe-uninitialized -Wno-class-memaccess -Wno-redundant-move
[Touch-packages] [Bug 2023437]
The binutils-2_40-branch branch has been updated by Alan Modra : https://sourceware.org/git/gitweb.cgi?p=binutils- gdb.git;h=03f49a0619c5598eea80511efef5a88c4f7bb293 commit 03f49a0619c5598eea80511efef5a88c4f7bb293 Author: Alan Modra Date: Wed Jun 21 22:44:09 2023 +0930 PR30536, ppc64el gold linker produces unusable clang-16 binary In commit 0961e631575b, the fix for PR30217, make_lplt_section and make_brlt_section were changed to use rela_dyn_ rather than their own separate dynamic reloc sections. This fails miserably whenever brlt_ is needed for long branches, due to needing to iterate sizing and thus reset brlt_ sizes. PR 30536 PR 30217 * powerpc.cc (Target_powerpc::make_brlt_section): Don't use rela_dyn_. (cherry picked from commit dc808a2ebab337b5517add4c1aad298cf836c239) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/2023437 Title: ppc64el gold linker produces unusable clang-16 binary Status in binutils: Fix Released Status in binutils package in Ubuntu: New Bug description: root@Unimatrix08-Jammy:/clang# /usr/bin/g++-12 -O3 -fstack-protector-strong -Wformat -Werror=format-security -Wno-unused-command-line-argument -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -fno-semantic-interposition -fvisibility-inlines-hidden -Werror=date-time -Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wno-missing-field-initializers -pedantic -Wno-long-long -Wimplicit-fallthrough -Wno-maybe-uninitialized -Wno-class-memaccess -Wno-redundant-move -Wno-pessimizing-move -Wno-noexcept-type -Wdelete-non-virtual-dtor -Wsuggest-override -Wno-comment -Wno-misleading-indentation -Wctad-maybe-unsupported -fdiagnostics-color -ffunction-sections -fdata-sections -fdebug-prefix-map=/llvm-toolchain-16-16.0.5/build-llvm=build-llvm -fdebug-prefix-map=/llvm-toolchain-16-16.0.5/= -no-canonical-prefixes -ffile-prefix-map=/llvm-toolchain-16-16.0.5/build-llvm=build-llvm -ffile-prefix-map=/llvm-toolchain-16-16.0.5/= -no-canonical-prefixes -fno-common -Woverloaded-virtual -fno-strict-aliasi ng -O3 -DNDEBUG -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,--build-id -fuse-ld=bfd-Wl,--gc-sections tools/clang/tools/driver/CMakeFiles/clang.dir/driver.cpp.o tools/clang/tools/driver/CMakeFiles/clang.dir/cc1_main.cpp.o tools/clang/tools/driver/CMakeFiles/clang.dir/cc1as_main.cpp.o tools/clang/tools/driver/CMakeFiles/clang.dir/cc1gen_reproducer_main.cpp.o tools/clang/tools/driver/CMakeFiles/clang.dir/clang-driver.cpp.o -o bin/clang-16-bfd -Wl,-rpath,"\$ORIGIN/../lib:" lib/libLLVMPowerPCCodeGen.a lib/libLLVMPowerPCAsmParser.a lib/libLLVMPowerPCDesc.a lib/libLLVMPowerPCDisassembler.a lib/libLLVMPowerPCInfo.a lib/libLLVMAnalysis.a lib/libLLVMCodeGen.a lib/libLLVMCore.a lib/libLLVMipo.a lib/libLLVMAggressiveInstCombine.a lib/libLLVMInstCombine.a lib/libLLVMInstrumentation.a lib/libLLVMMC.a lib/libLLVMMCParser.a lib/libLLVMObjCARCOpts.a lib/libLLVMOption.a lib/libLLVMScalarOpts.a lib/libLLVMSupport.a lib/libLLVMTargetParser.a lib/libLLVMTransformUtils.a lib/libLL VMVectorize.a lib/libclangBasic.a lib/libclangCodeGen.a lib/libclangDriver.a lib/libclangFrontend.a lib/libclangFrontendTool.a lib/libclangSerialization.a lib/libLLVMAsmPrinter.a lib/libLLVMGlobalISel.a lib/libLLVMSelectionDAG.a lib/libLLVMMCDisassembler.a lib/libclangCodeGen.a lib/libLLVMCoverage.a lib/libLLVMLTO.a lib/libLLVMExtensions.a lib/libPolly.a lib/libPollyISL.a lib/libLLVMPasses.a lib/libLLVMCodeGen.a lib/libLLVMObjCARCOpts.a lib/libLLVMTarget.a lib/libLLVMCoroutines.a lib/libLLVMipo.a lib/libLLVMInstrumentation.a lib/libLLVMVectorize.a lib/libLLVMBitWriter.a lib/libLLVMLinker.a lib/libLLVMIRPrinter.a lib/libclangExtractAPI.a lib/libclangRewriteFrontend.a lib/libclangARCMigrate.a lib/libclangStaticAnalyzerFrontend.a lib/libclangStaticAnalyzerCheckers.a lib/libclangStaticAnalyzerCore.a lib/libclangCrossTU.a lib/libclangIndex.a lib/libclangFrontend.a lib/libclangDriver.a lib/libLLVMWindowsDriver.a lib/libLLVMOption.a lib/libclangParse .a lib/libclangSerialization.a lib/libclangSema.a lib/libclangAnalysis.a lib/libclangASTMatchers.a lib/libLLVMFrontendHLSL.a lib/libclangEdit.a lib/libclangSupport.a lib/libclangAST.a lib/libLLVMFrontendOpenMP.a lib/libLLVMScalarOpts.a lib/libLLVMAggressiveInstCombine.a lib/libLLVMInstCombine.a lib/libLLVMTransformUtils.a lib/libLLVMAnalysis.a lib/libLLVMProfileData.a lib/libLLVMSymbolize.a lib/libLLVMDebugInfoDWARF.a lib/libLLVMDebugInfoPDB.a lib/libLLVMObject.a lib/libLLVMMCParser.a lib/libLLVMMC.a lib/libLLVMIRReader.a lib/libLLVMBitReader.a lib/libLLVMAsmParser.a lib/libLLVMTextAPI.a lib/libLLVMDebugInfoCodeView.a lib/libLLVMDebugInfoMSF.a lib/libLLVMCore.a
[Touch-packages] [Bug 2023437]
The master branch has been updated by Alan Modra : https://sourceware.org/git/gitweb.cgi?p=binutils- gdb.git;h=dc808a2ebab337b5517add4c1aad298cf836c239 commit dc808a2ebab337b5517add4c1aad298cf836c239 Author: Alan Modra Date: Wed Jun 21 22:44:09 2023 +0930 PR30536, ppc64el gold linker produces unusable clang-16 binary In commit 0961e631575b, the fix for PR30217, make_lplt_section and make_brlt_section were changed to use rela_dyn_ rather than their own separate dynamic reloc sections. This fails miserably whenever brlt_ is needed for long branches, due to needing to iterate sizing and thus reset brlt_ sizes. PR 30536 PR 30217 * powerpc.cc (Target_powerpc::make_brlt_section): Don't use rela_dyn_. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/2023437 Title: ppc64el gold linker produces unusable clang-16 binary Status in binutils: Fix Released Status in binutils package in Ubuntu: New Bug description: root@Unimatrix08-Jammy:/clang# /usr/bin/g++-12 -O3 -fstack-protector-strong -Wformat -Werror=format-security -Wno-unused-command-line-argument -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -fno-semantic-interposition -fvisibility-inlines-hidden -Werror=date-time -Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wno-missing-field-initializers -pedantic -Wno-long-long -Wimplicit-fallthrough -Wno-maybe-uninitialized -Wno-class-memaccess -Wno-redundant-move -Wno-pessimizing-move -Wno-noexcept-type -Wdelete-non-virtual-dtor -Wsuggest-override -Wno-comment -Wno-misleading-indentation -Wctad-maybe-unsupported -fdiagnostics-color -ffunction-sections -fdata-sections -fdebug-prefix-map=/llvm-toolchain-16-16.0.5/build-llvm=build-llvm -fdebug-prefix-map=/llvm-toolchain-16-16.0.5/= -no-canonical-prefixes -ffile-prefix-map=/llvm-toolchain-16-16.0.5/build-llvm=build-llvm -ffile-prefix-map=/llvm-toolchain-16-16.0.5/= -no-canonical-prefixes -fno-common -Woverloaded-virtual -fno-strict-aliasi ng -O3 -DNDEBUG -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,--build-id -fuse-ld=bfd-Wl,--gc-sections tools/clang/tools/driver/CMakeFiles/clang.dir/driver.cpp.o tools/clang/tools/driver/CMakeFiles/clang.dir/cc1_main.cpp.o tools/clang/tools/driver/CMakeFiles/clang.dir/cc1as_main.cpp.o tools/clang/tools/driver/CMakeFiles/clang.dir/cc1gen_reproducer_main.cpp.o tools/clang/tools/driver/CMakeFiles/clang.dir/clang-driver.cpp.o -o bin/clang-16-bfd -Wl,-rpath,"\$ORIGIN/../lib:" lib/libLLVMPowerPCCodeGen.a lib/libLLVMPowerPCAsmParser.a lib/libLLVMPowerPCDesc.a lib/libLLVMPowerPCDisassembler.a lib/libLLVMPowerPCInfo.a lib/libLLVMAnalysis.a lib/libLLVMCodeGen.a lib/libLLVMCore.a lib/libLLVMipo.a lib/libLLVMAggressiveInstCombine.a lib/libLLVMInstCombine.a lib/libLLVMInstrumentation.a lib/libLLVMMC.a lib/libLLVMMCParser.a lib/libLLVMObjCARCOpts.a lib/libLLVMOption.a lib/libLLVMScalarOpts.a lib/libLLVMSupport.a lib/libLLVMTargetParser.a lib/libLLVMTransformUtils.a lib/libLL VMVectorize.a lib/libclangBasic.a lib/libclangCodeGen.a lib/libclangDriver.a lib/libclangFrontend.a lib/libclangFrontendTool.a lib/libclangSerialization.a lib/libLLVMAsmPrinter.a lib/libLLVMGlobalISel.a lib/libLLVMSelectionDAG.a lib/libLLVMMCDisassembler.a lib/libclangCodeGen.a lib/libLLVMCoverage.a lib/libLLVMLTO.a lib/libLLVMExtensions.a lib/libPolly.a lib/libPollyISL.a lib/libLLVMPasses.a lib/libLLVMCodeGen.a lib/libLLVMObjCARCOpts.a lib/libLLVMTarget.a lib/libLLVMCoroutines.a lib/libLLVMipo.a lib/libLLVMInstrumentation.a lib/libLLVMVectorize.a lib/libLLVMBitWriter.a lib/libLLVMLinker.a lib/libLLVMIRPrinter.a lib/libclangExtractAPI.a lib/libclangRewriteFrontend.a lib/libclangARCMigrate.a lib/libclangStaticAnalyzerFrontend.a lib/libclangStaticAnalyzerCheckers.a lib/libclangStaticAnalyzerCore.a lib/libclangCrossTU.a lib/libclangIndex.a lib/libclangFrontend.a lib/libclangDriver.a lib/libLLVMWindowsDriver.a lib/libLLVMOption.a lib/libclangParse .a lib/libclangSerialization.a lib/libclangSema.a lib/libclangAnalysis.a lib/libclangASTMatchers.a lib/libLLVMFrontendHLSL.a lib/libclangEdit.a lib/libclangSupport.a lib/libclangAST.a lib/libLLVMFrontendOpenMP.a lib/libLLVMScalarOpts.a lib/libLLVMAggressiveInstCombine.a lib/libLLVMInstCombine.a lib/libLLVMTransformUtils.a lib/libLLVMAnalysis.a lib/libLLVMProfileData.a lib/libLLVMSymbolize.a lib/libLLVMDebugInfoDWARF.a lib/libLLVMDebugInfoPDB.a lib/libLLVMObject.a lib/libLLVMMCParser.a lib/libLLVMMC.a lib/libLLVMIRReader.a lib/libLLVMBitReader.a lib/libLLVMAsmParser.a lib/libLLVMTextAPI.a lib/libLLVMDebugInfoCodeView.a lib/libLLVMDebugInfoMSF.a lib/libLLVMCore.a lib/libLLVMBinaryFormat.a lib/libLLVMRemarks.a lib/libLLVMBitstreamReader.a lib/libclangFormat.a
[Touch-packages] [Bug 2023437]
I've been going down the wrong rabbit hole, I should have asked you at the outset to post the result of your g++ command with -v added. That would have shown your compiler is defaulting to PIEs while mine is not. Adding -pie to the gold command line shows a huge number of relative dynamic relocations are missing from 2.40 and mainline compared to 2.39. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/2023437 Title: ppc64el gold linker produces unusable clang-16 binary Status in binutils: Fix Released Status in binutils package in Ubuntu: New Bug description: root@Unimatrix08-Jammy:/clang# /usr/bin/g++-12 -O3 -fstack-protector-strong -Wformat -Werror=format-security -Wno-unused-command-line-argument -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -fno-semantic-interposition -fvisibility-inlines-hidden -Werror=date-time -Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wno-missing-field-initializers -pedantic -Wno-long-long -Wimplicit-fallthrough -Wno-maybe-uninitialized -Wno-class-memaccess -Wno-redundant-move -Wno-pessimizing-move -Wno-noexcept-type -Wdelete-non-virtual-dtor -Wsuggest-override -Wno-comment -Wno-misleading-indentation -Wctad-maybe-unsupported -fdiagnostics-color -ffunction-sections -fdata-sections -fdebug-prefix-map=/llvm-toolchain-16-16.0.5/build-llvm=build-llvm -fdebug-prefix-map=/llvm-toolchain-16-16.0.5/= -no-canonical-prefixes -ffile-prefix-map=/llvm-toolchain-16-16.0.5/build-llvm=build-llvm -ffile-prefix-map=/llvm-toolchain-16-16.0.5/= -no-canonical-prefixes -fno-common -Woverloaded-virtual -fno-strict-aliasi ng -O3 -DNDEBUG -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,--build-id -fuse-ld=bfd-Wl,--gc-sections tools/clang/tools/driver/CMakeFiles/clang.dir/driver.cpp.o tools/clang/tools/driver/CMakeFiles/clang.dir/cc1_main.cpp.o tools/clang/tools/driver/CMakeFiles/clang.dir/cc1as_main.cpp.o tools/clang/tools/driver/CMakeFiles/clang.dir/cc1gen_reproducer_main.cpp.o tools/clang/tools/driver/CMakeFiles/clang.dir/clang-driver.cpp.o -o bin/clang-16-bfd -Wl,-rpath,"\$ORIGIN/../lib:" lib/libLLVMPowerPCCodeGen.a lib/libLLVMPowerPCAsmParser.a lib/libLLVMPowerPCDesc.a lib/libLLVMPowerPCDisassembler.a lib/libLLVMPowerPCInfo.a lib/libLLVMAnalysis.a lib/libLLVMCodeGen.a lib/libLLVMCore.a lib/libLLVMipo.a lib/libLLVMAggressiveInstCombine.a lib/libLLVMInstCombine.a lib/libLLVMInstrumentation.a lib/libLLVMMC.a lib/libLLVMMCParser.a lib/libLLVMObjCARCOpts.a lib/libLLVMOption.a lib/libLLVMScalarOpts.a lib/libLLVMSupport.a lib/libLLVMTargetParser.a lib/libLLVMTransformUtils.a lib/libLL VMVectorize.a lib/libclangBasic.a lib/libclangCodeGen.a lib/libclangDriver.a lib/libclangFrontend.a lib/libclangFrontendTool.a lib/libclangSerialization.a lib/libLLVMAsmPrinter.a lib/libLLVMGlobalISel.a lib/libLLVMSelectionDAG.a lib/libLLVMMCDisassembler.a lib/libclangCodeGen.a lib/libLLVMCoverage.a lib/libLLVMLTO.a lib/libLLVMExtensions.a lib/libPolly.a lib/libPollyISL.a lib/libLLVMPasses.a lib/libLLVMCodeGen.a lib/libLLVMObjCARCOpts.a lib/libLLVMTarget.a lib/libLLVMCoroutines.a lib/libLLVMipo.a lib/libLLVMInstrumentation.a lib/libLLVMVectorize.a lib/libLLVMBitWriter.a lib/libLLVMLinker.a lib/libLLVMIRPrinter.a lib/libclangExtractAPI.a lib/libclangRewriteFrontend.a lib/libclangARCMigrate.a lib/libclangStaticAnalyzerFrontend.a lib/libclangStaticAnalyzerCheckers.a lib/libclangStaticAnalyzerCore.a lib/libclangCrossTU.a lib/libclangIndex.a lib/libclangFrontend.a lib/libclangDriver.a lib/libLLVMWindowsDriver.a lib/libLLVMOption.a lib/libclangParse .a lib/libclangSerialization.a lib/libclangSema.a lib/libclangAnalysis.a lib/libclangASTMatchers.a lib/libLLVMFrontendHLSL.a lib/libclangEdit.a lib/libclangSupport.a lib/libclangAST.a lib/libLLVMFrontendOpenMP.a lib/libLLVMScalarOpts.a lib/libLLVMAggressiveInstCombine.a lib/libLLVMInstCombine.a lib/libLLVMTransformUtils.a lib/libLLVMAnalysis.a lib/libLLVMProfileData.a lib/libLLVMSymbolize.a lib/libLLVMDebugInfoDWARF.a lib/libLLVMDebugInfoPDB.a lib/libLLVMObject.a lib/libLLVMMCParser.a lib/libLLVMMC.a lib/libLLVMIRReader.a lib/libLLVMBitReader.a lib/libLLVMAsmParser.a lib/libLLVMTextAPI.a lib/libLLVMDebugInfoCodeView.a lib/libLLVMDebugInfoMSF.a lib/libLLVMCore.a lib/libLLVMBinaryFormat.a lib/libLLVMRemarks.a lib/libLLVMBitstreamReader.a lib/libclangFormat.a lib/libclangToolingInclusions.a lib/libclangToolingCore.a lib/libclangRewrite.a lib/libclangLex.a lib/libclangBasic.a lib/libLLVMTargetParser.a lib/libLLVMSupport.a lib/libLLVMDemangle.a -l rt -ldl -lm /usr/lib/powerpc64le-linux-gnu/libz.so /usr/lib/powerpc64le-linux-gnu/libtinfo.so root@Unimatrix08-Jammy:/clang# /usr/bin/g++-12 -O3 -fstack-protector-strong -Wformat -Werror=format-security -Wno-unused-command-line-argument
[Touch-packages] [Bug 2023437]
Created attachment 14939 crt*.o files -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/2023437 Title: ppc64el gold linker produces unusable clang-16 binary Status in binutils: Fix Released Status in binutils package in Ubuntu: New Bug description: root@Unimatrix08-Jammy:/clang# /usr/bin/g++-12 -O3 -fstack-protector-strong -Wformat -Werror=format-security -Wno-unused-command-line-argument -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -fno-semantic-interposition -fvisibility-inlines-hidden -Werror=date-time -Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wno-missing-field-initializers -pedantic -Wno-long-long -Wimplicit-fallthrough -Wno-maybe-uninitialized -Wno-class-memaccess -Wno-redundant-move -Wno-pessimizing-move -Wno-noexcept-type -Wdelete-non-virtual-dtor -Wsuggest-override -Wno-comment -Wno-misleading-indentation -Wctad-maybe-unsupported -fdiagnostics-color -ffunction-sections -fdata-sections -fdebug-prefix-map=/llvm-toolchain-16-16.0.5/build-llvm=build-llvm -fdebug-prefix-map=/llvm-toolchain-16-16.0.5/= -no-canonical-prefixes -ffile-prefix-map=/llvm-toolchain-16-16.0.5/build-llvm=build-llvm -ffile-prefix-map=/llvm-toolchain-16-16.0.5/= -no-canonical-prefixes -fno-common -Woverloaded-virtual -fno-strict-aliasi ng -O3 -DNDEBUG -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,--build-id -fuse-ld=bfd-Wl,--gc-sections tools/clang/tools/driver/CMakeFiles/clang.dir/driver.cpp.o tools/clang/tools/driver/CMakeFiles/clang.dir/cc1_main.cpp.o tools/clang/tools/driver/CMakeFiles/clang.dir/cc1as_main.cpp.o tools/clang/tools/driver/CMakeFiles/clang.dir/cc1gen_reproducer_main.cpp.o tools/clang/tools/driver/CMakeFiles/clang.dir/clang-driver.cpp.o -o bin/clang-16-bfd -Wl,-rpath,"\$ORIGIN/../lib:" lib/libLLVMPowerPCCodeGen.a lib/libLLVMPowerPCAsmParser.a lib/libLLVMPowerPCDesc.a lib/libLLVMPowerPCDisassembler.a lib/libLLVMPowerPCInfo.a lib/libLLVMAnalysis.a lib/libLLVMCodeGen.a lib/libLLVMCore.a lib/libLLVMipo.a lib/libLLVMAggressiveInstCombine.a lib/libLLVMInstCombine.a lib/libLLVMInstrumentation.a lib/libLLVMMC.a lib/libLLVMMCParser.a lib/libLLVMObjCARCOpts.a lib/libLLVMOption.a lib/libLLVMScalarOpts.a lib/libLLVMSupport.a lib/libLLVMTargetParser.a lib/libLLVMTransformUtils.a lib/libLL VMVectorize.a lib/libclangBasic.a lib/libclangCodeGen.a lib/libclangDriver.a lib/libclangFrontend.a lib/libclangFrontendTool.a lib/libclangSerialization.a lib/libLLVMAsmPrinter.a lib/libLLVMGlobalISel.a lib/libLLVMSelectionDAG.a lib/libLLVMMCDisassembler.a lib/libclangCodeGen.a lib/libLLVMCoverage.a lib/libLLVMLTO.a lib/libLLVMExtensions.a lib/libPolly.a lib/libPollyISL.a lib/libLLVMPasses.a lib/libLLVMCodeGen.a lib/libLLVMObjCARCOpts.a lib/libLLVMTarget.a lib/libLLVMCoroutines.a lib/libLLVMipo.a lib/libLLVMInstrumentation.a lib/libLLVMVectorize.a lib/libLLVMBitWriter.a lib/libLLVMLinker.a lib/libLLVMIRPrinter.a lib/libclangExtractAPI.a lib/libclangRewriteFrontend.a lib/libclangARCMigrate.a lib/libclangStaticAnalyzerFrontend.a lib/libclangStaticAnalyzerCheckers.a lib/libclangStaticAnalyzerCore.a lib/libclangCrossTU.a lib/libclangIndex.a lib/libclangFrontend.a lib/libclangDriver.a lib/libLLVMWindowsDriver.a lib/libLLVMOption.a lib/libclangParse .a lib/libclangSerialization.a lib/libclangSema.a lib/libclangAnalysis.a lib/libclangASTMatchers.a lib/libLLVMFrontendHLSL.a lib/libclangEdit.a lib/libclangSupport.a lib/libclangAST.a lib/libLLVMFrontendOpenMP.a lib/libLLVMScalarOpts.a lib/libLLVMAggressiveInstCombine.a lib/libLLVMInstCombine.a lib/libLLVMTransformUtils.a lib/libLLVMAnalysis.a lib/libLLVMProfileData.a lib/libLLVMSymbolize.a lib/libLLVMDebugInfoDWARF.a lib/libLLVMDebugInfoPDB.a lib/libLLVMObject.a lib/libLLVMMCParser.a lib/libLLVMMC.a lib/libLLVMIRReader.a lib/libLLVMBitReader.a lib/libLLVMAsmParser.a lib/libLLVMTextAPI.a lib/libLLVMDebugInfoCodeView.a lib/libLLVMDebugInfoMSF.a lib/libLLVMCore.a lib/libLLVMBinaryFormat.a lib/libLLVMRemarks.a lib/libLLVMBitstreamReader.a lib/libclangFormat.a lib/libclangToolingInclusions.a lib/libclangToolingCore.a lib/libclangRewrite.a lib/libclangLex.a lib/libclangBasic.a lib/libLLVMTargetParser.a lib/libLLVMSupport.a lib/libLLVMDemangle.a -l rt -ldl -lm /usr/lib/powerpc64le-linux-gnu/libz.so /usr/lib/powerpc64le-linux-gnu/libtinfo.so root@Unimatrix08-Jammy:/clang# /usr/bin/g++-12 -O3 -fstack-protector-strong -Wformat -Werror=format-security -Wno-unused-command-line-argument -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -fno-semantic-interposition -fvisibility-inlines-hidden -Werror=date-time -Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wno-missing-field-initializers -pedantic -Wno-long-long -Wimplicit-fallthrough -Wno-maybe-uninitialized -Wno-class-memaccess
[Touch-packages] [Bug 2024585] Re: dbus-daemon segfault if group lookup fails
The attachment "dbus-reload-segv.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/2024585 Title: dbus-daemon segfault if group lookup fails Status in dbus package in Ubuntu: New Bug description: Ubuntu release: Ubuntu 22.04.2 LTS (but also tested on Ubuntu 20.04.6 LTS) dbus version: 1.12.20-2ubuntu4.1 This is related to https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/2023598, in which an sssd was upgraded before its libraries. This caused dbus-daemon to crash, which in turn ended the user's X session along with many other programs. It also triggered NetworkManager to exit so it was no longer doing DHCP renewals; he network connection was lost a few hours later when the lease expired. The failure of dbus-daemon was triggered by it reloading its configuration while group lookups were not functioning, which revealed an error in the dbus's error handling code. The failure happened in two stages. First, it failed to load the policy, and reported this error: dbus-daemon[1207]: Unable to reload configuration: (null) Then, a few seconds later, dbus-daemon reloaded its config again, and this time it segfaulted. dbus-daemon[1207]: segfault at 0 ip 5602b18336e4 sp 7ffe2579de28 error 6 in dbus-daemon[5602b181b000+24000] Code: 00 00 00 48 83 c4 08 c3 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 f3 0f 1e fa 83 07 01 48 89 f8 c3 0f 1f 44 00 00 f3 0f 1e fa <83> 2f 01 74 07 c3 66 0f 1f 44 00 00 e9 bb fb ff ff 66 66 2e 0f 1f The code corresponds to policy->refcount -= 1, inside bus_client_policy_unref(). This error can only happen if policy was NULL on entry. bus_connections_reload_policy() has this code: // connection.c line 1644 bus_client_policy_unref (d->policy); d->policy = bus_context_create_client_policy (connections->context, connection, error); if (d->policy == NULL) { _dbus_verbose ("Failed to create security policy for connection %p\n", connection); _DBUS_ASSERT_ERROR_IS_SET (error); return FALSE; } If bus_context_create_client_policy fails, the code decrements the policy reference count and sets d->policy to NULL. The second time round, the reference count is decremented again, but policy is already NULL from last time round, hence the crash. I've included a patch that I think should fix the error, but note that it is not well tested! Peter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/2024585/+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 2024560] Re: Check if 0010-set-language needs to be update for the new languages property
I'll comment on this in a bit. Busy with another thing ATM. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/2024560 Title: Check if 0010-set-language needs to be update for the new languages property Status in accountsservice package in Ubuntu: New Bug description: Upstream did changes to add a languages properties https://gitlab.freedesktop.org/accountsservice/accountsservice/-/commit/881e0ea7 I've rebased 0010-set-language to apply correctly but we should review if we need to adapt the patch to apply a similar logic to the new languages property that it's doing for old language one To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/2024560/+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 1985057] Re: Camera output freeze when using pipewiresrc
I am setting the bug status to Incomplete. ** Changed in: pipewire (Ubuntu Jammy) Status: Triaged => Incomplete ** Changed in: gstreamer1.0 (Ubuntu Jammy) Status: New => Incomplete ** Changed in: gst-plugins-base1.0 (Ubuntu Jammy) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1985057 Title: Camera output freeze when using pipewiresrc Status in OEM Priority Project: New Status in gst-plugins-base1.0 package in Ubuntu: New Status in gstreamer1.0 package in Ubuntu: New Status in pipewire package in Ubuntu: Fix Released Status in gst-plugins-base1.0 source package in Jammy: Incomplete Status in gstreamer1.0 source package in Jammy: Incomplete Status in pipewire source package in Jammy: Incomplete Bug description: [Impact] On Dell platform with Microdia Integrated webcam, the Cheese preview is stuck on jammy. The gst-launch-1.0 command suggested by gst-device-monitor-1.0 can reproduce it too. [Test Plan] 1. Install Jammy on the hardware issue reported, and hardware didn't report the issue to avoid the regression hardware list: a. 0bda:58ff Realtek Semiconductor Corp. Integrated_Webcam_HD b. 0c45:6747 Microdia Integrated_Webcam_HD c. 0c45:6a14 Microdia Integrated_Webcam_HD d. 1bcf:28d0 Sunplus Innovation Technology Inc. Integrated_Webcam_5M e. 04f2:b76b Chicony Electronics Co., Ltd HP HD Camera f. 0408:545a Quanta Computer, Inc. HP 5MP Camera g. 0408:5483 Quanta Computer, Inc. HP HD Camera h. 174f:2459 Syntek Integrated Camera (ThinkBook 14 Gen 4) i. 5986:116d Acer, Inc Integrated Camera (ThinkCentre Neo 50a) j. 0bda:5556 Realtek Semiconductor Corp. Integrated_Webcam_FHD 2. try to install the updated pipewire packages (= 0.3.48-1ubuntu2) 3. $ sudo reboot 4. Check if gst-launch-1.0 work a. $ gst-device-monitor-1.0 Video/Source to get caps and suggest gst-launch-1.0 command b. $ gst-launch-1.0 pipewiresrc path= ! ! decodebin ! videoconvert ! glimagesink c. Check if the result ok 5. Check the screencast function by pressing 'prt sc' a. the screenshot of all screen/selected region should work good b. the screenrecord of all screen/selected region should work good 6. Check that video recording in gnome-shell works - use Ctrl+Shift+Alt+R to start a recording, stop it from the indicator, verify that there is a new entry in ~/Video 7. Check that screen sharing is working - go to settings, screen sharing and enable the feature - try to connect using rdp/vnc from another client do those steps under wayland and unset X [Where problems could occur] The patches try to dequeue the shared buffer, instead of pool buffer to prevent the pool buffer being corrupted. it might cause some camera preview failed if shared buffer is corrupted. It is in upstream from 0.3.52 to 0.3.56, and there is no regression found, so the risk is low. [Other Info] Upstream commits: https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/7cc509b117a6db66c395fb56ac4f17fb8cbd0c92 https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/a1f33a99df5756c3dedd68f5ba2690819098d14f To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1985057/+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 1815101] Re: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted)
** Changed in: keepalived (Ubuntu) Assignee: (unassigned) => Athos Ribeiro (athos-ribeiro) -- 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/1815101 Title: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted) Status in netplan: Triaged Status in heartbeat package in Ubuntu: Won't Fix Status in keepalived package in Ubuntu: In Progress Status in systemd package in Ubuntu: Fix Released Status in keepalived source package in Xenial: Confirmed Status in systemd source package in Xenial: Won't Fix Status in keepalived source package in Bionic: Confirmed Status in systemd source package in Bionic: Fix Released Status in systemd source package in Disco: Won't Fix Status in systemd source package in Eoan: Fix Released Status in keepalived source package in Focal: Confirmed Status in systemd source package in Focal: Fix Released Bug description: [impact] - ALL related HA software has a small problem if interfaces are being managed by systemd-networkd: nic restarts/reconfigs are always going to wipe all interfaces aliases when HA software is not expecting it to (no coordination between them. - keepalived, smb ctdb, pacemaker, all suffer from this. Pacemaker is smarter in this case because it has a service monitor that will restart the virtual IP resource, in affected node & nic, before considering a real failure, but other HA service might consider a real failure when it is not. [test case] - comment #14 is a full test case: to have 3 node pacemaker, in that example, and cause a networkd service restart: it will trigger a failure for the virtual IP resource monitor. - other example is given in the original description for keepalived. both suffer from the same issue (and other HA softwares as well). [regression potential] - this backports KeepConfiguration parameter, which adds some significant complexity to networkd's configuration and behavior, which could lead to regressions in correctly configuring the network at networkd start, or incorrectly maintaining configuration at networkd restart, or losing network state at networkd stop. - Any regressions are most likely to occur during networkd start, restart, or stop, and most likely to involve missing or incorrect ip address(es). - the change is based in upstream patches adding the exact feature we needed to fix this issue & it will be integrated with a netplan change to add the needed stanza to systemd nic configuration file (KeepConfiguration=) [other info] original description: --- Configure netplan for interfaces, for example (a working config with IP addresses obfuscated) network: ethernets: eth0: addresses: [192.168.0.5/24] dhcp4: false nameservers: search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, phone.blah.com] addresses: [10.22.11.1] eth2: addresses: - 12.13.14.18/29 - 12.13.14.19/29 gateway4: 12.13.14.17 dhcp4: false nameservers: search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, phone.blah.com] addresses: [10.22.11.1] eth3: addresses: [10.22.11.6/24] dhcp4: false nameservers: search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, phone.blah.com] addresses: [10.22.11.1] eth4: addresses: [10.22.14.6/24] dhcp4: false nameservers: search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, phone.blah.com] addresses: [10.22.11.1] eth7: addresses: [9.5.17.34/29] dhcp4: false optional: true nameservers: search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, phone.blah.com] addresses: [10.22.11.1] version: 2 Configure keepalived (again, a working config with IP addresses obfuscated) global_defs # Block id { notification_email { sysadm...@blah.com } notification_email_from keepali...@system3.hq.blah.com smtp_server 10.22.11.7 # IP smtp_connect_timeout 30 # integer, seconds router_id system3 # string identifying the machine, # (doesn't have to be hostname). vrrp_mcast_group4 224.0.0.18 # optional, default 224.0.0.18 vrrp_mcast_group6 ff02::12 # optional, default ff02::12 enable_traps # enable SNMP traps } vrrp_sync_group collection { group {
[Touch-packages] [Bug 2024560] Re: Check if 0010-set-language needs to be update for the new languages property
I also had to revert https://gitlab.freedesktop.org/accountsservice/accountsservice/-/commit/bed11bbe (language-not-xpg.patch in the new upload) otherwise trying to move french over the top english entry in gnome- language-selector would error out > dbus.exceptions.DBusException: org.freedesktop.DBus.Error.InvalidArgs: Locale 'fr_FR:en' is not a valid XPG-formatted locale -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/2024560 Title: Check if 0010-set-language needs to be update for the new languages property Status in accountsservice package in Ubuntu: New Bug description: Upstream did changes to add a languages properties https://gitlab.freedesktop.org/accountsservice/accountsservice/-/commit/881e0ea7 I've rebased 0010-set-language to apply correctly but we should review if we need to adapt the patch to apply a similar logic to the new languages property that it's doing for old language one To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/2024560/+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 2021498] Re: Please merge 3.134 into mantic
Uploaded adduser 3.134ubuntu1 and pushed to https://code.launchpad.net/~ubuntu-core- dev/ubuntu/+source/adduser/+git/adduser/+ref/ubuntu/devel with some small changes: * Add commit "Update doc translation" with the changes that come from building the source * Fix the lintian warning: debian-changelog-has-wrong-day-of-week 2023-06-20 was a Tuesday * Changed the description of your top commit from "Changelog" to "Release adduser 3.134ubuntu1" Thanks for your contribution and the added test case. ** Changed in: adduser (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to adduser in Ubuntu. https://bugs.launchpad.net/bugs/2021498 Title: Please merge 3.134 into mantic Status in adduser package in Ubuntu: Fix Committed Bug description: The upstream version 3.134 should be merged into mantic. The current version is 3.129ubuntu1. See the merge conflict report: https://merges.ubuntu.com/a/adduser/REPORT Note: this is a tracking bug PPA for review: https://launchpad.net/~mateus- morais/+archive/ubuntu/adduser-merge-mantic-3.134-lp2021498 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/2021498/+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 2024585] [NEW] dbus-daemon segfault if group lookup fails
Public bug reported: Ubuntu release: Ubuntu 22.04.2 LTS (but also tested on Ubuntu 20.04.6 LTS) dbus version: 1.12.20-2ubuntu4.1 This is related to https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/2023598, in which an sssd was upgraded before its libraries. This caused dbus-daemon to crash, which in turn ended the user's X session along with many other programs. It also triggered NetworkManager to exit so it was no longer doing DHCP renewals; he network connection was lost a few hours later when the lease expired. The failure of dbus-daemon was triggered by it reloading its configuration while group lookups were not functioning, which revealed an error in the dbus's error handling code. The failure happened in two stages. First, it failed to load the policy, and reported this error: dbus-daemon[1207]: Unable to reload configuration: (null) Then, a few seconds later, dbus-daemon reloaded its config again, and this time it segfaulted. dbus-daemon[1207]: segfault at 0 ip 5602b18336e4 sp 7ffe2579de28 error 6 in dbus-daemon[5602b181b000+24000] Code: 00 00 00 48 83 c4 08 c3 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 f3 0f 1e fa 83 07 01 48 89 f8 c3 0f 1f 44 00 00 f3 0f 1e fa <83> 2f 01 74 07 c3 66 0f 1f 44 00 00 e9 bb fb ff ff 66 66 2e 0f 1f The code corresponds to policy->refcount -= 1, inside bus_client_policy_unref(). This error can only happen if policy was NULL on entry. bus_connections_reload_policy() has this code: // connection.c line 1644 bus_client_policy_unref (d->policy); d->policy = bus_context_create_client_policy (connections->context, connection, error); if (d->policy == NULL) { _dbus_verbose ("Failed to create security policy for connection %p\n", connection); _DBUS_ASSERT_ERROR_IS_SET (error); return FALSE; } If bus_context_create_client_policy fails, the code decrements the policy reference count and sets d->policy to NULL. The second time round, the reference count is decremented again, but policy is already NULL from last time round, hence the crash. I've included a patch that I think should fix the error, but note that it is not well tested! Peter ** Affects: dbus (Ubuntu) Importance: Undecided Status: New ** Patch added: "dbus-reload-segv.patch" https://bugs.launchpad.net/bugs/2024585/+attachment/5681228/+files/dbus-reload-segv.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/2024585 Title: dbus-daemon segfault if group lookup fails Status in dbus package in Ubuntu: New Bug description: Ubuntu release: Ubuntu 22.04.2 LTS (but also tested on Ubuntu 20.04.6 LTS) dbus version: 1.12.20-2ubuntu4.1 This is related to https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/2023598, in which an sssd was upgraded before its libraries. This caused dbus-daemon to crash, which in turn ended the user's X session along with many other programs. It also triggered NetworkManager to exit so it was no longer doing DHCP renewals; he network connection was lost a few hours later when the lease expired. The failure of dbus-daemon was triggered by it reloading its configuration while group lookups were not functioning, which revealed an error in the dbus's error handling code. The failure happened in two stages. First, it failed to load the policy, and reported this error: dbus-daemon[1207]: Unable to reload configuration: (null) Then, a few seconds later, dbus-daemon reloaded its config again, and this time it segfaulted. dbus-daemon[1207]: segfault at 0 ip 5602b18336e4 sp 7ffe2579de28 error 6 in dbus-daemon[5602b181b000+24000] Code: 00 00 00 48 83 c4 08 c3 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 f3 0f 1e fa 83 07 01 48 89 f8 c3 0f 1f 44 00 00 f3 0f 1e fa <83> 2f 01 74 07 c3 66 0f 1f 44 00 00 e9 bb fb ff ff 66 66 2e 0f 1f The code corresponds to policy->refcount -= 1, inside bus_client_policy_unref(). This error can only happen if policy was NULL on entry. bus_connections_reload_policy() has this code: // connection.c line 1644 bus_client_policy_unref (d->policy); d->policy = bus_context_create_client_policy (connections->context, connection, error); if (d->policy == NULL) { _dbus_verbose ("Failed to create security policy for connection %p\n", connection); _DBUS_ASSERT_ERROR_IS_SET (error); return FALSE; } If bus_context_create_client_policy fails, the code decrements the policy reference count and sets d->policy to NULL. The second time round, the
[Touch-packages] [Bug 2019856] Re: Add missing ARM-cores to support Grace-based systems
I was about to ask *why* Ubuntu users need this change before I read Steve's comment. It might be helpful to expand on that, because without a full explanation, we (SRU team) are only really _speculating_ on the actual user impact. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/2019856 Title: Add missing ARM-cores to support Grace-based systems Status in util-linux package in Ubuntu: Fix Released Status in util-linux source package in Jammy: In Progress Status in util-linux source package in Kinetic: Won't Fix Status in util-linux source package in Lunar: Incomplete Status in util-linux source package in Mantic: Fix Released Bug description: [Impact] When running "lscpu" on a Grace-based system + Ubuntu 22.04, it doesn't report a model name: Vendor ID: ARM Model: 0 [Fix] Adding the additional arm_part to sys-utils/lscpu-arm.c solves the problem. The commit below adds the specific codes missing from Jammy's version. https://github.com/util-linux/util- linux/commit/6857cccbb4157d5da34ca98f77a0ac9d68e1e740 [Test Steps] * Verify whether output of lscpu is correct on new CPUs; eg: Vendor ID: ARM Model name: Neoverse-V2 * Verify whether output of lscpu doesn't change on old CPUs; eg: Vendor ID: ARM Model name: Neoverse-N1 [What Could Go Wrong] The fix only introduces additional model identifiers to match against and print a model name string, thus regression impact should be contained within lscpu and printing cpus model name on ARM systems. Output doesn't change on systems with non-affected CPU models. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/2019856/+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 2024560] Re: Check if 0010-set-language needs to be update for the new languages property
** Changed in: accountsservice (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/2024560 Title: Check if 0010-set-language needs to be update for the new languages property Status in accountsservice package in Ubuntu: New Bug description: Upstream did changes to add a languages properties https://gitlab.freedesktop.org/accountsservice/accountsservice/-/commit/881e0ea7 I've rebased 0010-set-language to apply correctly but we should review if we need to adapt the patch to apply a similar logic to the new languages property that it's doing for old language one To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/2024560/+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 2024560] Re: Check if 0010-set-language needs to be update for the new languages property
** Tags added: udeng-833 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/2024560 Title: Check if 0010-set-language needs to be update for the new languages property Status in accountsservice package in Ubuntu: New Bug description: Upstream did changes to add a languages properties https://gitlab.freedesktop.org/accountsservice/accountsservice/-/commit/881e0ea7 I've rebased 0010-set-language to apply correctly but we should review if we need to adapt the patch to apply a similar logic to the new languages property that it's doing for old language one To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/2024560/+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 1933828] Re: NTP servers from DHCP are not propagated to timesyncd
This issue is also present on Bionic. Is there a chance that the network manager would be fixed in Bionic, as part of Ubuntu Pro? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1933828 Title: NTP servers from DHCP are not propagated to timesyncd Status in OEM Priority Project: New Status in network-manager package in Ubuntu: Confirmed Status in network-manager source package in Focal: Confirmed Bug description: Network manager gets NTP servers from DHCP but do not update timesyncd to use it which keeps using ntp.ubuntu.com. This is a problem on private networks which do not have access to public internet. On this type of network the configuration of timesyncd must be updated manually instead of inheriting the conf from the dhcp servers. This can be integrated with a NM dispatcher script such as below: etc/NetworkManager/dispatcher.d/10-update-timesyncd for example: ==8<=8<=8<=8<=8<== #! /usr/bin/bash [ -n "$CONNECTION_UUID" ] || exit INTERFACE=$1 ACTION=$2 case $ACTION in up | dhcp4-change | dhcp6-change) [ -n "$DHCP4_NTP_SERVERS" ] || exit mkdir -p /etc/systemd/timesyncd.conf.d/ cat< /etc/systemd/timesyncd.conf.d/$CONNECTION_UUID.conf [Time] NTP=$DHCP4_NTP_SERVERS RootDistanceMaxSec=15 EOF systemctl restart systemd-timesyncd ;; down) rm -f /etc/systemd/timesyncd.conf.d/$CONNECTION_UUID.conf systemctl restart systemd-timesyncd ;; esac ==8<=8<=8<=8<=8<== ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: network-manager 1.30.0-1ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-18.19+21.10.1-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jun 28 14:08:52 2021 InstallationDate: Installed on 2020-05-31 (393 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527) RebootRequiredPkgs: linux-image-5.11.0-20-generic linux-base SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.30.0 connected started full enabled enabled disabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1933828/+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 2011385] Re: [950XED, Realtek ALC298, Speaker, Internal] No sound at all
Same issue on Razer Blade 16 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2011385 Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: only bluetooth can work,im sungsang book2 pro ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wang 1658 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 13 15:41:47 2023 InstallationDate: Installed on 2023-03-08 (4 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wang 1658 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P08RGF.054.220817.ZQ dmi.board.asset.tag: No Asset Tag dmi.board.name: NT950XEW-A51AS dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGLFREEDOS-C00-R000-S+1.0. dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP08RGF.054.220817.ZQ:bd08/17/2022:br5.25:svnSAMSUNGELECTRONICSCO.,LTD.:pn950XED:pvrP08RGF:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNT950XEW-A51AS:rvrSGLFREEDOS-C00-R000-S+1.0.:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-ICPS-A5A5-ADLP-PRGF: dmi.product.family: Galaxy Book2 Pro dmi.product.name: 950XED dmi.product.sku: SCAI-ICPS-A5A5-ADLP-PRGF dmi.product.version: P08RGF dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2011385/+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 2024560] [NEW] Check if 0010-set-language needs to be update for the new languages property
Public bug reported: Upstream did changes to add a languages properties https://gitlab.freedesktop.org/accountsservice/accountsservice/-/commit/881e0ea7 I've rebased 0010-set-language to apply correctly but we should review if we need to adapt the patch to apply a similar logic to the new languages property that it's doing for old language one ** Affects: accountsservice (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/2024560 Title: Check if 0010-set-language needs to be update for the new languages property Status in accountsservice package in Ubuntu: New Bug description: Upstream did changes to add a languages properties https://gitlab.freedesktop.org/accountsservice/accountsservice/-/commit/881e0ea7 I've rebased 0010-set-language to apply correctly but we should review if we need to adapt the patch to apply a similar logic to the new languages property that it's doing for old language one To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/2024560/+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 2024558] Re: package linux-image-5.15.0-75-generic 5.15.0-75.82 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2024558 Title: package linux-image-5.15.0-75-generic 5.15.0-75.82 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: sdo do-release-upgrade ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-75-generic 5.15.0-75.82 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 21 10:56 seq crw-rw 1 root audio 116, 33 Jun 21 10:56 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown Date: Wed Jun 21 10:58:36 2023 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /sys/bus/usb/devices/usb1/rx_lanes: No such file or directory /sys/bus/usb/devices/usb1/tx_lanes: No such file or directory /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M MachineType: DigitalOcean Droplet PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz boot=live skipconfig fromiso=live/rescue_rootfs.squashfs net.ifnames=0 --- Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.06-2ubuntu7.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: initramfs-tools Title: package linux-image-5.15.0-75-generic 5.15.0-75.82 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to jammy on 2023-06-21 (0 days ago) dmi.bios.date: 12/12/2017 dmi.bios.vendor: DigitalOcean dmi.bios.version: 20171212 dmi.board.asset.tag: 360900599 dmi.board.name: Droplet dmi.board.vendor: DigitalOcean dmi.board.version: 20171212 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-6.1 dmi.modalias: dmi:bvnDigitalOcean:bvr20171212:bd12/12/2017:svnDigitalOcean:pnDroplet:pvr20171212:rvnDigitalOcean:rnDroplet:rvr20171212:cvnQEMU:ct1:cvrpc-i440fx-6.1: dmi.product.family: DigitalOcean_Droplet dmi.product.name: Droplet dmi.product.version: 20171212 dmi.sys.vendor: DigitalOcean To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2024558/+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 2024558] [NEW] package linux-image-5.15.0-75-generic 5.15.0-75.82 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: sdo do-release-upgrade ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-75-generic 5.15.0-75.82 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 21 10:56 seq crw-rw 1 root audio 116, 33 Jun 21 10:56 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown Date: Wed Jun 21 10:58:36 2023 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /sys/bus/usb/devices/usb1/rx_lanes: No such file or directory /sys/bus/usb/devices/usb1/tx_lanes: No such file or directory /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M MachineType: DigitalOcean Droplet PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz boot=live skipconfig fromiso=live/rescue_rootfs.squashfs net.ifnames=0 --- Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.06-2ubuntu7.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: initramfs-tools Title: package linux-image-5.15.0-75-generic 5.15.0-75.82 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to jammy on 2023-06-21 (0 days ago) dmi.bios.date: 12/12/2017 dmi.bios.vendor: DigitalOcean dmi.bios.version: 20171212 dmi.board.asset.tag: 360900599 dmi.board.name: Droplet dmi.board.vendor: DigitalOcean dmi.board.version: 20171212 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-6.1 dmi.modalias: dmi:bvnDigitalOcean:bvr20171212:bd12/12/2017:svnDigitalOcean:pnDroplet:pvr20171212:rvnDigitalOcean:rnDroplet:rvr20171212:cvnQEMU:ct1:cvrpc-i440fx-6.1: dmi.product.family: DigitalOcean_Droplet dmi.product.name: Droplet dmi.product.version: 20171212 dmi.sys.vendor: DigitalOcean ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy 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/2024558 Title: package linux-image-5.15.0-75-generic 5.15.0-75.82 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: sdo do-release-upgrade ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-75-generic 5.15.0-75.82 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 21 10:56 seq crw-rw 1 root audio 116, 33 Jun 21 10:56 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown Date: Wed Jun 21 10:58:36 2023 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /sys/bus/usb/devices/usb1/rx_lanes: No such file or directory /sys/bus/usb/devices/usb1/tx_lanes: No such file or directory /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M MachineType: DigitalOcean Droplet PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz boot=live skipconfig fromiso=live/rescue_rootfs.squashfs net.ifnames=0 --- Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.06-2ubuntu7.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: initramfs-tools Title: package linux-image-5.15.0-75-generic 5.15.0-75.82 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus:
[Touch-packages] [Bug 2019424] Re: Heimdal can be synced
I wanted to make sure again if my reasoning was correct (I guess it was), so I did rebuild in 2 PPAs. The ppc64el build failed, I did re-run the build and it failed again, so it is reproducible. Due to FTBFS we need to keep disabling LTO. New PPAs (named more explicitly, so now there is no problem distinguishing which is which): https://launchpad.net/~michal-maloszewski99/+archive/ubuntu/ppa1-heimdal-test-lto-off https://launchpad.net/~michal-maloszewski99/+archive/ubuntu/ppa2-heimdal-test-lto-on To sum up, we had a reason to disable LTO; this reason is gone, so we wanted to make it a sync; now there is a new reason to keep disabling LTO. I am going to set the status of the bug as a Won't Fix. ** Changed in: heimdal (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/2019424 Title: Heimdal can be synced Status in heimdal package in Ubuntu: Won't Fix Bug description: After heimdal merge process, I was trying to figure out if the delta that is still not dropped is required or not. So, to test it, I have created 2 PPAs, one in which lto is disabled, and the second one, where the lto is enabled. I have built them and downloaded the debs for i386 and amd64. Then I have compared amd64 deb from PPA1 with amd64 deb from PPA2. The same story with i386. The binary dependencies were identical. There is no difference between the files. So in that case, the delta can possibly be dropped. The package has already been merged again, with the change: heimdal (7.8.git20221117.28daf24+dfsg-2ubuntu1) mantic; urgency=low * Merge from Debian unstable. Remaining changes: - d/rules: Disable lto, to regain dep on roken, otherwise dependencies on amd64 are different than i386 resulting in different files on amd64 and i386. -- Steve Langasek Tue, 02 May 2023 09:56:10 +0200 heimdal (7.8.git20221117.28daf24+dfsg-1ubuntu1) lunar; urgency=low * Merge from Debian unstable. Remaining changes: - d/rules: Disable lto, to regain dep on roken, otherwise dependencies on amd64 are different than i386 resulting in different files on amd64 and i386. (LP #1934936) -- Steve Langasek Tue, 24 Jan 2023 19:14:54 -0800 Due to this, syncpackage doesn't run. The package can be sync'd next time it comes up. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/2019424/+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 2024396] Re: Xorg crash
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Please also ensure that you include the release and flavour of Ubuntu that you are using. Thank you! ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2024396 Title: Xorg crash Status in xorg package in Ubuntu: Incomplete Bug description: bug na tela travou na opção do som e acessar as configurações no Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.15.0-75.82~20.04.1-generic 5.15.99 Uname: Linux 5.15.0-75-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.182.03 Fri Feb 24 03:29:56 UTC 2023 GCC version: gcc version 9.4.0 (Ubuntu 9.4.0-1ubuntu1~20.04.1) ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jun 19 15:26:08 2023 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85 DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 470.182.03, 5.10.0-1014-oem, x86_64: installed nvidia, 470.182.03, 5.15.0-75-generic, x86_64: installed virtualbox, 6.1.38, 5.15.0-75-generic, x86_64: installed GraphicsCard: Intel Corporation Device [8086:9a49] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0b24] Subsystem: Dell Device [1028:0b24] InstallationDate: Installed on 2023-06-08 (11 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. Inspiron 15 5510 ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-75-generic root=UUID=7ca9b39c-6d76-473f-8f4b-d40298565bc7 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/09/2023 dmi.bios.release: 2.19 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.19.1 dmi.board.name: 07MY78 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.19.1:bd05/09/2023:br2.19:svnDellInc.:pnInspiron155510:pvr:rvnDellInc.:rn07MY78:rvrA00:cvnDellInc.:ct10:cvr:sku0B24: dmi.product.family: Inspiron dmi.product.name: Inspiron 15 5510 dmi.product.sku: 0B24 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2024396/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 2024520] Re: Moorethread GPU driver support on Xorg
Please propose the fix upstream first: https://gitlab.freedesktop.org/xorg/xserver/-/blob/master/hw/xfree86/common/xf86pciBus.c The fix should be released in Ubuntu 23.10, 23.04 and 22.04 before we consider 20.04. ** Tags added: focal ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Importance: Undecided => Wishlist ** Changed in: xorg-server (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2024520 Title: Moorethread GPU driver support on Xorg Status in xorg-server package in Ubuntu: Triaged Bug description: During our test for moorethreads GPU on Ubuntu 20.04 with lightdm+gnome+xorg desktop environment, we found that it can load DDX with mtgpu.drv.so, but during screen locking, the lightdm will start a new Xorg to display a greeter, this new Xorg would match a driver of modesettings_drv.sio instead of a correctly one mtgpu_drv.so. After debuging, we found the root cause is that xf86VideoPtrToDriverList function of Xorg is absent support for moorethreads GPU, there is a patch to fix this and hope it can be merged to Ubuntu release (20.04 LTS and following). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/2024520/+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