Re: Goodbye for now, kmail
ianseeks <[email protected]>
| Newsgroups | gmane.comp.kde.users.pim |
|---|---|
| Message-ID | <1804128.WgQHlxlQVE@lianli> |
On Saturday, 6 May 2017 10:20:54 BST Martin Steigerwald wrote: > ianseeks - 06.05.17, 10:11: > > On Saturday, 6 May 2017 09:36:51 BST Martin Steigerwald wrote: > > > ianseeks - 06.05.17, 08:29: > > > > > This is the really annoying part: it all just works for me. I don't > > > > > know > > > > > what I'm doing wrong, but it just works. I can't reproduce many of > > > > > the > > > > > misbehaviors and issues that users report and without that I can't > > > > > fix > > > > > them. Believe me that it really annoys me and that I'd much rather > > > > > had > > > > > the > > > > > most broken setup ever that I could just analyze and fix, but I > > > > > guess > > > > > I'm > > > > > just too lucky (or unlucky, depends on the point of view :-)) > > > > > > > > Is there someway we can all check release levels are all consistent > > > > with > > > > all the software required for KDEPIM? It could be that all your > > > > pieces > > > > of > > > > software are correctly matched with each other whereas a lot of us > > > > just > > > > accept the upgrades and some of us may now have misaligned software > > > > releases > > > > > > Well at least that one should be easy enough as Akonadi and KDEPIM has > > > same > > > version number on each release since quite some time. > > > > I was thinking more of versions of individual bits of software within the > > major versions, all it takes is for one failed update of one small piece > > of > > software to perhaps cause an issue. As Dan is not able to reproduce a > > lot > > of issues, maybe we should be able to validate our installation against > > his > > to see if there are differences. > > I don´t understand this one: If I made sure I have all packages below at > basically the same major version, what can be out of sync? At least on > Debian if this is true, I don´t see how any smaller piece can be out of > sync, unless the maintainers fail to grab the right source versions, which > I believe is *highly* unlikely to happen. I am grasping at straws here as Dan seems to work without issues and there are a fair few here that don't. I was more or less asking if there was a reference list of a clean working install that we could use ourselves to see if we have messed up our own systems. I know i've messed up my downloads by using a wrong repo in the past so i could have easily messed it all up myself. I guess i should perhaps wipe my machine and reinstall from scratch and backups to see if it cures the problems. > > > On Debian I´d try > > > > > > apt list | egrep "akonadi|kmail|kdepim-runtime" > > > > > > and make sure that Akonadi packages, libakonadi packages, libkf5akonadi > > > packages as well as kdepim-runtime (containing the Akonadi resources for > > > KDEPIM like IMAP or maildir resource) and kmail package are all the the > > > same major version, i.e. currently 16.04. But if you can I suggest you > > > try to use a later version, cause 16.04 is older than a year already. > > > However for me this one works pretty stable except for the performance > > > related shortcomings. > > > > > > Oh, BTW the folder has still not been moved. > > > > > > Ciao, -- opensuse:tumbleweed:20170505 Qt: 5.7.1 KDE Frameworks: 5.33.0 KDE Plasma: 5.9.5 kwin 5.9.5 kmail2 5.4.3 akonadiserver 5.4.3 Kernel: 4.10.13-1-default Nouveau: 1.0.15_1.1