*** This bug is a duplicate of bug 1883614 ***
https://bugs.launchpad.net/bugs/1883614
Hi Luis,
I can derive from your info in [2] that you are on Xenial, so I'll mark that
for now.
Do you happen to know if it also occurs on other releases?
Two things will commonly be needed to get any further on this.
1. your setup details, how did you setup sssd and your authentication exactly.
Are there particular actions to trigger this bug or is it just time/logins that
have to pass? If possible the best usually is if you are able to outline the
steps needed to set up a clean new VM with Ubuntu to reach the bad state
2. Since it reports a crash is there any crash that you could report [1] ?
[1]: https://help.ubuntu.com/community/ReportingBugs#Reporting_a_crash
[2]: https://answers.launchpad.net/ubuntu/+question/689804
The message somehow felt familiar, but I couldn't find a case I touched that
seemed like a full match. Looking further I found the old case I had in mind ...
=> https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1883614
I think I can mark this a dup and if you want you can chime in on the
other bug that is already a few steps further in the debug-process but
fell dead back then.
** Also affects: sssd (Ubuntu Bionic)
Importance: Undecided
Status: New
** No longer affects: sssd (Ubuntu Bionic)
** Also affects: sssd (Ubuntu Xenial)
Importance: Undecided
Status: New
** This bug has been marked a duplicate of bug 1883614
sssd got killed due to segfault in ubuntu 16.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871321
Title:
) [sssd] [talloc_log_fn] (0x0010): Bad talloc magic value - unknown
value
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1871321/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
