Re-login failure, using lightdm, when machine left idle …

[Member mikey777]

My single-core CPU Samsung netbook (64-bit) is running antixcore-LXDE (32bit).
When it is left idle for a while, the display goes off, even
when it’s not running from the battery.

When this happens, I then reinstate the lightdm login-box by touching the space bar.
However, when I re-login, the display stays on, but goes blank (nothing on it).
Before it goes blank, there is a fleeting image of the normal screen view with
icons and bottom panel – the image literally flashes in front of me in the blink
of an eye.

When the above happens, the only way I know of restarting the netbook is to use
the power on/off switch, which is obviously unsatisfactory.

How can I fix this ?

• This topic was modified 3 years, 2 months ago by mikey777.

▪ 32-bit antix19.4-core+LXDE installed on :
- (2011) Samsung NP-N145 Plus (JP04UK) – single-core CPU Intel Atom N455@1.66GHz, 2GB RAM, integrated graphics.
▪ 64-bit antix21-base+LXDE installed on:
- (2008) Asus X71Q (7SC002) – dual CPU Intel T3200@2.0GHz, 4GB RAM. Graphics: Intel Mobile 4 Series, integrated graphics
- (2007) Packard Bell Easynote MX37 (ALP-Ajax C3) – dual CPU Intel T2310@1.46GHz, 2GB RAM. Graphics: Silicon Integrated Systems.

[Moderator christophe]

Helpful

Up

0

::

I had a similar problem with MX recently, where whenever the screensaver locked the screen, that same thing you described happened.
I eventually hit on disabling the screen-locker, but kept the screen-saver turning the screen black. It was the screen-lock that caused the trouble, it seems. That solved it for me in MX.
Perhaps that will work for your LXDE?

• This reply was modified 3 years, 2 months ago by christophe. Reason: keeping on topic

confirmed antiX frugaler, since 2019

[Member mikey777]

Helpful

Up

0

::

Thanks Christophe.
Interesting to hear you had the same problem – I’ll try and disable the screen-locker and
see if that eliminates the problem – I’ll report back here when done.

▪ 32-bit antix19.4-core+LXDE installed on :
- (2011) Samsung NP-N145 Plus (JP04UK) – single-core CPU Intel Atom N455@1.66GHz, 2GB RAM, integrated graphics.
▪ 64-bit antix21-base+LXDE installed on:
- (2008) Asus X71Q (7SC002) – dual CPU Intel T3200@2.0GHz, 4GB RAM. Graphics: Intel Mobile 4 Series, integrated graphics
- (2007) Packard Bell Easynote MX37 (ALP-Ajax C3) – dual CPU Intel T2310@1.46GHz, 2GB RAM. Graphics: Silicon Integrated Systems.

[Member fungalnet]

Helpful

Up

0

::

mikey777 wrote:

When the above happens, the only way I know of restarting the netbook is to use
the power on/off switch, which is obviously unsatisfactory.

In general there is a better way than risking to corrupt your disk. Ctrl-Alt F2…F6 should give you a console prompt. Log in as root, run a ps -A and find the process like screen-lock and kill it (# kill process-id/no or killall process name). Ctrl-Alt F7 should take you back to your desktop.

anti-X - Adélie - obarun - systemd Free Space

[Member mikey777]

Helpful

Up

0

::

@christophe
Where do I find the screen-locker?
I have a minimal install with antixcore+LXDE, so maybe I’m missing a few files to enable me to find and manipulate this.
Do I need to install Xfce-powermanager to help me enable/disable screen-locker (or is there an LX alternative) ?

fungalnet wrote:

Ctrl-Alt F2…F6 should give you a console prompt.

Many thanks for your reply fungalnet.
Unfortunately, this doesn’t work – no response at all, after using Ctrl-Alt-F2 or Ctrl-Alt-F6, or using any of the F-keys in between …

▪ 32-bit antix19.4-core+LXDE installed on :
- (2011) Samsung NP-N145 Plus (JP04UK) – single-core CPU Intel Atom N455@1.66GHz, 2GB RAM, integrated graphics.
▪ 64-bit antix21-base+LXDE installed on:
- (2008) Asus X71Q (7SC002) – dual CPU Intel T3200@2.0GHz, 4GB RAM. Graphics: Intel Mobile 4 Series, integrated graphics
- (2007) Packard Bell Easynote MX37 (ALP-Ajax C3) – dual CPU Intel T2310@1.46GHz, 2GB RAM. Graphics: Silicon Integrated Systems.

[Moderator christophe]

Helpful

Up

0

::

Mikey, I poked around a little & did a test install in virtualbox:

Click on the root menu icon in the task panel. Click “Preferences,” then on “Desktop Session Settings.”
The “Automatically Started Applications” tab should be open. Uncheck the “Screen Locker” button.

I hope this works. (I’ve only just installed, so I don’t have a frame of reference…)

(Also, I notice now that I’m using LXDM to login (whereas you are using LightDM), though I don’t know if that should make a difference.)

confirmed antiX frugaler, since 2019

[Member mikey777]

Helpful

Up

0

::

christophe wrote:

Click on the root menu icon in the task panel. Click “Preferences,” then on “Desktop Session Settings.”
The “Automatically Started Applications” tab should be open. Uncheck the “Screen Locker” button.

Thanks Christophe – I’ve followed your instructions. There are only two items listed under Automatically Started Applications (both of these are ticked),
that is;
– Wicd Network Manager Tray
– User folders update

Maybe my poking around (mentioned in the GDBus errors thread that I started yesterday) has removed it ..? Don’t know.

▪ 32-bit antix19.4-core+LXDE installed on :
- (2011) Samsung NP-N145 Plus (JP04UK) – single-core CPU Intel Atom N455@1.66GHz, 2GB RAM, integrated graphics.
▪ 64-bit antix21-base+LXDE installed on:
- (2008) Asus X71Q (7SC002) – dual CPU Intel T3200@2.0GHz, 4GB RAM. Graphics: Intel Mobile 4 Series, integrated graphics
- (2007) Packard Bell Easynote MX37 (ALP-Ajax C3) – dual CPU Intel T2310@1.46GHz, 2GB RAM. Graphics: Silicon Integrated Systems.

[Moderator christophe]

Helpful

Up

0

::

It’s a mystery.
I installed only minimal packages to get my setup. In fact, on the latest one, I started with a core frugal install, ran apt full-upgrade, then installed only xorg & lxde. And everything that is on my system got pulled in as dependencies.

confirmed antiX frugaler, since 2019

[Moderator christophe]

Helpful

Up

0

::

Take a look at this in PCmanFM:

/home/netbook/.config/lxsession/LXDE/autostart

(Right-click “open” to open it in leafpad.)

Here we have something like:
@lxpanel --profile LXDE and other entries, probably.

Now, I wanted conky to autostart, so I added
@conky and it does indeed start up with LXDE.

So I’m thinking, that if you have an entry for screen-locker here, then I think you can disable it with a # in front of it…

(Just a wild guess, but it’s all I’ve got right now.)

confirmed antiX frugaler, since 2019

[Moderator christophe]

Helpful

Up

0

::

Take a look at your other related post — perhaps a fresh install is worthwhile (if not too inconvenient)?

https://www.antixforum.com/forums/topic/gd-bus-error-on-startup-unable-to-shutdown-reboot-using-gui/page/2/#post-33364

• This reply was modified 3 years, 2 months ago by christophe. Reason: slight clarification

confirmed antiX frugaler, since 2019

[Moderator Brian Masinick]

Helpful

Up

0

::

I often add the xscreensaver packages (usually also with xscreensaver-gl and the “extras” screensavers available with it and run it instead of other screen lock programs.

Does that work? I have not seen any problems with xscreensaver-gl over the years (unless a kernel doesn’t have gl support ( Then I just use xscreensaver instead.

--
Brian Masinick

[Author]

Posts