Just Enough Ducks
UBUniversal Blue
•Created by Just Enough Ducks on 11/28/2024 in #🛟bazzite-help
rpm-ostree installed J-Link package executables not in application menu and inaccessible to VSCode
sorry for bothering you
26 replies
UBUniversal Blue
•Created by Just Enough Ducks on 11/28/2024 in #🛟bazzite-help
rpm-ostree installed J-Link package executables not in application menu and inaccessible to VSCode
nvm, did it with sudo and it seems to work
26 replies
UBUniversal Blue
•Created by Just Enough Ducks on 11/28/2024 in #🛟bazzite-help
rpm-ostree installed J-Link package executables not in application menu and inaccessible to VSCode
Isn't /etc/udev read only so we can't copy to it?
26 replies
UBUniversal Blue
•Created by Just Enough Ducks on 11/28/2024 in #🛟bazzite-help
rpm-ostree installed J-Link package executables not in application menu and inaccessible to VSCode
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.
26 replies
UBUniversal Blue
•Created by Just Enough Ducks on 11/28/2024 in #🛟bazzite-help
rpm-ostree installed J-Link package executables not in application menu and inaccessible to VSCode
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
26 replies
UBUniversal Blue
•Created by Just Enough Ducks on 11/28/2024 in #🛟bazzite-help
rpm-ostree installed J-Link package executables not in application menu and inaccessible to VSCode
well thanks for helping. I will try with rootless distrobox
26 replies
UBUniversal Blue
•Created by Just Enough Ducks on 11/28/2024 in #🛟bazzite-help
rpm-ostree installed J-Link package executables not in application menu and inaccessible to VSCode
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
26 replies
UBUniversal Blue
•Created by Just Enough Ducks on 11/28/2024 in #🛟bazzite-help
rpm-ostree installed J-Link package executables not in application menu and inaccessible to VSCode
hmmm i wonder if it is better then to have konsole in distrobox as opposed to a flatpak
26 replies
UBUniversal Blue
•Created by Just Enough Ducks on 11/28/2024 in #🛟bazzite-help
rpm-ostree installed J-Link package executables not in application menu and inaccessible to VSCode
yeah, it kind of sucks doing it that way, but it seems like I have to
26 replies
UBUniversal Blue
•Created by Just Enough Ducks on 11/28/2024 in #🛟bazzite-help
rpm-ostree installed J-Link package executables not in application menu and inaccessible to VSCode
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
26 replies
UBUniversal Blue
•Created by Just Enough Ducks on 11/28/2024 in #🛟bazzite-help
rpm-ostree installed J-Link package executables not in application menu and inaccessible to VSCode
VS code was installed months ago through flatpak. It has been restarted many times
26 replies