@doliveira
Samba version is currently 4.0, the fix is intended to be released apart
of the Samba 4.1 release.
Samba 4.1 may be released as an update to Ubuntu 14.04 or the Ubuntu
devs may take just the memory leak patch and put it into 4.0 and then
put that through as an update.
Either way
** Package changed: ubuntu = ntp (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/781088
Title:
Time is not syncronized with NTP-server
--
Ubuntu-server-bugs mailing list
** Changed in: samba (Ubuntu)
Status: Triaged = Confirmed
--
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/288496
Title:
winbind postinst returned error exit status 1 (daemon
Setting back to confirmed since no upstream bug has been made or
attached, if someone can report the bug upstream then set it back to
triaged that would be great, thanks :)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in
** Changed in: clamav (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to clamav in ubuntu.
https://bugs.launchpad.net/bugs/708395
Title:
clamdscan can't scan anything
--
Ubuntu-server-bugs
I'm having a similar issue,
running clamscan as either root or as user will scan my home folder no
issues, installing clamav-daemon and running clamdscan will result in a
lot of permission errors being thrown up and some files being missed
entirely?
clamscan:
--- SCAN SUMMARY
Not a bug, appears to be mis-configuration.
** Changed in: samba (Ubuntu)
Status: New = Invalid
** Converted to question:
https://answers.launchpad.net/ubuntu/+source/samba/+question/104319
--
unable to mount location,failed to mount windows share
Thank you for taking the time to report this issue and helping to make
Ubuntu better. Examining the information you have given us, this does
not appear to be a bug report so we are closing it and converting it to
a question in the support tracker. We appreciate the difficulties you
are facing, but
