You are not logged in.
Hello everybody,
I am encountering the following problem:
I use openbox as my display manager. After startup i can open new windows just usual. About 5 seconds after openbox has started, I can't open new windows anymore. When I switch to tty1 I see the following message: INVALID MIT-MAGIC-COOKIE: can't open display.
my .xinitrc contains nothing but exec openbox-sessions
the openbox autostart file looks like this:
tint2 &
conky &
fbsetbg -c images/arch_linux_1440x900.png &I tried to use other Window Managers like fluxbox and Gnome3, no problems there.
thanks for your help!
Last edited by mhfj (2012-04-22 11:31:19)
Offline
What login manager do you use? Do you have dbus and consolekit running for the session? For example, latest slim 1.3.3 takes care of consolekit and dbus for your session, older does not. You can try ; exec dbus-launch ck-launch-session openbox-session in your .xinitrc.
Offline
i don't use a login manager, only startx.
i used to have my .xinitrc look like you described, but to find out, what the problem is, so i took them out ouf th .xinitrc.
Offline
And you get this issue when just logging in locally as a normal user (not using ssh X11 forwarding, logging in as root or whatever)?
What does your Xorg.log say?
Burninate!
Offline
yes, i log in as a normal user on a local machine.
I found out, this might be network-manager related. Right when network-manager connects to my wireless network at home I can't open new windows from inside openbox. Killing X and doing a fresh startx "solves" this problem.
My Xorg.log: http://pastebin.com/g4y01ZaC
I am not shure how a connection to a wlan could disconnect openbox from X.
Last edited by mhfj (2012-04-20 16:07:03)
Offline
Now that's an interesting turn of events indeed. Would you mind posting the content of the config files located in /etc/NetworkManager?
Last edited by Gcool (2012-04-20 16:24:10)
Burninate!
Offline
this is the configuration file for the network i connect to. I didn't create them by hand, nm-applet did his for me.
[connection]
id=****
uuid=****
type=802-11-wireless
[802-11-wireless]
ssid=****
mode=infrastructure
mac-address=***
security=802-11-wireless-security
[802-11-wireless-security]
key-mgmt=wpa-psk
psk=******
[ipv4]
method=auto
[ipv6]
method=autothe NetworkManager.conf:
[main]
plugins=keyfileso... nothing strange here, i think.
I found out this only happens wehn i connect to a wireless network.
Offline
This is a bit of a hunch/guess; but could you check if your /etc/hosts file differs in any way prior to and after networkmanager connects?
If you see any changes in your localhost entry, try removing the "host_name" entry from the "A list of options to request from the DHCP server" in /etc/dhcpd.conf and see if that makes any difference.
Last edited by Gcool (2012-04-20 18:02:53)
Burninate!
Offline
Yes, possibly nm changes the hostname after connecting, and then the .Xsession auth cookie (which has the hostname in it) doesn't work any more, since the name doesn't match.
Offline
Yes, you were right, that did it. Thanks a lot for the help everybody!
Offline