Summary: | media-tv/freevo - freeze when started as service after netmount | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Laurent Dufrechou <laurent.dufrechou> |
Component: | New packages | Assignee: | Television related Applications in Gentoo's Portage <media-tv> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | High | ||
Version: | 2006.0 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | freevo-1.5.4-r1.ebuild |
Description
Laurent Dufrechou
2006-08-27 14:12:05 UTC
I have the exact same Issue (In reply to comment #1) > I have the exact same Issue > My solution didn't work all the time.(freevo started before locales) To make it works always I've also added locales to depends. So freevo is the last to start and now it's works always... The problem is that freevo starts BEFORE the console is started (the init process ends). If the console starts after freevo it steals control of the keyboard from it. The easiest solution is starting freevo just before local is started and only works if the time used from local to start is less than the time taken from freevo (as it should be in most cases). This problems shows up even whith X if you start it too early... I made a script to start X without login manager and I experienced the same issue since it started too fast. Probably the best solution would be a check inside the init script to wait until local or console has started. my solution was to change the depend funtion in /etc/init.d/freevo to: depend() { use `ls /etc/init.d/ |cut -d"." -f1|grep -v freevo|grep -v local` } P.S. change the hardware platform from amd64 to all since this problem happens with every hardware and every version Changed the platform to all. What's next? As we've got a solution,is there somebody that will release a new version of the ebuild? I don't know how all works as this is my first bug release :) Ehm... this will work just for freevo-only systems and only if you don't have any stale file/disabled service in /etc/init.d/freevo. (please test, but imho this could be a ugly hack.....). What about creating 2 different freevo initscripts, one standard (/etc/init.d/freevo) waiting for locales and xdm to be launched, and another for no-x systems (/etc/init.d/freevo-no-x), waiting just for locales? forgot: or better, installing the script with depend(locales xdm) if X use flag is set, the one with depend(locales) if X use flag is not set ? Do you think this could be the correct solution? Created attachment 99732 [details]
freevo-1.5.4-r1.ebuild
(Proposed)
Modified ebuild (now /etc/init.d/freevo waits for xdm if X flag is set,
waits for local if X flag is not set). Please test and review, if anyone is
fine I'll commit (specify if I should change "xdm" or "local" with something
else, I haven't a freevo-only system to test, sorry).
Just a note, this may become obsolete by bug #150568 : Basically, nobody should use the initscript, non-x users can try: su - $USER -c `source /etc/profile;freevo 2>/dev/vc/10` while X users should set autologin (to non-privileged user!) in the login manager and start a freevo session. please try : depend() { use use net xfs lircd after hald dbus hotplug } I think that should work fixed with bug #150568 , freevo-1.5.4-r1 already in portage. No more initscript, a desktop session for X users and notes on how to configure an autologin-autofreevo system at the end of ebuild process for non-X users. Committed |