Page 1 of 2 12 LastLast
Results 1 to 10 of 12

Thread: NM connection editor is empty and uneditable (0.9.3.4)

  1. #1

    Default NM connection editor is empty and uneditable (0.9.3.4)

    Hi,

    after upgrading to OS 13.2 and installing updates, I now have NetworkManager 0.9.10.0-3.4., with plasma-nm 0.9.3.4-2.1.8 running under KDE.

    I disabled 'wicked'.

    THE PROBLEM: the new 'connection editor' (0.9.3.4) is not populated - no connections listed and adding a new connection does nothing.

    I tried using nmcli to try and get at more info:
    Code:
    jeremy@shrek:~> nmcli -v
    nmcli tool, version 0.9.10.0
    jeremy@shrek:~> nmcli g
    STATE      CONNECTIVITY  WIFI-HW  WIFI     WWAN-HW  WWAN    
    connected  full          enabled  enabled  enabled  enabled 
    jeremy@shrek:~> nmcli n
    enabled
    jeremy@shrek:~> nmcli c
    NAME  UUID  TYPE  DEVICE 
    jeremy@shrek:~> nmcli d
    DEVICE  TYPE      STATE        CONNECTION 
    wlan0   wifi      connected    --         
    eth0    ethernet  unavailable  --         
    lo      loopback  unmanaged    --         
    jeremy@shrek:~> nmcli r
    WIFI-HW  WIFI     WWAN-HW  WWAN    
    enabled  enabled  enabled  enabled
    that doesn't look promising as no info is returned by nmcli c
    then I tried nmtui
    Code:
    jeremy@shrek:~> nmtui
    (nmtui:7666): libnm-util-CRITICAL **: nm_utils_ssid_to_utf8: assertion 'ssid != NULL' failed
    again there were no connections listed.

    Am I right in thinking that connection details are still picked up from /etc/NetworkManager/system-connections/ ?

    /var/logs/NetworkManager contains the following:
    Code:
    03-16T12:02:56.960227+00:00 shrek NetworkManager[1643]: <info> NetworkManager (version 0.9.10.0) is starting...
    2015-03-16T12:02:56.962527+00:00 shrek NetworkManager[1643]: <info> Read config: /etc/NetworkManager/NetworkManager.conf
    2015-03-16T12:02:56.963833+00:00 shrek NetworkManager[1643]: <info> WEXT support is enabled
    2015-03-16T12:02:57.178098+00:00 shrek NetworkManager[1643]: <info> VPN: loaded org.freedesktop.NetworkManager.openvpn
    2015-03-16T12:02:57.179320+00:00 shrek NetworkManager[1643]: <info> VPN: loaded org.freedesktop.NetworkManager.vpnc
    2015-03-16T12:02:57.182468+00:00 shrek NetworkManager[1643]: <info> VPN: loaded org.freedesktop.NetworkManager.pptp
    2015-03-16T12:02:57.737201+00:00 shrek NetworkManager[1643]: <info> Loaded plugin ifcfg-suse: (C) 2008 Novell, Inc.  To report bugs please use the NetworkManager mailing list.
    2015-03-16T12:02:57.737970+00:00 shrek NetworkManager[1643]: <info> Loaded plugin keyfile: (c) 2007 - 2013 Red Hat, Inc.  To report bugs please use the NetworkManager mailing list.
    
    2015-03-16T12:02:57.738646+00:00 shrek NetworkManager[1643]: <warn>     error in connection /etc/NetworkManager/system-connections/bkp: File did not exist or was not a regular file //note: I moved all connections (other than active) to bkp folder in case one was corrupt - JS
    
    2015-03-16T12:02:57.774277+00:00 shrek NetworkManager[1643]: <info> new connection /etc/NetworkManager/system-connections/PlusnetWireless17C9AB
    2015-03-16T12:03:23.000210+00:00 shrek NetworkManager[1643]: <info> monitoring kernel firmware directory '/lib/firmware'.
    2015-03-16T12:03:23.001759+00:00 shrek NetworkManager[1643]: (NetworkManager:1643): GLib-GObject-WARNING **: invalid (NULL) pointer instance
    2015-03-16T12:03:23.002424+00:00 shrek NetworkManager[1643]: (NetworkManager:1643): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
    2015-03-16T12:03:23.003058+00:00 shrek NetworkManager[1643]: (NetworkManager:1643): GLib-GIO-CRITICAL **: g_dbus_proxy_call_internal: assertion 'G_IS_DBUS_PROXY (proxy)' failed
    2015-03-16T12:03:23.020394+00:00 shrek NetworkManager[1643]: <info> rfkill0: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.0/0000:01:00.0/ieee80211/phy0/rfkill0) (driver iwlwifi)
    2015-03-16T12:03:23.021120+00:00 shrek NetworkManager[1643]: <info> WiFi hardware radio set enabled
    2015-03-16T12:03:23.021763+00:00 shrek NetworkManager[1643]: <info> WWAN hardware radio set enabled
    2015-03-16T12:03:23.032637+00:00 shrek NetworkManager[1643]: <info> Loaded device plugin: /usr/lib/NetworkManager/libnm-device-plugin-adsl.so
    2015-03-16T12:03:23.071215+00:00 shrek NetworkManager[1643]: <info> Loaded device plugin: /usr/lib/NetworkManager/libnm-device-plugin-wwan.so
    2015-03-16T12:03:23.086007+00:00 shrek NetworkManager[1643]: <info> Loaded device plugin: /usr/lib/NetworkManager/libnm-device-plugin-wifi.so
    2015-03-16T12:03:23.093459+00:00 shrek NetworkManager[1643]: <info> Loaded device plugin: /usr/lib/NetworkManager/libnm-device-plugin-bluetooth.so
    2015-03-16T12:03:23.096543+00:00 shrek NetworkManager[1643]: <info> WiFi enabled by radio killswitch; enabled by state file
    2015-03-16T12:03:23.097490+00:00 shrek NetworkManager[1643]: <info> WWAN enabled by radio killswitch; enabled by state file
    2015-03-16T12:03:23.102242+00:00 shrek NetworkManager[1643]: <info> WiMAX enabled by radio killswitch; enabled by state file
    2015-03-16T12:03:23.103158+00:00 shrek NetworkManager[1643]: <info> Networking is enabled by state file
    2015-03-16T12:03:23.111519+00:00 shrek NetworkManager[1643]: <info> Setting system hostname to 'shrek.culty' (from system configuration)
    2015-03-16T12:03:23.121615+00:00 shrek NetworkManager[1643]: <info> (lo): link connected
    2015-03-16T12:03:23.122596+00:00 shrek NetworkManager[1643]: <info> (lo): carrier is ON
    2015-03-16T12:03:23.123809+00:00 shrek NetworkManager[1643]: <info> (lo): new Generic device (driver: 'unknown' ifindex: 1)
    2015-03-16T12:03:23.124727+00:00 shrek NetworkManager[1643]: <info> (lo): exported as /org/freedesktop/NetworkManager/Devices/0
    2015-03-16T12:03:23.126962+00:00 shrek NetworkManager[1643]: <info> (eth0): carrier is OFF
    2015-03-16T12:03:23.128363+00:00 shrek NetworkManager[1643]: <info> (eth0): new Ethernet device (driver: 'r8169' ifindex: 2)
    2015-03-16T12:03:23.129325+00:00 shrek NetworkManager[1643]: <info> (eth0): exported as /org/freedesktop/NetworkManager/Devices/1
    2015-03-16T12:03:23.130917+00:00 shrek NetworkManager[1643]: <info> (eth0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
    2015-03-16T12:03:23.141090+00:00 shrek NetworkManager[1643]: <info> (eth0): preparing device
    2015-03-16T12:03:23.151257+00:00 shrek NetworkManager[1643]: <info> (eth0): created default wired connection 'Wired connection 1'
    2015-03-16T12:03:23.155497+00:00 shrek NetworkManager[1643]: <info> (wlan0): using nl80211 for WiFi device control
    2015-03-16T12:03:23.158481+00:00 shrek NetworkManager[1643]: <info> (wlan0): new 802.11 WiFi device (driver: 'iwlwifi' ifindex: 3)
    2015-03-16T12:03:23.159171+00:00 shrek NetworkManager[1643]: <info> (wlan0): exported as /org/freedesktop/NetworkManager/Devices/2
    2015-03-16T12:03:23.159780+00:00 shrek NetworkManager[1643]: <info> (wlan0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
    2015-03-16T12:03:23.283778+00:00 shrek NetworkManager[1643]: <info> (wlan0): preparing device
    2015-03-16T12:03:23.290756+00:00 shrek NetworkManager[1643]: <info> use BlueZ version 5
    2015-03-16T12:03:23.521483+00:00 shrek NetworkManager[1643]: <info> ModemManager available in the bus
    2015-03-16T12:03:23.548875+00:00 shrek NetworkManager[1643]: <info> (wlan0) supports 5 scan SSIDs
    2015-03-16T12:03:23.549652+00:00 shrek NetworkManager[1643]: <info> (wlan0): supplicant interface state: starting -> ready
    2015-03-16T12:03:23.550286+00:00 shrek NetworkManager[1643]: <info> (wlan0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
    2015-03-16T12:03:23.551993+00:00 shrek NetworkManager[1643]: <info> (wlan0): supplicant interface state: ready -> disconnected
    2015-03-16T12:03:23.552744+00:00 shrek NetworkManager[1643]: <info> (wlan0) supports 5 scan SSIDs
    2015-03-16T12:03:23.606945+00:00 shrek nm-dispatcher: Dispatching action 'hostname'
    2015-03-16T12:03:26.675001+00:00 shrek NetworkManager[1643]: <info> Auto-activating connection 'PlusnetWireless17C9AB'.
    2015-03-16T12:03:27.768794+00:00 shrek NetworkManager[1643]: <info> Activation (wlan0) starting connection 'PlusnetWireless17C9AB'
    2015-03-16T12:03:27.770206+00:00 shrek NetworkManager[1643]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
    2015-03-16T12:03:27.770880+00:00 shrek NetworkManager[1643]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
    2015-03-16T12:03:27.771616+00:00 shrek NetworkManager[1643]: <info> (wlan0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
    2015-03-16T12:03:27.772342+00:00 shrek NetworkManager[1643]: <info> NetworkManager state is now CONNECTING
    2015-03-16T12:03:27.773102+00:00 shrek NetworkManager[1643]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
    2015-03-16T12:03:27.773873+00:00 shrek NetworkManager[1643]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
    2015-03-16T12:03:27.774622+00:00 shrek NetworkManager[1643]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
    2015-03-16T12:03:27.775305+00:00 shrek NetworkManager[1643]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
    2015-03-16T12:03:27.775959+00:00 shrek NetworkManager[1643]: <info> Activation (wlan0/wireless): connection 'PlusnetWireless17C9AB' has security, and secrets exist.  No new secrets needed.
    2015-03-16T12:03:27.776593+00:00 shrek NetworkManager[1643]: <info> Config: added 'ssid' value 'PlusnetWireless17C9AB'
    2015-03-16T12:03:27.777226+00:00 shrek NetworkManager[1643]: <info> Config: added 'scan_ssid' value '1'
    2015-03-16T12:03:27.777890+00:00 shrek NetworkManager[1643]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
    2015-03-16T12:03:27.778545+00:00 shrek NetworkManager[1643]: <info> Config: added 'psk' value '<omitted>'
    2015-03-16T12:03:27.779169+00:00 shrek NetworkManager[1643]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
    2015-03-16T12:03:27.779822+00:00 shrek NetworkManager[1643]: <info> (wlan0): supplicant interface state: disconnected -> inactive
    2015-03-16T12:03:27.780479+00:00 shrek NetworkManager[1643]: <info> Config: set interface ap_scan to 1
    2015-03-16T12:03:27.805257+00:00 shrek NetworkManager[1643]: <info> (wlan0): supplicant interface state: inactive -> authenticating
    2015-03-16T12:03:27.810605+00:00 shrek NetworkManager[1643]: <info> (wlan0): supplicant interface state: authenticating -> associating
    2015-03-16T12:03:27.841492+00:00 shrek NetworkManager[1643]: <info> (wlan0): supplicant interface state: associating -> 4-way handshake
    2015-03-16T12:03:27.875170+00:00 shrek NetworkManager[1643]: <info> (wlan0): supplicant interface state: 4-way handshake -> completed
    2015-03-16T12:03:27.875959+00:00 shrek NetworkManager[1643]: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'PlusnetWireless17C9AB'.
    2015-03-16T12:03:27.876623+00:00 shrek NetworkManager[1643]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
    2015-03-16T12:03:27.877196+00:00 shrek NetworkManager[1643]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
    2015-03-16T12:03:27.877798+00:00 shrek NetworkManager[1643]: <info> (wlan0): device state change: config -> ip-config (reason 'none') [50 70 0]
    2015-03-16T12:03:28.091615+00:00 shrek NetworkManager[1643]: <info> Activation (wlan0) Beginning DHCPv4 transaction (timeout in 45 seconds)
    2015-03-16T12:03:28.098466+00:00 shrek NetworkManager[1643]: <info> dhclient started with pid 2170
    2015-03-16T12:03:28.099180+00:00 shrek NetworkManager[1643]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
    2015-03-16T12:03:28.125269+00:00 shrek NetworkManager[1643]: Internet Systems Consortium DHCP Client 4.2.6
    //edited
    2015-03-16T12:03:28.193094+00:00 shrek NetworkManager[1643]: <info> (wlan0): DHCPv4 state changed nbi -> preinit
    2015-03-16T12:03:28.203466+00:00 shrek NetworkManager[1643]: Listening on LPF/wlan0/00:24:d6:5f:8b:60
    2015-03-16T12:03:28.204195+00:00 shrek NetworkManager[1643]: Sending on   LPF/wlan0/00:24:d6:5f:8b:60
    2015-03-16T12:03:28.204821+00:00 shrek NetworkManager[1643]: Sending on   Socket/fallback
    2015-03-16T12:03:28.205410+00:00 shrek NetworkManager[1643]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5 (xid=0x4580aa99)
    2015-03-16T12:03:28.215282+00:00 shrek NetworkManager[1643]: DHCPOFFER from 192.168.1.254
    2015-03-16T12:03:33.220537+00:00 shrek NetworkManager[1643]: DHCPREQUEST on wlan0 to 255.255.255.255 port 67 (xid=0x4580aa99)
    2015-03-16T12:03:33.232641+00:00 shrek NetworkManager[1643]: DHCPACK from 192.168.1.254 (xid=0x4580aa99)
    2015-03-16T12:03:33.235224+00:00 shrek NetworkManager[1643]: <info> (wlan0): DHCPv4 state changed preinit -> bound
    2015-03-16T12:03:33.235990+00:00 shrek NetworkManager[1643]: <info>   address 192.168.1.70
    2015-03-16T12:03:33.236598+00:00 shrek NetworkManager[1643]: <info>   plen 24 (255.255.255.0)
    2015-03-16T12:03:33.237150+00:00 shrek NetworkManager[1643]: <info>   gateway 192.168.1.254
    2015-03-16T12:03:33.237760+00:00 shrek NetworkManager[1643]: <info>   server identifier 192.168.1.254
    2015-03-16T12:03:33.238764+00:00 shrek NetworkManager[1643]: <info>   lease time 86400
    2015-03-16T12:03:33.239591+00:00 shrek NetworkManager[1643]: <info>   nameserver '192.168.1.254'
    2015-03-16T12:03:33.240534+00:00 shrek NetworkManager[1643]: <info>   domain name 'lan'
    2015-03-16T12:03:33.241423+00:00 shrek NetworkManager[1643]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
    2015-03-16T12:03:33.242603+00:00 shrek NetworkManager[1643]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Commit) started...
    2015-03-16T12:03:33.245309+00:00 shrek NetworkManager[1643]: <info> (wlan0): device state change: ip-config -> ip-check (reason 'none') [70 80 0]
    2015-03-16T12:03:33.245910+00:00 shrek NetworkManager[1643]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Commit) complete.
    2015-03-16T12:03:33.246616+00:00 shrek NetworkManager[1643]: <info> (wlan0): device state change: ip-check -> secondaries (reason 'none') [80 90 0]
    2015-03-16T12:03:33.247191+00:00 shrek NetworkManager[1643]: <info> (wlan0): device state change: secondaries -> activated (reason 'none') [90 100 0]
    2015-03-16T12:03:33.247786+00:00 shrek NetworkManager[1643]: <info> NetworkManager state is now CONNECTED_LOCAL
    2015-03-16T12:03:33.901158+00:00 shrek NetworkManager[1643]: bound to 192.168.1.70 -- renewal in 37596 seconds.
    2015-03-16T12:03:35.205644+00:00 shrek NetworkManager[1643]: <info> NetworkManager state is now CONNECTED_GLOBAL
    2015-03-16T12:03:35.207042+00:00 shrek NetworkManager[1643]: <info> Policy set 'PlusnetWireless17C9AB' (wlan0) as default for IPv4 routing and DNS.
    2015-03-16T12:03:35.216036+00:00 shrek NetworkManager[1643]: <info> Activation (wlan0) successful, device activated.
    2015-03-16T12:03:35.221360+00:00 shrek NetworkManager[1643]: <info> startup complete
    I am currently connecting via wi-fi OK, despite there being no connections recognised by plasma-nm

    has anyone else encountered this issue?

    best wishes - JS

  2. #2

    Default Re: NM connection editor is empty and uneditable (0.9.3.4)

    [Hi Admin, can you move this thread to 'Wireless', please? :: thanks, JS]

  3. #3
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    24,226

    Default Re: NM connection editor is empty and uneditable (0.9.3.4)

    Quote Originally Posted by jack_sprat View Post
    [Hi Admin, can you move this thread to 'Wireless', please? :: thanks, JS]
    \
    Maybe leave it here for the moment. As I see it, your problem is NM general, not Wifi specific.
    Henk van Velden

  4. #4

    Default Re: NM connection editor is empty and uneditable (0.9.3.4)

    more information:
    /etc/logs/messages records the following when 'connection editor' is opened:
    Code:
    2015-03-16T16:11:23.848588+00:00 shrek dbus[1782]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.57" (uid=1000 pid=4546 comm="/usr/bin/kde-nm-connection-editor ") interface="org.freedesktop.DBus.Introspectable" member="Introspect" error name="(unset)" requested_reply="0" destination="org.bluez" (uid=0 pid=2026 comm="/usr/lib/bluetooth/bluetoothd ")
    2015-03-16T16:11:23.850816+00:00 shrek dbus[1782]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.57" (uid=1000 pid=4546 comm="/usr/bin/kde-nm-connection-editor ") interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" error name="(unset)" requested_reply="0" destination="org.bluez" (uid=0 pid=2026 comm="/usr/lib/bluetooth/bluetoothd ")
    JS

  5. #5

    Default Re: NM connection editor is empty and uneditable (0.9.3.4)

    this may be a tangent, but...
    another recent problem (i.e. since upgrade to 13.2 c/w update) is that I can no longer auto mount USB filesystems; some digging has led me to question polkit settings for networkmanager and udisks/udisks2 - these both have auth_admin settings (see https://github.com/openSUSE/polkit-d...privs.standard), so I'm wondering if there's a problem here...

    any ideas out there?

    JS

  6. #6

    Default Re: NM connection editor is empty and uneditable (0.9.3.4)

    Quote Originally Posted by jack_sprat View Post
    this may be a tangent, but...
    another recent problem (i.e. since upgrade to 13.2 c/w update) is that I can no longer auto mount USB filesystems;
    Well, what exactly do you mean with "I can no longer auto mount USB filesystems"? How are you trying to mount them? What happens, what error messages do you get?

    Mounting USB filesystems is definitely unrelated to NetworkManager, but the reason for both could be permission problems.
    Please check whether your login session is correctly registered with logind, by running "loginctl".

    Do you use autofs by chance? There is/was a problem in 13.2 that having autofs.service enabled would cause logind to start too late, causing exactly such problems.
    Try to disable it as a test.

    some digging has led me to question polkit settings for networkmanager and udisks/udisks2 - these both have auth_admin settings (see https://github.com/openSUSE/polkit-d...privs.standard), so I'm wondering if there's a problem here...
    No, the default polkit settings should be ok.
    I don't know what exact rules you mean when you say "these both have auth_admin settings". Mounting external drives via udisks2 has "yes" for the active session. Most NetworkManager related rules have indeed auth_admin_keep, but that can't really cause your problem, because then _everybody_ should have it. At least on my systems everything works as expected with NetworkManager, and I haven't changed any polit rules...

  7. #7

    Default Re: NM connection editor is empty and uneditable (0.9.3.4)

    when I connect a USB filesystem (camera or flash drive) the Device Notifier delivers a message: Could not mount the following device... An unspecified error has occurred: Not authorized to perform operation.

    I can mount them manually with 'sudo mount' or with 'udisksctl mount', which then requires authentication, generating the following:
    Code:
    (udisksctl mount:6698): GLib-WARNING **: GChildWatchSource: Exit status of a child process was requested but ECHILD was received by waitpid(). Most likely the process is ignoring SIGCHLD, or some other thread is invoking waitpid() with a nonpositive first argument; either behavior can break applications that use g_child_watch_add()/g_spawn_sync() either directly or indirectly.
    when I try to connect networkmanager to a new access point there is a warning along the lines of "no session found for uid=1000"

    I've now activated logging for both plasma-nm and Device notifier

    JS

  8. #8

    Default Re: NM connection editor is empty and uneditable (0.9.3.4)

    Quote Originally Posted by jack_sprat View Post
    when I connect a USB filesystem (camera or flash drive) the Device Notifier delivers a message: Could not mount the following device... An unspecified error has occurred: Not authorized to perform operation.
    Well, this definitely sounds like a problem with registering the session with logind.
    So, again:
    Does "loginctl" list your user session?
    Do you use autofs?

    when I try to connect networkmanager to a new access point there is a warning along the lines of "no session found for uid=1000"
    This seems to indicate a not correctly registered user session as well.

  9. #9

    Default Re: NM connection editor is empty and uneditable (0.9.3.4)

    it seems that current session is not returned by loginctl and the current user is not listed:
    Code:
    jeremy@shrek:~> loginctl
       SESSION        UID USER             SEAT            
             1          0 root                             
            c2          0 root                             
    
    2 sessions listed.
    
    jeremy@shrek:~> loginctl list-users
           UID USER            
             0 root

    autofs is enabled and active

    JS

  10. #10

    Default Re: NM connection editor is empty and uneditable (0.9.3.4)

    Quote Originally Posted by jack_sprat View Post
    it seems that current session is not returned by loginctl and the current user is not listed:
    Code:
    jeremy@shrek:~> loginctl
       SESSION        UID USER             SEAT            
             1          0 root                             
            c2          0 root                             
    
    2 sessions listed.
    Right, and this causes your problems I suppose (at least the mount problem).

    autofs is enabled and active
    Then disable it for a test. It can prevent logind from starting in time, causing all this.
    Or disable auto-login and wait for about half a minute until you login, in this case the problem should also disappear.

    A quick test would also be to just logout and login again. The user session should be listed then, and mounting USB drives should work fine. (and NetworkManager hopefully would work as well).

    If you need autofs.service (probably, if you have it enabled), then just removing the line "Before=systemd-logind.service" in /usr/lib/systemd/system/autofs.service should fix the problem.

    If autofs is not the reason (i.e. none of the above helps), please post the output of:
    Code:
    ls -l /etc/pam.d
    grep systemd /etc/pam.d/*
    Last edited by wolfi323; 16-Mar-2015 at 16:31.

Page 1 of 2 12 LastLast

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •