Skip to content

[Bug]: SELinux flood when desktop app is open #1759

Description

@DarkGhostHunter

Before submitting

  • I have searched existing issues to confirm this is not a duplicate
  • I am running the latest version of Devsy

What happened?

When opening Debsy, SELinux denials flood the system and makes the CPU spike until the system is unresponsive.

What did you expect to happen instead?

To not do that.

Steps to reproduce

  1. Download Devsy as AppImage
  2. Add Podman as provider
  3. Create a dev container
  4. Exit
  5. Start Devsy desktop
  6. See the SELinux burn the CPU

devcontainer.json

Error output / logs

How often does this happen?

Every time

Operating system

Linux

Linux distribution (if applicable)

Fedora 44 Atomic GNOME 50 (Bluefin)

Architecture

AMD64

Desktop app or CLI?

Desktop app

Devsy version

1.26.0

Devsy provider

Docker

Provider version

No response

Screenshots

No response

Anything else?

Gonna copy-paste what the AI said:

Root cause

The chain:

  1. Devsy is an Electron AppImage — FUSE-mounted at /tmp/.mount_devsy.*, so its files are labeled fusefs_t.
  2. Devsy runs its agent inside a rootless podman container (/run/podman-init … internal agent container daemon), and podman uses passt/pasta for networking, which runs in the confined pasta_t domain.
  3. Devsy's daemon spawns podman without closing inherited file descriptors, so pasta ends up holding Electron's fds. pasta probes inherited fds (read/write to identify them) and touches paths from its parent — hence denials on fusefs_t ({ search } on the AppImage mount) and on Devsy's own Chromium caches ({ read write } on ~/.config/devsy-desktop/DawnWebGPUCache/*, config_home_t) — e.g. audit[313238]: AVC denied { read write } comm="pasta" path="…/DawnWebGPUCache/data_2" scontext=unconfined_u:unconfined_r:pasta_t.
  4. Every denial goes to audit → setroubleshootd → analysis + journal/DBus notification per event. Python, no backpressure → one thread spins (currently 52% overall, 100% on thread 266712; 260k context switches and climbing).

SELinux is Enforcing, so nothing is broken besides CPU burn and journal spam — but Devsy's container networking and its own config access are actually being denied.

Activity

  1. DarkGhostHunter commented on Nov 4, 2026

    @DarkGhostHunter
    Author

    Superseded by #1771

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions