I'm unable to pull from inside Atom. I get this error message:

From atom/atom#18170 looks like it's a packaging problem.
I'm on 18.04 and Atom 1.33.0

Would be nice to support Atom IDE by releasing 1.21 beta - probably by just patching the snapcraft.yaml to build 1.21 beta, send to edge, test, release that to beta, then we probably should patch snapcraft.yaml again to build from master to edge.

This suggestion is inspired by the process set out here, we maybe should hold off master builds for the time being - until the build service supports daily builds.

Atom 1.25 was released: http://blog.atom.io/2018/03/15/atom-1-25.html
Looking at the snapcraft.yml, it uses the "latest" so is there anything I can do to help so 1.25 be released as a snap?

Thank you.

Atom 1.52 was released today, if you wanna update the Snap: https://github.com/atom/atom/releases/tag/v1.52.0

Hello! Could you please update and publish version 1.31.1 to https://snapcraft.io/atom to fix atom/atom#18118? Thanks!

Atom releases: https://atom.io/releases

I can't see the toolbar, but I can access its buttons and they turn lighter.

A new upstream bugfix release is available (version 1.22.1).

Hi, the owner of @atom-community here.

The native addons that we make require GLIBCXX_3.4.22 for the reasons explained here by the nodejs maintainers. Could you add this library to the snap?

It solves these issues:

At /snap/core/current/usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.22' not found (required by /home/cool/.atom/packages/autocomplete-paths/node_modules/fuzzaldrin-plus-fast/build/Release/fuzzaldrinplusfast.node)

nodejs/node-gyp#2297
atom-community/ide-python#255

atom/atom#21291

Description

Atom crashes on startup with an int3. Atom is installed through snap. Purged the installation and reinstalled, followed all debugging advice, to no avail.

Steps to Reproduce

1. Launch atom

Expected behavior:

Atom launches as usual.

Actual behavior:

Atom reports a sigtrap through dmesg: (from 4 different attempts)

[85449.742298] traps: atom[88594] trap int3 ip:55a25bcab627 sp:7ffdef0a18f0 error:0 in atom[55a259d87000+5024000]
[85652.644715] traps: atom[88840] trap int3 ip:55ae5acaa627 sp:7ffd1cefe730 error:0 in atom[55ae58d86000+5024000]
[85655.479822] traps: atom[88866] trap int3 ip:558216a46627 sp:7fffb4e5f630 error:0 in atom[558214b22000+5024000]
[85657.797158] traps: atom[88893] trap int3 ip:55ba5f605627 sp:7ffdaaa43180 error:0 in atom[55ba5d6e1000+5024000]

Reproduces how often:

100% since 1.51.0

Versions

apm  2.5.0
npm  6.14.5
node 10.20.1 x64
atom 1.51.0
python 3.8.2
git 2.25.1

Additional Information

Running through gdb produces the following output:

Reading symbols from atom...
(No debugging symbols found in atom)
(gdb) r
Starting program: /snap/bin/atom 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7ffff5b2c700 (LWP 94112)]
[New Thread 0x7ffff532b700 (LWP 94113)]
[New Thread 0x7ffff4b2a700 (LWP 94114)]
[New Thread 0x7fffeffff700 (LWP 94115)]
[New Thread 0x7fffef7fe700 (LWP 94116)]
[New Thread 0x7fffeeffd700 (LWP 94117)]
[Thread 0x7fffef7fe700 (LWP 94116) exited]
[Thread 0x7fffeeffd700 (LWP 94117) exited]
[Thread 0x7fffeffff700 (LWP 94115) exited]
[Thread 0x7ffff4b2a700 (LWP 94114) exited]
[Thread 0x7ffff532b700 (LWP 94113) exited]
[Thread 0x7ffff5b2c700 (LWP 94112) exited]
process 94108 is executing new program: /snap/core/9804/usr/bin/snap
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7ffff7d3d700 (LWP 94118)]
[New Thread 0x7ffff753c700 (LWP 94119)]
[New Thread 0x7ffff6d3b700 (LWP 94120)]
[New Thread 0x7ffff653a700 (LWP 94121)]
[New Thread 0x7ffff5d39700 (LWP 94122)]
[New Thread 0x7ffff5538700 (LWP 94123)]
[Detaching after vfork from child process 94124]
[Thread 0x7ffff5d39700 (LWP 94122) exited]
[Thread 0x7ffff5538700 (LWP 94123) exited]
[Thread 0x7ffff653a700 (LWP 94121) exited]
[Thread 0x7ffff6d3b700 (LWP 94120) exited]
[Thread 0x7ffff753c700 (LWP 94119) exited]
[Thread 0x7ffff7d3d700 (LWP 94118) exited]
process 94108 is executing new program: /snap/core/9804/usr/lib/snapd/snap-confine
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
need to run as root or suid
--Type <RET> for more, q to quit, c to continue without paging--
[Inferior 1 (process 94108) exited with code 01]
(gdb) 

Somehow it is asking for root permission.

Hello! Could you please update and publish version 1.34.0 ? Thanks!

Atom releases: https://atom.io/releases

I have installed the 1.27.1 ubuntu snap and cli options are not working at all, atom --help, atom --wait etc. do nothing at all.

First reported here atom/atom#17437

I have installed atom as a snap package on Ubuntu 17.10 beta. After the install has finished it doesnt show up in the menus afterward. I am also unable to start via the terminal as well.

See also: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1718590

neofetch:
OS: Ubuntu 18.10 x86_64
Kernel: 4.19.0-041900-generic
Uptime: 24 mins
Packages: 2740 (dpkg), 50 (flatpak),
Shell: bash 4.4.19
Resolution: 1920x1200, 1680x1050
DE: GNOME 3.30.1
WM: GNOME Shell
WM Theme: Adwaita
Theme: Adwaita-dark [GTK2/3]
Icons: Yaru [GTK2/3]
Terminal: gnome-terminal
CPU: Intel i5-2400 (4) @ 3.400GHz
GPU: AMD ATI Radeon RX Vega 64
Memory: 2874MiB / 3925MiB

When I start Atom, I get this error message and it fails to fetch updates for the extensions etc:
/snap/atom/204/usr/share/atom/resources/app.asar.unpacked/node_modules/dugite/git/libexec/git-core/git-remote-https: /usr/lib/x86_64-linux-gnu/libcurl.so.4: version CURL_OPENSSL_3' not found (required by /snap/atom/204/usr/share/atom/resources/app.asar.unpacked/node_modules/dugite/git/libexec/git-core/git-remote-https) /snap/atom/204/usr/share/atom/resources/app.asar.unpacked/node_modules/dugite/git/libexec/git-core/git-remote-https: /snap/core/current/lib/x86_64-linux-gnu/libc.so.6: version GLIBC_2.25' not found (required by /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1)
/snap/atom/204/usr/share/atom/resources/app.asar.unpacked/node_modules/dugite/git/libexec/git-core/git-remote-https: /snap/core/current/lib/x86_64-linux-gnu/libc.so.6: version GLIBC_2.27' not found (required by /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2) /snap/atom/204/usr/share/atom/resources/app.asar.unpacked/node_modules/dugite/git/libexec/git-core/git-remote-https: /snap/core/current/lib/x86_64-linux-gnu/libc.so.6: version GLIBC_2.25' not found (required by /usr/lib/x86_64-linux-gnu/libgnutls.so.30)
/snap/atom/204/usr/share/atom/resources/app.asar.unpacked/node_modules/dugite/git/libexec/git-core/git-remote-https: /snap/core/current/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.26' not found (required by /usr/lib/x86_64-linux-gnu/libp11-kit.so.0)

Atom 1.28 released & 1.29 beta available: http://blog.atom.io/2018/06/21/atom-1-28.html

Is there any way to make these both available through the snap?

Thanks!

I installed Atom using

sudo snap install atom --classic

No .desktop was generated.

I have Lubuntu 18.04.2, snap 2.38.1, kernel 4.15.0-48-generic

PS: if possible, could you add it to Accessories and Programming menus?

As reported initially in #15, clicking on a URI in Atom (for instance a change log for a plugin) does not seem to be working properly. On Ubuntu 17.10, it spawns three consecutive Mozilla crash reports a short period of time after the click.

Apparently, the issue was confirmed for other Electron based snaps such as VSCode, so it may not be specific to Atom.

A snapshot of the issue is available here.

• OS: Ubuntu 19.10
• IBus version: 1.5.21
• Atom version: 1.45.0

When I switch to Chinese input mode (Intelligent Pinyin) and try to type Chinese into Atom 1.45.0 (snap version), it simply doesn't work.
When I type the letters into the window, it shall bring up the candidate list for me to pick words. But instead, the letters are directly typed into the window, but not Chinese characters.

Reported on LaunchPad: Link

Atom needs a contact field in the store. Probably should be https://github.com/snapcrafters/atom/issues.

Atom lacks an icon in the Unity Dash (has a question mark) and has the generic Electron icon in the Launcher.

$ snap list
atom                  1.20.0              36    snapcrafters  classic
core                  16-2.27.6           2898  canonical     core
$ snap version
snap    2.27.6
snapd   2.27.6
series  16
ubuntu  17.04
kernel  4.10.0-35-generic

When I try to run atom from the menu or the command line it simply fails to run. From the command line nothing happens at all, no output. This happens with Debian/Buster (10) and Debian/Sid (unstable).

$ snap info atom
name: atom
summary: A hackable text editor for the 21st Century.
publisher: Snapcrafters
store-url: https://snapcraft.io/atom
contact: https://github.com/snapcrafters/atom/issues
license: unset
description: |
Atom is a free and open source text editor that is modern,
approachable, and hackable to the core.

This snap is maintained by the Snapcrafters community, and is not necessarily endorsed or
officially maintained by the upstream developers.
commands:

• atom.apm
• atom
  snap-id: Lf1MF6tizzusVuA6l13ETyH5VDXxwA0D
  tracking: latest/stable
  refresh-date: 7 days ago, at 16:37 MST
  channels:
  latest/stable: 1.47.0 2020-05-21 (252) 236MB classic
  latest/candidate: ↑
  latest/beta: 1.47.0 2020-05-21 (252) 236MB classic
  latest/edge: 1.47.0 2020-05-21 (252) 236MB classic
  installed: 1.47.0 (252) 236MB classic

I recently started getting this error when trying to start atom:

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

I'm on OpenSUSE Tumbleweed which uses upstream soname for libpcre, so libpcre.so.1 is there. Honestly I can't quite trace how this only started happening recently and how it worked before. I found the debian bug report about incompatible soname for libpcre but it's nothing new and OpenSUSE has been using the upstream soname forever too.

In any case, would there be any chance of adding libpcre to the snap to avoid this?

Trying to start atom on Ubuntu 14.04 results in an error:

/snap/atom/53/usr/share/atom/atom: error while loading shared libraries: libsystemd.so.0: cannot open shared object file: No such file or directory

This seems to be caused by libdbus depending on libsystemd.so.0 which is not part of the core snap - and thus AFAIK should not be a dependency:

$ ldd /snap/atom/53/lib/x86_64-linux-gnu/libdbus-1.so.3
/snap/atom/53/lib/x86_64-linux-gnu/libdbus-1.so.3:
	[...]
	libsystemd.so.0 => not found
        [...]

Hi there. Running apm does nothing. Probably the apm output shouldn't be redirected and the process shouldn't be detached. This commit 78b5f36 changes the electron-launch file.

Atom is failing to build in 40c0d20:
https://gist.github.com/evandandrea/6611bb343c9948111e09c06da3b14f6b

sed: can't read usr/share/applications/atom.desktop: No such file or directory

I am not able to start up Atom editor today.
I tried the following commands:

atom --version
atom
atom .

All will not bring up atom editor, then I reinstall Atom editor through the Ubuntu Software (Snap).
It is still not working after reinstall.

The current version is
1.54.0
Ubuntu version
5.4.0-62-generic #70~18.04.1-Ubuntu

You can see from the snap store comments that the editor is not starting up after update.
I am using this editor as my daily driver, hope there is a quick fix for this soon.

I use ssh-agent in order to cache keys and avoid re-entering long passphrases within a session.

I…

1. Add a key to the agent, e.g. by using SSH from the command line.
2. Open the Atom snap.
3. Use a git remote operation, like fetch or push.

At this point I expect (from the behaviour of non-snap versions of Atom that I used previously):
4. Atom uses the ssh-agent cached key, without prompting me for a passphrase.

Instead:
4. Atom prompts me for the passphrase to unlock the key.

we also need to have the "apm" command

I updated my machine yesterday to Ubuntu 17.10 and suddenly I can no longer use the launcher to start Atom. It was installed as a snap and can be launched via the software app (proof that it is installed) but it will not show up when doing a search. I cannot set it as a favorite either.

The version of my Atom snap is 1.21.1 (updated 10/19/2017).

$ snap --version     
snap    2.28.5+17.10     
snapd   2.28.5+17.10     
series  16    
ubuntu  17.10     
kernel  4.13.0-16-generic 

There's a thread about this kind of bug on snapcore but I can't find/understand a solution there.

Apparently the main atom icon looks gone after the latest update, which happened on 2019-02-20, from 1.34.0 (rev 212) to 1.34.0 (rev 214).

Here it is when I'm searching in the available applications:

Here it is when loaded in the application sidebar:

$ snap info
snap version
snap    2.37.2
snapd   2.37.2
series  16
ubuntu  18.04
kernel  4.15.0-45-generic

When opening links from within atom (for example, the release notes link from Help -> About Atom -> Release Notes), it opens a separate Firefox profile to the standard Firefox installed with Ubuntu 20.04. This can be identified by missing addons, customisation, and Firefox signin all missing.

Expected behaviour: links are opened in the same Firefox profile as the rest of the desktop.

shows the two side by side - left is spawned from Atom, right is the standard Firefox as shipped with 20.04

Version tested: 1.18.0 snap rev 9

snap 2.27+git316.ef41c58ubuntu16.04.1
snapd 2.27+git316.ef41c58ubuntu16.04.1
series 16
ubuntu 17.04
kernel 4.10.0-32-generic

I have habit of using atom by spawning it from my bash shell in the directory of the project I want to hack on e.g.
my-code$ atom .

This worked well in the deb packaged atom and I've noticed also works in the snapped vscode for comparison. However with atom from the snap I get the following output and no return of control to the shell:

my-code$ atom .
bash: cannot set terminal process group (-1): Inappropriate ioctl for device
bash: no job control in this shell

I'm not sure if this is something that the confinement is blocking or possibly some behaviour created by a wrapper script.

Installed on Ubuntu 17.10 with snap install --edge atom to get version 1.21.

Running snap run atom produces the following output:

ln: failed to create symbolic link '/home/ghislain/snap/atom/42/.local/share/glib-2.0/schemas/org.gnome.desktop.a11y.applications.gschema.xml': File exists
ln: failed to create symbolic link '/home/ghislain/snap/atom/42/.local/share/glib-2.0/schemas/org.gnome.desktop.a11y.gschema.xml': File exists
ln: failed to create symbolic link '/home/ghislain/snap/atom/42/.local/share/glib-2.0/schemas/org.gnome.desktop.a11y.keyboard.gschema.xml': File exists
ln: failed to create symbolic link '/home/ghislain/snap/atom/42/.local/share/glib-2.0/schemas/org.gnome.desktop.a11y.magnifier.gschema.xml': File exists
ln: failed to create symbolic link '/home/ghislain/snap/atom/42/.local/share/glib-2.0/schemas/org.gnome.desktop.a11y.mouse.gschema.xml': File exists
ln: failed to create symbolic link '/home/ghislain/snap/atom/42/.local/share/glib-2.0/schemas/org.gnome.desktop.app-folders.gschema.xml': File exists
ln: failed to create symbolic link '/home/ghislain/snap/atom/42/.local/share/glib-2.0/schemas/org.gnome.desktop.background.gschema.xml': File exists
ln: failed to create symbolic link '/home/ghislain/snap/atom/42/.local/share/glib-2.0/schemas/org.gnome.desktop.datetime.gschema.xml': File exists
ln: failed to create symbolic link '/home/ghislain/snap/atom/42/.local/share/glib-2.0/schemas/org.gnome.desktop.default-applications.gschema.xml': File exists
ln: failed to create symbolic link '/home/ghislain/snap/atom/42/.local/share/glib-2.0/schemas/org.gnome.desktop.enums.xml': File exists
ln: failed to create symbolic link '/home/ghislain/snap/atom/42/.local/share/glib-2.0/schemas/org.gnome.desktop.input-sources.gschema.xml': File exists
ln: failed to create symbolic link '/home/ghislain/snap/atom/42/.local/share/glib-2.0/schemas/org.gnome.desktop.interface.gschema.xml': File exists
ln: failed to create symbolic link '/home/ghislain/snap/atom/42/.local/share/glib-2.0/schemas/org.gnome.desktop.lockdown.gschema.xml': File exists
ln: failed to create symbolic link '/home/ghislain/snap/atom/42/.local/share/glib-2.0/schemas/org.gnome.desktop.media-handling.gschema.xml': File exists
ln: failed to create symbolic link '/home/ghislain/snap/atom/42/.local/share/glib-2.0/schemas/org.gnome.desktop.notifications.gschema.xml': File exists
ln: failed to create symbolic link '/home/ghislain/snap/atom/42/.local/share/glib-2.0/schemas/org.gnome.desktop.peripherals.gschema.xml': File exists
ln: failed to create symbolic link '/home/ghislain/snap/atom/42/.local/share/glib-2.0/schemas/org.gnome.desktop.privacy.gschema.xml': File exists
ln: failed to create symbolic link '/home/ghislain/snap/atom/42/.local/share/glib-2.0/schemas/org.gnome.desktop.screensaver.gschema.xml': File exists
ln: failed to create symbolic link '/home/ghislain/snap/atom/42/.local/share/glib-2.0/schemas/org.gnome.desktop.search-providers.gschema.xml': File exists
ln: failed to create symbolic link '/home/ghislain/snap/atom/42/.local/share/glib-2.0/schemas/org.gnome.desktop.session.gschema.xml': File exists
ln: failed to create symbolic link '/home/ghislain/snap/atom/42/.local/share/glib-2.0/schemas/org.gnome.desktop.sound.gschema.xml': File exists
ln: failed to create symbolic link '/home/ghislain/snap/atom/42/.local/share/glib-2.0/schemas/org.gnome.desktop.thumbnail-cache.gschema.xml': File exists
ln: failed to create symbolic link '/home/ghislain/snap/atom/42/.local/share/glib-2.0/schemas/org.gnome.desktop.thumbnailers.gschema.xml': File exists
ln: failed to create symbolic link '/home/ghislain/snap/atom/42/.local/share/glib-2.0/schemas/org.gnome.desktop.wm.keybindings.gschema.xml': File exists
ln: failed to create symbolic link '/home/ghislain/snap/atom/42/.local/share/glib-2.0/schemas/org.gnome.desktop.wm.preferences.gschema.xml': File exists
ln: failed to create symbolic link '/home/ghislain/snap/atom/42/.local/share/glib-2.0/schemas/org.gnome.system.locale.gschema.xml': File exists
ln: failed to create symbolic link '/home/ghislain/snap/atom/42/.local/share/glib-2.0/schemas/org.gnome.system.location.gschema.xml': File exists
ln: failed to create symbolic link '/home/ghislain/snap/atom/42/.local/share/glib-2.0/schemas/org.gnome.system.proxy.gschema.xml': File exists
ln: failed to create symbolic link '/home/ghislain/snap/atom/42/.local/share/glib-2.0/schemas/org.gtk.Settings.ColorChooser.gschema.xml': File exists
ln: failed to create symbolic link '/home/ghislain/snap/atom/42/.local/share/glib-2.0/schemas/org.gtk.Settings.FileChooser.gschema.xml': File exists
/snap/atom/42/usr/sbin/update-icon-caches: 16: /snap/atom/42/usr/sbin/update-icon-caches: gtk-update-icon-cache-3.0: not found
WARNING: icon cache generation failed for /home/ghislain/snap/atom/42/.local/share/icons/Adwaita
/snap/atom/42/usr/sbin/update-icon-caches: 16: /snap/atom/42/usr/sbin/update-icon-caches: gtk-update-icon-cache-3.0: not found
WARNING: icon cache generation failed for /home/ghislain/snap/atom/42/.local/share/icons/DMZ-Black
/snap/atom/42/usr/sbin/update-icon-caches: 16: /snap/atom/42/usr/sbin/update-icon-caches: gtk-update-icon-cache-3.0: not found
WARNING: icon cache generation failed for /home/ghislain/snap/atom/42/.local/share/icons/DMZ-White
/snap/atom/42/usr/sbin/update-icon-caches: 16: /snap/atom/42/usr/sbin/update-icon-caches: gtk-update-icon-cache-3.0: not found
WARNING: icon cache generation failed for /home/ghislain/snap/atom/42/.local/share/icons/hicolor
/snap/atom/42/usr/sbin/update-icon-caches: 16: /snap/atom/42/usr/sbin/update-icon-caches: gtk-update-icon-cache-3.0: not found
WARNING: icon cache generation failed for /home/ghislain/snap/atom/42/.local/share/icons/Humanity
/snap/atom/42/usr/sbin/update-icon-caches: 16: /snap/atom/42/usr/sbin/update-icon-caches: gtk-update-icon-cache-3.0: not found
WARNING: icon cache generation failed for /home/ghislain/snap/atom/42/.local/share/icons/Humanity-Dark
/snap/atom/42/usr/sbin/update-icon-caches: 16: /snap/atom/42/usr/sbin/update-icon-caches: gtk-update-icon-cache-3.0: not found
WARNING: icon cache generation failed for /home/ghislain/snap/atom/42/.local/share/icons/LoginIcons
/snap/atom/42/usr/sbin/update-icon-caches: 16: /snap/atom/42/usr/sbin/update-icon-caches: gtk-update-icon-cache-3.0: not found
WARNING: icon cache generation failed for /home/ghislain/snap/atom/42/.local/share/icons/ubuntu-mono-dark
/snap/atom/42/usr/sbin/update-icon-caches: 16: /snap/atom/42/usr/sbin/update-icon-caches: gtk-update-icon-cache-3.0: not found
WARNING: icon cache generation failed for /home/ghislain/snap/atom/42/.local/share/icons/ubuntu-mono-light
/snap/atom/42/usr/sbin/update-icon-caches: 16: /snap/atom/42/usr/sbin/update-icon-caches: gtk-update-icon-cache-3.0: not found
WARNING: icon cache generation failed for /home/ghislain/snap/atom/42/.local/share/icons/HighContrast
Cannot load module /usr/lib/x86_64-linux-gnu/gtk-2.0/2.10.0/immodules/im-ibus.so: GModule (/usr/lib/x86_64-linux-gnu/gtk-2.0/2.10.0/immodules/im-ibus.so) initialization check failed: GLib version too old (micro mismatch)
/usr/lib/x86_64-linux-gnu/gtk-2.0/2.10.0/immodules/im-ibus.so does not export GTK+ IM module API: GModule (/usr/lib/x86_64-linux-gnu/gtk-2.0/2.10.0/immodules/im-ibus.so) initialization check failed: GLib version too old (micro mismatch)
bash: cannot set terminal process group (-1): Inappropriate ioctl for device
bash: no job control in this shell

Atom launches regardless, but I was wondering whether these warnings were expected.

Atom normally should use this directory as HOME:

/home/user_name/snap/atom

But atom (snap packaged version) use default user's home folder which is:

/home/user_name

Can you please fix this issue?

Thank you

Got following error while running github-desktop command after installation

/snap/github-desktop/63/app/github-desktop: error while loading shared libraries: libpcre.so.3: cannot open shared object file: No such file or directory

Hi, after installing it on bionic, it doesn't start (neither atom or apm).

Running apm --version from the snap directory (/snap/atom/current/usr/share/atom) returns the desired output. However, running atom from /snap/bin/atom returns this:

atom: error while loading shared libraries: libgconf-2.so.4: cannot open shared object file: No such file or directory

I know that this is probably caused by the way snap deals with libraries, and I probably shouldn't try to run atom from this directory, and run it via wrapper, but the bundled wrapper doesn't return anything, neither for atom or for apm).

Thanks in advance, regards.

When I try to open a project folder or file in atom, I usually don't see anything.

The folders and files failed to be visible

Is it possible to speed up the snap release cycle. Atom is actually stable at 1.21.0 but the stable snap is stuck on 1.20.0!

See https://discuss.atom.io/t/whenever-i-start-atom-it-opens-a-file-weird-file/75721 for more informations and also a way to fix it.

Happens on ubuntu 20.04 with latest atom/snap version, when I start the app from the user interface. Starting form command lines does not have the issue. Thanks a lot!

Fail to start atom from CLI on Fedora 27 with the error:
execv failed: No such file or directory

Please update the Atom snap to version 1.23.

I have an issue for Atom that only effects a snap install, or just me (I'm not sure). But the problem is resolved by using the official .deb instead. atom/atom#20937

Since updating to Atom 1.28.1 I keep getting logged out of Ubuntu, whenever I launch Atom. Installing it directly via the deb file fixed the issue, so it seems unique to the snap version.

Reploduction

1. Install this Snap.

   $ sudo snap install atom --classic
   

2. Running this Snap.

   $ snap run atom
   

3. Use input Japanese by ibus-mozc.

Matter

I can't input Hiragana, Alphabet instead.

Ideal

I want use input method engine on this Snap.

However, I think so Snappy not accepts input from input method engine.

Environment

• OS: Ubuntu 17.10 Artful
• Kernel: x86_64 Linux 4.13.0-17-lowlatency
• Shell: fish 2.6.0
• Desktop environment: Gnome Shell(Ubuntu default)
• CPU: Intel Core i5 M 450 @ 4x 2.4GHz
• RAM: 7650MiB

P.S.

I'm bat English too, but please forgive me.

1. install linter plugins: linter-pylint python-indent linter-pycodestyle
2. install linters: sudo apt install python3-pycodestyle pylint3
3. Open python file and press "save".

You get an error message saying that atom can't find pylint.

This makes the snap pretty much useless..

When trying to search for packages in Atom

When running apm manually

$ apm
/snap/atom/109/usr/bin/apm: line 63:  8312 Segmentation fault      (core dumped) "$binDir/$nodeBin" "$cliPath" "$@

I recently discovered that the go-plug plugin doesn't work with the snap-installed version of atom but works fine when atom is installed via deb.

I filed a bug against go-plus, initially thinking that something in the plugin was broken.

I switched back to the deb version, though, and the plugin resumed working as expected.

The relevant snaps:

$ snap list
Name        Version                 Rev   Tracking  Developer     Notes
atom        1.27.2                  159   stable    snapcrafters  classic
core        16-2.33                 4830  stable    canonical     core
go          1.10.3                  2130  stable    mwhudson      classic

I'm running stock Ubuntu 18.04. When using the Atom snap, I use the system "open file" dialog (Ctrl+O).

In this dialog, all the icons show as missing; see the screenshot.

Reproduce

1. Open a project
2. Try to remove a file, either with "delete" key or from Atom's right click menu

Outcome:
the file isn't deleted

Snap
snap 2.27.6+17.10
snapd 2.27.6+17.10
series 16
ubuntu 17.10
kernel 4.13.0-12-generic

Atom
1.20.0

To implement the "BIG-REQUESTS' hack for Remote Access, libxcb.so.1.1.0 needs to be edited. This library is contained in the snap, so it can't be edited. Hence, the snap-installed atom will not run using windows RDP and xfce.
$ snap run atom
Xlib: extension "XInputExtension" missing on display ":10.0".
Xlib: extension "XInputExtension" missing on display ":10.0".
Xlib: extension "XInputExtension" missing on display ":10.0".
$

Open a terminal tab:

andreas@obelix:~/work/grants_team_setup$ sudo
sudo: effective uid is not 0, is /usr/bin/sudo on a file system with the 'nosuid' option set or an NFS file system without root privileges?

Notice that the output of capsh --print inside and outside Atom are the same, stat / and stat /usr/bin/stat return the same inode.