Date: Tue, 12 Jan 2010 21:05:17 +0100 (CET) From: Damian Weber <dweber@htw-saarland.de> To: Greg Rivers <gcr+freebsd-stable@tharned.org> Cc: freebsd-stable@freebsd.org Subject: Re: strange abort with kcheckpass (solved) Message-ID: <alpine.BSF.2.00.1001122102500.76300@magritte.htw-saarland.de> In-Reply-To: <alpine.BSF.2.00.1001121249130.28715@roadkill.tharned.org> References: <alpine.BSF.2.00.1001121603340.74490@magritte.htw-saarland.de> <alpine.BSF.2.00.1001121249130.28715@roadkill.tharned.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 12 Jan 2010, Greg Rivers wrote: > Date: Tue, 12 Jan 2010 13:33:53 -0600 (CST) > From: Greg Rivers <gcr+freebsd-stable@tharned.org> > To: Damian Weber <dweber@htw-saarland.de> > Cc: freebsd-stable@freebsd.org > Subject: Re: strange abort with kcheckpass > > On Tue, 12 Jan 2010, Damian Weber wrote: > > > I've got a strange SIGABRT issue with kcheckpass. Of course, kcheckpass is > > not contained in the base system, yet I write to this list since the base > > system could be able to help with tracking this down. (kcheckpass is called > > from a screen locker which fails to operate properly as a consequence of the > > SIGABRT.) > > > > Normal behaviour: > > (for example with wrong password) > > $ kcheckpass > > Password: > > Authentication failure > > > > Strange behaviour here (called mybox below): > > $ kcheckpass > > Abort trap: 6 > > > > Have you set security.bsd.map_at_zero=0 ? In my experience, several ports > (eg. samba, cups, parts of kde3) depend on PIE and will not run with this > disabled on 7.x. > Yes - that was the problem. Thanks a lot. # sysctl security.bsd.map_at_zero=1 security.bsd.map_at_zero: 0 -> 1 magritte# kcheckpass Password: Authentication failure Best regards Damian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1001122102500.76300>