Todo list

[stefonarch]

• Prevent scale=1.25 on unconfigured accounts
• Export keyboard layout(s) - fix lxqt2kwinexporter which prevents start atm
• Check minimal dependencies for configuring

[tsujan]

Prevent scale=1.25 on unconfigured accounts

This issue didn't exist under Plasma-X11 6.0.2; I didn't test Plasma-Wayland though.

[stefonarch]

Fixed the layout export/import, don't export toggle shortcut keys as kwin doesn't support the XKB standard as LXQt and all other compositors, all combinations with "CapsLock" also activate it, Alt+Shift is not allowed and so on.

This issue didn't exist under Plasma-X11 6.0.2; I didn't test Plasma-Wayland though.

Looking at that file it looks new to the K-family in ~/.config/, I guess it's for tablet and else too. Retested, it defaults to 1.25, no idea how to handle this as it's generated reading displays. Im going to strip plasma* and keep only systemsettings and kwin.

[
    {
        "data": [
            {
                "autoRotation": "InTabletMode",
                "connectorName": "eDP-1",
                "edidHash": "751814c8857e0fa2f48d32c578a6d075",
                "edidIdentifier": "CMN 5621 0 15 2017 0",
                "highDynamicRange": false,
                "iccProfilePath": "",
                "mode": {
                    "height": 1080,
                    "refreshRate": 60008,
                    "width": 1920
                },
                "overscan": 0,
                "rgbRange": "Automatic",
                "scale": 1.25,
                "sdrBrightness": 200,
                "sdrGamutWideness": 0,
                "transform": "Normal",
                "vrrPolicy": "Automatic",
                "wideColorGamut": false
            }
        ],
        "name": "outputs"
    },
    {                                                                
        "data": [                                                    
            {                                                        
                "lidClosed": false,                                  
                "outputs": [
                    {
                        "enabled": true,
                        "outputIndex": 0,
                        "position": {
                            "x": 0,
                            "y": 0
                        },
                        "priority": 0
                    }
                ]
            }
        ],
        "name": "setups"
    }
]

[stefonarch]

Dependencies on arch:

Sync Dependency (1): kwin-6.0.0-2..

Packets (43) attica-6.0.0-1  karchive-6.0.0-1  kauth-6.0.0-2
               kbookmarks-6.0.0-1  kcmutils-6.0.0-2  kcodecs-6.0.0-1
               kcolorscheme-6.0.0-1  kcompletion-6.0.0-1  kconfig-6.0.0-1
               kconfigwidgets-6.0.0-1  kcoreaddons-6.0.0-1  kcrash-6.0.0-1
               kdbusaddons-6.0.0-1  kdeclarative-6.0.0-1  kglobalaccel-6.0.0-1
               kglobalacceld-6.0.0-1  kguiaddons-6.0.0-1  ki18n-6.0.0-1
               kiconthemes-6.0.0-1  kidletime-6.0.0-1  kio-6.0.0-1
               kirigami-6.0.0-1  kitemmodels-6.0.0-1  kitemviews-6.0.0-1
               kjobwidgets-6.0.0-1  knewstuff-6.0.0-2  knotifications-6.0.0-1
               kpackage-6.0.0-1  kquickcharts-6.0.0-1  kservice-6.0.0-1
               ksvg-6.0.0-1  kwallet-6.0.0-1  kwayland-6.0.0-1
               kwidgetsaddons-6.0.0-1  kxmlgui-6.0.0-1  libplasma-6.0.0-1
               libqaccessibilityclient-qt6-0.6.0-1  plasma-activities-6.0.0-1
               qca-qt6-2.3.8-2  qt6-sensors-6.6.2-1  solid-6.0.0-1
               syndication-6.0.0-1  kwin-6.0.0-2

Adding

Packets(2) krunner-6.0.0-1  systemsettings-6.0.2-3

we get a limitated configuration editor whith the first item loading the wrong content, and there is the "screen" setting missing, so users have 2 choices:

1. Edit the file
2. installing plasma-workspace or -desktop, don't know really the difference.

[marcusbritanicus]

If it's showing the wrong content, then it's likely a systemsettings bug. I have used a partially installed plasma setup (plasma 5.25 or 5.27 or something, but pre-6.0), and I have not faced this problem.

[tsujan]

My ~/.config/kwinoutputconfig.json:

[
    {
        "data": [
            {
                "autoRotation": "InTabletMode",
                "connectorName": "WL-0",
                "edidIdentifier": "",
                "highDynamicRange": false,
                "iccProfilePath": "",
                "mode": {
                    "height": 768,
                    "refreshRate": 60000,
                    "width": 1024
                },
                "overscan": 0,
                "rgbRange": "Automatic",
                "scale": 1,
                "sdrBrightness": 200,
                "sdrGamutWideness": 0,
                "transform": "Normal",
                "vrrPolicy": "Automatic",
                "wideColorGamut": false
            }
        ],
        "name": "outputs"
    },
    {
        "data": [
            {
                "lidClosed": false,
                "outputs": [
                    {
                        "enabled": true,
                        "outputIndex": 0,
                        "position": {
                            "x": 0,
                            "y": 0
                        },
                        "priority": 0
                    }
                ]
            }
        ],
        "name": "setups"
    }
]

The strange thing is that my resolution is 1920x1080, like yours, but this file is about 1024x768! I haven't touched any monitor setting in Plasma 6. Something seems wrong.

[tsujan]

kwin_wayland systemsettings doesn't show systemsettings under labwc anymore (it did with Plasma 5), but when I run systemsettings directly inside labwc, I get this:

I'm not going to log into Plasma 6 for now because otherwise, due to a bug somewhere, my system might freeze when I want to log back into labwc (or LXQt+kwin_x11) — it happened twice and the log said kernel: BUG: unable to handle page fault for address: 000000000002af04, but I don't think the bug is really in the kernel because the freeze happened only in sddm.

[stefonarch]

This file gets generated, in my home it has included now also "WL-0", probably from a nested kwin_wayland session:

[
    {
        "data": [
            {
                "autoRotation": "InTabletMode",
                "connectorName": "WL-0",
                "highDynamicRange": false,
                "iccProfilePath": "",
                "mode": {
                    "height": 768,
                    "refreshRate": 60000,
                    "width": 1024
                },
                "overscan": 0,
                "rgbRange": "Automatic",
                "scale": 1,
                "sdrBrightness": 200,
                "sdrGamutWideness": 0,
                "transform": "Normal",
                "vrrPolicy": "Automatic",
                "wideColorGamut": false
            },
            {
                "autoRotation": "InTabletMode",
                "connectorName": "eDP-1",
                "edidHash": "751814c8857e0fa2f48d32c578a6d075",
                "edidIdentifier": "CMN 5621 0 15 2017 0",
                "highDynamicRange": false,
                "iccProfilePath": "",
                "mode": {
                    "height": 1080,
                    "refreshRate": 60008,
                    "width": 1920
                },
                "overscan": 0,
                "rgbRange": "Automatic",
                "scale": 1,
                "sdrBrightness": 200,
                "sdrGamutWideness": 0,
                "transform": "Normal",                               
                "vrrPolicy": "Automatic",                            
                "wideColorGamut": false                              
            }
        ],
        "name": "outputs"
    },
    {
        "data": [
            {
                "lidClosed": false,
                "outputs": [
                    {
                        "enabled": true,
                        "outputIndex": 0,
                        "position": {
                            "x": 0,
                            "y": 0
                        },
                        "priority": 0
                    }
                ]
            },
            {
                "lidClosed": false,
                "outputs": [
                    {
                        "enabled": true,
                        "outputIndex": 1,
                        "position": {
                            "x": 0,
                            "y": 0
                        },
                        "priority": 0
                    }
                ]
            },
            {
                "lidClosed": true,
                "outputs": [
                    {
                        "enabled": true,
                        "outputIndex": 1,
                        "position": {
                            "x": 0,
                            "y": 0
                        },
                        "priority": 0
                    }
                ]
            }
        ],
        "name": "setups"
    }
]

kwin has also a --scale option, so we have three things with QT_SCALE_FACTOR ....

[marcusbritanicus]

@tsujan 1024x768 comes from your nested session. Here is a screenshot of my kwin_wayland systemsettings

This is my kwinoutputconfig.json

For display configuration to work, you need a compositor that implements kde-output-management, kde-output-order and kde-primary-output protocols. That's available only in kwin_wayland and kwinft_wayland

[tsujan]

@tsujan 1024x768 comes from your nested session.

But I spent a lot of time under Plasma 6.0.2 yesterday; don't have a nested session. I think many things should have been changed from 5.27 (your version) to 6.0.2 (mine). Actually, everything was OK for me too when I had 5.27.

[marcusbritanicus]

@tsujan I'm on 6.0.2 as well. I use Artix/Arch.

[marcusbritanicus]

Interestingly, I do not know to what end though, if we implement these protocols (kde-output-management, kde-output-order and kde-primary-output) on the compositor-side, then we might be able to see and edit the display configurations.

[stefonarch]

we might be able to see and edit the display configurations.

In fact, under kwin_wayland:

[marcusbritanicus]

Ah I see. Well, if we support kde-output-* protocols for other compositors, then we could get this working. This will be quite easy on wayfire due to its modular structure. However, I doubt if any other compositor can manage it.