Bug 1257572 - NM keep restarting, nm-applet in KDE flickers
NM keep restarting, nm-applet in KDE flickers
Status: CLOSED WORKSFORME
Product: Fedora
Classification: Fedora
Component: NetworkManager (Show other bugs)
22
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Lubomir Rintel
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-08-27 07:31 EDT by Stefan Neufeind
Modified: 2015-09-07 09:31 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-09-07 09:31:18 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Stefan Neufeind 2015-08-27 07:31:36 EDT
NM seem to restart (?) when looking for connections (and maybe it autoconnects).

Crashes/Restarts/... with: 1.0.6-0.2.20150813git7e2caa2.fc22
Works with: NetworkManager-1.0.2-1.fc22.x86_64
(one version before)

The network-icon (nm-applet?) in KDE flickers (goes away, comes back) in short cycles.

Aug 27 13:21:43 localhost NetworkManager[5149]: <info>  WiFi hardware radio set enabled
Aug 27 13:21:43 localhost NetworkManager[5149]: <info>  WWAN hardware radio set disabled
Aug 27 13:21:43 localhost NetworkManager[5149]: <info>  Loaded device plugin: NMVxlanFactory (internal)
Aug 27 13:21:43 localhost NetworkManager[5149]: <info>  Loaded device plugin: NMVlanFactory (internal)
Aug 27 13:21:43 localhost NetworkManager[5149]: <info>  Loaded device plugin: NMVethFactory (internal)
Aug 27 13:21:43 localhost NetworkManager[5149]: <info>  Loaded device plugin: NMTunFactory (internal)
Aug 27 13:21:43 localhost NetworkManager[5149]: <info>  Loaded device plugin: NMMacvlanFactory (internal)
Aug 27 13:21:43 localhost NetworkManager[5149]: <info>  Loaded device plugin: NMInfinibandFactory (internal)
Aug 27 13:21:43 localhost NetworkManager[5149]: <info>  Loaded device plugin: NMGreFactory (internal)
Aug 27 13:21:43 localhost NetworkManager[5149]: <info>  Loaded device plugin: NMEthernetFactory (internal)
Aug 27 13:21:43 localhost NetworkManager[5149]: <info>  Loaded device plugin: NMBridgeFactory (internal)
Aug 27 13:21:43 localhost NetworkManager[5149]: <info>  Loaded device plugin: NMBondFactory (internal)
Aug 27 13:21:43 localhost NetworkManager[5149]: <info>  Loaded device plugin: NMWifiFactory (/usr/lib64/NetworkManager/libnm-device-plugin-wifi.so)
Aug 27 13:21:43 localhost NetworkManager[5149]: <info>  Loaded device plugin: NMTeamFactory (/usr/lib64/NetworkManager/libnm-device-plugin-team.so)
Aug 27 13:21:43 localhost NetworkManager[5149]: <info>  Loaded device plugin: NMAtmManager (/usr/lib64/NetworkManager/libnm-device-plugin-adsl.so)
Aug 27 13:21:43 localhost NetworkManager[5149]: <info>  Loaded device plugin: NMWwanFactory (/usr/lib64/NetworkManager/libnm-device-plugin-wwan.so)
Aug 27 13:21:43 localhost NetworkManager[5149]: <info>  Loaded device plugin: NMBluezManager (/usr/lib64/NetworkManager/libnm-device-plugin-bluetooth.so)
Aug 27 13:21:43 localhost NetworkManager[5149]: <info>  WiFi enabled by radio killswitch; enabled by state file
Aug 27 13:21:43 localhost NetworkManager[5149]: <info>  WWAN disabled by radio killswitch; disabled by state file
Aug 27 13:21:43 localhost NetworkManager[5149]: <info>  WiMAX enabled by radio killswitch; disabled by state file
Aug 27 13:21:43 localhost NetworkManager[5149]: <info>  Networking is enabled by state file
Aug 27 13:21:43 localhost NetworkManager[5149]: <info>  (virbr0): new Bridge device (carrier: OFF, driver: 'bridge', ifindex: 6)
Aug 27 13:21:43 localhost NetworkManager[5149]: <info>  (virbr0-nic): new Tun device (carrier: OFF, driver: 'tun', ifindex: 7)
Aug 27 13:21:43 localhost NetworkManager[5149]: <info>  (virbr0): bridge port virbr0-nic was attached
Aug 27 13:21:43 localhost NetworkManager[5149]: <info>  (virbr0-nic): enslaved to virbr0
Aug 27 13:21:43 localhost NetworkManager[5149]: <info>  (enp0s25): new Ethernet device (carrier: OFF, driver: 'e1000e', ifindex: 2)
Aug 27 13:21:43 localhost NetworkManager[5149]: <info>  (enp0s25): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Aug 27 13:21:43 localhost NetworkManager[5149]: <info>  (wlp4s0): using nl80211 for WiFi device control
Aug 27 13:21:43 localhost NetworkManager[5149]: <info>  (wlp4s0): driver supports Access Point (AP) mode
Aug 27 13:21:43 localhost NetworkManager[5149]: <info>  (wlp4s0): new 802.11 WiFi device (carrier: UNKNOWN, driver: 'iwlwifi', ifindex: 4)
Aug 27 13:21:43 localhost NetworkManager[5149]: <info>  (wlp4s0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Aug 27 13:21:43 localhost NetworkManager[5149]: <info>  (enp0s20u2u1): link connected
Aug 27 13:21:43 localhost NetworkManager[5149]: <info>  (enp0s20u2u1): new Ethernet device (carrier: ON, driver: 'ax88179_178a', ifindex: 8)
Aug 27 13:21:43 localhost NetworkManager[5149]: <info>  (enp0s20u2u1): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Aug 27 13:21:43 localhost NetworkManager[5149]: <info>  (lo): link connected
Aug 27 13:21:43 localhost NetworkManager[5149]: <info>  (lo): new Generic device (carrier: ON, driver: 'unknown', ifindex: 1)
Aug 27 13:21:43 localhost NetworkManager[5149]: <info>  (enp0s20u2u1): device state change: unavailable -> disconnected (reason 'none') [20 30 0]
Aug 27 13:21:43 localhost NetworkManager[5149]: <info>  use BlueZ version 5
Aug 27 13:21:43 localhost NetworkManager[5149]: <info>  wpa_supplicant running
Aug 27 13:21:43 localhost NetworkManager[5149]: <info>  (wlp4s0) supports 5 scan SSIDs
Aug 27 13:21:43 localhost NetworkManager[5149]: <info>  (wlp4s0): supplicant interface state: starting -> ready
Aug 27 13:21:43 localhost NetworkManager[5149]: <info>  (wlp4s0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
Aug 27 13:21:45 localhost audit: <audit-1130> pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-wait-online comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Aug 27 13:21:45 localhost audit: <audit-1131> pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-wait-online comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Aug 27 13:21:45 localhost NetworkManager[5149]: <info>  caught SIGTERM, shutting down normally.
Aug 27 13:21:45 localhost NetworkManager[5149]: <info>  (virbr0): bridge port virbr0-nic was detached
Aug 27 13:21:45 localhost NetworkManager[5149]: <info>  (virbr0-nic): released from master virbr0
Aug 27 13:21:45 localhost NetworkManager[5149]: <info>  (enp0s25): device state change: unavailable -> unmanaged (reason 'unmanaged') [20 10 3]
Aug 27 13:21:45 localhost NetworkManager[5149]: <info>  (wlp4s0): device state change: disconnected -> unmanaged (reason 'unmanaged') [30 10 3]
Aug 27 13:21:45 localhost NetworkManager[5149]: <info>  (enp0s20u2u1): device state change: disconnected -> unmanaged (reason 'unmanaged') [30 10 3]
Aug 27 13:21:45 localhost NetworkManager[5149]: <info>  startup complete
Aug 27 13:21:45 localhost NetworkManager[5149]: <info>  exiting (success)
Aug 27 13:21:45 localhost audit: <audit-1131> pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Aug 27 13:23:24 localhost NetworkManager[5469]: <info>  NetworkManager (version 1.0.2-1.fc22) is starting...
Aug 27 13:23:24 localhost NetworkManager[5469]: <info>  Read config: /etc/NetworkManager/NetworkManager.conf and conf.d: 20-connectivity-fedora.conf
Aug 27 13:23:24 localhost NetworkManager[5469]: <info>  WEXT support is enabled
Comment 1 Lubomir Rintel 2015-08-27 09:41:40 EDT
Aug 27 13:21:45 localhost NetworkManager[5149]: <info>  caught SIGTERM, shutting down normally.

Well, something kills NetworkManager from outside. Is what you pasted a full output from journald or is there something else around those lines?
Comment 2 Lubomir Rintel 2015-08-27 09:45:23 EDT
You can find out what sends the signal by auditing sending of signals:

auditctl -a exit,always -F arch=b64 -S kill -F a1=1

Then watch the journal for audit messages.
Comment 3 Lubomir Rintel 2015-09-07 09:31:18 EDT
Closing this. Feel free to reopen in case you still believe there's an issue to be fixed.

Note You need to log in before you can comment on or make changes to this bug.