Open aalbacetef opened 1 year ago
Thanks a ton for reporting this!
While I'm not the most familiar with the errors presented, as they all have to do with internal drivers and such, I think it's easy to assume that this will be resolved after we can finally bump our Electron version.
Which is something that we have been hard at work on, for well really the past year. So it'll take time, but that sounds likely to be the fix.
I've got some more info!
For context, I have a laptop with an Nvidia graphics card and on Pop OS I have different modes I can use:
Usually I stay on integrated graphics mode due to the longer battery life. This is the mode I was on when I ran into the error yesterday.
I thought maybe the mode had something to do with it so I switched to Nvidia graphics mode and ran the app. It immediately exits with this error:
[5362:0930/095114.730212:FATAL:gpu_data_manager_impl_private.cc(415)] GPU process isn't usable. Goodbye.
Trace/breakpoint trap (core dumped)
If I add either one of the following flags when in Nvidia graphics mode it works just fine:
--disable-gpu-sandbox
--in-process-gpu
Did it not work with --no-sandbox
? Its a known thing so we have it as a note on the downloads page.
Did it not work with
--no-sandbox
? Its a known thing so we have it as a note on the downloads page.
It did, but --disable-gpu-sandbox
was also enough (no need to disable all sandboxes).
NOTE: this is when I'm in nvidia graphics mode, if I'm using the integrated graphics mode the flags do nothing and it just spits out the libva error before launching.
I was going to post a new issue but just gave Pulsar a try, downloaded it through deb-get (1.113.0) and whenever I tried to run it from the launcher nothing would happen.
dmesg spits out this:
[23718.355179] traps: Chrome_IOThread[96287] trap int3 ip:56011fde5cd8 sp:77fe3c9f9360 error:0 in pulsar[56011fbba000+6271000]
Here's the odd part, I can launch it just fine from the terminal. No errors, it launches perfectly.
If I run which
, it tells me pulsar is /usr/bin/pulsar
.
Cool, now what is the launcher trying to run? Well:
$ cat /usr/share/applications/pulsar.desktop
[Desktop Entry]
Name=Pulsar
Exec=/opt/Pulsar/pulsar %U
Terminal=false
Type=Application
Icon=pulsar
StartupWMClass=Pulsar
Comment=A Community-led Hyper-Hackable Text Editor
Categories=Development;
and sure enough, running this (entirely different binary) fails with the errors already discussed earlier in this thread, so adding the flags I used previously should fix it.
Why is pulsar shipping two different binaries? It seems like the robust one is the one in /usr/bin
. Would it not make sense to have the pulsar.desktop
file point to the /usr/bin/pulsar
binary?
Thanks for the information @aalbacetef but Pulsar should not be shipping two totally different binaries. We just build the one for each platform.
I believe @Daeraxa was the one to originally setup deb-get
maybe they might have some insight here
Thanks in advance for your bug report!
What happened?
Hi guys, I downloaded the latest AppImage, ran it and I get some errors in the terminal. The editor still works, but figured it'd be a good idea to open an issue anyways.
Errors that show up:
Output of
--version
:Output of
vainfo
:Output of
lsb_release -a
:Output of
uname -a
:Pulsar version
1.109.0
Which OS does this happen on?
🐧 Debian based (Linux Mint, Ubuntu, etc.)
OS details
Pop!_OS 22.04 LTS
Which CPU architecture are you running this on?
64-bit(x86_64)
What steps are needed to reproduce this?
Additional Information:
No response