Bug 347963

Summary: crashes when starting opensuse tumbleweed, had to roll back to kde4
Product: [Plasma] plasmashell Reporter: paul janson <plj>
Component: generalAssignee: David Edmundson <kde>
Status: RESOLVED DUPLICATE    
Severity: grave CC: bhush94, plasma-bugs
Priority: NOR    
Version: 5.3.0   
Target Milestone: 1.0   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: automatic generated crash report

Description paul janson 2015-05-19 18:37:18 UTC 
When starting opensuse tumbleweed with default plasma 5.3, it crashes plasma shell; and each retry. This happens each reboot, so I never got a working desktop. I had to select KDE 4 to make the netbook workable again.

Reproducible: Always

Steps to Reproduce:
1. Install thumbleweed with plasma 5.3 as default desktop on a axcer D522 and reboot.
2.
3.

Actual Results:  
It shows a crash report window which allows restarts which just crashes again. I could go to the debugger. I had to open another command window and use commandline yast to remove plasma5.3 and reinstall kde4 to get a booting netbook.

Expected Results:  
It should have shown a desktop:)

I use a (upgraded) Acer D522 netbook. This has an AMD netbook chipset C60 (dualcore 1GHz 64bits). I upgaded the netbook from 1GB to 4GB ram, which just works fine on 64bit linux and 32bit windows7. It has a build in GPU Type: Radeon HD 6290
Comment 1 David Edmundson 2015-05-19 23:23:45 UTC 
I'm sorry you had problems.
Unfortuantely I can't do anything without more info than that.

When you see the crash window, submit a bug report from there and it will have information about why it crashed, or click the developer tab and copy and paste the contents.
Comment 2 paul janson 2015-05-20 19:44:51 UTC 
Created attachment 92741 [details]
automatic generated crash report
Comment 3 Bhushan Shah 2015-05-21 03:13:13 UTC 

*** This bug has been marked as a duplicate of bug 284474 ***
Comment 4 Bhushan Shah 2015-05-21 03:55:11 UTC 
erm my bad.. pasted wrong bug id

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