Bug 375913 - KDE Discover crashes on launch in QSGRenderLoop::handleContextCreationFailure()
Summary: KDE Discover crashes on launch in QSGRenderLoop::handleContextCreationFailure()
Status: RESOLVED FIXED
Alias: None
Product: Discover
Classification: Applications
Component: discover (show other bugs)
Version: 5.7.5
Platform: unspecified Linux
: VHI crash
Target Milestone: ---
Assignee: phd
URL:
Keywords: drkonqi
: 367883 368888 372097 375463 377028 380425 383526 385469 386160 388504 388764 388875 392474 392591 394872 398227 398330 398520 399557 399635 399938 401275 403075 405184 405208 405251 405290 405412 405701 405748 405867 406091 408868 409987 410323 413808 415105 415216 415273 415515 417214 417411 417518 418652 419051 420200 420648 420828 420845 420938 421090 421380 421988 423627 423663 423742 427885 428480 428876 429591 429661 431246 431253 432373 438445 440291 449751 (view as bug list)
Depends on:
Blocks:
 
Reported: 2017-02-02 18:53 UTC by jang
Modified: 2022-02-07 18:31 UTC (History)
75 users (show)

See Also:
Latest Commit: https://invent.kde.org/frameworks/kdeclarative/commit/090610124d4650150af49a8e30f6b77ad9803dfe
Version Fixed In: 5.78
Sentry Crash Report:

Attachments
New crash information added by DrKonqi (77.06 KB, text/plain)
2017-02-23 02:44 UTC, Daniil Vasin 		Details
New crash information added by DrKonqi (15.87 KB, text/plain)
2017-10-21 23:31 UTC, phoenixrock86 		Details
New crash information added by DrKonqi (9.13 KB, text/plain)
2018-03-27 22:36 UTC, maxilous 		Details
attachment-15973-0.html (1.25 KB, text/html)
2019-03-26 16:57 UTC, Glen 		Details
attachment-26084-0.html (1.26 KB, text/html)
2019-08-05 00:39 UTC, Glen 		Details
attachment-5869-0.html (1.01 KB, text/html)
2020-03-11 12:56 UTC, Thunder 		Details
attachment-7392-0.html (2.10 KB, text/html)
2020-03-11 14:38 UTC, Glen 		Details
New crash information added by DrKonqi (12.26 KB, patch)
2020-07-04 16:39 UTC, s.d.mateja 		Details
New crash information added by DrKonqi (12.05 KB, patch)
2021-03-09 04:59 UTC, davidnyc16 		Details
New crash information added by DrKonqi (12.58 KB, patch)
2021-04-26 14:07 UTC, SkZ 		Details
New crash information added by DrKonqi (3.17 KB, text/plain)
2021-10-10 12:01 UTC, scordido 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description jang 2017-02-02 18:53:12 UTC 
Application: plasma-discover (5.7.5)

Qt Version: 5.6.1
Frameworks Version: 5.26.0
Operating System: Linux 4.8.0-37-generic x86_64
Distribution: Ubuntu 16.10

-- Information about the crash:
- What I was doing when the application crashed:

Absolutely nothing! Systray notification that 4 updates were available. Launch Discover via the "update" button and it crashes.

The crash can be reproduced every time.

-- Backtrace:
Application: Discover (plasma-discover), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f062a9bfd40 (LWP 16232))]

Thread 7 (Thread 0x7f0609391700 (LWP 16238)):
#0  __libc_enable_asynccancel () at ../sysdeps/unix/sysv/linux/x86_64/cancellation.S:67
#1  0x00007f063766e0b2 in poll () at ../sysdeps/unix/syscall-template.S:84
#2  0x00007f06348ee9d6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f06348eed62 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007f060ad814e6 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#5  0x00007f0634916325 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x00007f0634e126ca in start_thread (arg=0x7f0609391700) at pthread_create.c:333
#7  0x00007f063767a0af in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 6 (Thread 0x7f0609b92700 (LWP 16237)):
#0  0x00007f0637669c8d in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x00007f0630484f55 in ?? () from /usr/lib/nvidia-340/tls/libnvidia-tls.so.340.101
#2  0x00007f0634932c80 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f06348ee485 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007f06348ee974 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007f06348eeaec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x00007f06348eeb31 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x00007f0634916325 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x00007f0634e126ca in start_thread (arg=0x7f0609b92700) at pthread_create.c:333
#9  0x00007f063767a0af in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 5 (Thread 0x7f0617fff700 (LWP 16236)):
#0  0x00007f0637669c8d in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x00007f0630484f55 in ?? () from /usr/lib/nvidia-340/tls/libnvidia-tls.so.340.101
#2  0x00007f0634932c80 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f06348ee485 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007f06348ee974 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007f06348eeaec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x00007f06382a54ab in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x00007f063824d0fa in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x00007f0638072d43 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x00007f0638077c68 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x00007f0634e126ca in start_thread (arg=0x7f0617fff700) at pthread_create.c:333
#11 0x00007f063767a0af in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 4 (Thread 0x7f061e4f5700 (LWP 16235)):
#0  0x00007f063766e0bd in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x00007f06348ee9d6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f06348eeaec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f06382a54ab in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x00007f063824d0fa in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x00007f0638072d43 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x00007f063a237c65 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x00007f0638077c68 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x00007f0634e126ca in start_thread (arg=0x7f061e4f5700) at pthread_create.c:333
#9  0x00007f063767a0af in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 3 (Thread 0x7f061f706700 (LWP 16234)):
#0  0x00007f0637669c8d in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x00007f0630484f55 in ?? () from /usr/lib/nvidia-340/tls/libnvidia-tls.so.340.101
#2  0x00007f0634932c80 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f06348ee485 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007f06348ee974 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007f06348eeaec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x00007f06382a54ab in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x00007f063824d0fa in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x00007f0638072d43 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x00007f06356aa575 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#10 0x00007f0638077c68 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x00007f0634e126ca in start_thread (arg=0x7f061f706700) at pthread_create.c:333
#12 0x00007f063767a0af in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 2 (Thread 0x7f0627a5e700 (LWP 16233)):
#0  0x00007f063766e0bd in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x00007f06329bdc62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x00007f06329bf8d7 in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x00007f062a5e8299 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x00007f0638077c68 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x00007f0634e126ca in start_thread (arg=0x7f0627a5e700) at pthread_create.c:333
#6  0x00007f063767a0af in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 1 (Thread 0x7f062a9bfd40 (LWP 16232)):
[KCrash Handler]
#6  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:58
#7  0x00007f06375a93ea in __GI_abort () at abort.c:89
#8  0x00007f063805ecc1 in QMessageLogger::fatal(char const*, ...) const () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x00007f063a72ea13 in QSGRenderLoop::handleContextCreationFailure(QQuickWindow*, bool) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#10 0x00007f063a736b82 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#11 0x00007f063a736f63 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#12 0x00007f0638840f65 in QWindow::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#13 0x00007f063a76aa13 in QQuickWindow::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#14 0x00007f0638e1d8ac in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#15 0x00007f0638e22d4f in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#16 0x00007f063824f3b0 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x00007f063883629d in QGuiApplicationPrivate::processExposeEvent(QWindowSystemInterfacePrivate::ExposeEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#18 0x00007f0638836e7d in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#19 0x00007f0638814b2b in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#20 0x00007f062a61e660 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#21 0x00007f06348ee7d7 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x00007f06348eea40 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x00007f06348eeaec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#24 0x00007f06382a548f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#25 0x00007f063824d0fa in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#26 0x00007f063825590c in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#27 0x000055cdefd2c699 in ?? ()
#28 0x00007f06375923f1 in __libc_start_main (main=0x55cdefd2bf90, argc=1, argv=0x7ffc64e4ffc8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffc64e4ffb8) at ../csu/libc-start.c:291
#29 0x000055cdefd2c7ba in _start ()

Possible duplicates by query: bug 375284, bug 364721, bug 364342, bug 362635, bug 362228.

Reported using DrKonqi
Comment 1 Daniil Vasin 2017-02-23 02:44:23 UTC 
Created attachment 104178 [details]
New crash information added by DrKonqi

plasma-discover (5.9.2) using Qt 5.7.1

- What I was doing when the application crashed:

Opening a deb package or to install updates from the updates icon in System Tray

-- Backtrace (Reduced):
#6  0x00007efec0935428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54
#7  0x00007efec093702a in __GI_abort () at abort.c:89
#8  0x00007efec13e9811 in QMessageLogger::fatal(char const*, ...) const () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x00007efec3dab0e3 in QSGRenderLoop::handleContextCreationFailure(QQuickWindow*, bool) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
[...]
#12 0x00007efec1fa4735 in QWindow::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
Comment 2 Christoph Feck 2017-02-23 03:06:58 UTC 
Please ask in a forum of your distribution how to fix the installation of the OpenGL drivers.
Comment 3 Christoph Feck 2017-02-23 03:08:04 UTC 
*** Bug 375463 has been marked as a duplicate of this bug. ***
Comment 4 Christoph Feck 2017-03-01 02:54:55 UTC 
*** Bug 377028 has been marked as a duplicate of this bug. ***
Comment 5 Christoph Feck 2017-06-14 13:39:52 UTC 
*** Bug 380425 has been marked as a duplicate of this bug. ***
Comment 6 Aleix Pol 2017-09-04 14:48:55 UTC 
*** Bug 383246 has been marked as a duplicate of this bug. ***
Comment 7 Christoph Feck 2017-09-04 14:51:36 UTC 
*** Bug 383526 has been marked as a duplicate of this bug. ***
Comment 8 Christoph Feck 2017-09-04 14:51:48 UTC 
*** Bug 372097 has been marked as a duplicate of this bug. ***
Comment 9 Christoph Feck 2017-09-04 14:52:03 UTC 
*** Bug 368888 has been marked as a duplicate of this bug. ***
Comment 10 Christoph Feck 2017-09-04 14:52:25 UTC 
*** Bug 367883 has been marked as a duplicate of this bug. ***
Comment 11 Christoph Feck 2017-10-17 00:38:53 UTC 
*** Bug 385469 has been marked as a duplicate of this bug. ***
Comment 12 phoenixrock86 2017-10-21 23:31:57 UTC 
Created attachment 108496 [details]
New crash information added by DrKonqi

plasma-discover (5.10.5) using Qt 5.9.1

- What I was doing when the application crashed:

Just browsing on Chrome thats it. Downloaded and installed the NVIDIA Display driver 340 just before this event.

-- Backtrace (Reduced):
#6  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
#7  0x00007f9fb9747f5d in __GI_abort () at abort.c:90
#8  0x00007f9fb9f0c107 in QMessageLogger::fatal(char const*, ...) const () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x00007f9fbd409787 in QSGRenderLoop::handleContextCreationFailure(QQuickWindow*, bool) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
[...]
#12 0x00007f9fbaf4dd35 in QWindow::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
Comment 13 Nate Graham 2017-11-07 20:29:02 UTC 
*** Bug 386160 has been marked as a duplicate of this bug. ***
Comment 14 Aleix Pol 2018-01-10 17:51:42 UTC 
*** Bug 388504 has been marked as a duplicate of this bug. ***
Comment 15 Aleix Pol 2018-01-10 17:51:51 UTC 
*** Bug 388764 has been marked as a duplicate of this bug. ***
Comment 16 Nate Graham 2018-01-12 18:38:16 UTC 
*** Bug 388875 has been marked as a duplicate of this bug. ***
Comment 17 maxilous 2018-03-27 22:36:48 UTC 
Created attachment 111690 [details]
New crash information added by DrKonqi

plasma-discover (5.8.9) using Qt 5.6.1

- What I was doing when the application crashed:
Was notified of updates and clicked the update button.

The crash persists but I believe it is related to this bug.

-- Backtrace (Reduced):
#6  0x00007efe36fd0428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54
#7  0x00007efe36fd202a in __GI_abort () at abort.c:89
#8  0x00007efe37a97f41 in QMessageLogger::fatal(char const*, ...) const () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x00007efe3a189fe3 in QSGRenderLoop::handleContextCreationFailure(QQuickWindow*, bool) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
[...]
#12 0x00007efe38676b25 in QWindow::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
Comment 18 Aleix Pol 2018-03-29 11:36:49 UTC 
*** Bug 392474 has been marked as a duplicate of this bug. ***
Comment 19 Christoph Feck 2018-06-01 01:02:03 UTC 
*** Bug 392591 has been marked as a duplicate of this bug. ***
Comment 20 Christoph Feck 2018-06-07 00:02:04 UTC 
*** Bug 394872 has been marked as a duplicate of this bug. ***
Comment 21 Nate Graham 2018-09-13 17:13:17 UTC 
*** Bug 398520 has been marked as a duplicate of this bug. ***
Comment 22 Nate Graham 2018-09-13 17:41:23 UTC 
*** Bug 398330 has been marked as a duplicate of this bug. ***
Comment 23 Nate Graham 2018-09-13 17:41:41 UTC 
*** Bug 398227 has been marked as a duplicate of this bug. ***
Comment 24 Nate Graham 2018-10-10 20:50:02 UTC 
*** Bug 399557 has been marked as a duplicate of this bug. ***
Comment 25 Nate Graham 2018-10-10 22:09:03 UTC 
*** Bug 399635 has been marked as a duplicate of this bug. ***
Comment 26 Nate Graham 2018-10-18 19:19:05 UTC 
*** Bug 399938 has been marked as a duplicate of this bug. ***
Comment 27 Nate Graham 2018-11-26 17:29:33 UTC 
*** Bug 401275 has been marked as a duplicate of this bug. ***
Comment 28 Nate Graham 2019-01-15 16:34:38 UTC 
*** Bug 403075 has been marked as a duplicate of this bug. ***
Comment 29 Nate Graham 2019-03-07 23:54:07 UTC 
*** Bug 405184 has been marked as a duplicate of this bug. ***
Comment 30 Nate Graham 2019-03-17 13:08:13 UTC 
*** Bug 405412 has been marked as a duplicate of this bug. ***
Comment 31 Nate Graham 2019-03-17 13:08:14 UTC 
*** Bug 405290 has been marked as a duplicate of this bug. ***
Comment 32 Nate Graham 2019-03-17 14:49:16 UTC 
*** Bug 405251 has been marked as a duplicate of this bug. ***
Comment 33 Nate Graham 2019-03-20 21:37:45 UTC 
*** Bug 405701 has been marked as a duplicate of this bug. ***
Comment 34 Christoph Feck 2019-03-24 10:37:28 UTC 
*** Bug 405208 has been marked as a duplicate of this bug. ***
Comment 35 Christoph Feck 2019-03-26 08:04:28 UTC 
*** Bug 405867 has been marked as a duplicate of this bug. ***
Comment 36 Glen 2019-03-26 16:57:21 UTC 
Created attachment 119061 [details]
attachment-15973-0.html

Solved

On Tue, Mar 26, 2019 at 1:04 AM Christoph Feck <bugzilla_noreply@kde.org>
wrote:

> https://bugs.kde.org/show_bug.cgi?id=375913
>
> Christoph Feck <cfeck@kde.org> changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>                  CC|                            |natrox@outlook.com
>
> --- Comment #35 from Christoph Feck <cfeck@kde.org> ---
> *** Bug 405867 has been marked as a duplicate of this bug. ***
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.
Comment 37 Nate Graham 2019-03-26 21:29:50 UTC 
*** Bug 405748 has been marked as a duplicate of this bug. ***
Comment 38 Nate Graham 2019-04-01 17:31:49 UTC 
*** Bug 406091 has been marked as a duplicate of this bug. ***
Comment 39 Nate Graham 2019-06-18 17:56:10 UTC 
*** Bug 408868 has been marked as a duplicate of this bug. ***
Comment 40 Nate Graham 2019-08-05 00:30:08 UTC 
*** Bug 410323 has been marked as a duplicate of this bug. ***
Comment 41 Glen 2019-08-05 00:39:24 UTC 
Created attachment 121935 [details]
attachment-26084-0.html

Thanks no problem any more.

On Sun, Aug 4, 2019, 5:30 PM Nate Graham <bugzilla_noreply@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=375913
>
> Nate Graham <nate@kde.org> changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>                  CC|                            |
> tiagosouzareis97@gmail.com
>
> --- Comment #40 from Nate Graham <nate@kde.org> ---
> *** Bug 410323 has been marked as a duplicate of this bug. ***
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.
Comment 42 Nate Graham 2019-08-14 15:05:12 UTC 
*** Bug 409987 has been marked as a duplicate of this bug. ***
Comment 43 Nate Graham 2019-11-04 19:18:25 UTC 
*** Bug 413808 has been marked as a duplicate of this bug. ***
Comment 44 Nate Graham 2019-12-13 11:09:46 UTC 
*** Bug 415105 has been marked as a duplicate of this bug. ***
Comment 45 Nate Graham 2020-01-02 16:51:55 UTC 
*** Bug 415273 has been marked as a duplicate of this bug. ***
Comment 46 Nate Graham 2020-01-02 17:09:26 UTC 
*** Bug 415515 has been marked as a duplicate of this bug. ***
Comment 47 Christoph Feck 2020-01-09 10:25:26 UTC 
*** Bug 415216 has been marked as a duplicate of this bug. ***
Comment 48 Nate Graham 2020-02-06 20:06:50 UTC 
*** Bug 417214 has been marked as a duplicate of this bug. ***
Comment 49 Nate Graham 2020-02-12 21:38:41 UTC 
*** Bug 417518 has been marked as a duplicate of this bug. ***
Comment 50 Nate Graham 2020-02-12 22:02:09 UTC 
*** Bug 417411 has been marked as a duplicate of this bug. ***
Comment 51 Aleix Pol 2020-03-11 12:15:08 UTC 
We still crash here, we better handle it somehow.

I recently learned about this behaviour, I'll try to see if we can handle it somehow, although it's still a problem between the driver and Qt miscommunicating.
Comment 52 Aleix Pol 2020-03-11 12:15:20 UTC 
*** Bug 418652 has been marked as a duplicate of this bug. ***
Comment 53 Aleix Pol 2020-03-11 12:54:33 UTC 
For the moment, if any of you that can reproduce the crash, can try running it from the terminal and tell us about it, that would be really handy.
Comment 54 Thunder 2020-03-11 12:56:36 UTC 
Created attachment 126726 [details]
attachment-5869-0.html

How do i stop these bug emails i've been getting them for years now and the
bug is already gone, also i'm on arch and gnome now please stop.

On Wed, Mar 11, 2020, 14:54 Aleix Pol <bugzilla_noreply@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=375913
>
> --- Comment #53 from Aleix Pol <aleixpol@kde.org> ---
> For the moment, if any of you that can reproduce the crash, can try
> running it
> from the terminal and tell us about it, that would be really handy.
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.
Comment 55 Glen 2020-03-11 14:38:18 UTC 
Created attachment 126727 [details]
attachment-7392-0.html

No idea as to how to let people know this was resolved. Sorry.Sent from my Galaxy Tab® S2
-------- Original message --------From: Aleix Pol <bugzilla_noreply@kde.org> Date: 2020-03-11  5:15 AM  (GMT-08:00) To: grcoukell@gmail.com Subject: [Discover] [Bug 375913] KDE Discover crashes on launch in QSGRenderLoop::handleContextCreationFailure() https://bugs.kde.org/show_bug.cgi?id=375913Aleix Pol <aleixpol@kde.org> changed:           What    |Removed                     |Added----------------------------------------------------------------------------         Resolution|DOWNSTREAM                  |---     Ever confirmed|0                           |1             Status|RESOLVED                    |REOPENED--- Comment #51 from Aleix Pol <aleixpol@kde.org> ---We still crash here, we better handle it somehow.I recently learned about this behaviour, I'll try to see if we can handle itsomehow, although it's still a problem between the driver and Qtmiscommunicating.-- You are receiving this mail because:You are on the CC list for the bug.
Comment 56 postix 2020-03-13 10:49:43 UTC 
(In reply to Thunder from comment #54)
> How do i stop these bug emails i've been getting them for years now and the
> bug is already gone, also i'm on arch and gnome now please stop.

There's a checkbox on the top right:
> Ignore Bug Mail: 	(never email me about this bug) 
Check it and click on "save changes".
Comment 57 Aleix Pol 2020-03-15 19:52:49 UTC 
Git commit 6177c81d04a7490de558ab5f266d4a81f2fb8f20 by Aleix Pol.
Committed on 15/03/2020 at 19:52.
Pushed by apol into branch 'master'.

Allow providing an error message from the application

Summary:
Allows us keep the message provided by QQuickWindow::sceneGraphError to later have on our bug reports.
https://doc.qt.io/qt-5/qquickwindow.html#sceneGraphError
These are generally problems at the OpenGL level that the user will usually be unable to take action on.

Test Plan: See D27985

Reviewers: #frameworks, sitter, dfaure

Reviewed By: dfaure

Subscribers: dfaure, kde-frameworks-devel

Tags: #frameworks

Differential Revision: https://phabricator.kde.org/D27986

M  +8    -0    src/kcrash.cpp
M  +8    -0    src/kcrash.h

https://commits.kde.org/kcrash/6177c81d04a7490de558ab5f266d4a81f2fb8f20
Comment 58 Aleix Pol 2020-03-15 19:53:50 UTC 
Git commit 39ed9cf6449ef4a57054504f7817696715ab233f by Aleix Pol.
Committed on 15/03/2020 at 19:53.
Pushed by apol into branch 'master'.

Include s_kcrashErrorMessage in our traces

Summary: CCBUG: 375913

Test Plan: Called `kill -SIGSEGV plasma-discover` and got to see the string I passed.

Reviewers: #frameworks, sitter

Reviewed By: sitter

Subscribers: plasma-devel

Tags: #plasma

Differential Revision: https://phabricator.kde.org/D27985

M  +1    -1    src/data/debuggers/internal/gdbrc
M  +1    -1    src/data/debuggers/internal/lldbrc
M  +12   -2    src/tests/crashtest/crashtest.cpp

https://commits.kde.org/drkonqi/39ed9cf6449ef4a57054504f7817696715ab233f
Comment 59 Nate Graham 2020-04-17 17:42:41 UTC 
*** Bug 420200 has been marked as a duplicate of this bug. ***
Comment 60 Nate Graham 2020-05-01 14:00:23 UTC 
*** Bug 420845 has been marked as a duplicate of this bug. ***
Comment 61 Nate Graham 2020-05-01 14:12:06 UTC 
*** Bug 420828 has been marked as a duplicate of this bug. ***
Comment 62 Christoph Feck 2020-05-12 11:46:31 UTC 
*** Bug 421380 has been marked as a duplicate of this bug. ***
Comment 63 Christoph Feck 2020-05-12 11:46:46 UTC 
*** Bug 420938 has been marked as a duplicate of this bug. ***
Comment 64 Christoph Feck 2020-05-12 11:47:05 UTC 
*** Bug 420648 has been marked as a duplicate of this bug. ***
Comment 65 Christoph Feck 2020-05-12 11:47:41 UTC 
*** Bug 419051 has been marked as a duplicate of this bug. ***
Comment 66 Christoph Feck 2020-05-12 11:52:44 UTC 
*** Bug 421090 has been marked as a duplicate of this bug. ***
Comment 67 javaman07 2020-07-01 14:22:48 UTC 
*** Bug 423743 has been marked as a duplicate of this bug. ***
Comment 68 Christoph Feck 2020-07-01 14:46:06 UTC 
*** Bug 423742 has been marked as a duplicate of this bug. ***
Comment 69 Christoph Feck 2020-07-01 14:50:26 UTC 
Aleix, this bug is caused by a mismatch between NVIDIA kernel module and driver, caused by a missing reboot after installing/updating either of them.

I am not sure how you plan to handle it.

See also bug 346519 and bug 364593.
Comment 70 javaman07 2020-07-01 15:28:49 UTC 
In regards to the missing reboot causing a mismatch between kernel and driver.

One of the benefits of Linux is the reduced need for a reboot. If indeed kernel updates every few weeks necessitates a reboot, then that reduces that benefit.

Also, only some programs are affected by this, KDE Discover and systemsettings5; however most other programs I use are not affected by this kernel/driver mismatch; ie: Firefox, Keepass, Thunderbird, Filelight, Chrome, Konsole, PulseEffects, VirtualBox, RStudio, GIMP, Lincity-NG, Battle for Wesnoth, Armada: Modern Tanks, Remmina, Google Earth. Several of those are 3D applications, which I would assume to be more dependent on the Nvidia driver than 2D applications.
Comment 71 Nate Graham 2020-07-01 18:23:58 UTC 
If you're upset about this, the people to complain to are at NVIDIA, for making a reboot required to avoid weird graphics issues after re-installing or updating the drivers.
Comment 72 Nate Graham 2020-07-02 00:31:48 UTC 
*** Bug 423627 has been marked as a duplicate of this bug. ***
Comment 73 Nate Graham 2020-07-02 00:51:20 UTC 
*** Bug 423663 has been marked as a duplicate of this bug. ***
Comment 74 jedihawkk 2020-07-03 01:17:02 UTC 
Ran update manually, updated the proprietary Nvidia drivers, rebooted, now all seems well.  Have not yet removed the proprietary Nvidia drivers, but I will if I continue to have problems.
Comment 75 Christoph Feck 2020-07-03 20:16:46 UTC 
*** Bug 421988 has been marked as a duplicate of this bug. ***
Comment 76 s.d.mateja 2020-07-04 16:39:24 UTC 
Created attachment 129897 [details]
New crash information added by DrKonqi

plasma-discover (5.18.5) using Qt 5.12.8

- What I was doing when the application crashed:
Firefox was running
- Custom settings of the application:
-recently changed the user icon
- i noticed that the folders icons on desctop are not loading propely (lost texture), had to manualy move them to refresh. Problem with texture was solved this way.

-- Backtrace (Reduced):
#6  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#7  0x00007f7a7b7ea859 in __GI_abort () at abort.c:79
#8  0x00007f7a7bc1faad in QMessageLogger::fatal(char const*, ...) const () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x00007f7a7d8c8065 in QSGRenderLoop::handleContextCreationFailure(QQuickWindow*, bool) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5
[...]
#12 0x00007f7a7c7a09ad in QWindow::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5
Comment 77 eitan 2020-11-04 06:48:01 UTC 
It would be nice, as a user, if instead of just crashing, I got a notification like, "Qt apps cannot run until you restart your computer to finish updating Nvidia drivers"
Comment 78 Nate Graham 2020-11-04 19:42:55 UTC 
*** Bug 428480 has been marked as a duplicate of this bug. ***
Comment 79 Christoph Feck 2020-11-05 05:08:07 UTC 
*** Bug 427885 has been marked as a duplicate of this bug. ***
Comment 80 Nate Graham 2020-11-09 18:24:27 UTC 
*** Bug 428876 has been marked as a duplicate of this bug. ***
Comment 81 Nate Graham 2020-11-24 16:44:59 UTC 
*** Bug 429591 has been marked as a duplicate of this bug. ***
Comment 82 Christoph Feck 2020-11-24 20:02:12 UTC 
> Qt apps cannot run until you restart your computer to finish updating Nvidia drivers

OpenGL apps cannot run until you restart. This notification could be shown by the installer/updater of the NVIDIA driver and the kernel, but I doubt distributions are keen to work around defiencies of a closed-source driver.

I still don't understand how Discover maintainers to plan to address this issue.
Comment 83 Nate Graham 2020-12-01 01:33:41 UTC 
*** Bug 429661 has been marked as a duplicate of this bug. ***
Comment 84 phd 2020-12-01 04:05:36 UTC 
@ javaman07

> Also, only some programs are affected by this, KDE Discover and
> systemsettings5; however most other programs I use are not affected by
> this kernel/driver mismatch; ie: [...], VirtualBox, [...]

That's not true. After upgrading nvidia drivers I wasn't able to run any
VirtualBox machines. It complained about 'vga' module and refused to start.
Reboot fixed the problem.
Comment 85 Nate Graham 2020-12-16 21:36:27 UTC 
Git commit 090610124d4650150af49a8e30f6b77ad9803dfe by Nate Graham, on behalf of Piotr Henryk Dabrowski.
Committed on 16/12/2020 at 21:35.
Pushed by ngraham into branch 'master'.

[KQuickAddons] QtQuickSettings::checkBackend() for fallback to software backend

Fixes very annoying crashes of QtQuick KDE applications:
ksmserver-logout-greeter, krunner (if not running before), and others
occuring when the OpenGL driver stops being available (e.g. on upgrade).

This issue often occurs after upgrading graphic drivers, preventing reboot,
which in turn is needed for the drivers to work and not cause this crash.

No changes are required in the above applications, as they all already use
KQuickAddons::QtQuickSettings::init().
Related: bug 422995, bug 421493, bug 398199, bug 366156, bug 346519

M  +36   -3    src/quickaddons/qtquicksettings.cpp
M  +2    -1    src/quickaddons/qtquicksettings.h

https://invent.kde.org/frameworks/kdeclarative/commit/090610124d4650150af49a8e30f6b77ad9803dfe
Comment 86 Nate Graham 2021-01-07 17:38:06 UTC 
*** Bug 431253 has been marked as a duplicate of this bug. ***
Comment 87 Nate Graham 2021-01-07 18:00:03 UTC 
*** Bug 431246 has been marked as a duplicate of this bug. ***
Comment 88 Nate Graham 2021-01-07 18:17:53 UTC 
Re-opening and marking VHI since we still get many crashes from users. We currently have 63 duplicates.

Yes, Nvidia should fix it, and yes, users should reboot their systems after installing updates, but clearly these thing aren't happening. We need to come up with a way on the KDE side to keep users from hitting this.
Comment 89 Nate Graham 2021-01-07 18:20:40 UTC 
Oops, I forgot that https://invent.kde.org/frameworks/kdeclarative/commit/090610124d4650150af49a8e30f6b77ad9803dfe did in fact fix this, and the dupes are coming from people who don't have Frameworks 5.78 yet. Sorry for the noise.
Comment 90 phd 2021-01-09 23:53:15 UTC 
@Nate Graham

> [...] the dupes are coming from people who don't have Frameworks 5.78 yet.

And I guess the reports will still be coming for a long time. Especially when we have e.g. Kubuntu 20.04 LTS being stuck at Frameworks 5.68 [1] and Qt 5.12. Even the latest Kubuntu 20.10 provides outdated Frameworks 5.74 [2] and Qt 5.14.

Surely they can cherry-pick patches for their packages, but I'm not sure how likely this is to happen.

AFAIK KDE does not have LTS releases of Frameworks, nor point releases for them (something like 5.68.1), right?

I also wonder what is the history (and delay) of upgrades of KDE Frameworks (and also Qt) to new major versions in previous LTS releases of Ubuntu and distros like Opensuse or Fedora...

> https://invent.kde.org/frameworks/kdeclarative/commit/090610124d4650150af49a8e30f6b77ad9803dfe
> did in fact fix this

Do you know of any feedback from users who have this shipped?
(I guess the only users at the moment are those of KDE Neon Dev?)
Does it solve the problems for everyone and does it not cause any issues?

[1] https://packages.ubuntu.com/pl/focal/libkf5declarative5
[2] https://packages.ubuntu.com/pl/groovy/libkf5declarative5
Comment 91 Unknown 2021-01-10 01:12:04 UTC 
I can confirm that the kdeclarative patch works running Arch Linux (installed specifically the kdeclarative 5.78 package from the testing repos [1]). Downgrading back to 5.77 allows the error to reoccur.
It seems to be successfully falling back to the software backend if I watch kernel logs. As far as I can tell, there are no obvious issues.

[1]: https://archlinux.org/packages/testing/x86_64/kdeclarative/
Comment 92 Nate Graham 2021-02-01 17:16:14 UTC 
*** Bug 432373 has been marked as a duplicate of this bug. ***
Comment 93 davidnyc16 2021-03-09 04:59:49 UTC 
Created attachment 136508 [details]
New crash information added by DrKonqi

plasma-discover (5.18.5) using Qt 5.12.8

- What I was doing when the application crashed: trying to restart the computer

- Unusual behavior I noticed: cannot use keyboard prompts like crtl alt dtl for restarting or turning off the computer

- Custom settings of the application: none

-- Backtrace (Reduced):
#6  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#7  0x00007fae9aece859 in __GI_abort () at abort.c:79
[...]
#9  0x00007fae9cfac065 in QSGRenderLoop::handleContextCreationFailure(QQuickWindow*, bool) () at /lib/x86_64-linux-gnu/libQt5Quick.so.5
[...]
#12 0x00007fae9be849ad in QWindow::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Gui.so.5
#13 0x00007fae9d02f159 in QQuickWindow::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Quick.so.5
Comment 94 phd 2021-03-09 08:41:37 UTC 
@davidnyc16
From your attachment:
> Frameworks Version: 5.68.0
The fix was released in KDE Frameworks 5.78. Please upgrade.
Comment 95 SkZ 2021-04-26 14:07:06 UTC 
Created attachment 137926 [details]
New crash information added by DrKonqi

plasma-discover (5.18.5) using Qt 5.12.8

- What I was doing when the application crashed:
opening discover through "new updates" notification and through the manu, after awaking from sleep mode

- Unusual behavior I noticed:
I upgraded from 16.04 to 18.04 and to 20.04. This left several problems
Previously I have managed to update packeages, so the upgrade is not a direct cause.
Also "System settings" is crashing continously

-- Backtrace (Reduced):
#6  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#7  0x00007fc77c175859 in __GI_abort () at abort.c:79
#8  0x00007fc77c5aaaad in QMessageLogger::fatal(char const*, ...) const () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x00007fc77e253065 in QSGRenderLoop::handleContextCreationFailure(QQuickWindow*, bool) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
[...]
#12 0x00007fc77d12b9ad in QWindow::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
Comment 96 phd 2021-04-27 07:05:17 UTC 
@SkZ
After upgrading your system (especially graphic drivers) reboot the computer. This should solve those crashes.
Please replay if this is the case.

You need KDE Frameworks 5.78+ to have this issue fixed.
Ubuntu 20.04 and 20.10 come with an outdated version [1].
Only Ubuntu 21.04 provides recent enough release of KDE Frameworks.

[1] https://packages.ubuntu.com/search?keywords=libkf5declarative5&searchon=names
Comment 97 Nate Graham 2021-06-15 22:25:07 UTC 
*** Bug 438445 has been marked as a duplicate of this bug. ***
Comment 98 Nate Graham 2021-08-05 00:37:54 UTC 
*** Bug 440291 has been marked as a duplicate of this bug. ***
Comment 99 scordido 2021-10-10 12:01:08 UTC 
Created attachment 142298 [details]
New crash information added by DrKonqi

plasma-discover (5.22.5) using Qt 5.15.2

- Unusual behavior I noticed:

Discover crash everytime i try to open from the system tray everytime it shows that there's an update.

-- Backtrace (Reduced):
#4  0x00007f45a4879e34 in QQmlData::isSignalConnected(QAbstractDeclarativeData*, QObject const*, int) () from /lib64/libQt5Qml.so.5
#5  0x00007f45a3d49eda in void doActivate<false>(QObject*, int, void**) () from /lib64/libQt5Core.so.5
#6  0x00007f45312bc851 in QtPrivate::QFunctorSlotObject<RpmOstreeBackend::executeCheckUpdateProcess()::{lambda(int, QProcess::ExitStatus)#2}, 2, QtPrivate::List<int, QProcess::ExitStatus>, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) () from /usr/lib64/qt5/plugins/discover/rpmostree-backend.so
#7  0x00007f45a3d4a3a9 in void doActivate<false>(QObject*, int, void**) () from /lib64/libQt5Core.so.5
#8  0x00007f45a3c9de73 in QProcess::finished(int, QProcess::ExitStatus) () from /lib64/libQt5Core.so.5
Comment 100 Nate Graham 2022-02-07 18:31:15 UTC 
*** Bug 449751 has been marked as a duplicate of this bug. ***