#fedora-39 — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #fedora-39, aggregated by home.social.
-
Verwendet jemand von euch #OfflineImap? Seit meinem Update auf #Fedora39 bekomme ich es leider nicht mehr zum Laufen. Mit der alten Version 7.3.4 hat alles problemlos funktioniert, aber ab #Fedora 39 steht nur noch die Version 8.0.0 zur Verfügung. Scheinbar wird das Projekt auch nicht mehr aktiv weiterentwickelt. jetzt unter fedora41 besteht das Problem weiterhin.
Gibt es Alternativen?
-
I shouldn't only write about computers when they don't work.
This morning, for example, the upgrade from #fedora39 to #fedora40 went smoothly and the system could boot afterwards.#TimjanGrumpsOnComputers (<-- not today)
-
I am super impressed! The battery life on my #Framework laptop running #Fedora40 seems to be at least 130% compared to #Fedora39! 😍
💕 Kudos to @matthartley and the whole #Linux team at @frameworkcomputer, together with the @fedora community! 🚀
-
Damn, It wants me to skip Fedora 39.
Is it possible to update to Fedora 39 from Fedora 38? I do not want to use Fedora 40 like now...
-
Hmm.. upgraded my #Fedora39 to #Fedora40 on my main PC with a #Nvidia 3050 GPU.
Note: Running with KDE Plasma 6.
However both #Chrome and #Vivaldi browsers are both flickering like mad !
I cleared the GPUCache folders. No change.
I've re-installed both #Chrome and #Vivaldi but the flickering continues.
I've tried turning off Hardware Acceleration in both browsers..
I've tried running
sudo depmod -a
and rebooting but that didn't fix it.
Any thoughts/ideas?
-
There are a bunch of #youtube #linux content creators I regularly follow and they inspire me a lot. I don't have a favourite, but I like Matt's -@thelinux@[email protected] - approach a lot and today I have finally decided to give the @opensuse a try...I am curious if it detects my wifi adapter, #fedora39 did, then #Fedora40 didn't... I am quite tempted by the #kdeplasma6 DE, although the vast customization is not exaxtly what I would look for, but hey, it's there... :)
-
my Lenovo Z13 enjoys running #Fedora39 🥰 making me happy
system is subjectively more responsive and power consumption has gone down,
look like 7 hours working, #vscode and such are realistic
listening to #Beethoven on locked system gives up to 13 hours 😍
thanks a lot @fedora 🥰
tweaks to stretch battery life even longer are very much welcome
🤨 specs on vendors website promise 18 hours watch video 🤔 -
When I upgrade from #Fedora39 to #fedora40 , I'm thinking it's about time to do a clean install rather than continuing the upgrades-in-place I've been doing for the past few years. I hope that will clear the bug I have where my first login fails due to a gnome-shell crash that may be due to a gnome extension.
-
-
I encountered a very strange issue today.
After letting #Fedora40 update itself my laptop wouldn’t boot, not even to the BIOS, luckily I had encountered this before with #Fedora39 back when it was pre-release.
The solution? Open up my laptop 💻 remove the hard drive, boot to BIOS, power off, reinstall the same hard drive, power on again.
This is the second time I’ve had this issue with a pre-release version.
@fedora does this ring any bells?
-
Update 2: I was using the stock kernel when I installed Fedora. There is a Surface specific kernel on the Surface Linux github so I decided to install that.
I turned off the device last night with 87% battery. Turned on the device this morning and still had 87% battery. Life is good.
-
Update on the Fedora/Surface Go 2 project: I am noticing some major battery drainage when the unit is not being used.
For instance, I fully charged the device and turned it off last night. 24hrs later I turn the device on and I am at 0% battery.
I am not sure if this is a Microsoft hardware issue, a kernel issue, or a Fedora distribution causing this drainage. I'm leaning more towards a Microsoft hardware issue.
#SurfaceLinux
#Linux
#MicrosoftSurface
#Fedora39
#FedoraLinux -
I've always thought of #Gnome as "the light DE" when compared to #KDE throughout the years.
Although I have used KDE rigorously in the last few years I still check out Gnome from time to time. This weekend I did a simple test, set up #Fedora39 with #KDE and with #Gnome in separate, but equal, virtual machines on a #Proxmox server and I have to say that KDE is clearly faster now and lighter from what I felt and saw.Funny how things change =D
Btw, really looking forward to #Plasma6
-
This is a summary of the work done by Fedora Infrastructure & Release Engineering teams as of 2023. As these teams are working closely together, we will summarize the work done in one blog post by both teams.
This update is made from infographics and detailed updates. If you want to just see what’s new, check the infographics. If you want more details, continue reading.
About
Purpose of these teams is to take care of day-to-day business regarding Fedora Infrastructure and Fedora Release Engineering work. It’s responsible for developing and maintaining services running in Fedora and preparing things for the new Fedora Linux release (mirrors, mass branching, new namespaces etc.).
Issue trackers
Closed tickets
- Fedora Infrastructure – 585
- Fedora RelEng – 617
Fedora Infrastructure highlights
- Pagure to GitLab importer tool
- Digicert codesigning alternative
- Update koji messaging schema
- Skeleton for bridge from fasjson groups to discourse
- Flask-OIDC improvement
- ppc64le workers for osbuild
- mdapi rewrite
Fedora Release Engineering highlights
Photo by Taylor Vick on Unsplash. Modified by Justin W. Flory. CC BY-SA 4.0.
https://communityblog.fedoraproject.org/2023-year-in-review-infra-releng/
#Fedora39 #FedoraInfrastructure #FedoraLinux38 #Infra #InfraReleng #mdapi #ReleaseEngineering #YearInReview #YearInReview2023
-
This is a summary of the work done on initiatives by the Community Platform Engineering (CPE) Team. Every quarter, the CPE team works together with CentOS Project and Fedora Project community leaders and representatives to choose projects that will be being worked upon in that quarter. The CPE team is then split into multiple smaller sub-teams that will work on the chosen initiatives and day-to-day work that needs to be done. Some of the sub-teams are dedicated to the continuous efforts in the team whilst some are created only for the initiative purposes.
This update is made from infographics and detailed updates. If you want to just see what’s new, check the infographics. If you want more details, continue reading.
About
The Community Platform Engineering Team is a Red Hat team that is working exclusively on community projects. Its members are part of Fedora Infrastructure, Fedora Release Engineering and CentOS Infrastructure teams. This team works on initiatives, which are projects with larger scope related to community work that needs to be done. It also investigates possible initiatives with the ARC (The Advance Reconnaissance Crew), which is formed from a subset of the Infrastructure & Release Engineering sub-team members based on the initiative that is being investigated.
Issue trackers
Initiatives
PDC Retirement
PDC is the Product Definition Center, running at: https://pdc.fedoraproject.org/.
However, this application which was developed internally, is no longer maintained. This codebase has been “orphaned” for a few years now and we need to find a solution for it.
We are reviewing and having a critical look on what we store in there, see what is really needed and then find a solution for its replacement.
Status: In Progress
Issue trackers
Documentation
Application URLs
Matrix Native Zodbot
With ongoing stability issues with the Matrix <-> IRC bridge and many contributors switching over to Matrix, Zodbot has become increasingly unreliable. The bridge is currently shut off completely. This initiative aims to provide a future-proof solution and allow us to conduct meetings without wasting time troubleshooting the Matrix <-> IRC bridge and Zodbot.
Status: In Progress
Issue trackers
Documentation
FMN Replacement
FMN is a project that allows people in our community to get notified when messages that interest them fire on the message-bus, making the message-bus more useful to people that are not directly developing or troubleshooting applications running in our infra.
The previous solution had plenty of tech debt which caused lag times between an event happening and the subscriber to be notified, so this initiative rewrote the service from scratch and is now live! Users are recommended to migrate their rules to the new service and notifications can also now be configured to email, IRC and Matrix.
Status: Done
Issue trackers
Documentation
Application URLs
DNF-Countme Update
DNF Mirrors Countme scripts are used to gain statistics data about the downloads of Fedora. Purpose of this initiative is to optimize the current solution by adding more comprehensive testing, removing unnecessary code and reducing storage consumption of the data.
Status: Done
Issue trackers
Documentation
ARC Investigations
Investigate moving registry.fp.o to quay.io
Traditionally, registry.fedoraproject.org was needed as quay.io did not support multiarch which it now does. The purpose of this ticket is to carry out some investigation work to confirm all the above is true as well as finding any other potential blockers to the move.
Status: Done
Documentation
Spam fighting
We had plenty of spam on pagure.io this year. To fight it more effectively, the ARC team tried a few different approaches to recognize and delete spam. It’s now much easier to delete the spam user with all the spam it created.
Status: Done
ARC investigation/planning for FCAS
In order to have a quantitative understanding of how the contributor activity has changed over the years and to provide the foundational support to the Fedora Project strategy 2028’s guiding star about doubling the number of active contributors every week, it is important to have a service that tracks their statistics. This measurement would help make the strategy goal meaningful as well as assist the Fedora Council and the related bodies understand how far they have progressed into making this happen and identify the underlying particular problems that act as a barrier in realizing this objective.
Status: Done
Documentation
Badges backend for new Service
Fedora Badges is a service that grants virtual accolades for milestones and completing tasks within the Fedora Project community. For example, a community member may collect badges for testing package updates on Bodhi when they test 1, 5, 10, 20, 40, 80, 125, 250, 500 and 1000 updates.
Status: Done
Documentation
Pagure to GitLab importer
With Fedora and CentOS now having an official namespace on GitLab, multiple projects want to migrate their repositories from Pagure to GitLab. This initiative is aimed to provide an easy way to migrate those projects.
Status: Done
Documentation
DNF-countme
The purpose of this work was about investigating the current solution and it’s bottlenecks to identify what needs to be done to solve the following problems:
- Storage bottleneck when creating the intermediate database file
- Operations efficiency for the infrastructure team
Status: Done
Documentation
Dist-Git decoupling & ecosystem mapping
The objective of the potential initiative is to move repository contents (including but not limited to source codes, Packit configurations, RPM specfiles) from Pagure Dist-Git to another platform and confirm that the associated tooling and services (including but not limited to FMN, Datanommer, COPR, Toddlers, FMN, CI, Monitor-Gating, Packit, Bodhi, Fedpkg) work well with the newer platform. The investigation aims to be as agnostic as it can be regarding the destination platform to help ideate a general solution for the compatibility of the associated tooling and services.
Status: Done
Documentation
Epilogue
If you get here, thank you for reading this. If you want to contact us, feel free to do it on matrix.
As CPE members are part of Fedora Infrastructure, Fedora Release Engineering and CentOS Infrastructure, see also the Fedora Infra & Releng update and CentOS Infrastructure update.
https://communityblog.fedoraproject.org/2023-year-in-review-cpe/
#CPE #distGit #DNF #Fedora39 #FedoraInfrastructure #FedoraLinux38 #FedoraMessagingNotificationFMN_ #Infra #Meetbot #YearInReview #YearInReview2023
-
Really impressed with the performance of this Surface Go 2 laptop running Fedora 39. No hiccups, no issues...just feels natural.
-
It's been an exciting week y'all. I don't mean to gloat but a couple of really exciting updates in my life:
+ I finally got out of my ITIL based roles and landed a new job as a Cyber Systems Engineer
+ I finally installed Fedora GNOME on a Microsoft Surface Go 2 that I picked up on the FB marketplace
#cybersecurityjobs
#fedora39
#FedoraLinux
#Linux
#SystemsEngineer -
Installing #fedora silverblue 39 in an old Vostro 1400 with 4 Gb RAM. So far, 2 hrs, and it's 50% done. I'm still wondering if it will work at all.
Any comments or advice?
#linux #fedora39 #oldLaptops -
Just tried to use an #Asus #MB169B+ #USB connected #Displaylink monitor with my #Fedora39 install, all it took was one install and it's up and running! I remember when I got this thing and there was no way to use it on anything other than #Windows and #MacOS
Fantastic to see how things change for the better =D
Leaving this link here for others on a #rpm based system who have a monitor that uses #Displaylink as well
-
So, even as I agree with @HereToChewGum about the #distrohopping , I've grown gradually unhappy with my #linuxmint distro on my laptop. It has booted a bit longer than I'd like to, and I wanted to go off #ubuntu base.
Anyway...it's #fedora39 day!!!
And guess what...installation finished, wifi is not working. It has reminded me of the same problem I'd encountered trying to install #debian #bookworm on my desktop.
Luckily...one only needs to know how to search on the internet...what to say, the wifi is now working.
And #fedora with #kde spin looks interesting. Thanks @fedora ! -
Very helpful, thank you Redhat... Guess I need to hard shutdown my pc just because Minecraft broke the display server again. Pretty sure every single sysrq operation is disabled on Fedora.
-
Even though the odds were slim due to a strike of train operators, 10 Fedora friends (old & new) found their way to the first physical Frankfurt Fedora Release Party on November 16, 2023.
We started with a fun introduction game: draw your “animal guide” and share how it connects to you. This showed how diverse the community is: tiger, parrot, chameleon, Sid (ground sloth from the movie “Ice Age”), (teddy) bear, quokka, marmot, elephant with all their unique characteristics matching the participants’ personalities.
Given that we had a few participants “new(ish) to Fedora,” Aleksandra Fedorova kicked things off with an introduction to “Fedora, Fedora ELN and CentOS Stream – how it all works together.” Followed by an active discussion around experience, fun facts and additional questions around Fedora and the community… which continued over pizza and brownies.
Additional laughter and fun were the heated guesses during the closing pub quiz which tested newly acquired knowledge, random fun facts and Fedora insights.
Overall, all participants had fun and a great learning experience, made new connections and are looking forward to the next Release Party.
Thank you all for your interest and participation! We are looking forward to seeing you (new and old Fedora friends) for the Fedora 40 Release Party in 2024 – hopefully without any strike or other obstacles!
— Aleksandra & Julia
https://communityblog.fedoraproject.org/fedora-39-release-party-frankfurt-germany/
#community #eventReports #events #Fedora39 #releaseParties #releases
