The "drakconf" program crashed. Drakbug-18.32 caught it. Previously I had several other issues with this. I had about two SEGV bugs reported when I closed MCC. This is a new re-install of Cauldron, using the existing partitions, after an attempt to install using the "Erase and format the disk" option crashed on UEFI MBR issues. Yesterday MCC worked fine. On boot up, MCC does not react to the GUI launcher. Open properties; /usr/bin/ drakconf. Launcher no reaction on "Command" file icon. Terminal same. Internet cap. Will bug it later. Other issues as well. Similar. you must be root to run this program at /usr/lib/libDrakX/common.pm line 596. Perl's trace: drakbug::bug_handler() called from /usr/lib/libDrakX/common.pm:596 common::require_root_capability() called from /usr/libexec/drakconf:64 Theme name: Adwaita Kernel version = 5.7.9-desktop-1.mga8 Distribution=Mageia release 8 (Cauldron) for x86_64 CPU=Intel(R) Core(TM) i3-2328M CPU @ 2.20GHz
In a terminal such as konsole, try the command "mcc".
CC: (none) => davidwhodgins
There are several bugs pointing to MCC crashing when it is closed, notably Bug 26944, of which this is probably another duplicate. For the other points: > crashed on UEFI MBR issues It has never been a good idea to mix EFI (normally GPT) and MBR, too many parameters to fiddle. The answer is usually there in EFI BIOS/firmware. > MCC does not react to the GUI launcher etc You can accept that very many Mageia 8/Cauldron systems are running without these problems, so they look specific to you. You can raise other bugs. I was unsure what you meant by '"Command" file icon'.
CC: (none) => lewyssmith
(In reply to Dave Hodgins from comment #1) > In a terminal such as konsole, try the command "mcc". Did that and this is what I get; [root@localhost caldon]# mcc Too late to run INIT block at /usr/lib64/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. GLib-GObject-CRITICAL **: g_boxed_type_register_static: assertion 'g_type_from_name (name) == 0' failed at /usr/lib64/perl5/DynaLoader.pm line 210. GLib-GObject-CRITICAL **: g_boxed_type_register_static: assertion 'g_type_from_name (name) == 0' failed at /usr/lib64/perl5/DynaLoader.pm line 210. GLib-GObject-CRITICAL **: g_boxed_type_register_static: assertion 'g_type_from_name (name) == 0' failed at /usr/lib64/perl5/DynaLoader.pm line 210. GLib-GObject-CRITICAL **: g_boxed_type_register_static: assertion 'g_type_from_name (name) == 0' failed at /usr/lib64/perl5/DynaLoader.pm line 210. "cannot run /usr/sbin/isodumper" since it is not installed [Writing ISO] at /usr/libexec/drakconf line 833. Oops, secure memory pool already initialized Oops, secure memory pool already initialized MCC does open; however. (In reply to Lewis Smith from comment #2) > There are several bugs pointing to MCC crashing when it is closed, notably > Bug 26944, of which this is probably another duplicate. > > For the other points: > > crashed on UEFI MBR issues > It has never been a good idea to mix EFI (normally GPT) and MBR, too many > parameters to fiddle. The answer is usually there in EFI BIOS/firmware. > > > MCC does not react to the GUI launcher etc > You can accept that very many Mageia 8/Cauldron systems are running without > these problems, so they look specific to you. You can raise other bugs. > I was unsure what you meant by '"Command" file icon'. History. This is a Windows 8.1 i3 bought off the shelf. Converted it to Mageia 5, just after Mga4. MCC is not the issue. There are other issues related to this as I can see it. Dolphin has to be opened up AND my External Hard Drive opened by clicking on the Panel to get it in the window, before I can open a file in LibreOffice for instance. Error message "does not exist". Doing ]# "/usr/bin/dolphin" gives no response. Several others do the same. Both GUI and CLI. Doktor5000 helped me to get light-locker set up in 5. I used 6 and 6.1 and it did not work again. Skipped 7 and 7.1. Installed Cauldron and it worked. Then I started installing my applications and it went missing again. I plan to re-install Cauldron to see which application has that effect and when. Did this just now. [root@localhost caldon]# locate light-locker /usr/share/glib-2.0/schemas/60-xfce4-light-locker-settings.gschema.override [root@localhost caldon]# find light-locker find: ‘light-locker’: No such file or directory [root@localhost caldon]# which light-locker which: no light-locker in (/usr/local/sbin:/usr/sbin:/usr/local/bin:/usr/bin:/usr/lib64/qt5/bin) [root@localhost caldon]# The '"Command" file icon' can be found when you create a new Launcher or edit it. As for "crashed on UEFI MBR issues", not my doing. See History. I usually install Mageia off ISO disc, after clearing the HDD with Killdisk. This time neither Killdisk or Mageia would boot from ISO discs. This comes to you with the compliments of a USB stick. Oh yes, Isodumper and K3b did the same. The MCC GUI icon has the "/usr/bin/drakconfig" command as installed. That file is now missing from /usr/bin. Searched and tried "/usr/libexec/drakconfig". Same action but the file is there. Result. There is some link between GUI Launchers/Terminal and the applications themselves that went astray. FWIW; [root@localhost caldon]# lspcidrake -v xhci_pci : Intel Corporation|7 Series/C210 Series Chipset Family USB xHCI Host Controller [SERIAL_USB] (vendor:8086 device:1e31 subv:17aa subd:3977) (rev: 04) Card:Intel 810 and later: Intel Corporation|2nd Generation Core Processor Family Integrated Graphics Controller [DISPLAY_VGA] (vendor:8086 device:0116 subv:17aa subd:3977) (rev: 09) ehci_pci : Intel Corporation|7 Series/C216 Chipset Family USB Enhanced Host Controller #1 [SERIAL_USB] (vendor:8086 device:1e26 subv:17aa subd:3977) (rev: 04) ehci_pci : Intel Corporation|7 Series/C216 Chipset Family USB Enhanced Host Controller #2 [SERIAL_USB] (vendor:8086 device:1e2d subv:17aa subd:3977) (rev: 04) unknown : Intel Corporation|7 Series/C210 Series Chipset Family PCI Express Root Port 2 [BRIDGE_PCI] (vendor:8086 device:1e12) (rev: c4) unknown : Intel Corporation|2nd Generation Core Processor Family DRAM Controller [BRIDGE_HOST] (vendor:8086 device:0104 subv:17aa subd:3977) (rev: 09) i2c_i801 : Intel Corporation|7 Series/C216 Chipset Family SMBus Controller [SERIAL_SMBUS] (vendor:8086 device:1e22 subv:17aa subd:3977) (rev: 04) snd_hda_intel : Intel Corporation|7 Series/C216 Chipset Family High Definition Audio Controller [MULTIMEDIA_AUDIO_DEV] (vendor:8086 device:1e20 subv:17aa subd:3977) (rev: 04) alx : Qualcomm Atheros|AR8162 Fast Ethernet [NETWORK_ETHERNET] (vendor:1969 device:1090 subv:17aa subd:3979) (rev: 10) mei_me : Intel Corporation|7 Series/C216 Chipset Family MEI Controller #1 [COMMUNICATION_OTHER] (vendor:8086 device:1e3a subv:17aa subd:3977) (rev: 04) ath9k : Qualcomm Atheros|AR9485 Wireless Network Adapter [NETWORK_OTHER] (vendor:168c device:0032 subv:17aa subd:3218) (rev: 01) lpc_ich : Intel Corporation|HM76 Express Chipset LPC Controller [BRIDGE_ISA] (vendor:8086 device:1e59 subv:17aa subd:3977) (rev: 04) unknown : Intel Corporation|7 Series/C216 Chipset Family PCI Express Root Port 1 [BRIDGE_PCI] (vendor:8086 device:1e10) (rev: c4) unknown : Intel Corporation|7 Series Chipset Family 6-port SATA Controller [AHCI mode] [STORAGE_SATA] (vendor:8086 device:1e03 subv:17aa subd:3977) (rev: 04) hub : Linux 5.7.9-desktop-1.mga8 ehci_hcd|EHCI Host Controller [Hub|Unused|Full speed (or root) hub] (vendor:1d6b device:0002) hub : Intel Corp.|Integrated Rate Matching Hub [Hub|Unused|Full speed (or root) hub] (vendor:8087 device:0024) btusb : Atheros Communications|Bluetooth USB Host Controller [Wireless|Radio Frequency|Bluetooth] (vendor:0cf3 device:3004) rtsx_usb : Generic|USB2.0-CRW (vendor:0bda device:0129) hub : Linux 5.7.9-desktop-1.mga8 ehci_hcd|EHCI Host Controller [Hub|Unused|Full speed (or root) hub] (vendor:1d6b device:0002) hub : Intel Corp.|Integrated Rate Matching Hub [Hub|Unused|Full speed (or root) hub] (vendor:8087 device:0024) hub : Linux 5.7.9-desktop-1.mga8 xhci-hcd|xHCI Host Controller [Hub|Unused|Full speed (or root) hub] (vendor:1d6b device:0002) usbhid : Logitech|USB Receiver [Human Interface Device|Boot Interface Subclass|Mouse] (vendor:046d device:c52f) hub : VIA Labs, Inc. |USB2.0 Hub [Hub|Unused|Full speed (or root) hub] (vendor:2109 device:2811) hub : VIA Labs, Inc. |USB2.0 Hub [Hub|Unused|Full speed (or root) hub] (vendor:2109 device:2811) usb_storage : SanDisk|Cruzer [Mass Storage|SCSI|Bulk-Only] (vendor:0781 device:5530) hub : Linux 5.7.9-desktop-1.mga8 xhci-hcd|xHCI Host Controller [Hub|Unused|Full speed (or root) hub] (vendor:1d6b device:0003) hub : VIA Labs, Inc. |USB3.0 Hub [Hub|Unused|Full speed (or root) hub] (vendor:2109 device:8110) hub : VIA Labs, Inc. |USB3.0 Hub [Hub|Unused|Full speed (or root) hub] (vendor:2109 device:8110) usb_storage : Seagate |Expansion [Mass Storage|SCSI|Bulk-Only] (vendor:0bc2 device:2312) usb_storage : Seagate |Expansion [Mass Storage|SCSI|Bulk-Only] (vendor:0bc2 device:2312) hid_generic : Logitech USB Receiver hid_generic : Logitech USB Receiver hid_generic : Logitech M305 [root@localhost caldon]#
Too many problems special to you. Are you using Plasma? CC'ing Aurelian who is more expert about that. > Dolphin has to be opened up AND my External Hard Drive opened by clicking > on the Panel to get it in the window, before I can open a file in > LibreOffice for instance External drives have to be mounted before they can be accessed. There is usually a notification when they are connected (not tried booting with one already connected) asking what you want to do. I suspect the manipulation you describe is to do with this, and comes under 'normal behaviour'. There is probably an option somewhere about auto-mounting removable media. Desktops which show 'other' partitions/devices enable them to be mounted by right-clicking their desktop icons. > MCC does not react to the GUI launcher > dolphin gives no response. Several others do the same. Both GUI and CLI. Which I take it means that some applications do not launch from their menu or taskbar icons? Not even from a terminal? You are sure? MCC did. Are you saying that they do not launch after installation+update; or cease to launch later on? > # "/usr/bin/dolphin" gives no response $ sudo /usr/bin/dolphin Executing Dolphin with sudo is not possible due to unfixable security vulnerabilities. # dolphin [does not launch from root prompt] QStandardPaths: wrong ownership on runtime directory /run/user/1001, 1001 instead of 0 QStandardPaths: wrong ownership on runtime directory /run/user/1001, 1001 instead of 0 kf.service.services: The desktop entry file "/usr/share/applications/org.gnome.ChromeGnomeShell.desktop" has Type= "Application" but no Exec line kf.service.sycoca: Invalid Service : "/usr/share/applications/org.gnome.ChromeGnomeShell.desktop" "Session bus not found\nTo circumvent this problem try the following command (with Linux and bash)\nexport $(dbus-launch)" which probably is the same thing. Do not use Dolphin as root. > light-locker > Installed Cauldron and it worked. Then I started installing my > applications and it went missing again Why all the fuss about this? It is a normal package which requires use of lightdm - it says so. You are saying that having installed it - which has a lot of components - it just 'disappeared' after installing other applications? This is getting surreal. > neither Killdisk or Mageia would boot from ISO discs. > This comes to you with the compliments of a USB stick Having seen this recently, it was down to a BIOS/firmware setting. > no reaction on "Command" file icon One that you have created. For a program or location? On the desktop or the taskbar? Does it never work, or work initially then not work?
CC: (none) => ouaurelienSummary: drakconf crashed => Various Mageia 8 problems
This should be reported to a forum dedicated to Cauldron. Rationale to bugzilla is to take each bug separately. 1) In recent QT 5 and KDE Frameworks, Dolphin can't be launched as root with sudo or after a "su -" in a Terminal. GUI application can't run as root as-is. This behavior is needed with Wayland stuff. If you REALLY want to launch Dolphin as root, do: $ su -c 'dbus-launch dolphin' This should REALLY be avoided. 2) Why use light-locker with a Plasma environment? 3) UEFI can't boot DVD ISO, this is a firmware bug or a computer manufacturer who wants this behavior. Also, next time you reinstall, I suggest you to use a UEFI/GPT partition type. Mixing MBR and UEFI should really be avoided. 4) On Plasma, external drives mount when clicking on it on Dolphin sidebar or in Removable Device Tray icon. Some settings in Systemsettings5 could help you to have an other behavior. I use Mageia Cauldron on daily basis, I really advice you to reinstall from the beta 1 Classic ISO. Don't forget to update all installed packages on first reboot. I will close this INVALID, too many issues at the same time. Feel free to report one bug you found at once, feel free to add screenshots in order to help us understand. I really can't add here further action/details/proposing way as if I do this, I will open a pandora-box and future bug reports will have too many issues in them making us difficult to resolve them. Best regards,
Resolution: (none) => INVALIDStatus: NEW => RESOLVED
(In reply to Aurelien Oudelet from comment #5) > This should be reported to a forum dedicated to Cauldron. Chris, please use https://forums.mageia.org/en/viewforum.php?f=15 > Rationale to bugzilla is to take each bug separately.
CC: (none) => fri