[Interest] heads up - ksplashqml crash
roland at logikalsolutions.com
Mon Oct 7 16:58:58 CEST 2019
My hardware was new enough I could install 390. Others will most likely
not be as lucky. I was just sending up a flare making he assumption KDE
developer will try to kick this up the chain. Once I found a work around
I didn't care enough to diff the 340 and 390 APIs. 340 has been around a
very long time an appears to be quite stable. My knee-jerk suspicion
would be an API difference with "current" code written against newer
API. You could be correct though. This could be a long latent bug now
What is interesting is the fact this didn't surface until KDE pushed out
recent updates. After that the crash happened with each boot. Before
On 10/7/2019 9:29 AM, Sérgio Martins wrote:
> On Sat, Oct 5, 2019 at 11:22 PM Roland Hughes
> <roland at logikalsolutions.com> wrote:
>> Just in case this is deeper than the ksplashqml.
>> Don't know if it is specific to KDE or deeper within Qt. Appears to
>> happen with nvidia-340 driver but doesn't happen with nvidia-driver-390
> If the "display crashes", goes black for all apps and it's only repro
> on an older nvidia driver, as stated in the bug report, then I'd say
> the bug is not in Qt, but in the nvidia 340 driver.
> If you hope for a workaround in Qt then better get a minimal test-case.
Roland Hughes, President
More information about the Interest