Bug 1716397 - Installing snap breaks the whole system
Summary: Installing snap breaks the whole system
Keywords:
Status: CLOSED DUPLICATE of bug 1708991
Alias: None
Product: Fedora
Classification: Fedora
Component: snapd
Version: 30
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
Assignee: Maciek Borzecki
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-06-03 12:20 UTC by Cristian Morales Vega
Modified: 2019-06-04 06:21 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-06-04 06:21:08 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Cristian Morales Vega 2019-06-03 12:20:40 UTC 
I have been using a clean Fedora 30 install, with the Visual Studio Code snap package, without problems for a while.
But with today's snap update the whole system is broken. Lots of services fail to start with errors like

Jun 03 13:10:22 DESKTOP-CS3GGJG systemd[3391]: systemd-hostnamed.service: Failed to set up mount namespacing: Permission denied
Jun 03 13:10:22 DESKTOP-CS3GGJG systemd[3391]: systemd-hostnamed.service: Failed at step NAMESPACE spawning /usr/lib/systemd/systemd-hostnamed: Permission denied
Jun 03 13:10:22 DESKTOP-CS3GGJG systemd[1]: systemd-hostnamed.service: Main process exited, code=exited, status=226/NAMESPACE


"sudo dnf remove snapd" solves the issue. "sudo dnf install snapd" doesn't bring back the issue by itself. But the second I install again the Visual Studio Code snap package the whole system breaks.
Comment 1 Jan Schmitt 2019-06-03 17:13:34 UTC 
Same here. My DE starts lagging or freezes and every command I execute with sudo takes ages before I get an password prompt...
all happening since the last snapd update...
Comment 2 Neal Gompa 2019-06-04 02:06:49 UTC 
Maciek, you wrote this integration, can you please take a look at it?
Comment 3 Maciek Borzecki 2019-06-04 06:21:08 UTC 

*** This bug has been marked as a duplicate of bug 1708991 ***
Note You need to log in before you can comment on or make changes to this bug.