Bug 466204 - Total system freeze after login if an external monitor is connected (X11 and Wayland, Intel graphics)
Summary: Total system freeze after login if an external monitor is connected (X11 and ...
Status: RESOLVED FIXED
Alias: None
Product: kwin
Classification: Plasma
Component: multi-screen (show other bugs)
Version: 5.27.1
Platform: Other Linux
: NOR grave
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-02-21 19:54 UTC by Guido
Modified: 2024-05-17 15:33 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Guido 2023-02-21 19:54:48 UTC
SUMMARY
Black screen at startup if an external monitor is connected.
My configuration is: 
1) internal display: off
2) external display: on, primary

After the login screen (sddm) both displays turn black and the system hangs. I can't switch to text console with ctrl+alt+f2...f7

No problem if I connect the external display after plasmashell starts.



SOFTWARE/OS VERSIONS
Operating System: Manjaro Linux 
KDE Plasma Version: 5.27.1
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8
Kernel Version: 6.2.0-1-MANJARO (64-bit)
Graphics Platform: X11
Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz
Memory: 15.4 GiB of RAM
Graphics Processor: Mesa Intel® Xe Graphics
Manufacturer: Dell Inc.
Product Name: Inspiron 5502
Comment 1 Nate Graham 2023-02-22 18:26:48 UTC
Does this still happen if you configure the internal display to be on?

Can you attach the output of `kscreen-doctor -o` when the system is in a good state, i.e. when you connect the external display after plasma starts and then disable the internal screen?
Comment 2 Guido 2023-02-25 10:14:55 UTC
Output: 67 eDP1 disabled connected priority 0 Panel Modes: 72:1920x1080@60! 1887:1920x1080@60 1888:1920x1080@48 1889:1680x1050@60 1890:1400x1050@60 1891:1600x900@60 1892:1600x900@60 1893:1600x900@60 1894:1280x1024@60 1895:1400x900@60 1896:1400x900@60 1897:1280x960@60 1898:1368x768@60 1899:1368x768@60 1900:1368x768@60 1901:1280x800@60 1902:1280x800@60 1903:1280x720@60 1904:1280x720@60 1905:1280x720@60 1906:1024x768@60 1907:1024x576@60 1908:1024x576@60 1909:1024x576@60 1910:960x540@60 1911:960x540@60 1912:960x540@60 1913:800x600@60 1914:800x600@56 1915:864x486@60 1916:864x486@60 1917:864x486@60 1918:640x480@60 1919:720x405@60 1920:720x405@60 1921:720x405@59 1922:640x360@60 1923:640x360@59 1924:640x360@60 Geometry: 0,0 1920x1080 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown
Output: 68 DP1 disabled disconnected priority 0 DisplayPort Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown
Output: 69 HDMI1 enabled connected priority 1 HDMI Modes: 1889:1680x1050@60 1894:1280x1024@60 1906:1024x768@60 1913:800x600@60 1914:800x600@56 1918:640x480@60 1948:1920x1080@60! 1949:1920x1080@50 1950:1920x1080@60* 1951:1920x1080@60 1952:1920x1080@50 1953:1920x1080@30 1954:1920x1080@25 1955:1920x1080@24 1956:1920x1080@60 1957:1920x1080@30 1958:1920x1080@24 1959:1280x1024@75 1960:1280x720@60 1961:1280x720@50 1962:1280x720@60 1963:1024x768@75 1964:800x600@75 1965:720x576@50 1966:720x576@50 1967:720x480@60 1968:720x480@60 1969:720x480@60 1970:720x480@60 1971:640x480@75 1972:640x480@73 1973:640x480@67 1974:640x480@60 1975:720x400@70 Geometry: 0,0 1920x1080 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown
Output: 70 VIRTUAL1 disabled disconnected priority 0 Unknown Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown
Comment 3 Guido 2023-02-25 10:18:15 UTC
(In reply to Nate Graham from comment #1)
> Does this still happen if you configure the internal display to be on?

I'm trying. The bug occurs often but not every time, so I need to do more tests.
Comment 4 Guido 2023-02-25 10:26:46 UTC
Another thing I notice is that if I start with the 5.15 kernel, after logging in the internal screen turns off and the system starts on the external one without pause, whereas with the 6.2 kernel the external screen goes black for 2 seconds and then turns on again, unless it remains black because of the bug.
The bug in this report did not occur with version 5.26, but the black screen for 2 seconds with the 6.x kernel also happened with 5.26
Comment 5 Guido 2023-02-27 10:41:13 UTC
I would like to add one more detail: after logging in, the Plasma splash screen appears for 2-3 seconds, only then the screen goes black and the PC completely freezes.
Comment 6 Guido 2023-02-27 12:13:54 UTC
(In reply to Guido from comment #3)
> (In reply to Nate Graham from comment #1)
> > Does this still happen if you configure the internal display to be on?
> 
> I'm trying. The bug occurs often but not every time, so I need to do more
> tests.

I tried and the bug arises also when the internal dosplay is setted on.
Comment 7 Nate Graham 2023-02-27 17:15:14 UTC
Thanks, now can you attach the output of `kscreen-doctor -o` after the bug has happened?

That way I can compare the output between working and broken system states,
Comment 8 Guido 2023-02-27 17:18:45 UTC
(In reply to Nate Graham from comment #7)
> Thanks, now can you attach the output of `kscreen-doctor -o` after the bug
> has happened?
> 
> That way I can compare the output between working and broken system states,

I can't. When the bug appears, the system is freezed. I need to hard reset the laptop
Comment 9 Nate Graham 2023-02-27 18:55:19 UTC
Darn. Thanks.

Does it work if you log in to a Wayland session? Or is that broken too?
Comment 10 Guido 2023-02-27 19:22:16 UTC
(In reply to Nate Graham from comment #9)
> Darn. Thanks.
> 
> Does it work if you log in to a Wayland session? Or is that broken too?

Yes, also in Wayland session.
Comment 11 Nate Graham 2023-02-27 19:23:49 UTC
Thanks.
Comment 12 Guido 2024-05-17 15:33:25 UTC
it seems solved in Plasma 6