LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 09-27-2018, 09:35 AM   #1
Qury
Member
 
Registered: Feb 2004
Location: Naas,IE
Distribution: Slackware
Posts: 212

Rep: Reputation: 184Reputation: 184
vscode, atom, btackets - segfault on current


Hi All,

I think the update on the 21st broke atom,brackets and vscode editors.

I wonder whether any of the above editors work fine for you if you are running the latest current or is it just me?
 
Old 09-27-2018, 11:04 AM   #2
Darth Vader
Senior Member
 
Registered: May 2008
Location: Romania
Distribution: DARKSTAR Linux 2008.1
Posts: 2,727

Rep: Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247
Quote:
Originally Posted by Qury View Post
Hi All,

I think the update on the 21st broke atom,brackets and vscode editors.

I wonder whether any of the above editors work fine for you if you are running the latest current or is it just me?
Read again the Skype's story...

How all of your applications are Electron based, I believe that's either a crash caused by the current GLIBC or, well... they look for talking with (e)logind.
 
Old 09-27-2018, 11:28 AM   #3
ponce
LQ Guru
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 7,114

Rep: Reputation: 4189Reputation: 4189Reputation: 4189Reputation: 4189Reputation: 4189Reputation: 4189Reputation: 4189Reputation: 4189Reputation: 4189Reputation: 4189Reputation: 4189
regarding atom, as conraid on slacky.eu noted, the problem seems to be that it bundles a version of electron that it's not compatible with glibc-2.28

https://github.com/electron/electron/issues/13972

that is fixed with electron 2.0.8, but also the latest stable atom bundles a lower electron version.

so conraid suggest to go with the development version (ATM 1.32.0-beta0), and that works: if you want to try it you can apply the following modifications to the SlackBuild on SBo
Code:
diff --git a/development/atom/atom.SlackBuild b/development/atom/atom.SlackBuild
index 4b37a523e6..cb91f78ccf 100644
--- a/development/atom/atom.SlackBuild
+++ b/development/atom/atom.SlackBuild
@@ -23,7 +23,8 @@
 # ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

 PRGNAM=atom
-VERSION=${VERSION:-1.23.3}
+VERSION=${VERSION:-1.32.0_beta0}
+SRCVER=$(echo $VERSION | tr _ - )
 BUILD=${BUILD:-1}
 TAG=${TAG:-_SBo}

@@ -65,9 +66,9 @@ set -e
 rm -rf $PKG
 mkdir -p $TMP $PKG $OUTPUT
 cd $TMP
-rm -rf $PRGNAM-$VERSION
-tar -xvf $CWD/$PRGNAM-$VERSION.tar.gz || tar xvf $CWD/v$VERSION
-cd $PRGNAM-$VERSION
+rm -rf $PRGNAM-$SRCVER
+tar -xvf $CWD/$PRGNAM-$SRCVER.tar.gz
+cd $PRGNAM-$SRCVER
 chown -R root:root .
 find -L . \
  \( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm 555 \
@@ -120,7 +121,9 @@ if [ "${ELECTRON_VERSION}" != "" ]; then
     $PKG/$ATOM_RESOURCES/apm/node_modules/atom-package-manager/lib/apm.js
 else
   # packaged installation
-  cp -r out/$PRGNAM-$VERSION-$ARCH_OUTPUT $PKG/usr/share/atom
+  BETA=""
+  if echo $VERSION | grep -q beta ; then BETA="-beta" ; fi
+  cp -r out/${PRGNAM}${BETA}-$SRCVER-$ARCH_OUTPUT $PKG/usr/share/atom
 fi

 install -Dm755 atom.sh $PKG/usr/bin/atom
diff --git a/development/atom/atom.info b/development/atom/atom.info
index 2f69bc17d7..6f155359b4 100644
--- a/development/atom/atom.info
+++ b/development/atom/atom.info
@@ -1,8 +1,8 @@
 PRGNAM="atom"
-VERSION="1.23.3"
+VERSION="1.32.0_beta0"
 HOMEPAGE="https://atom.io/"
-DOWNLOAD="https://github.com/atom/atom/archive/v1.23.3/atom-1.23.3.tar.gz"
-MD5SUM="1dfc819b29c910daaed20c11a629b28f"
+DOWNLOAD="https://github.com/atom/atom/archive/v1.32.0-beta0/atom-1.32.0-beta0.tar.gz"                                                                                    
+MD5SUM="eab5898091d0e5e333d847e3025a158b"
 DOWNLOAD_x86_64=""
 MD5SUM_x86_64=""
 REQUIRES="nodejs"
regarding vscode and brackets I haven't checked at all, but if they use nodejs and electron like atom, most probably they suffer of a similar problem.
 
1 members found this post helpful.
Old 09-27-2018, 12:02 PM   #4
dugan
LQ Guru
 
Registered: Nov 2003
Location: Canada
Distribution: distro hopper
Posts: 11,244

Rep: Reputation: 5322Reputation: 5322Reputation: 5322Reputation: 5322Reputation: 5322Reputation: 5322Reputation: 5322Reputation: 5322Reputation: 5322Reputation: 5322Reputation: 5322
I've been reading the GitHub issues, and it sounds like: a) the next version of VS Code will fix this, and b) the current release of Electron should already have fixed this?
 
Old 09-27-2018, 12:31 PM   #5
Qury
Member
 
Registered: Feb 2004
Location: Naas,IE
Distribution: Slackware
Posts: 212

Original Poster
Rep: Reputation: 184Reputation: 184
i doubt this has anything to do with the skype story, it is indeed the glibc i think.
I will just have to wait until it get's fixed.
In the mean time i will just use the flatpak
 
Old 09-27-2018, 01:40 PM   #6
ponce
LQ Guru
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 7,114

Rep: Reputation: 4189Reputation: 4189Reputation: 4189Reputation: 4189Reputation: 4189Reputation: 4189Reputation: 4189Reputation: 4189Reputation: 4189Reputation: 4189Reputation: 4189
Quote:
Originally Posted by dugan View Post
I've been reading the GitHub issues, and it sounds like: a) the next version of VS Code will fix this, and b) the current release of Electron should already have fixed this?
yes, it should be fixed since electron-2.0.8, but this node sh*t gets bundled with the apps (by the apps developers) in many different versions and they are not necessarily the latest (I suppose they bundle the versions they have tested their stuff with): I quote myself just above
Quote:
Originally Posted by ponce View Post
that is fixed with electron 2.0.8, but also the latest stable atom bundles a lower electron version.
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Kopete segfault on -current ifo Slackware 7 10-22-2020 06:27 AM
segfault printing in slackware64-current Rod3775 Slackware 0 09-01-2018 10:45 PM
Segfault with konsole on -current michaelis Slackware 4 12-07-2017 04:14 AM
[SOLVED] Digikam segfault with current Bourdieu Slackware 17 07-25-2017 04:22 PM
Xterminal + current GTK = segfault crxssi Linux - Software 3 01-28-2006 06:58 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 07:38 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration