I see the same as Stephen in c46: snap-Firefox fails to start locally,
_sometimes_ – the error is not readily reproducable.
When it happens, the following errors appear in ~/.xsession-errors:
/user.slice/user-1000.slice/user@1000.service/app.slice/app-firefox_firefox-0403ae5e70f94aa6ace2ebfdfb404
On Jammy, I have installed the following packages from jammy-proposed:
- libkf5su-data (5.92.0-0ubuntu1.1)
- libkf5su5:amd64 (5.92.0-0ubuntu1.1)
- libkf5su-bin (5.92.0-0ubuntu1.1)
I have performed the following tests, in accordance with the bug description:
- launching KSystemLog from the K Menu
-
Note that with kdesu fixed, the hotfix to kubuntu-settings by Erich
Eickmeyer can possibly be reverted, removing the ugly xterm workaround
when launching Driver Manager from Kubuntu Settings.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
As noted in #57, this bug _does_ occur on standard desktop installs,
such as mine (updated from 21.10 to 22.04, thus taking firefox from .deb
to snap).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https:/
Unfortunately, I must disagree with Tim in #55: This problem affects me
on a standard desktop, with absolutely no remote access involved. I'm
running 22.04, which I updated from 21.10 with KDE Plasma, and firefox
intermittently(!) will not start, spouting the "not a snap cgroup" error
message (logg
I'd like to re-interate that I use a regular Kubuntu installation,
freshly installed as 21.10 and later upgraded to 22.04 (a few months
after 22.04 was released). During the upgrade to 22.04, the dpkg firefox
was replaced by the snap firefox. That's when the problem appeared.
--
You received this
6 matches
Mail list logo
