I guess you replied to me instead of the mailing list by accident and it's OK to take it back to the mailing list for everyone to see? I'm sure nothing you wrote was confidential!
In <[EMAIL PROTECTED]>, Nicolas Huillard <[EMAIL PROTECTED]> wrote: > Tony Houghton a �crit : > > >I've worked out that the problem is because I've been trying to run > >MPlayer remotely over ssh, and it needs to be run from the console to > >get non-root access. > > Relax permissions on the /dev/ttyN devices ? > From the top of my head : when you log-in on the console, login changes > the owner of your own /dev/ttyN device to allow you user to access it. > When you're logged over SSH, login obviously doesn't do that for you. > I think DirectFB apps need some kind of access permissions to /dev/ttyN, > even with "no-graphics-vt,no-vt-switching,no-vt-switch". > Changing group permissions or pertaining to the right group would do the > trick. Please report back... It does seem a nice, straightforward fix, but I've been trying that all along I'm afraid. As you say, the permissions of /dev/tty[0-9] seem to change dynamically, but I've been making sure they have g+rw access and that I'm a member of the appropriate group: they're currently owned by root but there is actually a tty group, which I've also made myself a member of. At one point I even backed up /dev/ and gave myself group access to the whole lot of it, but that didn't help either. At the moment my consoles are running on video=matroxfb:...; I was previously using no video parameter and presumably getting plain VGA text console. With the current setup I can launch mplayer successfully from the console by typing blind; I didn't try it from a text-mode console. Having consoles on the TV would be a nice little "bonus" feature as long as it doesn't interfere with DFB, but solving this access problem is my main priority for now. -- TH * http://www.realh.co.uk
