#Fedora42 #Bluetooth #luks I finally figured out how to enable bluetooth in the boot screen so I can unlock my crypted root fs with my Bluetooth keyboard. It is as easy as
`add_dracutmodules+=" bluetooth "` in `/etc/dracut.conf.d/bluetooth.conf ` followed by dracut -f . Not sure why I didn't go it earlier.
Recent searches
Search options
#Fedora42
0 posts0 participants0 posts today
Nested virt is always fun; #fedora42 /virt-manager/#qemu/kvm running #AlmaLinux 10/cockpit-virt/qemu/kvm running #debian 12 plain qemu/kvm running #void
Encore un upgrade de Fedora 41 vers Fedora 42 qui s'est déroulé sans encombre 
Doc : https://docs.fedoraproject.org/en-US/quick-docs/upgrading-fedora-offline/
Replied in thread
Okay. So I ran `sudo btrfs scrub start /dev/nvme0n1p3` & `sudo btrfs scrub status /dev/nvme0n1p3` and this is the result.
I still think what was suggested by @tokyo_0 and @dalias - https://mas.to/@tokyo_0/114521284421935167 - is the main reason. Still I'll backup my data as soon as possible.
Replied in thread
@tokyo_0 @abhijith @fossunleashed @llutz @zenbrowser (5/5)
It can't be a fluke right if it happened twice.
Replied in thread
@tokyo_0 @abhijith @fossunleashed @llutz @zenbrowser (4/5)
But, the moment I opened Zen Browser suddenly the filesystem went read-only. Coincidence, I think not. This also happened when I was offline. I opened Zen it showed me the webpage, all good. I reloaded it, it showed me the classic thing "something unexpected happened". All good. But when I closed the #browser, suddenly the FS went read-only.
Replied in thread
@tokyo_0 @abhijith @fossunleashed @llutz @zenbrowser (3/5)
To check the memory I used `sudo memtester 1024 5`. And EVERYTHING was fine. Even when I turned on the #wifi nothing changed. I opened the #gnomesoftware app, I also opened #firefox to browse #youtube and log in to this instance. Everything was fine.
Replied in thread
@tokyo_0 @abhijith @fossunleashed @llutz @zenbrowser (2/5)
So, today morning I opened the laptop with #wifi turned off and checked the system. It was going alright. The filesystem was behaving normally like it should. I also double-checked it using `mount | grep "btrfs"` and `fastfetch`. To check the nvme drive, I used `sudo smartctl --xall /dev/nvme0n1p3` + the diagnostics tool in the bios menu.
Replied in thread
@tokyo_0 @abhijith @fossunleashed
@llutz (1/5)
I now think that I can pinpoint the problem of the filesystem going read-only and it's (probably) neither the FS itself nor the nvme drive. And definitely not the RAM.
The problem is a single app that's causing this or that's what I found and its the @zenbrowser browser.
Well the #Bluefin desktop finally updated to #Fedora42. No hurry and hassle obviously and without me having to do anything. You get spoiled once you're on an atomic distro. #UniversalBlue
So, I'm facing a weird issue with my #fedora workstation. The filesystem goes "read-only" at random times and I dont know why. I've do a reboot to fix it. Do you have any idea about this and how to fix it ?
Continued thread
#Moin
#NobaraLinux schon mal unter meinen Erwartungen geblieben. Updates laufen gleich zu beginn nicht, habe ich keinen Bawk drauf.
Und: So schick #Debian auch ist, diese Hyperreduktion ist auch nicht gerade nutzer*innen-praktikabel…
Okay, also wieder einen #Bootstick erstellen – versuch ich’s mal mit #Fedora42 mit #KDE. 
Was ist eigentlich mit mir geschehen, dass ich halb 8 morgens #Linux -Installationen mache? 
I'm about to install #Fedora42 on a neighbours new computer.
I know, I'm a glutton for support complexity.
But I think, having tried a bunch of OSes last year, while I didn't personally like Fedora for some specific reasons. It seemed really stable and suitable for end users compared to many Debian based systems that seemed to be falling all over themselves recently.
Maybe it's money. Perhaps it's organisation. not sure.
Wish me luck!
Laptops with Fedora Workstation 42 are now shipping!
"An innovative platform for hardware, cloud, and containers built with love, by you" 
@fedora
Who else is already trying it out? 
#Fedora42 #LinuxLaptops #OpenSource
Continued thread
Solution: I was running #reaper as a portable install in a #toolbox from #Fedora 41 #Silverblue, so I recreated the toolbox using #Fedora42 image.
Continued thread
Put the KDE Plasma Spin of #fedora42 on my 15inch 2015 MacBook Pro Retina.
Works great, apart from the legacy Nvidia driver, which ran at about 1 frame every 30 seconds. Nouveau driver working well instead, at least for basic usage. I suspect things like Blender will struggle. A shame it doesn't seem possible to get legacy drivers working well.
However, much better than Ubuntu. APT ran like a dog and made it unusable.
Continued thread
Sortie de Fedora Linux 42, la réponse à la grande question sur le Libre, Linux et tout le reste ? par renault
En ce mardi 15 avril, les utilisateurs du Projet Fedora seront ravis d'apprendre la disponibilité de la version Fedora Linux 42.
