Bug 972614
| Summary: | emblem doesn't work properly with gvfs 1.14.2-4.fc18 | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Kazutoshi Morioka <morioka> | ||||||
| Component: | gvfs | Assignee: | Ondrej Holy <oholy> | ||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 18 | CC: | alexl, bnocera, dan.mashal, fedora, oholy, rdieter, stefano | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2014-02-05 23:11:30 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
|
Description
Kazutoshi Morioka
2013-06-10 08:31:25 UTC
I can confirm this with 1.6.1-4.fc18. Can post which version was working for you? Also a complete yum log would be fine. Do 'yum history', than 'yum history info <id>' from the update, and load up a attachment. Created attachment 759230 [details]
This is my recent yum history output
With my memory, mate-file-manager-1.5.5-1.fc18.x86_64 worked for me.
Created attachment 759231 [details]
And this is /var/log/yum.log
Sorry, but I confirmed that downgrade to the 1.5.1-1.fc18 don't fix this problem. And I found downgrade gvfs to the 1.14.2-3.fc18 fix this problem. I think this is a gvfs issue, not a mate-file-manager issue. This is tested matrix. gvfs version | mate-file-manager | result 1.14.2-4.fc18 | 1.6.1-4.fc18 | NG 1.14.2-4.fc18 | 1.5.1-1.fc18 | NG 1.14.2-3.fc18 | 1.6.1-4.fc18 | OK 1.14.2-3.fc18 | 1.5.1-1.fc18 | OK Thank you! i get same good results with 1.14.2-4.fc18. Fedora 19 has similar problem. Emblems can't be set nor clear. Should I file a separate bug report? (In reply to Kazutoshi Morioka from comment #6) > Fedora 19 has similar problem. Emblems can't be set nor clear. Should I file > a separate bug report? Yes this might be helpful. It seems that Fedora 19 has already fixed problem about emblems. Last night I tested Fedora 19 with latest gvfs and mate-file-manager and emblems are worked smoothly. Yes there were some dbus issues as well. I'll leave this open for a bit. Dan, the issue is cause by adding patches from gvfs-1.17 to f18 version. All is writen in changelogs. I believe https://bugzilla.redhat.com/show_bug.cgi?id=975521 may or may not be related as well. This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |