[Touch-packages] [Bug 2021409] Re: mdns failng with current versions of libnss-mdns and avahi-daemon
There's a detail in the github issue that wasn't noted here: I have Ubuntu Server 22.04.2 running in a VM (VMWare 13.0.2) on an Apple Silicon Mac running macOS 13.4. That makes the network driver situation less likely but the firewall situation still possible. A few extra questions: What kind of network is fusion set to - bridged, nat, host-only, etc + If you are using bridged, but to your macs wireless adapter, I have also experienced this not working as expected. Try use ethernet via a USB-Ethernet or native ethernet if your machine has it - and see if it works then. That was the case for me. If you google "vmware fusion bridge wifi" there are lots of posts with slightly different setups and symptoms. + If you are using nat/host-only I would expect only to be able to resolve hostnames with the host Mac and not the rest of the network Run tcpdump as directed, I am curious if you see any packets sent from any other node on your network. I am guessing not. If you are, it would be ideal to capture a pcap file (a copy of all the network packets on 5353) from both this linux VM, as well as another linux machine on the network that is not the host mac:L tcpdump -i -s 65535 -w lp2021409-$(hostname).pcap port 5353 Then run a query from both the VM and external host, for the other machine. While the pcap is running. Then stop it. Upload both files and note the IP addresses and hostnames of both machines. It's highly likely this is not a bug in avahi or nss-mdns but a network issue of some kind. Hopefully this will get you going in the right direction. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/2021409 Title: mdns failng with current versions of libnss-mdns and avahi-daemon Status in Avahi: New Status in avahi package in Ubuntu: New Status in nss-mdns package in Ubuntu: New Bug description: I have Ubuntu Server 22.04.2 I have installed avahi-daemon and libnss-mdns, but mdns resolution is not occurring over my primary network interface: Note that this is with `allow-interfaces=ens160` set /etc/avahi/avahi- daemon.conf. (22:25:17 Sat May 27 2023 jeremy@cid pts/0 aarch64) [648] ~ $ sudo resolvectl mdns ens160 1 (22:25:22 Sat May 27 2023 jeremy@cid pts/0 aarch64) [649] ~ $ resolvectl status Global Protocols: -LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported resolv.conf mode: stub Link 2 (ens160) Current Scopes: DNS mDNS/IPv4 mDNS/IPv6 Protocols: +DefaultRoute +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported Current DNS Server: 2601:647:6680:4b95::1 DNS Servers: 10.1.30.1 2601:647:6680:4b95::1 DNS Domain: localdomain (22:25:27 Sat May 27 2023 jeremy@cid pts/0 aarch64) [650] ~ $ avahi-resolve -n cid.local Failed to resolve host name 'cid.local': Timeout reached (22:26:03 Sat May 27 2023 jeremy@cid pts/0 aarch64) [651] ~ $ avahi-resolve -a 10.0.30.1 Failed to resolve address '10.0.30.1': Timeout reached (22:26:13 Sat May 27 2023 jeremy@cid pts/0 aarch64) [652] ~ $ sudo systemctl status avahi-daemon ● avahi-daemon.service - Avahi mDNS/DNS-SD Stack Loaded: loaded (/lib/systemd/system/avahi-daemon.service; enabled; vendor preset: enabled) Active: active (running) since Sat 2023-05-27 22:22:29 UTC; 3min 51s ago TriggeredBy: ● avahi-daemon.socket Main PID: 850 (avahi-daemon) Status: "avahi-daemon 0.8 starting up." Tasks: 2 (limit: 4523) Memory: 1.5M CPU: 15ms CGroup: /system.slice/avahi-daemon.service ├─850 "avahi-daemon: running [cid.local]" └─891 "avahi-daemon: chroot helper" May 27 22:22:29 cid avahi-daemon[850]: No service file found in /etc/avahi/services. May 27 22:22:29 cid avahi-daemon[850]: Joining mDNS multicast group on interface ens160.IPv6 with address 2601:647:6680:4b95:20c:29ff:fe42:f399. May 27 22:22:29 cid avahi-daemon[850]: New relevant interface ens160.IPv6 for mDNS. May 27 22:22:29 cid avahi-daemon[850]: Joining mDNS multicast group on interface ens160.IPv4 with address 10.1.30.2. May 27 22:22:29 cid avahi-daemon[850]: New relevant interface ens160.IPv4 for mDNS. May 27 22:22:29 cid avahi-daemon[850]: Network interface enumeration completed. May 27 22:22:29 cid avahi-daemon[850]: Registering new address record for 2601:647:6680:4b95:20c:29ff:fe42:f399 on ens160.*. May 27 22:22:29 cid avahi-daemon[850]: Registering new address record for 10.1.30.2 on ens160.IPv4. May 27 22:22:30 cid avahi-daemon[850]: Server startup complete. Host name is cid.local. Local service cookie is 2371061072. May 27 22:26:11 cid avahi-daemon[850]: wide-area.c: Query timed out. (22:27:14 Sat May 27 2023 jeremy@cid pts/0 aarch64) [657] ~ $ grep hosts /etc/nsswitch.conf hosts: files mdns4_minimal [NOTFOUND=return] dns --- If I set
[Touch-packages] [Bug 2021409] Re: mdns failng with current versions of libnss-mdns and avahi-daemon
If the primary issue is that other devices can only resolve your hostname after restarting avahi-daemon for a short time, plus, this machine doesn't see anything else on the network, it means that for one reason or another mDNS packets on port 5353 are not making it back to this host. The overwhelming majority of such cases are due to a bug in the driver for that network interface, almost always its a wireless interface or some kind - it's rare in wired ethernet drivers but not impossible. Very often setting the interface to promiscuous mode will fix this, because it tells the NIC to receive all packets (by default NICs filter out packets not intended for the host). You can try this command to set it: ip link set ens160 promisc on If this solves the issue, then it's 100% a buggy driver and I cannot do anything about that at the avahi level. You'll need to look at getting the driver fixed. This is common with bad wifi drivers, very rare with ethernet. If that doesn't help, it could be the driver also doesn't support promiscuous but I've not really seen that before. I would then check - Firewall on this machine, - Any features of your wireless network such as "multicast dns optimisation", etc If you run tcpdump for port 5353 you'll see packets coming and going. I suspect most likely your machine never receives any query packets from another host. So you can try run this command and then running a query from another host: sudo tcpdump -ni ens160 --no-promiscuous-mode port 5353 You can also try this without "--no-promiscuous-mode" (by default tcpdump puts the interface in promiscious mode, same as the above command). As a final note the resolvectl/resolved mdns support is totally independent of avahi, having it enabled could cause mDNS to fail in some cases - particularly with a network that performs 'multicast dns optimisation' where the packets are converted from multicast to unicast. Only a single process can bind to port 5353 for unicast packets and the packets will randomly get sent to resolved, avahi, chrome.. or any other process listening on port 5353. So disabling it (and anything else listening on 5353) could help in some specific circumstances though usually not necessary in most cases. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/2021409 Title: mdns failng with current versions of libnss-mdns and avahi-daemon Status in Avahi: New Status in avahi package in Ubuntu: New Status in nss-mdns package in Ubuntu: New Bug description: I have Ubuntu Server 22.04.2 I have installed avahi-daemon and libnss-mdns, but mdns resolution is not occurring over my primary network interface: Note that this is with `allow-interfaces=ens160` set /etc/avahi/avahi- daemon.conf. (22:25:17 Sat May 27 2023 jeremy@cid pts/0 aarch64) [648] ~ $ sudo resolvectl mdns ens160 1 (22:25:22 Sat May 27 2023 jeremy@cid pts/0 aarch64) [649] ~ $ resolvectl status Global Protocols: -LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported resolv.conf mode: stub Link 2 (ens160) Current Scopes: DNS mDNS/IPv4 mDNS/IPv6 Protocols: +DefaultRoute +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported Current DNS Server: 2601:647:6680:4b95::1 DNS Servers: 10.1.30.1 2601:647:6680:4b95::1 DNS Domain: localdomain (22:25:27 Sat May 27 2023 jeremy@cid pts/0 aarch64) [650] ~ $ avahi-resolve -n cid.local Failed to resolve host name 'cid.local': Timeout reached (22:26:03 Sat May 27 2023 jeremy@cid pts/0 aarch64) [651] ~ $ avahi-resolve -a 10.0.30.1 Failed to resolve address '10.0.30.1': Timeout reached (22:26:13 Sat May 27 2023 jeremy@cid pts/0 aarch64) [652] ~ $ sudo systemctl status avahi-daemon ● avahi-daemon.service - Avahi mDNS/DNS-SD Stack Loaded: loaded (/lib/systemd/system/avahi-daemon.service; enabled; vendor preset: enabled) Active: active (running) since Sat 2023-05-27 22:22:29 UTC; 3min 51s ago TriggeredBy: ● avahi-daemon.socket Main PID: 850 (avahi-daemon) Status: "avahi-daemon 0.8 starting up." Tasks: 2 (limit: 4523) Memory: 1.5M CPU: 15ms CGroup: /system.slice/avahi-daemon.service ├─850 "avahi-daemon: running [cid.local]" └─891 "avahi-daemon: chroot helper" May 27 22:22:29 cid avahi-daemon[850]: No service file found in /etc/avahi/services. May 27 22:22:29 cid avahi-daemon[850]: Joining mDNS multicast group on interface ens160.IPv6 with address 2601:647:6680:4b95:20c:29ff:fe42:f399. May 27 22:22:29 cid avahi-daemon[850]: New relevant interface ens160.IPv6 for mDNS. May 27 22:22:29 cid avahi-daemon[850]: Joining mDNS multicast group on interface ens160.IPv4 with address 10.1.30.2. May 27 22:22:29 cid avahi-daemon[850]: New relevant interface ens160.IPv4 for mDNS. May 27 22:22:29 cid avahi-daemon[850]:
[Touch-packages] [Bug 2013217] Re: package libpam0g:amd64 1.3.1-5ubuntu4.6 failed to install/upgrade: installed libpam0g:amd64 package post-installation script subprocess was killed by signal (Broken
[Expired for pam (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pam (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/2013217 Title: package libpam0g:amd64 1.3.1-5ubuntu4.6 failed to install/upgrade: installed libpam0g:amd64 package post-installation script subprocess was killed by signal (Broken pipe) Status in pam package in Ubuntu: Expired Bug description: not sure why the problem ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libpam0g:amd64 1.3.1-5ubuntu4.6 ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: prl_fs_freeze prl_fs prl_eth prl_tg ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Mar 25 07:27:49 2023 DpkgTerminalLog: Preparing to unpack .../libpam0g_1.3.1-5ubuntu4.6_amd64.deb ... Unpacking libpam0g:amd64 (1.3.1-5ubuntu4.6) over (1.3.1-5ubuntu4.3) ... Setting up libpam0g:amd64 (1.3.1-5ubuntu4.6) ... dpkg: error processing package libpam0g:amd64 (--configure): installed libpam0g:amd64 package post-installation script subprocess was killed by signal (Broken pipe) DuplicateSignature: package:libpam0g:amd64:1.3.1-5ubuntu4.6 Setting up libpam0g:amd64 (1.3.1-5ubuntu4.6) ... dpkg: error processing package libpam0g:amd64 (--configure): installed libpam0g:amd64 package post-installation script subprocess was killed by signal (Broken pipe) ErrorMessage: installed libpam0g:amd64 package post-installation script subprocess was killed by signal (Broken pipe) InstallationDate: Installed on 2020-08-07 (964 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) 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: pam Title: package libpam0g:amd64 1.3.1-5ubuntu4.6 failed to install/upgrade: installed libpam0g:amd64 package post-installation script subprocess was killed by signal (Broken pipe) UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/2013217/+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 2021438] [NEW] Display
Public bug reported: When the system turns off the screen by power management, the screen does not come back active again, having to activate the brightness keys for it to come back. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-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 525.105.17 Tue Mar 28 18:02:59 UTC 2023 GCC version: ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 28 21:14:21 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Lenovo CoffeeLake-H GT2 [UHD Graphics 630] [17aa:3a2d] NVIDIA Corporation GP107M [GeForce GTX 1050 3 GB Max-Q] [10de:1c91] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GP107M [GeForce GTX 1050 3 GB Max-Q] [17aa:3a2d] InstallationDate: Installed on 2023-05-28 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) MachineType: LENOVO 81TR ProcEnviron: LANG=pt_BR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=efac633a-69bd-49a0-b3ca-ba7e617e416a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/21/2021 dmi.bios.release: 1.34 dmi.bios.vendor: LENOVO dmi.bios.version: BGCN34WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: LENOVO IDEAPAD L340-15IRH dmi.ec.firmware.release: 1.34 dmi.modalias: dmi:bvnLENOVO:bvrBGCN34WW:bd05/21/2021:br1.34:efr1.34:svnLENOVO:pn81TR:pvrLENOVOIDEAPADL340-15IRH:rvnLENOVO:rnINVALID:rvrNoDPK:cvnLENOVO:ct10:cvrLENOVOIDEAPADL340-15IRH:skuLENOVO_MT_81TR_BU_idea_FM_IDEAPAD: dmi.product.family: IDEAPAD dmi.product.name: 81TR dmi.product.sku: LENOVO_MT_81TR_BU_idea_FM_IDEAPAD dmi.product.version: LENOVO IDEAPAD L340-15IRH dmi.sys.vendor: LENOVO 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.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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 -- 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/2021438 Title: Display Status in xorg package in Ubuntu: New Bug description: When the system turns off the screen by power management, the screen does not come back active again, having to activate the brightness keys for it to come back. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-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 525.105.17 Tue Mar 28 18:02:59 UTC 2023 GCC version: ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 28 21:14:21 2023 DistUpgraded: Fresh install DistroCodename:
[Touch-packages] [Bug 2020840] Re: package linux-image-5.15.0-72-generic 5.15.0-72.79 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: initramfs-tools (Ubuntu) Status: New => Confirmed -- 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/2020840 Title: package linux-image-5.15.0-72-generic 5.15.0-72.79 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: Confirmed Bug description: error update ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-72-generic 5.15.0-72.79 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown Date: Fri May 26 00:30:10 2023 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 IwConfig: lono wireless extensions. eth0 no wireless extensions. Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine ProcFB: 0 hyperv_drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=LABEL=desktop-rootfs ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. 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.1 RfKill: SourcePackage: initramfs-tools Title: package linux-image-5.15.0-72-generic 5.15.0-72.79 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/06/2022 dmi.bios.release: 4.1 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v4.1 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v4.1 dmi.chassis.asset.tag: 4521-1608-3807-0735-4847-9464-59 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v4.1 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.1:bd04/06/2022:br4.1:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.1:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.1:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.1:skuNone: dmi.product.family: Virtual Machine dmi.product.name: Virtual Machine dmi.product.sku: None dmi.product.version: Hyper-V UEFI Release v4.1 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2020840/+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 2019856] Re: Add missing ARM-cores to support Grace-based systems
The attachment "lp-2019856-add-missing-arm-cores-jammy.debdiff" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] -- 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: In Progress 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: In Progress Status in util-linux source package in Mantic: In Progress 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 589496] Re: bash --rcfile does not behave as documented
> Why does Debian enable -DSYS_BASHRC? This question does not seem to be answered anywhere. It does make sense for Debian (and Ubuntu) to enable SYS_BASHRC by default, as a system-wide /etc/bash.bashrc is a useful (and needed) configuration tool for sysadmins. It's standard behavior for many packages to read system-wide config file(s) from /etc and then merge user settings from ~/.* or ~/.config, so I don't think this is the issue. > Is there a workaround? Can someone release an alternate version of bash for Ubuntu without -DSYS_BASHRC? There's no need for an alternate release: if you have enough privileges to install system-wide software with apt, it means you're the admin who can also edit /etc/bash.bashrc to be a blank file to effectively disable it. If you're not the admin but want a custom bash for your user, you can compile bash yourself (without -DSYS_BASHRC or patched with a correct --rcfile behavior) and install it at ~/.local/bin. So admins can easily modify/disable /etc/bash.bashrc, and non-admins are not supposed to be able to bypass it anyway, at least for login shells. I believe the issue is not -DSYS_BASHRC being enabled by default, but rather `--rcfile` not behaving as it should, and documentation that mismatches current behavior. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/589496 Title: bash --rcfile does not behave as documented Status in bash package in Ubuntu: Confirmed Status in bash package in Debian: New Bug description: Binary package hint: bash the bash manpage says this about --rcfile --rcfile file Execute commands from file instead of the system wide initial‐ ization file /etc/bash.bashrc and the standard personal initial‐ ization file ~/.bashrc if the shell is interactive (see INVOCA‐ TION below). under INVOCATION it says When an interactive shell that is not a login shell is started, bash reads and executes commands from /etc/bash.bashrc and ~/.bashrc, if these files exist. This may be inhibited by using the --norc option. The --rcfile file option will force bash to read and execute commands from file instead of /etc/bash.bashrc and ~/.bashrc. but when i execute $ bash --rcfile somercfilewhichreallydoesexistandisreadableandall it will still read /etc/bash/bashrc (can be verified by adding --verbose) using lucid with bash 4.1-2ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/589496/+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 2019856] Re: Add missing ARM-cores to support Grace-based systems
util-linux 2.38.1-5ubuntu1 finally migrated from mantic-proposed to mantic (its autopkgtests were very slow/cycling last week, apparently). I'll check for potential sponsors to the debdiff in comment #10. -- 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: In Progress 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: In Progress Status in util-linux source package in Mantic: In Progress 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 2021418] Re: Incorrect response to mouse pointing
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2021418 Title: Incorrect response to mouse pointing Status in xorg package in Ubuntu: New Bug description: I am using a high resolution screen and have AnyDesk installed. The program icon appears in the right corner of the screen next to the icons for the selected language in the system, network management, sound volume and system shutdown. All icons respond correctly to mouse pointing. Anomaly - clicking on the desktop under the icons in the small space below the top line, results in the appearance of the AnyDesk configuration window. This makes it impossible to click on the icons of other windows whose top right corner is directly below the top bar. For example, you cannot close the program window, minimize it, etc. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Brak dostępu: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 28 13:55:38 2023 DistUpgraded: 2023-05-14 13:56:08,498 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2023-02-02 (114 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) Lsusb: Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 004: ID 0e0f:0008 VMware, Inc. Virtual Bluetooth Adapter Bus 001 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 001 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=ee607178-4028-4d20-91a5-41aa1cc72740 ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-05-14 (13 days ago) dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. 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: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2021418/+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 1932537] Re: CUPS + SSSD: cannot access local CUPS web interface with domain user (apparmor problem)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cups (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1932537 Title: CUPS + SSSD: cannot access local CUPS web interface with domain user (apparmor problem) Status in apparmor package in Ubuntu: Confirmed Status in cups package in Ubuntu: Confirmed Bug description: [Summary] My domain user can not access the local CUPS web interface due to apparmor denials. Adding the following two lines to /etc/apparmor.d/local/usr.sbin.cupsd fixes it: /var/lib/sss/pipes/private/pam rw, unix (bind) type=dgram addr=@userdb-*, [Details] I have a (relatively) clean install of Ubuntu 20.04 (no upgrade), which is joined to a Windows AD-domain via sssd, but currently used off site with cached credentials. When I try to log in with my domain user (who is in the lpadmingroup) at the local cups web interface (localhost:631 ...> Add Printer) with the default apparmor config for cupsd I get a: AVC apparmor="DENIED" operation="connect" profile="/usr/sbin/cupsd" name="/var/lib/sss/pipes/private/pam" pid=189759 comm="cupsd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 This already existed in Bionic and my workaround was to add '/var/lib/sss/pipes/private/pam rw,' to /etc/apparmor.d/local/usr.sbin.cupsd and reload the profile: # echo '/var/lib/sss/pipes/private/pam rw,' > /etc/apparmor.d/local/usr.sbin.cupsd # apparmor_parser -r -W -T /etc/apparmor.d/usr.sbin.cupsd This worked in Bionic, but leads to a crash of cupsd in Focal when I try to log in as domain user with a the following log message nearby: AVC apparmor="DENIED" operation="bind" profile="/usr/sbin/cupsd" pid=189759 comm="cupsd" family="unix" sock_type="dgram" protocol=0 requested_mask="bind" denied_mask="bind" addr="@userdb-7625b1ef65396344ef05f0a8aeda870e" This looks very similar to https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1890858 , so I applied the same fix and added 'unix (bind) type=dgram addr=@userdb-*,' to /etc/apparmor.d/local/usr.sbin.cupsd: # echo 'unix (bind) type=dgram addr=@userdb-*,' >> /etc/apparmor.d/local/usr.sbin.cupsd # apparmor_parser -r -W -T /etc/apparmor.d/usr.sbin.cupsd Which fixed my problem. I am not an expert on apparmor, so I have no idea, if the first line gives too broad permissions. I think that there are two unrelated issues: 1) Cupsd cannot access sssd at all. This already existed in Bionic (but I failed to report the issue -- sorry for that). 2) Once the login succeeds, cups tries to resolve a uid/gid as it isn't known locally. To resolve it it needs to bind a unix socket. See: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1890858/comments/37 I will attach a full log with added comments on what I did. [Infos] 1) lsb_release -rd Description:Ubuntu 20.04.2 LTS Release:20.04 2) apt-cache policy cups-daemon cups-daemon: Installiert: 2.3.1-9ubuntu1.1 Installationskandidat: 2.3.1-9ubuntu1.1 Versionstabelle: *** 2.3.1-9ubuntu1.1 500 500 http://ftp.uni-hannover.de/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 2.3.1-9ubuntu1 500 500 http://ftp.uni-hannover.de/ubuntu focal/main amd64 Packages 3) What you expected to happen: Be able to log in at the local cups web interface with my domain user, which is in the lpadmin group 4) What happened instead: Access was denied (asked again for my credentials) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1932537/+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 1932537] Re: CUPS + SSSD: cannot access local CUPS web interface with domain user (apparmor problem)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apparmor (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1932537 Title: CUPS + SSSD: cannot access local CUPS web interface with domain user (apparmor problem) Status in apparmor package in Ubuntu: Confirmed Status in cups package in Ubuntu: Confirmed Bug description: [Summary] My domain user can not access the local CUPS web interface due to apparmor denials. Adding the following two lines to /etc/apparmor.d/local/usr.sbin.cupsd fixes it: /var/lib/sss/pipes/private/pam rw, unix (bind) type=dgram addr=@userdb-*, [Details] I have a (relatively) clean install of Ubuntu 20.04 (no upgrade), which is joined to a Windows AD-domain via sssd, but currently used off site with cached credentials. When I try to log in with my domain user (who is in the lpadmingroup) at the local cups web interface (localhost:631 ...> Add Printer) with the default apparmor config for cupsd I get a: AVC apparmor="DENIED" operation="connect" profile="/usr/sbin/cupsd" name="/var/lib/sss/pipes/private/pam" pid=189759 comm="cupsd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 This already existed in Bionic and my workaround was to add '/var/lib/sss/pipes/private/pam rw,' to /etc/apparmor.d/local/usr.sbin.cupsd and reload the profile: # echo '/var/lib/sss/pipes/private/pam rw,' > /etc/apparmor.d/local/usr.sbin.cupsd # apparmor_parser -r -W -T /etc/apparmor.d/usr.sbin.cupsd This worked in Bionic, but leads to a crash of cupsd in Focal when I try to log in as domain user with a the following log message nearby: AVC apparmor="DENIED" operation="bind" profile="/usr/sbin/cupsd" pid=189759 comm="cupsd" family="unix" sock_type="dgram" protocol=0 requested_mask="bind" denied_mask="bind" addr="@userdb-7625b1ef65396344ef05f0a8aeda870e" This looks very similar to https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1890858 , so I applied the same fix and added 'unix (bind) type=dgram addr=@userdb-*,' to /etc/apparmor.d/local/usr.sbin.cupsd: # echo 'unix (bind) type=dgram addr=@userdb-*,' >> /etc/apparmor.d/local/usr.sbin.cupsd # apparmor_parser -r -W -T /etc/apparmor.d/usr.sbin.cupsd Which fixed my problem. I am not an expert on apparmor, so I have no idea, if the first line gives too broad permissions. I think that there are two unrelated issues: 1) Cupsd cannot access sssd at all. This already existed in Bionic (but I failed to report the issue -- sorry for that). 2) Once the login succeeds, cups tries to resolve a uid/gid as it isn't known locally. To resolve it it needs to bind a unix socket. See: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1890858/comments/37 I will attach a full log with added comments on what I did. [Infos] 1) lsb_release -rd Description:Ubuntu 20.04.2 LTS Release:20.04 2) apt-cache policy cups-daemon cups-daemon: Installiert: 2.3.1-9ubuntu1.1 Installationskandidat: 2.3.1-9ubuntu1.1 Versionstabelle: *** 2.3.1-9ubuntu1.1 500 500 http://ftp.uni-hannover.de/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 2.3.1-9ubuntu1 500 500 http://ftp.uni-hannover.de/ubuntu focal/main amd64 Packages 3) What you expected to happen: Be able to log in at the local cups web interface with my domain user, which is in the lpadmin group 4) What happened instead: Access was denied (asked again for my credentials) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1932537/+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 589496] Re: bash --rcfile does not behave as documented
What is the status of this? There is a further discussion from Chet here: https://www.mail-archive.com/bug-bash@gnu.org/msg20804.html Why does Debian enable -DSYS_BASHRC? This question does not seem to be answered anywhere. Is there a workaround? Can someone release an alternate version of bash for Ubuntu without -DSYS_BASHRC? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/589496 Title: bash --rcfile does not behave as documented Status in bash package in Ubuntu: Confirmed Status in bash package in Debian: New Bug description: Binary package hint: bash the bash manpage says this about --rcfile --rcfile file Execute commands from file instead of the system wide initial‐ ization file /etc/bash.bashrc and the standard personal initial‐ ization file ~/.bashrc if the shell is interactive (see INVOCA‐ TION below). under INVOCATION it says When an interactive shell that is not a login shell is started, bash reads and executes commands from /etc/bash.bashrc and ~/.bashrc, if these files exist. This may be inhibited by using the --norc option. The --rcfile file option will force bash to read and execute commands from file instead of /etc/bash.bashrc and ~/.bashrc. but when i execute $ bash --rcfile somercfilewhichreallydoesexistandisreadableandall it will still read /etc/bash/bashrc (can be verified by adding --verbose) using lucid with bash 4.1-2ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/589496/+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 1277020] Re: hideous mouse cursor when hovering over hyperlinks.
if you are using the Unity 7 desktop environment on X11 and want to launch a QML app capable of displaying hyperlinks, there are several options available. Apps like Friends-app, Webbrowser-app, and Webapps-container are suitable choices. electronics Launching one of these QML apps allows you to interact with hyperlinks within their respective interfaces. You can click on hyperlinks to open web pages or perform other actions associated with the linked content. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1277020 Title: hideous mouse cursor when hovering over hyperlinks. Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. On the desktop (unity7, x11), launch any qml app that is capable of displaying hyperlinks (friends-app, webbrowser-app, webapps-container, etc). 2. Mouse over any hyperlink. 3. Observe that it is a 2-bit icon that should have died in the 1980's. Where is this cursor coming from? It should really be updated to something more modern looking, especially as we converge towards qml/unity8 on the desktop. (we want to make webapps-container the default webapps experience in 14.04 desktop, but this bug makes the experience very ugly) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1277020/+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
