lxlock terminates/crashes the session instead of screenlocking

Bug #1579699 reported by Hadmut Danisch
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
light-locker (Ubuntu)
Expired
High
Unassigned
lxsession (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Hi,

I noticed that when I use Control-Alt-L in order to lock the screen, I get a fresh login prompt and fresh session, the old session is terminated and lost.

~/.config/openbox/lubuntu-rc.xml shows that

lxsession-default lock

will be executed, thus calling lxlock, since this is set as the default application.

It does, however, not start a screen lock, but kill the session for whatever reason.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: lxsession 0.5.2-0ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CurrentDesktop: LXDE
Date: Mon May 9 12:08:26 2016
InstallationDate: Installed on 2016-04-22 (16 days ago)
InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420)
SourcePackage: lxsession
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Hadmut Danisch (hadmut) wrote :
Revision history for this message
Hadmut Danisch (hadmut) wrote :

Sorry, I just noticed that I've reported against the wrong package. lxlock just calls

light-locker-command -l

which causes the problem.

Revision history for this message
Hadmut Danisch (hadmut) wrote :

I've noticed that lxlock is just a script that calls light-locker-command, so it was wrong to report against lxsession.

affects: lxsession (Ubuntu) → light-locker (Ubuntu)
Revision history for this message
Hadmut Danisch (hadmut) wrote :

strace revealed how light-locker dies:

16329 write(2, "\n(light-locker:16329): Gdk-WARNING **: light-locker: Fatal IO error 11 (Die Ressource ist zur Zeit nicht verf\303\274gbar) on X server :1.\n\n", 134) = 134
16329 exit_group(1) = ?

There's more error messages like that in the logs:

lxsession-default-apps: Fatal IO error 11 (Die Ressource ist zur Zeit nicht verfügbar) on X server :0.0.

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in light-locker (Ubuntu):
status: New → Confirmed
Changed in light-locker (Ubuntu):
importance: Undecided → High
Revision history for this message
Anton Melser (melser-anton) wrote :

Hi,

I just wanted to report that the session crashes I was experiencing appear to have been transitory, and I am no longer able to reproduce. If it returns I will attempt to gather some further low-level info - I didn't confirm with strace or anything but all of the system characteristics described above apply to mine also.
Thanks,
Anton

Revision history for this message
Theo Linkspfeifer (lastonestanding) wrote :

Does "dm-tool switch-to-greeter" trigger the crash also?

Changed in light-locker (Ubuntu):
status: Confirmed → Incomplete
Changed in lxsession (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for light-locker (Ubuntu) because there has been no activity for 60 days.]

Changed in light-locker (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for lxsession (Ubuntu) because there has been no activity for 60 days.]

Changed in lxsession (Ubuntu):
status: Incomplete → Expired
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.