Screensaver-Process does not terminate

Bug #1313082 reported by Ralph Scharpf on 2014-04-26
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kde-workspace (Ubuntu)

Bug Description

$ lsb_release -rd
Description: Ubuntu 14.04 LTS
Release: 14.04

  Installiert: 1.0.7-2
  Installationskandidat: 1.0.7-2
 *** 1.0.7-2 0
        500 trusty/universe amd64 Packages
        100 /var/lib/dpkg/status

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.

Ralph Scharpf (rscharpf) wrote :
Ralph Scharpf (rscharpf) wrote :

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.

affects: kcometen4 (Ubuntu) → kde-workspace (Ubuntu)
Ralph Scharpf (rscharpf) on 2014-05-03
affects: kde-workspace (Ubuntu) → kde-workspace
Ralph Scharpf (rscharpf) on 2014-05-03
affects: kde-workspace → kde-workspace (Ubuntu)
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers