[Touch-packages] [Bug 991666] Re: VPN Connects Successfully Then Shortly Thereafter Fails
On 14.04 experiencing the same problem. After I try to connect to my VPN in a matter of a few seconds after the successful connection I get disconnected. Following this post http://tdanas.blogspot.co.uk/2015/01 /ubuntu-vpn-connects-successfully-and.html I decide to see what are my routing tables while the connection is on. Results are: Destination Gateway Genmask Flags Metric Ref Use Iface default * 0.0.0.0 U 0 00 ppp0 cyrano2.cs.ucl.172.17.31.1 255.255.255.255 UGH 0 00 wlan0 cyrano2.cs.ucl.172.17.31.1 255.255.255.255 UGH 0 00 wlan0 winvpn11.cs.ucl * 255.255.255.255 UH 0 0 0 ppp0 172.17.31.0 * 255.255.255.0U 9 00 wlan0 I do not know how it works but having a duplicate entry in the routing table might be the cause of the problem. -- 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/991666 Title: VPN Connects Successfully Then Shortly Thereafter Fails Status in NetworkManager-PPTP: New Status in network-manager package in Ubuntu: Confirmed Bug description: I am able to successfully establish a PPTP VPN connection in Ubuntu 12.04 (kernel 3.2.0-24-generic) but after approximately 30 seconds to 1.5 minutes it will fail. During the connection time I am only able to load about 1-2 webpages and then they freeze and I cannot access resources on the VPN network. I do not believe this is related to my VPN server as I am able to establish VPN connections with my Windows machines and Smartphones all day long with no problems. Is there a solution to this problem? Description: Ubuntu 12.04 LTS Release: 12.04 network-manager: 0.9.4.0-0ubuntu3 Here is the syslog: Apr 30 00:17:50 satellite-p755 NetworkManager[994]: info Starting VPN service 'pptp'... Apr 30 00:17:50 satellite-p755 NetworkManager[994]: info VPN service 'pptp' started (org.freedesktop.NetworkManager.pptp), PID 15069 Apr 30 00:17:50 satellite-p755 NetworkManager[994]: info VPN service 'pptp' appeared; activating connections Apr 30 00:17:50 satellite-p755 NetworkManager[994]: info VPN plugin state changed: starting (3) Apr 30 00:17:51 satellite-p755 NetworkManager[994]: info VPN connection 'Schaefer Law Group' (Connect) reply received. Apr 30 00:17:51 satellite-p755 pppd[15073]: Plugin /usr/lib/pppd/2.4.5/nm-pptp-pppd-plugin.so loaded. Apr 30 00:17:51 satellite-p755 pppd[15073]: pppd 2.4.5 started by root, uid 0 Apr 30 00:17:51 satellite-p755 pppd[15073]: Using interface ppp0 Apr 30 00:17:51 satellite-p755 pppd[15073]: Connect: ppp0 -- /dev/pts/2 Apr 30 00:17:51 satellite-p755 NetworkManager[994]:SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/ppp0, iface: ppp0) Apr 30 00:17:51 satellite-p755 NetworkManager[994]:SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/ppp0, iface: ppp0): no ifupdown configuration found. Apr 30 00:17:51 satellite-p755 pptp[15076]: nm-pptp-service-15069 log[main:pptp.c:314]: The synchronous pptp option is NOT activated Apr 30 00:17:51 satellite-p755 pptp[15084]: nm-pptp-service-15069 log[ctrlp_rep:pptp_ctrl.c:251]: Sent control packet type is 1 'Start-Control-Connection-Request' Apr 30 00:17:51 satellite-p755 pptp[15084]: nm-pptp-service-15069 log[ctrlp_disp:pptp_ctrl.c:739]: Received Start Control Connection Reply Apr 30 00:17:51 satellite-p755 pptp[15084]: nm-pptp-service-15069 log[ctrlp_disp:pptp_ctrl.c:773]: Client connection established. Apr 30 00:17:52 satellite-p755 pptp[15084]: nm-pptp-service-15069 log[ctrlp_rep:pptp_ctrl.c:251]: Sent control packet type is 7 'Outgoing-Call-Request' Apr 30 00:17:52 satellite-p755 pptp[15084]: nm-pptp-service-15069 log[ctrlp_disp:pptp_ctrl.c:858]: Received Outgoing Call Reply. Apr 30 00:17:52 satellite-p755 pptp[15084]: nm-pptp-service-15069 log[ctrlp_disp:pptp_ctrl.c:897]: Outgoing call established (call ID 0, peer's call ID 0). Apr 30 00:17:55 satellite-p755 pppd[15073]: CHAP authentication succeeded Apr 30 00:17:55 satellite-p755 pppd[15073]: MPPE 128-bit stateless compression enabled Apr 30 00:17:55 satellite-p755 pppd[15073]: local IP address 192.168.1.20 Apr 30 00:17:55 satellite-p755 pppd[15073]: remote IP address 192.168.1.1 Apr 30 00:17:55 satellite-p755 pppd[15073]: primary DNS address 8.8.8.8 Apr 30 00:17:55 satellite-p755 pppd[15073]: secondary DNS address 8.8.4.4 Apr 30 00:17:55 satellite-p755 NetworkManager[994]: info VPN connection 'Schaefer Law Group' (IP Config Get) reply received. Apr 30 00:17:55 satellite-p755 NetworkManager[994]: info VPN Gateway: 75.75.79.330 Apr 30 00:17:55 satellite-p755
[Touch-packages] [Bug 1311316] Re: After locking screen there is no input field to type password for unlock
Can any of the people still experiencing the problems to add 'debug' to in /etc/pam.d/unity to each of the modules used and potentially post some of their /var/log/auth.log. For me I found this is an issue of the PAM module for fprtind giving me: Feb 23 12:52:23 botev-ThinkPad-T440 unity[2008]: pam_fprintd(unity): get_devices failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Bug description: *** IMPORTANT ** *** The fix is not included in TRUSTY. Will be included with next SRU. *** If you can reproduce this bug please be sure to provide the following info: 1. Do you use a multi-head setup? If yes, using just one monitor fixes the issue? 2. Can you reproduce all the time? 3. Do you use ldap? If yes, using gnome-screensaver fix the issue (see comment #115) can you still reproduce that? 4. Please consider posting /var/log/auth.log (at least part of it, should not contain sensitive information) 5. Please specify the unity version *** END IMPORTANT ** Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+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 1311316] Re: After locking screen there is no input field to type password for unlock
So you just add it to the end of the line of an entry, of course monitor the /var/log/auth.log, as this means you are passing it as an argument, which might not be valid for all packages(its a common practice to be tough, but who knows). For instance my /etc/pam.d/common-auth looks like this: # # /etc/pam.d/common-auth - authentication settings common to all services # # This file is included from other service-specific PAM config files, # and should contain a list of the authentication modules that define # the central authentication scheme for use on the system # (e.g., /etc/shadow, LDAP, Kerberos, etc.). The default is to use the # traditional Unix authentication mechanisms. # # As of pam 1.0.1-6, this file is managed by pam-auth-update by default. # To take advantage of this, it is recommended that you configure any # local modules either before or after the default block, and use # pam-auth-update to manage selection of other modules. See # pam-auth-update(8) for details. # here are the per-package modules (the Primary block) auth[success=2 default=ignore] pam_fprintd.so max_tries=1 timeout=10 debug auth[success=1 default=ignore] pam_unix.so nullok_secure try_first_pass debug # here's the fallback if no module succeeds authrequisite pam_deny.so # prime the stack with a positive return value if there isn't one already; # this avoids us returning an error just because nothing sets a success code # since the modules above will each just jump around authrequiredpam_permit.so # and here are more per-package modules (the Additional block) authoptionalpam_cap.so # end of pam-auth-update config If you want full debug some packages (including fprintd) would require to be compiled from source with a debug flag on. Even without that, enabling debug can produce some usefull stuff in the auth.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Bug description: *** IMPORTANT ** *** The fix is not included in TRUSTY. Will be included with next SRU. *** If you can reproduce this bug please be sure to provide the following info: 1. Do you use a multi-head setup? If yes, using just one monitor fixes the issue? 2. Can you reproduce all the time? 3. Do you use ldap? If yes, using gnome-screensaver fix the issue (see comment #115) can you still reproduce that? 4. Please consider posting /var/log/auth.log (at least part of it, should not contain sensitive information) 5. Please specify the unity version *** END IMPORTANT ** Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+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 1311316] Re: After locking screen there is no input field to type password for unlock
I have the same bug as described on my fresh install of Ubuntu 14.04, however I'm with a newer kernel because of problems with my wifi drivers in previous versions, which were fixed: Linux 3.17.3-031703-generic #201411141335 SMP Fri Nov 14 18:36:40 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Ubuntu 14.04.1 LTS 14.04 trusty The problem is reproducible multiple times. After closing the laptop lid and going in suspend for a longer period, when opened the laptop displays the welcome screen with my wallpaper, but does not have any field to enter password. Clicking any sound/lang icons on the menu bar does not help, but waiting for a bit of time does. Diagnostics so far: So I dig a bit myself and looked at the log of lightdm, with the problem occurring here: [+0.28s] DEBUG: Session pid=1224: Running command /usr/lib/lightdm/lightdm-greeter-session /usr/sbin/unity-greeter [+0.28s] DEBUG: Creating shared data directory /var/lib/lightdm-data/lightdm [+0.28s] DEBUG: Session pid=1224: Logging to /var/log/lightdm/x-0-greeter.log [+0.33s] DEBUG: Activating VT 7 [+0.33s] DEBUG: Activating login1 session c1 [+0.45s] DEBUG: Session pid=1224: Greeter connected version=1.10.3 [+0.60s] DEBUG: Session pid=1224: Greeter start authentication for alex [+0.60s] DEBUG: Session pid=1283: Started with service 'lightdm', username 'alex' [+1.67s] DEBUG: Session pid=1283: Got 1 message(s) from PAM [+1.67s] DEBUG: Session pid=1224: Prompt greeter with 1 message(s) [+3.49s] DEBUG: Session pid=1283: Authentication complete with return value 0: Success As can be seen the period 0.60-1.67 is just waiting for the PAM service to respond (1 minute wait). I typed my password asap as it was available, so my guess is it is connected with the PAM service. I will look into it, but if someone has an idea why would be great. The /var/log/auth.log does not contain any useful information for the why the problem is occurring. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Bug description: *** IMPORTANT ** *** The fix is not included in TRUSTY. Will be included with next SRU. *** If you can reproduce this bug please be sure to provide the following info: 1. Do you use a multi-head setup? If yes, using just one monitor fixes the issue? 2. Can you reproduce all the time? 3. Do you use ldap? If yes, using gnome-screensaver fix the issue (see comment #115) can you still reproduce that? 4. Please consider posting /var/log/auth.log (at least part of it, should not contain sensitive information) 5. Please specify the unity version *** END IMPORTANT ** Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+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 1311316] Re: After locking screen there is no input field to type password for unlock
Also if you could answer the question in #108 this could help us a lot to further debug if necessary the PAM module. And to add, I'm also using a finger print reader (fprintd) as an authentication before the password, but there are some interesting facts about it(before anyone jump and point fingers there): It has a timeout of 10s, the wait for the password text area is ~1 min If I suspend the laptop manually and wake it it uses the fingerprint reader normally. If I close the lid and open it - the finger print reader authentication is not available and the bug occurs. Conclusion: Possibly the fprintd.so library is not loaded for some reason on lid open, or the PAM module encounters some problems, after which it falls back (somehow) to the unix password. Again if you answer #108 would be most appreciated. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Bug description: *** IMPORTANT ** *** The fix is not included in TRUSTY. Will be included with next SRU. *** If you can reproduce this bug please be sure to provide the following info: 1. Do you use a multi-head setup? If yes, using just one monitor fixes the issue? 2. Can you reproduce all the time? 3. Do you use ldap? If yes, using gnome-screensaver fix the issue (see comment #115) can you still reproduce that? 4. Please consider posting /var/log/auth.log (at least part of it, should not contain sensitive information) 5. Please specify the unity version *** END IMPORTANT ** Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+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
