I'll work on this next.
** Changed in: sssd (Ubuntu Xenial)
Status: New => Confirmed
** Changed in: sssd (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: sssd (Ubuntu Xenial)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
--
You received this bug
The configuration change is correct, but I think it's not working in the
end. Upstream has a bug about it:
https://github.com/rsyslog/rsyslog/issues/477
And I filed
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1703987 for the
ubuntu packages.
** Bug watch added:
*** This bug is a duplicate of bug 1531622 ***
https://bugs.launchpad.net/bugs/1531622
I filed bug #1703987 for the problem I mentioned in comment #3
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
*** This bug is a duplicate of bug 1531622 ***
https://bugs.launchpad.net/bugs/1531622
On second thought, it's better to open a new bug I believe. Sorry.
** This bug has been marked a duplicate of bug 1531622
default config still using a legacy keyword: KLogPermitNonKernelFacility
--
*** This bug is a duplicate of bug 1531622 ***
https://bugs.launchpad.net/bugs/1531622
I just saw that this was fixed in yakkety:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1531622
I will therefore repurpose this bug to be about my findings in comment
#3
--
You received this
** Changed in: rsyslog (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1675515
Title:
old KLogPermitNonKernel directive error in rsyslog.conf
The new option doesn't seem to be working correctly:
https://github.com/rsyslog/rsyslog/issues/477
With the old style config:
#module(load="imklog" permitnonkernelfacility="on") # provides kernel logging
support
$ModLoad imklog
#KLogPermitNonKernelFacility on
I get kernel messages in
For some reason bug expiration isn't working for this bug. Given that
there were no updates for over two months, I'm marking it as invalid.
Feel free to reopen it if you have more information about the problem.
Thanks!
** Changed in: cyrus-sasl2 (Ubuntu)
Status: Incomplete => Invalid
I also rebuilt the debian package with llvm-3.9, and the test also
passes.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1692073
Title:
check_clamav test fails
To manage
I tried rebuilding with llvm 3.8 and the same test fails. Given that the
debian unstable package uses LVM 3.8, something else is going on here in
the case of artful.
** Summary changed:
- check_clamav fails
+ check_clamav test fails
** Bug watch added: Gentoo Bugzilla #616192
@gpfdave, please open a new bug describing your problem and attaching
/var/log/samba/log* and /etc/samba/smb.conf files please. From the bits
you posted, it's a different issue.
You can do so by invoking "apport-bug samba"
Thanks
--
You received this bug notification because you are a member
It could be that, in the case where /etc/fstab is used, there are extra
options being passed to mount.cifs and that is what is causing the
difference in behaviour.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
Remember that if you update or reinstall this printer driver again in
the future, it will undo this fix and you will have to apply it again.
Cheers! :)
** Changed in: samba (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
For anybody else who is trying to build clamav in current artful, you
will need at least the attached fixes to reach the reported test error
stage.
Pardon the incomplete DEP3 header as this is work in progress.
** Patch added: "artful-clamav-some-build-fixes.debdiff"
IP addresses work fine too.
--
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/1703490
Title:
Unable to mount network volume on 17.10 Samba server
To manage notifications about this bug
Correct, these lines do influence operation. These are the so called LSB
headers and they influence service startup and shutdown ordering.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
Here is what I got with xfce on 16.04 using thunar. Just the home share
is read-only, as expected.
** Attachment added: "thunar-xfce.png"
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1703490/+attachment/4913443/+files/thunar-xfce.png
--
You received this bug notification because you
Sorry about your frustration, we are just trying to narrow it down. It
could be that something in artful's samba changed and that thunar needs
to adapt, for example.
We need to determine why this test case that you mentioned when opening
the bug doesn't work:
"""
16.04 client mount.cifs to 17.10
Try this one. Don't forget to chmod it to 0755 after it's in place.
** Attachment added: "panasoniclpd-init"
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1702601/+attachment/4913438/+files/panasoniclpd-init
--
You received this bug notification because you are a member of Ubuntu
19 matches
Mail list logo
