Sigil 2.7.0 crashes

[RbnJrg]

I don't know why, but lately I've had to restart Sigil three or more times under Arch Linux because the program crashes as soon as it starts. I ran it through a console and the message I get is:

Warning: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: Connection already associated with an application ID")

What surprises me is that I don't have any applications installed via Flatpak. What could be causing Sigil 2.7.0 to crash?

[KevinH]

DBus is not just associated with Flatpak. It is used to read desktop theme changes as well.

Arch is probably using Qt 6.10.x or later.

I recommend trying our AppImage for Linux (from our Releases page) and not the distribution based build. Does it exhibit the same errors?

If not, then the problem is most likely due to Qt issues.

You could try to enable core dumps and debug the post crash coredump with gdb to generate a backtrace, or even start Sigil, then attach to it with gdb and generate a backtrace that way if Sigil does not crash immediately.

Hopefully a gdb backtrace will provide some hints as to the cause. I regularly run Sigil 2.7.0 on Manjaro with no crashes or issues.

Also you might have somehow corrupted your ini settings files? Try creating a new user on your Linux box and logging in as them and and running Sigil from there to see if it crashes immediately (a new user would start Sigil with clean default settings ini files).

One other question ... Has Sigil 2.7.0 always crashed on startup on your Arch Linux system, or is this just started recently?

Please let us know what you find out.

[DiapDealer]

I doubt that particular warning is actually related to your crash.

I'm not experiencing any crashes with Sigil 2.7.0 and Qt6.10 on Arch Linux. I don't use the repository version however. I compile it myself.

If you recently updated your system, have tried rebooting (or at least logging out and back in)?

[RbnJrg]

I debugged Sigil with gdb and received the following message:

Starting program: /usr/lib/sigil/sigil
/usr/lib/sigil/sigil: error while loading shared libraries: libsigilgumbo.so: cannot open shared object file: No such file or directory

Apparently, the inability to find this library is causing Sigil to abort. I'm going to reinstall the program to see if that solves the problem.

EDIT: By the way, in /usr/lib/sigil/, both files are in that location: sigil and libsigilgumbo.so, so I should conclude that the last one must be corrupted.

[DiapDealer]

If you're starting Sigil directly using /usr/lib/sigil/sigil, you'll need to manually set the variables that are set in the launch script /usr/bin/sigil. Otherwise, as you found out, it won't be able to find libsigilgumbo. Nothing is corrupted. The launch script prepends /usr/lib/sigil/ to LD_LIBRARY_PATH. Binaries in Linux don't automagically find/load shared libraries just because they're in the same directory.

[DiapDealer]

For the purposes of using gdb, just export the new LD_LIBRARY_PATH in the terminal before launching gdb with /usr/lib/sigil/sigil by entering:

export LD_LIBRARY_PATH=/usr/lib/sigil:$LD_LIBRARY_PATH

Then launch /usr/lib/sigil/sigil with gdb. You only need to export that one time per terminal session.

[RbnJrg]

Originally Posted by DiapDealer

If you're starting Sigil directly using /usr/lib/sigil/sigil, you'll need to manually set the variables that are set in the launch script /usr/bin/sigil. Otherwise, as you found out, it won't be able to find libsigilgumbo. Nothing is corrupted. The launch script prepends /usr/lib/sigil/ to LD_LIBRARY_PATH. Binaries in Linux don't automagically find/load shared libraries just because they're in the same directory.

Indeed! After changing the script /usr/bin/sigil with the following:

SIGIL_LIB_DIR="/usr/lib/sigil"

export LD_LIBRARY_PATH="$SIGIL_LIB_DIR${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH}"

export SIGIL_SHARE_PREFIX="/usr"

exec /usr/lib/sigil/sigil "$@"

did the trick! What surprises me is that with previous versions of Sigil, the program worked fine without needing to change the script.

[DiapDealer]

Hmmm... All of those variables should have been properly set in the launch script already. Perhaps your script is what got damaged.

What was in /usr/bin/sigil before you edited it?

[RbnJrg]

Originally Posted by DiapDealer

Hmmm... All of those variables should have been properly set in the launch script already. Perhaps your script is what got damaged.

What was in /usr/bin/sigil before you edited it?

The following:

#!/bin/sh

# Entry point for Sigil on Unix systems.
# Adds linked Qt's lib directory to the LD_LIBRARY_PATH

QTLIB_DIR="/usr/lib"
SIGIL_BIN_DIR="/usr/lib/sigil"

if [ -z "$LD_LIBRARY_PATH" ]; then
  LD_LIBRARY_PATH="$SIGIL_BIN_DIR:$QTLIB_DIR"
else
  LD_LIBRARY_PATH="$SIGIL_BIN_DIR:$QTLIB_DIR:$LD_LIBRARY_PATH"
fi

# Create an environment var for the Sigil share directory location.
if [ -z "$SIGIL_SHARE_PREFIX" ]; then
  SIGIL_SHARE_PREFIX="/usr"
  export SIGIL_SHARE_PREFIX
fi

# Not really needed anymore but left in for fringe cases
if [ -z "$SIGIL_EXTRA_ROOT" ]; then
  SIGIL_EXTRA_ROOT="/usr/share/sigil"
  export SIGIL_EXTRA_ROOT
fi

export LD_LIBRARY_PATH

exec /usr/lib/sigil/sigil "$@"
#!/bin/sh

But after restarting the system, the fix didn't work anymore. So I asked Gemini what can be wrong and told me to create a file named sigil.conf in /etc/ld.so.conf.d/ with the following content:

/usr/lib/sigil

and so far, all is working (even after restarting the system).

[DiapDealer]

The script is correct already (except for the extra #!/bin/sh line at the very end). If you exclusively use the launch script to start Sigil (and never the binary in /usr/lib/sigil) it should work. It works for everyone one else using the distro version of Sigil (without an ld.so.conf.d entry).

Are you perhaps using a shortcut to launch Sigil that points directly to the binary in /usr/lib/sigil instead of the launch script in /usr/bin? Sigil should never be launched with anything other than the script in /usr/bin under normal circumstances.

[KevinH]

Maybe the menu or gui to launch sigil is pointing to the wrong place and skipping the script?

[DiapDealer]

If Sigil can't find the libsigilgumbo shared library, it's a dead giveaway that the launch script is 1) misconfigured; or 2) not being processed (skipped). A reboot should have no effect whatsoever on a properly configured launch script that is correctly (and consistently) being used to start Sigil.

[RbnJrg]

Originally Posted by DiapDealer

If Sigil can't find the libsigilgumbo shared library, it's a dead giveaway that the launch script is 1) misconfigured; or 2) not being processed (skipped). A reboot should have no effect whatsoever on a properly configured launch script that is correctly (and consistently) being used to start Sigil.

For some time now I have been using the following launcher without issues (until this problem where the library is not found):

[Desktop Entry]
Type=Application
Name=Sigil
Comment=ePUB file editor
TryExec=sigil
Exec=env QT_QUICK_BACKEND=software sigil %F
Icon=sigil
Categories=Office;
MimeType=application/epub+zip;
Path=
Terminal=false
StartupNotify=true

[DiapDealer]

When you type "which sigil" (no quotes) at a terminal, what are the results?

Also, can you verify that the last line of /usr/bin/sigil is really #!/bin/sh (as indicated in your previous post)? If it is, please remove that line. It's not part of the original. I would hope it would be interpreted as a comment, but I'm not entirely sure.

[RbnJrg]

Originally Posted by DiapDealer

When you type "which sigil" (no quotes) at a terminal, what are the results?

/usr/bin/sigil

Also, can you verify that the last line of /usr/bin/sigil is really #!/bin/sh (as indicated in your previous post)? If it is, please remove that line. It's not part of the original. I would hope it would be interpreted as a comment, but I'm not entirely sure.

The /usr/bin/sigil I'm using now is:

SIGIL_LIB_DIR="/usr/lib/sigil"

export LD_LIBRARY_PATH="$SIGIL_LIB_DIR${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH}"

export SIGIL_SHARE_PREFIX="/usr"

exec /usr/lib/sigil/sigil "$@"

The code I posted was to answer your question:

What was in /usr/bin/sigil before you edited it?

With that code (and also with the above one) Sigil crashed. But after writing /etc/ld.so.conf.d/sigil.conf (with the comand /usr/lib/sigil) all is working fine. I don't know why Sigil couldn't find the .so file.