Bug 954434

Summary:	Plasma crashes immediately after first start after installation when using libvirt/qemu
Product:	[openSUSE] openSUSE Tumbleweed	Reporter:	Oliver Kurz <okurz>
Component:	KDE Workspace (Plasma)	Assignee:	E-Mail List <opensuse-kde-bugs>
Status:	RESOLVED DUPLICATE	QA Contact:	E-mail List <qa-bugs>
Severity:	Major
Priority:	P5 - None	CC:	okurz, tchvatal
Version:	Current
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Bug Depends on:
Bug Blocks:	954538
Attachments:	kdeinit5 crash window in blank plasma session journalctl_current_boot-stripped.log Xorg.0.log xsession-errors kdeinit5-20151122-215606.kcrash.txt

Description Oliver Kurz 2015-11-10 11:34:51 UTC

Created attachment 655356 [details]
kdeinit5 crash window in blank plasma session

observation:
blank and unusable plasma5 session, only error window about kdeinit5 (see screenshot)

steps to reproduce:
 1. virt-install --name opensuse_leap --ram 2048 --disk path=~/local/virtual/opensuse_leap2.qcow2,size=8 --vcpus 1 --os-type linux --os-variant generic --location 'http://download.opensuse.org/distribution/leap/42.1/repo/oss/'
 2. wait for end of installation and first boot
 3. observe error

problem:
I reproduced this problem using virt-install (three times) based on the online repo, one time using the virt-manager install helper using the dvd-iso as well as on Tumbleweed (TODO ref bug).
different hypotheses (Hx):
 - H1: plasma erroneously detects 3D acceleration available which is not in virtual machine
 - H2: could be related to https://bugzilla.opensuse.org/show_bug.cgi?id=949978
 - H3: Something related to my host environment


suggestions:
experiments (Ex-y) corresponding to hypotheses (Hx):
 - E1-1: Try with different backends or virtualization solutions, e.g. virtualbox
 - E3-1: Someone else reproduce it

Comment 1 Tomáš Chvátal 2015-11-10 13:11:16 UTC

Please provide the backtrace that is in the secondtab of the crasher. Also install debug symbols as without it we can't identify it properly.

Comment 2 Oliver Kurz 2015-11-10 13:16:42 UTC

Problem is that it seems there is no window manager installed so actually I can not "click" and call anything. Will try to call window manager externally.

Comment 3 Oliver Kurz 2015-11-19 13:58:11 UTC

Created attachment 656654 [details]
journalctl_current_boot-stripped.log

Comment 4 Oliver Kurz 2015-11-19 13:58:42 UTC

Created attachment 656655 [details]
Xorg.0.log

Comment 5 Oliver Kurz 2015-11-19 13:59:09 UTC

Created attachment 656656 [details]
xsession-errors

Comment 6 Oliver Kurz 2015-11-22 22:28:16 UTC

Created attachment 656882 [details]
kdeinit5-20151122-215606.kcrash.txt

I reproduced the issue with a fresh install of Tumbleweed snapshot 20151118. Immediately at launch of a fresh Tumbleweed installation x86_64 from DVD ISO with KDE desktop selected using the install wizard in "virt-manager" I get a black screen with only the mouse cursor. After switching to a text console and back I see the window of crashed kdeinit5 as reported before. I can actually click on the second tab of the crash reporter and also call "Install Debug Symbols" which unfortunately fails. I guess I need to add a debug symbol repository?

https://en.opensuse.org/openSUSE:Bugreport_KDE mentions some packages which are all outdated (for kde5). Also, the "factory" repo is mentioned, which should be tumbleweed. Actually, it redirects to the tumbleweed repo which is ok. Finally, I managed to install all necessary debuginfo packages and provide a hopefully usable stack trace.

Comment 7 Tomáš Chvátal 2015-11-24 12:19:05 UTC

Basically graphiccard error:

#9  QMessageLogger::fatal (this=this@entry=0x7ffe529b1d60, msg=msg@entry=0x7fe26a576e60 "Cannot create window: no screens available") at global/qlogging.cpp:781

@xorg: you guys handle bugs in qemu thingies or it is on qemu guys? If so please reassign.

Comment 8 Tomáš Chvátal 2015-12-08 12:00:26 UTC

Actually this is the xcb bug.

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