Crew-Launcher: Cannot add Firefox using package name or .desktop file

[aghebert]

Tried to add firefox installed from chromebrew using crew-launcher; crew-launcher new firefox The browser pops up asking "add to launcher", which adds a firefox icon to the chromeOS launcher. However, when the launcher icon is clicked, firefox does not start.

So I tried to add firefox using the .desktop file, but it kept saying firefox is not installed.

Versions and system information

chromebrew: 1.17.5

ChromeOS: CHROMEOS_RELEASE_BOARD=octopus-signed-mp-v31keys CHROMEOS_RELEASE_BRANCH_NUMBER=77 CHROMEOS_RELEASE_BUILDER_PATH=octopus-release/R93-14092.77.0 CHROMEOS_RELEASE_BUILD_NUMBER=14092 CHROMEOS_RELEASE_BUILD_TYPE=Official Build CHROMEOS_RELEASE_CHROME_MILESTONE=93 CHROMEOS_RELEASE_DESCRIPTION=14092.77.0 (Official Build) stable-channel octopus CHROMEOS_RELEASE_KEYSET=mp-v31 CHROMEOS_RELEASE_NAME=Chrome OS CHROMEOS_RELEASE_PATCH_NUMBER=0 CHROMEOS_RELEASE_TRACK=stable-channel CHROMEOS_RELEASE_UNIBUILD=1 CHROMEOS_RELEASE_VERSION=14092.77.0 DEVICETYPE=CHROMEBOOK GOOGLE_RELEASE=14092.77.0

Model: Acer Spin 512

Architecture: x86_64

[uberhacker]

@aghebert: Does firefox start in your crosh shell? If not, that could be your issue.

[aghebert]

Yes, it works. If I start Firefox using firefox in crosh shell, it will start normally.

[supechicken]

Could you try the steps listed in https://github.com/supechicken666/pwashortcut/blob/stable/installer.html after crew-launcher new firefox?

Yes, it works. If I start Firefox using firefox, it will start normally.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/skycocker/chromebrew/issues/6314#issuecomment-946097424, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARQDSSNQEWD4ZEVD65IJ3N3UHRYXDANCNFSM5GHJWWIA .

[aghebert]

Those instructions don't work. I get this error when I click the firefox shortcut;

I checked to make sure the server was running as well.

[supechicken]

Since the crew-launcher new firefox command created a new profile for firefox, you need to install the shortcut once more (also the pwa) and use the new shortcut in the launcher (make sure that you are using the new shortcut :) )

[aghebert]

I'm not sure I understand. I removed the old Firefox shortcut from crew-launcher, created a new Firefox shortcut using crew-launcher, and clicked on the new shortcut. What am I missing?

[uberhacker]

@aghebert: Do you have any ad or popup blocker extensions enabled in your browser?

[supechicken]

I'm not sure I understand. I removed the old Firefox shortcut from crew-launcher, created a new Firefox shortcut using crew-launcher, and clicked on the new shortcut. What am I missing?

Your steps are correct, could you provide the output of crew-launcher uuid firefox?

[aghebert]

crew-launcher uuid firefox
15f6f48b-87f5-4664-bed7-916e78d08795

[aghebert]

Update! Looks like i have leftover shortcut icons. I didn't realize this and was clicking on an older firefox shortcut. The newer one works!

EDIT: I take it back, seems like this shortcut is one and done. Can't get it to work after pinning it in the bar. Seems to launch a window, but that closes almost instantly and firefox does not start.

[supechicken]

Update! Looks like i have leftover shortcut icons. I didn't realize this and was clicking on an older firefox shortcut. The newer one works!

EDIT: I take it back, seems like this shortcut is one and done. Can't get it to work after pinning it in the bar. Seems to launch a window, but that closes almost instantly and firefox does not start.

If the window closes immediately, we can confirm the shortcut itself is working :) Seems that firefox is trying use Wayland to display instead of x11, could you try the following:

GDK_DISPLAY=x11
startsommelier
crew-launcher stop && crew-launcher start

The shortcut should work now

[uberhacker]

@aghebert: I just tested the new edge package and it works fine for me. Is your server running? What is the output of crew-launcher status? If not, run crew-launcher start and try to load firefox from the launcher. If this works then it might be a good idea to add crew-launcher start in your ~/.bashrc so the server starts when you login. EDIT: Actually, you don't need to add crew-launcher start to ~/.bashrc since /usr/local/etc/env.d/crew_launcher already does this for you.

[zeglol1234]

Can somebody tell me how to use --display, im lost here

[Zopolis4]

This issue is probably better suited for the crew-launcher repo, right? Should someone transfer it?