Bug 361200

Summary:	Plasmashell Signal: Illegal Instruction - On KUBUNTU 16.04 Beta2 - During Install - Under Hyper-V
Product:	[Plasma] plasmashell	Reporter:	Harrison <sainokawara.sisyphus>
Component:	general	Assignee:	David Edmundson <kde>
Status:	RESOLVED WORKSFORME
Severity:	crash	CC:	bshah, plasma-bugs
Priority:	NOR	Keywords:	triaged
Version First Reported In:	5.5.95
Target Milestone:	1.0
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	First page of "backtrace" Second page of "backtrace"

Description Harrison 2016-03-30 18:27:55 UTC

Problem occurs at boot of .iso doing Install:  I did see a "Logon Request" screen and then the crash occurred when it appeared to try to use the Plasma Desktop.  In addition to running the new Kubuntu 16.04 Beta 2 under Windows 10 Hyper-V, it is on the new Intel Xeon E3-1275-v5 AND I am using the onboard processor graphics support, not a graphics card.

I will be happy to run/test anything you have that will allow you collect any additional information you require.  There are so many new things involved in this failure, I wouldn't know where to start.

Reproducible: Always

Steps to Reproduce:
1. Install under Windows 10 Hyper-V
2. Boot new Kubuntu 16.04 Beta 2 .ISO File for Install
3. Possibly related to new Intel Xeon E3-1275-v5 onboard processor graphics support

Actual Results:  
Get message: "Executable: plasmashell PID: 1922 Signal: Illedgal instruction (4)

Unfortunately, "Not Enough Information to submit "bug report" through the normal channel.

Expected Results:  
Not "crashed".

If someone has something they would like me to try or report, I will be more than happy to do so.  Unfortunately, I am currently limited on trying this in a different physical environment: non-Hyper-V, non-Windows 10, using a graphics card instead of the onboard E3-1275-v5 processor graphics support.

Comment 1 Harrison 2016-03-31 22:49:23 UTC

Installed Kubuntu 15.10 under Hyper-V on Intel E3-1275-v5 & chipset C236 and everything worked fine.

Comment 2 David Edmundson 2016-04-02 06:49:44 UTC

I need a backtrace with symbols.

please install -dbg packages for plasma and reproduce

Comment 3 Harrison 2016-04-02 15:12:25 UTC

Created attachment 98208 [details]
First page of "backtrace"

The crash occurs so early in the Install process that it is difficult for me to capture any data.  However, Kubuntu appears to be operational so I might be able to install/configure SSH after the crash so I can copy the "backtrace" to my Windows system.  Until then, perhaps, the following two screen capture pages contain something of value.  And, I definitely saw a "flash" of the Plasma Desktop before it crashed this time.

Comment 4 Harrison 2016-04-02 15:15:07 UTC

Created attachment 98209 [details]
Second page of "backtrace"

Comment 5 Harrison 2016-04-02 19:03:48 UTC

Good news, the problem ONLY occurs under Hyper-V!  I created an Install DVD and it boots just fine.  So, the problem must be related to something in the release of Plasmashell that is shipped with Kubuntu 16.04 [famous last words].  Is there any possibility of having someone else with a different environment try this under Hyper-V to eliminate the possibility that it is unique to my environment: Intel XEON E3-1275-v5 running on a ASRockRack C236M systemboard with the Intel C236 chipset using the onboard processor graphics support?

If the "backtrace" would be of additional value, I will see whether there is some way of creating a file that I can send to you.  The problem is, as I previously said, this problem occurs so early in the Install process, there isn't even any formatted disks upon which to put the backtrace file when the crash occurs.  And, Hyper-V imposes limitations/restrictions on the test environment [by design].

Comment 6 Andrew Crouthamel 2018-09-26 22:06:32 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Comment 7 Andrew Crouthamel 2018-10-27 04:22:07 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!