Unix & Linux Stack Exchange
Q&A for users of Linux, FreeBSD and other Unix-like operating systems
Latest Questions
1
votes
1
answers
3355
views
LightDM - default user session does not seem to work
I need to choose which default window manager is choosen by LightDM at startup. I have edited `/etc/lightdm/lightdm.conf`: [SeatDefaults] user-session=i3 autologin-user=ibox It does not seem to work, it still boot on LXDE. I removed the `.dmrc` file in my home directory.
I need to choose which default window manager is choosen by LightDM at startup. I have edited
/etc/lightdm/lightdm.conf
:
[SeatDefaults]
user-session=i3
autologin-user=ibox
It does not seem to work, it still boot on LXDE. I removed the .dmrc
file in my home directory.
Mathieu
(111 rep)
May 19, 2016, 08:59 AM
• Last activity: Aug 3, 2025, 08:04 PM
0
votes
1
answers
3199
views
Fixing a problem with lightdm; boot-loop
I think I messed up my Ubuntu 17.04 a little. In order to describe my problem I can only provide the symptoms + a suspicious log-file. My quenstion on this is: 1.: Can I repair it by doing something with lightdm? (cf. below)? Symptoms: When I start the pc, it never reaches the log-in-mask. Instead i...
I think I messed up my Ubuntu 17.04 a little. In order to describe my problem I can only provide the symptoms + a suspicious log-file.
My quenstion on this is:
1.: Can I repair it by doing something with lightdm? (cf. below)?
Symptoms: When I start the pc, it never reaches the log-in-mask. Instead it seems to be trying to launch the graphical surface over and over again, but always fails to do so. I can hardly work on it in this state. I can switch to Ctrl+Alt+F2 and log in via terminal. Here I can do stuff, but roughly all 30seconds the monitor becomes black and shortly displays 'No signal'. After some seconds I can re-switch to there and start from were I left. Reboot does not help.
DISPLAY-variable is 1. $startx does not work.
System: Ubuntu 17.04, build pc, all parts were bought 2 months ago.
What I did: I installed pekwm and started it a few times, I also switched between the window-managers via $pekwm --replace& resp. $compiz --replace&. It worked fine.
I installed conky and wrote a .desktop-file to autostart it. This never worked. I deleted said .desktop-file, after the problem occurred.
Right before the problem occured, I do not recall having done anything else than firefox, LaTeX and mathematica.
It MIGHT be, that I messed up lighdm, without realizing. Here are last few lines of /var/log/lightdm/lightdm.log:
[+29.10s] DEBUG: Exiting with return value 1
[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.00s] DEBUG: Starting Light Display Manager 1.22.0, UID=0 PID=5482
[+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/45-unity8.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-disable-guest.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-disable-log-backup.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-greeter-wrapper.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-guest-wrapper.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-ubuntu.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-unity-greeter.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-xserver-command.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.01s] DEBUG: Monitoring logind for seats
[+0.01s] DEBUG: New seat added from logind: seat0
[+0.01s] DEBUG: Seat seat0: Loading properties from config section Seat:*
[+0.01s] DEBUG: Seat seat0: Starting
[+0.01s] DEBUG: Seat seat0: Creating greeter session
[+0.01s] DEBUG: Seat seat0: Creating display server of type x
[+0.02s] DEBUG: Using VT 7
[+0.02s] DEBUG: Seat seat0: Starting local X display on VT 7
[+0.02s] DEBUG: XServer 1: Logging to /var/log/lightdm/x-1.log
[+0.02s] DEBUG: XServer 1: Writing X server authority to /var/run/lightdm/root/:1
[+0.02s] DEBUG: XServer 1: Launching X Server
[+0.02s] DEBUG: Launching process 5487: /usr/bin/X -core :1 -seat seat0 -auth /var/run/lightdm/root/:1 -nolisten tcp vt7 -novtswitch
[+0.02s] DEBUG: XServer 1: Waiting for ready signal from X server :1
[+0.02s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.02s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0
[+0.02s] DEBUG: Loading users from org.freedesktop.Accounts
[+0.02s] DEBUG: User /org/freedesktop/Accounts/User1000 added
[+0.31s] DEBUG: Seat seat0 changes active session to c12
[+0.91s] DEBUG: Got signal 10 from process 5487
[+0.91s] DEBUG: XServer 1: Got signal from X server :1
[+0.91s] DEBUG: XServer 1: Connecting to XServer :1
[+1.18s] DEBUG: Seat seat0: Display server ready, starting session authentication
[+1.18s] DEBUG: Session pid=5642: Started with service 'lightdm-greeter', username 'lightdm'
[+1.18s] DEBUG: Seat seat0 changes active session to
[+1.20s] DEBUG: Session pid=5642: Authentication complete with return value 0: Success
[+1.20s] DEBUG: Seat seat0: Session authenticated, running command
[+1.20s] DEBUG: Session pid=5642: Running command /usr/lib/lightdm/lightdm-greeter-session /usr/sbin/unity-greeter
[+1.20s] DEBUG: Creating shared data directory /var/lib/lightdm-data/lightdm
[+1.20s] DEBUG: Session pid=5642: Logging to /var/log/lightdm/seat0-greeter.log
[+1.27s] DEBUG: Activating VT 7
[+1.28s] DEBUG: Activating login1 session c13
[+1.28s] DEBUG: Seat seat0 changes active session to c13
[+1.28s] DEBUG: Session c13 is already active
[+1.51s] DEBUG: Greeter connected version=1.22.0 api=1 resettable=false
[+1.79s] DEBUG: Greeter start authentication for hein
[+1.79s] DEBUG: Session pid=5796: Started with service 'lightdm', username 'hein'
[+1.80s] DEBUG: Session pid=5796: Got 1 message(s) from PAM
[+1.80s] DEBUG: Prompt greeter with 1 message(s)
[+3.52s] DEBUG: Seat seat0 changes active session to 2
[+29.98s] DEBUG: Greeter closed communication channel
[+29.98s] DEBUG: Session pid=5642: Exited with return value 0
[+29.98s] DEBUG: Seat seat0: Session stopped
[+29.98s] DEBUG: Seat seat0: Stopping; failed to start a greeter
[+29.98s] DEBUG: Seat seat0: Stopping
[+29.98s] DEBUG: Seat seat0: Stopping display server
[+29.98s] DEBUG: Sending signal 15 to process 5487
[+29.98s] DEBUG: Seat seat0: Stopping session
[+29.98s] DEBUG: Session pid=5796: Sending SIGTERM
[+29.98s] DEBUG: Session pid=5796: Terminated with signal 15
[+29.98s] DEBUG: Session: Failed during authentication
[+29.98s] DEBUG: Seat seat0: Session stopped
[+29.98s] DEBUG: Process 5487 exited with return value 0
[+29.98s] DEBUG: XServer 1: X server stopped
[+29.98s] DEBUG: Releasing VT 7
[+29.98s] DEBUG: XServer 1: Removing X server authority /var/run/lightdm/root/:1
[+29.98s] DEBUG: Seat seat0: Display server stopped
[+29.98s] DEBUG: Seat seat0: Stopped
[+29.98s] DEBUG: Required seat has stopped
[+29.98s] DEBUG: Stopping display manager
[+29.98s] DEBUG: Display manager stopped
[+29.98s] DEBUG: Stopping daemon
[+29.98s] DEBUG: Exiting with return value 1
[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.00s] DEBUG: Starting Light Display Manager 1.22.0, UID=0 PID=5861
[+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/45-unity8.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-disable-guest.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-disable-log-backup.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-greeter-wrapper.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-guest-wrapper.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-ubuntu.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-unity-greeter.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-xserver-command.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.02s] DEBUG: Monitoring logind for seats
[+0.02s] DEBUG: New seat added from logind: seat0
[+0.02s] DEBUG: Seat seat0: Loading properties from config section Seat:*
[+0.02s] DEBUG: Seat seat0: Starting
[+0.02s] DEBUG: Seat seat0: Creating greeter session
[+0.02s] DEBUG: Seat seat0: Creating display server of type x
[+0.02s] DEBUG: Using VT 7
[+0.02s] DEBUG: Seat seat0: Starting local X display on VT 7
[+0.02s] DEBUG: XServer 0: Logging to /var/log/lightdm/x-0.log
[+0.02s] DEBUG: XServer 0: Writing X server authority to /var/run/lightdm/root/:0
[+0.02s] DEBUG: XServer 0: Launching X Server
[+0.02s] DEBUG: Launching process 5866: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+0.02s] DEBUG: XServer 0: Waiting for ready signal from X server :0
[+0.02s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.02s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0
[+0.02s] DEBUG: Loading users from org.freedesktop.Accounts
[+0.02s] DEBUG: User /org/freedesktop/Accounts/User1000 added
[+0.04s] DEBUG: Seat seat0 changes active session to c13
[+0.61s] DEBUG: Got signal 10 from process 5866
[+0.61s] DEBUG: XServer 0: Got signal from X server :0
[+0.61s] DEBUG: XServer 0: Connecting to XServer :0
[+0.66s] DEBUG: Seat seat0: Display server ready, starting session authentication
[+0.66s] DEBUG: Session pid=5888: Started with service 'lightdm-greeter', username 'lightdm'
[+0.68s] DEBUG: Session pid=5888: Authentication complete with return value 0: Success
[+0.68s] DEBUG: Seat seat0: Session authenticated, running command
[+0.68s] DEBUG: Session pid=5888: Running command /usr/lib/lightdm/lightdm-greeter-session /usr/sbin/unity-greeter
[+0.68s] DEBUG: Creating shared data directory /var/lib/lightdm-data/lightdm
[+0.68s] DEBUG: Session pid=5888: Logging to /var/log/lightdm/seat0-greeter.log
[+0.71s] DEBUG: Activating VT 7
[+0.71s] DEBUG: Activating login1 session c14
[+0.71s] DEBUG: Seat seat0 changes active session to c14
[+0.71s] DEBUG: Session c14 is already active
[+0.78s] DEBUG: Greeter connected version=1.22.0 api=1 resettable=false
[+0.92s] DEBUG: Greeter start authentication for hein
[+0.92s] DEBUG: Session pid=5943: Started with service 'lightdm', username 'hein'
[+0.92s] DEBUG: Session pid=5943: Got 1 message(s) from PAM
[+0.92s] DEBUG: Prompt greeter with 1 message(s)
[+4.29s] DEBUG: Seat seat0 changes active session to 2
[+29.09s] DEBUG: Greeter closed communication channel
[+29.09s] DEBUG: Session pid=5888: Exited with return value 0
[+29.09s] DEBUG: Seat seat0: Session stopped
[+29.09s] DEBUG: Seat seat0: Stopping; failed to start a greeter
[+29.09s] DEBUG: Seat seat0: Stopping
[+29.09s] DEBUG: Seat seat0: Stopping display server
[+29.09s] DEBUG: Sending signal 15 to process 5866
[+29.09s] DEBUG: Seat seat0: Stopping session
[+29.09s] DEBUG: Session pid=5943: Sending SIGTERM
[+29.09s] DEBUG: Session pid=5943: Terminated with signal 15
[+29.09s] DEBUG: Session: Failed during authentication
[+29.09s] DEBUG: Seat seat0: Session stopped
[+29.09s] DEBUG: Process 5866 exited with return value 0
[+29.09s] DEBUG: XServer 0: X server stopped
[+29.09s] DEBUG: Releasing VT 7
[+29.09s] DEBUG: XServer 0: Removing X server authority /var/run/lightdm/root/:0
[+29.09s] DEBUG: Seat seat0: Display server stopped
[+29.09s] DEBUG: Seat seat0: Stopped
[+29.09s] DEBUG: Required seat has stopped
[+29.09s] DEBUG: Stopping display manager
[+29.09s] DEBUG: Display manager stopped
[+29.09s] DEBUG: Stopping daemon
[+29.09s] DEBUG: Exiting with return value 1
[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.00s] DEBUG: Starting Light Display Manager 1.22.0, UID=0 PID=6033
[+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/45-unity8.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-disable-guest.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-disable-log-backup.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-greeter-wrapper.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-guest-wrapper.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-ubuntu.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-unity-greeter.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-xserver-command.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.02s] DEBUG: Monitoring logind for seats
[+0.02s] DEBUG: New seat added from logind: seat0
[+0.02s] DEBUG: Seat seat0: Loading properties from config section Seat:*
[+0.02s] DEBUG: Seat seat0: Starting
[+0.02s] DEBUG: Seat seat0: Creating greeter session
[+0.02s] DEBUG: Seat seat0: Creating display server of type x
[+0.02s] DEBUG: Using VT 7
[+0.02s] DEBUG: Seat seat0: Starting local X display on VT 7
[+0.02s] DEBUG: XServer 1: Logging to /var/log/lightdm/x-1.log
[+0.02s] DEBUG: XServer 1: Writing X server authority to /var/run/lightdm/root/:1
[+0.02s] DEBUG: XServer 1: Launching X Server
[+0.02s] DEBUG: Launching process 6038: /usr/bin/X -core :1 -seat seat0-auth /var/run/lightdm/root/:1 -nolisten tcp vt7 -novtswitch
[+0.02s] DEBUG: XServer 1: Waiting for ready signal from X server :1
[+0.02s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.02s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0
[+0.02s] DEBUG: Loading users from org.freedesktop.Accounts
[+0.02s] DEBUG: User /org/freedesktop/Accounts/User1000 added
[+0.27s] DEBUG: Seat seat0 changes active session to c14
[+0.88s] DEBUG: Got signal 10 from process 6038
[+0.88s] DEBUG: XServer 1: Got signal from X server :1
[+0.88s] DEBUG: XServer 1: Connecting to XServer :1
[+1.14s] DEBUG: Seat seat0: Display server ready, starting session authentication
[+1.14s] DEBUG: Session pid=6193: Started with service 'lightdm-greeter', username 'lightdm'
[+1.14s] DEBUG: Seat seat0 changes active session to
[+1.16s] DEBUG: Session pid=6193: Authentication complete with return value 0: Success
[+1.16s] DEBUG: Seat seat0: Session authenticated, running command
[+1.16s] DEBUG: Session pid=6193: Running command /usr/lib/lightdm/lightdm-greeter-session /usr/sbin/unity-greeter
[+1.16s] DEBUG: Creating shared data directory /var/lib/lightdm-data/lightdm
[+1.16s] DEBUG: Session pid=6193: Logging to /var/log/lightdm/seat0-greeter.log
[+1.21s] DEBUG: Activating VT 7
[+1.21s] DEBUG: Activating login1 session c15
[+1.22s] DEBUG: Seat seat0 changes active session to c15
[+1.22s] DEBUG: Session c15 is already active
[+1.49s] DEBUG: Greeter connected version=1.22.0 api=1 resettable=false
[+1.75s] DEBUG: Greeter start authentication for hein
[+1.75s] DEBUG: Session pid=6340: Started with service 'lightdm', username 'hein'
[+1.75s] DEBUG: Session pid=6340: Got 1 message(s) from PAM
[+1.75s] DEBUG: Prompt greeter with 1 message(s)
[+6.23s] DEBUG: Seat seat0 changes active session to 2
Thanks in advance!
person10
(1 rep)
Sep 26, 2017, 11:54 AM
• Last activity: Jul 18, 2025, 04:03 PM
1
votes
1
answers
2240
views
Blank screen at startup, xset is unable to open display ""
Seemingly from out of nowhere, I get a blank screen during startup on Arch Linux. Going into the TTY shows me ``` xset: unable to open display "" Unable to connect to X server ``` I use X11, LightDM and i3. Here LightDM seems to be able to show a blank screen with a cross as a cursor (both during st...
Seemingly from out of nowhere, I get a blank screen during startup on Arch Linux. Going into the TTY shows me
xset: unable to open display ""
Unable to connect to X server
I use X11, LightDM and i3. Here LightDM seems to be able to show a blank screen with a cross as a cursor (both during startup and after running lightdm
in the TTY).
I suspect it can be can be caused of i3, since the file ~/.xsession-errors
has the content
i3status: trying to auto-detect output_format setting
i3status: auto-detected "i3bar"
i3status: exiting due to signal.
However, running exec i3 -V -d all &>> "$HOME/i3.log"
only shows i3: Cannot open display
, so perhaps its not i3.
When running htop
, I can see that Xorg
is running with command
/usr/lib/Xorg :0 -seat seat0 -auth /run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
which should tell me that the correct display indeed is :0
. I tried export DISPLAY=":0"
, but I don't know what to do after this.
I did update my system yesterday via pacman, could something there have caused this? I see that i3wm
for Arch was updated a couple of days ago, which could explain it.
What should I do in order to get it working?
aahlback
(31 rep)
Feb 2, 2022, 12:07 PM
• Last activity: Jul 13, 2025, 05:05 AM
-1
votes
2
answers
3350
views
GDM does not start on boot
GDM does not start on boot: I'm having same problem I also read tis problem that you solved before, I tried that but got nothing. Please help me im stuck in try.
GDM does not start on boot: I'm having same problem I also read tis problem that you solved before, I tried that but got nothing. Please help me im stuck in try.
Raman
(1 rep)
Jul 29, 2020, 07:05 AM
• Last activity: Jul 6, 2025, 12:04 AM
1
votes
1
answers
4044
views
No display manager after Debian 12 installation on Hyper-V
I installed (graphical installation, selecting xfce) [Debian 12][1] on Hyper-V Gen1 VM within Windows 10. When reboot Debian no login screen appears. What cause the problem that lightdm does not start? Same issue if I run Debian 12 live iso with different DEs. Go to text terminal `alt+f1` and collec...
I installed (graphical installation, selecting xfce) Debian 12 on Hyper-V Gen1 VM within Windows 10. When reboot Debian no login screen appears. What cause the problem that lightdm does not start? Same issue if I run Debian 12 live iso with different DEs. Go to text terminal
alt+f1
and collect some information:
$ sudo cat /etc/X11/default-display-manager
/usr/sbin/lightdm
$ systemctl status lightdm.service
× lightdm.service - Light Display Manager
Loaded: loaded (/lib/systemd/system/lightdm.service; enabled; preset: enabled)
Active: failed (Result: exit-code) since Thu 2023-07-13 23:48:57 CEST; 22min ago
Duration: 34ms
Docs: man:lightdm(1)
Main PID: 612 (code=exited, status=1/FAILURE)
CPU: 36ms
Warning: some journal files were not opened due to insufficient permissions.
$ sudo lightdm --test-mode --debug
[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.00s] DEBUG: Starting Light Display Manager 1.26.0, UID=0 PID=6878
[+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.00s] DEBUG: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs?
[+0.00s] DEBUG: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus Screen "Default Screen Section" (0)
[ 6.525] (**) | |-->Monitor ""
[ 6.525] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 6.525] (==) Automatically adding devices
[ 6.525] (==) Automatically enabling devices
[ 6.525] (==) Automatically adding GPU devices
[ 6.525] (==) Automatically binding GPU devices
[ 6.525] (==) Max clients allowed: 256, resource mask: 0x1fffff
[ 6.525] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[ 6.525] Entry deleted from font path.
[ 6.525] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins
[ 6.525] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 6.525] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 6.525] (II) Loader magic: 0x55f4a49d2f00
[ 6.525] (II) Module ABI versions:
[ 6.525] X.Org ANSI C Emulation: 0.4
[ 6.525] X.Org Video Driver: 25.2
[ 6.525] X.Org XInput driver : 24.4
[ 6.525] X.Org Server Extension : 10.0
[ 6.526] (++) using VT number 7
[ 6.526] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[ 6.527] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 6.527] (II) Platform probe for /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:07/VMBUS:01/5620e0c7-8062-4dce-aeb7-520c7ef76171/drm/card0
[ 6.531] (--) PCI:*(0@0:8:0) 1414:5353:0000:0000 rev 0, Mem @ 0xf8000000/67108864, BIOS @ 0x????????/131072
[ 6.531] (II) LoadModule: "glx"
[ 6.532] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 6.533] (II) Module glx: vendor="X.Org Foundation"
[ 6.533] compiled for 1.21.1.7, module version = 1.0.0
[ 6.533] ABI class: X.Org Server Extension, version 10.0
[ 6.533] (==) Matched modesetting as autoconfigured driver 0
[ 6.533] (==) Matched fbdev as autoconfigured driver 1
[ 6.533] (==) Matched vesa as autoconfigured driver 2
[ 6.533] (==) Assigned the driver to the xf86ConfigLayout
[ 6.533] (II) LoadModule: "modesetting"
[ 6.533] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[ 6.533] (II) Module modesetting: vendor="X.Org Foundation"
[ 6.533] compiled for 1.21.1.7, module version = 1.21.1
[ 6.533] Module class: X.Org Video Driver
[ 6.533] ABI class: X.Org Video Driver, version 25.2
[ 6.533] (II) LoadModule: "fbdev"
[ 6.533] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[ 6.533] (II) Module fbdev: vendor="X.Org Foundation"
[ 6.533] compiled for 1.21.1.3, module version = 0.5.0
[ 6.533] Module class: X.Org Video Driver
[ 6.533] ABI class: X.Org Video Driver, version 25.2
[ 6.533] (II) LoadModule: "vesa"
[ 6.533] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[ 6.533] (II) Module vesa: vendor="X.Org Foundation"
[ 6.533] compiled for 1.21.1.3, module version = 2.5.0
[ 6.533] Module class: X.Org Video Driver
[ 6.533] ABI class: X.Org Video Driver, version 25.2
[ 6.533] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 6.534] (II) FBDEV: driver for framebuffer: fbdev
[ 6.534] (II) VESA: driver for VESA chipsets: vesa
[ 6.534] (WW) Falling back to old probe method for modesetting
[ 6.535] (II) modeset(1): using default device
[ 6.535] (II) Loading sub module "fbdevhw"
[ 6.535] (II) LoadModule: "fbdevhw"
[ 6.535] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[ 6.535] (II) Module fbdevhw: vendor="X.Org Foundation"
[ 6.535] compiled for 1.21.1.7, module version = 0.0.2
[ 6.535] ABI class: X.Org Video Driver, version 25.2
[ 6.535] (EE) Unable to find a valid framebuffer device
[ 6.535] (WW) Falling back to old probe method for fbdev
[ 6.535] (II) Loading sub module "fbdevhw"
[ 6.535] (II) LoadModule: "fbdevhw"
[ 6.535] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[ 6.535] (II) Module fbdevhw: vendor="X.Org Foundation"
[ 6.535] compiled for 1.21.1.7, module version = 0.0.2
[ 6.535] ABI class: X.Org Video Driver, version 25.2
[ 6.535] (II) FBDEV(3): using default device
[ 6.535] vesa: Ignoring device with a bound kernel driver
[ 6.536] (II) modeset(G0): using drv /dev/dri/card0
[ 6.536] (EE) Screen 0 deleted because of no matching config section.
[ 6.536] (II) UnloadModule: "modesetting"
[ 6.536] (EE) Screen 1 deleted because of no matching config section.
[ 6.536] (II) UnloadModule: "fbdev"
[ 6.536] (II) UnloadSubModule: "fbdevhw"
[ 6.536] (EE) Screen 2 deleted because of no matching config section.
[ 6.536] (II) UnloadModule: "vesa"
[ 6.536] (EE)
Fatal server error:
[ 6.536] (EE) Cannot run in framebuffer mode. Please specify busIDs for all framebuffer devices
[ 6.536] (EE)
[ 6.536] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 6.536] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 6.536] (EE)
[ 6.544] (EE) Server terminated with error (1). Closing log file.
I also found this post, that describes same problem (but on Hyper-V Gen2 insted of Gen1) and suggest to install xf86-video-fbdev
. I reinstalled the equivalent package for Debian and lightdm
as well:
sudo apt-get install --reinstall xserver-xorg-video-fbdev
sudo apt-get install --reinstall lightdm
If I'm not wrong it is called a greeter, the GUI that prompts the user for credentials. So I checked lightdm config:
$ sudo lightdm --show-config
[sudo] password for user:
[Seat:*]
A greeter-session=lightdm-greeter
A greeter-hide-users=true
A session-wrapper=/etc/X11/Xsession
[LightDM]
B logind-check-graphical=false
Sources:
A /usr/share/lightdm/lightdm.conf.d/01_debian.conf
B /etc/lightdm/lightdm.conf
Is lightdm-greeter
a correct greeter? I ask because if I search for greeter I found lightdm-gtk-greeter
, lightdm-deepin-greeter
, lightdm-pantheon-greeter
, lightdm-webkit2-greeter
, etc. but no lightdm-greeter
.
Murmulodi
(1226 rep)
Jul 13, 2023, 10:18 PM
• Last activity: Jul 4, 2025, 07:26 PM
2
votes
2
answers
3387
views
Debian 9 DM won't load after dist-upgrade
I used to have Debian 8, and today I decided to upgrade to Debian 9. I did so by running: sed 's/jessie/stretch/g' /etc/apt/sources.list sudo apt-get update && sudo apt-get upgrade sudo apt-get dist-upgrade I noticed quite a few weird stuff going on after this. First, the GRUB bootloader is in a way...
I used to have Debian 8, and today I decided to upgrade to Debian 9. I did so by running:
sed 's/jessie/stretch/g' /etc/apt/sources.list
sudo apt-get update && sudo apt-get upgrade
sudo apt-get dist-upgrade
I noticed quite a few weird stuff going on after this. First, the GRUB bootloader is in a way, broken. If I reboot the system, the arrow keys simply don't work (however, if I use the arrow keys, the countdown stops), but the arrow keys do work if I shut down the system and turn it on again.
Also, the system fails to boot to the GUI login now, and instead boots to the tty. Here's what shows up during boot, before loading the tty:
I tried running startx manually, but that didn't work and gave an error 1, stating,
Failed to load module fglrx (Module does not exist 0)
I ran
sudo apt-get install fglrx
but it said there's no installation candidate. How can I fix this?
EDIT: Some additional output from some commands I ran.

systemctl status lightdm.service
gave:
lightdm.service - Light Display Manager
Loaded: loaded (/lib/systemd/system/lightdm.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Thu 2017-07-06 19:17:26 IST; 2min 18s ago
Docs: man:lightdm(1)
Process: 864 ExecStart=/usr/sbin/lightdm (code=exited, status=1/FAILURE)
Process: 860 ExecStartPre=/bin/sh -c [ "$(cat /etc/X11/default-display-manager 2>/dev/null)" = "/usr/sbin/lightdm" ] (code=exited, status=0/SUCCESS)
Main PID: 864 (code=exited, status=1/FAILURE)
Here's the output of sudo startx
:
X.Org X Server 1.19.2
Release Date: 2017-03-02
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian
Current Operating System: Linux rahul-pc 4.9.0-3-amd64 #1 SMP Debian 4.9.30-2+deb9u2 (2017-06-26) x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.9.0-3-amd64 root=UUID=4fb31b35-931b-4790-8dff-f0b97dd35154 ro quiet
Build Date: 03 March 2017 03:14:41PM
xorg-server 2:1.19.2-1 (https://www.debian.org/support)
Current version of pixman: 0.34.0
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Thu Jul 6 19:13:40 2017
(==) Using config directory: "/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(EE)
Fatal server error:
(EE) no screens found(EE)
(EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
(EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
(EE)
(EE) Server terminated with error (1). Closing log file.
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error
Like I mentioned in the comments, the upgrade also changed my kernel from 3.16 to 4.9, and I just found it interesting that sudo startx
shows these kernel and OS versions.
My graphics card is:
$ lspci -vnn | grep VGA – Vlastimil 16 hours ago
00:01.0 VGA compatible controller : Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R4/R5 Graphics] [1002:9851] (rev 45) (prog-if 00 [VGA controller])
Rahul
(121 rep)
Jul 6, 2017, 01:24 PM
• Last activity: Jul 3, 2025, 02:04 PM
1
votes
2
answers
3517
views
How to change cursor size in LightDM+GTK
I am using the GTK greeter for LightDM but the cursor looks very tiny on my laptop's 1080 display. I have already set the DPI setting and some text looks big, but the center input is still small and the cursor remains small, too. I followed some instructions [here][1] which advice to use `dconf` as...
I am using the GTK greeter for LightDM but the cursor looks very tiny on my laptop's 1080 display. I have already set the DPI setting and some text looks big, but the center input is still small and the cursor remains small, too. I followed some instructions here which advice to use
dconf
as root, but doing:
dconf write /org/gnome/desktop/interface/cursor-size 32
fails saying that the connection is closed.
Also, I found out that root isn't supposed to use dconf
. I tried dconf-editor
with the same results, and /etc/gtk-3.0
doesn't even exist in my system (Fedora 29). What can I do?
arielnmz
(559 rep)
Dec 31, 2018, 07:31 AM
• Last activity: Jun 28, 2025, 11:05 PM
0
votes
1
answers
1215
views
Changing the default lightdm greeter not working on Arch with XFCE
I installed two greeters: ls -la /usr/share/xgreeters -rw-r--r-- 1 root root 187 Sep 6 2022 lightdm-gtk-greeter.desktop -rw-r--r-- 1 root root 137 May 25 04:52 lightdm-mini-greeter.desktop And made the change to select a greeter session in /etc/lightdm/lightdm.conf: greeter-session = lightdm-mini-gr...
I installed two greeters:
ls -la /usr/share/xgreeters
-rw-r--r-- 1 root root 187 Sep 6 2022 lightdm-gtk-greeter.desktop
-rw-r--r-- 1 root root 137 May 25 04:52 lightdm-mini-greeter.desktop
And made the change to select a greeter session in /etc/lightdm/lightdm.conf:
greeter-session = lightdm-mini-greeter
I have the greeter config in /etc/lightdm/lightdm-mini-greeter.conf.
This is per instructions on https://wiki.archlinux.org/title/LightDM and https://github.com/prikhi/lightdm-mini-greeter .
However, looking at the logs in /var/log/lightdm from when the system boots:
[+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
[+0.00s] DEBUG: [LightDM] contains unknown option greeter-session
...
[+1.45s] DEBUG: Session pid=599: Running command /usr/bin/lightdm-gtk-greeter
I am then greeted by the default gtk greeter.
If you can share any idea what I may be doing wrong, or what else I should configure?
Alex
(1 rep)
May 25, 2023, 05:00 AM
• Last activity: Jun 21, 2025, 10:15 PM
2
votes
2
answers
2866
views
How to stop Gnome Keyring from asking for Login password, like it used to?
Previously, Gnome Keyring only asked for the Default Keyring password when I attempted to launch Chrome. I tried playing around with settings in Seahorse to see if there was a work around for this, other than leaving the password database unencrypted. During that process I switched the default keyri...
Previously, Gnome Keyring only asked for the Default Keyring password when I attempted to launch Chrome. I tried playing around with settings in Seahorse to see if there was a work around for this, other than leaving the password database unencrypted. During that process I switched the default keyring to the Login Keyring. Obviously, that did not impact Chrome asking for a keyring password; so, I switched the default keyring back to the Default Keyring.
Now, when Lightdm auto logs me in to Cinnamon, Gnome Keyring asks for the Login password every time, after logging in. I cancel that prompt and Gnome Keyring asks for the Default Keyring when I launch Chrome. (I'm fine with this) How do i return to the old behaviour of having the Login Keyring encrypted, but never asking for my user password? (default uses root)
I never explicitly set up a password for the Login Keyring prior, and I'm pretty sure it was encrypted before since there has been a Login keyring file since I installed Gnome Keyring a few weeks back.
ZeroPhase
(381 rep)
Jun 29, 2018, 01:31 AM
• Last activity: Jun 12, 2025, 04:09 AM
0
votes
1
answers
1995
views
xrandr - Issues using --left-of to set up a second display
I have two monitors, DP-3 with 2560x1440 resolution, and HDMI-1 with 1920x1200 resolution. I want HDMI-1 to be displayed to the left of DP-3. When I run ```xrandr --output HDMI-1 --auto --right-of DP-3``` everything displays as intended, but when I use ```--left-of``` the entirety of what originally...
I have two monitors, DP-3 with 2560x1440 resolution, and HDMI-1 with 1920x1200 resolution. I want HDMI-1 to be displayed to the left of DP-3. When I run
--output HDMI-1 --auto --right-of DP-3
everything displays as intended, but when I use --left-of
the entirety of what originally displayed on HDMI-1 gets displayed on the DP-3 monitor and the rest of what was originally displayed on DP-3 extends into the monitor of HDMI-1.
There is another thread here from a few years ago where someone was having a similar issue, but the solution posted doesn't work for me. It also is never explained why --left-of
apparently messes with scaling.
I don't know if this helps, but I'm using i3 and LightDM as my windowing and display managers
user522454
Apr 16, 2022, 03:38 PM
• Last activity: May 14, 2025, 06:03 PM
3
votes
2
answers
5344
views
Debian login loop, can't login with correct password
I've updated my repositories on synabtics the upgraded firefox to newer version, when I open it it crashes, while this I was having my hard drive plugged .. so I tried to reboot to fix Firefox crash .. From that point I can't login, tried many solutions as I can. Additional information could help yo...
I've updated my repositories on synabtics the upgraded firefox to newer version, when I open it it crashes, while this I was having my hard drive plugged .. so I tried to reboot to fix Firefox crash ..
From that point I can't login, tried many solutions as I can. Additional information could help you solving my problem that my computer reading the unplugged hard drive with its two partions .. tried to unmount it but with no success.
Mohamed Ibrahim
(161 rep)
Nov 9, 2017, 07:14 PM
• Last activity: Apr 20, 2025, 10:03 AM
0
votes
0
answers
204
views
Dbus issue when trying to run Wayland session
My distro is based on Slackware, therefore it doesn't have systemd, but SysVinit + elogind. I'm trying to use LightDM to initiliaze my desktop environment sessions, but I have either dbus services working properly or Wayland working. My `/etc/lightdm/Xsession` file is like this: ``` [ -z "$BASH" ] &...
My distro is based on Slackware, therefore it doesn't have systemd, but SysVinit + elogind. I'm trying to use LightDM to initiliaze my desktop environment sessions, but I have either dbus services working properly or Wayland working.
My
Also, when using Wayland the error above always happens.
Is there a clean solution that fixes the issues I'm facing?
/etc/lightdm/Xsession
file is like this:
[ -z "$BASH" ] && exec $SHELL --login $0 "$@"
shopt -q login_shell || exec $SHELL --login $0 "$@"
set +o posix
userresources=$HOME/.Xresources
usermodmap=$HOME/.Xmodmap
sysresources=/etc/X11/xinit/.Xresources
sysmodmap=/etc/X11/xinit/.Xmodmap
[ -f $sysresources ] && xrdb -merge $sysresources
[ -f $sysmodmap ] && xmodmap $sysmodmap
[ -f $userresources ] && xrdb -merge $userresources
[ -f $usermodmap ] && xmodmap $usermodmap
dbus-launch --exit-with-session $@
It works fine, except if I want to start a Wayland session, which in this case it doesn't load in LXQt 2.1.0 or Cinnamon 6.4.9. The log ~/.xsession-errors
says something like:
dbus-update-activation-environment: error: unable to connect to D-Bus: Failed to connect to socket /tmp/dbus-6WcQhFZXE2: No such file or directory
If I change the last line of /etc/lightdm/Xsession
to dbus-run-session -- $@
, then
the Wayland sessions work, however some services stop working properly due to a dbus problem. For instance, cron daemon (crond
), which is executed in a boot script that runs before Xsession: if cron is set to shutdown my Xfce session, it doesn't find the Xfce dbus session:

Fulalas
(119 rep)
Apr 5, 2025, 10:59 AM
• Last activity: Apr 5, 2025, 11:29 AM
1
votes
1
answers
1409
views
How do I stop my Ubuntu desktop computer from "sleeping" when nobody is logged in?
**In short** - I have an issue where my Ubuntu Desktop computer seems to "sleep" when no user is logged in, and I would love to prevent this. **More Details -** > Pre-emptive apology if something I write is unclear or redundant - I'm > very new to Linux & Ubuntu. To state the obvious - the issue is...
**In short** - I have an issue where my Ubuntu Desktop computer seems to "sleep" when no user is logged in, and I would love to prevent this.
**More Details -**
> Pre-emptive apology if something I write is unclear or redundant - I'm
> very new to Linux & Ubuntu.
To state the obvious - the issue is not my monitor turning off, it is that the computer seems to fall asleep after a few minutes of being in the user login screen with no user logged in.
The symptoms are:
- Computer visually appears powered down, lighting up only when the power button is pressed again
- Display is off
- Interacting with keyboard/mouse which are plugged in doesn't do anything
- (The real issue) servers that the computer is running are offline
This is in contrast to when I'm actually logged into my user. In this scenario, the screen can turn off after X minutes but the computer never logs out/goes to sleep (as per the configuration in
Settings
-> Power
-> Power Saving
).
This is a pretty fresh installation running Ubuntu 24.04.2 LTS. I installed Ubuntu Desktop and changed to lightdm.
Thanks in advance! Would be happy to share more info if relevant.
Clicksurfer
(13 rep)
Mar 4, 2025, 02:09 PM
• Last activity: Mar 7, 2025, 12:44 PM
0
votes
1
answers
434
views
Black screen with mouse cursor after unlocking the screen after some inactivity, on an Nvidia card
[I uploaded all logs here](https://drive.google.com/drive/folders/1eeaPYZiyEWxNmFYkiQlbnQ7g_fO9-4Oz?usp=sharing). After unlocking the PC after a period of inactivity (a few hours?), I'm often met with a black screen with nothing but a mouse cursor on it (that I can move). The only fix I found is kil...
[I uploaded all logs here](https://drive.google.com/drive/folders/1eeaPYZiyEWxNmFYkiQlbnQ7g_fO9-4Oz?usp=sharing) .
After unlocking the PC after a period of inactivity (a few hours?), I'm often met with a black screen with nothing but a mouse cursor on it (that I can move).
The only fix I found is killing the X server with CtrlAltBackspace, but that also kills all my GUI apps. Ideally I'm looking for a full fix, or at least for a more graceful way to recover from this without closing my apps.
---
Some more details:
I've started getting this issue after switching to a new laptop with an Nvidia card (the previous one had an integrated AMD card and no such issues). This is the same Arch installation (except I added NVidia drivers), so I'm sure this is Nvidia-related.
The laptop has both an integrated AMD card and a dedicated Nvidia one, but I disabled the former in the BIOS because it was causing other issues, and the PC feels more repsonsive now. I don't remember if I had this issue while having both cards on, I think not.
I can still switch to another TTY and back, and type commands in it, but I didn't find any commands that helped.
*One time* pressing random hotkeys made it unstuck, but I wasn't able to replicate that.
I can still move the mouse in this state, and the cursor changes according to the apps I'm supposed to have open. But if I click, the cursor shape gets stuck to whatever it is now.
Unplugging and plugging a second monitor doesn't help.
---
I'm using Xfce, with light-locker and lightdm-gtk-greeter. I haven't tried xfce4-screensaver instead of light-locker because it has other issues (doesn't disable backlight in the locked state).
I'm on Arch Linux, on the latest kernel which is
6.12.9-arch1-1 #1 SMP PREEMPT_DYNAMIC Fri, 10 Jan 2025 00:39:41 +0000 x86_64 GNU/Linux
.
I'm using open-source Nvidia drivers from the nvidia-open
package. I also tried nvidia-open-dkms
on the LTS kernel, but no cigar, and the LTS kernel gives me other issues.
This is the full list of nvidia-related packages I have installed, from pacman -Qs nvidia
:
local/egl-gbm 1.1.2-1
local/egl-wayland 4:1.1.17-1
local/egl-x11 1.0.0-1
local/lib32-libvdpau 1.5-3
local/lib32-nvidia-utils 565.77-1
local/libvdpau 1.5-3
local/libxnvctrl 565.57.01-1
local/nvidia-open 565.77-11
local/nvidia-prime 1.0-5
local/nvidia-settings 565.57.01-1
local/nvidia-utils 565.77-3
local/xf86-video-nouveau 1.0.18-1 (xorg-drivers)
This is a Lenovo LOQ 2024 laptop (15AHP9, 83DX0070RK). Neofetch identifies following hardware:
CPU: AMD Ryzen 7 8845HS w/ Radeon 780M Graphics (16) @
GPU: AMD ATI 05:00.0 Phoenix3
GPU: NVIDIA GeForce RTX 4050 Max-Q / Mobile
HolyBlackCat
(170 rep)
Jan 15, 2025, 08:21 AM
• Last activity: Feb 7, 2025, 07:37 AM
29
votes
7
answers
53381
views
When I log in, it hangs until crng init done
When I log in with LightDM on my laptop running Debian Unstable, it recently started to hang for around 2 minutes until `journalctl` shows the message `kernel: random: crng init done`. When I press random keys on my keyboard while it hangs, it logs in faster (around 10 seconds). Before I didn't have...
When I log in with LightDM on my laptop running Debian Unstable, it recently started to hang for around 2 minutes until
journalctl
shows the message kernel: random: crng init done
. When I press random keys on my keyboard while it hangs, it logs in faster (around 10 seconds). Before I didn't have this issue, is there any way I can fix it?
Edit: using linux-image-4.15.0-3-amd64
instead of linux-image-4.16.0-1-amd64
works, but I don't want to use an older kernel.
wb9688
(739 rep)
May 9, 2018, 07:26 AM
• Last activity: Jan 20, 2025, 12:20 AM
3
votes
1
answers
10563
views
gdm3 or lighdm not working (X11 won't start)
I am using Debian 9. After installing Gnome I only see my mouse cursor on my computer screen. I uninstalled Gnome and enabled X11 but it didn't work. I need to connect to the board I use via ssh and type > startx in order to get an image on the screen. I may have messed something up while installing...
I am using Debian 9. After installing Gnome I only see my mouse cursor on my computer screen. I uninstalled Gnome and enabled X11 but it didn't work. I need to connect to the board I use via ssh and type
> startx
in order to get an image on the screen. I may have messed something up while installing gnome.
**Update:**
apt install gdm
is not working:
root@linaro-alip:~# apt install gdm
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package gdm is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or is
only available from another source However the following packages replace
it: libgdm1 cinnamon-control-center-data
E: Package 'gdm' has no installation candidate
**Update 2:**
dpkg-reconfigure lightdm
>> I manually selected lightdm
root@linaro-alip:~# systemctl enable lightdm
Synchronizing state of lightdm.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable lightdm
The unit files have no installation config (WantedBy, RequiredBy, Also, Alias
settings in the [Install] section, and DefaultInstance for template units).
This means they are not meant to be enabled using systemctl.
Possible reasons for having this kind of units are:
1) A unit may be statically enabled by being symlinked from another unit's
.wants/ or .requires/ directory.
2) A unit's purpose may be to act as a helper for some other unit which has
a requirement dependency on it.
3) A unit may be started when needed via activation (socket, path, timer,
D-Bus, udev, scripted systemctl call, ...).
4) In case of template units, the unit is meant to be enabled with some
instance name specified.
The problem is still not fixed.
When I use the below command it says the file does not exist. How can I fix this?
update-rc.d '/etc/init.d/xserver start' defaults
update-rc.d: error: initscript does not exist: /etc/init.d//etc/init.d/xserver start
Buket
(61 rep)
Oct 15, 2021, 08:45 AM
• Last activity: Dec 1, 2024, 02:05 AM
0
votes
0
answers
47
views
Help to set up bspwm on Ubuntu in VMware
I've installed bspwm and sxhkd on Ubuntu Server LTS 24.04 in vmware. I use lightDM as display manager, qterminal as terminal emulator. When I open a terminal in bspwm gui, it looks like there are some kind of buffer: a letter I typed would not appear until I type again. (for example, when I type 'He...
I've installed bspwm and sxhkd on Ubuntu Server LTS 24.04 in vmware. I use lightDM as display manager, qterminal as terminal emulator. When I open a terminal in bspwm gui, it looks like there are some kind of buffer: a letter I typed would not appear until I type again. (for example, when I type 'Hello', the 'e' wouldn't appear until I type 'l'), backspace and enter have the same problem.
Other TTYs are alright. Any ideas why that happens? Thanks in advance.
Enthalpia
(1 rep)
Oct 25, 2024, 04:57 PM
• Last activity: Oct 25, 2024, 05:04 PM
0
votes
0
answers
25
views
Incoming network (ping/sshd) inaccessible after LightDM starts in Debian 12 (bookworm) on a 2010 iMac?
(Previously posted on https://superuser.com/ without much uptake ...) Debian 12 (bookworm) running on a 2010 iMac. After the machine boots but **before the window manager (LightDM) starts** I am able to ping and SSH into the machine from a remote machine. Once LightDM starts I can't ping or ssh from...
(Previously posted on https://superuser.com/ without much uptake ...)
Debian 12 (bookworm) running on a 2010 iMac.
After the machine boots but **before the window manager (LightDM) starts** I am able to ping and SSH into the machine from a remote machine. Once LightDM starts I can't ping or ssh from remote any more (and a running ssh session hangs). (I think this was also happening with GDM before I switched window managers, but not 100% sure and don't feel like switching back to test unless someone thinks it would be useful).
service sshd status
says sshd is still up and running, and I'm able to ping and SSH from the machine into itself (from a terminal window or from an alternative console via Alt+Ctrl+F1).
Does LightDM do something to networking/firewall settings when it starts? I haven't been able to find anything useful in dmesg
(but admittedly I don't know what I'm looking for).
The machine has a static IP address, and as far as I can tell from ifconfig
output the machine still has an interface open at that IP address (enp2s0: flags=4163 ... inet
)
Happy to provide further diagnostics on request.
Ben Bolker
(101 rep)
Sep 17, 2024, 12:07 AM
0
votes
2
answers
456
views
How to change lightdm's wallpaper per user?
I changed the display manager from sddm to lightdm. I'm using Kubuntu 22.04, and slick-greeter as lightdm's greeter. I remembered that when I was using xfce4 and changed the wallpaper in the xfce4's settings, lightdm's wallpaper was changed when I selected a different user. I want to set the wallpap...
I changed the display manager from sddm to lightdm.
I'm using Kubuntu 22.04, and slick-greeter as lightdm's greeter.
I remembered that when I was using xfce4 and changed the wallpaper in the xfce4's settings, lightdm's wallpaper was changed when I selected a different user.
I want to set the wallpaper up to be changed per user, as I did then.
However, I don't want to install xfce4 just for that purpose.
Does anyone know how to set up lightdm to change the wallpaper per user without xfce4?
TranslucentFoxHuman
(1 rep)
Apr 17, 2023, 04:50 AM
• Last activity: May 8, 2024, 09:45 PM
1
votes
0
answers
576
views
Debian 12 boot fails to load lightdm and stops
Debian 12 fails to boot after last upgrades writing sth like [failed] Lightm did not load The content of /var/log/lightdm/lightdm.log is as follows ```[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log [+0.00s] DEBUG: Starting Light Display Manager 1.26.0, UID=0 PID=722 [+0.00s] DEBUG: Loading...
Debian 12 fails to boot after last upgrades writing sth like
[failed] Lightm did not load
The content of /var/log/lightdm/lightdm.log is as follows
[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.00s] DEBUG: Starting Light Display Manager 1.26.0, UID=0 PID=722
[+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.00s] DEBUG: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus Screen "Screen0" (0)
[ 1310.592] (**) | |-->Monitor "Monitor0"
[ 1310.593] (**) | |-->Device "Card0"
[ 1310.593] (**) |-->Input Device "Mouse0"
[ 1310.593] (**) |-->Input Device "Keyboard0"
[ 1310.593] (==) Automatically adding devices
[ 1310.593] (==) Automatically enabling devices
[ 1310.593] (==) Automatically adding GPU devices
[ 1310.593] (==) Automatically binding GPU devices
[ 1310.593] (==) Max clients allowed: 256, resource mask: 0x1fffff
[ 1310.593] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[ 1310.593] Entry deleted from font path.
[ 1310.593] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[ 1310.593] Entry deleted from font path.
[ 1310.593] (**) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins,
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins
[ 1310.593] (**) ModulePath set to "/usr/lib/xorg/modules"
[ 1310.593] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
[ 1310.593] (WW) Disabling Mouse0
[ 1310.593] (WW) Disabling Keyboard0
[ 1310.729] (EE) [drm] Failed to open DRM device for pci:0000:01:00.0: -19
[ 1310.730] Number of created screens does not match number of detected devices.
Configuration failed.
[ 1310.730] (EE) Server terminated with error (2). Closing log file.
I used to try to install cuda some time before the last upgrade. It led to gui malfunctioning , so i uninstalled cuda, returned to nouveau, and ran Xorg -configure
and everything seemed to work. And it still works if i boot to the previous version of Debian on grub (sth like 6.8 instead of 6.10).
Current xorg.conf is as follows
Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "Files"
ModulePath "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/X11/misc"
FontPath "/usr/share/fonts/X11/cyrillic"
FontPath "/usr/share/fonts/X11/100dpi/:unscaled"
FontPath "/usr/share/fonts/X11/75dpi/:unscaled"
FontPath "/usr/share/fonts/X11/Type1"
FontPath "/usr/share/fonts/X11/100dpi"
FontPath "/usr/share/fonts/X11/75dpi"
FontPath "built-ins"
EndSection
Section "Module"
Load "glx"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5 6 7"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
EndSection
Section "Device"
### Available Driver options are:-
### Values: : integer, : float, : "True"/"False",
### : "String", : " Hz/kHz/MHz",
### : "%"
### [arg]: arg optional
#Option "SWcursor" # []
#Option "HWcursor" # []
#Option "NoAccel" # []
#Option "ShadowFB" # []
#Option "VideoKey" #
#Option "WrappedFB" # []
#Option "GLXVBlank" # []
#Option "ZaphodHeads" #
#Option "PageFlip" # []
#Option "SwapLimit" #
#Option "AsyncUTSDFS" # []
#Option "AccelMethod" #
#Option "DRI" #
Identifier "Card0"
Driver "nouveau"
BusID "PCI:1:0:0"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
SubSection "Display"
Viewport 0 0
Depth 1
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 4
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 8
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 15
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection
My graphics card is Nvidia GeForce 240M.
Иван Катаев
(11 rep)
Apr 29, 2024, 10:52 AM
• Last activity: Apr 29, 2024, 05:49 PM
Showing page 1 of 20 total questions