Login
You're viewing the functional.cafe public feed.
  • Nov 12, 2026, 10:04 PM

    @novelwriter
    Sorry, I can't log a proper bug report because I'm no longer on GitHub, but the latest version on flatpack has stopped working on Fedora.
    Something to do with Python. Refuses to open altogether. Attached crash report which I can't send.
    I've managed to get round by using the AppImage, but that has weird spell check which doesn't like apostrophe'd words like it's. Probably something to do with the apostrophe because if you use its correction its happy.

    Image of NovelWriter where spell check doesn't like the word "let's" and "we'll".
    A crash log of NovelWriter. Its a load of Python code, which incant understand.
    The rest of the error log from a crashed NovelWriter.
    💬 1🔄 0⭐ 1

Replies

  • 💬 2🔄 0⭐ 0
  • Nov 14, 2026, 12:07 PM

    @DodoTheDev Ok, so the crash is on the Qt side and is likely a Qt bug, but the code in novelWriter that triggers it is related to the current line highlight. You can try to turn that off, and I will see if I can avoid triggering this issue from novelWriter in 26.2.3.

    💬 1🔄 0⭐ 0
  • Nov 14, 2026, 12:34 PM

    @veronica
    Ah, in that case sorry for bothering you but thank you do much for letting me know.

    Unfortunately, I can't turn off the setting as it won't even launch the app to let me change the settings.

    💬 1🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0
  • 💬 2🔄 0⭐ 0
  • Nov 14, 2026, 12:36 PM

    @DodoTheDev Ok, just needed to check if it was a Wayland issue. The crash is in Qt, not novelWriter, as mentioned. Do you have "highlight current line" enabled? If you turn it off, does that help? You'd need to edit the config file inside the flatpak's user config folder. It should be:

    ~/.var/app/io.novelwriter.novelwriter/config/noverlwriter.toml

    The setting is lineHighlight

    💬 1🔄 0⭐ 0
  • 💬 1🔄 0⭐ 0
  • Nov 14, 2026, 12:49 PM

    @DodoTheDev Much appreciated 😊

    I'm redesigning the line highlight to draw on the underlying frame instead of via the text layout, which is where the crash happens. There's a tiny overhead when doing this, but I think it's worth it here.

    I'm planning to release 26.2.3 later today, so you can hopefully turn on the highlight feature after that. At least for testing that the fix works, which would be helpful too.

    💬 1🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0
  • Nov 14, 2026, 12:40 PM

    @DodoTheDev And the screenshot indicates that it wasn't even able to run without Wayland, so it doesn't rule out if this is Wayland-related. In any case, the whole code path in Qt that is crashing here is best avoided, so I'm working on a way to get around the problem.

    💬 0🔄 0⭐ 0
  • Nov 14, 2026, 12:52 PM

    @DodoTheDev As for the dictionary issue, this is handled by the actual underlying dictionaries loaded from your system, not novelWriter, but it may be worth patching in novelWriter too. I'll look into it.

    Not sure why it behaves differently with AppImage than Flatpak. It may be loading different dictionaries. Flatpak images are very sandboxed, and I don't think the Flatpak actually reads system dictionaries. I'll have to look into that.

    The Flatpak release is still experimental.

    💬 0🔄 0⭐ 0