Mageia forum

Before you jump in here telling me to read, I have! kdebase4-runtime-4.8.2-3.mga2 is installed from the initial install (DVD).

So this https://bugs.mageia.org/show_bug.cgi?id=5840 has nothing to do with the problem I have.

I have not installed Mageia2 on my desktop yet and this problem in on my laptop. If I boot and just go I am ok. Once I close the lid and open it Kmail always says "working offline". HItting work online fixes it and it checks mail. Hit check mail again, and it says offline again. Also Kopete does not see the resumed connection and does not sign you back in, so it appears other programs cannot see the connection.

This is very annoying. Also, I check marked watched interfaces, wireless, and it will not hold that setting.

Anyone have a solution?

Just to make that clear, you did a fresh install, no upgrade? And did you use an old /home?

Hey Dok,

It was a fresh install. Didn't save Mandriva 2010 /home. I moved everything to a Win7 partition and wiped it clean. I've been going nuts on this. When set to auto check mail, it errors. Kopte don't see the network on resume and checking watched interface does not stay checked, but reverts to "Auto".

The network connects at boot faster then 2010 ever did, and my Win7 is slooooow to connect. I usually don't ask unless I've tried my best and I just don't get it. I tried selecting work offline in Kmail, and then selecting work online hoping this would toggle something.

Could you gave me the result of

qdbus org.kde.kded /modules/networkstatus org.kde.Solid.Networking.Client.Status

when the problem occurs ?

It might be related to ntrack as mentionned in mga #5840 & https://bugs.kde.org/show_bug.cgi?id=294441.
If it's still happening i guess i'll disable ntrack support for next kde update

knetwork-manager is not installed. Connection was checked to allow interface to be controlled by network manager. I installed NM and it seemed to drag the system down bigtime. It was using 30-40 CPU...mouse freezing....

I put it back like it was.

The output you ask for:

[root@localhost john]# qdbus org.kde.kded /modules/networkstatus org.kde.Solid.Networking.Client.Status

Could not connect to D-Bus server: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

System Settings>Information Sources is set to wicd...Solid blank....Modem manager is set to modem manager 0.4.

yankee495 wrote:[root@localhost john]# qdbus org.kde.kded /modules/networkstatus org.kde.Solid.Networking.Client.Status

Could not connect to D-Bus server: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

You should have run that as user, as your KDE session also runs as user.

[john@localhost ~]$ qdbus org.kde.kded /modules/networkstatus org.kde.Solid.Networking.Client.Status

4

[john@localhost ~]$

Everytime I mess with it I loose my net. wicd was not installed and neither was knetworkmanager durring the initial install. Frowm what I'm reading you need one or the other.

Honestly, I've never dealt with either. It just worked. I installed wicd and get an error at login:

Could not connect to wicd's D-Bus interface. Check the wicd log for error messages.

you does not need wicd or nm to get it working.
Here the network seems to be functionnal, so kmail should not be offline.

& btw it's strange that you're able to install wicd, i thought it has been removed from mga 2

Now: qdbus org.kde.kded /modules/networkstatus org.kde.Solid.Networking.Client.Status

Gives me: 1

I can confirm this behaviour. I don't think the current version of kdebase4-runtime has fixed the issue. The Akonadi connection to my Google calendar and tasks also thinks that it's offline after a suspend.

I work around the KMail issue by explicitly telling it to go into offline mode and then switching back to working online. I work around the Akonadi issue by restarting Akonadi. But there seems to be an issue with the detection of the wireless network connection after a suspend.

So probably the bug linked in the original report needs reopening ...

Hey Dok,

I don't know how, but my realtek 8192ce driver got screwed up in all this mess, so I plugged in a USB stick I got at newegg on sale for $10 with free S&H because everyone said it was plug and play in Linux. It is, works great. It is reported as rtl8187.

Now I have to figure out the 8192. Thought I had that. I can get it to show up, and load a module with insmod...but it won't connect...off reading.

yankee495 wrote:Now: qdbus org.kde.kded /modules/networkstatus org.kde.Solid.Networking.Client.Status

Gives me: 1

oki.

I pushed a new kde-runtime without ntrack support in core_testing.
Could you test it once build is done (& package available on mirrors) ?

A GOOD WORK AROUND!

I've spent a lot of time on this, learned a lot I guess. I can tell you all about what don't fix it. So here is a nice little work around that works pretty good.

Install KNemo and go to notifications and tell it to run this script.

#!/bin/bash
sleep 5
qdbus org.kde.kded /modules/networkstatus org.kde.Solid.Networking.setNetworkStatus "ntrack" 4


The sleep 5 seconds gives it time to get connected and then it triggers the "4" for the rest of the system. Kopete connects and Kmail works.

I haven't seen a down side. Simple, anyone can do it and easily removable when a true fix comes along.

@Yankee
Could you please test the kdebase4-runtime (4.8.2-3.1) package (so upgrade from core/updates_testing) which came without ntrack support ?

mikala wrote:@Yankee
Could you please test the kdebase4-runtime (4.8.2-3.1) package (so upgrade from core/updates_testing) which came without ntrack support ?

List of updates packages :
for x86_64

Code: Select all

kdebase4-runtime-4.8.2-3.1.mga2.x86_64.rpm   
kdebase4-runtime-devel-4.8.2-3.1.mga2.x86_64.rpm     
kdebase4-runtime-handbook-4.8.2-3.1.mga2.noarch.rpm   
kwallet-daemon-4.8.2-3.1.mga2.x86_64.rpm
lib64kwalletbackend4-4.8.2-3.1.mga2.x86_64.rpm     
lib64molletnetwork4-4.8.2-3.1.mga2.x86_64.rpm       
lib64nepomukdatamanagement4-4.8.2-3.1.mga2.x86_64.rpm
lib64nepomuksync4-4.8.2-3.1.mga2.x86_64.rpm
nepomuk-4.8.2-3.1.mga2.x86_64.rpm   

for i586

Code: Select all

kdebase4-runtime-4.8.2-3.1.mga2.i586.rpm   
kdebase4-runtime-devel-4.8.2-3.1.mga2.i586.rpm     
kdebase4-runtime-handbook-4.8.2-3.1.mga2.noarch.rpm   
kwallet-daemon-4.8.2-3.1.mga2.i586.rpm
lib64kwalletbackend4-4.8.2-3.1.mga2.i586.rpm     
lib64molletnetwork4-4.8.2-3.1.mga2.i586.rpm       
lib64nepomukdatamanagement4-4.8.2-3.1.mga2.i586.rpm
lib64nepomuksync4-4.8.2-3.1.mga2.i586.rpm
nepomuk-4.8.2-3.1.mga2.i586.rpm     

What does it use if not ntrack? I've been using Mandriva for years and just never had to worry about that. Akonadi was another story. Powerful stuff, when it works. I get the idea of Ntrack, but something is wrong. I worked on it all day yesterday. For such a basic feature of just being connected to be broken is unbelievable.

KDE has bugs that affect Compiz too. I understand Ntrack is compiled as a dependency of KDE or vise-versa. So these have no Ntrack? I also have Windows on this computer and don't want to screw that up. My 2010.2 ran so good I almost didn't install Mageia.

So I would select the packages above from /core/updates_testing?

Then just hit apply...and reboot?

I enabled /core/updates testing and I don't see anything when I go to update.

It won't let me check mark updates, just enable.

yankee495 wrote:What does it use if not ntrack?

ntrack support seems to be broken (either in kde-runtime since 4.8.x since it was working before in 4.7.x when it was introduced or eventually directly in ntrack by upstream change) so it's better to remove the support at all instead of providing a broken system.
ntrack support was not use/enable in kde-runtime for KDE 4.6.x (so neither in mga 1 or eventually mandriva 2011).

I found them on ftp server. Got them with kget. Why do they not show up in update list or anywhere?

Are you a Mageia developer?

They do not sow in updates because the media (core/updates_testing) is disabled by default & is available for testing updates only. so you need to enable it/resfresh it to be able to get package from it.
For the second question i'm part of the mageia kde's team.