Gtk-WARNING **: cannot open display:

ncsuapex · 08-25-2006, 07:03 PM

Ive read and read the forums and tried and tried other suggestions but none of them worked for me. I am trying to run gtkpod as root(nevermind why, I just need to) but I get the error: Gtk-WARNING **: cannot open display:

I also get this error if I try to run any GUI application as root from the terminal.

I had this problem before and the xhost + command fixed it, but that fix is no longer working. I used to be able to run GUI apps as root but I did something and ended up taking the "video" group away from root. I added it back in and its still not working. Can anyone help? Below are some commands I've tried with the results.

Ive also tried logging in as root into the Xwindow(KDE) and got the same errors.

root@hostname:~# groups
root bin daemon sys adm disk wheel floppy audio video
root@hostname:~#

root@hostname:~# gtkpod

(gtkpod:12996): Gtk-WARNING **: cannot open display

root@hostname:~# slapt-get -search gtkpod
gtkpod-0.99.4-i486-1ahl [inst=yes]: gtkpod (GUI for Apple's iPod)
libgpod-0.3.2-i486-1ahl [inst=yes]: libgpod (Library for Apple's iPod)
python-gpod-0.3.2-i486-1cl [inst=yes]: python-gpod 0.3.2

root@hostname:~# /usr/X11R6/bin/xhost +
/usr/X11R6/bin/xhost: unable to open display ""
root@hostname:~#

username@hostname:/mnt$ xhost +
access control disabled, clients can connect from any host

root@hostname:~# gtkpod

(gtkpod:13041): Gtk-WARNING **: cannot open display:

root@hostname:~# xhost +
xhost: unable to open display ""

username@hostname:/mnt$ xhost +localhost
localhost being added to access control list

root@hostname:~# gtkpod

(gtkpod:13089): Gtk-WARNING **: cannot open display:

username@hostname:/mnt$ xhost +localhost
root@username:~# export DISPLAY=localhost:0.0
root@username:~# gtkpod

(gtkpod:13107): Gtk-WARNING **: cannot open display:

each time I did a xhost + and the command failed I went back as username and did a xhost -

What the F is wrong? Any other suggestions?

Alien Bob · 08-25-2006, 07:42 PM

You forgot to set the DISPLAY variable. It is empty and your app does not know where to display.

As an alternative to the insecure "host +" command try this:

Code:

echo $DISPLAY                  # you'll be needing this value 3 lines below
sudo -i                        # or "su -" on older Slackwares
xauth merge ~alien/.Xauthority # use your own username here instead of "alien"
export DISPLAY=:0.0            # use the value of DISPLAY you've seen 3 lines before

Eric

ncsuapex · 08-25-2006, 07:50 PM

Awesome! Thanks.. That did the trick except now I'm getting the "SEGMENTATION ERRORS" when the gtkpod reads the ipod...

But now I can run GUI commands from root.. so thanks alot for helping me with that!

caduqued · 05-05-2008, 06:32 PM

Quote:

Originally Posted by Alien Bob

You forgot to set the DISPLAY variable. It is empty and your app does not know where to display.

As an alternative to the insecure "host +" command try this:

Code:

echo $DISPLAY                  # you'll be needing this value 3 lines below
sudo -i                        # or "su -" on older Slackwares
xauth merge ~alien/.Xauthority # use your own username here instead of "alien"
export DISPLAY=:0.0            # use the value of DISPLAY you've seen 3 lines before

Eric

Hi Eric,

I've been using some of your scripts and your slackbuild page as reference point to introduce myself in Slackware world.

I had been obtaining this problem also, and with your post it was totally solved, Thanks a lot (again

). I have just one question, is it probably some type of intrusion that change this (not be able to run any xserver app as root) in my slack? I was wondering this because, I had my slackware functioning perfectly well, and just from one day to another I begun to get this problem. I just was a little worried by what produced this behaviour in my slack. (???)

Something else, I have slackware 12, not and old one, but the command sudo doesn't function if I don't "feed" the sudoers file; however, a lot of people cite use of sudoers in slackware without problem, I don't understand what I am missing (???). In particular, your sudo line didn't help me, I had to login as root, put the .Xauthority, and then logout again. Did it I well?

Thanks, bye.

caduqued

T3slider · 05-05-2008, 09:22 PM

`su -` will get you to login to a full root shell. Try that instead.

nitrofurano · 01-03-2013, 03:11 AM

Quote:

Originally Posted by Alien Bob

You forgot to set the DISPLAY variable. It is empty and your app does not know where to display.

As an alternative to the insecure "host +" command try this:

Code:

echo $DISPLAY                  # you'll be needing this value 3 lines below
sudo -i                        # or "su -" on older Slackwares
xauth merge ~alien/.Xauthority # use your own username here instead of "alien"
export DISPLAY=:0.0            # use the value of DISPLAY you've seen 3 lines before

Eric

hi Eric,
this solution works fine when temporary, but it doesn't works after then next login - how can i have it working after a boot, just like i have not such problems after a fresh install? (i'm using Crunchbang-Debian distro, upgraded to Wheezy)
thanks!

Alien Bob · 01-03-2013, 03:15 AM

Quote:

Originally Posted by nitrofurano

hi Eric,
this solution works fine when temporary, but it doesn't works after then next login - how can i have it working after a boot, just like i have not such problems after a fresh install? (i'm using Crunchbang-Debian distro, upgraded to Wheezy)
thanks!

First: this is a 5-year old thread and you should not dig it up from the grave, it is considered rude.
Second: this is a Slackware forum.

Please open your own new thread in a Debian forum here on LQ.

Eric

nitrofurano · 01-04-2013, 05:54 PM

Quote:

Originally Posted by Alien Bob

First: this is a 5-year old thread and you should not dig it up from the grave, it is considered rude.
Second: this is a Slackware forum.

Please open your own new thread in a Debian forum here on LQ.

Eric

i really can't understand it: why is it considered rude, if the problem may still exist on most of people (like me), this thread was actually started (and there was no meaning for bloating this forum with this same question), and the answer provided here where not really useful yet? isn't this a valid reason for keeping this thread "alive"?

(thanks saying this honestly in this way, Eric: for understanding why "digging old threads from the grave" is that rude, i should understand why (and i really can't, sorry...), and not taking it as rude just because someone is saying, isn't it? so, do you think i should believe on what everybody says without a valid explanation, even those people that sells snake oil?)

btw, i'm not only a Debian user, i also use Puppy and TinyCore a lot, even Slax (based on Slackware), so i though this very concerning question is actually related to all GNU/Linux distros - and after searching from google/duckduckgo/etc..., i really can't find further started threads like this one!

cheers and thanks for the feedback,
Paulo