Description of problem: 6dev1 : x86_64 : Live Plasma5 : Legacy boot MCC crashes with the following report: "/usr/sbin/drakmenustyle" is not executable [Menus] at /usr/libexec/drakconf line 831 "/usr/sbin/drakbackup" is not executable [Backups] at /usr/libexec/drakconf line 831 "/usr/sbin/tomoyo-gui" is not executable [Tomoyo Policy] at /usr/libexec/drakconf line 831 (drakconf:20762): Glib-GIO-ERROR xx: No GSettings schemas are installed on the system Version-Release number of selected component (if applicable): drakconf-12.60-2.mga6 How reproducible: Steps to Reproduce: 1. 2. 3. Reproducible: Steps to Reproduce:
Not sure if that should have been labelled critical given that mcc is a wrapper for system utilities.
benmc has pointed out that this problem has to do with the necessity of starting the desktop as root in the absence of a login/display manager in the 6dev1 Plasma Live install. His fix was to urpme drakconf, update the media and reinstall drakconf. That somehow gets past the Glib-GIO-ERROR. Not sure what the status of this bug is now.
This must be fixed in lib{,64}gtk+[23]. Both should pulls the needed glib stuff. Else pulling gimp on Plasma5 would fail too...
CC: (none) => thierry.vignaudAssignee: bugsquad => olavSource RPM: drakconf-12.60-2.mga6.src.rpm => gtk+3.0
*** Bug 17247 has been marked as a duplicate of this bug. ***
CC: (none) => westel
Component: Release (media or process) => RPM PackagesSource RPM: gtk+3.0 => gtk+2.0, gtk+3.0
Actually lib{64,}gtk+{2.0_0,3_0} do pull glib2.0-common So sg must be fishy in the gtk+ stack. Do you have a /usr/share/glib-2.0/schemas/gschemas.compiled files?
Keywords: (none) => NEEDINFO
But gsettings-desktop-schemas is not pulled by gtk+. Only by gnome-session/gnome-shell & a couple gtk+ apps (such as gitg or nautilus). It should be pulled by lib(64)gtk+[23] if it's mandated for any gtk+[23] application!!!
Keywords: NEEDINFO => (none)Summary: drakconf crashes in Live Plasma5 desktop in absence of GSettings schemas => drakconf crashes in Live Plasma5 desktop b/c gsettings-desktop-schemas is not pulled by libgtk+[23]
Priority: Normal => HighSeverity: normal => major
CC: (none) => wilcal.int
Should be fixed in latest gtk+[23]
Status: NEW => RESOLVEDResolution: (none) => FIXED
valid for Mageia-6-dev1-i586-DVD.iso: Sun Nov 29 21:42:03 CET 2015 LXDE install
GTK+2.0 doesn't make use of gsettings. Do a grep -r g_setting and you'll se GTK+3.0 delivers the gsettings/schemas it needs with the package. This is not fixed properly.
Status: RESOLVED => UNCONFIRMEDResolution: FIXED => (none)Ever confirmed: 1 => 0
Same here [root@localhost nutzer]# mcc Vector smash protection is enabled. "/usr/sbin/drakmenustyle" is not executable [Menus] at /usr/libexec/drakconf line 831. "/usr/sbin/drakbackup" is not executable [Backups] at /usr/libexec/drakconf line 831. "/usr/sbin/tomoyo-gui" is not executable [Tomoyo Policy] at /usr/libexec/drakconf line 831. openjdk version "1.8.0_65" OpenJDK Runtime Environment (build 1.8.0_65-b17) OpenJDK 64-Bit Server VM (build 25.65-b01, mixed mode) (drakconf:2379): GLib-GIO-ERROR **: No GSettings schemas are installed on the system
CC: (none) => linux
btw: Deskopmanager : LXDE
For me MCC works now.
Sry. No it doesnt. I installed some packages/programs and it installed the missing lib/schemas (as dependency for those packages) too.
valid for Mageia-6-dev1-x86_64-DVD.iso: Sun Nov 29 21:51:31 CET 2015 LXDE after updates as part of installation. current work-a-round is to urpmi nautilus + dependencies
Today i tested Mageia-6-dev1-i586-DVD.iso on VM. Selected MATE De only. Lightdm refused to start Mate, X restarts instead. Journalctl logs show me that there are "No Gsettings schemas installed". Upon installing this iso, there are lots of script failed messages but they did not show which packages script failed. I went to tty2 and compiled gschemas my self: glib-compile-schemas /usr/share/glib-2.0/schemas Then i can log into a working Mate session.So, it is likely that schemas installed but rpm filetriggers failing to compile schemas.
CC: (none) => tarakbumba
Whiteboard: (none) => 6dev1
Status: UNCONFIRMED => NEWEver confirmed: 0 => 1
What's the report of "rpm -qf /usr/share/glib-2.0/schemas/*|sort -u" on affected machines?
(In reply to Thierry Vignaud from comment #16) > What's the report of "rpm -qf /usr/share/glib-2.0/schemas/*|sort -u" on > affected machines? [atilla@localhost ~]$ rpm -qf /usr/share/glib-2.0/schemas/*|sort -u atril-1.12.0-1.mga6 caja-schemas-1.12.0-1.mga6 cheese-3.18.1-1.mga6 dconf-editor-3.19.2-1.mga6 empathy-3.12.11-1.mga6 engrampa-1.12.0-1.mga6 evolution-data-server-3.19.2-1.mga6 folks-common-0.11.2-1.mga6 gcr-3.18.0-1.mga6 glib2.0-common-2.47.3-1.mga6 gnome-keyring-3.18.3-1.mga6 gnome-online-accounts-3.19.2-1.mga6 gnome-packagekit-common-3.18.0-1.mga6 gsettings-desktop-schemas-3.19.2-1.mga6 gthumb-3.4.1-1.mga6 gtk+3.0-3.19.3-2.mga6 gucharmap-3.18.2-1.mga6 gvfs-1.26.2-1.mga6 libgweather-3.18.1-1.mga6 libmatekbd-1.12.0-1.mga6 libmateweather-1.12.0-1.mga6 marco-1.12.0-1.mga6 mate-control-center-1.12.0-1.mga6 mate-desktop-schemas-1.12.0-1.mga6 mate-notification-daemon-1.12.0-1.mga6 mate-panel-1.12.0-1.mga6 mate-power-manager-1.12.0-1.mga6 mate-screensaver-1.12.0-1.mga6 mate-session-manager-1.12.0-1.mga6 mate-settings-daemon-1.12.0-1.mga6 mate-terminal-1.12.0-1.mga6 mousetweaks-3.12.0-3.mga5 pluma-1.12.0-1.mga6 telepathy-logger-0.8.2-1.mga6 telepathy-mission-control-5.16.3-4.mga5 totem-3.18.1-1.mga6 yelp-3.19.1-1.mga6 As you can see that gsetings-desktop-schemas already installed. Thus your fix is unneeded. We must fix rpm filetriggers.
Created attachment 7269 [details] mga6-dev1_Package installation screen in installer This screen shows the scripts failed errors on installer.
Because of the "script failed for" we habe Bug #17217
valid for : Mageia-6-dev1-LiveDVD-PLASMA5-x86_64-DVD.iso: Sun Dec 6 13:30:00 CET 2015 workaround: urpmi:addmedia.... urpme drakconf urpmi drakconf [ 31 packages install ]
(In reply to psyca from comment #19) > Because of the "script failed for" we habe Bug #17217 So, this may in close relation with #17217. Note that this problem not only occurs with drakconf but applications those use gsettings.
Note that mageia-theme-gnome used to still manually run/call glib-compile-schemas. As this should be handled by file triggers I removed that in mageia-theme mageia-theme-1.5.0.44-3.mga6. Another indicator that something could be up with the filetrigger during install.
Created attachment 7273 [details] a method for fixing Live Plasma5 x86 MCC crash At launch of desktop Plasma5 x86 dvd live system, while in live mode, I check if MCC or Mageia Welcome crash- if so, I open konsole and add online media, urpmi.addmedia --distrib --mirrorlist'......etc, when added I then remove drakconf: urpme drakconf. Orphans are reported, but I don't remove them, and then urpmi drakconf,which pulls in these packages.
CC: (none) => ngompa13Whiteboard: 6dev1 => (none)
(In reply to ben mcmonagle from comment #23) > Created attachment 7273 [details] > a method for fixing Live Plasma5 x86 MCC crash > > At launch of desktop Plasma5 x86 dvd live system, while in live mode, I > check if MCC or Mageia Welcome crash- if so, I open konsole and add online > media, urpmi.addmedia --distrib --mirrorlist'......etc, when added I then > remove drakconf: urpme drakconf. Orphans are reported, but I don't remove > them, and then urpmi drakconf,which pulls in these packages. This also indicates that it is a rpm-filetrigger issue at distro install time. It is obvious that removing and reinstalling drakconf triggers glib-compile-schemas and thus workarounds the issue. Problem is finding why scriplets failed at installing Mageia. May be a missed configuration at installer?
IMO this is because of bug 17217. I'm fairly sure that ldconfig is ran too late as explained in bug 17217 comment 9. Loads of filetriggers fail with error 127. The schema update filetrigger specifically checks if the command it runs exists. No way it can fail with error 127 other than some problem with the command itself. *** This bug has been marked as a duplicate of bug 17217 ***
Status: NEW => RESOLVEDResolution: (none) => DUPLICATE
*** Bug 17382 has been marked as a duplicate of this bug. ***
CC: (none) => bittwister2