That is provide by dconf-editor and is required by task-mate but not for task-mate-minimal

Whiteboard: (none) => MGA9TOO
Source RPM: mate-panel => task-mate

To be clear 

Requires: dconf-editor 

should be moved from task-mate to task-mate-minimal

I'd say the Requires: should be in mate-panel itself.

in mate-panel, or if needed by every component the requirement can be made by the central lib (e.g. lib64mate-desktop) or mate-desktop

(In reply to Jani Välimaa from comment #3)
> I'd say the Requires: should be in mate-panel itself.
You are the guru for this sort of thing.

Assigning this globally so the 'requires' can be done where best.

Assignee: bugsquad => pkg-bugs
Source RPM: task-mate => task-mate, mate-panel
CC: (none) => jani.valimaa

Looks like this is already fixed in cauldron.
Adding the requirement for mga9 too.

Updated mate-panel
An missing requirement caused mate-panel to crash. This update adds the requirement.

Updates in core/updates_testing

RPM:
lib64mate-panel-applet-gir4.0-1.26.3-1.1.mga9.x86_64.rpm
lib64mate-panel-applet4_1-1.26.3-1.1.mga9.x86_64.rpm
lib64mate-panel-applet4_1-debuginfo-1.26.3-1.1.mga9.x86_64.rpm
lib64mate-panel-applet-devel-1.26.3-1.1.mga9.x86_64.rpm
mate-panel-debuginfo-1.26.3-1.1.mga9.x86_64.rpm
mate-panel-debugsource-1.26.3-1.1.mga9.x86_64.rpm
mate-panel-1.26.3-1.1.mga9.x86_64.rpm

SRPM:
mate-panel-1.26.3-1.1.mga9.src.rpm

Assignee: mageia => qa-bugs

Created attachment 14585 [details]
Test mate-panel packages

I not use mate so just test:

1. Current package not require dconf-editor
2. Testing package require dconf-editor
3. Install mate-panel without issues
4. Uninstall mate-panel and all requires

Despite I'm sure this solves the reported issue, if a real mate user confirms will be good

Mageia9, x64

$ rpm -q mate-panel
mate-panel-1.26.3-1.mga9
$ rpm -q ca.desrt.dconf-editor.Settings
package ca.desrt.dconf-editor.Settings is not installed

In this case Mate is chosen during system installation and task-mate is installed after first boot.

$ locate desrt
/usr/share/applications/ca.desrt.dconf-editor.desktop
/usr/share/dbus-1/services/ca.desrt.dconf-editor.service
/usr/share/dbus-1/services/ca.desrt.dconf.service
/usr/share/glib-2.0/schemas/ca.desrt.dconf-editor.gschema.xml
/usr/share/icons/hicolor/scalable/actions/ca.desrt.dconf-editor.big-rows-symbolic.svg
/usr/share/icons/hicolor/scalable/actions/ca.desrt.dconf-editor.small-rows-symbolic.svg
/usr/share/icons/hicolor/scalable/apps/ca.desrt.dconf-editor.Devel.svg
/usr/share/icons/hicolor/scalable/apps/ca.desrt.dconf-editor.svg
/usr/share/icons/hicolor/symbolic/apps/ca.desrt.dconf-editor-symbolic.svg
/usr/share/metainfo/ca.desrt.dconf-editor.appdata.xml

Have not seen the crash, ever.

CC: (none) => tarazed25

(In reply to Len Lawrence from comment #9)
> Mageia9, x64
> 
> $ rpm -q mate-panel
> mate-panel-1.26.3-1.mga9
> $ rpm -q ca.desrt.dconf-editor.Settings
> package ca.desrt.dconf-editor.Settings is not installed
> 
> In this case Mate is chosen during system installation and task-mate is
> installed after first boot.

If you use task-mate you never get the bug because task-mate have dconf-editor as require, you must use task-mate-minimal

But for testing purposes, you can just uninstall dconf-editor

rpm -e --nodeps dconf-editor

Thanks.  So I would have seen it if I had tested straight after system installation because only task-mate-minimal is installed at that point.  task-mate is installed during post-install configuration, i.e. almost immediately.

Thomas I think you can validate

OK. I was holding back to see if Len wanted to do more. 

Validating.

Keywords: (none) => validated_update
CC: (none) => sysadmin-bugs

An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGAA-2024-0160.html

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