Atom from Snaps cannot be launched, missing libkeyutils.so.1
Closed, WontfixPublic

Description

Greetings,

A small disclaimer, yes I know Atom is packaged within Solus but updates are very slow (repo sync, etc + there seems to be issues with VSCode and npm5 builds so Solus is falling behind) for these apps (namely Atom & VSCode) which I rely on very much. So I resorted to using tar.gz download for VSCode and snap for Atom. The latter one has a problem when installed via snap.

/snap/atom/20/usr/share/atom/atom: error while loading shared libraries: libkeyutils.so.1: cannot open shared object file: No such file or directory

Would be nice to get all the libs in so Atom can run successfully.

I don't see how the issue with VS Code relates to Atom. Atom isn't affected, it's fully updated in unstable, and we're working towards more frequent syncs.

It's just to prevent comments why use Atom from snaps when Solus has it in repo. Main issue here is missing libkeyutils.so.1

ikey added a subscriber: ikey.Aug 25 2017, 12:47 PM

Is it a classic snap or a confined snap? Because the idea of Snaps is that we're not meant to provide ABI compatibility ..

It's a classic snap. When I tried to install atom via

sudo snap install atom

it complained that it needs

--classic
ikey closed this task as "Wontfix".Aug 25 2017, 1:28 PM
ikey claimed this task.

So yeah I've spoken to Snapcraft guys about this, its a bug in the Snap, and not in Solus.

See: https://github.com/snapcrafters/atom/pull/3 - the wonderful folks at Snapcraft identified said bug and have a fix readied for it.

(Marking as wontfix here as its not an internal bug)

ikey added a comment.Aug 25 2017, 2:42 PM

Upstream says:

[15:41:07] <ogra_> ikey, if you feel like you can tell your users to "snap refresh atom --edge" to test the fix ;) (and to show off how quick snaps can be fixed ;) )

Please give it a whirl @Nikki1993 and see if it works :)

@ikey no success xD getting this now

/snap/atom/26/usr/share/atom-beta/atom: error while loading shared libraries: libpcre.so.3: cannot open shared object file: No such file or directory

Should I report this upstream?