Our apologies to all. Got a little upset… more with ourselves than anyone else… cause we couldn’t get across just what the problem was/still is. Went off and pouted and played with Android on our cell phone. We learned (and in case anyone reading this didn’t know) that Android is really Linux underneath. So, we learned how to ‘root’ our phone.
Now back to the Problem… if we may:
As stated in the beginning, this involves .xinitrc. We like to have two terminal Windows created and opened during our boot. Been doing that since version 6.2. Please notice that we are stating that we have done this same thing ever since SuSE 6.2. (Also in UNIX) What?? Including two -or- more terminal windows in our .xinitrc. We used to do a lot of work in text/command line mode. To keep track of things we used different colored backgrounds on the teminals.
This “problem” occurred in RC2 -but- went away by a “strange fix”. Please notice that we are including RC2… it happened there -BUT- as stated… we had a “strange fix” so we ignored it for the time. What strange fix?? We have a Triple boot system (Windows, Current Stable SuSE, and the latest developement SuSE) and prior to this day, openSuse 11.4 was our main system. We booted up into it by accident How?? It was our Main System and it was the default and we weren’t paying attention at boot time and let it slip thru to 11.4 instead of 12.2 RC2. We immediately exited the 11.4 and re-booted into * 12.2 RC2*.
AFTER re-booting into RC2 the terminals appeared in the correct location -and- the correct size. So, since the “problem went away” we just ignored it as a possible fluke and figured that it would be correct in the Released Version. Unfortunately, it was not.
Please notice the strange 'fix’. This was AFTER the ‘accidental’ attempt to boot into openSuSE 11.4. The xterms appeared -and- in the correct size -and- positions. We can not duplicate this ‘fix’ cause we replaced the 11.4 with this new 12.2.
During Start-up AFTER the new Grub2 fancy selection screen we will see the xterms flash on the screen in the correct positions and sizes.
Please notice when this happens -and- notice that they are the correct size and in the correct position on the screen. This happens just before the march of the devices. First one being a Hard Disk, second the Tools -and- for the life of me can’t remember what the others are!! Anyway, that is not important.
What is important … is that when the Desktop finally appears.… both xterm windows are plastered against the top of the screen and about 11 lines to short. Looks like they have take on the ‘Failsafe’ values. Please notice in the code below that we have specified 35 lines -and- these two terms that appear are only 24 and their tops are at the top of the screen. They appear to be correct in width and in the correct Horizontal position -but- NOT the vertical position NOR the height (wrong number of rows).
We understand that we can create a script and execute it AFTER the logon -but- that is NOT how it is supposed to work. Hasn’t for over 10 years… or more. IF this is NOT the way the system works anymore … could someone please tell us what changed.
Now we can close out both of the INCORRECT windows… and click on the .xinitrc inside of a Dolphin widow, get a warning about the window manager already running… -but- the terminal windows will get created and in the correct positions and the correct sizes. -But- this same code fails to produce the correct result during boot-up.
We are using the supplied template. We “used to” just copy our old one over. -BUT- with this version it did not work -and- now we are finding the “correct” one doesn’t work either. We are using the supplied .xintrc template as a base to create our *** .xinitrc*** and only adding the following lines: (in the spot where it says ‘Add your own lines here…’)
xterm -geometry 100x35+385+180
-fg Black -bg NavajoWhite -sb
-rightbar
-title NavajoWhite
-fn 8x13 &
xterm -geometry 100x35+165+390
-sb
-rightbar
-title For_coding
-fn 8x13 &
Ok. Hope this clarifies it all. We are also investigating it. Seems to be somehow “failing” and using part of the ‘Failsafe’ values. IF one of you would like to try — edit the xinitrc.template and copy/paste the above terminal values in it and save it as your .xinitrc. Then restart your system and see what happens. The details of my system are listed in the signature below.
Thanks and have fun,
Chuck
thought that we had put in enough info -but- some of you are like us… don’t read everything or have another way of interpreting what we said.:shame: Anywho, we will try to clarify the first posting: (thishas created and interesting discussion.)
