Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Various Flatpak test failures due to fusermount error #5027

Closed
4 tasks done
TheComputerGuy96 opened this issue Aug 3, 2022 · 2 comments
Closed
4 tasks done
Labels

Comments

@TheComputerGuy96
Copy link

Checklist

  • I agree to follow the Code of Conduct that this project adheres to.
  • I have searched the issue tracker for a bug that matches the one I want to file, without success.
  • If this is an issue with a particular app, I have tried filing it in the appropriate issue tracker for the app (e.g. under https://github.com/flathub/) and determined that it is an issue with Flatpak itself.
  • This issue is not a report of a security vulnerability (see here if you need to report a security issue).

Flatpak version

1.12.7

What Linux distribution are you using?

Arch Linux

Linux distribution version

No response

What architecture are you using?

x86_64

How to reproduce

  1. Have an up-to-date Arch Linux install ready using the Arch install guide
  2. Install all the dependencies listed in the Flatpak PKGBUILD
  3. Clone the Flatpak Arch package build files
  4. Run makepkg -s in the directory with the build files

(these instructions are bad, but I want to quickly post this issue)

Expected Behavior

There should be no test failures

Actual Behavior

There are ~26 test failures because of this error:

+ fusermount -u /tmp/test-flatpak-iyk1Fm/runtime/doc
fusermount: entry for /tmp/test-flatpak-iyk1Fm/runtime/doc not found in /etc/mtab

Which causes the failing tests to say too few tests run

Additional Information

The error above shows up near all failing tests

I also tried building 1.13.3 but I get the same error (and I tried rebooting my system too)

BTW my build has a patch to remove ptrace from blocked syscalls (VMProtect needs ptrace for some reason), but i doubt that would affect the results

@swick
Copy link
Contributor

swick commented Jul 3, 2023

Running into the same issue on a Fedora 38 toolbox.

@swick
Copy link
Contributor

swick commented Jul 6, 2023

The output is misleading but the root cause is simply fuse3 not being installed. E.g. in the toolbox a sudo dnf install fuse3 fixed the issue. Seems like the arch PKGBUILD needs updating as well.

Still running into issues on toolbox but they are unrelated. This issue can be closed.

@smcv smcv closed this as not planned Won't fix, can't repro, duplicate, stale Jul 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants