Jason Tackaberry wrote:
[snip]
Beacon complaining about not being able to find inotify_init sounds like
a bug.  Was it a python exception?  Or a linker problem? 
  
Since it has been some time since I did the first glibc-recompile, I can't be really sure of what happened, but this is as I recall it:
- In the beginning I got the "inotify not supported in glibc; using built-in support instead." message during kaa-setup. I think at that time I upgraded my kernel and recompiled (possibly upgraded) glibc, still with the old 2.6.11 linux-headers, and the message went away.

Only today I actually started to run beacon and the inotify_init-message appeared (in the beacon errorlog / commandline). I can't be sure at this moment whether that was generated by python, if you really need this info I can try downgrading again.

Possibly the problem is related to the one described here: http://www.dovecot.org/list/dovecot/2006-June/014072.html


  
The next problem was the unpickle error discussed before. I was using 
sqlite 3.3.5-r1 and pysqlite 2.3.1. Upgrading to sqlite 3.3.6 solved the 
problem (which seems to contradict the conclusion reached before that it 
was a bug in the pysqlite library). Interestingly, I just decided to 
downgrade to 3.3.5-r1 again, and the error doesn't re-appear now (even 
after deleting the ~/.beacon dir). Could this possibly be connected to 
using newer linux-headers or a newer glibc too?
    

Interesting speculation, and I think a very sensible one given what
you've experienced.  I've asked the last person to report this issue
what glibc version they're using.

Though this isn't quite consistent with what dischi experienced.  He had
the problem, updated either sqlite or pysqlite2 (but not glibc) and the
problem went away.

In any case, I'll have to spend some time getting to the bottom of this
before we release a 2.0 preview.
  
Well, updating to 3.3.6 actually solved my problem too, even before I upgraded glibc, but I'm pretty sure it wasn't working at that time with 3.3.5-r1, so it might be a combination of things.

  
Next, it complained about connecting to the dbus. Starting the dbus 
deamon (/etc/init.d/dbus) fixed this, however now it's complaining about 
not being able to find org.freedesktop.Hal in any .services file.  
Emerging hal and hal-device-manager and (re)starting the hal and dbus 
daemons took care of this problem (I could imagine dbus and hal only 
being used to notice a new cd/dvd being inserted, so beacon might run 
without it, I just don't want to risk any cascading error from this).
    

I think beacon will resort to polling to see if media has been inserted
in the absence of hal.  dischi?
  
Actually, without dbus-deamon running, this is the output, so it seems at least dbus is needed:
INFO server(25): start hardware monitor
INFO beacon(325): connect to thumbnailer ...
INFO beacon(327): connection to thumbnailer established
INFO beacon(330): connect to hwmon ...
INFO beacon(332): connection to hwmon established
INFO server(75): start beacon
INFO media(26): new media kaa.beacon.root
INFO server(301): start crawler for /
INFO server(60): beacon <-> hwmon connected
ERROR server(47): unable to connect to dbus
ERROR async(84): InProgress exception: local variable 'fd' referenced before assignment
ERROR async(84): InProgress exception: local variable 'fd' referenced before assignment
ERROR async(84): InProgress exception: local variable 'fd' referenced before assignment
ERROR async(84): InProgress exception: local variable 'fd' referenced before assignment
ERROR async(84): InProgress exception: local variable 'fd' referenced before assignment
ERROR async(84): InProgress exception: local variable 'fd' referenced before assignment
ERROR async(84): InProgress exception: local variable 'fd' referenced before assignment

Dbus without hal emerged said the following:
INFO beacon(325): connect to thumbnailer ...
INFO server(25): start hardware monitor
Introspect error: The name org.freedesktop.Hal was not provided by any .service files
INFO beacon(327): connection to thumbnailer established
INFO beacon(330): connect to hwmon ...
INFO beacon(332): connection to hwmon established
INFO server(75): start beacon
INFO media(26): new media kaa.beacon.root
INFO server(301): start crawler for /
INFO server(60): beacon <-> hwmon connected
Introspect error: The name org.freedesktop.Hal was not provided by any .service files


But I think I recall that if I let that run a little longer, the same complaints about the fd-variable re-appeared. Again, I can investigate if needed.

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Freevo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freevo-devel

Reply via email to