I am going to mark this as fixed released, but this is probably a good
candidate for an SRU.
chuck
** Changed in: samba (Ubuntu)
Status: Confirmed => Fix Released
--
samba PANIC: failed to set uid
https://bugs.launchpad.net/bugs/341816
You received this bug notification because you are a
Having the same issue here:
kernel 2.6.24-23-server x64
samba 3.0.28a-1ubuntu4.9
The setting "change notify = no" seems to work as a workaround.
--
samba PANIC: failed to set uid
https://bugs.launchpad.net/bugs/341816
You received this bug notification because you are a member of Ubuntu
Server T
** Changed in: samba (Ubuntu)
Status: Incomplete => Confirmed
--
samba PANIC: failed to set uid
https://bugs.launchpad.net/bugs/341816
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
--
Ubuntu-server-bugs mailing
Sorry, as I said before, I can't try the package because it is a
productive environment...
--
samba PANIC: failed to set uid
https://bugs.launchpad.net/bugs/341816
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
--
Ubunt
This might not be a duplicate of bug 216358.
Could the reporter try the packages in my PPA and see if they fix it for him
(as well as 3.0.34 did).
(samba_3.0.28a-1ubuntu4.9~ppa1) at https://launchpad.net/~ttx/+archive/ppa
Thanks !
** This bug is no longer a duplicate of bug 216358
Samba crashe
*** This bug is a duplicate of bug 216358 ***
https://bugs.launchpad.net/bugs/216358
** This bug has been marked a duplicate of bug 216358
Samba crashes repeatedly to assert_uid
--
samba PANIC: failed to set uid
https://bugs.launchpad.net/bugs/341816
You received this bug notification bec
I think you did the right thing by installing Samba 3.0.34.
Indeed the changelog suggest that it was fixed there:
http://www.samba.org/samba/history/samba-3.0.34.html
o Andrew Tridgell
* Avoid a race condition in glibc between AIO and setresuid().
* Become root for AIO operations.
2009/
Yes, i have seen a lot of similar bug reports too, but all of them were
unresolved.
When the problem appeared we checked a lot of configuration issues.
The problem seems NOT to be user or client specific.
The users where the PANIC appeared:
- had a unix account
- a samba account with the same ui
Thank you for this bug report.
Many other similar bugs have been reported, some on Ubuntu, sometimes on
Fedora, or even in FreeBSD.
In Ubuntu I speak of bug #216358, bug #314657 and bug #229654.
Could you check if user ID 11789 really exist by doing:
sudo cat /etc/passwd | grep 11789
sudo cat /e