[Bug 969675] New: Kmail pop filter amnesia and an apparent race condition present.
http://bugzilla.opensuse.org/show_bug.cgi?id=969675 Bug ID: 969675 Summary: Kmail pop filter amnesia and an apparent race condition present. Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: x86-64 OS: openSUSE 42.1 Status: NEW Severity: Major Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs@opensuse.org Reporter: stakanov@freenet.de QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- KDE 4.4.17 KMAIL 4.14.10 Plasma 5: 5.5.4 QT 5.5.1 interface language Italian. This is a default installation of Leap 42.1. As Kmail in the default with Leap is held (rightly I would say) at version 4.14.10 this applies KDE 4 and Kmail running on it. However in the thread I did open in opensuse-KDE mailinglist another user complains that this is also true in TW for a pure plasma 5, framework 5, kmail5 installation with the very same symptoms. In my case: First aspect: when opening the user A, and setting Kontact to automatic start up, and if you put: check mail on start up, or if you click on check for mail right after the program started, filter will fail. The mail will be retrieved, it will be all put into the default folder of the respective account. If you select the folder and go into the menu and choose: folder: apply all filters to that folders, then the mail is filtered and distributed correctly. But, new mail will again not be filtered at all. This will apply to all accounts present. Now, if you logout and login again of that user. Then the filers will work now, no matter if you do respect the wait period or not. That is why I speak about a race condition of something starting up and not being ready when requesting new mail. Second problem: this issue is not without consequences on the filter listings. You will be prompted sooner nor later (normally on every start-up by another filter) with a window telling that for the filter X Kmail does not find the account. You are asked to choose ... but the list is empty. Now, if you click on the first line of the empty window you can actually change the grayed out status of the OK button to normal. And press O.K. and for now you are done. In about 30% (estimated) of this events you loose the filter in question. It is deleted of the filter lists and does not exist any more. If you click on cancel when this window appears you DO loose that filter immediately. Sometimes two filer are hit, so two separate windows to confirm pop up one after another. With the time you will loose at least half of all your filter. You may recreate them, but still for unknown reasons some vanish, and some have this problem. I have noticed also a slight dependency on one specific settings: if you have let us say about 6 mailboxes with pop with the same numbers of accounts, then, if you set the filter to be applicable to that specific account and not to the others, this filter will be hit much more frequently with this "cannot find account of filter" dialogue. Once the "amnesia" started it will "cycle" through and loose one by one a filter in the list (direction generally from top to bottom - without guarantee, it sometime can hit in the middle of the list). In this cases you may not be presented with the little window complaining not to find the account. You will just loose the filters one by one. Now let us speak about the dependency of this with "waiting". If you start up the user A with kmail in automatic and a) either open another user and then return to kmail to check mail. Or b) you do wait at least about 40 seconds to 1 minute usually the filter never fails. But it fails always and repeatably triggered by immediately asking for mail. Then the filter does not work and will not work up to logout/in again as stated. As this bug is loosing data (filter setup with a lot of care) it is quite annoying and may also ruin filter collections of users. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=969675
http://bugzilla.opensuse.org/show_bug.cgi?id=969675#c1
--- Comment #1 from Stakanov Schufter
http://bugzilla.opensuse.org/show_bug.cgi?id=969675
http://bugzilla.opensuse.org/show_bug.cgi?id=969675#c2
Wolfgang Bauer
http://bugzilla.opensuse.org/show_bug.cgi?id=969675
http://bugzilla.opensuse.org/show_bug.cgi?id=969675#c3
Stakanov Schufter
http://bugzilla.opensuse.org/show_bug.cgi?id=969675
http://bugzilla.opensuse.org/show_bug.cgi?id=969675#c4
Wolfgang Bauer
So, if I well understand we are now reporting KDE bugs only to KDE right?
If it is clearly a bug in KDE's software, it's better to report it directly to KDE, yes. If it is a bug in our packaging, you should of course report it to us.
The fact is they are setting all kde-bugs for kde4 as not supported any more.
If they fix it for the KF5 version, it might be possible to backport it. Although in particular those filtering bugs rather sound like fundamental problems in the whole architecture to me. And KDEPIM5 is included in Leap 42.1, the latest version even. We just do not replace KDEPIM4 automatically yet, to not surprise users. One problem in particular is that some applications (e.g. ktimetracker, kjots, knode) have been dropped without replacement in the KF5 version. Nothing prevents you to switch to it though. It is greatly improved, especially speed-wise.
The solution IMAP instead of POP is curious. I would open a proposal to enhance kmail then: as POP doesn't work, you do not support it any more. Only IMAP supported.
??? POP does work. But filtering mails in KMail/Akonadi has severe problems (no matter whether you use POP or IMAP), and that since years. I just told you what I did, and that fixed all my filtering problems (duplicated mails e.g.) and has also other advantages, especially if you want to access . IMAP is a much more modern and flexible protocol than POP. It was not meant as a "solution" to this bug.
Allow me the comment that, given that KDE does not fix kde4 any more, no kde4 package should be still in Leap. As no bug there will be fixed any more.
Well, not all applications have been ported to KF5 yet. So it is not completely true that KDE does not fix KDE4 any more. Even kdelibs4 does still get fixes. And those applications that have been ported to KF5, have been replaced in Leap by the KF5 versions too. Just KDEPIM is still available in both versions.
And sorry that I did post. This was posted to KDE bugzilla by me as a bug about 3 years ago, given the status of "duplicate" and form then on.....nothing happened any more. Nor will anything happen any more. Wontfix is the magic word.
Sorry, but that's not our fault. And how do you expect the 4 openSUSE packagers to fix a bug like this? This needs deep knowledge and understanding of Akonadi's code and inner workings.
However, as for a normal user it is not possible to know if a bug is a packaging bug or not (how can one tell?) I will refrain from posting any bug here concerning KDE. Right?
Wrong. Yes, it is sometimes (often?) not easy to tell whether it is a bug in KDE or in openSUSE, not even always for us. But then, choose what you think is more likely, you will be redirected if it was wrong. That doesn't mean you should not post any bug here concerning KDE, and I never wrote that. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=969675
http://bugzilla.opensuse.org/show_bug.cgi?id=969675#c5
Stakanov Schufter
If they fix it for the KF5 version, it might be possible to backport it. Although in particular those filtering bugs rather sound like fundamental problems in the whole architecture to me.
And KDEPIM5 is included in Leap 42.1, the latest version even. We just do not replace KDEPIM4 automatically yet, to not surprise users. One problem in particular is that some applications (e.g. ktimetracker, kjots, knode) have been dropped without replacement in the KF5 version.
Well not only. If have tried it on another machine. No calender function available in version 5. If not, I would have changed with my working machine. But it does not seem to work?
Nothing prevents you to switch to it though. It is greatly improved, especially speed-wise. As said I would love to....
But filtering mails in KMail/Akonadi has severe problems (no matter whether you use POP or IMAP), and that since years.
I just told you what I did, and that fixed all my filtering problems (duplicated mails e.g.) and has also other advantages, especially if you want to access . IMAP is a much more modern and flexible protocol than POP.
It was not meant as a "solution" to this bug.
Ok. Thank you, that was not clear. Now it is.
Allow me the comment that, given that KDE does not fix kde4 any more, no kde4 package should be still in Leap. As no bug there will be fixed any more.
Well, not all applications have been ported to KF5 yet. So it is not completely true that KDE does not fix KDE4 any more. Even kdelibs4 does still get fixes. It is difficult. I receive messages to bugs posted ages ago, never had any attention and closed with: as you know kde4 now is out of support. How should I understand this. No really knowing what to say.
And those applications that have been ported to KF5, have been replaced in Leap by the KF5 versions too. Just KDEPIM is still available in both versions.
And sorry that I did post. This was posted to KDE bugzilla by me as a bug about 3 years ago, given the status of "duplicate" and form then on.....nothing happened any more. Nor will anything happen any more. Wontfix is the magic word.
Sorry, but that's not our fault.
I did not say it is. Sorry if you should have understood it this way. I obviously have to improve my communicative skills.
And how do you expect the 4 openSUSE packagers to fix a bug like this? This needs deep knowledge and understanding of Akonadi's code and inner workings. Right question: how do you think a standard user that wants not to leech but to contribute and give back to the project to be able to understand what is what? There is the whole caveat.
But then, choose what you think is more likely, you will be redirected if it was wrong.
That doesn't mean you should not post any bug here concerning KDE, and I never wrote that. Good, that is cleared and I will also clear this with what I did post (wrongly then) on the mailing list. I did understand it as such. Therefore I will have to foster my listening skills.
Since we are there: For the calender not working in kdepim5 where should I open the bug, upstream or here? (sorry I take advantage, but if that is possible I will do to be able to switch then). -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=969675
http://bugzilla.opensuse.org/show_bug.cgi?id=969675#c6
Wolfgang Bauer
Well not only. If have tried it on another machine. No calender function available in version 5. If not, I would have changed with my working machine. But it does not seem to work?
KDEPIM5 does have calendar functionality, KOrganizer has been ported and is in the package korganizer5. If you mean that Plasma's calendar does not display events from Akonadi, then yes. This has been implemented only recently (because KDEPIM wasn't ported to KF5) and is not part of the release yet.
It is difficult. I receive messages to bugs posted ages ago, never had any attention and closed with: as you know kde4 now is out of support. How should I understand this. No really knowing what to say.
Well, not all applications are really well maintained. Most that are have indeed been ported to KF5 as well already. But again: KDE4 is *not* out of support yet. The desktop is, and in the case of applications that are already ported the KDE4 version is normally dropped, yes. Still, you wrote yourself that this bug is apparently still present in the KF5 version too. And the upstream bug report is still open. Unfortunately there are often too few people actually working on the bugs, and especially KDEPIM is very underpowered.
Right question: how do you think a standard user that wants not to leech but to contribute and give back to the project to be able to understand what is what? There is the whole caveat.
I don't understand what you mean with "what is what". What is upstream (those who actually develop the software) and what is openSUSE?
Since we are there: For the calender not working in kdepim5 where should I open the bug, upstream or here? (sorry I take advantage, but if that is possible I will do to be able to switch then).
The calendar should work. It works fine here. But your question is impossible to answer. "calendar not working" could be anything. Is/was korganizer5 installed? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=969675
http://bugzilla.opensuse.org/show_bug.cgi?id=969675#c7
--- Comment #7 from Wolfgang Bauer
I just told you what I did, and that fixed all my filtering problems (duplicated mails e.g.) and has also other advantages, especially if you want to access .
Sorry, something went missing in that sentence. It should read: especially if you want to access your mail from several systems. And something else I'd like to mention, the developers are currently redesigning Akonadi from scratch (e.g. it will work without a central server and database then). "Akonadi Next" will hopefully solve all those architectural problems, but it will still take a while to finish it. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com