Description of problem: In a Plasma Wayland session, the start button of the menu applications don't work, only work with the "Windows or Linux keyboard key" Version-Release number of selected component (if applicable): Plasma Wayland - Mageia 8 How reproducible: Install plasma-workspace-wayland and reboot in wayland session Steps to Reproduce: 1. Install plasma-workspace-wayland. 2. Reboot in Plasma-wayland session. 3. Click in start button with mouse or touchpad. The start button don't work.
Perhaps there is a misunderstanding. plasma-workspace-wayland-5.20.4-5.2.mga8 I am running Mageia 8 Plasma Wayland (I needed to change to SDDM to see it; and it is not working too well - X type copy/paste from terminal does nothing!): $ env DESKTOP_SESSION=/usr/share/wayland-sessions/plasmawayland XDG_SESSION_TYPE=wayland Taking 'start button" to be the bottom left Mageia icon, showing on hover "Application Menu A launcher based on cascading popup menus" a left mouse click *does* pop up the menu, same as the 'Windows' key. I tried in vain to screenshot it... Are you talking about something else?
Status: NEW => UNCONFIRMEDEver confirmed: 1 => 0CC: (none) => lewyssmithSource RPM: Wayland plasma workspace => plasma-workspace-wayland-5.20.4-5.2.mga8
I have tried that you comment. I have panel with a size 28 px and is by this that start button don't work with mouse button. It should be a composition issue of wayland.
Status: UNCONFIRMED => NEWEver confirmed: 0 => 1
I have just reduced my panel height to 28px to see whether that mattered. But no: it still works as describe in my comment 1. Please leave this as Unconfirmed until somebody else can reproduce your fault. We need to find the reason, but it is apparently not generic. You know of course that Plasma/Wayland is still 'experimental', so some things can be expected not to work (like MCC!). CC'ing Morgan & sturmvogel to see what they come up with.
CC: (none) => fri, sturm-frEver confirmed: 1 => 0Status: NEW => UNCONFIRMED
I can't contribute much to the topic because I don't use Wayland on any of my machines. Since it is known that Wayland is still very "experimental" in connection with plasma, I did not feel like dealing with it until now. The upstream bugtracker for Plasma/Wayland is quite big…
Unfortuanately I can only say the same as sturmvogel. I posted a question with a link to this bug on QA-list now.
Hi, I have tried this in two different computers. I have the same result in the two. The firs one with Mageia 8 Plasma x86_64 Slimbook ProX Amd 4800H with Amd Vega 7 integrated graphics. The second one with Mageia 8 Plasma x86_64 Asus Intel core I5 with intel graphics. I have the panel with 24 px (befor I have said bad..)
Out of boredom did the same test as Lewis from comment 1 and partly comment 3 (reducing width to 28 px...even tried 20px). I was not able to reproduce this issue with an i7 with HD graphics and i915 kernel module.
Could I be missing some Plasma component that affects the wayland session?
Good idea. On my system: $ rpm -qa | grep wayland | sort kwayland-5.76.0-1.mga8 kwayland-integration-5.20.4-1.mga8 kwayland-server-5.20.4-1.mga8 kwin-wayland-5.20.4-3.mga8 lib64gstwayland1.0_0-1.18.5-1.mga8.tainted lib64kf5wayland5-5.76.0-1.mga8 lib64kwaylandserver5-5.20.4-1.mga8 lib64qt5waylandclient5-5.15.2-2.mga8 lib64qt5waylandcompositor5-5.15.2-2.mga8 lib64wayland-client0-1.18.0-3.mga8 lib64wayland-cursor0-1.18.0-3.mga8 lib64wayland-egl1-1.18.0-3.mga8 lib64wayland-server0-1.18.0-3.mga8 plasma-workspace-wayland-5.20.4-5.2.mga8 qtwayland5-5.15.2-2.mga8 x11-server-xwayland-1.20.14-3.mga8 Post you equivalent output.
On my system: rpm -qa | grep wayland | sort kwayland-5.76.0-1.mga8 kwayland-integration-5.20.4-1.mga8 kwayland-server-5.20.4-1.mga8 kwin-wayland-5.20.4-3.mga8 lib64gstwayland1.0_0-1.18.5-1.mga8.tainted lib64kf5wayland5-5.76.0-1.mga8 lib64kwaylandserver5-5.20.4-1.mga8 lib64qt5waylandclient5-5.15.2-2.mga8 lib64qt5waylandcompositor5-5.15.2-2.mga8 lib64wayland-client0-1.18.0-3.mga8 lib64wayland-cursor0-1.18.0-3.mga8 lib64wayland-egl1-1.18.0-3.mga8 lib64wayland-server0-1.18.0-3.mga8 plasma-workspace-wayland-5.20.4-5.2.mga8 qtwayland5-5.15.2-2.mga8 x11-server-xwayland-1.20.14-3.mga8 It seeems like we have the same packages installed. Could be a plasma component??
I add too, that don't work for me the option cut and copy from remmina desktop to my desktop, for example, from ERP in remmina to Libreoffice Calc in my local desktop. I have tried to install "task-plasma" and "task-plasma-minimal" packages, in case there is a missing library for wayland, but the issue is here still.
I wonder whether your usage is more complicated - Remmina. I found that 'X' copy/paste did not work under Wayland. Yours is another example. > I have tried to install "task-plasma" and "task-plasma-minimal" packages You surely must have already had them. Why are you using Wayland at all?
Apparently, it feels more fluid than Xorg, but it have somes issues still. I will wait for Mageia 9 for try it. For the moment, this bug is here still, even in a Mageia 8 clean installation from complete ISO DVD.
It is curious that just you sees this - and on two different hardware systems (comment 6). Also from a clean install. I do not see how to progress it.
We can close it until Mageia 9 is realeased, for see if the issue is there with the last updates of wayland and Plasma.
Better you test it in Cauldron *before* mga9 release ;)
I have tried in mageia 9 Cauldron, but I have a bug with a library of wayland and i can't install wayland in plasma...
Is that bug reported so it can be fixed?
I can't reported it, I have tried to install a Mageia9 vbox, but the mirrors don't work, and I can't install it. If somebody can try and report...
(In reply to Jose Manuel López from comment #19) > I can't reported it, I have tried to install a Mageia9 vbox, but the mirrors > don't work, and I can't install it. This is unspecific. Do a Mageia 8 installation in VB and update it to the latest packages. After that follow our wiki https://wiki.mageia.org/en/Cauldron but chose a specific mirror: urpmi.removemedia -a urpmi.addmedia --distrib https://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/distrib/cauldron/x86_64/ urpmi --auto-update --auto As it is a tier 1 mirror jussieu.fr is reliable.
plasma-workspace-wayland cannot be installed atm in cauldron because of a major version numbering issue. See bug 30706
Just the bug 30706 is the same for me.
I have an idea to pursue this. Without having tried it (yet), I am sure it is possible to add another instance (widget?) of the Mageia menu launch button to the panel. Do that; does it work? If it does not - stalemate. If the duplicate does work, move it next to the one that does not. Does the duplicate still work? If so, try putting the duplicate where the standard icon sits at the left-hand end of the panel, displacing but not deleting the original instance. Try both.
Hi,I have tried to add new widget menu, and I see that, if I put the menu to right side, the menu works fine, but if I move it to left side, it doesn't work...
Thank you for trying this. It is unclear whether what you report is for the duplicate icon - indeed, whether you added one - or just playing with the original one. Putting it on the RH side is unclear: on the RH side of the panel, but NOT in Systray? Or inside Systray? And does it work if you displace it just by one icon (or 2 or 3) from the LH end? And if you did add a duplicate menu launcher, and put that on the LH end, does that also not work there? Sorry for asking all this, but we cannot try these things ourselves, not having the problem.
Did you set a special behaviour for screen edges in systemsettings -> workspave behaviour -> screen edges? Especially the lower left corner?
Hello! I've tried duplicating the apps menu and putting it on the left side of the screen. It doesn't work here. I've tried putting the duplicate menu on the right side of the screen. Here it does work (my initial menu also works here). I don't have any corner settings in system preferences. In fact, I disable all those options when I install plasma because I don't need them. I currently have it at the top of the screen, but if I change it to the bottom of the screen, it works.
This is a good example why it is so unbelievable important to make a precise bug description and tell everything about your setup....27 comments...so many wasted time... :( (In reply to Jose Manuel López from comment #27) > I currently have it at the top of the screen... I can repeat this behaviour now but you need to move the task bar to the top of the screen or to the left side of the screen. It is not possible to open any application/plasmoid/starter which is in the upper left corner of the screen under wayland...
But there is an really easy workaround: If you have the task bar on top of the screen/left side of screen, add a panel spacer to the left/top of the application menu starter. This moves the application starter into the region of the task bar wher it is clickable.
@Jose Yes, it really was unhelpful NOT to say from the start that you had the panel at the top. > this bug is here still, even in a Mageia 8 clean installation from > complete ISO DVD It was not a 'clean' out-of-the-box install (Plasma panel at bottom) if you then fiddled with it. This looks like an upstream bug. Can you look there - forum & bugs?
Ever confirmed: 0 => 1Summary: Start button of the menu applications don't works in Plasma Wayland => Launchers at the top left corner of the screen don't work in Plasma Wayland: the first item on a panel at top or leftStatus: UNCONFIRMED => UPSTREAM
https://wiki.mageia.org/en/Mageia_8_Errata#Plasma
Status comment: (none) => Workaround: add panel spacer at left/topKeywords: (none) => IN_ERRATA8
Unsolved, like bug 31841, perhaps with the update to Plasma 5.27.9 we will resolve the bug?