Thank you for taking the time to report this bug and helping to make
Ubuntu better.
>From your stack trace, it looks likely to me that the crash is in libtdb
rather than winbind itself, unless winbind is corrupting memory somehow.
Can you check all tdb files for corruption using tdbtool (I presume this
needs to be done when winbind and samba are shut down), and if you are
able then run winbind under valgrind? It isn't clear to me whether this
really is a bug or local corruption or a hardware fault or something
like that. These steps might give us something really obvious to help
decide.
Please also report exact package numbers. The command "apport-collect
1100787" will do this for you automatically.
Please change the bug status back to New when you are done. Thanks!
** Changed in: samba (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1100787
Title:
Samba 3.6.3 segfault or panic.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1100787/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
