Red Hat Bugzilla – Bug 846466
pls add X-Mate to OnlyShowIn entry in desktop files
Last modified: 2013-05-30 22:24:11 EDT
Description of problem:
The desktop file of the daemons contains this entry.
Can you add X-Mate to the OnlyShowIn entry because without X-Mate the 4 daemons doesn't start really in Mate-Desktop.
A lot of applications need gnome-keyring for goog working.
eg. networkmanager, claws, etc.
X-Mate because Mate isn't implemented in desktopfile now.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
i'm fedora packager of mate-keyring and other MATE packages.
It would be very nice if you could iplement this in your desktop files.
This helps me and users to get all popular gnome and other applications to get working well in mate.
This affects also f17 and f16 because we building packages for those too.
My fas user name raveit65 .
Thank you if you could do that for us.
PS: If you need more info let me know.
Sorry for some typos errors.
A good description of the issue you can find here
Also what i try to for the moment to solve the issue.
This sounds like something that should go upstream. Unless you have strong reasons why not, could you please file a bug at bugzilla.gnome.org rather than patching this in here in the Fedora package?
What does 'mate-keyring' have to do with this bug report? Actually, why does mate-keyring even exist? Non GNOME desktops have been using gnome-keyring since forever. It seems strange that Mate would need to fork it.
Oh and when you do file that bug upstream, could you provide a patch please? Thanks :)
(In reply to comment #2)
> This sounds like something that should go upstream. Unless you have strong
> reasons why not, could you please file a bug at bugzilla.gnome.org rather
> than patching this in here in the Fedora package?
Thx, i will do that, in this case it's good for all other distros.
Actually mate is in linuxmint and f18, but linuxmint has complete switch to mate-keyring so far as i know.
So for the moment this affected only fedora.
> What does 'mate-keyring' have to do with this bug report? Actually, why does
> mate-keyring even exist? Non GNOME desktops have been using gnome-keyring
> since forever. It seems strange that Mate would need to fork it.
I'm not mate upsream, if they forked gnome2 they decided to fork gnome-keyring too.
My personaly opion is not to use a second keyring framework for mate, as you said other DE's also use gnome-keyring.
Becuse this prodused issues.
But current situation is that they use their own keyring.
Created attachment 603214 [details]
patch for 3.2.1 is different
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.
(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)
More information and reason for this action is here:
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This was fixed upstream: