Comment 3 for bug 508305

It's reported by insserv and caused by mismatched boot and shutdown
orders in the LSB headers of the init script shipped with libchipcard;
it causes recursive boot/shutdown conflicts between other packages.
Fixing this requires changing the boot dependency order in
libchipcard's ini script's LSB headers.

On Sun, Jan 17, 2010 at 4:48 PM, Micha Lenk <email address hidden> wrote:
> Martin-Éric, I don't understand. What exactly is the loop and what do
> you suggest to do in order to break the loop?
>
> --
> init script LSB dependencies need upgrading for rsyslog
> https://bugs.launchpad.net/bugs/508305
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “libchipcard” package in Ubuntu: New
>
> Bug description:
> insserv: There is a loop between service rsyslog and chipcardd if stopped
> insserv:  loop involving service chipcardd at depth 3
> insserv:  loop involving service rsyslog at depth 2
> insserv:  loop involving service udev at depth 1
> insserv:  loop involving service sendsigs at depth 4
> insserv:  loop involving service nullmailer at depth 2
> insserv: There is a loop between service rsyslog and chipcardd if stopped
> insserv:  loop involving service umountnfs at depth 6
> insserv: exiting now without changing boot order!
>
> ProblemType: Bug
> Architecture: i386
> Date: Sat Jan 16 10:35:50 2010
> DistroRelease: Ubuntu 10.04
> Package: libchipcard-tools 4.2.8-1ubuntu1
> ProcEnviron:
>  LANGUAGE=fi_FI.UTF-8
>  PATH=(custom, user)
>  LANG=fi_FI.UTF-8
>  SHELL=/bin/bash
> ProcVersionSignature: Ubuntu 2.6.32-10.14-generic
> SourcePackage: libchipcard
> Tags: lucid
> Uname: Linux 2.6.32-10-generic i686
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/libchipcard/+bug/508305/+subscribe
>