Pulsar not working in RockyLinux9 #747

stefaniecg · 2023-09-30T09:56:57Z

Thanks in advance for your bug report!

Have you reproduced issue in safe mode?
Have you used the debugging guide to try to resolve the issue?
Have you checked our FAQs to make sure your question isn't answered there?
Have you checked to make sure your issue does not already exist?
Have you checked you are on the latest release of Pulsar?

What happened?

I installed Pulsar in Rocky Linux 9, but no GUI ever comes up.

sudo dnf install -y ./pulsar-1.109.2023092802.x86_64.rpm

Infos about pulsar and OS below.
Please help, thanx

$ pulsar -v  
Pulsar  : 1.109.2023092802  
Electron: 12.2.3  
Chrome  : 89.0.4389.128  
Node    : 14.16.0

$ cat /etc/os-release 
NAME="Rocky Linux"
VERSION="9.2 (Blue Onyx)"
ID="rocky"
ID_LIKE="rhel centos fedora"
VERSION_ID="9.2"
PLATFORM_ID="platform:el9"
PRETTY_NAME="Rocky Linux 9.2 (Blue Onyx)"
ANSI_COLOR="0;32"
LOGO="fedora-logo-icon"
CPE_NAME="cpe:/o:rocky:rocky:9::baseos"
HOME_URL="https://rockylinux.org/"
BUG_REPORT_URL="https://bugs.rockylinux.org/"
SUPPORT_END="2032-05-31"
ROCKY_SUPPORT_PRODUCT="Rocky-Linux-9"
ROCKY_SUPPORT_PRODUCT_VERSION="9.2"
REDHAT_SUPPORT_PRODUCT="Rocky Linux"
REDHAT_SUPPORT_PRODUCT_VERSION="9.2"

Pulsar version

1.109.2023092802

Which OS does this happen on?

🐧 Red Hat based (Fedora, Alma, RockyLinux, CentOS Stream, etc.)

OS details

Rocky Linux 9.2

Which CPU architecture are you running this on?

64-bit(x86_64)

What steps are needed to reproduce this?

In Rocky Linux 9.2 install pulsar:

sudo dnf install -y ./pulsar-1.109.2023092802.x86_64.rpm

Then try:

pulsar

no GUI comes up.

Additional Information:

Thank you for the help you ca provide.

The text was updated successfully, but these errors were encountered:

Daeraxa · 2023-09-30T13:24:00Z

Probably a duplicate of #733. Can you run it from the terminal and check the error is the same about GLIBC?

stefaniecg · 2023-09-30T17:31:12Z

I think it's not the same.
I have runned pulsar in command line and there are no errors, it just does not open the GUI.
What is the problem? How can i have a work around it?
Should i install a previous version of Pulsar or another binary?
Please let me know, thank u

confused-Techie · 2023-10-01T01:42:29Z

While I'm not sure if this is the same issue as #146
It might be beneficial to see if running with --no-sandbox or --in-process-gpu or even a combination of both gets you any results.

Thanks a ton for reporting the issue, hope this helps

stefaniecg · 2023-10-01T05:03:39Z

Hi, unfortunately non of those options (--no-sandbox or --in-process-gpu) got a GUI to appear.
What could be a work around?

Charadon · 2023-10-01T08:02:12Z

I think it's not the same. I have runned pulsar in command line and there are no errors, it just does not open the GUI. What is the problem? How can i have a work around it? Should i install a previous versoin of Pulsar or another binary? Please let me know, thank u

Are you running pulsar with the -f flag when running from the command-line? Otherwise it won't show any output.

stefaniecg · 2023-10-01T12:27:41Z

With the -f option now we get some error feedback.
Is there a work around ?

$ pulsar -f
/lib64/libstdc++.so.6: version `GLIBCXX_3.4.30' not found (required by /tmp/.org.chromium.Chromium.085Hct)
Error: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.30' not found (required by /tmp/.org.chromium.Chromium.085Hct)
    at process.func [as dlopen] (electron/js2c/asar_bundle.js:5:1846)
    at Object.Module._extensions..node (internal/modules/cjs/loader.js:1138:18)
    at Object.func [as .node] (electron/js2c/asar_bundle.js:5:2073)
    at Module.load (internal/modules/cjs/loader.js:935:32)
    at Module._load (internal/modules/cjs/loader.js:776:14)
    at Function.f._load (electron/js2c/asar_bundle.js:5:12913)
    at Module.require (internal/modules/cjs/loader.js:959:19)
    at require (internal/modules/cjs/helpers.js:88:18)
    at Object.<anonymous> (/opt/Pulsar/resources/app.asar/node_modules/nsfw/js/src/index.js:4:14)
    at Module._compile (internal/modules/cjs/loader.js:1078:30)

stefaniecg · 2023-10-01T12:52:34Z

I have taken a look and the file /lib64/libstdc++.so.6 does exist.
So I'm not sure what the problem is.
Why this version is not accepted by pulsar?

Alternativelly i thought i could copy the "right version" of libstdc++.so.6 to my local libraries directory: /usr/local/lib64, would that help?
In which case: what is the "right version"?

Please let me know what i can do to run Pulsar on this distribution, thank you.

DeeDeeG · 2023-10-01T16:14:20Z

Error: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.30' not found (required by /tmp/.org.chromium.Chromium.085Hct)

I think we should build on the oldest Linux version that CI will let us build on. Older Linux in CI will include older glibc.

Newer glibc occasionally has breaking changes that aren't backward-compatible. So, official Atom always stayed building on the oldest Linux the CI environment would let them use, for broadest compatibility with long-lived distros that are very much not "bleeding edge" in their updates, especially (at the time) CentOS, so this being an issue for the Red Hat extended family today is a bit of a callback to that previous discussion I remember from official Atom.

EDIT to add: If we need to build in a Docker container using an older Linux distro, that could be an option.

stefaniecg · 2023-10-01T16:46:00Z

@DeeDeeG, thank you for your answer, yet I don't understanding exacly what I need to do to get Pulsar running in my RockyLinux9 distribution. :)

I'm not sure how to "build on the oldest Linux version that CI will let us build on", but if you explain a bit what needs to be done, i can try it out. :)

Or maybe someone else could help out with the "building" of these binaries.

Let me know how to move forward, as I'd love to get Pulsar running on my Rocky instalation. :)
Thank you for your help.

aalbacetef · 2023-10-01T19:35:14Z

@DeeDeeG, thank you for your answer, yet I don't understanding exacly what I need to do to get Pulsar running in my RockyLinux9 distribution. :)

I'm not sure how to "build on the oldest Linux version that CI will let us build on", but if you explain a bit what needs to be done, i can try it out. :)

Or maybe someone else could help out with the "building" of these binaries.

Let me know how to move forward, as I'd love to get Pulsar running on my Rocky instalation. :) Thank you for your help.

Can you try the appimage instead? It might be better than tinkering with your glibc installation (btw: ldd --version should spit out the version you have).

aalbacetef · 2023-10-01T19:44:07Z

@Daeraxa it would be a good idea to downgrade the build process to an older version and also to use the bitnami/minideb images. I'd be happy to give it a try.

stefaniecg · 2023-10-01T20:06:02Z

Can you try the appimage instead? It might be better than tinkering with your glibc installation (btw: ldd --version should spit out the version you have).

Regarding ldd, here is the terminal output:

$ldd --version
ldd (GNU libc) 2.34
Copyright (C) 2021 Free Software Foundation, Inc.

Regarding trying the AppImage, i want to try this.
Meaning i will download the Appimage version of the Rolling release: Pulsar-1.109.2023100116.AppImage and install it by double clicking it. Right?

But before i install it, can someone please tell me how to uninstall the current Pulsar installation? so i get a clean new appimage install

Thank you for your help !

Daeraxa · 2023-10-01T21:56:53Z

@stefaniecg Appimages don't actually install (unless you are using AppimageLauncher which will prompt anyway), they are essentially self contained applications. You can have it alongside an installed version and it would work the same (as they use the same config folder). You should be able to uninstall with dnf remove pulsar, Pulsar was installed but you just couldn't launch it.

@aalbacetef I'll have to defer to the experts there I'm afraid, @DeeDeeG for example has a much better handle on this.

Either way we should close one of these issues (i.e. this or #733), we already have a conversation split between them and it does appear to be the same problem.

aalbacetef · 2023-10-01T22:15:21Z

@stefaniecg You can uninstall using the command that @Daeraxa wrote.

As per the AppImage, think of it as a portable binary, you don't install it, you run it (don't forget to chmod +x it!).

Here's what I suggest:

create a directory where you'd like to place the AppImage (if you don't already have one), some people like using ~/.local/bin, others /opt/bin, your choice!
add it to your path: at the end of your ~/.bashrc add a line export PATH="/path/to/new/dir:$PATH"
(optional) either rename the AppImage to pulsar or symlink it with ln -s

Now you should be able to launch pulsar directly from the terminal.

If you'd like to have it run as an app, you'll want to create a .desktop file.

Here's an example of a pulsar.desktop file:

#!/usr/bin/env xdg-open
[Desktop Entry]
Terminal=false
Type=Application
Name=Pulsar
Exec=/path/to/bin/pulsar
Categories=Utility;

and drop it in the appropriate directory, usually ~/.local/share/applications.

stefaniecg · 2023-10-02T07:58:05Z

So i uninstalled pulsar with: sudo dnf remove pulsar,
then chmod +x Pulsar-1.109.2023100116.AppImage,
then executed it ./Pulsar-1.109.2023100116.AppImage , but the same error popped up.
What can i do now? :)
Thank you so much for your help.

$./Pulsar-1.109.2023100116.AppImage 
/lib64/libstdc++.so.6: version `GLIBCXX_3.4.30' not found (required by /tmp/.org.chromium.Chromium.XIxwSK)
Error: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.30' not found (required by /tmp/.org.chromium.Chromium.XIxwSK)
    at process.func [as dlopen] (electron/js2c/asar_bundle.js:5:1846)
    at Object.Module._extensions..node (internal/modules/cjs/loader.js:1138:18)
    at Object.func [as .node] (electron/js2c/asar_bundle.js:5:2073)
    at Module.load (internal/modules/cjs/loader.js:935:32)
    at Module._load (internal/modules/cjs/loader.js:776:14)
    at Function.f._load (electron/js2c/asar_bundle.js:5:12913)
    at Module.require (internal/modules/cjs/loader.js:959:19)
    at require (internal/modules/cjs/helpers.js:88:18)
    at Object.<anonymous> (/tmp/.mount_PulsarenEM92/resources/app.asar/node_modules/nsfw/js/src/index.js:4:14)
    at Module._compile (internal/modules/cjs/loader.js:1078:30)

Daeraxa · 2023-10-02T08:33:21Z

Unfortunately I think the only answer at the moment is to go for an earlier release until we sort out what we are going to do. Essentially we are building Pulsar on a machine that means older versions of Linux aren't supported.

stefaniecg · 2023-10-02T12:22:30Z

@Daeraxa, ok, i'll do that.
What earlier release would work?
Where do i download it?

Thank you for the help :)

Charadon · 2023-10-02T13:52:19Z

@Daeraxa, ok, i'll do that. What earlier release would work? Where do i download it?

Thank you for the help :)

I compiled some binaries that were made on Debian 8, you can try these and tell me if they work: https://ftp.iotib.net/Projects/Pulsar%20Older%20Glibc/v1.109.0/

If not, then you could use the flatpak?

stefaniecg · 2023-10-02T16:13:49Z

@Charadon,
I downloaded your binaries and installed sudo dnf install -y ./pulsar-1.109.0.x86_64.rpm and it worked like a charm !
Thank you so much for your help ! 👍

stefaniecg · 2023-10-02T16:18:55Z

Just a couple of questions, to get an idea:

Q1. what was the problem? is it that Rocky9 OS has too OLD or too NEW versions of the libstdc++.so.6 library?
Q2. i understand that these are the only binaries that will work for my distribution now, do you have an idea when will i be able to use the 'normal' binaries for installation? i.e. update Pulsar.

Let me know.
Thank you all for your support :)

Charadon · 2023-10-02T16:31:39Z

Just a couple of questions, to get an idea:

Q1. what was the problem? is it that Rocky9 OS has too OLD or too NEW versions of the libstdc++.so.6 library? Q2. i understand that these are the only binaries that will work for my distribution now, do you have an idea when will i be able to use the 'normal' binaries for installation? i.e. update Pulsar.

Let me know. Thank you all for your support :)

I wrote up an explanation on why this happens here: #733 (comment)

DeeDeeG · 2023-10-17T02:46:33Z

Hi again, sorry for the delayed response.

Q1. what was the problem? is it that Rocky9 OS has too OLD or too NEW versions of the libstdc++.so.6 library?

The problem is Rocky 9 having too old a version of glibc, or in other words the problem is Pulsar being compiled for too new a version of glibc to be compatible.

Q2. i understand that these are the only binaries that will work for my distribution now, do you have an idea when will i be able to use the 'normal' binaries for installation? i.e. update Pulsar.

We have some binaries generated by Pulsar team now, if you prefer those. (See: #733 (comment).)

As for a timeline for when these binaries might be made routinely during our usual release process: We are still running into some problems when trying to automatically test these binaries for quality assurance purposes, to confirm they continue to work with each change to Pulsar during deveopment, but folks have who have tried them manually so far have commented that it's working for them.

If we can't find a way to automatically test these like we test our other binaries, we may provide them "as-is" as separate "legacy" binaries. We're still figuring out what we want to do about this, to be honest.

More details in my comment in the other issue: #733 (comment)

I'm not sure how much work it will take to make progress on automated testing, so no firm plans at the moment regarding when we'd want to make these widely available as part of our usual releases.

stefaniecg · 2024-01-29T11:56:18Z

@confused-Techie , hi, so i can now install Pulsar in RockyLInux9 using the Pulsar Regular Release for linux installer from the website?

confused-Techie · 2024-01-29T16:02:19Z

@confused-Techie , hi, so i can now install Pulsar in RockyLInux9 using the Pulsar Regular Release for linux installer from the website?

If the PR has worked as intended then on the next Pulsar Regular Release yes you could. So keep an eye out for our Pulsar Release in mid February, or otherwise if you install the Rolling Release, that should already have this fix.

stefaniecg · 2024-01-29T16:19:18Z

ok @confused-Techie , thank you so much for your help !

stefaniecg added the bug Something isn't working label Sep 30, 2023

DeeDeeG mentioned this issue Oct 16, 2023

[meta] Build x86 Linux binaries on Ubuntu 20.04, for older (more compatible) glibc #760

Merged

confused-Techie mentioned this issue Oct 17, 2023

Getting a Glibc error and Pulsar won't run on Debian #773

Closed

5 tasks

Daeraxa mentioned this issue Oct 19, 2023

can't update to latest #778

Closed

5 tasks

DeeDeeG mentioned this issue Jan 13, 2024

CI: build Linux x86-64 binaries on older Linux #858

Merged

confused-Techie closed this as completed in #858 Jan 29, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Pulsar not working in RockyLinux9 #747

Pulsar not working in RockyLinux9 #747

stefaniecg commented Sep 30, 2023

Daeraxa commented Sep 30, 2023

stefaniecg commented Sep 30, 2023 •

edited

Loading

confused-Techie commented Oct 1, 2023

stefaniecg commented Oct 1, 2023 •

edited

Loading

Charadon commented Oct 1, 2023

stefaniecg commented Oct 1, 2023

stefaniecg commented Oct 1, 2023

DeeDeeG commented Oct 1, 2023 •

edited

Loading

stefaniecg commented Oct 1, 2023 •

edited

Loading

aalbacetef commented Oct 1, 2023

aalbacetef commented Oct 1, 2023

stefaniecg commented Oct 1, 2023

Daeraxa commented Oct 1, 2023 •

edited

Loading

aalbacetef commented Oct 1, 2023 •

edited

Loading

stefaniecg commented Oct 2, 2023

Daeraxa commented Oct 2, 2023

stefaniecg commented Oct 2, 2023

Charadon commented Oct 2, 2023

stefaniecg commented Oct 2, 2023

stefaniecg commented Oct 2, 2023

Charadon commented Oct 2, 2023

DeeDeeG commented Oct 17, 2023 •

edited

Loading

stefaniecg commented Jan 29, 2024

confused-Techie commented Jan 29, 2024

stefaniecg commented Jan 29, 2024

Pulsar not working in RockyLinux9 #747

Pulsar not working in RockyLinux9 #747

Comments

stefaniecg commented Sep 30, 2023

Thanks in advance for your bug report!

What happened?

Pulsar version

Which OS does this happen on?

OS details

Which CPU architecture are you running this on?

What steps are needed to reproduce this?

Additional Information:

Daeraxa commented Sep 30, 2023

stefaniecg commented Sep 30, 2023 • edited Loading

confused-Techie commented Oct 1, 2023

stefaniecg commented Oct 1, 2023 • edited Loading

Charadon commented Oct 1, 2023

stefaniecg commented Oct 1, 2023

stefaniecg commented Oct 1, 2023

DeeDeeG commented Oct 1, 2023 • edited Loading

stefaniecg commented Oct 1, 2023 • edited Loading

aalbacetef commented Oct 1, 2023

aalbacetef commented Oct 1, 2023

stefaniecg commented Oct 1, 2023

Daeraxa commented Oct 1, 2023 • edited Loading

aalbacetef commented Oct 1, 2023 • edited Loading

stefaniecg commented Oct 2, 2023

Daeraxa commented Oct 2, 2023

stefaniecg commented Oct 2, 2023

Charadon commented Oct 2, 2023

stefaniecg commented Oct 2, 2023

stefaniecg commented Oct 2, 2023

Charadon commented Oct 2, 2023

DeeDeeG commented Oct 17, 2023 • edited Loading

stefaniecg commented Jan 29, 2024

confused-Techie commented Jan 29, 2024

stefaniecg commented Jan 29, 2024

stefaniecg commented Sep 30, 2023 •

edited

Loading

stefaniecg commented Oct 1, 2023 •

edited

Loading

DeeDeeG commented Oct 1, 2023 •

edited

Loading

stefaniecg commented Oct 1, 2023 •

edited

Loading

Daeraxa commented Oct 1, 2023 •

edited

Loading

aalbacetef commented Oct 1, 2023 •

edited

Loading

DeeDeeG commented Oct 17, 2023 •

edited

Loading