cannot open display; WAS: no video signal after loading DE

capoeira · 2014-02-08 21:23:43

this started yesterday with "Gtk-WARNING **: cannot open display" errors when trying to start any program.
I rebooted sometimes and the problem was gone suddenly

but today (next boot), i have this huge problem:
x11 seams to start because slim´s login screen shows up;
than after the login and the DE start ( i tested two DEs) my monitor (TV actualy; HDMI) shows the "no signal" message.

I found this thread: https://bbs.archlinux.org/viewtopic.php?id=59575
and actually I just yesterday switched the router!!!!!!!!
but i use connman (econnman) and i don´t seam to have "nm-system-settings.conf" which was pointed out as the culprit

i uninstalled connman to see if it would solve the problem, but no

i connected to the old router to see if it solves, but no

help me; where do i start to solve this?

EDIT: this is the worst problem i ever had with linux......i can´t use my instalation.....this sucks so much

one thing in slim.log wich is repeating a lot at the end: "waiting for xserver to accept connections"

Last edited by capoeira (2014-02-13 11:52:49)

capoeira · 2014-02-09 10:18:14

delete

Last edited by capoeira (2014-02-09 13:38:56)

jasonwryan · 2014-02-09 17:06:57

You have been warned before about post blanking: https://wiki.archlinux.org/index.php/Fo … way_Street
This is your final warning.

Read your Xorg.log and check your journal.

capoeira · 2014-02-09 17:53:55

show some compassion for someone who doesnt have a working system for almost 24 hours

added nomodeset to kernel line in grub:

now it shows error message on screen> http://www.divshare.com/image/25152416-428

i tried adding intel_agp and i915 to modules to initramfs > didnt solve

after adding acpi=off to kernel line i get: http://www.divshare.com/image/25152672-676

journal shows this for the last boot: http://www.divshare.com/image/25152675-95b

adding acpi=noirq to kernel line results in the no signal message form monitor again

if someone has mercy to help a desperated, i would be thankfull

EDIT: only now i see that i am logged in @new-host
what is going on?

Last edited by capoeira (2014-02-09 18:50:31)

ewaller · 2014-02-09 18:50:07

Okay, I just came across this thread after having closed the thread you to which you linked in your OP. Let's keep the discussion here.

Before I get into your problem, as Jason pointed out, we consider post blanking to be discourteous. It is also unhelpful. As an engineer, I learned way back in school never to erase or discard any of my notes. If one finds they are way off base, it is best to draw a line though it and move on. Later, when someone else comes across your work, or when you go back over what you have done, one has the benefit of seeing the thought process, and what did and did not work. The content in the blanked post is forever gone to me. Furthermore, don't beg or grovel. It is off-putting, many of us stop reading when we encounter it. You may want to read the article linked in my signature.

Enough with the lecture. When you have the no-signal indication, change to a different console (Ctrl-Alt-F2 or F3 through F6), log in, and look at /var/log/Xorg.0.log for clues. Also, look at the journal and the output of dmesg. If you wish, go ahead and pastebin the output and post the links here. To do that, look at wgetpaste.

capoeira · 2014-02-09 19:40:20

ewaller wrote:

When you have the no-signal indication, change to a different console (Ctrl-Alt-F2 or F3 through F6).

nothing happens

ewaller wrote:

look at /var/log/Xorg.0.log for clues.

http://bpaste.net/show/177316/

i dont see error message

ewaller wrote:

Also, look at the journal.

http://bpaste.net/show/177319/

didnt see nothing either

ewaller wrote:

and the output of dmesg

http://bpaste.net/show/177322/

seams normal?

also this:

capoeira wrote:

EDIT: only now i see that i am logged in @new-host
what is going on?

vesa driver gives me a desktop, but it is unusable (part of the right side of the screen is on the left side, some part hidden)

ewaller · 2014-02-09 19:50:09

capoeira wrote:

ewaller wrote:
When you have the no-signal indication, change to a different console (Ctrl-Alt-F2 or F3 through F6).
nothing happens

What does that mean? Did you get a console? or did the monitors all indicate "No Signal"?
If not, how did you get the logs?

It appears from your Xorg log, that it starts normally, uses the Intel driver, then exits normally. This indicates you have a problem with your .xinitrc file. For whatever reason, the script is exiting and Xorg terminates. You might share your .xinitrc file with us. Also, for now, disable slim. Log in from the console, and use startx. When the script terminates, you will be able to see the messages that had been output by the script and your window manager.

capoeira · 2014-02-09 20:02:45

ewaller wrote:

capoeira wrote:
ewaller wrote:
When you have the no-signal indication, change to a different console (Ctrl-Alt-F2 or F3 through F6).
nothing happens
What does that mean? Did you get a console? or did the monitors all indicate "No Signal"?
If not, how did you get the logs?
It appears from your Xorg log, that it starts normally, uses the Intel driver, then exits normally. This indicates you have a problem with your .xinitrc file. For whatever reason, the script is exiting and Xorg terminates. You might share your .xinitrc file with us. Also, for now, disable slim. Log in from the console, and use startx. When the script terminates, you will be able to see the messages that had been output by the script and your window manager.

yes, it continued with "No Signal"

i got the output on next boot after hard reset, since i allready have had disabled slim.service

but, thanks a lot for your time but I guess it was E18 related

I do not know what happened but after renaming .e folder (E18 config folder) the desktop is running again.
no clue what happened

gues i just configure my desktop again instead of loosing more time to find out what the problem was.

i feel kind of stupid now, having done all this crying....so sorry

Last edited by capoeira (2014-02-09 20:03:52)

capoeira · 2014-02-13 12:02:32

so, i'm stil having the problem which had originated my DE problem later (which I solved)

it seams that on evry first login I get the "Gtk-WARNING **: cannot open display" problem.
i than have to logout from DE and login again, than progams start

solutions I found are related to Networkmanager, which I don't use.
for example here: https://bbs.archlinux.org/viewtopic.php?id=59575
but as in this thread this began on my machine at the same time i switched to my neighbours router

also I noticed that my hostname is "new-host" in terminal. that has to be related
and again solutions I found are related to Networkmanager, which I don't use.
for example here: https://bbs.archlinux.org/viewtopic.php?id=156413

I'm using connman (econnman), and I tried wicd afterwards, which doesn't solve

since I was asked (I doubt it is related), my .xinitrc:

#!/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 gnome-session
# exec startkde
# exec startxfce4
# exec wmaker
# exec icewm
# exec blackbox
# exec fluxbox
# exec openbox-session

#        exec enlightenment_start dbus-launch
 exec enlightenment_start

exec xterm

jasonwryan · 2014-02-13 17:15:41

xinitrc page on Arch Wiki wrote:

Note: Make sure to uncomment only one exec line, since that will be the last command run from the script; all the following lines will just be ignored.

capoeira · 2014-02-13 17:55:34

jasonwryan wrote:

xinitrc page on Arch Wiki wrote:
Note: Make sure to uncomment only one exec line, since that will be the last command run from the script; all the following lines will just be ignored.

i know; if the last one is ignored, what's the problem? but i'll coment out. but i doubt this is the problem

Last edited by capoeira (2014-02-13 18:26:24)

capoeira · 2014-02-18 11:13:30

jasonwryan wrote:

xinitrc page on Arch Wiki wrote:
Note: Make sure to uncomment only one exec line, since that will be the last command run from the script; all the following lines will just be ignored.

so, this didn't solve

and things are getting worse, i now have to login about 3-4 times until DE works

i would like to solve this "new-host" problem, to see if this is the culprit
i didn't found info on this in wiki.

I have 3 files in /etc:

#
# /etc/host.conf
#

order hosts,bind
multi on

# End of file

  GNU nano 2.2.6           Arquivo: /etc/hostname

studiohost

#
# /etc/hosts: static lookup table for host names
#

#<ip-address>   <hostname.domain.org>   <hostname>
127.0.0.1       localhost.localdomain   localhost myhost
::1             localhost.localdomain   localhost myhost

# End of file

anything suspicious?

Arch Linux

#1 2014-02-08 21:23:43

cannot open display; WAS: no video signal after loading DE

#2 2014-02-09 10:18:14

Re: cannot open display; WAS: no video signal after loading DE

#3 2014-02-09 17:06:57

Re: cannot open display; WAS: no video signal after loading DE

#4 2014-02-09 17:53:55

Re: cannot open display; WAS: no video signal after loading DE

#5 2014-02-09 18:50:07

Re: cannot open display; WAS: no video signal after loading DE

#6 2014-02-09 19:40:20

Re: cannot open display; WAS: no video signal after loading DE

#7 2014-02-09 19:50:09

Re: cannot open display; WAS: no video signal after loading DE

#8 2014-02-09 20:02:45

Re: cannot open display; WAS: no video signal after loading DE

#9 2014-02-13 12:02:32

Re: cannot open display; WAS: no video signal after loading DE

#10 2014-02-13 17:15:41

Re: cannot open display; WAS: no video signal after loading DE

#11 2014-02-13 17:55:34

Re: cannot open display; WAS: no video signal after loading DE

#12 2014-02-18 11:13:30

Re: cannot open display; WAS: no video signal after loading DE

Board footer