Summary: | plasmashell occasionally crashes inQSGBatchRenderer::Renderer::renderBatches() | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | Jiri Slaby <jirislaby> |
Component: | general | Assignee: | David Edmundson <kde> |
Status: | RESOLVED UPSTREAM | ||
Severity: | crash | CC: | albertosdneto, ali, andreas.blochberger, andrew, anton.ermolenko, artur.cuvasov, aseques, baito30, bertil.bonus, bhush94, blackmetalowiec, boitshokomosholi, bugs, bugseforuns, bugskdeorgth, deutschkurs2015madrid, dezelin, dmitry.gulin, dvdlvrdb, dylan.bedin, elo.edson, emelenas, emrecio, evan, facorread, fairbanksmorgan, forsyth.daniel, friesoft, g111, geisserml, gekapes, gerhard.riener, gilberto.nunes32, grgoffe, hayas, hotmusicfan, info, internet_user, jakubkolar, james.ellis, jcg.apollosoyuz, jonrysh, joshmassey25, jr, kde, kde, kde, kirys, kns7, kortatu, kropotkin, krzysztof.cichy, lagodasr, lee295012, lenar, m.billanitsch, masa.dessy, mgbeltranb, mike-romberg, mitya57, nate, nfd, niklas.laxstrom, nilsrehwald+KDE, p92, pavel.nedr, pedron.alexandre, pereira.alex, petrbren, pizzicato_str, plasma-bugs, ppalaga, r1backman, ralf.neugierig, ralph, ramindeh, rdieter, reavertm, robert-kde, rosand86, ruedberued, ruth.cheesley, shawn.starr, sp_4_wn, support, thenscheid, thomas.pasch, trashman, travneff, tyduptyler13, ufo0815, v.gladshtein, valentine.stubbs, valorie.zimmerman, vikigoyal, vivek.saxena, vljubovic, waynelai01011231, wikispam, yury.donskoy, zorethspam, zpk.aquila |
Priority: | NOR | Keywords: | drkonqi |
Version: | 5.3.1 | ||
Target Milestone: | 1.0 | ||
Platform: | openSUSE | ||
OS: | Linux | ||
See Also: |
https://bugs.kde.org/show_bug.cgi?id=354604 https://bugs.kde.org/show_bug.cgi?id=410964 |
||
Latest Commit: | Version Fixed In: | ||
Attachments: | attachment-26543-0.html |
Description
Jiri Slaby
2015-06-23 08:57:43 UTC
*** This bug has been marked as a duplicate of bug 349677 *** *** Bug 349842 has been marked as a duplicate of this bug. *** this is different from the other one. this is https://bugs.freedesktop.org/show_bug.cgi?id=86281 *** Bug 350152 has been marked as a duplicate of this bug. *** *** Bug 350170 has been marked as a duplicate of this bug. *** *** Bug 350193 has been marked as a duplicate of this bug. *** *** Bug 350230 has been marked as a duplicate of this bug. *** *** Bug 350420 has been marked as a duplicate of this bug. *** *** Bug 350479 has been marked as a duplicate of this bug. *** *** Bug 350529 has been marked as a duplicate of this bug. *** *** Bug 350024 has been marked as a duplicate of this bug. *** *** Bug 350678 has been marked as a duplicate of this bug. *** *** Bug 350683 has been marked as a duplicate of this bug. *** *** Bug 350701 has been marked as a duplicate of this bug. *** *** Bug 350706 has been marked as a duplicate of this bug. *** An observation: deactivating compositing, installing oxygen themes etc., restarting and reactivating compositing seems to fix things for me. (In reply to Martin Tlustos from comment #16) > An observation: deactivating compositing, installing oxygen themes etc., > restarting and reactivating compositing seems to fix things for me. Tried that already, but in my case nothing changed. Maybe amount of crashes decreased (maybe not, that's just an observation), but the traces were similar and error was still occurring. *** Bug 350842 has been marked as a duplicate of this bug. *** *** Bug 350835 has been marked as a duplicate of this bug. *** *** Bug 350902 has been marked as a duplicate of this bug. *** *** Bug 351227 has been marked as a duplicate of this bug. *** As a workaround you can export environment variable QT_XCB_FORCE_SOFTWARE_OPENGL=1 which will work round the buggy driver, at the expense of being slower. *** Bug 351509 has been marked as a duplicate of this bug. *** *** Bug 351933 has been marked as a duplicate of this bug. *** *** Bug 352114 has been marked as a duplicate of this bug. *** *** Bug 352132 has been marked as a duplicate of this bug. *** *** Bug 352142 has been marked as a duplicate of this bug. *** I declare this: LIBGL_ALWAYS_SOFTWARE="true" and works fine here... Thanks! *** Bug 352172 has been marked as a duplicate of this bug. *** *** Bug 352175 has been marked as a duplicate of this bug. *** *** Bug 352180 has been marked as a duplicate of this bug. *** *** Bug 352196 has been marked as a duplicate of this bug. *** *** Bug 352189 has been marked as a duplicate of this bug. *** *** Bug 352203 has been marked as a duplicate of this bug. *** *** Bug 352212 has been marked as a duplicate of this bug. *** *** Bug 352210 has been marked as a duplicate of this bug. *** *** Bug 352231 has been marked as a duplicate of this bug. *** *** Bug 352244 has been marked as a duplicate of this bug. *** *** Bug 352257 has been marked as a duplicate of this bug. *** *** Bug 352286 has been marked as a duplicate of this bug. *** *** Bug 352244 has been marked as a duplicate of this bug. *** There's another workaround not listed here: ========== A workaround is simply to switch back to the older UXA acceleration method from the current default SNA method in the intel DDX. One way to do this is to put the following in e. g. /etc/X11/xorg.conf.d/20-intel.conf: Section "Device" Identifier "Intel Graphics" Driver "intel" Option "AccelMethod" "uxa" EndSection *** Bug 352300 has been marked as a duplicate of this bug. *** *** Bug 352309 has been marked as a duplicate of this bug. *** *** Bug 352342 has been marked as a duplicate of this bug. *** *** Bug 352335 has been marked as a duplicate of this bug. *** *** Bug 352380 has been marked as a duplicate of this bug. *** *** Bug 352352 has been marked as a duplicate of this bug. *** *** Bug 352360 has been marked as a duplicate of this bug. *** *** Bug 352417 has been marked as a duplicate of this bug. *** *** Bug 352389 has been marked as a duplicate of this bug. *** *** Bug 352433 has been marked as a duplicate of this bug. *** *** Bug 352439 has been marked as a duplicate of this bug. *** *** Bug 352456 has been marked as a duplicate of this bug. *** *** Bug 352467 has been marked as a duplicate of this bug. *** (In reply to David Edmundson from comment #42) > There's another workaround not listed here: > > ========== > A workaround is simply to switch back to the older UXA acceleration method > from the current default SNA method in the intel DDX. One way to do this is > to put the following in e. g. /etc/X11/xorg.conf.d/20-intel.conf: > > Section "Device" > Identifier "Intel Graphics" > Driver "intel" > Option "AccelMethod" "uxa" > EndSection This workaround seems to have worked for me. But this *just* started within the last couple of months. *Then* it became worse since last Thursday's update (had to switch desktop environments to lxde/failsafe). Was the default changed without testing? If so, OK, but they should have rolled out a conf to cover this, and if people were interested, then change it over. It's a waste of a work day. *** Bug 352496 has been marked as a duplicate of this bug. *** *** Bug 352505 has been marked as a duplicate of this bug. *** *** Bug 352515 has been marked as a duplicate of this bug. *** This bug has been RESOLVED UPSTREAM. Where is the fix in the release process? In particular, when will it appear as an update to Fedora 22? (Please pardon my ignorance about this.) It means it's Fedora's problem, they are aware of this and releasing the fix is their job. There isn't anything we can do. Sorry Created attachment 94499 [details] attachment-26543-0.html I had thought that FIXED UPSTREAM means that the fix is upstream from you. But it seems you ARE upstream. I will query Fedora about this. BTW: Where can I read about the nature of the bug and the fix? On my system the problem has been pretty severe, sometimes a crash every half hour or so. All the best - jon On Thu, 2015-09-10 at 15:15 +0000, David Edmundson wrote: > https://bugs.kde.org/show_bug.cgi?id=349519 > > --- Comment #61 from David Edmundson <kde@davidedmundson.co.uk> --- > It means it's Fedora's problem, they are aware of this and releasing > the fix is > their job. > > There isn't anything we can do. Sorry For fedora users here, you can watch downstream bug https://bugzilla.redhat.com/show_bug.cgi?id=1259443 for progress on getting fixes/workarounds deployed *** Bug 352546 has been marked as a duplicate of this bug. *** So, can this file /etc/X11/xorg.conf.d/20-intel.conf: just be created by hand to resolve this issue? It doesn't exist on my Fedora 22 system. (In reply to Yury Donskoy from comment #65) > So, can this file /etc/X11/xorg.conf.d/20-intel.conf: just be created by > hand to resolve this issue? It doesn't exist on my Fedora 22 system. yes. Reboot afterwards so X can pickup the change. You can confirm UXA rendering via 'cat /var/log/Xorg.0.log | grep UXA'. any return is good - try '... |grep SNA' and you will see no result meaning SNA is not in use. i did notice a small performance hit when scrolling and moving windows around, but it's very slight. It's fixed the issue on my T450s FC22 and just waiting for FC to release the proposed bugfix previously mentioned in 63. *** Bug 352609 has been marked as a duplicate of this bug. *** Thanks for the advice. It's been stable for me since I created the file yesterday, not crashing once in that time. Before, it was going down every half-hour or so. *** Bug 352632 has been marked as a duplicate of this bug. *** *** Bug 352678 has been marked as a duplicate of this bug. *** Just as an update for fedora users: FC22 received the required intel SNA/mesa update yesterday. update: 'mesa-10.6.3-2.20150729.fc22'. fix report: https://bodhi.fedoraproject.org/updates/FEDORA-2015-15543 *** Bug 352694 has been marked as a duplicate of this bug. *** This bug also impacts Kubuntu 15.10 *** Bug 352972 has been marked as a duplicate of this bug. *** *** Bug 353007 has been marked as a duplicate of this bug. *** Kubuntu should get the patch to workaround it as part of the mesa 11.0.0 update https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1484279 (In reply to veehexx from comment #71) > Just as an update for fedora users: FC22 received the required intel > SNA/mesa update yesterday. update: 'mesa-10.6.3-2.20150729.fc22'. > fix report: https://bodhi.fedoraproject.org/updates/FEDORA-2015-15543 The update does seem to have cured the problem. I installed the fix in #42, which cured the problem, and removed it yesterday 9/21 at 7:00am. The problem has stayed cured. *** Bug 353109 has been marked as a duplicate of this bug. *** *** Bug 352979 has been marked as a duplicate of this bug. *** I've fedora 22 latest update and I'm affected by this issue also with uxa driver :( *** Bug 353609 has been marked as a duplicate of this bug. *** *** Bug 353681 has been marked as a duplicate of this bug. *** *** Bug 353673 has been marked as a duplicate of this bug. *** *** Bug 353791 has been marked as a duplicate of this bug. *** *** Bug 354031 has been marked as a duplicate of this bug. *** *** Bug 354155 has been marked as a duplicate of this bug. *** *** Bug 354243 has been marked as a duplicate of this bug. *** *** Bug 353923 has been marked as a duplicate of this bug. *** *** Bug 354577 has been marked as a duplicate of this bug. *** *** Bug 354593 has been marked as a duplicate of this bug. *** *** Bug 354619 has been marked as a duplicate of this bug. *** *** Bug 354788 has been marked as a duplicate of this bug. *** *** Bug 354913 has been marked as a duplicate of this bug. *** *** Bug 355101 has been marked as a duplicate of this bug. *** (In reply to Jonathan Ryshpan from comment #77) > (In reply to veehexx from comment #71) > > Just as an update for fedora users: FC22 received the required intel > > SNA/mesa update yesterday. update: 'mesa-10.6.3-2.20150729.fc22'. > > fix report: https://bodhi.fedoraproject.org/updates/FEDORA-2015-15543 > > The update does seem to have cured the problem. I installed the fix in #42, > which cured the problem, and removed it yesterday 9/21 at 7:00am. The > problem has stayed cured. Unfortunately, the problem is not completely cured. Plasmashell still crashes, though much less frequently than before the update. *** Bug 355209 has been marked as a duplicate of this bug. *** If I apply the workaround in comment 42 (https://bugs.kde.org/show_bug.cgi?id=349519#c42), it causes this DisplayPort related bug to resurface: https://bugs.kde.org/show_bug.cgi?id=349362 Plugging in a DisplayPort cable to DisplayPort 1.2 capable screen with the UXA change in causes the desktop to completely lock up and requires a hard reset. Removing the workaround (switching back to "SNA") makes #349362 go away. Using Plasma 5.4.3 just released from Kubuntu Wily backports Here are some relevant intel logs from Xorg.0.log, hope it's of interest: $ grep intel /var/log/Xorg.0.log [ 21.930] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets: [ 21.930] (II) intel: Driver for Intel(R) HD Graphics: 2000-6000 [ 21.930] (II) intel: Driver for Intel(R) Iris(TM) Graphics: 5100, 6100 [ 21.930] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics: 5200, 6200, P6300 [ 21.930] (II) intel(0): Using Kernel Mode Setting driver: i915, version 1.6.0 20150522 [ 21.930] (II) intel(0): SNA compiled: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 (Robert Ancell <robert.ancell@canonical.com>) [ 21.930] (II) intel(0): SNA compiled for use with valgrind [ 21.931] (--) intel(0): Integrated Graphics Chipset: Intel(R) Iris(TM) Pro Graphics 5200 *** Bug 355366 has been marked as a duplicate of this bug. *** *** Bug 355375 has been marked as a duplicate of this bug. *** *** Bug 355789 has been marked as a duplicate of this bug. *** *** Bug 356078 has been marked as a duplicate of this bug. *** *** Bug 354604 has been marked as a duplicate of this bug. *** *** Bug 356378 has been marked as a duplicate of this bug. *** *** Bug 356707 has been marked as a duplicate of this bug. *** *** Bug 357178 has been marked as a duplicate of this bug. *** *** Bug 357730 has been marked as a duplicate of this bug. *** *** Bug 358318 has been marked as a duplicate of this bug. *** *** Bug 358349 has been marked as a duplicate of this bug. *** *** Bug 358809 has been marked as a duplicate of this bug. *** *** Bug 358788 has been marked as a duplicate of this bug. *** *** Bug 358676 has been marked as a duplicate of this bug. *** *** Bug 358969 has been marked as a duplicate of this bug. *** *** Bug 359432 has been marked as a duplicate of this bug. *** *** Bug 359398 has been marked as a duplicate of this bug. *** *** Bug 359395 has been marked as a duplicate of this bug. *** *** Bug 359582 has been marked as a duplicate of this bug. *** *** Bug 359635 has been marked as a duplicate of this bug. *** *** Bug 359696 has been marked as a duplicate of this bug. *** *** Bug 359885 has been marked as a duplicate of this bug. *** *** Bug 359953 has been marked as a duplicate of this bug. *** *** Bug 360222 has been marked as a duplicate of this bug. *** *** Bug 360814 has been marked as a duplicate of this bug. *** *** Bug 360721 has been marked as a duplicate of this bug. *** *** Bug 360726 has been marked as a duplicate of this bug. *** *** Bug 361152 has been marked as a duplicate of this bug. *** *** Bug 361143 has been marked as a duplicate of this bug. *** *** Bug 361205 has been marked as a duplicate of this bug. *** *** Bug 361421 has been marked as a duplicate of this bug. *** *** Bug 361507 has been marked as a duplicate of this bug. *** *** Bug 361647 has been marked as a duplicate of this bug. *** *** Bug 361745 has been marked as a duplicate of this bug. *** *** Bug 362769 has been marked as a duplicate of this bug. *** *** Bug 364904 has been marked as a duplicate of this bug. *** *** Bug 375619 has been marked as a duplicate of this bug. *** *** Bug 410964 has been marked as a duplicate of this bug. *** *** Bug 405628 has been marked as a duplicate of this bug. *** *** Bug 438523 has been marked as a duplicate of this bug. *** *** Bug 438875 has been marked as a duplicate of this bug. *** Wow. I hadn't seen an issue with so many duplicates yet. Could anything be done about it on the Plasma side? I'm not sure whether Bug 438875 really is a duplicate of this issue, since it affects only Wayland... *** Bug 440072 has been marked as a duplicate of this bug. *** *** Bug 443823 has been marked as a duplicate of this bug. *** *** Bug 447190 has been marked as a duplicate of this bug. *** |