ivman, rox, and automount... "cannot open display"

hedpe · 11-14-2005, 05:17 AM

Hi,

I have a bit of a problem. IVMAN runs as root, which automounts my devices. IVMAN is automounting them properly, and I have setup a script that does something along the lines of "touch ~/afile" and it puts "afile" into /root because IVMAN is running as root. Well, I want IVMAN to add a folder to my desktop using the script I made "rox.add"

If i open up a terminal as a user, and run the "rox.add" script, it adds the icon to my desktop perfectly, but, when I assign IVMAN to run the script, it cannot put the icon on my desktop since it is running as root.

If i do: "rox.add", i get:
(ROX-Filer:13830): Gtk-WARNING **: cannot open display:

my local hostname is "monster", if i ping "monster" i am pinging myself.

So, I did this as the regular user:

Code:

hedpe@monster ~ $ export DISPLAY=":0.0"
hedpe@monster ~ $ xhost +monster
monster being added to access control list

And now as root:

Code:

monster hedpe # rox.add /mnt/laptophd/ 100 100 Test

(process:13967): Gdk-WARNING **: locale not supported by C library

(ROX-Filer:13967): Gtk-WARNING **: Locale not supported by C library.
        Using the fallback 'C' locale.
monster hedpe # 
** (ROX-Filer:13972): CRITICAL **: pinboard_pin_with_args: assertion `current_pinboard != NULL' failed

Trying to use sudo:

Code:

monster hedpe # sudo -u hedpe rox.add /mnt/laptophd/ 100 100 Test

(ROX-Filer:13977): Gtk-WARNING **: cannot open display:

And finally one last condition, exporting a new DISPLAY as root:

Code:

monster hedpe # export DISPLAY="monster:0.0"
monster hedpe # rox.add /mnt/laptophd/ 100 100 Test

(process:14039): Gdk-WARNING **: locale not supported by C library

(ROX-Filer:14039): Gtk-WARNING **: Locale not supported by C library.
        Using the fallback 'C' locale.

(ROX-Filer:14039): Gtk-WARNING **: cannot open display:  
monster hedpe #

Any suggestions would be greatly appreciated!

Thanks!
George

AdaHacker · 11-15-2005, 04:07 PM

One work-around you might consider is running another instance of ivman. If you create per-user ivman configuration files under $HOME/.ivman/, then when ivman runs as that user, it will only use those files.

So, you could put try putting the rules to do your ROX stuff in $HOME/.ivman/IvmConfigActions.xml and add a line to your ~/.xinitrc (or ~/.xsession, or a symlink for ROX-Session, or however you start your X session) to run ivman. That way, you will have two instances of ivman running - one that does the mounting as root and another that does your X stuff as you.