After installation of Pluma it fails to start with error message (pluma:13080): GLib-GIO-ERROR **: Settings schema 'org.mate.lockdown' is not installed Manual installation of package 'mate-desktop-schemas' fixed it. It seems that Pluma is missing a dependency on the 'mate-desktop-schemas' package Reproducible: Steps to Reproduce:
Thanks, assigned to maintainer.
Keywords: (none) => Junior_job, PATCHAssignee: bugsquad => tarakbumbaSeverity: normal => major
I ran across the same problem myself today
CC: (none) => crxssi
I have uploaded an updated pluma package for Mageia 5. Suggested advisory: ======================== This update adds 'mate-desktop-schemas' as a package dependency to fix crashes upon starting.(mga#16186) ======================== Updated packages in core/updates_testing: ======================== pluma-1.8.1-3.1.mga5 pluma-devel-1.8.1-3.1.mga5 Source RPMs: pluma-1.8.1-3.1.mga5.src.rpm
Assignee: tarakbumba => qa-bugs
CC: (none) => davidwhodginsWhiteboard: (none) => advisory
Before update: $ sudo urpmi pluma Package pluma-1.8.1-3.mga5.x86_64 is already installed [lcl@vega ~/test]$ locate org.mate.lockdown /usr/share/glib-2.0/schemas/org.mate.lockdown.gschema.xml Running pluma at the command line brought up a gui with an untitled document. So the schema must have been installed by something at some point. ?? Updated pluma from Core Updates Testing but had to install the development package by hand. [root@vega ~]# urpmi pluma-devel To satisfy dependencies, the following packages are going to be installed: Package Version Release Arch (medium "Core Release (distrib1)") graphite2 1.2.4 3.mga5 x86_64 lib64atk1.0-devel 2.14.0 3.mga5 x86_64 lib64cairo-devel 1.14.0 1.mga5 x86_64 lib64directfb-devel 1.7.5 4.mga5 x86_64 lib64drm-devel 2.4.59 1.mga5 x86_64 lib64graphite2-devel 1.2.4 3.mga5 x86_64 lib64gtk+2.0-devel 2.24.26 3.mga5 x86_64 lib64gtksourceview-2.0-devel 2.11.2 7.mga5 x86_64 lib64harfbuzz-devel 0.9.36 1.mga5 x86_64 lib64pango1.0-devel 1.36.8 3.mga5 x86_64 lib64pciaccess-devel 0.13.2 4.mga5 x86_64 lib64wayland-devel 1.6.0 2.mga5 x86_64 lib64xcomposite-devel 0.4.4 7.mga5 x86_64 lib64xcursor-devel 1.1.14 5.mga5 x86_64 lib64xdamage-devel 1.1.4 7.mga5 x86_64 lib64xfixes-devel 5.0.1 5.mga5 x86_64 lib64xft-devel 2.3.2 3.mga5 x86_64 lib64xi-devel 1.7.4 3.mga5 x86_64 lib64xinerama-devel 1.1.3 5.mga5 x86_64 lib64xrandr-devel 1.4.2 4.mga5 x86_64 lib64xrender-devel 0.9.8 5.mga5 x86_64 lib64xshmfence-devel 1.1 3.mga5 x86_64 lib64xxf86vm-devel 1.1.3 5.mga5 x86_64 pango-doc 1.36.8 3.mga5 noarch (recommended) wayland-tools 1.6.0 2.mga5 x86_64 (medium "Core Updates (distrib3)") lib64expat-devel 2.1.0 9.1.mga5 x86_64 lib64gdk_pixbuf2.0-devel 2.32.1 1.mga5 x86_64 lib64pixman-devel 0.32.8 1.mga5 x86_64 (medium "Core Updates Testing (distrib5)") pluma-devel 1.8.1 3.1.mga5 x86_64 (medium "Tainted Release (distrib21)") lib64dri-drivers 10.5.7 3.mga5.taint> x86_64 lib64gbm1 10.5.7 3.mga5.taint> x86_64 lib64gbm1-devel 10.5.7 3.mga5.taint> x86_64 lib64glapi0-devel 10.5.7 3.mga5.taint> x86_64 lib64mesaegl1 10.5.7 3.mga5.taint> x86_64 lib64mesaegl1-devel 10.5.7 3.mga5.taint> x86_64 lib64mesagl1 10.5.7 3.mga5.taint> x86_64 lib64mesagl1-devel 10.5.7 3.mga5.taint> x86_64 lib64txc-dxtn 1.0.1 7.mga5.taint> x86_64 mesa 10.5.7 3.mga5.taint> x86_64 49MB of additional disk space will be used. 10MB of packages will be retrieved. Used pluma to open a local text file. No problems.
CC: (none) => tarazed25
Testing MGA5 x64 I already had Mate (and hence mate-desktop-schemas) installed, and dared not take out the latter for fear of it taking a raft of stuff with it. So I just compared the Pluma pkg requirements with urpmq. They did *not* change with the update... BEFORE $ rpm -qa | grep pluma pluma-1.8.1-3.mga5 pluma-plugins-1.4.0-3.mga5 $ urpmq --requires pluma caja-schemas ... mate-dialogs ... AFTER $ rpm -qa | grep pluma pluma-1.8.1-3.1.mga5 pluma-plugins-1.4.0-3.mga5 $ urpmq --requires pluma caja-schemas ... mate-dialogs ... NO mate-desktop-schemas. The urpmq --requires ouput for pluma was *identical* to before the update. Is this a valid test? Can I temporarily remove *just* mate-desktop-schemas for a better test?
CC: (none) => lewyssmith
Testing complete mga5 64 urpmq checks the versions in the repository rather than the one installed Lewis, which you can check with rpm instead. With testing disabled it will only check the versions in release & updates. You can specify the media with the --media switch. ie. $ urpmq --requires pluma | grep mate-desktop-schemas --requires behaviour changed, use --requires-recursive to get the old behaviour $ urpmq --requires pluma --media "Core Updates Testing" | grep mate-desktop-schemas --requires behaviour changed, use --requires-recursive to get the old behaviour mate-desktop-schemas Verified with madb diff of the srpm that the only change was to add the require. +Requires: mate-desktop-schemas I'll add the OK for this.
Keywords: (none) => validated_updateWhiteboard: advisory => advisory mga5-64-okCC: (none) => sysadmin-bugs
Repeating for x64, even though already OK'd. Comment 6: > urpmq checks the versions in the *repository* rather than the one installed, > which you can check with rpm instead. With testing disabled it will only check > the versions in release & updates. Yes, I fell into that trap. So my comment 5 was worthless. pluma-1.8.1-3.1.mga5 [the installed update] $ rpm -q -R pluma ... mate-desktop-schemas ... So I confirm the OK.
An update for this issue has been pushed to Mageia Updates repository. http://advisories.mageia.org/MGAA-2015-0152.html
Status: NEW => RESOLVEDResolution: (none) => FIXED