[opensuse-kde] Plasmashell “randomly” crashing
Hi all. Running TW with Nvidia proprietary drivers (384.59) on a GTX750 card, with kernel 4.12.4-1.g2a27bf2-default x86_64 (from the kernel/stable/standard repository). Every now and then, Plasmashell simply crashes and leaves me with a black screen and whatever apps were open at the time. Most recently (a few seconds ago) I had only google Chrome open, browsing fb. Nothing else special happening. Computer has been on for a couple of hours (uptime was 2:05) - instant black screen, no toolbar etc. Alt-F2, run Plasmashell and all is back to normal. According to Help ->About Kmail -> Libraries: KDE Frameworks 5.36.0 Qt 5.9.1 (built against 5.9.1) The xcb windowing system Rpm -qa | grep ‘plasma’ show: plasma5-pk-updates-0.2-7.3.x86_64 plasma5-defaults-openSUSE-42.1.1-22.1.noarch plasma5-workspace-branding-openSUSE-42.1.1-22.1.noarch plasma-nm5-ssh-5.10.4-1.1.x86_64 plasma-framework-devel-5.36.0-1.1.x86_64 plasma5-pa-5.10.4-1.1.x86_64 plasma-nm5-sstp-5.10.4-1.1.x86_64 plasma-theme-caledonia-1.5-2.10.noarch plasma-vault-lang-5.9.96-1.2.noarch plasma-nm5-iodine-5.10.4-1.1.x86_64 plasma-framework-5.36.0-1.1.x86_64 plasma-nm5-openconnect-5.10.4-1.1.x86_64 plasma5-desktop-5.10.4-1.1.x86_64 plasma-nm5-openswan-5.10.4-1.1.x86_64 plasma5-session-5.10.4-1.1.noarch plasmate-1.0-1.78.x86_64 plasma5-integration-plugin-5.10.4-1.1.x86_64 plasma-nm5-strongswan-5.10.4-1.1.x86_64 plasma-nm5-5.10.4-1.1.x86_64 plasma-theme-glassified-4.1.0-1.16.noarch plasma5-addons-5.10.4-1.1.x86_64 plasma-nm5-l2tp-5.10.4-1.1.x86_64 plasma-vault-5.9.96-1.2.x86_64 plasma5-theme-openSUSE-42.1.1-22.1.noarch patterns-kde-kde_plasma-20170319-6.1.x86_64 plasma5-openSUSE-42.1.1-22.1.noarch plasma5-workspace-devel-5.10.4-1.1.x86_64 plasma-nm5-vpnc-5.10.4-1.1.x86_64 plasma-nm5-openvpn-5.10.4-1.1.x86_64 plasma-theme-oxygen-17.04.3-1.2.x86_64 plasma-theme-helium-4.1.0-2.18.noarch plasma-framework-private-5.36.0-1.1.x86_64 plasma5-workspace-libs-5.10.4-1.1.x86_64 plasma-nm5-pptp-5.10.4-1.1.x86_64 plasma-framework-components-5.36.0-1.1.x86_64 plasma5-workspace-5.10.4-1.1.x86_64 Plasma5-pk-updates-lang-0.2-7.3.noarch All have been installed from the TW repo except plasma-theme-[caledonia| glassified|helium] from KDE:Extra (TW). I do have KDE:Extra (TW) enabled, primarily for apps that are not in the standard TW repo. I’m just making sure that they’re the only packages installed from KDE:Extra. This has been happening seemingly at random for a few weeks, with multiple updates of TW and a couple of different Nvidia driver versions. The Nvidia driver has usually been reinstalled after each update to make sure that none of its dependencies have been overwritten by kde or xorg updates (but the crashes have happened whether or not that has been done). Are there any logs that will perhaps give a clue as to the cause of the crash so that I can investigate and perhaps log a bug report? When it happens I don’t even get the KDE crash handler dialog pop up to have the opportunity to capture a stack trace, so not too sure where to start looking with this one. Regards, Rodney. -- ============================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au ============================================================== -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On dimanche, 6 août 2017 16.45:58 h CEST Rodney Baker wrote:
Hi all. Running TW with Nvidia proprietary drivers (384.59) on a GTX750 card, with kernel 4.12.4-1.g2a27bf2-default x86_64 (from the kernel/stable/standard repository). Every now and then, Plasmashell simply crashes and leaves me with a black screen and whatever apps were open at the time. Most recently (a few seconds ago) I had only google Chrome open, browsing fb. Nothing else special happening. Computer has been on for a couple of hours (uptime was 2:05) - instant black screen, no toolbar etc.
Alt-F2, run Plasmashell and all is back to normal.
According to Help ->About Kmail -> Libraries:
KDE Frameworks 5.36.0 Qt 5.9.1 (built against 5.9.1) The xcb windowing system
Rpm -qa | grep ‘plasma’ show:
plasma5-pk-updates-0.2-7.3.x86_64 plasma5-defaults-openSUSE-42.1.1-22.1.noarch plasma5-workspace-branding-openSUSE-42.1.1-22.1.noarch plasma-nm5-ssh-5.10.4-1.1.x86_64 plasma-framework-devel-5.36.0-1.1.x86_64 plasma5-pa-5.10.4-1.1.x86_64 plasma-nm5-sstp-5.10.4-1.1.x86_64 plasma-theme-caledonia-1.5-2.10.noarch plasma-vault-lang-5.9.96-1.2.noarch plasma-nm5-iodine-5.10.4-1.1.x86_64 plasma-framework-5.36.0-1.1.x86_64 plasma-nm5-openconnect-5.10.4-1.1.x86_64 plasma5-desktop-5.10.4-1.1.x86_64 plasma-nm5-openswan-5.10.4-1.1.x86_64 plasma5-session-5.10.4-1.1.noarch plasmate-1.0-1.78.x86_64 plasma5-integration-plugin-5.10.4-1.1.x86_64 plasma-nm5-strongswan-5.10.4-1.1.x86_64 plasma-nm5-5.10.4-1.1.x86_64 plasma-theme-glassified-4.1.0-1.16.noarch plasma5-addons-5.10.4-1.1.x86_64 plasma-nm5-l2tp-5.10.4-1.1.x86_64 plasma-vault-5.9.96-1.2.x86_64 plasma5-theme-openSUSE-42.1.1-22.1.noarch patterns-kde-kde_plasma-20170319-6.1.x86_64 plasma5-openSUSE-42.1.1-22.1.noarch plasma5-workspace-devel-5.10.4-1.1.x86_64 plasma-nm5-vpnc-5.10.4-1.1.x86_64 plasma-nm5-openvpn-5.10.4-1.1.x86_64 plasma-theme-oxygen-17.04.3-1.2.x86_64 plasma-theme-helium-4.1.0-2.18.noarch plasma-framework-private-5.36.0-1.1.x86_64 plasma5-workspace-libs-5.10.4-1.1.x86_64 plasma-nm5-pptp-5.10.4-1.1.x86_64 plasma-framework-components-5.36.0-1.1.x86_64 plasma5-workspace-5.10.4-1.1.x86_64 Plasma5-pk-updates-lang-0.2-7.3.noarch
All have been installed from the TW repo except plasma-theme-[caledonia| glassified|helium] from KDE:Extra (TW).
I do have KDE:Extra (TW) enabled, primarily for apps that are not in the standard TW repo. I’m just making sure that they’re the only packages installed from KDE:Extra.
This has been happening seemingly at random for a few weeks, with multiple updates of TW and a couple of different Nvidia driver versions. The Nvidia driver has usually been reinstalled after each update to make sure that none of its dependencies have been overwritten by kde or xorg updates (but the crashes have happened whether or not that has been done).
Are there any logs that will perhaps give a clue as to the cause of the crash so that I can investigate and perhaps log a bug report?
When it happens I don’t even get the KDE crash handler dialog pop up to have the opportunity to capture a stack trace, so not too sure where to start looking with this one.
Regards, Rodney.
Seems drkonqui is become useless with coredump (from systemd). And I would really like to be able to have the right backtrace. So fixing drkonqui to pick backtrace from coredump will be an enhancement, one day if you check dmesg you should see segfault of plasma now if you run a coredump list --no-pager you should see the list of crash handled by coredump. With a bit of chance, you can debug it with the help of coredump gdp PID (extracted from the previous list command) you will certainly have to install -debuginfo corresponding packages to have a full backtrace. If it happen in nvidia drivers, then no luck, except that most of the crash I've experimented was on non-lts nvidia drivers (aka post 384.59) Also you should be able to seen crash and errors in ~/.xsession-errors-\:0 Another way to see them live, next time plasmashell crash, try to restart it directly from konsole ... Hope all of this help you a bit in your free crash quest -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch Bareos Partner, openSUSE Member, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Monday, 7 August 2017 6:31:11 ACST Bruno Friedmann wrote:
Seems drkonqui is become useless with coredump (from systemd). And I would really like to be able to have the right backtrace. So fixing drkonqui to pick backtrace from coredump will be an enhancement, one day
if you check dmesg you should see segfault of plasma now if you run a coredump list --no-pager you should see the list of crash handled by coredump.
With a bit of chance, you can debug it with the help of
coredump gdp PID (extracted from the previous list command) you will certainly have to install -debuginfo corresponding packages to have a full backtrace.
If it happen in nvidia drivers, then no luck, except that most of the crash I've experimented was on non-lts nvidia drivers (aka post 384.59)
Also you should be able to seen crash and errors in ~/.xsession-errors-\:0
Another way to see them live, next time plasmashell crash, try to restart it directly from konsole ...
Hope all of this help you a bit in your free crash quest
Thanks, Bruno. That gives me somewhere to start, at least. :) R. -- ============================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au ============================================================== -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
participants (2)
-
Bruno Friedmann -
Rodney Baker