Bug 346549 - Login to a KDE 5.2 fails 90%+ of the time, when logging in everything is choppy
Summary: Login to a KDE 5.2 fails 90%+ of the time, when logging in everything is choppy
Status: RESOLVED WORKSFORME
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (show other bugs)
Version: 5.2.2
Platform: Fedora RPMs Linux
: NOR grave
Target Milestone: 1.0
Assignee: David Edmundson
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2015-04-24 10:35 UTC by Hannu Valtonen
Modified: 2018-10-27 02:54 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Hannu Valtonen 2015-04-24 10:35:53 UTC
Using Plasma 5.2.2 (frameworks 5.9.0) on Fedora 22 most of the time even login to a plasma session fails, leaving ksplash progress bar hanging about 3/4 of the way through the progress bar. 

Logging through SSH doesn't show any special CPU usage in ksplash, or in the one instance of me actually being able to successfully log in. The one time I actually managed to log in, mouse was choppy as in updating the cursor every 5 seconds or so. Clicking on the K-menu did open the menu after a while (1 minute or so) but would not let me start any applications. 

The hardware is an Ivy Bridge Apple Mac Mini. On my other machines (with different HW) the same packages seem to work fine.


Reproducible: Sometimes

Steps to Reproduce:
1. Try to login into a plasma session





One suspicious thing that did pop up was a lot DRM edid messages like these in dmesg:

[  149.883162] [drm:drm_edid_block_valid [drm]] *ERROR* EDID checksum is invalid, remainder is 213
[  150.142936] [drm:drm_edid_block_valid [drm]] *ERROR* EDID checksum is invalid, remainder is 92
[  151.448017] [drm:drm_edid_block_valid [drm]] *ERROR* EDID checksum is invalid, remainder is 228
[  151.752206] [drm:drm_edid_block_valid [drm]] *ERROR* EDID checksum is invalid, remainder is 159
[  152.664505] [drm:drm_edid_block_valid [drm]] *ERROR* EDID checksum is invalid, remainder is 221
[  152.968244] [drm:drm_edid_block_valid [drm]] *ERROR* EDID checksum is invalid, remainder is 55
[  153.989404] [drm:drm_edid_block_valid [drm]] *ERROR* EDID checksum is invalid, remainder is 111
[  154.965288] [drm:drm_edid_block_valid [drm]] *ERROR* EDID checksum is invalid, remainder is 55
[  155.944422] [drm:drm_edid_block_valid [drm]] *ERROR* EDID checksum is invalid, remainder is 195
Comment 1 David Edmundson 2015-04-24 10:41:37 UTC
Can you look in .config for any files that end in .lock ?
Comment 2 Hannu Valtonen 2015-04-24 10:58:33 UTC
There are none within ~/.config.
Comment 3 David Edmundson 2015-04-24 11:03:27 UTC
OK, next questions.

When you ssh in, is plasmashell running?
is kwin_x11 running?

Is there anything useful in ~/.xsession-errors.
Comment 4 Hannu Valtonen 2015-04-24 11:13:33 UTC
Just a lot of EDID modelines like these:

huhti 24 14:11:50 ohmu3 kernel: [drm:drm_edid_block_valid [drm]] *ERROR* EDID checksum is invalid, remainder is 67
huhti 24 14:11:50 ohmu3 /usr/libexec/gdm-x-session[6686]: (II) intel(0): EDID vendor "APP", prod id 37415
huhti 24 14:11:50 ohmu3 /usr/libexec/gdm-x-session[6686]: (II) intel(0): DDCModeFromDetailedTiming: Ignoring: We don't handle stereo.
huhti 24 14:11:50 ohmu3 /usr/libexec/gdm-x-session[6686]: (II) intel(0): DDCModeFromDetailedTiming: Ignoring tiny 565x0 mode
huhti 24 14:11:50 ohmu3 /usr/libexec/gdm-x-session[6686]: (II) intel(0): DDCModeFromDetailedTiming: Ignoring: We don't handle stereo.
huhti 24 14:11:50 ohmu3 /usr/libexec/gdm-x-session[6686]: (II) intel(0): Printing DDC gathered Modelines:
huhti 24 14:11:50 ohmu3 /usr/libexec/gdm-x-session[6686]: (II) intel(0): Modeline "2560x1440"x0.0  241.50  2560 2608 2640 2720  1440 1443 1448 1481 +hsync -vsync (88.8 kHz eP)
huhti 24 14:11:50 ohmu3 /usr/libexec/gdm-x-session[6686]: (II) intel(0): Modeline "1280x720"x0.0   74.50  1280 1344 1472 1664  720 723 728 748 -hsync +vsync (44.8 kHz e)
huhti 24 14:11:51 ohmu3 kernel: [drm:drm_edid_block_valid [drm]] *ERROR* EDID checksum is invalid, remainder is 240
huhti 24 14:11:51 ohmu3 /usr/libexec/gdm-x-session[6686]: (II) intel(0): EDID vendor "APP", prod id 37415
huhti 24 14:11:51 ohmu3 /usr/libexec/gdm-x-session[6686]: (II) intel(0): Printing DDC gathered Modelines:
huhti 24 14:11:51 ohmu3 /usr/libexec/gdm-x-session[6686]: (II) intel(0): Modeline "2560x1440"x0.0  241.50  2560 2608 2640 2720  1440 1443 1448 1481 +hsync -vsync (88.8 kHz eP)
huhti 24 14:11:51 ohmu3 /usr/libexec/gdm-x-session[6686]: (II) intel(0): Modeline "1280x720"x0.0   74.50  1280 1344 1472 1664  720 723 728 748 -hsync +vsync (44.8 kHz e)
huhti 24 14:11:51 ohmu3 kernel: [drm:drm_edid_block_valid [drm]] *ERROR* EDID checksum is invalid, remainder is 169
huhti 24 14:11:51 ohmu3 /usr/libexec/gdm-x-session[6686]: (II) intel(0): EDID vendor "APP", prod id 37415
huhti 24 14:11:51 ohmu3 /usr/libexec/gdm-x-session[6686]: (II) intel(0): DDCModeFromDetailedTiming: Ignoring: We don't handle stereo.
huhti 24 14:11:51 ohmu3 /usr/libexec/gdm-x-session[6686]: (II) intel(0): DDCModeFromDetailedTiming: Ignoring tiny 256x0 mode
huhti 24 14:11:51 ohmu3 /usr/libexec/gdm-x-session[6686]: (II) intel(0): DDCModeFromDetailedTiming: Ignoring: We don't handle stereo.
huhti 24 14:11:51 ohmu3 /usr/libexec/gdm-x-session[6686]: (II) intel(0): Printing DDC gathered Modelines:
huhti 24 14:11:51 ohmu3 /usr/libexec/gdm-x-session[6686]: (II) intel(0): Modeline "2560x1440"x0.0  241.50  2560 2608 2640 2720  1440 1443 1448 1481 +hsync -vsync (88.8 kHz eP)
huhti 24 14:11:51 ohmu3 /usr/libexec/gdm-x-session[6686]: (II) intel(0): Modeline "1280x720"x0.0   74.50  1280 1344 1472 1664  720 723 728 748 -hsync +vsync (44.8 kHz e)
huhti 24 14:11:52 ohmu3 kernel: [drm:drm_edid_block_valid [drm]] *ERROR* EDID checksum is invalid, remainder is 99
huhti 24 14:11:52 ohmu3 /usr/libexec/gdm-x-session[6686]: (II) intel(0): EDID vendor "APP", prod id 37415
huhti 24 14:11:52 ohmu3 /usr/libexec/gdm-x-session[6686]: (II) intel(0): Printing DDC gathered Modelines:
huhti 24 14:11:52 ohmu3 /usr/libexec/gdm-x-session[6686]: (II) intel(0): Modeline "2560x1440"x0.0  241.50  2560 2608 2640 2720  1440 1443 1448 1481 +hsync -vsync (88.8 kHz eP)
huhti 24 14:11:52 ohmu3 /usr/libexec/gdm-x-session[6686]: (II) intel(0): Modeline "1280x720"x0.0   74.50  1280 1344 1472 1664  720 723 728 748 -hsync +vsync (44.8 kHz e)
huhti 24 14:11:53 ohmu3 kernel: [drm:drm_edid_block_valid [drm]] *ERROR* EDID checksum is invalid, remainder is 208
huhti 24 14:11:53 ohmu3 /usr/libexec/gdm-x-session[6686]: (II) intel(0): EDID vendor "APP", prod id 37415
huhti 24 14:11:53 ohmu3 /usr/libexec/gdm-x-session[6686]: (II) intel(0): DDCModeFromDetailedTiming: Ignoring: We don't handle stereo.
huhti 24 14:11:53 ohmu3 /usr/libexec/gdm-x-session[6686]: (II) intel(0): Printing DDC gathered Modelines:
huhti 24 14:11:53 ohmu3 /usr/libexec/gdm-x-session[6686]: (II) intel(0): Modeline "2560x1440"x0.0  241.50  2560 2608 2640 2720  1440 1443 1448 1481 +hsync -vsync (88.8 kHz eP)
huhti 24 14:11:53 ohmu3 /usr/libexec/gdm-x-session[6686]: (II) intel(0): Modeline "1280x720"x0.0   74.50  1280 1344 1472 1664  720 723 728 748 -hsync +vsync (44.8 kHz e)
Comment 5 Hannu Valtonen 2015-04-24 11:20:46 UTC
And both kwin_x11 and plasmashell seem to be running:

$ ps ax|grep plasmashell
 7674 ?        Sl     0:00 /usr/bin/plasmashell --shut-up
 7714 pts/1    S+     0:00 grep --color=auto plasmashell
$ ps ax|grep kwin_x11
 7662 ?        Sl     0:00 kwin_x11
 7718 pts/1    S+     0:00 grep --color=auto kwin_x11
Comment 6 Martin Klapetek 2015-05-13 16:16:12 UTC
Is there any other process using your CPU? I had a similar problem with MacBook and a kernel interrupt keeping the CPU busy all the time (it was a bug in the SMC or something).
Comment 7 Hannu Valtonen 2015-05-13 17:02:57 UTC
No, on the Mac minis the CPUs are fairly idle. It is far more likely that it has something to do with searching for EDID modelines since it keeps on spamming those forever.

(And yes I've seen the thing you describe elsewhere on a Macbook Air which has an issue with GPE66 interrupt)
Comment 8 Martin Klapetek 2015-05-14 09:03:20 UTC
Have you tried different DE like Gnome/Unity and have you tried logging in using SDDM (which is what we officially recommend and support)?
Comment 9 Hannu Valtonen 2015-05-14 09:13:55 UTC
Yes Gnome3 3.16.1 works just fine. (as does KDE 4.x) Haven't tried with SDDM (since the login works just fine on other machines with a similar software stack) 

I can give SDDM a try though.
Comment 10 Hannu Valtonen 2015-05-22 10:52:33 UTC
With SDDM it actually works. Seems to be realted to GDM wayland setup that Fedora 22 defaults to.
Comment 11 Martin Klapetek 2016-03-11 18:44:26 UTC
Is this still reproducible with newest GDM and Plasma?
Comment 12 Andrew Crouthamel 2018-09-26 22:14:10 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 13 Andrew Crouthamel 2018-10-27 02:54:22 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!