Came here after using nomachine (remote desktop client) to run on a
headless ubuntu server with gnome on x11.
nomachine starts its own display manager. I can connect and use gnome
remotely, all gui apps work fine, I can take screenshots, or view them
in shotwell. Firefox and Chrome refuse to launc
So I had this same issue on two machines that are running Ubuntu 22.04.4
LTS Desktop with more or less the same software installed.
I run `sudo apt update && sudo apt full-upgrade -y && sudo apt
autoremove -y && sudo apt autoclean && sudo apt clean && sudo snap
refresh` when I haven't been on any
** Tags removed: rls-nn-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951491
Title:
Can't run snaps: .slice/session-1.scope is not a snap cgroup
To manage notifications about this bug go
Thanks for the bug report, unfortunately this has become quite
convoluted and I've identified at least 3 different strands of
discussion in here that are not related.
Some stuff, like "runuser" in a cron job is clearly never going to work,
but I don't know how the other two instances - sessions wi
** Changed in: snapd (Ubuntu)
Importance: Undecided => High
** Tags added: rls-nn-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951491
Title:
Can't run snaps: .slice/session-1.scope is
Encountered this problem while attempting to run a confined snap from a
cronjob.
All that is wrong actually is that the systemd user session has not been
properly setup.
I had to install dbus-user-session and then make sure the
/run/user/../bus was initialized by for example runuser -u user
/bin/
I All,
I can confirm same problem with Ubuntu MATE 22.04 running Xtightvnc
session.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951491
Title:
Can't run snaps: .slice/session-1.scope is not a sna
It has been reported also for Debian 11
https://forum.snapcraft.io/t/non-classic-snaps-fail-to-load-due-to-
cgroup-apparmor-issue/28756
looking at `tail -f /var/log/syslog` I see almost the same message
May 13 08:31:15 iltoshibo dbus-daemon[15558]: [session uid=1000 pid=15556]
Activating servic
Same problem with both 22.04 Server and Ubuntu Mate 22.04.
All the confined GUI snaps have this problem and thus can't run.
First, I encountered running MATE desktop via X2Go Server.
Then I tried to see if using xRDP would work. No still problem persists whether
I use xRDP or X2Go
Left unable to r
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951491
Title:
Ca
Same problem in 21.10 with Firefox, Chromium, and Waterfox Classic. All
have suddenly stopped working with error
/user.slice/user-1000.slice/session-30.scope is not a snap cgroup
I'm running MATE inside X2Go
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
FWIW systemd --user is expected to have been started as part of your
session. This is supposed to be fully automatic. I don't think you can
start it yourself, as it's up to systemd/logind to properly start the
process and move it to the right cgroup. I've added systemd to the bug
report, so maybe t
$ systemd --user
Failed to create /user.slice/user-1000.slice/session-1.scope/init.scope control
group: Permission denied
Failed to allocate manager object: Permission denied
that's it.
Still:
SNAPD_DEBUG=1 snap run chromium
2022/04/08 09:33:56.722937 tool_linux.go:204: DEBUG: restarting into
ah, I forgot about usb headset, I saw pulseaudio relay on systemd
--user, maybe via dbus, so starting with headset could has triggered the
start of systemd --user?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
headset? umh, well I found that I have no `systemd --user` running
(thank to Maciej Borzecki comment in #1956942), then I run it in a
terminal, and this fixed the problem.
I started session by `startx`, like enen above, I have no idea about gdm
session, but I can guess systemd --user is started th
I ran into this problem today when i had my headset attached via usb on
startup. the problem disappeared, when i restarted without the usb
headset attached to the notebook?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
i ran into this error today when i ran my X server through startx rather
than gdm.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951491
Title:
Can't run snaps: .slice/session-1.scope is not a snap
No, it just means that the journal is not collecting any user session
logs. I'm afraid this is beyond snapd scope at this point. Perhaps you
can try to make you openbox session to be more like what GNOME and KDE
set up, that is with systemd user instance that can be accessed via
dbus. I don't know
$ journalctl --user
No journal files were found.
-- No entries --
Does it need to be configured to show snap information somehow?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951491
Title:
Can't
Ok, so the logs you attached earlier are:
2021/12/03 15:21:45.540312 tracking.go:45: DEBUG: creating transient scope
snap.chromium.chromium
2021/12/03 15:21:45.543273 tracking.go:185: DEBUG: using session bus
2021/12/03 15:21:45.547127 tracking.go:290: DEBUG: StartTransientUnit failed
with "org.
Sure. Do you want the full output (162 lines)? Or maybe just the output
of systemctl --user | grep snap, or something? I'm not sure what you're
looking for.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
Can you run `systemctl --user`? Does it work at all?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951491
Title:
Can't run snaps: .slice/session-1.scope is not a snap cgroup
To manage notification
$DBUS_SESSION_BUS_ADDRESS is:
unix:abstract=/tmp/dbus-rBFSkTtKSd,guid=9839721c1a52b5cd5e2e0d6961ae292d
ls -l of that gives No such file or directory
My window manager is openbox, started with /usr/bin/dbus-launch --exit-
with-session openbox
--
You received this bug notification because you ar
Snapd needs to talk to systemd user instance to setup a scope for the
snap. This is done over a session bus.
Is DBUS_SESSION_BUS_ADDRESS set in your environment? Run `echo
$DBUS_SESSION_BUS_ADDRESS`, the output should be like
`unix:path=/run/user/NNN/bus` (where NNN is your uid). Can you then run
** Attachment added: "recent_updates.txt"
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1951491/+attachment/5545306/+files/recent_updates.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/19
I have the same issue, but chromium was working on impish prior to this
issue (last boot was 11/18, so about 20 days uptime). SNAPD_DEBUG=1
attached. Dbus daemon appears to be running and /run/user/{id}/bus
exists.
I don't see an update that could have caused this, and I haven't really
made any sy
** Changed in: snapd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951491
Title:
Can't run snaps: .slice/session-1.scope is not a snap cgroup
To manage no
Can you run `SNAPD_DEBUG=1 snap run firefox` and attach the output?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951491
Title:
Can't run snaps: .slice/session-1.scope is not a snap cgroup
To mana
** Also affects: snapd (Debian)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951491
Title:
Can't run snaps: .slice/session-1.scope is not a snap cgroup
29 matches
Mail list logo
