[Desktop-packages] [Bug 1774447] Re: Approx. 50% of tap to clicks does not work since upgrade to Ubuntu 18.04
Well, after uninstalling xserver-xorg-input-synaptics it seems to be working fine. At least short testing looks promising. Bud bad is two- finger scrolling stopped working. I can only switch to edge scrolling, which works, but when two-finger scrolling is enabled, it does not work. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1774447 Title: Approx. 50% of tap to clicks does not work since upgrade to Ubuntu 18.04 Status in xserver-xorg-input-synaptics package in Ubuntu: New Bug description: Since upgrade from Ubuntu 17.10 to Ubuntu 18.04 I have issues with tap to click. Approximately 50% of taps does not work as clicks. I do not know if it is general issue or an issue related to my HW (Lenovo L450) but it is very annoying. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libinput10 1.10.4-1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 31 17:38:44 2018 DistUpgraded: 2018-05-04 10:19:30,946 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.10, 4.15.0-20-generic, x86_64: installed virtualbox, 5.2.10, 4.15.0-22-generic, x86_64: installed GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:503c] InstallationDate: Installed on 2015-10-05 (968 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: LENOVO 20DT0003XS ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=0ff426ff-3b6c-433c-81a3-8a8a4116c973 ro SourcePackage: libinput UpgradeStatus: Upgraded to bionic on 2018-05-04 (27 days ago) dmi.bios.date: 03/16/2016 dmi.bios.vendor: LENOVO dmi.bios.version: JDET57WW (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: Intel powered classmate PC dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJDET57WW(1.19):bd03/16/2016:svnLENOVO:pn20DT0003XS:pvrThinkPadL450:rvnLENOVO:rnIntelpoweredclassmatePC:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L450 dmi.product.name: 20DT0003XS dmi.product.version: ThinkPad L450 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sat Jan 20 21:06:39 2018 xserver.configfile: default xserver.errors: Error loading keymap /var/lib/xkb/server-0.xkm Error loading keymap /var/lib/xkb/server-0.xkm XKB: Failed to load keymap. Loading default keymap instead. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1094 vendor LGD xserver.version: 2:1.19.3-1ubuntu1.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1774447/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1682918] [NEW] Different than default keyboard layout can't be used in login screen of Ubuntu 17.04
Public bug reported: I upgraded from Ubuntu 16.04 to 16.10 and immediately from 16.10 to 17.04. I had and also have SK and US keyboard layouts defined. I noticed after boot in the login screen, for entering the password, only the keyboard layout defined in /etc/default/keyboard, works (in my case it is US). When I select different layout via indicator (I select SK keyboard layout), only the one defined in the /etc/default/keyboard (US layout) is used. Once I am logged in and use Ctrl+Alt+L for locking the screen, then all layouts works. So the problem is only after boot and I noticed the problem is also when switching to not logged other user. Steps for reproducing: 1. Have installed Ubuntu 16.04 LTS and define SK and US layout via "Text entry" 2. Upgrade from Ubuntu 16.04 LTS to 16.10 and immediately upgrade from 16.10 to 17.04 3. Reboot your PC and notice only one keyboard layout works in the login screen (the layout which is defined in /etc/default/keyboard) ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: lightdm 1.22.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Fri Apr 14 21:47:51 2017 InstallationDate: Installed on 2015-10-05 (557 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: lightdm UpgradeStatus: Upgraded to zesty on 2017-04-14 (0 days ago) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1682918 Title: Different than default keyboard layout can't be used in login screen of Ubuntu 17.04 Status in lightdm package in Ubuntu: New Bug description: I upgraded from Ubuntu 16.04 to 16.10 and immediately from 16.10 to 17.04. I had and also have SK and US keyboard layouts defined. I noticed after boot in the login screen, for entering the password, only the keyboard layout defined in /etc/default/keyboard, works (in my case it is US). When I select different layout via indicator (I select SK keyboard layout), only the one defined in the /etc/default/keyboard (US layout) is used. Once I am logged in and use Ctrl+Alt+L for locking the screen, then all layouts works. So the problem is only after boot and I noticed the problem is also when switching to not logged other user. Steps for reproducing: 1. Have installed Ubuntu 16.04 LTS and define SK and US layout via "Text entry" 2. Upgrade from Ubuntu 16.04 LTS to 16.10 and immediately upgrade from 16.10 to 17.04 3. Reboot your PC and notice only one keyboard layout works in the login screen (the layout which is defined in /etc/default/keyboard) ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: lightdm 1.22.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Fri Apr 14 21:47:51 2017 InstallationDate: Installed on 2015-10-05 (557 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: lightdm UpgradeStatus: Upgraded to zesty on 2017-04-14 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1682918/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1671606] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1
** Description changed: I use my company's cisco vpn via network-manager in Ubuntu 16.04.2 LTS. After recent upgrade of network-manager:amd64 from version 1.2.2-0ubuntu0.16.04.4 to version 1.2.6-0ubuntu0.16.04.1 DNS resolution of VPN's server hostnames does not work. Roll back to version 1.2.2-0ubuntu0.16.04.4 solves the problem. Steps for reproducing: 1. upgrade network-manager:amd64 from version 1.2.2-0ubuntu0.16.04.4 to version 1.2.6-0ubuntu0.16.04.1 2. connect to VPN via network-manager applet 3. nslookop servername.internal --> ** server can't find servername.internal: NXDOMAIN 4. disconnect from VPN via network-manager applet 5. roll back network-manager via command: sudo apt-get install network-manager=1.2.2-0ubuntu0.16.04.4 - 6. connect to VPN via network-manager applet - 7. nslookop servername.internal --> the server is resolved correctly + 6. restart network-manager via sudo service network-manager restart + 7. connect to VPN via network-manager applet + 8. nslookop servername.internal --> the server is resolved correctly ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 9 19:49:55 2017 InstallationDate: Installed on 2015-10-05 (520 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) NetworkManager.state: - [main] - NetworkingEnabled=true - WirelessEnabled=true - WWANEnabled=true - WimaxEnabled=true + [main] + NetworkingEnabled=true + WirelessEnabled=true + WWANEnabled=true + WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: - RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN - running 1.2.6connected started full enabled enabled enabled enabled enabled + RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN + running 1.2.6connected started full enabled enabled enabled enabled enabled -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1671606 Title: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1 Status in network-manager package in Ubuntu: New Bug description: I use my company's cisco vpn via network-manager in Ubuntu 16.04.2 LTS. After recent upgrade of network-manager:amd64 from version 1.2.2-0ubuntu0.16.04.4 to version 1.2.6-0ubuntu0.16.04.1 DNS resolution of VPN's server hostnames does not work. Roll back to version 1.2.2-0ubuntu0.16.04.4 solves the problem. Steps for reproducing: 1. upgrade network-manager:amd64 from version 1.2.2-0ubuntu0.16.04.4 to version 1.2.6-0ubuntu0.16.04.1 2. connect to VPN via network-manager applet 3. nslookop servername.internal --> ** server can't find servername.internal: NXDOMAIN 4. disconnect from VPN via network-manager applet 5. roll back network-manager via command: sudo apt-get install network-manager=1.2.2-0ubuntu0.16.04.4 6. restart network-manager via sudo service network-manager restart 7. connect to VPN via network-manager applet 8. nslookop servername.internal --> the server is resolved correctly ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 9 19:49:55 2017 InstallationDate: Installed on 2015-10-05 (520 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1671606/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1671606] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1
** Attachment removed: "JournalErrors.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1671606/+attachment/4834874/+files/JournalErrors.txt ** Attachment removed: "IwConfig.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1671606/+attachment/4834873/+files/IwConfig.txt ** Attachment removed: "CRDA.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1671606/+attachment/4834868/+files/CRDA.txt ** Attachment removed: "ProcEnviron.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1671606/+attachment/4834883/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1671606 Title: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1 Status in network-manager package in Ubuntu: New Bug description: I use my company's cisco vpn via network-manager in Ubuntu 16.04.2 LTS. After recent upgrade of network-manager:amd64 from version 1.2.2-0ubuntu0.16.04.4 to version 1.2.6-0ubuntu0.16.04.1 DNS resolution of VPN's server hostnames does not work. Roll back to version 1.2.2-0ubuntu0.16.04.4 solves the problem. Steps for reproducing: 1. upgrade network-manager:amd64 from version 1.2.2-0ubuntu0.16.04.4 to version 1.2.6-0ubuntu0.16.04.1 2. connect to VPN via network-manager applet 3. nslookop servername.internal --> ** server can't find servername.internal: NXDOMAIN 4. disconnect from VPN via network-manager applet 5. roll back network-manager via command: sudo apt-get install network-manager=1.2.2-0ubuntu0.16.04.4 6. connect to VPN via network-manager applet 7. nslookop servername.internal --> the server is resolved correctly ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 9 19:49:55 2017 InstallationDate: Installed on 2015-10-05 (520 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1671606/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
