ghostwriter no longer runs on ubuntu noble

[Chris Guiver]

Ubuntu noble (desktop is LXQt; so Lubuntu if technical)

I've used ghostwriter on this box before, so expect it to run without issue... alas it no longer is

guiverc@d7050-next:~$ ghostwriter
Command "pandoc" is not available.
Command "multimarkdown" is not available.
Command "cmark" is not available.
Hspell: can't open /usr/share/hspell/hebrew.wgz.sizes.
kf.sonnet.clients.hspell: HSpellDict::HSpellDict: Init failed
[1103820:1103820:0112/100524.977724:FATAL:credentials.cc(125)] Check failed: . : Permission denied (13)
Trace/breakpoint trap (core dumped)

I've also on another Ubuntu noble box `sudo apt install ghostwriter` & get a similar failure on attempt to run.

Of note:

I also tried the snap version of ghostwriter (hoping to use in the meantime) and it's also failing; I've not tried the snap before so this may not be different. I've not reboot in a week (probably equal on my other box too)

guiverc@d7050-next:/de2900/lubuntu/testcases_2023/ubuntu-manual-tests/testcases/image$ uptime
 10:04:55 up 7 days, 23:23, 1 user, load average: 4.90, 2.05, 1.69

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: ghostwriter 23.08.4+ds-0ubuntu1
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: LXQt
Date: Sat Jan 13 10:01:32 2024
InstallationDate: Installed on 2023-08-29 (137 days ago)
InstallationMedia: Xubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230829)
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: ghostwriter
UpgradeStatus: No upgrade log present (probably fresh install)

[Sudip Mukherjee (sudipmuk)]

Thanks for reprorting the bug.

I can reproduce the issue and its being caused as its not having the permission to create a namespace.
apparmor needs to have a profile allowing the namespace.

[Sudip Mukherjee (sudipmuk)]

I have now tested with the attached profile and confirmed that ghostwriter works after the policy update.