| Summary: | mate-keyring-daemon gets activated instead of gnome-keyring | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Chris Denice <eatdirt> |
| Component: | RPM Packages | Assignee: | Malo Deniélou <pmdenielou> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | tarakbumba |
| Version: | Cauldron | Keywords: | Triaged |
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | mate-keyring-1.6.0-1.mga4.src.rpm | CVE: | |
| Status comment: | |||
|
Description
Chris Denice
2013-10-01 21:39:39 CEST
(if it's wrongly assigned tell us) Keywords:
(none) =>
Triaged
Atilla ÖNTAŞ
2013-10-24 10:59:41 CEST
CC:
(none) =>
tarakbumba For what it worth, I workaround the bug on wmudmount by patching it to link against libmate-keyring and use mate-keyring-daemon (which makes more sense for light window managers). But that bug should remain open till it is definitely fixed without workaround. cheers. Please tell me if i add conflict with gnome-keyring in mate-keyring-daemon helps? I don't think so, that may trigger unwanted conflicts elsewhere, so better let is be this way for the time being. This problem should be fix upstream I guess. cheers, chris. Unfortunately upstream has deprecated mate-keyring in favour of gnome-keyring. mate-keyring won't be in Mate 1.8 See: https://github.com/mate-desktop/mate-keyring/issues/27 I'm closing this bug report as wontfix. Status:
NEW =>
RESOLVED Yep, if mate-keyring becomes deprecated, that's indeed a fix :) Let's wait it dies then! but you provide mate 1.6 no ? so the bug will be still valid in mageia 4 Hi guys, I think WONTFIX is fair, that's not RESOLVED, and the only program which was affected, up to my knowledge, on mga4 is wmudmount that I managed to workaround. So, we are fine for mga4. When mate-keyring will be made obsoleted by gnome-keyring, let's assume for mga5, I can revert my patch for wmudmount to use gnome-keyring and we can drop mate-keyring. So let's see. Anyone is free to reopen that bugs if other progs are affected. cheers, chris. ok great, it's fine for me (In reply to Manuel Hiebel from comment #7) You're right but upstream wont fix this for 1.6 series also. Let it RIP. |