Bug#921538: Fails to start since upgrade to 1.9.0-1

2019-02-09 Thread Simon Deziel
On 2019-02-09 8:28 p.m., Robert Edmonds wrote: > Probably it's better to use the --with-chroot-dir= argument to configure > rather than directly patching the source to change the default. Indeed and that's what's being proposed in the merge request. Regards, Simon

Bug#921538: Fails to start since upgrade to 1.9.0-1

2019-02-08 Thread Simon Deziel
On 2019-02-08 7:26 a.m., Kepi wrote: > Chroot workaround is working for me too. Good. > Anyway in the long term would it be better to have chroot setup > automatically again? I found out that it was working before, at least > some work was done in #579622 for auto support. The auto-chroot setup

Bug#921538: Fails to start since upgrade to 1.9.0-1

2019-02-06 Thread Simon Deziel
Here is a merge request [*] to disable chroot'ing again like it has been since version 1.0.0-3 Regards, Simon *: https://salsa.debian.org/dns-team/unbound/merge_requests/3 signature.asc Description: OpenPGP digital signature

Bug#921538: Fails to start since upgrade to 1.9.0-1

2019-02-06 Thread Simon Deziel
Hi Ryan, On 2019-02-06 11:12 a.m., Ryan Kavanagh wrote: > Since the upgrade to 1.9.0-1, unbound fails to start. Purging the > package and reinstalling does not fix the issue. The errors seem to be > due to being unable to read various configuration files. > > Feb 06 11:01:12 zeta unbound[28647]:

Bug#919326: msmtp: account default not found: no configuration file available

2019-01-15 Thread Simon Deziel
On 2019-01-14 6:03 p.m., Sergio Mendoza wrote: > Yes. I have now checked and I have .msmtprc as a symlink. If it is not > a symlink then I have no problems and everything runs smooth. Great, thanks Sergio. > In any case > this is the output you asked for: > > root@quetzalli:~# dmesg | grep

Bug#919326: msmtp: account default not found: no configuration file available

2019-01-14 Thread Simon Deziel
Hi Sergio, On 2019-01-14 5:40 p.m., Sergio Mendoza wrote: > A few days ago, msmtp fails to work. It all seems to be related to the > inability to read ~/.msmtprc file. In other words it seems that > ~/.msmtprc needs to have mode 644. This is not at all desired since > sensible (private)

Bug#662960: ssmtp doesn't validate server TLS certificates

2019-01-09 Thread Simon Deziel
On 2019-01-09 10:23 a.m., Cédric Dufour - Idiap Research Institute wrote: > PS: ssmtp is extremely handy to forward machine-generated messages in large > deployments, internally, iow. where TLS is not required ssmtp seems like abandonware. Have you tried msmtp(-mta)? It works in a similar way,

Bug#882122: thunderbird: Thunderbird can't connect to X server, fails to start

2017-11-23 Thread Simon Deziel
On 2017-11-23 03:12 PM, Jack Henschel wrote: > $ sudo dmesg -T | grep apparmor > ... > [Thu Nov 23 21:01:24 2017] audit: type=1400 audit(1511467287.665:8): > apparmor="STATUS" operation="profile_load" profile="unconfined" > name="thunderbird" pid=498 comm="apparmor_parser" > [Thu Nov 23 21:01:24

Bug#882122: thunderbird: Thunderbird can't connect to X server, fails to start

2017-11-23 Thread Simon Deziel
On 2017-11-23 12:18 AM, Carsten Schoenert wrote: >> Also, directly running /usr/lib/thunderbird/thunderbird-bin works, too! >> Which is really weird because /usr/lib/thunderbird/thunderbird and >> /usr/lib/thunderbird/thunderbird-bin are the same, but only the latter one >> can connect to the X