Bug 363289 - plasma and kactivitymonitord crash when a fourth VM is started in virt-manager
Summary: plasma and kactivitymonitord crash when a fourth VM is started in virt-manager
Status: RESOLVED WORKSFORME
Alias: None
Product: plasmashell
Classification: Plasma
Component: Containment (other bugs)
Version First Reported In: 5.6.3
Platform: Fedora RPMs Linux
: NOR major
Target Milestone: 1.0
Assignee: Sebastian Kügler
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2016-05-19 18:40 UTC by piconewton
Modified: 2018-10-29 02:02 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description piconewton 2016-05-19 18:40:40 UTC 
On a fedora 23 system with 65 GB of RAM and a 6 core I7 CPU, starting three VMs with virt-manager shows no issues. When a fourth is started, the wallpaper goes black and the task bar disappears. System must be shutdown to correct the issue.
Many more VMs can be started under gnome.

Reproducible: Always

Steps to Reproduce:
1. start four VMs with virt-manager
2. background goes black, everything else sems to work correctly
3.

Actual Results:  
Wallpaper went black.

Expected Results:  
No chnage in wallpaper
Comment 1 Alexander Mentyu 2017-12-08 17:06:49 UTC 
Can't reproduce in:

Distribution: KDE neon Developer Edition - Stable Branches
Plasma: 5.11.4
Frameworks: 5.41.0
Qt: 5.9.3
Kernel 4.10.0-40-generic
Comment 2 David Edmundson 2018-08-09 23:22:24 UTC 
Crashes need a backtrace or we can't do anything
Comment 3 Andrew Crouthamel 2018-09-28 03:40:02 UTC 
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Andrew Crouthamel 2018-10-29 02:02:06 UTC 
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!