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

I can't start portmaster-start core #1750

Closed
securegh opened this issue Nov 22, 2024 · 3 comments
Closed

I can't start portmaster-start core #1750

securegh opened this issue Nov 22, 2024 · 3 comments
Labels
bug TYPE: a report on something that isn't working stale ATTRIBUTE: this issue has not had recent activity

Comments

@securegh
Copy link

Pre-Submit Checklist:

What happened:
I can't start /opt/safing/portmaster/portmaster-start core

Error: failed to exec lock: failed to get path of existing process: readlink /proc/1604/exe: no such file or directory

What did you expect to happen?:

Starting portmaster-start core

How did you reproduce it?:

Open terminal on Fedora 40

sudo /opt/safing/portmaster/portmaster-start core

Debug Information:

Software Information:

  • Firmware Version: 1.60
  • OS Name: Fedora Linux 40 (Workstation Edition)
  • OS Build: (null)
  • OS Type: 64-bit
  • GNOME Version: 46
  • Windowing System: X11
  • Kernel Version: Linux 6.11.8-200.fc40.x86_64
@securegh securegh added the bug TYPE: a report on something that isn't working label Nov 22, 2024
Copy link

Greetings and welcome to our community! As this is the first issue you opened here, we wanted to share some useful infos with you:

  • 🗣️ Our community on Discord is super helpful and active. We also have an AI-enabled support bot that knows Portmaster well and can give you immediate help.
  • 📖 The Wiki answers all common questions and has many important details. If you can't find an answer there, let us know, so we can add anything that's missing.

Copy link

This issue has been automatically marked as inactive because it has not had activity in the past two months.

If no further activity occurs, this issue will be automatically closed in one week in order to increase our focus on active topics.

@github-actions github-actions bot added the stale ATTRIBUTE: this issue has not had recent activity label Jan 27, 2025
Copy link

github-actions bot commented Feb 3, 2025

This issue has been automatically closed because it has not had recent activity. Thank you for your contributions.

If the issue has not been resolved, you can find more information in our Wiki or continue the conversation on our Discord.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Feb 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug TYPE: a report on something that isn't working stale ATTRIBUTE: this issue has not had recent activity
Projects
None yet
Development

No branches or pull requests

1 participant