| View previous topic :: View next topic |
| Author |
Message |
hoacker
Guru
Joined: 04 Aug 2007
Posts: 491
Location: Bürstadt, Germany
|
 Posted: Fri Feb 24, 2017 8:29 pm Post subject: [solved] KDE: Plasmashell crashes frequently |
 |
|
Hi there.
On my laptop Plasmashell crashes very often, sometimes 2 or 3 times within one hour. Kill and restart plasmashell helps, but this is so annoying. This started last year but only rare. It became worse somewhen this month
Current package: kde-frameworks/plasma-5.29.0 (since Jan. 19. Before 5.26.0, which also crashed, if I recall correctly).
I've searched the net for tips but none helped so far:
- clear "~/.cache"
- switch compositor (OpenGL 2.0 vs. 3.1)
- try other xorg-server (happens with both 1.18.4 and 1.19.1)
| Code: | # lspci
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) |
| Code: | # glxinfo | grep -i vendor
server glx vendor string: SGI
client glx vendor string: Mesa Project and SGI
Vendor: Intel Open Source Technology Center (0x8086)
OpenGL vendor string: Intel Open Source Technology Center |
emerge --info: http://pastebin.com/QnRyw2nH
Anybody got an idea? Any help appreciated.
Last edited by hoacker on Sat Feb 25, 2017 9:31 pm; edited 1 time in total |
|
| Back to top |
|
 |
asturm
Developer
Joined: 05 Apr 2007
Posts: 6876
Location: Austria
|
| Posted: Fri Feb 24, 2017 8:36 pm Post subject: |
|
|
Probably something went wrong at some xf86-video-intel snapshot. You should definitely check dmesg for errors and maybe switch to modeset driver instead. Even Intel devs seem to recommend that now...
_________________
backend.cpp:92:2: warning: #warning TODO - this error message is about as useful as a cooling unit in the arctic |
|
| Back to top |
|
|
hoacker
Guru
Joined: 04 Aug 2007
Posts: 491
Location: Bürstadt, Germany
|
| Posted: Fri Feb 24, 2017 8:47 pm Post subject: |
|
|
Danke, asturm.
Checked dmesg and indeed I get the same error multiple times. Have no idea if this is related.
| Code: | # dmesg
mce: [Hardware Error]: Machine check events logged |
| Code: |
# mcelog --client
mcelog: client connect: No such file or directory
mcelog: client command write: Transport endpoint is not connected
mcelog: client read: Invalid argument
mcelog: client connect: No such file or directory
mcelog: client command write: Transport endpoint is not connected
mcelog: client read: Invalid argument |
I'll try modeset driver. I just need to figure out, how to. Don't worry, the search engine is my friend... |
|
| Back to top |
|
|
hoacker
Guru
Joined: 04 Aug 2007
Posts: 491
Location: Bürstadt, Germany
|
| Posted: Sat Feb 25, 2017 9:33 pm Post subject: |
|
|
No crashes with modeset driver so far. Problem seems to be solved.
Thanks again, asturm. |
|
| Back to top |
|
|
|
Desktop Environments
