Bug 1156945 - Graphic issues with latest kernel
Summary: Graphic issues with latest kernel
Status: RESOLVED DUPLICATE of bug 1156928
Alias: None
Product: openSUSE Distribution
Classification: openSUSE
Component: Kernel (show other bugs)
Version: Leap 15.1
Hardware: x86-64 Other
: P5 - None : Normal with 1 vote (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-11-16 23:48 UTC by Caleb McKay
Modified: 2019-11-18 09:10 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Caleb McKay 2019-11-16 23:48:31 UTC
User-Agent:       Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:70.0) Gecko/20100101 Firefox/70.0
Build Identifier: 

Clean install of 15.1 with KDE worked fine. After installing updates and rebooting started getting strange behavior. Screen would begin blinking during plymouth screens. Login screen would eventually come up as normal, but after login I would get a blank desktop. After about 5 minutes, other components such as desktop icons, menus, etc would eventually load. But occasionally still get screen blinking, like when opening firefox. Thought maybe it was a KDE problem, so I did another clean install with XFCE instead. Get the same exact behavior. So to rule out the kernel first, I installed the current 4.19 kernel from OBS and the problem ceased. I don't know what information would be relevant to troubleshoot, but I'd be happy rollback the kernel to stock, reinstall, provide, logs or whatever else might help.

Reproducible: Always

Steps to Reproduce:
1.Update kernel
2.restart
3.
Actual Results:  
Display turns off and on repeatedly during plymouth. Once logged in, desktop takes an excessive time to load.
Comment 1 Tristan Miller 2019-11-18 09:10:47 UTC
Boldly closing this is as a duplicate of my report, younger by two days. (And according to the comments there, the reporter concurs that this is a dupe.)

*** This bug has been marked as a duplicate of bug 1156928 ***