Bug 355787 - KDE5 (Plasma 5) returns black screen afeter xorg-server updated to 1.18
Summary: KDE5 (Plasma 5) returns black screen afeter xorg-server updated to 1.18
Status: RESOLVED DOWNSTREAM
Alias: None
Product: kwin
Classification: Plasma
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-11-23 14:36 UTC by SinClaus
Modified: 2015-12-03 13:49 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:
thomas.luebking: NVIDIA+


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description SinClaus 2015-11-23 14:36:35 UTC
Linux XXXX 4.2.5-1-ARCH #1 SMP PREEMPT Tue Oct 27 08:13:28 CET 2015 x86_64 GNU/Linux
NVIDIA Corporation GT218 [GeForce 210] (rev a2)
nvidia 340.96-2.1 driver
xorg-server 1.18.0-3

after reboot I have black screen and frame only from auto-started application with black inside.

Reproducible: Always
Comment 1 Thomas Lübking 2015-11-23 22:44:47 UTC
> frame only from auto-started application
That means you can see the titlebar and border of the window?

Suspend the compositor (SHIFT+Alt+F12) and also try xrender compositing in "kcmshell5 kwincompositing" but notice that you're on a legacy driver and 340.96 is the first and "hot" version claimed to be compatible with brand new Xorg ABI 20

=> I bet all your arms it's between nvidia and Xorg, redirection of windows will simply fail.
=> Tagging invalid unless convinced that it's *not* nvidia ./. ABI 20
Comment 2 SinClaus 2015-11-24 02:40:08 UTC
(In reply to Thomas Lübking from comment #1)
> > frame only from auto-started application
> That means you can see the titlebar and border of the window?
> 
> Suspend the compositor (SHIFT+Alt+F12) and also try xrender compositing in
> "kcmshell5 kwincompositing" but notice that you're on a legacy driver and
> 340.96 is the first and "hot" version claimed to be compatible with brand
> new Xorg ABI 20
> 
> => I bet all your arms it's between nvidia and Xorg, redirection of windows
> will simply fail.
> => Tagging invalid unless convinced that it's *not* nvidia ./. ABI 20

I have to say that KDE4 works OK with this driver and xorg 1.18 on my home comp.
Comment 3 Martin Flöser 2015-11-24 06:58:40 UTC
> I have to say that KDE4 works OK with this driver and xorg 1.18 on my home comp.

Qt 4 uses way less OpenGL. With Qt 5 each and every window is rendered through OpenGL. If you have a broken driver it really hurts with Qt 5.
Comment 4 Thomas Lübking 2015-11-24 07:36:13 UTC
- Do or do you not see the windows titlebar?
- Does suspending the compositor change anything or not?
- Does XRender compositing work or not?
- Does downgrading Xorg and driver alone make a difference?
Comment 5 SinClaus 2015-11-24 07:46:37 UTC
I downgrade Xorg to 1.17 and system work OK with this video driver.
Comment 6 Thomas Lübking 2015-11-24 08:06:26 UTC
I could assume more/extra trouble with new ABI, nvidia (legacy) and fences.
-> Feel free to try
    KWIN_EXPLICIT_SYNC=0 kwin_x11 --replace &
Comment 7 SinClaus 2015-11-25 03:40:40 UTC
There was no chance to apply this settings: I try to reinstall Xorg-server 1.18 but boot was stopped on Xorg init. Systems with KDE4 works OK. System with  KDE5 works on Xorg-server V 1.17.
Comment 8 Thomas Lübking 2015-11-25 08:27:22 UTC
How can KDE4 work if "boot was stopped on Xorg init"?? KDE4 relies on Xorg just as much as KDE5. Maybe you changed the DM as well (and SDDM fails where KDM works, likely due to SDDM relying on OpenGL?)
Did you keep the Xorg log?
Comment 9 SinClaus 2015-11-25 08:36:37 UTC
Boot is stopped with KDE5 only, but I know why, I hope. Info will be later.
Comment 10 SinClaus 2015-11-30 03:06:25 UTC
Second try.
Boot was stopped on "Reached target Graphical Interface". Xorg can't find display driver, but don't try to load nvidia driver.
Comment 11 Thomas Lübking 2015-11-30 08:04:25 UTC
(In reply to SinClaus from comment #10)

> Boot was stopped on "Reached target Graphical Interface". Xorg can't find
> display driver, but don't try to load nvidia driver.

Because the nvidia driver will be ABI incompatible, check the latest Xorg log.

I do frankly not see where this has anything to do with KDE5, you won't get KDE4 running from this state either. You likely refer to different distributions/versions by this where one drags in the newer Xorg or the other provides a compatible nvidia blob.
Comment 12 SinClaus 2015-12-03 05:46:08 UTC
I don't catch what do you mean... Latest Xorg log shows that Xorg looking for nouveau, vesa and so on, but nvidia.
Comment 13 Thomas Lübking 2015-12-03 08:50:18 UTC
I mean this:
> Boot was stopped on "Reached target Graphical Interface". Xorg can't find
> display driver, but don't try to load nvidia driver.

It means that you fail to start X11 (because lacking a compatible display driver) - this has *nothing* (repeat after me: not a thing) to do with KDE. Not with KDE4 nor with KDE5. Not with Qt and not with SDDM or KDM or whatever. It means that you need to install a compatible display driver. Nouveau (and likely VESA) will require kms, while nvidia will require kms to be disabled.
Once you have trouble *after* reaching the X11 layer, they *may* be related to KWin/KF5/Qt (or the driver), but until then, there's nothing we could do and certainly no (kwin) bug.
Comment 14 SinClaus 2015-12-03 11:39:11 UTC
Pleas read by characters: Comp with KDE4, same Nvidia driver and new Xorg works without problems.
Comment 15 Thomas Lübking 2015-12-03 13:49:52 UTC
You *clearly* stated:
> Xorg can't find display driver, but don't try to load nvidia driver.

If X doesn't find a usable display driver, it won't start. And that is *certainly* NOT related to the session that you're about to start *after* the X server started.