light-locker-settings does not start

Bug #1559735 reported by Tim Schaaf on 2016-03-20
This bug affects 19 people
Affects Status Importance Assigned to Milestone
light-locker-settings (Ubuntu)

Bug Description

Lubuntu Xenial Xerus (development branch) 16.04, daily release for 3/19/16
light-locker-settings version: 1.5.0-0ubuntu1
light-locker-settings does not start
source package: light-locker-settings

In Python 3.5 it looks like "psutil.get_pid_list()" changed to "psutil.pids". /usr/share/light-locker-settings/light-locker-settings/ needs to be updated.

I found this fix in a bug for menulibre: Bug # 1474484

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: light-locker-settings 1.5.0-0ubuntu1 [modified: usr/share/light-locker-settings/light-locker-settings/]
ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5
Uname: Linux 4.4.0-14-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CurrentDesktop: LXDE
Date: Sun Mar 20 10:19:59 2016
ExecutablePath: /usr/share/light-locker-settings/light-locker-settings/
InstallationDate: Installed on 2016-03-20 (0 days ago)
InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160319)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
 PATH=(custom, no user)
SourcePackage: light-locker-settings
UpgradeStatus: No upgrade log present (probably fresh install)

Tim Schaaf (timuntu) wrote :
Launchpad Janitor (janitor) wrote :

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

Changed in light-locker-settings (Ubuntu):
status: New → Confirmed
phroggster (phroggster) wrote :

Console output from running the impacted light-locker-settings (1.5.0-0ubuntu1) on Xubuntu 16.04 beta 1 is attached, as well as a diff showing the changes required to get light-locker-settings operational again. See API Changes for 2.0.0 under as reference.

phroggster (phroggster) wrote :

The attachment "light-locker-settings_python-psutil-newer-than-2.0.0.diff" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]

tags: added: patch
golisp (golisp) wrote :

Patch was manually tested by me on 16.04 (Lubuntu PPC), and it works. Thanks.

Changed in light-locker-settings (Ubuntu):
importance: Undecided → High
pinportal (pinportal) wrote :

I have Lubuntu 16.04 64bits and found this bug too.

Light Locker settings does not start, I click and nothing happens.

How can I solve this bug? Step by step.

Thank you very much!

Christian Pointner (equinox-i) wrote :

Changes in #3 fix the problem for me. Thanks!

Bump. We have a patch for this, someone just needs to merge it and upload a new package.

chesterman (chesterman86) wrote :

Can anyone point to me how to manually apply the patch in #3? I'm not a dev.

@chesterman86 Download the light-locker-settings_python-psutil-newer-than-2.0.0.diff file from post #3. Then run;

sudo patch /usr/share/light-locker-settings/light-locker-settings/ /<path_to_the_diff_file>/light-locker-settings_python-psutil-newer-than-2.0.0.diff

Make sure you use the correct <path_to_the_diff_file> which you downloaded. The resulting output in your terminal should say "patching file" and Light Locker Settings should work. If you couldn't patch it just try to edit the py file manually in the /usr/share/... directory by removing the lines with a - in front and adding lines with a + in front from the diff file.

LinuxFreak (bwvienna) wrote :

The patch at #3 worked for me today for Lubuntu 16.04 i386 32 Bit.
Who or how will put the patch available for sudo apt-get update?
regards AP

Umar (umarfq1996) wrote :

Hi, I am sorry if i am asking a silly question. I am new user joining ububtu (xubuntu).

I seem to have trouble downloading the patch file at #3. it shows me a text on a new tab when i click on it. How can i download it?

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers