I finally got around to the 15.1>15.2 upgrade the other day using the iso image on dvd, and here's a few notes. I'd like to hear what people think. a reasonable thought I initially tried to update all repositories before the upgrade, but I must have messed up the pacman url, because it was not found and I had conflicts. I tried to use the back button to fix it, but couldn't find my back to the right spot, and decided to be conservative and start again with just the dvd. I ended up with conflicts anyway and resolved them one by one.
The result was about 400 packages deleted. A lot of them were development packages and debuginfo and whatnot. I haven't looked further yet. This is not unusual if you used a lot of particular repos. I cannot confirm so many packages, the main part of my upgrade (done via zypper however) at the time was smooth. After the upgrade I used Yast to switch to pacman, and it did pull some packages back in. I also used Yast for a serious online update. BTW, I noticed the main repository does not carry some chess packages such as xboard; they are only available from pacman. The offer between vendors seems to change all the time. I expect a major remix with the 15.3 as the code base AFAIU will change quite a lot. I then noticed about 600 packages still had an "x-lp151.x" sort of moniker-- zypper up took care of that.
In data venerdì 19 febbraio 2021 08:57:25 CET, Robert Hardy ha scritto: that is odd. But not related to the problems now listed below.
KDE's notification system isn't working due to a problem with xfce as described here: https://forums.opensuse.org/showthread.php/543232-Lost-notifications . I'm not entirely happy with the proposed solutions. I seem to recall KDE notification problems before, perhaps with 15.0, or maybe 42.0, where my system would fall back to xfce notifications until the KDE problems were fixed. That seemed like a nice behavior, all in all. I do not use xfce so I cannot tell. ksysguard has gone from maybe 6-8% of one CPU to 30-40%. I've always tended to leave that running on one desktop, but 30-40% is unacceptable. It also apparently replaced my file read/write columns with Download/Upload. I confirm this.
I have a CPU temp monitor in one of the panels that is not working. Any attempt to open its configuration dialog crashes plasmashell. I can confirm this too.
Then there's akonadi. Akonadi_imap_resource, akonadiserver, and mysqld hog CPU continually on admittedly very large gmail folders until such time as akonadiserver "closes unexpectedly". I've also suddenly got 1131-300-200-100-300 emails in a drafts folder as reported variously by kontact and xfce. None of them are visible. Akonadi server somehow restarts itself. Hey, I can't watch Netflix while akonadi is running! At times past, I've bumped akonadi's priority down a notch. This was the reason why I had to give up two times the upgrade to 15.2 and switched back to 15.1. It is also the reason why I will skip all together 15.2. My personal experience is that with 15.2 and KDE you are not getting your work done.
I haven't mentioned bluetooth which has been an ongoing problem for a long time. I've successfully nursed it in the past with restarts and whatnot, but I don't want to get into that at the moment. I used to use serial over bluetooth a lot, as well as tethering to my phone, but for the moment, it's a bit beyond me. This appears to be a problem of KDE and pulseaudio. While the issue with audioprofiles is quite old, I am quite worried to see that in Tumbleweed currently since some time the BT support is practically broken with a strongly reduced functionality and an odd looking window that causes more confusion. This must be a "feature" I bet. I do not recall my BT broken in 15.2 though.
So, comments? I can follow up on my downtime, keeping in mind that it will take time away from watching Netflix! ;-) My I experience segfaults, zombie processes, excessive CPU usage, unusable IMAP with constantly broken indexes and severe data loss (until complete loss of IMAP folder from this mailing list from a few thousand to 0 (beyond repair). You can see it as a kind of "data sanitizing" (no,...that is too cynical maybe). Overheating of the CPU due to silent segfaults with zombie processes blocking one CPU to 100% were also frequent. Temperature rises n this case to 120°C. And the archiving also failed, probably because the indexes are broken. So you risk also to be without backup of your mail.
What was better with 15.2: there are a few memory leaks that do not appear, but mainly because the system crashes often so you do not reach maybe sufficient idle time. There seem to be people that claim that "I had no issue at all" (see this list). This is very good for them. But I can totally accept and confirm the greater part of your problems. Some people have claimed that erasing the indexes and reindex from scratch did help. I would also then delete the mail filter if you do it. Further you will loose all(!) settings of default folders in all accounts an personality and you have to recover them by hand. I did this all, but still faced total corruption of indexes, crashes etc so I switched back to 15.1. Your IMAP problem you find it here: bugzilla.opensuse.org/show_bug.cgi?id=1173759 ( "Kmail 20.04 as found in Leap 15.2 is unbearably slow") you can join to the cc list, currently AFAIK there is not fix foreseen as it appears it is not clear what is broken or has to be backported.