-
Notifications
You must be signed in to change notification settings - Fork 3
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
Scripting plugin from Sebastian Richter generate errors #21
Comments
It took me weeks to find out the reason for this error, so here is the error message that is generated that others may find it without having to know in advance that the Flatpak version of jameica is the culprit:
You may find the complete message log of Hibiscus in Sebastian's forum: https://scripting-forum.derrichter.de/viewtopic.php?f=34&t=1138#p7677 Edit: While my skills are not good enough to help solving the issue, I will be happy to support when it comes to testing if that helps. |
Full log for reference:
|
Related code change: 0a2ecf2 |
Webkitgtk seems to be removed in gnome-platform 43 (compare https://gitlab.gnome.org/GNOME/gnome-build-meta/-/tree/gnome-42/files to https://gitlab.gnome.org/GNOME/gnome-build-meta/-/tree/gnome-43/files). Rolling back to gnome-platform 42 should fix the issue for now. |
Thanks a lot for preparing a fix! I tried to install the test build noted in the issue to test it but got:
Am I missing something? |
Regarding webkitgtk I'm maybe on the wrong track since the missing folder mentioned in the comment above is only about some build patches. Nevertheless I'm going to merge the rollback to gnome platform 42 so we can narrow the source of the issue. If the issue persists after the rollback it has to be related to the dbus access changes and we have to dig deeper a bit. |
@Braintoe Please check once the build has been published to flathub. |
Good news: Flathub just offered me the new build - and the scripting plugin works again with it. @tobias-hammerschmidt Thank you! :-) The only error I still get (after sync is completed) is:
This tells me the Mashup script fails to kill the headless chromium browser which might be a security risk. But I do not know (yet) if this is caused by Flathub or if I should contact Sebastian Richter about this. |
I think the mentioned remaining issue is caused by the flathub sandbox which most likely doesn't include the killall command. I don't know how the scripting plugin is implemented - maybe there is an alternative method for cleaning up the started processes? |
Since the last update of the flatpak, where we removed system access to d-bus, the scripting plugin from Sebastian Richter works no longer. The rest of the application, including HBCI transfers in Hibiscus work fine.
It seems that the underlying Eclipse framework has no access to requested functions of the headless browser, so it is not able to log in to the websites.
The text was updated successfully, but these errors were encountered: