[Touch-packages] [Bug 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog
Happens since I upgraded to Ubuntu 22.04. I can force focus on the Save As dialog, hit to be able to rename my download, but the focus doesn't stay on the file name and instead - after typing a character - the focus switches to a search field inside the Save As dialog. root@pswsl01:~# uname -a Linux pswsl01 5.18.10-76051810-generic #202207071639~1659403207~22.04~cb5f582~dev-Ubuntu SMP PREEMPT_DY x86_64 x86_64 x86_64 GNU/Linux root@pswsl01:~# cat /proc/version Linux version 5.18.10-76051810-generic (buildd@lcy02-amd64-047) (gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #202207071639~1659403207~22.04~cb5f582~dev-Ubuntu SMP PREEMPT_DY root@pswsl01:~# lscpu Architecture:x86_64 CPU op-mode(s):32-bit, 64-bit Address sizes: 48 bits physical, 48 bits virtual Byte Order:Little Endian CPU(s): 12 On-line CPU(s) list: 0-11 Vendor ID: AuthenticAMD Model name:AMD Ryzen 5 5500U with Radeon Graphics CPU family: 23 Model: 104 Thread(s) per core: 2 Core(s) per socket: 6 Socket(s): 1 Stepping:1 root@pswsl01:~# snap list Name Version RevTracking Publisher Notes airshark 0.4 3 latest/stablepd - bare 1.0 5 latest/stable canonical✓base chromium 105.0.5195.52 2076 latest/stable canonical✓- core 16-2.56.2 13425 latest/stable canonical✓core core18 202207062538 latest/stable canonical✓base core20 202208051611 latest/stable canonical✓base firefox104.0.1-1 1775 latest/stablemozilla✓ - gh 2.6.0-15-g1a10fd5a 502latest/stable casper-dcl- gnome-3-28-18043.28.0-19-g98f9e67.98f9e67 161latest/stable canonical✓- gnome-3-34-18040+git.3556cb3 77 latest/stable/… canonical✓- gnome-3-38-20040+git.891e5bc 115latest/stable canonical✓- gtk-common-themes 0.1-81-g442e511 1535 latest/stable/… canonical✓- signal-desktop 5.52.0 392latest/stable snapcrafters - snap-store 3.38.0-66-gbd5b8f7 558latest/stable/… canonical✓- snapd 2.56.2 16292 latest/stable canonical✓snapd -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1949340 Title: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog Status in Mozilla Firefox: Unknown Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in gtk4 package in Ubuntu: Confirmed Status in xdg-desktop-portal-gnome package in Ubuntu: Confirmed Status in xdg-desktop-portal-gtk package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Open Chromium (release does not matter, here deb-packaged version from 18.04 LTS is used) 2a. Navigate to some page, press + 2b. Navigate to some page, with "Ask where to save each file before downloading" enabled try to download some file Actual result: * file chooser dialog is unfocused, user should select the window by mouse and then hit for specified location Expected result: * file chooser dialog is focused, user can simply hit to save in previously selected location. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1949340/+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 1648319] Re: Failed to use bus name org.freedesktop.DisplayManager
Folks, I get the Same error. lightdm --test-mode Failed to use bus name org.freedesktop.DisplayManager, do you have appropriate permissions? It's been a few years without activity... Thanks for your attention. Regards Pedro -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1648319 Title: Failed to use bus name org.freedesktop.DisplayManager Status in lightdm package in Ubuntu: Confirmed Bug description: I have implemented the command lightdm --test-mode --debug and I happened here such error: == [+0.01s] DEBUG: Logging to /var/log/lightdm/lightdm.log [+0.01s] DEBUG: Starting Light Display Manager 1.10.3, UID=0 PID=1683 [+0.01s] DEBUG: Loading configuration dirs from /var/lib/menu-xdg/lightdm/lightdm.conf.d [+0.01s] DEBUG: Loading configuration dirs from /usr/share/gdm/lightdm/lightdm.conf.d [+0.01s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d [+0.01s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/01_debian.conf [+0.01s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d [+0.01s] DEBUG: Loading configuration dirs from /var/lib/menu-xdg/lightdm/lightdm.conf.d [+0.01s] DEBUG: Loading configuration dirs from /usr/share/gdm/lightdm/lightdm.conf.d [+0.01s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d [+0.01s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/01_debian.conf [+0.01s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d [+0.01s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d [+0.01s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf [+0.01s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager [+0.01s] DEBUG: Using Xephyr for X servers [+0.01s] DEBUG: Registered seat module xlocal [+0.01s] DEBUG: Registered seat module xremote [+0.01s] DEBUG: Registered seat module unity [+0.01s] DEBUG: Registered seat module surfaceflinger [+1.13s] DEBUG: Adding default seat [+1.13s] DEBUG: Seat: Starting [+1.13s] DEBUG: Seat: Creating greeter session [+1.17s] DEBUG: Seat: Creating display server of type x [+1.20s] DEBUG: Could not run plymouth --ping: Failed to execute child process "plymouth" (No such file or directory) [+1.20s] DEBUG: Using VT 7 [+1.20s] DEBUG: Seat: Starting local X display on VT 7 [+1.20s] DEBUG: DisplayServer x-1: Logging to /var/log/lightdm/x-1.log [+1.36s] DEBUG: DisplayServer x-1: Writing X server authority to /var/run/lightdm/root/:1 [+1.36s] DEBUG: DisplayServer x-1: Launching X Server [+1.36s] DEBUG: Launching process 1687: /usr/bin/Xephyr :1 -seat seat0 -auth /var/run/lightdm/root/:1 -nolisten tcp vt7 -novtswitch [+1.36s] DEBUG: DisplayServer x-1: Waiting for ready signal from X server :1 [+1.36s] DEBUG: Acquired bus name org.freedesktop.DisplayManager [+1.36s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0 Failed to use bus name org.freedesktop.DisplayManager, do you have appropriate permissions? = On the Internet I have the exact solution to this problem is not found. The computer I have is only one graphics card and built-in The controller is not present. Somebody help than you can! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1648319/+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 1648319] Re: Failed to use bus name org.freedesktop.DisplayManager
BTW.. root@###:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.04 LTS Release:22.04 Codename: jammy root@###:~# apt list lightdm --installed Listing... Done lightdm/jammy,now 1.30.0-0ubuntu5 amd64 [installed,automatic] -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1648319 Title: Failed to use bus name org.freedesktop.DisplayManager Status in lightdm package in Ubuntu: Confirmed Bug description: I have implemented the command lightdm --test-mode --debug and I happened here such error: == [+0.01s] DEBUG: Logging to /var/log/lightdm/lightdm.log [+0.01s] DEBUG: Starting Light Display Manager 1.10.3, UID=0 PID=1683 [+0.01s] DEBUG: Loading configuration dirs from /var/lib/menu-xdg/lightdm/lightdm.conf.d [+0.01s] DEBUG: Loading configuration dirs from /usr/share/gdm/lightdm/lightdm.conf.d [+0.01s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d [+0.01s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/01_debian.conf [+0.01s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d [+0.01s] DEBUG: Loading configuration dirs from /var/lib/menu-xdg/lightdm/lightdm.conf.d [+0.01s] DEBUG: Loading configuration dirs from /usr/share/gdm/lightdm/lightdm.conf.d [+0.01s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d [+0.01s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/01_debian.conf [+0.01s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d [+0.01s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d [+0.01s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf [+0.01s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager [+0.01s] DEBUG: Using Xephyr for X servers [+0.01s] DEBUG: Registered seat module xlocal [+0.01s] DEBUG: Registered seat module xremote [+0.01s] DEBUG: Registered seat module unity [+0.01s] DEBUG: Registered seat module surfaceflinger [+1.13s] DEBUG: Adding default seat [+1.13s] DEBUG: Seat: Starting [+1.13s] DEBUG: Seat: Creating greeter session [+1.17s] DEBUG: Seat: Creating display server of type x [+1.20s] DEBUG: Could not run plymouth --ping: Failed to execute child process "plymouth" (No such file or directory) [+1.20s] DEBUG: Using VT 7 [+1.20s] DEBUG: Seat: Starting local X display on VT 7 [+1.20s] DEBUG: DisplayServer x-1: Logging to /var/log/lightdm/x-1.log [+1.36s] DEBUG: DisplayServer x-1: Writing X server authority to /var/run/lightdm/root/:1 [+1.36s] DEBUG: DisplayServer x-1: Launching X Server [+1.36s] DEBUG: Launching process 1687: /usr/bin/Xephyr :1 -seat seat0 -auth /var/run/lightdm/root/:1 -nolisten tcp vt7 -novtswitch [+1.36s] DEBUG: DisplayServer x-1: Waiting for ready signal from X server :1 [+1.36s] DEBUG: Acquired bus name org.freedesktop.DisplayManager [+1.36s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0 Failed to use bus name org.freedesktop.DisplayManager, do you have appropriate permissions? = On the Internet I have the exact solution to this problem is not found. The computer I have is only one graphics card and built-in The controller is not present. Somebody help than you can! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1648319/+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 1924494] [NEW] Systemd shutdown order unmounts filesystem used by qemu/kvm guest before shutting down the guest
Public bug reported: Last night I started a reboot without manually shutting down a qemu/kvm guest first. After X went down a bunch of I/O errors associated with a network block device that contains a NTFS filesystem showed up on the console. I noticed that the umount.target had been reached but the virt-guest-shutdown.target was still waiting for the guest to shut down, until it timed out. Wouldn't it be beneficial for all guests to be shutdown before unmounting all filesystems? ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: systemd 246.6-1ubuntu1.3 ProcVersionSignature: Ubuntu 5.8.0-49.55-generic 5.8.18 Uname: Linux 5.8.0-49-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Apr 15 08:35:48 2021 InstallationDate: Installed on 2021-01-17 (88 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: HP HP ZBook 15u G6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-49-generic root=UUID=25df7fed-1baf-421e-941e-7f7c280db6e8 ro iommu=pt intel_iommu=on default_hugepagesz=1G hugepagesz=1G hugepages=6 pcie_aspm.policy=performance SourcePackage: systemd UpgradeStatus: Upgraded to groovy on 2021-04-08 (6 days ago) dmi.bios.date: 01/08/2021 dmi.bios.release: 8.1 dmi.bios.vendor: HP dmi.bios.version: R70 Ver. 01.08.01 dmi.board.name: 8549 dmi.board.vendor: HP dmi.board.version: KBC Version 52.67.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 82.103 dmi.modalias: dmi:bvnHP:bvrR70Ver.01.08.01:bd01/08/2021:br8.1:efr82.103:svnHP:pnHPZBook15uG6:pvr:rvnHP:rn8549:rvrKBCVersion52.67.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook dmi.product.name: HP ZBook 15u G6 dmi.product.sku: 9AP56LP#ABA dmi.sys.vendor: HP ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- 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/1924494 Title: Systemd shutdown order unmounts filesystem used by qemu/kvm guest before shutting down the guest Status in systemd package in Ubuntu: New Bug description: Last night I started a reboot without manually shutting down a qemu/kvm guest first. After X went down a bunch of I/O errors associated with a network block device that contains a NTFS filesystem showed up on the console. I noticed that the umount.target had been reached but the virt-guest-shutdown.target was still waiting for the guest to shut down, until it timed out. Wouldn't it be beneficial for all guests to be shutdown before unmounting all filesystems? ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: systemd 246.6-1ubuntu1.3 ProcVersionSignature: Ubuntu 5.8.0-49.55-generic 5.8.18 Uname: Linux 5.8.0-49-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Apr 15 08:35:48 2021 InstallationDate: Installed on 2021-01-17 (88 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: HP HP ZBook 15u G6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-49-generic root=UUID=25df7fed-1baf-421e-941e-7f7c280db6e8 ro iommu=pt intel_iommu=on default_hugepagesz=1G hugepagesz=1G hugepages=6 pcie_aspm.policy=performance SourcePackage: systemd UpgradeStatus: Upgraded to groovy on 2021-04-08 (6 days ago) dmi.bios.date: 01/08/2021 dmi.bios.release: 8.1 dmi.bios.vendor: HP dmi.bios.version: R70 Ver. 01.08.01 dmi.board.name: 8549 dmi.board.vendor: HP dmi.board.version: KBC Version 52.67.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 82.103 dmi.modalias: dmi:bvnHP:bvrR70Ver.01.08.01:bd01/08/2021:br8.1:efr82.103:svnHP:pnHPZBook15uG6:pvr:rvnHP:rn8549:rvrKBCVersion52.67.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook dmi.product.name: HP ZBook 15u G6 dmi.product.sku: 9AP56LP#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1924494/+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 1657837] Re: systemd-networkd can't add a VLAN interface to bridge
Nope, it is still a problem in "systemd 231-9ubuntu4 amd64". Actually, it seems like multiple features documented in the Ubuntu Manpages for systemd.network are not functioning. Below are some error messages (journalctl -a -u systemd-networkd), followed by the configuration files. ERROR MESSAGES - START may 01 11:34:31 ps01lnx systemd-networkd[30661]: ovsbr0p1: MAC configured for tap, ignoring may 01 11:34:31 ps01lnx systemd-networkd[30661]: ovsbr0p0: MAC configured for tap, ignoring may 01 11:34:31 ps01lnx systemd-networkd[30661]: [/etc/systemd/network/7-ovsbr0lcl1.netdev:8] Unknown lvalue 'DefaultPVID' in section 'Bridge' may 01 11:34:31 ps01lnx systemd-networkd[30661]: [/etc/systemd/network/7-ovsbr0lcl1.netdev:10] Unknown lvalue 'STP' in section 'Bridge' may 01 11:34:31 ps01lnx systemd-networkd[30661]: NetDev with invalid Kind configured in /etc/systemd/network/3-vlan1.netdev. Ignoring may 01 11:34:31 ps01lnx systemd-networkd[30661]: [/etc/systemd/network/9-ovsbr0p1.network:9] Unknown lvalue 'bridge' in section 'Network' may 01 11:34:31 ps01lnx systemd-networkd[30661]: [/etc/systemd/network/9-ovsbr0p0.network:9] Unknown lvalue 'bridge' in section 'Network' ERROR MESSAGES - END SYSTEMD CONFIGURATION systemctl enable systemd-networkd === /etc/systemd/network/3-vlan1.netdev === [Netdev] Name=br0vlan1 Kind=vlan [VLAN] Id=1 === /etc/systemd/network/3-vlan1.network === [Match] Name=br0vlan1 [Network] Bridge=ovsbr0lcl1 === /etc/systemd/network/7-ovsbr0lcl1.netdev === [NetDev] Name=ovsbr0lcl1 Kind=bridge MTUBytes=8996 MACAddress=52:54:00:5a:9e:90 [Bridge] DefaultPVID=1 VLANFiltering=true STP=false === /etc/systemd/network/7-ovsbr0p0.netdev === [NetDev] Name=ovsbr0p0 Kind=tap MACAddress=52:54:00:5a:9e:92 === /etc/systemd/network/7-ovsbr0p1.netdev === [NetDev] Name=ovsbr0p1 Kind=tap MACAddress=52:54:00:5a:9e:93 === /etc/systemd/network/8-ovsbr0lcl1.link === [Match] MACAddress=52:54:00:5a:9e:90 OriginalName=ovsbr0lcl1 Driver=bridge [Link] Name=ovsbr0lcl1 Alias=br0lcl1 MACAddressPolicy=persistent MTUBytes=8996 === /etc/systemd/network/8-ovsvbr0p0.link === [Match] OriginalName=ovsbr0p0 MACAddress=52:54:00:5a:9e:92 [Link] MTUBytes=8996 MACAddress=52:54:00:5a:9e:92 === /etc/systemd/network/8-ovsvbr0p1.link === [Match] OriginalName=ovsbr0p1 [Link] MTUBytes=8996 MACAddress=52:54:00:5a:9e:93 === /etc/systemd/network/9-ovsbr0lcl1.network === [Match] Name=ovsbr0lcl1 MACAddress=52:54:00:5a:9e:90 [Link] MACAddress=52:54:00:5a:9e:90 MTUBytes=8996 [Network] DHCP=no Address=192.168.56.1/24 LinkLocalAddressing=no MulticastDNS=false IPv6AcceptRA=false === /etc/systemd/network/9-ovsbr0p0.network === [Match] Name=ovsbr0p0 [Link] MACAddress=52:54:00:5a:9e:92 MTUBytes=8996 [Network] bridge=ovsbr0lcl1 Address=192.168.56.2/24 LinkLocalAddressing=no MulticastDNS=false IPv6AcceptRA=false [BridgeVLAN] VLAN=1 EgressUntagged=1 PVID=1 === /etc/systemd/network/9-ovsbr0p1.network === [Match] Name=ovsbr0p1 [Link] MACAddress=52:54:00:5a:9e:93 MTUBytes=8996 [Network] bridge=ovsbr0lcl1 Address=192.168.56.3/24 LinkLocalAddressing=no MulticastDNS=false IPv6AcceptRA=false [BridgeVLAN] VLAN=1 EgressUntagged=1 PVID=1 -- 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/1657837 Title: systemd-networkd can't add a VLAN interface to bridge Status in systemd package in Ubuntu: Confirmed Bug description: This is apparently fixed in systemd 231: https://lists.freedesktop.org/archives/systemd- devel/2016-August/037385.html When systemd tries to put a VLAN interface into a bridge on Xenial, it fails: # journalctl --boot -u systemd-networkd Jan 15 09:16:46 hydrogen systemd[1]: Started Network Service. Jan 15 09:16:46 hydrogen systemd-networkd[1903]: br-mgmt: netdev exists, using existing without changing its parameters Jan 15 09:16:46 hydrogen systemd-networkd[1903]: br-mgmt: Could not append VLANs: Operation not permitted Jan 15 09:16:46 hydrogen systemd-networkd[1903]: br-mgmt: Failed to assign VLANs to bridge port: Operation not permitted Jan 15 09:16:46 hydrogen systemd-networkd[1903]: br-mgmt: Could not set bridge vlan: Operation not permitted Jan 15 09:16:59 hydrogen systemd-networkd[1903]: enp3s0: Configured Jan 15 09:16:59 hydrogen systemd-networkd[1903]: enp2s0: Configured Here are the systemd-networkd configs I used: root@hydrogen:/etc/systemd/network# cat enp3s0.network [Match] Name=enp3s0 [Network] VLAN=vlan10 root@hydrogen:/etc/systemd/network# cat vlan10.netdev [NetDev] Name=vlan10 Kind=vlan [VLAN] Id=10 root@hydrogen:/etc/systemd/network# cat vlan10.network [Match] N
[Touch-packages] [Bug 1657837] Re: systemd-networkd can't add a VLAN interface to bridge
And the error messages pertinent to the issue with the VLAN are: = may 01 11:34:31 ps01lnx systemd[1]: Started Network Service. may 01 11:34:31 ps01lnx systemd[1]: systemd-networkd.service: Failed to send unit change signal for systemd-networkd.service: Connection reset by peer may 01 11:34:31 ps01lnx systemd-networkd[30661]: ovsbr0lcl1: IPv6 disabled for interface: Success may 01 11:34:31 ps01lnx systemd-networkd[30661]: ovsbr0lcl1: Could not append VLANs: Operation not permitted may 01 11:34:31 ps01lnx systemd-networkd[30661]: ovsbr0lcl1: Failed to assign VLANs to bridge port: Operation not permitted may 01 11:34:31 ps01lnx systemd-networkd[30661]: ovsbr0lcl1: Could not set bridge vlan: Operation not permitted may 01 11:34:31 ps01lnx systemd-networkd[30661]: ovsbr0p0: IPv6 disabled for interface: Success may 01 11:34:31 ps01lnx systemd-networkd[30661]: ovsbr0p1: IPv6 disabled for interface: Success may 01 11:34:31 ps01lnx systemd-networkd[30661]: ovsbr0lcl1: Configured may 01 11:34:31 ps01lnx systemd-networkd[30661]: ovsbr0p0: Configured may 01 11:34:31 ps01lnx systemd-networkd[30661]: ovsbr0p1: Configured = As you can see, the bridge and the two ports (tap devices) were configured. But the bridge VLAN did not receive the intended configuration, and the tap devices failed to be associated with the bridge. -- 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/1657837 Title: systemd-networkd can't add a VLAN interface to bridge Status in systemd package in Ubuntu: Confirmed Bug description: This is apparently fixed in systemd 231: https://lists.freedesktop.org/archives/systemd- devel/2016-August/037385.html When systemd tries to put a VLAN interface into a bridge on Xenial, it fails: # journalctl --boot -u systemd-networkd Jan 15 09:16:46 hydrogen systemd[1]: Started Network Service. Jan 15 09:16:46 hydrogen systemd-networkd[1903]: br-mgmt: netdev exists, using existing without changing its parameters Jan 15 09:16:46 hydrogen systemd-networkd[1903]: br-mgmt: Could not append VLANs: Operation not permitted Jan 15 09:16:46 hydrogen systemd-networkd[1903]: br-mgmt: Failed to assign VLANs to bridge port: Operation not permitted Jan 15 09:16:46 hydrogen systemd-networkd[1903]: br-mgmt: Could not set bridge vlan: Operation not permitted Jan 15 09:16:59 hydrogen systemd-networkd[1903]: enp3s0: Configured Jan 15 09:16:59 hydrogen systemd-networkd[1903]: enp2s0: Configured Here are the systemd-networkd configs I used: root@hydrogen:/etc/systemd/network# cat enp3s0.network [Match] Name=enp3s0 [Network] VLAN=vlan10 root@hydrogen:/etc/systemd/network# cat vlan10.netdev [NetDev] Name=vlan10 Kind=vlan [VLAN] Id=10 root@hydrogen:/etc/systemd/network# cat vlan10.network [Match] Name=vlan10 [Network] Bridge=br-mgmt root@hydrogen:/etc/systemd/network# cat br-mgmt.netdev [NetDev] Name=br-mgmt Kind=bridge root@hydrogen:/etc/systemd/network# cat br-mgmt.network [Match] Name=br-mgmt [Network] Address=172.29.236.21/22 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1657837/+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 1378802] [NEW] update-manager Couldn't connect to accessibility bus
Public bug reported: ** (update-manager:7750): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-GxEtj3txBA: Connection refused Always happens when using update-manager.. System originally installed from Trusty media, upgraded to Utopic. Happened in both. Amongst kernels used are: 3.15, 3.16.0.20, 3.17. Same error. Current kernel: Linux ps01lnx 3.17.0-031700-generic #201410060605 SMP Mon Oct 6 10:07:09 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Description:Ubuntu Utopic Unicorn (development branch) Release:14.10 dbus: Installed: 1.8.8-1ubuntu2 Candidate: 1.8.8-1ubuntu2 Version table: *** 1.8.8-1ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: dbus 1.8.8-1ubuntu2 Uname: Linux 3.17.0-031700-generic x86_64 ApportVersion: 2.14.7-0ubuntu5 Architecture: amd64 Date: Wed Oct 8 08:28:33 2014 InstallationDate: Installed on 2014-07-01 (98 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: dbus UpgradeStatus: No upgrade log present (probably fresh install) upstart.dbus.log: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. ** Affects: dbus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1378802 Title: update-manager Couldn't connect to accessibility bus Status in “dbus” package in Ubuntu: New Bug description: ** (update-manager:7750): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-GxEtj3txBA: Connection refused Always happens when using update-manager.. System originally installed from Trusty media, upgraded to Utopic. Happened in both. Amongst kernels used are: 3.15, 3.16.0.20, 3.17. Same error. Current kernel: Linux ps01lnx 3.17.0-031700-generic #201410060605 SMP Mon Oct 6 10:07:09 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Description: Ubuntu Utopic Unicorn (development branch) Release: 14.10 dbus: Installed: 1.8.8-1ubuntu2 Candidate: 1.8.8-1ubuntu2 Version table: *** 1.8.8-1ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: dbus 1.8.8-1ubuntu2 Uname: Linux 3.17.0-031700-generic x86_64 ApportVersion: 2.14.7-0ubuntu5 Architecture: amd64 Date: Wed Oct 8 08:28:33 2014 InstallationDate: Installed on 2014-07-01 (98 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: dbus UpgradeStatus: No upgrade log present (probably fresh install) upstart.dbus.log: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1378802/+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
