It has been a while since I looked at this with current build. Just made a
new in install and will give motion a try with it. It may be a week before
there is the opportunity.
On Thu, Mar 4, 2010 at 23:37, sanitycheck <email address hidden> wrote:
> I wonder if the problem you observe is the same as the problem I
> observe.
>
> Motion in Ubuntu 9.10 (3.2.11-1) will not view BTTV cameras properly on
> the first try, either as daemon on a reboot or just starting manually in
> shell, or starting daemon manually after a system has been up for a
> while. Initially I get a green screen. If I force a restart with
> /etc/init.d/motion restart it will start to monitor the camera. This
> has been observed on different servers, 32-bit and 64-bit versions. The
> problem persists even if I replace repository version with version I
> build from source.
>
> >From the response I got from the Motion mailing list, the problem may be
> limited to Motion running on Ubuntu (and maybe Debian).
>
> --
> motion device occupied with intrepid
> https://bugs.launchpad.net/bugs/311388
> You received this bug notification because you are a direct subscriber
> of the bug.
>
It has been a while since I looked at this with current build. Just made a
new in install and will give motion a try with it. It may be a week before
there is the opportunity.
On Thu, Mar 4, 2010 at 23:37, sanitycheck <email address hidden> wrote:
> I wonder if the problem you observe is the same as the problem I /bugs.launchpad .net/bugs/ 311388
> observe.
>
> Motion in Ubuntu 9.10 (3.2.11-1) will not view BTTV cameras properly on
> the first try, either as daemon on a reboot or just starting manually in
> shell, or starting daemon manually after a system has been up for a
> while. Initially I get a green screen. If I force a restart with
> /etc/init.d/motion restart it will start to monitor the camera. This
> has been observed on different servers, 32-bit and 64-bit versions. The
> problem persists even if I replace repository version with version I
> build from source.
>
> >From the response I got from the Motion mailing list, the problem may be
> limited to Motion running on Ubuntu (and maybe Debian).
>
> --
> motion device occupied with intrepid
> https:/
> You received this bug notification because you are a direct subscriber
> of the bug.
>
--
Tom Gilmore