To reproduce this, please can you say how you get Plasma to run under Wayland - which is normally reserved for Gnome.

CC: (none) => lewyssmith

I have installed plasma-workspace-wayland.
After reboot, I select it in the kdm, I choose plasma wayland in the select list.

I know, Wayland is normally for Gnome, but Xorg don't work with my intel graphics card.
Wayland could by an alternative.

Thanks for the Wayland info. kdm->SDDM.

My system has AMD/ATI/Radeon graphics.
Trying this bug after adding 'plasma-workspace-wayland', and restarting X.
SDDM does indeed offer Plasma-Wayland, running under it now.

MCC does not launch from any icon or menu. Nor does rpmdrake=Add/Remove software - and what else?
In all such cases, the root password dialogue is shown.

From a terminal as normal user, both commands popped the root password dialogue, then died. The fact that the X copy/paste mechanism does not work from Konsole makes it difficult to show the output; BUT it *does* work with Mate terminal (possibly others), so here goes:

$ mcc
Too late to run INIT block at /usr/lib64/perl5/vendor_perl/Glib/Object/Introspection.pm line 257.
 [root pw dialogue]
Ignore the following Glib::Object::Introspection & Gtk3 warnings
No protocol specified
Unable to init server: Could not connect: Connection refused
Cannot be run in console mode.
$
$ rpmdrake
 [root pw dialogue]
Ignore the following Glib::Object::Introspection & Gtk3 warnings
No protocol specified
Unable to init server: Could not connect: Connection refused
Cannot be run in console mode.
$

From a root terminal, MCC does not start, but rpmdrake *does*.

# mcc      [does not launch]
Too late to run INIT block at /usr/lib64/perl5/vendor_perl/Glib/Object/Introspection.pm line 257.
No protocol specified
(mcc:9790): dbind-WARNING **: 21:45:12.658: Could not open X display
Ignore the following Glib::Object::Introspection & Gtk3 warnings
No protocol specified
Unable to init server: Could not connect: Connection refused
Cannot be run in console mode.
#

# rpmdrake     [does work]
Ignore the following Glib::Object::Introspection & Gtk3 warnings
No protocol specified

(drakrpm:11348): dbind-WARNING **: 21:46:20.074: Could not open X display
Subroutine Gtk3::main redefined at /usr/share/perl5/vendor_perl/Gtk3.pm line 525.
Use of uninitialized value $value in numeric eq (==) at /usr/share/perl5/vendor_perl/Gtk3.pm line 791.
... *n
Impossible to set by_group view as default
getting lock on urpmi
using mirror http://ftp.free.fr/mirrors/mageia.org/distrib/7/x86_64
archwilio ffeil synthesis [/var/lib/urpmi/Core Release/synthesis.hdlist.cz]
... *n
unlocking urpmi database
------------------------
It is worth noting that Plasma under Wayland, on brief acquaintance, is ropy. Inconsistent copy/paste, mouse scroll wheel, Alt/Tab only cycled through the 2 most recent windows; probably lots of other glitches.
-----------------------------------------------------
Not sure where to point this: both Mageia tools, CC'd KDE/Plasma.

CC: lewyssmith => kde
Source RPM: Kwayland => (none)
Assignee: bugsquad => mageiatools

Hi Lewis,
Thanks for trying.
> Cannot be run in console mode.
There is at least this problem. Wayland doesn't allow that graphical application can be run as root.
There is a workaround for running mcc tools in Gnome Wayland. I'm surprised that this has not the expected effect in Plasma. This is because I suggested to Olivier to file the report.

CC: (none) => yves.brungard_mageia

It looks like Plasma didn't start Xwayland (as it looks like the DISPLAY env variable is not set)
Can you confirm it?

Keywords: (none) => NEEDINFO
CC: (none) => thierry.vignaud

The result :
$ echo $DISPLAY
:0

I am using a notebook Asus VivoBook 15 X512FA and have the same bug under Plasma Wayland.

CC: (none) => ed1

Did mcc works after:

$ xhost +

CC: (none) => guichard.adrien

The command "xhost +" doesn't work and I get the following message.
Invalid MIT-MAGIC-COOKIE-1 keyxhost:  unable to open display ":1"
This problem might be related to the fact that I use Plasma Wayland.

plasma-workspace isn't setting Xwayland right (or at all)…

Source RPM: (none) => plasma-workspace
CC: (none) => mageia
Assignee: mageiatools => bugsquad

I have my new notebook Asus VivoBook 15 X512FA and run into quite some problems in different desktops environments (bugs #26399, #26524). Video and some applications I need only work under Wayland although even Wayland isn't perfect (see this bug and #26543). This is the reason why I use Wayland.

I like to add that mcc work under Gnome Wayland.

(In reply to Thierry Vignaud from comment #10)
> plasma-workspace isn't setting Xwayland right (or at all)…

If so, and:
(In reply to Béat E from comment #12)
> I like to add that mcc work under Gnome Wayland.

Assigning to KDE maintainers.

Keywords: NEEDINFO => (none)
Assignee: bugsquad => kde

Adding some interesting bytes here:

Under a M7 Plasma system fully updated (in a x86_64 VM)

If you managed to install:

qtwayland5-5.12.6-1.mga7.x86_64               
plasma-workspace-wayland-5.15.4-1.1.mga7.x86_64
lib64qt5waylandcompositor5-5.12.6-1.mga7.x86_64
lib64qt5waylandclient5-5.12.6-1.mga7.x86_64
kwin-wayland-5.15.4-1.1.mga7.x86_64
kwayland-integration-5.15.4-1.mga7.x86_64
egl-wayland-json-1.0.3-4.mga7.noarch

(You could do same on Intel-based graphic devices and recent AMD one for M7),
if you look at ~/.local/share/sddm/wayland-session.log:

subsequent launching MCC with the Plasma Menu, you can see:
Too late to run INIT block at /usr/lib64/perl5/vendor_perl/Glib/Object/Introspection.pm line 257.
No protocol specified
Unable to init server: Impossible de se connecter : Connexion refusée
org.kde.kwindowsystem.keyserver.x11: X11 implementation of KKeyServer accessed from non-X11 platform! This is an application bug.

Nota bene: Firefox launches very well and so does Thunderbird...

CC: (none) => ouaurelien

Can confirm this is also a problem under mageia 8.
using asus ux31 in plasma wayland.

wayland packages installed.

lib64gstwayland1.0_0-1.18.2-2.mga8.tainted
wayland-tools-1.18.0-3.mga8
lib64wayland-cursor0-1.18.0-3.mga8
kwayland-integration-5.20.4-1.mga8
lib64kf5wayland5-5.76.0-1.mga8
kwin-wayland-5.20.4-1.mga8
qtwayland5-5.15.2-1.mga8
lib64qt5waylandclient5-5.15.2-1.mga8
lib64wayland-egl1-1.18.0-3.mga8
plasma-workspace-wayland-5.20.4-2.mga8
plasma-wayland-protocols-1.1.1-1.mga8
lib64wayland-client0-1.18.0-3.mga8
x11-server-xwayland-1.20.10-2.mga8
lib64kwaylandserver5-5.20.4-1.mga8
kwayland-5.76.0-1.mga8
lib64wayland-server0-1.18.0-3.mga8
lib64qt5waylandcompositor5-5.15.2-1.mga8
kwayland-server-5.20.4-1.mga8

plasma wayland itself on intel 810 graphics is fantastic, brave, and thunderbird work fine.
but have to logout select plasma x11 before i can use mcc.

CC: (none) => peter.winterflood

further investigation, has led me to find that running xhost + or a more controlled version of that wildcard example, fixes this.
and allows MCC to run.

I have the same problem here.

Regards

CC: (none) => ezequiel_partida

Mageia 7 is EOL since July 1st 2021.
There will not have any further bugfix for this release.

You are encouraged to upgrade to Mageia 8 as soon as possible.

@reporter, if this bug still apply with Mageia 8, please let us know it.

@packager, if you work on the Mageia 7 version of your package, please check the Mageia 8 package if issue is also present. In this case, please fix the Mageia 8 version instead.

This bug report will be closed OLD if there is no further notice within 1st September 2021.

Hi bug reporter and hi assignee and others involved,

Please reopen this bug report if it is still valid for Mageia 8 or 9(cauldron), and change "Version:" in the upper left of this report accordingly.

This report is being closed as OLD because it was filed against Mageia 7, for which  support ended on June 30th 2021.

Thanks,
Marja

Status: NEW => RESOLVED
Resolution: (none) => OLD

I encountered this bug in Mageia 8. 

My system has AMD/ATI/Radeon graphics.
Trying this bug after adding 'plasma-workspace-wayland'.

MCC does not launch from the task manager's icon neither from the welcome window's one. In both cases, the root password window is shown, accepts the passowrd but then nothing happens.

Back on plasma-xorg MCC's window is showing again.

Status: RESOLVED => UNCONFIRMED
CC: (none) => zini.lorenzo
Ever confirmed: 1 => 0
Resolution: OLD => (none)