test

test@lists.fedoraproject.org

22 participants
57340 discussions

anyone own an Intel Mac?
by Chris Murphy 25 Mar '25

25 Mar '25

If you have an Intel Mac with macOS installed, please see https://bugzilla.redhat.com/show_bug.cgi?id=2354671#c8 and respond with the output from the requested lsblk command. Thanks, -- Chris Murphy

2 1

[Fedora 42]Bluetooth devices reconnection fails
by Jan Maehner 23 Mar '25

23 Mar '25

After upgrading from Fedora 41 to Fedora 42 Bluetooth connection became unstable. Connection to mouse and keyboard get lost after turning power off and on mouse/keyboard. Reconnection doesn't has any effect - devices needs to be repaired. Already tried bluetoothctl connect -> trust without success.

1 0

F42: missing driver for bluethooth
by Roger Grosswiler 23 Mar '25

23 Mar '25

Hi, Installed F42 on a new Acer Swift SF16-51. Everything went fine, except bluetooth. According to dmesg, there are missing files within /lib/firmware/intel: root@fedora:/lib/firmware/intel# dmesg | grep -i bluetooth [ 3.716279] Bluetooth: Core ver 2.22 [ 3.716319] NET: Registered PF_BLUETOOTH protocol family [ 3.716321] Bluetooth: HCI device and connection manager initialized [ 3.716325] Bluetooth: HCI socket layer initialized [ 3.716328] Bluetooth: L2CAP socket layer initialized [ 3.716332] Bluetooth: SCO socket layer initialized [ 3.787225] Bluetooth: hci0: Device revision is 0 [ 3.787239] Bluetooth: hci0: Secure boot is enabled [ 3.787240] Bluetooth: hci0: OTP lock is disabled [ 3.787241] Bluetooth: hci0: API lock is enabled [ 3.787242] Bluetooth: hci0: Debug lock is disabled [ 3.787242] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [ 3.787244] Bluetooth: hci0: Bootloader timestamp 2023.33 buildtype 1 build 45995 [ 3.790830] Bluetooth: hci0: Found device firmware: intel/ibt-0190-0291-iml.sfi [ 3.790835] Bluetooth: hci0: Boot Address: 0x30099000 [ 3.790836] Bluetooth: hci0: Firmware Version: 58-7.25 [ 3.841204] Bluetooth: hci0: Waiting for firmware download to complete [ 3.841226] Bluetooth: hci0: Firmware loaded in 49211 usecs [ 3.841300] Bluetooth: hci0: Waiting for device to boot [ 3.843371] Bluetooth: hci0: Device booted in 2073 usecs [ 3.843380] Bluetooth: hci0: Waiting for device transition to d0 [ 3.843384] Bluetooth: hci0: Device moved to D0 in 4 usecs [ 3.843641] Bluetooth: hci0: dsbr: enable: 0x01 value: 0x0f [ 3.843790] Bluetooth: hci0: Failed to load Intel firmware file intel/ibt-0190-0291-pci.sfi (-2) [ 3.843793] Bluetooth: hci0: Firmware download retry count: 1 [ 3.882051] Bluetooth: hci0: Device revision is 0 [ 3.882055] Bluetooth: hci0: Secure boot is enabled [ 3.882056] Bluetooth: hci0: OTP lock is disabled [ 3.882057] Bluetooth: hci0: API lock is enabled [ 3.882057] Bluetooth: hci0: Debug lock is disabled [ 3.882057] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [ 3.882058] Bluetooth: hci0: Bootloader timestamp 2023.33 buildtype 1 build 45995 [ 3.885002] Bluetooth: hci0: Found device firmware: intel/ibt-0190-0291-iml.sfi [ 3.885006] Bluetooth: hci0: Boot Address: 0x30099000 [ 3.885006] Bluetooth: hci0: Firmware Version: 58-7.25 [ 3.934083] Bluetooth: hci0: Waiting for firmware download to complete [ 3.934096] Bluetooth: hci0: Firmware loaded in 47940 usecs [ 3.934169] Bluetooth: hci0: Waiting for device to boot [ 3.936247] Bluetooth: hci0: Device booted in 2087 usecs [ 3.936250] Bluetooth: hci0: Waiting for device transition to d0 [ 3.936251] Bluetooth: hci0: Device moved to D0 in 1 usecs [ 3.936497] Bluetooth: hci0: dsbr: enable: 0x01 value: 0x0f *[ 3.936630] Bluetooth: hci0: Failed to load Intel firmware file intel/ibt-0190-0291-pci.sfi (-2) [ 3.936712] Bluetooth: hci0: Failed to read MSFT supported features (-56)* [ 4.779139] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 4.779143] Bluetooth: BNEP filters: protocol multicast [ 4.779148] Bluetooth: BNEP socket layer initialized Device00:14.7 Bluetooth: Intel Corporation Device a876 (rev 10) How can i get bluetooth working? Regards, Roger

2 2

[Fedora 42] CoreOS Test Week
by Sumantro Mukherjee 22 Mar '25

22 Mar '25

Mark your calendars for the upcoming Fedora 42 CoreOS Test Week, which will take place from March 24 to 28, 2025! The test week is an opportunity for the community to test FCOS based on Fedora 42 content before it is released as part of the `testing` and `stable` streams. Your contributions will make a significant impact on the quality and stability of Fedora CoreOS (FCOS). To get started we will first host a virtual in-person prep video session this Friday, March 21'st at 14:30 UTC (10:30 EDT) to discuss some of the details related to the test week. On March 26'th at 16:30 UTC (12:30 EDT) we will host the main session, where you can drop in, ask questions, and get help from members of the Fedora CoreOS team! If you want to participate in the Test Week, check out the Fedora Wiki page for details and log your results in the Test Day page. * Fedora Project Wiki: [Test Day: Fedora 42 CoreOS]( https://fedoraproject.org/wiki/Test_Day:Fedora_42_CoreOS) * Test Day Results: [Fedora 42 CoreOS Test Day]( https://testdays.fedoraproject.org/events/211) * FCOS GitHub Tracker: [F42: Fedora CoreOS Test Week · Issue #1885 ]( https://github.com/coreos/fedora-coreos-tracker/issues/1885) * Pagure.io QA Ticket: [Issue #805: F42 Fedora CoreOS test week 24-03-2025 - 28-03-2025](https://pagure.io/fedora-qa/issue/805) * Fri Mar 21 Prep Meeting Link: https://meet.google.com/grs-ewth-nrw * Wed Mar 26 Meeting Link: https://meet.google.com/hze-qdgc-uyj * Wed Mar 26 Notes Doc: [Fedora CoreOS 42 Test Week - HackMD]( https://hackmd.io/19OpguDrTRCRlXUe4AQEtw) We hope to see you online! -- //sumantro Fedora QE TRIED AND PERSONALLY TESTED, ERGO TRUSTED <https://redhat.com/trusted>

1 0

2025-03-24 @ 16:00 UTC - Fedora 42 Blocker Review Meeting
by Adam Williamson 22 Mar '25

22 Mar '25

# F42 Blocker Review meeting # Date: 2025-03-24 # Time: 16:00 UTC # Location: https://matrix.to/#/#blocker-review:fedoraproject.org?web-instance[element.… Hi folks! It's time for a Fedora 42 blocker review meeting! We have 3 proposed blockers and 1 proposed freeze exception for Final. Here is a handy link which should show you the meeting time in your local time: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Fedora+41+Blocker… The meeting will be on Matrix. Click the link above to join in a web client - you can authenticate with your FAS account - or use a dedicated client of your choosing. If you have time this weekend, you can take a look at the proposed or accepted blockers before the meeting - the full lists can be found here: https://qa.fedoraproject.org/blockerbugs/ . Remember, you can also now vote on bugs outside of review meetings! If you look at the bug list in the blockerbugs app, you'll see links labeled "Vote!" next to all proposed blockers and freeze exceptions. Those links take you to tickets where you can vote. https://pagure.io/fedora-qa/blocker-review has instructions on how exactly you do it. We usually go through the tickets shortly before the meeting and apply any clear votes, so the meeting will just cover bugs where there wasn't a clear outcome in the ticket voting yet. **THIS MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!** We'll be evaluating these bugs to see if they violate any of the Release Criteria and warrant the blocking of a release if they're not fixed. Information on the release criteria for F42 can be found on the wiki [0]. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go and you want to run one - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting Have a good weekend and see you on Monday! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org https://www.happyassassin.net

1 0

2025-03-17 - Fedora Quality Meeting - Minutes
by Adam Williamson 22 Mar '25

22 Mar '25

===================================== # #meeting:fedoraproject.org: Quality ===================================== Meeting started by @adamwill:fedora.im at 2025-03-17 15:00:53 Meeting summary --------------- * TOPIC: Roll Call (@adamwill:fedora.im, 15:00:57) * TOPIC: Previous meeting follow-up (@adamwill:fedora.im, 15:05:09) * INFO: there were no ation items (@adamwill:fedora.im, 15:05:31) * TOPIC: Fedora 42 status, Beta release pre-flight check (@adamwill:fedora.im, 15:08:55) * INFO: Beta release is tomorrow (@adamwill:fedora.im, 15:09:33) * INFO: kparal reports many issues with the software RAID functionality in webUI, he is organizing them into individual bugs ATM (@adamwill:fedora.im, 15:17:53) * TOPIC: Test Day / community event status (@adamwill:fedora.im, 15:19:45) * INFO: coreos, GNOME and IoT test days seem to be in the works, stay tuned for more details (@adamwill:fedora.im, 15:23:26) * INFO: i18n test week happened recently with some solid participation: https://testdays.fedoraproject.org/events/210 (@adamwill:fedora.im, 15:23:54) * TOPIC: Open floor (@adamwill:fedora.im, 15:25:30) Meeting ended at 2025-03-17 15:32:13 Action items ------------ People Present (lines said) --------------------------- * @adamwill:fedora.im (37) * @kparal:matrix.org (12) * @lruzicka:matrix.org (4) * @derekenz:fedora.im (3) * @zodbot:fedora.im (2) * @meetbot:fedora.im (2) * @sumantrom:fedora.im (1) * @tablepc:fedora.im (1) -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org https://www.happyassassin.net

1 0

2025-03-03 - Fedora Quality Meeting - Minutes
by Adam Williamson 22 Mar '25

22 Mar '25

===================================== # #meeting:fedoraproject.org: Quality ===================================== Meeting started by @adamwill:fedora.im at 2025-03-03 16:01:33 Meeting summary --------------- * TOPIC: Roll Call (@adamwill:fedora.im, 16:01:37) * TOPIC: Previous meeting follow-up (@adamwill:fedora.im, 16:06:40) * INFO: no action items from previous meeting; since nobody objected to the proposed webui storage test cases and matrix changes, i'll put those live today (@adamwill:fedora.im, 16:07:07) * TOPIC: Fedora 42 status and Beta checkin (@adamwill:fedora.im, 16:11:11) * INFO: F42 Beta blocker review meeting is right after this meeting, first go/no-go is on Thursday (@adamwill:fedora.im, 16:11:53) * TOPIC: Test Day / community event status (@adamwill:fedora.im, 16:49:47) * INFO: the i18n test week starts tomorrow: https://testdays.fedoraproject.org/events/210 (@adamwill:fedora.im, 16:56:10) * TOPIC: Open floor (@adamwill:fedora.im, 16:56:28) Meeting ended at 2025-03-03 17:04:04 Action items ------------ People Present (lines said) --------------------------- * @adamwill:fedora.im (87) * @nielsenb:fedora.im (22) * @tablepc:fedora.im (22) * @lruzicka:matrix.org (6) * @zodbot:fedora.im (5) * @boniboyblue:fedora.im (2) * @derekenz:fedora.im (2) * @meetbot:fedora.im (2) -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org https://www.happyassassin.net

1 0

clazy failure on f42 beta
by Steven Trabert 19 Mar '25

19 Mar '25

Clazy is failing for me on the f42 beta. This is related to the default clang version, clang 20. It works if I set "export CLANGXX=/usr/bin/clang++-19", but without this: -- Check for working CXX compiler: /usr/bin/clazy -- Check for working CXX compiler: /usr/bin/clazy - broken CMake Error at /usr/share/cmake/Modules/CMakeTestCXXCompiler.cmake:73 (message): The C++ compiler "/usr/bin/clazy" is not able to compile a simple test program. It fails with the following output: Change Dir: '/home/tsteven4/gpsbabel/bld-clazy/CMakeFiles/CMakeScratch/TryCompile-0a90ti' Run Build Command(s): /usr/bin/ninja-build -v cmTC_d46b8 [1/2] /usr/bin/clazy -o CMakeFiles/cmTC_d46b8.dir/testCXXCompiler.cxx.o -c /home/tsteven4/gpsbabel/bld-clazy/CMakeFiles/CMakeScratch/TryCompile-0a90ti/testCXXCompiler.cxx FAILED: CMakeFiles/cmTC_d46b8.dir/testCXXCompiler.cxx.o /usr/bin/clazy -o CMakeFiles/cmTC_d46b8.dir/testCXXCompiler.cxx.o -c /home/tsteven4/gpsbabel/bld-clazy/CMakeFiles/CMakeScratch/TryCompile-0a90ti/testCXXCompiler.cxx PLEASE submit a bug report to https://github.com/llvm/llvm-project/issues/ and include the crash backtrace, preprocessed source, and associated run script. Stack dump: 0. Program arguments: clang++ -Qunused-arguments -Xclang -load -Xclang ClazyPlugin.so -Xclang -add-plugin -Xclang clazy -o CMakeFiles/cmTC_d46b8.dir/testCXXCompiler.cxx.o -c /home/tsteven4/gpsbabel/bld-clazy/CMakeFiles/CMakeScratch/TryCompile-0a90ti/testCXXCompiler.cxx 1. <eof> parser at end of file Stack dump without symbol names (ensure you have llvm-symbolizer in your PATH or set the environment var `LLVM_SYMBOLIZER_PATH` to point to it): 0 libLLVM.so.20.1 0x00007fe1a0c27eba llvm::sys::PrintStackTrace(llvm::raw_ostream&, int) + 58 1 libLLVM.so.20.1 0x00007fe1a0c24e44 llvm::sys::RunSignalHandlers() + 84 2 libLLVM.so.20.1 0x00007fe1a0b3ec44 3 libc.so.6 0x00007fe1a0426df0 4 ClazyPlugin.so 0x00007fe1a00ec71b ClazyASTConsumer::HandleTranslationUnit(clang::ASTContext&) + 155 5 libclang-cpp.so.20.1 0x00007fe1abb5be4c clang::MultiplexConsumer::HandleTranslationUnit(clang::ASTContext&) + 44 6 libclang-cpp.so.20.1 0x00007fe1a9412dc9 clang::ParseAST(clang::Sema&, bool, bool) + 777 7 libclang-cpp.so.20.1 0x00007fe1abb16d9f clang::FrontendAction::Execute() + 47 8 libclang-cpp.so.20.1 0x00007fe1aba7a754 clang::CompilerInstance::ExecuteAction(clang::FrontendAction&) + 1076 9 libclang-cpp.so.20.1 0x00007fe1abbaa85e clang::ExecuteCompilerInvocation(clang::CompilerInstance*) + 654 10 clang++ 0x000055cf43c85687 cc1_main(llvm::ArrayRef<char const*>, char const*, void*) + 8071 11 clang++ 0x000055cf43c81727 12 libclang-cpp.so.20.1 0x00007fe1ab61b5bd 13 libLLVM.so.20.1 0x00007fe1a0b3e950 llvm::CrashRecoveryContext::RunSafely(llvm::function_ref<void ()>) + 144 14 libclang-cpp.so.20.1 0x00007fe1ab61ae75 clang::driver::CC1Command::Execute(llvm::ArrayRef<std::optional<llvm::StringRef>>, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char>>*, bool*) const + 373 15 libclang-cpp.so.20.1 0x00007fe1ab5d7129 clang::driver::Compilation::ExecuteCommand(clang::driver::Command const&, clang::driver::Command const*&, bool) const + 553 16 libclang-cpp.so.20.1 0x00007fe1ab5d73e7 clang::driver::Compilation::ExecuteJobs(clang::driver::JobList const&, llvm::SmallVectorImpl<std::pair<int, clang::driver::Command const*>>&, bool) const + 151 17 libclang-cpp.so.20.1 0x00007fe1ab5f9f49 clang::driver::Driver::ExecuteCompilation(clang::driver::Compilation&, llvm::SmallVectorImpl<std::pair<int, clang::driver::Command const*>>&) + 489 18 clang++ 0x000055cf43c80b54 clang_main(int, char**, llvm::ToolContext const&) + 6452 19 clang++ 0x000055cf43c90978 main + 104 20 libc.so.6 0x00007fe1a04105f5 21 libc.so.6 0x00007fe1a04106a8 __libc_start_main + 136 22 clang++ 0x000055cf43c7ee05 _start + 37 clang++: error: clang frontend command failed with exit code 139 (use -v to see invocation) clang version 20.1.0 (Fedora 20.1.0-1.fc42) Target: x86_64-redhat-linux-gnu Thread model: posix InstalledDir: /usr/lib64/llvm20/bin Configuration file: /etc/clang/x86_64-redhat-linux-gnu-clang++.cfg clang++: note: diagnostic msg: ******************** PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT: Preprocessed source(s) and associated run script(s) are located at: clang++: note: diagnostic msg: /tmp/testCXXCompiler-7fb8b3.cpp clang++: note: diagnostic msg: /tmp/testCXXCompiler-7fb8b3.sh clang++: note: diagnostic msg: ******************** ninja: build stopped: subcommand failed. CMake will not be able to correctly generate this project. Call Stack (most recent call first): CMakeLists.txt:11 (project) -- Configuring incomplete, errors occurred!

1 0

A nice blocker bug for Fedora 42 final
by AV 19 Mar '25

19 Mar '25

This concerns a Dell Precision 5690 laptop with Intel Core Ultra7 155H CPU and Mesa Intel Arc graphics. This laptop was bought in 2023 with Ubuntu installed (It actually is an "Ubuntu Certified" laptop) and has been happily running Fedora Workstation ever since until I switched from Fedora 41 Workstation to Fedora 41 KDE in November 2024 because I wanted to try the new Plasma and use the KDE app "Info Center" for some system info. F41 with KDE also worked without problems. However it is impossible to install Fedora 42 beta on this laptop! I tried F42 beta Workstation live, F42 KDE live and F42 XFCE live. For example F42 KDE gets no further than the KDE Splash Screen and then the screen goes black with only the cursor visible (which can move (the 'blue screen of death' also made an appearance in the beginning)). The same goes for F42 beta Workstation if you substitute the Workstation analogs to KDE appearance. With XFCE live at least the desktop appeared and was completely configurable but the install itself also failed: after clicking the 'install' icon it seemed a small outline of a window wanted to appear on the screen but aborted. I did succeed in installing F42 beta (Workstation and KDE) using F42 beta 'Everything' and using 'DNF system-upgrade'. But with both methods the laptop went dead as a dodo after entering password and booting. Same as with the live installs. As a check I installed F42 beta on a Dell Inspiron 16 5625 with AMD Ryzen 7 5825U and Radeon Graphics. Both Workstation live and KDE live installed flawlessly and worked perfectly. No problems. I won't try to squeeze further info out of the Dell Precision. I am getting to old for these kind of shenanigans. Been wrestling with mainframes and VAXes and wrestling with OS/2 and since 1995 RedHat Linux (floppy disks) and later Fedora on PCs and laptops (and the occasional tryout of other distros). Though I might try Ubuntu 25.04 beta when it appears (after all it is an 'UBuntu Certified' machine). If that is no go then I will reinstall F41. To reproduce get a comparable Dell Precision 5690.

2 1

Using "Reinstall Fedora" on legacy BIOS machine with F42 Beta gives error "No devices found for boot loader partition 'biosboot'"
by Andre Robatino 17 Mar '25

17 Mar '25

I tried using "Reinstall Fedora" (F41 -> F42 Beta) on 2 legacy BIOS machines, using the GNOME Workstation Live, and got the above error with each. (On one of them, which is Fedora only, and only a small amount of data in home, I worked around it by using "Use entire disk".) I don't see anything in Bugzilla, or in the RC-1.4 Test Matrix. I'm guessing this has to do with installing over an existing installation? I clean install each new version of Fedora and have never seen this error before.

2 3

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

test