| Summary: | KDE Discover crashes on launch in QSGRenderLoop::handleContextCreationFailure() | ||
|---|---|---|---|
| Product: | [Applications] Discover | Reporter: | jang <kde.org> |
| Component: | discover | Assignee: | phd <phd> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | a.omerarol, aer0usa, agentti002x, akikara, alpha_command, antiheld.dlehitna+kdebugs, arno.igne, arssbars14, ashley, c4rb0n_unit, damien.j.s, danikvasin, dave, david.landrith, davidnyc16, eaglexboy, eitan, eugene, flying-sheep, francesco.belladonna, francogpellegrini, fsandefur, gear259, grcoukell, jake, javaman07, jay+kde, jcamussi, jedihawkk, jonatanayllon, jsevold, jtzemp, kaifer741, kde-bugs, kdebug, kleber.romano, kortatu, lally.singh, lelelodi01, lewisgardner, lordjaba, lordman1982, luiz.spies, lukascech1, max, maxilous, mcfletch, mike.sparks, minhnguyenduc72, molly.moggins, nahuel.j.gareis, nate, natrox, nick.craig.law, null, os9dude, paletteguy, pansorg, phd, phil3email, phoenixrock86, postix, powerss456, rr.mariani, s.d.mateja, scordido, skz5k2, thunderboyu, tiagosouzareis97, tonyb, troelswittrupjensen, trufanovan, vinlark, warichter1, wodencafe |
| Priority: | VHI | Keywords: | drkonqi |
| Version: | 5.7.5 | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| See Also: |
https://bugs.kde.org/show_bug.cgi?id=364593 https://bugs.kde.org/show_bug.cgi?id=346519 https://bugs.kde.org/show_bug.cgi?id=437339 |
||
| 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
New crash information added by DrKonqi New crash information added by DrKonqi attachment-15973-0.html attachment-26084-0.html attachment-5869-0.html attachment-7392-0.html New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi |
||
|
Description
jang
2017-02-02 18:53:12 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
Please ask in a forum of your distribution how to fix the installation of the OpenGL drivers. *** Bug 375463 has been marked as a duplicate of this bug. *** *** Bug 377028 has been marked as a duplicate of this bug. *** *** Bug 380425 has been marked as a duplicate of this bug. *** *** Bug 383246 has been marked as a duplicate of this bug. *** *** Bug 383526 has been marked as a duplicate of this bug. *** *** Bug 372097 has been marked as a duplicate of this bug. *** *** Bug 368888 has been marked as a duplicate of this bug. *** *** Bug 367883 has been marked as a duplicate of this bug. *** *** Bug 385469 has been marked as a duplicate of this bug. *** 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
*** Bug 386160 has been marked as a duplicate of this bug. *** *** Bug 388504 has been marked as a duplicate of this bug. *** *** Bug 388764 has been marked as a duplicate of this bug. *** *** Bug 388875 has been marked as a duplicate of this bug. *** 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
*** Bug 392474 has been marked as a duplicate of this bug. *** *** Bug 392591 has been marked as a duplicate of this bug. *** *** Bug 394872 has been marked as a duplicate of this bug. *** *** Bug 398520 has been marked as a duplicate of this bug. *** *** Bug 398330 has been marked as a duplicate of this bug. *** *** Bug 398227 has been marked as a duplicate of this bug. *** *** Bug 399557 has been marked as a duplicate of this bug. *** *** Bug 399635 has been marked as a duplicate of this bug. *** *** Bug 399938 has been marked as a duplicate of this bug. *** *** Bug 401275 has been marked as a duplicate of this bug. *** *** Bug 403075 has been marked as a duplicate of this bug. *** *** Bug 405184 has been marked as a duplicate of this bug. *** *** Bug 405412 has been marked as a duplicate of this bug. *** *** Bug 405290 has been marked as a duplicate of this bug. *** *** Bug 405251 has been marked as a duplicate of this bug. *** *** Bug 405701 has been marked as a duplicate of this bug. *** *** Bug 405208 has been marked as a duplicate of this bug. *** *** Bug 405867 has been marked as a duplicate of this bug. *** 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. *** Bug 405748 has been marked as a duplicate of this bug. *** *** Bug 406091 has been marked as a duplicate of this bug. *** *** Bug 408868 has been marked as a duplicate of this bug. *** *** Bug 410323 has been marked as a duplicate of this bug. *** 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. *** Bug 409987 has been marked as a duplicate of this bug. *** *** Bug 413808 has been marked as a duplicate of this bug. *** *** Bug 415105 has been marked as a duplicate of this bug. *** *** Bug 415273 has been marked as a duplicate of this bug. *** *** Bug 415515 has been marked as a duplicate of this bug. *** *** Bug 415216 has been marked as a duplicate of this bug. *** *** Bug 417214 has been marked as a duplicate of this bug. *** *** Bug 417518 has been marked as a duplicate of this bug. *** *** Bug 417411 has been marked as a duplicate of this bug. *** 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. *** Bug 418652 has been marked as a duplicate of this bug. *** 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. 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. 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. (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". 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 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 *** Bug 420200 has been marked as a duplicate of this bug. *** *** Bug 420845 has been marked as a duplicate of this bug. *** *** Bug 420828 has been marked as a duplicate of this bug. *** *** Bug 421380 has been marked as a duplicate of this bug. *** *** Bug 420938 has been marked as a duplicate of this bug. *** *** Bug 420648 has been marked as a duplicate of this bug. *** *** Bug 419051 has been marked as a duplicate of this bug. *** *** Bug 421090 has been marked as a duplicate of this bug. *** *** Bug 423743 has been marked as a duplicate of this bug. *** *** Bug 423742 has been marked as a duplicate of this bug. *** 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. 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. 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. *** Bug 423627 has been marked as a duplicate of this bug. *** *** Bug 423663 has been marked as a duplicate of this bug. *** 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. *** Bug 421988 has been marked as a duplicate of this bug. *** 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
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" *** Bug 428480 has been marked as a duplicate of this bug. *** *** Bug 427885 has been marked as a duplicate of this bug. *** *** Bug 428876 has been marked as a duplicate of this bug. *** *** Bug 429591 has been marked as a duplicate of this bug. *** > 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.
*** Bug 429661 has been marked as a duplicate of this bug. *** @ 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.
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 *** Bug 431253 has been marked as a duplicate of this bug. *** *** Bug 431246 has been marked as a duplicate of this bug. *** 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. 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. @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 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/ *** Bug 432373 has been marked as a duplicate of this bug. *** 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
@davidnyc16
From your attachment:
> Frameworks Version: 5.68.0
The fix was released in KDE Frameworks 5.78. Please upgrade.
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
@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 *** Bug 438445 has been marked as a duplicate of this bug. *** *** Bug 440291 has been marked as a duplicate of this bug. *** 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
*** Bug 449751 has been marked as a duplicate of this bug. *** |