After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 764332 - connections doesn't work after update to 1.2.0-0.7.beta2.fc25
connections doesn't work after update to 1.2.0-0.7.beta2.fc25
Status: RESOLVED FIXED
Product: NetworkManager
Classification: Platform
Component: general
1.2.x
Other Linux
: Normal major
: ---
Assigned To: NetworkManager maintainer(s)
NetworkManager maintainer(s)
Depends on:
Blocks: nm-1-2
 
 
Reported: 2016-03-29 20:24 UTC by Igor Gnatenko
Modified: 2016-03-30 13:15 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
logs from broken version with debuglevel (88.79 KB, text/plain)
2016-03-30 07:28 UTC, Igor Gnatenko
Details
Suggested fix (3.82 KB, text/plain)
2016-03-30 11:15 UTC, Lubomir Rintel
Details

Description Igor Gnatenko 2016-03-29 20:24:55 UTC
Usually I see:
DEVICE      TYPE      STATE      CONNECTION 
virbr0      bridge    connected  virbr0     
wlp3s0      wifi      connected  Brain      
lo          loopback  unmanaged  --         
virbr0-nic  tun       unmanaged  --    

But after update it got to:
DEVICE      TYPE      STATE        CONNECTION
cdc-wdm2    gsm       unavailable  --
virbr0-nic  ethernet  unmanaged    --

I'm using Fedora 25 (Rawhide).
It works with version 1.2.0-0.6.beta2.fc25.x86_64 and does not with 1.2.0-0.7.beta2.fc25.

I was looking to Fedora's git and found only two changes between:
1. http://pkgs.fedoraproject.org/cgit/rpms/NetworkManager.git/commit/?id=f561df45ac8a825e67ea29bf91894b1204d66ddd
2. http://pkgs.fedoraproject.org/cgit/rpms/NetworkManager.git/commit/?id=bb908ed4e4ef876e97618d33b355aec73c3ee0f1

I guess first patch could be a problem.

I don't see anything strange in logs of NM/wpa_supplicant (to be precised that there is nothing in wpa_supplicant logs which means that it does not go to wpa_supplicant). I tried to enable debug loglevel in NM but there was nothing interesting.
Mar 29 22:09:31 x1carbon.localdomain NetworkManager[1233]: <debug> [1459282171.2890] manager: WiFi hw-enabled 1 sw-enabled 1

and after that nothing.

Once I downgraded NM it started working again.

03:00.0 Network controller [0280]: Intel Corporation Centrino Advanced-N 6205 [Taylor Peak] [8086:0085] (rev 96)
	Subsystem: Intel Corporation Device [8086:c220]
	Flags: bus master, fast devsel, latency 0, IRQ 31
	Memory at f0c00000 (64-bit, non-prefetchable) [size=8K]
	Capabilities: [c8] Power Management version 3
	Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
	Capabilities: [e0] Express Endpoint, MSI 00
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [140] Device Serial Number 84-3a-4b-ff-ff-cf-eb-84
	Kernel driver in use: iwlwifi
	Kernel modules: iwlwifi



Let me know if some more information is required.
Comment 1 Igor Gnatenko 2016-03-29 20:25:48 UTC
I also tried to update to beta3 version which also didn't help. My guessing is something broken in that patch.
Comment 2 Beniamino Galvani 2016-03-29 21:59:07 UTC
I'm using 1.2.0-0.6.beta2.fc25.x86_64 on Rawhide and I don't see the problem. Would it be possible for you to attach NM logs with debug log level (set level=DEBUG in the logging section of NetworkManager.conf and restart NM)? Thanks.
Comment 3 Igor Gnatenko 2016-03-30 07:27:22 UTC
Broken version:
[brain@x1carbon ~]$ nmcli d
DEVICE    TYPE  STATE        CONNECTION 
cdc-wdm2  gsm   unavailable  --         

Working version:
[brain@x1carbon ~]$ nmcli d
DEVICE      TYPE      STATE         CONNECTION 
virbr0      bridge    connected     virbr0     
wlp3s0      wifi      disconnected  --         
cdc-wdm2    gsm       unavailable   --         
lo          loopback  unmanaged     --         
virbr0-nic  tun       unmanaged     --         


Attaching logs.
Comment 4 Igor Gnatenko 2016-03-30 07:28:01 UTC
(In reply to Beniamino Galvani from comment #2)
> I'm using 1.2.0-0.6.beta2.fc25.x86_64 on Rawhide and I don't see the
> problem. Would it be possible for you to attach NM logs with debug log level
> (set level=DEBUG in the logging section of NetworkManager.conf and restart
> NM)? Thanks.

And btw you have correct version - it works here as well, update to -0.7.beta2
Comment 5 Igor Gnatenko 2016-03-30 07:28:27 UTC
Created attachment 324990 [details]
logs from broken version with debuglevel
Comment 6 Beniamino Galvani 2016-03-30 07:59:51 UTC
(In reply to Igor Gnatenko from comment #4)
> (In reply to Beniamino Galvani from comment #2)
> > I'm using 1.2.0-0.6.beta2.fc25.x86_64 on Rawhide and I don't see the
> > problem.
>
> And btw you have correct version - it works here as well, update to
> -0.7.beta2

Sorry, I meant NetworkManager-1.2.0-0.7.beta2. What seems strange is that I see a different log format (the new one), while the logs you attached still have the old one. Seems like the packages we are using are different... I have no idea why.
Comment 7 Lubomir Rintel 2016-03-30 11:15:03 UTC
Created attachment 325002 [details]
Suggested fix
Comment 8 Beniamino Galvani 2016-03-30 11:50:49 UTC
(In reply to Lubomir Rintel from comment #7)
> Created attachment 325002 [details]

Looks good.
Comment 9 Lubomir Rintel 2016-03-30 12:40:48 UTC
This problem has been fixed in the unstable development version. The fix will be available in the next major software release. You may need to upgrade your Linux distribution to obtain that newer version.