Sysop: | Amessyroom |
---|---|
Location: | Fayetteville, NC |
Users: | 43 |
Nodes: | 6 (0 / 6) |
Uptime: | 96:31:32 |
Calls: | 290 |
Files: | 904 |
Messages: | 76,426 |
Michael wrote:
Since I upgraded to KDE Frameworks 6 I have observed some rather unwanted window behaviours.
1. Window Interaction with Gkrellm
DESIRED BEHAVIOUR:
==================
I have Gkrellm started up by Plasma at login and placed at the top left of the screen. I can't remember where/how I set this up, but at least it is still respected by KDE 6. I've always set Gkrellm via its Configuration
General > Properties with:
+ Set sticky state
+ Set window type to be a dock or panel
This allowed the following interaction with other application windows:
- Other windows would launch without overlapping the Gkrellm window. On
an
otherwise empty desktop they would be placed on the right of it.
- When a window was maximised it did not extend sideways to cover the
whole
screen beyond the position of the the Grkellm.
- When I dragged a window to force it to infringe the boundary of the Gkrellm window, the Gkrellm would overlap the dragged window.
I'm having issues with gkrellm as well. I tend to put gkrellm on
desktop 10 on the left side. I'd like it to be on screen 1 as well.
When I first login, gkrellm is on desktop 1 and on screen 2. I have to
move it every time.
Usually I right click on the top bar of a window,
select More Actions and either Window Settings or Application Settings, depending on which I want. I can then add Properties and set it like I
want. It is best to have it like you want it before you start. It
already has the settings that way. I do this for Seamonkey, both
browser and email, QB and a few other apps. Thing is, gkrellm doesn't
have a title bar to right click on.
It works fine on my old rig but not
on the new rig. When I had to use the old rig to watch TV, I checked, I couldn't find anything that tells gkrellm to be where it is but it comes
up where I want it each time, apparently without me doing anything at
all. New rig, it goes to the wrong place every single time. It's wrong
but it is consistent.
I have KDE set to remember what was open and where at logout. I don't
know if KDE just isn't remembering where to put gkrellm because it isn't really a window or what. I might add tho, even tho screen 1 is set as primary, it still acts like screen 2 is primary for some things. I
wonder if that is why gkrellm parks itself on screen 2 instead. Some
apps I use open to screen 2 until I set up a rule forcing it to open on screen 1. It should open there by default but it doesn't. I might add,
when I plug in a USB stick, the notification thingy pops up on screen 2,
not screen 1 where it should be.
I mention all this because it might give you a clue on where or how KDE
is working now. Clearly gkrellm is unique because I can get everything
else to work right, even if I have to force it with window/application
rules.
Oh, when looking at window rules in System Settings, it has a export and import feature. I never saw that before. Might be new. It's at the
top I think. If you use that tool, may want to back up your settings
when you get everything done.
Hope that gives you some clue to a fix. Maybe.
Dale
:-) :-)
For some reason, the second monitor has a plasma thing, where app menu
icon, virtual desktop, clock and such is, on the second monitor as
well. My TV screen has nothing. No desktop icons, plasma thingy or anything. It just has a default background image and that is it. Why
the second monitor got done that way, I dunno. May I should remove the plasma thing completely.
I might add, another odd thing that started after a recent update. When
I logout of KDE or when first booting and am on the sddm login screen,
my first monitor powers off. The second monitor stays on and has the
login screen as does the TV screen. Yet the primary screen turns off.
At first when we got past the wonky monitor problem, all three would
stay on and mirror each other. Now it doesn't.
I might add, if I switch to a console, screen one turns back on and all
three mirror each other. I kinda like that because if I need to do
something that takes a bit, I don't have to go to the living room to
turn the TV back on again.
Michael wrote:
On Friday 6 September 2024 12:04:08 BST Dale wrote:
I might add, another odd thing that started after a recent update. When >> I logout of KDE or when first booting and am on the sddm login screen,
my first monitor powers off. The second monitor stays on and has the
login screen as does the TV screen. Yet the primary screen turns off.
At first when we got past the wonky monitor problem, all three would
stay on and mirror each other. Now it doesn't.
I might add, if I switch to a console, screen one turns back on and all
three mirror each other. I kinda like that because if I need to do
something that takes a bit, I don't have to go to the living room to
turn the TV back on again.
It sounds as if the primary monitor is using DPMS in Xorg, if you're running X, or some similar energy saving feature. Check SystemSettings > Power Management > Display and Brightness.
You may be on to something. I have DPMS enabled on my two main monitors
but not the TV. That said, I had my monitors set to not turn off. I
did that the other day so that they would stay on while I was doing my
emerge -e world. I wanted to keep a eye on it in case something failed
and the emerge stopped.
Should I have DPMS set to on or turn them all off in xorg.conf? I'm
thinking on. Thursday a week ago tho, everything turned off when I
locked the screen, TV as well. It seems it can turn things off even
without DPMS.
Meanwhile back at the ranch, I think my Gkrellm dock panel problem is related to KDE 6 not identifying the Gkrellm window as a 'dock/panel', probably because the Gtk2 code is far too old to integrate with Plasma.This is bad. It's a sign gkrellm might stop working. I hope someone
:-(
who can code will update and keep gkrellm alive and going. I'd hate to
see that go away. That's a awesome tool that is impossible to replace.
I don't know of anything that comes close.
Dale
:-) :-)
The second problem I started this thread with, related to the Kmail composer window inheriting the main Kmail window size and vice versa,
seems to occur because both windows are identified having the same
"kmail org.kde.kmail2" named Class. I played around with various properties, like window type and what not, but I have not been able
to add a separate window size for the composer alone without
affecting the main Kmail window. If anyone comes up with a working solution please chime in!
On 2024.09.06 11:12, Michael wrote:
[snip ....]
The second problem I started this thread with, related to the Kmail composer window inheriting the main Kmail window size and vice versa,
seems to occur because both windows are identified having the same
"kmail org.kde.kmail2" named Class. I played around with various properties, like window type and what not, but I have not been able
to add a separate window size for the composer alone without
affecting the main Kmail window. If anyone comes up with a working solution please chime in!
I haven't been following very closely, but it sound like one approach
would be to have one of the windows use a different name Class. Might
it be worth raising as an issue for kmail itself?