Thu, 5 Dec 2024 08:21:55 -0500 bent fender <slowroller@trixtar.org> :
Thu, 5 Dec 2024 11:27:58 +0100 "Carlos E. R." <robin.listas@telefonica.net> :
On 2024-12-05 03:07, bent fender wrote:
There's nothing wrong with the script that executes xeyes but there is something wrong with me when I call that script from within ~/.profile. It's something I've been warned about before (I think Carlos obliged once) but I just wouldn't listen.
The way it was being called: bash my-xeyes-launch.bsh
The way it should and now is being called: my-xeyes-launch.bsh
I should be ashamed of it but that has never been one of my habbits. It would be nice though to understand HOW this makes a difference? With the latter (correct) call the low-res screen (initially thrown by ssdm or whatever DM being used) is free of the two pairs of eyeballs. As soon as as I use the former (wrong) call they are there again.
It may be lack of coffee, but I don't see why it would matter. :-o
I know I don't use the first method, though, unless the script is not marked executable.
Thanks to all for hints to keep me trying, especially Robert.
-- Cheers / Saludos,
Carlos E. R. (from 15.5 x86_64 at Telcontar)
Aaah, COME ON, GUYS, I DON'T NEED THIS! I thought I had it licked, even tried it back and forth to make sure I could duplicate, and I can duplicate. If I call without a prepended 'bash' I get two pairs of eyeballs, otherwise four. Funny thing is that on my laptop using the same splashma-6 kde this difference does NOT exist. So it has to do with graphics implementation or the vcard. On my laptop (morning and daytime) I get no lo-res DM screen at all, but on my destktop THAT's where the 'early' extra pair appears but then stays carried into the hi-res screen in the thus wrong place. Also, the phenomenon never materialized until a few months ago and I've been using the script with same call for it for many years. In the last few months I've been swapping cards like chopper blades and doing zypper-dups, that's all. Even with this current card everything worked fine until it just didn't anymore. I think I don't have a proper driver for it so I get a lo-res screen at first, then a virtual 1920x1080 that still has the two pairs of eyeballs from its low-res ancestor.
I'm expecting another card tomorrow (Yunir RX 590 8GB), we'll se what that gives, for now here's the entire script (which I must have gotten from someone else because it certaily is not at the same level of syntax use that I am).
#!/bin/sh if [ -n "$DISPLAY" ] then if [ "$XDG_CURRENT_DESKTOP" = "" ] then desktop=$(echo "$XDG_DATA_DIRS" | sed 's/.*\(xfce\|kde\| gnome\).*/\1/') else desktop=$XDG_CURRENT_DESKTOP fi
desktop=${desktop,,} # convert to lower case echo "$desktop" else echo nodesktop no exeyes fi
if [ "$desktop" = "kde" ] then echo it is kde xeyes -geometry 70x50+36+420 & xeyes -geometry 70x50+1810+420 & else echo No kde, no xeyes fi exit #done
An hour after that last post I received the new old gpu card Advanced Micro Devices, Inc. [AMD/ATI] Polaris 20 XL [Radeon RX 580 2048SP] (rev e7) The label on tyhe card says 590, inserted it and could not boot to a graphic desktop i.e could not boot at all. I tried a fresh install but it forced me to use ncurses because "you idiot your hardware does not meet minimums!" HUH??????? once TYW istalled the card works Did an (also forced ncurses) upgrade of existing isntallation and tested both ways of launching the subject script. Now I could not get 3 pairs of eyeballs even if I wanted to. Evidently the card OR its handling were the cause. BTW what's this about not meeting minimums with a card that isn't all that old? AND, since my monitor isn't 4k, is there a way that I can test this card for 4k operability?