Bug 420427 - Crash in radeonsi_dri.so when opening Team Viewer, copying a flameshot image to clipboard, and when receiving notifications on whatsapp (version with electron)
Summary: Crash in radeonsi_dri.so when opening Team Viewer, copying a flameshot image ...
Status: RESOLVED DOWNSTREAM
Alias: None
Product: plasmashell
Classification: Plasma
Component: generic-crash (show other bugs)
Version: 5.18.4
Platform: unspecified Linux
: NOR crash
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2020-04-22 15:57 UTC by phrazão
Modified: 2020-05-14 15:50 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description phrazão 2020-04-22 15:57:28 UTC
Application: plasmashell (5.18.4)

Qt Version: 5.14.1
Frameworks Version: 5.68.0
Operating System: Linux 5.3.0-46-generic x86_64
Windowing system: X11
Distribution: Feren OS

-- Information about the crash:
- What I was doing when the application crashed:
this time was when openning Team Viewer, but it also crashes using flameshot or wathsapp.
Since this upgrade from FerenOS, i lost completely the stability of the system, essencialy in the KDE...

-- Backtrace (Reduced):
#6  0x00007ff07aeca2c5 in  () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#7  0x00007ff0a4f6a3ad in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#8  0x00007ff0a4f6a56b in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#9  0x00007ff0a4f21060 in QSGBatchRenderer::Renderer::renderMergedBatch(QSGBatchRenderer::Batch const*) () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#10 0x00007ff0a4f25785 in QSGBatchRenderer::Renderer::renderBatches() () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5


Possible duplicates by query: bug 418888, bug 418316, bug 418084, bug 416926, bug 416905.

Reported using DrKonqi
Comment 1 Nate Graham 2020-04-22 17:06:35 UTC
Hmm, crashing in the graphics drivers.
Comment 2 Christoph Feck 2020-05-14 15:50:25 UTC
Indeed. If this is reproducible, please report this issue directly to Mesa developers via https://www.mesa3d.org/bugs.html