X crashed, cannot open display in screen session for X apps

I had X crash and logged back in, and now in my screen session I can't open any apps that use X, ie.,:
~/.fluxbox # gedit keys
cannot open display:
Run 'gedit --help' to see a full list of available command line options.
~/.fluxbox #
Must I start a new screen to have it work again or can be fixed within current screen? Thanks for any help!

Looks like your DISPLAY variable isn't set? What does
$ echo $DISPLAY
show? If nothing, try the following in your screen session (you may have to do this for each shell within screen that you're running):
$ export DISPLAY=":0"
(assuming that it is DISPLAY 0, which is the default)
Last edited by nogoma (2008-08-12 17:17:54)

Similar Messages

I have update to iOS 8.1.3, and I cannot open both centers, or use and cancel apps, or the screen change color to gray, or the display do not recognise that I touch it, and more. If I restart it, I find another mistake in next five hours.Help me pls.

I have update to iOS 8.1.3, and I cannot open both centers, or use and cancel apps, or the screen change color to gray, or the display do not recognise that I touch it, and more. If I restart it, I find another mistake in next five hours. Help me please.
iOS 8.1.3
iPhone 5s 32 GB
CPU 64 bit

If you have an iPad 1, the max iOS is 5.1.1. For newer iPads, the current iOS is 6.0.1. For the iPad Mini the iOS is 6.0.2. The Settings>General>Software Update only appears if you have iOS 5.0 or higher currently installed.
iOS 5: Updating your device to iOS 5 or Later
http://support.apple.com/kb/HT4972
How to install iOS 6
http://www.macworld.com/article/2010061/hands-on-with-ios-6-installation.html
iOS: How to update your iPhone, iPad, or iPod touch
http://support.apple.com/kb/HT4623
If you are currently running an iOS lower than 5.0, connect the iPad to the computer, open iTunes. Then select the iPad under the Devices heading on the left, click on the Summary tab and then click on Check for Update.
Tip - If connected to your computer, you may need to disable your firewall and anitvirus software temporarily. Then download and install the iOS update. Be sure and backup your iPad before the iOS update. After you update an iPad (except iPad 1) to iOS 6.x, the next update can be installed via wifi (i.e., not connected to your computer).
 Cheers, Tom

(gnome-session:4336): Gtk-WARNING **: cannot open display.

I'm having troble getting gnome running on my system.
When I'm running gnome-session Im getting (gnome-session:4336): Gtk-WARNING **: cannot open display.
The exact same setup will allow me to run xfce4 without any problem.
I did manage to start gnome once with gdm, but then nothing but rightclick on the mouse and the desktop icons would work, and after that one time both gdm and gnome wont work.
I just did a base install of arch 0.7, xorg, gnome, nvidia and sound drivers.
Also, if I put exec gnome-session in my .xinitrc file I get a Fatal server error: Requested entity already in use.

the .xinitrc it is executed by the X window system after the X Server is started
if you run gnome-session from a console shell and there is no X server started, it cannot open the display...
the X server is normally started during "startx" or "xinit"
Last edited by danielsoft (2008-04-03 10:18:40)

Cannot open display error MATE

I installed MATE alongside XFCE but when I try to open MATE after I login at boot it just comes up with the error Cannot open display and it then exits?
I used the command:
exec mate-session
to try and start MATE.
Thanks
Al.
PS I've you need any more details about my system just ask.

Thats what I added to ~/.xinitrc as per the wiki.
#!/bin/sh
# ~/.xinitrc
#Executed by startx (run your window manager from here)
if [ -d /etc/X11/xinit/xinitrc.d ]; then
for f in /etc/X11/xinit/xinitrc.d/*; do
[ -x "$f" ] && . "$f"
done
unset f
fi
exec ck-launch-session mate-session
# exec gnome-session
# exec startkde
# exec startxfce4
# ...or the Window Manager of your choice

[SOLVED] Cannot open display: . Problem from Terminal

Hi,
I have a small problem with X I guess. I hope you can help me, as extensive googleling did not help.
I'm just configuring my arch install (newbie). Everything I have configured so far works great, the documentation is really good. I can start my xfce sessions an everything. However, I just wanted to look something up, when
$ xfce4-about
printed the following error:
xfce4-about: Cannot open display: .
This happened from terminal, not within a xfce-session.
Does anyone have an idea how I should proceed to eliminate this minor problem?
Thanks for your help in advance.
Last edited by jared (2012-02-22 04:38:21)

Seems you can't run xfce4-about from the non-X terminal, just like you can't run firefox.

Loosing X ... 'Error: cannot open display: localhost:11.0'

Hello, I hope some may be able to help me finding a solution to this X related problem.
Before Lion everything worked as expected.
From a terminal I
ssh -X user@linuxbox
and it work as expected... all the X application come back to my Mac.
but after a while (generaly not long ... about 5 to 10 min)
I cannot launch any X application anymore.
within my Terminal I get "Error: cannot open display: localhost:11.0"
and on the linuxbox side I get " sshd[xxxx]: channel 4: open failed: administratively prohibited: open failed"
Running 10.7.1. fully updated (from my 10.6.8 Mac I do not have this problem
... and never had)
Thanks in advance for your help
PhS

'arch' is set as the alias for localhost. I never entered 'arch' anyway, that's just what the error said.
e: I tried ssh-ing into a X session on another laptop running an Ubuntu live CD. I can ssh into it normally, but when I run 'xinit -e ssh -XCT [email protected] gnome-session -- :1' it just starts a new X session on ctrl+alt+F8 using my startx file, rather than the one on the other computer.
Last edited by Yes (2008-07-11 19:17:28)

XOrg - Error: cannot open display: 0

I was recently using 'play on linux' to play 'League Of Legends' when the game crashed. On reboot and starting my GUI using 'startx' my GUI worked for about 40 seconds, after that I lost the ability to exit/restart my Window Manager(i3) or start any new programs. If I try to start a program from a previously existing terminal window I get something along the lines of 'Error: Cannot Open Display :0'.
I can still switch workspaces and seemingly operate already existing terminal windows.
This happens on every boot. My only known method of exiting the GUI is to restart the Machine. The 'echo $DISPLAY' command returns ':0'. I dont seem to have /var/log/Xorg.0.log' or '/var/log/Xorg.log'. Im posting from my phone.
I have already uninstalled Play on Linux, and reinstalled xorg-server.

VexatioN wrote:If I try to start a program from a previously existing terminal window I get something along the lines of 'Error: Cannot Open Display :0'
https://bbs.archlinux.org/viewtopic.php?id=57855
VexatioN wrote:I dont seem to have /var/log/Xorg.0.log' or '/var/log/Xorg.log'
Look in ~/.local/share/xorg/Xorg.0.log
Anything in the journal?

[Solved] "cannot open display" after suspend/resume, possibly broadcom

Hey peoples,
[EDIT: I think my initial assumptions are incorrect, this issue seems to be occurring independently of whatever wifi driver I have loaded]
I'm finding that after suspend/resume my machine will not open any new windows. The windows that were already open continue to function. If I've left a terminal open, and attempt to open a new window I get the message:
[framps@localhost ~]$ firefox
Invalid MIT-MAGIC-COOKIE-1 keyInvalid MIT-MAGIC-COOKIE-1 keyError: cannot open display: :0.0
I've found that removing the broadcom-wl driver from my system seems to fix the issue. I can't see anything particularly obvious in my dmesg. I think I need the broadcom-wl driver as I have not been able to get b43 or bcma to work for my machine.
[ 948.814261] cfg80211: World regulatory domain updated:
[ 948.814266] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 948.814269] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 948.814272] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 948.814275] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 948.814277] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 948.814280] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 949.404722] r8169 0000:0c:00.0 eth0: link down
[ 949.404741] r8169 0000:0c:00.0 eth0: link down
[ 949.404773] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 949.355635] PM: Syncing filesystems ... done.
[ 949.717960] PM: Preparing system for mem sleep
[ 949.851316] Freezing user space processes ... (elapsed 0.01 seconds) done.
[ 949.862059] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
[ 949.875377] PM: Entering mem sleep
[ 949.875472] Suspending console(s) (use no_console_suspend to debug)
[ 950.064255] xhci_hcd 0000:00:14.0: WARN Event TRB for slot 1 ep 0 with no TDs queued?
[ 950.064507] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[ 950.075138] sd 0:0:0:0: [sda] Stopping disk
[ 950.165918] ERROR @wl_notify_scan_status : Scan complete while device not scanning
[ 950.477845] i915 0000:00:02.0: power state changed by ACPI to D3hot
[ 950.551140] PM: suspend of devices complete after 676.056 msecs
[ 950.551485] PM: late suspend of devices complete after 0.342 msecs
[ 950.567669] r8169 0000:0c:00.0: wake-up capability enabled by ACPI
[ 950.581418] ehci_hcd 0000:00:1d.0: wake-up capability enabled by ACPI
[ 950.594384] ehci_hcd 0000:00:1a.0: wake-up capability enabled by ACPI
[ 950.620974] xhci_hcd 0000:00:14.0: wake-up capability enabled by ACPI
[ 950.634321] PM: noirq suspend of devices complete after 82.939 msecs
[ 950.634762] ACPI: Preparing to enter system sleep state S3
[ 950.730816] PM: Saving platform NVS memory
[ 950.736910] Disabling non-boot CPUs ...
[ 950.738461] smpboot: CPU 1 is now offline
[ 950.840631] smpboot: CPU 2 is now offline
[ 950.943831] smpboot: CPU 3 is now offline
[ 950.944231] Extended CMOS year: 2000
[ 950.945389] ACPI: Low-level resume complete
[ 950.945427] PM: Restoring platform NVS memory
[ 950.945811] Extended CMOS year: 2000
[ 950.945864] Enabling non-boot CPUs ...
[ 950.949268] smpboot: Booting Node 0 Processor 1 APIC 0x1
[ 950.963117] CPU1 is up
[ 950.966520] smpboot: Booting Node 0 Processor 2 APIC 0x2
[ 950.980330] CPU2 is up
[ 950.980386] smpboot: Booting Node 0 Processor 3 APIC 0x3
[ 950.994238] CPU3 is up
[ 950.997398] ACPI: Waking up from system sleep state S3
[ 951.471580] i915 0000:00:02.0: power state changed by ACPI to D0
[ 951.498111] xhci_hcd 0000:00:14.0: wake-up capability disabled by ACPI
[ 951.524753] ehci_hcd 0000:00:1a.0: wake-up capability disabled by ACPI
[ 951.551380] ehci_hcd 0000:00:1d.0: wake-up capability disabled by ACPI
[ 951.564744] nvidia 0000:01:00.0: power state changed by ACPI to D0
[ 951.591567] PM: noirq resume of devices complete after 120.295 msecs
[ 951.591837] PM: early resume of devices complete after 0.236 msecs
[ 951.591891] i915 0000:00:02.0: setting latency timer to 64
[ 951.591894] xhci_hcd 0000:00:14.0: setting latency timer to 64
[ 951.591968] mei 0000:00:16.0: irq 43 for MSI/MSI-X
[ 951.591983] ehci_hcd 0000:00:1a.0: setting latency timer to 64
[ 951.592037] ehci_hcd 0000:00:1d.0: setting latency timer to 64
[ 951.592108] ahci 0000:00:1f.2: setting latency timer to 64
[ 951.592119] snd_hda_intel 0000:00:1b.0: irq 46 for MSI/MSI-X
[ 951.594182] r8169 0000:0c:00.0: wake-up capability disabled by ACPI
[ 951.634511] [drm:__gen6_gt_force_wake_mt_get] *ERROR* Timed out waiting for forcewake old ack to clear.
[ 951.636110] [drm] Enabling RC6 states: RC6 on, RC6p on, RC6pp off
[ 951.796066] r8169 0000:0c:00.0 eth0: link down
[ 951.824070] Extended CMOS year: 2000
[ 951.831119] usb 3-1.3: reset full-speed USB device number 3 using ehci_hcd
[ 951.910921] ata5: SATA link down (SStatus 0 SControl 300)
[ 951.916168] btusb 3-1.3:1.0: no reset_resume for driver btusb?
[ 951.916171] btusb 3-1.3:1.1: no reset_resume for driver btusb?
[ 951.924226] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 951.926030] ata2.00: configured for UDMA/100
[ 951.981369] usb 4-1.6: reset high-speed USB device number 3 using ehci_hcd
[ 952.876326] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 952.877743] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
[ 952.877747] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
[ 952.877750] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
[ 952.880489] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
[ 952.880493] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
[ 952.880496] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
[ 952.881600] ata1.00: configured for UDMA/100
[ 952.893105] sd 0:0:0:0: [sda] Starting disk
[ 952.911681] PM: resume of devices complete after 1321.544 msecs
[ 952.912745] PM: Finishing wakeup.
[ 952.912748] Restarting tasks ... done.
[ 953.018321] video LNXVIDEO:00: Restoring backlight state
[ 953.018862] video LNXVIDEO:01: Restoring backlight state
[ 953.376503] r8169 0000:0c:00.0 eth0: link up
[ 953.376515] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Any help would be greatly appreciated. Thanks.
Last edited by frampy (2013-03-16 01:20:57)

It seems that the only option for my wifi card, BCM43228 is the proprietary broadcom-wl.
Can anyone suggest how I might be able to get any debugging information for this module? Maybe this driver is conflicting with something else on my system, as I can't find anyone else that is seeing this same issue.
Very frustrating, my machine is a Thinkpad Edge E530. Because I ordered from New Zealand there was no option to include the alternative Intel card and I was stuck with the broadcom. Apparently there's a whitelist on the BIOS aswell which will prevent me from installing another card.

"cannot open display" error meaning

I'm trying to get dwm running for a while now, and when I try to run it, it says "cannot open display". Then I thought, ok, maybe i have to install an X server, so I got Xorg, installed it, removed dwm and then recompiled it, but I got the same error. Then I thought that maybe I didn't have the right configurations (even though I never bothered config.h or config.mk), so I got gnome (hoping that it would auto-configure itself) so that I can test if it's something with dwm or some other problem with the system. When I tried to start gnome, I got the "cannot open display" error, again (my keyboard will never forgive me for what I did when I saw that).
I went through dwm's wiki more than once, googled the problem, read about Xorg, I just don't know what I'm doing wrong.
Everything was done on a fresh netinstall.
Could you please help me out with this? (Or just link me to somewhere I can find some meaningful information about the problem)
Last edited by imv (2012-04-01 15:02:00)

@lifeafter2am I read that, xorg_server and xorg_apps were already installed, since I installed xorg (as in, the whole xorg package). xinit, startx ~/.xinitrc and /etc/X11/xinit/xinitrc , all files/programs mentioned in the wiki, ar missing, though, perhaps it's a hint of some sort
@istbrad212 the video card driver was already installed
Sorry for the slow responses, I have to constantly reboot in order to try everything.

Gtk-WARNING **: cannot open display [Solved]

Hello,
I've just installed openbox and experimenting with it. But I'am unable to run any panel. Ive already install lxpanel, fbpanel, plank, but each time I try to launch them from the terminal I get the same error massages. Firefox, leafpad, terminal, all launch properly, only the panels I can't make them run. Any idea how to solve this?
[mak@myhost ~]$ fbpanel
(fbpanel:688): Gtk-WARNING **: cannot open display:
[mak@myhost ~]$
[mak@myhost ~]$ plank
[INFO 19:09:21.484514] [AbstractMain:170] Plank version: 0.7.1
[INFO 19:09:21.484627] [AbstractMain:171] Kernel version: 3.17.6-1-ARCH
[INFO 19:09:21.484704] [AbstractMain:172] GLib version: 2.42.1
[INFO 19:09:21.484784] [AbstractMain:173] GTK+ version: 3.14.6
[INFO 19:09:21.484850] [AbstractMain:175] + HiDPI support enabled
[INFO 19:09:21.484915] [AbstractMain:177] Wnck version: 3.4.9
[INFO 19:09:21.485001] [AbstractMain:178] Cairo version: 1.14.0
[INFO 19:09:21.485081] [AbstractMain:179] Pango version: 1.36.8
Unable to init server: Could not connect: Connection refused
[WARN 19:09:21.493039] [Gtk] cannot open display:
[mak@myhost ~]$
Last edited by jmak (2014-12-19 00:25:02)

karol wrote:
The display should be set on its own. It's
$ echo $DISPLAY
:0
for my first X server and
$ echo $DISPLAY
:1
for the other one I'm running.
How exactly do you start X?
I start manually,
startx

Gtk-WARNING **: cannot open display:

Hi Folks,
Has anyone every came across this problem when trying to run firefox remotely? I use putty to connect to my solaris box but cannot display back firefox as the following error occurs :
Gtk-WARNING **: cannot open display:
When I run echo $DISPLAY nothing is returned. I have also tried setting the display using the following command :
export DISPLAY=0:0
Nothing seems to work.
Can anyone help?

Hi Jacob,
You are seeing the warning because your machine does not have an Xserver running which is needed to convert to postscript using the command line (with Reader 7.0.9).
If running an Xserver is not an option for you, you could upgrade to the latest version of Reader (8.1.2) in which this issue has been fixed.
Sincerely,
Neha

Ttatsc: cannot open display 'unix:10'

Hi,
in integrated an winxp-"server" (winxp, windows-rdp-application) into SGD v4.40.917
running on fedora-core8. If i log in to SGD and start the application, i got the Error message
shown below.
If i connect via "ssh -X" to the SGD server and run rdesktop to the winxp, all works fine.
Running "xclock"or "xterm (ssh)" via SGD on the SGD-server works also ...
Could somebody help me to track down this problem ?
regards
Danny
Third tier output log:
The current launch has failed.
If the problem persists, restart the server.
2008/07/22 18:03:49.531 pem/launch #4
Sun Secure Global Desktop Software(4.4) ERROR:
ErrTransportNotAvailable
Script 14444 exited with code 0 and signal 6
Standard error of script process:
ttatsc: cannot open display 'unix:10' (error = 1)
ErrCommandExecutionFailed
Third tier output log:
The current launch has failed.
If the problem persists, restart the server.

did you have answer to this question?

"cannot open display" with cron script

This works fine from the CLI, but when it runs with the cron daemon, the log file shows "xfburn: cannot open display." How do I go about fixing this?
#!/usr/bin/perl -w
`xfburn --version > /home/tim/scripts/blah.log`;

Hmm I'm not really sure what to do with that. I'll post the whole thing. This is my first time writing in perl, so I'm sure it's really inefficient and ugly.
It's supposed to grab 'svn info' from all my svn packages in /var/local/abs, find my currently installed versions of the svns, and write the results to ~/scripts/svn-updates/outdated.log file.
It works correctly when I run it from the command line, but when I put it in cron.daily, "@svninfo = `$pkgname --version --display=:0.0`;" doesn't work.
#!/usr/bin/perl -w
use strict;
our (@svns, %local_revs, %latest_revs);
our $svn_dir = "/var/abs/local";
our $outdated_log = "/home/tim/scripts/svn-updates/outdated.log";
# Get list of local svn packages
sub get_svns {
my ($name, @svns_results);
opendir(DIR, $svn_dir) or die "Error opening $svn_dir: $!";
foreach $name (readdir(DIR)) {
if($name =~ /(.*)-svn$/) {
push(@svns_results,$1);
closedir(DIR);
return @svns_results;
# Get latest svn revisions
sub get_latest_revs {
my ($pkgname, $svntrunk, $i, @svninfo, %latest_revs_results);
foreach $pkgname (@_) {
# Find trunk path in PKGBUILD
open(INFILE, "$svn_dir/$pkgname-svn/PKGBUILD");
while(<INFILE>) {
if(/^_svntrunk="(.*)"/) {
$svntrunk = $1;
close(INFILE);
# Grab svn info on current package
@svninfo = `svn info $svntrunk`;
# Add latest revision to hash table
foreach $i (@svninfo) {
if($i =~ /^Revision: (\w*)/) {
$latest_revs_results{$pkgname} = $1;
return %latest_revs_results;
# Get local svn revisions
sub get_local_revs {
my ($pkgname, $j, @svninfo, %local_revs_results);
foreach $pkgname (@_) {
@svninfo = `$pkgname --version --display=:0.0`;
# Add local revision to hash table
foreach $j (@svninfo) {
if($j =~ /^.*svn-(\w*)/) {
$local_revs_results{$pkgname} = $1;
return %local_revs_results;
# Write outdated packages to $outdated_log
sub write_outdated {
my $pkg;
`echo > $outdated_log`;
foreach $pkg (@_) {
unless($local_revs{$pkg}==$latest_revs{$pkg}) {
`echo "$pkg $local_revs{$pkg} ($latest_revs{$pkg})" >> $outdated_log`;
# Main
@svns = &get_svns;
%latest_revs = &get_latest_revs(@svns);
%local_revs = &get_local_revs(@svns);
&write_outdated(@svns);

[SOLVED] Chromuim: Gtk-WARNING **: cannot open display:

I've just tried to install chromium, but the program doesn't start.
From terminal I recieve this:
[7183:7183:4023157347:FATAL:chrome/browser/browser_main.cc(537)] Check failed: profile. Cannot get default profile.
Abortito
trying as root:
[federico@giunta-desktop ~]$ su
Password:
[root@giunta-desktop federico]# chromium
No protocol specified
(chromium:7209): Gtk-WARNING **: cannot open display: :0
How can I fix this problem?
Last edited by FeDiX 91 (2010-09-02 16:47:46)

FeDiX 91 wrote:
i found a sort of fix to this problem, but I have to repeat it ever time i launch the app...
This is the link: [lnk]http://ubuntuforums.org/archive/index.php/t-166863.html[/lnk]
another question which han nothing to do whith this... are there some shortcuts in this site for html codes? thanks
Using xhost+ creates automatically a security problem for Xorg, do NOT do that.

[Solved] Cannot open display :0.0

Yup, the xhost thing fixed it (although I had to use localhost rather than local). Thanks!
I sometimes use secondary accounts by way of profile control, that is if I want to try programs with different settings I'll su to a different shell account. Up until this week when I upgraded to the latest everything, I could open an xterm, su to my secondary login, and start firefox or whatever just fine.
Now suddenly I can't do that; I get two lines of
No protocol specified
and then
Error: Cannot open display: :0.0
And one more
No protocol specified
I'm sure it's a permissions issue, and probably fixes a security hole from previous versions; root can still do this but not my non-root accounts. Any idea which device files I need to modify to allow account B to open a window on account A's desktop?
Last edited by WyoPBS (2011-12-29 04:15:59)

try
xhost +local:
in your primary account.
Also check these topics:
https://bbs.archlinux.org/viewtopic.php?id=45941
https://bbs.archlinux.org/viewtopic.php?id=122848

X crashed, cannot open display in screen session for X apps

Similar Messages

Maybe you are looking for