I have no idea what you’re doing but again, you’re back to gdm and wayland.
Im doing nothing, I just had to delete the /etc/lightdm/lightdm.conf to make my computer turn on again
Other than that I did nothing else
I’m not sure whether you’re making fun of me or your system is making fun of you, I don’t know of a way of automagically switching login manager on its own.
Please attach the log files
/var/log/gpu-manager.log
/var/log/lightdm/lightdm.log
I promise you Im more frustrated than you about this and I am not making fun of you.
I have concatenated the 2 log files to one file and have separated them using a title looks like this:
##############################################
######## file name
##############################################
files.log (11.1 KB)
So then your system is making fun of you. This is really mysterious. According to the logs, when switched to lightdm, everything should work right but it doesn’t. Please switch back to lightdm
sudo dpkg-reconfigure lightdm
and then post
xrandr --listproviders
and
xrandr --verbose
Hi,
SO it seems like the computer won’t change to lightdm even after
sudo dpkg-reconfigure lightdm
you can see the output are the same:
Screen 0: minimum 320 x 200, current 5760 x 2160, maximum 8192 x 8192
XWAYLAND3 connected 3840x2160+0+0 (0x25) normal (normal left inverted right x axis y axis) 340mm x 190mm
Identifier: 0x2d5
Timestamp: 24239
Subpixel: unknown
Gamma: 1.0:1.0:1.0
Brightness: 0.0
Clones:
CRTC: 0
CRTCs: 0
Transform: 1.000000 0.000000 0.000000
0.000000 1.000000 0.000000
0.000000 0.000000 1.000000
filter:
3840x2160 (0x25) 712.750MHz -HSync +VSync *current +preferred
h: width 3840 start 4160 end 4576 total 5312 skew 0 clock 134.18KHz
v: height 2160 start 2163 end 2168 total 2237 clock 59.98Hz
XWAYLAND4 connected 1920x1080+3840+0 (0x24) normal (normal left inverted right x axis y axis) 530mm x 300mm
Identifier: 0x2ec
Timestamp: 24239
Subpixel: unknown
Gamma: 1.7:-0.37:-0.54
Brightness: 0.0078
Clones:
CRTC: 1
CRTCs: 1
Transform: 1.000000 0.000000 0.000000
0.000000 1.000000 0.000000
0.000000 0.000000 1.000000
filter:
1920x1080 (0x24) 173.000MHz -HSync +VSync *current +preferred
h: width 1920 start 2048 end 2248 total 2576 skew 0 clock 67.16KHz
v: height 1080 start 1083 end 1088 total 1120 clock 59.96Hz
Providers: number : 0
Weird and weirder. Try enabling it the hard way:
sudo systemctl disable display-manager
sudo systemctl disable gdm
ln -s /lib/systemd/system/lightdm.service /etc/systemd/system/display-manager.service
sudo systemctl enable display-manager
When I try to enable I get this:
Failed to enable unit: Refusing to operate on linked unit file display-manager.service
Should be ok. Does lightdm start after reboot?
I promise I am not messing with you:
This is the output (Main difference is that now its XWAYLAND0/1 and not 3/4) :
Screen 0: minimum 320 x 200, current 5760 x 2160, maximum 8192 x 8192
XWAYLAND0 connected 1920x1080+3840+0 (0x24) normal (normal left inverted right x axis y axis) 530mm x 300mm
Identifier: 0x21
Timestamp: 21642
Subpixel: unknown
Gamma: 1.0:1.0:1.0
Brightness: 0.0
Clones:
CRTC: 0
CRTCs: 0
Transform: 1.000000 0.000000 0.000000
0.000000 1.000000 0.000000
0.000000 0.000000 1.000000
filter:
1920x1080 (0x24) 173.000MHz -HSync +VSync *current +preferred
h: width 1920 start 2048 end 2248 total 2576 skew 0 clock 67.16KHz
v: height 1080 start 1083 end 1088 total 1120 clock 59.96Hz
XWAYLAND1 connected 3840x2160+0+0 (0x25) normal (normal left inverted right x axis y axis) 340mm x 190mm
Identifier: 0x23
Timestamp: 21642
Subpixel: unknown
Gamma: 1.0:1.0:1.0
Brightness: 0.0
Clones:
CRTC: 1
CRTCs: 1
Transform: 1.000000 0.000000 0.000000
0.000000 1.000000 0.000000
0.000000 0.000000 1.000000
filter:
3840x2160 (0x25) 712.750MHz -HSync +VSync *current +preferred
h: width 3840 start 4160 end 4576 total 5312 skew 0 clock 134.18KHz
v: height 2160 start 2163 end 2168 total 2237 clock 59.98Hz
I have no idea what’s going on, your system behaves completely erratically. You should consider a reinstall, it doesn’t react to any commands.
for those who point to similar issue: I just had similar scenario and what I’ve figured out is realy silly:
I’ve used https://linuxconfig.org/how-to-disable-blacklist-nouveau-nvidia-driver-on-ubuntu-20-04-focal-fossa-linux as a first link to disable nouvea-driver but I even haven’t read the name of the question properly. and here I am, I’ve just putted nvidia-driver in blacklist and wondered why I see similar issue on my machine.
long story short:
sudo rm /etc/modprobe.d/blacklist-nvidia-nouveau.conf
and create /etc/modprobe.d/blacklist-nouveau.conf with same contents:
blacklist nouveau
options nouveau modeset=0
and dont forget to set “ubuntu” instead of “Wayland” on your login screen
silly silly, very silly ><
*hope no one will point to same issue