Date: Mon, 28 Nov 2022 07:21:53 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 268033] xscreenaver: crashing and dumping core on unlock Message-ID: <bug-268033-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D268033 Bug ID: 268033 Summary: xscreenaver: crashing and dumping core on unlock Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: ports-bugs@FreeBSD.org Reporter: duncan@bayne.id.au Created attachment 238390 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D238390&action= =3Dedit Contains xscreensaver.log (generated during auth crash), and .xscreensaver settings. xscreensaver 6.04, installed either from packages or by building from sourc= e in ports, crashes during authentication. When this happens, xscreensaver does not unlock (good!), and core is dumped= to ~/xscreensaver-auth.core. I've attached a tarball of the log and config, and can generate a coredump = if required (as a different user, as the generated coredump seems to contain my password). Repro steps: 1. install xscreensaver with: sudo pkg install xscreensaver 2. run xscreensaver with: xscreensaver --log xscreensaver.log 3. lock the screen with: xscreensaver-command -lock 4. attempt to unlock the screen with my password 5. expected: the screen unlocks 6. actual: the screen doesn't unlock --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-268033-7788>