http://bugzilla.opensuse.org/show_bug.cgi?id=1183133 Eric Benton <erbenton@comcast.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1183133 http://bugzilla.opensuse.org/show_bug.cgi?id=1183133#c2 Hans-Peter Jansen <hpj@urpla.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |erbenton@comcast.net Flags| |needinfo?(erbenton@comcast. | |net) --- Comment #2 from Hans-Peter Jansen <hpj@urpla.net> --- Dear Eric, (In reply to Eric Benton from comment #1)

Using: KDE 5.98.0 Plasma 5.25.5 Qt: 5.15.6

and gkrellm version 2.3.11

When i have two instances running, one on each monitor, they work fine. But on startup the two instances go to the same spot (one on top of the other) on a single monitor and do not remember their previous positions. I can drag the top instance to the other monitor and then they are fine until the next boot when the same thing happens again. I have: "Remember screen location at exit and move to it at next startup" => checked "Allow multiple instances" => checked

both of these are checked in each instance. Both monitors are the same make and model and each has a resolution of 1920x1080 and setup side by side The mouse can move from one screen to the other and i can drag anything across monitors

I looked at some of gkrellm's config files and this one:

${HOME}/.gkrellm2/data/startup_position

has just 0 0 on one line shouldn't it also have a 2nd line with the startup location for the second instance? something like (assuming its x and y in that order) 0 0 1980 0 What am I missing? Seems like a bug to me.

Ahem, I guess, your usage pattern is unusual a bit. Being a long term gkrellm user, that brought maintainer ship of this goodie to me, I can say, that I never heard from a usage case of two instances *for* the same system. Running multiple instances on a single system for multiple hosts is working just fine (which is the most common usage pattern, that I know of), because you would execute the gkrellms for other hosts with gkrellm -s hostname, resulting in the necessary separation in ~/.gkrellm2 (_S-hostname is appended to the files/dirs. So, you might want to try to run one gkrellm as usual, and the other with -s localhost. Probably, this will solve your problem. Monitoring other hosts would require the execution of the gkrellmd service and probably to open port 19150/tcp. -- You are receiving this mail because: You are on the CC list for the bug.