fedora

This magazine is from a federated server and may be incomplete. Browse more on the original instance.

datendefekt, in [YT] Project Bluefin Tour on a Framework Laptop
@datendefekt@lemmy.ml avatar

Just installed Bluefin and I also like the way that the base OS, GUI apps and CLI programs are partitioned. I enable auto updates - does anyone know how I get informed that an update happened, and that I should reboot?

boredsquirrel,

The main ublue variants (bluefin/aurora, bazzite) use ublue-update for updating.

This fixes many issues like not updating on metered connections or on low battery.

Have a look in there, maybe you can hook a notify-send -t 0 -a “Update” “Update finished” “reboot any time to apply them”

The -t 0 makes the message stay there forever until clicked. Otherwise you can enter a number in seconds.

You could also open a PR in their ublue upate. They dont want update messages as normies never update manually. So a config could enable this message opt-in.

potkulautapaprika, in Various issues with Fedora 40 KDE spin

My five cents, you need to set both windows and Linux using the same time base, otherwise it’s just being few hours in the past or future when you boot win(at least 10).

For the not giving you a dual boot entry, you need to have windows drive mounted so grub’s os-prober finds it, as an aside systemd-boot just picks it up automagically.

And for point 2: yea definitely a kwallet thing, I have no idea how to wrangle that bastard to do my bidding.

boredsquirrel, (edited ) in Various issues with Fedora 40 KDE spin

You may find more help on discussion.fedoraproject.org

First: please mention “I am dual booting the Fedora KDE spin with Windows” at the top, to make things clearer :)

But lets see.

--

It’s e the time in my BIOS is correct.

Dont understand that sentence. But this may be a typical windows thing, as Windows is changing the BIOS time to the one used, while Linux normally keeps the BIOS time normal and uses the offset (like UTC+3).

Have a look at this page, ItsFoss is awesome


<span style="color:#323232;">timedatectl set-local-rtc 1
</span>

--

This sounds like a KDE Wallet issue.

Under systemsettings, see your KDE Wallet settings. Do you have a wallet set as default, that was created by default?

The default wallet uses your login password and gets opened with the login from SDDM. If you changed your login password, or something else, this doesnt work.

In the network settings, did you select “save password for this user (encrypted)” or “save password for all users (unencrypted)”? For wifi passwords you could use that as a fallback, its actually more secure in some scenarios afaik, as only plasma can read it.

--

You are using an nVidia card, did you install any drivers? Nvidia didnt care for linux way too long. You may want to install them manually.

As your system is fresh, and as you need Nvidia drivers, I highly recommend switching to universal blue. Their kinoite-nvidia image has all the drivers and settings, and if something breaks, it is at their end and you will not get the update.

I really cant recommend some hacky way to install the drivers, blacklist nouveau, enable the drivers etc.

ublue.it

I use kinoite-main daily, it is awesome. Atomic/image based Fedora is way better.

Note though that dualbooting is not as easy it seems.

(The rpm-ostree variants are now called “Atomic Desktops” but not long, in the past the GNOME “Fedora Silverblue” was the most dominant)

--

Linux Mint uses legacy boot and is not secureboot compatible. Fedora should actually cause less problems.

Search on Fedora Discuss, this is also a common problem with a fix.

--

Discover only shows graphical apps, you install it from the Terminal (Konsole).

But as I said, I do not recommend installing NVidia drivers on your own on Fedora, as it has too many updates and sometimes drivers break. This happens way too often.

Also to use them you will need to make some more small changes to some files, it is not complex but a few steps.

I recommend kinoite-nvidia by ublue, or as ublue has this as their main variant, Aurora:

getaurora.dev

deczzz,
@deczzz@lemmy.dbzer0.com avatar

Thanks for your detailed reply.

  1. The solution for setting the clock seem to work! Awesome.
  2. I don’t have kWallet enabled but saving the password as unencrypted in the network settings.
  3. Hmm, I just installed akmod-nvidia.x86_64 with dnf. Tried to run nvidia-settings in terminal. I get this error:

<span style="color:#323232;">ERROR: NVIDIA driver is not loaded
</span><span style="color:#323232;">
</span><span style="color:#323232;">(nvidia-settings:14910): GLib-GObject-CRITICAL **: 14:10:49.551: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
</span><span style="color:#323232;">
</span><span style="color:#323232;">** (nvidia-settings:14910): CRITICAL **: 14:10:49.552: ctk_powermode_new: assertion '(ctrl_target != NULL) && (ctrl_target->h != NULL)' failed
</span>
      1. I guess I need to hop distro again! :( But it will probably be faster than fixing
boredsquirrel,
  1. Then maybe try to use Kwallet. Create a new one using KwalletManager, use blowfish, set your login password. In systemsettings enable it as default.

The process is overcomplicated poorly.

  1. The steps are more. As I said, you need to blacklist the opensource nouveau (which seem to work well but not completely) and set the.proprietary ones to be loaded. UBlue does that for you.
skeletorsass, in Various issues with Fedora 40 KDE spin

Time issue: is Windows using UTC time? If it is not:

Open regedit in windows

Navigate HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlTimeZoneInformation

Create new QWORD here, RealTimeIsUniversal as name

Set value 1

Reboot

deczzz,
@deczzz@lemmy.dbzer0.com avatar

I cannot boot into Windows, see point 4. But thanks anyway - might fix the problem if I would be able to boot into Windows.

Guenther_Amanita, in Various issues with Fedora 40 KDE spin

I think a lot of these problems (time settings, etc.) are because of Windows.

Maybe get a second drive and install Aurora or Bazzite on that.
Nvidia drivers and other stuff is included ootb and Fedora Atomic images always were way smoother than the KDE spin in my experience.

deczzz, (edited )
@deczzz@lemmy.dbzer0.com avatar

Thanks for the suggestion.

narc0tic_bird, in Various issues with Fedora 40 KDE spin
  1. If you dual-boot into Windows, that’s probably what sets the time. Linux expects the time in the BIOS to be set to UTC by default, Windows does not. You can change some registry entry in Windows so it uses UTC as well.
  2. Might be related to 5.
  3. Discover is (mostly) for GUI applications. Follow this guide to install the NVIDIA driver.
aleph,

For #1, I found it easier to force the Linux installation to use local time instead of UTC by running the following in a terminal:

timedatectl set-local-rtc 1 --adjust-system-clock

deczzz,
@deczzz@lemmy.dbzer0.com avatar

No idea what the command does but it seems to work :) Thanks

deczzz,
@deczzz@lemmy.dbzer0.com avatar

The problem is that I am not able to boot into Windows. I don’t have the option when I boot into GRUB. My thinking is that it does not have to do with windows setting the time.

ebits21, in [YT] Project Bluefin Tour on a Framework Laptop
@ebits21@lemmy.ca avatar

I rebased from the main Silverblue base image and am liking it quite a bit!

Still using nix home-manager instead of homebrew though. Was just working for me perfect already.

boredsquirrel, in Fedora 40 - DJ Ware, detailed overview

Very good and detailed review, I recommend watching!

theshatterstone54,

I mean, it’s DJWare, so I know it will be good, but okay.

boredsquirrel, in A meta-package to prevent out-of-sync mesa-freeworld

This is really cool! You might want to post this on the discussion site and ping uBlue

hellequin67, in Fedora 40 Released

I’ve been running Fedora39 Workstation on my laptop for the last 3 months as it couldn’t upgrade to W11 and for purposes Linux gives me everything I need.

I run Gnome with KDE Spin and OpenSuse KDE on Boxes, as I wasn’t sure what I was going to stay with.

But following the seamless update using dnf on both Gnome and KDE I’m sold on Fedora going forward, i never expected a version upgrade to be so straight forward on Linux and so far, fingers crossed, everything still working.

Dark_Arc, in Fedora 40 Released
@Dark_Arc@social.packetloss.gg avatar

Updated two machines, both AMD based systems, no major issues.

One fairly low impact SELinux issue with ecryptfs (an error on login about a file read being denied that doesn’t actually seem to have broken anything). A few “this pixel feels out of place” things with KDE, but generally a very smooth update, especially for one that contains a major KDE release.

possiblylinux127, in Fedora 40 Released

I’ll hold off updating for a while until the dust settles

Enragedzeus,

If you’re in 39 you have like 4 weeks or so until EOL

ebits21,
@ebits21@lemmy.ca avatar

Security support for 39 ends Nov 12th, 2024

Michal, (edited ) in Fedora 40 Released

I have been waiting for it to finally dual boot on my main laptop, but it looks like it doesn’t support my ultra wide monitor and won’t allow me to set screen refresh rate higher than 50hz (even with nvidia drivers). Looks like I’m still stuck with windows.

Edit: i solved the problem by using the correct TB cable! Linux now shows full resolution/refresh rate, and windows started showing HDR and 10 bit color. It seems i was limited to 6 bit with previous cable.

Enragedzeus,

I am using a nuc as my testing machine and I can go to 144hz. Not sure why you can’t go higher.

Michal,

The native resolution is 5120 x 2160. I can increase refresh rate if i decrease resolution, then it’s smooth but blurry…

Enragedzeus, (edited )

Hm, I’ll have to test when I finally finish building my new gaming rig.

Edit: spelling hard

snowfalldreamland, in The Wireplumber configuration format changed in Fedora 40

Thanks! This will be veryuseful when I update in a month. I have some config to prevent popping sounds when the soundcard goes to sleep.

e8d79,

Yes that is more or less the issue I needed to fix as well. My issues where fixed by creating a new config at ~/.config/wireplumber/wireplumber.conf.d/alsa-vm.conf with the following content:


<span style="color:#323232;"># ALSA node property overrides for virtual machine hardware
</span><span style="color:#323232;">
</span><span style="color:#323232;">monitor.alsa.rules = [
</span><span style="color:#323232;">  # Generic PCI cards on any VM type
</span><span style="color:#323232;">  {
</span><span style="color:#323232;">    matches = [
</span><span style="color:#323232;">      {
</span><span style="color:#323232;">        node.name = "~alsa_output.*"
</span><span style="color:#323232;">      }
</span><span style="color:#323232;">    ]
</span><span style="color:#323232;">    actions = {
</span><span style="color:#323232;">      update-props = {
</span><span style="color:#323232;">        session.suspend-timeout-seconds = 0
</span><span style="color:#323232;">      }
</span><span style="color:#323232;">    }
</span><span style="color:#323232;">  }
</span><span style="color:#323232;">]
</span>
shrugal, in Moving to Fedora from Arch, what to expect?

Well, first you’ll need a nice hat, it’s not optional…

iJustGhost,
@iJustGhost@lemmy.ml avatar

Is neck beard optional? Please say yes.

shrugal,

I think that’s decided upstream.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • fedora@lemmy.ml
  • DreamBathrooms
  • magazineikmin
  • cubers
  • everett
  • rosin
  • Youngstown
  • ngwrru68w68
  • slotface
  • osvaldo12
  • Durango
  • kavyap
  • InstantRegret
  • tacticalgear
  • khanakhh
  • megavids
  • GTA5RPClips
  • normalnudes
  • thenastyranch
  • mdbf
  • ethstaker
  • modclub
  • Leos
  • tester
  • provamag3
  • cisconetworking
  • anitta
  • JUstTest
  • lostlight
  • All magazines
    •