I am using latest Ubuntu version today (23.10 mantic) and it is not
working. How is possible that something so basic as Ubuntu remote
desktop with vnc just does not work or take so long. I am feed up of
asking google. I remember years ago I just desist of doing a remote
connection using vnc, cause
So, this won't be fixed until https://gitlab.gnome.org/GNOME/gnome-
shell/-/issues/6565 is resolved? Or is it fixed in newer Ubuntu
releases? (On 22.04 I am experiencing the problem quite often, wondering
if there is any point in upgrading)
--
You received this bug notification because you are a
so...what's the fix?
My Bitwarden is also acting up now
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/2011806
Title:
[lunar] Snaps don't launch due to cgroup issue
Status in
@Jonas: If KDE is launching apps in the same way gnome-shell was, it is
inherently racy. It needs to make sure the child process is in the new
cgroup before executing the application.
Doing the cgroup move after the app is already running causes problems
if the application itself wants to
This is also happening for me. It takes multiple tries to launch some of
my snap applications like Discord, Zoom, and Slack from my Application
Menu. I don't have this problem for IntelliJ Ultimate. It seemed like a
lot of the applications that are having this issue rely on core22, but I
don't
Operating System: Kubuntu 23.10
KDE Plasma Version: 5.27.9
KDE Frameworks Version: 5.112.0
Qt Version: 5.15.10
Kernel Version: 6.5.0-10-generic (64-bit)
Graphics Platform: X11
Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor
Memory: 62.7 GiB of RAM
Graphics Processor: AMD Radeon RX 6900 XT
When I launch Thunderbird
Nov 14 20:12:55 systemd[9205]: Started
snap.thunderbird.thunderbird-218c47bb-9cdf-4585-8487-1e76547933b3.scope.
Nov 14 20:12:55 systemd[9205]: Started
app-thunderbird_thunderbird-4758a597c99d427f91814da5b05c365a.scope -
Thunderbird Mail - Mail Client.
Nov 14 20:12:55
Any updates with this one?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/2011806
Title:
[lunar] Snaps don't launch due to cgroup issue
Status in GNOME Shell:
New
Status in
Can confirm it affects KDE users as well - discovered this while trying
to launch Discord for the first time in a long time. The snap will only
launch from a terminal, not the shell ("not a snap cgroup error").
Flatpak version launches from shell just fine.
--
You received this bug notification
Launchpad has imported 8 comments from the remote bug at
https://bugs.kde.org/show_bug.cgi?id=423756.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
** Also affects: kde-baseapps via
https://bugs.kde.org/show_bug.cgi?id=423756
Importance: Unknown
Status: Unknown
** Changed in: snapd (Ubuntu)
Status: Confirmed => Opinion
--
You received this bug notification because you are a member of Desktop
Packages, which is
I did a search through the KDE bug tracker, and it looks like someone
reported the same root problem back in 2020:
https://bugs.kde.org/show_bug.cgi?id=423756
** Bug watch added: KDE Bug Tracking System #423756
https://bugs.kde.org/show_bug.cgi?id=423756
--
You received this bug
> There is no "snapd tracker".
Yeah, I mean not part of the daemon itself, I was referring to this piece of
code:
- https://github.com/snapcore/snapd/blob/master/sandbox/cgroup/tracking.go
But I see why it can't adjust things itself.
Thanks for the report upstream.
** Also affects:
** Changed in: gnome-shell
Status: Unknown => New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/2011806
Title:
[lunar] Snaps don't launch due to cgroup issue
Status in
I've filed https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6565
upstream to cover the gnome-shell problem.
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #6565
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6565
** Also affects: gnome-shell via
> So, I feel snapd tracker should somewhat be able to track that an app
> changed its cgroup and move it back to what it belongs, but as discussed
> in https://github.com/systemd/systemd/issues/26925 there's nothing
> telling us that right now.
There is no "snapd tracker". It's the "snap run"
The black window is bug 1987976.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/2011806
Title:
[lunar] Snaps don't launch due to cgroup issue
Status in gnome-shell package in
I got it too but definitely another issue.
Il mar 28 mar 2023, 19:40 Gunnar Hjalmarsson <2011...@bugs.launchpad.net>
ha scritto:
> I still have an issue. Not sure if it is related.
>
> When clicking the Firefox icon in the dock, a completely black window
> opens. Then I can close it and try
Same here.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/2011806
Title:
[lunar] Snaps don't launch due to cgroup issue
Status in gnome-shell package in Ubuntu:
Fix Released
I still have an issue. Not sure if it is related.
When clicking the Firefox icon in the dock, a completely black window
opens. Then I can close it and try again, and the second time it works
as expected. This repeats itself in each session.
--
You received this bug notification because you are
Fix works for me (after reboot/reload Gnome), fast job, thanks! :)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/2011806
Title:
[lunar] Snaps don't launch due to cgroup issue
This bug was fixed in the package gnome-shell - 44.0-2ubuntu2
---
gnome-shell (44.0-2ubuntu2) lunar; urgency=medium
* debian/patches: Cherry-pick more upstream fixes from stable branch
* debian/patches: Give more priority to desktop files matching startup-wm
class (LP:
The workaround that is coming in gnome-shell is enough to handle the
normal snap cases, however that's not to be considered a proper
solution.
The usage of `ChildSetupFunc` is not easily doable without some refactor
in the shell that I'm not keen to do for something that is not likely
going to be
** Changed in: gnome-shell (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/2011806
Title:
[lunar] Snaps don't launch due to
** Changed in: snapd (Ubuntu)
Status: Won't Fix => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/2011806
Title:
[lunar] Snaps don't launch due to cgroup issue
** Changed in: kio (Ubuntu)
Importance: Undecided => Critical
** Changed in: snapd (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
** Also affects: snapd (Ubuntu)
Importance: Undecided
Status: New
** Changed in: snapd (Ubuntu)
Status: New => Won't Fix
** Also affects: kio (Ubuntu)
Importance: Undecided
Status: New
** Changed in: kio (Ubuntu)
Status: New => Confirmed
--
You received this
Another idea for how to synchronise the StartTransientUnit call without
resorting to passing pipe file descriptors to the child: we could simply
have the child_setup_func call kill(getpid(), SIGSTOP). The parent
process can now do the cgroup move at its leisure, and then send a
SIGCONT to the
@Batuhan: it's different code, but looks to be the same type of problem:
https://github.com/KDE/kio/blob/5bda428992cbd168fc1898661d80a089a8217449/src/gui/systemd/scopedprocessrunner.cpp#L13-L41
It's moving the process to a new cgroup after the application has
started executing (so happens
We're also tracking a crash in bug 2012839 (private for now) which might
explain similar issues seen outside of gnome-shell.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/2011806
Same issue here, I have never seen any snaps opening from the dash (both
Firefox and Brave) and they both put out a cgroup error in the syslog. Starting
from terminal works and without the cgroup error in the log.
Maybe also noticable, I see snap core20 and core22 both installed and cannot
> I think this is down to a race condition between gnome-shell and
snapd.
As someone who is using Kubuntu where gnome-shell is not present, I'd
like to mention that I'm also experiencing the same exact issue. Not
sure if there is a similar race condition is present on a KDE
application in Kubuntu
Not super how much it helps, but I have the same exact issue on two
different systems (one using Kubuntu 22.10 -- with a mainline kernel of
6.0 and the other one using Kubuntu 23.04 [upgraded from 22.10]
development branch with a mainline kernel of 6.2.7).
This specifically happens when krunner
Same problem here on Ubuntu 23.04 with wayland on AMD Ryzen 6850. Most
snaps only start occasionally from dash icon. Works every time from
console.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
** Changed in: gnome-shell (Ubuntu)
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
** Changed in: gnome-shell (Ubuntu)
Status: Confirmed => In Progress
** No longer affects: snapd (Ubuntu)
** Tags added: dt-1154
** Changed in: gnome-shell (Ubuntu)
Milestone: None =>
** Tags added: lunar
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/2011806
Title:
[lunar] Snaps don't launch due to cgroup issue
Status in gnome-shell package in Ubuntu:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-shell (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
Sharing debug details from jamesh
When starting snap applications via the shell, log messages like the following
are produced:
Mar 21 18:07:49 MGLT-Ubuntu chromium_chromium.desktop[13099]:
/user.slice/user-1000.slice/user@1000.service/app.slice/app-gnome-chromium_chromium-13099.scope
is not a
38 matches
Mail list logo