Announcement

Collapse
No announcement yet.

NetworkManagement widget: not connecting to wifi automatically

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    NetworkManagement widget: not connecting to wifi automatically

    I upgraded to 14.10 a couple of days ago and haven't been able to get Kubuntu to automatically connect to my router when I log in.

    I'm using KDE4.14.1 (not the KDE5 preview).

    In 14.04, NM would connnect to the network instantly, but now it doesn't. I didn't change any settings initially, but since I first noticed the problem I have deleted the old settings and re-entered them. No dice.

    To be clear: I can connect manually just fine, I just don't understand why NM doesn't do it automatically.

    Has anyone else had this problem? Any suggestions?

    Thanks!
    samhobbs.co.uk

    #2
    nice heads up ,,,,,,,, will be installing the 14.10 some time this weekend and will look into this as well

    VINNY
    i7 4core HT 8MB L3 2.9GHz
    16GB RAM
    Nvidia GTX 860M 4GB RAM 1152 cuda cores

    Comment


      #3
      Thanks Vinny... I'm not sure if it's something I've done or a problem with NM.

      I get the same problem when the laptop wakes up from sleep.

      Perhaps plasma 5 would do this better, who knows! I might try it, but I doubt it's easy to roll back to v4 if I have more/different problems.

      I'm also getting some strange touchpad behaviour where it seems "sticky" or unresponsive for the first part of some movements, particularly if the cursor starting position is over a button or scroll bar. Not sure if that's a touchpad config problem, I guess it could be a new "feature" for window behaviour in this version of KDE. Anyway, that's another thread...
      samhobbs.co.uk

      Comment


        #4
        Originally posted by Feathers McGraw View Post
        Thanks Vinny... I'm not sure if it's something I've done or a problem with NM.

        I get the same problem when the laptop wakes up from sleep.

        Perhaps plasma 5 would do this better, who knows! I might try it, but I doubt it's easy to roll back to v4 if I have more/different problems.

        I'm also getting some strange touchpad behaviour where it seems "sticky" or unresponsive for the first part of some movements, particularly if the cursor starting position is over a button or scroll bar. Not sure if that's a touchpad config problem, I guess it could be a new "feature" for window behaviour in this version of KDE. Anyway, that's another thread...
        just DL'd the 2 K-14.10 .iso's ,,,,,standard and plasma5 .

        I installed the plasma5 one in a KVM ,,,,, but the desktop dose not display correctly despite any application launched being correctly displayed ,,,,,,,,,,,,,,,,,this of course may be a prob with the KVM's display settings IDK yet

        VINNY
        i7 4core HT 8MB L3 2.9GHz
        16GB RAM
        Nvidia GTX 860M 4GB RAM 1152 cuda cores

        Comment


          #5
          That's weird, do you get the same behaviour when you use a live USB?
          samhobbs.co.uk

          Comment


            #6
            Originally posted by Feathers McGraw View Post
            That's weird, do you get the same behaviour when you use a live USB?
            have not tryed it yet ,,,,I went strait from DL to plasma5 KVM , couldn't resist ,,,,,,,just made a USB of the standard 14.10.iso

            will install to one of the 2 remaining OS partitions on the Bonox8 in a few and see how NM works @hear

            VINNY
            i7 4core HT 8MB L3 2.9GHz
            16GB RAM
            Nvidia GTX 860M 4GB RAM 1152 cuda cores

            Comment


              #7
              Originally posted by Feathers McGraw View Post
              I upgraded to 14.10 a couple of days ago and haven't been able to get Kubuntu to automatically connect to my router when I log in.
              Reboot, log in, and then take a look at /var/log/syslog for wireless-related error messages (starting at the point in time when you rebooted, of course). Anything?

              Comment


                #8
                OK just finished the 14.10 install ,,,,,,,,,,,,,,,,,, sense I had configured the wireless during the install it was auto conected at boot .

                sence you have 2 wireless AP's to connect to connect to the one you prefer and check..... click the NM applet>click your connection>click the wrench>select your connection in the connection editor and click edit>in the "general"tab see that "Automatically connect to this network when it is available "is checked.

                then do the same for the one you do not want to use and make sure it is unchecked

                VINNY
                i7 4core HT 8MB L3 2.9GHz
                16GB RAM
                Nvidia GTX 860M 4GB RAM 1152 cuda cores

                Comment


                  #9
                  Thanks for taking an interest Steve,

                  Here are what I think are the relevant lines (from cat /var/log/syslog | grep -i networkmanager). It's still quite a lot of output, sorry for that:

                  Code:
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]: <info> NetworkManager (version 0.9.8.8) is starting...
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]: <info> Read config file /etc/NetworkManager/NetworkManager.conf
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]: <info> WEXT support is enabled
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]: <info> VPN: loaded org.freedesktop.NetworkManager.pptp
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]: <info> VPN: loaded org.freedesktop.NetworkManager.openvpn
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]: <info> VPN: loaded org.freedesktop.NetworkManager.vpnc
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]: <info> DNS: loaded plugin dnsmasq
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]:    SCPlugin-Ifupdown: init!
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]:    SCPlugin-Ifupdown: update_system_hostname
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]:       interface-parser: parsing file /etc/network/interfaces
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]:       interface-parser: finished parsing file /etc/network/interfaces
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]:    SCPluginIfupdown: management mode: unmanaged
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]:    SCPlugin-Ifupdown: devices added (path: /sys/devices/pci0000:00/0000:00:19.0/net/eth0, iface: eth0)
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]:    SCPlugin-Ifupdown: device added (path: /sys/devices/pci0000:00/0000:00:19.0/net/eth0, iface: eth0): no ifupdown configuration found.
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]:    SCPlugin-Ifupdown: devices added (path: /sys/devices/pci0000:00/0000:00:1c.1/0000:03:00.0/net/wlan0, iface: wlan0)
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]:    SCPlugin-Ifupdown: device added (path: /sys/devices/pci0000:00/0000:00:1c.1/0000:03:00.0/net/wlan0, iface: wlan0): no ifupdown configuration found.
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]:    SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/lo, iface: lo)
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]:    SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/lo, iface: lo): no ifupdown configuration found.
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]:    SCPlugin-Ifupdown: end _init.
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]: <info> Loaded plugin ifupdown: (C) 2008 Canonical Ltd.  To report bugs please use the NetworkManager mailing list.
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]: <info> Loaded plugin keyfile: (c) 2007 - 2010 Red Hat, Inc.  To report bugs please use the NetworkManager mailing list.
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]:    SCPlugin-Ofono: Acquired D-Bus service com.canonical.NMOfono
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]:    SCPlugin-Ofono: init!
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]:    SCPlugin-Ofono: end _init.
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]: <info> Loaded plugin (null): (null)
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]:    Ifupdown: get unmanaged devices count: 0
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]:    SCPlugin-Ifupdown: (31037200) ... get_connections.
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]:    SCPlugin-Ifupdown: (31037200) ... get_connections (managed=false): return empty list.
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]:    keyfile: parsing ROCKI_B55BE6 ... 
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]:    keyfile:     read connection 'ROCKI_B55BE6'
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]:    keyfile: parsing Turbo-Hub-5GHz ... 
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]:    keyfile:     read connection 'Turbo-Hub-5GHz'
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]:    keyfile: parsing Private Internet Access ... 
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]:    keyfile:     read connection 'PIA VPN Toronto Canada'
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]:    keyfile: parsing BTHub4-GH32 ... 
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]:    keyfile:     read connection 'BTHub4-GH32'
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]:    keyfile: parsing UK Southampton ... 
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]:    keyfile:     read connection 'PIA VPN UK Southampton'
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]:    keyfile: parsing BTHub5-FKZQ_EXT ... 
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]:    keyfile:     read connection 'BTHub5-FKZQ_EXT'
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]:    keyfile: parsing BTHub5-FKZQ ... 
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]:    keyfile:     read connection 'BTHub5-FKZQ'
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]:    SCPlugin-Ofono: (30844432) ... get_connections.
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]:    SCPlugin-Ofono: (30844432) connections count: 0
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]:    Ifupdown: get unmanaged devices count: 0
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]: <info> monitoring kernel firmware directory '/lib/firmware'.
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]: <info> rfkill2: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.1/0000:03:00.0/ieee80211/phy0/rfkill2) (driver iwlwifi)
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]: <info> WiFi enabled by radio killswitch; enabled by state file
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]: <info> WWAN enabled by radio killswitch; enabled by state file
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]: <info> WiMAX enabled by radio killswitch; enabled by state file
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]: <info> Networking is enabled by state file
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]: <warn> failed to allocate link cache: (-26) Protocol mismatch
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]: <info> (eth0): carrier is OFF
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]: <info> (eth0): new Ethernet device (driver: 'e1000e' ifindex: 2)
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]: <info> (eth0): exported as /org/freedesktop/NetworkManager/Devices/0
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]: <info> (eth0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]: <info> (eth0): bringing up device.
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]: <info> (eth0): preparing device.
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]: <info> (eth0): deactivating device (reason 'managed') [2]
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]: <info> Added default wired connection 'Wired connection 1' for /sys/devices/pci0000:00/0000:00:19.0/net/eth0
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]: <info> (wlan0): using nl80211 for WiFi device control
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]: <info> (wlan0): driver supports Access Point (AP) mode
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]: <info> (wlan0): new 802.11 WiFi device (driver: 'iwlwifi' ifindex: 3)
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]: <info> (wlan0): exported as /org/freedesktop/NetworkManager/Devices/1
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]: <info> (wlan0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]: <info> (wlan0): bringing up device.
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]: <info> (wlan0): preparing device.
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]: <info> (wlan0): deactivating device (reason 'managed') [2]
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring...
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring...
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]: <info> urfkill disappeared from the bus
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]: <info> ModemManager available in the bus
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]: <info> wpa_supplicant started
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]: <info> (wlan0) supports 5 scan SSIDs
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]: <warn> Trying to remove a non-existant call id.
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]: <info> (wlan0): supplicant interface state: starting -> ready
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]: <info> (wlan0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]: <info> (wlan0): supplicant interface state: ready -> disconnected
                  Oct 25 23:59:09 Hobbs-T440s NetworkManager[820]: <info> (wlan0) supports 5 scan SSIDs
                  Oct 25 23:59:13 Hobbs-T440s NetworkManager[820]: <info> (wlan0): supplicant interface state: disconnected -> inactive
                  Oct 25 23:59:19 Hobbs-T440s NetworkManager[820]: <info> WiFi hardware radio set enabled
                  Oct 25 23:59:36 Hobbs-T440s NetworkManager[820]: <info> (wlan0): supplicant interface state: inactive -> scanning
                  Oct 26 00:07:41 Hobbs-T440s NetworkManager[820]: <info> Activation (wlan0) starting connection 'Turbo-Hub-5GHz'
                  Oct 26 00:07:41 Hobbs-T440s NetworkManager[820]: <info> (wlan0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
                  Oct 26 00:07:41 Hobbs-T440s NetworkManager[820]: <info> NetworkManager state is now CONNECTING
                  Oct 26 00:07:41 Hobbs-T440s NetworkManager[820]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
                  Oct 26 00:07:41 Hobbs-T440s NetworkManager[820]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
                  Oct 26 00:07:41 Hobbs-T440s NetworkManager[820]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
                  Oct 26 00:07:41 Hobbs-T440s NetworkManager[820]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
                  Oct 26 00:07:41 Hobbs-T440s NetworkManager[820]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
                  Oct 26 00:07:41 Hobbs-T440s NetworkManager[820]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
                  Oct 26 00:07:41 Hobbs-T440s NetworkManager[820]: <info> Activation (wlan0/wireless): access point 'Turbo-Hub-5GHz' has security, but secrets are required.
                  Oct 26 00:07:41 Hobbs-T440s NetworkManager[820]: <info> (wlan0): device state change: config -> need-auth (reason 'none') [50 60 0]
                  Oct 26 00:07:41 Hobbs-T440s NetworkManager[820]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
                  Oct 26 00:07:41 Hobbs-T440s NetworkManager[820]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.
                  Oct 26 00:07:41 Hobbs-T440s NetworkManager[820]: get_secret_flags: assertion 'is_secret_prop (setting, secret_name, error)' failed
                  Oct 26 00:07:41 Hobbs-T440s NetworkManager[820]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
                  Oct 26 00:07:41 Hobbs-T440s NetworkManager[820]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
                  Oct 26 00:07:41 Hobbs-T440s NetworkManager[820]: <info> (wlan0): device state change: need-auth -> prepare (reason 'none') [60 40 0]
                  Oct 26 00:07:41 Hobbs-T440s NetworkManager[820]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
                  Oct 26 00:07:41 Hobbs-T440s NetworkManager[820]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
                  Oct 26 00:07:41 Hobbs-T440s NetworkManager[820]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
                  Oct 26 00:07:41 Hobbs-T440s NetworkManager[820]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
                  Oct 26 00:07:41 Hobbs-T440s NetworkManager[820]: <info> Activation (wlan0/wireless): connection 'Turbo-Hub-5GHz' has security, and secrets exist.  No new secrets needed.
                  Oct 26 00:07:41 Hobbs-T440s NetworkManager[820]: <info> Config: added 'ssid' value 'Turbo-Hub-5GHz'
                  Oct 26 00:07:41 Hobbs-T440s NetworkManager[820]: <info> Config: added 'scan_ssid' value '1'
                  Oct 26 00:07:41 Hobbs-T440s NetworkManager[820]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
                  Oct 26 00:07:41 Hobbs-T440s NetworkManager[820]: <info> Config: added 'auth_alg' value 'OPEN'
                  Oct 26 00:07:41 Hobbs-T440s NetworkManager[820]: <info> Config: added 'psk' value '<omitted>'
                  Oct 26 00:07:41 Hobbs-T440s NetworkManager[820]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
                  Oct 26 00:07:41 Hobbs-T440s NetworkManager[820]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.
                  Oct 26 00:07:41 Hobbs-T440s NetworkManager[820]: <info> Config: set interface ap_scan to 1
                  Oct 26 00:07:41 Hobbs-T440s NetworkManager[820]: <info> (wlan0): supplicant interface state: scanning -> authenticating
                  Oct 26 00:07:45 Hobbs-T440s NetworkManager[820]: <info> (wlan0): supplicant interface state: authenticating -> associating
                  Oct 26 00:07:45 Hobbs-T440s NetworkManager[820]: <info> (wlan0): supplicant interface state: associating -> associated
                  Oct 26 00:07:45 Hobbs-T440s NetworkManager[820]: <info> (wlan0): supplicant interface state: associated -> completed
                  Oct 26 00:07:45 Hobbs-T440s NetworkManager[820]: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'Turbo-Hub-5GHz'.
                  Oct 26 00:07:45 Hobbs-T440s NetworkManager[820]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
                  Oct 26 00:07:45 Hobbs-T440s NetworkManager[820]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
                  Oct 26 00:07:45 Hobbs-T440s NetworkManager[820]: <info> (wlan0): device state change: config -> ip-config (reason 'none') [50 70 0]
                  Oct 26 00:07:45 Hobbs-T440s NetworkManager[820]: <info> Activation (wlan0) Beginning DHCPv4 transaction (timeout in 45 seconds)
                  Oct 26 00:07:45 Hobbs-T440s NetworkManager[820]: <info> dhclient started with pid 3005
                  Oct 26 00:07:45 Hobbs-T440s NetworkManager[820]: <info> Activation (wlan0) Beginning IP6 addrconf.
                  Oct 26 00:07:45 Hobbs-T440s NetworkManager[820]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
                  Oct 26 00:07:45 Hobbs-T440s NetworkManager[820]: <info> (wlan0): DHCPv4 state changed nbi -> preinit
                  Oct 26 00:07:45 Hobbs-T440s NetworkManager[820]: <info> (wlan0): DHCPv4 state changed preinit -> reboot
                  Oct 26 00:07:45 Hobbs-T440s NetworkManager[820]: <info>   address 192.168.1.112
                  Oct 26 00:07:45 Hobbs-T440s NetworkManager[820]: <info>   prefix 24 (255.255.255.0)
                  Oct 26 00:07:45 Hobbs-T440s NetworkManager[820]: <info>   gateway 192.168.1.1
                  Oct 26 00:07:45 Hobbs-T440s NetworkManager[820]: <info>   hostname 'Hobbs-T440s'
                  Oct 26 00:07:45 Hobbs-T440s NetworkManager[820]: <info>   nameserver '192.168.1.1'
                  Oct 26 00:07:45 Hobbs-T440s NetworkManager[820]: <info>   domain name 'lan'
                  Oct 26 00:07:45 Hobbs-T440s NetworkManager[820]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
                  Oct 26 00:07:45 Hobbs-T440s NetworkManager[820]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Commit) started...
                  Oct 26 00:07:46 Hobbs-T440s NetworkManager[820]: <info> (wlan0): device state change: ip-config -> secondaries (reason 'none') [70 90 0]
                  Oct 26 00:07:46 Hobbs-T440s NetworkManager[820]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Commit) complete.
                  Oct 26 00:07:46 Hobbs-T440s NetworkManager[820]: <info> (wlan0): device state change: secondaries -> activated (reason 'none') [90 100 0]
                  Oct 26 00:07:46 Hobbs-T440s NetworkManager[820]: <info> NetworkManager state is now CONNECTED_GLOBAL
                  Oct 26 00:07:46 Hobbs-T440s NetworkManager[820]: <info> Policy set 'Turbo-Hub-5GHz' (wlan0) as default for IPv4 routing and DNS.
                  Oct 26 00:07:46 Hobbs-T440s NetworkManager[820]: <info> DNS: starting dnsmasq...
                  Oct 26 00:07:46 Hobbs-T440s NetworkManager[820]: <warn> dnsmasq not available on the bus, can't update servers.
                  Oct 26 00:07:46 Hobbs-T440s NetworkManager[820]: <error> [1414278466.852101] [nm-dns-dnsmasq.c:396] update(): dnsmasq owner not found on bus: Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such name
                  Oct 26 00:07:46 Hobbs-T440s NetworkManager[820]: <warn> DNS: plugin dnsmasq update failed
                  Oct 26 00:07:46 Hobbs-T440s NetworkManager[820]: <info> Writing DNS information to /sbin/resolvconf
                  Oct 26 00:08:06 Hobbs-T440s NetworkManager[820]: <info> (wlan0): IP6 addrconf timed out or failed.
                  Oct 26 00:08:06 Hobbs-T440s NetworkManager[820]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
                  Oct 26 00:08:06 Hobbs-T440s NetworkManager[820]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) started...
                  Oct 26 00:08:06 Hobbs-T440s NetworkManager[820]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) complete.
                  This includes me actually connecting to the network after letting it sit for a bit.
                  samhobbs.co.uk

                  Comment


                    #10
                    Is this laptop plugged in or on battery?

                    Comment


                      #11
                      I think (not 100%) it was plugged in at the time of that output, but the problem also exists when it's running on battery.
                      samhobbs.co.uk

                      Comment


                        #12
                        Same problem here on the w520, after a reboot I have to reconnect, this is running on mains.

                        Update;
                        While typing the above I remebered a person with an attitude complaining 'we' did not right away give him a solution to the same problem
                        Go into the WIFI settings and tick the 'All users can connect' (or similar)

                        This way the connection will come up automatically.

                        PPS, in hindsight the question might have been in the Ubuntu newsgroup.
                        Last edited by Teunis; Oct 25, 2014, 06:27 PM.

                        Comment


                          #13
                          I bet you've encountered a power management issue. The system is trying to make a connection before the wireless interface is completely powered up. It was one of the things that came up when I Googled for "device state change unavailable disconnected reason supplicant available." Nothing else in the log seems like it indicates a potential problem.

                          Comment


                            #14
                            Originally posted by SteveRiley View Post
                            I bet you've encountered a power management issue. The system is trying to make a connection before the wireless interface is completely powered up. It was one of the things that came up when I Googled for "device state change unavailable disconnected reason supplicant available." Nothing else in the log seems like it indicates a potential problem.
                            That's interesting, do you have any suggestions for troubleshooting steps?

                            Another oddity I've noticed (not new, but it has never seemed to cause me problems before) is that the "wired connection" always says it was used minutes ago regardless of how long ago I actually connected an Ethernet cable.

                            Can you think of an explanation for this? Could there be an "internal Ethernet" connection or some hardware specific trickery causing this?
                            samhobbs.co.uk

                            Comment


                              #15
                              Originally posted by Teunis View Post
                              Update;
                              While typing the above I remebered a person with an attitude complaining 'we' did not right away give him a solution to the same problem
                              Go into the WIFI settings and tick the 'All users can connect' (or similar)

                              This way the connection will come up automatically.
                              Just seen this, tried it and it worked! Thank you!

                              I wonder why though?

                              I also noticed that the PSK for this network is hard coded into the file, whereas other networks have the psk-flags=1 parameter set, which hands control of the password over to the "user session secret agent" (Kwallet in this case). Perhaps the problem is with Kwallet, not NM?

                              Does anyone know if the password is always hardcoded in the file when the connection is shared between all users?
                              samhobbs.co.uk

                              Comment

                              Working...
                              X