Bug 2217704 - mate-desktop-libs coredumps because it packages an old org.mate.sound.gschema.xml
Summary: mate-desktop-libs coredumps because it packages an old org.mate.sound.gschema...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: mate-desktop
Version: epel9
Hardware: Unspecified
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Robert Scheck
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-06-26 23:56 UTC by bugzilla
Modified: 2023-08-17 20:48 UTC (History)
3 users (show)

Fixed In Version: mate-desktop-1.26.1-2.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-07-08 01:53:39 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description bugzilla 2023-06-26 23:56:57 UTC
Description of problem:

Changing the volume with the volume hotkey triggers the following core dump:

(mate-settings-daemon:18336): GLib-GIO-ERROR **: 14:01:27.785: Settings schema 'org.mate.sound' does not contain a key named 'volume-overamplifiable'

Version-Release number of selected component (if applicable):

mate-desktop-libs-1.26.1-1.el9.x86_64



How reproducible:

easy

Steps to Reproduce:
1. Install mate desktop
2. Start a mate session
3. Set a hotkey for "Volume Up" in System->Prefs->Hardware->Keyboard Shortuts
4. Press the hotkey

Actual results:

Crash with: 

(mate-settings-daemon:18336): GLib-GIO-ERROR **: 14:01:27.785: Settings schema 'org.mate.sound' does not contain a key named 'volume-overamplifiable'


Expected results:

No crash, increase volume.

Additional info:

=== FIX ===

It seems that the /usr/share/glib-2.0/schemas/org.mate.sound.gschema.xml file packaged in `mate-desktop-1.26.1-1.el9.src.rpm` (installed in `mate-desktop-libs-1.26.1-1.el9.x86_64`) does not contain the org.mate.sound/volume-overamplifiable key. 

The fix is to download the latest version from mate's github.

This oneliner fixes it:
```
wget -O /usr/share/glib-2.0/schemas/org.mate.sound.gschema.xml https://raw.githubusercontent.com/mate-desktop/mate-desktop/9f81a561186ea52c2bef57b9aaba9e596af4bce2/schemas/org.mate.sound.gschema.xml
```

but to be more precise, this file needs included in `mate-desktop-1.26.1-1.el9.src.rpm`:

https://github.com/mate-desktop/mate-desktop/blob/master/schemas/org.mate.sound.gschema.xml

Comment 1 Fedora Update System 2023-06-29 20:53:21 UTC
FEDORA-EPEL-2023-7f2c84d61d has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-7f2c84d61d

Comment 2 Fedora Update System 2023-06-29 20:54:49 UTC
FEDORA-EPEL-2023-fcb6c86952 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-fcb6c86952

Comment 3 Fedora Update System 2023-06-30 01:51:19 UTC
FEDORA-EPEL-2023-7f2c84d61d has been pushed to the Fedora EPEL 9 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-7f2c84d61d

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 4 Fedora Update System 2023-06-30 01:51:20 UTC
FEDORA-EPEL-2023-fcb6c86952 has been pushed to the Fedora EPEL 9 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-fcb6c86952

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 5 Fedora Update System 2023-07-08 01:53:39 UTC
FEDORA-EPEL-2023-7f2c84d61d has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 6 Fedora Update System 2023-07-08 01:53:41 UTC
FEDORA-EPEL-2023-fcb6c86952 has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 7 Scott Milner 2023-08-17 20:48:16 UTC
This problem is currently present in the EPEL 8 repos (package mate-desktop-1.26.1-1.el8)


Note You need to log in before you can comment on or make changes to this bug.