| Summary: | Crash in st_clear | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | colin <bugs.kde.org> |
| Component: | general | Assignee: | David Edmundson <kde> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | CC: | aspotashev, bhush94, bugs.kde.org, jburgess777, kamilmroz12, marius_mps, miroslav, notmart, plasma-bugs, thekla.damaschke, yosieabdi |
| Priority: | NOR | Keywords: | drkonqi |
| Version: | 5.4.1 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi New crash information added by DrKonqi |
||
|
Description
colin
2015-10-20 20:33:51 UTC
*** Bug 354580 has been marked as a duplicate of this bug. *** *** Bug 353763 has been marked as a duplicate of this bug. *** Created attachment 95218 [details]
New crash information added by DrKonqi
plasmashell (5.4.2) using Qt 5.5.0
- What I was doing when the application crashed:
logged in after cold boot up
- Custom settings of the application:
dual screen, displays rotated 90°
-- Backtrace (Reduced):
#5 0x00007f333a6df279 in update_framebuffer_state () from /usr/lib64/dri/r600_dri.so
#6 0x00007f333a6de1c5 in st_validate_state () from /usr/lib64/dri/r600_dri.so
#7 0x00007f333a6e52a1 in st_Clear () from /usr/lib64/dri/r600_dri.so
#8 0x00007f33612c03fa in QSGBatchRenderer::Renderer::renderBatches() () from /lib64/libQt5Quick.so.5
#9 0x00007f33612c5de2 in QSGBatchRenderer::Renderer::render() () from /lib64/libQt5Quick.so.5
So this crash happens multiple times. This time crash reporter would not let me select my own bug report and proceed with it. A further warning dialog later appeared eventually warning that some process ( maybe k5-init-something) had died. I tried to copy-n-paste from there, but here is what was left in Clipboard. /var/spool/abrt/ccpp-2015-11-02-11:03:52-2558 plasma is still unstable and nearly unuseable on Fedora22 each login: Sometimes a blank desktop (i.e. black - no desktop wallpaper) task bar location not preserved - it randomnly appears on left or right screen window locations are lost. open windows not restored. rendering problems - flashing, blank areas , rectangles not updated unwanted greying out, flickering etc. etc. etc. :-( Created attachment 95307 [details]
New crash information added by DrKonqi
plasmashell (5.4.2) using Qt 5.5.0
- What I was doing when the application crashed:
Colid boot. Logged in.
- Unusual behavior I noticed:
Dual screen setup-
very long pause whilst desktop wallpaper loading, black areas of non- rendered screen area.
very long delay to taskbar appearing- on the wrong screen.
-- Backtrace (Reduced):
#5 0x00007fbabc93db49 in update_framebuffer_state () at /usr/lib64/dri/r600_dri.so
#6 0x00007fbabc93cc65 in st_validate_state () at /usr/lib64/dri/r600_dri.so
#7 0x00007fbabc9439d1 in st_Clear () at /usr/lib64/dri/r600_dri.so
#8 0x00007fbae31253fa in QSGBatchRenderer::Renderer::renderBatches() () at /lib64/libQt5Quick.so.5
#9 0x00007fbae312ade2 in QSGBatchRenderer::Renderer::render() () at /lib64/libQt5Quick.so.5
Can someone with apitrace run: apitrace trace plasmashell and reproduce the crash, so we have something to send upstream to Mesa? As a last resort, running with: QT_XCB_FORCE_SOFTWARE_OPENGL=1 will almost certainly not crash, but will give worse performance We've got a few bugs here now, but on different drivers. Created attachment 95571 [details]
New crash information added by DrKonqi
plasmashell (5.4.3) using Qt 5.5.0
kdeshell 5.4.3-1FC23 Qt 4.8.7-3fc23
- What I was doing when the application crashed:
login after cold boot
- Unusual behavior I noticed:
long boot time, black screen pauses. The login window spans 1.5 screens (using the bigger resolution but starting on the smaller screen)
After login and initial KDE screeen long black screen then swaps between displays and flickering.
After the crash the screens are initailized but with wrong primary and all panels are on the primary overlapping each other.
On earlier reboots sometimes the secondary has no wallpaper and doesnt react on mouseclicks.
Application windows can be dragged there though.
Often the panels end all up on primary.
Once I didnt get any panels or desktop content on any screen but context menu worked on primary.
Logging out and in again without reboot only gives a garbled desktop.
- Custom settings of the application:
dual screen with different resolution, selected screen on dvi2 as primary.
-- Backtrace (Reduced):
#5 0x00007f5deeb1c5e9 in update_framebuffer_state () from /usr/lib64/dri/nouveau_dri.so
#6 0x00007f5deeb1b535 in st_validate_state () from /usr/lib64/dri/nouveau_dri.so
#7 0x00007f5deeb22611 in st_Clear () from /usr/lib64/dri/nouveau_dri.so
#8 0x00007f5e156f03fa in QSGBatchRenderer::Renderer::renderBatches() () from /lib64/libQt5Quick.so.5
#9 0x00007f5e156f5de2 in QSGBatchRenderer::Renderer::render() () from /lib64/libQt5Quick.so.5
I noticed this Mesa bug which has a similar back trace: https://bugs.freedesktop.org/show_bug.cgi?id=91687 I haven't seen plasma crash since I disabled compositing so this could implicate indirect rendering. I just came across this one too but I'm not really sure how to reproduce it. Seems more or less random but this happened after an update. *** Bug 377984 has been marked as a duplicate of this bug. *** *** This bug has been marked as a duplicate of bug 371275 *** |