Date: Tue, 10 Jan 2023 03:14:05 +0000 From: bugzilla-noreply@freebsd.org To: x11@FreeBSD.org Subject: [Bug 268033] x11/xscreensaver: Crashing and dumping core on unlock Message-ID: <bug-268033-7141-KdIj5dAc6H@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-268033-7141@https.bugs.freebsd.org/bugzilla/> References: <bug-268033-7141@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D268033 omars <omars1234@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |omars1234@gmail.com --- Comment #11 from omars <omars1234@gmail.com> --- Yes, this bug does still exist in 13.1-RELEASE-p5 releng/13.1-753d65a19 Tested against a from-scratch fresh build and fresh ports tree, running und= er Xorg. Happens as OP desdcribed, /usr/local/bin/xscreensaver-hacks/xscreensaver-auth seg-faults on a good password. Verified against both $1 and $6 hashed passwords. lldb run on the core says: (lldb) bt all * thread #1, name =3D 'xscreensaver-auth', stop reason =3D signal SIGSEGV * frame #0: 0x0000000500664e84 libc.so.7`strlen + 84 frame #1: 0x0000000500bfb0c1 Aside: we shouldn't closing active bugs for "Feedback Timeout" in just a mo= nth (didn't get a reply). Perhaps OP is busy during the month of western holida= ys, or otherwise unable to follow up, but the bug still exists and is egregious (core function of port is broken). --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-268033-7141-KdIj5dAc6H>