Description of problem: I try to launch mcc from the window manager menu. It fails. I try to launch mcc from a terminal. It fails, but produces some diagnostics. I did all the updates, and it still fails. Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. install mageia 10 alpha 1 i686 (with lxde window manager) 2. run all updates 3. try to run mcc, and it fails Here is the output of mcc, as well as uname: # mcc Too late to run INIT block at /usr/lib/perl5/vendor_perl/Glib/Object/Introspection.pm line 257. Ignore the following Glib::Object::Introspection & Gtk3 warnings Subroutine Gtk3::main redefined at /usr/share/perl5/vendor_perl/Gtk3.pm line 539. Attempt to call undefined import method with arguments (":helpers" ...) via package "ugtk3" (Perhaps you forgot to load the package?) at /usr/lib/libDrakX/ugtk3.pm line 1501. "cannot run /usr/sbin/isodumper" since it is not installed [Writing ISO] at /usr/libexec/drakconf line 841. Overriding existing handler for signal 10. Set JSC_SIGNAL_FOR_GC if you want WebKit to use a different signal libEGL warning: DRI3 error: Could not get DRI3 device libEGL warning: Activate DRI3 at Xorg or build mesa with DRI2 libEGL warning: DRI3 error: Could not get DRI3 device libEGL warning: Activate DRI3 at Xorg or build mesa with DRI2 [root@localhost xxx]# uname -a Linux localhost 6.12.62-desktop-5.mga10 #1 SMP PREEMPT_DYNAMIC Wed Dec 17 13:01:13 UTC 2025 i686 GNU/Linux Hardware is a HP s7310n with a Celeron M 370 D and 2.5gb of ram.
Summary: mcc fails => mcc fails on mageia 10 alpha 1 i686
Thank you for the report. Please post the ouput of: $ inxi -MS to summarise your system. Assigning to tools for MCC.
Keywords: (none) => 10alpha1Status comment: (none) => mageia 10 alpha 1 i686Assignee: bugsquad => mageiatools
# inxi -MS System: Host: localhost Kernel: 6.18.6-desktop-2.mga10 arch: i686 bits: 32 Desktop: LXQt v: 2.3.2 Distro: Mageia 10 Machine: Type: Desktop System: HP Pavilion 061 product: EN996AA-ABA s7310n v: 0nx1201RE101ONYX200 serial: CNH6091QQZ NA610 Mobo: ASUSTeK model: Onyx2 v: 1.xx serial: X312345678 Firmware: BIOS vendor: American Megatrends v: 3.06 date: 10/28/2005
Your card or graphic driver perhaps not support DRI3 Provide output of inxi -G
Guiseppe don't you have build a mesa compat package? I not see it
Flags: (none) => need_info?(ghibomgx)
compat-mesa currently provides primarily the missing libxatracker2, which is used for instance by the DDX vmware driver (e.g., for VirtualBox). It doesn't yet provide support for older chipsets; mesa-amber would be needed for that, and we don't have it yet. I started working on it some time ago, it's essentially a stripped-down mesa-21.3.9, but haven't had time to complete it (bug #31921). Anyway the mesa-compat package *is* available for i686, and I see libxatracker in the current cauldron i686 build. I can run MCC in an i686 VM and although there are warnings about acceleration, it doesn't prevent MCC from starting. I suggest trying to complete the installation in text mode (booting to text mode, typing "text") and then upgrading to the current cauldron to get everything updated.
CC: (none) => ghibomgx
# inxi -G Graphics: Device-1: Intel 82915G/GV/910GL Integrated Graphics driver: i915 v: kernel Display: x11 server: X.org v: 1.21.1.21 with: Xwayland v: 24.1.9 driver: X: loaded: intel,v4l dri: i915 gpu: i915 resolution: 1920x1080~60Hz API: OpenGL v: 4.5 vendor: mesa v: 25.3.3 renderer: llvmpipe (LLVM 20.1.8 128 bits) API: EGL Message: EGL data requires eglinfo. Check --recommends. Info: Tools: api: glxinfo de: kscreen-doctor x11: xdpyinfo, xprop, xrandr The installation is complete, and I have updated all packages as of about 2 hours ago. mcc still fails with the DRI3 error.
Are you using modesetting or intel driver in /etc/X11/xorg.conf?
lspcidrake -v what video chipset shows?
grep -i intel xorg.conf VendorName "Intel Corporation" BoardName "Intel 810 and later" Driver "intel" lspcidrake -v | grep -i graphic Card:Intel 810 and later: Intel Corporation|82915G/GV/910GL Integrated Graphics Controller [DISPLAY_VGA] (vendor:8086 device:2582 subv:103c subd:2a2d) (rev: 04)
Try to switch to modesetting (Intel Kernel Mode setting (Xorg modesetting) or modesetting) from drakx11 or replacing "intel" with "modesetting" in the Driver line of xorg.conf and see if obtaining the same problems.
By changing the Driver line in xorg.conf to modesetting, and then rebooting, mcc now runs correctly. Unfortunately, the graphical login for mageia now does not display any text of any kind. So the username is blank. When i type in my password, there are no black dots, rather there is no text of any kind. The system is usable as long as I don't want to change users logging in.
Does other display managers (gdm, xdm) from drakdm, shows the same behaviour?
It is not clear how to switch display managers, as there is no text visible on the login screen to enable me to see what display manager is selected.
xdm works properly, displaying text.
The issue with login could be recent changes in cauldron force sddm-wayland package Try unistall and switch back to sddm or install lightdm and use drakdsm to switch
I installed lightdm, and switched to it via drakdm. When I rebooted, I got a full screen of text error messages listing a bunch of deleted files and deleted <name>.so files. I get a mouse cursor, but I am unable to log in. I thought I set the graphical login to be disabled during install, but it seemed to be enabled, and now the system is in an unusable state. I cannot log in. I suppose I could reinstall, but that seems to be my only option. Hopefully with the info I have provided, some bug fixes can be made.
So to resume: - switching to modesetting works but loose characters with sddm display manager, after login but mcc works and system seems to be stable with it. - switching to xdm, get display manager and system working - switching to lxdm got in an unpredictable and unstable state. Does 3D work when you can successful login? E.g. "glxinfo -B" shows llvmpipe or hardware acceleration? Try to boot in VT mode (adding 3 to booting cmdline) then switch to a working dm using text utilities (drakdm, drakx11, etc). Then look in journal (journalctl) or dmesg to see if there are some hings about which error is detect.
(In reply to jeff deifik from comment #16) > I installed lightdm, and switched to it via drakdm. > When I rebooted, I got a full screen of text error messages listing a bunch > of deleted files and deleted <name>.so files. I get a mouse cursor, but I am > unable to log in. > > I thought I set the graphical login to be disabled during install, but it > seemed to be enabled, and now the system is in an unusable state. I cannot > log in. > > I suppose I could reinstall, but that seems to be my only option. > > Hopefully with the info I have provided, some bug fixes can be made. Maybe you switch to text mode (CTRL-ALT-F3 e.g.) and then login in the text console, then put xdm back as it's the only one working for you.
CC: (none) => bruno
I was able to switch back to xdm. # glxinfo -B name of display: :0 display: :0 screen: 0 direct rendering: Yes Extended renderer info (GLX_MESA_query_renderer): Vendor: Mesa Project (0x8086) Device: i915 (chipset: 915G) (0x2582) Version: 25.3.3 Accelerated: yes Video memory: 192MB Unified memory: yes Preferred profile: compat (0x2) Max core profile version: 0.0 Max compat profile version: 2.1 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 2.0 OpenGL vendor string: Mesa Project OpenGL renderer string: i915 (chipset: 915G) OpenGL version string: 2.1 Mesa 25.3.3 OpenGL shading language version string: 1.20 OpenGL ES profile version string: OpenGL ES 2.0 Mesa 25.3.3 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 1.0.16
What is the output of "rpm -qa | grep sddm"? Does coredumpctl shows anything about the previous crashes? So definitively is this chipset better supported with "modesetting" than "intel"? However this is an old chipset and it's supporting at most opengl 2.1, with a core profile of 0.0 (which means almost nothing...). Most of modern desktop requires at least a complete OpenGL 3.3, that's why probably the other display managers were crashing, because they assumed there was an higher OpenGL level available. Plasma might be also unstable there too. Have you tried it? You might also try to disable the hardware 3D acceleration and rely on software only 3D rendering, trough llvmpipe. There is an option in drakx11 (-> Options --> Graphic card Options -> Disable Hardware Acceleration). With llvmpipe renderer the OpenGL level exposed is of 4.5.
# rpm -qa | grep sddm sddm-0.21.0-9.mga10 coredumpctl TIME PID UID GID SIG COREFILE EXE SIZE Thu 2026-01-22 09:49:27 PST 2325 0 0 SIGFPE present /usr/bin/perl5.42.0 8.2M Thu 2026-01-22 09:51:46 PST 2818 0 0 SIGFPE present /usr/bin/perl5.42.0 8.2M Thu 2026-01-22 09:55:03 PST 3529 0 0 SIGFPE present /usr/bin/perl5.42.0 8.2M Thu 2026-01-22 10:31:53 PST 25328 0 0 SIGFPE present /usr/bin/perl5.42.0 8.2M Thu 2026-01-22 15:10:39 PST 2829 0 0 SIGFPE present /usr/bin/perl5.42.0 8.3M Fri 2026-01-23 09:47:11 PST 287 0 0 SIGSEGV none /usr/sbin/plymouthd - Fri 2026-01-23 10:17:46 PST 1757 1000 1000 SIGTRAP present /usr/bin/light-locker 1.8M Fri 2026-01-23 14:11:01 PST 1782 1000 1000 SIGTRAP present /usr/bin/light-locker 1.8M
(In reply to Giuseppe Ghibò from comment #20) > You might also try to disable the hardware 3D acceleration and rely on > software only 3D rendering, trough llvmpipe. There is an option in drakx11 > (-> Options --> Graphic card Options -> Disable Hardware Acceleration). With > llvmpipe renderer the OpenGL level exposed is of 4.5. Of course this is only for Xorg, and won't apply if you have the display manager running the greeter itself under Wayland, as for comment #15. But in your case shouldn't, as you have now only sddm installed and not sddm-plasma-wayland.
Strange that FPE in perl. What is the output of "coredumpctl debug 2325"?
No idea. How do I view/include it?
I have similar warning connecting by ssh from mga9 system to cauldron system after become root in the remote system and try to run mcc mcc runs well if I run from rustdesk session so is not an issue in the remote system
Another way to disable the 3D hw acceleration if the driver has a too poor opengl level supported, is to add Option "AccelMethod" "none" (same as from drakx11), to the Device section of xorg.conf.
(In reply to jeff deifik from comment #24) > No idea. How do I view/include it? just type "coredumpctl debug 2325" (it might require to install the gdb package) and see the lines near the stack trace.
Created attachment 15370 [details] output from coredumpctl
Done. See the_dump.txt I did install gdb, but perhaps more is needed for a useful output.
I see lots of Can't open file But this one get my attention Could not load shared library symbols for [32m/lib/libgallium-25.1.9.so The last file is libgallium-25.3.4.so I really think you should update your system by example liblzma.so.5.8.1 is replaced by liblzma.so.5.8.2 from liblzma5-5.8.2 Also check if you still have mga9 packages rpm -qa|grep mga9 Other possibility is you got a rotten mirror if you use the mirror list
It is a fresh install, so there is no mageia-9 packages present. This is a detailed core dump of past problems, not current issues, so I don't see much value in debugging it, as I don't know how I would recreate the issue. I did an update after installing after jan 20th 2026.
> I did an update after installing after jan 20th 2026. Update again for liblzma5-5.8.2-1.mga10.i686.rpm, Comment 30 That package file date is 2025-12-20 so you should have got it, please check.
CC: (none) => fri
Using mcc, I was able to update my update sources. I then updated all packages, however, liblzma was not in the list of rpm's to update. There were about 30 packages updated.
liblzma5-5.8.2-1.mga10 is currently installed.
See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=33208