Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: vdradmin-am (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1001810
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-lts-xenial (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1001810
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-lts-trusty (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1001810
** Also affects: linux-lts-xenial (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1001810
Title:
vdradmin-am preconfigured not to (auto)start in
Since /var/cache/vdradmin-am/usr/ through
/var/cache/vdradmin-am/usr/share/vdradmin-am/template belong to root:root
rather than vdradmin-am:vdradmin-am (and look like they have wrongly been
placed into a relative path),
the Perl Zlib issue can be fixed by sudo chown -R vdradmin-am:vdradmin-am
Still the same old (and now new) bugs in Ubuntu 16.04.2 LTS,
not logging or returning any reason why "sudo service vdradmin-am start had" no
effect either.
For a web interface, there really shouldn't be a weak, plaintext default
PASSWORD = linvdr in /var/lib/vdradmin-am/vdradmind.conf in 2017
In Ubuntu 14.04 LTS, a barely noticeable line in apt-get's output hints at this
* VDRAdmin-AM disabled - enable in /etc/default/vdradmin-am
but user still has to find and change PASSWORD = ToSomethingMoreSecure from
linvdr
via sudo nano -w /var/lib/vdradmin-am/vdradmind.conf
and ENABLED=1 (from
