05-01-2026, 10:54 AM
|
#31 |
|
Sigil Developer
  Posts: 9,669
Karma: 6774048
Join Date: Nov 2009
Device: many
|
I still think it may be related to AppArmor. See this link:
https://askubuntu.com/questions/1511...eation-restric It seems to impact many AppImages, all Electron Apps, and many other apps. So many that some distributions like Linux mint are reverting the AppArmor kernel changes. Last edited by KevinH; 05-01-2026 at 11:04 AM. |
|
|
|
05-01-2026, 11:00 AM
|
#32 |
|
Sigil Developer
Posts: 9,669
Karma: 6774048
Join Date: Nov 2009
Device: many
|
Perhaps checking the system log for apparmor related denied message would tell us if AppArmor was the problem?
Try starting up Sigil and right after it fails do: sudo journalctl -k | grep -i "apparmor.*DENIED" | tail -n 20 That should tell us if AppArmor is the issue. |
|
|
|
|
05-01-2026, 11:06 AM
|
#33 |
|
Grand Sorcerer
Posts: 29,458
Karma: 212177022
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
|
It may be involved, but why would our app start working fine with just a couple of QT envars being set? The unprivileged usernamespace restriction doesn't seem to be fatal for us in that regard.
I guess we could find out for sure by creating the apparmor profile that exempts the Sigil AppImage and then try to launch the AppImage with no other env vars set. |
|
|
|
|
05-01-2026, 11:47 AM
|
#34 |
|
Sigil Developer
Posts: 9,669
Karma: 6774048
Join Date: Nov 2009
Device: many
|
I do not know exactly what changes a software back end or disabling gpu does to how QtWebEngine works? All I know is that according to that post AppArmor does stop many AppImages and all Electron apps and even native apps with no profile.
But it would be nice to see proof it is not involved (ie no apparmor denied system kernel log messages) so we can rule it out. But you are right, graphic drivers are most probably the issue since it is the mesa libgallium driver that is calling out into the weeds that is causing the segfault consistently in all back traces. |
|
|
|
|
05-01-2026, 11:55 AM
|
#35 | |
|
Addict
Posts: 362
Karma: 518
Join Date: Nov 2015
Location: Europe EEC
Device: Kindle Fire HD6 & HD8
|
Quote:
It looks like the sandbox is responsible for the long initial startup time. Not a major problem, but I'll look into the link you provided in your following post. I have the following vulkan packages installed: libvulkan-dev mesa-vulkan-drivers vulkan-tools vulkan-tools is described as 'miscellaneous vulkan utilities' vulkan-utils is not listed as an available package, but there is a package 'vulkan-utility-libraries-dev', although not installed. lspci -k | grep -i VGA gives the following result: Code:
01:00.0 VGA compatible controller: NVIDIA Corporation GK208B [GeForce GT 710] (rev a1) |
|
|
|
|
|
05-01-2026, 12:33 PM
|
#36 | |
|
Addict
Posts: 362
Karma: 518
Join Date: Nov 2015
Location: Europe EEC
Device: Kindle Fire HD6 & HD8
|
Quote:
Spoiler:
|
|
|
|
|
|
05-01-2026, 01:10 PM
|
#37 |
|
Grand Sorcerer
Posts: 29,458
Karma: 212177022
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
|
See if putting back the env vars that allow the AppImage to run without crashing changes the output of that sudo journalctl -k | grep -i "apparmor.*DENIED" | tail -n 20 command.
Particularly the fusermount3 entries and the one unprivileged_userns related to sigil. |
|
|
|
|
05-01-2026, 01:14 PM
|
#38 |
|
Sigil Developer
Posts: 9,669
Karma: 6774048
Join Date: Nov 2009
Device: many
|
Hmm .. looking at what gets denied right at the end I see:
Code:
May 01 18:20:44 Osiris kernel: audit: type=1400 audit(1777652444.040:426): apparmor="DENIED" operation="capable" class="cap" profile="fusermount3" pid=17396 comm="fusermount3" capability=1 capname="dac_override" May 01 18:20:44 Osiris kernel: audit: type=1400 audit(1777652444.040:427): apparmor="DENIED" operation="capable" class="cap" profile="fusermount3" pid=17396 comm="fusermount3" capability=7 capname="setuid" May 01 18:20:44 Osiris kernel: audit: type=1400 audit(1777652444.040:428): apparmor="DENIED" operation="capable" class="cap" profile="fusermount3" pid=17397 comm="fusermount3" capability=7 capname="setuid" Code:
May 01 18:20:49 Osiris kernel: audit: type=1400 audit(1777652449.340:430): apparmor="DENIED" operation="capable" class="cap" profile="unprivileged_userns" pid=17416 comm="sigil" capability=21 capname="sys_admin" Code:
May 01 18:21:00 Osiris kernel: audit: type=1400 audit(1777652460.148:431): apparmor="DENIED" operation="capable" class="cap" profile="fusermount3" pid=17496 comm="fusermount3" capability=1 capname="dac_override" May 01 18:21:00 Osiris kernel: audit: type=1400 audit(1777652460.148:432): apparmor="DENIED" operation="capable" class="cap" profile="fusermount3" pid=17496 comm="fusermount3" capability=7 capname="setuid" May 01 18:21:00 Osiris kernel: audit: type=1400 audit(1777652460.148:433): apparmor="DENIED" operation="capable" class="cap" profile="fusermount3" pid=17497 comm="fusermount3" capability=7 capname="setuid" So ubuntu's AppArmor is most definitely part of the problem. But DiapDealer is right, with the working env vars set, if these message still appear, then what are they doing? Are they just warnings then? Last edited by KevinH; 05-01-2026 at 01:50 PM. |
|
|
|
|
05-01-2026, 02:06 PM
|
#39 | |
|
Sigil Developer
Posts: 9,669
Karma: 6774048
Join Date: Nov 2009
Device: many
|
Update - it seems Ubuntu 's AppArmor can be set to different modes. One mode is called Complain Mode.
Quote:
So if these messages appear when env-vars.txt are set to make things work for Sigil, then AppArmor must be in Complain mode, and then the issue is most probably driver related as DiapDealer suspects. I know that nvidia cards have lots of issues with Qt WebEngine and Wayland. The issue may be really hard to track down. Last edited by KevinH; 05-01-2026 at 02:10 PM. |
|
|
|
|
|
05-01-2026, 02:13 PM
|
#40 | |
|
Addict
Posts: 362
Karma: 518
Join Date: Nov 2015
Location: Europe EEC
Device: Kindle Fire HD6 & HD8
|
Quote:
Spoiler:
|
|
|
|
|
|
05-01-2026, 02:20 PM
|
#41 |
|
Sigil Developer
Posts: 9,669
Karma: 6774048
Join Date: Nov 2009
Device: many
|
Yep, those denied messages are right there at the end and they did not prevent Sigil from working!
So AppArmor must be in Complain mode and not actually blocking/preventing anything. So DiapDealer is right this is a graphics card driver issue. Please try the following variation: lspci -k | grep -A 3 "VGA" one more time as it should show us exactly what kernel module driver is being used on its 3rd line. |
|
|
|
|
05-01-2026, 03:09 PM
|
#42 |
|
Grand Sorcerer
Posts: 29,458
Karma: 212177022
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
|
I tend to assume that the video driver (or hardware) is aging or insufficient whenever QtWebEngine's hardware acceleration needs to be disabled for Sigil to work on Linux or Windows. But this was all working out of the box before @philja had upgraded some hardware (and reinstalled the OS) if I'm reading things correctly.
So unless the graphics card was somehow downgraded, I would expect things to work as they did. Expecially since the version of Qt being used stayed the same--due to the AppImage being the same). One thing to try (after Kevin's requested output) since he has vulkan-tools installed is try the vkcube-wayland command (from a terminal). This should result in a window with a spinning cube. If it doesn't, the vulkaninfo command should print a list of supported features. Last edited by DiapDealer; 05-01-2026 at 03:18 PM. |
|
|
|
|
05-01-2026, 04:04 PM
|
#43 |
|
Sigil Developer
Posts: 9,669
Karma: 6774048
Join Date: Nov 2009
Device: many
|
On Manjaro the command is just vkcube. I tried it and it failed on my box until I figured out how to change kernel drivers (modules) from the older radeon driver to the newer amdgpu driver (with si_support=1) which required me to modify grub.cfg and rebuild it.
My Amd Radeon graphics card can be driven by both the older radeon driver and the newer amdgpu driver but only the newer amdgpu driver supported vulkan. Sigil still starts up in gbm mode via egl opengl just fine under wayland. So I will stick with it. export QT_LOGGING_RULES="qt.webenginecontext=true;qt.webe ngine.compositor=true" export QTWEBENGINE_CHROMIUM_FLAGS="--enable-logging" sigil Spoiler:
After a restart with the amdgpu driver, vkcube brought up a wonderfully fast spinning cube. Selected WSI platform: wayland Selected GPU 0: AMD Radeon HD 7800 Series (RADV PITCAIRN), type: DiscreteGpu Last edited by KevinH; 05-01-2026 at 04:07 PM. |
|
|
|
zone_platform_qt.cpp(218)] Failed to load keymap file, falling back to StubKeyboardLayoutEngine|
05-01-2026, 04:46 PM
|
#44 | |
|
Addict
Posts: 362
Karma: 518
Join Date: Nov 2015
Location: Europe EEC
Device: Kindle Fire HD6 & HD8
|
Quote:
Code:
$ lspci -k | grep -A 3 "VGA"
01:00.0 VGA compatible controller: NVIDIA Corporation GK208B [GeForce GT 710] (rev a1)
Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c93
Kernel driver in use: nouveau
Kernel modules: nvidiafb, nouveau, nova_core
|
|
|
|
|
|
05-01-2026, 04:50 PM
|
#45 | |
|
Addict
Posts: 362
Karma: 518
Join Date: Nov 2015
Location: Europe EEC
Device: Kindle Fire HD6 & HD8
|
Quote:
|
|
|
|
|
 |
«
Previous Thread
|
Next Thread
»
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Sigil 2.7.0 crashes | RbnJrg | Sigil | 39 | 12-23-2025 12:14 PM |
| Sigil 0.7.4 crashes | jiarevalo | Sigil | 3 | 12-06-2013 06:44 AM |
| Sigil 0.7.4 CRASHES all the time | JSWolf | Sigil | 6 | 11-01-2013 01:50 PM |
| Epub crashes on Sigil for Mac, OK on Sigil for PC | crystamichelle | Sigil | 6 | 08-14-2013 02:52 PM |
| sigil crashes? | bobcdy | Sigil | 7 | 03-05-2011 05:36 AM |
All times are GMT -4. The time now is 01:15 AM.