You are not logged in.
I am running Openbox with Cairo-compmgr. X86_64 with Intel 915 graphics. When I try to use xterm, it starts normally, and operates nominally for 6 seconds, then it exits and returns 0. Invoking it using:
time xterm
yields run times of 6 +/- 0.2 seconds. Commands, quickly typed, operate correctly. The shell just exits.-- even if it is idling or if you are trying to type something
Xfce4 Terminal works fine. Entering the command, given above, in Xfce4 terminal blocks until the shell exits. My PS1 reports non-zero return values.
I've searched these forums, Arch bug reports and Google.
Any ideas?
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline
Any errors in the logs?
Offline
I should have mentioned that. No, nothing.
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline
Can you run xterm with a bare X server? Is it working OK?
When did it start happening, is it tied to some updates or config changes?
How do you start xterm: from the commandline, is it uxterm, some fancy fonts etc. Check you aliases, maybe somebody played some prank on you:
xxx () {
nohup xterm &
sleep 6
pkill xterm; }Offline
Can you run xterm with a bare X server? Is it working OK?
When did it start happening, is it tied to some updates or config changes?
How do you start xterm: from the commandline, is it uxterm, some fancy fonts etc. Check you aliases, maybe somebody played some prank on you:xxx () { nohup xterm & sleep 6 pkill xterm; }
I'm configured for Openbox only right now. I guess I'll rewicker my ~/.xinitrc tonight when I get home and try a X bare server.
The problem has popped up recently. About 2 weeks ago, I excised Gnome 3 from my system and it was working after that. I have a key binding that launches htop in xterm. I noticed the problem when that combination died after a few seconds. In debugging this, I tried just using xterm from gmrun and from tilda.
I like the script. This is my home laptop. I don't think my wife or daughters would try that; I also don't think they have the skills. Of course, I do have a SSH server facing the internet that does not require keys, but nothing out of the ordinary has shown up in /var/log/fail2ban.log
Never-the-less, I guess I'll check that too.
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline
Well. it is related to cairo-compmgr. Xterm seems to be sensitive to the Freeze plugin:
Freeze
Obscured windows frozen
Version: 0.3.0
I'll wager the timeout on whatever magic this plug in does is about 6 seconds ![]()
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline