Self explanatory, I am have a problem where every time i boot the login screen would appear on the wrong monitor of the 2 i have, not a deal breaker but i would like to solve this if it is possible. I also would like to know if there is a way to boot straight into endeavor instead of waiting 5 seconds for different boot options.
Hi.
Run xrandr in terminal to see a list of your connected monitors.
Then run xrandr --output your_primary_monitor --primary to set your default monitor but replace “your_primary_monitor” with the actual name of your desired primary monitor from the output in the first command above
If for any reason this command resets when you reboot, you may need to force it to autorun on every boot in a script.
Thanks ill restart right away and tell you about the results
Nope, the login windows appears in the wrong monitor still, which is weird cause when it goes to sleep it does appear in the right one. Ill try what you said and force a script to run on boot
If I recall, there’s sometimes an option for this in the BIOS of your motherboard depending on the specific board. I had an ASUS board in the past that had this specific setting buried in there somewhere. Please take a close look.
What display manager is in use, SDDM? If so, try setting up a script in /usr/share/sddm/scripts to set the display as described here: https://wiki.archlinux.org/title/SDDM#Login_session_appears_on_an_unexpected_display
Login session appears on an unexpected display
It can happen that the SDDM login session appears on a different display than your primary display if multiple displays are connected. This problem can be annoying if the secondary display is rotated and the primary display is not. A simple fix to this problem is to use xrandr to configure the displays before the login session using Xsetup script. E.g. here xrandr reports that there are two connected displays where the secondary display (DP-2) is left of the primary display (DP-4).
# xrandr | grep -w connected DP-2 connected 2160x3840+0+0 left (normal left inverted right x axis y axis) 597mm x 336mm DP-4 connected primary 3840x2160+2160+0 (normal left inverted right x axis y axis) 697mm x 392mmThe following Xsetup recreates the above setup for the login window:
/usr/share/sddm/scripts/Xsetup#!/bin/sh # Xsetup - run as root before the login dialog appears xrandr --output DP-4 --auto --primary xrandr --output DP-2 --left-of DP-4 --rotate left --noprimary
Really sorry for the late response,
Here is my output of the xrandr:
HDMI-0 connected 1080x1920+0+0 left (normal left inverted right x axis y axis) 598mm x 336mm
DP-2 connected primary 2560x1440+1080+480 (normal left inverted right x axis y axis) 698mm x 393mm
my main monitor is DP-2.
So should i create a script in that directory even though a folder does not exist currently?
aso how do i make it run before the login dialog appears
What is also interesting is that my steam notifications appear in my other monitor even though its not my main one
Yes, my understanding from reading that wiki post is SDDM will honor the script if you add it to /usr/share/sddm/scripts. If /usr/share/sddm/scripts does not exist, you can create it with sudo mkdir.
Just make the script executable, and I believe SDDM will take it from there.
I was trying to find that sddm dir since i dont have it, turns out, my display manager is light display manager, so i dont know if what you sent me is still valid, also this is my output:
● lightdm.service - Light Display Manager
Loaded: loaded (/usr/lib/systemd/system/lightdm.service; enabled; preset: disabled)
Active: active (running) since Sat 2023-12-09 16:37:35 -05; 3h 6min ago
Docs: man:lightdm(1)
Main PID: 999 (lightdm)
Tasks: 6 (limit: 38331)
Memory: 92.9M (peak: 109.1M)
CPU: 5min 35.175s
CGroup: /system.slice/lightdm.service
├─ 999 /usr/bin/lightdm
└─1006 /usr/lib/Xorg :0 -seat seat0 -auth /run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
Dec 09 16:37:35 zaMoon-PC systemd[1]: Starting Light Display Manager…
Dec 09 16:37:35 zaMoon-PC systemd[1]: Started Light Display Manager.
Dec 09 16:37:37 zaMoon-PC lightdm[1030]: pam_unix(lightdm-greeter:session): session opened for user lightdm(uid=966) by (uid=0)
Dec 09 16:38:12 zaMoon-PC lightdm[1106]: gkr-pam: unable to locate daemon control file
Dec 09 16:38:12 zaMoon-PC lightdm[1106]: gkr-pam: stashed password to try later in open session
Dec 09 16:38:12 zaMoon-PC lightdm[1106]: pam_unix(lightdm:session): session opened for user jyumg(uid=1000) by jyumg(uid=0)
Dec 09 16:38:12 zaMoon-PC lightdm[1106]: gkr-pam: unlocked login keyring
In that case you should be able to set the correct monitor in /etc/lightdm/lightdm.conf, see here: https://wiki.archlinux.org/title/LightDM#LightDM_displaying_in_wrong_monitor
LightDM displaying in wrong monitor
If you are using multiple monitors, LightDM may display in the wrong one (e.g. if your primary monitor is on the right). To force the LightDM login screen to display on a specific monitor, edit
/etc/lightdm/lightdm.confand change the display-setup-script parameter like this:/etc/lightdm/lightdm.confdisplay-setup-script=xrandr --output *HDMI-1* --primaryReplace HDMI-1 with your real monitor ID, which you can find from xrandr command output.
Alternatively, if you are using the GTK greeter, you can edit
/etc/lightdm/lightdm-gtk-greeter.confand add the active-monitor parameter like this:/etc/lightdm/lightdm-gtk-greeter.conf[greeter] active-monitor=0Replace 0 with the desired display number.