FedoraForum.org - Fedora Support Forums and Community
Page 1 of 2 12 LastLast
Results 1 to 15 of 18
  1. #1
    Join Date
    Mar 2012
    Location
    München, Deutschland
    Posts
    897
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Question (putty:<PID>): Gtk-WARNING **: cannot open display: :0

    Any insight why I could not open pop-up windows in superuser mode in Fedora 25???

    Using F25 VM on the top of VMWorkstation 12.5 VMM (HYP type 2), over WIN10 64 Pro.

    Kernel used 4.8.0-0.rc8.git0.1.fc25.x86_64

    PHP Code:
    [user@localhost ~]$ which putty
    /usr/bin/putty
    [user@localhost ~]$ putty&
    [
    1] 2930
    [user@localhost ~]$ 
    [
    1]+  Done                    putty
    [user@localhost ~]$ su -m
    Password
    : 
    [
    root@localhost ~]# which putty
    /usr/bin/putty
    [root@localhost ~]# putty&
    [1] 2988
    [root@localhost ~]# No protocol specified

    (putty:2988): Gtk-WARNING **: cannot open display: :0

    [1]+  Exit 1                  putty
    [root@localhost ~]# uname -a
    Linux localhost.localdomain 4.8.0-0.rc8.git0.1.fc25.x86_64 #1 SMP Mon Sep 26 17:12:24 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
    [root@localhost ~]# 
    --- addendum to original post ---

    dmesg output shows nothing, while journalctl -f output shown below.

    PHP Code:
    [root@localhost ~]# putty&
    [1] 3113
    No protocol specified

    (putty:3113): Gtk-WARNING **: cannot open display: :0
    [1]+  Exit 1                  putty
    [root@localhost ~]# journalctl -f
    -- Logs begin at Wed 2016-03-16 12:05:57 CET. --
    Oct 06 13:01:31 localhost.localdomain gnome-terminal-[2879]: TerminalWindow 0x5645bf692490 is drawn without a current allocation. This should not happen.
    Oct 06 13:01:31 localhost.localdomain gnome-terminal-[2879]: GtkScrollbar 0x5645bf46c8e0 is drawn without a current allocation. This should not happen.
    Oct 06 13:01:31 localhost.localdomain gnome-terminal-[2879]: GtkHeaderBar 0x5645bf9251b0 is drawn without a current allocation. This should not happen.
    Oct 06 13:01:31 localhost.localdomain gnome-terminal-[2879]: GtkBox 0x5645bf4c9a10 is drawn without a current allocation. This should not happen.
    Oct 06 13:01:31 localhost.localdomain gnome-terminal-[2879]: GtkLabel 0x5645bf864840 is drawn without a current allocation. This should not happen.
    Oct 06 13:01:36 localhost.localdomain gnome-terminal-[2879]: TerminalWindow 0x5645bf692490 is drawn without a current allocation. This should not happen.
    Oct 06 13:01:36 localhost.localdomain gnome-terminal-[2879]: GtkScrollbar 0x5645bf46c8e0 is drawn without a current allocation. This should not happen.
    Oct 06 13:01:36 localhost.localdomain gnome-terminal-[2879]: GtkHeaderBar 0x5645bf9251b0 is drawn without a current allocation. This should not happen.
    Oct 06 13:01:36 localhost.localdomain gnome-terminal-[2879]: GtkBox 0x5645bf4c9a10 is drawn without a current allocation. This should not happen.
    Oct 06 13:01:36 localhost.localdomain gnome-terminal-[2879]: GtkLabel 0x5645bf864840 is drawn without a current allocation. This should not happen.
    Oct 06 13:01:43 localhost.localdomain gnome-terminal-[2879]: GtkScrollbar 0x5645bf46c8e0 is drawn without a current allocation. This should not happen.
    Oct 06 13:01:44 localhost.localdomain gnome-terminal-[2879]: GtkScrollbar 0x5645bf46c8e0 is drawn without a current allocation. This should not happen.
    Oct 06 13:01:44 localhost.localdomain gnome-terminal-[2879]: GtkScrollbar 0x5645bf46c8e0 is drawn without a current allocation. This should not happen.
    Oct 06 13:01:45 localhost.localdomain gnome-terminal-[2879]: GtkScrollbar 0x5645bf46c8e0 is drawn without a current allocation. This should not happen.
    Oct 06 13:01:45 localhost.localdomain gnome-terminal-[2879]: GtkScrollbar 0x5645bf46c8e0 is drawn without a current allocation. This should not happen.
    Oct 06 13:01:45 localhost.localdomain gnome-terminal-[2879]: GtkScrollbar 0x5645bf46c8e0 is drawn without a current allocation. This should not happen.
    Oct 06 13:01:45 localhost.localdomain gnome-terminal-[2879]: GtkScrollbar 0x5645bf46c8e0 is drawn without a current allocation. This should not happen.
    Oct 06 13:01:54 localhost.localdomain gnome-terminal-[2879]: GtkScrollbar 0x5645bf46c8e0 is drawn without a current allocation. This should not happen.
    Oct 06 13:01:54 localhost.localdomain gnome-terminal-[2879]: GtkScrollbar 0x5645bf46c8e0 is drawn without a current allocation. This should not happen.
    Oct 06 13:01:54 localhost.localdomain gnome-terminal-[2879]: GtkScrollbar 0x5645bf46c8e0 is drawn without a current allocation. This should not happen.
    Oct 06 13:01:54 localhost.localdomain gnome-terminal-[2879]: GtkScrollbar 0x5645bf46c8e0 is drawn without a current allocation. This should not happen.
    Oct 06 13:01:54 localhost.localdomain gnome-terminal-[2879]: GtkScrollbar 0x5645bf46c8e0 is drawn without a current allocation. This should not happen.
    Oct 06 13:01:54 localhost.localdomain gnome-terminal-[2879]: GtkScrollbar 0x5645bf46c8e0 is drawn without a current allocation. This should not happen.
    Oct 06 13:01:54 localhost.localdomain gnome-terminal-[2879]: GtkScrollbar 0x5645bf46c8e0 is drawn without a current allocation. This should not happen.
    Oct 06 13:01:55 localhost.localdomain gnome-terminal-[2879]: GtkScrollbar 0x5645bf46c8e0 is drawn without a current allocation. This should not happen.
    Oct 06 13:01:55 localhost.localdomain gnome-terminal-[2879]: GtkScrollbar 0x5645bf46c8e0 is drawn without a current allocation. This should not happen.
    Oct 06 13:01:55 localhost.localdomain gnome-terminal-[2879]: GtkScrollbar 0x5645bf46c8e0 is drawn without a current allocation. This should not happen.
    Oct 06 13:01:55 localhost.localdomain gnome-terminal-[2879]: GtkScrollbar 0x5645bf46c8e0 is drawn without a current allocation. This should not happen.
    Oct 06 13:01:55 localhost.localdomain gnome-terminal-[2879]: GtkScrollbar 0x5645bf46c8e0 is drawn without a current allocation. This should not happen.
    Oct 06 13:01:55 localhost.localdomain gnome-terminal-[2879]: GtkScrollbar 0x5645bf46c8e0 is drawn without a current allocation. This should not happen.
    Oct 06 13:01:55 localhost.localdomain gnome-terminal-[2879]: GtkScrollbar 0x5645bf46c8e0 is drawn without a current allocation. This should not happen.
    Oct 06 13:01:55 localhost.localdomain gnome-terminal-[2879]: GtkScrollbar 0x5645bf46c8e0 is drawn without a current allocation. This should not happen.
    Oct 06 13:01:55 localhost.localdomain gnome-terminal-[2879]: GtkScrollbar 0x5645bf46c8e0 is drawn without a current allocation. This should not happen.
    Oct 06 13:01:55 localhost.localdomain gnome-terminal-[2879]: GtkScrollbar 0x5645bf46c8e0 is drawn without a current allocation. This should not happen.
    Oct 06 13:01:56 localhost.localdomain gnome-terminal-[2879]: GtkScrollbar 0x5645bf46c8e0 is drawn without a current allocation. This should not happen.
    Oct 06 13:01:56 localhost.localdomain gnome-terminal-[2879]: GtkScrollbar 0x5645bf46c8e0 is drawn without a current allocation. This should not happen.
    Oct 06 13:01:56 localhost.localdomain gnome-terminal-[2879]: GtkScrollbar 0x5645bf46c8e0 is drawn without a current allocation. This should not happen.
    Oct 06 13:01:56 localhost.localdomain gnome-terminal-[2879]: GtkScrollbar 0x5645bf46c8e0 is drawn without a current allocation. This should not happen.
    Oct 06 13:01:56 localhost.localdomain gnome-terminal-[2879]: GtkScrollbar 0x5645bf46c8e0 is drawn without a current allocation. This should not happen.
    Oct 06 13:01:56 localhost.localdomain gnome-terminal-[2879]: GtkScrollbar 0x5645bf46c8e0 is drawn without a current allocation. This should not happen.
    Oct 06 13:01:56 localhost.localdomain gnome-terminal-[2879]: GtkScrollbar 0x5645bf46c8e0 is drawn without a current allocation. This should not happen.
    Oct 06 13:01:56 localhost.localdomain gnome-terminal-[2879]: GtkScrollbar 0x5645bf46c8e0 is drawn without a current allocation. This should not happen.
    Oct 06 13:01:56 localhost.localdomain gnome-terminal-[2879]: GtkScrollbar 0x5645bf46c8e0 is drawn without a current allocation. This should not happen.
    Oct 06 13:01:56 localhost.localdomain gnome-terminal-[2879]: GtkScrollbar 0x5645bf46c8e0 is drawn without a current allocation. This should not happen.

    [
    snap]

    Oct 06 13:01:59 localhost.localdomain gnome-terminal-[2879]: GtkScrollbar 0x5645bf46c8e0 is drawn without a current allocation. This should not happen.
    Oct 06 13:01:59 localhost.localdomain gnome-terminal-[2879]: GtkScrollbar 0x5645bf46c8e0 is drawn without a current allocation. This should not happen.
    Oct 06 13:01:59 localhost.localdomain gnome-terminal-[2879]: GtkScrollbar 0x5645bf46c8e0 is drawn without a current allocation. This should not happen.
    Oct 06 13:01:59 localhost.localdomain gnome-terminal-[2879]: GtkScrollbar 0x5645bf46c8e0 is drawn without a current allocation. This should not happen.
    Oct 06 13:01:59 localhost.localdomain gnome-terminal-[2879]: GtkScrollbar 0x5645bf46c8e0 is drawn without a current allocation. This should not happen.
    Oct 06 13:01:59 localhost.localdomain gnome-terminal-[2879]: GtkScrollbar 0x5645bf46c8e0 is drawn without a current allocation. This should not happen.
    Oct 06 13:01:59 localhost.localdomain gnome-terminal-[2879]: GtkScrollbar 0x5645bf46c8e0 is drawn without a current allocation. This should not happen.
    Oct 06 13:01:59 localhost.localdomain gnome-terminal-[2879]: GtkScrollbar 0x5645bf46c8e0 is drawn without a current allocation. This should not happen.
    Oct 06 13:02:00 localhost.localdomain gnome-terminal-[2879]: GtkScrollbar 0x5645bf46c8e0 is drawn without a current allocation. This should not happen.

    [
    snap] 
    Thank you in advance!
    _nobody_
    Last edited by nobody; 6th October 2016 at 12:07 PM.

  2. #2
    Join Date
    Mar 2015
    Location
    Europe
    Posts
    73
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: (putty:<PID>): Gtk-WARNING **: cannot open display: :0

    This is a known issue for running GUI applications as root under Wayland: https://bugzilla.redhat.com/show_bug.cgi?id=1274451

    Anyway, why would you ever want to start putty as root? That doesn't make any sense at all. Please, please, never try to run a GUI application as root. This is unsafe and may brick your system.

  3. #3
    Join Date
    Mar 2012
    Location
    München, Deutschland
    Posts
    897
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Question Re: (putty:<PID>): Gtk-WARNING **: cannot open display: :0

    Quote Originally Posted by BkkLQ
    This is a known issue for running GUI applications as root under Wayland: https://bugzilla.redhat.com/show_bug.cgi?id=1274451

    Anyway, why would you ever want to start putty as root? That doesn't make any sense at all. Please, please, never try to run a GUI application as root. This is unsafe and may brick your system.
    Number 8.. U R FF (Fast and Furious - what is, in my view, not at all negative). But sometimes... You should pull the hand brake UP as far as it goes (ASAP). Just friendly advice!

    Why? This is THE Real (very similar) Issue: https://bugzilla.redhat.com/show_bug.cgi?id=1274451#c0

    Here it is (the real one):

    PHP Code:
    [root@localhost ~]# virtualbox&
    [1] 2055
    [root@localhost ~]# No protocol specified
    Qt FATAL: QXcbConnection: Could not connect to display :0
    ^C
    [1]+  Aborted                 (core dumped) virtualbox
    [root@localhost ~]# virtualbox&
    [1] 2088
    [root@localhost ~]# No protocol specified
    Qt FATAL: QXcbConnection: Could not connect to display :0
    ^C
    [1]+  Aborted                 (core dumped) virtualbox
    [root@localhost ~]# 
    (BTW, I am not John Dulaney)

    Do you get the REAL problem???

    _nobody_

  4. #4
    Join Date
    Jun 2005
    Location
    Montreal, Québec, Canada
    Age
    85
    Posts
    10,233
    Mentioned
    36 Post(s)
    Tagged
    0 Thread(s)

    Re: (putty:<PID>): Gtk-WARNING **: cannot open display: :0

    I raised the initial bug report with F23 in September 2015. It was recognized, as sucn, and subsequently, there was a follow up bugreport filed in Nov with some deep explanation of the problem.

    Apparently we should not be running gui code like gparted, from the command line.

    We do that because the GUI interface to gparted, putty, etc, does not allow specific parameter passing to the target program. :
    Leslie in Montreal

    Interesting web sites list
    http://forums.fedoraforum.org/showth...40#post1697840
    We get too soon old, and too late smart!

  5. #5
    Join Date
    Mar 2012
    Location
    München, Deutschland
    Posts
    897
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Question Re: (putty:<PID>): Gtk-WARNING **: cannot open display: :0

    Quote Originally Posted by lsatenstein
    I raised the initial bug report with F23 in September 2015. It was recognized, as such, and subsequently, there was a follow up bugreport filed in Nov with some deep explanation of the problem.
    Ahhh... So you are John Dulaney after all!

    This is your report, I found it: https://bugzilla.redhat.com/show_bug.cgi?id=1266771

    And I see your comment, dated two days ago:

    PHP Code:
    Leslie Satenstein 2016-10-05 16:56:04 EDT
    This bug
    , filed September, duplicate bug filed November.

    Just say, this bug replaced by bug 1274451

    Still is a problem 
    for F25 beta. 
    Quote Originally Posted by lsatenstein
    Apparently we should not be running gui code like gparted, from the command line.

    We do that because the GUI interface to gparted, putty, etc, does not allow specific parameter passing to the target program. :
    I agree wih you. How I am going to run virtualbox, using GFX???

    I always run commands from the CLI. For many reasons.

    _nobody_

  6. #6
    Join Date
    May 2006
    Location
    Hampshire, UK
    Posts
    148
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: (putty:<PID>): Gtk-WARNING **: cannot open display: :0

    So OP,

    I think you need to reassess what you're trying to do.
    What is not explained is;
    • Is there a specific reason why you're using PuTTY instead of your native DE's terminal application?
    • Why are you trying to run GUI applications directly from a root shell instead of using something like pkexec from your own user account?

    Additionally you would not normally run the VirtualBox application as root either, you should add your user to the vboxusers group and run it as your user.

    Essentially your post reads to me as "Why can't I do these things that I should not be doing?", my answer to that would be that it's for your own safety and your should stop doing that, but there is a valid reason why your root shell might be failing to connect to the X server.

    The "cannot open display" message is simply telling you that you either that you do not have the DISPLAY variable exported in your current shell (check this with "echo $DISPLAY"), or if the value of the DISPLAY variable is correct in your root session the root user probably does not have access to your user account's current X session, this X server security configuration has been default since f24.
    Executing...
    Code:
    xhost local:root
    ... in your terminal will grant the root user access to your local X display.

    I'll reiterate there is no reason in your use case to run these graphical programs as root and you are essentially compromising your system's security trying to do so but let us know how you get on.


    HTH
    Last edited by vinbob; 7th October 2016 at 01:39 PM.
    Chapeau Linux
    http://chapeaulinux.org

  7. #7
    Join Date
    Mar 2012
    Location
    München, Deutschland
    Posts
    897
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Arrow Re: (putty:<PID>): Gtk-WARNING **: cannot open display: :0

    OK, Bob...

    I am not going to explain to you that I use Linux since version 2.4.9 (Y2003), and that I am VERY aware of potential danger to do stuff as supeuser a.k.a root. You should understand that I can do many stuff as root, but I ALWAYS do the stuff as ordinary user, unless it comes to necessity. And now, this is one of the moments. I do not remember that I twisted anything as root since Y2007... Let it be.

    So, I am VERY aware of dangers you already (and number 8 as well) mentioned. Who knows, maybe I am even more aware that you two... One only knows!

    And, as you said, I'll follow your advises, just to try to comply.

    So, let us begin (here I login from GNOME as user intel - why intel, not the concern, now):

    PHP Code:
    [intel@localhost ~]$ pwd
    /home/intel
    [intel@localhost ~]$ whoami
    intel
    [intel@localhost ~]$ cd projects/win.iso/
    [
    intel@localhost win.iso]$ ls -al
    total 3494544
    drwxrwxrwx
    . 2 intel intel       4096 Sep 28 08:56 .
    drwxrwxr-x. 9 intel intel       4096 Oct  7 18:15 ..
    -
    rwxrwxrwx. 1 intel intel 2048196608 Sep 27 20:20 7601.17514.101119-1850_Update_Sp_Wave1-GRMSP1.1_DVD.iso
    -rwxrwxrwx. 1 intel intel  619581440 Dec 14  2015 Win10PESE_x64.ISO
    -rw-rw-r--. 1 intel intel  563934504 Sep 28 08:55 windows6.1-KB976932-X86.exe
    -rwxrwxrwx. 1 intel intel  346666496 Sep 27 19:52 Windows_Win7SP1.7601.17514.101119-1850.X86FRE.Symbols.msi
    [intel@localhost win.iso]$ echo $DISPLAY
    :0
    [intel@localhost win.iso]$ virtualbox
    Qt WARNING
    : libpng warning: iCCP: known incorrect sRGB profile 
    Launched virtualbox... And after choosing 7601.17514.101119-1850_Update_Sp_Wave1-GRMSP1.1_DVD.iso (32bit WIN7 SP1 Ultimate), I got the following message:

    Code:
    Cannot create the machine folder 7601.17514.101119-1850_Update_Sp_Wave1-GRMSP1.1_DVD.iso in the parent folder /home/intel/projects/win.iso.
    
    Please check that the parent really exists and that you have permissions to create the machine folder.
    Now, I did the following:

    PHP Code:
    [intel@localhost win.iso]$ su -m
    Password
    : 
    [
    root@localhost win.iso]# virtualbox
    No protocol specified
    Qt FATAL
    : QXcbConnection: Could not connect to display :0
    Aborted 
    (core dumped)
    [
    root@localhost win.iso]# echo $DISPLAY
    :0
    [root@localhost win.iso]# xhost local:root
    No protocol specified
    xhost
    :  unable to open display ":0"
    [root@localhost win.iso]# pwd
    /home/intel/projects/win.iso
    [root@localhost win.iso]# exit
    exit
    [
    intel@localhost win.iso]$ echo $DISPLAY
    :0
    [intel@localhost win.iso]$ xhost local:root
    non
    -network local connections being added to access control list
    [
    intel@localhost win.iso]$ su -m
    Password
    : 
    [
    root@localhost win.iso]# echo $DISPLAY
    :0
    [root@localhost win.iso]# virtualbox
    Qt WARNING: libpng warning: iCCP: known incorrect sRGB profile
    [root@localhost win.iso]# 
    Yep, yep... It does the trick!

    Code:
    [intel@localhost win.iso]$ xhost local:root
    non-network local connections being added to access control list
    This issue is solved, but much more important one... Is not!

    Cannot create the machine folder 7601.17514.101119-1850_Update_Sp_Wave1-GRMSP1.1_DVD.iso in the parent folder /root.
    Please check that the parent really exists and that you have permissions to create the machine folder.
    _nobody_

  8. #8
    Join Date
    May 2006
    Location
    Hampshire, UK
    Posts
    148
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: (putty:<PID>): Gtk-WARNING **: cannot open display: :0

    As stated earlier, it's likely that Virtualbox isn't working because;

    a) It's not meant to be run as root.
    b) When running VirtualBox as your 'intel' user I'm guessing 'intel' isn't a member of the 'vboxusers' group (which it needs to be to run Virtualbox guests), have you checked?

    There are many long-term Linux and Unix users including myself but that is not relevant to this conversation.
    Anyway I'll leave it at that as you don't seem to be very receptive to help despite asking for it and receiving the answer, so good luck.
    Chapeau Linux
    http://chapeaulinux.org

  9. #9
    Join Date
    Mar 2012
    Location
    München, Deutschland
    Posts
    897
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Talking Re: (putty:<PID>): Gtk-WARNING **: cannot open display: :0

    Quote Originally Posted by vinbob
    As stated earlier, it's likely that Virtualbox isn't working because;
    a) It's not meant to be run as root.
    Not meant, but must!

    Quote Originally Posted by vinbob
    b) When running VirtualBox as your 'intel' user I'm guessing 'intel' isn't a member of the 'vboxusers' group (which it needs to be to run Virtualbox guests), have you checked?
    Did not, thank you for the tips. You might be right, but I need to investigate further.

    Quote Originally Posted by vinbob
    There are many long-term Linux and Unix users including myself but that is not relevant to this conversation.
    Again, you are correct.

    Quote Originally Posted by vinbob
    Anyway I'll leave it at that as you don't seem to be very receptive to help despite asking for it and receiving the answer, so good luck.
    I was born alone, and my best guess, I'll die alone. Well...

    Good luck to you as well!

    _nobody_

  10. #10
    Join Date
    Jun 2005
    Location
    Montreal, Québec, Canada
    Age
    85
    Posts
    10,233
    Mentioned
    36 Post(s)
    Tagged
    0 Thread(s)

    Re: (putty:<PID>): Gtk-WARNING **: cannot open display: :0

    Hi VinBob

    As a retired old fxxt, I found that I had accumulated a half dozen disk drives, mainly 1 terrrabyte units. I have multiple different Linux Gnome and Mate versions installed. And at least once a week or so, I cleanout a test version, (except it's /home) and test with another iso. Many times I evaluate software and know that to remove it with dnf is risky. So, from the X11 command line, I choose to run gparted as sudo gparted /dev/sd? where ? refers to one of the letters a..e . I can run this command with X11, but not with Wayland interface. It blows up under Wayland. There was a discussion that (for security reasons) suggested that no GUI should be runnable from the command line. Polkit was mentioned as allowing the X11 workaround.

    Today I plan tol do a sudo gparted /dev/sdc where I have my Fedora25 alpha installed, and wipe it clean. On the 11th I will install the F25 beta.

    With virtual box software, my system output shudders when I try to run a live version of a distribution. I think it's the fair schedular algorithm that timeslices badly. But since I have the disks, I use direct installs to disk. I use gparted to
    a) format, label and name a partition, including resize.
    b) copy the UUID info to a new fstab

    Gparted is my universal disk management tool of preference. As long as I can only run gparted from the X11 interface, I will not, because of ease of use, migrate to Wayland.
    Leslie in Montreal

    Interesting web sites list
    http://forums.fedoraforum.org/showth...40#post1697840
    We get too soon old, and too late smart!

  11. #11
    Join Date
    Mar 2012
    Location
    München, Deutschland
    Posts
    897
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Exclamation Re: (putty:<PID>): Gtk-WARNING **: cannot open display: :0

    Hello Leslie,

    Since I don't like to be in the Dark, when certain things are happening (and in my very long career, some external forces kept me scattered all over the IT place, HW, FW and SW, and SW from boot-loaders, BIOSes all the way to most commercial OSes, thus making me running around as crazy for decades), I started googling. I recalled, in early 1990s I used this two nice commands on System V Unix box (I remember, this was at the time HP box, also there were SUN boxes with BSD Unix all over the place): echo $DISPLAY and xhost+ (to allow any connection to connect to X server). Then I did it blindly (overloaded with the other work), and forgot about them.

    So here is what I found (since I am anyhow not a GFX expert, not on the levels running in Linux, I understand more on the GFX HW level) is the following:

    http://unix.stackexchange.com/questi...ost-command-do

    In the nutshell, what I understood from this answer is the following: local (normal) users in some X11 list are by default added as hosts, and automatically allowed to connect to X server, while root is NOT added by the obvious rule stated by vinbob and rule of the thumb :

    The number 1 rated high risk system vulnerability noted by the recent ISS audit of BNL was the use of "xhost +" or an open X display. Using "xhost +" allows anyone the ability to watch your keystrokes, capture windows and insert command strings into your windows. This situation is particularly bad when you have root access to a machine. There is no legitimate reason to run "xhost +". Most people will be using ssh to make their connections to other machines than their desktop and ssh tunnels X11 traffic, eliminating any need for "xhost +".
    In other words, you can try xhost command, thus adding your root to this list and allowing GFX windows based SW to run in superuser mode, but you have to be very careful.

    _nobody_

  12. #12
    Join Date
    Mar 2012
    Location
    München, Deutschland
    Posts
    897
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Question Re: (putty:<PID>): Gtk-WARNING **: cannot open display: :0

    Quote Originally Posted by vinbob
    b) When running VirtualBox as your 'intel' user I'm guessing 'intel' isn't a member of the 'vboxusers' group (which it needs to be to run Virtualbox guests), have you checked?
    Virtualbox could not start because of some different reasons. Has nuthin' to do with this statement... Rather with some other stuff, which are nontrivial.

    But, as it might sound enough crazy (and it is), I was able start booting Fedora-Workstation-Live-i386-25_Beta-1.1.iso - 1.42GB (Fedora 25 32bit Beta .iso image downloaded from: https://getfedora.org/en/workstation/prerelease/), and the structure I am all running it is the following:

    [1] I run on bare HP EliteBook 840 G1 notebook (Dual CORE i5-4300U (HSW mobile sku)) WIN10 64 PRO;
    [2] On the top of it I run VMWorkstation 12.5 64bit VMWare VMM/HYP Type 2;
    [3] On the top of it I run Fedora 25 Beta x86_64 VM, where I installed virtualbox from ORACLE;
    [4] On the top of Fedora 25 Beta x86_64 VM I run virtualbox, VMM/Hyp Type 2;
    [5] On the top of virtualbox I start booting Fedora-Workstation-Live-i386-25_Beta-1.1.iso), which went to the booting loop:


    I need to investigate more!



    _nobody_
    Attached Images Attached Images

  13. #13
    Join Date
    Dec 2013
    Location
    United Kingdom
    Posts
    7,133
    Mentioned
    7 Post(s)
    Tagged
    1 Thread(s)

    Re: (putty:<PID>): Gtk-WARNING **: cannot open display: :0

    have you tried GNOME Boxes or virt-manager to boot the Fedora ISO inside the VMWare installation of Fedora? If so, does it produce the same loop?

  14. #14
    Join Date
    May 2006
    Location
    Hampshire, UK
    Posts
    148
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    The fact that your guest is booting confirms that all is OK now with your Virtualbox installation.

    The cause of the graphics not working in your guest may be due to Wayland not supporting the proprietary Virtualbox virtual graphics adapter in your guest.

    As anti suggested maybe you should consider using the hypervisor already built-in to your Linux system, KVM.
    It's faster than Virtualbox and easy to use with the likes of virt-manager or Gnome Boxes.
    Last edited by vinbob; 12th October 2016 at 08:37 PM.
    Chapeau Linux
    http://chapeaulinux.org

  15. #15
    Join Date
    Mar 2012
    Location
    München, Deutschland
    Posts
    897
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Arrow Re: (putty:<PID>): Gtk-WARNING **: cannot open display: :0

    Quote Originally Posted by antikythera
    have you tried GNOME Boxes or virt-manager to boot the Fedora ISO inside the VMWare installation of Fedora? If so, does it produce the same loop?
    AntiKerbera,

    I'do it. I'll test at least (I can promise that) virt-manager (which I'll open the new thread here, since we started mixing apples, oranges and melons in this thread). I'll do it for Fedora 25 community.

    Few questions to you?
    [1] Is virt-manager RHEL HYP/VMM type 2? Am I right?
    [2] Please, enlighten me what are GNOME Boxes???

    For [1], please, give me some time (I have other job to do as well), since ORACLE guys (I started talking with) become to be cumbersome... I dropped on them too much load. I need this to get going first (problems described above with virtualbox).

    Quote Originally Posted by vinbob
    The fact that your guest is booting confirms that all is OK now with your Virtualbox installation.

    The cause of the graphics not working in your guest may be due to Way land not supporting the proprietary Virtualbox virtual graphics adapter in your guest.

    As anti suggested maybe you should consider using the hypervisor already built in to you Linux System, KVM.
    It's faster than Virtualbox and easy to use with the likes of virt-manager or Gnome Boxes.
    Bob,

    Thank you for the suggestions. I will come back to KVM later... I promise.

    _nobody_

Page 1 of 2 12 LastLast

Similar Threads

  1. Gtk-WARNING **: cannot open display
    By rikm27 in forum Using Fedora
    Replies: 0
    Last Post: 8th August 2015, 10:32 PM
  2. Gtk-WARNING **: cannot open display: :0
    By debo2011 in forum F18 Development
    Replies: 3
    Last Post: 21st December 2012, 09:09 AM
  3. (mini-wm:1462): Gtk-WARNING **: cannot open display: :1
    By flyingpengwin in forum Installation, Upgrades and Live Media
    Replies: 1
    Last Post: 27th January 2009, 08:21 PM
  4. Gtk-Warning Cannot open display
    By clindsey in forum Installation, Upgrades and Live Media
    Replies: 2
    Last Post: 19th July 2006, 01:26 PM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •