[SRU] no WiFi card, ends with segfault
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
horst (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Focal |
Won't Fix
|
Undecided
|
Unassigned | ||
Jammy |
Won't Fix
|
Undecided
|
Unassigned | ||
Lunar |
Won't Fix
|
Undecided
|
Unassigned | ||
Mantic |
Won't Fix
|
Undecided
|
Unassigned | ||
Noble |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[ Impact ]
The usage of horst is not affect and horst is perfectly usable on a system where a wifi hardware is present.
But if any user who does not have a wifi hardware executes horst then it will segfault which is unexpected and the user will not expect a segfault.
This ultimateley affects the user experience.
[ Test Plan ]
There needs to be two tests:
1. Execute horst on a system where wifi hardware is not present to confirm the segfault is fixed.
2. Execute horst on a system where wifi hardware is present and then horst should work normally.
[ Where problems could occur ]
The patch checks if the wifi interface, which horst will try to use, is present on the system or not. It will then exit gracefully if the interface is not present instead of trying to use a non-existent device. This is not changing any other part of the code and the check is added at the beginnning. So, there is very minimum chance of it affecting the normal functioning of horst.
[ Other Info ]
* All versions from Focal are affected by this.
[ Original Bug Description ]
Ubuntu 22.04.3, amd64
PC has no WiFi card. Horst crashes:
$ horst -v
5.1 (build date: Nov 28 2021 18:51:58)
$ horst
failed to find nl80211
Segmentation fault (core dumped)
$ gdb horst
...
(gdb) run
Starting program: /usr/sbin/horst
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_
failed to find nl80211
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff7e40bc6 in genl_family_get_id () from /lib/x86_
(gdb)
tags: | added: focal jammy lunar mantic noble |
Changed in horst (Ubuntu Focal): | |
status: | New → In Progress |
Changed in horst (Ubuntu Jammy): | |
status: | New → In Progress |
Changed in horst (Ubuntu Lunar): | |
status: | New → In Progress |
Changed in horst (Ubuntu Mantic): | |
status: | New → In Progress |
Changed in horst (Ubuntu Noble): | |
status: | New → In Progress |
Changed in horst (Ubuntu Focal): | |
assignee: | nobody → Sudip Mukherjee (sudipmuk) |
Changed in horst (Ubuntu Jammy): | |
assignee: | nobody → Sudip Mukherjee (sudipmuk) |
Changed in horst (Ubuntu Lunar): | |
assignee: | nobody → Sudip Mukherjee (sudipmuk) |
Changed in horst (Ubuntu Mantic): | |
assignee: | nobody → Sudip Mukherjee (sudipmuk) |
Changed in horst (Ubuntu Noble): | |
assignee: | nobody → Sudip Mukherjee (sudipmuk) |
Changed in horst (Ubuntu Noble): | |
status: | Confirmed → In Progress |
Changed in horst (Ubuntu Mantic): | |
status: | Confirmed → In Progress |
I have now tested and I can reproduce the problem in all releases from Noble, Mantic, Lunar, Jammy and Focal.