First Last Prev Next    This bug is not in your last search results.
Bug 1026022 - Unable to use wifi network after selecting "Minimal X Environment" (no iw, wpa_supplicant)
Unable to use wifi network after selecting "Minimal X Environment" (no iw, w...
Status: NEW
Classification: openSUSE
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Patterns
Current
x86-64 SUSE Other
: P5 - None : Minor (vote)
: ---
Assigned To: Dominique Leuenberger
E-mail List
https://trello.com/c/q1CuUYd1
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2017-02-18 08:59 UTC by João Pinto
Modified: 2023-03-08 13:19 UTC (History)
2 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description João Pinto 2017-02-18 08:59:47 UTC 
I have installed with the "Minimal X Environment" option with the expectation to setup a different windows manager (cinammon) after installing the system. I only have Wifi connectivity, and the detection and system install from the Net worked fine with it.

After installing the system, I have attempted to configure the network from YaST, however I have found that wifi's core packages were missing: "iw", "wpa_supplicant". Using the Net install option, and with only wifi connectivity I was unable to setup the network. 

The wifi core packages should be installed when using the "Minimal X Environment" system.
Comment 1 Josef Reidinger 2017-02-20 08:51:27 UTC 
Michal - does network proposal have such ability to mark required packages for working network?
Comment 2 Martin Vidner 2017-04-25 14:30:31 UTC 
I'm not sure about the installation proposal, but the network code does declare the needed packages, including `iw` and `wpa_supplicant`:
https://github.com/yast/yast-network/blob/c4cb236531d704a466b5a285af75261fd64dfda5/src/modules/Lan.rb#L889
Comment 3 Stefan Hundhammer 2023-03-08 13:06:31 UTC 
This is really a patterns problem.
First Last Prev Next    This bug is not in your last search results.