-
Notifications
You must be signed in to change notification settings - Fork 270
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
Markdown preview shows nothing #1302
Comments
I am not saying it is the reason, but it is certainly possible. Markdown preview uses webkit2gtk which uses a lot of the G*1 infrastructure. By its nature that isn't a focus of a KDE distro, so its possible that there are interactions between the G* libraries and the KDE display server. Are you using a Wayland or X11 session? Footnotes
|
Thank you for the response.
Geany says, it's been compiled using GTK 3.24. Could this be a reason, there being no libwebkit2gtk version 3.something? |
The markdown plugin uses libwebkit2gtk 4.0 so that should be ok. Also 1.38 is two years old, if you can build Geany and plugins maybe try Geany 2.0 because I'm not sure when the plugin was switched to that version of libwebkit2gtk, but I suspect it might have been after 1.38. Edit: no it was changed to 4.0 6 years ago, my, doesn't time fly. |
I now have compiled geany from sources, however the Markdown plug-in doesn't appear to be included. Sorry, if the questions are very basic. Simply compiling the plug-ins made them appear next time I launched gedit. The markdown plugin is there, but still doesn't show anything.
If I lauch geany from the command line, I see some errors:
Any ideas what they could mean? |
Google says Just to confirm those messages are from markdown, first launch Geany from the command line with default configuration by Also you could see if the webhelper plugin has the same issues, it uses webkit2gtk as well. Footnotes
|
I opened geany
Yes, webhelper also produced those error messages.
|
Ok, that indeed looks like its the webkit2gtk bug. So you only need to wait for your distro to provide the fixed version. |
Until they fix webkit.
From wailsapp/wails#2977 (comment) Oct 13, 2023 |
Debian-based distros may not be so lucky until this RC bug is resolved: https://bugs.debian.org/1061406 Basically what @jbicha said already, but now the autoremoval clock is ticking for geany-plugins. |
The situation is summarised here, and the current status is:
As Geany-plugins is a collection, each plugin individually enables or disables based on availability of its dependencies during configure, so Debian should not have to do anything to have those plugins not build as above. It should be noted that those on LTS distros (like me) do not have Libsoup3 available, and therefore not Webkit 4.1, so we can't test #1295 or provide any other PRs, but I really doubt that all geany contributors are on LTS distros, so until "somebody" contributes the patches those plugins will not get distributed, and maybe that will trigger contributions. |
@elextr Which distro version are you using? If your distro doesn't have libsoup3, then it probably does not have a version of webkitgtk that gets security updates. :( For Ubuntu (click the diff link), I wrote a simple patch to switch Markdown to webkitgtk 4.1, added the proposed webhelper webkit 4.1 patch, and disabled the other 2 plugins. |
@jbicha Ubuntu says 20.04 LTS has standard support until April 2025, so users would expect security updates, but for webkit2gtk they may not come from upstream if its not supporting it anymore. Edit: although webkit2gtk 4.1 is API compatible with webkit2gtk 4.0, libsoup3 is not API compatible with libsoup2, so LTS precludes it replacing libsoup2 since it would require updating all dependent software, so that precludes wibkit2gtk 4.1 which uses libsoup3. |
Ubuntu 20.04 LTS no longer is supported by the webkitgtk project. Ubuntu Security also does not offer security support for webkitgtk for Ubuntu 20.04 LTS. |
I suggest adding a configure option for webkitgtk 4.0 / 4.1 defaulting to the 4.1 option. If 4.1 is selected, then it disables the plugins that are not supported yet. |
I wouldn't worry too much about the geany-plugins autoremoval warning in Debian. If the Maintainer does not act in time, I can do a non-maintainer upload to apply the same adjustments I did for Ubuntu. |
It would be better to make PRs here so its available to all distros, not just specific ones. As I said it needs somebody to test it who has libsoup3/webkit 4.1 and somebody who has the old version to check that still falls back if the distro does not have the newer versions. |
I have installed geany-1.38 and the markdown-plugin from Ubuntu-22.04's package repository.
The markdown preview does nothing, at first I thought there's some error with images or something. However, even the most trivial file produces no output.
On another computer, also running Ubuntu-22.04, I was using geany with markdown-preview regularly without any issues. The one major difference is that my current machine uses KDE, whereas the other one used Gnome; but this can't be the reason.
The screenshot below shows the file plus the preview along with the debug messages for good measure.
I see nothing that would give me some hints. The preview remains solidly grey.
Here are the debug messages as text
That's the template.html file, that the plug-in uses. I have done nothing to it.
The text was updated successfully, but these errors were encountered: