https://bugs.kde.org/show_bug.cgi?id=492996
Cars <carz...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|DOWNSTREAM |BACKTRACE
--- Comment #6 from Cars <carz...@gmail.com> ---
(In reply to Nate Graham from comment #5)
> Thanks, that's better than what we had before at least. This stuff makes me
> nervous though:
>
> #1 0x00007f3944142189 in PR_Lock () from /lib64/libnspr4.so
> #2 0x00007f3944145736 in PR_CallOnce () from /lib64/libnspr4.so
> #3 0x00007f3944187688 in ?? () from /lib64/libnss3.so
> #4 0x00007f394418bd49 in NSS_Init () from /lib64/libnss3.so
> #5 0x00007f394528a696 in pam_sm_authenticate () from
> /usr/lib64/security/pam_pkcs11.so
> #6 0x00007f394d9a72e3 in ?? () from /lib64/libpam.so.0
> #7 0x00007f394d9a7b49 in pam_authenticate () from /lib64/libpam.so.0
>
> So depending on what you did to try to get smart card auth working, that
> could be quite related. At this point I would recommend talking to the
> openSUSE folks about how to get that working properly, and after following
> their instructions, let's see if it still crashes. If so, we can go down the
> path of manually downloading debug symbols using zypper and we'll re-open
> the bug.
>
> Does that sound like a plan?
I definitely can, though in an ideal world, this issue wouldn't also knock out
kscreenlocker_greet. I'm happy to dive more into this issue if someone from the
dev community can give me some help with more in-depth debugging. I understand
this is probably a low priority given the niche problem, so if I don't hear
back from anyone I'll report back once I talk to the opensuse folks
--
You are receiving this mail because:
You are watching all bug changes.
