Re: knetworkmanager stopped working

2008-10-06 Thread Anton Moiseev
  When I start nm-applet from console, I receive the following error message:
 
  ** (nm-applet:8134): WARNING **: WARN
  applet_dbus_manager_start_service(): Could not acquire the
  NetworkManagerUserSettings service as it is already taken.  Return: 3
 
 
  (nm-applet:8134): GLib-GObject-CRITICAL **: g_object_unref: assertion
  `G_IS_OBJECT (object)' failed

 Was KNetworkManager running at the same time?


Thank's everybody for help, I have solved my problem.

In no way anybody in this list could guess the reason of the issue, but
the guiding questions did help to find it.

The reason of the problem was that I had networkmanager-kde4 plasmoid installed
in my system. Even though I did not have it added to my deskop, it still somehow
prevented knetworkmanager from working normally (and also nm-applet to start).
I have removed the package from the system, and magically, all started to work
- first, I was able to start nm-applet in kde, then I knetworkmanager
again started
to work.



Just for history (if someone is interested or would ever find this
thread while solving
the same problem). I have came to this solution while trying to start
nm-applet under
kde. Initially, when I tried to start it in kde4, I did receive the
above error message,
so for clearance I have tried to start lightweight wm (icewn), did
start nm-applet there
and it worked (though my icewm does not have tray and I could not see the icon,
but there were also no errors in the console output). Then I killed
nm-applet, started
knetworkmanager, started nm-applet and it did show the same error as
described above, so
I understood that knetworkmanager does prevent nm-applet from starting.

But when I tried to repeat the same in KDE4, this did not work - I
killed knetworkmanager,
then I even removed it from the system and rebooted - nm-applet still
could not start in KDE4.
And then I have remembered about networkmanager kde4 plasmoid - that
was the last thing is
the system which  could do lock resources from nm-applet, as
knetworkmanager (kde3) did.
I have removed this package from system and all works now.

Thank's again
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: knetworkmanager stopped working

2008-10-04 Thread Helmut Schaa
Am Freitag, 3. Oktober 2008 schrieb Anton Moiseev:
 The thing is that I have completely removed all updated packages and 
 reinstalled
 NetworkManager and NetworkManager-kde from OpenSUSE installation DVD,
 and those versions did work together after initial system setup.
 I have also tried to remove all configuration settings of knetworkmanager
 (~/.kde/share/apps/knetworkmanagerrc) from my home directory, so for me I
 have rather closely reproduced the situation in which knetworkmanager did work
 in the past, but now it does not. So I must have missed something here
 - probably
 this could be some DBUS update or config file which I have missed.

Strange. Which version of KDE4 do you use?

 I will try to write to knetworkmanager mailing list provided above.
 
 
 
 
 As temporary workaround I would ask another question - is it possible to run
 gnome network manager (nm-applet) under kde4?

Yes, should be possible.

 When I start nm-applet from console, I receive the following error message:
 
 ** (nm-applet:8134): WARNING **: WARN
 applet_dbus_manager_start_service(): Could not acquire the
 NetworkManagerUserSettings service as it is already taken.  Return: 3
 
 
 (nm-applet:8134): GLib-GObject-CRITICAL **: g_object_unref: assertion
 `G_IS_OBJECT (object)' failed

Was KNetworkManager running at the same time?

Helmut
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: knetworkmanager stopped working

2008-10-03 Thread Dan Williams
On Thu, 2008-10-02 at 17:07 +0200, Helmut Schaa wrote:
 Hi,
 
 Am Donnerstag, 2. Oktober 2008 schrieb Anton Moiseev:
  Oct  2 18:39:41 benderamp-hp NetworkManager: WARN
  wait_for_connection_expired(): Connection (2)
  /org/freedesktop/NetworkManagerSettings/Connection/1 failed to
  activate (timeout): (0) Connection was not provided by any settings
  service
 
 Looks like a configuration mismatch between KNM and NM to me. You could
 try to recreate your connections.

It means that something (knm probably) told NetworkManager to activate a
connection, but that thing (knm probably) didn't actually provide that
connection over D-Bus.

Dan


___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: knetworkmanager stopped working

2008-10-03 Thread Dan Williams
On Fri, 2008-10-03 at 00:20 +0200, Helmut Schaa wrote:
 Am Donnerstag, 2. Oktober 2008 schrieb Dan Williams:
  On Thu, 2008-10-02 at 17:07 +0200, Helmut Schaa wrote:
   Hi,
   
   Am Donnerstag, 2. Oktober 2008 schrieb Anton Moiseev:
Oct  2 18:39:41 benderamp-hp NetworkManager: WARN
wait_for_connection_expired(): Connection (2)
/org/freedesktop/NetworkManagerSettings/Connection/1 failed to
activate (timeout): (0) Connection was not provided by any settings
service
   
   Looks like a configuration mismatch between KNM and NM to me. You could
   try to recreate your connections.
  
  It means that something (knm probably) told NetworkManager to activate a
  connection, but that thing (knm probably) didn't actually provide that
  connection over D-Bus.
 
 Or NM rejected the connection because some setting's properties changed
 (e.g. NM property name != KNM property name) due to a NM or KNM update. That's
 what I observed in the majority of cases.

Ah, understood.  I don't think any of the settings have changed for more
than a month now...  vpn data/secrets split should have been the last
one.

Dan


___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: knetworkmanager stopped working

2008-10-03 Thread Anton Moiseev
   Oct  2 18:39:41 benderamp-hp NetworkManager: WARN
   wait_for_connection_expired(): Connection (2)
   /org/freedesktop/NetworkManagerSettings/Connection/1 failed to
   activate (timeout): (0) Connection was not provided by any settings
   service
 
  Looks like a configuration mismatch between KNM and NM to me. You could
  try to recreate your connections.

 It means that something (knm probably) told NetworkManager to activate a
 connection, but that thing (knm probably) didn't actually provide that
 connection over D-Bus.

 Or NM rejected the connection because some setting's properties changed
 (e.g. NM property name != KNM property name) due to a NM or KNM update. That's
 what I observed in the majority of cases.

 Helmut


The thing is that I have completely removed all updated packages and reinstalled
NetworkManager and NetworkManager-kde from OpenSUSE installation DVD,
and those versions did work together after initial system setup.
I have also tried to remove all configuration settings of knetworkmanager
(~/.kde/share/apps/knetworkmanagerrc) from my home directory, so for me I
have rather closely reproduced the situation in which knetworkmanager did work
in the past, but now it does not. So I must have missed something here
- probably
this could be some DBUS update or config file which I have missed.

I will try to write to knetworkmanager mailing list provided above.




As temporary workaround I would ask another question - is it possible to run
gnome network manager (nm-applet) under kde4? if it is possible, then how.

When I start nm-applet from console, I receive the following error message:

** (nm-applet:8134): WARNING **: WARN
applet_dbus_manager_start_service(): Could not acquire the
NetworkManagerUserSettings service as it is already taken.  Return: 3


(nm-applet:8134): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT (object)' failed


I have wireless network, protected with password, which is stored in
gnome keyring,
if that makes sense.

Thank's to all for help
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: knetworkmanager stopped working

2008-10-02 Thread Helmut Schaa
Am Donnerstag, 2. Oktober 2008 schrieb Anton Moiseev:
 I have posted this problem to opensuse mailing list, and then to the
 kde-linux mailing list, but there were no response, and this list
 seems to be the most relevant.

KNetworkManager list:
https://mail.kde.org/mailman/listinfo/kde-networkmanager

 I have Opensuse 11 with kde4 and knetworkmanager 0.7r826733 from
 opensuse repo and knetworkmanager stopped working for me.

I'm pretty sure you've updated NM and did not update KNM or vice versa.
What does the NM log (/var/log/NetworkManager) tells you?

Helmut
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: knetworkmanager stopped working

2008-10-02 Thread Helmut Schaa
Hi,

Am Donnerstag, 2. Oktober 2008 schrieb Anton Moiseev:
 Oct  2 18:39:41 benderamp-hp NetworkManager: WARN
 wait_for_connection_expired(): Connection (2)
 /org/freedesktop/NetworkManagerSettings/Connection/1 failed to
 activate (timeout): (0) Connection was not provided by any settings
 service

Looks like a configuration mismatch between KNM and NM to me. You could
try to recreate your connections.

Helmut
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


knetworkmanager stopped working

2008-10-01 Thread Anton Moiseev
Hello,

I have posted this problem to opensuse mailing list, and then to the
kde-linux mailing list, but there were no response, and this list
seems to be the most relevant.

I have Opensuse 11 with kde4 and knetworkmanager 0.7r826733 from
opensuse repo and knetworkmanager stopped working for me.

--
Part1

I had to switch off the notebook in a bad way - by holding the power
key. After rebooting knetworkmanager
stopped connecting to wireless networks. I can see the network list,
but when I click on the network name
the tray icon just stays gray and nothing happens. It even does not
try to do anything - previously the tray icon changed to blue gear
at least for a half of second, even if the connection could not
be established - now it just remains gray all the time.

I did try to remove knetworkmanager config file from ~/.kde dir, tried
to login as another user, tried to remove
NetworkManager-kde package and install it again - nothing helped here.

I have installed gnome and tried its native networkmanaged applet -
this one did work. Knetworkmanager still does not.

--
Part2

Ok, I have started kneworkmanager from console. When I select network name
in the menu, I can see the message there:

Activate Connection
/org/freedesktop/NetworkManagerSettings/Connection/7 on Device
/org/freedesktop/Hal/devices/net_00_1f_3c_36_58_77

And nothing else happens - neither in the console, no in UI. So the gui does
react on my connection request, but somehow its HAL cooperation is broken.
Any ideas where to go further?

---
Part 3
As soon as nobody suggested a simple solution, I have decided to go deeper

I have compiled networkmanager from source code (I have taken the opensuse
src.rpm as svn version did not compile). Then I have found a file with
Activate Connection string - that was knetworkmanager-wireless_menuitem.cpp

This is this part of code:


void WirelessNetworkItem::slotActivate()
{
   NMProxy* nm = NMProxy::getInstance();
   int id;
   QDBusError err;
   if (_dev  nm)
   {
   if ( _conn )
   {
   printf(Activate Connection %s on Device %s\n,
_conn-getObjectPath().data(), _dev-getObjectPath().ascii());
   if (!nm-ActivateConnectionAsync(id,
NM_DBUS_SERVICE_USER_SETTINGS,
_conn-getObjectPath(),
QDBusObjectPath(QCString(_dev-getObjectPath())),
_conn-getObjectPath(), err)) {
   printf(ActivateDevice failed\n);
   } else {
 printf(Device activated!!! \n);
   }
...
---

Here nm-ActivateConnectionAsync(..) the main call - if it returns false
(device is not activated), the ActivateDevice failed message would be printed;
if it would return true (device is activated), nothing would be
printed by default,
but I have added another printf(Device activated!!! \n);, and in my case
I could see this message in the console output when tried to activate network
with knetworkmanager menu.

But even though it prints OK, the network is actually not activated - the
request went somewhere inside DBUS, the response is true, but
things still do not work.

So, it seems that the problem lays further at least somewhere at the DBUS level.
I have installed kdbus and could see

/org/freedesktop/NetworkManagerSettings and
/org/freedesktop/Hal/devices

items there, but I do not know what to do further with them.
--

Please help, I just want my internet in kde4 back, I would appreciate any help,
probably the solution is very simple and does not require exploring the source
code and debugging with DBUS

Thank's
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list