https://bugs.kde.org/show_bug.cgi?id=388390
Bug ID: 388390
Summary: Plasma crashes and restarts with no clear user
interaction
Product: plasmashell
Version: 5.8.7
Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: generic-crash
Assignee: plasma-b...@kde.org
Reporter: luke.mcdoug...@outlook.com
Target Milestone: 1.0
Created attachment 109604
--> https://bugs.kde.org/attachment.cgi?id=109604&action=edit
Generated crash report from the built-in crash reporting tool. Failed to submit
due to backtrace.
Application: plasmashell (5.8.7)
Qt Version: 5.6.2
Frameworks Version: 5.32.0
Operating System: Linux 4.4.103-36-default x86_64
Distribution: "openSUSE Leap 42.3"
-- Information about the crash:
- What I was doing when the application crashed:
No similar crashes had happened until I started Kmail and KDE's PIM services.
However, I also started HP's driver interface tool and had it open (this, now
that I think about it, is more likely at fault).
- Custom settings of the application:
No custom settings of Kmail or PIM services, however, I am using 1.5x desktop
scaling on Nvidia proprietary graphics, which seems to produce visual errors
with Kmail in particular. Possible that errors are occurring on the rendering
side of plasma. HP drivers did install a proprietary blob for a
network-attached scanner.
- Additional notes:
During use of the HP application, the entire desktop interface hung for ~2
second intervals when some menus were clicked (even when the contents were not
dynamic and had already been accessed). Crashing appears to have stopped after
the HP application closed.
Sorry that debug symbols were not included. I attempted to install them through
the Crash Reporting Assistant but the installation failed.
This format was generated with the built-in bug reporting tool, however, that
tool failed to submit the error. I have included the tool's exact txt output,
including duplicates of a lot of the comments here.
I cannot reproduce the crash. The crash occurred multiple sequential times. It
is unclear what has changed.
Report to https://bugs.kde.org/
--
You are receiving this mail because:
You are watching all bug changes.
