Hello, Could you please test & validate this update of kdebase4-runtime? Initial problem: For people using kmail/korganizer with an akonadi ressource *and* not using networkmanager it seems that akonadi are *wrongly* notified of a non working network via solid due to some bug (either in kde-runtime or in ntrack) I simply rebuild the package without the ntrack support which seems to prevent this issue again according to this thread : https://forums.mageia.org/en/viewtopic.php?f=7&t=2586 So in summary how to reproduce : - install a kde mageia & add for example an imap account on kmail - suspend to disk/ram - resume your session - launch kmail & noticed that the imap ressource are offline. additionnaly you can use in konsole (as normal user) qdbus org.kde.kded /modules/networkstatus org.kde.Solid.Networking.Client.Status to get the solid network status which should be 1 (if not working) After installing the update package kmail should be functionnal after a suspend to disk/ram Packages list : For x86_64 : 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: 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.rp Update advisory: « After a suspend to disk/ram network connection was wrongly set as not working, this update fix this issue allowing kde applications (such as kmail ,kopete, korganizer) to correctly notice network connection. » Regards,
It solved all the offline troubles I had with kmail. After installing these packages, everything seems to work perfectly. Testing on Mageia 2, 64-bits.
CC: (none) => olivier.delaune
It solved all my kmail offline problems too, on Mageia 2, 64 bits. I, however, am on a wired connection and do never use suspend. I had the problem after I shut down and restart my connection. After reconnect, Kmail would insist on me being offline. This patch solved the issue. Regards Johnny :o)
CC: (none) => j_e_n_pub
Blocks: (none) => 5895
that does look like my issue... i had closed kontact, stopped akonadi, and logged out and back in again, and that worked as a workaround.
CC: (none) => alien
Confirmed the bug i586. Installing update candidates now. Thanks John for the list.
Since confirming the bug I'm suffering the same symptoms as AL13N in https://bugs.mageia.org/show_bug.cgi?id=5895#c7 It appears stuck in offline mode. I can switch it back to online mode but next time kmail is started it still complains of being in offline mode. When I try to send a mail after syncing the imap folders it says the mail dispatcher is offline and click yes to put it back online. It puts the email in the local outbox though where it stays without being sent until i right click the outbox and tell it to send queued messages. The update does not appear to fix the problem here.
did you do: 1. akonadictl stop 2. log out 3. log back in?
I even rebooted
(In reply to comment #5) > Since confirming the bug I'm suffering the same symptoms as AL13N in > > https://bugs.mageia.org/show_bug.cgi?id=5895#c7 > > It appears stuck in offline mode. I can switch it back to online mode but next > time kmail is started it still complains of being in offline mode. > > When I try to send a mail after syncing the imap folders it says the mail > dispatcher is offline and click yes to put it back online. It puts the email in > the local outbox though where it stays without being sent until i right click > the outbox and tell it to send queued messages. > > The update does not appear to fix the problem here. The mail agent dispatcher issue is another problem & not related to this bug fix. You can restart it using akonadiconsole. You should also check ~/.config/akonadi/agent_config_akonadi_maildispatcher_agent to ensure that it's set to be online & not offline. There's a bug reported upstream against this issue if i'm not wrong.
CC: (none) => balcaen.john
Does that also explain being in offline mode when it is started John? I'll check the contents of that file, thanks.
@Claire probably.
Testing x86_64 Before ------ Before suspend.. $ qdbus org.kde.kded /modules/networkstatus org.kde.Solid.Networking.Client.Status 4 After suspend... $ qdbus org.kde.kded /modules/networkstatus org.kde.Solid.Networking.Client.Status 1
After ----- Installed updates and rebooted Before suspend.. $ qdbus org.kde.kded /modules/networkstatus org.kde.Solid.Networking.Client.Status 1 After suspend.. $ qdbus org.kde.kded /modules/networkstatus org.kde.Solid.Networking.Client.Status 1 If 1 means this is not working then it doesn't seem to be working John.
Unfortunately kmail crashes on startup with a message 'Failed to fetch resource collection'
Created a new user and logged in. Kmail refuses to switch to online mode, although after clicking Work online and looking in the file menu it says Work offline, which means it thinks its online and offline at the same time. $ qdbus org.kde.kded /modules/networkstatus org.kde.Solid.Networking.Client.Status 1 Something still seems wrong here John. Others say it has corrected their kmail issues though so perhaps this is a different issue to the one this bug is fixing. WDYT?
CC: (none) => mailinglistsduraph
i can test this bug, i encounter this on my wife's computer.
CC: (none) => nicolas.lecureuil
Ok so just a summary regarding our irc discussion : - how to test the bug availabilty ? after a suspend to disk/ram the result of qdbus org.kde.kded /modules/networkstatus org.kde.Solid.Networking.Client.Status should be 1 if it's 4 you're not affected (should be the case if you're using networkmanager) - once update is installed the result of qdbus org.kde.kded /modules/networkstatus org.kde.Solid.Networking.Client.Status should be 4 after a suspend to disk/ram It seems that when nm is installed but *not* activated ( it's pulled by gnome here)the result is 1 which is a *normal* result since nm is installed & does not detect the nm. You can check networkmanager status using in console : nmcli nm So you can « fix » it either by removing networkmanager ( in order to avoid removing half of gnome you can use rpm -e --nodeps) or by using it really aka it should managed network connection. A « more » correct fix should probably to removed the nm support in kde-runtime however since 4.8.4 is already available on svn that would mean to either : - reverse the commit to go back to 4.8.2 & pushed a new candidate package - skip this update candidate & push 4.8.4 without the nm support (easier :p ) We can also push this package (once the test is done *without* nm) & provides a more proprer fix for 4.8.4. Regards,
This bug has meant I have been almost unable to send email (including mail related to Mageia) since I upgraded from mga1 to mga2 last weekend. I use my laptop, and suspend twice every work day, resuming on a wireless network which requires manual entry of a WPA2-EAP password, so Kmail would only allow me to send if I subsequently logged out and back in again (although it would happily download IMAP mail, even if it showed the IMAP source was offline). I upgraded to the packages in testing, and I was able to send mail after a resume on the WPA2-EAP network. (I honestly have no need for NM, and 'network detection' is IMHO almost impossible to get right, because the upstream connectivity can have different properties, for a long time I had 3G only at home via my WiFi network, and really didn't want IMAP synchronisation there ... kmail really *must* ensure the *user* can force kmail to do whatever it is trying to auto-detect, or it is ****broken***). BTW., after resume: [bgmilne@tiger ~]$ qdbus org.kde.kded /modules/networkstatus org.kde.Solid.Networking.Client.Status 0 From my experience, I believe this update should be pushed ASAP. Unfortunately, due to the full day I have lost working on getting kmail to work (firstly addressing failed upgrade from kmail1 with *no* information provided on how to address problems, and re-attempt, secondly on trying to send mails), I can't afford much testing besides what I have done so far.
CC: (none) => bgmilne
Thankyou for testing Buchan. We are very short of people in the QA team since the release of Mageia 2 so are having to concentrate on security updates, sadly at the expense of bugfixes like this one. I have been promising John for two weeks now to look at this but so far have not found the time. As several people have conformed it fixes the problem for them I think we should validate, I know John will be pleased as he is waiting to update KDE. If you'd like to help QA or know others who might then please find more info on our wiki pages and come and say Hi. https://wiki.mageia.org/en/QA_Team I'll validate this one now.
Validating Update advisory: « After a suspend to disk/ram network connection was wrongly set as not working, this update fix this issue allowing kde applications (such as kmail ,kopete, korganizer) to correctly notice network connection. » srpm: kdebase4-runtime-4.8.2-3.1.mga2.src.rpm Could sysadmin please push from core/updates_testing to core/updates Thankyou!
Keywords: (none) => validated_updateCC: (none) => sysadmin-bugs
Update pushed: https://wiki.mageia.org/en/Support/Advisories/MGAA-2012-0093
Status: NEW => RESOLVEDCC: (none) => tmbResolution: (none) => FIXED