** Changed in: openct (Debian)
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/368683
Title:
Openct needs to be restarted when inserting an eToken
To manage not
** Bug watch added: Debian Bug tracker #498920
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=498920
** Changed in: openct (Debian)
Status: Fix Released => Unknown
** Changed in: openct (Debian)
Remote watch: bugs.debian.org/ #498920 => Debian Bug tracker #498920
--
Openct needs to
This bug was fixed in the package openct - 0.6.19-1ubuntu1
---
openct (0.6.19-1ubuntu1) lucid; urgency=low
* Fake merge from debian unstable (LP: #519713)
* Patch for merge from hal to udev: (LP: #503119) (LP: #436545)
(Taken from http://bugs.debian.org/cgi-bin/bugreport.cgi?
The better fix would be to update to openct-0.6.16 which already handles
the switch to udevadm
--
Openct needs to be restarted when inserting an eToken
https://bugs.launchpad.net/bugs/368683
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Regarding "exec 2> /tmp/openct-script.log 2>&1" -- this is a mistake. It
redirects stderr first to the file then redirects stderr to stdout.
That's why the logfile was created but blank. You meant "exec 2> /tmp
/openct-script.log 1>&2" to capture both stdout and stderr.
Alternatively "exec 2> /tmp
Regarding "exec 2> /tmp/openct-script.log 2>&1" -- this is a mistake. It
redirects stderr first to the file then redirects stderr to stdout.
That's why the logfile was created but blank. You meant "exec 2> /tmp
/openct-script.log 1>&2" to capture both stdout and stderr.
Alternatively "exec 2> /tmp
** Changed in: openct (Debian)
Status: New => Fix Released
--
Openct needs to be restarted when inserting an eToken
https://bugs.launchpad.net/bugs/368683
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing lis
new debdiff file, please apply / upload fixed package to universe
jaunty-updates.
** Attachment added: "debdiff file with the trivial bugfix"
http://launchpadlibrarian.net/26923554/openct_0.6.14-3ubuntu3.debdiff
--
Openct needs to be restarted when inserting an eToken
https://bugs.launchpad.n
Am Dienstag 19 Mai 2009 06:13:13 schrieb David Medberry:
> Hi Andreas,
>
> Your openct 0.6.16-0 worked flawlessly for me on i386 platform as well.
> Any idea when this will go into Jaunty? Any place else we need to
> request that?
the important wiki pages seem to be
https://wiki.ubuntu.com/StableRe
Hi Andreas,
Your openct 0.6.16-0 worked flawlessly for me on i386 platform as well.
Any idea when this will go into Jaunty? Any place else we need to
request that?
--
Openct needs to be restarted when inserting an eToken
https://bugs.launchpad.net/bugs/368683
You received this bug notification b
Hi Andreas,
On 29/04/09 11:05, Andreas Jellinghaus wrote:
> thanks to a huge amount of work by Stanislav Brabec from suse, openct
> has even much better hal setup now, and I created a pre-release from svn
> trunk and packaged it for ubuntu, and it works on my machine. can you
> give it a try?
>
we had problems like this before: the kernel finds out there is a new
usb device. udev gets an event. udev manages both to tell openct
about it and create a file in /dev/ somewhere. but again the communication
is flawed somehow, openct is not told what that new device file is. sad.
lets switch to
On 28/04/09 22:06, Andreas Jellinghaus wrote:
> can you check which configuration the ubuntu package has?
> a hal file (official suggestion), an udev rule or a hotplug map file?
It seems to use a udev rule file, /lib/udev/rules.d/40-openct.rules
> if so, what is the usb vendor and product id, and
Hi Andreas,
On 29/04/09 07:58, Andreas Jellinghaus wrote:
> /lib/udev/rules.d/40-openct.rules
> replace
> ENV{MODALIAS}=="usb:v0529p0514", RUN+="/lib/udev/openct_usb"
> with
> ENV{MODALIAS}=="usb:v0529p0514*", RUN+="/lib/udev/openct_usb"
>
> and it should work.
I made the change but it didn't w
** Changed in: openct (Debian)
Status: Unknown => New
--
Openct needs to be restarted when inserting an eToken
https://bugs.launchpad.net/bugs/368683
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubu
for reference, the upstream fix was commit 1063 in october 2008.
http://www.opensc-project.org/openct/changeset/1063/trunk/etc/openct.udev.modalias.in
the debian bug is 498920
** Bug watch added: bugs.debian.org/ #498920
http://bugs.debian.org:80/cgi-bin/bugreport.cgi?bug=498920
** Also affe
/lib/udev/rules.d/40-openct.rules
replace
ENV{MODALIAS}=="usb:v0529p0514", RUN+="/lib/udev/openct_usb"
with
ENV{MODALIAS}=="usb:v0529p0514*", RUN+="/lib/udev/openct_usb"
and it should work.
can anyone fix the jaunty openct package with this trivial typo fix?
or will openct users need to wait 6 m
can you check which configuration the ubuntu package has?
a hal file (official suggestion), an udev rule or a hotplug map file?
if so, what is the usb vendor and product id, and are those matched
in that file? what script is configured to be triggered by that file?
can you check if that script is
Same issue here on 2 different computers (one upgraded from 8.10, the
other has been installed from scratch).
** Changed in: openct (Ubuntu)
Status: New => Confirmed
--
Openct needs to be restarted when inserting an eToken
https://bugs.launchpad.net/bugs/368683
You received this bug noti
19 matches
Mail list logo
