- This topic has 21 replies, 5 voices, and was last updated Mar 8-4:25 pm by mikey777.
-
Posts
-
mikey777
When I leave my Samsung netbook idle for some time, the screen goes blank and it’s not possible to relogin, through lightdm, as the screen is unresponsive. I’ve reported this problem recently, at https://www.antixforum.com/forums/topic/re-login-failure-using-lightdm-when-machine-left-idle/
In that thread, I mentioned that to relogin, I have to shutdown using the machine’s on/off switch, which of course is inadvisable, as it risks corrupting the system.
I think the system has become corrupted, as when I boot up, I get a GD Bus error message – see attached screenshot. Also, I’m now only able to shutdown or reboot using the terminal, as shutdown or rebooting through the GUI has now stopped working. Furthermore, when I attach a USB drive, I get an onscreen error message that reads: “Not authorized to perfoerm operation”, therefore I’m unable to access files on my USB-drives.
How can I fix this ?
- This topic was modified 3 years, 2 months ago by mikey777.
Attachments:
▪ 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.
fatmac
I don’t know, but maybe running “sudo apt-get install –fix-broken” may help, no guarantees, but it won’t harm your system.
Edit: That’s two – before the fix-broken, (this software has run them into one).
Linux (& BSD) since 1999
sybok
1) Some links I have found suggests to post/explore information from
/var/log/lightdm/lightdm.log(location as in Arch Linux, may differ in antiX) after A) login B) the failed shutdown via GUI.
Perhaps posting admesg | tailmight also give some hints regarding the cause of the issue.
Can you do that?I had similar error after the login in antiX a long time ago and hence I have abandoned using Lightdm on non-systemd systems (unless already installed).
2) A somewhat related problem with desktop launch error (approx. 6 years old). I would definitely backup the file they suggest to remove.
3) I would try to reinstall the lightdm-related packages in the case that something has been corrupted.
Hope it helps.
Edit: @fatmac’s reply – The approach suggested is probably best tried first and replaces my 3) completely.
- This reply was modified 3 years, 2 months ago by sybok. Reason: Other comment appeared in the meantime
mikey777
maybe running “sudo apt-get install –fix-broken” may help
Many thanks for this suggestion – sadly, this didn’t work, following reboot.
- This reply 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.mikey777
3) I would try to reinstall the lightdm-related packages in the case that something has been corrupted.
I’ve just tried this, but the problem persists.
I’m afraid my linux skills aren’t advanced enough to be able to interpret the following that you suggested.For the first thing you mentioned, the terminal output is as follows …
sudo gedit /var/log/lightdm/lightdm.log [+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log [+0.00s] DEBUG: Starting Light Display Manager 1.26.0, UID=0 PID=1734 [+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/01_debian.conf [+0.00s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d [+0.00s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d [+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf [+0.00s] DEBUG: Registered seat module local [+0.00s] DEBUG: Registered seat module xremote [+0.00s] DEBUG: Registered seat module unity [+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager [+0.06s] DEBUG: Monitoring logind for seats [+0.06s] DEBUG: New seat added from logind: seat0 [+0.06s] DEBUG: Seat seat0: Loading properties from config section Seat:* [+0.06s] DEBUG: Seat seat0: Starting [+0.06s] DEBUG: Seat seat0: Creating greeter session [+0.06s] DEBUG: Seat seat0: Creating display server of type x [+0.06s] DEBUG: posix_spawn avoided (fd close requested) [+0.07s] DEBUG: Could not run plymouth --ping: Failed to execute child process “plymouth” (No such file or directory) [+0.07s] DEBUG: Using VT 7 [+0.07s] DEBUG: Seat seat0: Starting local X display on VT 7 [+0.07s] DEBUG: XServer 0: Logging to /var/log/lightdm/x-0.log [+0.07s] DEBUG: XServer 0: Writing X server authority to /var/run/lightdm/root/:0 [+0.07s] DEBUG: XServer 0: Launching X Server [+0.07s] DEBUG: Launching process 1763: /bin/X :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch [+0.07s] DEBUG: XServer 0: Waiting for ready signal from X server :0 [+0.08s] DEBUG: Acquired bus name org.freedesktop.DisplayManager [+0.08s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0 [+0.10s] WARNING: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Accounts was not provided by any .service files [+0.11s] DEBUG: Loading user config from /etc/lightdm/users.conf [+0.12s] DEBUG: User netbook added [+0.12s] DEBUG: posix_spawn avoided (automatic reaping requested) (fd close requested) [+1.32s] DEBUG: Got signal 10 from process 1763 [+1.32s] DEBUG: XServer 0: Got signal from X server :0 [+1.32s] DEBUG: XServer 0: Connecting to XServer :0 [+1.32s] DEBUG: posix_spawn avoided (fd close requested) (child_setup specified) [+1.32s] DEBUG: Seat seat0: Display server ready, starting session authentication [+1.32s] DEBUG: Session pid=1949: Started with service 'lightdm-greeter', username 'lightdm' [+1.38s] DEBUG: Session pid=1949: Authentication complete with return value 0: Success [+1.38s] DEBUG: Seat seat0: Session authenticated, running command [+1.38s] DEBUG: Session pid=1949: Running command /sbin/lightdm-gtk-greeter [+1.39s] DEBUG: Creating shared data directory /var/lib/lightdm/data/lightdm [+1.39s] DEBUG: Session pid=1949: Logging to /var/log/lightdm/seat0-greeter.log [+1.42s] DEBUG: Activating VT 7 [+1.42s] DEBUG: Activating login1 session c1 [+1.42s] DEBUG: Seat seat0 changes active session to c1 [+1.42s] DEBUG: Session c1 is already active [+2.30s] DEBUG: Greeter connected version=1.26.0 api=1 resettable=false [+3.11s] DEBUG: Greeter start authentication [+3.11s] DEBUG: Session pid=2012: Started with service 'lightdm', username '(null)' [+3.15s] DEBUG: Session pid=2012: Got 1 message(s) from PAM [+3.15s] DEBUG: Prompt greeter with 1 message(s) [+6.66s] DEBUG: Greeter start authentication for netbook [+6.66s] DEBUG: Session pid=2012: Sending SIGTERM [+6.66s] DEBUG: Session pid=2019: Started with service 'lightdm', username 'netbook' [+6.67s] DEBUG: Session pid=2012: Terminated with signal 15 [+6.67s] DEBUG: Session: Failed during authentication [+6.67s] DEBUG: Seat seat0: Session stopped [+6.69s] DEBUG: Session pid=2019: Got 1 message(s) from PAM [+6.69s] DEBUG: Prompt greeter with 1 message(s) [+11.11s] DEBUG: Continue authentication [+11.31s] DEBUG: Session pid=2019: Authentication complete with return value 0: Success [+11.31s] DEBUG: Authenticate result for user netbook: Success [+11.31s] DEBUG: User netbook authorized [+11.33s] DEBUG: Greeter requests session lightdm-xsession [+11.33s] DEBUG: Seat seat0: Stopping greeter; display server will be re-used for user session [+11.33s] DEBUG: Terminating login1 session c1 [+11.34s] DEBUG: Session pid=1949: Sending SIGTERM [+11.35s] DEBUG: Seat seat0 changes active session to [+11.39s] DEBUG: Greeter closed communication channel [+11.39s] DEBUG: Session pid=1949: Exited with return value 0 [+11.39s] DEBUG: Seat seat0: Session stopped [+11.39s] DEBUG: Seat seat0: Greeter stopped, running session [+11.39s] DEBUG: Registering session with bus path /org/freedesktop/DisplayManager/Session0 [+11.40s] DEBUG: posix_spawn avoided (fd close requested) (child_setup specified) [+11.40s] DEBUG: Session pid=2019: Running command /etc/X11/Xsession default [+11.40s] DEBUG: Creating shared data directory /var/lib/lightdm/data/netbook [+11.40s] DEBUG: Session pid=2019: Logging to .xsession-errors [+11.42s] DEBUG: Activating VT 7 [+11.43s] DEBUG: Activating login1 session 1 [+11.43s] DEBUG: Seat seat0 changes active session to 1 [+11.43s] DEBUG: Session 1 is already activeFor the second thing you mentioned, the terminal output is as follows:
netbook@antixcore:~ $ sudo dmesg | tail [ 173.156116] [UFW BLOCK] IN=wlan0 OUT= MAC=01:00:5e:00:00:01:5c:b1:3e:b1:06:ac:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2 [ 203.167315] [UFW BLOCK] IN=wlan0 OUT= MAC=01:00:5e:00:00:01:5c:b1:3e:b1:06:ac:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2 [ 233.186499] [UFW BLOCK] IN=wlan0 OUT= MAC=01:00:5e:00:00:01:5c:b1:3e:b1:06:ac:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2 [ 263.190291] [UFW BLOCK] IN=wlan0 OUT= MAC=01:00:5e:00:00:01:5c:b1:3e:b1:06:ac:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2 [ 293.199516] [UFW BLOCK] IN=wlan0 OUT= MAC=01:00:5e:00:00:01:5c:b1:3e:b1:06:ac:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2[ 323.210525] [UFW BLOCK] IN=wlan0 OUT= MAC=01:00:5e:00:00:01:5c:b1:3e:b1:06:ac:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2
[ 353.223850] [UFW BLOCK] IN=wlan0 OUT= MAC=01:00:5e:00:00:01:5c:b1:3e:b1:06:ac:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2
[ 383.232739] [UFW BLOCK] IN=wlan0 OUT= MAC=01:00:5e:00:00:01:5c:b1:3e:b1:06:ac:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2
[ 413.243776] [UFW BLOCK] IN=wlan0 OUT= MAC=01:00:5e:00:00:01:5c:b1:3e:b1:06:ac:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2
[ 443.253858] [UFW BLOCK] IN=wlan0 OUT= MAC=01:00:5e:00:00:01:5c:b1:3e:b1:06:ac:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2▪ 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.sybok
The lightdm’s log does not provide much info as it contains mostly debug messages; the WARNING is probably a rather harmless bug due to an unmet dependency (2016). The resolution was to install package ‘accountsservice’.
Similarly fordmesg | tailCould you please try to reproduce one of the errors you have and then extract ERROR/WARNING/FATAL messages only from the lightdm’s log? E.g. using
grep -n -C 1 's] [EWF][A-Z]\+:' /var/log/lightdm/lightdm.logExplanation:
Log line structure seems to be
[<time>s] INFO|DEBUG|WARNING|ERROR|FATAL: <message>-n = with line numbers
-C <integer> = context of <integer> lines above and below the matched line.
‘s] [EWF][A-Z]\+:’ matches the log-level description starting with ‘E’, ‘W’ or ‘F’, [A-Z]\+ is any capital letter (at least once) and ‘:’ is just the colon.- This reply was modified 3 years, 2 months ago by sybok.
- This reply was modified 3 years, 2 months ago by sybok. Reason: fix a sentence
christophe
In an attempt to help…
I (re)installed LXDE (with LXDM the first time, and LightDM as display mgr the second time) to antiX core in virtualbox. Incidentally, both display managers (LightDM & LXDM) give me the same GDBus errors (popup warning at start & then lxterminal needed to leave LXDE).confirmed antiX frugaler, since 2019
mikey777
Incidentally, both display managers (LightDM & LXDM) give me the same GDBus errors (popup warning at start & then lxterminal needed to leave LXDE).
Thanks christophe – I have a few questions for you, so that I can learn from this, before I reinstall antixcore and avoid this problem in the future.
Do you get GDBus errors & need lxterminal to leave LXDE, even when screen-locker is disabled ?
Do you think one way of avoiding this mess is simply to avoid having a display manager, deleting lightdm & lightdm-gtk-greeter following the initial antiXcore install, and just do manual login following boot and use the startx command to access the desktop ?By the way, how do I disable the screen-locker in antixcore (either GUI or terminal method) ?
- This reply 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.mikey777
@sybok
@fatmacThe problem appears partly fixed, due to a bit of fiddling around.
I deleted elogind, lightdm, lightdm-gtk-greeter and then reinstalled them. I also installed accountsservice (as you indicated sybok).
The GDBus error notification no longer appears on booting, and now I can reboot or shutdown normally again, using the gui.I also deleted gvfs and reinstalled this, hoping that USB functionality would return, but my USB-drives are still not identified by the file manager pcmanfm.
However, something unexpected and positive has happened with my pottering around above 🙂
Very beautiful screensavers that appear, instead of a blank screen, if the netbook is left idle for a few minutes.
Where did these come from (what file or application is responsible for these) ?- This reply 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.christophe
Because I found the issue in both display managers, I’m thinking (though I may be wrong) that this error comes from LXDE not having something that it needs to operate, that isn’t listed as a dependency. It looks to me to be independent of display manager.
FWIW, I’ve never seen this GDBus error using a Window Manager, whether antiX full/base or building up from core. I’ve never had the screen lock issue in antiX either.
confirmed antiX frugaler, since 2019
christophe
I just saw your post about working through/around this. Excellent!
confirmed antiX frugaler, since 2019
mikey777
Screen-locker – how did you disable this ?
In future, do I need to install an application to enable me to do this ?Thanks Christophe for your replies – much appreciated.
NB. I’ve just seen your reply to this question at
https://www.antixforum.com/forums/topic/re-login-failure-using-lightdm-when-machine-left-idle/#post-33332
Many thanks again.- This reply 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.mikey777
Because I found the issue in both display managers, I’m thinking (though I may be wrong) that this error comes from LXDE not having something that it needs to operate, that isn’t listed as a dependency. It looks to me to be independent of display manager.
Thanks – that’s a helpful thought – I think I’ll take a closer look at this possibility …
▪ 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.mikey777
I also deleted gvfs and reinstalled this, hoping that USB functionality would return, but my USB-drives are still not identified by the file manager pcmanfm.
I appear unable to reinstall gvfs, which prevents pcmanfs from identifying my USB-drives.
The output from terminal in response tosudo apt-get install gvfsreads:
“Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some requred packages have not
yet been created or been moved out of Incoming.
The following information may help to resolve the situation:The following packages have unmet dependencies:
gvfs : Depends: gvfs-daemons (< 1.38.1-5.1~) but it is not going to be installed
Depends: gvfs-daemons (>= 1.38.1-5) but is not going to be installed
E: Unable to correct problems, you have held broken packages.”However, running sudo apt-get install –fix-broken doesn’t seem to do anything. All I
get is: “0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded”When I run
sudo apt-get install gvfs-daemonsI get
gvfs-daemons : Depends : udisks2 but is not going to be installedWhen I run
sudo apt-get install udisks2I get
udisks2 : Depends : libpam-systemdand … then libpam-systemd seems to depend on systemd (yikes!)
I think I’ll just have to reinstall antixcore to get USB-functionality. A shame really, as I feel I’m almost there …
I’ll wait a bit though, just in case anyone has any further ideas …- This reply 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.mikey777
Very beautiful screensavers that appear, instead of a blank screen, if the netbook is left idle for a few minutes.
Where did these come from (what file or application is responsible for these) ?Poking around, I’ve now found that the screensavers that kick in when the machine is idle come from the following files: xscreensaver and xscreensaver-data
–▪ 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.
- You must be logged in to reply to this topic.
