| Summary: | Info Center crashed in findNICs() | ||
|---|---|---|---|
| Product: | [Applications] kinfocenter | Reporter: | mrbscottc |
| Component: | general | Assignee: | David Hubner <hubn3rd> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | nate, sitter |
| Priority: | NOR | Keywords: | drkonqi |
| Version First Reported In: | 5.18.0 | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | https://commits.kde.org/kinfocenter/8cb749531a3c3ab139e51bd1f741edddccf69873 | Version Fixed/Implemented In: | 5.18.1 |
| Sentry Crash Report: | |||
|
Description
mrbscottc
2020-02-17 17:44:09 UTC
What's the output of `ip a` on your system? Git commit 8cb749531a3c3ab139e51bd1f741edddccf69873 by Harald Sitter.
Committed on 18/02/2020 at 09:29.
Pushed by sitter into branch 'Plasma/5.18'.
make sure ifa_addr isn't null
Summary:
the manpage:
The ifa_addr field points to a structure containing the interface
address. (The sa_family subfield should be consulted to determine
the format of the address structure.) This field may contain a null
pointer.
why that exactly happens I do not know in absence of more debug info.
I expect it's something to do with an interface being up but not quite
somehow. I utterly failed to simulate this though :|
because of that I do not know if such a device has any use being listed,
and I am adding some possibly relevant debug output in the hopes of
maybe getting some data reported.
if these devices still turn out useful, the MyNIC construction needs
partially moving before the ifa_addr check.
FIXED-IN: 5.18.1
Test Plan: hoping for the best!
Reviewers: ngraham
Subscribers: plasma-devel
Tags: #plasma
Differential Revision: https://phabricator.kde.org/D27467
M +7 -0 Modules/nics/nic.cpp
https://commits.kde.org/kinfocenter/8cb749531a3c3ab139e51bd1f741edddccf69873
|