[Desktop-packages] [Bug 1808959] Re: [snap] core18-based snap fails to start on Solus/fedora29

2019-09-20 Thread Zygmunt Krynicki
In absense of test systems to check this I'm marking this as incomplete. If the reporter can confirm the issue is fixed it would help us with the bug tracking. ** Changed in: snapd Status: New => Incomplete -- You received this bug notification because you are a member of Desktop

[Desktop-packages] [Bug 1808959] Re: [snap] core18-based snap fails to start on Solus/fedora29

2019-06-06 Thread Olivier Tilloy
Just tested again in a fully up-to-date Fedora 29 VM, and the chromium snap from the candidate channel now starts and works as expected. I don't have a Solus VM handy, but given the last comment, I'm going to assume it's fixed there too. Tentatively marking fixed. ** Changed in: chromium-browser

[Desktop-packages] [Bug 1808959] Re: [snap] core18-based snap fails to start on Solus/fedora29

2019-03-30 Thread Girtablulu
I just found the issue with our solus snapd package, I had to build snap-exec static and after this chromium snap starts again. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu.

[Desktop-packages] [Bug 1808959] Re: [snap] core18-based snap fails to start on Solus

2019-03-15 Thread Olivier Tilloy
Fully up-to-date Fedora 29 VM, the chromium snap still fails to launch with the same error. ** Also affects: snapd Importance: Undecided Status: New ** Summary changed: - [snap] core18-based snap fails to start on Solus + [snap] core18-based snap fails to start on Solus/fedora29 --

[Desktop-packages] [Bug 1808959] Re: [snap] core18-based snap fails to start on Solus

2019-02-18 Thread Cody Hodges
I am experiencing this same issue on Fedora 29 after installing the Krita snap. It is using core18 also. krita: execl failed: No such file or directory child exited with status 1 snap2.37.2-1.fc29 snapd 2.37.2-1.fc29 series 16 fedora 29 kernel 4.20.8-200.fc29.x86_64 core18 18

[Desktop-packages] [Bug 1808959] Re: [snap] core18-based snap fails to start on Solus

2019-02-12 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: chromium-browser (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu.

[Desktop-packages] [Bug 1808959] Re: [snap] core18-based snap fails to start on Solus

2019-02-12 Thread Henrik Steen
FYI, this is still an issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1808959 Title: [snap] core18-based snap fails to start on Solus Status in chromium-browser

[Desktop-packages] [Bug 1808959] Re: [snap] core18-based snap fails to start on Solus

2019-01-09 Thread Olivier Tilloy
The core18 version of the chromium snap is the only supported and maintained version now. The stable/core16 channel is provided only as a short-term workaround for a bug that should be addressed in snapd on Fedora 29 / Solus. -- You received this bug notification because you are a member of

[Desktop-packages] [Bug 1808959] Re: [snap] core18-based snap fails to start on Solus

2019-01-07 Thread Henrik Steen
I'm also trying to run the Chromium snap on Solus, I get the same error. I don't think the solution to use core 16 is right, due to the old Chromium version that comes with it. Is it possible to maintain the core 16 version of Chromium as well? -- You received this bug notification because you