after upgrade to signal-desktop 1.15.0, it crashes with `GLIBCXX_3.4.21' not found #2604
Comments
|
Same issue exists on Debian Jessie. Works as expected on Debian Stretch. edit: repost to mitigate the "me too" spam...
|
|
I am having the problem too with 1.15.0 on Ubuntu 14.04. Seems they are expecting us to have newer libc than the OS will provide. |
|
They also seem to make it impossible to find previous version to reinstall. The packages come from updates.signal.org but is impossible to browse this site. Fortunately I had previous version still in /var/cache/apt/archives/signal-desktop_1.14.4_amd64.deb. If you can find previous version then can install with "dpkg -i deb-file", as a temporary work around until this is resolved. This worked for me and Signal Desktop is running again. Also be sure to lock the version so it doesn't get updated to 1.15 again when you run the software updater, can do that in various ways as described here for example, https://askubuntu.com/questions/18654/how-to-prevent-updating-of-a-specific-package |
|
same story @LMDE2 |
|
It seems to 1.50 release did fail the QA testing - there are issues on all platforms with this rel. Is it possible to release a successor that reverts to 1.14 for now? I mean official 1.15.1 package that is basically the previous stable 1.14? |
|
Can confirm this for Ubuntu 14.04. |
|
Confirmed by on debian jessie. Reverted to 1.14.4 successfully. |
|
I'm getting the same error on 1.15.2. |
|
version 1.15.2 on debian jessie problem still unsolved |
|
Issue still on 1.15.3. I am on Linux Mint 17.3 (Ubuntu 14.04). Reverted back to 1.14.4 successfully. Thanks @scarf!!! |
|
In case you want to validate a 1.14.4 build you locate, here is the |
|
Matches, if someone needs to grab this |
|
I was able to downgrade from 1.15.3 to 1.14.4 using the package that @mykhi linked to (and I confirmed that the Here's a Bash one-liner to verify the signature yourself: |
|
Same issue here. After reverting to 1.14.1, which was still cached by apt, it works again. |
|
Same issue here, with Debian Jessie. |
|
Same issue on 14.04 |
|
Same issue with Linux Mint 17.3 Cinnamon 2.8.8 and Signal Version 1.15.5 |
|
I have also this issue on Ubuntu 14.04 |
|
Same problem here. Kubuntu 14.04, all updates installed. :~$ signal-desktop :~$ apt show libstdc++6:amd64 :~$ strings /usr/lib/x86_64-linux-gnu/libstdc++.so.6|grep GLIBC |
|
Same issue with LMDE2 (Linux Mind Debian Edition). It does run in the Beta LMDE3, however it's not stable enough for normal uses. Had run it in VirtualBox. Very disappointing older, working, stable versions of Signal Desktop are not kept in the repository for an easy downgrade to a functional version. |
|
So, I guess we wait for signal to make the compiler version required more forgiving or for Debian to update the compiler version in stable? |
|
yes, we wait for signal to build a special signal-desktop package for us or for the distribution to update the package libstdc++.so.6 . But I don't even know if thats possible, maybe a system upgrade is necessary |
$ yarn install --frozen-lockfile ## from upstream, dl.yarnpkg.com
yarn install v1.9.4
[1/6] Validating package.json...
error signal-desktop@1.15.5: The engine "node" is incompatible with this module.
Expected version "^8.9.3".
error Found incompatible modulejessie-backports only ships None of this is really Signal's problem, but it does highlight the need for proper package archives. |
WorkaroundBack in business 👌
|
|
Is this fixed in 16? |
|
Nope. I tried it when 1.16.0 was first released and same issue. Had to downgrade back to 1.14.4. |
|
Have same issue with my Mint 17.3 Cinnamon.
|
|
Another workaround is to download newer libstdc and start signal-desktop with LD_LIBRARY_PATH environment variable. I prefer this than installing whole new development environment and compiling signal-desktop from source everytime a new version is released. With this workaround, signal-desktop can be kept up to date using repository like normal, only need to update the launcher command when signal-desktop gets updated. For example, Ubuntu 14.04: Now you may quit signal-desktop and update the launcher so you don't have to use command line always. For me I'm using Unity and the launcher is the file /usr/share/applications/signal-desktop.desktop. Update the line so it looks like this (warning, you may need to exit your desktop session and switch to a console (ctrl-alt+F1) since when I edited this file it crashed the session, but could be because I entered the wrong data initially): |
|
@moxie-signal @scottnonnenberg-signal |
|
To name but a few: I had convinced many people to use signal ... "unfortunately", I must say, because now they all complain to me and move back (and even worse: they will not return) to other messengers. This all would not be a problem, if there was a package maintained by the proper debian package manager. However, as I discovered: signal doesn't want proper package managers, because: "Distributing it through another channel would only complicate things without providing any clear benefit." Great idea, because the result is distributing a package which doesn't work and - even better - it is not allowed to use the working one anymore. Big detriment to signal (and to my reputation through recommeding signal). |
|
I'm glad that signal already did not work when I wanted to start using it a few weeks ago. Just imagine all of this would have happened a few weeks after migrating to Signal and persuade other to also do so. Would have been prette annoying and embarassing. |
|
Out of curiosity, what is happening with this? We are three months later with no resolution. Do we give up on Signal? I also don't currently have time to upgrade my machine to the latest Linux Mint LTS just so Signal will work. It would be nice to hear from a Signal representative to have some hope @moxie-signal @scottnonnenberg-signal @gasi-signal |
|
Considering that those people have been mentioned multiple times on this issue and have yet to react to any of those notifications, I guess Signal's official position is "get fucked". So we return to the dark ages of 2015: There is no Signal desktop client. |
|
Just adding my name to the pile as I'd been struggling to fix this myself for a while now - @scarf thanks for the directions, that worked great! @Chris56 makes great points IMO, but I stay hopeful that Signal devs will at least let us know their thoughts sometime soon. There's an older request in Debian bugs (wishlist) that had stalled - perhaps a good time to revive discussion there instead? Note that there are potential minor issues should there be continued push against direct Debian inclusion - the app identified by it's current name and icon may be a trademark issue. |
|
I'd like to provide a bit of additional information on how to go from the git repo to a .deb file that can be installed (on Ubuntu 14.04 (ancient!)). My version of signal warned me that I had to update to keep using, and I got into this mess here. The steps I post are based on @mockturtl 's message, and also cover deb release creation and installation. At the end of these steps here, you'll be able to start the latest version of signal desktop from the window manager Launcher. (no need to run some yarn command from a git checkout folder). Not being a developer in this project, it wasn't exactly obvious how one should go from a dev build to a debian file which was installable. The build instructions cited earlier leave you in a state where you have to start it from the checked out repo folder... which is not very practical, especially if you have to select your node version each time. I considered downloading the deb posted earlier in the thread, but I'm not sure what the hash of the official release used to be. In the interest of freshness, I've decided to install the latest code available. (I'm aware that technically, there's an entirely different chain of trust involved in downloading from GitHub, but at least it's meant to be an official source -- are release hashes stored in some verifiable log?).
If this information was elsewhere on the site, my apologies for the duplication. I didn't see it in the build readme. |
|
Just wanted to join in on the fun, I'm experiencing this with signal-desktop 1.18.1 on ubuntu 14.04.5 I don't have time to upgrade my OS just for Signal, or test these debugging steps, but I'll come back and give them a go soon. |
|
@alexburner i think this is the easiest work-around for now: #2604 (comment) |
Agreed! It worked for me. Just note you have to update |
You can use |
|
Excellent, thank you @scarf ! We'll see which I get to first: the patch or finally updating ubuntu |
|
Confirming this challenge with latest stable Signal 1.18.1, Debian 8 Jessie at 64-bit, GNOME 3.14.1, Kernel 4.9.0-0
|
|
Confirming this challenge with latest beta Signal 1.19.0-beta.3, Debian 8 Jessie at 64-bit, GNOME 3.14.1, Kernel 4.9.0-0
|
1.14.4 WorkedThis is to confirm that the temporary workaround with reverting to “signal-desktop_1.14.4_amd64.deb” worked. Thanks @mykhi for this package above. The downside with Signal Desktop 1.14.4 is that you are not allow to send SMS. If you try this error message is display:
Lock Version 1.14.4For those using Debian, Linux Mint, Ubuntu. And not familiar with the lock version. Until this challenge is resolved, you might be interested to lock Signal to version 1.14.4. Otherwise during your next system update there is a risk that your Signal version 1.14.4 will be automatically replace by the latest version. In turn, the challenge could be back. If you're not familiar with how to lock a package version, find this how-to at: |
|
@Francewhoa does that actually work for you? 'cause my 1.14.4 still shows me the
banner. Like, can you not just start the client, but actually exchange messages with it? Edit: To clarify: You said you couldn't send SMS with it. Can you send Signal-native messages with it? |
Yes and no. No I can not send SMS with 1.14.4 :( I added this screenshot to my comment above. And yes I can start the client :)
I don't know. I'm not familiar with Signal-native messages. What I tested is into this screenshot above. I'm considering using https://ring.cx instead of Signal. Ring have a much better support for Linux. For example Ring has one dedicated repository per distro and per distro version. In comparison Signal has only one repository for all distros and all distro versions. Which seems very risky to create challenge and confusion. Ring package can easily be downloaded either automatically or manually. Including all previous versions. Compare to Ring where only the last version can be manually downloaded. Both Signal and Ring are open source, cross-platform, encrypted, with strong privacy commitment. In November 2016 Ring became part of the GNU Project. |
|
Hi,
Is there another Signal version (>1.14) that does not have this crash bug that is able to send messages ? |
|
@sebma No, there is not. You can either compile from source yourself (#2604 (comment)) or download a newer |
|
@501st-alpha1 I just don't understand : I have installed a newer $ apt-cache policy libstdc++6
libstdc++6:
Installed: 9.1.0-2ubuntu2~14.04.2
Candidate: 9.1.0-2ubuntu2~14.04.2
Version table:
*** 9.1.0-2ubuntu2~14.04.2 0
500 http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu/ trusty/main amd64 Packages
100 /var/lib/dpkg/status
4.8.4-2ubuntu1~14.04.4 0
500 http://fr.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages
4.8.2-19ubuntu1 0
500 http://fr.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packagesbut I still get these errors : $ signal-desktop
signal-desktop: /lib/x86_64-linux-gnu/libdbus-1.so.3: no version information available (required by signal-desktop)
/opt/Signal/signal-desktop: /lib/x86_64-linux-gnu/libdbus-1.so.3: no version information available (required by /opt/Signal/signal-desktop)
Set Windows Application User Model ID (AUMID) { appUserModelId: 'org.whispersystems.signal-desktop' }
NODE_ENV production
NODE_CONFIG_DIR /opt/Signal/resources/app.asar/config
NODE_CONFIG {}
ALLOW_CONFIG_MUTATIONS undefined
HOSTNAME undefined
NODE_APP_INSTANCE undefined
SUPPRESS_NO_CONFIG_WARNING undefined
userData: /home/sebastien/.config/Signal
config/get: Successfully read user config file
config/get: Successfully read ephemeral config file
making app single instance
Fontconfig warning: "/etc/fonts/fonts.conf", line 86: unknown element "blank"
{"name":"log","hostname":"seb-C70D-B-311","pid":18361,"level":30,"msg":"app ready","time":"2019-06-01T06:08:04.182Z","v":0}
{"name":"log","hostname":"seb-C70D-B-311","pid":18361,"level":30,"msg":"starting version 1.25.1","time":"2019-06-01T06:08:04.183Z","v":0}
/opt/Signal/signal-desktop: relocation error: /tmp/.org.chromium.Chromium.KBqn0R: symbol _ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE9_M_createERmm, version GLIBCXX_3.4.21 not defined in file libstdc++.so.6 with link time referenceCan you help me ? |
|
@sebma Sorry, I don't know enough to help with that. It looks like its a slightly different error though, so if no one else responds here, it might be worth opening a new issue. |
No clear benefit … bullshit. This is exactly what I experienced time and again over the past like 10 or 15 years. Devs doing stuff you just don’t understand, and then they won’t change their mind, no matter what reasonable arguments against their decisions you come up with. It’s extremely frustrating. You find a cool piece of software, perfectly suiting your needs, and then the devs ruin it. Gnome, Firefox, Signal. They just don’t have that certain piece of sense of responsibility they inevitably acquire with publishing software for others. It always ends up in some dogmatic, sect-like mess of ideology about software development or gui design. I just installed Signal on someone’s phone and tried to install Signal Desktop on their machine. Won’t start up. The machine is running Mint 17, which is obsolete, I know, but that’s not the point. Signal could be in repos and in F-Droid for a long time now. But one person doesn’t want to, so we don’t get to have that. Yeah, it’s free, we’re not paying customers. But we’re the users. Who else would you write software for? |
|
@scytho I understand that you are very frustrated, but it's not about reasonable arguments. Supporting very old platforms is extremely costly. We can't justify that effort. You'll note that the Android and iOS apps periodically drop support for the oldest Android phones as well. Moreover, when platforms like Mint 17 reach their end of life (a little over one year ago in Mint 17's case) it is a very bad idea to continue using them, because they no longer get security updates. |
|
@scottnonnenberg-signal |
|
@scottnonnenberg-signal: I didn’t expect anything else. That’s exactly my point. I have stated that Mint 17 is crap old, and we are going to replace it. But that’s not the thing in question here. It was about Signal not using distro repos. Where does that lead to? Every piece of software having its own update routine. Wait, where do I know that from … Ah! Yes! Windows! Not my favorite OS, in case that didn’t shine through yet. Yes, it is about reasonable arguments. Be it the hypermonsterbar in Firefox, be it stupid design decisions in Gnome 3, be it this uber annoying device verification when signing in here at GH (here or here), it’s always the same story:
So, no, you don’t seem to really understand just how frustrating this is. This is pure unreasonableness (do you really say that in English?). Most users are no developers and thus unable to change things by themselves. The users depend on the devs. The devs develop for the users, not just for themselves (I guess). It can’t be the objective that everyone builds their own forks, anyway. End of story: The devs act like Apple. They know better what’s good for all of us and basically tell us to shut the fuck up. They would never be able to do this, if they actually had to earn a living with the software, i.e. by selling it. Unless they were Apple or Microsoft or the like. Which in turn is one reason why I don’t like those big players. |
|
2024 and I just installed the app following instructions on the Signal website, and the app won't open on Linux Mint 22 |
|
I'm going to close this issue out in favor of asking people to forward issues like this to signal@support.org. Issues like this tend to have multiple root causes and it's difficult to offer support for many people in a single thread like this spanning several years. When sending a report like this please include a debuglog and/or crash report: https://support.signal.org/hc/en-us/articles/360007318591-Debug-Logs-and-Crash-Reports |
and others
There is another issue #2595 open for 1.15.0 crashing but I don't think is the same issue.
Bug description
After upgrading signal-desktop from 1.14.4 to 1.15.0, it stopped working. Running from console gives this error message:
Steps to reproduce
Actual result:
Expected result:
It should start without errors. It worked before the upgrade.
Platform info
Signal version: 1.15.0
Operating System: Linux Mint Mate 17.3
The text was updated successfully, but these errors were encountered: