KNetworkManager problem after console login

[nick_battle]

Originally Posted by Akoellh

It should, but I just tested it and it doesn't, no interfaces are available in knetworkmanager although NWM, dbus and hal are running.

Thanks very much for confirming this isn't just me!

Do you think it's worth raising a bug, or is it too obscure to really matter? Very low priority perhaps?

Cheers,
-nick

[lwfinger]

nick battle wrote:
> Akoellh;1962453 Wrote:
>> It should, but I just tested it and it doesn't, no interfaces are
>> available in knetworkmanager although NWM, dbus and hal are running.
>
> Thanks very much for confirming this isn't just me!
>
> Do you think it's worth raising a bug, or is it too obscure to really
> matter? Very low priority perhaps?

There is a bug already posted - #486267.

In fact, we think we have the reason that some systems fail, and others work the
way they should.

Please check your system for the presence of a directory named

/var/run/dbus/at_console/root

If it exists, does the command

sudo rm -rf /var/run/dbus/at_console/root

make NM work correctly again?

Larry

[nick_battle]

Originally Posted by lwfinger

Please check your system for the presence of a directory named

/var/run/dbus/at_console/root

Hi Larry. Unfortunately that directory doesn't exist. I just have two sub-directories in /var/run/dbus/at_console:

drwxr-xr-x 2 root root 4096 2009-03-14 11:07 linux
drwxr-xr-x 2 root root 4096 2009-03-24 17:17 nick

The linux sub-directory is empty (created at install by the look of the date); nick has a sub-directory called Session1, but that is also empty.

Cheers,
-nick

[lwfinger]

nick battle wrote:
> lwfinger;1962486 Wrote:
>> Please check your system for the presence of a directory named
>>
>> /var/run/dbus/at_console/root
>>
>
> Hi Larry. Unfortunately that directory doesn't exist. I just have two
> sub-directories in /var/run/dbus/at_console:
>
> drwxr-xr-x 2 root root 4096 2009-03-14 11:07 linux
> drwxr-xr-x 2 root root 4096 2009-03-24 17:17 nick
>
> The linux sub-directory is empty (created at install by the look of the
> date); nick has a sub-directory called Session1, but that is also
> empty.

Does deleting the linux directory help? It should not be there.

[nick_battle]

Originally Posted by lwfinger

Does deleting the linux directory help? It should not be there.

I'm afraid not.

Cheers,
-nick

[leszekr]

I have very simmilar thing but does not depend on console login...

My knetworkmanager does not work all the time... shows available networks but when i click on one of them "nothing" happens, I've tried cnetworkmanager and it complains about not being able to connect to networkmanager because another process is "using it". quote form console:
cnetworkmanager 0.8 - Command Line Interface for NetworkManager
Could not provide settings service, another applet is running (pid 4095)

this pid 4095 happens to be kded4 process. if i kill and restart kded4 and then restart knetworkmanger or cnetworkmanager everything works ok... it must be some bug in kded4.... or settings or something... i don't know how/where to dig to find out more...

Thanks

[wdaniau]

Hi all,

here's the solution of the problem.

The d-bus configuration of networkmanager is so that the user must be considered to be "at console" to be able to use it. The misunderstanding is that "at console" means in fact "sitting in front the computer" and this is something which is set by the graphical login but not by a login at the "console". This is handle by the ConsoleKit package.

Just add the following line to your /etc/pam.d/login file :

session optional pam_ck_connector.so

after that when login at the console you will be considered to be "at console" by dbus, then if you startx and launch knetwormanager it will work.

Enjoy.