July 2020 - openSUSE KDE - openSUSE Mailing Lists

[opensuse-kde] [tumbleweed] kde/plasma/wayland: Primary Selection Protocol (middle-mouse to paste)
by Sedat Dilek 27 Sep '21

27 Sep '21

Hi, after I tried KDE/Plasma/Wayland on Debian/testing AMD64 I inspired my colleague Joop Boonen to test it on OpenSuse/tumbleweed. Everything was fine besides Primary Selection (middle-mouse to paste), so I stopped using Plasma/Wayland. Joop is able to use primary selection in every application (KDE or GTK). So, I was surprised. Here on KDE/Plasma 5.12.5 I cannot do that (for example cut-n-paste in konsole via middle-mouse paste into firefox). I asked on the wayland-devel ML [1] with no answer. The retired KWin maintainer wanted to have this feature in wayland-protocols before implementing it in KWin/Plasma/Wayland. So, what magic did you do in OpenSuse? The Gnome-way? [1] has references on how Gnome did it in mutter. Or can you point me to the relevant packages with name (sources and patches)? Thanks in advance. Regards, - Sedat - [1] https://lists.freedesktop.org/archives/wayland-devel/2018-April/037748.html -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

5 12

[opensuse-kde] KDE file dialogs in Thunderbird and Firefox
by Tom 23 Jul '20

23 Jul '20

Hi all, it seems like Thunderbird and Firefox use GTK dialogs for opening and saving files by default. To make them use native KDE dialogs the environment variable GTK_USE_PORTAL must be set to 1. One way to do that is to edit the .desktop files for the applications [1]. Alternatively, the line export GTK_USE_PORTAL=1 can be added in ~/.profile or even globally under /etc/profile.d/. Would it make sense to add the global export in a package (e.g., a branding package)? This should make Firefox and Thunderbird use the KDE file dialogs by default for most users. Or would that have any unwanted side effects? Best, Tom [1] https://pointieststick.com/2018/12/16/this-week-in-usability-productivity-p… -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

9 15

[opensuse-kde] KDE repos for Leap 15.2
by Luiz Fernando Ranghetti 22 Jul '20

22 Jul '20

Hi, It's really necessary to add all 3 repos (Qt5, Frameworks and Applications) on Leap 15.2? For 15.1 I understand, Qt was at a lower version which is not the case anymore. Regards, Luiz -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

3 4

[opensuse-kde] Survey on changes of Plasma defaults: XWayland, xf86-input-synaptics
by Fabian Vogt 09 Jul '20

09 Jul '20

Hi, we are considering a few changes in the defaults offered by the KDE Plasma and related packages. If you have a touchpad or use any of the Plasma Wayland sessions, they will likely have an impact on your workflow, so we'd like to hear your feedback before committing to anything. Let us know! Offer only "Full Wayland" instead of both "Xwayland" / "Full Wayland" sessions ---------- To ease the transition into a Plasma Wayland session, it's configured that Qt and GTK applications prefer XCB over native Wayland: in other words, Xwayland is used for most applications instead of the native Wayland client implementations. This is what the "Plasma (Wayland)" session does, which is referred to here as "Xwayland" session for clarity. This means that some benefits of Wayland, like isolation of clients and support for per-monitor scaling (mixed-DPI setups), are missing. To mitigate that, there is a second session, called "Full Wayland", which forces both Qt and GTK applications to use their native Wayland client implementation again. Now there is a discussion upstream where it was requested that this split and GTK/Qt behaviour difference compared to other distros should be dropped: https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/85 The arguments here are that this is not appropriate for developers and that most of the issues worked around by the Xwayland session are fixed meanwhile. So far we have read about both sides, some which wouldn't be able to use the Plasma Wayland session without the Xwayland setup and some which have a better experience with the "Full Wayland" session. Arguments pro Full Wayland: - Scaling works properly (including per-output scaling) - More consistent application behaviour (assuming that they can speak wayland natively) - More isolation between applications - ...? Arguments pro Xwayland: - Upstream, Qt does not consider qtwayland to be a good default in GNOME sessions due to various compatibility issues and so it explicitly uses the fallback to XCB there (https://bugreports.qt.io/browse/QTBUG-68619) - It avoids certain incompatibilities like with Yakuake and stability issues, like with KMail (and other users of WebEngine) - ...? I'd argue that developers are able to switch to the "Full Wayland" kind of session themselves. If the "Full Wayland" session is perfectly usable by those who use the "Xwayland" session currently, there's no reason to keep this split anymore though. Otherwise, please tell us what makes the "Full Wayland" session a worse experience. Note that this won't touch the Xorg session at all: it'll stay the default for the at least near future. Don't recommend xf86-input-synaptics by default ---------- There are two main X11 drivers for touchpads: xf86-input-synaptics and xf86-input-libinput. Synaptics is practically dead upstream while libinput is the de-facto replacement, also for tablets. Currently, if plasma5-desktop is installed, xf86-input-synaptics is automatically pulled in as well. It takes precedence over the libinput driver. While it's a simple step to remove the package and thus let libinput take over, the question is whether this should be the default state. Pro synaptics: - More configuration options - Some say it works better for them - ...? Pro libinput: - Maintained upstream - Some say it works better for them - Used by wayland compositors, so a more consistent experience - Better handling of some hardware configurations (e.g. Thinkpad trackpoints) - ...? Cheers, the openSUSE KDE maintainers -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

2 1

[opensuse-kde] Window unchangable
by JJM de Faber 05 Jul '20

05 Jul '20

In the left corner of the window titlebar is menu with an item named 'more actions/special application settings'. The next menu contains a tab 'Apperance and fixes'. This menu has an item 'No tittle bar and frame'. I activated this selection and the titlebar and frame where gone as expected. The problem is how to do additional setting now the title bar with the menu entry is gone? The window configuration is now unchangable because there is no entrypoint for the menu of this window! Doe anybody know a solution ??? Thanks, Hans -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

3 3