Bug 301463 - network management plasmoid doesn't startup after boot and says NetworkManager is not running
Summary: network management plasmoid doesn't startup after boot and says NetworkManage...
Status: RESOLVED DOWNSTREAM
Alias: None
Product: Network Management
Classification: Miscellaneous
Component: knetworkmanager (show other bugs)
Version: 0.9
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Lamarque V. Souza
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-06-08 17:21 UTC by Jorge Adriano
Modified: 2012-07-03 12:40 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jorge Adriano 2012-06-08 17:21:57 UTC
Just upgraded to KDE 4.9 beta 1 (KDE 4.8.80 OpenSUSE rpms from unstable repository). 

Rebooted and on log in the Network Management applet did not start up as usual. Added it manually to the panel, and it showed no connections, and displayed the message: 
     "NetworkManager is not running. Please start it."
Also the "enable networking" option was not ticked. Turning that on was enough to connect to the internet but still, no connections appear as available, and the same error message is displayed.

There is a NeworkManager process running: 
"ps -A |grep NetworkManager
921 ?        00:00:08 NetworkManager"

And rcnetwork status displays:
"redirecting to systemctl
network.service - LSB: Configure the localfs depending network interfaces
          Loaded: loaded (/etc/init.d/network)
          Active: active (exited) since Thu, 07 Jun 2012 21:40:39 +0100; 20h ago
         Process: 959 ExecStart=/etc/init.d/network start (code=exited, status=0/SUCCESS)
          CGroup: name=systemd:/system/network.service"
    

Reproducible: Always

Steps to Reproduce:
1. Install OpenSUSE KDE Unstable rpms
2. Reboot 
3. Login
Actual Results:  
No Network Manager applet, and adding one manually shows no connections, and the "enable networking" option is not ticked. And of course no connection to internet is active. 

Expected Results:  
Network Manager applet on systray, available connections displayed, enable networking option ticked, and default connection activated.
Comment 1 Lamarque V. Souza 2012-06-08 18:22:04 UTC
Paste the output of the commands below:

nm-tool
qdbus --system org.freedesktop.NetworkManager
Comment 2 Jorge Adriano 2012-06-08 18:28:56 UTC
NetworkManager Tool

State: connected (global)

- Device: wlan0  [Stormwind] ---------------------------------------------------
  Type:              802.11 WiFi
  Driver:            iwlagn
  State:             connected
  Default:           yes
  HW Address:        8C:A9:82:10:8E:F0

  Capabilities:
    Speed:           54 Mb/s

  Wireless Properties
    WEP Encryption:  yes
    WPA Encryption:  yes
    WPA2 Encryption: yes

  Wireless Access Points (* = current AP)
    SKY54945:        Infra, E8:BE:81:74:D6:A2, Freq 2462 MHz, Rate 54 Mb/s, Strength 19 WPA
    NETGEAR:         Infra, 00:18:4D:BD:3F:32, Freq 2462 MHz, Rate 54 Mb/s, Strength 44 WPA
    BTFON:           Infra, 0A:21:04:D0:7C:E2, Freq 2462 MHz, Rate 54 Mb/s, Strength 19
    SKY79968:        Infra, 14:D6:4D:A8:A9:D9, Freq 2412 MHz, Rate 54 Mb/s, Strength 19 WPA WPA2
    TalkTalkWiFi:    Infra, 00:26:B6:39:5A:CE, Freq 2412 MHz, Rate 54 Mb/s, Strength 19 WPA
    BTHomeHub2-QFW7: Infra, 00:21:04:D0:7C:E2, Freq 2462 MHz, Rate 54 Mb/s, Strength 20 WPA WPA2
    O2wireless483134:Infra, 00:1D:68:EF:18:E7, Freq 2437 MHz, Rate 54 Mb/s, Strength 20 WEP
    INTERFACEWIFI:   Infra, 14:D6:4D:FF:1C:8A, Freq 2447 MHz, Rate 54 Mb/s, Strength 24 WPA WPA2
    central:         Infra, 40:F4:EC:7E:D0:B0, Freq 2462 MHz, Rate 54 Mb/s, Strength 17
    eduroam:         Infra, 40:F4:EC:7E:D0:B1, Freq 2462 MHz, Rate 54 Mb/s, Strength 20 WPA WPA2 Enterprise
    IT:              Infra, 2C:B0:5D:39:54:1C, Freq 2412 MHz, Rate 54 Mb/s, Strength 22 WPA2
    Chris's Wi-Fi Network: Infra, 70:73:CB:B8:AB:F3, Freq 2462 MHz, Rate 54 Mb/s, Strength 19 WPA2
    BTOpenzone-H:    Infra, 06:21:04:D0:7C:E2, Freq 2462 MHz, Rate 54 Mb/s, Strength 19
    mynetwork1:      Infra, 00:1B:9E:94:7D:B3, Freq 2462 MHz, Rate 54 Mb/s, Strength 80 WEP
    Home_123:        Infra, 00:17:3F:7C:93:32, Freq 2472 MHz, Rate 54 Mb/s, Strength 50 WEP
    IT:              Infra, 2C:B0:5D:39:54:01, Freq 2437 MHz, Rate 54 Mb/s, Strength 30 WPA2
    *Stormwind:      Infra, 00:14:BF:D7:19:C2, Freq 2427 MHz, Rate 54 Mb/s, Strength 100 WPA2

  IPv4 Settings:
    Address:         192.168.3.43
    Prefix:          24 (255.255.255.0)
    Gateway:         192.168.3.1

    DNS:             192.168.3.1


- Device: eth0 -----------------------------------------------------------------
  Type:              Wired
  Driver:            r8169
  State:             unavailable
  Default:           no
  HW Address:        14:DA:E9:32:AF:49

  Capabilities:
    Carrier Detect:  yes
    Speed:           10 Mb/s

  Wired Properties
    Carrier:         off
Comment 3 Jorge Adriano 2012-06-08 18:29:35 UTC
/
/org
/org/freedesktop
/org/freedesktop/NetworkManager
/org/freedesktop/NetworkManager/AccessPoint
/org/freedesktop/NetworkManager/AccessPoint/21
/org/freedesktop/NetworkManager/AccessPoint/315
/org/freedesktop/NetworkManager/AccessPoint/316
/org/freedesktop/NetworkManager/AccessPoint/317
/org/freedesktop/NetworkManager/AccessPoint/337
/org/freedesktop/NetworkManager/AccessPoint/366
/org/freedesktop/NetworkManager/AccessPoint/367
/org/freedesktop/NetworkManager/AccessPoint/369
/org/freedesktop/NetworkManager/AccessPoint/371
/org/freedesktop/NetworkManager/AccessPoint/372
/org/freedesktop/NetworkManager/AccessPoint/373
/org/freedesktop/NetworkManager/AccessPoint/377
/org/freedesktop/NetworkManager/AccessPoint/378
/org/freedesktop/NetworkManager/AccessPoint/379
/org/freedesktop/NetworkManager/AccessPoint/380
/org/freedesktop/NetworkManager/AccessPoint/381
/org/freedesktop/NetworkManager/AccessPoint/382
/org/freedesktop/NetworkManager/AccessPoint/383
/org/freedesktop/NetworkManager/ActiveConnection
/org/freedesktop/NetworkManager/ActiveConnection/1
/org/freedesktop/NetworkManager/AgentManager
/org/freedesktop/NetworkManager/DHCP4Config
/org/freedesktop/NetworkManager/DHCP4Config/0
/org/freedesktop/NetworkManager/Devices
/org/freedesktop/NetworkManager/Devices/0
/org/freedesktop/NetworkManager/Devices/1
/org/freedesktop/NetworkManager/IP4Config
/org/freedesktop/NetworkManager/IP4Config/0
/org/freedesktop/NetworkManager/Settings
/org/freedesktop/NetworkManager/Settings/0
/org/freedesktop/NetworkManager/Settings/1
/org/freedesktop/NetworkManager/Settings/2
Comment 4 Lamarque V. Souza 2012-06-08 18:44:45 UTC
What does the command below return?

qdbus --system org.freedesktop.NetworkManager \
/org/freedesktop/NetworkManager org.freedesktop.NetworkManager.Version

qdbus org.kde.networkmanagement

What happen if you retstart plasma-desktop using the commands below?

kquitapp plasma-desktop && sleep 5 && kdeinit4_wrapper plasma-desktop
Comment 5 Jorge Adriano 2012-06-08 18:49:13 UTC
> qdbus --system org.freedesktop.NetworkManager \ /org/freedesktop/NetworkManager org.freedesktop.NetworkManager.Version: 

0.9.2.0

> qdbus org.kde.networkmanagement

/
/KBookmarkManager
/KBookmarkManager/kfilePlaces
/KIO
/KIO/Scheduler
/Layouts
/MainApplication
/Mixers
/Mixers/0
/Mixers/0/alsa_output_pci_0000_00_1b_0_analog_stereo
/Mixers/1
/Mixers/1/alsa_input_pci_0000_00_1b_0_analog_stereo
/Mixers/2
/Mixers/2/restore_sink_input_by_media_role_event
/Mixers/2/stream_1
/Mixers/2/stream_10
/Mixers/2/stream_11
/Mixers/2/stream_111
/Mixers/2/stream_112
/Mixers/2/stream_113
/Mixers/2/stream_114
/Mixers/2/stream_115
/Mixers/2/stream_116
/Mixers/2/stream_117
/Mixers/2/stream_118
/Mixers/2/stream_119
/Mixers/2/stream_120
/Mixers/2/stream_121
/Mixers/2/stream_122
/Mixers/2/stream_123
/Mixers/2/stream_124
/Mixers/2/stream_125
/Mixers/2/stream_126
/Mixers/2/stream_127
/Mixers/2/stream_128
/Mixers/2/stream_129
/Mixers/2/stream_130
/Mixers/2/stream_131
/Mixers/2/stream_132
/Mixers/2/stream_133
/Mixers/2/stream_134
/Mixers/2/stream_135
/Mixers/2/stream_136
/Mixers/2/stream_145
/Mixers/2/stream_146
/Mixers/2/stream_147
/Mixers/2/stream_149
/Mixers/2/stream_150
/Mixers/2/stream_151
/Mixers/2/stream_155
/Mixers/2/stream_156
/Mixers/2/stream_157
/Mixers/2/stream_158
/Mixers/2/stream_159
/Mixers/2/stream_160
/Mixers/2/stream_161
/Mixers/2/stream_162
/Mixers/2/stream_163
/Mixers/2/stream_164
/Mixers/2/stream_165
/Mixers/2/stream_166
/Mixers/2/stream_167
/Mixers/2/stream_168
/Mixers/2/stream_169
/Mixers/2/stream_17
/Mixers/2/stream_170
/Mixers/2/stream_171
/Mixers/2/stream_175
/Mixers/2/stream_176
/Mixers/2/stream_177
/Mixers/2/stream_18
/Mixers/2/stream_185
/Mixers/2/stream_186
/Mixers/2/stream_187
/Mixers/2/stream_188
/Mixers/2/stream_189
/Mixers/2/stream_19
/Mixers/2/stream_190
/Mixers/2/stream_191
/Mixers/2/stream_192
/Mixers/2/stream_193
/Mixers/2/stream_194
/Mixers/2/stream_195
/Mixers/2/stream_196
/Mixers/2/stream_197
/Mixers/2/stream_198
/Mixers/2/stream_2
/Mixers/2/stream_20
/Mixers/2/stream_200
/Mixers/2/stream_201
/Mixers/2/stream_202
/Mixers/2/stream_203
/Mixers/2/stream_204
/Mixers/2/stream_205
/Mixers/2/stream_206
/Mixers/2/stream_207
/Mixers/2/stream_208
/Mixers/2/stream_209
/Mixers/2/stream_21
/Mixers/2/stream_210
/Mixers/2/stream_211
/Mixers/2/stream_212
/Mixers/2/stream_213
/Mixers/2/stream_214
/Mixers/2/stream_215
/Mixers/2/stream_216
/Mixers/2/stream_217
/Mixers/2/stream_218
/Mixers/2/stream_219
/Mixers/2/stream_22
/Mixers/2/stream_220
/Mixers/2/stream_221
/Mixers/2/stream_222
/Mixers/2/stream_223
/Mixers/2/stream_224
/Mixers/2/stream_225
/Mixers/2/stream_226
/Mixers/2/stream_227
/Mixers/2/stream_228
/Mixers/2/stream_229
/Mixers/2/stream_23
/Mixers/2/stream_230
/Mixers/2/stream_231
/Mixers/2/stream_232
/Mixers/2/stream_233
/Mixers/2/stream_234
/Mixers/2/stream_235
/Mixers/2/stream_236
/Mixers/2/stream_237
/Mixers/2/stream_238
/Mixers/2/stream_239
/Mixers/2/stream_240
/Mixers/2/stream_241
/Mixers/2/stream_242
/Mixers/2/stream_243
/Mixers/2/stream_244
/Mixers/2/stream_245
/Mixers/2/stream_246
/Mixers/2/stream_247
/Mixers/2/stream_248
/Mixers/2/stream_250
/Mixers/2/stream_255
/Mixers/2/stream_256
/Mixers/2/stream_257
/Mixers/2/stream_259
/Mixers/2/stream_260
/Mixers/2/stream_261
/Mixers/2/stream_262
/Mixers/2/stream_263
/Mixers/2/stream_264
/Mixers/2/stream_265
/Mixers/2/stream_266
/Mixers/2/stream_269
/Mixers/2/stream_270
/Mixers/2/stream_271
/Mixers/2/stream_273
/Mixers/2/stream_274
/Mixers/2/stream_275
/Mixers/2/stream_276
/Mixers/2/stream_279
/Mixers/2/stream_280
/Mixers/2/stream_281
/Mixers/2/stream_282
/Mixers/2/stream_283
/Mixers/2/stream_284
/Mixers/2/stream_3
/Mixers/2/stream_324
/Mixers/2/stream_325
/Mixers/2/stream_326
/Mixers/2/stream_327
/Mixers/2/stream_328
/Mixers/2/stream_329
/Mixers/2/stream_330
/Mixers/2/stream_331
/Mixers/2/stream_332
/Mixers/2/stream_336
/Mixers/2/stream_337
/Mixers/2/stream_338
/Mixers/2/stream_339
/Mixers/2/stream_340
/Mixers/2/stream_341
/Mixers/2/stream_344
/Mixers/2/stream_378
/Mixers/2/stream_382
/Mixers/2/stream_384
/Mixers/2/stream_385
/Mixers/2/stream_386
/Mixers/2/stream_387
/Mixers/2/stream_396
/Mixers/2/stream_4
/Mixers/2/stream_401
/Mixers/2/stream_402
/Mixers/2/stream_403
/Mixers/2/stream_404
/Mixers/2/stream_405
/Mixers/2/stream_408
/Mixers/2/stream_409
/Mixers/2/stream_426
/Mixers/2/stream_430
/Mixers/2/stream_431
/Mixers/2/stream_432
/Mixers/2/stream_433
/Mixers/2/stream_434
/Mixers/2/stream_5
/Mixers/2/stream_6
/Mixers/2/stream_7
/Mixers/2/stream_71
/Mixers/2/stream_75
/Mixers/2/stream_76
/Mixers/2/stream_77
/Mixers/2/stream_78
/Mixers/2/stream_79
/Mixers/2/stream_80
/Mixers/2/stream_81
/Mixers/2/stream_82
/Mixers/2/stream_83
/Mixers/2/stream_84
/Mixers/2/stream_85
/Mixers/2/stream_86
/Mixers/2/stream_87
/Mixers/2/stream_88
/Mixers/2/stream_89
/Mixers/2/stream_9
/Mixers/2/stream_90
/Mixers/2/stream_91
/Mixers/2/stream_92
/Mixers/2/stream_93
/Mixers/2/stream_94
/Mixers/2/stream_95
/Mixers/2/stream_96
/Mixers/2/stream_97
/Mixers/2/stream_98
/Mixers/2/stream_99
/Mixers/3
/StatusNotifierWatcher
/kbuildsycoca
/kded
/modules
/modules/StatusNotifierWatcher
/modules/bluedevil
/modules/device_automounter
/modules/dnssdwatcher
/modules/favicons
/modules/freespacenotifier
/modules/kcookiejar
/modules/keyboard
/modules/khotkeys
/modules/kmixd
/modules/ktimezoned
/modules/kwrited
/modules/nepomuksearchmodule
/modules/networkmanagement
/modules/networkstatus
/modules/obexftpdaemon
/modules/powerdevil
/modules/randrmonitor
/modules/remotedirnotify
/modules/solidautoeject
/modules/statusnotifierwatcher
/org
/org/freedesktop
/org/freedesktop/PowerManagement
/org/freedesktop/PowerManagement/Inhibit
/org/kde
/org/kde/Solid
/org/kde/Solid/PowerManagement
/org/kde/Solid/PowerManagement/PolicyAgent
/org/kde/networkmanagement
Comment 6 Jorge Adriano 2012-06-08 18:54:47 UTC
After restarting plasma-desktop as you've suggested the applet does show in the systray. I had also noticed that was the case when logging out and back in KDE. 

However the applet is not working. Doesn't show any available connection, and complains about Network Manager not running. Also "enable networking" is ticked off, but marking it on doesn't change anything.
Comment 7 Lamarque V. Souza 2012-06-08 19:07:20 UTC
(In reply to comment #6)
> After restarting plasma-desktop as you've suggested the applet does show in
> the systray. I had also noticed that was the case when logging out and back
> in KDE. 
> 
> However the applet is not working. Doesn't show any available connection,
> and complains about Network Manager not running. Also "enable networking" is
> ticked off, but marking it on doesn't change anything.

If the applet thinks NetworkManager is not running the "enable networking" will never work, they are symptoms of the same problem. For some reason neither the applet nor the kded module can contact NetworkManager. Which Plasma version are you using? You can see the version in "Manage Connections" -> "Other"
Comment 8 Jorge Adriano 2012-06-08 19:22:42 UTC
Version 0.9.0.2 (nm09 20120523)
Comment 9 Lamarque V. Souza 2012-06-08 20:42:57 UTC
Well, the only thing I can think of that could this problem is NetworkManager refusing to authenticate the kded module and the plasmoid (maybe a problem with polkit and/or consolekit). This looks like a problem specific to systemd. I do not use systemd, so I cannot reproduce it here. Try looking into OpenSuse's bugzilla and see if it is a known problem there.
Comment 10 Jorge Adriano 2012-06-08 20:46:19 UTC
OK thank you, I will do that.
Comment 11 Michi 2012-06-11 19:53:24 UTC
Hi,

the problem is ConsoleKit. NM is trying to get its information via the dbus interface of ConsoleKit which has been dropped, at least by distributions that are now using systemd. systemd provides logind which now has taken over the job at question.
Comment 12 Lamarque V. Souza 2012-06-17 15:56:20 UTC
Manullay restarting NetworkManager when this problem happens seems to workaround the problem in Fedora: https://bugzilla.redhat.com/show_bug.cgi?id=826847
Comment 13 Michi 2012-06-19 14:42:54 UTC
(In reply to comment #12)
> Manullay restarting NetworkManager when this problem happens seems to
> workaround the problem in Fedora:
> https://bugzilla.redhat.com/show_bug.cgi?id=826847

Lamarque, have you looked into the dbus interface yet? It's on the system bus under org.freedesktop.login1
Comment 14 Lamarque V. Souza 2012-06-19 14:54:58 UTC
I do not use systemd.
Comment 15 Michi 2012-06-19 16:10:57 UTC
(In reply to comment #14)
> I do not use systemd.

And who of the maintainers does?

Here is the dbus interface that I think is relevant:
http://cgit.freedesktop.org/systemd/systemd/tree/src/login/org.freedesktop.login1.conf
Comment 16 Lamarque V. Souza 2012-06-19 16:22:17 UTC
I am the only maintainer and usualy only me fixes bugs in Plasma NM. Anyway, Plasma NM does not use polkit or consolekit directly (that is the same for nm-applet). Only NetworkManager needs to talk to polkit/consolekit, if systemd changed that than there is nothing I can do for now (I am not going to install systemd just because of that).
Comment 17 Michi 2012-06-19 16:36:59 UTC
(In reply to comment #16)
and what NM interface is plasma NM using that does not provide the proper information? Where would I have to poke the NM guys to look into?

thx Michi
Comment 18 Lamarque V. Souza 2012-06-19 17:17:00 UTC
Plasma NM prints that "NetworkManager is not running" message when the NetworkManager version is empty (qdbus --system org.freedesktop.NetworkManager  /org/freedesktop/NetworkManager org.freedesktop.NetworkManager.Version == ""). The Solid NM backend retrieves the version when it is loading, so if NetworkManager is already running when Plasma NM starts then it should get the version string without problems.

What does the command below return?

solid-network query status
Comment 19 Michi 2012-06-19 18:13:01 UTC
(In reply to comment #18)
> Plasma NM prints that "NetworkManager is not running" message when the
> NetworkManager version is empty (qdbus --system
> org.freedesktop.NetworkManager  /org/freedesktop/NetworkManager
> org.freedesktop.NetworkManager.Version == ""). The Solid NM backend
> retrieves the version when it is loading, so if NetworkManager is already
> running when Plasma NM starts then it should get the version string without
> problems.
> 
> What does the command below return?
> 
> solid-network query status

networking: is not enabled
Comment 20 Lamarque V. Souza 2012-06-19 18:23:16 UTC
Run the program kdebugdialog, search for the string "solid", enable all checkboxes that will appear, click on the Ok Button, repeat the command "solid-network query status" and paste the return text here.
Comment 21 Michi 2012-06-19 19:06:35 UTC
(In reply to comment #20)

solid-network(4980)/kdecore (KSycoca) KSycocaPrivate::openDatabase: Trying to open ksycoca from "/home/XXX/ksycoca4"
solid-network(4980)/Solid (NetworkManager) NMNetworkManagerPrivate::NMNetworkManagerPrivate: "org.freedesktop.NetworkManager"
solid-network(4980)/Solid (NetworkManager) NMNetworkManager::NMNetworkManager: Error getting device list:  "org.freedesktop.DBus.Error.AccessDenied" :  "Rejected send message, 2 matched rules; type="method_call", sender=":1.62" (uid=1000 pid=4980 comm="solid-network query status ") interface="org.freedesktop.NetworkManager" member="GetDevices" error name="(unset)" requested_reply="0" destination="org.freedesktop.NetworkManager" (uid=0 pid=1043 comm="/usr/sbin/NetworkManager --no-daemon ")"
solid-network(4980)/Solid (NetworkManager) NMNetworkManager::NMNetworkManager: Active connections:
solid-network(4980) Solid::Control::ManagerBasePrivate::loadBackend: Backend loaded:  "Fake NetworkManager 0.9"
networking: is not enabled
Comment 22 Lamarque V. Souza 2012-06-19 19:24:59 UTC
NetworkManager is indeed denying access to Plasma NM.

Probably your /etc/dbus-1/system.d/NetworkManager.conf is not configured to allow sending calls to org.freedesktop.NetworkManager interface. With consolekit you would need to add something like that to that file:

<policy at_console="true">
<allow send_destination="org.freedesktop.NetworkManager"
                       send_interface="org.freedesktop.NetworkManager"/>
... # there are other interfaces that also must grant access to programs running at_console.
</policy>

With logind there should be something like that to allow Plasma NM to use NetworkManager.
Comment 23 Michi 2012-06-19 19:37:40 UTC
(In reply to comment #22)
I think my dbus configuration is correct. I rather think that the "Active Console" state is not recognized since that is in fact what CK was about.

Thanks for your inspiration, and I think I know how to proceed from here.
Comment 24 Jorge Adriano 2012-06-21 17:13:17 UTC
I've updated to 4.9 Beta 2 (OpenSUSE Unstable, Version  : 4.8.90_20120617) 
After rebooting, everything seems to be working fine again.
Comment 25 Lamarque V. Souza 2012-06-22 22:27:54 UTC
Adding some usefull information for those with this problem: http://forums.gentoo.org/viewtopic-t-924004-highlight-networkmanagement.html

The problem is not in Plasma NM, so this bug is still a downstream bug.
Comment 26 Lamarque V. Souza 2012-07-03 12:40:26 UTC
Some more info about a similar bug: https://bugs.gentoo.org/show_bug.cgi?id=421577