XUbuntu 18.10 light-locker wrong behavior Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)Adjust screen brightness doesn't work Xubuntu 13.04 xfce4 keyboard shortcut fn+f2/f3 Toshiba L840 laptopxubuntu 13.10 xfce4-power-manager not workingHow to show GNOME power preferences in Xubuntu 14.04?org.gnome.settings-daemon.plugins.power Settings Ignored in Xubuntu 14.04.1Xubuntu 15.04 Cannot Suspend when inactiveNeed to change Xubuntu(xfce) default suspend settingsXubuntu logs out on power button pressHow do I disable Xfce display power management in xubuntu 16.04 at the command line?xUbuntu: use pm-suspend to suspend the computerLock screen by xfce4-power-manager/light-locker by timeout
2001: A Space Odyssey's use of the song "Daisy Bell" (Bicycle Built for Two); life imitates art or vice-versa?
List of Python versions
English words in a non-english sci-fi novel
How to deal with a team lead who never gives me credit?
How does the particle を relate to the verb 行く in the structure「A を + B に行く」?
What's the purpose of writing one's academic biography in the third person?
Is the Standard Deduction better than Itemized when both are the same amount?
Extract all GPU name, model and GPU ram
Short Story with Cinderella as a Voo-doo Witch
Storing hydrofluoric acid before the invention of plastics
51k Euros annually for a family of 4 in Berlin: Is it enough?
What's the meaning of 間時肆拾貳 at a car parking sign
porting install scripts : can rpm replace apt?
Why aren't air breathing engines used as small first stages
What exactly is a "Meth" in Altered Carbon?
Do I really need recursive chmod to restrict access to a folder?
Why am I getting the error "non-boolean type specified in a context where a condition is expected" for this request?
String `!23` is replaced with `docker` in command line
Why was the term "discrete" used in discrete logarithm?
What LEGO pieces have "real-world" functionality?
When do you get frequent flier miles - when you buy, or when you fly?
Should I use a zero-interest credit card for a large one-time purchase?
Why is "Consequences inflicted." not a sentence?
Using et al. for a last / senior author rather than for a first author
XUbuntu 18.10 light-locker wrong behavior
Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)Adjust screen brightness doesn't work Xubuntu 13.04 xfce4 keyboard shortcut fn+f2/f3 Toshiba L840 laptopxubuntu 13.10 xfce4-power-manager not workingHow to show GNOME power preferences in Xubuntu 14.04?org.gnome.settings-daemon.plugins.power Settings Ignored in Xubuntu 14.04.1Xubuntu 15.04 Cannot Suspend when inactiveNeed to change Xubuntu(xfce) default suspend settingsXubuntu logs out on power button pressHow do I disable Xfce display power management in xubuntu 16.04 at the command line?xUbuntu: use pm-suspend to suspend the computerLock screen by xfce4-power-manager/light-locker by timeout
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
With XUbuntu 18.10 (pretty fresh install) when locking the system the monitor is immediately suspended; pressing any key or mouse button doesn't wake it. Pressing CTRL + ALT + F7 finally wakes the monitor and the message below is presented:
This session is locked
You'll be redirected to the unlock
dialog automatically in a few seconds
then the lock screen appears and everything goes as expected.
Another solution is to type the password (while the monitor is still blank) then press ENTER which then wakes the monitor and also unlocks the session (if the password is correctly typed, of course).
I have these settings (Display Power Management on or off and/or Automatically lock the session activated or not make no difference):
The expected behavior with Display Power Management on and Automatically lock the session activated is:
- when locking the system first the monitor should be still on
- the lock window should be presented
- after 10 min the monitor should go black
- after 15 min the monitor should sleep
- after 60 min the monitor should switch off
- when pressing any key or mouse the monitor should switch on and the lock window be presented
What should I do in order to obtain the desired behavior? also I don't want to avoid the problem by using xscreensaver
UPDATE
The same behavior is no matter what I choose for Display Power Management and/or Automatically lock the session.
With Power Manager unchecked in Session and Startup (Screen Locker still checked) the behavior is the same. I guess it's a Screen Locker (light-locker) issue.
This is the /var/log/syslog created when locking:
Apr 12 20:24:26 adrhc systemd[1]: Started /run/user/111 mount wrapper.
Apr 12 20:24:26 adrhc systemd[1]: Created slice User Slice of UID 111.
Apr 12 20:24:26 adrhc systemd[1]: Starting User Manager for UID 111...
Apr 12 20:24:26 adrhc systemd[1]: Started Session c9 of user lightdm.
Apr 12 20:24:26 adrhc systemd[21272]: Reached target Paths.
Apr 12 20:24:26 adrhc systemd[21272]: Listening on GnuPG network certificate management daemon.
Apr 12 20:24:26 adrhc systemd[21272]: Starting D-Bus User Message Bus Socket.
Apr 12 20:24:26 adrhc systemd[21272]: Listening on GnuPG cryptographic agent and passphrase cache.
Apr 12 20:24:26 adrhc systemd[21272]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Apr 12 20:24:26 adrhc systemd[21272]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Apr 12 20:24:26 adrhc systemd[21272]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Apr 12 20:24:26 adrhc systemd[21272]: Listening on Sound System.
Apr 12 20:24:26 adrhc systemd[21272]: Reached target Timers.
Apr 12 20:24:26 adrhc systemd[21272]: Listening on D-Bus User Message Bus Socket.
Apr 12 20:24:26 adrhc systemd[21272]: Reached target Sockets.
Apr 12 20:24:26 adrhc systemd[21272]: Reached target Basic System.
Apr 12 20:24:26 adrhc systemd[21272]: Reached target Default.
Apr 12 20:24:26 adrhc systemd[21272]: Startup finished in 33ms.
Apr 12 20:24:26 adrhc systemd[1]: Started User Manager for UID 111.
Apr 12 20:24:26 adrhc systemd[21272]: Started D-Bus User Message Bus.
Apr 12 20:24:26 adrhc dbus-daemon[21342]: [session uid=111 pid=21342] AppArmor D-Bus mediation is enabled
Apr 12 20:24:26 adrhc dbus-daemon[21342]: [session uid=111 pid=21342] Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service' requested by ':1.1' (uid=111 pid=21337 comm="/usr/sbin/lightdm-gtk-greeter " label="unconfined")
Apr 12 20:24:26 adrhc systemd[21272]: Starting Accessibility services bus...
Apr 12 20:24:26 adrhc dbus-daemon[21342]: [session uid=111 pid=21342] Successfully activated service 'org.a11y.Bus'
Apr 12 20:24:26 adrhc systemd[21272]: Started Accessibility services bus.
Apr 12 20:24:26 adrhc at-spi-bus-launcher[21343]: dbus-daemon[21348]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=111 pid=21337 comm="/usr/sbin/lightdm-gtk-greeter " label="unconfined")
Apr 12 20:24:26 adrhc dbus-daemon[21342]: [session uid=111 pid=21342] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.3' (uid=111 pid=21337 comm="/usr/sbin/lightdm-gtk-greeter " label="unconfined")
Apr 12 20:24:26 adrhc at-spi-bus-launcher[21343]: dbus-daemon[21348]: Successfully activated service 'org.a11y.atspi.Registry'
Apr 12 20:24:26 adrhc at-spi-bus-launcher[21343]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Apr 12 20:24:26 adrhc systemd[21272]: Starting Virtual filesystem service...
Apr 12 20:24:26 adrhc dbus-daemon[21342]: [session uid=111 pid=21342] Successfully activated service 'org.gtk.vfs.Daemon'
Apr 12 20:24:26 adrhc systemd[21272]: Started Virtual filesystem service.
Apr 12 20:24:57 adrhc systemd[1]: session-c9.scope: Killing process 21244 (lightdm) with signal SIGTERM.
Apr 12 20:24:57 adrhc systemd[1]: session-c9.scope: Killing process 21327 (gnome-keyring-d) with signal SIGTERM.
Apr 12 20:24:57 adrhc systemd[1]: session-c9.scope: Killing process 21336 (lightdm-greeter) with signal SIGTERM.
Apr 12 20:24:57 adrhc systemd[1]: session-c9.scope: Killing process 21337 (lightdm-gtk-gre) with signal SIGTERM.
Apr 12 20:24:57 adrhc systemd[1]: Stopping Session c9 of user lightdm.
Apr 12 20:24:57 adrhc systemd[1]: Stopped Session c9 of user lightdm.
Apr 12 20:24:57 adrhc systemd[1]: user-runtime-dir@111.service: Unit not needed anymore. Stopping.
Apr 12 20:24:57 adrhc systemd[1]: Stopping User Manager for UID 111...
Apr 12 20:24:57 adrhc systemd[21272]: Stopped target Default.
Apr 12 20:24:57 adrhc gvfsd[21352]: A connection to the bus can't be made
Apr 12 20:24:57 adrhc systemd[21272]: Stopping Accessibility services bus...
Apr 12 20:24:57 adrhc systemd[21272]: Stopping D-Bus User Message Bus...
Apr 12 20:24:57 adrhc systemd[21272]: Stopping Virtual filesystem service...
Apr 12 20:24:57 adrhc systemd[21272]: Stopped D-Bus User Message Bus.
Apr 12 20:24:57 adrhc systemd[21272]: Stopped Accessibility services bus.
Apr 12 20:24:57 adrhc systemd[21272]: Stopped Virtual filesystem service.
Apr 12 20:24:57 adrhc systemd[21272]: Stopped target Basic System.
Apr 12 20:24:57 adrhc systemd[21272]: Stopped target Paths.
Apr 12 20:24:57 adrhc systemd[21272]: Stopped target Timers.
Apr 12 20:24:57 adrhc systemd[21272]: Stopped target Sockets.
Apr 12 20:24:57 adrhc systemd[21272]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
Apr 12 20:24:57 adrhc systemd[21272]: Closed GnuPG cryptographic agent and passphrase cache.
Apr 12 20:24:57 adrhc systemd[21272]: Closed Sound System.
Apr 12 20:24:57 adrhc systemd[21272]: Closed GnuPG network certificate management daemon.
Apr 12 20:24:57 adrhc systemd[21272]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
Apr 12 20:24:57 adrhc systemd[21272]: Closed GnuPG cryptographic agent (ssh-agent emulation).
Apr 12 20:24:57 adrhc systemd[21272]: Closed D-Bus User Message Bus Socket.
Apr 12 20:24:57 adrhc systemd[21272]: Reached target Shutdown.
Apr 12 20:24:57 adrhc systemd[21272]: Starting Exit the Session...
Apr 12 20:24:57 adrhc systemd[1]: user-runtime-dir@111.service: Unit not needed anymore. Stopping.
Apr 12 20:24:57 adrhc systemd[1]: Stopped User Manager for UID 111.
Apr 12 20:24:57 adrhc systemd[1]: user-runtime-dir@111.service: Unit not needed anymore. Stopping.
Apr 12 20:24:57 adrhc systemd[1]: Stopping /run/user/111 mount wrapper...
Apr 12 20:24:57 adrhc systemd[1]: Removed slice User Slice of UID 111.
Apr 12 20:24:57 adrhc systemd[1]: Stopped /run/user/111 mount wrapper.
xfce4-power-manager
asked Apr 12 at 16:44
adrhcadrhc
18019
add a comment |
With XUbuntu 18.10 (pretty fresh install) when locking the system the monitor is immediately suspended; pressing any key or mouse button doesn't wake it. Pressing CTRL + ALT + F7 finally wakes the monitor and the message below is presented:
This session is locked
You'll be redirected to the unlock
dialog automatically in a few seconds
then the lock screen appears and everything goes as expected.
Another solution is to type the password (while the monitor is still blank) then press ENTER which then wakes the monitor and also unlocks the session (if the password is correctly typed, of course).
I have these settings (Display Power Management on or off and/or Automatically lock the session activated or not make no difference):
The expected behavior with Display Power Management on and Automatically lock the session activated is:
- when locking the system first the monitor should be still on
- the lock window should be presented
- after 10 min the monitor should go black
- after 15 min the monitor should sleep
- after 60 min the monitor should switch off
- when pressing any key or mouse the monitor should switch on and the lock window be presented
What should I do in order to obtain the desired behavior? also I don't want to avoid the problem by using xscreensaver
UPDATE
The same behavior is no matter what I choose for Display Power Management and/or Automatically lock the session.
With Power Manager unchecked in Session and Startup (Screen Locker still checked) the behavior is the same. I guess it's a Screen Locker (light-locker) issue.
This is the /var/log/syslog created when locking:
Apr 12 20:24:26 adrhc systemd[1]: Started /run/user/111 mount wrapper.
Apr 12 20:24:26 adrhc systemd[1]: Created slice User Slice of UID 111.
Apr 12 20:24:26 adrhc systemd[1]: Starting User Manager for UID 111...
Apr 12 20:24:26 adrhc systemd[1]: Started Session c9 of user lightdm.
Apr 12 20:24:26 adrhc systemd[21272]: Reached target Paths.
Apr 12 20:24:26 adrhc systemd[21272]: Listening on GnuPG network certificate management daemon.
Apr 12 20:24:26 adrhc systemd[21272]: Starting D-Bus User Message Bus Socket.
Apr 12 20:24:26 adrhc systemd[21272]: Listening on GnuPG cryptographic agent and passphrase cache.
Apr 12 20:24:26 adrhc systemd[21272]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Apr 12 20:24:26 adrhc systemd[21272]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Apr 12 20:24:26 adrhc systemd[21272]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Apr 12 20:24:26 adrhc systemd[21272]: Listening on Sound System.
Apr 12 20:24:26 adrhc systemd[21272]: Reached target Timers.
Apr 12 20:24:26 adrhc systemd[21272]: Listening on D-Bus User Message Bus Socket.
Apr 12 20:24:26 adrhc systemd[21272]: Reached target Sockets.
Apr 12 20:24:26 adrhc systemd[21272]: Reached target Basic System.
Apr 12 20:24:26 adrhc systemd[21272]: Reached target Default.
Apr 12 20:24:26 adrhc systemd[21272]: Startup finished in 33ms.
Apr 12 20:24:26 adrhc systemd[1]: Started User Manager for UID 111.
Apr 12 20:24:26 adrhc systemd[21272]: Started D-Bus User Message Bus.
Apr 12 20:24:26 adrhc dbus-daemon[21342]: [session uid=111 pid=21342] AppArmor D-Bus mediation is enabled
Apr 12 20:24:26 adrhc dbus-daemon[21342]: [session uid=111 pid=21342] Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service' requested by ':1.1' (uid=111 pid=21337 comm="/usr/sbin/lightdm-gtk-greeter " label="unconfined")
Apr 12 20:24:26 adrhc systemd[21272]: Starting Accessibility services bus...
Apr 12 20:24:26 adrhc dbus-daemon[21342]: [session uid=111 pid=21342] Successfully activated service 'org.a11y.Bus'
Apr 12 20:24:26 adrhc systemd[21272]: Started Accessibility services bus.
Apr 12 20:24:26 adrhc at-spi-bus-launcher[21343]: dbus-daemon[21348]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=111 pid=21337 comm="/usr/sbin/lightdm-gtk-greeter " label="unconfined")
Apr 12 20:24:26 adrhc dbus-daemon[21342]: [session uid=111 pid=21342] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.3' (uid=111 pid=21337 comm="/usr/sbin/lightdm-gtk-greeter " label="unconfined")
Apr 12 20:24:26 adrhc at-spi-bus-launcher[21343]: dbus-daemon[21348]: Successfully activated service 'org.a11y.atspi.Registry'
Apr 12 20:24:26 adrhc at-spi-bus-launcher[21343]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Apr 12 20:24:26 adrhc systemd[21272]: Starting Virtual filesystem service...
Apr 12 20:24:26 adrhc dbus-daemon[21342]: [session uid=111 pid=21342] Successfully activated service 'org.gtk.vfs.Daemon'
Apr 12 20:24:26 adrhc systemd[21272]: Started Virtual filesystem service.
Apr 12 20:24:57 adrhc systemd[1]: session-c9.scope: Killing process 21244 (lightdm) with signal SIGTERM.
Apr 12 20:24:57 adrhc systemd[1]: session-c9.scope: Killing process 21327 (gnome-keyring-d) with signal SIGTERM.
Apr 12 20:24:57 adrhc systemd[1]: session-c9.scope: Killing process 21336 (lightdm-greeter) with signal SIGTERM.
Apr 12 20:24:57 adrhc systemd[1]: session-c9.scope: Killing process 21337 (lightdm-gtk-gre) with signal SIGTERM.
Apr 12 20:24:57 adrhc systemd[1]: Stopping Session c9 of user lightdm.
Apr 12 20:24:57 adrhc systemd[1]: Stopped Session c9 of user lightdm.
Apr 12 20:24:57 adrhc systemd[1]: user-runtime-dir@111.service: Unit not needed anymore. Stopping.
Apr 12 20:24:57 adrhc systemd[1]: Stopping User Manager for UID 111...
Apr 12 20:24:57 adrhc systemd[21272]: Stopped target Default.
Apr 12 20:24:57 adrhc gvfsd[21352]: A connection to the bus can't be made
Apr 12 20:24:57 adrhc systemd[21272]: Stopping Accessibility services bus...
Apr 12 20:24:57 adrhc systemd[21272]: Stopping D-Bus User Message Bus...
Apr 12 20:24:57 adrhc systemd[21272]: Stopping Virtual filesystem service...
Apr 12 20:24:57 adrhc systemd[21272]: Stopped D-Bus User Message Bus.
Apr 12 20:24:57 adrhc systemd[21272]: Stopped Accessibility services bus.
Apr 12 20:24:57 adrhc systemd[21272]: Stopped Virtual filesystem service.
Apr 12 20:24:57 adrhc systemd[21272]: Stopped target Basic System.
Apr 12 20:24:57 adrhc systemd[21272]: Stopped target Paths.
Apr 12 20:24:57 adrhc systemd[21272]: Stopped target Timers.
Apr 12 20:24:57 adrhc systemd[21272]: Stopped target Sockets.
Apr 12 20:24:57 adrhc systemd[21272]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
Apr 12 20:24:57 adrhc systemd[21272]: Closed GnuPG cryptographic agent and passphrase cache.
Apr 12 20:24:57 adrhc systemd[21272]: Closed Sound System.
Apr 12 20:24:57 adrhc systemd[21272]: Closed GnuPG network certificate management daemon.
Apr 12 20:24:57 adrhc systemd[21272]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
Apr 12 20:24:57 adrhc systemd[21272]: Closed GnuPG cryptographic agent (ssh-agent emulation).
Apr 12 20:24:57 adrhc systemd[21272]: Closed D-Bus User Message Bus Socket.
Apr 12 20:24:57 adrhc systemd[21272]: Reached target Shutdown.
Apr 12 20:24:57 adrhc systemd[21272]: Starting Exit the Session...
Apr 12 20:24:57 adrhc systemd[1]: user-runtime-dir@111.service: Unit not needed anymore. Stopping.
Apr 12 20:24:57 adrhc systemd[1]: Stopped User Manager for UID 111.
Apr 12 20:24:57 adrhc systemd[1]: user-runtime-dir@111.service: Unit not needed anymore. Stopping.
Apr 12 20:24:57 adrhc systemd[1]: Stopping /run/user/111 mount wrapper...
Apr 12 20:24:57 adrhc systemd[1]: Removed slice User Slice of UID 111.
Apr 12 20:24:57 adrhc systemd[1]: Stopped /run/user/111 mount wrapper.
xfce4-power-manager
asked Apr 12 at 16:44
adrhcadrhc
18019
Disable lightlocker and install xscreensaver. That was the only answer I found that worked.
– Organic Marble
Apr 13 at 4:03
add a comment |
With XUbuntu 18.10 (pretty fresh install) when locking the system the monitor is immediately suspended; pressing any key or mouse button doesn't wake it. Pressing CTRL + ALT + F7 finally wakes the monitor and the message below is presented:
This session is locked
You'll be redirected to the unlock
dialog automatically in a few seconds
then the lock screen appears and everything goes as expected.
Another solution is to type the password (while the monitor is still blank) then press ENTER which then wakes the monitor and also unlocks the session (if the password is correctly typed, of course).
I have these settings (Display Power Management on or off and/or Automatically lock the session activated or not make no difference):
The expected behavior with Display Power Management on and Automatically lock the session activated is:
- when locking the system first the monitor should be still on
- the lock window should be presented
- after 10 min the monitor should go black
- after 15 min the monitor should sleep
- after 60 min the monitor should switch off
- when pressing any key or mouse the monitor should switch on and the lock window be presented
What should I do in order to obtain the desired behavior? also I don't want to avoid the problem by using xscreensaver
UPDATE
The same behavior is no matter what I choose for Display Power Management and/or Automatically lock the session.
With Power Manager unchecked in Session and Startup (Screen Locker still checked) the behavior is the same. I guess it's a Screen Locker (light-locker) issue.
This is the /var/log/syslog created when locking:
Apr 12 20:24:26 adrhc systemd[1]: Started /run/user/111 mount wrapper.
Apr 12 20:24:26 adrhc systemd[1]: Created slice User Slice of UID 111.
Apr 12 20:24:26 adrhc systemd[1]: Starting User Manager for UID 111...
Apr 12 20:24:26 adrhc systemd[1]: Started Session c9 of user lightdm.
Apr 12 20:24:26 adrhc systemd[21272]: Reached target Paths.
Apr 12 20:24:26 adrhc systemd[21272]: Listening on GnuPG network certificate management daemon.
Apr 12 20:24:26 adrhc systemd[21272]: Starting D-Bus User Message Bus Socket.
Apr 12 20:24:26 adrhc systemd[21272]: Listening on GnuPG cryptographic agent and passphrase cache.
Apr 12 20:24:26 adrhc systemd[21272]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Apr 12 20:24:26 adrhc systemd[21272]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Apr 12 20:24:26 adrhc systemd[21272]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Apr 12 20:24:26 adrhc systemd[21272]: Listening on Sound System.
Apr 12 20:24:26 adrhc systemd[21272]: Reached target Timers.
Apr 12 20:24:26 adrhc systemd[21272]: Listening on D-Bus User Message Bus Socket.
Apr 12 20:24:26 adrhc systemd[21272]: Reached target Sockets.
Apr 12 20:24:26 adrhc systemd[21272]: Reached target Basic System.
Apr 12 20:24:26 adrhc systemd[21272]: Reached target Default.
Apr 12 20:24:26 adrhc systemd[21272]: Startup finished in 33ms.
Apr 12 20:24:26 adrhc systemd[1]: Started User Manager for UID 111.
Apr 12 20:24:26 adrhc systemd[21272]: Started D-Bus User Message Bus.
Apr 12 20:24:26 adrhc dbus-daemon[21342]: [session uid=111 pid=21342] AppArmor D-Bus mediation is enabled
Apr 12 20:24:26 adrhc dbus-daemon[21342]: [session uid=111 pid=21342] Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service' requested by ':1.1' (uid=111 pid=21337 comm="/usr/sbin/lightdm-gtk-greeter " label="unconfined")
Apr 12 20:24:26 adrhc systemd[21272]: Starting Accessibility services bus...
Apr 12 20:24:26 adrhc dbus-daemon[21342]: [session uid=111 pid=21342] Successfully activated service 'org.a11y.Bus'
Apr 12 20:24:26 adrhc systemd[21272]: Started Accessibility services bus.
Apr 12 20:24:26 adrhc at-spi-bus-launcher[21343]: dbus-daemon[21348]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=111 pid=21337 comm="/usr/sbin/lightdm-gtk-greeter " label="unconfined")
Apr 12 20:24:26 adrhc dbus-daemon[21342]: [session uid=111 pid=21342] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.3' (uid=111 pid=21337 comm="/usr/sbin/lightdm-gtk-greeter " label="unconfined")
Apr 12 20:24:26 adrhc at-spi-bus-launcher[21343]: dbus-daemon[21348]: Successfully activated service 'org.a11y.atspi.Registry'
Apr 12 20:24:26 adrhc at-spi-bus-launcher[21343]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Apr 12 20:24:26 adrhc systemd[21272]: Starting Virtual filesystem service...
Apr 12 20:24:26 adrhc dbus-daemon[21342]: [session uid=111 pid=21342] Successfully activated service 'org.gtk.vfs.Daemon'
Apr 12 20:24:26 adrhc systemd[21272]: Started Virtual filesystem service.
Apr 12 20:24:57 adrhc systemd[1]: session-c9.scope: Killing process 21244 (lightdm) with signal SIGTERM.
Apr 12 20:24:57 adrhc systemd[1]: session-c9.scope: Killing process 21327 (gnome-keyring-d) with signal SIGTERM.
Apr 12 20:24:57 adrhc systemd[1]: session-c9.scope: Killing process 21336 (lightdm-greeter) with signal SIGTERM.
Apr 12 20:24:57 adrhc systemd[1]: session-c9.scope: Killing process 21337 (lightdm-gtk-gre) with signal SIGTERM.
Apr 12 20:24:57 adrhc systemd[1]: Stopping Session c9 of user lightdm.
Apr 12 20:24:57 adrhc systemd[1]: Stopped Session c9 of user lightdm.
Apr 12 20:24:57 adrhc systemd[1]: user-runtime-dir@111.service: Unit not needed anymore. Stopping.
Apr 12 20:24:57 adrhc systemd[1]: Stopping User Manager for UID 111...
Apr 12 20:24:57 adrhc systemd[21272]: Stopped target Default.
Apr 12 20:24:57 adrhc gvfsd[21352]: A connection to the bus can't be made
Apr 12 20:24:57 adrhc systemd[21272]: Stopping Accessibility services bus...
Apr 12 20:24:57 adrhc systemd[21272]: Stopping D-Bus User Message Bus...
Apr 12 20:24:57 adrhc systemd[21272]: Stopping Virtual filesystem service...
Apr 12 20:24:57 adrhc systemd[21272]: Stopped D-Bus User Message Bus.
Apr 12 20:24:57 adrhc systemd[21272]: Stopped Accessibility services bus.
Apr 12 20:24:57 adrhc systemd[21272]: Stopped Virtual filesystem service.
Apr 12 20:24:57 adrhc systemd[21272]: Stopped target Basic System.
Apr 12 20:24:57 adrhc systemd[21272]: Stopped target Paths.
Apr 12 20:24:57 adrhc systemd[21272]: Stopped target Timers.
Apr 12 20:24:57 adrhc systemd[21272]: Stopped target Sockets.
Apr 12 20:24:57 adrhc systemd[21272]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
Apr 12 20:24:57 adrhc systemd[21272]: Closed GnuPG cryptographic agent and passphrase cache.
Apr 12 20:24:57 adrhc systemd[21272]: Closed Sound System.
Apr 12 20:24:57 adrhc systemd[21272]: Closed GnuPG network certificate management daemon.
Apr 12 20:24:57 adrhc systemd[21272]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
Apr 12 20:24:57 adrhc systemd[21272]: Closed GnuPG cryptographic agent (ssh-agent emulation).
Apr 12 20:24:57 adrhc systemd[21272]: Closed D-Bus User Message Bus Socket.
Apr 12 20:24:57 adrhc systemd[21272]: Reached target Shutdown.
Apr 12 20:24:57 adrhc systemd[21272]: Starting Exit the Session...
Apr 12 20:24:57 adrhc systemd[1]: user-runtime-dir@111.service: Unit not needed anymore. Stopping.
Apr 12 20:24:57 adrhc systemd[1]: Stopped User Manager for UID 111.
Apr 12 20:24:57 adrhc systemd[1]: user-runtime-dir@111.service: Unit not needed anymore. Stopping.
Apr 12 20:24:57 adrhc systemd[1]: Stopping /run/user/111 mount wrapper...
Apr 12 20:24:57 adrhc systemd[1]: Removed slice User Slice of UID 111.
Apr 12 20:24:57 adrhc systemd[1]: Stopped /run/user/111 mount wrapper.
xfce4-power-manager
asked Apr 12 at 16:44
adrhcadrhc
18019
With XUbuntu 18.10 (pretty fresh install) when locking the system the monitor is immediately suspended; pressing any key or mouse button doesn't wake it. Pressing CTRL + ALT + F7 finally wakes the monitor and the message below is presented:
This session is locked
You'll be redirected to the unlock
dialog automatically in a few seconds
then the lock screen appears and everything goes as expected.
Another solution is to type the password (while the monitor is still blank) then press ENTER which then wakes the monitor and also unlocks the session (if the password is correctly typed, of course).
I have these settings (Display Power Management on or off and/or Automatically lock the session activated or not make no difference):
The expected behavior with Display Power Management on and Automatically lock the session activated is:
- when locking the system first the monitor should be still on
- the lock window should be presented
- after 10 min the monitor should go black
- after 15 min the monitor should sleep
- after 60 min the monitor should switch off
- when pressing any key or mouse the monitor should switch on and the lock window be presented
What should I do in order to obtain the desired behavior? also I don't want to avoid the problem by using xscreensaver
UPDATE
The same behavior is no matter what I choose for Display Power Management and/or Automatically lock the session.
With Power Manager unchecked in Session and Startup (Screen Locker still checked) the behavior is the same. I guess it's a Screen Locker (light-locker) issue.
This is the /var/log/syslog created when locking:
Apr 12 20:24:26 adrhc systemd[1]: Started /run/user/111 mount wrapper.
Apr 12 20:24:26 adrhc systemd[1]: Created slice User Slice of UID 111.
Apr 12 20:24:26 adrhc systemd[1]: Starting User Manager for UID 111...
Apr 12 20:24:26 adrhc systemd[1]: Started Session c9 of user lightdm.
Apr 12 20:24:26 adrhc systemd[21272]: Reached target Paths.
Apr 12 20:24:26 adrhc systemd[21272]: Listening on GnuPG network certificate management daemon.
Apr 12 20:24:26 adrhc systemd[21272]: Starting D-Bus User Message Bus Socket.
Apr 12 20:24:26 adrhc systemd[21272]: Listening on GnuPG cryptographic agent and passphrase cache.
Apr 12 20:24:26 adrhc systemd[21272]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Apr 12 20:24:26 adrhc systemd[21272]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Apr 12 20:24:26 adrhc systemd[21272]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Apr 12 20:24:26 adrhc systemd[21272]: Listening on Sound System.
Apr 12 20:24:26 adrhc systemd[21272]: Reached target Timers.
Apr 12 20:24:26 adrhc systemd[21272]: Listening on D-Bus User Message Bus Socket.
Apr 12 20:24:26 adrhc systemd[21272]: Reached target Sockets.
Apr 12 20:24:26 adrhc systemd[21272]: Reached target Basic System.
Apr 12 20:24:26 adrhc systemd[21272]: Reached target Default.
Apr 12 20:24:26 adrhc systemd[21272]: Startup finished in 33ms.
Apr 12 20:24:26 adrhc systemd[1]: Started User Manager for UID 111.
Apr 12 20:24:26 adrhc systemd[21272]: Started D-Bus User Message Bus.
Apr 12 20:24:26 adrhc dbus-daemon[21342]: [session uid=111 pid=21342] AppArmor D-Bus mediation is enabled
Apr 12 20:24:26 adrhc dbus-daemon[21342]: [session uid=111 pid=21342] Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service' requested by ':1.1' (uid=111 pid=21337 comm="/usr/sbin/lightdm-gtk-greeter " label="unconfined")
Apr 12 20:24:26 adrhc systemd[21272]: Starting Accessibility services bus...
Apr 12 20:24:26 adrhc dbus-daemon[21342]: [session uid=111 pid=21342] Successfully activated service 'org.a11y.Bus'
Apr 12 20:24:26 adrhc systemd[21272]: Started Accessibility services bus.
Apr 12 20:24:26 adrhc at-spi-bus-launcher[21343]: dbus-daemon[21348]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=111 pid=21337 comm="/usr/sbin/lightdm-gtk-greeter " label="unconfined")
Apr 12 20:24:26 adrhc dbus-daemon[21342]: [session uid=111 pid=21342] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.3' (uid=111 pid=21337 comm="/usr/sbin/lightdm-gtk-greeter " label="unconfined")
Apr 12 20:24:26 adrhc at-spi-bus-launcher[21343]: dbus-daemon[21348]: Successfully activated service 'org.a11y.atspi.Registry'
Apr 12 20:24:26 adrhc at-spi-bus-launcher[21343]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Apr 12 20:24:26 adrhc systemd[21272]: Starting Virtual filesystem service...
Apr 12 20:24:26 adrhc dbus-daemon[21342]: [session uid=111 pid=21342] Successfully activated service 'org.gtk.vfs.Daemon'
Apr 12 20:24:26 adrhc systemd[21272]: Started Virtual filesystem service.
Apr 12 20:24:57 adrhc systemd[1]: session-c9.scope: Killing process 21244 (lightdm) with signal SIGTERM.
Apr 12 20:24:57 adrhc systemd[1]: session-c9.scope: Killing process 21327 (gnome-keyring-d) with signal SIGTERM.
Apr 12 20:24:57 adrhc systemd[1]: session-c9.scope: Killing process 21336 (lightdm-greeter) with signal SIGTERM.
Apr 12 20:24:57 adrhc systemd[1]: session-c9.scope: Killing process 21337 (lightdm-gtk-gre) with signal SIGTERM.
Apr 12 20:24:57 adrhc systemd[1]: Stopping Session c9 of user lightdm.
Apr 12 20:24:57 adrhc systemd[1]: Stopped Session c9 of user lightdm.
Apr 12 20:24:57 adrhc systemd[1]: user-runtime-dir@111.service: Unit not needed anymore. Stopping.
Apr 12 20:24:57 adrhc systemd[1]: Stopping User Manager for UID 111...
Apr 12 20:24:57 adrhc systemd[21272]: Stopped target Default.
Apr 12 20:24:57 adrhc gvfsd[21352]: A connection to the bus can't be made
Apr 12 20:24:57 adrhc systemd[21272]: Stopping Accessibility services bus...
Apr 12 20:24:57 adrhc systemd[21272]: Stopping D-Bus User Message Bus...
Apr 12 20:24:57 adrhc systemd[21272]: Stopping Virtual filesystem service...
Apr 12 20:24:57 adrhc systemd[21272]: Stopped D-Bus User Message Bus.
Apr 12 20:24:57 adrhc systemd[21272]: Stopped Accessibility services bus.
Apr 12 20:24:57 adrhc systemd[21272]: Stopped Virtual filesystem service.
Apr 12 20:24:57 adrhc systemd[21272]: Stopped target Basic System.
Apr 12 20:24:57 adrhc systemd[21272]: Stopped target Paths.
Apr 12 20:24:57 adrhc systemd[21272]: Stopped target Timers.
Apr 12 20:24:57 adrhc systemd[21272]: Stopped target Sockets.
Apr 12 20:24:57 adrhc systemd[21272]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
Apr 12 20:24:57 adrhc systemd[21272]: Closed GnuPG cryptographic agent and passphrase cache.
Apr 12 20:24:57 adrhc systemd[21272]: Closed Sound System.
Apr 12 20:24:57 adrhc systemd[21272]: Closed GnuPG network certificate management daemon.
Apr 12 20:24:57 adrhc systemd[21272]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
Apr 12 20:24:57 adrhc systemd[21272]: Closed GnuPG cryptographic agent (ssh-agent emulation).
Apr 12 20:24:57 adrhc systemd[21272]: Closed D-Bus User Message Bus Socket.
Apr 12 20:24:57 adrhc systemd[21272]: Reached target Shutdown.
Apr 12 20:24:57 adrhc systemd[21272]: Starting Exit the Session...
Apr 12 20:24:57 adrhc systemd[1]: user-runtime-dir@111.service: Unit not needed anymore. Stopping.
Apr 12 20:24:57 adrhc systemd[1]: Stopped User Manager for UID 111.
Apr 12 20:24:57 adrhc systemd[1]: user-runtime-dir@111.service: Unit not needed anymore. Stopping.
Apr 12 20:24:57 adrhc systemd[1]: Stopping /run/user/111 mount wrapper...
Apr 12 20:24:57 adrhc systemd[1]: Removed slice User Slice of UID 111.
Apr 12 20:24:57 adrhc systemd[1]: Stopped /run/user/111 mount wrapper.
xfce4-power-manager
xfce4-power-manager
asked Apr 12 at 16:44
adrhcadrhc
18019
asked Apr 12 at 16:44
adrhcadrhc
18019
edited Apr 12 at 21:41
adrhc
asked Apr 12 at 16:44
adrhcadrhc
18019
asked Apr 12 at 16:44
adrhcadrhc
18019
asked Apr 12 at 16:44
adrhcadrhc
18019
18019
Disable lightlocker and install xscreensaver. That was the only answer I found that worked.
– Organic Marble
Apr 13 at 4:03
add a comment |
Disable lightlocker and install xscreensaver. That was the only answer I found that worked.
– Organic Marble
Apr 13 at 4:03
Disable lightlocker and install xscreensaver. That was the only answer I found that worked.
– Organic Marble
Apr 13 at 4:03
Disable lightlocker and install xscreensaver. That was the only answer I found that worked.
– Organic Marble
Apr 13 at 4:03
add a comment |
1 Answer
1
active
oldest
votes
I do not have the actual solution of your problem yet but a temporary solution.
I found here a way to recover the situation without reboot the machine/LightDM.
In your tty1 Ctrl+Alt+F1, as root, type loginctl unlock-session [id], where [id] is the session id you get by running loginctl list-sessions.
If it doesn't work with the first ID, try with the other session IDs of your user account.
Try this as well.
sudo service lightdm restart
edited Apr 13 at 5:28
karel
61.1k13132155
answered Apr 12 at 17:21
Muntaha LiaqatMuntaha Liaqat
195
I already said that pressingCTRL + ALT + F7brings me to the unlock window.
– adrhc
Apr 12 at 17:29
I think you mistook it.... my command is change... its (Ctrl+Alt+F1), not F7
– Muntaha Liaqat
Apr 12 at 17:30
Well, what I mean is that your solution is more complicated or at least less comfortable than mine. Also is not the solution for the question I asked (see the question).
– adrhc
Apr 12 at 17:38
ok no problem... thank you for your reply.... I will search about it more...
– Muntaha Liaqat
Apr 12 at 17:40
@MuntahaLiaqat Welcome to AskUbuntu. Please take a look at the Markdown help page.
– Eric Carvalho
Apr 13 at 0:25
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "89"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1133341%2fxubuntu-18-10-light-locker-wrong-behavior%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I do not have the actual solution of your problem yet but a temporary solution.
I found here a way to recover the situation without reboot the machine/LightDM.
In your tty1 Ctrl+Alt+F1, as root, type loginctl unlock-session [id], where [id] is the session id you get by running loginctl list-sessions.
If it doesn't work with the first ID, try with the other session IDs of your user account.
Try this as well.
sudo service lightdm restart
edited Apr 13 at 5:28
karel
61.1k13132155
answered Apr 12 at 17:21
Muntaha LiaqatMuntaha Liaqat
195
I already said that pressingCTRL + ALT + F7brings me to the unlock window.
– adrhc
Apr 12 at 17:29
I think you mistook it.... my command is change... its (Ctrl+Alt+F1), not F7
– Muntaha Liaqat
Apr 12 at 17:30
Well, what I mean is that your solution is more complicated or at least less comfortable than mine. Also is not the solution for the question I asked (see the question).
– adrhc
Apr 12 at 17:38
ok no problem... thank you for your reply.... I will search about it more...
– Muntaha Liaqat
Apr 12 at 17:40
@MuntahaLiaqat Welcome to AskUbuntu. Please take a look at the Markdown help page.
– Eric Carvalho
Apr 13 at 0:25
add a comment |
I do not have the actual solution of your problem yet but a temporary solution.
I found here a way to recover the situation without reboot the machine/LightDM.
In your tty1 Ctrl+Alt+F1, as root, type loginctl unlock-session [id], where [id] is the session id you get by running loginctl list-sessions.
If it doesn't work with the first ID, try with the other session IDs of your user account.
Try this as well.
sudo service lightdm restart
edited Apr 13 at 5:28
karel
61.1k13132155
answered Apr 12 at 17:21
Muntaha LiaqatMuntaha Liaqat
195
I already said that pressingCTRL + ALT + F7brings me to the unlock window.
– adrhc
Apr 12 at 17:29
I think you mistook it.... my command is change... its (Ctrl+Alt+F1), not F7
– Muntaha Liaqat
Apr 12 at 17:30
Well, what I mean is that your solution is more complicated or at least less comfortable than mine. Also is not the solution for the question I asked (see the question).
– adrhc
Apr 12 at 17:38
ok no problem... thank you for your reply.... I will search about it more...
– Muntaha Liaqat
Apr 12 at 17:40
@MuntahaLiaqat Welcome to AskUbuntu. Please take a look at the Markdown help page.
– Eric Carvalho
Apr 13 at 0:25
add a comment |
I do not have the actual solution of your problem yet but a temporary solution.
I found here a way to recover the situation without reboot the machine/LightDM.
In your tty1 Ctrl+Alt+F1, as root, type loginctl unlock-session [id], where [id] is the session id you get by running loginctl list-sessions.
If it doesn't work with the first ID, try with the other session IDs of your user account.
Try this as well.
sudo service lightdm restart
edited Apr 13 at 5:28
karel
61.1k13132155
answered Apr 12 at 17:21
Muntaha LiaqatMuntaha Liaqat
195
I do not have the actual solution of your problem yet but a temporary solution.
I found here a way to recover the situation without reboot the machine/LightDM.
In your tty1 Ctrl+Alt+F1, as root, type loginctl unlock-session [id], where [id] is the session id you get by running loginctl list-sessions.
If it doesn't work with the first ID, try with the other session IDs of your user account.
Try this as well.
sudo service lightdm restart
edited Apr 13 at 5:28
karel
61.1k13132155
answered Apr 12 at 17:21
Muntaha LiaqatMuntaha Liaqat
195
edited Apr 13 at 5:28
karel
61.1k13132155
edited Apr 13 at 5:28
karel
61.1k13132155
edited Apr 13 at 5:28
karel
61.1k13132155
61.1k13132155
answered Apr 12 at 17:21
Muntaha LiaqatMuntaha Liaqat
195
answered Apr 12 at 17:21
Muntaha LiaqatMuntaha Liaqat
195
answered Apr 12 at 17:21
Muntaha LiaqatMuntaha Liaqat
195
195
I already said that pressingCTRL + ALT + F7brings me to the unlock window.
– adrhc
Apr 12 at 17:29
I think you mistook it.... my command is change... its (Ctrl+Alt+F1), not F7
– Muntaha Liaqat
Apr 12 at 17:30
Well, what I mean is that your solution is more complicated or at least less comfortable than mine. Also is not the solution for the question I asked (see the question).
– adrhc
Apr 12 at 17:38
ok no problem... thank you for your reply.... I will search about it more...
– Muntaha Liaqat
Apr 12 at 17:40
@MuntahaLiaqat Welcome to AskUbuntu. Please take a look at the Markdown help page.
– Eric Carvalho
Apr 13 at 0:25
add a comment |
I already said that pressingCTRL + ALT + F7brings me to the unlock window.
– adrhc
Apr 12 at 17:29
I think you mistook it.... my command is change... its (Ctrl+Alt+F1), not F7
– Muntaha Liaqat
Apr 12 at 17:30
Well, what I mean is that your solution is more complicated or at least less comfortable than mine. Also is not the solution for the question I asked (see the question).
– adrhc
Apr 12 at 17:38
ok no problem... thank you for your reply.... I will search about it more...
– Muntaha Liaqat
Apr 12 at 17:40
@MuntahaLiaqat Welcome to AskUbuntu. Please take a look at the Markdown help page.
– Eric Carvalho
Apr 13 at 0:25
I already said that pressing
CTRL + ALT + F7 brings me to the unlock window.– adrhc
Apr 12 at 17:29
I already said that pressing
CTRL + ALT + F7 brings me to the unlock window.– adrhc
Apr 12 at 17:29
I think you mistook it.... my command is change... its (Ctrl+Alt+F1), not F7
– Muntaha Liaqat
Apr 12 at 17:30
I think you mistook it.... my command is change... its (Ctrl+Alt+F1), not F7
– Muntaha Liaqat
Apr 12 at 17:30
Well, what I mean is that your solution is more complicated or at least less comfortable than mine. Also is not the solution for the question I asked (see the question).
– adrhc
Apr 12 at 17:38
Well, what I mean is that your solution is more complicated or at least less comfortable than mine. Also is not the solution for the question I asked (see the question).
– adrhc
Apr 12 at 17:38
ok no problem... thank you for your reply.... I will search about it more...
– Muntaha Liaqat
Apr 12 at 17:40
ok no problem... thank you for your reply.... I will search about it more...
– Muntaha Liaqat
Apr 12 at 17:40
@MuntahaLiaqat Welcome to AskUbuntu. Please take a look at the Markdown help page.
– Eric Carvalho
Apr 13 at 0:25
@MuntahaLiaqat Welcome to AskUbuntu. Please take a look at the Markdown help page.
– Eric Carvalho
Apr 13 at 0:25
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1133341%2fxubuntu-18-10-light-locker-wrong-behavior%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Disable lightlocker and install xscreensaver. That was the only answer I found that worked.
– Organic Marble
Apr 13 at 4:03