However, RealPlayer doesn't like being run by sudo. If I enter in a terminal: sudo -u realplay /home/realplay/RealPlayer/realplay I get: Xlib: connection to ":0.0" refused by server Xlib: No protocol specified ** ERROR **: Unable to open display
The error report, as usual, tells you where the problem is. O:-) RealPlayer probably doesn't have anything against itself running suid - and any program having something to say on that topic is likely to spurt out a meaningful message. Anyhow, what you're getting is a message from X telling you that it has denied an unprivileged user of access to your display. When you run your X, it defaults to allowing access to you and only to you (i.e. only to processes which you own), so root cannot start XLib apps on that display.
There's a simple command "xhost" which is used to manimulate the access list. Typically 'xhost +root' or even 'xhost +' (strongly discouraged, esp. if networked!) will do your job.
By the way, this accounts for all the other XLib: connection to ":0.0" refused by server messages.
Best
Zoran
Attachment:
signature.asc
Description: This is a digitally signed message part
_______________________________________________ gnome-list mailing list gnome-list@xxxxxxxxx http://mail.gnome.org/mailman/listinfo/gnome-list
