View Single Post
Old 12-23-2025, 10:27 AM   #37
RbnJrg
Wizard
RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.
 
Posts: 1,930
Karma: 9600001
Join Date: Mar 2013
Location: Rosario - Santa Fe - Argentina
Device: Kindle 4 NT
Quote:
Originally Posted by DiapDealer View Post
Try one more thing for me:

Put everything back to a stock install (including your custom launcher with just sigil--not the full path).

Remove the empty "Path=" line from your custom desktop launcher. There's no reason for it to be there if it's empty.

See if that makes a difference.
I did what you asked me and with the following launcher:

Code:
[Desktop Entry]
Type=Application
Name=Sigil
Comment=ePUB file editor
TryExec=sigil
Exec=sigil %F
Icon=sigil
Categories=Office;
MimeType=application/epub+zip;
Path=
Terminal=false
StartupNotify=true
Sigil crashed I've been using the same launcher (not the one I posted above, but the one I posted before) since several previous versions of Sigil (ever since I discovered that Sigil works better without hardware acceleration) and I've never had any problems until now. I honestly don't know what could be happening.

EDIT: If I change:

Code:
Exec=sigil %F
with:

Code:
Exec=/usr/bin/sigil %F
Sigil starts fine.

Last edited by RbnJrg; 12-23-2025 at 10:30 AM.
RbnJrg is offline   Reply With Quote