kde4 network manager plasmoid doesn't work.

Pity. Then that’s not your problem.
Btw, libibus is not required by the things you list. It’s rather the other way round. “rpm -q -R libibus-1_0-5” lists what packages libibus requires.

Otherwise, as a “outstanding” package, I use postgresql-9.3 from the distro.

What do you mean with “outstanding”?

I doubt that postgresql would cause those problems.

I meant an unusual bulky package that could cause trouble :expressionless:

Some news…
Apparently the problem at hand can be caused by autofs:
http://bugzilla.opensuse.org/show_bug.cgi?id=905639

So try to disable it, if you have it enabled.

systemctl disable autofs.service

My suspicion is that the “Before=systemd-logind.service” line in autofs.service (which wasn’t there in 13.1 yet) might cause logind to be started too late and not be ready at (first) login.
Probably that line should be removed, or maybe display-manager.service is missing a dependency on systemd-logind.service.

THAT’S IT !

I use autofs for a NFS server that I only boot up when needed. But autofs before logind is logical anyway, because you should be able to login on a remote /home filesystem drive by autofs.

So, in my case, I started autofs after logind

Thx very much for the tip !!! :slight_smile:

Greetings, I have the same issue, but don’t know how to start autofs after logind. Could you please let me know how you did this?

Thank you!

D’oh, I found it in the bug report link above. Never mind! Thanks anyway!

i have the same problem with nm-applet with HSDPA usb modem. when i insterted the modem, sometimes, pretty often, the HSDPA connection entry appears grayed out and it does not work. it does not connect even when i try to connect by network editor window.
last night, i have remove that line and the system seems to work okay. i will see this in the next few days if the problem strikes back.

okay, the issue is up and running. it is impossible to me to connect via HSDPA. i even reinstalled plasma-nm with no positive result.
maybe someone can help me to handle this. it seems that this plasma-mn applet is real messed up.

as i promise, i will attach two screenshot to see the behaviour. what is strange is that sometimes is happening but sometimes don’t.
http://i.imgur.com/cjKPNYz.png
http://i.imgur.com/W4hPzwM.png

as you can see, this is far from right.

I don’t use HSPDA so cannot help at all with that.
But I doubt that this is the applet’s fault. The applet is just a frontend to NetworkManager.

Try to use “nm-applet” instead (you can even run it at the same time as KDE’s applet). If you see the same issue there, it proves that your problem lies somewhere else.

Btw, the original problem here in this thread was a general lack of permissions because the user session couldn’t be registered with logind (caused by autofs.service delaying logind’s start).
Your problem doesn’t really sound related… Or do you have problems mounting USB devices/with audio as well when the networkmanagement applet doesn’t work?

thanx man…
as i told, i removed that line from autofs.
what is really strange is that the problem did not appear for last two days but in this evening, it reappears again.
if i watch “journalctl -f” i get an error like “policykit permision…”
i am thinking to replace “plasma-nm” with “nm-applet” or “knetworkmanager”.

now it is working again…
message before this was written from ubuntu. now that i reboot to opensuse, the plasma-nm is working again.
this is the output of the “journalctl” of the time that it did not work.

Dec 21 19:22:58 linux.site kernel: usb 1-3: usbfs: interface 0 claimed by usbfs while 'soffice.bin' sets config #1
Dec 21 19:22:59 linux.site kernel: usb 1-3: usbfs: interface 0 claimed by usbfs while 'soffice.bin' sets config #1
Dec 21 19:22:59 linux.site kernel: usb 1-3: usbfs: interface 0 claimed by usbfs while 'soffice.bin' sets config #1
Dec 21 19:22:59 linux.site kernel: usb 1-3: usbfs: interface 0 claimed by usbfs while 'soffice.bin' sets config #1
Dec 21 19:23:19 linux.site kernel: usb 1-3: usbfs: interface 0 claimed by usbfs while 'soffice.bin' sets config #1
Dec 21 19:23:20 linux.site kernel: usb 1-3: usbfs: interface 0 claimed by usbfs while 'soffice.bin' sets config #1
Dec 21 19:23:20 linux.site kernel: usb 1-3: usbfs: interface 0 claimed by usbfs while 'soffice.bin' sets config #1
Dec 21 19:23:20 linux.site kernel: usb 1-3: usbfs: interface 0 claimed by usbfs while 'soffice.bin' sets config #1
Dec 21 19:23:21 linux.site kernel: usb 1-3: usbfs: interface 0 claimed by usbfs while 'soffice.bin' sets config #1
Dec 21 19:23:34 linux.site NetworkManager[728]: <info> Activation (ttyUSB2) starting connection 'telekom internet'
Dec 21 19:23:34 linux.site NetworkManager[728]: <info> Activation (ttyUSB2) Stage 1 of 5 (Device Prepare) scheduled...
Dec 21 19:23:34 linux.site NetworkManager[728]: <info> Activation (ttyUSB2) Stage 1 of 5 (Device Prepare) started...
Dec 21 19:23:34 linux.site NetworkManager[728]: <info> (ttyUSB2): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Dec 21 19:23:34 linux.site NetworkManager[728]: <info> NetworkManager state is now CONNECTING
Dec 21 19:23:34 linux.site NetworkManager[728]: <info> Activation (ttyUSB2) Stage 1 of 5 (Device Prepare) complete.
Dec 21 19:23:34 linux.site NetworkManager[728]: <warn> (ttyUSB2) failed to connect modem: PolicyKit authorization error: 'authority not found'
Dec 21 19:23:34 linux.site NetworkManager[728]: <info> (ttyUSB2): device state change: prepare -> failed (reason '(null)') [40 120 1]
Dec 21 19:23:34 linux.site NetworkManager[728]: <info> NetworkManager state is now DISCONNECTED
Dec 21 19:23:34 linux.site NetworkManager[728]: <info> Disabling autoconnect for connection 'telekom internet'.
Dec 21 19:23:34 linux.site NetworkManager[728]: <warn> Activation (ttyUSB2) failed for connection 'telekom internet'
Dec 21 19:23:34 linux.site NetworkManager[728]: <info> (ttyUSB2): device state change: failed -> disconnected (reason 'none') [120 30 0]
Dec 21 19:23:34 linux.site NetworkManager[728]: <info> (ttyUSB2): deactivating device (reason 'none') [0]
Dec 21 19:23:35 linux.site NetworkManager[728]: <info> Activation (ttyUSB2) starting connection 'telekom internet'
Dec 21 19:23:35 linux.site NetworkManager[728]: <info> Activation (ttyUSB2) Stage 1 of 5 (Device Prepare) scheduled...
Dec 21 19:23:35 linux.site NetworkManager[728]: <info> Activation (ttyUSB2) Stage 1 of 5 (Device Prepare) started...
Dec 21 19:23:35 linux.site NetworkManager[728]: <info> (ttyUSB2): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Dec 21 19:23:35 linux.site NetworkManager[728]: <info> NetworkManager state is now CONNECTING
Dec 21 19:23:35 linux.site NetworkManager[728]: <info> Activation (ttyUSB2) Stage 1 of 5 (Device Prepare) complete.
Dec 21 19:23:35 linux.site NetworkManager[728]: <warn> (ttyUSB2) failed to connect modem: PolicyKit authorization error: 'authority not found'
Dec 21 19:23:35 linux.site NetworkManager[728]: <info> (ttyUSB2): device state change: prepare -> failed (reason '(null)') [40 120 1]
Dec 21 19:23:35 linux.site NetworkManager[728]: <info> NetworkManager state is now DISCONNECTED
Dec 21 19:23:35 linux.site NetworkManager[728]: <info> Disabling autoconnect for connection 'telekom internet'.
Dec 21 19:23:35 linux.site NetworkManager[728]: <warn> Activation (ttyUSB2) failed for connection 'telekom internet'
Dec 21 19:23:35 linux.site NetworkManager[728]: <info> (ttyUSB2): device state change: failed -> disconnected (reason 'none') [120 30 0]
Dec 21 19:23:35 linux.site NetworkManager[728]: <info> (ttyUSB2): deactivating device (reason 'none') [0]
Dec 21 19:24:00 linux.site polkitd[768]: Unregistered Authentication Agent for unix-session:1 (system bus name :1.33, object path /org/kde/PolicyKit1/Auth
Dec 21 19:24:15 linux.site org.a11y.atspi.Registry[1403]: XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
Dec 21 19:24:15 linux.site org.a11y.atspi.Registry[1403]: after 485 requests (485 known processed) with 0 events remaining.
Dec 21 19:24:15 linux.site org.kde.kuiserver[1165]: kuiserver: Fatal IO error: client killed
Dec 21 19:24:15 linux.site org.gtk.vfs.Daemon[1165]: A connection to the bus can't be made
Dec 21 19:24:15 linux.site org.gtk.vfs.Daemon[1165]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes
Dec 21 19:24:15 linux.site org.a11y.Bus[1165]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an
Dec 21 19:24:15 linux.site systemd-udevd[1772]: error opening ATTR{/sys/devices/virtual/bdi/0:33/device/power_profile} for writing: No such file or direct
Dec 21 19:24:15 linux.site kdm[1047]: :0[1047]: pam_unix(xdm-np:session): session closed for user rich1974
Dec 21 19:24:16 linux.site bluetoothd[710]: Endpoint unregistered: sender=:1.30 path=/MediaEndpoint/A2DPSource
Dec 21 19:24:16 linux.site bluetoothd[710]: Endpoint unregistered: sender=:1.30 path=/MediaEndpoint/A2DPSink
Dec 21 19:24:16 linux.site avahi-daemon[712]: Got SIGTERM, quitting.
Dec 21 19:24:16 linux.site avahi-daemon[712]: avahi-daemon 0.6.31 exiting.
Dec 21 19:24:16 linux.site sshd[832]: Received signal 15; terminating.
Dec 21 19:24:16 linux.site ModemManager[717]: <info>  Caught signal, shutting down...
Dec 21 19:24:16 linux.site iscsiadm[1783]: iscsiadm: No matching sessions found
Dec 21 19:24:16 linux.site bluetoothd[710]: Terminating
Dec 21 19:24:16 linux.site systemd[1058]: pam_unix(systemd-user:session): session closed for user rich1974
Dec 21 19:24:16 linux.site bluetoothd[710]: Stopping SDP server
Dec 21 19:24:16 linux.site bluetoothd[710]: Exit
Dec 21 19:24:16 linux.site NetworkManager[728]: <info> (ttyUSB2): device state change: disconnected -> unmanaged (reason 'removed') [30 10 36]
Dec 21 19:24:16 linux.site NetworkManager[728]: <info> ModemManager disappeared from bus
Dec 21 19:24:16 linux.site ModemManager[717]: <info>  ModemManager is shut down
Dec 21 19:24:16 linux.site NetworkManager[728]: <info> wpa_supplicant stopped
Dec 21 19:24:16 linux.site NetworkManager[728]: <warn> disconnected by the system bus.
Dec 21 19:24:16 linux.site NetworkManager[728]: g_dbus_connection_real_closed: Remote peer vanished with error: Error receiving message: Connection reset 
Dec 21 19:24:16 linux.site postfix/postfix-script[1821]: stopping the Postfix mail system
Dec 21 19:24:16 linux.site postfix/master[1022]: terminating on signal 15
Dec 21 19:24:16 linux.site display-manager[1787]: Shutting down service kdm..done
Dec 21 19:24:17 linux.site NetworkManager[728]: <info> caught signal 15, shutting down normally.
Dec 21 19:24:17 linux.site NetworkManager[728]: <info> (eth0): device state change: unavailable -> unmanaged (reason 'removed') [20 10 36]
Dec 21 19:24:17 linux.site NetworkManager[728]: <info> (wlan0): device state change: unavailable -> unmanaged (reason 'removed') [20 10 36]
Dec 21 19:24:17 linux.site kernel: b44 ssb1:0 eth0: powering down PHY
Dec 21 19:24:17 linux.site kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Dec 21 19:24:17 linux.site kernel: IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Dec 21 19:24:17 linux.site NetworkManager[728]: <info> exiting (success)
Dec 21 19:24:17 linux.site NetworkManager[728]: (NetworkManager:728): GLib-CRITICAL **: Source ID 30 was not found when attempting to remove it
Dec 21 19:24:22 linux.site haveged[401]: haveged: Stopping due to signal 15
Dec 21 19:24:22 linux.site haveged[401]: haveged starting up
Dec 21 19:24:22 linux.site systemd-udevd[1896]: error opening ATTR{/sys/devices/pci0000:00/0000:00:12.0/ata3/host2/target2:0:0/2:0:0:0/block/sda/sda8/devi
Dec 21 19:24:22 linux.site systemd-udevd[1896]: error opening ATTR{/sys/devices/pci0000:00/0000:00:12.0/ata3/host2/target2:0:0/2:0:0:0/block/sda/sda8/devi
Dec 21 19:24:22 linux.site auditd[544]: The audit daemon is exiting.
Dec 21 19:24:22 linux.site kernel: audit: type=1305 audit(1419182662.356:156): audit_pid=0 old=544 auid=4294967295 ses=4294967295 res=1
Dec 21 19:24:22 linux.site kernel: audit: type=1131 audit(1419182662.360:157): pid=1 uid=0 auid=4294967295 ses=4294967295 msg=' comm="systemd-random-seed"
Dec 21 19:24:22 linux.site kernel: audit: type=1131 audit(1419182662.360:158): pid=1 uid=0 auid=4294967295 ses=4294967295 msg=' comm="auditd" exe="/usr/li
Dec 21 19:24:22 linux.site kernel: audit: type=1400 audit(1419182662.368:159): apparmor="STATUS" operation="profile_remove" name="/sbin/klogd" pid=1892 co
Dec 21 19:24:22 linux.site kernel: audit: type=1300 audit(1419182662.368:159): arch=40000003 syscall=4 success=yes exit=11 a0=1 a1=b76c5000 a2=b a3=b item
Dec 21 19:24:22 linux.site kernel: audit: type=1327 audit(1419182662.368:159): proctitle=2F62696E2F7368002F6574632F696E69742E642F626F6F742E61707061726D6F7
Dec 21 19:24:22 linux.site kernel: audit: type=1400 audit(1419182662.368:160): apparmor="STATUS" operation="profile_remove" name="/sbin/syslog-ng" pid=189
Dec 21 19:24:22 linux.site kernel: audit: type=1300 audit(1419182662.368:160): arch=40000003 syscall=4 success=yes exit=15 a0=1 a1=b76c5000 a2=f a3=f item
Dec 21 19:24:22 linux.site kernel: audit: type=1327 audit(1419182662.368:160): proctitle=2F62696E2F7368002F6574632F696E69742E642F626F6F742E61707061726D6F7
Dec 21 19:24:22 linux.site boot.apparmor[1859]: Unloading AppArmor profiles  ..done
Dec 21 19:24:22 linux.site dmeventd[365]: dmeventd shutting down.
Dec 21 19:24:22 linux.site systemd-journal[354]: Journal stopped
-- Reboot --

maybe someone has any clue.

now, for the sake of comparison, to put the normal bihaviuor, when it works:

Dec 21 21:19:57 linux.site ModemManager[683]: <info> Modem /org/freedesktop/ModemManager1/Modem/1: 3GPP Registration state changed (unknown -> registering)
Dec 21 21:19:57 linux.site ModemManager[683]: <info> Modem /org/freedesktop/ModemManager1/Modem/1: 3GPP Registration state changed (registering -> roaming)
Dec 21 21:19:57 linux.site ModemManager[683]: <info> Modem /org/freedesktop/ModemManager1/Modem/1: 3GPP location updated (MCC: ‘0’, MNC: ‘0’, Location area code: ‘7D4’, Cell ID: ‘7D51’)
Dec 21 21:19:57 linux.site ModemManager[683]: <info> Modem /org/freedesktop/ModemManager1/Modem/1: 3GPP location updated (MCC: ‘226’, MNC: ‘6’, Location area code: ‘7D4’, Cell ID: ‘7D51’)
Dec 21 21:19:57 linux.site ModemManager[683]: <info> Modem /org/freedesktop/ModemManager1/Modem/1: state changed (enabling -> registered)
Dec 21 21:19:57 linux.site NetworkManager[706]: <info> (ttyUSB2): modem state changed, ‘enabling’ –> ‘registered’ (reason: user-requested)
Dec 21 21:19:57 linux.site ModemManager[683]: <info> Modem /org/freedesktop/ModemManager1/Modem/1: signal quality updated (29)
Dec 21 21:19:57 linux.site ModemManager[683]: <info> Modem /org/freedesktop/ModemManager1/Modem/1: access technology changed (unknown -> umts)
Dec 21 21:20:15 linux.site NetworkManager[706]: <info> Activation (ttyUSB2) starting connection ‘telekom internet’
Dec 21 21:20:15 linux.site NetworkManager[706]: <info> Activation (ttyUSB2) Stage 1 of 5 (Device Prepare) scheduled…
Dec 21 21:20:15 linux.site NetworkManager[706]: <info> Activation (ttyUSB2) Stage 1 of 5 (Device Prepare) started…
Dec 21 21:20:15 linux.site NetworkManager[706]: <info> (ttyUSB2): device state change: disconnected -> prepare (reason ‘none’) [30 40 0]
Dec 21 21:20:15 linux.site NetworkManager[706]: <info> NetworkManager state is now CONNECTING
Dec 21 21:20:15 linux.site NetworkManager[706]: <info> Activation (ttyUSB2) Stage 1 of 5 (Device Prepare) complete.
Dec 21 21:20:15 linux.site ModemManager[683]: <info> Simple connect started…
Dec 21 21:20:15 linux.site ModemManager[683]: <info> Simple connect state (4/8): Wait to get fully enabled
Dec 21 21:20:15 linux.site ModemManager[683]: <info> Simple connect state (5/8): Register
Dec 21 21:20:15 linux.site ModemManager[683]: <info> Simple connect state (6/8): Bearer
Dec 21 21:20:15 linux.site ModemManager[683]: <info> Simple connect state (7/8): Connect
Dec 21 21:20:15 linux.site ModemManager[683]: <info> Modem /org/freedesktop/ModemManager1/Modem/1: state changed (registered -> connecting)
Dec 21 21:20:15 linux.site NetworkManager[706]: <info> (ttyUSB2): modem state changed, ‘registered’ –> ‘connecting’ (reason: user-requested)
Dec 21 21:20:15 linux.site ModemManager[683]: <info> Modem /org/freedesktop/ModemManager1/Modem/1: state changed (connecting -> connected)
Dec 21 21:20:15 linux.site ModemManager[683]: <info> Simple connect state (8/8): All done
Dec 21 21:20:15 linux.site NetworkManager[706]: <info> (ttyUSB2): modem state changed, ‘connecting’ –> ‘connected’ (reason: user-requested)
Dec 21 21:20:15 linux.site NetworkManager[706]: <warn> (ttyUSB2): failed to look up interface index
Dec 21 21:20:15 linux.site NetworkManager[706]: <info> Activation (ttyUSB2) Stage 2 of 5 (Device Configure) scheduled…
Dec 21 21:20:15 linux.site NetworkManager[706]: <info> Activation (ttyUSB2) Stage 2 of 5 (Device Configure) starting…
Dec 21 21:20:15 linux.site NetworkManager[706]: <info> (ttyUSB2): device state change: prepare -> config (reason ‘none’) [40 50 0]
Dec 21 21:20:15 linux.site NetworkManager[706]: <info> Activation (ttyUSB2) Stage 2 of 5 (Device Configure) successful.
Dec 21 21:20:15 linux.site NetworkManager[706]: <info> Activation (ttyUSB2) Stage 3 of 5 (IP Configure Start) scheduled.
Dec 21 21:20:15 linux.site NetworkManager[706]: <info> Activation (ttyUSB2) Stage 2 of 5 (Device Configure) complete.
Dec 21 21:20:15 linux.site NetworkManager[706]: <info> Activation (ttyUSB2) Stage 3 of 5 (IP Configure Start) started…
Dec 21 21:20:15 linux.site NetworkManager[706]: <info> (ttyUSB2): device state change: config -> ip-config (reason ‘none’) [50 70 0]
Dec 21 21:20:15 linux.site NetworkManager[706]: <warn> (ttyUSB2): interface ttyUSB2 not up for IP configuration
Dec 21 21:20:15 linux.site NetworkManager[706]: <info> using modem-specified IP timeout: 20 seconds
Dec 21 21:20:15 linux.site NetworkManager[706]: <info> starting PPP connection
Dec 21 21:20:15 linux.site NetworkManager[706]: <info> pppd started with pid 2079
Dec 21 21:20:15 linux.site NetworkManager[706]: <info> Activation (ttyUSB2) Stage 4 of 5 (IPv6 Configure Timeout) scheduled…
Dec 21 21:20:15 linux.site NetworkManager[706]: <info> Activation (ttyUSB2) Stage 3 of 5 (IP Configure Start) complete.
Dec 21 21:20:15 linux.site NetworkManager[706]: <info> Activation (ttyUSB2) Stage 4 of 5 (IPv6 Configure Timeout) started…
Dec 21 21:20:15 linux.site NetworkManager[706]: <info> Activation (ttyUSB2) Stage 4 of 5 (IPv6 Configure Timeout) complete.
Dec 21 21:20:15 linux.site pppd[2079]: Plugin /usr/lib/pppd/2.4.7/nm-pppd-plugin.so loaded.
Dec 21 21:20:15 linux.site pppd[2079]: pppd 2.4.7 started by root, uid 0
Dec 21 21:20:15 linux.site pppd[2079]: Using interface ppp0
Dec 21 21:20:15 linux.site pppd[2079]: Connect: ppp0 <–> /dev/ttyUSB2
Dec 21 21:20:15 linux.site systemd-udevd[2080]: error opening ATTR{/sys/devices/virtual/net/ppp0/device/power_profile} for writing: No such file or directory
Dec 21 21:20:15 linux.site NetworkManager[706]: <info> (ppp0): new Generic device (driver: ‘unknown’ ifindex: 5)
Dec 21 21:20:15 linux.site NetworkManager[706]: <info> (ppp0): exported as /org/freedesktop/NetworkManager/Devices/6
Dec 21 21:20:15 linux.site systemd-udevd[2080]: error opening ATTR{/sys/devices/virtual/net/ppp0/queues/rx-0/device/power_profile} for writing: No such file or directory
Dec 21 21:20:15 linux.site NetworkManager[706]: Plugin /usr/lib/pppd/2.4.7/nm-pppd-plugin.so loaded.
Dec 21 21:20:15 linux.site NetworkManager[706]: nm-pppd-plugin-Message: nm-ppp-plugin: (plugin_init): initializing
Dec 21 21:20:15 linux.site NetworkManager[706]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_phasechange): status 3 / phase ‘serial connection’
Dec 21 21:20:15 linux.site NetworkManager[706]: Using interface ppp0
Dec 21 21:20:15 linux.site NetworkManager[706]: Connect: ppp0 <–> /dev/ttyUSB2
Dec 21 21:20:15 linux.site NetworkManager[706]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_phasechange): status 5 / phase ‘establish’
Dec 21 21:20:15 linux.site NetworkManager[706]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_phasechange): status 6 / phase ‘authenticate’
Dec 21 21:20:15 linux.site NetworkManager[706]: nm-pppd-plugin-Message: nm-ppp-plugin: (get_credentials): passwd-hook, requesting credentials…
Dec 21 21:20:15 linux.site NetworkManager[706]: nm-pppd-plugin-Message: nm-ppp-plugin: (get_credentials): got credentials from NetworkManager
Dec 21 21:20:15 linux.site pppd[2079]: CHAP authentication succeeded
Dec 21 21:20:15 linux.site pppd[2079]: CHAP authentication succeeded
Dec 21 21:20:15 linux.site systemd-udevd[2082]: error opening ATTR{/sys/devices/virtual/net/ppp0/queues/tx-0/device/power_profile} for writing: No such file or directory
Dec 21 21:20:15 linux.site NetworkManager[706]: CHAP authentication succeeded
Dec 21 21:20:15 linux.site NetworkManager[706]: CHAP authentication succeeded
Dec 21 21:20:15 linux.site NetworkManager[706]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_phasechange): status 8 / phase ‘network’
Dec 21 21:20:18 linux.site pppd[2079]: Could not determine remote IP address: defaulting to 10.64.64.64
Dec 21 21:20:18 linux.site pppd[2079]: local IP address 10.236.2.35
Dec 21 21:20:18 linux.site pppd[2079]: remote IP address 10.64.64.64
Dec 21 21:20:18 linux.site pppd[2079]: primary DNS address 193.231.100.120
Dec 21 21:20:18 linux.site pppd[2079]: secondary DNS address 193.231.100.124
Dec 21 21:20:18 linux.site NetworkManager[706]: Could not determine remote IP address: defaulting to 10.64.64.64
Dec 21 21:20:18 linux.site NetworkManager[706]: local IP address 10.236.2.35
Dec 21 21:20:18 linux.site NetworkManager[706]: remote IP address 10.64.64.64
Dec 21 21:20:18 linux.site NetworkManager[706]: primary DNS address 193.231.100.120
Dec 21 21:20:18 linux.site NetworkManager[706]: secondary DNS address 193.231.100.124
Dec 21 21:20:18 linux.site NetworkManager[706]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_phasechange): status 9 / phase ‘running’
Dec 21 21:20:18 linux.site NetworkManager[706]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_ip_up): ip-up event
Dec 21 21:20:18 linux.site NetworkManager[706]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_ip_up): sending Ip4Config to NetworkManager…
Dec 21 21:20:18 linux.site NetworkManager[706]: <info> (ppp0): device state change: unmanaged -> unavailable (reason ‘connection-assumed’) [10 20 41]
Dec 21 21:20:18 linux.site NetworkManager[706]: <info> (ppp0): device state change: unavailable -> disconnected (reason ‘connection-assumed’) [20 30 41]
Dec 21 21:20:18 linux.site NetworkManager[706]: <info> Activation (ppp0) starting connection ‘ppp0’
Dec 21 21:20:18 linux.site NetworkManager[706]: <info> Activation (ppp0) Stage 1 of 5 (Device Prepare) scheduled…
Dec 21 21:20:18 linux.site NetworkManager[706]: <info> PPP manager(IP Config Get) reply received.
Dec 21 21:20:18 linux.site NetworkManager[706]: <info> Activation (ttyUSB2) Stage 5 of 5 (IPv4 Configure Commit) scheduled…
Dec 21 21:20:18 linux.site NetworkManager[706]: <info> Activation (ppp0) Stage 1 of 5 (Device Prepare) started…
Dec 21 21:20:18 linux.site NetworkManager[706]: <info> (ppp0): device state change: disconnected -> prepare (reason ‘none’) [30 40 0]
Dec 21 21:20:18 linux.site NetworkManager[706]: <info> Activation (ppp0) Stage 2 of 5 (Device Configure) scheduled…
Dec 21 21:20:18 linux.site NetworkManager[706]: <info> Activation (ppp0) Stage 1 of 5 (Device Prepare) complete.
Dec 21 21:20:18 linux.site NetworkManager[706]: <info> Activation (ttyUSB2) Stage 5 of 5 (IPv4 Commit) started…
Dec 21 21:20:18 linux.site NetworkManager[706]: <info> (ttyUSB2): device state change: ip-config -> ip-check (reason ‘none’) [70 80 0]
Dec 21 21:20:18 linux.site NetworkManager[706]: <info> Activation (ttyUSB2) Stage 5 of 5 (IPv4 Commit) complete.
Dec 21 21:20:18 linux.site NetworkManager[706]: <info> Activation (ppp0) Stage 2 of 5 (Device Configure) starting…
Dec 21 21:20:18 linux.site NetworkManager[706]: <info> (ppp0): device state change: prepare -> config (reason ‘none’) [40 50 0]
Dec 21 21:20:18 linux.site NetworkManager[706]: <info> Activation (ppp0) Stage 2 of 5 (Device Configure) successful.
Dec 21 21:20:18 linux.site NetworkManager[706]: <info> Activation (ppp0) Stage 3 of 5 (IP Configure Start) scheduled.
Dec 21 21:20:18 linux.site NetworkManager[706]: <info> Activation (ppp0) Stage 2 of 5 (Device Configure) complete.
Dec 21 21:20:18 linux.site NetworkManager[706]: <info> Activation (ppp0) Stage 3 of 5 (IP Configure Start) started…
Dec 21 21:20:18 linux.site NetworkManager[706]: <info> (ppp0): device state change: config -> ip-config (reason ‘none’) [50 70 0]
Dec 21 21:20:18 linux.site NetworkManager[706]: <info> Activation (ppp0) Stage 5 of 5 (IPv4 Configure Commit) scheduled…
Dec 21 21:20:18 linux.site NetworkManager[706]: <info> Activation (ppp0) Stage 3 of 5 (IP Configure Start) complete.
Dec 21 21:20:18 linux.site NetworkManager[706]: <info> (ttyUSB2): device state change: ip-check -> secondaries (reason ‘none’) [80 90 0]
Dec 21 21:20:18 linux.site NetworkManager[706]: <info> Activation (ppp0) Stage 5 of 5 (IPv4 Commit) started…
Dec 21 21:20:18 linux.site NetworkManager[706]: <info> (ppp0): device state change: ip-config -> ip-check (reason ‘none’) [70 80 0]
Dec 21 21:20:18 linux.site NetworkManager[706]: <info> Activation (ppp0) Stage 5 of 5 (IPv4 Commit) complete.
Dec 21 21:20:18 linux.site NetworkManager[706]: <info> (ttyUSB2): device state change: secondaries -> activated (reason ‘none’) [90 100 0]
Dec 21 21:20:18 linux.site NetworkManager[706]: <info> NetworkManager state is now CONNECTED_LOCAL
Dec 21 21:20:18 linux.site NetworkManager[706]: <info> NetworkManager state is now CONNECTED_GLOBAL
Dec 21 21:20:18 linux.site NetworkManager[706]: <info> Policy set ‘telekom internet’ (ppp0) as default for IPv4 routing and DNS.
Dec 21 21:20:18 linux.site NetworkManager[706]: <info> Policy set ‘telekom internet’ (ppp0) as default for IPv6 routing and DNS.
Dec 21 21:20:18 linux.site NetworkManager[706]: <info> Activation (ttyUSB2) successful, device activated.
Dec 21 21:20:18 linux.site dbus[689]: [system] Activating via systemd: service name=‘org.freedesktop.nm_dispatcher’ unit=‘dbus-org.freedesktop.nm-dispatcher.service’
Dec 21 21:20:18 linux.site NetworkManager[706]: <info> (ppp0): device state change: ip-check -> secondaries (reason ‘none’) [80 90 0]
Dec 21 21:20:18 linux.site NetworkManager[706]: <info> (ppp0): device state change: secondaries -> activated (reason ‘none’) [90 100 0]
Dec 21 21:20:18 linux.site dbus[689]: [system] Successfully activated service ‘org.freedesktop.nm_dispatcher’
Dec 21 21:20:18 linux.site nm-dispatcher[2087]: Dispatching action ‘up’ for ppp0
Dec 21 21:20:18 linux.site NetworkManager[706]: <info> Activation (ppp0) successful, device activated.
Dec 21 21:20:18 linux.site automount[2109]: failed to to open old config /etc/sysconfig/autofs
Dec 21 21:20:18 linux.site automount[2112]: lookup_init:139: lookup(yp): map auto.master: Local domain name not set
Dec 21 21:20:18 linux.site nm-dispatcher[2087]: Dispatching action ‘up’ for ppp0
Dec 21 21:20:18 linux.site automount[2179]: failed to to open old config /etc/sysconfig/autofs
Dec 21 21:20:18 linux.site automount[2188]: lookup_init:139: lookup(yp): map auto.master: Local domain name not set
Dec 21 21:20:28 linux.site ModemManager[683]: <info> Modem /org/freedesktop/ModemManager1/Modem/1: signal quality updated (29)

i am very sorry but this problem really bothers me.

Ok, so this seems indeed to be that permissions problem.

i am thinking to replace “plasma-nm” with “nm-applet” or “knetworkmanager”.

Won’t help then. It is NetworkManager that needs those permissions, and if your user doesn’t have those permissions it doesn’t matter which frontend you use.

I suppose, disabling autofs.service is not an option for you, right?
Have you ever looked into that bug report?
IIRC, there’s another workaround in there as well, and there are new NetworkManager packages mentioned there that should fix the issue. You could try to install those.

it seems that i am out of luck for now. i enabled “systemctl enable autofs.service”, i readded that line “before=…” and i installed the network manager from “factory”.
i even disable the autologin…
last night it seens to work, but in this morning, it do not! these are the significant errors that i see:

 <warn> (ttyUSB2) failed to enable modem: GDBus.Error:org.freedesktop.ModemManager1.Error.Core.Failed: PolicyKit authorization error: 'authority not found'

<warn> (ttyUSB2) failed to connect modem: PolicyKit authorization error: 'authority not found'

From “factory”? What exactly do you mean with that?

That fix got only accepted yesterday to Factory and is not in the repos yet I suppose.
Better use the version from aarvidjar’s testing repo, as written here:
https://bugzilla.opensuse.org/show_bug.cgi?id=905639#c39

If you did that, I have no idea, other than trying to disable autofs.service and see if it is fixed then (your problem might be triggered by something else too).
And/or join the bug report and state that you still have problems even with this fix installed.

PS: to be sure whether this is really the same problem, run “loginctl” when the problem occurs and check whether your user session is listed or not. If yes, you have a completely different problem…

what is really strange is that the issue is happening randomly. for this moment, it works okay:

rich1974@linux:~> su
Password: 
linux:/home/rich1974 # loginctl
   SESSION        UID USER             SEAT            
         1       1000 rich1974         seat0           

1 sessions listed.
linux:/home/rich1974 # 

by factory i mean that i entered the opensuse.software, looking for networkmanager packege and choose factory from that list.

for disable autofs.service i must run “systemctl disable autofs.service” and then reboot, is this okay, isn’t it?
and for enable “systemctl enable autofs.service” and reboot, isn’t it?

and about that updated NM that you told me about, i see that is related to gnome, i am running KDE, is that a problem?

Well, it is a race-condition/timing problem, so it is not strange at all that it happens randomly. Such things are difficult to debug/fix (or even to find before the release… :wink: ) therefore.

FTR, I could not reproduce this problem here at all, on two different systems. Even if I enable autofs.service and Auto-Login, everything works fine. So probably some particular autofs config is necessary as well I suppose…

by factory i mean that i entered the opensuse.software, looking for networkmanager packege and choose factory from that list.

???
I don’t see any Package for Factory there, only Tumbleweed.
But this package does not contain the fix yet.
Install the one from aarvidjar’s home repo, as explained in the bug report.

for disable autofs.service i must run “systemctl disable autofs.service” and then reboot, is this okay, isn’t it?
and for enable “systemctl enable autofs.service” and reboot, isn’t it?

Yes.

and about that updated NM that you told me about, i see that is related to gnome, i am running KDE, is that a problem?

No. NetworkManager is a GNOME product, but NM itself is desktop agnostic.
There is only one NetworkManager that is used by all NM frontends.

okay, it is tumbleweed, sorry, my bad…

but who is this Andrei Borzenkov, is he some king of developer for opensuse? is he trustworthy person? anyway…the update seems to be a piece of cake, i must add his testing repositori, update packege source and install the update by running only this three commands, one at the time:

zypper ar obs://home:arvidjaar:bnc:905639/standard [bnc905639](http://bugzilla.novell.com/show_bug.cgi?id=905639)
zypper refresh [bnc905639](http://bugzilla.novell.com/show_bug.cgi?id=905639)
zypper dup -r [bnc905639](http://bugzilla.novell.com/show_bug.cgi?id=905639)

ps: before this post, i have rebooted again and the system works okay, before this reboot i have disabled the autofs.service. from this behavior, i came to the conclusion that my networkmanager has nothing to do weather the autofs.service is emable or not.

thanx again for your time!

Yes, it is “arvidjaar” here in the forums.
And his patch has been accepted to Factory anyway, so you’d use it sooner or later, especially if you’d install that Factory/Tumbleweed package.
You can of course look yourself at the changes he made:
https://build.opensuse.org/package/show/home:arvidjaar:bnc:905639/NetworkManager
Btw, that patch is taken from NetworkManager upstream. :wink:

Anyway, your only other option is to wait until this is released as online update…
So please decide yourself whether you’d trust him or not, and whether the issue is problematic enough to you to rectify doing so.

the update seems to be a piece of cake, i must add his testing repositori, update packege source and install the update by running only this three commands, one at the time:

zypper ar obs://home:arvidjaar:bnc:905639/standard [bnc905639](http://bugzilla.novell.com/show_bug.cgi?id=905639)
zypper refresh [bnc905639](http://bugzilla.novell.com/show_bug.cgi?id=905639)
zypper dup -r [bnc905639](http://bugzilla.novell.com/show_bug.cgi?id=905639)

Yes.
You could download and install all the packages manually too if you wanted, but why make it more difficult than necessary? :wink:

ps: before this post, i have rebooted again and the system works okay, before this reboot i have disabled the autofs.service. from this behavior, i came to the conclusion that my networkmanager has nothing to do weather the autofs.service is emable or not.

???
Of course NetworkManager has nothing to do whether autofs.service is enabled or not.
Those are two different services. You can enable/disable them independent of each other.
autofs doesn’t need NetworkManager anyway. But apparently that “Before: systemd-logind” line introduced some cyclic dependency between autofs, systemd-logind and NetworkManager which caused logind to start too late or something like that, which that updated package should fix.