Hi,
I got a similar error, I'm using a amd64 and the problem was that the beacon
server wasn't started correctly. I have sent a fix for the bug at inotify. This
is included in the newest svn tree.
Just try to see if the beacon server is running correctly.
Mathias
Original-Nachricht --
Hi,
I fell about the following problem, when I tried to test freevo2.0.
I included my media file directories in the automatically created
freevo2.conf file.
After that the freevo main menu shows entries for the corresponding
media as expected. But when I select such a media menu entry, freevo
fr
Duncan Webb a écrit :
> On Tue, 13 February, 2007 12:21 am, Evan Hisey wrote:
>
>> Pascal-
>> I had a similiar but less stark issue with to nearly identical
>> hardrives. Try using hdparm /dev/ to see what the settings are on
>> each drive. I would expect the old 40 to be a bit slower but not th
"mike lewis" wrote:
> [EMAIL PROTECTED]:/build/freevo/freevo2/kaa$ python setup.py install
> --prefix=/home/mick/freevo2
> [setup] Entering freevo submodule lib/notifier
> running install
> running build
> running build_py
> running install_lib
> creating /home/mick/freevo2
> creating /home/mick/fr
On 2/13/07, mike lewis <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED]:/build/freevo/freevo2/kaa$ python setup.py install
> --prefix=/home/mick/freevo2
> [setup] Entering freevo submodule lib/notifier
> running install
> running build
> running build_py
> running install_lib
> creating /home/mick/fr
[EMAIL PROTECTED]:/build/freevo/freevo2/kaa$ python setup.py install
--prefix=/home/mick/freevo2
[setup] Entering freevo submodule lib/notifier
running install
running build
running build_py
running install_lib
creating /home/mick/freevo2
creating /home/mick/freevo2/lib
creating /home/mick/freevo2/
