rpm-ostree installed J-Link package executables not in application menu and inaccessible to VSCode
Hello,
I have been using Bazzite for a while, but I also need to use it for development and not just gaming. After finding out that I had to manually download the J-Link package from their website (since there is no flatpak) and install it via rpm-ostree, I did that and unlike the few other programs I installed via rpm-ostree, none of the 10 or so executables showed up in my application menu and none of the command line tools are available in the terminal. If I navigate in Dolphin directly to the files, I can execute them no problem and they have loose permissions of 755.
Now even with explicit R/W permission given to VSCode for /opt/SEGGER/, it still can't even see into the JLink directories under it. What is going on here? Has anyone used J-Link in Bazzite before?
12 Replies
How is VS code installed?
And did you restart after installing it?
VS code was installed months ago through flatpak. It has been restarted many times
I am not going the route of trying to just download the .tar.gz and then putting it in /usr/lib and pointing it to the library via $PATH, but export PATH="$PATH:/folder" does not work in flatpaks
Flatpak is sandboxed, and I believe cannot access opt, and cannot access usr under any circumstance
Ideally you would uninstall vscode and j-link
And then install both of them in a distrobox container
yeah, it kind of sucks doing it that way, but it seems like I have to
It's objectively the best way, outside of something like dev containers
You just export it after it's installed in distrobox
hmmm i wonder if it is better then to have konsole in distrobox as opposed to a flatpak
Definitely stick to the flatpak there
interesting why vscode would even make a flatpak if you can't install almost any functional extensions on it. Unless that is more of an atomic/classic system split and it would be fine with flatpak on a classic system
Nope it's a flatpak thing
A lot of the common extensions are packaged as flatpaks so they work
If you need outside of that ecosystem, there's other options for you. It serves the most basic needs
well thanks for helping. I will try with rootless distrobox
Eh, it works library wise, but now I have to fight udev rules since nothing will program. I assume because I have the udev rules in distrobox and they don't translate to the host
If they have separate UDev packages as most things do you can just layer those
Otherwise just copying the files into etc would be enough
nah, they only have a .deb package for their udev rules. In the arch distrobox they have made a package from the tarball, but they have no RPM to layer.
Isn't /etc/udev read only so we can't copy to it?
nvm, did it with sudo and it seems to work
sorry for bothering you