[Touch-packages] [Bug 919200] Re: Doesn't know system default layout/variant
*** This bug is a duplicate of bug 1051288 *** https://bugs.launchpad.net/bugs/1051288 ** This bug has been marked a duplicate of bug 1051288 LightDM assumes there's only ONE system default layout -- 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/919200 Title: Doesn't know system default layout/variant Status in Light Display Manager: Fix Released Status in lightdm package in Ubuntu: Triaged Bug description: lightdm_get_layout does not return the correct system default keyboard layout/variant. For that, pitti says we need to access xkl_config->layouts[0]/xkl_config->variants[0]. Currently, we just grab the first layout returned from xkl_config_registry_foreach_layout, which only returns the available layouts, not the configured layouts. So "us" will always be first there. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/919200/+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 1666256] Re: Mouse Pointer flicking and blocked after locked screen with two displays
** Also affects: lightdm (Ubuntu) Importance: Undecided Status: New -- 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/1666256 Title: Mouse Pointer flicking and blocked after locked screen with two displays Status in light-locker package in Ubuntu: New Status in lightdm package in Ubuntu: New Status in xorg-hwe-16.04 package in Ubuntu: New Status in xserver-xorg-video-intel-hwe-16.04 package in Ubuntu: New Bug description: After upgrading to the HWE (Xubuntu 16.04.2) I am experiencing sometimes the following bug: When the screen is locked, I wake the displays up. The mouse pointer is flicking and cannot be moved. The keyboard is not responsive as well regarding the light locker. I can change to another terminal (via CTRL+ALT+F1) and quit the session. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: light-locker 1.7.0-2ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 Uname: Linux 4.8.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Feb 20 16:51:54 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-10 (893 days ago) InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140723) SourcePackage: light-locker UpgradeStatus: Upgraded to xenial on 2016-10-10 (133 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1666256/+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 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
Sorry, I mean in comment #20! -- 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/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS Status in systemd: New Status in systemd package in Ubuntu: Confirmed Bug description: I use a VPN configured with network-manager-openconnect-gnome in which a split-horizon DNS setup assigns different addresses to some names inside the remote network than the addresses seen for those names from outside the remote network. However, systemd-resolved often decides to ignore the VPN’s DNS servers and use the local network’s DNS servers to resolve names (whether in the remote domain or not), breaking the split-horizon DNS. This related bug, reported by Lennart Poettering himself, was closed with the current Fedora release at the time reaching EOL: https://bugzilla.redhat.com/show_bug.cgi?id=1151544 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1624317/+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 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
I can confirm that using the workaround in #6 makes the VPN operable again. -- 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/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS Status in systemd: New Status in systemd package in Ubuntu: Confirmed Bug description: I use a VPN configured with network-manager-openconnect-gnome in which a split-horizon DNS setup assigns different addresses to some names inside the remote network than the addresses seen for those names from outside the remote network. However, systemd-resolved often decides to ignore the VPN’s DNS servers and use the local network’s DNS servers to resolve names (whether in the remote domain or not), breaking the split-horizon DNS. This related bug, reported by Lennart Poettering himself, was closed with the current Fedora release at the time reaching EOL: https://bugzilla.redhat.com/show_bug.cgi?id=1151544 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1624317/+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 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
Here is my output for @piti: Positive Trust Anchors: . IN DS19036 8 2 49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5 Negative trust anchors: 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa 168.192.in-addr.arpa corp home internal intranet lan local private test Using system hostname 'Thinkpad-T440s'. New scope on link *, protocol dns, family * Found new link 3/wlan0 Found new link 2/eth0 Found new link 1/lo New scope on link eth0, protocol llmnr, family AF_INET6 Excercising transaction 8616 for on scope llmnr on eth0/AF_INET6. Delaying llmnr transaction for 4242us. New scope on link eth0, protocol llmnr, family AF_INET Excercising transaction 28149 for on scope llmnr on eth0/AF_INET. Delaying llmnr transaction for 51982us. Sent message type=method_call sender=n/a destination=org.freedesktop.DBus object=/org/freedesktop/DBus interface=org.freedesktop.DBus member=Hello cookie=1 reply_cookie=0 error=n/a Got message type=method_return sender=org.freedesktop.DBus destination=:1.128 object=n/a interface=n/a member=n/a cookie=1 reply_cookie=1 error=n/a Sent message type=method_call sender=n/a destination=org.freedesktop.DBus object=/org/freedesktop/DBus interface=org.freedesktop.DBus member=RequestName cookie=2 reply_cookie=0 error=n/a Got message type=method_return sender=org.freedesktop.DBus destination=:1.128 object=n/a interface=n/a member=n/a cookie=4 reply_cookie=2 error=n/a Sent message type=method_call sender=n/a destination=org.freedesktop.DBus object=/org/freedesktop/DBus interface=org.freedesktop.DBus member=AddMatch cookie=3 reply_cookie=0 error=n/a Got message type=method_return sender=org.freedesktop.DBus destination=:1.128 object=n/a interface=n/a member=n/a cookie=5 reply_cookie=3 error=n/a Switching to system DNS server 127.0.1.1. Got message type=signal sender=org.freedesktop.DBus destination=:1.128 object=/org/freedesktop/DBus interface=org.freedesktop.DBus member=NameAcquired cookie=2 reply_cookie=0 error=n/a Got message type=signal sender=org.freedesktop.DBus destination=:1.128 object=/org/freedesktop/DBus interface=org.freedesktop.DBus member=NameAcquired cookie=3 reply_cookie=0 error=n/a Timeout reached on transaction 8616. Retrying transaction 8616. Excercising transaction 8616 for on scope llmnr on eth0/AF_INET6. Sending query packet with id 8616 on interface 2/AF_INET6. Timeout reached on transaction 28149. Retrying transaction 28149. Excercising transaction 28149 for on scope llmnr on eth0/AF_INET. Sending query packet with id 28149 on interface 2/AF_INET. Got LLMNR query packet for id 8616 Sending response packet with id 8616 on interface 2/AF_INET6. Got LLMNR query packet for id 28149 Sending response packet with id 28149 on interface 2/AF_INET. Got LLMNR reply packet for id 8616 Processing incoming packet on transaction 8616. Got LLMNR reply packet for id 28149 Processing incoming packet on transaction 28149. Timeout reached on transaction 8616. Retrying transaction 8616. Excercising transaction 8616 for on scope llmnr on eth0/AF_INET6. Sending query packet with id 8616 on interface 2/AF_INET6. Timeout reached on transaction 28149. Retrying transaction 28149. Excercising transaction 28149 for on scope llmnr on eth0/AF_INET. Sending query packet with id 28149 on interface 2/AF_INET. Got LLMNR query packet for id 8616 Sending response packet with id 8616 on interface 2/AF_INET6. Got LLMNR query packet for id 28149 Sending response packet with id 28149 on interface 2/AF_INET. Got LLMNR reply packet for id 8616 Processing incoming packet on transaction 8616. Got LLMNR reply packet for id 28149 Processing incoming packet on transaction 28149. Timeout reached on transaction 8616. Retrying transaction 8616. Excercising transaction 8616 for on scope llmnr on eth0/AF_INET6. Sending query packet with id 8616 on interface 2/AF_INET6. Timeout reached on transaction 28149. Retrying transaction 28149. Excercising transaction 28149 for on scope llmnr on eth0/AF_INET. Sending query packet with id 28149 on interface 2/AF_INET. Got LLMNR query packet for id 8616 Sending response packet with id 8616 on interface 2/AF_INET6. Got LLMNR query packet for id 28149 Sending response packet with id 28149 on interface 2/AF_INET. Got LLMNR reply packet for id 8616 Processing incoming packet on transaction 8616. Got LLMNR reply packet for id 28149 Processing incoming packet on transaction 28149. Timeout reached on transaction 8616. Retrying transaction 8616. Transaction 8616 for on scope llmnr on eth0/AF_INET6 now complete with from none (unsigned). Record Thinkpad-T440s. IN fe80::95eb:8e44:c908:cafc successfully probed. Freeing transaction 8616. Timeout reached on
[Touch-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
Same problem with VPNC and 16.04.2. Worked before on fresh upgrade to 16.04.0. At the moment I am not able to work remote. Please fix this! ** Tags added: xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS Status in systemd: New Status in systemd package in Ubuntu: Confirmed Bug description: I use a VPN configured with network-manager-openconnect-gnome in which a split-horizon DNS setup assigns different addresses to some names inside the remote network than the addresses seen for those names from outside the remote network. However, systemd-resolved often decides to ignore the VPN’s DNS servers and use the local network’s DNS servers to resolve names (whether in the remote domain or not), breaking the split-horizon DNS. This related bug, reported by Lennart Poettering himself, was closed with the current Fedora release at the time reaching EOL: https://bugzilla.redhat.com/show_bug.cgi?id=1151544 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1624317/+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
