I wrote a script to change the perms adding the execute for the sasl
group (which postfix user is member of).
#!/bin/bash
#
while read line; do
setoctal=`echo $line |awk '{print $1}'`
filename=`echo $line | awk '{print $2}'`
if [ -f $filename ]; then
octal=`stat -c '%a' "$filename"
Hello,
Am having similar issues.
I am migrating to a new internal mail relay that has Sasldb auth on
postfix (submission/587)
Though your suggestions to add the groups entry with systemctl edit
saslauthd changes the group membership on the directory
/var/spool/postfix/var/run/saslauthd; However
Just two little suggestions to make the software more friendly:
$ strings /usr/bin/dbus-daemon | grep 'Unknown username "%s" in'
Unknown username "%s" in message bus configuration file
It would be nice if the printer of this error message (dbus-daemon)
would change the error message so:
Public bug reported:
Ubuntu 17.04
xserver-xorg-input-synaptics:
Installed: 1.9.0-1ubuntu1
Candidate: 1.9.0-1ubuntu1
Version table:
*** 1.9.0-1ubuntu1 500
500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages
100 /var/lib/dpkg/status
I get no response from touchpad
I tried the solution proposed in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1442908/comments/4
and it worked. You can use wicd-kde instead wicd-gtk; but, besides that,
you must follow the instructions. Wicd doesn't recognizes automatically
the encryption, so you must try the most common:
Public bug reported:
This is a bug report on 'watch' from procps.
Essentially, it doesn't seem like -c/--color (ANSI color sequences
support) works.
Here's how to reproduce:
'man watch says':
-c, --color
Interpret ANSI color sequences.
This works as expected in bash or da
Hello.
When i tried to unlock the lockscreen,i enter with any password and with no
password.
The same is when i log in my session.
My account has a very strong password made during installation.
Thanks for your help.
--
You received this bug notification because you are a member of Ubuntu
Touch
@tpo-deb: you are right, I didn't notice that the messages differ
somewhat. However, my point remains, Gimp 2.8.14 in Debian still
corrupts the file "somehow"! The original Nikon file does not produce
any warnings when read by exiv2, the gimp file does.
--
You received this bug notification beca
@tpo-deb: the proble is still there in current Gimp 2.8.14-1+b1 from
Debian testing/unstable. I guess we have to wait until the Jessy freeze
is over for a fix.
$ exiv2 -pc a.jpg # original Nikon file
$ gimp a.jpg # cropped, saved as aa.jpg
$ exiv2 -pc aa.jpg
Error: Directory NikonPr
9 matches
Mail list logo
