how to fix "Could not find the Mozilla runtime." startup error problem issue

General project discussion.
Use this as a last resort if your topic does not fit in any of the other boards but it still on-topic.
Forum rules
This General Discussion board is meant for topics that are still relevant to Pale Moon, web browsers, browser tech, UXP applications, and related, but don't have a more fitting board available.

Please stick to the relevance of this forum here, which focuses on everything around the Pale Moon project and its user community. "Random" subjects don't belong here, and should be posted in the Off-Topic board.
User avatar
Palea
Newbie
Newbie
Posts: 4
Joined: 2023-04-17, 11:32

how to fix "Could not find the Mozilla runtime." startup error problem issue

Unread post by Palea » 2023-04-20, 10:20

Hello,

PaleMoonHackerz: strange thing: when starting palemoon via mozo created entry in the MATE Desktop menu "it just works" :D

but when linking to it via
ln -sv /home/user/software/browser/palemoon/palemoon /usr/bin/pale

which would allow starting it via Alt+F2 and typing "pale" + ENTER

which is often much faster than the mouze

but results in: "Could not find the Mozilla runtime."

Searching the forum it says "needs to be accessible as a file" and build a wrapper, so tried a bunch of stuff.

what ultimately WORKED was:

1. instead of linking directly to the palemoon-bin
2. create a script /usr/bin/pale with the following content:

Code: Select all

#!/bin/bash
/home/user/software/browser/palemoon/palemoon https://callthissiteforstartup.com
3. mark it runnable chmod +x pale

4. now running it like opening up a new non-root terminal and typing pale works just fine :D also Alt+F2 startup no problem :D

so the "trick" was to pass it an argument :D and it stopped complaining.

CHEEERS! :D :thumbup:

PS: for completeness the mozo created pale.desktop has the following content:

Code: Select all

cat pale.desktop 
#!/usr/bin/env xdg-open
[Desktop Entry]
Version=1.0
Type=Application
Terminal=false
Icon=/home/user/software/browser/palemoon/browser/chrome/icons/default/default48.png
Icon[en_US]=/home/user/software/browser/palemoon/browser/chrome/icons/default/default48.png
Exec=/home/user/software/browser/palemoon/palemoon
Name[en_US]=pale
Name=pale
and starts like a charm :D

User avatar
Moonchild
Pale Moon guru
Pale Moon guru
Posts: 35474
Joined: 2011-08-28, 17:27
Location: Motala, SE
Contact:

Re: how to fix "Could not find the Mozilla runtime." startup error problem issue

Unread post by Moonchild » 2023-04-20, 10:29

Totally predictable though; that's the problem with making symbolic links to binaries that need runtime libraries in the linked-to directory. a symbolic link will NOT give access to those from the binary launched.
Symbolic links can be a powerful tool but you should know when you can (and cannot) use them.
"Sometimes, the best way to get what you want is to be a good person." -- Louis Rossmann
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite

User avatar
Palea
Newbie
Newbie
Posts: 4
Joined: 2023-04-17, 11:32

Re: how to fix "Could not find the Mozilla runtime." startup error problem issue

Unread post by Palea » 2023-04-21, 10:35

now to get to lightning fast 3-letter startup the user can do: (allowing to start the very-often-used-program with Alt+F2 typing "pal" + ENTER)

Code: Select all

ln -sv /usr/bin/pale /usr/bin/pal
CHEERS & keep up good health, spirit, mood + Open Source as long as possible :D

Locked