[SOLVED] New systemd/gnome3.6 wifi connects fail after screen off/on

keepitsimpleengineer · 2012-11-15 00:08:01

A new, clean systemd/Gnome 3.6 install on Lenovo S12 32bit Intel Atom (cheap) laptop. Broadcom WiFi chip, driver and firmware installed.

Pretty happy, seems everything I use works, except...

If ignored for a bit, the screen goes dark. When re-illuminated, NetworkManager has dropped connection and will not (re)connect to WiFi, or connect to a 2ndary WiFi channel.

A pop-up opens asking for the password, which it has, the text-box filled with a bunch of "•"s.

It has the correct passwords, and always reconnects when system restarted (rebooted). NetworkManager worked normally with a prior distro (Ubuntu12.04).

The lap top is set to never suspend. If the screen off/on is not too long, the connection will be kept

I'm pretty much old school and don't use WiFi or the new desktops that much, although I do like systemd.

I grepped 'NetworkManager' from journalctl, but don't quite know what to look for. It's at pastebin. http://pastebin.com/sDruQCZH

Shown as far as I can tell, the failed attempts to connect to kise (default) and kise2 (2ndary), then after restart normal connection.

Any suggestions about where to look or a solution would be greatly appreciated

Last edited by keepitsimpleengineer (2012-12-13 16:09:55)

keepitsimpleengineer · 2012-11-28 18:08:00

An Internet search revealed that the wireless network may be configured with power management set to 'on'.

I installed 'wireless_tools' from packages and ran 'iwconfig'.

It reported "Power Management:off".

keepitsimpleengineer · 2012-11-28 18:15:36

An internet search revealed that NetworkManager may have problems with netcfg. I checked the systemctl status of netcfg and it was not running.

Since it is not used, I removed the package 'netcfg', basically in hope that this would solved the problem.

The problems still remains.

Last edited by keepitsimpleengineer (2012-11-28 21:24:28)

10PinkPanther · 2012-11-28 18:53:53

Hi!

What wireless card do you have?What driver?It would be good to check "Broadcom wireless" in wiki.It helped me with my Broadcom 4312,b43,b43-fwcutter and b43-firmware.

keepitsimpleengineer · 2012-11-28 20:27:47

10PinkPanther wrote:

Hi!
What wireless card do you have?What driver?It would be good to check "Broadcom wireless" in wiki.It helped me with my Broadcom 4312,b43,b43-fwcutter and b43-firmware.

This has been done. Broadcom 4313,b43,b43-fwcutter and b43-firmware. All installed and verified, no connection possible without these.

keepitsimpleengineer · 2012-11-28 20:57:25

I finally got ssh working (sshd.service must be enabled and started, as they are not enabled by default in the new systemd) and figured out some of the things about journalctl.

I booted the S12 at 4:30 p.m. yesterday and this morning it had lost the Wi-Fi connection over night.

I ran journalctl --since="2012-11-27 16:28:06" --until="2012-11-28 07:37:53" _SYSTEMD_UNIT=NetworkManager.service and pasted the results at http://pastebin.com/6e9BNvmD. (Note: journalctl ignored --until="2012-11-28 07:37:53" but I edited out the excess lines.
--until=
From this there are some troubling things...

This line (with different time tags) appears often...

Nov 27 19:17:28 KISE-007 NetworkManager[223]: <warn> nl_recvmsgs() error: (-33) Dump inconsistency detected, interrupted

An internet search shows bug reports related to VPN, which I don't use.

And this was me trying to connect manually the next morning...

Nov 28 00:07:27 KISE-007 NetworkManager[223]: <info> (wlan0): supplicant interface state: completed -> disconnected
Nov 28 00:07:27 KISE-007 NetworkManager[223]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Nov 28 00:07:29 KISE-007 NetworkManager[223]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Nov 28 00:07:29 KISE-007 NetworkManager[223]: <info> (wlan0): supplicant interface state: authenticating -> associating
Nov 28 00:07:29 KISE-007 NetworkManager[223]: <info> (wlan0): supplicant interface state: associating -> 4-way handshake
Nov 28 00:07:39 KISE-007 NetworkManager[223]: <info> (wlan0): supplicant interface state: 4-way handshake -> disconnected
Nov 28 00:07:40 KISE-007 NetworkManager[223]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Nov 28 00:07:41 KISE-007 NetworkManager[223]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Nov 28 00:07:41 KISE-007 NetworkManager[223]: <info> (wlan0): supplicant interface state: authenticating -> associating
Nov 28 00:07:41 KISE-007 NetworkManager[223]: <info> (wlan0): supplicant interface state: associating -> associated
Nov 28 00:07:41 KISE-007 NetworkManager[223]: <info> (wlan0): supplicant interface state: associated -> 4-way handshake
Nov 28 00:07:42 KISE-007 NetworkManager[223]: <warn> (wlan0): link timed out.

Hoping for some insight here...

Edit: Here is the full journalctl output covering time the connection was dropped...

Nov 27 18:06:09 KISE-007 dbus-daemon[227]: dbus[227]: [system] Rejected send message, 2 matched rules; type="method_return", sender=":1.1" (uid=0 pid=224 comm="/usr/lib/systemd/systemd-logind ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.10" (uid=1000 pid=283 comm="gnome-s
Nov 27 18:06:09 KISE-007 dbus[227]: [system] Rejected send message, 2 matched rules; type="method_return", sender=":1.1" (uid=0 pid=224 comm="/usr/lib/systemd/systemd-logind ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.10" (uid=1000 pid=283 comm="gnome-session ")
Nov 27 18:11:58 KISE-007 NetworkManager[223]: <warn> nl_recvmsgs() error: (-33) Dump inconsistency detected, interrupted
Nov 27 18:19:25 KISE-007 upowerd[336]: (upowerd:336): UPower-Linux-WARNING **: energy 51.440000 bigger than full 47.680000
Nov 27 19:17:28 KISE-007 NetworkManager[223]: <warn> nl_recvmsgs() error: (-33) Dump inconsistency detected, interrupted
Nov 27 19:41:46 KISE-007 NetworkManager[223]: <warn> nl_recvmsgs() error: (-33) Dump inconsistency detected, interrupted
Nov 27 19:44:46 KISE-007 NetworkManager[223]: <warn> nl_recvmsgs() error: (-33) Dump inconsistency detected, interrupted
Nov 27 19:57:16 KISE-007 NetworkManager[223]: <warn> nl_recvmsgs() error: (-33) Dump inconsistency detected, interrupted
Nov 27 21:25:15 KISE-007 dbus-daemon[227]: dbus[227]: [system] Rejected send message, 2 matched rules; type="method_return", sender=":1.1" (uid=0 pid=224 comm="/usr/lib/systemd/systemd-logind ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.10" (uid=1000 pid=283 comm="gnome-s
Nov 27 21:25:15 KISE-007 dbus[227]: [system] Rejected send message, 2 matched rules; type="method_return", sender=":1.1" (uid=0 pid=224 comm="/usr/lib/systemd/systemd-logind ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.10" (uid=1000 pid=283 comm="gnome-session ")
Nov 27 21:35:15 KISE-007 dbus-daemon[227]: dbus[227]: [system] Rejected send message, 2 matched rules; type="method_return", sender=":1.1" (uid=0 pid=224 comm="/usr/lib/systemd/systemd-logind ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.10" (uid=1000 pid=283 comm="gnome-s
Nov 27 21:35:15 KISE-007 dbus[227]: [system] Rejected send message, 2 matched rules; type="method_return", sender=":1.1" (uid=0 pid=224 comm="/usr/lib/systemd/systemd-logind ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.10" (uid=1000 pid=283 comm="gnome-session ")
Nov 27 21:38:22 KISE-007 NetworkManager[223]: <warn> nl_recvmsgs() error: (-33) Dump inconsistency detected, interrupted
Nov 27 22:49:34 KISE-007 NetworkManager[223]: <warn> nl_recvmsgs() error: (-33) Dump inconsistency detected, interrupted
Nov 27 22:51:34 KISE-007 NetworkManager[223]: <warn> nl_recvmsgs() error: (-33) Dump inconsistency detected, interrupted
Nov 27 23:36:10 KISE-007 NetworkManager[223]: <warn> nl_recvmsgs() error: (-33) Dump inconsistency detected, interrupted
Nov 27 23:44:12 KISE-007 dbus-daemon[227]: dbus[227]: [system] Rejected send message, 2 matched rules; type="method_return", sender=":1.1" (uid=0 pid=224 comm="/usr/lib/systemd/systemd-logind ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.10" (uid=1000 pid=283 comm="gnome-s
Nov 27 23:44:12 KISE-007 dbus[227]: [system] Rejected send message, 2 matched rules; type="method_return", sender=":1.1" (uid=0 pid=224 comm="/usr/lib/systemd/systemd-logind ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.10" (uid=1000 pid=283 comm="gnome-session ")
Nov 27 23:47:40 KISE-007 NetworkManager[223]: <warn> nl_recvmsgs() error: (-33) Dump inconsistency detected, interrupted
Nov 27 23:47:46 KISE-007 NetworkManager[223]: <warn> nl_recvmsgs() error: (-33) Dump inconsistency detected, interrupted
Nov 27 23:50:40 KISE-007 NetworkManager[223]: <warn> nl_recvmsgs() error: (-33) Dump inconsistency detected, interrupted
Nov 27 23:53:58 KISE-007 NetworkManager[223]: <warn> nl_recvmsgs() error: (-33) Dump inconsistency detected, interrupted
Nov 27 23:54:12 KISE-007 dbus-daemon[227]: dbus[227]: [system] Rejected send message, 2 matched rules; type="method_return", sender=":1.1" (uid=0 pid=224 comm="/usr/lib/systemd/systemd-logind ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.10" (uid=1000 pid=283 comm="gnome-s
Nov 27 23:54:12 KISE-007 dbus[227]: [system] Rejected send message, 2 matched rules; type="method_return", sender=":1.1" (uid=0 pid=224 comm="/usr/lib/systemd/systemd-logind ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.10" (uid=1000 pid=283 comm="gnome-session ")
Nov 27 23:54:46 KISE-007 NetworkManager[223]: <warn> nl_recvmsgs() error: (-33) Dump inconsistency detected, interrupted
Nov 27 23:56:40 KISE-007 NetworkManager[223]: <warn> nl_recvmsgs() error: (-33) Dump inconsistency detected, interrupted
Nov 27 23:57:46 KISE-007 NetworkManager[223]: <warn> nl_recvmsgs() error: (-33) Dump inconsistency detected, interrupted
Nov 28 00:00:34 KISE-007 NetworkManager[223]: <warn> nl_recvmsgs() error: (-33) Dump inconsistency detected, interrupted
Nov 28 00:00:58 KISE-007 NetworkManager[223]: <warn> nl_recvmsgs() error: (-33) Dump inconsistency detected, interrupted
Nov 28 00:02:58 KISE-007 NetworkManager[223]: <warn> nl_recvmsgs() error: (-33) Dump inconsistency detected, interrupted
Nov 28 00:06:04 KISE-007 NetworkManager[223]: <warn> nl_recvmsgs() error: (-33) Dump inconsistency detected, interrupted
Nov 28 00:07:27 KISE-007 kernel: wlan0: deauthenticated from 00:18:f8:f9:63:74 (Reason: 7)
Nov 28 00:07:27 KISE-007 kernel: cfg80211: Calling CRDA to update world regulatory domain
Nov 28 00:07:27 KISE-007 NetworkManager[223]: <info> (wlan0): supplicant interface state: completed -> disconnected
Nov 28 00:07:27 KISE-007 NetworkManager[223]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Nov 28 00:07:29 KISE-007 kernel: wlan0: authenticate with 00:18:f8:f9:63:74
Nov 28 00:07:29 KISE-007 kernel: wlan0: send auth to 00:18:f8:f9:63:74 (try 1/3)
Nov 28 00:07:29 KISE-007 kernel: wlan0: authenticated
Nov 28 00:07:29 KISE-007 NetworkManager[223]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Nov 28 00:07:29 KISE-007 kernel: b43 ssb0:0: wlan0: disabling HT as WMM/QoS is not supported
Nov 28 00:07:29 KISE-007 kernel: wlan0: associate with 00:18:f8:f9:63:74 (try 1/3)
Nov 28 00:07:29 KISE-007 NetworkManager[223]: <info> (wlan0): supplicant interface state: authenticating -> associating
Nov 28 00:07:29 KISE-007 kernel: wlan0: RX AssocResp from 00:18:f8:f9:63:74 (capab=0x431 status=0 aid=1)
Nov 28 00:07:29 KISE-007 kernel: wlan0: associated
Nov 28 00:07:29 KISE-007 NetworkManager[223]: <info> (wlan0): supplicant interface state: associating -> 4-way handshake
Nov 28 00:07:39 KISE-007 kernel: wlan0: disassociating from 00:18:f8:f9:63:74 by local choice (reason=3)
Nov 28 00:07:39 KISE-007 kernel: wlan0: deauthenticating from 00:18:f8:f9:63:74 by local choice (reason=3)
Nov 28 00:07:39 KISE-007 kernel: cfg80211: Calling CRDA to update world regulatory domain
Nov 28 00:07:39 KISE-007 NetworkManager[223]: <info> (wlan0): supplicant interface state: 4-way handshake -> disconnected
Nov 28 00:07:40 KISE-007 NetworkManager[223]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Nov 28 00:07:41 KISE-007 kernel: wlan0: authenticate with 00:18:f8:f9:63:74
Nov 28 00:07:41 KISE-007 kernel: wlan0: send auth to 00:18:f8:f9:63:74 (try 1/3)
Nov 28 00:07:41 KISE-007 kernel: wlan0: authenticated
Nov 28 00:07:41 KISE-007 kernel: b43 ssb0:0: wlan0: disabling HT as WMM/QoS is not supported
Nov 28 00:07:41 KISE-007 NetworkManager[223]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Nov 28 00:07:41 KISE-007 kernel: wlan0: associate with 00:18:f8:f9:63:74 (try 1/3)
Nov 28 00:07:41 KISE-007 kernel: wlan0: RX AssocResp from 00:18:f8:f9:63:74 (capab=0x431 status=0 aid=1)
Nov 28 00:07:41 KISE-007 kernel: wlan0: associated
Nov 28 00:07:41 KISE-007 NetworkManager[223]: <info> (wlan0): supplicant interface state: authenticating -> associating

Last edited by keepitsimpleengineer (2012-11-28 21:03:05)

10PinkPanther · 2012-11-28 21:07:02

Do you have netcfg enabled together with network manager?It can get in conflict and cause disconnection.If you have disable one of them.
EDIT:Oops,I didn't see your post about you already removing netcfg.Sorry.

Last edited by 10PinkPanther (2012-11-28 21:21:34)

keepitsimpleengineer · 2012-11-28 21:14:01

One more thing, may not be revalent but it's worrisome. NetworkManager takes a long time to start in the boot process.

[root@KISE-007 Desktop]# systemd-analyze blame
 85761ms NetworkManager.service
  4436ms sshdgenkeys.service
  4426ms polkit.service
  3977ms accounts-daemon.service
  3952ms gdm.service
  2712ms systemd-remount-fs.service
  2680ms systemd-logind.service
  2479ms systemd-vconsole-setup.service
  2164ms systemd-binfmt.service
  1449ms systemd-sysctl.service
  1431ms dev-mqueue.mount
  1424ms dev-hugepages.mount
  1419ms sys-kernel-debug.mount
  1370ms proc-sys-fs-binfmt_misc.mount
  1211ms systemd-udevd.service
  1177ms systemd-udev-trigger.service
  1029ms wpa_supplicant.service
   919ms systemd-tmpfiles-setup.service
   605ms rtkit-daemon.service
   600ms colord.service
   417ms udisks2.service
   405ms systemd-user-sessions.service
   281ms tmp.mount
   227ms upower.service
   171ms dev-sda2.swap
     3ms sys-fs-fuse-connections.mount

keepitsimpleengineer · 2012-11-28 21:22:04

10PinkPanther wrote:

Do you have netcfg enabled together with network manager?It can get in conflict and cause disconnection.If you have disable one of them.

I checked and is was not enabled. To be safe I removed the netcfg package.

Here is the status of the related packages...

[root@KISE-007 Desktop]# systemctl status net-auto-wireless
net-auto-wireless.service
          Loaded: error (Reason: No such file or directory)
          Active: inactive (dead)

[root@KISE-007 Desktop]# systemctl status net-auto-wired
net-auto-wired.service
          Loaded: error (Reason: No such file or directory)
          Active: inactive (dead)

Nov 26 19:32:18 KISE-007 ifplugd[199]: Initialization complete, link beat not detected.
Nov 27 00:29:05 KISE-007 ifplugd[199]: Exiting.
Nov 27 00:29:05 KISE-007 systemd[1]: Stopped Provides automatic netcfg wired connection.
Nov 27 14:56:26 KISE-007 ifplugd[220]: ifplugd 0.28 initializing.
Nov 27 14:56:26 KISE-007 ifplugd[220]: Using interface eth0/00:1F:16:2B:6F:85 with driver <tg3> (version: 3.124)
Nov 27 14:56:26 KISE-007 ifplugd[220]: Using detection mode: SIOCETHTOOL
Nov 27 14:56:26 KISE-007 ifplugd[220]: Initialization complete, link beat not detected.
Nov 27 16:28:06 KISE-007 ifplugd[220]: Exiting.
Nov 27 16:28:06 KISE-007 systemd[1]: Stopped Provides automatic netcfg wired connection.
Nov 27 16:28:06 KISE-007 systemd[1]: Unit net-auto-wired.service entered failed state

keepitsimpleengineer · 2012-11-28 23:14:26

So I thought I would try a different wireless connector and let it sit overnight, and see what happens. I have a TP-LINK USB Wi-Fi USB dongle as a spare, which I'll use.

That plan was scotched (hopefully temporarily) when Network Manager failed to connect to the AP using the USB dongle.

It insisted that it needed a password, which when checked, it had the proper password. This is similar to the behavior of the original connection after it was dropped.

Maybe I'll get a chance to look at this tomorrow...

keepitsimpleengineer · 2012-11-30 17:38:38

keepitsimpleengineer wrote:

Maybe I'll get a chance to look at this tomorrow...

I decided to file an upstream bug report .
https://bugzilla.gnome.org/show_bug.cgi?id=689366

keepitsimpleengineer · 2012-12-02 19:53:44

New behavior, drops connection without notification in Notification Tray.

This morning the laptop did not show the connection as dropped, but when I tried to use it, I got no connection.

I am about 1 nano-meter from deprecating Gnome 3.6.

Last edited by keepitsimpleengineer (2012-12-02 19:54:03)

keepitsimpleengineer · 2012-12-09 21:37:32

I dropped Gnome 3.6 and attempted a Frugalware install, but it wanted me to move the primary partition (WinXP) so I forwent completing it.

I then did a fresh Archlinux(2012.12.01)/Xfce4 install with NetworkManager and am experiencing very nearly the same problem, the difference being that xset s off and xset -dpms work to keep the laptop up all night.

Also similar problems have been reported with Ubuntu.

So I conclude it is a NetworkManager problem.

I think I will try Netcfg.

keepitsimpleengineer · 2012-12-09 22:26:16

Checked on upstream bug and found these related bugs:
• needlessly asks for wpa passphrase
• Mobile broadband does not reconnect
• NM-Applet no longer connects after extended use on a roaming ESSID
• Reconnection
• Network Manager won't maintain a WLAN connection when wicd will

And from Ubuntu's Launchpad, affecting 179 users...
• Wireless connection frequently drops [deauthenticating by local choice (reason=3)]

I think I will file another.

EDIT: Filed wireless connection drops, asks for unneeded password, fails reconnect, restart req'd and prior bug marked as duplicate.

Last edited by keepitsimpleengineer (2012-12-09 22:59:01)

keepitsimpleengineer · 2012-12-12 19:59:13

Frustrated with NetworkManager, I replaced it with netcfg.

It too drops the network connection after a long period of none use.

It also reports 12Mb/s versus the 48-52Mb/s when the system is running WinXP.

Now very frustrated....

bgc1954 · 2012-12-12 20:33:55

Have you seen and tried https://bbs.archlinux.org/viewtopic.php?id=150160&p=2

There are countless posts about b43 dropping out with a plethera of suggestions on solving it...or not.

You seem to be bumping your thread endlessly--even on the same day, within minutes or hours. It makes your thread look like its gettting alot of activity so some might not bother to look at your post--and it's not the best forum etiquette.

keepitsimpleengineer · 2012-12-12 22:57:19

bgc1954 wrote:

Have you seen and tried https://bbs.archlinux.org/viewtopic.php?id=150160&p=2
There are countless posts about b43 dropping out with a plethera of suggestions on solving it...or not.
You seem to be bumping your thread endlessly--even on the same day, within minutes or hours. It makes your thread look like its gettting alot of activity so some might not bother to look at your post--and it's not the best forum etiquette.

Thanks for the tip on bumping and thanks for the tip on the thread, which I had not seen. The thread was interesting and could be useful, but I suspect the culprit has been found.

There is a module loaded on Lenovo, acer_vmi, which caused problems with the Broadcom 4312 WiFi chip, supposedly fixed in kernel 2.6. … - the symptoms being no connection at all - and the fix being to blacklist it. The error messages were similar to mine.

Further, there have been changes in using bcma/brcmsmac modules with the early 3. … kernels. My suspicion is there is a new problem with the acer_vmi module. I have blacklisted it and we will see in the morning if that's the cure.

Re: Bumping - each post has had new information, and there have now 17 posts over 28 days, compared to 44 posts over 11 days for https://bbs.archlinux.org/viewtopic.php?id=150160&p=2. I didn't see this as bumping, and if I'm in error I apologize.

keepitsimpleengineer · 2012-12-13 16:09:20

Well, blacklisting acer_wmi did not solve the problem. It dropped the connection within a few hours.

So I removed netcfg and installed wicd. The connection sustained itself overnight. Boy was I happy.

It had been my understanding that development/support of wicd had ended, but I was wrong about that.

Arch Linux

#1 2012-11-15 00:08:01

[SOLVED] New systemd/gnome3.6 wifi connects fail after screen off/on

#2 2012-11-28 18:08:00

Re: [SOLVED] New systemd/gnome3.6 wifi connects fail after screen off/on

#3 2012-11-28 18:15:36

Re: [SOLVED] New systemd/gnome3.6 wifi connects fail after screen off/on

#4 2012-11-28 18:53:53

Re: [SOLVED] New systemd/gnome3.6 wifi connects fail after screen off/on

#5 2012-11-28 20:27:47

Re: [SOLVED] New systemd/gnome3.6 wifi connects fail after screen off/on

#6 2012-11-28 20:57:25

Re: [SOLVED] New systemd/gnome3.6 wifi connects fail after screen off/on

#7 2012-11-28 21:07:02

Re: [SOLVED] New systemd/gnome3.6 wifi connects fail after screen off/on

#8 2012-11-28 21:14:01

Re: [SOLVED] New systemd/gnome3.6 wifi connects fail after screen off/on

#9 2012-11-28 21:22:04

Re: [SOLVED] New systemd/gnome3.6 wifi connects fail after screen off/on

#10 2012-11-28 23:14:26

Re: [SOLVED] New systemd/gnome3.6 wifi connects fail after screen off/on

#11 2012-11-30 17:38:38

Re: [SOLVED] New systemd/gnome3.6 wifi connects fail after screen off/on

#12 2012-12-02 19:53:44

Re: [SOLVED] New systemd/gnome3.6 wifi connects fail after screen off/on

#13 2012-12-09 21:37:32

Re: [SOLVED] New systemd/gnome3.6 wifi connects fail after screen off/on

#14 2012-12-09 22:26:16

Re: [SOLVED] New systemd/gnome3.6 wifi connects fail after screen off/on

#15 2012-12-12 19:59:13

Re: [SOLVED] New systemd/gnome3.6 wifi connects fail after screen off/on

#16 2012-12-12 20:33:55

Re: [SOLVED] New systemd/gnome3.6 wifi connects fail after screen off/on

#17 2012-12-12 22:57:19

Re: [SOLVED] New systemd/gnome3.6 wifi connects fail after screen off/on

#18 2012-12-13 16:09:20

Re: [SOLVED] New systemd/gnome3.6 wifi connects fail after screen off/on

Board footer