Grub 2 occasionally boots to CLI when default is GUI

Duglas · 12-25-2022, 09:02 AM

I am running Debian Bullseye. When I upgraded to Bullseye I used the latest Netinst iso, then added my favorite packages to customize to what I wanted.
The PC is a Dell Optiplex 7040 with 2 monitors. I powerdown every night.

Most times when I powerup, Grub boots to Debian and the window manager.
Occasionally it boots to the CLI!

Easy fix -- Login, type password, and "startx", problem solved until next time.

This never happened before Bullseye and Grub 2.

Now the same problem has started on my spouse's PC. My "Easy fix" is not so easy, if I am out.

Anybody have any ideas?
thanks in advance.

mrmazda · 12-25-2022, 01:59 PM

Before typing startx, try typing cat /var/log/Xorg.0.log | pastebinit and providing here the URI. It sounds like your DM is failing. Have you tried waiting at least a minute to see of given more time it will succeed? Also include here output from inxi -Gaz run from an X terminal.

Duglas · 01-01-2023, 09:06 AM

I will try your instructions, the next time it happens. Thanks.

Duglas · 06-11-2023, 07:59 AM

I tried the instructions above, but there is nothing in Xorg.0.log. Probably because X has not started yet!
I also ran $ inxi -Gaz and got the following:
Graphics: Device-1: Intel HD Graphics 530 vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:1912
class ID: 0300
Display: server: X.Org 1.20.11 driver: loaded: modesetting alternate: fbdev,vesa display ID: :0 screens: 1
Screen-1: 0 s-res: 3040x900 s-dpi: 96 s-size: 804x238mm (31.7x9.4") s-diag: 838mm (33")
Monitor-1: HDMI-1 res: 1440x900 hz: 60 dpi: 99 size: 370x230mm (14.6x9.1") diag: 436mm (17.2")
Monitor-2: HDMI-2 res: 1600x900 hz: 60 dpi: 92 size: 443x249mm (17.4x9.8") diag: 508mm (20")
OpenGL: renderer: Mesa Intel HD Graphics 530 (SKL GT2) v: 4.6 Mesa 20.3.5 direct render: Yes

Is there anything in this that causes booting the CLI instead of X?

mrmazda · 06-12-2023, 12:12 AM

Quote:

Originally Posted by Duglas

I tried the instructions above, but there is nothing in Xorg.0.log. Probably because X has not started yet!

I see nothing in inxi output to suggest what the problem may be.

Did you literally find an Xorg.0.log that's empty, or did you not find any Xorg.0.log in /var/log/? An Xorg.0.log should be found somewhere if X ever tried to start. If her PC is using Gnome, it may be that Xorg.0.log is sequestered in her ~/.local/share/xorg/.

If you ever share inxi output again, or any other command output, please follow the instructions here.