Bug 274116 - Kopete and Konversation do not reconnect automatically using Wicd
Summary: Kopete and Konversation do not reconnect automatically using Wicd
Status: RESOLVED FIXED
Alias: None
Product: solid
Classification: Frameworks and Libraries
Component: networkmanagement (show other bugs)
Version: unspecified
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Will Stephenson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-25 16:21 UTC by Bernhard Beschow
Modified: 2011-08-30 16:45 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In: 4.7.1


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Bernhard Beschow 2011-05-25 16:21:30 UTC
Version:           unspecified (using KDE 4.6.3) 
OS:                Linux

Since both Kopete and Konversation do not reconnect after network loss, and since (IIRC) both rely on Solid for network change events, I'm reporting this bug to Solid.

See also bug 273472 for details regarding Konversation.

Reproducible: Always

Steps to Reproduce:
1) Use Wicd as network backend.
2) Select Wicd as data source in system settings.
3) Start Kopete/Konversation.
4) Drop and bring back network connection.


Actual Results:  
Kopete and Konversation don't reconnect automatically after the networks is back.

Expected Results:  
Kopete and Konversation should get signalled when the network is back.

I have selected Wicd as the data backend in system settings.
Comment 1 Médéric Boquien 2011-08-29 21:57:30 UTC
I can confirm this bug with KDE 4.7.0. It seems to affect Akonadi too which does not put the SMTP backend online for instance.
Comment 2 Manuel Nickschas 2011-08-29 22:10:09 UTC
Also is broken with the nm09 backend, confirmed in KDE master as of a week ago.
Comment 3 Lamarque V. Souza 2011-08-30 00:06:22 UTC
The nm09 backend works with NetworkManager only, it has nothing to do with wicd. When using wicd you must change the Solid's backend to wicd in systemsettings -> Information Sources. Have you all tried doing that?
Comment 4 Médéric Boquien 2011-08-30 00:09:13 UTC
Yes. NM is not even installed here and wicd is the selected solid backend.
Comment 5 Lamarque V. Souza 2011-08-30 02:00:19 UTC
I have found the cause of the problem. Kded's networkstatus module listen to NetworkManager's state changes only and ignores Wicd's state changes. See file kde-runtime/solid-networkstatus/kded/networkmanagerstatus.cpp.

I am not sure how to handle this problem. Usually all KDE's programs should use solid's network backends to talk to NetworkManager and Wicd. But I guess kde-runtime is compiled before kde-workspace, so if I changed kded's networkstatus module to use solid's network backends I would add a dependency that could have side effects. At the edge of 4.7.1 tag date (two days from now) I think the best approach is postpone this change and think about a better way to handle this problem for 4.7.2.
Comment 6 Médéric Boquien 2011-08-30 02:15:49 UTC
Hi. Thanks a lot for having investigated this. I will ping you again after 4.7.1 is tagged to make sure this is solved for 4.7.2.
Comment 7 Manuel Nickschas 2011-08-30 05:56:08 UTC
Ah, you probably misunderstood my comment: I am using NetworkManager 0.9 with Solid (no Wicd involved), and I too have the problem that applications are not notified when I go online.

So your description of the cause of the bug doesn't seem to match the symptoms I see.
Comment 8 Lamarque V. Souza 2011-08-30 16:29:47 UTC
Fixed in commit http://commits.kde.org/kde-runtime/3bb1ef2cc8ffed0b927811bf923c90534c709bee

Konversation reconnects with both NetworkManager and Wicd now. I will close this bug as fixed.

Kopete still does not reconnect when system goes online (with both NetworkManager and Wicd). Please follow this entry about this particular Kopete's bug: http://bugs.kde.org/210734
Comment 9 Médéric Boquien 2011-08-30 16:32:24 UTC
Thanks a lot! I will test that as soon as i put my hand on 4.7.1 packages, in ~1 week i assume.
Comment 10 Lamarque V. Souza 2011-08-30 16:45:43 UTC
(In reply to comment #9)
> Thanks a lot! I will test that as soon as i put my hand on 4.7.1 packages, in
> ~1 week i assume.

Exactly one week according to the release schedule: http://techbase.kde.org/Schedules/KDE4/4.7_Release_Schedule