Slack and Steam snaps

Support and Help
1

Hi everyone,

I’ve been having some trouble lately with two Snaps on Resolute Beta: Slack and Steam.

In both cases, I am unable to click on any buttons within the menu bar. Additionally, in Slack, the right-click context menu (for copying and pasting) isn’t working at all.

What I’ve tested so far:

I tried the Slack .deb version, and it works perfectly fine. I checked on my laptop, and everything seems to be working correctly there in 25.10.

Is anyone else experiencing this issue? I want to make sure it’s not just me before I submit an official bug report through the proper channels.

Thanks!

2

Snaps are independent of any Ubuntu version (like 26.04), so I have moved your support question out of the 26.04 testing area.

3 Likes
3

I’m seeing similar regressions on the Resolute 26.04 daily builds, because I have tried Ubuntu 26.04 daily build on my laptop. This appears to be an input-grabbing conflict between Wayland and the current Snapd confinement on GNOME 49/50. Since the deb works, it’s likely a sandbox communication issue. A few workarounds to try:

  • Switch to Xorg: Log out and select “Ubuntu on Xorg” from the gear icon. This usually restores menu functionality immediately.
  • Steam Fix: Go to Settings > Interface and toggle “Enable context focus compatibility mode.”
  • Snap Refresh: Try switching to the edge channel to see if a patch is pushed: sudo snap refresh slack --edge.

If the issue persists on Xorg, please grab your logs via journalctl -f and attach them to a bug report on Launchpad under the snapd package.

1 Like
4

When I first moved to Ubuntu I originally ran the SNAP version of steam only to later replace it with the deb package as I found that much more stable when moving releases.

In regards to Slack I have only used it as a PWA and not any of the standalone apps, I know it may be annoying but it could potentially get you through until a new version is released

5

In this case, I do think it’s an issue with 26.04. I mean, I checked on another machine running 25.10 and didn’t run into that problem there. The Steam and Slack Snaps haven’t been updated in several months, so I believe the error has to do with how they integrate into the new version of Ubuntu.

6

In my case, Slack doesn’t start at all - it shows no UI and the process just quits immediately. Started to happen immediately after upgrade to Ubuntu 26.04. journalctl shows some “denied” messages:

huhti 16 10:06:06 mavi-fw kernel: audit: type=1326 audit(1776323166.224:557): auid=1000 uid=1000 gid=1000 ses=3 subj=snap.slack.slack pid=214212 comm=“slack” exe=“/snap/slack/224/usr/lib/slack/slack” sig=0 arch=c000003e syscall=330 compat=0 ip=0x71a807ab927b code=0x50000
huhti 16 10:06:06 mavi-fw kernel: audit: type=1326 audit(1776323166.224:556): auid=1000 uid=1000 gid=1000 ses=3 subj=snap.slack.slack pid=214211 comm=“slack” exe=“/snap/slack/224/usr/lib/slack/slack” sig=0 arch=c000003e syscall=330 compat=0 ip=0x74c7ebe3927b code=0x50000
huhti 16 10:06:06 mavi-fw kernel: audit: type=1326 audit(1776323166.227:558): auid=1000 uid=1000 gid=1000 ses=3 subj=snap.slack.slack pid=214182 comm=“slack” exe=“/snap/slack/224/usr/lib/slack/slack” sig=0 arch=c000003e syscall=425 compat=0 ip=0x747f46da19ad code=0x50000
huhti 16 10:06:06 mavi-fw kernel: audit: type=1326 audit(1776323166.250:559): auid=1000 uid=1000 gid=1000 ses=3 subj=snap.slack.slack pid=214182 comm=“slack” exe=“/snap/slack/224/usr/lib/slack/slack” sig=0 arch=c000003e syscall=425 compat=0 ip=0x747f46da19ad code=0x50000
huhti 16 10:06:06 mavi-fw kernel: audit: type=1326 audit(1776323166.250:560): auid=1000 uid=1000 gid=1000 ses=3 subj=snap.slack.slack pid=214182 comm=“DelayedTaskSche” exe=“/snap/slack/224/usr/lib/slack/slack” sig=0 arch=c000003e syscall=425 compat=0 ip=0x747f46da19ad code=0x50000
huhti 16 10:06:06 mavi-fw kernel: audit: type=1326 audit(1776323166.440:561): auid=1000 uid=1000 gid=1000 ses=3 subj=snap.slack.slack pid=214182 comm=“slack” exe=“/snap/slack/224/usr/lib/slack/slack” sig=0 arch=c000003e syscall=92 compat=0 ip=0x747f46d985db code=0x50000
huhti 16 10:06:06 mavi-fw kernel: audit: type=1400 audit(1776323166.552:562): apparmor=“DENIED” operation=“open” class=“file” profile=“snap.slack.slack” name=“/etc/” pid=214182 comm=“libuv-worker” requested_mask=“r” denied_mask=“r” fsuid=1000 ouid=0
huhti 16 10:06:06 mavi-fw kernel: audit: type=1326 audit(1776323166.567:563): auid=1000 uid=1000 gid=1000 ses=3 subj=snap.slack.slack pid=214182 comm=“slack” exe=“/snap/slack/224/usr/lib/slack/slack” sig=0 arch=c000003e syscall=92 compat=0 ip=0x747f46d985db code=0x50000
huhti 16 10:06:06 mavi-fw kernel: audit: type=1400 audit(1776323166.577:564): apparmor=“DENIED” operation=“open” class=“file” profile=“snap.slack.slack” name=“/proc/214233/mem” pid=214233 comm=“slack” requested_mask=“r” denied_mask=“r” fsuid=1000 ouid=1000
huhti 16 10:06:06 mavi-fw kernel: audit: type=1400 audit(1776323166.577:565): apparmor=“DENIED” operation=“open” class=“file” profile=“snap.slack.slack” name=“/proc/214233/mem” pid=214233 comm=“slack” requested_mask=“r” denied_mask=“r” fsuid=1000 ouid=1000
huhti 16 10:06:07 mavi-fw systemd\[8541\]: snap.slack.slack-8ca1c793-d52b-4497-baf9-93abcc5cca09.scope: Consumed 862ms CPU time over 957ms wall clock time, 107.5M memory peak.

Slack installed via snap: latest/stable channel, 4.47.69 2026-04-14 (224)

7

I believe Slack is to blame here. I had to perform a sudo revert slack. If it’s a fresh install and you don’t have a backup copy of Slack, you can use this command:

sudo snap refresh slack --revision=216
1 Like
8

Thanks, this helped out. It started with this version.

I tried even their latest/beta 4.49.89 (4/22/2026) without success.

I tried to see if there was any logs, but apparently I don’t know how to check them correctly. I tried journalctl -u snap.* -f and then started Slack and got no logs during the monitoring session while starting Slack :man_shrugging:

9

I haven’t tested slack, but I did run into the same issues on the steam snap, and again, after installing the official deb, it worked fine. I tried uninstalling steam and installing the snap package again, and after using the one setting I could use (which was the steam context focus compatibility mode), it still remained nonfunctional. I think this is, unfortunately, a snap package exclusive issue.

10

I would recommend contacting the maintainers and filing a bug report.

snap info [packagename] should have a contact field with relevant information.

11

They are already working on it:

2 Likes
12

For anyone else needing help with Slack specifically, I have (in the past) found their standard support people to be mega-friendly, knowledgeable and fast at turning around support tickets. Whether for the snap or any other package, worth a try.

2 Likes
13

This topic was automatically closed after 29 days. New replies are no longer allowed.