I mean the crash is not frequent enough.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1810827
Title:
There is a fix available, but is not frequent enough and there is a
simple workaround: restart instead of reload. Also only that specific
"force group" config change is affected.
** Tags removed: server-next
** Also affects: samba (Ubuntu Bionic)
Importance: Undecided
Status: New
**
Still in our queue.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1810827
Title:
/usr/sbin/smbd:6:dump_core:smb_panic_s3:smb_panic:change_to_user_internal:smbd_smb2_request_check_tcon
I can reproduce this crash with the instructions from the samba upstream
bug:
1. Define a share without `force group=...` in the smb.conf.
2. Connect to the share by an SMB client.
3. Add `force group=...` to the share definition in the smb.conf.
4. Run `smbcontrol all reload-config` to
This might be https://bugzilla.samba.org/show_bug.cgi?id=13690
** Bug watch added: Samba Bugzilla #13690
https://bugzilla.samba.org/show_bug.cgi?id=13690
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to samba in Ubuntu.
