Bug 314884 - KDE 4.10.0 gets stuck in the middle of splash screen
Summary: KDE 4.10.0 gets stuck in the middle of splash screen
Status: RESOLVED NOT A BUG
Alias: None
Product: kwin
Classification: Plasma
Component: compositing (show other bugs)
Version: 4.10.0
Platform: openSUSE Linux
: NOR grave
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-02-11 09:56 UTC by Jiri Slaby
Modified: 2013-02-12 22:21 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments
kwin_support.txt (5.85 KB, text/plain)
2013-02-11 16:03 UTC, Jiri Slaby
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jiri Slaby 2013-02-11 09:56:43 UTC
After yesterday's update to 4.10.0 (from 4.9.98), KDE no longer starts properly. The last thing
I see is the splash screen where icons like KDE, tools and disk are shown. It
continues after pressing alt-shift-f12 -- a short-cut for disabling effects. If
I enable effects again, it also stops redrawing windows.

# rpm -q `rpmqpack |grep -i kde`|sort
bundle-lang-kde-cs-12.3-4.1.noarch
flash-player-kde4-11.2.202.261-1.3.x86_64
kdeartwork4-wallpapers-weather-4.10.0-1.1.noarch
kdeartwork4-wallpapers-4.10.0-1.1.noarch
kdebase4-artwork-4.10.0-1.1.noarch
kdebase4-libkonq-4.10.0-1.1.x86_64
kdebase4-openSUSE-lang-12.3-16.1.noarch
kdebase4-openSUSE-12.3-16.1.x86_64
kdebase4-runtime-branding-upstream-4.10.0-1.1.x86_64
kdebase4-runtime-4.10.0-1.1.x86_64
kdebase4-session-4.10.0-4.3.noarch
kdebase4-workspace-branding-upstream-4.10.0-4.1.x86_64
kdebase4-workspace-ksysguardd-4.10.0-4.1.x86_64
kdebase4-workspace-liboxygenstyle-4.10.0-4.1.x86_64
kdebase4-workspace-plasma-calendar-4.10.0-4.1.x86_64
kdebase4-workspace-4.10.0-4.1.x86_64
kdelibs3-default-style-3.5.10-70.1.x86_64
kdelibs3-3.5.10-70.1.x86_64
kdelibs4-branding-upstream-4.10.0-2.1.x86_64
kdelibs4-core-4.10.0-2.1.x86_64
kdelibs4-4.10.0-2.1.x86_64
kdenlive-0.9.4-2.6.x86_64
kdepimlibs4-4.10.0-1.1.x86_64
kdepim4-runtime-4.10.0-1.1.x86_64
kde4-filesystem-4.10.0-1.1.x86_64
kde4-kgreeter-plugins-4.10.0-4.1.x86_64
kde4-l10n-cs-4.10.0-1.1.noarch
libkdecore4-4.10.0-2.1.x86_64
libkdeedu4-data-4.10.0-1.1.noarch
libkdepimlibs4-4.10.0-1.1.x86_64
libkdepim4-4.10.0-1.1.x86_64
libkde4-4.10.0-2.1.x86_64
liblockdev1-1.0.3_git201003141408-21.6.x86_64
liblockdev1-32bit-1.0.3_git201003141408-21.6.x86_64
libproxy1-config-kde4-0.4.11-1.1.x86_64
lockdev-1.0.3_git201003141408-21.6.x86_64
mozilla-kde4-integration-0.6.4-36.1.x86_64
polkit-kde-agent-1-0.99.0-14.6.x86_64
polkit-kde-kcmmodules-1-0.98.1+git20110929-4.6.x86_64
python-kde4-4.10.0-2.1.x86_64
qtcurve-kde4-1.8.14-1.3.x86_64

Reproducible: Always
Comment 1 Jiri Slaby 2013-02-11 09:59:48 UTC
Oh, and I have openGL compositioning enabled.
Comment 2 Thomas Lübking 2013-02-11 15:37:39 UTC
please run:

qdbus org.kde.kwin /Compositor setCompositing true; sleep 10; qdbus org.kde.kwin /KWin supportInformation > kwin_support.txt; sleep 5; qdbus org.kde.kwin /Compositor setCompositing false

(this will enable compositing, print the support informations into kwin_support.txt and then disable compositing - hopefully ;-)

Attach kwin_support.txt here.

XRender compositing works?
Comment 3 Jiri Slaby 2013-02-11 16:03:12 UTC
Created attachment 77140 [details]
kwin_support.txt
Comment 4 Jiri Slaby 2013-02-11 16:04:18 UTC
(In reply to comment #2)
> XRender compositing works?

Yeah.
Comment 5 Thomas Lübking 2013-02-11 16:16:28 UTC
Comment on attachment 77140 [details]
kwin_support.txt

try:
kwriteconfig --file kwinrc --group Compositing --key GLStrictBinding true
kwin --replace &
(and of course report the impact ;-)
Comment 6 Jiri Slaby 2013-02-11 16:20:08 UTC
(In reply to comment #5)
> kwriteconfig --file kwinrc --group Compositing --key GLStrictBinding true
> kwin --replace &
> (and of course report the impact ;-)

Hmm, no change.
Comment 7 Thomas Lübking 2013-02-11 19:12:23 UTC
kwrite --file kwinrc --group Compositing --key GLLegacy true
kwin --replace &

if that does not do either, try whether indirect rendering still works
KWIN_DIRECT_GL LIBGL_ALWAYS_INDIRECT=1 kwin --replace &

if that also does not work, please enable the "show paint" plugin and see whether there's region update flicker

Don't forget to reset the things above (ideally delete the keys on ~/.kde/share/config/kwinrc, k*config can't do that)
Comment 8 Jiri Slaby 2013-02-11 19:23:20 UTC
(In reply to comment #7)
> kwrite --file kwinrc --group Compositing --key GLLegacy true
> kwin --replace &

This doesn't work.

> if that does not do either, try whether indirect rendering still works
> KWIN_DIRECT_GL LIBGL_ALWAYS_INDIRECT=1 kwin --replace &

Should that be KWIN_DIRECT_GL=1 or KWIN_DIRECT_GL=0?

> if that also does not work, please enable the "show paint" plugin and see
> whether there's region update flicker

No, no region updates/no flickers.
Comment 9 Thomas Lübking 2013-02-11 19:24:41 UTC
> Should that be KWIN_DIRECT_GL=1 or KWIN_DIRECT_GL=0?

Should be "KWIN_DIRECT_GL= ", ie. ensure to unset the variable =)
Comment 10 Jiri Slaby 2013-02-11 19:26:19 UTC
(In reply to comment #9)
> > Should that be KWIN_DIRECT_GL=1 or KWIN_DIRECT_GL=0?
> 
> Should be "KWIN_DIRECT_GL= ", ie. ensure to unset the variable =)

Ok, still no cookies.
Comment 11 Thomas Lübking 2013-02-11 20:59:45 UTC
Did you update anything else (like esp. mesa)?

It's not like the window content does not update, but nothing does (also not when you attempt to move a window), yesno?

Please deactivte all effect plugins and set the sacel method to "smooth" or "crisp" (but this is unlikely gonna help)
Comment 12 Jiri Slaby 2013-02-11 21:14:09 UTC
(In reply to comment #11)
> Did you update anything else (like esp. mesa)?

Not Mesa (it was and is 9.0.2). But intel driver from 2.20.19 to 2.21.0. Let me check if downgrading helps.

> It's not like the window content does not update, but nothing does (also not
> when you attempt to move a window), yesno?

Exactly, the whole screen is stuck. When I move a window, nothing happens until I disable compositing with alt-shift-f12.
Comment 13 Jiri Slaby 2013-02-12 18:58:29 UTC
(In reply to comment #12)
> (In reply to comment #11)
> > Did you update anything else (like esp. mesa)?
> 
> Not Mesa (it was and is 9.0.2). But intel driver from 2.20.19 to 2.21.0. Let
> me check if downgrading helps.

No, but downgrading kernel does. Baah. Sorry for the noise.
Comment 14 Thomas Lübking 2013-02-12 19:07:18 UTC
Nevermind. Happens more then less often =)
Comment 15 Jiri Slaby 2013-02-12 22:21:09 UTC
Just for the record:
https://lkml.org/lkml/2013/2/12/513