Continous crashing of kscreenlocker_greet

Bug #1450173 reported by Paul Cullum

This bug report will be marked for expiration in 32 days if no further activity occurs. (find out why)

22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
plasma-workspace (Ubuntu)
Incomplete
Critical
Unassigned
Nominated for Vivid by Alberto Salvia Novella

Bug Description

1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu
 Description: Ubuntu 15.04
 Release: 15.04

2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center
plasma-workspace:
  Installed: 4:5.2.2-0ubuntu3
  Candidate: 4:5.2.2-0ubuntu3
  Version table:
 *** 4:5.2.2-0ubuntu3 0
        500 http://ca.archive.ubuntu.com/ubuntu/ vivid/universe amd64 Packages
        100 /var/lib/dpkg/status

3) What you expected to happen
 That kscreenlocker_greet not continuously crash.

4) What happened instead
 kscreenlocker_greet crashes

I upgraded from 14.10 to 15.04 yesterday. Following the upgrade it seemed as though the load average seemed higher than it ought to be. While investigating what was going on I noticed that new apport processes were being spawned continuously. Looking in apport.log I found this was being written out at a fairly high rate:

ERROR: apport (pid 4310) Wed Apr 29 15:32:21 2015: debug: session gdbus call:
ERROR: apport (pid 4310) Wed Apr 29 15:32:21 2015: this executable already crashed 2 times, ignoring
ERROR: apport (pid 4314) Wed Apr 29 15:32:21 2015: called for pid 4313, signal 6, core limit 0
ERROR: apport (pid 4314) Wed Apr 29 15:32:21 2015: executable: /usr/lib/x86_64-linux-gnu/libexec/kscreenlocker_greet (command line "/usr/lib/x86_64-linux-gnu/libexec/kscreenlocker_greet --immediateLock --ksldfd 44")
ERROR: apport (pid 4314) Wed Apr 29 15:32:21 2015: gdbus call error: Error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files

ERROR: apport (pid 4314) Wed Apr 29 15:32:21 2015: debug: session gdbus call:
ERROR: apport (pid 4314) Wed Apr 29 15:32:21 2015: this executable already crashed 2 times, ignoring
ERROR: apport (pid 4318) Wed Apr 29 15:32:22 2015: called for pid 4317, signal 6, core limit 0
ERROR: apport (pid 4318) Wed Apr 29 15:32:22 2015: executable: /usr/lib/x86_64-linux-gnu/libexec/kscreenlocker_greet (command line "/usr/lib/x86_64-linux-gnu/libexec/kscreenlocker_greet --immediateLock --ksldfd 44")
ERROR: apport (pid 4318) Wed Apr 29 15:32:22 2015: gdbus call error: Error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files

ERROR: apport (pid 4318) Wed Apr 29 15:32:22 2015: debug: session gdbus call:
ERROR: apport (pid 4318) Wed Apr 29 15:32:22 2015: this executable already crashed 2 times, ignoring
ERROR: apport (pid 4322) Wed Apr 29 15:32:22 2015: called for pid 4321, signal 6, core limit 0
ERROR: apport (pid 4322) Wed Apr 29 15:32:22 2015: executable: /usr/lib/x86_64-linux-gnu/libexec/kscreenlocker_greet (command line "/usr/lib/x86_64-linux-gnu/libexec/kscreenlocker_greet --immediateLock --ksldfd 44")
ERROR: apport (pid 4322) Wed Apr 29 15:32:22 2015: gdbus call error: Error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files

ERROR: apport (pid 4322) Wed Apr 29 15:32:22 2015: debug: session gdbus call:
ERROR: apport (pid 4322) Wed Apr 29 15:32:22 2015: this executable already crashed 2 times, ignoring
ERROR: apport (pid 4326) Wed Apr 29 15:32:22 2015: called for pid 4325, signal 6, core limit 0
ERROR: apport (pid 4326) Wed Apr 29 15:32:22 2015: executable: /usr/lib/x86_64-linux-gnu/libexec/kscreenlocker_greet (command line "/usr/lib/x86_64-linux-gnu/libexec/kscreenlocker_greet --immediateLock --ksldfd 44")
ERROR: apport (pid 4326) Wed Apr 29 15:32:22 2015: gdbus call error: Error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: plasma-workspace 4:5.2.2-0ubuntu3
ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
Uname: Linux 3.19.0-15-generic x86_64
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
CurrentDesktop: KDE
Date: Wed Apr 29 15:32:39 2015
InstallationDate: Installed on 2012-10-18 (923 days ago)
InstallationMedia: Kubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120820.1)
SourcePackage: plasma-workspace
UpgradeStatus: Upgraded to vivid on 2015-04-28 (0 days ago)

Revision history for this message
Paul Cullum (paul-cullum) wrote :
Revision history for this message
Paul Cullum (paul-cullum) wrote :

I should add that I tried to upgrade to Plasma 5.3.0 (from ppa:kubuntu-ppa/backports) to see if that would fix the problem. It didn't. Then I had to downgrade back to 5.2.2 so that I could file the report against the official package.

Revision history for this message
Paul Cullum (paul-cullum) wrote :

Adding apport crash report.

Revision history for this message
Paul Cullum (paul-cullum) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in plasma-workspace (Ubuntu):
status: New → Confirmed
Changed in plasma-workspace (Ubuntu):
importance: Undecided → Critical
Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

Please:
  1. Report to <https://bugs.kde.org/>.
  2. Paste the new report URL here.
  3. Set this bug status back to "confirmed".

Thank you.

Changed in plasma-workspace (Ubuntu):
status: Confirmed → Incomplete
tags: added: asked-to-upstream
Revision history for this message
Manuel Quinteiro (mquinteiro) wrote :

Same here with Plasma 5.3.2

Revision history for this message
Scarlett Gately Moore (scarlettmoore) wrote :

This bug is very old, if it remains an issue please update the bug with info from a supported release.

no longer affects: kde-workspace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.