1 Like
My latest issues that in the end necessitated reinstalling you can check out here.
As for most of what the rest of you said I have to say Fedora really isn’t impressing me so far. Even after adding a bunch of extra repos I’m still having trouble finding and installing basic packages with that dnf of theirs, things that didn’t take even a microsecond in Endeavour…
Sigh, I miss EOS already… 
1 Like
I warned you…you’ll be back! 
8 Likes
What packages couldn’t you find?
1 Like
- brave - eventually solved with help
- double commander - someone else managed to find it but I had to use their website in the end
- anything containing “amdonly” - still unsolved
- mission-center - currently trying to build the flatpak but I am failing, asked for help, waiting for answer
And that’s just off the top of my head, there where probably others… 
Huh? What packages are you having trouble finding? You don’t normally use dnf directly in Fedora for package management (you can but that’s not the easiest way). Use the software/discovery app to find and install packages.
It’s actually easier to “find packages” in Fedora than it is in EOS because everything shows in the software/discovery app.
EOS is great and it’s my main distro on my desktop and laptop but it certainly isn’t easier than Fedora.
You and I had very different experiences then, forget the same ballpark, they aren’t even in the same universe!!!.. 
1 Like
I generally don’t have much issue finding anything in any distro, unless of course it’s not actually there 
1 Like
You need brave from the official brave repo.
Can you link the Arch package I’ve never heard of that? This one?
https://archlinux.org/packages/extra/x86_64/doublecmd-qt6
What do you mean with amdonly? What packages specifically?
You can just install the one from Flathub which is built and maintained by the developer?
flatpak install io.missioncenter.MissionCenter
Doesn’t sound like basic packages to me because most of those are already part of a desktop environment, sound more like extra packages to me. But so far seems still installable on Fedora whether that through another repo or flatpak? But I guess everyone has a different definition of basic.
1 Like
I use both distros daily and you’re having experiences that most people don’t.
What are you talking about “building the flatpak”? You don’t have to build the flatpak, simply install it in the discover software app. It’s right there or you can copy and paste the following to install it fromt he CLI…
flatpak install flathub io.missioncenter.MissionCenter
Well hey if anyone is curious to see how much I’ve f-ed up, check out the main thread where I asked for help there…
by building the flatpak @LBTRS I mean following the instructions here, or trying to anyway…
Why are you following those instructions? Just install Mission Center from flathub…it’s available by default in Fedora.
This one?
Name : doublecmd-qt6
Epoch : 0
Version : 1.1.21
Release : 1.fc41
Architecture : x86_64
Download size : 5.2 MiB
Installed size : 17.0 MiB
Source : doublecmd-1.1.21-1.fc41.src.rpm
Repository : updates
Summary : Twin-panel (commander-style) file manager (Qt6)
URL : http://doublecmd.sourceforge.net
1 Like
Yeap, that’s the one and I tried different dnf search and then dnf list --available , etc. and could not find it, same with all the others I mentioned.
Thank you so much @LBTRS indeed your command worked to install mission center, yaaay, one down.
Well packages can be named different. This his how I searched.
dnf search doublecmd Updating and loading repositories:
Repositories loaded.
Matched fields: name
doublecmd-common.x86_64: Common files for Double Commander
doublecmd-gtk.x86_64: Twin-panel (commander-style) file manager (GTK)
doublecmd-qt.x86_64: Twin-panel (commander-style) file manager (Qt5)
doublecmd-qt6.x86_64: Twin-panel (commander-style) file manager (Qt6)
Which ones were you specifically looking for? What do you need them for or what do they do?
1 Like
I meant what I said mate, anything, do yay amdonly in EOS see ho much stuff pops up, then go do dnf search amdonly in Fedora, nothing, not a single package shows up…
Ok, here is what I had installed in EOS, I am guessing I am gonna need a least some of them(if not all) for things to work properly again..:
amdonly-gaming-mesa-git
amdonly-gaming-opencl-clover-mesa-git
amdonly-gaming-opencl-rusticl-mesa-git
lib32-amdonly-gaming-mesa-git
lib32-amdonly-gaming-opencl-clover-mesa-git
lib32-amdonly-gaming-opencl-rusticl-mesa-git
Glad it worked but can I give you some advice? You’re making this much harder on yourself than it needs to be. You need to stop using DNF directly to manage your packages until you get more experienced. There are much easier ways.
What desktop are you using, KDE or Gnome?
What packages do you get in return when running “yay amdonly” in EndeavourOS is my question because “amdonly” is probably something specific to pacman or yay and dnf is a totally different package manager. Sounds more like you are running into issues with still needing to learn to get used to a new package manager since you were already used to pacman/yay. But that’s fine, just trying to point out that Fedora is not the problem and it’s also fine if you prefer pacman/yay but you didn’t give it long enough to get used to dnf.
Anyways, welcome back!
KDE Plasma, but cmon mate, I’m not trying to be difficult really, but can you people please make up your mind already??!.. While I was here all I heard was “use the console, get familiar with it, install with yay, forget gui package managers, etc”, now after I’ve finally adapted that mentality and actually come to enjoy typing stuff in the console you tell me the execat opposite… 
Because you’re having all kinds of trouble…you switched to Fedora because the difficulty of EOS wasn’t for you. Use the tools Fedora has to do things instead of frusterating yourself with all this nonsense. Use the Discover Software app to install the apps you’re looking for and practice using DNF without getting frustrated.
The problems you’re having are caused by you not understanding things correctly or spelling the commands wrong, etc. This can all be solved for you by using the tools you have by default in Fedora.
EOS doesn’t come with the Discover Software app and is meant to be ran from the command line. That isn’t the case with Fedora and they give you this tool to use.
2 Likes