Re: [Interest] heads up - ksplashqml crash
A lot of people don't have any money. They use a corporate or relative's cast-off. Still others, like the older computers I have on the workbench behind me, have been re-purposed to run BOINC. They won't be upgraded. If a drive dies and I have a spare laying around I'll put that in and re-load a distro, but by and large the machines won't be fixed. They'll search for the cure for cancer and other projects beneficial to humans as well as help look for ET, but unless I need to throw a lot of machines at something, that is how they will spend their remaining years. On 10/7/19 10:06 AM, Konstantin Tokarev wrote: 07.10.2019, 18:00, "Roland Hughes" : My hardware was new enough I could install 390. Others will most likely not be as lucky. It may be a good reason to replace their 9 years old GPU to something up-to-date. -- Roland Hughes, President Logikal Solutions (630)-205-1593 http://www.theminimumyouneedtoknow.com http://www.infiniteexposure.net http://www.johnsmith-book.com http://www.logikalblog.com http://www.interestingauthors.com/blog ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] heads up - ksplashqml crash
07.10.2019, 18:00, "Roland Hughes" : > My hardware was new enough I could install 390. Others will most likely > not be as lucky. It may be a good reason to replace their 9 years old GPU to something up-to-date. -- Regards, Konstantin ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] heads up - ksplashqml crash
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 exposed. 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 that, nada. On 10/7/2019 9:29 AM, Sérgio Martins wrote: On Sat, Oct 5, 2019 at 11:22 PM Roland Hughes wrote: Just in case this is deeper than the ksplashqml. https://bugs.kde.org/show_bug.cgi?id=408904 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 installed. 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. Regards, Sergio -- Roland Hughes, President Logikal Solutions (630)-205-1593 (cell) http://www.theminimumyouneedtoknow.com http://www.infiniteexposure.net http://www.johnsmith-book.com ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] heads up - ksplashqml crash
On Sat, Oct 5, 2019 at 11:22 PM Roland Hughes wrote: > > Just in case this is deeper than the ksplashqml. > > https://bugs.kde.org/show_bug.cgi?id=408904 > > 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 > installed. 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. Regards, Sergio ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
