What do you think of Fedora? So far I enjoy the stability combined with near-arch levels of getting new updates!
I switched away from other distros to Fedora (KDE spin), and am happy here.
Do I wish they were better open-source citizens, yes, of course! But they're still allot better than Microsoft/Windows close-source solution.
And as far as the distro goes, its nice to have solid support for hardware, and a good rolling release cycle that doesn't brick my OS, and that has quick support for gaming, etc.
If you're the type of person who wants a Windows alternative OS to use as just a tool for gaming/business first and foremost, and not to tinker with the OS for fun (unless they want to), Fedora is the best, and what we all should be proposing to others when they ask about moving to Linux.
Ι don't agree with what they did. They removed browser integration, not just the "favicon" thing. If this was a problem for normal users, well, normal users would just use Firefox's built-in password manager, not keepassxc. That change made the app useless to me, and going forward it will be a headache for NEW users who won't know of the -full package. It was a bad decision.
Fedora is not Red Hat per se, it is upstream. Red Hat is a few things in different spaces. For one is is a great source of documentation. Secondly, a sizable chunk of kernel code is developed and maintained by Red Hat. They are known for their zero down time kernel updating system among other things.
Fedora is excellent. However, it is very different than Ubuntu by design. Fedora is primarily useful for entry level users that intend on only running software that is regularly kept up to date and maintained. You will start running into problems with software that is not kept up to date. There are relatively easy tools like distrobox, toolbox, and podman that can run most software regardless. The exception to this comes with the GPU. If you are running a GPU, you're likely getting updates in Fedora with will break your older projects entirely. This is because Fedora is constantly updating the Linux kernel. Fedora is pushing out these updates constantly and looking for problems that might pop up. These issues get fixed and down stream to Red Hat to make it rock solid.
Ubuntu is based on a much longer term stability with even longer term LTS versions. This means the kernel and dependencies are frozen in time at a specific state. If you want to write some custom package that never gets broken when a dependency is updated, Ubuntu is the goto distro. You must be aware that, on Ubuntu, the native packages are largely out of date. You can add a ppa to the sources list in aptitude so that you get the latest packages, but these should be used only in special cases. If you want to be up to date, use the proper distro for the task.
This context is more important for servers where you want to deploy a project using a bunch of apps and packages. Once it is working, it should stay working for however long the LTS kernel is supported.
Fedora updates the kernel because maintaining backports is engineering-intensive, Ubuntu backports fixes into their kernels. I don’t think Fedora kernels affect Red Hat much at all, Red Hat does extensive back porting into a set version and their stable kernel often has hundreds of releases of the “same” kernel version.
For Guake the version in Bookworm is from 2022 and you may need to set an environmental variable or perhaps it isn't built with Wayland support on Debian.
You could hit up the Debian forums for a better answer.
That's unfortunate. Will have to switch back to X.Org until this is fixed by the Wayland/XWayland developers, is there any clue as to why it specifically wouldn't work? If it's updated as recently as 2019 then I'd have expected Wayland to fix this by now, not like I'm trying to run a DOS game or something haha!
If it is a newer Mac (Apple silicon), asahi is your only option that I know of. It is good but idle and sleep power management leave something to be desired. If not, I would recommend debian. It is stable, so you don't have to worry about an update breaking it right before a class or anything like that.
The response by the debian maintainer responsible for this change to the keepassxc developer is an actual disgrace
Request to revert change:
@julian-klode this needs to be reverted asap. This is now our fourth bug report because of the decision to neuter the base KeePassXC package in Debian. Put the base package back where it was and create a keepassxc-minimal.
Response by debian maintainer:
julian-klode commented 9 hours ago:
I'm afraid that's not going to happen. It was a mistake to ship with all plugins built by default. This will be painful for a year as users annoyingly do not read the NEWS files they should be reading but there's little that can be done about that.
It is our responsibility to our users to provide them the most secure option possible as the default. All of these features are superfluous and do not really belong in a local password database manager, these developments are all utterly misguided.
Users who need this crap can install the crappy version but obviously this increases the risk of drive-by contributor attacks.
The whole github issue is worth a read, as it actually explains the issue with the change.
Edit: as i gave the debian maintainers view visibility i wanted to give a quick summary of the keepassxc point of view as well:
julian-klode specifically mentions attacks by contributors of keepassxc. If you don’t trust the developers, why would you trust the minimal package which is developed by the same people?
If the Debian packagers have good reason to believe the keepassxc-full version presents a broader attack surface, then they ought to present what they've seen that makes them feel that way, not promote baseless innuendo.
the features are disabled by default. If you do not opt in, the code never gets executed.
the safest version of keepassxc is the one thats tested, meaning full featured
removing all those features doesn’t make it more secure, it dumbs it down to an encrypted spreadsheet and makes it less secure. Users should be automatically notified when one of their accounts has been breached and their password for that account has been found floating in a db dump. Users should rely on their password manager to handle logins for them, so they're less likely to get tricked into a phishing page.
if you disagree with features in someones app you fork it. You do not change it and distribute it under the same name. A -minimal version would have been ok
Debians own policy is to communicate with upstream beforehand before introducing changes. This was not the case, nor was there a chance to collaborate on an effective solution for both parties.
Debian could have chosen to give users an informed choice between -full and -minimal. Instead they broke existing users installs.
People saying it was released in Debian sid, which is meant for changes. It is also meant for Feedback, which julian-klode refuses to listen to.
@krash@steeznson I always recommend #gentoo to anyone interested in learning about linux. I'd advise LFS only as a follow up to that once they have an understanding of what goes where.
I believe h.265 has particular handling for "film grain". And it has hardware decoding on just about every chip out there. And you probably already have a hardware encoder, so you can do something like QSV in a reasonable time frame.
300MB for a half-hour is a pretty reasonable bitrate, for one and a half hours it is quite dire.
I wouldn't call it a dangerous opinion, Ubuntu is a great starter distro and was probably top dog back then, it is just that their recent actions have been not liked by the Linux community.
I personally fell in love with opensuse tumbleweed w/ kde 6, but I do want to give fedora a try at some point as well.
set(WITH_XC_ALL OFF CACHE BOOL "Build in all available plugins")
option(WITH_XC_AUTOTYPE "Include Auto-Type." ON)
option(WITH_XC_NETWORKING "Include networking code (e.g. for downloading website icons)." OFF)
option(WITH_XC_BROWSER "Include browser integration with keepassxc-browser." OFF)
option(WITH_XC_BROWSER_PASSKEYS "Passkeys support for browser integration." OFF)
option(WITH_XC_YUBIKEY "Include YubiKey support." OFF)
option(WITH_XC_SSHAGENT "Include SSH agent support." OFF)
option(WITH_XC_KEESHARE "Sharing integration with KeeShare" OFF)
option(WITH_XC_UPDATECHECK "Include automatic update checks; disable for controlled distributions" ON)
if(UNIX AND NOT APPLE)
option(WITH_XC_FDOSECRETS "Implement freedesktop.org Secret Storage Spec server side API." OFF)
endif()
option(WITH_XC_DOCS "Enable building of documentation" ON)
set(WITH_XC_X11 ON CACHE BOOL "Enable building with X11 deps")
# stuff inbetween cut out
if(WITH_XC_ALL)
# Enable all options (except update check and docs)
set(WITH_XC_AUTOTYPE ON)
set(WITH_XC_NETWORKING ON)
set(WITH_XC_BROWSER ON)
set(WITH_XC_BROWSER_PASSKEYS ON)
set(WITH_XC_YUBIKEY ON)
set(WITH_XC_SSHAGENT ON)
set(WITH_XC_KEESHARE ON)
if(UNIX AND NOT APPLE)
set(WITH_XC_FDOSECRETS ON)
endif()
endif()
I'm no CMake expert, but it looks like to me, from the first line of the above snippet, that the default in the upstream build script is WITH_XC_ALL=OFF.
Debian sid user here, and long time keepassxc user
Debian maintainer didnt communicate this well, but i agree that i dont want my password manager having any access to networking or interacting with anything other than the clipboard.
I'm not a developer or a security expert. This is just my gut feeling talking
Exactly. And if you want those features, you install the full version. Packages can break in sid, that is the whole point of it.
I am also running sid and keepassxc and I see no problem with this change. In fact it seems like a very sane thing to do, and something I wished more packages did.
Sane move by maintainer, but he should not go around calling other people's code crap unless there is proof that the code was actually crap with gaping security hole
He could have handled it better. But he didn't call the code crap directly, just the bundle of everything.
Having a meta package and let users choose seems like the best way. But this is a Debian issue, and not a keepassxc issue. It is up to Debian to package it anyway they want.
Linux
Hot
This magazine is not receiving updates (last activity 49 day(s) ago).