You are not logged in.
Pages: 1
Hello guys,
to be more precisely they are working but not when xerm is opened out of a udev rule.
The responsible line in the rule:
ACTION=="add", ENV{crypto}!="", PROGRAM=="/usr/bin/xterm -display :0.0 -e 'echo Password for /dev/%k; /usr/sbin/cryptsetup luksOpen %N %k'"
Due to this setting xterm automatically starts when I plug in an encrypted drive.
In the following my settings in .Xdefaults:
xterm*background: #1A1A1A
xterm*foreground: #A9A9A9
!black
*color0: #333333
*color8: #3D3D3D
!red
*color1: #8C4665
*color9: #BF4D80
!green
*color2: #287373
*color10: #53A6A6
!yellow
*color3: #7C7C99
*color11: #9E9ECB
!blue
*color4: #395573
*color12: #477AB3
!magenta
*color5: #5E468C
*color13: #7E62B3
!cyan
*color6: #31658C
*color14: #6096BF
!white
*color7: #899CA1
*color15: #C0C0C0
Any ideas why this isn't working?
Thank you.
Regards
orschiro
Last edited by orschiro (2010-05-02 21:34:26)
Offline
I don't know if this matters, but the X and T in my .Xdefaults are capital
EDIT: I also have the settings in .Xresources. Maybe try that as well?
Last edited by cesura (2010-05-02 20:50:49)
Offline
Cool that capital XTerm commands seem to work for that special case.
That's it, changing .Xresources wasn't necessary as it symlinks to .Xdefaults.
Thank you itsbrad.
EDIT:
I added the capital commands to my .Xdefaults and then merged the change with xrdb -merge ~/.Xdefaults. After that it worked.
But now I try the same after a reboot and see then it isn't working anymore.
It's also interesting that it's not only the colors of background and font that weren't set, it's also the font config and my settings as a whole.
Last edited by orschiro (2010-05-02 21:17:49)
Offline
Does xterm working correct when invoking directly without any udev?
If yes, try placing that config file in /root.
Pages: 1