Display output remains disabled when monitor is connected after boot without an active display
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 28/100
- Tipo de issue
- Error
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- linux, python
- Área
- desktop-dev
Línea de trabajo
The payload names no Slick Greeter source file, and the component responsible is explicitly unresolved. Start by reading the linked cinnamon issue and the Debian/Fedora threads, then inspect how the greeter's X11/Vala code initialises the display at startup and whether it subscribes to RandR events. Done means the maintainers have settled whether greeter, LightDM or another component owns hotplug activation, followed by a patch that activates a connected output when no CRTC is assigned at the greeter.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Summary
When Linux Mint boots without a connected monitor, subsequently connecting a display does not automatically activate the display output at the LightDM login screen.
Xorg successfully detects the monitor, reads its EDID and generates RandR hotplug events. However, the display output remains disabled until explicitly activated using xrandr.
An event-driven RandR listener has been implemented and successfully tested as a workaround.
System information
Component | Version / model -- | -- Distribution | Linux Mint 22.3 Cinnamon Computer | Lenovo ThinkCentre M75q Gen 2 GPU | AMD Radeon integrated graphics (PCI ID 1002:1638) BIOS | M47KT41A Linux kernels tested | 6.17.0-40-generic, 7.0.0-42-generic Xorg server | 2:21.1.12-1ubuntu1.9 Xorg AMDGPU driver | 23.0.0-1ubuntu0.24.04.1 Alternative Xorg driver tested | modesetting libdrm-amdgpu1 | 2.4.125-1ubuntu0.1~24.04.2 Mesa DRI | 25.2.8-0ubuntu0.24.04.4 LightDM | 1.30.0-0ubuntu14 Slick Greeter | 2.2.6+zena Cinnamon | 6.6.9+zena Muffin | 6.6.3+zena systemd | 255.4-1ubuntu8.18 Plymouth | 24.004.60-1ubuntu7.2 Python Xlib | 0.33-2 RandR protocol | 1.5 Monitor | Samsung Odyssey G9 S49DG912SU Display switch | Ugreen AV701 (65878)Implemented workaround
An external Python Xlib RandR event listener was implemented to verify whether the missing automatic activation could be addressed without restarting LightDM or interfering with the active desktop session.
The listener:
Subscribes to RandR screen and output change events.
Waits two seconds after the last relevant event for the connection state to settle.
Verifies that the active local session belongs to the LightDM greeter.
Checks whether at least one connected output has available display modes.
Checks that no output has an assigned CRTC.
Activates an available connected output using
xrandr --auto --primary.
The greeter session is identified using the following systemd-logind properties:
Class=greeter
Service=lightdm-greeter
Type=x11
Active=yes
Seat=seat0
Display=:0
Remote=noThe listener is event-driven and does not continuously poll the display state. It does not intentionally modify display settings during a normal Cinnamon desktop session.
The listener is managed by a systemd service associated with LightDM.
Example journal output from a successful cold-boot test:
INFO: RandR listener started
INFO: Activating output DisplayPort-0
INFO: Output DisplayPort-0 activatedThe workaround was successfully tested with both kernel versions, a direct DisplayPort connection and the original display-switch configuration.
Repeated display switching during an active Cinnamon desktop session continued to work normally, without observed changes to the configured resolution or refresh rate.
The Python implementation and systemd service configuration can be provided if useful.
Related reports
A similar Linux Mint issue:
https://github.com/linuxmint/cinnamon/issues/12866
A similar issue involving LightDM and GTK Greeter reported by a Debian user:
https://lists.debian.org/debian-user/2026/02/msg00056.html
A related report involving Fedora and a KVM switch:
https://lists.debian.org/debian-user/2026/02/msg00062.html
These reports suggest that the issue may not be specific to Slick Greeter, AMD graphics or Linux Mint.
Requested improvement
Could Slick Greeter handle RandR hotplug events by automatically activating an available connected display when no display output is currently active?
Alternatively, could the maintainers clarify whether this functionality should be implemented in Slick Greeter, LightDM or another component?
The exact component responsible for the missing activation has not been conclusively identified. The external listener is a tested workaround rather than a proposed upstream patch.
Additional diagnostic information and the workaround source code can be provided upon request.
- Lenguaje dominante
- Vala
- Estrellas
- 441
- Forks
- 72
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Preparar el entorno
Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de linuxmint/slick-greeter
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 25/100
linuxmint/slick-greeter#296 ·
-
Bootup now requires password to get to desktop after setting it to no password for the last 6 yearsAbierto
Dificultad 4/5 3-5 días Aptitud para principiantes 38/100
linuxmint/slick-greeter#292 · 3 comentarios ·
-
bug
Dificultad 4/5 3-5 días Aptitud para principiantes 48/100
linuxmint/slick-greeter#291 ·
-
Dificultad 4/5 3-5 días Aptitud para principiantes 45/100
linuxmint/slick-greeter#289 · 1 comentario ·
-
Dificultad 4/5 3-5 días Aptitud para principiantes 55/100
linuxmint/slick-greeter#287 ·
Todos los issues de linuxmint/slick-greeter
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
yetanotherbrowser/yab#1008 ·
Los mantenedores suelen responder en 2 días
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 87/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
longbridge/nsh#2540 ·
Los mantenedores suelen responder en 1 día
-
Closing a pinned tab jumps to the Tabs section instead of the next open pinned tabPosiblemente ocupada @seenimohamed la tomó hoy. Abiertobug
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
ardia-browser/ardia#2769 ·
Los mantenedores suelen responder en 1 día
-
Copy/paste broken on Linux: ClassCastException (HeapByteBuffer → byte[]) in ClipboardActions.pasteAbierto3rd party problem bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100