Linux Bibisco fails to start from KDE Application Menu if not set to start in terminal.

[bjwest]

Neither the .zip nor .deb packages of version 2.3.1 or 2.4.0 will start from the KDE Application Menu unless the 'run in a terminal' in the Advanced settings is checked. If run from a terminal or KRunner with the same path as is in the Menu, it runs just fine. This occurs with both the SE and CE versions after setting the bibisco file from the .zip package as executable.

Operating System: KDE neon 5.25 KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 Kernel Version: 5.13.0-35-generic (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 3800X 8-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX 5600 XT Product Name: X570 Steel Legend

[xahodo]

Works fine here.

I manually made my own menu entry, and put bibisco in my /home//bibisco/* . In the KDE menu editor, for the bibisco entry, I filled in the "Command" field in the "General" tab to point to executable, after that I filled in the "Work path" in the "Advanced" tab to point to the directory where the bibisco executable was located.

Perhaps try filling in the working path to point to where bibisco itself is located?

EDIT: I didn't need to set ¨Run in terminal" on bibisco.

Operating system: Solus 4.3 (well, it's a rolling release distro, but you get the gist) KDE plasma version: 5.25.3 KDE framework version: 5.96.0 Qt version: 5.15.5 Kernel version: 5.15.61-217.current (64-bit) Graphics platform: X11 Processor: 4xCore i5-6400 @ 2.70GHz Memory: 7.7GiB of RAM Product name: Aspire XC-780

[bjwest]

I manually entered the menu entry when I installed the .zip package, and the package manager made the entry when I installed the .deb package, however this seems to have been some kind of fluke or something, as it's working fine now.