Bug 790501 - No protocol specified Cannot open display:
No protocol specified Cannot open display:
Status: CLOSED NOTABUG
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: virt-viewer (Show other bugs)
6.4
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: Daniel Berrange
Virtualization Bugs
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-02-14 12:19 EST by gregrwm
Modified: 2012-02-16 12:36 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-02-16 12:36:27 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
package list (84.54 KB, application/octet-stream)
2012-02-14 12:19 EST, gregrwm
no flags Details

  None (edit)
Description gregrwm 2012-02-14 12:19:55 EST
Created attachment 561975 [details]
package list

Description of problem:
No protocol specified
Cannot open display:

Version-Release number of selected component (if applicable):
virt-viewer          0.4.1   7.el6

Steps to Reproduce:
0.  install rhel-server-6.2-x86_64-dvd.iso
1.  login (as g)
2.  vncserver <args>
3.  sudo xterm #run subsequent commands in the root xterm in Xvnc
4.  rhn_register
5.  alias vinst='virt-install -wbridge:br1 --accelerate'
6.  lvcreate -L 5G VGpecan6 -n6a
7.  vinst -r500 --disk path=/dev/VGpecan6/6a -n 6a -c/var/local/nfs/r6/rhel-server-6.2-x86_64-dvd.iso --os-variant=rhel6
8.  virsh list #6a running
9.  virt-viewer 6a
10. yum update
11. reboot
12. repeat steps 1-3
13. virsh list #6a running
14. virt-viewer 6a
  
Actual results: virt-install and virt-viewer both complain
No protocol specified
Cannot open display:

Expected results:
a virt-viewer window

Additional info:
am i missing a needed package?
Comment 2 gregrwm 2012-02-16 03:19:55 EST
umm, so, is virt-viewer simply DOA in rhel6.2?  is there anything i'm doing here that's out of the ordinary?
Comment 3 Daniel Berrange 2012-02-16 04:41:10 EST
> Cannot open display:

That means there is no DISPLAY environment variable set and thus virt-viewer cannot connect to the X server.
Comment 4 gregrwm 2012-02-16 10:37:27 EST
ok got it.  bizarre.  i can "su", and from there i can launch xterms, and those root xterms can launch other xterms ad infinitum, but as soon as the "su" process exits, none of the root xterms can launch anything anymore.  well clearly that's not a virt-install bug, sorry.  i've no idea which module, but clearly not well thought out behaviour.
Comment 5 Daniel Berrange 2012-02-16 12:36:27 EST
When you run 'su' it'll add an entry to your $HOME/.Xauthority file which gives the root applications the permission to connect the X server. When you exit 'su', I presume it is removeing the .Xauthority entry, which will prevent further apps from starting.

Note You need to log in before you can comment on or make changes to this bug.