You are not logged in.

#1 2006-05-17 19:46:42

Kern
Member
From: UK
Registered: 2005-02-09
Posts: 464

Terminal v xfterm4 - bug? [Solved]

using xfce4 im finding that the menu icons leading to an xterm use xfterm4 (default black text on white back,  and a VT menu on top bar)

this is ok, but, say running alsamixer, the terminal just goes black. Similar with other apps that make use of the terminal screen, like testdisk.

running Terminal, the $ on a blackscreen icon under System, i get to see whats what.

similarly, the progress bar in gtk-gnutella is just a black letterbox. usually the colourfill denotes type of progress.

all this since the last pacman -Syu

tweaking menu.xml to call up Terminal by default, not xfterm4, but i think theres an underlying problem.

any ideas where i might start looking? wondering if its gtk related.

Offline

#2 2006-05-17 21:03:27

hollywoodb
Member
From: USA
Registered: 2003-10-03
Posts: 39

Re: Terminal v xfterm4 - bug? [Solved]

xfterm doesn't really do much... it is only a shell script that calls xterm unless $TERMCMD is set to something else.

XFCE 4.4 and beyond will drop xfterm4 in favour of Terminal.

If you have xfce 4.2.x packages installed, /opt/xfce/bin/xfterm4 is the bash script that launches the terminal

From XFCE 4.2.x documentation:

Postinstallation Tasks

After installing Xfce, you may want to set the $BROWSER and $TERMCMD environment variable which point out respectively your favorite brower and terminal. They will notably be used by the xfhelp4 and xfterm4 script provided by Xfce. Just add the following lines to your ~/.bash_profile, then logout/login:
export BROWSER="your_favorite_browser"
export TERMCMD="your_favorite_terminal"

I chose 'firefox' and 'Terminal', respectively

--------------------

I have the same xterm problem, however....

hollywoodb@hollywoodb ~ $ xterm
Warning: locale not supported by C library, locale unchanged
Warning: Cannot convert string "-adobe-helvetica-bold-r-normal--*-120-*-*-*-*-iso8859-*" to type FontStruct
xterm: Cannot allocate color green3
xterm: Cannot allocate color cyan3
xterm: Cannot allocate color cyan
xterm: Cannot allocate color white

hollywoodb@hollywoodb ~ $ xterm -bg black -fg white
Warning: locale not supported by C library, locale unchanged
Warning: Color name "black" is not defined
Warning: Color name "white" is not defined
Warning: Cannot convert string "-adobe-helvetica-bold-r-normal--*-120-*-*-*-*-iso8859-*" to type FontStruct
xterm: Cannot allocate color green3
xterm: Cannot allocate color cyan3
xterm: Cannot allocate color cyan
xterm: Cannot allocate color white

hollywoodb@hollywoodb ~ $

hollywoodb@hollywoodb ~ $ grep LOCALE /etc/rc.conf
# LOCALE: available languages can be listed with the 'locale -a' command
LOCALE="en_US.utf8"

hollywoodb@hollywoodb ~ $

xterm for me won't display any other color than black, so if I try to run alsamixer or similar in an xterm I get a black screen as well.

Offline

#3 2006-05-18 01:19:05

Snowman
Developer/Forum Fellow
From: Montreal, Canada
Registered: 2004-08-20
Posts: 5,212

Re: Terminal v xfterm4 - bug? [Solved]

hollywoodb: Make sure you have
        RgbPath      "/usr/share/X11/rgb"
in your xorg.conf and that the file /usr/share/X11/rgb.txt exist.

Offline

#4 2006-05-18 01:54:08

Kern
Member
From: UK
Registered: 2005-02-09
Posts: 464

Re: Terminal v xfterm4 - bug? [Solved]

Guys, Thanks for taking the time to reply, problem now solved

Snowman: yes xorg.conf was the prob.
xorg.conf default pointed to the wrong place for rgb file

both terminal and gnutella now have colours. smile

thanks again

Kern

=================

xorg.conf:....
<snip>
Section "Files"

# The location of the RGB database.  Note, this is the name of the
# file minus the extension (like ".txt" or ".db").  There is normally
# no need to change the default.
 
   commented out this  --> RgbPath       "/usr/X11R6/lib/X11/rgb"

    inserted this      ---> RgbPath "/usr/share/X11/rgb"

<snip>
8)

Offline

Board footer

Powered by FluxBB