[Touch-packages] [Bug 1975566] Re: radeon / amdgpu bad performance or panics
Oh I see you started with Ubuntu Server. Please: 1. Don't disable Wayland. Wayland should be enabled. 2. Answer the previous question: After you have switched back to a 'stock' config and kernel, what does vulkaninfo report? 3. Try booting desktop Ubuntu from USB: https://ubuntu.com/download/desktop If that just works then we're probably wasting time here figuring out how to un-customise this server install. Just install desktop instead. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1975566 Title: radeon / amdgpu bad performance or panics Status in mesa package in Ubuntu: Incomplete Bug description: Recently I upgraded my machine and moved my GPU over from the old (Intel something) to the new machine (AMD Ryzen 7 5700X, B550 motherboard). I did a fresh Ubuntu install (server) and added packages to get my GUI rolling (lightdm + awesomewm), just like before. The graphics cards is a "Gigabyte GV-R928XOC-3GD Rev. 2.0" which has the R9 280X chip (TAHITI / Southern Islands). On my old system, I could play games with Vulkan, but with this system it doesn't work. If I run the 'default' setup, it uses the 'radeon' kernel module. The first couple of seconds I get reasonable performance (glxgears @ 60 FPS), then it suddenly drop to 4 and motion is almost not visible). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg (not installed) Uname: Linux 5.18.0-051800-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue May 24 06:49:56 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Tahiti XT [Radeon HD 7970/8970 OEM / R9 280X] [1002:6798] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Tahiti XTL [Radeon R9 280X OC] [1458:3001] InstallationDate: Installed on 2022-05-14 (9 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.18.0-051800-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P2.30 dmi.board.name: B550 Phantom Gaming-ITX/ax dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP2.30:bd02/25/2022:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB550PhantomGaming-ITX/ax:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 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/mesa/+bug/1975566/+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 827151] Re: Annoying log message "DIGEST-MD5 common mech free"
Got a reply[1] from upstream, and this is expected. I'll go ahead and MP this patch. 1. https://github.com/cyrusimap/cyrus- sasl/commit/cb549ef71c5bb646fe583697ebdcaba93267a237#r74534186 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/827151 Title: Annoying log message "DIGEST-MD5 common mech free" Status in Cyrus-sasl2: Fix Released Status in cyrus-sasl2 package in Ubuntu: Triaged Status in cyrus-sasl2 source package in Trusty: Won't Fix Status in cyrus-sasl2 source package in Xenial: Incomplete Status in cyrus-sasl2 source package in Yakkety: Fix Released Status in cyrus-sasl2 source package in Focal: Triaged Status in cyrus-sasl2 source package in Impish: Triaged Status in cyrus-sasl2 source package in Jammy: Confirmed Status in cyrus-sasl2 package in Debian: Fix Released Bug description: I recently updated the libsasl2-modules to 2.1.24~rc1.dfsg1+cvs2011-05-23-4ubuntu1 in oneiric. That triggered the bug also described in Debian here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631932 The annoying message is logged in auth.log. In my case, it is associated with svnserve: svnserve: DIGEST-MD5 common mech free I'm not exactly sure what action triggers the message, but I can investigate more if required. $ lsb_release -rd Description:Ubuntu oneiric (development branch) Release:11.10 To manage notifications about this bug go to: https://bugs.launchpad.net/cyrus-sasl2/+bug/827151/+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 1970799] Re: wifi connection on hotspot with wpa enterprise on 22.04
I'm in the location where i can test the hotspot (for 3 days).. dammed ... it doesn't work ! is there any additional info you need? -- 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/1970799 Title: wifi connection on hotspot with wpa enterprise on 22.04 Status in Ubuntu MATE: New Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Status in wpa package in Ubuntu: Incomplete Bug description: With 20.04 I used a wifi connection with a hotspot Telenet with following parametres: security : WPA2 entreprise authentification : tunneled TLS no AC certificat drequired inner authentication : MSCHAPV2(non EAP) user name: my id password : my pswd with 22.04 it doesn’t work anymore nor with the internal broadcom wifi nor with dongles (nor my Dlink 140 nor TP-link WN7200) This problem is only present with hotspot requesting an identification (user+pswd) awith hotspots without identification everything is OK in appendice some infos --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michelvlt 1725 F pulseaudio /dev/snd/pcmC0D0p: michelvlt 1725 F...m pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: source /etc/network/interfaces.d/* InstallationDate: Installed on 2022-04-21 (7 days ago) InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IpRoute: default via 192.168.86.254 dev wlp3s0 proto dhcp metric 600 10.101.9.0/24 dev pan1 proto kernel scope link src 10.101.9.1 linkdown 169.254.0.0/16 dev pan1 scope link metric 1000 linkdown 192.168.86.0/24 dev wlp3s0 proto kernel scope link src 192.168.86.157 metric 600 MachineType: Apple Inc. MacBookPro8,1 NonfreeKernelModules: wl Package: wpa PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=90724096-caa9-4e64-820f-c775b9de339c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 Tags: jammy Uname: Linux 5.15.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/13/2019 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 87.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-94245B3640C91C81 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro8,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-94245B3640C91C81 dmi.modalias: dmi:bvnAppleInc.:bvr87.0.0.0.0:bd06/13/2019:br0.1:svnAppleInc.:pnMacBookPro8,1:pvr1.0:rvnAppleInc.:rnMac-94245B3640C91C81:rvrMacBookPro8,1:cvnAppleInc.:ct10:cvrMac-94245B3640C91C81:skuSystemSKU#: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro8,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1970799/+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 827151] Re: Annoying log message "DIGEST-MD5 common mech free"
I applied that patch in cyrus-sasl2 2.1.28 from kinetic, and it did get rid of the other DIGEST-MD5 messages. But I'm having difficulties in finding a client sasl app where I can set log_level to see if with a high log_level I can restore that logging, to make sure it's working. I tried ldapwhoami from openldap, smtptest from cyrus, and sasl-sample- client from cyrus-sasl2, but they don't seem to read a sasl-specific config file (like in /etc/sasl2/.conf) where I could set "log_level: 7" for example. I confirmed with strace that they don't even try to open such a config file. I asked upstream for some guidance, but it's probably just a minor thing. I'll give it some time and then land this, or wait for 2.1.29 which has this committed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/827151 Title: Annoying log message "DIGEST-MD5 common mech free" Status in Cyrus-sasl2: Fix Released Status in cyrus-sasl2 package in Ubuntu: Triaged Status in cyrus-sasl2 source package in Trusty: Won't Fix Status in cyrus-sasl2 source package in Xenial: Incomplete Status in cyrus-sasl2 source package in Yakkety: Fix Released Status in cyrus-sasl2 source package in Focal: Triaged Status in cyrus-sasl2 source package in Impish: Triaged Status in cyrus-sasl2 source package in Jammy: Confirmed Status in cyrus-sasl2 package in Debian: Fix Released Bug description: I recently updated the libsasl2-modules to 2.1.24~rc1.dfsg1+cvs2011-05-23-4ubuntu1 in oneiric. That triggered the bug also described in Debian here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631932 The annoying message is logged in auth.log. In my case, it is associated with svnserve: svnserve: DIGEST-MD5 common mech free I'm not exactly sure what action triggers the message, but I can investigate more if required. $ lsb_release -rd Description:Ubuntu oneiric (development branch) Release:11.10 To manage notifications about this bug go to: https://bugs.launchpad.net/cyrus-sasl2/+bug/827151/+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 1975667] Re: systemd-resolved does not reset DNS server and search domain list properly after VPN disconnect
I think there are actually two similar bugs here. The first I think is caused by [1], which I have confirmed is present in impish, but not focal or jammy. This can be demonstrated by the following: $ resolvectl dns eth0 8.8.8.8 8.8.4.4 1.1.1.1 $ resolvectl dns eth0 Link 110 (eth0): 8.8.8.8 8.8.4.4 1.1.1.1 $ resolvectl dns eth0 "" # This SHOULD clear all DNS servers $ resolvectl dns eth0 Link 110 (eth0): 8.8.4.4 1.1.1.1 # Only 8.8.8.8 was removed. I think the second issue is caused by [2], which I have confirmed is present in impish and jammy, but not focal. This can be demonstrated by the following: $ resolvectl domain eth0 search1.internal search2.internal search3.internal $ resolvectl domain eth0 Link 2 (ens3): search1.internal search2.internal search3.internal $ resolvectl domain eth0 "" # This SHOULD clear all search domains $ resolvectl domain eth0 Link 2 (ens3): search2.internal search3.internal # Only search1.internal was removed [1] https://github.com/systemd/systemd/issues/19651 [2] https://github.com/systemd/systemd/issues/23027 ** Bug watch added: github.com/systemd/systemd/issues #19651 https://github.com/systemd/systemd/issues/19651 ** Bug watch added: github.com/systemd/systemd/issues #23027 https://github.com/systemd/systemd/issues/23027 ** Tags added: rls-ii-incoming rls-jj-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1975667 Title: systemd-resolved does not reset DNS server and search domain list properly after VPN disconnect Status in systemd package in Ubuntu: New Bug description: Hi, in Ubuntu 21.10 I am facing a problem with DNS server list and search domain list is not properly reset back to the previous values after a VPN is disconnected. I reproduced this in Ubuntu 21.10 instance which was upgraded from the older version of Ubuntu as well as in Live USB Ubuntu 21.10 so it is not an "upgrade issue". I use this resolv.conf symlink: /etc/resolv.conf -> ../run/systemd/resolve/resolv.conf Actual behavior: VPN connect will add VPN's DNS servers and search domains into /etc/resolv.conf. When VPN is disconnected there are some of the VPN's DNS server and search domain entries left there, so it is not reset back properly. Desired behavior: VPN connect will add VPN's DNS servers and search domains into /etc/resolv.conf. When VPN is disconnected DNS servers and search domain list is restored to exactly the same state as was prior to the VPN connection. Steps for reproducing: 1. Before VPN is connected this is the DNS server and search domain list in /etc/resolv.conf: nameserver 192.168.122.1 search . 2. Once the VPN is connected, we see there were VPN's DNS server and serach domain list entries added: nameserver 2xx.xx.xx.x0 nameserver 2xx.xx.xx.x1 nameserver 192.168.122.1 search domain1.local domain2.internal domain3.internal 3. After VPN disconnection, we see the DNS server and search domain list in /etc/resolv.conf is not restored to the state at point (1.) and some entries from VPN is being kept there: nameserver 2xx.xx.xx.x1 nameserver 192.168.122.1 search domain2.internal domain3.internal ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: systemd 248.3-1ubuntu8 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465 CurrentDesktop: ubuntu:GNOME Date: Wed May 25 06:06:05 2022 LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet 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/15p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- 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: No
[Touch-packages] [Bug 1975566] Re: radeon / amdgpu bad performance or panics
Sorry for the late reply. tonight I installed the full ubuntu-desktop package (with a "clean" test user) and experienced crashes/hangs and other weird behaviour with the stock setup. When I disabled Wayland in GDM3, it got a little better, until that had issues as well. Note: I went from an 7+ year old Intel CPU -> AMD Ryzen CPU (GPU stayed the same) What kind of information is useful to provide including which logs? Would it help if I provided journalctl logs of with/without wayland and until the moment of the crash/hang? P.S. thanks for trying to help me out here -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1975566 Title: radeon / amdgpu bad performance or panics Status in mesa package in Ubuntu: Incomplete Bug description: Recently I upgraded my machine and moved my GPU over from the old (Intel something) to the new machine (AMD Ryzen 7 5700X, B550 motherboard). I did a fresh Ubuntu install (server) and added packages to get my GUI rolling (lightdm + awesomewm), just like before. The graphics cards is a "Gigabyte GV-R928XOC-3GD Rev. 2.0" which has the R9 280X chip (TAHITI / Southern Islands). On my old system, I could play games with Vulkan, but with this system it doesn't work. If I run the 'default' setup, it uses the 'radeon' kernel module. The first couple of seconds I get reasonable performance (glxgears @ 60 FPS), then it suddenly drop to 4 and motion is almost not visible). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg (not installed) Uname: Linux 5.18.0-051800-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue May 24 06:49:56 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Tahiti XT [Radeon HD 7970/8970 OEM / R9 280X] [1002:6798] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Tahiti XTL [Radeon R9 280X OC] [1458:3001] InstallationDate: Installed on 2022-05-14 (9 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.18.0-051800-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P2.30 dmi.board.name: B550 Phantom Gaming-ITX/ax dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP2.30:bd02/25/2022:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB550PhantomGaming-ITX/ax:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 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/mesa/+bug/1975566/+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 1700814] Re: Default capability of cap_setfcap+i should be set on setcap
@serge-hallyn I'm not sure why I got this bug assigned. :-) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libcap2 in Ubuntu. https://bugs.launchpad.net/bugs/1700814 Title: Default capability of cap_setfcap+i should be set on setcap Status in libcap2 package in Ubuntu: New Bug description: If I grant a user (via pam_cap) cap_setfcap+i, I would then expect them to be able to use setcap without sudo. setcap is not provided with any default file capabilities however, so either the user has to sudo, or I have to grant the setfcap capability to setcap with setcap. In my mind, it would be reasonable to grant setfcap+i to setcap by default on installation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcap2/+bug/1700814/+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 827151] Re: Annoying log message "DIGEST-MD5 common mech free"
Ok, specifically this log message is fixed in 2.1.28: DIGEST-MD5 common mech free Via https://git.launchpad.net/ubuntu/+source/cyrus- sasl2/tree/debian/patches/0001-plugins-digestmd5-Remove-debug-log-mech- free.patch That patch is just in Ubuntu Kinetic for now. But I still see a lot of DIGEST-MD5 noise in the logs when I just attempt a DIGEST-MD5 auth: May 25 19:15:01 k1-sasl-digest ldapwhoami: DIGEST-MD5 client step 2 May 25 19:15:01 k1-sasl-digest ldapwhoami: DIGEST-MD5 parse_server_challenge() May 25 19:15:01 k1-sasl-digest ldapwhoami: DIGEST-MD5 ask_user_info() May 25 19:15:03 k1-sasl-digest ldapwhoami: DIGEST-MD5 client step 2 May 25 19:15:03 k1-sasl-digest ldapwhoami: DIGEST-MD5 ask_user_info() May 25 19:15:03 k1-sasl-digest ldapwhoami: DIGEST-MD5 make_client_response() May 25 19:15:03 k1-sasl-digest ldapwhoami: DIGEST-MD5 create_layer_keys() May 25 19:15:03 k1-sasl-digest ldapwhoami: DIGEST-MD5 client mech dispose May 25 19:15:03 k1-sasl-digest ldapwhoami: DIGEST-MD5 common mech dispose All except the "common mech free" one ;) The fix for that was committed 22 days ago: https://github.com/cyrusimap/cyrus- sasl/commit/cb549ef71c5bb646fe583697ebdcaba93267a237 And also affects kinetic. I'll reopen this bug then, as it's the same type of noise in the same plugin. ** Changed in: cyrus-sasl2 (Ubuntu) Status: Fix Released => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/827151 Title: Annoying log message "DIGEST-MD5 common mech free" Status in Cyrus-sasl2: Fix Released Status in cyrus-sasl2 package in Ubuntu: Triaged Status in cyrus-sasl2 source package in Trusty: Won't Fix Status in cyrus-sasl2 source package in Xenial: Incomplete Status in cyrus-sasl2 source package in Yakkety: Fix Released Status in cyrus-sasl2 source package in Focal: Triaged Status in cyrus-sasl2 source package in Impish: Triaged Status in cyrus-sasl2 source package in Jammy: Confirmed Status in cyrus-sasl2 package in Debian: Fix Released Bug description: I recently updated the libsasl2-modules to 2.1.24~rc1.dfsg1+cvs2011-05-23-4ubuntu1 in oneiric. That triggered the bug also described in Debian here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631932 The annoying message is logged in auth.log. In my case, it is associated with svnserve: svnserve: DIGEST-MD5 common mech free I'm not exactly sure what action triggers the message, but I can investigate more if required. $ lsb_release -rd Description:Ubuntu oneiric (development branch) Release:11.10 To manage notifications about this bug go to: https://bugs.launchpad.net/cyrus-sasl2/+bug/827151/+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 827151] Re: Annoying log message "DIGEST-MD5 common mech free"
** Changed in: cyrus-sasl2 (Ubuntu Jammy) Status: In Progress => Fix Released ** Changed in: cyrus-sasl2 (Ubuntu Jammy) Status: Fix Released => Confirmed ** Changed in: cyrus-sasl2 (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/827151 Title: Annoying log message "DIGEST-MD5 common mech free" Status in Cyrus-sasl2: Fix Released Status in cyrus-sasl2 package in Ubuntu: Fix Released Status in cyrus-sasl2 source package in Trusty: Won't Fix Status in cyrus-sasl2 source package in Xenial: Incomplete Status in cyrus-sasl2 source package in Yakkety: Fix Released Status in cyrus-sasl2 source package in Focal: Triaged Status in cyrus-sasl2 source package in Impish: Triaged Status in cyrus-sasl2 source package in Jammy: Confirmed Status in cyrus-sasl2 package in Debian: Fix Released Bug description: I recently updated the libsasl2-modules to 2.1.24~rc1.dfsg1+cvs2011-05-23-4ubuntu1 in oneiric. That triggered the bug also described in Debian here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631932 The annoying message is logged in auth.log. In my case, it is associated with svnserve: svnserve: DIGEST-MD5 common mech free I'm not exactly sure what action triggers the message, but I can investigate more if required. $ lsb_release -rd Description:Ubuntu oneiric (development branch) Release:11.10 To manage notifications about this bug go to: https://bugs.launchpad.net/cyrus-sasl2/+bug/827151/+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 1975735] [NEW] Build with libedit support by default
Public bug reported: The libedit support needs to be enabled by default. Even though dash is the default sh on Ubuntu and is mainly used to run POSIX shell scripts, it's also a good interactive shell for testing scripts and prototype code. Enabling history will make life much easier. Otherwise, the "Command Line Editing" section and the "fc" command should be removed from the man page as it's currently misleading. ** Affects: dash (Ubuntu) Importance: Undecided Status: Opinion ** Changed in: dash (Ubuntu) Status: New => Opinion -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dash in Ubuntu. https://bugs.launchpad.net/bugs/1975735 Title: Build with libedit support by default Status in dash package in Ubuntu: Opinion Bug description: The libedit support needs to be enabled by default. Even though dash is the default sh on Ubuntu and is mainly used to run POSIX shell scripts, it's also a good interactive shell for testing scripts and prototype code. Enabling history will make life much easier. Otherwise, the "Command Line Editing" section and the "fc" command should be removed from the man page as it's currently misleading. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dash/+bug/1975735/+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 1802483] Please test proposed package
Hello Marco, or anyone else affected, Accepted libnotify into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libnotify/0.7.7-3ubuntu0.18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnotify in Ubuntu. https://bugs.launchpad.net/bugs/1802483 Title: Notifications emitted by a snap with local files or desktop files use wrong namespace Status in libnotify package in Ubuntu: Fix Released Status in libnotify source package in Bionic: Fix Committed Status in libnotify source package in Focal: Fix Committed Status in libnotify source package in Jammy: Fix Committed Bug description: As can be tested using this example snap: - https://github.com/3v1n0/notify-send-test-snap Basically the icons are referenced using absolute paths in snap environment, while they should be readapted so that they depend on $SNAP location. As we do with appindicators and libunity emblems. [ Impact ] Icons sonuds and desktop files referenced by a snapped app using notifications aren't exposed to the desktop in absolute paths [ Test case ] Build the test snap (or install it from the attached files to this bug): git clone https://github.com/3v1n0/notify-send-test-snap snapcraft prime snap try prime To use the pre-built snap (https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1802483/comments/7) snap install --dangerous notify-send-test-snap_*.snap Check that icons are shown when launching: notify-send-test-snap notify-send-test-snap.image-path notify-send-test-snap.image-uri Ensure that desktop entry is correctly sent, monitoring the dbus session: In a terminal: dbus-monitor --session --monitor "interface='org.freedesktop.Notifications'" In the other: notify-send-test-snap.desktop-entry notify-send-test-snap.desktop-entry-explicit-id notify-send-test-snap.desktop-entry-explicit-file-name notify-send-test-snap.desktop-entry-explicit-path notify-send-test-snap.desktop-entry-explicit-uri notify-send-test-snap.desktop-entry-explicit-snapped-uri The `desktop-entry` value sent to dbus should be either: - A `notify-send-test-snap_`-prefixed desktop ID - A .desktop file path (readable from both inside and outside the snap) - A .desktop file uri (readable from both inside and outside the snap) [ Regression potential ] Normal applications that are run with a SNAP environment variable set, might use wrong paths for files or desktop file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1802483/+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 1802483] Re: Notifications emitted by a snap with local files or desktop files use wrong namespace
Sorry I missed your reply, but to make progress I just tweaked the version string in a new upload that I signed. It's otherwise identical. So I'll just accept that. ** Changed in: libnotify (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnotify in Ubuntu. https://bugs.launchpad.net/bugs/1802483 Title: Notifications emitted by a snap with local files or desktop files use wrong namespace Status in libnotify package in Ubuntu: Fix Released Status in libnotify source package in Bionic: Fix Committed Status in libnotify source package in Focal: Fix Committed Status in libnotify source package in Jammy: Fix Committed Bug description: As can be tested using this example snap: - https://github.com/3v1n0/notify-send-test-snap Basically the icons are referenced using absolute paths in snap environment, while they should be readapted so that they depend on $SNAP location. As we do with appindicators and libunity emblems. [ Impact ] Icons sonuds and desktop files referenced by a snapped app using notifications aren't exposed to the desktop in absolute paths [ Test case ] Build the test snap (or install it from the attached files to this bug): git clone https://github.com/3v1n0/notify-send-test-snap snapcraft prime snap try prime To use the pre-built snap (https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1802483/comments/7) snap install --dangerous notify-send-test-snap_*.snap Check that icons are shown when launching: notify-send-test-snap notify-send-test-snap.image-path notify-send-test-snap.image-uri Ensure that desktop entry is correctly sent, monitoring the dbus session: In a terminal: dbus-monitor --session --monitor "interface='org.freedesktop.Notifications'" In the other: notify-send-test-snap.desktop-entry notify-send-test-snap.desktop-entry-explicit-id notify-send-test-snap.desktop-entry-explicit-file-name notify-send-test-snap.desktop-entry-explicit-path notify-send-test-snap.desktop-entry-explicit-uri notify-send-test-snap.desktop-entry-explicit-snapped-uri The `desktop-entry` value sent to dbus should be either: - A `notify-send-test-snap_`-prefixed desktop ID - A .desktop file path (readable from both inside and outside the snap) - A .desktop file uri (readable from both inside and outside the snap) [ Regression potential ] Normal applications that are run with a SNAP environment variable set, might use wrong paths for files or desktop file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1802483/+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 1975549] Re: NetworkManager uses tethered Android phone as ethernet connection instead of wired ethernet connection
> Sebastien Bacher wrote:
>
> yes, the current details are about a working system but we want to work on
> the bug
Thanks again Sebastien.
I rebooted the machine with the phone tethered and it used USB0 as the
network adapter. I then ran 'apport-collect 1975549'.
Here is the current nmcli when running the command in its current state
(boot with phone tethered):
$ nmcli
usb0: connected to Ethernet
"Google Nexus 4/5/7/10"
ethernet (rndis_host), 82:1F:DF:52:0B:39, hw, mtu 1500
ip4 default
inet4 192.168.11.182/24
route4 0.0.0.0/0
route4 192.168.11.0/24
route4 169.254.0.0/16
inet6 fe80::801f:dfff:fe52:b39/64
route6 fe80::/64
enp4s0: disconnected
"Qualcomm Atheros Killer E2400"
1 connection available
ethernet (alx), D8:9E:F3:92:24:60, hw, mtu 1500
wlp3s0: disconnected
"Qualcomm Atheros QCA9377"
wifi (ath10k_pci), 90:32:4B:76:E0:B9, hw, mtu 1500
p2p-dev-wlp3s0: disconnected
"p2p-dev-wlp3s0"
wifi-p2p, hw
lo: unmanaged
"lo"
loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536
DNS configuration:
servers: 192.168.11.111
interface: usb0
Use "nmcli device show" to get complete information about known devices and
"nmcli connection show" to get an overview on active connection profiles.
Consult nmcli(1) and nmcli-examples(7) manual pages for complete usage
details.
--
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/1975549
Title:
NetworkManager uses tethered Android phone as ethernet connection
instead of wired ethernet connection
Status in network-manager package in Ubuntu:
New
Bug description:
I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
trouble the last week or two ssh'sing into the machine, and printing
from the machine when I am sitting at the keyboard. I also could not
connect to my external firewall when sitting at the keyboard.
I keep a Google Pixel 4a tethered to the USB hub for charging. The
Android phone is running Android 12, and the phone is set to "USB
Tethering". The phone is fully patched, too.
I found if I reboot the machine with the phone tethered, then the
machine uses the Android phone as the ethernet connection. It
literally calls the connection "ethernet", as if it was using the
network adapter. This is new behavior over the last week or two.
This is unexpected behavior for three reasons. First, it is new
behavior. Second, the wired gigabit ethernet connection is not used by
default. And thrid, the Android phone's connection is called
"ethernet" instead of something more meaningful like "USB" or
"Android" or "wired hotspot".
The third item ("ethernet" name when using Android phone) was
misleading enough to waste a lot of time troubleshooting the issue. I
thought I had an odd firewall issue or a mDNS issue.
The reason I was having so many troubles, like printing and ssh, is
the Android phone uses Wifi and it is on a different VLAN and subnet
to keep traffic segregated from my trusted internal network.
-
It looks like I am running network-manager via systemd:
# service systemd-networkd status
● systemd-networkd.service - Network Service
Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled;
vendor prese>
Active: inactive (dead)
Docs: man:systemd-networkd.service(8)
# service network-manager status
● NetworkManager.service - Network Manager
Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled;
vendor preset: >
Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
Docs: man:NetworkManager(8)
Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
Memory: 12.0M
CGroup: /system.slice/NetworkManager.service
└─928 /usr/sbin/NetworkManager --no-daemon
...
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2022-02-05 (107 days ago)
InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64
(20210819.1)
IpRoute:
default via 172.16.1.1 dev enp4s0 proto dhcp metric 100
169.254.0.0/16 dev enp4s0 scope link metric 1000
172.16.0.0/12 dev enp4s0 proto kernel scope link src 172.16.2.10 metric 100
Package: network-manager 1.22.10-1ubuntu2.3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
Tags: focal
Uname: Linux 5.13.0-44-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
nmcli-con:
NAME UUID
[Touch-packages] [Bug 1975549] WifiSyslog.txt
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1975549/+attachment/5592936/+files/WifiSyslog.txt
--
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/1975549
Title:
NetworkManager uses tethered Android phone as ethernet connection
instead of wired ethernet connection
Status in network-manager package in Ubuntu:
New
Bug description:
I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
trouble the last week or two ssh'sing into the machine, and printing
from the machine when I am sitting at the keyboard. I also could not
connect to my external firewall when sitting at the keyboard.
I keep a Google Pixel 4a tethered to the USB hub for charging. The
Android phone is running Android 12, and the phone is set to "USB
Tethering". The phone is fully patched, too.
I found if I reboot the machine with the phone tethered, then the
machine uses the Android phone as the ethernet connection. It
literally calls the connection "ethernet", as if it was using the
network adapter. This is new behavior over the last week or two.
This is unexpected behavior for three reasons. First, it is new
behavior. Second, the wired gigabit ethernet connection is not used by
default. And thrid, the Android phone's connection is called
"ethernet" instead of something more meaningful like "USB" or
"Android" or "wired hotspot".
The third item ("ethernet" name when using Android phone) was
misleading enough to waste a lot of time troubleshooting the issue. I
thought I had an odd firewall issue or a mDNS issue.
The reason I was having so many troubles, like printing and ssh, is
the Android phone uses Wifi and it is on a different VLAN and subnet
to keep traffic segregated from my trusted internal network.
-
It looks like I am running network-manager via systemd:
# service systemd-networkd status
● systemd-networkd.service - Network Service
Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled;
vendor prese>
Active: inactive (dead)
Docs: man:systemd-networkd.service(8)
# service network-manager status
● NetworkManager.service - Network Manager
Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled;
vendor preset: >
Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
Docs: man:NetworkManager(8)
Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
Memory: 12.0M
CGroup: /system.slice/NetworkManager.service
└─928 /usr/sbin/NetworkManager --no-daemon
...
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2022-02-05 (107 days ago)
InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64
(20210819.1)
IpRoute:
default via 172.16.1.1 dev enp4s0 proto dhcp metric 100
169.254.0.0/16 dev enp4s0 scope link metric 1000
172.16.0.0/12 dev enp4s0 proto kernel scope link src 172.16.2.10 metric 100
Package: network-manager 1.22.10-1ubuntu2.3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
Tags: focal
Uname: Linux 5.13.0-44-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
nmcli-con:
NAME UUID TYPE TIMESTAMP
TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY
DBUS-PATH ACTIVE DEVICE STATE
ACTIVE-PATH SLAVE FILENAME
Ethernet 5d31ea14-c1cd-318f-a982-09ce6723dadb ethernet 1653403311 Tue 24
May 2022 10:41:51 AM EDT yes -100 no
/org/freedesktop/NetworkManager/Settings/1 yes enp4s0 activated
/org/freedesktop/NetworkManager/ActiveConnection/4 --
/etc/NetworkManager/system-connections/Ethernet.nmconnection
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.22.10 connected started full enabled enabled
enabled enabled enabled
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2022-02-05 (108 days ago)
InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64
(20210819.1)
IpRoute:
default via 192.168.11.111 dev usb0 proto dhcp metric 100
169.254.0.0/16 dev usb0 scope link metric 1000
[Touch-packages] [Bug 1975549] nmcli-dev.txt
apport information
** Attachment added: "nmcli-dev.txt"
https://bugs.launchpad.net/bugs/1975549/+attachment/5592937/+files/nmcli-dev.txt
--
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/1975549
Title:
NetworkManager uses tethered Android phone as ethernet connection
instead of wired ethernet connection
Status in network-manager package in Ubuntu:
New
Bug description:
I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
trouble the last week or two ssh'sing into the machine, and printing
from the machine when I am sitting at the keyboard. I also could not
connect to my external firewall when sitting at the keyboard.
I keep a Google Pixel 4a tethered to the USB hub for charging. The
Android phone is running Android 12, and the phone is set to "USB
Tethering". The phone is fully patched, too.
I found if I reboot the machine with the phone tethered, then the
machine uses the Android phone as the ethernet connection. It
literally calls the connection "ethernet", as if it was using the
network adapter. This is new behavior over the last week or two.
This is unexpected behavior for three reasons. First, it is new
behavior. Second, the wired gigabit ethernet connection is not used by
default. And thrid, the Android phone's connection is called
"ethernet" instead of something more meaningful like "USB" or
"Android" or "wired hotspot".
The third item ("ethernet" name when using Android phone) was
misleading enough to waste a lot of time troubleshooting the issue. I
thought I had an odd firewall issue or a mDNS issue.
The reason I was having so many troubles, like printing and ssh, is
the Android phone uses Wifi and it is on a different VLAN and subnet
to keep traffic segregated from my trusted internal network.
-
It looks like I am running network-manager via systemd:
# service systemd-networkd status
● systemd-networkd.service - Network Service
Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled;
vendor prese>
Active: inactive (dead)
Docs: man:systemd-networkd.service(8)
# service network-manager status
● NetworkManager.service - Network Manager
Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled;
vendor preset: >
Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
Docs: man:NetworkManager(8)
Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
Memory: 12.0M
CGroup: /system.slice/NetworkManager.service
└─928 /usr/sbin/NetworkManager --no-daemon
...
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2022-02-05 (107 days ago)
InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64
(20210819.1)
IpRoute:
default via 172.16.1.1 dev enp4s0 proto dhcp metric 100
169.254.0.0/16 dev enp4s0 scope link metric 1000
172.16.0.0/12 dev enp4s0 proto kernel scope link src 172.16.2.10 metric 100
Package: network-manager 1.22.10-1ubuntu2.3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
Tags: focal
Uname: Linux 5.13.0-44-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
nmcli-con:
NAME UUID TYPE TIMESTAMP
TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY
DBUS-PATH ACTIVE DEVICE STATE
ACTIVE-PATH SLAVE FILENAME
Ethernet 5d31ea14-c1cd-318f-a982-09ce6723dadb ethernet 1653403311 Tue 24
May 2022 10:41:51 AM EDT yes -100 no
/org/freedesktop/NetworkManager/Settings/1 yes enp4s0 activated
/org/freedesktop/NetworkManager/ActiveConnection/4 --
/etc/NetworkManager/system-connections/Ethernet.nmconnection
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.22.10 connected started full enabled enabled
enabled enabled enabled
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2022-02-05 (108 days ago)
InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64
(20210819.1)
IpRoute:
default via 192.168.11.111 dev usb0 proto dhcp metric 100
169.254.0.0/16 dev usb0 scope link metric 1000
[Touch-packages] [Bug 1975549] RfKill.txt
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1975549/+attachment/5592935/+files/RfKill.txt
--
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/1975549
Title:
NetworkManager uses tethered Android phone as ethernet connection
instead of wired ethernet connection
Status in network-manager package in Ubuntu:
New
Bug description:
I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
trouble the last week or two ssh'sing into the machine, and printing
from the machine when I am sitting at the keyboard. I also could not
connect to my external firewall when sitting at the keyboard.
I keep a Google Pixel 4a tethered to the USB hub for charging. The
Android phone is running Android 12, and the phone is set to "USB
Tethering". The phone is fully patched, too.
I found if I reboot the machine with the phone tethered, then the
machine uses the Android phone as the ethernet connection. It
literally calls the connection "ethernet", as if it was using the
network adapter. This is new behavior over the last week or two.
This is unexpected behavior for three reasons. First, it is new
behavior. Second, the wired gigabit ethernet connection is not used by
default. And thrid, the Android phone's connection is called
"ethernet" instead of something more meaningful like "USB" or
"Android" or "wired hotspot".
The third item ("ethernet" name when using Android phone) was
misleading enough to waste a lot of time troubleshooting the issue. I
thought I had an odd firewall issue or a mDNS issue.
The reason I was having so many troubles, like printing and ssh, is
the Android phone uses Wifi and it is on a different VLAN and subnet
to keep traffic segregated from my trusted internal network.
-
It looks like I am running network-manager via systemd:
# service systemd-networkd status
● systemd-networkd.service - Network Service
Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled;
vendor prese>
Active: inactive (dead)
Docs: man:systemd-networkd.service(8)
# service network-manager status
● NetworkManager.service - Network Manager
Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled;
vendor preset: >
Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
Docs: man:NetworkManager(8)
Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
Memory: 12.0M
CGroup: /system.slice/NetworkManager.service
└─928 /usr/sbin/NetworkManager --no-daemon
...
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2022-02-05 (107 days ago)
InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64
(20210819.1)
IpRoute:
default via 172.16.1.1 dev enp4s0 proto dhcp metric 100
169.254.0.0/16 dev enp4s0 scope link metric 1000
172.16.0.0/12 dev enp4s0 proto kernel scope link src 172.16.2.10 metric 100
Package: network-manager 1.22.10-1ubuntu2.3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
Tags: focal
Uname: Linux 5.13.0-44-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
nmcli-con:
NAME UUID TYPE TIMESTAMP
TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY
DBUS-PATH ACTIVE DEVICE STATE
ACTIVE-PATH SLAVE FILENAME
Ethernet 5d31ea14-c1cd-318f-a982-09ce6723dadb ethernet 1653403311 Tue 24
May 2022 10:41:51 AM EDT yes -100 no
/org/freedesktop/NetworkManager/Settings/1 yes enp4s0 activated
/org/freedesktop/NetworkManager/ActiveConnection/4 --
/etc/NetworkManager/system-connections/Ethernet.nmconnection
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.22.10 connected started full enabled enabled
enabled enabled enabled
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2022-02-05 (108 days ago)
InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64
(20210819.1)
IpRoute:
default via 192.168.11.111 dev usb0 proto dhcp metric 100
169.254.0.0/16 dev usb0 scope link metric 1000
[Touch-packages] [Bug 1975549] NetworkManager.conf.txt
apport information
** Attachment added: "NetworkManager.conf.txt"
https://bugs.launchpad.net/bugs/1975549/+attachment/5592931/+files/NetworkManager.conf.txt
--
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/1975549
Title:
NetworkManager uses tethered Android phone as ethernet connection
instead of wired ethernet connection
Status in network-manager package in Ubuntu:
New
Bug description:
I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
trouble the last week or two ssh'sing into the machine, and printing
from the machine when I am sitting at the keyboard. I also could not
connect to my external firewall when sitting at the keyboard.
I keep a Google Pixel 4a tethered to the USB hub for charging. The
Android phone is running Android 12, and the phone is set to "USB
Tethering". The phone is fully patched, too.
I found if I reboot the machine with the phone tethered, then the
machine uses the Android phone as the ethernet connection. It
literally calls the connection "ethernet", as if it was using the
network adapter. This is new behavior over the last week or two.
This is unexpected behavior for three reasons. First, it is new
behavior. Second, the wired gigabit ethernet connection is not used by
default. And thrid, the Android phone's connection is called
"ethernet" instead of something more meaningful like "USB" or
"Android" or "wired hotspot".
The third item ("ethernet" name when using Android phone) was
misleading enough to waste a lot of time troubleshooting the issue. I
thought I had an odd firewall issue or a mDNS issue.
The reason I was having so many troubles, like printing and ssh, is
the Android phone uses Wifi and it is on a different VLAN and subnet
to keep traffic segregated from my trusted internal network.
-
It looks like I am running network-manager via systemd:
# service systemd-networkd status
● systemd-networkd.service - Network Service
Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled;
vendor prese>
Active: inactive (dead)
Docs: man:systemd-networkd.service(8)
# service network-manager status
● NetworkManager.service - Network Manager
Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled;
vendor preset: >
Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
Docs: man:NetworkManager(8)
Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
Memory: 12.0M
CGroup: /system.slice/NetworkManager.service
└─928 /usr/sbin/NetworkManager --no-daemon
...
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2022-02-05 (107 days ago)
InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64
(20210819.1)
IpRoute:
default via 172.16.1.1 dev enp4s0 proto dhcp metric 100
169.254.0.0/16 dev enp4s0 scope link metric 1000
172.16.0.0/12 dev enp4s0 proto kernel scope link src 172.16.2.10 metric 100
Package: network-manager 1.22.10-1ubuntu2.3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
Tags: focal
Uname: Linux 5.13.0-44-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
nmcli-con:
NAME UUID TYPE TIMESTAMP
TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY
DBUS-PATH ACTIVE DEVICE STATE
ACTIVE-PATH SLAVE FILENAME
Ethernet 5d31ea14-c1cd-318f-a982-09ce6723dadb ethernet 1653403311 Tue 24
May 2022 10:41:51 AM EDT yes -100 no
/org/freedesktop/NetworkManager/Settings/1 yes enp4s0 activated
/org/freedesktop/NetworkManager/ActiveConnection/4 --
/etc/NetworkManager/system-connections/Ethernet.nmconnection
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.22.10 connected started full enabled enabled
enabled enabled enabled
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2022-02-05 (108 days ago)
InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64
(20210819.1)
IpRoute:
default via 192.168.11.111 dev usb0 proto dhcp metric 100
169.254.0.0/16 dev usb0 scope
[Touch-packages] [Bug 1975549] NetDevice.wlp3s0.txt
apport information
** Attachment added: "NetDevice.wlp3s0.txt"
https://bugs.launchpad.net/bugs/1975549/+attachment/5592930/+files/NetDevice.wlp3s0.txt
--
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/1975549
Title:
NetworkManager uses tethered Android phone as ethernet connection
instead of wired ethernet connection
Status in network-manager package in Ubuntu:
New
Bug description:
I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
trouble the last week or two ssh'sing into the machine, and printing
from the machine when I am sitting at the keyboard. I also could not
connect to my external firewall when sitting at the keyboard.
I keep a Google Pixel 4a tethered to the USB hub for charging. The
Android phone is running Android 12, and the phone is set to "USB
Tethering". The phone is fully patched, too.
I found if I reboot the machine with the phone tethered, then the
machine uses the Android phone as the ethernet connection. It
literally calls the connection "ethernet", as if it was using the
network adapter. This is new behavior over the last week or two.
This is unexpected behavior for three reasons. First, it is new
behavior. Second, the wired gigabit ethernet connection is not used by
default. And thrid, the Android phone's connection is called
"ethernet" instead of something more meaningful like "USB" or
"Android" or "wired hotspot".
The third item ("ethernet" name when using Android phone) was
misleading enough to waste a lot of time troubleshooting the issue. I
thought I had an odd firewall issue or a mDNS issue.
The reason I was having so many troubles, like printing and ssh, is
the Android phone uses Wifi and it is on a different VLAN and subnet
to keep traffic segregated from my trusted internal network.
-
It looks like I am running network-manager via systemd:
# service systemd-networkd status
● systemd-networkd.service - Network Service
Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled;
vendor prese>
Active: inactive (dead)
Docs: man:systemd-networkd.service(8)
# service network-manager status
● NetworkManager.service - Network Manager
Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled;
vendor preset: >
Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
Docs: man:NetworkManager(8)
Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
Memory: 12.0M
CGroup: /system.slice/NetworkManager.service
└─928 /usr/sbin/NetworkManager --no-daemon
...
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2022-02-05 (107 days ago)
InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64
(20210819.1)
IpRoute:
default via 172.16.1.1 dev enp4s0 proto dhcp metric 100
169.254.0.0/16 dev enp4s0 scope link metric 1000
172.16.0.0/12 dev enp4s0 proto kernel scope link src 172.16.2.10 metric 100
Package: network-manager 1.22.10-1ubuntu2.3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
Tags: focal
Uname: Linux 5.13.0-44-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
nmcli-con:
NAME UUID TYPE TIMESTAMP
TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY
DBUS-PATH ACTIVE DEVICE STATE
ACTIVE-PATH SLAVE FILENAME
Ethernet 5d31ea14-c1cd-318f-a982-09ce6723dadb ethernet 1653403311 Tue 24
May 2022 10:41:51 AM EDT yes -100 no
/org/freedesktop/NetworkManager/Settings/1 yes enp4s0 activated
/org/freedesktop/NetworkManager/ActiveConnection/4 --
/etc/NetworkManager/system-connections/Ethernet.nmconnection
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.22.10 connected started full enabled enabled
enabled enabled enabled
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2022-02-05 (108 days ago)
InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64
(20210819.1)
IpRoute:
default via 192.168.11.111 dev usb0 proto dhcp metric 100
169.254.0.0/16 dev usb0 scope link
[Touch-packages] [Bug 1975549] ProcEnviron.txt
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1975549/+attachment/5592934/+files/ProcEnviron.txt
--
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/1975549
Title:
NetworkManager uses tethered Android phone as ethernet connection
instead of wired ethernet connection
Status in network-manager package in Ubuntu:
New
Bug description:
I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
trouble the last week or two ssh'sing into the machine, and printing
from the machine when I am sitting at the keyboard. I also could not
connect to my external firewall when sitting at the keyboard.
I keep a Google Pixel 4a tethered to the USB hub for charging. The
Android phone is running Android 12, and the phone is set to "USB
Tethering". The phone is fully patched, too.
I found if I reboot the machine with the phone tethered, then the
machine uses the Android phone as the ethernet connection. It
literally calls the connection "ethernet", as if it was using the
network adapter. This is new behavior over the last week or two.
This is unexpected behavior for three reasons. First, it is new
behavior. Second, the wired gigabit ethernet connection is not used by
default. And thrid, the Android phone's connection is called
"ethernet" instead of something more meaningful like "USB" or
"Android" or "wired hotspot".
The third item ("ethernet" name when using Android phone) was
misleading enough to waste a lot of time troubleshooting the issue. I
thought I had an odd firewall issue or a mDNS issue.
The reason I was having so many troubles, like printing and ssh, is
the Android phone uses Wifi and it is on a different VLAN and subnet
to keep traffic segregated from my trusted internal network.
-
It looks like I am running network-manager via systemd:
# service systemd-networkd status
● systemd-networkd.service - Network Service
Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled;
vendor prese>
Active: inactive (dead)
Docs: man:systemd-networkd.service(8)
# service network-manager status
● NetworkManager.service - Network Manager
Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled;
vendor preset: >
Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
Docs: man:NetworkManager(8)
Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
Memory: 12.0M
CGroup: /system.slice/NetworkManager.service
└─928 /usr/sbin/NetworkManager --no-daemon
...
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2022-02-05 (107 days ago)
InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64
(20210819.1)
IpRoute:
default via 172.16.1.1 dev enp4s0 proto dhcp metric 100
169.254.0.0/16 dev enp4s0 scope link metric 1000
172.16.0.0/12 dev enp4s0 proto kernel scope link src 172.16.2.10 metric 100
Package: network-manager 1.22.10-1ubuntu2.3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
Tags: focal
Uname: Linux 5.13.0-44-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
nmcli-con:
NAME UUID TYPE TIMESTAMP
TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY
DBUS-PATH ACTIVE DEVICE STATE
ACTIVE-PATH SLAVE FILENAME
Ethernet 5d31ea14-c1cd-318f-a982-09ce6723dadb ethernet 1653403311 Tue 24
May 2022 10:41:51 AM EDT yes -100 no
/org/freedesktop/NetworkManager/Settings/1 yes enp4s0 activated
/org/freedesktop/NetworkManager/ActiveConnection/4 --
/etc/NetworkManager/system-connections/Ethernet.nmconnection
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.22.10 connected started full enabled enabled
enabled enabled enabled
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2022-02-05 (108 days ago)
InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64
(20210819.1)
IpRoute:
default via 192.168.11.111 dev usb0 proto dhcp metric 100
169.254.0.0/16 dev usb0 scope link metric 1000
[Touch-packages] [Bug 1975549] NetDevice.usb0.txt
apport information
** Attachment added: "NetDevice.usb0.txt"
https://bugs.launchpad.net/bugs/1975549/+attachment/5592929/+files/NetDevice.usb0.txt
--
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/1975549
Title:
NetworkManager uses tethered Android phone as ethernet connection
instead of wired ethernet connection
Status in network-manager package in Ubuntu:
New
Bug description:
I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
trouble the last week or two ssh'sing into the machine, and printing
from the machine when I am sitting at the keyboard. I also could not
connect to my external firewall when sitting at the keyboard.
I keep a Google Pixel 4a tethered to the USB hub for charging. The
Android phone is running Android 12, and the phone is set to "USB
Tethering". The phone is fully patched, too.
I found if I reboot the machine with the phone tethered, then the
machine uses the Android phone as the ethernet connection. It
literally calls the connection "ethernet", as if it was using the
network adapter. This is new behavior over the last week or two.
This is unexpected behavior for three reasons. First, it is new
behavior. Second, the wired gigabit ethernet connection is not used by
default. And thrid, the Android phone's connection is called
"ethernet" instead of something more meaningful like "USB" or
"Android" or "wired hotspot".
The third item ("ethernet" name when using Android phone) was
misleading enough to waste a lot of time troubleshooting the issue. I
thought I had an odd firewall issue or a mDNS issue.
The reason I was having so many troubles, like printing and ssh, is
the Android phone uses Wifi and it is on a different VLAN and subnet
to keep traffic segregated from my trusted internal network.
-
It looks like I am running network-manager via systemd:
# service systemd-networkd status
● systemd-networkd.service - Network Service
Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled;
vendor prese>
Active: inactive (dead)
Docs: man:systemd-networkd.service(8)
# service network-manager status
● NetworkManager.service - Network Manager
Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled;
vendor preset: >
Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
Docs: man:NetworkManager(8)
Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
Memory: 12.0M
CGroup: /system.slice/NetworkManager.service
└─928 /usr/sbin/NetworkManager --no-daemon
...
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2022-02-05 (107 days ago)
InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64
(20210819.1)
IpRoute:
default via 172.16.1.1 dev enp4s0 proto dhcp metric 100
169.254.0.0/16 dev enp4s0 scope link metric 1000
172.16.0.0/12 dev enp4s0 proto kernel scope link src 172.16.2.10 metric 100
Package: network-manager 1.22.10-1ubuntu2.3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
Tags: focal
Uname: Linux 5.13.0-44-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
nmcli-con:
NAME UUID TYPE TIMESTAMP
TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY
DBUS-PATH ACTIVE DEVICE STATE
ACTIVE-PATH SLAVE FILENAME
Ethernet 5d31ea14-c1cd-318f-a982-09ce6723dadb ethernet 1653403311 Tue 24
May 2022 10:41:51 AM EDT yes -100 no
/org/freedesktop/NetworkManager/Settings/1 yes enp4s0 activated
/org/freedesktop/NetworkManager/ActiveConnection/4 --
/etc/NetworkManager/system-connections/Ethernet.nmconnection
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.22.10 connected started full enabled enabled
enabled enabled enabled
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2022-02-05 (108 days ago)
InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64
(20210819.1)
IpRoute:
default via 192.168.11.111 dev usb0 proto dhcp metric 100
169.254.0.0/16 dev usb0 scope link metric
[Touch-packages] [Bug 1975549] PciNetwork.txt
apport information
** Attachment added: "PciNetwork.txt"
https://bugs.launchpad.net/bugs/1975549/+attachment/5592932/+files/PciNetwork.txt
--
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/1975549
Title:
NetworkManager uses tethered Android phone as ethernet connection
instead of wired ethernet connection
Status in network-manager package in Ubuntu:
New
Bug description:
I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
trouble the last week or two ssh'sing into the machine, and printing
from the machine when I am sitting at the keyboard. I also could not
connect to my external firewall when sitting at the keyboard.
I keep a Google Pixel 4a tethered to the USB hub for charging. The
Android phone is running Android 12, and the phone is set to "USB
Tethering". The phone is fully patched, too.
I found if I reboot the machine with the phone tethered, then the
machine uses the Android phone as the ethernet connection. It
literally calls the connection "ethernet", as if it was using the
network adapter. This is new behavior over the last week or two.
This is unexpected behavior for three reasons. First, it is new
behavior. Second, the wired gigabit ethernet connection is not used by
default. And thrid, the Android phone's connection is called
"ethernet" instead of something more meaningful like "USB" or
"Android" or "wired hotspot".
The third item ("ethernet" name when using Android phone) was
misleading enough to waste a lot of time troubleshooting the issue. I
thought I had an odd firewall issue or a mDNS issue.
The reason I was having so many troubles, like printing and ssh, is
the Android phone uses Wifi and it is on a different VLAN and subnet
to keep traffic segregated from my trusted internal network.
-
It looks like I am running network-manager via systemd:
# service systemd-networkd status
● systemd-networkd.service - Network Service
Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled;
vendor prese>
Active: inactive (dead)
Docs: man:systemd-networkd.service(8)
# service network-manager status
● NetworkManager.service - Network Manager
Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled;
vendor preset: >
Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
Docs: man:NetworkManager(8)
Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
Memory: 12.0M
CGroup: /system.slice/NetworkManager.service
└─928 /usr/sbin/NetworkManager --no-daemon
...
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2022-02-05 (107 days ago)
InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64
(20210819.1)
IpRoute:
default via 172.16.1.1 dev enp4s0 proto dhcp metric 100
169.254.0.0/16 dev enp4s0 scope link metric 1000
172.16.0.0/12 dev enp4s0 proto kernel scope link src 172.16.2.10 metric 100
Package: network-manager 1.22.10-1ubuntu2.3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
Tags: focal
Uname: Linux 5.13.0-44-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
nmcli-con:
NAME UUID TYPE TIMESTAMP
TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY
DBUS-PATH ACTIVE DEVICE STATE
ACTIVE-PATH SLAVE FILENAME
Ethernet 5d31ea14-c1cd-318f-a982-09ce6723dadb ethernet 1653403311 Tue 24
May 2022 10:41:51 AM EDT yes -100 no
/org/freedesktop/NetworkManager/Settings/1 yes enp4s0 activated
/org/freedesktop/NetworkManager/ActiveConnection/4 --
/etc/NetworkManager/system-connections/Ethernet.nmconnection
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.22.10 connected started full enabled enabled
enabled enabled enabled
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2022-02-05 (108 days ago)
InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64
(20210819.1)
IpRoute:
default via 192.168.11.111 dev usb0 proto dhcp metric 100
169.254.0.0/16 dev usb0 scope link metric 1000
[Touch-packages] [Bug 1975549] ProcCpuinfoMinimal.txt
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1975549/+attachment/5592933/+files/ProcCpuinfoMinimal.txt
--
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/1975549
Title:
NetworkManager uses tethered Android phone as ethernet connection
instead of wired ethernet connection
Status in network-manager package in Ubuntu:
New
Bug description:
I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
trouble the last week or two ssh'sing into the machine, and printing
from the machine when I am sitting at the keyboard. I also could not
connect to my external firewall when sitting at the keyboard.
I keep a Google Pixel 4a tethered to the USB hub for charging. The
Android phone is running Android 12, and the phone is set to "USB
Tethering". The phone is fully patched, too.
I found if I reboot the machine with the phone tethered, then the
machine uses the Android phone as the ethernet connection. It
literally calls the connection "ethernet", as if it was using the
network adapter. This is new behavior over the last week or two.
This is unexpected behavior for three reasons. First, it is new
behavior. Second, the wired gigabit ethernet connection is not used by
default. And thrid, the Android phone's connection is called
"ethernet" instead of something more meaningful like "USB" or
"Android" or "wired hotspot".
The third item ("ethernet" name when using Android phone) was
misleading enough to waste a lot of time troubleshooting the issue. I
thought I had an odd firewall issue or a mDNS issue.
The reason I was having so many troubles, like printing and ssh, is
the Android phone uses Wifi and it is on a different VLAN and subnet
to keep traffic segregated from my trusted internal network.
-
It looks like I am running network-manager via systemd:
# service systemd-networkd status
● systemd-networkd.service - Network Service
Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled;
vendor prese>
Active: inactive (dead)
Docs: man:systemd-networkd.service(8)
# service network-manager status
● NetworkManager.service - Network Manager
Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled;
vendor preset: >
Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
Docs: man:NetworkManager(8)
Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
Memory: 12.0M
CGroup: /system.slice/NetworkManager.service
└─928 /usr/sbin/NetworkManager --no-daemon
...
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2022-02-05 (107 days ago)
InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64
(20210819.1)
IpRoute:
default via 172.16.1.1 dev enp4s0 proto dhcp metric 100
169.254.0.0/16 dev enp4s0 scope link metric 1000
172.16.0.0/12 dev enp4s0 proto kernel scope link src 172.16.2.10 metric 100
Package: network-manager 1.22.10-1ubuntu2.3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
Tags: focal
Uname: Linux 5.13.0-44-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
nmcli-con:
NAME UUID TYPE TIMESTAMP
TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY
DBUS-PATH ACTIVE DEVICE STATE
ACTIVE-PATH SLAVE FILENAME
Ethernet 5d31ea14-c1cd-318f-a982-09ce6723dadb ethernet 1653403311 Tue 24
May 2022 10:41:51 AM EDT yes -100 no
/org/freedesktop/NetworkManager/Settings/1 yes enp4s0 activated
/org/freedesktop/NetworkManager/ActiveConnection/4 --
/etc/NetworkManager/system-connections/Ethernet.nmconnection
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.22.10 connected started full enabled enabled
enabled enabled enabled
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2022-02-05 (108 days ago)
InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64
(20210819.1)
IpRoute:
default via 192.168.11.111 dev usb0 proto dhcp metric 100
169.254.0.0/16 dev usb0 scope
[Touch-packages] [Bug 1975549] NetDevice.enp4s0.txt
apport information
** Attachment added: "NetDevice.enp4s0.txt"
https://bugs.launchpad.net/bugs/1975549/+attachment/5592927/+files/NetDevice.enp4s0.txt
--
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/1975549
Title:
NetworkManager uses tethered Android phone as ethernet connection
instead of wired ethernet connection
Status in network-manager package in Ubuntu:
New
Bug description:
I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
trouble the last week or two ssh'sing into the machine, and printing
from the machine when I am sitting at the keyboard. I also could not
connect to my external firewall when sitting at the keyboard.
I keep a Google Pixel 4a tethered to the USB hub for charging. The
Android phone is running Android 12, and the phone is set to "USB
Tethering". The phone is fully patched, too.
I found if I reboot the machine with the phone tethered, then the
machine uses the Android phone as the ethernet connection. It
literally calls the connection "ethernet", as if it was using the
network adapter. This is new behavior over the last week or two.
This is unexpected behavior for three reasons. First, it is new
behavior. Second, the wired gigabit ethernet connection is not used by
default. And thrid, the Android phone's connection is called
"ethernet" instead of something more meaningful like "USB" or
"Android" or "wired hotspot".
The third item ("ethernet" name when using Android phone) was
misleading enough to waste a lot of time troubleshooting the issue. I
thought I had an odd firewall issue or a mDNS issue.
The reason I was having so many troubles, like printing and ssh, is
the Android phone uses Wifi and it is on a different VLAN and subnet
to keep traffic segregated from my trusted internal network.
-
It looks like I am running network-manager via systemd:
# service systemd-networkd status
● systemd-networkd.service - Network Service
Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled;
vendor prese>
Active: inactive (dead)
Docs: man:systemd-networkd.service(8)
# service network-manager status
● NetworkManager.service - Network Manager
Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled;
vendor preset: >
Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
Docs: man:NetworkManager(8)
Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
Memory: 12.0M
CGroup: /system.slice/NetworkManager.service
└─928 /usr/sbin/NetworkManager --no-daemon
...
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2022-02-05 (107 days ago)
InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64
(20210819.1)
IpRoute:
default via 172.16.1.1 dev enp4s0 proto dhcp metric 100
169.254.0.0/16 dev enp4s0 scope link metric 1000
172.16.0.0/12 dev enp4s0 proto kernel scope link src 172.16.2.10 metric 100
Package: network-manager 1.22.10-1ubuntu2.3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
Tags: focal
Uname: Linux 5.13.0-44-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
nmcli-con:
NAME UUID TYPE TIMESTAMP
TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY
DBUS-PATH ACTIVE DEVICE STATE
ACTIVE-PATH SLAVE FILENAME
Ethernet 5d31ea14-c1cd-318f-a982-09ce6723dadb ethernet 1653403311 Tue 24
May 2022 10:41:51 AM EDT yes -100 no
/org/freedesktop/NetworkManager/Settings/1 yes enp4s0 activated
/org/freedesktop/NetworkManager/ActiveConnection/4 --
/etc/NetworkManager/system-connections/Ethernet.nmconnection
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.22.10 connected started full enabled enabled
enabled enabled enabled
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2022-02-05 (108 days ago)
InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64
(20210819.1)
IpRoute:
default via 192.168.11.111 dev usb0 proto dhcp metric 100
169.254.0.0/16 dev usb0 scope link
[Touch-packages] [Bug 1975549] NetDevice.lo.txt
apport information
** Attachment added: "NetDevice.lo.txt"
https://bugs.launchpad.net/bugs/1975549/+attachment/5592928/+files/NetDevice.lo.txt
--
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/1975549
Title:
NetworkManager uses tethered Android phone as ethernet connection
instead of wired ethernet connection
Status in network-manager package in Ubuntu:
New
Bug description:
I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
trouble the last week or two ssh'sing into the machine, and printing
from the machine when I am sitting at the keyboard. I also could not
connect to my external firewall when sitting at the keyboard.
I keep a Google Pixel 4a tethered to the USB hub for charging. The
Android phone is running Android 12, and the phone is set to "USB
Tethering". The phone is fully patched, too.
I found if I reboot the machine with the phone tethered, then the
machine uses the Android phone as the ethernet connection. It
literally calls the connection "ethernet", as if it was using the
network adapter. This is new behavior over the last week or two.
This is unexpected behavior for three reasons. First, it is new
behavior. Second, the wired gigabit ethernet connection is not used by
default. And thrid, the Android phone's connection is called
"ethernet" instead of something more meaningful like "USB" or
"Android" or "wired hotspot".
The third item ("ethernet" name when using Android phone) was
misleading enough to waste a lot of time troubleshooting the issue. I
thought I had an odd firewall issue or a mDNS issue.
The reason I was having so many troubles, like printing and ssh, is
the Android phone uses Wifi and it is on a different VLAN and subnet
to keep traffic segregated from my trusted internal network.
-
It looks like I am running network-manager via systemd:
# service systemd-networkd status
● systemd-networkd.service - Network Service
Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled;
vendor prese>
Active: inactive (dead)
Docs: man:systemd-networkd.service(8)
# service network-manager status
● NetworkManager.service - Network Manager
Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled;
vendor preset: >
Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
Docs: man:NetworkManager(8)
Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
Memory: 12.0M
CGroup: /system.slice/NetworkManager.service
└─928 /usr/sbin/NetworkManager --no-daemon
...
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2022-02-05 (107 days ago)
InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64
(20210819.1)
IpRoute:
default via 172.16.1.1 dev enp4s0 proto dhcp metric 100
169.254.0.0/16 dev enp4s0 scope link metric 1000
172.16.0.0/12 dev enp4s0 proto kernel scope link src 172.16.2.10 metric 100
Package: network-manager 1.22.10-1ubuntu2.3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
Tags: focal
Uname: Linux 5.13.0-44-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
nmcli-con:
NAME UUID TYPE TIMESTAMP
TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY
DBUS-PATH ACTIVE DEVICE STATE
ACTIVE-PATH SLAVE FILENAME
Ethernet 5d31ea14-c1cd-318f-a982-09ce6723dadb ethernet 1653403311 Tue 24
May 2022 10:41:51 AM EDT yes -100 no
/org/freedesktop/NetworkManager/Settings/1 yes enp4s0 activated
/org/freedesktop/NetworkManager/ActiveConnection/4 --
/etc/NetworkManager/system-connections/Ethernet.nmconnection
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.22.10 connected started full enabled enabled
enabled enabled enabled
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2022-02-05 (108 days ago)
InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64
(20210819.1)
IpRoute:
default via 192.168.11.111 dev usb0 proto dhcp metric 100
169.254.0.0/16 dev usb0 scope link metric
[Touch-packages] [Bug 1975549] Dependencies.txt
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1975549/+attachment/5592924/+files/Dependencies.txt
--
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/1975549
Title:
NetworkManager uses tethered Android phone as ethernet connection
instead of wired ethernet connection
Status in network-manager package in Ubuntu:
New
Bug description:
I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
trouble the last week or two ssh'sing into the machine, and printing
from the machine when I am sitting at the keyboard. I also could not
connect to my external firewall when sitting at the keyboard.
I keep a Google Pixel 4a tethered to the USB hub for charging. The
Android phone is running Android 12, and the phone is set to "USB
Tethering". The phone is fully patched, too.
I found if I reboot the machine with the phone tethered, then the
machine uses the Android phone as the ethernet connection. It
literally calls the connection "ethernet", as if it was using the
network adapter. This is new behavior over the last week or two.
This is unexpected behavior for three reasons. First, it is new
behavior. Second, the wired gigabit ethernet connection is not used by
default. And thrid, the Android phone's connection is called
"ethernet" instead of something more meaningful like "USB" or
"Android" or "wired hotspot".
The third item ("ethernet" name when using Android phone) was
misleading enough to waste a lot of time troubleshooting the issue. I
thought I had an odd firewall issue or a mDNS issue.
The reason I was having so many troubles, like printing and ssh, is
the Android phone uses Wifi and it is on a different VLAN and subnet
to keep traffic segregated from my trusted internal network.
-
It looks like I am running network-manager via systemd:
# service systemd-networkd status
● systemd-networkd.service - Network Service
Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled;
vendor prese>
Active: inactive (dead)
Docs: man:systemd-networkd.service(8)
# service network-manager status
● NetworkManager.service - Network Manager
Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled;
vendor preset: >
Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
Docs: man:NetworkManager(8)
Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
Memory: 12.0M
CGroup: /system.slice/NetworkManager.service
└─928 /usr/sbin/NetworkManager --no-daemon
...
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2022-02-05 (107 days ago)
InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64
(20210819.1)
IpRoute:
default via 172.16.1.1 dev enp4s0 proto dhcp metric 100
169.254.0.0/16 dev enp4s0 scope link metric 1000
172.16.0.0/12 dev enp4s0 proto kernel scope link src 172.16.2.10 metric 100
Package: network-manager 1.22.10-1ubuntu2.3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
Tags: focal
Uname: Linux 5.13.0-44-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
nmcli-con:
NAME UUID TYPE TIMESTAMP
TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY
DBUS-PATH ACTIVE DEVICE STATE
ACTIVE-PATH SLAVE FILENAME
Ethernet 5d31ea14-c1cd-318f-a982-09ce6723dadb ethernet 1653403311 Tue 24
May 2022 10:41:51 AM EDT yes -100 no
/org/freedesktop/NetworkManager/Settings/1 yes enp4s0 activated
/org/freedesktop/NetworkManager/ActiveConnection/4 --
/etc/NetworkManager/system-connections/Ethernet.nmconnection
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.22.10 connected started full enabled enabled
enabled enabled enabled
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2022-02-05 (108 days ago)
InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64
(20210819.1)
IpRoute:
default via 192.168.11.111 dev usb0 proto dhcp metric 100
169.254.0.0/16 dev usb0 scope link metric
[Touch-packages] [Bug 1975549] IpAddr.txt
apport information
** Attachment added: "IpAddr.txt"
https://bugs.launchpad.net/bugs/1975549/+attachment/5592925/+files/IpAddr.txt
--
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/1975549
Title:
NetworkManager uses tethered Android phone as ethernet connection
instead of wired ethernet connection
Status in network-manager package in Ubuntu:
New
Bug description:
I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
trouble the last week or two ssh'sing into the machine, and printing
from the machine when I am sitting at the keyboard. I also could not
connect to my external firewall when sitting at the keyboard.
I keep a Google Pixel 4a tethered to the USB hub for charging. The
Android phone is running Android 12, and the phone is set to "USB
Tethering". The phone is fully patched, too.
I found if I reboot the machine with the phone tethered, then the
machine uses the Android phone as the ethernet connection. It
literally calls the connection "ethernet", as if it was using the
network adapter. This is new behavior over the last week or two.
This is unexpected behavior for three reasons. First, it is new
behavior. Second, the wired gigabit ethernet connection is not used by
default. And thrid, the Android phone's connection is called
"ethernet" instead of something more meaningful like "USB" or
"Android" or "wired hotspot".
The third item ("ethernet" name when using Android phone) was
misleading enough to waste a lot of time troubleshooting the issue. I
thought I had an odd firewall issue or a mDNS issue.
The reason I was having so many troubles, like printing and ssh, is
the Android phone uses Wifi and it is on a different VLAN and subnet
to keep traffic segregated from my trusted internal network.
-
It looks like I am running network-manager via systemd:
# service systemd-networkd status
● systemd-networkd.service - Network Service
Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled;
vendor prese>
Active: inactive (dead)
Docs: man:systemd-networkd.service(8)
# service network-manager status
● NetworkManager.service - Network Manager
Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled;
vendor preset: >
Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
Docs: man:NetworkManager(8)
Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
Memory: 12.0M
CGroup: /system.slice/NetworkManager.service
└─928 /usr/sbin/NetworkManager --no-daemon
...
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2022-02-05 (107 days ago)
InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64
(20210819.1)
IpRoute:
default via 172.16.1.1 dev enp4s0 proto dhcp metric 100
169.254.0.0/16 dev enp4s0 scope link metric 1000
172.16.0.0/12 dev enp4s0 proto kernel scope link src 172.16.2.10 metric 100
Package: network-manager 1.22.10-1ubuntu2.3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
Tags: focal
Uname: Linux 5.13.0-44-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
nmcli-con:
NAME UUID TYPE TIMESTAMP
TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY
DBUS-PATH ACTIVE DEVICE STATE
ACTIVE-PATH SLAVE FILENAME
Ethernet 5d31ea14-c1cd-318f-a982-09ce6723dadb ethernet 1653403311 Tue 24
May 2022 10:41:51 AM EDT yes -100 no
/org/freedesktop/NetworkManager/Settings/1 yes enp4s0 activated
/org/freedesktop/NetworkManager/ActiveConnection/4 --
/etc/NetworkManager/system-connections/Ethernet.nmconnection
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.22.10 connected started full enabled enabled
enabled enabled enabled
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2022-02-05 (108 days ago)
InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64
(20210819.1)
IpRoute:
default via 192.168.11.111 dev usb0 proto dhcp metric 100
169.254.0.0/16 dev usb0 scope link metric 1000
[Touch-packages] [Bug 1975549] IwConfig.txt
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1975549/+attachment/5592926/+files/IwConfig.txt
--
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/1975549
Title:
NetworkManager uses tethered Android phone as ethernet connection
instead of wired ethernet connection
Status in network-manager package in Ubuntu:
New
Bug description:
I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
trouble the last week or two ssh'sing into the machine, and printing
from the machine when I am sitting at the keyboard. I also could not
connect to my external firewall when sitting at the keyboard.
I keep a Google Pixel 4a tethered to the USB hub for charging. The
Android phone is running Android 12, and the phone is set to "USB
Tethering". The phone is fully patched, too.
I found if I reboot the machine with the phone tethered, then the
machine uses the Android phone as the ethernet connection. It
literally calls the connection "ethernet", as if it was using the
network adapter. This is new behavior over the last week or two.
This is unexpected behavior for three reasons. First, it is new
behavior. Second, the wired gigabit ethernet connection is not used by
default. And thrid, the Android phone's connection is called
"ethernet" instead of something more meaningful like "USB" or
"Android" or "wired hotspot".
The third item ("ethernet" name when using Android phone) was
misleading enough to waste a lot of time troubleshooting the issue. I
thought I had an odd firewall issue or a mDNS issue.
The reason I was having so many troubles, like printing and ssh, is
the Android phone uses Wifi and it is on a different VLAN and subnet
to keep traffic segregated from my trusted internal network.
-
It looks like I am running network-manager via systemd:
# service systemd-networkd status
● systemd-networkd.service - Network Service
Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled;
vendor prese>
Active: inactive (dead)
Docs: man:systemd-networkd.service(8)
# service network-manager status
● NetworkManager.service - Network Manager
Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled;
vendor preset: >
Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
Docs: man:NetworkManager(8)
Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
Memory: 12.0M
CGroup: /system.slice/NetworkManager.service
└─928 /usr/sbin/NetworkManager --no-daemon
...
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2022-02-05 (107 days ago)
InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64
(20210819.1)
IpRoute:
default via 172.16.1.1 dev enp4s0 proto dhcp metric 100
169.254.0.0/16 dev enp4s0 scope link metric 1000
172.16.0.0/12 dev enp4s0 proto kernel scope link src 172.16.2.10 metric 100
Package: network-manager 1.22.10-1ubuntu2.3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
Tags: focal
Uname: Linux 5.13.0-44-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
nmcli-con:
NAME UUID TYPE TIMESTAMP
TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY
DBUS-PATH ACTIVE DEVICE STATE
ACTIVE-PATH SLAVE FILENAME
Ethernet 5d31ea14-c1cd-318f-a982-09ce6723dadb ethernet 1653403311 Tue 24
May 2022 10:41:51 AM EDT yes -100 no
/org/freedesktop/NetworkManager/Settings/1 yes enp4s0 activated
/org/freedesktop/NetworkManager/ActiveConnection/4 --
/etc/NetworkManager/system-connections/Ethernet.nmconnection
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.22.10 connected started full enabled enabled
enabled enabled enabled
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2022-02-05 (108 days ago)
InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64
(20210819.1)
IpRoute:
default via 192.168.11.111 dev usb0 proto dhcp metric 100
169.254.0.0/16 dev usb0 scope link metric 1000
[Touch-packages] [Bug 1975549] Re: NetworkManager uses tethered Android phone as ethernet connection instead of wired ethernet connection
apport information
** Description changed:
I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
trouble the last week or two ssh'sing into the machine, and printing
from the machine when I am sitting at the keyboard. I also could not
connect to my external firewall when sitting at the keyboard.
I keep a Google Pixel 4a tethered to the USB hub for charging. The
Android phone is running Android 12, and the phone is set to "USB
Tethering". The phone is fully patched, too.
I found if I reboot the machine with the phone tethered, then the
machine uses the Android phone as the ethernet connection. It literally
calls the connection "ethernet", as if it was using the network adapter.
This is new behavior over the last week or two.
This is unexpected behavior for three reasons. First, it is new
behavior. Second, the wired gigabit ethernet connection is not used by
default. And thrid, the Android phone's connection is called "ethernet"
instead of something more meaningful like "USB" or "Android" or "wired
hotspot".
The third item ("ethernet" name when using Android phone) was misleading
enough to waste a lot of time troubleshooting the issue. I thought I had
an odd firewall issue or a mDNS issue.
The reason I was having so many troubles, like printing and ssh, is the
Android phone uses Wifi and it is on a different VLAN and subnet to keep
traffic segregated from my trusted internal network.
-
It looks like I am running network-manager via systemd:
# service systemd-networkd status
● systemd-networkd.service - Network Service
Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled;
vendor prese>
Active: inactive (dead)
Docs: man:systemd-networkd.service(8)
# service network-manager status
● NetworkManager.service - Network Manager
Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled;
vendor preset: >
Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
Docs: man:NetworkManager(8)
Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
Memory: 12.0M
CGroup: /system.slice/NetworkManager.service
└─928 /usr/sbin/NetworkManager --no-daemon
...
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2022-02-05 (107 days ago)
InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64
(20210819.1)
IpRoute:
default via 172.16.1.1 dev enp4s0 proto dhcp metric 100
169.254.0.0/16 dev enp4s0 scope link metric 1000
172.16.0.0/12 dev enp4s0 proto kernel scope link src 172.16.2.10 metric 100
Package: network-manager 1.22.10-1ubuntu2.3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
Tags: focal
Uname: Linux 5.13.0-44-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
nmcli-con:
NAME UUID TYPE TIMESTAMP
TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY
DBUS-PATH ACTIVE DEVICE STATE
ACTIVE-PATH SLAVE FILENAME
Ethernet 5d31ea14-c1cd-318f-a982-09ce6723dadb ethernet 1653403311 Tue 24
May 2022 10:41:51 AM EDT yes -100 no
/org/freedesktop/NetworkManager/Settings/1 yes enp4s0 activated
/org/freedesktop/NetworkManager/ActiveConnection/4 --
/etc/NetworkManager/system-connections/Ethernet.nmconnection
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.22.10 connected started full enabled enabled
enabled enabled enabled
+ ---
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.24
+ Architecture: amd64
+ CasperMD5CheckResult: skip
+ CurrentDesktop: KDE
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2022-02-05 (108 days ago)
+ InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64
(20210819.1)
+ IpRoute:
+ default via 192.168.11.111 dev usb0 proto dhcp metric 100
+ 169.254.0.0/16 dev usb0 scope link metric 1000
+ 192.168.11.0/24 dev usb0 proto kernel scope link src 192.168.11.182 metric
100
+ Package: network-manager 1.22.10-1ubuntu2.3
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
+ Tags: focal
+ Uname: Linux 5.13.0-44-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True
+ nmcli-con:
+
[Touch-packages] [Bug 1524879] Re: initramfs-tools, Xenial is missing NVME kernel driver
This bug is still present in 20.04, k5.4.0-113 at this writing. Apparently the script looks *only* at /boot to decide which drivers are needed. When root (or /home) is on a separate nvme drive, the system won't boot until initramfs is updated manually (with nvme driver). The fix seems pretty simple; just test the root fs type and include the drivers if different from those of /boot, then update initramfs. -- 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/1524879 Title: initramfs-tools, Xenial is missing NVME kernel driver Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Trusty: Triaged Status in initramfs-tools package in Debian: Fix Released Bug description: I can't boot from a PCIe NVME device on Xenial because the nvme.ko is missing from the initramfs. Can this please be added. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1524879/+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 1974230] Re: Negative cache results from dnsmasq do not include SOA as required in RFC2308
Thanks Simon to pick this up with your SME, have you opened a tracker bug for this in Debian or Upstream so that we can track it if it is implemented some day. ** Tags removed: server-triage-discuss ** Changed in: dnsmasq (Ubuntu) Importance: Undecided => Wishlist ** Changed in: dnsmasq (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1974230 Title: Negative cache results from dnsmasq do not include SOA as required in RFC2308 Status in dnsmasq package in Ubuntu: Triaged Bug description: RFC2308 states: 6 - Negative answers from the cache When a server, in answering a query, encounters a cached negative response it MUST add the cached SOA record to the authority section of the response with the TTL decremented by the amount of time it was stored in the cache. This allows the NXDOMAIN / NODATA response to time out correctly. The effect is that the negative cache results returned by dnsmasq cannot be cached by other resolvers such as systemd-resolved. A good example of why this is a problem: Two clients with systemd-resolved send DNS queries to dnsmasq for the same record The first one makes a query and gets NXDOMAIN with SOA. This results in systemd-resolved caching the negative result. The second client makes a query and gets NODATA without the SOA. This results in systemd-resolved not caching the negative result. Consider a domain name that only has an A record published. When connecting to that domain a lookup happens for the and A record. One can end up in a situation where systemd-resolved has the A record cached locally, but it still goes out to the network to perform the lookup only to get the same negative cache result that is missing the SOA I see this behavior in 18.04 and 22.04 First query to dnsmasq can be cached: dig @10.0.1.21 a.google.com ; <<>> DiG 9.16.1-Ubuntu <<>> @10.0.1.21 a.google.com ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 3107 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 512 ;; QUESTION SECTION: ;a.google.com. IN A ;; AUTHORITY SECTION: google.com. 60 IN SOA ns1.google.com. dns-admin.google.com. 449437361 900 900 1800 60 ;; Query time: 15 msec ;; SERVER: 10.0.1.21#53(10.0.1.21) ;; WHEN: Thu May 19 15:00:12 EDT 2022 ;; MSG SIZE rcvd: 91 Cached response from dnsmasq cannot be cached: dig @10.0.1.21 a.google.com ; <<>> DiG 9.16.1-Ubuntu <<>> @10.0.1.21 a.google.com ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 61408 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;a.google.com. IN A ;; Query time: 0 msec ;; SERVER: 10.0.1.21#53(10.0.1.21) ;; WHEN: Thu May 19 15:00:13 EDT 2022 ;; MSG SIZE rcvd: 41 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1974230/+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 1805178] Re: Apparmor should include letsencrypt directory for Slapd
Andreas fixed that in 2.4.49+dfsg-2ubuntu1 [Focal] which started to have profile in openldap and include ssl_cert which (as Christian Bolz outlined above) do include those paths. # grep ssl_c /etc/apparmor.d/usr.sbin.slapd #include # grep enc /etc/apparmor.d/abstractions/ssl_certs /etc/letsencrypt/archive/*/cert*.pem r, /etc/letsencrypt/archive/*/chain*.pem r, /etc/letsencrypt/archive/*/fullchain*.pem r, Fixed Focal onwads, and since users can modify the local overrides if needed I'm not sure how important an SRU of the same is (changing isolation in SRUs is discouraged AFAIK). ** Changed in: openldap (Ubuntu) Status: Triaged => Fix Released -- 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/1805178 Title: Apparmor should include letsencrypt directory for Slapd Status in openldap package in Ubuntu: Fix Released Bug description: Apparmor denies access to /etc/letsencrypt for slapd, which is confusing for users trying to secure ldap with Letsencrypt in a stock configuration. The fix is inserting the following line in /etc/apparmor.d/usr.sbin.slapd: /etc/letsencrypt/** r, and then refreshing the profile: # apparmor_parser -vr usr.sbin.slapd This line should simply be included. tarek : ) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1805178/+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 1802483] Re: Notifications emitted by a snap with local files or desktop files use wrong namespace
Apart from that the Bionic upload looks fine. I note that notification- Handle-snap-applications.patch is added over the SRU for Focal, but that makes sense as that functionality is required for the other patches. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnotify in Ubuntu. https://bugs.launchpad.net/bugs/1802483 Title: Notifications emitted by a snap with local files or desktop files use wrong namespace Status in libnotify package in Ubuntu: Fix Released Status in libnotify source package in Bionic: In Progress Status in libnotify source package in Focal: Fix Committed Status in libnotify source package in Jammy: Fix Committed Bug description: As can be tested using this example snap: - https://github.com/3v1n0/notify-send-test-snap Basically the icons are referenced using absolute paths in snap environment, while they should be readapted so that they depend on $SNAP location. As we do with appindicators and libunity emblems. [ Impact ] Icons sonuds and desktop files referenced by a snapped app using notifications aren't exposed to the desktop in absolute paths [ Test case ] Build the test snap (or install it from the attached files to this bug): git clone https://github.com/3v1n0/notify-send-test-snap snapcraft prime snap try prime To use the pre-built snap (https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1802483/comments/7) snap install --dangerous notify-send-test-snap_*.snap Check that icons are shown when launching: notify-send-test-snap notify-send-test-snap.image-path notify-send-test-snap.image-uri Ensure that desktop entry is correctly sent, monitoring the dbus session: In a terminal: dbus-monitor --session --monitor "interface='org.freedesktop.Notifications'" In the other: notify-send-test-snap.desktop-entry notify-send-test-snap.desktop-entry-explicit-id notify-send-test-snap.desktop-entry-explicit-file-name notify-send-test-snap.desktop-entry-explicit-path notify-send-test-snap.desktop-entry-explicit-uri notify-send-test-snap.desktop-entry-explicit-snapped-uri The `desktop-entry` value sent to dbus should be either: - A `notify-send-test-snap_`-prefixed desktop ID - A .desktop file path (readable from both inside and outside the snap) - A .desktop file uri (readable from both inside and outside the snap) [ Regression potential ] Normal applications that are run with a SNAP environment variable set, might use wrong paths for files or desktop file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1802483/+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 1802483] Re: Notifications emitted by a snap with local files or desktop files use wrong namespace
Yeah... A missing fixup on a cherry-pick... Maybe we should re-upload this? Would that be accepted? I guess should be changed to 1.18.04.1 or what? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnotify in Ubuntu. https://bugs.launchpad.net/bugs/1802483 Title: Notifications emitted by a snap with local files or desktop files use wrong namespace Status in libnotify package in Ubuntu: Fix Released Status in libnotify source package in Bionic: In Progress Status in libnotify source package in Focal: Fix Committed Status in libnotify source package in Jammy: Fix Committed Bug description: As can be tested using this example snap: - https://github.com/3v1n0/notify-send-test-snap Basically the icons are referenced using absolute paths in snap environment, while they should be readapted so that they depend on $SNAP location. As we do with appindicators and libunity emblems. [ Impact ] Icons sonuds and desktop files referenced by a snapped app using notifications aren't exposed to the desktop in absolute paths [ Test case ] Build the test snap (or install it from the attached files to this bug): git clone https://github.com/3v1n0/notify-send-test-snap snapcraft prime snap try prime To use the pre-built snap (https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1802483/comments/7) snap install --dangerous notify-send-test-snap_*.snap Check that icons are shown when launching: notify-send-test-snap notify-send-test-snap.image-path notify-send-test-snap.image-uri Ensure that desktop entry is correctly sent, monitoring the dbus session: In a terminal: dbus-monitor --session --monitor "interface='org.freedesktop.Notifications'" In the other: notify-send-test-snap.desktop-entry notify-send-test-snap.desktop-entry-explicit-id notify-send-test-snap.desktop-entry-explicit-file-name notify-send-test-snap.desktop-entry-explicit-path notify-send-test-snap.desktop-entry-explicit-uri notify-send-test-snap.desktop-entry-explicit-snapped-uri The `desktop-entry` value sent to dbus should be either: - A `notify-send-test-snap_`-prefixed desktop ID - A .desktop file path (readable from both inside and outside the snap) - A .desktop file uri (readable from both inside and outside the snap) [ Regression potential ] Normal applications that are run with a SNAP environment variable set, might use wrong paths for files or desktop file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1802483/+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 1802483] Re: Notifications emitted by a snap with local files or desktop files use wrong namespace
+libnotify (0.7.7-3ubuntu0.20.04.1) bionic; urgency=medium Shouldn't this be ...0.18.04.1? The version number used will work, but is confusing. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnotify in Ubuntu. https://bugs.launchpad.net/bugs/1802483 Title: Notifications emitted by a snap with local files or desktop files use wrong namespace Status in libnotify package in Ubuntu: Fix Released Status in libnotify source package in Bionic: In Progress Status in libnotify source package in Focal: Fix Committed Status in libnotify source package in Jammy: Fix Committed Bug description: As can be tested using this example snap: - https://github.com/3v1n0/notify-send-test-snap Basically the icons are referenced using absolute paths in snap environment, while they should be readapted so that they depend on $SNAP location. As we do with appindicators and libunity emblems. [ Impact ] Icons sonuds and desktop files referenced by a snapped app using notifications aren't exposed to the desktop in absolute paths [ Test case ] Build the test snap (or install it from the attached files to this bug): git clone https://github.com/3v1n0/notify-send-test-snap snapcraft prime snap try prime To use the pre-built snap (https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1802483/comments/7) snap install --dangerous notify-send-test-snap_*.snap Check that icons are shown when launching: notify-send-test-snap notify-send-test-snap.image-path notify-send-test-snap.image-uri Ensure that desktop entry is correctly sent, monitoring the dbus session: In a terminal: dbus-monitor --session --monitor "interface='org.freedesktop.Notifications'" In the other: notify-send-test-snap.desktop-entry notify-send-test-snap.desktop-entry-explicit-id notify-send-test-snap.desktop-entry-explicit-file-name notify-send-test-snap.desktop-entry-explicit-path notify-send-test-snap.desktop-entry-explicit-uri notify-send-test-snap.desktop-entry-explicit-snapped-uri The `desktop-entry` value sent to dbus should be either: - A `notify-send-test-snap_`-prefixed desktop ID - A .desktop file path (readable from both inside and outside the snap) - A .desktop file uri (readable from both inside and outside the snap) [ Regression potential ] Normal applications that are run with a SNAP environment variable set, might use wrong paths for files or desktop file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1802483/+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 1947588] Re: Infinite Loop in OpenSSL s_server
** Merge proposal linked: https://code.launchpad.net/~schopin/ubuntu/+source/openssl/+git/openssl/+merge/423153 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1947588 Title: Infinite Loop in OpenSSL s_server Status in openssl package in Ubuntu: Confirmed Status in openssl source package in Focal: Confirmed Status in openssl source package in Impish: Confirmed Status in openssl source package in Jammy: Confirmed Bug description: Launching openssl s_server as follows: $ openssl s_server -nocert -psk 01020304 -dtls1 And using openssl s_client to connect to it like this: $ openssl s_client -dtls1 -psk 01020304 Results in s_server entering an infinite loop: Using default temp DH parameters ACCEPT ERROR 140247926990208:error:141FC044:SSL routines:tls_setup_handshake:internal error:../ssl/statem/statem_lib.c:109: ERROR 140247926990208:error:141FC044:SSL routines:tls_setup_handshake:internal error:../ssl/statem/statem_lib.c:109: ERROR ...and so on... I have confirmed that upstream OpenSSL does not have this issue in a default build of 1.1.1j or 1.1.1k. Upstream 1.1.1l has a different bug with these commands (https://github.com/openssl/openssl/issues/16707) and it was while working on the fix for that issue (https://github.com/openssl/openssl/pull/16838) that I noticed this problem in the Ubuntu packages. $ lsb_release -rd Description: Ubuntu 21.04 Release: 21.04 $ apt-cache policy openssl openssl: Installed: 1.1.1j-1ubuntu3.5 Candidate: 1.1.1j-1ubuntu3.5 Version table: *** 1.1.1j-1ubuntu3.5 500 500 http://gb.archive.ubuntu.com/ubuntu hirsute-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu hirsute-security/main amd64 Packages 100 /var/lib/dpkg/status 1.1.1j-1ubuntu3 500 500 http://gb.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages $ openssl version -a OpenSSL 1.1.1j 16 Feb 2021 built on: Mon Aug 23 17:02:39 2021 UTC platform: debian-amd64 options: bn(64,64) rc4(16x,int) des(int) blowfish(ptr) compiler: gcc -fPIC -pthread -m64 -Wa,--noexecstack -Wall -Wa,--noexecstack -g -O2 -ffile-prefix-map=/build/openssl-5U8yxE/openssl-1.1.1j=. -flto=auto -ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format-security -DOPENSSL_TLS_SECURITY_LEVEL=2 -DOPENSSL_USE_NODELETE -DL_ENDIAN -DOPENSSL_PIC -DOPENSSL_CPUID_OBJ -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DKECCAK1600_ASM -DRC4_ASM -DMD5_ASM -DAESNI_ASM -DVPAES_ASM -DGHASH_ASM -DECP_NISTZ256_ASM -DX25519_ASM -DPOLY1305_ASM -DNDEBUG -Wdate-time -D_FORTIFY_SOURCE=2 OPENSSLDIR: "/usr/lib/ssl" ENGINESDIR: "/usr/lib/x86_64-linux-gnu/engines-1.1" Seeding source: os-specific To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1947588/+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 1972056] Re: [openssl3] please sync openssl.cnf to ease changing security level
** Merge proposal linked: https://code.launchpad.net/~schopin/ubuntu/+source/openssl/+git/openssl/+merge/423153 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1972056 Title: [openssl3] please sync openssl.cnf to ease changing security level Status in openssl package in Ubuntu: Confirmed Status in openssl source package in Jammy: Confirmed Status in openssl source package in Kinetic: Confirmed Status in openssl package in Debian: Fix Released Bug description: openssl.cnf as provided misses some directive, which make it a bit difficult to change security level, which since openssl 3 disables SHA1 signatures. See also this Debian bug https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=1010360 and the committed fix: https://salsa.debian.org/debian/openssl/-/commit/b507914c40270e32cde6afcc8af93707c225e7f4 Can you please sync this change in Ubuntu openssl? This way one should just add a single directive to change the security level. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1972056/+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 1588915] Re: ifup does not block for interface to be up with static addresses
** Tags added: network-online-ordering -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1588915 Title: ifup does not block for interface to be up with static addresses Status in ifupdown package in Ubuntu: Confirmed Bug description: Description:Ubuntu 16.04 LTS (server) Release:16.04 systemd: Installed: 229-4ubuntu6 Candidate: 229-4ubuntu6 Version table: *** 229-4ubuntu6 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 229-4ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages This issue is more about systemd integration then an issue with systemd package itself. The general problem is the distinction between the network being configured and the network being up and what that means for services that depend on the network. upstream systemd has network.target (network is configured) and network-online.target (network is up), however xenial server (dunno about desktop) doesn't seem to use network-online.target. The result of which is, as soon as the network is configured both network.target and network-online.target are considered complete. At which point services dependent on either of those will get started. However this can lead to problems if the services in question are actually dependent on the network (ie dns lookups) when they are starting up. Here's an example of what I mean. If you install openntpd and add the -s option there is a race on boot if it will or wont be able to do the initial sync. Jun 02 16:58:02 xenial64 systemd[1]: Reached target Network. Jun 02 16:58:02 xenial64 systemd[1]: Starting OpenNTPd Network Time Protocol... Jun 02 16:58:02 xenial64 systemd[1]: Reached target Network is Online. Jun 02 16:58:02 xenial64 ntpd[920]: constraint certificate verification turned off Jun 02 16:58:02 xenial64 ntpd[928]: ntp engine ready Jun 02 16:58:02 xenial64 kernel: tg3 :02:00.0 enp2s0: Link is down Jun 02 16:58:05 xenial64 kernel: tg3 :02:00.0 enp2s0: Link is up at 1000 Mbps, full duplex Jun 02 16:58:05 xenial64 kernel: tg3 :02:00.0 enp2s0: Flow control is on for TX and on for RX Jun 02 16:58:05 xenial64 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enp2s0: link becomes ready Jun 02 16:58:17 xenial64 ntpd[920]: no reply received in time, skipping initial time setting openntpd was started 3 seconds before the interface even got link. I believe this issue is only going to effect physical servers with static ips. vm's interfaces will instantly have link when they are brought up and dhcp, the interface will already be up or else they wouldn't have been able to get an ip. thanks jim To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1588915/+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 1652269] Re: udev script shortcuts ifup-scripts
We are - as always - trying to clean and recheck old bugs. This - sadly - clearly is one of them. The situation is still correct, but with the full switch to networkd and netplan as well as the demotion of ifupdown in later versions of Ubuntu this has become even less important. And it didn#t even find enough importance/attendence before :-/ I'm retagging this as a Xenial/Bionic issue, because later releases would just work totally different anyway. ** Also affects: bridge-utils (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: bridge-utils (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: bridge-utils (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: bridge-utils (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: bridge-utils (Ubuntu Focal) Status: New => Invalid ** Changed in: bridge-utils (Ubuntu Jammy) Status: New => Invalid ** Changed in: bridge-utils (Ubuntu Bionic) Status: New => Confirmed ** Changed in: bridge-utils (Ubuntu Xenial) Status: New => Confirmed ** Changed in: bridge-utils (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bridge-utils in Ubuntu. https://bugs.launchpad.net/bugs/1652269 Title: udev script shortcuts ifup-scripts Status in bridge-utils package in Ubuntu: Invalid Status in bridge-utils source package in Xenial: Confirmed Status in bridge-utils source package in Bionic: Confirmed Status in bridge-utils source package in Focal: Invalid Status in bridge-utils source package in Jammy: Invalid Bug description: Hi, I just ran into a problem. I've configured a bridge as a virtual lan (for lxc, lxd, and these things), but also configured an USB Ethernet dongle to be part of the bridge. If the dongle is present at boot time or if the dongle is put in while the bridge is down, then /lib/udev/bridge-network-interface tries to take the bridge up. Nice. But it does not call ifup, instead it directly calls IFACE=$port /etc/network/if-pre-up.d/vlan This ifup is not aware that the interface is up and still thinks it would be down, and all the other settings (up/down-scripts ...) are not executed. Breaks functionality (and can be a security problem, since firewall settings my be skipped.) ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: bridge-utils 1.5-9ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11 Uname: Linux 4.8.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Dec 23 11:31:43 2016 Dependencies: gcc-6-base 6.2.0-5ubuntu12 libc6 2.24-3ubuntu2 libgcc1 1:6.2.0-5ubuntu12 InstallationDate: Installed on 2016-04-22 (244 days ago) InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420) SourcePackage: bridge-utils UpgradeStatus: Upgraded to yakkety on 2016-10-17 (67 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bridge-utils/+bug/1652269/+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 1975578] Re: NetworkManager does not push search domains to systemd-resolved
** Description changed: Search domains defined in a NetworkManager connection are not pushed to systemd-resolved. DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu 22.04 LTS" PRETTY_NAME="Ubuntu 22.04 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04 LTS (Jammy Jellyfish)" VERSION_CODENAME=jammy ID=ubuntu ID_LIKE=debian UBUNTU_CODENAME=jammy + NetworkManager -V + 1.36.4 + Details: DNS search domains can be set per NetworkManager connection. In my case it looks like this: nmcli con show MyConnection | grep ipv4.dns-search ipv4.dns-search: mydomain.at,org.mydomain.at,linux.mydomain.at Afaik NetworkManager should push them to systemd-resolved automatically. But this does not happen. The entries do not make it to /etc/resolv.conf. (If I do it manually with resolvectl, it works.) ** Description changed: Search domains defined in a NetworkManager connection are not pushed to systemd-resolved. DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu 22.04 LTS" PRETTY_NAME="Ubuntu 22.04 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04 LTS (Jammy Jellyfish)" VERSION_CODENAME=jammy ID=ubuntu ID_LIKE=debian UBUNTU_CODENAME=jammy NetworkManager -V 1.36.4 + resolvectl --version + systemd 249 (249.11-0ubuntu3.1) + +PAM +AUDIT +SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT +GNUTLS -OPENSSL +ACL +BLKID +CURL +ELFUTILS -FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP -LIBFDISK +PCRE2 -PWQUALITY -P11KIT -QRENCODE +BZIP2 +LZ4 +XZ +ZLIB +ZSTD -XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified + Details: DNS search domains can be set per NetworkManager connection. In my case it looks like this: nmcli con show MyConnection | grep ipv4.dns-search ipv4.dns-search: mydomain.at,org.mydomain.at,linux.mydomain.at Afaik NetworkManager should push them to systemd-resolved automatically. But this does not happen. The entries do not make it to /etc/resolv.conf. (If I do it manually with resolvectl, it works.) -- 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/1975578 Title: NetworkManager does not push search domains to systemd-resolved Status in network-manager package in Ubuntu: Incomplete Bug description: Search domains defined in a NetworkManager connection are not pushed to systemd-resolved. DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu 22.04 LTS" PRETTY_NAME="Ubuntu 22.04 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04 LTS (Jammy Jellyfish)" VERSION_CODENAME=jammy ID=ubuntu ID_LIKE=debian UBUNTU_CODENAME=jammy NetworkManager -V 1.36.4 resolvectl --version systemd 249 (249.11-0ubuntu3.1) +PAM +AUDIT +SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT +GNUTLS -OPENSSL +ACL +BLKID +CURL +ELFUTILS -FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP -LIBFDISK +PCRE2 -PWQUALITY -P11KIT -QRENCODE +BZIP2 +LZ4 +XZ +ZLIB +ZSTD -XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified Details: DNS search domains can be set per NetworkManager connection. In my case it looks like this: nmcli con show MyConnection | grep ipv4.dns-search ipv4.dns-search: mydomain.at,org.mydomain.at,linux.mydomain.at Afaik NetworkManager should push them to systemd-resolved automatically. But this does not happen. The entries do not make it to /etc/resolv.conf. (If I do it manually with resolvectl, it works.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1975578/+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 1975578] Re: NetworkManager does not push search domains to systemd-resolved
** Description changed: Search domains defined in a NetworkManager connection are not pushed to systemd-resolved. + + DISTRIB_ID=Ubuntu + DISTRIB_RELEASE=22.04 + DISTRIB_CODENAME=jammy + DISTRIB_DESCRIPTION="Ubuntu 22.04 LTS" + PRETTY_NAME="Ubuntu 22.04 LTS" + NAME="Ubuntu" + VERSION_ID="22.04" + VERSION="22.04 LTS (Jammy Jellyfish)" + VERSION_CODENAME=jammy + ID=ubuntu + ID_LIKE=debian + UBUNTU_CODENAME=jammy ** Description changed: Search domains defined in a NetworkManager connection are not pushed to systemd-resolved. DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu 22.04 LTS" PRETTY_NAME="Ubuntu 22.04 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04 LTS (Jammy Jellyfish)" VERSION_CODENAME=jammy ID=ubuntu ID_LIKE=debian UBUNTU_CODENAME=jammy + + Details: + DNS search domains can be set per NetworkManager connection. In my case it looks like this: + + nmcli con show MyConnection | grep ipv4.dns-search + ipv4.dns-search: mydomain.at,org.mydomain.at,linux.mydomain.at + + Afaik NetworkManager should push them to systemd-resolved automatically. + But this does not happen. The entries do not make it to + /etc/resolv.conf. + + (If I do it manually with resolvectl, it works.) -- 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/1975578 Title: NetworkManager does not push search domains to systemd-resolved Status in network-manager package in Ubuntu: Incomplete Bug description: Search domains defined in a NetworkManager connection are not pushed to systemd-resolved. DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu 22.04 LTS" PRETTY_NAME="Ubuntu 22.04 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04 LTS (Jammy Jellyfish)" VERSION_CODENAME=jammy ID=ubuntu ID_LIKE=debian UBUNTU_CODENAME=jammy Details: DNS search domains can be set per NetworkManager connection. In my case it looks like this: nmcli con show MyConnection | grep ipv4.dns-search ipv4.dns-search: mydomain.at,org.mydomain.at,linux.mydomain.at Afaik NetworkManager should push them to systemd-resolved automatically. But this does not happen. The entries do not make it to /etc/resolv.conf. (If I do it manually with resolvectl, it works.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1975578/+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 1871148] Re: services start before apparmor profiles are loaded
Oh, this is interesting! Then, Etienne, my suggestion is the following: re-enable the snapd.apparmor service, and if that (as I expect) fixes the bug, let's stop discussing this issue here, and instead open a separate issue about the service being disabled. It may be that something went wrong during the upgrade to Jammy. If we file this as a separate bug, we might be able to see if other people have met the same issue. -- 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/1871148 Title: services start before apparmor profiles are loaded Status in AppArmor: Invalid Status in snapd: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in snapd package in Ubuntu: Fix Released Status in zsys package in Ubuntu: Invalid Status in apparmor source package in Focal: Fix Released Status in snapd source package in Focal: Fix Released Status in zsys source package in Focal: Invalid Bug description: Per discussion with Zyga in #snapd on Freenode, I have hit a race condition where services are being started by the system before apparmor has been started. I have a complete log of my system showing the effect somewhere within at https://paste.ubuntu.com/p/Jyx6gfFc3q/. Restarting apparmor using `sudo systemctl restart apparmor` is enough to bring installed snaps back to full functionality. Previously, when running any snap I would receive the following in the terminal: --- cannot change profile for the next exec call: No such file or directory snap-update-ns failed with code 1: File exists --- Updated to add for Jamie: $ snap version snap2.44.2+20.04 snapd 2.44.2+20.04 series 16 ubuntu 20.04 kernel 5.4.0-21-generic To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1871148/+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 1975566] Re: radeon / amdgpu bad performance or panics
Before the upgrade it was an Intel GPU. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1975566 Title: radeon / amdgpu bad performance or panics Status in mesa package in Ubuntu: Incomplete Bug description: Recently I upgraded my machine and moved my GPU over from the old (Intel something) to the new machine (AMD Ryzen 7 5700X, B550 motherboard). I did a fresh Ubuntu install (server) and added packages to get my GUI rolling (lightdm + awesomewm), just like before. The graphics cards is a "Gigabyte GV-R928XOC-3GD Rev. 2.0" which has the R9 280X chip (TAHITI / Southern Islands). On my old system, I could play games with Vulkan, but with this system it doesn't work. If I run the 'default' setup, it uses the 'radeon' kernel module. The first couple of seconds I get reasonable performance (glxgears @ 60 FPS), then it suddenly drop to 4 and motion is almost not visible). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg (not installed) Uname: Linux 5.18.0-051800-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue May 24 06:49:56 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Tahiti XT [Radeon HD 7970/8970 OEM / R9 280X] [1002:6798] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Tahiti XTL [Radeon R9 280X OC] [1458:3001] InstallationDate: Installed on 2022-05-14 (9 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.18.0-051800-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P2.30 dmi.board.name: B550 Phantom Gaming-ITX/ax dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP2.30:bd02/25/2022:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB550PhantomGaming-ITX/ax:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 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/mesa/+bug/1975566/+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 1871148] Re: services start before apparmor profiles are loaded
$ systemctl status snapd.apparmor ○ snapd.apparmor.service - Load AppArmor profiles managed internally by snapd Loaded: loaded (/lib/systemd/system/snapd.apparmor.service; disabled; vendor preset: enabled) Active: inactive (dead) I do NOT remember having manually disabled this service. -- 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/1871148 Title: services start before apparmor profiles are loaded Status in AppArmor: Invalid Status in snapd: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in snapd package in Ubuntu: Fix Released Status in zsys package in Ubuntu: Invalid Status in apparmor source package in Focal: Fix Released Status in snapd source package in Focal: Fix Released Status in zsys source package in Focal: Invalid Bug description: Per discussion with Zyga in #snapd on Freenode, I have hit a race condition where services are being started by the system before apparmor has been started. I have a complete log of my system showing the effect somewhere within at https://paste.ubuntu.com/p/Jyx6gfFc3q/. Restarting apparmor using `sudo systemctl restart apparmor` is enough to bring installed snaps back to full functionality. Previously, when running any snap I would receive the following in the terminal: --- cannot change profile for the next exec call: No such file or directory snap-update-ns failed with code 1: File exists --- Updated to add for Jamie: $ snap version snap2.44.2+20.04 snapd 2.44.2+20.04 series 16 ubuntu 20.04 kernel 5.4.0-21-generic To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1871148/+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 1974056] Re: iptables-1.8.7/iptables/tests/shell/testcases/nft-only/0009-needless-bitwise_0 fails on s390x
--- Comment From boris.m...@de.ibm.com 2022-05-25 04:39 EDT--- Description by Canonical (LP#1974056): command17 FAIL stderr: W: [FAILED] ././testcases/nft-only/0009-needless- bitwise_0: expected 0 but got 1 this can be reproduced with: pull-lp-source iptables cd iptables-1.8.7/ chmod +x ./iptables/tests/shell/testcases/iptables/0007-zero-counters_0 cd iptables/tests/shell sudo ./run-tests.sh --host ** Tags added: architecture-s39064 bugnameltc-198367 severity-high targetmilestone-inin2204 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1974056 Title: iptables-1.8.7/iptables/tests/shell/testcases/nft-only/0009-needless- bitwise_0 fails on s390x Status in iptables: Unknown Status in Ubuntu on IBM z Systems: New Status in iptables package in Ubuntu: New Bug description: In Ubuntu, we execute the full iptables shell testcases across all architectures. They seem to all pass everywhere, however iptables-1.8.7/iptables/tests/shell/testcases/nft-only/0009-needless- bitwise_0 is currently failing on s390x like so: command17FAIL stderr: W: [FAILED] ././testcases/nft- only/0009-needless-bitwise_0: expected 0 but got 1 i wonder if there is some endian bug, as this is currently Ubuntu's only big-endian architecture. this can be reproduced with: pull-lp-source iptables cd iptables-1.8.7/ chmod +x ./iptables/tests/shell/testcases/iptables/0007-zero-counters_0 cd iptables/tests/shell sudo ./run-tests.sh --host To manage notifications about this bug go to: https://bugs.launchpad.net/iptables/+bug/1974056/+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 1975566] Re: radeon / amdgpu bad performance or panics
aiui the radv vulkan driver requires amdgpu kernel driver, so I don't know how you could have it working before the upgrade. the default driver for SI cards is radeon, that won't change so essentially we don't support vulkan on those -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1975566 Title: radeon / amdgpu bad performance or panics Status in mesa package in Ubuntu: Incomplete Bug description: Recently I upgraded my machine and moved my GPU over from the old (Intel something) to the new machine (AMD Ryzen 7 5700X, B550 motherboard). I did a fresh Ubuntu install (server) and added packages to get my GUI rolling (lightdm + awesomewm), just like before. The graphics cards is a "Gigabyte GV-R928XOC-3GD Rev. 2.0" which has the R9 280X chip (TAHITI / Southern Islands). On my old system, I could play games with Vulkan, but with this system it doesn't work. If I run the 'default' setup, it uses the 'radeon' kernel module. The first couple of seconds I get reasonable performance (glxgears @ 60 FPS), then it suddenly drop to 4 and motion is almost not visible). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg (not installed) Uname: Linux 5.18.0-051800-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue May 24 06:49:56 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Tahiti XT [Radeon HD 7970/8970 OEM / R9 280X] [1002:6798] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Tahiti XTL [Radeon R9 280X OC] [1458:3001] InstallationDate: Installed on 2022-05-14 (9 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.18.0-051800-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P2.30 dmi.board.name: B550 Phantom Gaming-ITX/ax dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP2.30:bd02/25/2022:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB550PhantomGaming-ITX/ax:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 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/mesa/+bug/1975566/+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 1975673] Re: libgpg-error/1.45-2 fails autopkgtest on i386
I think there's another problem: it fails to install gcc-mingw-w64-i686 because autopkgtest tries to install gcc-mingw-w64-i686:i386 which does not exist since it only exists as gcc-mingw-w64-i686:all. I added :all to the test dependency, and then it works, the test passes correctly on i386 \o/ But I'll come up with the proper patch in autopkgtest: it should try :$arch first and then :all in case it does not work. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libgpg-error in Ubuntu. https://bugs.launchpad.net/bugs/1975673 Title: libgpg-error/1.45-2 fails autopkgtest on i386 Status in libgpg-error package in Ubuntu: New Bug description: The failure was introduced by this change in Debian: https://salsa.debian.org/debian/libgpg-error/-/commit/0c11fe4ae16c2800e13758ff1ee64c561354e628 It started to fail for i386 on autopkgtest.u.c: https://autopkgtest.ubuntu.com/packages/libgpg-error/kinetic/i386 https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic/kinetic/i386/libg/libgpg-error/20220523_114919_e3142@/log.gz The relevant log is this: ``` The following packages have unmet dependencies: builddeps:/tmp/autopkgtest.VMjBik/1-autopkgtest-satdep.dsc:i386 : Depends: gcc-mingw-w64-x86-64:i386 but it is not installable E: Unable to correct problems, you have held broken packages. win64 FAIL badpkg [...] autopkgtest [11:49:03]: summary win32 SKIP Test lists explicitly supported architectures, but the current architecture amd64 isn't listed. win64 FAIL badpkg blame: libgpg-error badpkg: Test dependencies are unsatisfiable. A common reason is that your testbed is out of date with respect to the archive, and you need to use a current testbed or run apt-get update or use -U. build PASS ``` As can be seen, the i386/win32 test is skipped while amd64/win64 is executed and fails with "badpkg" error due to not being able to install "gcc-mingw-w64-x86-64:i386". = Even if that can be fixed (https://code.launchpad.net/~ubuntu-release/autopkgtest/+git/development/+merge/423176), the "win64" test is skipped now and "win32" executed, "win32" fails with a "badpkg" error, which probably needs solving in the archive. $ PYTHONPATH=lib/ runner/autopkgtest libgpg-error --apt-pocket=proposed=src:libgpg-error -a i386 -U -- qemu /data/autopkgtest-kinetic-amd64.img [...] win64 SKIP Test lists explicitly supported architectures, but the current architecture i386 isn't listed. [...] The following packages have unmet dependencies: builddeps:/tmp/autopkgtest.8Maso6/1-autopkgtest-satdep.dsc:i386 : Depends: gcc-mingw-w64-i686:i386 but it is not installable Depends: wine32:i386 but it is not going to be installed E: Unable to correct problems, you have held broken packages. win32 FAIL badpkg blame: libgpg-error badpkg: Test dependencies are unsatisfiable. A common reason is that your testbed is out of date with respect to the archive, and you need to use a current testbed or run apt-get update or use -U. Full log: https://paste.ubuntu.com/p/JYHrJpMGbn/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgpg-error/+bug/1975673/+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 1975675] Re: GUI problem from {Online Accounts} Google Microsoft and {Ubuntu Desktop Guide}
*** This bug is a duplicate of bug 1924251 ***
https://bugs.launchpad.net/bugs/1924251
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1924251, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.
** Package changed: xorg (Ubuntu) => ubuntu
** This bug has been marked a duplicate of bug 1924251
Embedded browser display corruption under Wayland on Pi desktop
--
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/1975675
Title:
GUI problem from {Online Accounts} Google Microsoft and {Ubuntu
Desktop Guide}
Status in Ubuntu:
New
Bug description:
raspberry pi 4 (8GB memory, USB SSD boot) ubuntu 64 with 2 monitors
Description: Ubuntu 22.04 LTS
Release: 22.04
Seems like the GUI for {Online Accounts} Google Microsoft and {Ubuntu Desktop
Guide} can't render themselves correctly. Meanwhile, the Firefox can play
YouTube on 2 monitors without any problem.
Please refer to the attached snapshot.
apt-cache policy
Package files:
100 /var/lib/dpkg/status
release a=now
500 http://ports.ubuntu.com/ubuntu-ports jammy-security/universe arm64
Packages
release
v=22.04,o=Ubuntu,a=jammy-security,n=jammy,l=Ubuntu,c=universe,b=arm64
origin ports.ubuntu.com
500 http://ports.ubuntu.com/ubuntu-ports jammy-security/restricted arm64
Packages
release
v=22.04,o=Ubuntu,a=jammy-security,n=jammy,l=Ubuntu,c=restricted,b=arm64
origin ports.ubuntu.com
500 http://ports.ubuntu.com/ubuntu-ports jammy-security/main arm64 Packages
release v=22.04,o=Ubuntu,a=jammy-security,n=jammy,l=Ubuntu,c=main,b=arm64
origin ports.ubuntu.com
100 http://ports.ubuntu.com/ubuntu-ports jammy-backports/universe arm64
Packages
release
v=22.04,o=Ubuntu,a=jammy-backports,n=jammy,l=Ubuntu,c=universe,b=arm64
origin ports.ubuntu.com
500 http://ports.ubuntu.com/ubuntu-ports jammy-updates/universe arm64
Packages
release
v=22.04,o=Ubuntu,a=jammy-updates,n=jammy,l=Ubuntu,c=universe,b=arm64
origin ports.ubuntu.com
500 http://ports.ubuntu.com/ubuntu-ports jammy-updates/restricted arm64
Packages
release
v=22.04,o=Ubuntu,a=jammy-updates,n=jammy,l=Ubuntu,c=restricted,b=arm64
origin ports.ubuntu.com
500 http://ports.ubuntu.com/ubuntu-ports jammy-updates/main arm64 Packages
release v=22.04,o=Ubuntu,a=jammy-updates,n=jammy,l=Ubuntu,c=main,b=arm64
origin ports.ubuntu.com
500 http://ports.ubuntu.com/ubuntu-ports jammy/multiverse arm64 Packages
release v=22.04,o=Ubuntu,a=jammy,n=jammy,l=Ubuntu,c=multiverse,b=arm64
origin ports.ubuntu.com
500 http://ports.ubuntu.com/ubuntu-ports jammy/universe arm64 Packages
release v=22.04,o=Ubuntu,a=jammy,n=jammy,l=Ubuntu,c=universe,b=arm64
origin ports.ubuntu.com
500 http://ports.ubuntu.com/ubuntu-ports jammy/restricted arm64 Packages
release v=22.04,o=Ubuntu,a=jammy,n=jammy,l=Ubuntu,c=restricted,b=arm64
origin ports.ubuntu.com
500 http://ports.ubuntu.com/ubuntu-ports jammy/main arm64 Packages
release v=22.04,o=Ubuntu,a=jammy,n=jammy,l=Ubuntu,c=main,b=arm64
origin ports.ubuntu.com
Pinned packages:
librados2 -> 17.2.0-0ubuntu0.22.04.1 with priority 1
crimson-osd -> 17.2.0-0ubuntu0.22.04.1 with priority 1
ec2-instance-connect -> 1.1.14-0ubuntu1.1 with priority 1
python3-etcd3gw -> 0.2.5-1ubuntu1.22.04.1 with priority 1
budgie-control-center-data -> 1.0.1-2ubuntu2 with priority 1
xdg-desktop-portal-tests -> 1.14.3-0ubuntu2.22.04.1 with priority 1
budgie-desktop -> 10.6.1-1ubuntu1~22.04 with priority 1
python-etcd3gw-doc -> 0.2.5-1ubuntu1.22.04.1 with priority 1
ceph-volume -> 17.2.0-0ubuntu0.22.04.1 with priority 1
evolution-dev -> 3.44.1-0ubuntu1 with priority 1
libbudgietheme0 -> 10.6.1-1ubuntu1~22.04 with priority 1
rbd-fuse -> 17.2.0-0ubuntu0.22.04.1 with priority 1
ceph-mgr-modules-core -> 17.2.0-0ubuntu0.22.04.1 with priority 1
libgtk-4-common -> 4.6.3+ds1-0ubuntu1 with priority 1
ceph-grafana-dashboards -> 17.2.0-0ubuntu0.22.04.1 with priority 1
gir1.2-clutter-gst-3.0 -> 3.0.27-2ubuntu1 with priority 1
libgail-3-dev -> 3.24.33-1ubuntu2 with priority 1
libgail-3-doc -> 3.24.33-1ubuntu2 with priority 1
ceph-resource-agents -> 17.2.0-0ubuntu0.22.04.1 with priority 1
ceph-base -> 17.2.0-0ubuntu0.22.04.1 with priority 1
libsqlite3-mod-ceph-dev ->
[Touch-packages] [Bug 1975675] Re: GUI problem from {Online Accounts} Google Microsoft and {Ubuntu Desktop Guide}
*** This bug is a duplicate of bug 1924251 ***
https://bugs.launchpad.net/bugs/1924251
** 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/1975675
Title:
GUI problem from {Online Accounts} Google Microsoft and {Ubuntu
Desktop Guide}
Status in Ubuntu:
New
Bug description:
raspberry pi 4 (8GB memory, USB SSD boot) ubuntu 64 with 2 monitors
Description: Ubuntu 22.04 LTS
Release: 22.04
Seems like the GUI for {Online Accounts} Google Microsoft and {Ubuntu Desktop
Guide} can't render themselves correctly. Meanwhile, the Firefox can play
YouTube on 2 monitors without any problem.
Please refer to the attached snapshot.
apt-cache policy
Package files:
100 /var/lib/dpkg/status
release a=now
500 http://ports.ubuntu.com/ubuntu-ports jammy-security/universe arm64
Packages
release
v=22.04,o=Ubuntu,a=jammy-security,n=jammy,l=Ubuntu,c=universe,b=arm64
origin ports.ubuntu.com
500 http://ports.ubuntu.com/ubuntu-ports jammy-security/restricted arm64
Packages
release
v=22.04,o=Ubuntu,a=jammy-security,n=jammy,l=Ubuntu,c=restricted,b=arm64
origin ports.ubuntu.com
500 http://ports.ubuntu.com/ubuntu-ports jammy-security/main arm64 Packages
release v=22.04,o=Ubuntu,a=jammy-security,n=jammy,l=Ubuntu,c=main,b=arm64
origin ports.ubuntu.com
100 http://ports.ubuntu.com/ubuntu-ports jammy-backports/universe arm64
Packages
release
v=22.04,o=Ubuntu,a=jammy-backports,n=jammy,l=Ubuntu,c=universe,b=arm64
origin ports.ubuntu.com
500 http://ports.ubuntu.com/ubuntu-ports jammy-updates/universe arm64
Packages
release
v=22.04,o=Ubuntu,a=jammy-updates,n=jammy,l=Ubuntu,c=universe,b=arm64
origin ports.ubuntu.com
500 http://ports.ubuntu.com/ubuntu-ports jammy-updates/restricted arm64
Packages
release
v=22.04,o=Ubuntu,a=jammy-updates,n=jammy,l=Ubuntu,c=restricted,b=arm64
origin ports.ubuntu.com
500 http://ports.ubuntu.com/ubuntu-ports jammy-updates/main arm64 Packages
release v=22.04,o=Ubuntu,a=jammy-updates,n=jammy,l=Ubuntu,c=main,b=arm64
origin ports.ubuntu.com
500 http://ports.ubuntu.com/ubuntu-ports jammy/multiverse arm64 Packages
release v=22.04,o=Ubuntu,a=jammy,n=jammy,l=Ubuntu,c=multiverse,b=arm64
origin ports.ubuntu.com
500 http://ports.ubuntu.com/ubuntu-ports jammy/universe arm64 Packages
release v=22.04,o=Ubuntu,a=jammy,n=jammy,l=Ubuntu,c=universe,b=arm64
origin ports.ubuntu.com
500 http://ports.ubuntu.com/ubuntu-ports jammy/restricted arm64 Packages
release v=22.04,o=Ubuntu,a=jammy,n=jammy,l=Ubuntu,c=restricted,b=arm64
origin ports.ubuntu.com
500 http://ports.ubuntu.com/ubuntu-ports jammy/main arm64 Packages
release v=22.04,o=Ubuntu,a=jammy,n=jammy,l=Ubuntu,c=main,b=arm64
origin ports.ubuntu.com
Pinned packages:
librados2 -> 17.2.0-0ubuntu0.22.04.1 with priority 1
crimson-osd -> 17.2.0-0ubuntu0.22.04.1 with priority 1
ec2-instance-connect -> 1.1.14-0ubuntu1.1 with priority 1
python3-etcd3gw -> 0.2.5-1ubuntu1.22.04.1 with priority 1
budgie-control-center-data -> 1.0.1-2ubuntu2 with priority 1
xdg-desktop-portal-tests -> 1.14.3-0ubuntu2.22.04.1 with priority 1
budgie-desktop -> 10.6.1-1ubuntu1~22.04 with priority 1
python-etcd3gw-doc -> 0.2.5-1ubuntu1.22.04.1 with priority 1
ceph-volume -> 17.2.0-0ubuntu0.22.04.1 with priority 1
evolution-dev -> 3.44.1-0ubuntu1 with priority 1
libbudgietheme0 -> 10.6.1-1ubuntu1~22.04 with priority 1
rbd-fuse -> 17.2.0-0ubuntu0.22.04.1 with priority 1
ceph-mgr-modules-core -> 17.2.0-0ubuntu0.22.04.1 with priority 1
libgtk-4-common -> 4.6.3+ds1-0ubuntu1 with priority 1
ceph-grafana-dashboards -> 17.2.0-0ubuntu0.22.04.1 with priority 1
gir1.2-clutter-gst-3.0 -> 3.0.27-2ubuntu1 with priority 1
libgail-3-dev -> 3.24.33-1ubuntu2 with priority 1
libgail-3-doc -> 3.24.33-1ubuntu2 with priority 1
ceph-resource-agents -> 17.2.0-0ubuntu0.22.04.1 with priority 1
ceph-base -> 17.2.0-0ubuntu0.22.04.1 with priority 1
libsqlite3-mod-ceph-dev -> 17.2.0-0ubuntu0.22.04.1 with priority 1
libjson-c-dev -> 0.15-3~ubuntu1.22.04.1 with priority 1
libjson-c-doc -> 0.15-3~ubuntu1.22.04.1 with priority 1
xdg-desktop-portal-dev -> 1.14.3-0ubuntu2.22.04.1 with priority 1
gstreamer1.0-clutter-3.0 -> 3.0.27-2ubuntu1 with priority 1
python3-ceph-common -> 17.2.0-0ubuntu0.22.04.1 with priority 1
librbd1 -> 17.2.0-0ubuntu0.22.04.1 with priority 1
gir1.2-budgie-1.0 -> 10.6.1-1ubuntu1~22.04 with priority 1
libraven0 -> 10.6.1-1ubuntu1~22.04 with priority 1
librgw2 -> 17.2.0-0ubuntu0.22.04.1 with priority 1
libusb-1.0-0-dev
[Touch-packages] [Bug 1975675] [NEW] GUI problem from {Online Accounts} Google Microsoft and {Ubuntu Desktop Guide}
You have been subscribed to a public bug:
raspberry pi 4 (8GB memory, USB SSD boot) ubuntu 64 with 2 monitors
Description:Ubuntu 22.04 LTS
Release:22.04
Seems like the GUI for {Online Accounts} Google Microsoft and {Ubuntu Desktop
Guide} can't render themselves correctly. Meanwhile, the Firefox can play
YouTube on 2 monitors without any problem.
Please refer to the attached snapshot.
apt-cache policy
Package files:
100 /var/lib/dpkg/status
release a=now
500 http://ports.ubuntu.com/ubuntu-ports jammy-security/universe arm64 Packages
release
v=22.04,o=Ubuntu,a=jammy-security,n=jammy,l=Ubuntu,c=universe,b=arm64
origin ports.ubuntu.com
500 http://ports.ubuntu.com/ubuntu-ports jammy-security/restricted arm64
Packages
release
v=22.04,o=Ubuntu,a=jammy-security,n=jammy,l=Ubuntu,c=restricted,b=arm64
origin ports.ubuntu.com
500 http://ports.ubuntu.com/ubuntu-ports jammy-security/main arm64 Packages
release v=22.04,o=Ubuntu,a=jammy-security,n=jammy,l=Ubuntu,c=main,b=arm64
origin ports.ubuntu.com
100 http://ports.ubuntu.com/ubuntu-ports jammy-backports/universe arm64
Packages
release
v=22.04,o=Ubuntu,a=jammy-backports,n=jammy,l=Ubuntu,c=universe,b=arm64
origin ports.ubuntu.com
500 http://ports.ubuntu.com/ubuntu-ports jammy-updates/universe arm64 Packages
release
v=22.04,o=Ubuntu,a=jammy-updates,n=jammy,l=Ubuntu,c=universe,b=arm64
origin ports.ubuntu.com
500 http://ports.ubuntu.com/ubuntu-ports jammy-updates/restricted arm64
Packages
release
v=22.04,o=Ubuntu,a=jammy-updates,n=jammy,l=Ubuntu,c=restricted,b=arm64
origin ports.ubuntu.com
500 http://ports.ubuntu.com/ubuntu-ports jammy-updates/main arm64 Packages
release v=22.04,o=Ubuntu,a=jammy-updates,n=jammy,l=Ubuntu,c=main,b=arm64
origin ports.ubuntu.com
500 http://ports.ubuntu.com/ubuntu-ports jammy/multiverse arm64 Packages
release v=22.04,o=Ubuntu,a=jammy,n=jammy,l=Ubuntu,c=multiverse,b=arm64
origin ports.ubuntu.com
500 http://ports.ubuntu.com/ubuntu-ports jammy/universe arm64 Packages
release v=22.04,o=Ubuntu,a=jammy,n=jammy,l=Ubuntu,c=universe,b=arm64
origin ports.ubuntu.com
500 http://ports.ubuntu.com/ubuntu-ports jammy/restricted arm64 Packages
release v=22.04,o=Ubuntu,a=jammy,n=jammy,l=Ubuntu,c=restricted,b=arm64
origin ports.ubuntu.com
500 http://ports.ubuntu.com/ubuntu-ports jammy/main arm64 Packages
release v=22.04,o=Ubuntu,a=jammy,n=jammy,l=Ubuntu,c=main,b=arm64
origin ports.ubuntu.com
Pinned packages:
librados2 -> 17.2.0-0ubuntu0.22.04.1 with priority 1
crimson-osd -> 17.2.0-0ubuntu0.22.04.1 with priority 1
ec2-instance-connect -> 1.1.14-0ubuntu1.1 with priority 1
python3-etcd3gw -> 0.2.5-1ubuntu1.22.04.1 with priority 1
budgie-control-center-data -> 1.0.1-2ubuntu2 with priority 1
xdg-desktop-portal-tests -> 1.14.3-0ubuntu2.22.04.1 with priority 1
budgie-desktop -> 10.6.1-1ubuntu1~22.04 with priority 1
python-etcd3gw-doc -> 0.2.5-1ubuntu1.22.04.1 with priority 1
ceph-volume -> 17.2.0-0ubuntu0.22.04.1 with priority 1
evolution-dev -> 3.44.1-0ubuntu1 with priority 1
libbudgietheme0 -> 10.6.1-1ubuntu1~22.04 with priority 1
rbd-fuse -> 17.2.0-0ubuntu0.22.04.1 with priority 1
ceph-mgr-modules-core -> 17.2.0-0ubuntu0.22.04.1 with priority 1
libgtk-4-common -> 4.6.3+ds1-0ubuntu1 with priority 1
ceph-grafana-dashboards -> 17.2.0-0ubuntu0.22.04.1 with priority 1
gir1.2-clutter-gst-3.0 -> 3.0.27-2ubuntu1 with priority 1
libgail-3-dev -> 3.24.33-1ubuntu2 with priority 1
libgail-3-doc -> 3.24.33-1ubuntu2 with priority 1
ceph-resource-agents -> 17.2.0-0ubuntu0.22.04.1 with priority 1
ceph-base -> 17.2.0-0ubuntu0.22.04.1 with priority 1
libsqlite3-mod-ceph-dev -> 17.2.0-0ubuntu0.22.04.1 with priority 1
libjson-c-dev -> 0.15-3~ubuntu1.22.04.1 with priority 1
libjson-c-doc -> 0.15-3~ubuntu1.22.04.1 with priority 1
xdg-desktop-portal-dev -> 1.14.3-0ubuntu2.22.04.1 with priority 1
gstreamer1.0-clutter-3.0 -> 3.0.27-2ubuntu1 with priority 1
python3-ceph-common -> 17.2.0-0ubuntu0.22.04.1 with priority 1
librbd1 -> 17.2.0-0ubuntu0.22.04.1 with priority 1
gir1.2-budgie-1.0 -> 10.6.1-1ubuntu1~22.04 with priority 1
libraven0 -> 10.6.1-1ubuntu1~22.04 with priority 1
librgw2 -> 17.2.0-0ubuntu0.22.04.1 with priority 1
libusb-1.0-0-dev -> 2:1.0.25-1ubuntu2 with priority 1
libclutter-gst-3.0-dev -> 3.0.27-2ubuntu1 with priority 1
libclutter-gst-3.0-doc -> 3.0.27-2ubuntu1 with priority 1
ceph-mgr-cephadm -> 17.2.0-0ubuntu0.22.04.1 with priority 1
libcephfs-dev -> 17.2.0-0ubuntu0.22.04.1 with priority 1
budgie-control-center -> 1.0.1-2ubuntu2 with priority 1
ceph-common -> 17.2.0-0ubuntu0.22.04.1 with priority 1
libusb-1.0-doc -> 2:1.0.25-1ubuntu2 with priority 1
libcephfs-jni -> 17.2.0-0ubuntu0.22.04.1 with priority 1
evolution-plugins
[Touch-packages] [Bug 1965439] Re: software-properties-qt can no longer launch when called by kdesu
** No longer affects: software-properties (Ubuntu) ** No longer affects: software-properties (Ubuntu Impish) ** No longer affects: software-properties (Ubuntu Jammy) ** No longer affects: policykit-1 (Ubuntu Impish) ** No longer affects: policykit-1 (Ubuntu Jammy) ** No longer affects: policykit-1 (Ubuntu) ** Summary changed: - software-properties-qt can no longer launch when called by kdesu + applications can no longer launch when called by kdesu ** Also affects: ubuntustudio-default-settings via https://bugs.kde.org/show_bug.cgi?id=452532 Importance: Unknown Status: Unknown ** No longer affects: ubuntustudio-default-settings ** No longer affects: ubuntustudio-default-settings (Ubuntu Impish) ** No longer affects: sudo (Ubuntu Impish) ** No longer affects: kubuntu-settings (Ubuntu Impish) ** No longer affects: kdesu (Ubuntu Impish) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1965439 Title: applications can no longer launch when called by kdesu Status in kdesu package in Ubuntu: Confirmed Status in kubuntu-settings package in Ubuntu: In Progress Status in sudo package in Ubuntu: Confirmed Status in ubuntustudio-default-settings package in Ubuntu: In Progress Status in kdesu source package in Jammy: Confirmed Status in kubuntu-settings source package in Jammy: In Progress Status in sudo source package in Jammy: Confirmed Status in ubuntustudio-default-settings source package in Jammy: In Progress Bug description: See description below. As the driver manager is done inside software- properties-qt, it's basically the same bug, but now it's affected by something we can't exactly get into the mechanism of: plasma- discover's "Software Sources" link. Steps to recrate: 1) Open Plasma-discover 2) Go to Settings 3) Under click on "Software Sources" 4) Attempt to enter password Expected: Software properties opens Actual: Pkexec keeps asking for password. -- Earlier description: The driver manager for both Ubuntu Studio and Kubuntu can no longer launch due to some updated security measures in PolicyKit. The original behavior was that systemsettings would open /usr/bin/ubuntustudio-driver-manager (or /usr/bin/kubuntu-driver- manger) via pkexec, which would then open software-settings-qt. Unfortunately, the new behavior does not act correctly to pkexec and pkexec does not see the user as available in the sudoers file. The only way around this was to pass "export DISPLAY=:0" inside the appropriate driver manager executable with the command "sudo software- properties-qt". The KCM itself needs to execute the driver-manager via xterm, which then prompts for a password. It's ugly, but it works. I will attach a debdiff for the kubuntu-settings package. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntustudio-default-settings 22.04.19 [modified: usr/share/sddm/themes/ubuntustudio/theme.conf] ProcVersionSignature: Ubuntu 5.15.0-22.22-lowlatency 5.15.19 Uname: Linux 5.15.0-22-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Mar 17 12:19:44 2022 InstallationDate: Installed on 2021-03-20 (361 days ago) InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 (20210320) PackageArchitecture: all SourcePackage: ubuntustudio-default-settings UpgradeStatus: Upgraded to jammy on 2021-11-07 (130 days ago) modified.conffile..etc.skel..local.share.konsole.Profile: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdesu/+bug/1965439/+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 1975673] [NEW] libgpg-error/1.45-2 fails autopkgtest on i386
Public bug reported: The failure was introduced by this change in Debian: https://salsa.debian.org/debian/libgpg-error/-/commit/0c11fe4ae16c2800e13758ff1ee64c561354e628 It started to fail for i386 on autopkgtest.u.c: https://autopkgtest.ubuntu.com/packages/libgpg-error/kinetic/i386 https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic/kinetic/i386/libg/libgpg-error/20220523_114919_e3142@/log.gz The relevant log is this: ``` The following packages have unmet dependencies: builddeps:/tmp/autopkgtest.VMjBik/1-autopkgtest-satdep.dsc:i386 : Depends: gcc-mingw-w64-x86-64:i386 but it is not installable E: Unable to correct problems, you have held broken packages. win64 FAIL badpkg [...] autopkgtest [11:49:03]: summary win32 SKIP Test lists explicitly supported architectures, but the current architecture amd64 isn't listed. win64 FAIL badpkg blame: libgpg-error badpkg: Test dependencies are unsatisfiable. A common reason is that your testbed is out of date with respect to the archive, and you need to use a current testbed or run apt-get update or use -U. build PASS ``` As can be seen, the i386/win32 test is skipped while amd64/win64 is executed and fails with "badpkg" error due to not being able to install "gcc-mingw-w64-x86-64:i386". = Even if that can be fixed (https://code.launchpad.net/~ubuntu-release/autopkgtest/+git/development/+merge/423176), the "win64" test is skipped now and "win32" executed, "win32" fails with a "badpkg" error, which probably needs solving in the archive. $ PYTHONPATH=lib/ runner/autopkgtest libgpg-error --apt-pocket=proposed=src:libgpg-error -a i386 -U -- qemu /data/autopkgtest-kinetic-amd64.img [...] win64 SKIP Test lists explicitly supported architectures, but the current architecture i386 isn't listed. [...] The following packages have unmet dependencies: builddeps:/tmp/autopkgtest.8Maso6/1-autopkgtest-satdep.dsc:i386 : Depends: gcc-mingw-w64-i686:i386 but it is not installable Depends: wine32:i386 but it is not going to be installed E: Unable to correct problems, you have held broken packages. win32 FAIL badpkg blame: libgpg-error badpkg: Test dependencies are unsatisfiable. A common reason is that your testbed is out of date with respect to the archive, and you need to use a current testbed or run apt-get update or use -U. Full log: https://paste.ubuntu.com/p/JYHrJpMGbn/ ** Affects: libgpg-error (Ubuntu) Importance: Undecided Status: New ** Tags: update-excuse ** Merge proposal linked: https://code.launchpad.net/~ubuntu-release/autopkgtest/+git/development/+merge/423176 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libgpg-error in Ubuntu. https://bugs.launchpad.net/bugs/1975673 Title: libgpg-error/1.45-2 fails autopkgtest on i386 Status in libgpg-error package in Ubuntu: New Bug description: The failure was introduced by this change in Debian: https://salsa.debian.org/debian/libgpg-error/-/commit/0c11fe4ae16c2800e13758ff1ee64c561354e628 It started to fail for i386 on autopkgtest.u.c: https://autopkgtest.ubuntu.com/packages/libgpg-error/kinetic/i386 https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic/kinetic/i386/libg/libgpg-error/20220523_114919_e3142@/log.gz The relevant log is this: ``` The following packages have unmet dependencies: builddeps:/tmp/autopkgtest.VMjBik/1-autopkgtest-satdep.dsc:i386 : Depends: gcc-mingw-w64-x86-64:i386 but it is not installable E: Unable to correct problems, you have held broken packages. win64 FAIL badpkg [...] autopkgtest [11:49:03]: summary win32 SKIP Test lists explicitly supported architectures, but the current architecture amd64 isn't listed. win64 FAIL badpkg blame: libgpg-error badpkg: Test dependencies are unsatisfiable. A common reason is that your testbed is out of date with respect to the archive, and you need to use a current testbed or run apt-get update or use -U. build PASS ``` As can be seen, the i386/win32 test is skipped while amd64/win64 is executed and fails with "badpkg" error due to not being able to install "gcc-mingw-w64-x86-64:i386". = Even if that can be fixed (https://code.launchpad.net/~ubuntu-release/autopkgtest/+git/development/+merge/423176), the "win64" test is skipped now and "win32" executed, "win32" fails with a "badpkg" error, which probably needs solving in the archive. $ PYTHONPATH=lib/ runner/autopkgtest libgpg-error --apt-pocket=proposed=src:libgpg-error -a i386 -U -- qemu /data/autopkgtest-kinetic-amd64.img [...] win64 SKIP Test lists explicitly supported architectures, but the current architecture i386 isn't listed. [...] The following packages have unmet dependencies: builddeps:/tmp/autopkgtest.8Maso6/1-autopkgtest-satdep.dsc:i386 : Depends:
[Touch-packages] [Bug 1975549] Re: NetworkManager uses tethered Android phone as ethernet connection instead of wired ethernet connection
yes, the current details are about a working system but we want to work
on the bug
--
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/1975549
Title:
NetworkManager uses tethered Android phone as ethernet connection
instead of wired ethernet connection
Status in network-manager package in Ubuntu:
New
Bug description:
I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
trouble the last week or two ssh'sing into the machine, and printing
from the machine when I am sitting at the keyboard. I also could not
connect to my external firewall when sitting at the keyboard.
I keep a Google Pixel 4a tethered to the USB hub for charging. The
Android phone is running Android 12, and the phone is set to "USB
Tethering". The phone is fully patched, too.
I found if I reboot the machine with the phone tethered, then the
machine uses the Android phone as the ethernet connection. It
literally calls the connection "ethernet", as if it was using the
network adapter. This is new behavior over the last week or two.
This is unexpected behavior for three reasons. First, it is new
behavior. Second, the wired gigabit ethernet connection is not used by
default. And thrid, the Android phone's connection is called
"ethernet" instead of something more meaningful like "USB" or
"Android" or "wired hotspot".
The third item ("ethernet" name when using Android phone) was
misleading enough to waste a lot of time troubleshooting the issue. I
thought I had an odd firewall issue or a mDNS issue.
The reason I was having so many troubles, like printing and ssh, is
the Android phone uses Wifi and it is on a different VLAN and subnet
to keep traffic segregated from my trusted internal network.
-
It looks like I am running network-manager via systemd:
# service systemd-networkd status
● systemd-networkd.service - Network Service
Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled;
vendor prese>
Active: inactive (dead)
Docs: man:systemd-networkd.service(8)
# service network-manager status
● NetworkManager.service - Network Manager
Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled;
vendor preset: >
Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
Docs: man:NetworkManager(8)
Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
Memory: 12.0M
CGroup: /system.slice/NetworkManager.service
└─928 /usr/sbin/NetworkManager --no-daemon
...
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2022-02-05 (107 days ago)
InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64
(20210819.1)
IpRoute:
default via 172.16.1.1 dev enp4s0 proto dhcp metric 100
169.254.0.0/16 dev enp4s0 scope link metric 1000
172.16.0.0/12 dev enp4s0 proto kernel scope link src 172.16.2.10 metric 100
Package: network-manager 1.22.10-1ubuntu2.3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
Tags: focal
Uname: Linux 5.13.0-44-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
nmcli-con:
NAME UUID TYPE TIMESTAMP
TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY
DBUS-PATH ACTIVE DEVICE STATE
ACTIVE-PATH SLAVE FILENAME
Ethernet 5d31ea14-c1cd-318f-a982-09ce6723dadb ethernet 1653403311 Tue 24
May 2022 10:41:51 AM EDT yes -100 no
/org/freedesktop/NetworkManager/Settings/1 yes enp4s0 activated
/org/freedesktop/NetworkManager/ActiveConnection/4 --
/etc/NetworkManager/system-connections/Ethernet.nmconnection
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.22.10 connected started full enabled enabled
enabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1975549/+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 1975667] [NEW] systemd-resolved does not reset DNS server and search domain list properly after VPN disconnect
Public bug reported: Hi, in Ubuntu 21.10 I am facing a problem with DNS server list and search domain list is not properly reset back to the previous values after a VPN is disconnected. I reproduced this in Ubuntu 21.10 instance which was upgraded from the older version of Ubuntu as well as in Live USB Ubuntu 21.10 so it is not an "upgrade issue". I use this resolv.conf symlink: /etc/resolv.conf -> ../run/systemd/resolve/resolv.conf Actual behavior: VPN connect will add VPN's DNS servers and search domains into /etc/resolv.conf. When VPN is disconnected there are some of the VPN's DNS server and search domain entries left there, so it is not reset back properly. Desired behavior: VPN connect will add VPN's DNS servers and search domains into /etc/resolv.conf. When VPN is disconnected DNS servers and search domain list is restored to exactly the same state as was prior to the VPN connection. Steps for reproducing: 1. Before VPN is connected this is the DNS server and search domain list in /etc/resolv.conf: nameserver 192.168.122.1 search . 2. Once the VPN is connected, we see there were VPN's DNS server and serach domain list entries added: nameserver 2xx.xx.xx.x0 nameserver 2xx.xx.xx.x1 nameserver 192.168.122.1 search domain1.local domain2.internal domain3.internal 3. After VPN disconnection, we see the DNS server and search domain list in /etc/resolv.conf is not restored to the state at point (1.) and some entries from VPN is being kept there: nameserver 2xx.xx.xx.x1 nameserver 192.168.122.1 search domain2.internal domain3.internal ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: systemd 248.3-1ubuntu8 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465 CurrentDesktop: ubuntu:GNOME Date: Wed May 25 06:06:05 2022 LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet 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/15p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- 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: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.14.0-2 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-6.0 dmi.modalias: dmi:bvnSeaBIOS:bvr1.14.0-2:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-6.0:sku:cvnQEMU:ct1:cvrpc-q35-6.0: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-6.0 dmi.sys.vendor: QEMU ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish -- 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/1975667 Title: systemd-resolved does not reset DNS server and search domain list properly after VPN disconnect Status in systemd package in Ubuntu: New Bug description: Hi, in Ubuntu 21.10 I am facing a problem with DNS server list and search domain list is not properly reset back to the previous values after a VPN is disconnected. I reproduced this in Ubuntu 21.10 instance which was upgraded from the older version of Ubuntu as well as in Live USB Ubuntu 21.10 so it is not an "upgrade issue". I use this resolv.conf symlink: /etc/resolv.conf -> ../run/systemd/resolve/resolv.conf Actual behavior: VPN connect will add VPN's DNS servers and search domains into /etc/resolv.conf. When VPN is disconnected there are some of the VPN's DNS server and search domain entries left there, so it is not reset back properly. Desired behavior: VPN connect will add VPN's DNS servers and search domains into /etc/resolv.conf. When VPN is disconnected DNS servers and search domain list is restored to exactly
[Touch-packages] [Bug 1975650] Re: Display stuck in low resolution
Thanks for the bug report. It appears your Nvidia kernel driver is not loading anymore so low resolution is expected. This may have been caused by a recent kernel update. Please try this: sudo apt install --reinstall nvidia-driver-510/jammy sudo apt install --reinstall nvidia-dkms-510/jammy and then reboot. ** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-510 (Ubuntu) ** Summary changed: - Display stuck in low resolution + [nvidia] Display stuck in low resolution ** Changed in: nvidia-graphics-drivers-510 (Ubuntu) Status: New => Incomplete ** Tags added: nvidia -- 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/1975650 Title: [nvidia] Display stuck in low resolution Status in nvidia-graphics-drivers-510 package in Ubuntu: Incomplete Bug description: I often have to forcibly power down my PC because of this bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970808. Well, the most recent time I did that, when the computer restarted, the resolution is stuck on 1024x768 even though I am on a 1920x1080 monitor. I restarted my PC again and it is still stuck on the low resolution. This Ask Ubuntu answer (https://askubuntu.com/a/1167437/1589552) did allow me to force my resolution to 1920x1080, but a few things still seemed off: - The display settings page in the Gnome settings app still showed my display as "unknown display" and did not have any options for changing the resolution. - A WebGL-based application I use for work was very slow compared to normal. I reverted the change to my Grub config and now I'm back to 1024x768. I have an Nvidia GTX 1060 connected to a 1920x1080 monitor via HDMI. Let me know of any other information I can provide that would be helpful. Also let me know if there is a workaround other than reinstalling the OS. Edit: I have a Windows dual boot on this PC, with Windows installed on a separate SSD. I booted into Windows and everything seems completely fine. This provides further evidence that this is a software issue, not a hardware one. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 24 20:14:55 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GP106 [GeForce GTX 1060 3GB] [1462:3287] InstallationDate: Installed on 2022-04-23 (31 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Gigabyte Technology Co., Ltd. B450M DS3H ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=c4ac1391-7d4e-4282-94ba-fbae3c4c044c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: Default string dmi.board.name: B450M DS3H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd01/25/2019:br5.13:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: B450M DS3H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 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 1975566] Re: radeon / amdgpu bad performance or panics
I don't know much about AMD GPUs but from what I've seen there is usually only one kernel graphics driver that works for a given GPU. After you have switched back to a 'stock' config and kernel, what does vulkaninfo report? Does the "bad performance" persist? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1975566 Title: radeon / amdgpu bad performance or panics Status in mesa package in Ubuntu: Incomplete Bug description: Recently I upgraded my machine and moved my GPU over from the old (Intel something) to the new machine (AMD Ryzen 7 5700X, B550 motherboard). I did a fresh Ubuntu install (server) and added packages to get my GUI rolling (lightdm + awesomewm), just like before. The graphics cards is a "Gigabyte GV-R928XOC-3GD Rev. 2.0" which has the R9 280X chip (TAHITI / Southern Islands). On my old system, I could play games with Vulkan, but with this system it doesn't work. If I run the 'default' setup, it uses the 'radeon' kernel module. The first couple of seconds I get reasonable performance (glxgears @ 60 FPS), then it suddenly drop to 4 and motion is almost not visible). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg (not installed) Uname: Linux 5.18.0-051800-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue May 24 06:49:56 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Tahiti XT [Radeon HD 7970/8970 OEM / R9 280X] [1002:6798] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Tahiti XTL [Radeon R9 280X OC] [1458:3001] InstallationDate: Installed on 2022-05-14 (9 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.18.0-051800-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P2.30 dmi.board.name: B550 Phantom Gaming-ITX/ax dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP2.30:bd02/25/2022:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB550PhantomGaming-ITX/ax:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 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/mesa/+bug/1975566/+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 1975557] Re: blank screen does not turn off display backlight
The difference between 21.10 and 22.04 might just be that we now default to Wayland instead of Xorg. So the display subsystems are different. Please run this command to gather more information: apport-collect 1975557 And to save time in future please use the 'ubuntu-bug' command to report new bugs. ** Tags added: jammy ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (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/1975557 Title: blank screen does not turn off display backlight Status in gnome-shell package in Ubuntu: Incomplete Bug description: I updated a system from 21.10 to 22.04 and noticed that when the screen is blanked by no keyboard or mouse activity that the backlight in the VGA monitor is still on. The "settings->Displays" has "Unknown Display" which I assume means the system does not know what commands to send to the monitor to shut it off. I booted a live DVD of 21.10 and the settings has the VGA display as 'AOC 22" ' which is correct and the screen blanking works correctly. So it seems that the definition for the AOC displays have been removed from 22.04. This behavior is different on Ubuntu 21.10, the VGA display is blank and the backlight is off. A minor nit is on 21.10 the "settings->Displays" shows the VGA display manufacture name, on 22.04 the VGA display manufacture name is "Unknown Display". I have discovered that the settings have the following options "settings->Power->Screen Blank" with a time value to be selected and the following text on the next line "Turns the screen off after a period of inactivity" "settings->Privacy->Screen->Blank Screen Display" with a time value to be selected and the following text on the next line "Period of inactivity after which the screen will go blank" The two options have different actions but seem to be connected because changing the time on one changes the time on the other. My guess is that the update changed the action for Ubuntu 22.04. I would like the 21.10 behavior, that is to turn off the VGA display not just blank the display when selecting the "settings->Power->Screen Blank" for 22.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1975557/+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
