Matthias Griessmeier changed bug 1060990
What Removed Added
Status CONFIRMED NEW
Blocker --- Yes
CC   mgriessmeier@suse.com
Summary [Build 18.34] openQA test fails in kontact in wayland session, kontact window looks bleached and is marked as unresponsive [Build 18.34] kontact is unusable when running in wayland (unresponsive, crashs)

Comment # 4 on bug 1060990 from
(In reply to Fabian Vogt from comment #1)
> I tried to reproduce it locally, but failed. It might be due to RAM
> constraints, but 2GiB should be enough...

We did following steps manually as well as in openQA:
(System specs: 1 CPU, 2048M RAM)

1. start livecd
2. login with default settings
3. start kontact
4. it's a bit slow, but responsive

see openQA reference (http://opeth.suse.de/tests/6244)


When doing the same with wayland enabled (following the same steps as openQA is
doing it in http://opeth.suse.de/tests/6317), we could reproduce the issue
manually

1. Start liveCD and login
2. execute wayland startup magic
> mkdir -p ~/.config/plasma-workspace/env
> echo 'echo export GALLIUM_DRIVER=softpipe >> ~/.config/startupconfig' > ~/.config/plasma-workspace/env/softpipe.sh
3. logout and select "Plasma (Wayland)"
4. login again and start kontact
=> system gets unusable (blurry, slow, unresponsive application which leads to
crash in the end)


You are receiving this mail because: