SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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
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
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?
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!
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.
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!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.