-
Notifications
You must be signed in to change notification settings - Fork 588
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
ktorrent: Cannot start application: No such file or directory #5414
Comments
Python is blocked by
We can add it to our default ktorrent.profile if this fixes it for you. Or you can create a PR if you want. |
Seems that is not all getting blocked:
|
Sadly I'm not really familiar with KDE to explain all these warnings, although IMO most of them look harmless. The ktorrent profile uses |
Also check your syslog for seccomp messages. |
firejail fails to create the following file: * ~/.kde/share/config/ktorrentrc Because it does not create the preceding directories beforehand: * ~/.kde/share/config Relates to netblue30#5414.
I can launch Ktorrent using the default profile on Archlinux without problems. The real problem with Ktorrent profile is already reported: #1793 So, if you open Ktorrent for the first time, will not save any configurations because firejail can´t write on /.config/ktorrentrc. You have to launch Ktorrent outside firejail, configure the program to your liking, let Ktorrent create a valid /.config/ktorrentrc file and using ktorrent firejailed. In the default ktorrent profile I see strange things, for example: private-bin kbuildsycoca4,kdeinit4 <---- KDE4 programs |
@X6B Odd because I do have Ktorrent already configured, and it works outside of firejail but with firejail nothing. One question, are you actively running KDE? I'm trying to launch Ktorrent from HerbstluftWM instead of KDE. Again it works without firejail this way though. @kmk3 That at least takes care of that issue, but I'm still having the same problem. After implementing the other suggestions in the thread here is an updated output of @rusty-snake The only log I see seccomp in other than the debug output of firejail is AppArmor's audit log but I don't see anything for ktorrent. |
|
I don't follow what you mean here? Should I add Edit: I see now, Still to test is without the |
I should not write the first part of the sentence, look up something and then write the rest without re-reading the first part ... It should contain |
@vendion Yes, I'm an Archlinux KDE user and never had a problem starting Ktorrent under firejail. The only problem is that the configuration files seem to be opened in read-only mode. |
Okay, I manage to get Ktorrent to launch under firejail with the following profile: /etc/firejail/ktorrent.profile
.config/firejail/ktorrent.local
|
|
firejail fails to create the following files: * ~/.kde/share/config/ktorrentrc * ~/.kde4/share/config/ktorrentrc Because it does not create the preceding directories beforehand: * ~/.kde/share/config * ~/.kde4/share/config Relates to netblue30#5414.
Maybe it's about time to get rid of all that kde4 cruft altogether. From all big distributions it looks like only RHEL 7 still supports KDE/Plasma 4, and will do so till mid 2024. As far as I understand there are no free RHEL 7 clones any more, now that CentOS has been discontinued. It would help also in other ways. Profiles like that for Okular don't have a Nowadays all of that is not true anymore. |
Sounds like a good idea to me. (Though I'd postpone doing such a refactoring until after 0.9.72) Could you open an issue to track/discuss this? |
Yes, will do that.
I was wrong by the way. CentOS 7 and RHEL 7 reach EOL at the same time. |
Description
Ktorrent 22.08.1 doesn't launch with the default firejail profile, instead a fatal python error is thrown.
Steps to Reproduce
Steps to reproduce the behavior
LC_ALL=C firejail /usr/bin/ktorrent
(gave full path as I have firejail setup so apps are ran under it by default)Expected behavior
Ktorrent to open up.
Actual behavior
Ktorrent errored out before even opening the main window.
Behavior without a profile
Without a profile Ktorrent opens up just fine.
Additional context
Environment
Checklist
/usr/bin/vlc
) "fixes" it).https://github.com/netblue30/firejail/issues/1139
)browser-allow-drm yes
/browser-disable-u2f no
infirejail.config
to allow DRM/U2F in browsers.--profile=PROFILENAME
to set the right profile. (Only relevant for AppImages)Log
Output of
LC_ALL=C firejail /path/to/program
Output of
LC_ALL=C firejail --debug /path/to/program
https://gist.github.com/vendion/894010a10ebc4b2d00a9834ae41c9873
The text was updated successfully, but these errors were encountered: