4:51 p.m.
Hello,
I had to leave Fedora a year ago because of breaking KDE Plasma
updates mid-cycle (even on "current minus one" Fedora). I have since
learned that this problem is unavoidable because of the Plasma release
cycle, when the previous (non-LTS) release immediately stops being
supported; this forces an update mid-cycle to a new Plasma and
glitches can happen.
I am looking at trying again, but can I somehow freeze all Plasma
packages, while not disabling updates for all other stuff? I know what
"dnf versionlock" is, but how do I create a correct list for it?
The idea would be to freeze Plasma packages in advance of a Plasma
version update and unfreeze a month after the new version goes into
Fedora, watching for critical security issues in the meantime.
--
Yours, Mikhail Ramendik
Unless explicitly stated, all opinions in my mail are my own and do
not reflect the views of any organization
9:30 a.m.
On Thu, 2020-12-17 at 22:51 +0000, Mikhail Ramendik wrote:
Hello,
I had to leave Fedora a year ago because of breaking KDE Plasma
updates mid-cycle (even on "current minus one" Fedora). I have since
learned that this problem is unavoidable because of the Plasma
release
cycle, when the previous (non-LTS) release immediately stops being
supported; this forces an update mid-cycle to a new Plasma and
glitches can happen.
I am looking at trying again, but can I somehow freeze all Plasma
packages, while not disabling updates for all other stuff? I know
what
"dnf versionlock" is, but how do I create a correct list for it?
The idea would be to freeze Plasma packages in advance of a Plasma
version update and unfreeze a month after the new version goes into
Fedora, watching for critical security issues in the meantime.
first guess is kwayland , please try remove kwayland with dnf remove
kwayland , and test it again
--
Yours, Mikhail Ramendik
Unless explicitly stated, all opinions in my mail are my own and do
not reflect the views of any organization
_______________________________________________
kde mailing list -- kde(a)lists.fedoraproject.org
To unsubscribe send an email to kde-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/kde@lists.fedoraproject.org
--
Sérgio M. B.
4:16 p.m.
On Fri, 18 Dec 2020 at 15:31, Sérgio Basto <sergio(a)serjux.com> wrote:
> The idea would be to freeze Plasma packages in advance of a
Plasma
> version update and unfreeze a month after the new version goes into
> Fedora, watching for critical security issues in the meantime.
first guess is kwayland , please try remove kwayland with dnf remove
kwayland , and test it again
The breaking updates happened in late 2019. I don't think kwayland was
in use at all at the time, but I had crashes going for two or three
weeks then a fix eventually arrived. The root cause is that an update
to a new version of Plasma happens in the middle of the Fedora cycle.
I am looking at trying Fedora again but I want to shield myself from
this issue in advance, by blocking all Plasma package updates as soon
as a new version is expected.
--
Yours, Mikhail Ramendik
Unless explicitly stated, all opinions in my mail are my own and do
not reflect the views of any organization
4:37 p.m.
On Fri, 18 Dec 2020 at 22:16, Mikhail Ramendik <mr(a)ramendik.ru> wrote:
The breaking updates happened in late 2019. I don't think
kwayland was
in use at all at the time, but I had crashes going for two or three
weeks then a fix eventually arrived.
I now found the bug that hit me back then. It took over a month to
fix. https://bugzilla.redhat.com/show_bug.cgi?id=1746465
I want to exclude, or significantly lower, the possibility of such
major bugs arriving to my system at random times. I am looking at
doing it by freezing only the Plasma-related parts.
Though honestly I don't understand why this major update with a large
probability of breaking something (to KDE Frameworks 5.59) happened at
that particular time in August 2019. I now checked and the KDE
Frameworks version was old news by the time (it came out in June)
while KDE Plasma 5.17 came out in December. Was there a rationale for
the mid-release push of KDE Frameworks to Fedora 29, which was
"current minus one" at the time?
I really need to understand if I can use some freeze lists and
scheduling to shield myself from such updates.
--
Yours, Mikhail Ramendik
Unless explicitly stated, all opinions in my mail are my own and do
not reflect the views of any organization
4:37 p.m.
On Fri, 18 Dec 2020 at 22:37, Mikhail Ramendik <mr(a)ramendik.ru> wrote:
that particular time in August 2019. I now checked and the KDE
Frameworks version was old news by the time (it came out in June)
while KDE Plasma 5.17 came out in December.
Sorry - mixup here - September. But still not August.
--
Yours, Mikhail Ramendik
Unless explicitly stated, all opinions in my mail are my own and do
not reflect the views of any organization
8:04 p.m.
On 17/12/2020 15:51, Mikhail Ramendik wrote:
Hello,
I had to leave Fedora a year ago because of breaking KDE Plasma
updates mid-cycle (even on "current minus one" Fedora). I have since
learned that this problem is unavoidable because of the Plasma release
cycle, when the previous (non-LTS) release immediately stops being
supported; this forces an update mid-cycle to a new Plasma and
glitches can happen.
I am looking at trying again, but can I somehow freeze all Plasma
packages, while not disabling updates for all other stuff? I know what
"dnf versionlock" is, but how do I create a correct list for it?
The idea would be to freeze Plasma packages in advance of a Plasma
version update and unfreeze a month after the new version goes into
Fedora, watching for critical security issues in the meantime.
I am having weird lockups with nvidia driver. Need to use the binary
source for some apps I use. Machine is not 100% frozen as I can ssh in
and make a clean shutdown.
I am using Xorg still.
It only seems to happen when playing videos in full screen on one monitor.
I do have some issues when switching between sessions as I have multiple
users logged in at one time and all the time. If I use Plasma desktop,
I end up with a KWIN using 100% of a CPU. I have not had time to worry
about it yet. Going to wait to update to F33 first.
I am concerned about KDE stability at present. Many little things
adding up to a major headache.
6:04 a.m.
On Mon, 2020-12-21 at 19:04 -0700, Robin Laing wrote:
On 17/12/2020 15:51, Mikhail Ramendik wrote:
> Hello,
>
> I had to leave Fedora a year ago because of breaking KDE Plasma
> updates mid-cycle (even on "current minus one" Fedora). I have
> since
> learned that this problem is unavoidable because of the Plasma
> release
> cycle, when the previous (non-LTS) release immediately stops being
> supported; this forces an update mid-cycle to a new Plasma and
> glitches can happen.
>
> I am looking at trying again, but can I somehow freeze all Plasma
> packages, while not disabling updates for all other stuff? I know
> what
> "dnf versionlock" is, but how do I create a correct list for it?
>
> The idea would be to freeze Plasma packages in advance of a Plasma
> version update and unfreeze a month after the new version goes into
> Fedora, watching for critical security issues in the meantime.
>
I am having weird lockups with nvidia driver. Need to use the
binary
source for some apps I use. Machine is not 100% frozen as I can ssh
in
and make a clean shutdown.
I am using Xorg still.
It only seems to happen when playing videos in full screen on one
monitor.
I do have some issues when switching between sessions as I have
multiple
users logged in at one time and all the time. If I use Plasma
desktop,
I end up with a KWIN using 100% of a CPU. I have not had time to
worry
about it yet. Going to wait to update to F33 first.
I am concerned about KDE stability at present. Many little things
adding up to a major headache.
what nvidia do you have ? I don't remember any freeze problem in many
months or years .
Now problems and freezes with old nvidia cards I got some , in a old
laptop I need to use kernel 4.14 TLS ...
--
Sérgio M. B.
1:07 a.m.
On 23/12/2020 05:04, Sérgio Basto wrote:
On Mon, 2020-12-21 at 19:04 -0700, Robin Laing wrote:
> On 17/12/2020 15:51, Mikhail Ramendik wrote:
>> Hello,
>>
>> I had to leave Fedora a year ago because of breaking KDE Plasma
>> updates mid-cycle (even on "current minus one" Fedora). I have
>> since
>> learned that this problem is unavoidable because of the Plasma
>> release
>> cycle, when the previous (non-LTS) release immediately stops being
>> supported; this forces an update mid-cycle to a new Plasma and
>> glitches can happen.
>>
>> I am looking at trying again, but can I somehow freeze all Plasma
>> packages, while not disabling updates for all other stuff? I know
>> what
>> "dnf versionlock" is, but how do I create a correct list for it?
>>
>> The idea would be to freeze Plasma packages in advance of a Plasma
>> version update and unfreeze a month after the new version goes into
>> Fedora, watching for critical security issues in the meantime.
>>
>
> I am having weird lockups with nvidia driver. Need to use the
> binary
> source for some apps I use. Machine is not 100% frozen as I can ssh
> in
> and make a clean shutdown.
>
> I am using Xorg still.
>
> It only seems to happen when playing videos in full screen on one
> monitor.
>
> I do have some issues when switching between sessions as I have
> multiple
> users logged in at one time and all the time. If I use Plasma
> desktop,
> I end up with a KWIN using 100% of a CPU. I have not had time to
> worry
> about it yet. Going to wait to update to F33 first.
>
> I am concerned about KDE stability at present. Many little things
> adding up to a major headache.
>
what nvidia do you have ? I don't remember any freeze problem in many
months or years .
Now problems and freezes with old nvidia cards I got some , in a old
laptop I need to use kernel 4.14 TLS ...
GeForce GTX 960
Only seems to happen when using one of two monitors for full screen
video. nVidia driver goes to 100%.
Also having issues with switching between users and sddm but I am
waiting to upgrade to 33 to try to debug.
I have many problem with the present iteration of KDE on Fedora but
waiting for F33 on this computer.
--
Save money, use Open Source Software.
Free Office Suite at
http://www.libreoffice.org
1:50 a.m.
On 26/12/2020 00:07, Robin Laing wrote:
On 23/12/2020 05:04, Sérgio Basto wrote:
> On Mon, 2020-12-21 at 19:04 -0700, Robin Laing wrote:
>> On 17/12/2020 15:51, Mikhail Ramendik wrote:
>>> Hello,
>>>
>>> I had to leave Fedora a year ago because of breaking KDE Plasma
>>> updates mid-cycle (even on "current minus one" Fedora). I have
>>> since
>>> learned that this problem is unavoidable because of the Plasma
>>> release
>>> cycle, when the previous (non-LTS) release immediately stops being
>>> supported; this forces an update mid-cycle to a new Plasma and
>>> glitches can happen.
>>>
>>> I am looking at trying again, but can I somehow freeze all Plasma
>>> packages, while not disabling updates for all other stuff? I know
>>> what
>>> "dnf versionlock" is, but how do I create a correct list for it?
>>>
>>> The idea would be to freeze Plasma packages in advance of a Plasma
>>> version update and unfreeze a month after the new version goes into
>>> Fedora, watching for critical security issues in the meantime.
>>>
>>
>> I am having weird lockups with nvidia driver. Need to use the
>> binary
>> source for some apps I use. Machine is not 100% frozen as I can ssh
>> in
>> and make a clean shutdown.
>>
>> I am using Xorg still.
>>
>> It only seems to happen when playing videos in full screen on one
>> monitor.
>>
>> I do have some issues when switching between sessions as I have
>> multiple
>> users logged in at one time and all the time. If I use Plasma
>> desktop,
>> I end up with a KWIN using 100% of a CPU. I have not had time to
>> worry
>> about it yet. Going to wait to update to F33 first.
>>
>> I am concerned about KDE stability at present. Many little things
>> adding up to a major headache.
>>
>
> what nvidia do you have ? I don't remember any freeze problem in many
> months or years .
> Now problems and freezes with old nvidia cards I got some , in a old
> laptop I need to use kernel 4.14 TLS ...
>
>
GeForce GTX 960
Only seems to happen when using one of two monitors for full screen
video. nVidia driver goes to 100%.
Also having issues with switching between users and sddm but I am
waiting to upgrade to 33 to try to debug.
I have many problem with the present iteration of KDE on Fedora but
waiting for F33 on this computer.
Had a slightly different freeze the other day and it didn't kill
everything but it did freeze one of my monitors and caused other issues
that would only end with a reboot.
All my desktop freezes had only one thing in common and that was Falkon
open. This last freeze was directly related to Falkon as the process
QtWebEngineProc.
From top.
965530 XXXX 20 0 3454544 1.6g 87892 R 138.6 5.2 4:55.10
QtWebEngineProc
QtWebEngineProc is called by Falkon. Looking through various lists, it
does seem that there are some issues with this process and it is used
for displaying stuff from the browser.
I am still on 32.
When I killed the QtWebEngineProc, is affected kscreenlocker and
prevented me from switching accounts as there was no login prompt on the
other account. kscreenlocker was at 100% for the second account.
1188
days inactive
1218
days old
8 comments
3 participants
participants (3)
-
Mikhail Ramendik -
Robin Laing -
Sérgio Basto