-
-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
light-locker is broken on Juno #92
Comments
Unless you're a time traveler, you're certainly not running Juno Beta. Can we get your actual system information please? If you're installing development packages on another operating system, you should not expect to have a working system. Closing as "incomplete" |
I'm also experiencing this with an alpha build. btkostner@New-Caprica:~$ light-locker-command -l
** Message: 15:28:33.879: Received error message from the locker: GDBus.Error:org.freedesktop.DBus.Error.NotSupported: This method is not implemented btkostner@New-Caprica:~$ uname -a
Linux New-Caprica 4.15.0-12-generic #13-Ubuntu SMP Thu Mar 8 06:24:47 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux btkostner@New-Caprica:~$ light-locker --version
light-locker 1.8.0 |
Since we started using light-locker years ago I had to create a DPMS daemon to set values that light-locker expects/requires. However, it requires a patched GSD. Since components are getting upstreamed to other distros, this has become a point of controversy. I would like a cleaner way to accomplish the same goal but I have no idea what that is. I am holding off on "fixing" this bug for as long as possible. Patched GSD: https://bazaar.launchpad.net/~elementary-os/elementaryos/os-patch-gnome-settings-daemon-xenial/revision/2 elementary-dpms-helper: https://github.com/elementary/dpms-helper/blob/master/bin/elementary-dpms-helper |
Yeah, it would be nice to have a working screen lock without having to rely on gnome-settings-daemon patches (which I can't do on fedora, for example). |
Is there a way I can fix light-locker without having to patch gnome-settings-daemon? |
How to get this fix? |
This hotfix was it released? Because this error persists.
|
Any updates? ~
➜ light-locker-command -l
** Message: 20:45:23.309: Received error message from the locker: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.ScreenSaver was not provided by any .service files
|
@codygarver Screen is not Locking for me either
|
Still happens in Juno release. |
@codygarver any idea why people might still be experiencing this issue? |
One situation where this can happen is if |
Hello Cody, none of those packages are installed. This happens on a fresh Juno install, no extra packages added. I downloaded the .ISO 2 days ago from the elementary site, so the version is up to date. I tried once with the nvidia binary drivers I normally use; then reinstalled just using the nouveau driver, thinking about dpms having something to do, somehow. Problem persisted on both cases. |
Just to be certain, you're experiencing this error message, right?:
Can you post a log of your installed packages?:
It seems like something is preventing the lock from being possible, according to the error message, instead of being missing DPMS settings that set the timeout. |
I'll check the logs tonight, as there's no message displayed, along with my currently installed packages. Bear in mind that this happens with the default Juno installation, with or without additional system updates, restricted extras, and/or system updates (I've already tested all these scenarios by reinstalling from scratch, formatting partitions each time). My machine is a ThinkPad T410s (1st. gen i5 @ 2.53Mhz, Nvidia NVS3100M, 4 GB RAM). |
As requested, Since I needed to get some work done, I had to install packages and remove |
About the error message: I reinstalled
It's the same message. |
Hrm, I don't see anything obvious in the installed packages that could be breaking this. I'm curious what hardware others who are experiencing this issue have. In the meantime, I recommend you write an email payment@elementary.io and ask for a refund. |
I'll leave my hardware specs here, it may help pinning down the problem cause. |
@codygarver, I also have the same situation with locker. My system is a bit littered(I've been trying |
The problem occurs while I'm using the GPU is an NVidia NVS3100M |
Is this still an issue? It seems very stale (@tintou maybe you could close this) |
There are 2 problems I'm still experiencing while using the 1.- Locking the screen brings the user back to the login screen, right? Well, that login screen is at a lower resolution than the desktop's, as if somehow it weren't the original If this behavior should be described in another ticket, I can do so. Thanks for looking into this! 😄 |
Thanks. All of that sounds different than the op. It also seems they're considering replacing light-locker, but depending on the severity of the issues they could issue a bugfix still. |
@worldofpeace Will do. Thanks for looking into it! |
Closing as we've not had recent reports that match this issue, plus we've had significant greeter and session changes since it was reported. New issues can of course still be reported or this one can be re-opened if it's still relevant. |
Ok, as per @worldofpeace's suggestion, I've opened a related ongoing issue with the current greeter |
I'm getting the same error now when clicking on the lock button or when using keyboard shortcut. Here's some debug info: OS: elementary OS 5.1.7 Hera x86_64
Kernel: 5.8.5-050805-generic $ journalctl --since "2 min ago"
Sep 29 23:57:05 dude wingpanel[14742]: session_widgets_userbox_update_state: assertion 'self != NULL' failed
Sep 29 23:57:07 dude wingpanel[14742]: Indicator.vala:163: Unable to lock: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.ScreenSaver was not provided by any .service files $ light-locker-command -V
light-locker-command 1.8.0
$ light-locker-command -q
** Message: 00:22:43.618: Locker is not running! During restart I get Oct 01 20:55:15 dude light-locker[2132]: The program 'light-locker' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
(Details: serial 180 error_code 2 request_code 26 (core protocol) minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the GDK_SYNCHRONIZE environment
variable to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.) And then when trying to lock with ctrl+L
|
can not lock screen
asus@asus-K46CA:
$ light-locker-command -l$ light-locker-command -a** Message: 09:15:13.030: Received error message from the locker: GDBus.Error:org.freedesktop.DBus.Error.NotSupported: This method is not implemented
asus@asus-K46CA:
** Message: 09:16:37.186: Received error message from the locker: GDBus.Error:org.freedesktop.DBus.Error.NotSupported: This method is not implemented
light-locker not working
please help me
Juno Beta
The text was updated successfully, but these errors were encountered: