Eterm won't run causing X to exit

[BSDRich]

I'm using Fluxbox and when I try to run Eterm it dumps me out to the command line. Maybe it's a shell but I don't know how to exit it if it is. If I type exit I get logged out. I can type startx to get back to the desktop. Are there any logs I can check? I have no idea why it won't run. Any ideas?

FreeBSD 7.2 64
Intel Core 2 Duo
2G RAM

[graudeejs]

I think your ~./xinitrc is not written correctly. (show it to us)

I use fvwm, here's how mine looks.

rm -Rf ~/Desktop
LC_ALL='en_GB.UTF-8'
LC_CTYPE='en_GB.UTF-8'
LANG='en_GB.UTF-8'
export LC_ALL LC_CTYPE LANG

exec fvwm &

(note first and last line)
last line with exec and & at the end


also I think, that
x11/rxvt-unicode is much better terminal
I bet you use Esetroot which comes with Eterm to display wallpapers
Instead of Esetroot I use graphics/hsetroot - it's great

[Beastie]

rm -Rf ~/Desktop
[...]



Why would you remove your Desktop every time you initialize X?

[graudeejs]

Because that folder pisses me off.
I don't use it, I have no desktop icons, and it drives me nuts, when I see folders in my home, which are empty.
I like my directory structure, and I hate, when someone forces me to change it.

~/Desktop is useless to me, if I knew other way to disable it, I would use it.

[BSDRich]

It's a fresh new system, all it has is one line that reads;

exec fluxbox

Does it need more?

[graudeejs]

add & at the end of line

exec fluxbox &

and that should work

[Beastie]

The ampersand is only useful if you want a command to run in the background so that it doesn't block subsequent commands. But it's unnecessary if the command is the last (or only) one, as is the case here.


exec fluxbox should be enough in .xinitrc if you start X using xinit or startx.
Do you always start X this way?

Also, how are you running Eterm? Is it on your Fluxbox root menu and you're just clicking it or what?

Have you tried running Xterm instead. What happens then?

If there is any problem, X usually prints error messages on the tty that was used to start it. So, when you get kicked out, what message(s) do you see?

[lme@]

Actually exec startfluxbox is better as it reads ~/.fluxbox/startup where you can put all the programs you want to execute.

[BSDRich]

I hate to sound like a newb but it's working now. I was going to run it to get the info you wanted but it worked. Since the problem happened I've upgraded ports and installed a lot of stuff. Maybe some files that were needed got installed, I don't know but thanks for the help.

[BSDRich]

Jesus christ, now it's doing it again. I turned on my machine today and executed Eterm that was working yesterday and now it dumps me out to that command line again. This is so frustrating, I spend more time working on the computer than actually using it.

[BSDRich]

"exec fluxbox should be enough in .xinitrc if you start X using % xinit or % startx."
Do you always start X this way?

After I login I just type startx from the command line.


"Also, how are you running Eterm? Is it on your Fluxbox root menu and you're just clicking it or what?"

I type "Eterm" in the xterm and after I get it working the way
I want I put that command line in the fluxbox menu file.


"Have you tried running Xterm instead. What happens then?"

Works without problem.


"If there is any problem, X usually prints error messages on the tty that was used to start it. So, when you get kicked out, what message(s) do you see?"


Failed to read: session.screen0.titlebar.right
Setting default value
Waiting for X server to shut down XIO:
fatal IO error 35 (Resource temporarily unavailable) on X server ":0.0"
after 545 requests (542 known processed) with 1 events remaining.
info: [drm] Resetting GPU
Output CRT2 disable success
Blank CRT0 success
Disable CRT0 success
Disable CRT1 success
Enable CRT0 success
Unblank CRT0 success

Without any typos of course, I transcribed this to paper then typed it here. It is intermittent. It did work once today but then not anymore. I didn't change anything but I did notice my mouse cursor when I got dumped to the command line. What does that tell us?

[Daisuke_Aramaki]

Failed to read: session.screen0.titlebar.right
Setting default value

This one seems like an error with the init file in your .fluxbox directory. Can you paste the contents of your init file here? It should be ~/.fluxbox/init

Also use the code tags to paste text.

[BSDRich]

It worked a few times today so I started using it then after a few xterm sessions it bombed out again and dumped me to the command prompt.



session.screen0.tab.placement: Top
session.screen0.tab.width: 64
session.screen0.tab.height: 16
session.screen0.slit.layer: Dock
session.screen0.slit.onhead: 0
session.screen0.slit.alpha: 255
session.screen0.slit.onTop: False
session.screen0.slit.acceptKdeDockapps: true
session.screen0.slit.maxOver: false
session.screen0.slit.autoHide: false
session.screen0.slit.placement: RightBottom
session.screen0.menu.alpha: 255
session.screen0.toolbar.tools: workspacename, prevworkspace, nextworkspace, iconbar, systemtray, prevwindow, nextwindow, clock
session.screen0.toolbar.alpha: 255
session.screen0.toolbar.layer: Dock
session.screen0.toolbar.maxOver: false
session.screen0.toolbar.placement: BottomCenter
session.screen0.toolbar.visible: true
session.screen0.toolbar.onhead: 0
session.screen0.toolbar.height: 0
session.screen0.toolbar.widthPercent: 66
session.screen0.toolbar.onTop: False
session.screen0.toolbar.autoHide: false
session.screen0.window.focus.alpha: 255
session.screen0.window.unfocus.alpha: 255
session.screen0.clientMenu.usePixmap: true
session.screen0.overlay.lineWidth: 1
session.screen0.overlay.lineStyle: LineSolid
session.screen0.overlay.joinStyle: JoinMiter
session.screen0.overlay.capStyle: CapNotLast
session.screen0.tabs.usePixmap: true
session.screen0.tabs.maxOver: false
session.screen0.tabs.intitlebar: true
session.screen0.iconbar.usePixmap: true
session.screen0.iconbar.iconTextPadding: 10l
session.screen0.iconbar.iconWidth: 70
session.screen0.iconbar.alignment: Relative
session.screen0.iconbar.mode: {static groups} (workspace)
session.screen0.menuDelayClose: 200
session.screen0.opaqueMove: false
session.screen0.maxIgnoreIncrement: true
session.screen0.userFollowModel: Follow
session.screen0.edgeSnapThreshold: 10
session.screen0.windowScrollAction:
session.screen0.autoRaise: true
session.screen0.rowPlacementDirection: LeftToRight
session.screen0.tabFocusModel: ClickToTabFocus
session.screen0.maxDisableMove: false
session.screen0.workspaces: 4
session.screen0.windowScrollReverse: false
session.screen0.tooltipDelay: 500
session.screen0.clickRaises: true
session.screen0.windowMenu: /home/Rich/.fluxbox/windowmenu
session.screen0.workspaceNames: one,two,three,four,
session.screen0.colPlacementDirection: TopToBottom
session.screen0.maxDisableResize: false
session.screen0.windowPlacement: RowSmartPlacement
session.screen0.strftimeFormat: %k:%M
session.screen0.allowRemoteActions: false
session.screen0.menuMode: Delay
session.screen0.defaultDeco: NORMAL
session.screen0.noFocusWhileTypingDelay: 0l
session.screen0.focusNewWindows: true
session.screen0.menuDelay: 200
session.screen0.workspacewarping: true
session.screen0.focusModel: ClickFocus
session.screen0.rootCommand: fbsetbg ~/Pictures/wave.jpg
session.screen0.followModel: Ignore
session.screen0.showwindowposition: true
session.screen0.fullMaximization: false
session.slitlistFile: ~/.fluxbox/slitlist
session.opaqueMove: False
session.cacheMax: 200l
session.tabPadding: 0
session.imageDither: True
session.autoRaiseDelay: 250
session.appsFile: ~/.fluxbox/apps
session.configVersion: 10
session.menuFile: ~/.fluxbox/menu
session.ignoreBorder: false
session.cacheLife: 5l
session.tabsAttachArea: Window
session.styleOverlay: ~/.fluxbox/overlay
session.styleFile: /usr/local/share/fluxbox/styles/zimek_darkblue
session.keyFile: ~/.fluxbox/keys
session.forcePseudoTransparency: false
session.colorsPerChannel: 4
session.doubleClickInterval: 250

[Beastie]

Failed to read: session.screen0.titlebar.right
Setting default value

It probably only means that the line is present but its value is not set or is bogus, or that it's missing (your case).
This variable only defines what buttons will appear at the right side of your titlebar (in general min, max and close buttons).
I doubt this has anything to do with your problem.



I tested Eterm 0.9.5 (Fluxbox 1.1.0.1_5) yesterday, and it works fine.
Try reinstalling Eterm, or maybe upgrading (or downgrading) it.
I've never had any problem like yours, so I can't really help you much.

[Daisuke_Aramaki]

It worked a few times today so I started using it then after a few xterm sessions it bombed out again and dumped me to the command prompt.

It is evident from your init file the titlebar parameters are not defined at all.

Add these two lines in the beginning of your init file and save it. And then restart fluxbox, and report back if you experience a crash again.


session.screen0.titlebar.left: Stick
session.screen0.titlebar.right: Minimize Maximize Close

[BSDRich]

No, it didn't help adding those lines but I'm not getting that error anymore anyway even before adding those two lines. I don't know why it went away. The default fluxbox init file doesn't have those two lines you suggested adding. Why? Eterm is working intermittently and I can't figure out why or get it to repeat. I can't make the problem happen. Sometimes it works and sometimes it doesn't. I've reinstalled both fluxbox and Eterm. I installed wterm and that's working fine. Eterm is also working fine on awesome. Fluxbox and Eterm are just not getting along on this machine. It works on other machines I have and obviously for other people.

[hydra]

BSDRich it's not only your machine. Fluxbox doesn't work for me either (amd64 only, i386 works without problems), Eterm kills Xorg and moving around the virtual screens does the same. Because of these problems, I replaced Fluxbox with Xfce4, it looks like Fluxbox, but I have no problems with it. I admit, it's larger a little bit, but it works.

[BSDRich]

Yes it looks nice. I'll give that a try. I got awesome working to a tolerable level but when I move a transparent eterm window it takes all the original pixels behind it with it. In other words, it doesn't show the new things behind it but the old stuff. The view behind the transparent window stays the same. That's dumb. It's always something not working.

[BSDRich]

hydra, I installed xfce and xfce4 but when I try to start it I get a black desktop with a toolbar at the bottom and no mouse pointer and the whole system locks up. Is there some config I need to set up first? I put;

exec startxfce

in .xinitrc then run startx.

[Beastie]

Is there some config I need to set up first?
Do you have HAL enabled? It's indispensable.


I put;

exec startxfce

in .xinitrc then run startx.
It's enough, but for version 4.x.x, it's probably startxfce4.

[BSDRich]

"Do you have HAL enabled? It's indispensable."

I don't know. How can I tell?

I realized I only had xfce not xfce4. When I tried to install xfce4 it failed with:




checking for XML::Parser... configure: error: XML::Parser perl module is required for intltool
===> Script "configure" failed unexpectedly.
Please run the gnomelogalyzer, available from
"http://www.freebsd.org/gnome/gnomelogalyzer.sh", which will diagnose the
problem and suggest a solution. If - and only if - the gnomelogalyzer cannot
solve the problem, report the build failure to the FreeBSD GNOME team at
gnome@FreeBSD.org



Any idea why? yet another thing that doesn't work.

[lme@]

"Do you have HAL enabled? It's indispensable."

I don't know. How can I tell?



/usr/local/etc/rc.d/hald status

[Beastie]

I realized I only had xfce not xfce4.
Um, I'm not 100% sure Xfce pre-4 depends on HAL, but try it anyway.
You enable it by adding dbus_enable="YES" and hald_enable="YES" to /etc/rc.conf, and loading it with /usr/local/etc/rc.d/dbus start and /usr/local/etc/rc.d/hal start.



When I tried to install xfce4 it failed with:
[...]
Any idea why? yet another thing that doesn't work.

Have you tried the pre-compiled packages (using pkg_add -r)?

[hydra]

I would recommend to deinstall x11-wm/xfce and install x11-wm/xfce4 only. Afterwards, you need to start HAL and Dbus as mentioned in the Handbook (http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x-config.html). My .xinitrc:

#!/bin/sh
/usr/local/bin/startxfce4


textproc/p5-XML-Parser fails for you ? Try to install only that port and then return to xfce4 install. Show us what it prints (I can compile it without any problems). Aren't you mixing ports and packages ?

[BSDRich]

I ran make deinstall on xfce than tried to install textproc/p5-XML-Parser but it said it's already installed. Xfce4 still fails to install with the same error. Mixing ports and packages? To be honest I don't think I've ever installed a package in the fews years I've been working with FreeBSD, always ports.

[hydra]

Try to deinstall textproc/p5-XML-Parser and install Xfce4 only.

[BSDRich]

I did that and xfce4 still won't install. It keeps failing telling me to run that gnomeanalyzer thing. What a hassle.

[jb_fvwm2]

pkg_delete -f /var/db/pkg/p5-XML-Parser-(something)
cd /usr/ports/textproc/p5-XML-Parser
make missing
/bin/rm -rf work
make install # && yell maybe (/yell/)

This is only answering the post above, No time to read the first
twenty (again...)

[BSDRich]

Ok, I reinstalled xfce4 and it got further but now it's failing to find xml2po even though it exists;


Making all in lgpl
/usr/local/bin/xml2po: not found
gmake[3]: *** [ar/lgpl.xml] Error 127
gmake[2]: *** [all-recursive] Error 1
gmake[1]: *** [all-recursive] Error 1
gmake: *** [all] Error 2
*** Error code 1

Stop in /usr/ports/x11/gnome-desktop.
*** Error code 1

Stop in /usr/ports/x11/gdm.
*** Error code 1

Stop in /usr/ports/x11/gdm.
*** Error code 1

Stop in /usr/ports/x11-wm/xfce4.
*** Error code 1

Stop in /usr/ports/x11-wm/xfce4.

#whereis xml2po
xml2po: /usr/local/bin/xml2po /usr/local/man/man1/xml2po.1.gz



The same error when I try to install gimp. Why can't it find the file when it is there?