Found this thread with the help of a friend after trying the pinned rdewalt method and Lutris. The other two install methods largely worked fine, but had a goofy bug where the main font selector was inoperable and sometimes crashed the program. Scrivenix resolved that issue, so thank you for your work on this project! Also, I am a Linux noob transitioning away from Windows as of this week, so if I say anything super ignorant, apologies.
Scrivenix install works on Nobara 43 (KDE Plasma desktop version) (Wayland)
1440p and 1080p monitors –somewhere around 144dpi seems okay, but still tweaking UI & physical desk setup for a new PC
Here’s some notes from the install process:
udisks2
udisks2 caused me a bunch of anxiety, since it changed the ID and Vendor fields inside the pop-up dialogs for drive mounting. Other new users to Linux that are relying heavily on GUI might have a similar panic attack, thinking their system’s security became compromised. It might be helpful to make a note about this in the install directions or in the installer itself.
Possible Bazaar flatpak manager compatibility issues
The Scrivenix install seems to temporarily or irregularly break Bazaar, which is my OS’s suggested flatpak manager. On open, the program hangs for a litle bit, then closes. What little debugging I could figure out seemed to point to a bwrap issue. Here’s the few lines before the app closes:
F: Running '/usr/bin/bwrap --args 72 -- /usr/bin/xdg-dbus-proxy --args=75'
F: Running '/usr/bin/bwrap --args 72 -- bazaar '%U''
Failed to register: Timeout was reached
A PC restart found Bazaar back to normal & functioning, with Scrivenix listed in the GUI. Bazaar also seemed to properly notify me of necessary updates and handled them without error. However, the next time I tried to open Bazaar, it exhibited the same crash. (I didn’t debug, sorry!) I don’t have enough data yet to say if Scrivenix is causing this to happen, or if something else is the culprit. To note, I’ve also been having some (harmless?) bwrap issues with Steam that I haven’t gotten around to troubleshooting–unsure if related. If I had to hazard an ignorant guess, perhaps the manual install of a flatpak isn’t playing nice with how Bazaar likes to keep track of its installs, related files, and/or folders?
Accidental launch of multiple instances of Scrivenix
Accidentally launching a 2nd instance of Scrivenix causes it to lock up badly enough that both the processes and the window have to be terminated manually; the window, in particular, must be killed, even after the processes have ended. GUI prompts asking to terminate the window do absolutely nothing.
cabextract
Nobara comes with 1.11 already installed. Scrivenix installation failed as follows:
flatpak-builder --force-clean --install --user build-dir com.local.Scrivenix.yml
Downloading sources
Downloading https://www.cabextract.org.uk/cabextract-1.11.tar.gz
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
Failed to download sources: module cabextract: The requested URL returned error: 403
Commenting out the cabextract section of the .yml allowed the installation to proceed. My troubleshooting friend, on ubuntu, also had the module installed on his system–so many future users might be affected by this. Could a version check & bypass be added for this step? (And, perhaps any other modules that an OS might already have installed?)
Fonts
Scrivener’s default UI fonts aren’t part of the Scrivenix install for me. Not sure if that’s intentional, or if my particular install failed in some way. As such, the entire UI defaults to Arial, which displays very poorly on my system–especially if the DPI is set too high or too low, or OS sub-pixel rendering is off. This is pretty rough to deal with during initial install, DPI tweaking, test-opening important projects, etc….
My OS had sub-pixel rendering OFF by default. Suggest telling the user to change that setting in their OS before starting the install. This should help visibility during the install and post-install configuration processes. My OS also features “hinting” options for fonts, set to “slight” by default. I barely notice a difference between the options at normal font sizes, but any users with this feature might want to play with it to see if it helps them.
Question: I’ve got a custom font I’d like to use if at all possible. Can this be done without breaking things? If so, what’s the process? (It’s already installed on my OS, but those fonts are not showing up in Scrivenix by default.)
That’s all I’ve got! Hope the text wall is useful in some way. Thanks again for the awesome work (and for inadvertently leveling my Linux knowledge up! ;P)