X Window Color Problem with Fedora Core 2

From: Mike McCarty (mike.mccarty_at_sbcglobal.net)
Date: 06/29/05

  • Next message: Tim Holmes: "RE: Some thoughts for the future"
    Date: Wed, 29 Jun 2005 16:42:10 -0500
    To: For users of Fedora Core releases <fedora-list@redhat.com>
    
    

    Recently I began having a problem with X Window and Fedora
    Core 2. Various applications (xscreensaver, xterm, others)
    are displaying this message:

    <program>: can't parse color: e6e6e6
    <program>: can't parse color: 000000

    I am using Gnome GTK 2.0 with BlueCurve as the theme. I have
    found two files with e6e6e6 in them, specifying colors, but
    each has "#e6e6e6", not just "e6e6e6". For example, in
    /usr/share/themes/Bluecurve/gtk-2.0/gtkrc is the line

         bg[NORMAL] = "#e6e6e6"

    I do not have a $HOME/.Xresources file. I have not edited
    /etc/X11/Xresources, and it has only this in it:

    ========================================================
    ! This is the global resources file that is loaded when
    ! all users log in, as well as for the login screen
                                                                                    

    ! Fix the Xft dpi to 96; this prevents tiny fonts
    ! or HUGE fonts depending on the screen size.
    Xft.dpi: 96
                                                                                    

    ! hintstyle: medium means that (for Postscript fonts) we
    ! position the stems for maximum constrast and consistency
    ! but don't force the stems to integral widths. hintnone,
    ! hintslight, and hintfull are the other possibilities.
    Xft.hintstyle: hintmedium
    Xft.hinting: true
    ========================================================

    I have read the startup scripts to the best of my ability,
    and the only two files I can find that might affect X
    are $HOME/.Xresources and /etc/X11/Xresources.

    I have tried doing a "xrdb -query -all > xfix.txt" and editing
    the resulting file to put "#" in front of all the "e6e6e6"
    and "000000" strings in there (quite a few), and then doing
    "xrdb -nocpp xfix.txt"

    This fixes xterm, but not xscreensaver, and only until the next boot,
    when I have to go through it all over again.

    As a temporary workaround, I have edited /usr/lib/X11R6/rgb.txt
    to have lines

     230 230 230 e6e6e6
       0 0 0 000000

    so those "colors" are now recognized, and come out as intended,
    but this can't be right.

    I have no $HOME/.profile
    The only things my $HOME/.bashrc does is export some path names.

    As root, I did a "find" with "grep" for "xrdb", and found several
    scripts which use it (like /etc/X11/xinit/xinitrc and
    /etc/X11/gdm/Init/:0), but they only use either $HOME/.Xresources
    or /etc/X11/Xresources

    Can anyone give me some insight on what is wrong, and what I can
    do to fix it?

    I am not an X Window guru, nor a Linux guru, nor a Gnome guru.
    All help appreciated.

    Thanks so much for your time and consideration.

    Mike

    -- 
    p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);}
    This message made from 100% recycled bits.
    I can explain it for you, but I can't understand it for you.
    I speak only for myself, and I am unanimous in that!
    -- 
    fedora-list mailing list
    fedora-list@redhat.com
    To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
    

  • Next message: Tim Holmes: "RE: Some thoughts for the future"

    Relevant Pages

    • [SECURITY] [DSA-380-1] New xfree86 packages fix multiple vulnerabilities
      ... Four vulnerabilities have been discovered in XFree86. ... CAN-2003-0063 - xterm window title reporting escape sequence can deceive user ... Debian has resolved this problem by backporting an upstream fix ...
      (Bugtraq)
    • [Full-Disclosure] [SECURITY] [DSA-380-1] New xfree86 packages fix multiple vulnerabilities
      ... Four vulnerabilities have been discovered in XFree86. ... CAN-2003-0063 - xterm window title reporting escape sequence can deceive user ... Debian has resolved this problem by backporting an upstream fix ...
      (Full-Disclosure)
    • ssh and X11
      ... I have a problem opening an Xterm window on my Suse linux machine ... after I ssh to a remote machine. ... In fact I lose keyboard input capabilities in the window where I ...
      (comp.security.ssh)
    • Curses and resizing windows
      ... > I've been writing an application using curses, ... if running in xterm or similar. ... No matter how much I shrink the window, ... > derived from stdscr. ...
      (comp.lang.python)
    • Re: about Maximum x window
      ... Andreas, thanks for your info. ... > Actually it should be set by the window manager automatically according to ... > That is strange as there should be dozens of fonts. ... Xterm and Aixterm?? ...
      (comp.unix.aix)