On Sat, 30 Nov 2024 22:28:23 -0500, bent fender <slowroller@trixtar.org> wrote:
Sun, 1 Dec 2024 02:35:59 +0000 (UTC) Robert Webb via openSUSE Users <users@lists.opensuse.org> :
On Fri, 29 Nov 2024 21:09:14 -0500, bent fender <slowroller@trixtar.org> wrote:
Fri, 29 Nov 2024 14:03:17 +0900 Masaru Nomiya <nomiya@lake.dti.ne.jp> :
In the Message; Subject : Re: 3 pairs of xeyes? Message-ID : <20241128204357.f65eb98ee381055b2a459989@trixtar.org> Date & Time: Thu, 28 Nov 2024 20:43:57 -0500 [SF] == bent fender <slowroller@trixtar.org> has written: [...] SF> sddm started booting my Tumbleweed desktop SF> first in low-res mode, then in high-res and THAT's where I think it hit SF> the fan bigtime. [...] It seems to me that ~/.profile which hosts the xeyes calls is being run twice in two different resolutions.
# ps -D '%F %T' -O ppid,pgid,lstart -C xeyes
PID PPID PGID STARTED S TTY TIME COMMAND
2528 1 2324 2024-11-30 21:28:00 S tty2 00:00:10 xeyes -geometry 70x50+36+420
2529 1 2324 2024-11-30 21:28:00 S tty2 00:00:10 xeyes -geometry 70x50-36+420
2886 2275 2877 2024-11-30 21:28:06 S ? 00:00:11 xeyes -geometry 70x50+36+420
2887 2275 2877 2024-11-30 21:28:06 S ? 00:00:11 xeyes -geometry 70x50-36+420
It seems to support my suspicion, two calls just as resolution changes. I think the 3 I see are #2 obscuring #1, #3, & #4
Yes. To trace whatever invokes ~/.profile, you could log its executions to the journal by adding this line to .profile: logger -i ".profile[$$] ppid $PPID($(ps -q $PPID -o args=))" That records the pid of the shell executing .profile, and the command of the shell's parent. Then, after booting, show the logged lines with: journalctl -g '^\.profile\[[0-9]+\] ppid ' -- Robert Webb