On 30/12/2003 21:55, Jan Elders wrote:

...

Hello world, Could it be that the .xinitrc file in my home directory is ignored ?

Reason I ask is that I have added in the .xintrc file in my home directory the following (near the end of the file) : # # Add your own lines here... # xmodmap -e 'keycode 96 = EuroSign'

However, after my user-session is started, key 96 still renders the F12 function and not the eurosign. When I go to shell and give the same command then it works OK.

So, my preliminary conclusion is that the .xinitrc file in my home directory is ignored at startup of the session. Is that possible ? If so, how could I remedy that ?

TIA and HAND,

As I understand it, .xinitrc is used if you login to runlevel 3 and issue startx. If you login to runlevel 5, the file used is .xsession. Try making a link from .xinitrc to .xsession and see if that helps. Well, thanks for the suggestion Vic, but .......... I forgot to mention that I'm running SuSE 9.0 and SuSE's SDB explicitely states the following : =================== Symptom SUSE LINUX 9.0 ignores the entries in the file ~/.xsession. Cause SUSE LINUX 9.0 only considers entries in the file ~/.xinitrc. Solution Write the content of the file ~/.xsession to the file ~/.xinitrc. =================== So, it really should execute .xinitrc, but it doesn't. :-( Cheers, -- Jan Elders

On Tuesday 30 December 2003 23:32, Vic Ayres wrote: the Netherlands http://www.xs4all.nl/~jrme/ "Home of the Network Acronyms"

On Wednesday 31 December 2003 18:13, Vic Ayres wrote:

On 31/12/2003 16:44, Jan Elders wrote:

...

On Tuesday 30 December 2003 23:32, Vic Ayres wrote:

<snip>

...

...

As I understand it, .xinitrc is used if you login to runlevel 3 and issue startx. If you login to runlevel 5, the file used is .xsession. Try making a link from .xinitrc to .xsession and see if that helps.

Well, thanks for the suggestion Vic, but .......... I forgot to mention that I'm running SuSE 9.0 and SuSE's SDB explicitely states the following : =================== Symptom SUSE LINUX 9.0 ignores the entries in the file ~/.xsession. Cause SUSE LINUX 9.0 only considers entries in the file ~/.xinitrc. Solution Write the content of the file ~/.xsession to the file ~/.xinitrc. =================== So, it really should execute .xinitrc, but it doesn't. :-( Cheers,

Yes, as it happens, I saw that SDB article not long after posting my reply. But, as I was about to post to that effect, I also saw a post by Patrick Shanahan subject Re: [SLE] Crash has trashed init 5/startx [SOLVED] where it appears that it (SUSE9.0) does indeed reference ~/.xsession.

Nope. I added ln -s .xinitrc .xsession in my home directory, but .... no joy. In fact I notice that several things are not working on my system : * .xinitrc is clearly NOT executed at session start * .xsession is clearly NOT executed at session start * .Xmodmap is clearly NOT executed at session start * the Mode_switch function appears to be NOT working (after having assigned Mode-switch to AltGr, then AltGr 5 does not render €, although everything is defined correctly in xmodmap - this has been checked thoroughly) * the same applies to the Multi-key function; after having prepared my desired settings (correctly, I'm confident) it still appears to be NOT working. All of the above combined gives me the feeling that something is fundamentally wrong on my system (some system function corrupted ??) but I have no idea what and where. Anybody any clues ? TIA and Happy New Year, -- Jan Elders the Netherlands http://www.xs4all.nl/~jrme/ "Home of the Network Acronyms"

On Wednesday 31 December 2003 11:51 am, Jan Elders wrote:

Guess what ? This .Xmodmap also isn't executed at session startup.

So in fact the problem is that both .xinitrc and .Xmodmap (and godzilla knows what other files are NOT executed at session startup). I wonder : could something be corrupted in my system ?

I don't believe that .Xmodmap has any effect unless the xmodmap program is called -- and the call to xmodmap normally resides in ~/.xinitrc. So if ~/.xinitrc isn't being executed, it's unsurprising that ~/.Xmodmap has no effect. Paul Abrahams

On Wednesday 31 December 2003 00:34, Paul W. Abrahams wrote:

On Tuesday 30 December 2003 4:55 pm, Jan Elders wrote:

...

Hello world, Could it be that the .xinitrc file in my home directory is ignored ?

Reason I ask is that I have added in the .xintrc file in my home directory

the

...

following (near the end of the file) : # # Add your own lines here... # xmodmap -e 'keycode 96 = EuroSign'

However, after my user-session is started, key 96 still renders the F12 function and not the eurosign. When I go to shell and give the same command then it works OK.

Interesting -- I've run into a similar problem with the X11 Modifier Map under KDE, which of course traces back to X files (I haven't checked as to which ones). What's even more interesting is that if I log out and log back in again, the modifier map seems to get updated properly.

Not in my case. Log out - log in doesn't help. Cheers, -- Jan Elders the Netherlands http://www.xs4all.nl/~jrme/ "Home of the Network Acronyms"

On Wednesday 31 December 2003 06:01, Mike Grello wrote:

On Tuesday 30 December 2003 16:55, Jan Elders wrote:

...

Hello world, Could it be that the .xinitrc file in my home directory is ignored ?

[stuff cut]

Which version of SuSE are you using? Runnig SuSE 9.0 Professional.

I am using 8.1 and it works. However, I have Mandrake 9.2 running on another system and I have had to create a file in /etc/X11/xinit.d with my desired changes. You see /etc/X11/Xsession loops through all the files in that directory. It may be this way in later versions of SuSE also. You could create a file in /etc/X11/xinit.d which checks for the existence of an xinitrc file in the user's home directory and runs it if found, if you wish to keep things as you are familiar. Well, you're probably right, but I don't know exactly how to make the check you recommend. But anyway, I think there is a more fundamental problem in my SuSE 9.0 :

I also tried to make modifications by means of a .Xmodmap file in my home directory. Guess what ? This .Xmodmap also isn't executed at session startup. So in fact the problem is that both .xinitrc and .Xmodmap (and godzilla knows what other files are NOT executed at session startup). I wonder : could something be corrupted in my system ? Anybody with suggestions ? Cheers -- Jan Elders the Netherlands http://www.xs4all.nl/~jrme/ "Home of the Network Acronyms"

On Friday 02 January 2004 00:32, Yongtao Yang wrote:

Jan Elders writes:

...

Hello world, Could it be that the .xinitrc file in my home directory is ignored ?

Reason I ask is that I have added in the .xintrc file in my home directory the following (near the end of the file) : # # Add your own lines here... # xmodmap -e 'keycode 96 = EuroSign'

However, after my user-session is started, key 96 still renders the F12 function and not the eurosign. When I go to shell and give the same command then it works OK.

So, my preliminary conclusion is that the .xinitrc file in my home directory is ignored at startup of the session. Is that possible ? If so, how could I remedy that ?

TIA and HAND, --

Hi, Jan

Just a wild guess here. Is your .xinitrc executable? What did "ls -l ~/.xinitrc" say? It should be at least executable by the owner.

Try "chmod u+x ~/.xinitrc" and relogin.

Blush !!!!! Yes of course, I should have checked. It was NOT executable, so I corrected this. Thanks for your "wild guess" ! But .... amazingly the xmodmap command as mentioned above still insn't executed (or anyway does not result in setting the eurosign to the F12 key) after re-login. I know by now that .xinitrc is executed because I added a statement : logger ".xinit executed by me" , which I can see in /var/log/messages. So : any suggestions why the xmodmap statement has no result ??? (The same statement works allright when I execute it by hand in shell) TIA and cheers, -- Jan Elders the Netherlands http://www.xs4all.nl/~jrme/ "Home of the Network Acronyms"

On Friday 02 January 2004 20:48, Richard Bos wrote:

Op vrijdag 2 januari 2004 20:38, schreef Jan Elders:

...

I know by now that .xinitrc is executed because I added a statement : logger ".xinit executed by me" , which I can see in /var/log/messages.

So : any suggestions why the xmodmap statement has no result ??? (The same statement works allright when I execute it by hand in shell)

Try this, put it above the xmodmap statement ot if you want to know what is going on from the beginning, put it in the top of .xinitrc: --- exec 2>/tmp/debug set -x ---

Now check the file /tmp/debug after execution of X

All right, did that (put just in front of xmodmap statement). The following is shown in /tmp/debug : + xmodmap -e 'keycode 96 = EuroSign' + logger '.xinitrc called for user me' + exec /usr/X11R6/bin/kde xset: bad font path element (#113), possible causes are: Directory does not exist or has wrong permissions Directory missing fonts.dir Incorrect font server address or syntax xset: bad font path element (#113), possible causes are: Directory does not exist or has wrong permissions Directory missing fonts.dir Incorrect font server address or syntax kbuildsycoca running... ....... and some more stuff ........ What does this tell us ??? I believe the xset errormessage relates to the exec /usr/X11R6/bin/kde command, and has nothing to do with the xmodmap command. Right ? Anyway, I have no clue what to do next. Cheers, -- Jan Elders the Netherlands http://www.xs4all.nl/~jrme/ "Home of the Network Acronyms"

On Friday 02 January 2004 21:47, Richard Bos wrote:

Op vrijdag 2 januari 2004 21:13, schreef Jan Elders:

...

...

--- exec 2>/tmp/debug set -x ---

Now check the file /tmp/debug after execution of X

All right, did that (put just in front of xmodmap statement). The following is shown in /tmp/debug : + xmodmap -e 'keycode 96 = EuroSign' + logger '.xinitrc called for user me' + exec /usr/X11R6/bin/kde xset:  bad font path element (#113), possible causes are:     Directory does not exist or has wrong permissions     Directory missing fonts.dir     Incorrect font server address or syntax xset:  bad font path element (#113), possible causes are:     Directory does not exist or has wrong permissions     Directory missing fonts.dir     Incorrect font server address or syntax kbuildsycoca running... ....... and some more stuff ........

What does this tell us ??? I believe the xset errormessage relates to the exec /usr/X11R6/bin/kde command, and has nothing to do with the xmodmap command. Right ? Anyway, I have no clue what to do next.

Me neither ..., but some hints for the above error: You can put the same debugging trick in /usr/X11R6/bin/kde. It will give you the location that goes wrong in /usr/X11R6/bin/kde which is btw a link to /opt/kde3/bin/startkde. OK will do.

I don't remember what you already did; Did you try to use the .Xmodmap file already, the one in your $HOME and the system one. Does something change grep xmodmap .* .xinitrc.template: test -r $XLIBDIR/Xmodmap && xmodmap $XLIBDIR/Xmodmap .xinitrc.template: test -r $HOME/.Xmodmap && xmodmap $HOME/.Xmodmap

XLIBDIR=/usr/X11R6/lib/X11/Xmodmap Ehh, you lost me here. Yes I tried the .Xmodmap approach, but also that file seems to be not executed. Sigh ! But, I don't understand what you are suggesting to me above. Can you please explain a little further ?

I tried the following, from a xterm, konsole, etc. - run kword - press F12 => result nothing - xmodmap -e 'keycode 96 = EuroSign' - run kword - press F12 => there she is.

Sure, that also works on my system, but I want it automatically at session startup. Hence the .xinitrc approach, that doesn't work for me.

Next thing try the debugging thing in /usr/bin/X11/startx and see what files are executed.... Yes, but I'll be like a little boy in a big town (not really understanding what I'm looking at).

-- Jan Elders the Netherlands http://www.xs4all.nl/~jrme/ "Home of the Network Acronyms"

On Friday 02 January 2004 22:15, Richard Bos wrote: <snip>

...

...

Next thing try the debugging thing in /usr/bin/X11/startx and see what files are executed....

Yes, but I'll be like a little boy in a big town (not really understanding what I'm looking at).

Of course. There are some references to xinitrc: pilchard:~> grep -n xinitrc /usr/X11/bin/startx 7:# interface than xinit. It looks for user .xinitrc and .xserverrc 8:# files, then system xinitrc and xserverrc files, else lets xinit choose 9:# its default. The system xinitrc should probably do things like check 143:userclientrc=$HOME/.xinitrc 145:sysclientrc=/usr/X11R6/lib/X11/xinit/xinitrc

Let's see if you find these back in the debug log file. It will be interesting what is the outcome of line 208 (on my system): 208:xinit $clientargs -- $serverargs

OK, I added the following in the very beginning of startx (just before the "check for installed servers") : exec 2>/tmp/debug set -x However, after re-login (and even re-boot) there is NO file debug in /tmp !!!!???? What would that imply ? Cheers, -- Jan Elders the Netherlands http://www.xs4all.nl/~jrme/ "Home of the Network Acronyms"

On Friday 02 January 2004 23:14, Richard Bos wrote:

Op vrijdag 2 januari 2004 23:14, schreef Jan Elders:

...

OK, I added the following in the very beginning of startx (just before the "check for installed servers") : exec 2>/tmp/debug set -x

However, after re-login (and even re-boot) there is NO file debug in   /tmp   !!!!???? What would that imply ?

That the file is not called by the startup machinery. This file is probably only used if you start X manually. Which is a nice exercise to see if xmodmap work: from root: init 3 than login as yourself from a virtual console and from there execute startx.

Yes, you're right. Now I have the following in debug : ++ ls -1 '/usr/X11R6/bin/Xsun*' /usr/X11R6/bin/XFree86 '/usr/X11R6/bin/XF86_*' '/usr/X11R6/bin/Xaccel*' '/usr/X11R6/bin/XSuSE*' '/usr/X11R6/bin/Xmetr*' '/ usr/X11R6/bin/XFCom*' '/usr/X11R6/bin/XBF*' + INSTALLED_SERVERS=/usr/X11R6/bin/XFree86 + '[' -z /usr/X11R6/bin/XFree86 ']' + type -p wmlist +++ wmlist ++ sort ++ echo kde ++ echo windowmaker ++ echo fvwm2 ++ echo mwm ++ echo twm + WMLIST=fvwm2 kde mwm twm windowmaker + test -z 'fvwm2 kde mwm twm windowmaker' + test '' = -- + test -n '' + test fvwm2 = '' + test kde = '' + test mwm = '' + test twm = '' + test windowmaker = '' + unset WINDOWMANAGERLIST WMLIST WANTEDWM WM + '[' '!' -L /usr/X11R6/bin/X ']' + '[' '!' -L /var/X11R6/bin/X ']' + '[' '!' -x /var/X11R6/bin/X ']' + userclientrc=/home/jrm/.xinitrc + userserverrc=/home/jrm/.xserverrc + sysclientrc=/usr/X11R6/lib/X11/xinit/xinitrc + sysserverrc=/usr/X11R6/lib/X11/xinit/xserverrc + clientargs= + serverargs= + '[' -f /home/jrm/.xinitrc ']' + clientargs=/home/jrm/.xinitrc + '[' -f /home/jrm/.xserverrc ']' + '[' -f /usr/X11R6/lib/X11/xinit/xserverrc ']' + serverargs=/usr/X11R6/lib/X11/xinit/xserverrc + display=:0 + whoseargs=client + '[' x '!=' x ']' ++ mcookie + mcookie=a74ad0088917e4579ff2374197dab87d + '[' X = X ']' + authfile=/home/jrm/.Xauthority + serverargs=/usr/X11R6/lib/X11/xinit/xserverrc -auth /home/jrm/.Xauthority + xauth -f /home/jrm/.Xauthority source - ++ hostname -f ++ hostname -f + mcookie= + xinit /home/jrm/.xinitrc -- /usr/X11R6/lib/X11/xinit/xserverrc -auth /home/ jrm/.Xauthority This is a pre-release version of XFree86, and is not supported in any way. Bugs may be reported to XFree86@XFree86.Org and patches submitted to fixes@XFree86.Org. Before reporting bugs in pre-release versions, please check the latest version in the XFree86 CVS repository (http://www.XFree86.Org/cvs). XFree86 Version 4.3.0.1 Release Date: 9 May 2003 X Protocol Version 11, Revision 0, Release 6.6 Build Operating System: SuSE Linux [ELF] SuSE Build Date: 02 October 2003 Before reporting problems, check http://www.XFree86.Org/ to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/XFree86.0.log", Time: Fri Jan 2 23:26:17 2004 (==) Using config file: "/etc/X11/XF86Config" (II) Initializing extension GLX Could not init font path element /usr/X11R6/lib/X11/fonts/local, removing from list! Could not init font path element /usr/X11R6/lib/X11/fonts/kwintv, removing from list! Could not init font path element /usr/X11R6/lib/X11/fonts/CID, removing from list! xset: bad font path element (#113), possible causes are: Directory does not exist or has wrong permissions Directory missing fonts.dir Incorrect font server address or syntax xset: bad font path element (#113), possible causes are: Directory does not exist or has wrong permissions Directory missing fonts.dir Incorrect font server address or syntax kbuildsycoca running... kio (KService*): WARNING: The service/mime type config file all/Usenet News Message.desktop does not contain a ServiceType=... or MimeType=... entry kdecore (KLibLoader): WARNING: KLibrary: /opt/kde3/lib/libkdecore.so.4: undefined symbol: init_kwifimanager_kcmodule mcop warning: user defined signal handler found for SIG_PIPE, overriding ERROR: Communication problem with susewatcher, it probably crashed. Invalid entry (missing '=') at /home/jrm/.kde/share/apps/suseplugger/ Desktop-MEDION/data4.desktop:1 Invalid entry (missing '=') at /home/jrm/.kde/share/apps/suseplugger/ Desktop-MEDION/data4.desktop:1 Invalid entry (missing '=') at /home/jrm/.kde/share/apps/suseplugger/ Desktop-MEDION/data4.desktop:1 Invalid entry (missing '=') at /home/jrm/.kde/share/apps/suseplugger/ Desktop-MEDION/data4.desktop:1 Invalid entry (missing '=') at /home/jrm/.kde/share/apps/suseplugger/ Desktop-MEDION/data4.desktop:1 Invalid entry (missing '=') at /home/jrm/.kde/share/apps/suseplugger/ Desktop-MEDION/data4.desktop:1 Invalid entry (missing '=') at /home/jrm/.kde/share/apps/suseplugger/ Desktop-MEDION/data4.desktop:1 Invalid entry (missing '=') at /home/jrm/.kde/share/apps/suseplugger/ Desktop-MEDION/data4.desktop:1 Invalid entry (missing '=') at /home/jrm/.kde/share/apps/suseplugger/ Desktop-MEDION/data4.desktop:1 Invalid entry (missing '=') at /home/jrm/.kde/share/apps/suseplugger/ Desktop-MEDION/data4.desktop:1 Invalid entry (missing '=') at /home/jrm/.kde/share/apps/suseplugger/ Desktop-MEDION/data4.desktop:1 Invalid entry (missing '=') at /home/jrm/.kde/share/apps/suseplugger/ Desktop-MEDION/data4.desktop:1 Invalid entry (missing '=') at /home/jrm/.kde/share/apps/suseplugger/ Desktop-MEDION/data4.desktop:1 Invalid entry (missing '=') at /home/jrm/.kde/share/apps/suseplugger/ Desktop-MEDION/data4.desktop:1 Invalid entry (missing '=') at /home/jrm/.kde/share/apps/suseplugger/ Desktop-MEDION/data4.desktop:1 Invalid entry (missing '=') at /home/jrm/.kde/share/apps/suseplugger/ Desktop-MEDION/data4.desktop:1 Invalid entry (missing '=') at /home/jrm/.kde/share/apps/suseplugger/ Desktop-MEDION/data4.desktop:1 Invalid entry (missing '=') at /home/jrm/.kde/share/apps/suseplugger/ Desktop-MEDION/data4.desktop:1 Invalid entry (missing '=') at /home/jrm/.kde/share/apps/suseplugger/ Desktop-MEDION/data4.desktop:1 Invalid entry (missing '=') at /home/jrm/.kde/share/apps/suseplugger/ Desktop-MEDION/data4.desktop:1 Invalid entry (missing '=') at /home/jrm/.kde/share/apps/suseplugger/ Desktop-MEDION/data4.desktop:1 Invalid entry (missing '=') at /home/jrm/.kde/share/apps/suseplugger/ Desktop-MEDION/data4.desktop:1 Invalid entry (missing '=') at /home/jrm/.kde/share/apps/suseplugger/ Desktop-MEDION/data4.desktop:1 Invalid entry (missing '=') at /home/jrm/.kde/share/apps/suseplugger/ Desktop-MEDION/data4.desktop:1 Invalid entry (missing '=') at /home/jrm/.kde/share/apps/suseplugger/ Desktop-MEDION/data4.desktop:1 Invalid entry (missing '=') at /home/jrm/.kde/share/apps/suseplugger/ Desktop-MEDION/data4.desktop:1 Invalid entry (missing '=') at /home/jrm/.kde/share/apps/suseplugger/ Desktop-MEDION/data4.desktop:1 Invalid entry (missing '=') at /home/jrm/.kde/share/apps/suseplugger/ Desktop-MEDION/data4.desktop:1 Invalid entry (missing '=') at /home/jrm/.kde/share/apps/suseplugger/ Desktop-MEDION/data4.desktop:1 Invalid entry (missing '=') at /home/jrm/.kde/share/apps/suseplugger/ Desktop-MEDION/data4.desktop:1 Invalid entry (missing '=') at /home/jrm/.kde/share/apps/suseplugger/ Desktop-MEDION/data4.desktop:1 Invalid entry (missing '=') at /home/jrm/.kde/share/apps/suseplugger/ Desktop-MEDION/data4.desktop:1 Invalid entry (missing '=') at /home/jrm/.kde/share/apps/suseplugger/ Desktop-MEDION/data4.desktop:1 Invalid entry (missing '=') at /home/jrm/.kde/share/apps/suseplugger/ Desktop-MEDION/data4.desktop:1 SuSEhwItem::startPollCD: unable to open /dev/hdc Invalid entry (missing '=') at /home/jrm/.kde/share/apps/suseplugger/ Desktop-MEDION/data4.desktop:1 Invalid entry (missing '=') at /home/jrm/.kde/share/apps/suseplugger/ Desktop-MEDION/data4.desktop:1 Invalid entry (missing '=') at /home/jrm/.kde/share/apps/suseplugger/ Desktop-MEDION/data4.desktop:1 Invalid entry (missing '=') at /home/jrm/.kde/share/apps/suseplugger/ Desktop-MEDION/data4.desktop:1 Invalid entry (missing '=') at /home/jrm/.kde/share/apps/suseplugger/ Desktop-MEDION/data4.desktop:1 Invalid entry (missing '=') at /home/jrm/.kde/share/apps/suseplugger/ Desktop-MEDION/data4.desktop:1 Invalid entry (missing '=') at /home/jrm/.kde/share/apps/suseplugger/ Desktop-MEDION/data4.desktop:1 Invalid entry (missing '=') at /home/jrm/.kde/share/apps/suseplugger/ Desktop-MEDION/data4.desktop:1 Invalid entry (missing '=') at /home/jrm/.kde/share/apps/suseplugger/ Desktop-MEDION/data4.desktop:1 Invalid entry (missing '=') at /home/jrm/.kde/share/apps/suseplugger/ Desktop-MEDION/data4.desktop:1 Invalid entry (missing '=') at /home/jrm/.kde/share/apps/suseplugger/ Desktop-MEDION/data4.desktop:1 Invalid entry (missing '=') at /home/jrm/.kde/share/apps/suseplugger/ Desktop-MEDION/data4.desktop:1 Invalid entry (missing '=') at /home/jrm/.kde/share/apps/suseplugger/ Desktop-MEDION/data4.desktop:1 Invalid entry (missing '=') at /home/jrm/.kde/share/apps/suseplugger/ Desktop-MEDION/data4.desktop:1 Invalid entry (missing '=') at /home/jrm/.kde/share/apps/suseplugger/ Desktop-MEDION/data4.desktop:1 Invalid entry (missing '=') at /home/jrm/.kde/share/apps/suseplugger/ Desktop-MEDION/data4.desktop:1 Invalid entry (missing '=') at /home/jrm/.kde/share/apps/suseplugger/ Desktop-MEDION/data4.desktop:1 Invalid entry (missing '=') at /home/jrm/.kde/share/apps/suseplugger/ Desktop-MEDION/data4.desktop:1 Invalid entry (missing '=') at /home/jrm/.kde/share/apps/suseplugger/ Desktop-MEDION/data4.desktop:1 Invalid entry (missing '=') at /home/jrm/.kde/share/apps/suseplugger/ Desktop-MEDION/data4.desktop:1 SuSEhwItem::startPollCD: unable to open /dev/sr0 WARNING: KDE detected X Error: BadDrawable (invalid Pixmap or Window parameter) \x09 Major opcode: \x0e END OF "DEBUG" POSTING. Well, this looks rather troublesome to me, although I don't really understand all that is reported here. How to continue next ? BTW : what is the use of this excercise if startx is not called during 'normal' session start ? Cheers, -- Jan Elders the Netherlands http://www.xs4all.nl/~jrme/ "Home of the Network Acronyms"

On Friday 02 January 2004 21:26, Yongtao Yang wrote:

Jan Elders writes: <snip>

...

! But .... amazingly the xmodmap command as mentioned above still insn't executed (or anyway does not result in setting the eurosign to the F12 key) after re-login. I know by now that .xinitrc is executed because I added a statement : logger ".xinit executed by me" , which I can see in /var/log/messages.

So : any suggestions why the xmodmap statement has no result ??? (The same statement works allright when I execute it by hand in shell)

TIA and cheers,

In your original post, you said the xmodmap line is close to the end of your .xinitrc file, but how close? I mean you should put any other noncomment lines before the line executing the WINDOWMANAGER, like "exec /usr/bin/fvwm2". Since it will only return after you end your X session.

So did you put the XMODMAP line before the WINDOWMANAGER line? Otherwise can you just post your whole .xinitrc file?

Sure, here it is : #!/bin/bash # # Sample .xinitrc for SuSE Linux # This script is called from 'startx' when you start an X session # # # In case everything goes wrong, we at least fall back to a plain xterm # failsafe="xterm -ls -T Failsave -geometry 80x24-0-0" trap "exec $failsafe" EXIT SIGHUP SIGINT SIGPIPE SIGTERM SIGIO # # Some bash (1 and 2) settings to avoid trouble on a # failed program call. # test -n "$BASH" && set +o posix no_exit_on_failed_exec=1 type shopt > /dev/null 2>&1 && shopt -s execfail set +e > /dev/null 2>&1 # # This should be the default # export TERM=xterm # # choose a window manager # if test -n "$WINDOWMANAGER" ; then WINDOWMANAGER=`type -p $WINDOWMANAGER` fi if test -z "$WINDOWMANAGER" ; then if test -x /usr/X11R6/bin/kde ; then WINDOWMANAGER=/usr/X11R6/bin/kde elif test -x /usr/X11R6/bin/startkde ; then WINDOWMANAGER=/usr/X11R6/bin/startkde elif test -x /usr/X11R6/bin/fvwm2 ; then WINDOWMANAGER=/usr/X11R6/bin/fvwm2 elif test -x /usr/X11R6/bin/wmlist ; then for i in `/usr/X11R6/bin/wmlist` ; do WINDOWMANAGER=`type -p $i` test -n "$WINDOWMANAGER" && break done elif test -x /usr/X11R6/bin/twm ; then WINDOWMANAGER=/usr/X11R6/bin/twm fi fi if test -z "$WINDOWMANAGER" ; then echo "Error: Unable to find a window manager. Please make sure you installed one!" echo "Exiting..." xmessage -timeout 10 -default okay -center -file - <<-EOF Error: Unable to find a window manager. Please make sure you installed one! Exiting... EOF exit 1 fi # # Load system and users resources if not already done # (XSESSION_IS_UP set by xdm in $XLIBDIR/xdm/Xsession) # if test "$XSESSION_IS_UP" != "yes" ; then XLIBDIR=/usr/X11R6/lib/X11 test -r $XLIBDIR/Xmodmap && xmodmap $XLIBDIR/Xmodmap test -r $HOME/.Xmodmap && xmodmap $HOME/.Xmodmap test -r $XLIBDIR/Xresources && xrdb -load -retain $XLIBDIR/Xresources test -r $HOME/.Xdefaults && xrdb -I$HOME -merge $HOME/.Xdefaults test -r $HOME/.Xresources && xrdb -I$HOME -merge $HOME/.Xresources fi # Start the XIM server XIMFILE=/etc/X11/xim test -r $HOME/.xim && XIMFILE=$HOME/.xim test -r $XIMFILE && source $XIMFILE # Enable Numlock if set test -r /var/run/numlock-on -a -x /usr/X11R6/bin/numlock && /usr/X11R6/bin/ numlock # Disable new Xcursor themes if none is specified resp. located in $HOME # (use "unset XCURSOR_CORE" to enable them again later) #if [ "x$XCURSOR_THEME" == "x" -a ! -d $HOME/.icons ]; then # export XCURSOR_CORE=true #else # unset XCURSOR_CORE #fi # Prevent keyboard bouncing for Toshiba Notebooks # Means, disable AccessX test -r /etc/sysconfig/sax && source /etc/sysconfig/sax if [ "x$KBD_BOUNCE_FIX" = "xyes" ]; then test -x /usr/X11R6/bin/xbounce && /usr/X11R6/bin/xbounce fi # # Add your own lines here... # exec 2>/tmp/debug set -x xmodmap -e 'keycode 96 = EuroSign' logger ".xinitrc called for user me" # day planer deamon # pland & # # finally start the window manager # exec $WINDOWMANAGER # call failsafe exit 0 END OF .XINITRC POSTING. Remark : as result of the exec 2>/tmp/debug command (recommended by another person) I see in /tmp/debug the following : + xmodmap -e 'keycode 96 = EuroSign' + logger '.xinitrc called for user me' + exec /usr/X11R6/bin/kde xset: bad font path element (#113), possible causes are: Directory does not exist or has wrong permissions Directory missing fonts.dir Incorrect font server address or syntax xset: bad font path element (#113), possible causes are: Directory does not exist or has wrong permissions Directory missing fonts.dir Incorrect font server address or syntax kbuildsycoca running... ....... and some more stuff ........ What does this tell us ??? I believe the xset errormessage relates to the exec /usr/X11R6/bin/kde command, and has nothing to do with the xmodmap command. Right ? Anyway, I have no clue what to do next. Cheers, -- Jan Elders the Netherlands http://www.xs4all.nl/~jrme/ "Home of the Network Acronyms"

On Friday 02 January 2004 22:36, Yongtao Yang wrote:

Jan Elders writes:

...

Sure, here it is : ...

I am not surprised as I see you are using KDE, which has the bad tradition of ignoring user configurations(.Xmodmp/.Xdefaults etc). I guess the xmodmap line in your .xinitrc was executed by overwrited by kde.

Can you try another windowmanager? For example install fvwm, and in your .xinitrc file, put WINDOWMANAGER="PATH_TO_FVWM2" right before the line exec $WINDOWMANAGER

Well, sorry, I don't really like to start in this direction. It should work with KDE as well. It is my understanding that lots of people are doing this with KDE without problem. I think that there is just something corrupted on my system, that's what I would like to find out. Cheers, -- Jan Elders the Netherlands http://www.xs4all.nl/~jrme/ "Home of the Network Acronyms"

On Fri, Jan 02, Jan Elders wrote:

# # Load system and users resources if not already done # (XSESSION_IS_UP set by xdm in $XLIBDIR/xdm/Xsession) # if test "$XSESSION_IS_UP" != "yes" ; then XLIBDIR=/usr/X11R6/lib/X11 test -r $XLIBDIR/Xmodmap && xmodmap $XLIBDIR/Xmodmap test -r $HOME/.Xmodmap && xmodmap $HOME/.Xmodmap test -r $XLIBDIR/Xresources && xrdb -load -retain $XLIBDIR/Xresources test -r $HOME/.Xdefaults && xrdb -I$HOME -merge $HOME/.Xdefaults test -r $HOME/.Xresources && xrdb -I$HOME -merge $HOME/.Xresources fi

I've dealt with this strangeness for years myself by simply *repeating* the line

test -r $HOME/.Xmodmap && xmodmap $HOME/.Xmodmap

Works for me. YMMV. Michael -- Michael Fischer Happiness is a config option. michael@visv.net Recompile and be happy.

On Fri, Jan 02, Jan Elders wrote:

On Friday 02 January 2004 23:08, Michael Fischer wrote:

...

On Fri, Jan 02, Jan Elders wrote:

...

# # Load system and users resources if not already done # (XSESSION_IS_UP set by xdm in $XLIBDIR/xdm/Xsession) # if test "$XSESSION_IS_UP" != "yes" ; then XLIBDIR=/usr/X11R6/lib/X11 test -r $XLIBDIR/Xmodmap && xmodmap $XLIBDIR/Xmodmap test -r $HOME/.Xmodmap && xmodmap $HOME/.Xmodmap test -r $XLIBDIR/Xresources && xrdb -load -retain $XLIBDIR/Xresources test -r $HOME/.Xdefaults && xrdb -I$HOME -merge $HOME/.Xdefaults test -r $HOME/.Xresources && xrdb -I$HOME -merge $HOME/.Xresources fi

I've dealt with this strangeness for years myself by simply *repeating* the line

...

test -r $HOME/.Xmodmap && xmodmap $HOME/.Xmodmap

Works for me. YMMV.

Michael, Where should I put that repeated line ?

I just do it twice in a row, where the SuSE .xinitrc has it. So... if test "$XSESSION_IS_UP" != "yes" ; then XLIBDIR=/usr/X11R6/lib/X11 test -r $XLIBDIR/Xmodmap && xmodmap $XLIBDIR/Xmodmap test -r $HOME/.Xmodmap && xmodmap $HOME/.Xmodmap test -r $HOME/.Xmodmap && xmodmap $HOME/.Xmodmap test -r $XLIBDIR/Xresources && xrdb -load -retain $XLIBDIR/Xresources test -r $HOME/.Xdefaults && xrdb -I$HOME -merge $HOME/.Xdefaults test -r $HOME/.Xresources && xrdb -I$HOME -merge $HOME/.Xresources fi Michael -- Michael Fischer Happiness is a config option. michael@visv.net Recompile and be happy.