Bug#994441: jetty9 uses deprecated configuration options

2021-09-16 Thread Martin van Es
Package: jetty9 Version: 9.4.16-0+deb10u1 Severity: minor When starting jetty9 using the package default start.ini, jetty-console.log logs: WARN:oejx.XmlConfiguration:main: Property 'threads.min' is deprecated, use 'jetty.threadPool.minThreads' instead WARN:oejx.XmlConfiguration:main: Property

Bug#994440: jetty9 systemd unit too strict for normal use

2021-09-16 Thread Martin van Es
Package: jetty9 Version: 9.4.16-0+deb10u1 Severity: important On a default jetty9 install, the systemd unit file restricts readwrite operations to /var/lib/jetty9/ using the systemd ProtectSystem and ReadWritePaths options. The complaint is that this is way too strict for normal operation and d

Bug#971584: libsane1: Scanner no more identified after upgrade to 1.0.31 version

2020-10-12 Thread Martin van Es
I can confirm that creating /var/lock/sane solves the problem for packaged libsane-plustek.so.1.0.31. I don't need to add the USB device id to plustek.conf to make it work though. Martin On Mon, Oct 12, 2020 at 9:51 AM Andreas Tscharner wrote: > Hello World, > > I've had the same problem with m

Bug#971584: libsane1: Scanner no more identified after upgrade to 1.0.31 version

2020-10-07 Thread Martin van Es
I'm also seeing this problem on a recently updated Ubuntu 20.10 (soon to be release). On request of the ubuntu bug replier, I tried to compile 1.0.31 myself and both master and 1.0.31 don't have this problem. I can even use the packaged scanimage if I replace the packaged libsane-plustek.so.1 with

Bug#834790: strace output available

2016-10-16 Thread Martin van Es
I'm exeriencing the same problem and want to counter the argument that it's a good incentive to correct the apt configuration. I allways have backports PPA configured to have current packages in latest (ubuntu) stable release. At the release time of a new stable, the backports repositories are

Bug#511248: xdg-screensaver and xscreensaver

2009-02-01 Thread Martin van Es
(I know "s off" is superfluous in this case, I just let it linger for clarity's sake). Regards, Martin van Es -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#360066: sudo fails to lookup hostname if it contains a hyphen (-)

2006-03-30 Thread Martin van Es
Package: sudo Version: 1.6.8p12-1 Severity: important sudo complains about not being able to lookup the hostname via gethostbyname if the hostname contains one or more hyphens as demonstrated below: [EMAIL PROTECTED]:~$ sudo ps sudo: unable to lookup az-svr-01 via gethostbyname() PID TTY