Re: [Touch-packages] [Bug 1891548] Re: autofs-ldap's /etc/ldap/schema/autofs.schema crashes slapd

2020-08-20 Thread msp3k
Will do, thanks.Michael Peek On Thu, 2020-08-20 at 15:10 +, Paride Legovini wrote: > Hi Michael and thanks for all the digging. If I understand > correctlythere are two issues here: > 1. The slapd crash due to the caseExactMatch/caseExactIA5Match typo, > forwhich you submitted a fix upstream

[Touch-packages] [Bug 1891548] Re: autofs-ldap's /etc/ldap/schema/autofs.schema crashes slapd

2020-08-19 Thread msp3k
I didn't realize that this was considered unusual. AutoFs integration has been a critical part of our infrastructure across multiple departments at our university for decades, starting with NIS/NIS+. Without AutoFS integration we would be ... very, very sad. I have filed a bug report w/ Debian

Re: [Touch-packages] [Bug 1891548] Re: autofs-ldap's /etc/ldap/schema/autofs.schema crashes slapd

2020-08-14 Thread msp3k
As a follow-up, I figured out a workaround for the following error that I reported earlier: adding new entry "ou=auto.master,dc=example,dc=org"ldap_add: Invalid syntax (21) additional info: objectClass: value #1 invalid per syntax Original steps: 1) Install /etc/ldap/slapd.conf (which

[Touch-packages] [Bug 1891548] Re: autofs-ldap's /etc/ldap/schema/autofs.schema crashes slapd

2020-08-14 Thread msp3k
SORRY -- This is the correct autofs-fixed.schema. That last one was a file I was poking around with using a schema I found online. The only difference between this file and the one that ships with autofs-ldap is "caseExactMatch" -> "caseExactIA5Match". ** Attachment added: "autofs-fixed.schema"

[Touch-packages] [Bug 1891548] Re: autofs-ldap's /etc/ldap/schema/autofs.schema crashes slapd

2020-08-14 Thread msp3k
** Attachment added: "Replaced "exactCaseMatch" w/ "exactCaseIA5Match" to fix bug that caused slapd to crash on startup" https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1891548/+attachment/5401476/+files/autofs-fixed.schema -- You received this bug notification because you are a

[Touch-packages] [Bug 1891548] Re: autofs-ldap's /etc/ldap/schema/autofs.schema crashes slapd

2020-08-14 Thread msp3k
Attached is an example /etc/ldap/slapd.conf file that I'm working from. Maybe there's a problem in here somewhere that I'm not catching. Including it just in case. Database password is "superSecretPassword" -> "{MD5}Yy8s0xf5ONysHHbtpvA+ig==". The include for /etc/ldap/schema/autofs.schema has

[Touch-packages] [Bug 1891548] Re: autofs-ldap's /etc/ldap/schema/autofs.schema crashes slapd

2020-08-14 Thread msp3k
** Attachment added: "LDAP entries to recreate my test setup" https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1891548/+attachment/5401474/+files/input.ldif -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in

Re: [Touch-packages] [Bug 1530914] Re: sshd crashed with SIGSEGV in _IO_vfprintf_internal()

2016-10-27 Thread msp3k
I have not come across this bug yet in 16.04. It may have been fixed. Michael On 10/26/2016 06:08 PM, Joshua Powers wrote: > ** Changed in: openssh (Ubuntu) >Status: New => Incomplete > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages,

Re: [Touch-packages] [Bug 1575644] Re: resolvconf doesn't create the correct /etc/resolv.conf file when static IP addresses are used

2016-04-28 Thread msp3k
*** This bug is a duplicate of bug 1003842 *** https://bugs.launchpad.net/bugs/1003842 I reformatted over 14.04 and installed 16.04 as a fresh start. I use a slightly customized server install ISO image that includes my own preseed file for automation. My approach is to start with a

Re: [Touch-packages] [Bug 1575644] Re: resolvconf doesn't create the correct /etc/resolv.conf file when static IP addresses are used

2016-04-27 Thread msp3k
I'll give it a go and see if any problems occur. Thanks for your help! Michael On 04/27/2016 03:21 PM, Thomas Hood wrote: > That name service does not work properly when dnsmasq is installed is > most probably due to bug #1003842. If that is the case then if you > remove 8.8.8.8 from the list

Re: [Touch-packages] [Bug 1575644] Re: resolvconf doesn't create the correct /etc/resolv.conf file when static IP addresses are used

2016-04-27 Thread msp3k
No, it does not work when dnsmasq is installed. At least, not reliably. I discovered this when apache2 started ignoring the configuration for my virtual hosts because it couldn't resolve the virtual host names. I could reach some hosts, like archive.ubuntu.com for instance whenever I did an

Re: [Touch-packages] [Bug 1575644] Re: resolvconf doesn't create the correct /etc/resolv.conf file when static IP addresses are used

2016-04-27 Thread msp3k
Ah, I understand now. Sorry. Michael On 04/27/2016 12:42 PM, Thomas Hood wrote: > The answer to the question "shouldn't those DNS servers should be > included in /etc/resolv.conf regardless of the presence of dnsmasq?" is > "no". Resolvconf doesn't list any nameserver addresses after any >

Re: [Touch-packages] [Bug 1575644] Re: resolvconf doesn't create the correct /etc/resolv.conf file when static IP addresses are used

2016-04-27 Thread msp3k
/re-installed 16.04. Under 14.04 this wasn't a problem. This just started under 16.04. And the contents of my /etc/network/interfaces hasn't changed from 14.04. Michael On 04/27/2016 12:21 PM, msp3k wrote: > They are specified in /etc/network/interfaces just as you instruc

Re: [Touch-packages] [Bug 1575644] Re: resolvconf doesn't create the correct /etc/resolv.conf file when static IP addresses are used

2016-04-27 Thread msp3k
They are specified in /etc/network/interfaces just as you instructed, and the dnsmasq-base package is installed. But when dnsmasq is installed then resolvconf generates an incorrect /etc/resolv.conf. If I remove the dnsmasq package then resolvconf works properly and generates the expected

[Touch-packages] [Bug 1575644] [NEW] resolvconf doesn't create the correct /etc/resolv.conf file when static IP addresses are used

2016-04-27 Thread msp3k
Public bug reported: By default, when installing ubuntu-desktop (and when installing some other packages as well), apt will also install dnsmasq as a dependency. When dnsmask is installed, and static IP addresses are used, resolv.conf creates a nearly empty /etc/resolv.conf file. The file only

[Touch-packages] [Bug 1555171] Re: systemd does not shut down rsyslog

2016-03-09 Thread msp3k
Nevermind. Apparently "systemctl stop " doesn't do what I thought it should do. Rsyslogd can be stopped with: systemctl disable rsyslog systemctl stop rsyslog After issuing the disable command, the stop command worked as I expected. -- You received this bug notification because you are a

[Touch-packages] [Bug 1555171] Re: systemd does not shut down rsyslog

2016-03-09 Thread msp3k
This is on Ubuntu Server 16.04 beta -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1555171 Title: systemd does not shut down rsyslog Status in rsyslog package in Ubuntu:

[Touch-packages] [Bug 1555171] [NEW] systemd does not shut down rsyslog

2016-03-09 Thread msp3k
Public bug reported: This bug is 100% reproducible. Example output: Script started on Wed 09 Mar 2016 10:04:42 AM EST root@flea:/etc/init.d# ps -ef | grep rsyslog syslog5219 1 0 10:04 ?00:00:00 /usr/sbin/rsyslogd -n root 5240 5227 0 10:04 pts/000:00:00 grep

Re: [Touch-packages] [Bug 1530914] Re: sshd crashed with SIGSEGV in _IO_vfprintf_internal()

2016-01-06 Thread msp3k
I tried following one of the links to ubuntu.com, but was told "Sorry, you are not a member of a group that is allowed to see the data from error reports." If you think it's safe to do so, I can reply with the last few links. Would it be safe to assume that they are listed in a newest-first

[Touch-packages] [Bug 1530914] [NEW] sshd crashed with SIGSEGV in _IO_vfprintf_internal()

2016-01-04 Thread msp3k
Public bug reported: sshd crashes several times a day with the following information: ExecutablePath: /usr/sbin/sshd Package: openssh-server 1:6.6p1-2ubuntu2.3 ProblemType: Crash Title: sshd crashed with SIGSEGV in _IO_vfprintf_internal() Architecture: amd64 DistroRelease: Ubuntu 14.04 I've

Re: [Touch-packages] [Bug 1311316] Re: After locking screen there is no input field to type password for unlock

2015-03-18 Thread msp3k
My understanding is that if you type: dpkg -l unity And see the version number 7.2.x, then you have the patch. Michael Peek On 03/18/2015 05:11 AM, Jonathan Laserson wrote: How do I obtain the fix? This still happens. I have Ubuntu 14.04 LTS. -- You received this bug notification

Re: [Touch-packages] [Bug 1311316] Re: After locking screen there is no input field to type password for unlock

2014-12-11 Thread msp3k
On 12/10/2014 09:24 PM, Andrea Azzarone wrote: Please consider answering the question markes ad *** IMPORTANT *** in the description. 2014-12-11 1:26 GMT+01:00 harrychillboy 1311...@bugs.launchpad.net: Bug description: *** IMPORTANT ** If you can reproduce this bug please be sure to

Re: [Touch-packages] [Bug 1311316] Re: After locking screen there is no input field to type password for unlock

2014-12-10 Thread msp3k
1) The bug just bit my boss again. Here's the auth.log: Dec 10 09:13:23 anolis compiz: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory Dec 10 09:13:23 anolis compiz: PAM adding faulty module: pam_kwallet.so Dec 10

Re: [Touch-packages] [Bug 1311316] Re: After locking screen there is no input field to type password for unlock

2014-12-09 Thread msp3k
1) Maybe I'm just derping, but how do I run gnome-screensaver? $ ps -ef | grep -i screensaver peek 24604 24163 0 08:51 pts/47 00:00:00 grep -i screensaver $ gnome-screensaver ** (gnome-screensaver:24665): WARNING **: screensaver already running in this session 2) If this is an LDAP

Re: [Touch-packages] [Bug 1311316] Re: After locking screen there is no input field to type password for unlock

2014-12-09 Thread msp3k
to enable accessibility (e.g. on screen keyabord) from the control center. 2014-12-09 14:56 GMT+01:00 msp3k p...@nimbios.org: 1) Maybe I'm just derping, but how do I run gnome-screensaver? $ ps -ef | grep -i screensaver peek 24604 24163 0 08:51 pts/47 00:00:00 grep -i screensaver $ gnome

Re: [Touch-packages] [Bug 1311316] Re: After locking screen there is no input field to type password for unlock

2014-12-08 Thread msp3k
I must have missed something. Permissions on what path? And what should the permissions be? Michael Peek On 12/06/2014 09:03 AM, Andrea Azzarone wrote: We released a fix but it does not work. The one we released was about text entry not showing randomly on multimonitor and seems to be fixed.

Re: [Touch-packages] [Bug 1311316] Re: After locking screen there is no input field to type password for unlock

2014-12-05 Thread msp3k
I am using ldap as well. Out of 80 hosts and 110 users this bug only affects one user on one host. (Unfortunately that user happens to be one of my bosses.) It's irregular, but frequent. Michael Peek On 12/05/2014 09:06 AM, Andrea Azzarone wrote: @Philipp also I just read you are using ldap.

Re: [Touch-packages] [Bug 1311316] Re: After locking screen there is no input field to type password for unlock

2014-12-01 Thread msp3k
Light-locker is not installed on our machines. On 12/01/2014 10:56 AM, LGB [Gábor Lénárt] wrote: I don't know if it helps, but I always had problems like no input field for password or the double unlock (if the first problem does not occur, unlock presented another unlock field with a sightly

Re: [Touch-packages] [Bug 1311316] Re: After locking screen there is no input field to type password for unlock

2014-11-04 Thread msp3k
Out of 90-somethign users this bug only seems to affect one user. (Of course, that user happens to be one of my bosses...) Because the problem is hard to reproduce I have a feeling that it'lll be difficult to track down and fix. Michael On 11/03/2014 05:18 PM, Bruce MacNaughton wrote: msp3k

Re: [Touch-packages] [Bug 1311316] Re: After locking screen there is no input field to type password for unlock

2014-11-03 Thread msp3k
I would like to know the answer to that as well. Back in the good 'ol days the screen lock was a separate process, and pkill -9 gnome-screensaver would bring back the desktop. But now...? There is a process called /usr/lib/unity/unity-panel-service --lockscreen-mode, but if I kill -9 on it, it

Re: [Touch-packages] [Bug 1311316] Re: After locking screen there is no input field to type password for unlock

2014-11-03 Thread msp3k
When I do that, I get the desktop back, but no dash, launcher, or panel. On 11/03/2014 08:54 AM, Erik wrote: unity --replace On Mon, Nov 3, 2014 at 5:38 AM, Bruce MacNaughton bmacnaugh...@msn.com wrote: I have this problem but can access the desktop using SSH. Is there a process I can

[Touch-packages] [Bug 1358745] [NEW] Screen lock has no place to type in a password

2014-08-19 Thread msp3k
Public bug reported: After the screen saver kicks in, there is a chance that, upon returning to the machine, there will be no place to type in a password. (Picture included.) The bug does not occur regularly, but does occur quite often. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: