With my new notebook notebook Asus VivoBook 15 X512FA I had several problems with different desktops (bugs #26524 and #26399) and that is why I switched to Plasma Wayland where the most annoying problems are fixed. Now I discovered that in Plasma Wayland there are problems too. The most inconvenient is that the clipboard Klipper is not working. I can copy paste within the same application, but not to another application because Klipper is not saving any copied text. I tested this with Firefox, Thunderbird, Scribus, Libreoffice and Chromium Browser. I can copy from one KDE application to another, e.g. a file name from Dolphin to Kate or Konsole. But even then Klipper remains empty. Copied texts do not get saved in Klipper. Steps to Reproduce: 1. Copy a text in an application, e.g. Firefox 2. Paste it in another application, e.g. Libreoffice 3. Nothing gets pasted or 1. Copy any text in any application 2. Open Klipper 3. Nothing has been saved
I just want to add that Klipper works fine in Plasma without Wayland.
This looks like similar to this bug: https://bugs.kde.org/show_bug.cgi?id=405509
Pardon me asking, but can you say how you got Plasma to use Wayland? What I found elsewhere referred to just one package, 'plasma-wayland-session'; but that was for different distributions, we do not have it. We do have several Plasma/Wayland related packages, which I happen to have on my system (which has Wayland for Gnome) I would like to try this problem before passing the bug on. The KDE bug reference you gave above is indeed similar, except it makes NO reference to Wayland... Caution is being preached about using Plasma under Wayland at present, for example: https://community.kde.org/Plasma/Wayland_Showstoppers
CC: (none) => lewyssmith
(In reply to Lewis Smith from comment #3) > Pardon me asking, but can you say how you got Plasma to use Wayland? What I Boot to run level 3, login and run the command ... XDG_SESSION_TYPE=wayland dbus-run-session startplasmacompositor
CC: (none) => davidwhodgins
It is much easier to get Plasma with Wayland. I installed most of the Wayland packages and after reboot I was able to chose "Plasma (Wayland)" (the last item in the dropdown list) for the session when I logged in.
Thanks; found it! I thought it had to be something like that - otherwise how would you have known? [The reason for me not seeing it is that with SDDM there is a long-standing bug whereby if you have many desktops to choose from (I have), the last several in the list are not visible: you have to know they are there, and find them blindly. Which I did, and here I am with Plasma (Wayland); whose presence in the list I was previously unaware of]. @Dave : thanks for your learned tip, but few people would know that trick! No time now to explore things, but I have immediately discovered something that does not work.
Under Plasma/Wayland, I found the following: * In all that follows, klipper *never* showed the content = this bug. But note that Ctrl/C|V *did* work, so that basic functionality remains. * Within 1 Gtk application, X copy/past worked, also Ctrl/C|V. * Between 2 Gtk applications, [either above or below, I have forgotten]. * Within 1 KDE application, X copy/paste did *not* work, but Ctrl/C|V did. * Between 2 KDE applications, X copy/paste did *not* work, but Ctrl/C|V did. * Between GTk & KDE applications, X copy/paste did *not* work, but Ctrl/C|V did. Under normal Plasma, all things work. Including klipper. @Béat : Plasma/Wayland is openly experimental. You cannot at present expect us to deal with its problems, of which yours is just one; I encountered many others in a short usage. I am tempted to close this - with no disrespect - invalid; but am passing it to the KDE team for their information and possible comment.
Keywords: (none) => UPSTREAMURL: (none) => https://bugs.kde.org/show_bug.cgi?id=405509Assignee: bugsquad => kde
I don't mind if you close this because I understand that Wayland is still experimental. I only use it because it has less disadvantages than the other environments. The problem is my hardware that isn't fully compatible with Linux yet. I hope that my other problems ((bug #26524 and #26399)) can get fixed soon so that there is no need anymore to use Wayland.
(In reply to Béat E from comment #8) > I don't mind if you close this because I understand that Wayland is still > experimental. Thank you for saying this, it saves time.
Resolution: (none) => WONTFIXStatus: NEW => RESOLVED
This will be resolved upstream for Plasma 5.20 (October 13th, 2020) https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/1
Resolution: WONTFIX => INVALIDCC: (none) => ouaurelien