Description of problem:Some bugs with wayland in plasma 5.27: - When Mageia go to blockscreen, the blackscreen appears and I can't go back to the session. - I have the plasma panel at the top with a size of 26, and the start menu doesn't work if I click with the touchpad. It does work if I access it from the Meta+ key (linux key in my slimbook, hehe). - The sistem don't shutdown. Appears a black screen saying: "The sistem will shutdown now... " but the sistem don't shutdown, only thinking... Version-Release number of selected component (if applicable): Plasma-workspace-plasma How reproducible: Install workspace-plasma-wayland and try these procceses Steps to Reproduce: 1. Install Plasma-workspace-wayland package 2. Try these processes. 3. Waylang don't work correctly
Thank you for the report. I believe that Plasma on Wayland is still experimental, so problems can be expected. I will install Plasma-workspace-wayland and try to reproduce your problems.
CC: (none) => lewyssmith
(In reply to Jose Manuel López from comment #0) > - I have the plasma panel at the top with a size of 26, and the start menu > doesn't work if I click with the touchpad. It does work if I access it from > the Meta+ key (linux key in my slimbook, hehe). Already reported in bug 30654. Intermediate solution already provided in this bug...
I always find a few quirks whenever i try Plasma wayland, like resuming from suspend, possibly same as the issue in this bug... We really should list Plasma Wayland known quirks and workarounds in the errata -even if experimental and upstream, we do supply the option.
CC: (none) => friKeywords: (none) => FOR_ERRATA9
plasma-workspace-wayland-5.27.4.1-2.mga9 I confirm: * Locking the screen with the Systray padlock icon seems to leave you with a blank screen you cannot get out of. * Panel at top size 26, the main menu does not function with a mouse click (but the Meta key does work). Nor does it at any size up to 40 at least. This is related to having the panel at the top, because at the bottom the main menu does work with a moue click at size 26 or whatever. Saving these comments before trying the last: shutdown.
Source RPM: Plasma-workspace-wayland => plasma-workspace-wayland-5.27.4.1-2.mga9
With the panel at the bottom, trying shutdown. This is variable. The Systray icon pops its slogan, and seems to do nothing if clicked: no confirmation dialogue, but you can get a delayed sudden shutdown. The main menu direct shutdown icon, or Power/Session-Shutdown, seem to do nothing (no confirmation dialogue), but do give a delayed & unexpected shutdown. I suspect that any keystroke precipitates a pending shutdown request which seems to have been ignored. Another point: a keyboard with a separate numeric keypad - that does not work. More on locked blank screen: it seems the whole K/B is ignored, not even Ctl/Alt/Fn nor Ctl/Alt/Bksp/Bksp work after an automatic screenlock. (In reply to Morgan Leijström from comment #3) > We really should list Plasma Wayland known quirks and workarounds in the > errata Yes: a single item for Plasma/Wayland noting what problems we know of. Assigning to the KDE people, even though one doubts whether they can do anything.
Assignee: bugsquad => kde
Trying on my main machine. GPU = nvidia GTX750 DM used: SDDM Using driver nvidia-current (R525): when logging into Plasma, screen go black, no cauldron image, two tones play and i am back at login. I tried the tip from https://wiki.mageia.org/en/Mageia_9_Release_Notes#Plasma : > "Note also that Wayland session with Nvidia's 460 (current) nonfree-drivers is available by making sure that "nokmsboot" is removed and "nouveau.modeset=0" is passed to Kernel command line. - This is provided as Technology Preview for testers." That did not help a bit :( New ideas? (side note: that text should not mention nvidia 460, but 525 (current mga9 nvidia-current) -- and with tips that work. Maybe I should try using driver nvidia470. I changed driver to to Xorg modesetting and Plasma and Gnome seem to work well (albeit a bit slow) MCC starts OK. Can we delete from Errata 9?: > mga#28365 - Control Center does not start in Plasma Wayland. Temporary fix: as normal user, first issue xhost +si:localuser:root One problem: after screen saving (monitor sleeps, but system is not sleeping or hibernating) the screen is completely black except a graphic mouse cursor arrow. ctrl-alt-bkspc-bkspc back to login... CC Giuseppe for ideas, i.e Kernel command line parameters
CC: (none) => ghibomgx
Release notes need be updated too, per #6, when we know more
Keywords: (none) => FOR_RELEASENOTES9
I was just wondering how is the wayland plasma support in other cards (e.g. Intel)? Is stable enough? For instance for wayland (e.g. in GNOME) I see that we have two server running, i.e. both Xorg and Xwayland at the same time. While on other distro I see only Xwayland and not Xorg.
(In reply to Morgan Leijström from comment #6) > Trying on my main machine. GPU = nvidia GTX750 > DM used: SDDM > > Using driver nvidia-current (R525): when logging into Plasma, screen go > black, no cauldron image, two tones play and i am back at login. > > I tried the tip from > https://wiki.mageia.org/en/Mageia_9_Release_Notes#Plasma : > > "Note also that Wayland session with Nvidia's 460 (current) nonfree-drivers is available by making sure that "nokmsboot" is removed and "nouveau.modeset=0" is passed to Kernel command line. - This is provided as Technology Preview for testers." > > That did not help a bit :( > New ideas? > > (side note: that text should not mention nvidia 460, but 525 (current mga9 > nvidia-current) -- and with tips that work. Maybe I should try using driver > nvidia470. > > I changed driver to to Xorg modesetting and Plasma and Gnome seem to work > well (albeit a bit slow) > > MCC starts OK. Can we delete from Errata 9?: > > mga#28365 - Control Center does not start in Plasma Wayland. Temporary fix: as normal user, first issue xhost +si:localuser:root > > One problem: after screen saving (monitor sleeps, but system is not sleeping > or hibernating) the screen is completely black except a graphic mouse cursor > arrow. ctrl-alt-bkspc-bkspc back to login... > > > CC Giuseppe for ideas, i.e Kernel command line parameters If you uncomment: #options nvidia-drm modeset=1 so that it become options nvidia-drm modeset=1 in /etc/modprobe.d/display-driver.conf would change anything?
back on nvidia-current; 525. After uncommenting #options nvidia-drm modeset=1 and rebooting: Still after login from SDDM to Plasma only black screen, but now it lasts longer - the whole login sound is played, and some seconds more pause -then back at login. Also tried with I tried the tip removing "nokmsboot" and added "nouveau.modeset=0" to Kernel command line, no change. Logging in to Gnome Wayland it just hangs, had to REISUB
And changing to gdm instead of sddm?
GDM do not show entry to launch Plasma Wayland. Launching GNOME works, but i do not think it use wayland; $ sudo journalctl -b|grep wayla jun 02 19:48:50 svarten.tribun systemd[6817]: Starting org.gnome.Shell@wayland.service... jun 02 19:48:50 svarten.tribun systemd[6817]: org.gnome.Shell@wayland.service: Skipped due to 'exec-condition'. jun 02 19:48:50 svarten.tribun systemd[6817]: Condition check resulted in org.gnome.Shell@wayland.service being skipped. a few lines later: jun 02 19:48:50 svarten.tribun gnome-shell[9117]: Running GNOME Shell (using mutter 44.1) as a X11 window and compositing manager
Using kde on cauldron, up to date, seems to keep defaulting to wayland on bootup, odd if its experimental. has failure to recover from sleep issue,(black screen with cursor) can be "recovered" with ctl+alt+backspace or switching to terminal and telinit 3, telinit 5 commands. verified this is not the 6.2 kernel issue by booting old kernel, 6.0something. (on 6.3.6-desktop currently) I'm using i965 xorg driver, using latte-dock vs regular kde dock, otherwise default install on Lenovo x260, x201T and x300, all work perfectly with xorg as far as sleep/wakeup go, none with wayland, although wayland so far seems usable for me including menus etc if sleep/screen blank etc are disabled. no issues with video/audio playback noted with wayland, will beat it up some more.
CC: (none) => gjmcgee
(In reply to Greg McGee from comment #13) > Using kde on cauldron, up to date, seems to keep defaulting to wayland on > bootup This is selected by the DM. It should remember your selection until next login. Works here.
(In reply to Lewis Smith from comment #5) > With the panel at the bottom, trying shutdown. > This is variable. The Systray icon pops its slogan, and seems to do nothing > if clicked: no confirmation dialogue, but you can get a delayed sudden > shutdown. > The main menu direct shutdown icon, or Power/Session-Shutdown, seem to do > nothing (no confirmation dialogue), but do give a delayed & unexpected > shutdown. > I suspect that any keystroke precipitates a pending shutdown request which > seems to have been ignored. I can reproduce this problem with Plasma Wayland. This is working fine with Plasma X11. IMO the problem is that with Wayland, Plasma is unable to display the confirmation dialogue and so the user has to wait till the 30 seconds countdown is over. Is it an upstream bug or is this specific to Mageia 9?
CC: (none) => LpSolit
Is the real problem here that Wayland should *not* be used for Plasma unless specifically asked for? Once you have added the bits for Plasma to use Wayland, SDDM at least has a separate menu entry for that; which I do not think the other display managers show. I would expect them to use X11. Need to look.
(In reply to Lewis Smith from comment #16) > Is the real problem here that Wayland should *not* be used for Plasma unless > specifically asked for? Once you have added the bits for Plasma to use > Wayland, SDDM at least has a separate menu entry for that; which I do not > think the other display managers show. I would expect them to use X11. Need > to look. IMHO it's the overlapping of many problems due to combinations of wayland with: a) sddm b) nvidia proprietary drivers c) plasma itself afaik the most stable is wayland started on non-nvidia chipset (e.g. intel) on plasma and when not started by sddm (e.g. xdm can be used, or gdm). then you might add nvidia, and finally sddm. Note also that according to display manager you might have also two X server started at same time (Xorg and Xwayland), you might check with 'ps'.
I had this problem on a laptop with only Intel graphics. After some digging, I found that installing "layer-shell-qt" fixed it. `urpmi layer-shell-qt` I suggest adding "layer-shell-qt" and "plasma-wayland-protocols" as dependencies for "plasma-workspace-wayland"
CC: (none) => mustafa1024m
Release notes since a while link to this and two other bugs related to Plasm with Wayland, under Mageia_9_Errata#Plasma_and_Wayland If we can give some general proactive advice maybe put it in Release notes, so I let the flag FOR_RELEASENOTES9 stand.
Keywords: FOR_ERRATA9 => IN_ERRATA9
CC: (none) => davidwhodgins
Effectively adding layer-shell-qt and plasma-wayland-protocols as suggested in comment #c18 let plasma-wayland working better (just quickly tested under amdgpu with gdm), remain to test with other chipset (intel, nvidia proprietary, nvidia nouveau/modesetting) and sddm. plasma-workspace-(wayland)-5.27.5-3.mga9 with newer Requires in core/updates_testing.
(In reply to Mustafa Muhammad from comment #18) > After some digging, I found that installing "layer-shell-qt" fixed it. > `urpmi layer-shell-qt` I confirm that installing layer-shell-qt fixes the problem with an intel i7-12700 processor (no dedicated graphics card). Installing plasma-wayland-protocols wasn't needed in my case.
Ok, just for further infos, while the current fix improves wayland stability on amd/intel, I re-tested with nvidia proprietary 535.86.05 and still doesn't work (I see segfault in kwin_wayland). Also in the same nvidia proprietary config doesn't work Gnome wayland too.
(In reply to Frédéric "LpSolit" Buclin from comment #21) > (In reply to Mustafa Muhammad from comment #18) > > After some digging, I found that installing "layer-shell-qt" fixed it. > > `urpmi layer-shell-qt` > > I confirm that installing layer-shell-qt fixes the problem with an intel > i7-12700 processor (no dedicated graphics card). Installing > plasma-wayland-protocols wasn't needed in my case. You are correct, "plasma-wayland-protocols" is not needed for this fix.
(In reply to Giuseppe Ghibò from comment #20) > Effectively adding layer-shell-qt and plasma-wayland-protocols as suggested > in comment #c18 let plasma-wayland working better (just quickly tested under > amdgpu with gdm), remain to test with other chipset (intel, nvidia > proprietary, nvidia nouveau/modesetting) and sddm. > > plasma-workspace-(wayland)-5.27.5-3.mga9 with newer Requires in > core/updates_testing. As Frédéric said, "plasma-wayland-protocols" is not required for this fix, sorry for causing the confusion, I think removing it might be better. For me using sddm works okayish, things work fine until I reboot or shut down, and sddm (and X.org) stay hang for a while delaying the shutdown.
(In reply to Mustafa Muhammad from comment #24) > (In reply to Giuseppe Ghibò from comment #20) > > Effectively adding layer-shell-qt and plasma-wayland-protocols as suggested > > in comment #c18 let plasma-wayland working better (just quickly tested under > > amdgpu with gdm), remain to test with other chipset (intel, nvidia > > proprietary, nvidia nouveau/modesetting) and sddm. > > > > plasma-workspace-(wayland)-5.27.5-3.mga9 with newer Requires in > > core/updates_testing. > > As Frédéric said, "plasma-wayland-protocols" is not required for this fix, > sorry for causing the confusion, I think removing it might be better. Dropped in plasma-workspace-wayland-5.27.5-4.mga9 in updates_testing. > > For me using sddm works okayish, things work fine until I reboot or shut > down, and sddm (and X.org) stay hang for a while delaying the shutdown. you might try whether with sddm-0.20.0 (see on one of the above links) changes something.
(In reply to Giuseppe Ghibò from comment #25) > (In reply to Mustafa Muhammad from comment #24) > > (In reply to Giuseppe Ghibò from comment #20) > > > Effectively adding layer-shell-qt and plasma-wayland-protocols as suggested > > > in comment #c18 let plasma-wayland working better (just quickly tested under > > > amdgpu with gdm), remain to test with other chipset (intel, nvidia > > > proprietary, nvidia nouveau/modesetting) and sddm. > > > > > > plasma-workspace-(wayland)-5.27.5-3.mga9 with newer Requires in > > > core/updates_testing. > > > > As Frédéric said, "plasma-wayland-protocols" is not required for this fix, > > sorry for causing the confusion, I think removing it might be better. > > Dropped in plasma-workspace-wayland-5.27.5-4.mga9 in updates_testing. Can you please provide a new "plasma-workspace-wayland" that requires "layer-shell-qt"? > > > > > For me using sddm works okayish, things work fine until I reboot or shut > > down, and sddm (and X.org) stay hang for a while delaying the shutdown. > > you might try whether with sddm-0.20.0 (see on one of the above links) > changes something. I couldn't find the link you meant, I also couldn't find sddm-0.20.0 in updates_testing-x86_64 Is there a repo where I can test it?
I am trying Plasma 5.27.5.3 and i have seen that the update icon see bad. It is not well re-scaled
Created attachment 13936 [details] Update button with Wayland in Plasma KDE This is the update icon with plasma KDE and a panel with 26px of height.
(In reply to Mustafa Muhammad from comment #26) > (In reply to Giuseppe Ghibò from comment #25) > > (In reply to Mustafa Muhammad from comment #24) > > > (In reply to Giuseppe Ghibò from comment #20) > > > > Effectively adding layer-shell-qt and plasma-wayland-protocols as suggested > > > > in comment #c18 let plasma-wayland working better (just quickly tested under > > > > amdgpu with gdm), remain to test with other chipset (intel, nvidia > > > > proprietary, nvidia nouveau/modesetting) and sddm. > > > > > > > > plasma-workspace-(wayland)-5.27.5-3.mga9 with newer Requires in > > > > core/updates_testing. > > > > > > As Frédéric said, "plasma-wayland-protocols" is not required for this fix, > > > sorry for causing the confusion, I think removing it might be better. > > > > Dropped in plasma-workspace-wayland-5.27.5-4.mga9 in updates_testing. > > Can you please provide a new "plasma-workspace-wayland" that requires > "layer-shell-qt"? > The version plasma-workspace-wayland-5.27.5-4.mga9 in core/updates_testing is already the one dropping extra plasma-workspace-wayland and requiring layer-shell-qt > > > > > > > > For me using sddm works okayish, things work fine until I reboot or shut > > > down, and sddm (and X.org) stay hang for a while delaying the shutdown. > > > > you might try whether with sddm-0.20.0 (see on one of the above links) > > changes something. > > I couldn't find the link you meant, I also couldn't find sddm-0.20.0 in > updates_testing-x86_64 > Is there a repo where I can test it? sddm-0.20.0 it's not in updates_testing, because it's not a candidate for core/release due to rversion bump, however the RPMS are here: https://download.copr.fedorainfracloud.org/results/ghibo/mageia9-bonus/mageia-cauldron-x86_64/06097855-sddm/
For missing layer-shell-qt dependency this is not the right fix, real fix would be to make sure that layer-shell-qt is installed with his main library on lib(64)layershellqtinterface5 as this one is required by many some others plasma packages, like I done in this commit: https://svnweb.mageia.org/packages?view=revision&revision=1964430 layer-shell-qt should be also installed for all users and not only by those using wayland, so the requires added in plasma-workspace is unneeded and not correct.
CC: (none) => geiger.david68210
(In reply to David GEIGER from comment #30) > For missing layer-shell-qt dependency this is not the right fix, real fix > would be to make sure that layer-shell-qt is installed with his main library > on lib(64)layershellqtinterface5 as this one is required by many some others > plasma packages, like I done in this commit: > https://svnweb.mageia.org/packages?view=revision&revision=1964430 > > layer-shell-qt should be also installed for all users and not only by those > using wayland, so the requires added in plasma-workspace is unneeded and not > correct. Please can you submit the fixed layer-shell-qt (lib(64)layershellqtinterface5) with your fix, there is still the old version in the repos.
(In reply to Giuseppe Ghibò from comment #29) > The version plasma-workspace-wayland-5.27.5-4.mga9 in core/updates_testing > is already the one dropping extra plasma-workspace-wayland and requiring > layer-shell-qt Thanks, it did install "layer-shell-qt" as a dependency. > > sddm-0.20.0 it's not in updates_testing, because it's not a candidate for > core/release due to rversion bump, however the RPMS are here: > > https://download.copr.fedorainfracloud.org/results/ghibo/mageia9-bonus/ > mageia-cauldron-x86_64/06097855-sddm/ sddm-0.20.0 fixes the my problems of delaying shutdown, thank you. sddm 0.19 was released in 2020, while 0.20 was release this year. It fixed a lot of problems and better supports wayland. I don't know the policy for package versions, but I really think 'sddm' should be updated to 0.20 before the Mageia 9 release (maybe through an exception if there are rules against version upgrades).
I would suggest to after mga9 release, in cauldron (then for mga10) introduce sddm-0.20 and then backport it to mga9.
(In reply to Morgan Leijström from comment #33) > I would suggest to after mga9 release, in cauldron (then for mga10) > introduce sddm-0.20 and then backport it to mga9. (In reply to Mustafa Muhammad from comment #32) > (In reply to Giuseppe Ghibò from comment #29) > > The version plasma-workspace-wayland-5.27.5-4.mga9 in core/updates_testing > > is already the one dropping extra plasma-workspace-wayland and requiring > > layer-shell-qt > > Thanks, it did install "layer-shell-qt" as a dependency. > > > > > sddm-0.20.0 it's not in updates_testing, because it's not a candidate for > > core/release due to rversion bump, however the RPMS are here: > > > > https://download.copr.fedorainfracloud.org/results/ghibo/mageia9-bonus/ > > mageia-cauldron-x86_64/06097855-sddm/ > > sddm-0.20.0 fixes the my problems of delaying shutdown, thank you. > > > sddm 0.19 was released in 2020, while 0.20 was release this year. > It fixed a lot of problems and better supports wayland. > > I don't know the policy for package versions, but I really think 'sddm' > should be updated to 0.20 before the Mageia 9 release (maybe through an > exception if there are rules against version upgrades). Version freeze was more than 1 month ago, furthermore there are still something to review in sddm 0.20, in the internals startup scripts, so while it might be better for some stuff (wayland, hidpi, etc.), it might be not for something other, so better to delay sddm 0.20 post mga9 final release or backports. Also considering that the mga9 final is imminent.
(In reply to Morgan Leijström from comment #33) > I would suggest to after mga9 release, in cauldron (then for mga10) > introduce sddm-0.20 and then backport it to mga9. Yep, it might go in backports or updates/updates_testing post-mga9.
layer-shell-qt-5.27.5-2.mga9 submitted to cauldron!
Confirmed here on my cauldron that now lib64layershellqtinterface5 requires and installs the missing layer-shell-qt package! $ cat /etc/release Mageia release 9 (Cauldron) for x86_64
(In reply to David GEIGER from comment #37) > Confirmed here on my cauldron that now lib64layershellqtinterface5 requires > and installs the missing layer-shell-qt package! > > $ cat /etc/release > Mageia release 9 (Cauldron) for x86_64 Ok, to keep in sync, I dropped the layer-shell-qt extra Requires from plasma-workspace-wayland-5.27.5-5.mga9 (in updates_testing), as it's now redundant, since dep it's retrieved anyway in lib64layershellqtinterface5.