[Bug 1289961] Re: 8086:08b2 [Lenovo ThinkPad T440s] Power management causes Intel wifi 7260 slowness
I can confirm the problem, and also tried to update the kernel to 3.17.3 and use the latest driver 23.11.10.0, but the speed was still much lower than using the 22.24.8.0 so I reverted back. Hope it is resolved. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1289961 Title: 8086:08b2 [Lenovo ThinkPad T440s] Power management causes Intel wifi 7260 slowness To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1289961/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/991666 Title: VPN Connects Successfully & Then Shortly Thereafter Fails To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager-pptp/+bug/991666/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1424368] [NEW] fprintd - Problem after resuming from LID closed
Public bug reported: Hi, So I got this error as I described on the mailing of fprintd: So I have the problem that often after LID open it seems that fprintd does not seem to respond to the PAM module, thus I have about 30 sec of no way of logging in my session, which is a bit frustrating - I get the screen, but no option for finger verification or password. After ~30-40sec I get the password field finally, but note that fprintd has 10 sec timeout in the PAM module. After putting out debug on I got this: Feb 21 10:04:44 botev-ThinkPad-T440 systemd-logind[556]: Lid closed. Feb 21 10:04:44 botev-ThinkPad-T440 systemd-logind[556]: Suspending... Feb 21 10:16:06 botev-ThinkPad-T440 unity[2100]: pam_fprintd(unity): timeout specified as: 10 Feb 21 10:16:06 botev-ThinkPad-T440 systemd-logind[556]: Operation finished. Feb 21 10:16:06 botev-ThinkPad-T440 systemd-logind[556]: Lid opened. Feb 21 10:16:32 botev-ThinkPad-T440 unity[2100]: 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. Any idea how to fix this or what exactly is the issue? *** As suggest by Vasily Khoruzhick, I'm posting this here after I recompiled libfprintd and fprintd with debug on for more logging. Also note that I now I use 0.6.0 rather than 0.5.1. The error is still there, but now I have more logs (hope they help someone): Feb 22 00:51:43 botev-ThinkPad-T440 systemd-logind[588]: Lid closed. Feb 22 00:51:43 botev-ThinkPad-T440 systemd-logind[588]: Suspending... Feb 22 00:51:43 botev-ThinkPad-T440 systemd-logind[588]: Removed session c1. Feb 22 00:51:43 botev-ThinkPad-T440 unity[2193]: pam_fprintd(unity): Using device /net/reactivated/Fprint/Device/0 Feb 22 10:43:31 botev-ThinkPad-T440 unity[2193]: pam_fprintd(unity): verify_finger_selected Swipe your finger across the fingerprint reader Feb 22 10:43:32 botev-ThinkPad-T440 unity[2193]: pam_fprintd(unity): Verify result: verify-unknown-error Feb 22 10:43:32 botev-ThinkPad-T440 systemd-logind[588]: Operation finished. Feb 22 10:43:32 botev-ThinkPad-T440 systemd-logind[588]: Lid opened. Feb 22 10:43:57 botev-ThinkPad-T440 unity[2193]: pam_fprintd(unity): ReleaseDevice 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. Feb 22 10:44:22 botev-ThinkPad-T440 sudo[3507]: pam_fprintd(sudo): Using device /net/reactivated/Fprint/Device/0 Feb 22 10:44:23 botev-ThinkPad-T440 sudo[3507]: pam_fprintd(sudo): verify_finger_selected Swipe your finger across the fingerprint reader Feb 22 10:45:00 botev-ThinkPad-T440 sudoedit[3507]: pam_unix(sudo:auth): conversation failed Feb 22 10:45:00 botev-ThinkPad-T440 sudoedit[3507]: pam_unix(sudo:auth): unable to obtain a password Feb 22 10:45:00 botev-ThinkPad-T440 sudoedit[3507]: pam_unix(sudo:auth): auth could not identify password for [alex] Feb 22 10:53:48 botev-ThinkPad-T440 gnome-keyring-daemon[1855]: couldn't allocate secure memory to keep passwords and or keys from being written to the disk Info: Description:Ubuntu 14.04.2 LTS Release:14.04 fprintd and libfprintd - 0.6.0 - compiled from source - http://lists.freedesktop.org/archives/fprint/2015-February/000675.html ** Affects: fprintd (Ubuntu) Importance: Undecided Status: New ** Tags: fprintd pam-fprintd -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1424368 Title: fprintd - Problem after resuming from LID closed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1424368/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
