-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problems with Darkest Dark (DevStyle) plugin #16
Comments
I still don't understand why this problem happened, however it disappeared once my flatpak package was upgraded from Eclipse 2020-06 to 2020-09 and I followed the migration procedure to reinstall all plugins (including DevStyle). |
Hi @mauromol, could you please point me to the plugins migration procedure you are mentioning please? |
@HL72 after the flatpak package was (automatically) upgraded from 2020-06 to 2020-09, Eclipse was not starting any more, due to #12 . Then I had to start the Eclipse flatpak by adding -clean command line option: in this way Eclipse started again. As soon as it started for the first time (perhaps after choosing a workspace, I can't remember exactly) a migration wizard I had never seen before shown up and asked me to upgrade the installed plugins. This procedure is not perfect because it seems like it uses a mixture of old and new update sites, but in some way it worked for the built in plugins (I probably just had to remove some of my third-party plugins and then reinstall them later on from the correct new update site). If I remember well, DevStyle was one of the plugins that was automatically upgraded in this way (or perhaps it did not require any update at all). This said, after my flatpak installation of Eclipse 2020-09 was back working, I never saw this exception any more... almost. I mean, I'm not sure the upgrade was indeed the complete solution, because I still have an old workspace that keeps on showing this problem even when I open Eclipse 2020-09 on it, but all the other old workspaces I was using don't exhibit this problem any more. I really don't know what is going on here, probably a race condition? The Resource plugin is indeed present in the flatpak package, so I don't understand why that exception pops up. I may suggest you to try to rebuild your workspace from scratch (by opening Eclipse on an empty workspace folder and then import back your projects there), perhaps you will fix this problem. I also opened a report to DevStyle developers at https://www.genuitec.com/forums/topic/exception-thrown-whenever-eclipse-starts-when-using-eclipse-flatpak-distribution/ but it was not fruitful so far, so maybe you can participate to the discussion there too. |
@HL72 @mauromol FWIW, the Spectrum theme plug-in is a pretty decent successor to Darkest Dark theme plug-in: https://marketplace.eclipse.org/content/eclipse-spectrum-dark-theme It might be worth checking out. |
Same problem on STS 4.8 and STS 4.9 in various laptops |
I installed Eclipse 2020-06 flatpak and, after installing Genuitec's DevStyle plugin to get the Darkest Dark theme, I have this error on Eclipse start, which also pops up as an error dialog:
If I look at the whole error log, this error is preceded by many instances of this:
Apart from this, the theme and the other DevStyle features seems to work fine, although I don't know the consequences of the above errors.
Any idea on what is going on? Is this something that you can fix on your side or something that Genuitec should try to fix on their side? I may try to contact them but some context would be useful.
The text was updated successfully, but these errors were encountered: