init script needs to be fixed

openct (0.6.8-1ubuntu1) edgy; urgency=low

  * etc/init-script.in: enable setting owner and permissions on
    /var/run/openct

Fixed in openct 0.6.8-1ubuntu1

I permit myself to reopen this bug because I still get the same problem. I only install libopenct1 (I don't need the openct package) and get an error about the missing /var/run/openct directory too. I get this error with everything linked againts libopenct, the init script should be in the libopenct1 package not the openct one.

Laurent Bigonville wrote:
> I permit myself to reopen this bug because I still get the same problem.
> I only install libopenct1 (I don't need the openct package) and get an
> error about the missing /var/run/openct directory too. I get this error
> with everything linked againts libopenct, the init script should be in
> the libopenct1 package not the openct one.
>
> ** Changed in: openct (Ubuntu)
> Status: Fix Released => Unconfirmed
>

you didn't mention which application you are using, so I guess it is
opensc. to quote the FAQ from http://www.opensc-project.org/faq.html

--cut--
/var/run/openct/status: No such file or directory
  OpenSC has support for three driver types below it: PCSC, OpenCT and
CT-API. If you want to use OpenSC with PC/SC-Lite only, please edit
opensc.conf, look for reader_drivers like and remove the openct driver.

  If you get this message, but want to use OpenSC with OpenCT, then you
have not properly installed OpenCT. Please have a look at the QuickStart
docucument in OpenCT, most likely you didn't start the init script or it
was not properly installed or something like that.
--cut--

if you want to use opensc with pcsc only, edit the reader_drivers
setting in opensc.conf. if you want to use opensc with openct, you need
to install the openct package too. so I think the error message you get
is correct, and you need to take either action.

btw: the same is true for opensc and pcsc, you get a similar error
message if you install opensc and libpcsclite only, and then you need to
either remove pcsc from the reader_drivers setting or install pcscd.

Regards, Andreas

moving this back to 'fix released'; the re-opening was probably due to misconfiguration, and there hasn't been any action on it in several months.