Launching from Ubuntu pulsar.desktop fails

[croaker000]

Starting Pulsar from the Ubuntu dashboard fails to start the program. Nothing happens. Launching from a terminal window by typing "pulsar" works fine.

The dashboard method reports this in the log. Why is Pulsar trying to start Bluetooth (Bluez)? I don't have bluetooth on this box.

Apr  4 15:46:12 bomanz dbus-daemon[2603]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.1479' (uid=1000 pid=1038638 comm="/opt/Pulsar/pulsar" label="unconfined")
Apr  4 15:46:12 bomanz systemd[1]: Bluetooth service was skipped because of a failed condition check (ConditionPathIsDirectory=/sys/class/bluetooth).
Apr  4 15:46:13 bomanz systemd[1]: Starting Process error reports when automatic reporting is enabled...
Apr  4 15:46:13 bomanz systemd[1]: Started crash report submission.
Apr  4 15:46:13 bomanz whoopsie[1038770]: [15:46:13] Using lock path: /var/lock/whoopsie/lock
Apr  4 15:46:13 bomanz systemd[1]: whoopsie.service: Deactivated successfully.
Apr  4 15:46:13 bomanz whoopsie-upload-all[1038769]: INFO:root:Collecting info for /var/crash/_opt_Pulsar_pulsar.1000.crash...
Apr  4 15:46:13 bomanz systemd[1]: Started crash report submission.
Apr  4 15:46:13 bomanz whoopsie[1038781]: [15:46:13] Using lock path: /var/lock/whoopsie/lock
Apr  4 15:46:13 bomanz systemd[1]: whoopsie.service: Deactivated successfully.
Apr  4 15:46:15 bomanz pulsar.desktop[1038638]: [1038638:0404/154615.092825:FATAL:gpu_data_manager_impl_private.cc(415)] GPU process isn't usable. Goodbye.
Apr  4 15:46:15 bomanz kernel: [439706.601472] traps: Chrome_IOThread[1038701] trap int3 ip:55708c3aacd8 sp:7f7f9d0763e0 error:0 in pulsar[55708c17f000+6271000]
Apr  4 15:46:17 bomanz whoopsie-upload-all[1038769]: WARNING: hook failed for processing /var/crash/_opt_Pulsar_pulsar.1000.crash:
Apr  4 15:46:17 bomanz whoopsie-upload-all[1038769]: ERROR: processing /var/crash/_opt_Pulsar_pulsar.1000.crash: Compressed file ended before the end-of-stream marker was reached
Apr  4 15:46:17 bomanz systemd[1]: Started crash report submission.
Apr  4 15:46:17 bomanz systemd[1]: apport-autoreport.service: Deactivated successfully.
Apr  4 15:46:17 bomanz systemd[1]: Finished Process error reports when automatic reporting is enabled.
Apr  4 15:46:17 bomanz systemd[1]: apport-autoreport.service: Consumed 4.752s CPU time.
Apr  4 15:46:17 bomanz whoopsie[1039582]: [15:46:17] Using lock path: /var/lock/whoopsie/lock
Apr  4 15:46:17 bomanz systemd[1]: whoopsie.service: Deactivated successfully.

[Daeraxa]

What package are you using? Was it an automatic .desktop file (e.g. from the .deb) or was it made yourself or by a tool like appimagelauncher if using one of the others.

[croaker000]

It was the deb package download from the Pulsar site. The .desktop was the one included in the deb.

I can't see anything untoward in it.

[confused-Techie]

I'd have to investigate but is it possible that it's Electrons Chromium that tries to access bluetooth? The same way that the built in Chromium of Electron will fail on Linux systems without CUPS.

Are you able to run any other Electron apps? Think Discord, or Bitwardens Desktop Client

[confused-Techie]

Really I think the best thing we could do would be to see if Chromium works. That way we can at least try to determine if this issue has been fixed in later chromium builds.

[croaker000]

I'm on Ubuntu 22.10 which only has direct access to the snap version <yuck!>

Using: https://fosspost.org/chromium-deb-package-ubuntu-22-04 , I've installed the deb version which runs from the .desktop file and reports:

Version 108.0.5359.40 (Developer Build) Ubuntu 22.10 (64-bit)

Hope that helps...

[croaker000]

One thing I still haven't figured out is why the .desktop file route fails from the dashboard but typing "pulsar" from a terminal window or Ubuntu's ALT-F2 "Run a command" window works fine.

[Spiker985]

One thing to check would be if adding --no-sandbox to the .desktop helps for some god forsaken reason

It's something that's added inside the pulsar.sh, that is missing from the .desktop file that electron-builder creates

[croaker000]

That did it! Well done. Sorted. Thanks.

[Spiker985]

Son of a- Alright, I'll see if I can PR that into the electron builder config

[confused-Techie]

Son of a- Alright, I'll see if I can PR that into the electron builder config

It might be worth mentioned that when investigate the other day it looked like it was possible to add some flags during runtime, right before the application window is created, at this point if we need it on all Linux systems, then maybe it's possible to add it there instead of trying to shove it into every possible way Pulsar could be launched?

Also @croaker000 had no clue it worked via the CLI, so glad a solution was found. But really interesting that --no-sandbox disables the requiring of core components like that

[Spiker985]

Son of a- Alright, I'll see if I can PR that into the electron builder config

It might be worth mentioned that when investigate the other day it looked like it was possible to add some flags during runtime, right before the application window is created, at this point if we need it on all Linux systems, then maybe it's possible to add it there instead of trying to shove it into every possible way Pulsar could be launched?

Also @croaker000 had no clue it worked via the CLI, so glad a solution was found. But really interesting that --no-sandbox disables the requiring of core components like that

If we could inject it, that would also presumably fix the instances where the app image doesn't function properly as well

Edit: The problem is, that flag is for Electron and I'm unsure if we can set it that late in the startup