Sigil on Linux

[eschwartz]

The interesting thing is that Qt5 can actually be built statically (linking in qt plugins is weird though) but sadly not supported for webengine.

It would be a neat thought to be able to ship one exe file plus the sharedir... Sadly not to be...

[Camelot]

I am running Debian/unstable and must note that the “current” Sigil 1.4.3 causes a crash on startup.
Terminal;

Warning: WebEngineContext used before QtWebEngine::initialize() or OpenGL context creation failed.
Warning: QGLXContext: Failed to create dummy context

Error dialogue from Sigil:

Error info: Fatal: Failed to create OpenGL context for format QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize 24, redBufferSize -1, greenBufferSize -1, blueBufferSize -1, alphaBufferSize -1, stencilBufferSize 8, samples 0, swapBehavior QSurfaceFormat::DefaultSwapBehavior, swapInterval 1, colorSpace QSurfaceFormat::DefaultColorSpace, profile  QSurfaceFormat::NoProfile) 
Sigil version: 1.4.3
Runtime Qt: 5.15.2
Compiled Qt: 5.15.1
System: Debian GNU/Linux 11 (bullseye)
Architecture: x86_64

Edit: Resolved
Today there was a update from nvidia driver and i did not reboot. After reboot Sigil works again. Sorry…

[DiapDealer]

Is that the Debian unstable Sigil package, or did you compile Sigil yourself? If the former, you should check with the package maintainer. He's always been pretty accessible in the past.

The last time I saw that error on Linux (that prevented Sigil from launching), I actually had to "Pull a Windows" and shut down and reboot. I think my video driver kernel modules had updated at the same time Sigil had, or some such.

[Camelot]

The package is from the Debian repository.

[DiapDealer]

I've got a Debian Stable virtual machine that seems to install/run the 1.4.3 sigil package from buster-backports just fine. Might be a video driver issue. Did you try the reboot? I know that's foreign to linux users, but...

[Camelot]

Yes, I rebooted (was really strange to me), see my edit in my first posting. Sigil worked fine after restart.

[DiapDealer]

Originally Posted by Camelot

Yes, I rebooted (was really strange to me), see my edit in my first posting. Sigil worked fine after restart.

Gotcha... I missed the update to the post. Thanks for the update. Same thing happened to me on Arch with new nvidia drivers and Sigil. That's why I mentioned it. And yes... I always feel a little dirty and suggesting that Linux users should shut down and reboot!

But not knowing people's personal skill levels: telling someone to reboot is much easier than walking a neophyte through manually unloading/loading kernel modules.

[eschwartz]

Rebooting is the only way to take advantage of improvements that are provided as kernel updates. It's perfectly reasonable to reboot sometimes to fix certain problems.

Windows is annoying because "did you try rebooting" is somehow supposed to be a solution to everything, from kernel updates to general windows userland updates, to "a program I installed says I have to reboot before I can use it", to "your computer is slow today, maybe you went too long without rebooting".

Compared to all that, "just reboot whenever the kernel or video drivers are updated" is a relief for how rare it is. Any other program can be reloaded by just... restarting the program or at *worst* logging out then back in which takes much less time than rebooting.