Screensaver-Process does not terminate
Bug #1313082 reported by
Ralph Scharpf
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| kde-workspace (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
$ lsb_release -rd
Description: Ubuntu 14.04 LTS
Release: 14.04
kcometen4:
Installiert: 1.0.7-2
Installations
Versionstabelle:
*** 1.0.7-2 0
500 http://
100 /var/lib/
Whenever the screensaver is unlocked a new instance of process kcometen4 keeps running. Each process is occupying about 15% of a core (4% of the whole CPU resource) and ~20MByte of RAM. I would expect that at maximum one process is spawned or that the process is terminated whe the scrrensaver exits.
Please find attached a screenshot of the tasklist.
Revision history for this message
| Ralph Scharpf (rscharpf) wrote | #1 |
Revision history for this message
| Ralph Scharpf (rscharpf) wrote | #2 |
Revision history for this message
| Ralph Scharpf (rscharpf) wrote | #3 |
| affects: | kcometen4 (Ubuntu) → kde-workspace (Ubuntu) |
| affects: | kde-workspace (Ubuntu) → kde-workspace |
| affects: | kde-workspace → kde-workspace (Ubuntu) |
To post a comment you must log in.
I investigated the problem deeper. The issues occurs on _ALL_ scrennsaver modules. The problem occurs _ONLY_ when the screensaver is started via timeout. A manually starting (lock screen) does not show the issue.
When multiple screensavers are running you can also see this on the monitor.