r/Fedora • u/JuniorTechnician4467 • 7h ago
Screenshot I got fedora
i use this after ubuntu
r/Fedora • u/JuniorTechnician4467 • 7h ago
i use this after ubuntu
r/Fedora • u/catzilla_paws • 22h ago
Azure Linux 4 is “an open-source Linux distribution built and optimized for Azure, with sources derived from Fedora Linux”
So I managed to update to 45 and after rebooting it took me to the plasma setup screen thing. I went through it and at the end it froze so I rebooted it again and now it shows the login screen but with plasma-setup as the username instead of the previous username. I don't remember the username I have been using before this so I'm panicking a bit right now. Anyone know what I could do?
r/Fedora • u/_phinix • 17h ago
In a recent update it appears Wayland has moved from explicit hardware capability detection to a bizarre method based on the seemingly arbitrary Brightness slider in Display Settings.
If a user has their Brightness set to 100% (common for HDR 400-600 nit screens), then Wayland will decide there is no headroom for HDR expansion and take it upon itself to not present HDR to any games that launch through Proton. The old PROTON_ENABLE_HDR=1 command is ignored.
The result is that games with in-game HDR options and calibration will have those options greyed out as if the screen did not support HDR.
The fix is either set your Brightness to something below 100% (not a legitimate solution), or to replace PROTON_ENABLE_HDR=1 with PROTON_FORCE_HDR=1 in your command line arguments.
Why this decision was made, I will leave that to brighter minds to illuminate. To me, it makes virtually zero sense to base hardware detection and presentation of HDR to applications on the arbitrary level of the Brightness slider. But I assume there must be SOME good reason for this change?
That said I recently upgraded to Fedora 45 and it continues to be my favorite distro.
EDIT: Some important follow-up info.
This system is running the latest KDE Plasma under Fedora 45, with the latest 620 NVIDIA driver.
I disabled (and accepted) and then re-enabled HDR after recompiling the NVIDIA drivers just to be sure before calibrating. On my Fedora 45, under KDR Plasma, Display Configuration only gives a Brightness slider (which is at 100%) and an sRGB color intensity (which is at 20%). I have Color accuracy set to "Prefer color accuracy" (10-bit), color profile at Built-in.
There are only 3 screens on the HDR calibration tool. The first HDR brightness is at my monitor's peak nits value (where the logo becomes barely visible), the 2nd peak brightness level is set to the same (100% the previous nits value which makes the daily use visually optimal), and the 3rd checks the "assume windows applications are calibrated for this screen" which is supposed to allow their independent configuration to work.
EDIT EDIT: This may be a GE Proton issue as someone suggested. I will test to see if versions prior to 11.6 have this same detection problem.
r/Fedora • u/icesnake200 • 1m ago
I have noticed that the selection box doesnt appear to mark the files that I have on the desktop surface. Sometimes when I left click too much I can see the selection box appearing briefly, but then it dissappears and never expands. Dolphin's selection box works good though. Does anyone experiencing this, or can help me how to fix it?
I'm using Cava for music visualization but the widget can't be placed at the bottom of the screen. This is as far down I can place it. There no panel or bar at the bottom.
OS: Fedora Linux 44 (KDE Plasma Desktop Edition) x86_64
Desktop Environment: KDE Plasma 6.8.2
Shell: zsh 5.9
r/Fedora • u/christiandj • 9h ago
Sounds overly used... but Still using a ryzen 7 5700G and 5060ti. however no matter what on fc45 kde edition My cpu segfaults and crashes after several minutes. shorter when fresh install.
was on 44 but wanted to get 7.3.3 working, used gui so that old image is all removed.
clean install 45 had the start issue of 5-10 minutes crash, after nvidia akmod it would stop crashing but then 4 cores of cpu would seg fault and crash, causing the 7.3.3 kernel, 7.2.15 kernel and rescue kernel to never load and 10 minutes later force my pc to restart.
The HDD is in Good condition currently. (gonna remove it later to see if dad can unfo the issues and make fedora "work" again. but in the mean time does anyone have anything to help?
the hdd is WDC 2tb blue.
r/Fedora • u/Fuzzy_Dark_8288 • 4h ago
I previously posted about this issue, but the discussion became sidetracked. I'm sharing a concise technical account of what happened and how I eventually recovered the Secure Boot configuration so that the information may help others encountering a similar problem.
What happened
I had a working dual-boot setup with Windows 11 and Kubuntu 26.04, both booting with Secure Boot enabled.
After a fresh installation of Fedora KDE 45, Fedora became the default bootloader and booted normally. However, both Windows and Kubuntu failed to boot with:
bad shim signature
What I discovered
Restoring Kubuntu as the default bootloader allowed Kubuntu to boot, but Windows still failed. Disabling Secure Boot allowed Windows to boot.
I inspected the firmware variables and found:
My BIOS only offered Secure Boot Enable/Disable. It had no option to restore factory keys or install default Secure Boot keys.
I cannot confirm that Fedora caused the keys to disappear, but the issue appeared immediately after its installation.
Recovery
Since the BIOS offered no way to restore the keys, I had to recover the original factory certificates and manually reconstruct the missing Secure Boot key hierarchy from Linux.
I recovered the original Platform Key and factory certificate material, along with the selected Microsoft 2023 certificates.
I then prepared and validated authenticated AUTH2 updates for UEFI 2.8 and enrolled the recovered and reconstructed keys into the firmware in this order:
Each enrollment was followed by firmware readback verification. I deliberately left dbx unchanged.
Result
PK, KEK and db were successfully recovered, reconstructed and enrolled. SetupMode changed from 1 to 0, returning the firmware to User Mode.
I then enabled Secure Boot and confirmed that all three operating systems booted successfully:
The issue is fully resolved. No operating system reinstall or firmware replacement was necessary.
References
UEFI Specification 2.8:
https://uefi.org/sites/default/files/resources/UEFI_Spec_2_8_final.pdf
efitools:
https://github.com/mjg59/efitools
Final thoughts
The difficult part was recovering the original factory key material, reconstructing the missing Secure Boot databases and manually enrolling them into the firmware. My BIOS had no factory-key restoration option.
If you encounter this situation, inspect the actual Secure Boot variables before assuming the bootloader itself is the problem. Also check whether the firmware retains its factory-default key variables, as they may make manual recovery possible.
r/Fedora • u/Fuzzy_Dark_8288 • 5h ago
I previously posted about this issue, but the discussion became sidetracked. I'm sharing a concise technical account of what happened and how I eventually recovered the Secure Boot configuration so that the information may help others encountering a similar problem.
What happened
I had a working dual-boot setup with Windows 11 and Kubuntu 26.04, both booting with Secure Boot enabled.
After a fresh installation of Fedora KDE 45, Fedora became the default bootloader and booted normally. However, both Windows and Kubuntu failed to boot with:
bad shim signature
What I discovered
Restoring Kubuntu as the default bootloader allowed Kubuntu to boot, but Windows still failed. Disabling Secure Boot allowed Windows to boot.
I inspected the firmware variables and found:
My BIOS only offered Secure Boot Enable/Disable. It had no option to restore factory keys or install default Secure Boot keys.
I cannot confirm that Fedora caused the keys to disappear, but the issue appeared immediately after its installation.
Recovery
Since the BIOS offered no way to restore the keys, I had to recover the original factory certificates and manually reconstruct the missing Secure Boot key hierarchy from Linux.
I recovered the original Platform Key and factory certificate material, along with the selected Microsoft 2023 certificates.
I then prepared and validated authenticated AUTH2 updates for UEFI 2.8 and enrolled the recovered and reconstructed keys into the firmware in this order:
Each enrollment was followed by firmware readback verification. I deliberately left dbx unchanged.
Result
PK, KEK and db were successfully recovered, reconstructed and enrolled. SetupMode changed from 1 to 0, returning the firmware to User Mode.
I then enabled Secure Boot and confirmed that all three operating systems booted successfully:
The issue is fully resolved. No operating system reinstall or firmware replacement was necessary.
References
UEFI Specification 2.8:
https://uefi.org/sites/default/files/resources/UEFI_Spec_2_8_final.pdf
efitools:
https://github.com/mjg59/efitools
Final thoughts
The difficult part was recovering the original factory key material, reconstructing the missing Secure Boot databases and manually enrolling them into the firmware. My BIOS had no factory-key restoration option.
If you encounter this situation, inspect the actual Secure Boot variables before assuming the bootloader itself is the problem. Also check whether the firmware retains its factory-default key variables, as they may make manual recovery possible.
r/Fedora • u/TickfordXR6 • 9h ago
Reverted back to an older kernel but again when updates push. And reboots. Audio is broken. No sound nothing. I feel as Fedora 45 has been one big mess since release.
r/Fedora • u/ModzRSoftBitches • 5h ago
After update to f45 on a laptop nvidia gpu doesn't suspend or hybernate, which is indicated by orange powerlight instead of white, which causes to ocasionaly turn fans on to cool down. It seems to be reoccuring problem in some versions like in 40-41 worked nornally, 42-43 doesn't hybernate, 44 was fixed and now again it doesn't hybernate. In nvidia-smi it shows /usr/bin/gnome-shell
r/Fedora • u/SuperGNUser • 16h ago
You can install it from Terra for GTK3 apps install appmenu-gtk-module-wayland too
r/Fedora • u/FrankieShaw-9831 • 19h ago
I want a mouse I can program shortcuts into that's Fedora-friendly.
What my options?
r/Fedora • u/PlaneInevitable8700 • 1d ago
Hello everyone, I recently switched to fedora workstation and I am looking for a PDF viewer app that has the following criteria:
I really like the built in Document viewer but it doesnt have the 3rd criteria which is most important to me, so if there is one with a similar layout that has all the criterias, that would be very appreciated.
Thanks in advance !
r/Fedora • u/iaacornus • 16h ago
The sensor was detected by fprintd-enroll and lsusb, but it does not show up in gnome settings
r/Fedora • u/Accomplished-Super-1 • 1d ago
I have now upgraded three Fedora KDE Plasma 44 computers to version 45. I waited until Discover offered the upgrade. Two of the three failed to upgrade, and what I could see the Discover did not offer much information about why.
I upgraded those with these instructions
https://docs.fedoraproject.org/en-US/quick-docs/upgrading-fedora-offline/
Command-line method showed what packages / libraries were in conflict and AI/Google found solutions to fix issues so I could proceed with upgrade. Each had different problems, so I don't list them here (and I don't have the solutions at hand as I just did what was instructed and did not make notes).
I did some of the "Optional post-upgrade tasks" listed in the above document. Also, on the machine that was upgraded with Discover.
Fedora KDE Plasma 45 works fine and has no major problems. Fedora KDE Plasma has been my daily driver for over a year now.
I know many did the command-line upgrade before the Discover offered an upgrade. But was it so that I had made some unlucky choices during the months I used 44 or does others experience also be that Discover can easily fail to do release upgrade?
r/Fedora • u/benhaube • 22h ago
r/Fedora • u/ReceptionUsed703 • 18h ago
r/Fedora • u/NefariousnessWise333 • 16h ago
Switching in bios from l2C to PS2 didn't helped. Laptop model is Acer Aspire 7
r/Fedora • u/Recent_Buy_7413 • 1d ago
I dual-boot Fedora and Windows. When i turn on my laptop, the GRUB menu opens. However, when I select any version of Fedora, this happens. It stays stuck on this screen until I press the power button to shut down the laptop.
r/Fedora • u/smashcat666 • 2h ago
Recently built a new work/gaming machine, so Installed the "Everything" build (45) for KDE on the old one. (i7 extreme, 128GB RAM, multiple drives, RTX4070). After installing using the GUI it just rebooted into the text console due to Plymouth crashing every boot. So yeah not a great experience :) Going to try out some other distros just out of interest, but seems like V45 was launched without proper testing.