Hybrid mode finish current session when connect external monitor
See original GitHub issueAll was good until yersterday system update, after that, on next boot appears login screen (SDDM), but I have automatic login, so it was odd, thent I disconnect everything and destopt load successfully, but when I connect HDMI current session was finished and turn me to login screen, so if I enable integrated (intel) or Nvidia, it works ok.
System info
- Archlinux 5.12.15-arch1-1
- KDE
- SDDM
- Lenovo Legion Y530 (GTX-1050)
- optimus-manager 1.4
- Your custom optimus-manager configuration file at
/etc/optimus-manager/optimus-manager.conf
, if you made one
Logs 7] INFO: # Xorg pre-start hook [7] INFO: Previous state was: {‘type’: ‘pending_pre_xorg_start’, ‘requested_mode’: ‘nvidia’, ‘current_mode’: ‘hybrid’} [7] INFO: Requested mode is: nvidia [8] ERROR: Config parsing : error in option “dri” in section [intel] : invalid value “0” [8] INFO: Falling back to default value “3” [8] ERROR: Config parsing : error in option “dri” in section [amd] : invalid value “0” [8] INFO: Falling back to default value “3” [22] INFO: Writing to /etc/X11/xorg.conf.d/10-optimus-manager.conf [22] INFO: Writing state {‘type’: ‘pending_post_xorg_start’, ‘switch_id’: ‘20210712T162943’, ‘requested_mode’: ‘nvidia’} [22] INFO: Xorg pre-start hook completed successfully. [6] INFO: # Xorg post-start hook [6] INFO: Running xrandr commands [271] INFO: Running /etc/optimus-manager/xsetup-nvidia.sh [276] ERROR: Config parsing : error in option “dri” in section [intel] : invalid value “0” [276] INFO: Falling back to default value “3” [276] ERROR: Config parsing : error in option “dri” in section [amd] : invalid value “0” [276] INFO: Falling back to default value “3” [281] INFO: Writing state {‘type’: ‘done’, ‘switch_id’: ‘20210712T162943’, ‘current_mode’: ‘nvidia’} [282] INFO: Xorg post-start hook completed successfully.
Issue Analytics
- State:
- Created 2 years ago
- Comments:8
Top GitHub Comments
This is fixed in the latest xorg server version, so I think this can be closed.
The culprit is the xorg-server 1.20.12,there is a patch incoming but for the moment downgrade to 1.20.11 and it will fix the issue
https://gitlab.freedesktop.org/xorg/xserver/-/issues/1195