• Re: [gentoo-user] KDE Frameworks 6 window management

    From Michael@21:1/5 to All on Thu Sep 5 17:59:00 2024
    On Thursday 5 September 2024 15:34:06 BST Dale wrote:
    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.

    Gkrellm should show up on all desktops, if you select 'Set sticky state'. However, I understand the position on the desktop is a Plasma setting, not an application setting.


    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.

    If you right click on the Gkrellm on the Plasma toolbar you will be access the same Plasma window decorations as other windows have. Or, easier, click
    Alt+F3 to popup the Plasma window menu on any application.

    There is also a Grekllm setting under General > Properties > "Use window type decorations", but you'll have to restart Gkrellm for any changes to show up if you select this.


    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.

    Quit Gkrellm, then relaunch it and place it where you want it on the screen. Hopefully Plasma will store this and survive a logout. If not, open the
    Window decoration Plasma menu of Gkrellm after you reveal it as mentioned
    above and add the window 'Position' property. Apply, then click OK.

    NOTE: I found such window positioning behavior to be particularly bad on X11 as opposed to Wayland, but I understand NVidia is not yet working as well on Wayland so YMMV.


    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.

    Hmm ... from what I see here notifications always popup on the primary screen
    - assuming you have no task bar on your secondary screen.

    Also, if you click to launch an application, but you move your mouse and click quickly on the wallpaper on another screen, the application will launch on the screen you placed and clicked your mouse on.


    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

    :-) :-)

    SystemSettings > Window Management > Window Rules, shows any windows you have set bespoke settings for. You can add and modify application window settings there, or you can do the same Alt+F3, the select More Actions and use the settings at the bottom of the menu.
    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCAAdFiEEXqhvaVh2ERicA8Ceseqq9sKVZxkFAmbZ41QACgkQseqq9sKV ZxmJsA//cgnkaqlak5f65C1IRIwEmSo3bCi3JpTxcMozlRCQ8XENHqS0RSd4njKO vPmIVTxm+LQIJ8zb4SBbWPkoiec0Va9n0Vi76PcHv/VnbckY0Pj9tXpoE0bq27Km Ly01tmP37M9Lv00ZiTu0sZ1UKY1Dt2ut4tUNbE2s0CzYwOjZnx8sVkYmbmmvSq+3 waIpjOR9/Wm8Nr5TEUP2sQr91jpLncUlTjd5fkGkkI0fHNknYkkg1Y5EHx9XZz5/ 82k+8SIwP/1fUYZ0qGYd4J1WWsBpZp8jW+JuFU5ndgzjShVAKp1+Hgx7BpGWDAdH 728ZGuIEd7PW6U8nPsuosx0Rkow8MQL5w/7sEjKDAFtYigB0KirLTYD5XJrjILW1 9GPFCxzdi1FIPFjeHdab1YTmEOYEYIz8m1G3nVd+x0qFrnUoS84sv0FXB19s7uPX U5qlo5PyAkUJLBLG49ZMBYuashpGG6PECsNB1+miaBLk/tuSL1PAk96dsaMds4eo HnYyCsZqw4IS5TY0UQ/WC9k2mg0ON1Mc0YbE8+a2utAuUWe27YZGjJxuPe7/z7jf G1kZAFixoaSzhRDXX8/OrkdSv0bRxLuNRS/bzUtGmrytG7g+8NUy+TDOqxBFZvFn 7XEKnGcq7OXdbJiZEPc8KmhSXjE1Cc+z112I6zn3pc3kddCNtIk=
    =FD9G
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Michael@21:1/5 to All on Fri Sep 6 09:43:42 2024
    On Friday 6 September 2024 02:02:55 BST Dale wrote:

    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.

    The "... plasma thing" = Plasma Panel container

    Can be placed on any screen edge.

    Can be more than one.

    Starting from the left, it contains:

    1. Kmenu (i.e. application menu/launcher)
    2. Desktop pager (virtual desktops)
    3. Task manager (shortcut icons to applications and open applications)
    4. System Tray (notifications, Kmix, clock, etc.)

    From what I recall SystemSettings allows you to select to have the Plasma
    Panel only on the primary monitor. That's how I've set it on a dual monitor
    PC here.
    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCAAdFiEEXqhvaVh2ERicA8Ceseqq9sKVZxkFAmbawL4ACgkQseqq9sKV Zxl0RRAAhuQ7L6T24YNnnn0HgDhe/GgKu/gbsUX8tle4G1ZAXGpsU+yetQJkJDtE l03Fur11XAAQwz5GJOu8043v9/X1sYWUMqcf45CZrnKdNTUkK2dpb+3d2SsfR7d4 N1V6qc5hr3TRgYN6swo3J5RuTBvbKzq2AxATb5XURH2n3MwHP6Sm1RGyrf0/vV/J XDXkBPnucAkfybCqZYIYTBSB4K9TkrOgYJ+8gj+wFpKh5OUCEFMVNZBRK9kRPDIm 8n5+4Ql3UQIzYoKkMtvSceD/VE6BuBPk/8MUlivG7jHse35DzgIxzwTxVw1xeAGa Ev9fK0yaxIjuawzy6p+S4QaYhvUFwqLILTEeQPhGb6BAMB1o9z5IpVcjqpPEwesZ +e5GkSRhQnvOHLVcgRfRco8y+f9i3bNgZvDVW04YTJAMzck/mWUlGu/8bqoyNQEN fOkeO97Xtm/LGNMqj8FdmLaDzIqg335u8dZiX1CoIUKkRnxVtKEAS1/vo061FE0d wp1LH7Vbdn2Su5/uxyTGnd1e6wItHhsAVqPx5IAREcB1aeJzEmNh3AyevmSu493b PFxWBE4ltJ3bXoZ0vPQ3BxfHvebSUxKTR2pZTOlufpkRMmhrlKnii/Anw9wtTHxH WHiTGYZuyu9y67zSOJrb+vVdT+lnGr/7zOY88/nNOQvaGUgSg+4=
    =yjpc
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Michael@21:1/5 to All on Fri Sep 6 12:28:59 2024
    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.

    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. :-(



    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCAAdFiEEXqhvaVh2ERicA8Ceseqq9sKVZxkFAmba53sACgkQseqq9sKV ZxmuWA/7BsVKg9ouzUwDX9TVHo0evtJjPB0BD1bisD3off+JOBVu5cs+C1EAsYkf N+ifS1MXOncnZFmIxH9G7ugkKBH4YjMGBwBNwTIjTN/XIE+TiqxzwXPts4RFmX/o I7qZUmcKgkK0+H8lGSCA831NodMW0nek1N1J7UvrCOM3dkUzZaHvqoDQ2+fS8QLW phFmbmo3mGIPqrg86iyRii0e2jgk0n/cg/4RtWSxmLtsJIFlS91vy5Q1jpHM9vbq UQGjf3AF7Z0rrsJMO7Oe/gF/8XtVorZGHYMygtt+j9I2Ydtf0DxVC+/5Q0DZpuAb jDlc75NdhyX4u9d69rd43erkFwC47EEClLVkMCh9aWEkB/6fspR5fO3Zj+JpIwKz ZLkAxq0jjZNyjxEjNbh5d3LydBx3Ed24PIvnnbega06ZU9UTMawFnDvs0isT/UkE Vf7y3/ki649D9D9vp9EGh8BVp8UxCFcile+qZ2Y+01DVSJOkIzJ4gFV7KJTUsXai jPf0bfRW8nQDI2n71wFFSJ62VyC5GlRo9CjrWEjrVjSO8KBFFJ+m+/nNY2XIk9KM +AIbRhHYIrRCiaANJuzF3SdnDrp7mtThg/5hSFWyv49Zahm3Oi1OqE67e9tsJZH3 tXG6W/ix00HU550qGwxA4f4cp4GBBsSE90KvYEG/U7VHfcMB6RY=
    =WBLG
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Michael@21:1/5 to All on Fri Sep 6 16:12:14 2024
    On Friday 6 September 2024 12:40:25 BST Dale wrote:
    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!
    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCAAdFiEEXqhvaVh2ERicA8Ceseqq9sKVZxkFAmbbG84ACgkQseqq9sKV ZxmO7BAAm0GRbs5hdax5utQBc8ApFUK7/XcNuczsCt4bPE3RqtLY8i/m4ZrHhyy9 rp6w3WRSLdyCHDocHFoMzwEQqJaUxzB/5SuYG1bkyHFYr/IyesPJNXU89fXYWJB0 fJMZqIZ3Tu20fq7FM2bycfWREpTiGXDRuBhpFb0EnpTqd2OQitCLkYlb3CBfk2xa OQiC/0kzmtk2dcPetSbAEACzZNIkAZBjHn4oBB/4ZUpvk5cAdxed5t8PTW/YZ9lZ k5zq9T4ss8RfjEmvwzcLQ0AcjGKrYoJyTpfBzP6NF73g6i7fWaQANP/u6zz56ZQ0 OSDYZe2SUMfQvpAcbwWL7jA7QbBz2mzbxpSPFuri5BbjT2pZUQ+OZmo6e3A7HHW4 QFAA9F39auEsLCcSUqrEVyGnwbas+vy4riS+Qsj+J3iytFD32DjQU3tP2yFOS3rk YsXT/TKbcD2WAHsjfz9O9BXHDV0nnY7nqWXZ68t+eSHX/3R0wNc6cabnGYBO4y8J IDuT0VdaEY5qlQx1SA/ICaDvPZcTVjc467AUnTx6Rk9TIHIfUJAOCUf8cZxsU/aP dPT2zCooSfV0zZqgt20JZUz4KhXiTT1NfvfrTSwTseNu0IjeGojMLjqbRNOhmDdY EUeRF/Q50ioPvw8p1qSUtp+UF+mZdRU6ULXapprBmBR2Fi4Sey0=
    =Bxjc
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Jack@21:1/5 to Michael on Fri Sep 6 21:40:01 2024
    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?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Michael@21:1/5 to All on Sat Sep 7 11:38:38 2024
    On Friday 6 September 2024 20:37:59 BST Jack wrote:
    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?

    I understood the Window Class of an application is hard coded, all a user like me can do is select it. I can't claim to understand this correctly, or furthermore understand how the X11 properties transpose over to a Wayland desktop:

    https://www.x.org/releases/current/doc/xorg-docs/icccm/ icccm.html#WM_CLASS_Property

    Either way, the good news is others have been annoyed similarly by this behaviour and raised a bug report. It seems to be a regression bug:

    https://bugs.kde.org/show_bug.cgi?id=484327

    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCAAdFiEEXqhvaVh2ERicA8Ceseqq9sKVZxkFAmbcLS4ACgkQseqq9sKV ZxmGVhAArZYzqoaF1Uk2tsa73ODDmSkS9xX0VqMdObo9dch4iSGmzEybMYvM53uf vwHOqfDgxlSGtdbnVEebWo27v7lhecFAghi0+Zh5S7I6Ctsd1ihBfAxn+jXvyE8r ywE6fBB2wGrR64XH06VVXpBZUsJcbyoq0g7Rs2wLwloywHDAW5fHpaQGIjcuHzn0 /mR2AE58NNbm1FFnOa7uFBBsOZSKBUx6fSkjM6SQBntmfoa+l8jYXguMy2rJ3/wk octwedIg7BYLJAvxSTkiry9Md7GA3s5rcFWVEpHPwC72Wxfg43F5KTRAL4yGHPy4 HijnB8XS+NfbQX4bErN2VDn9h+AhiiARUds2uIihQCwkVMTkqgqEbas46UztfscV PzNo6qoypxGy6aTR3/di34HsRxFNJnWQ/aTzuSo9pniYQwhCe3xExMuy9/0DMnQb pqv55YXAsikS/SQCY07mIX9SKBPXjOlvR8/5OVh1fVL9aXS/Ot9YZLMxSZqErRyS b3/aqOII4NXcT38CNkBLNVWmCYmvemtD1PYL11RdUuo3yupgmzEY1dvBSB8O3Q6F S5ulSYOvAWRabCmhCo1wdSJGlXt+9GONGl5eKqhxVPP6eKU1w5WPJrVRP21yP6uz eIXwx1qChGFEev99+LNfdx2KYN5pGgBM5nQdKuOmTbLaDmkKEQA=
    =0ot/
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)