http://bugzilla.opensuse.org/show_bug.cgi?id=1199550 Dominique Leuenberger changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1199550 http://bugzilla.opensuse.org/show_bug.cgi?id=1199550#c1 Dominique Leuenberger changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |IN_PROGRESS --- Comment #1 from Dominique Leuenberger --- (In reply to Hans-Peter Jansen from comment #0)

Guess, this is related to the package separation, splitting off NetworkManager-wifi among other sub packages. The result of a zypper dup (over wifi of course) was, that the connection died after installing the NetworkManager package. It couldn't re-establish the connection after reboot (obviously).

Yes, that's indeed the reason here (and also why this was not yet forwarded to Factory, but only lives in the devel project). Preferably we would auto-trigger the -wifi subpackage based on wifi chips presence, but that might not work. As a short-term solution, I guess we will recommend -wifi from the main package

From my experience, ppl use NM due to wifi switching/hopping, hence a Recommends or Supplements like for tui would be advisable. Otherwise, you cut the rope, that connect our poor devices with the world and suggestions, like install NetworkManger-wifi might sound cynical to some of them, that have no alternative.. Switching to a wicked based config to fix the situation will probably work, but isn't the best UX.

Outdated experience. Nowadays NM is the primary network managing stuck on all openSUSE TUmbleweed installs, so even on servers with LAN-only connection (wicked is phasing out)

Expect more of these complaints until this is fixed.

Sure - that's what for we have devel projects :) to catch errors before people in the distro run into them :) So thanks for being a devel project tester

While at it, the relationship between wwan and blues escapes me. Usually, the wifi devices hosts bluetooth as well, rarely the wwan modems.

It's rather: when NetworkManager requires Bluetooth to connect to a network, it is most commonly to a 'mobile phone' that then opens a wwan connection Otherwise, NetworkManager would not do a Bluetooth connection -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1199550 http://bugzilla.opensuse.org/show_bug.cgi?id=1199550#c2 --- Comment #2 from Hans-Peter Jansen --- Hi Dominique,

...

Expect more of these complaints until this is fixed.

Sure - that's what for we have devel projects :) to catch errors before people in the distro run into them :) So thanks for being a devel project tester

My pleasure!

...

While at it, the relationship between wwan and blues escapes me. Usually, the wifi devices hosts bluetooth as well, rarely the wwan modems.

It's rather: when NetworkManager requires Bluetooth to connect to a network, it is most commonly to a 'mobile phone' that then opens a wwan connection

Otherwise, NetworkManager would not do a Bluetooth connection

Fair enough. Rev. 438 looks fine now, epecially the new release sounds promising. Will do some tests, especially around the former WPA2+WPA3 insufficiency (if not supported from wifi hardware), which might even allow to revert my revert from wpa_supplicant rev. 91. (bsc#1195312) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1199550 http://bugzilla.opensuse.org/show_bug.cgi?id=1199550#c3 Dominique Leuenberger changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED --- Comment #3 from Dominique Leuenberger --- Issue has been addressed -- You are receiving this mail because: You are on the CC list for the bug.