[Bug 1835446] Re: radvd unit still references /var/run for pidfile

2019-07-07 Thread Michael Griego
The compat mapping is present.  I should have clarified that the
behavior didn't manifest itself until a system restart.  The first time
I started up the service with a valid config, it ran.  After I rebooted
the system, the service no longer came up and presented with the error
message I included above.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1835446

Title:
  radvd unit still references /var/run for pidfile

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/radvd/+bug/1835446/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1835446] [NEW] radvd unit still references /var/run for pidfile

2019-07-04 Thread Michael Griego
Public bug reported:

Package: radvd

$ lsb_release -rd
Description:Ubuntu 19.04
Release:19.04

$ apt-cache policy radvd
radvd:
  Installed: 1:2.17-2
  Candidate: 1:2.17-2
  Version table:
 *** 1:2.17-2 500
500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages
100 /var/lib/dpkg/status


The systemd service hasn't yet been updated to move the pidfile from
/var/run to /run.  This is causing a service startup failure in 19.04
with the following error logged:

/lib/systemd/system/radvd.service:11: PIDFile= references path below
legacy directory /var/run/, updating /var/run/radvd.pid →
/run/radvd.pid; please update the unit file accordingly.

I was able to fix this locally by applying the following override via
"systemctl edit radvd.service":

[Service]
PIDFile=/run/radvd.pid

I'm happy to submit a patch for this, but I'm not sure which file is the
appropriate one to set the PATH_RADVD_PID build variable in the ubuntu
package.

** Affects: radvd (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/1835446

Title:
  radvd unit still references /var/run for pidfile

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/radvd/+bug/1835446/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1438289] [NEW] KRDC unable to connect to Mac hosts due to libvncserver problem

2015-03-30 Thread Michael Griego
Public bug reported:

KRDC in Ubuntu 14.10/Utopic is unable to connect to Mac hosts that are
using native username/password authentication.  When a connection is
made, the username/password dialog pops up.  Once submitted, KRDC
crashes, and the following is logged in syslog:

krdc: Libgcrypt error: acquiring FSM lock failed: Invalid argument -
abort

According to reports in the libvncserver GitHub repo, it looks like this
has been fixed upstream.  See:
https://github.com/LibVNC/libvncserver/pull/51 and
https://github.com/LibVNC/libvncserver/issues/45


Current package versions:

libvncserver0: 0.9.9+dfsg-6ubuntu1
libgcrypt20: 1.6.1-2ubuntu1
krdc: 4:4.14.1-0ubuntu1

** Affects: libvncserver (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/1438289

Title:
  KRDC unable to connect to Mac hosts due to libvncserver problem

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvncserver/+bug/1438289/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs