Announcement

Collapse
No announcement yet.

knetworkmanager, kopete and dbus

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    knetworkmanager, kopete and dbus

    hello all,

    yesterday i switched from debian testing to dapper (and i am still happy with it!). So on my fresh install i want to use a wpa encrypted wireless network. Instead of using a wpasupplicant.conf file and a lot of hacking in the console i decided to try knetworkmanager. Great!! This very easy tool is managing my networks perfect (i can switch from wireless to wired etc without typing or thinking).
    But of course (why else would i be here), something is not so perfect.
    When i understood it right, networkmanager sends a signal over dbus, whenever a connection is available. So theoretically kopete and my nice superkaramba-weather-widget should (re)connect when necessary. But they don't! This means that when i boot my computer, networkmanager is slower than kopete and i get a warning that there is no network and have to connect manually.
    Is this a bug and if so, any ideas on which side of the problem? Is this a wannahave feature that does not exist? Or am I making a mistake somewhere?

    Tnx for your answers,

    Martijn

    #2
    Re: knetworkmanager, kopete and dbus

    edit:
    I am sorry, it appears to work after all... but not immediately, kopete connects at a random time after networkmanager did. so... i can live with this, but it is not entirely clean

    Comment

    Working...
    X