Bug 6159 - Update for kdebase4-runtime
Summary: Update for kdebase4-runtime
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 2
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: QA Team
QA Contact:
URL: https://bugs.kde.org/show_bug.cgi?id=...
Whiteboard:
Keywords: validated_update
Depends on:
Blocks: 5895
  Show dependency treegraph
 
Reported: 2012-05-29 21:53 CEST by John Balcaen
Modified: 2012-06-30 19:46 CEST (History)
9 users (show)

See Also:
Source RPM: kdebase4-runtime-4.8.2-3.1.mga2.src.rpm
CVE:
Status comment:


Attachments

Description John Balcaen 2012-05-29 21:53:20 CEST
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,
Comment 1 Olivier Delaune 2012-05-30 13:30:28 CEST
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

Comment 2 Delete me 2012-05-31 20:37:09 CEST
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

John Balcaen 2012-06-03 11:36:07 CEST

Blocks: (none) => 5895

Comment 3 AL13N 2012-06-03 14:51:07 CEST
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

Comment 4 claire robinson 2012-06-05 17:59:06 CEST
Confirmed the bug i586. Installing update candidates now.

Thanks John for the list.
Comment 5 claire robinson 2012-06-05 18:22:12 CEST
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.
Comment 6 AL13N 2012-06-05 19:59:19 CEST
did you do:

1. akonadictl stop
2. log out
3. log back in?
Comment 7 claire robinson 2012-06-05 20:03:15 CEST
I even rebooted
Comment 8 John Balcaen 2012-06-05 21:18:59 CEST
(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

Comment 9 claire robinson 2012-06-06 09:33:27 CEST
Does that also explain being in offline mode when it is started John?

I'll check the contents of that file, thanks.
Comment 10 John Balcaen 2012-06-16 13:15:50 CEST
@Claire probably.
Comment 11 claire robinson 2012-06-16 15:28:25 CEST
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
Comment 12 claire robinson 2012-06-16 15:53:54 CEST
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.
Comment 13 claire robinson 2012-06-16 16:02:46 CEST
Unfortunately kmail crashes on startup with a message 'Failed to fetch resource collection'
Comment 14 claire robinson 2012-06-16 16:16:11 CEST
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?
Raphaël Vinet 2012-06-17 20:07:28 CEST

CC: (none) => mailinglistsduraph

Comment 15 Nicolas Lécureuil 2012-06-19 21:11:11 CEST
i can test this bug, i encounter this on my wife's computer.

CC: (none) => nicolas.lecureuil

Comment 16 John Balcaen 2012-06-20 11:57:37 CEST
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,
Comment 17 Buchan Milne 2012-06-29 10:55:49 CEST
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

Comment 18 claire robinson 2012-06-29 11:18:38 CEST
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.
Comment 19 claire robinson 2012-06-29 11:22:34 CEST
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_update
CC: (none) => sysadmin-bugs

Comment 20 Thomas Backlund 2012-06-30 19:46:03 CEST
Update pushed:
https://wiki.mageia.org/en/Support/Advisories/MGAA-2012-0093

Status: NEW => RESOLVED
CC: (none) => tmb
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.