[Bug 1314058] Re: app_stack.so: undefined symbol: ast_agi_unregister

2015-01-11 Thread Nick Piggott
I can confirm the workaround in #8 works for me. Thanks, much appreciated. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1314058 Title: app_stack.so: undefined symbol: ast_agi_unregister To manage

[Bug 1314058] Re: app_stack.so: undefined symbol: ast_agi_unregister

2015-01-05 Thread Nick Piggott
I'm running Ubuntu 14.04 with Asterisk 11.7.0~dfsg-1ubuntu1 and FreePBX 12.0.25. app_stack.so will not load at boot, either autoloading or with a specific load directive in the startup scripts. I can load it manually by connecting to the asterisk console ("sudo asterisk -r") and then manually typ

[Bug 1314095] Re: Unity Lockscreen in 14.04 can't unlock when using LDAP account

2014-05-31 Thread Nick Piggott
I can confirm I'm using libpam-ldapd:amd64 (0.8.13-3) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1314095 Title: Unity Lockscreen in 14.04 can't unlock when using LDAP account To manage notificat

[Bug 1314095] Re: Unity Lockscreen in 14.04 can't unlock when using LDAP account

2014-05-25 Thread Nick Piggott
Workaround in #2 also working for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1314095 Title: Unity Lockscreen in 14.04 can't unlock when using LDAP account To manage notifications about this

[Bug 1315648] [NEW] LDAP user can't unlock screensaver

2014-05-03 Thread Nick Piggott
Public bug reported: Ubuntu 14.04 LTS (3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux) - Upgrade from 13.10 to 14.04 LTS - Screensaver configured to trigger after 5 minutes, and requires password to unlock - Screensaver triggers - User name is show

[Bug 799605] Re: pam-auth-update creates a 'common-account' that fails with cached logins

2012-06-19 Thread Nick Piggott
** PLEASE IGNORE THE ABOVE COMMENT ** It's the wrong common-account. This is the correct one: # here are the per-package modules (the "Primary" block) account [success=2 new_authtok_reqd=done default=ignore]pam_unix.so account [success=1 authinfo_unavail=1 default=ignore] pam_ldap.so

[Bug 799605] Re: pam-auth-update creates a 'common-account' that fails with cached logins

2012-06-19 Thread Nick Piggott
I've subsequently implemented a slightly more elegant solution: # here are the per-package modules (the "Primary" block) account [success=2 new_authtok_reqd=done default=ignore]pam_unix.so account [success=1 default=ignore] pam_ldap.so # here's the fallback if no module succeeds acc

[Bug 799605] Re: pam-auth-update creates a 'common-account' that fails with cached logins

2011-06-20 Thread Nick Piggott
I agree that cached shadow would enable pam_unix to operate correctly. As far as I'm aware, nss_updatedb does not support local caching of shadow, only passwd and group, and the db option can't be used on the shadow entry (only files and ldap) in nsswitch.conf. I presume that's because of security

[Bug 799605] [NEW] pam-auth-update creates a 'common-account' that fails with cached logins

2011-06-19 Thread Nick Piggott
Public bug reported: Running Ubuntu 11.04 on a Dell Mini 1018 Netbook On a system running LDAP, Kerberos and Cached Credentials, pam-auth- update creates a 'common-account' file that will always fail if the machine uses cached credentials (presumably because it's offline). The relevant lines fro

[Bug 294977] Re: not clear how to configure with pam-auth-update

2011-01-08 Thread Nick Piggott
The common-account created by pam-auth-update when configuring for cached credentials is failing on my stock Ubuntu Maverick 10.10 install. The common-account created by pam-auth-update is: # here are the per-package modules (the "Primary" block) account [success=2 new_authtok_reqd=done default=i

[Bug 339891] Re: [Jaunty] wireless rt2860 not connecting to WPA

2009-06-10 Thread Nick Piggott
Confirming that my system: * eee 901 * Ubuntu Jaunty 9.04 * kernel 2.6.28-11-generic was unable to connect to WPA2 networks with mixed AES/TKIP encryprtion. Application of the patch in comment #47 and updated at comment#72 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/339891/comments/72

[Bug 309767] Re: Calendar entries created by Evolution on Exchange 2003 do not sync to Nokia handset

2009-01-12 Thread Nick Piggott
** Bug watch added: GNOME Bug Tracker #567534 http://bugzilla.gnome.org/show_bug.cgi?id=567534 ** Also affects: evolution via http://bugzilla.gnome.org/show_bug.cgi?id=567534 Importance: Unknown Status: Unknown -- Calendar entries created by Evolution on Exchange 2003 do not sync

[Bug 309767] Re: Calendar entries created by Evolution on Exchange 2003 do not sync to Nokia handset

2009-01-12 Thread Nick Piggott
Still having the same problem with Intrepid (8.10) and Evolution (2.24.2). Have sent upstream to Gnome / Evolution, and will bug link here. -- Calendar entries created by Evolution on Exchange 2003 do not sync to Nokia handset https://bugs.launchpad.net/bugs/309767 You received this bug notifica

[Bug 309767] Re: Calendar entries created by Evolution on Exchange 2003 do not sync to Nokia handset

2008-12-19 Thread Nick Piggott
Created a calendar entry in Evolution, then checked it was visible in Outlook and Webmail. Have grabbed two debugs from the phone (attached) According to the "admin_log.txt" file attached, the sync noticed that something had changed in the Calendar, and initiated a sync - but no changes were made

[Bug 309767] Re: Calendar entries created by Evolution on Exchange 2003 do not sync to Nokia handset

2008-12-19 Thread Nick Piggott
This is the "pdu.txt" file ** Attachment added: "A pdu.txt debug file, drawn from the Nokia handset "Mail for Exchange" folder" http://launchpadlibrarian.net/20580959/pdu_log.txt -- Calendar entries created by Evolution on Exchange 2003 do not sync to Nokia handset https://bugs.launchpad.ne

[Bug 309767] Re: Calendar entries created by Evolution on Exchange 2003 do not sync to Nokia handset

2008-12-19 Thread Nick Piggott
In this example, I have created an entry using Microsoft Webmail The Admin_log file seems very similar (I had to start the sync manually because it was after my automatic sync period of 08:00 - 18:00), but shows 1 entry correctly added to the phone. ** Attachment added: "admin_log1.txt" http:/

[Bug 309767] Re: Calendar entries created by Evolution on Exchange 2003 do not sync to Nokia handset

2008-12-19 Thread Nick Piggott
But the pdu_log.txt is very different. A whole set of cal: fields has appeared, with the *most* bizarre time zone information. ** Attachment added: "pdu_log.txt" http://launchpadlibrarian.net/20581062/pdu_log.txt -- Calendar entries created by Evolution on Exchange 2003 do not sync to Nokia