Bug 2340697
| Summary: | kismet: FTBFS in Fedora rawhide/f42 | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Fedora Release Engineering <releng> | ||||||||||
| Component: | kismet | Assignee: | Gwyn Ciesla <gwync> | ||||||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||
| Priority: | unspecified | ||||||||||||
| Version: | 42 | CC: | atu.guda, awilliam, gwync, rh-bugzilla | ||||||||||
| Target Milestone: | --- | ||||||||||||
| Target Release: | --- | ||||||||||||
| Hardware: | Unspecified | ||||||||||||
| OS: | Unspecified | ||||||||||||
| Whiteboard: | |||||||||||||
| Fixed In Version: | kismet-0.0.2023.07.R2-1.fc42 | Doc Type: | If docs needed, set a value | ||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2025-08-03 01:14:30 UTC | Type: | --- | ||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||
| Documentation: | --- | CRM: | |||||||||||
| Verified Versions: | Category: | --- | |||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||
| Embargoed: | |||||||||||||
| Bug Depends On: | |||||||||||||
| Bug Blocks: | 2300528, 2382580 | ||||||||||||
| Attachments: |
|
||||||||||||
|
Description
Fedora Release Engineering
2025-01-22 20:39:06 UTC
Created attachment 2070628 [details]
build.log
file build.log too big, will only attach last 32768 bytes
Created attachment 2070629 [details]
root.log
file root.log too big, will only attach last 32768 bytes
Created attachment 2070630 [details]
state.log
This bug appears to have been reported against 'rawhide' during the Fedora Linux 42 development cycle. Changing version to 42. Looks to me like https://github.com/kismetwireless/kismet/commit/82e0ca25d54af40e59fe7f3e08c60ef02c8b51a3 fixed this, but we have a version before that landed. So updating to a newer version should help... You'd think, but I don't see those changes in -R2. That commit also doesn't apply cleanly, but I'll see if I can backport. Created attachment 2098079 [details]
more simple patch to build 2023-07-R2
I succeeded to build 2023-07-R2 with this patch.
That works! Please redeem this comment for 2 beverages of your choice if we're ever in the same physical location. Thank you! Still fails on ppc64le: https://kojipkgs.fedoraproject.org//work/tasks/5360/135205360/build.log Simply not applying the patch to ppc64le seems to fix it. Why does the patch comment out an fclose? That seems unrelated. Good question. I'll try a build without and drop it if works. Issue with fclose was detected by gcc - if we failed to open a file, it's useless to close. In this case fclose receives null pointer, and man pages says nothing about such condition. FEDORA-2025-518b2c4a0f (kismet-0.0.2023.07.R2-1.fc42) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2025-518b2c4a0f (In reply to Anton Guda from comment #13) > Issue with fclose was detected by gcc - if we failed to open a file, it's > useless to close. > In this case fclose receives null pointer, and man pages says nothing about > such condition. Ok. I'll leave it out for now, and see what upstream does. FEDORA-2025-518b2c4a0f has been pushed to the Fedora 42 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-518b2c4a0f` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-518b2c4a0f See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2025-518b2c4a0f (kismet-0.0.2023.07.R2-1.fc42) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report. |