Bug 827685
| Summary: | MercurialEclipsePlugin gives org.eclipse.swt.SWTError Invalid thread access with eclipse 4.2 (Juno) | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Thomas Meyer <thomas.mey> |
| Component: | eclipse-mercurial | Assignee: | Severin Gehwolf <sgehwolf> |
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 17 | CC: | mziaei, patrickm, sgehwolf |
| 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: | 2013-07-08 21:19:56 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: | |||
|
Description
Thomas Meyer
2012-06-02 09:23:46 UTC
The problem is caused by Mercurial not obeying Eclipse rules. In Eclipse, there is only UI thread, and only from that's thread it is possible to access UI elements. In this case, we have a generic background thread (Worker) trying to access the UI bits (getImageRegistry). I'm rather suprised that it worked earlier, but maybe the registry was initialized in the UI thread, and the read-only access from the non-UI thread was allowed. This should be reported upstream. current fedora version is: Name : eclipse-mercurial Architektur : noarch Version : 1.8.2 Ausgabe : 1.fc16 Größe : 1.3 M Repo : fedora Zusammenfassung : Eclipse Mercurial plugin URL : http://javaforge.com/project/HGE Lizenz : EPL Beschreibung : Eclipse plugins to interact with Mercurial Repositories. Latest version provided by http://javaforge.com/project/HGE is 1.9.1. Version 1.9.1 of the plug-in works correctly with eclipse-rcp-4.2.0 Is it possible to update the version delivered with fedora to 1.9.1? I'll look into updating this. Upstream bug is: http://javaforge.com/issue/52552 This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 '17'. 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 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 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 17'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. closed as nobody cares. I'm using the upstream version of eclipse now, which works for me. |