New issue by TeusLollo on void-packages repository

https://github.com/void-linux/void-packages/issues/37555

Description:
### System

* xuname:  
Void 5.15.45_1 x86_64 GenuineIntel uptodate rFFFF
* package:  
gnome-disk-utility-41.0_1

### Expected behavior
"org.gnome.DiskUtility.desktop" file located into "/usr/share/applications" should execute the "gnome-disks" executable when selected through a given App Launcher Application compatible with freedesktop.org specifications, thus launching the Gnome-Disks App. 

### Actual behavior
"org.gnome.DiskUtility.desktop" file located into "/usr/share/applications" fails completely with no error messages when selected into a given App Launcher Application ("wofi" in my current case, with "sway" WM).

Yet, executing the "gnome-disks" executable through CLI works perfectly, and the App itself works perfectly too. 

Also, I went ahead, and utilized "gendesk" to create a custom .desktop file which I put into "~/local/share/applications". I can confirm that such a custom .desktop file WORKS perfectly, and have in fact been using it for a few months already (Hence why I forgot to report before).

Code of MY custom .desktop file, created through "gendesk", and located into "~/local/share/applications", is as follows:

###############################################################################
[Desktop Entry]
Version=1.0
Type=Application
Name=Disks-Gnome
Comment=Disks-Gnome
Exec=gnome-disks
Icon=/home/username/.local/share/applications/FlatDisks.png
Terminal=false
StartupNotify=false
Categories=Application;
###############################################################################

My custom .desktop file, aside from missing localization tags, also misses the "DBusActivatable=true" parameter which I found into "org.gnome.DiskUtility.desktop" file located into "/usr/share/applications", yet I presume this is not very relevant to the issue at hand. 

This has been happening for a few months already (My custom .desktop works fine, thus I forgot to report in the meantime), and has been happening on three separate machines to boot, all with manual install only. App Launcher is currently "wofi" with "sway" WM, but months ago I also saw this happening with "rofi", on "openbox" WM.  

### Steps to reproduce the behavior

Simply select the "org.gnome.DiskUtility.desktop" (Tag-named to "Disks" if App Launcher can read such tags, and is configured to do so) into a given freedesktop.org-compatible App Launcher (This has been happening both with "wofi" and "rofi" on me), and it will NOT execute the "gnome-disks" executable, thus NOT launching the Gnome-Disks App. 

However, executing "gnome-disks" through the CLI, or otherwise utilizing a custom .desktop file created through "gendesk" as mentioned above, both launch the App just fine. 

Maybe some post-install MIME update is missing? This has been happening also on a very recent (Less than 4 weeks) manual Void Install.