| Summary: | Segfault in Start Menu | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | Josh <joshmassey25> |
| Component: | general | Assignee: | David Edmundson <kde> |
| Status: | CLOSED DUPLICATE | ||
| Severity: | crash | CC: | bhush94, emrecio, m.k.lamb1003, plasma-bugs, vikigoyal |
| Priority: | NOR | Keywords: | drkonqi |
| Version: | 5.3.2 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
New crash information added by DrKonqi
Another crash. Opened firefox and clicked network status icon to check network connection and it crashed. New crash information added by DrKonqi |
||
|
Description
Josh
2015-09-03 23:53:46 UTC
Created attachment 94393 [details]
New crash information added by DrKonqi
plasmashell (5.3.2) using Qt 5.5.0
- What I was doing when the application crashed:
The systemc is up since a day & was under stress due to backups being taken overnight. I logged in & checked screens, after which I started firefox which crashed it.
Top at time of reporting.
top - 10:20:18 up 21:03, 11 users, load average: 0.09, 0.62, 0.42
Tasks: 315 total, 1 running, 312 sleeping, 1 stopped, 1 zombie
%Cpu(s): 13.8 us, 5.8 sy, 0.1 ni, 61.4 id, 17.8 wa, 0.0 hi, 1.0 si, 0.0 st
KiB Mem : 7611624 total, 129080 free, 1043792 used, 6438752 buff/cache
KiB Swap: 10485756 total, 9841624 free, 644132 used. 6310928 avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
4926 vikram 20 0 3166104 38548 27368 S 12.5 0.5 5:57.31 kwin_x11
5259 vikram 20 0 770456 31652 27808 S 12.5 0.4 3:56.72 kget
1 root 20 0 46732 4588 3460 S 0.0 0.1 0:06.24 systemd
2 root 20 0 0 0 0 S 0.0 0.0 0:00.07 kthreadd
3 root 20 0 0 0 0 S 0.0 0.0 0:05.35 ksoftirqd/0
5 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kworker/0:0H
7 root 20 0 0 0 0 S 0.0 0.0 0:54.98 rcu_sched
8 root 20 0 0 0 0 S 0.0 0.0 0:00.00 rcu_bh
9 root 20 0 0 0 0 S 0.0 0.0 0:49.94 rcuos/0
10 root 20 0 0 0 0 S 0.0 0.0 0:00.00 rcuob/0
11 root rt 0 0 0 0 S 0.0 0.0 0:00.12 migration/0
12 root rt 0 0 0 0 S 0.0 0.0 0:00.21 watchdog/0
13 root rt 0 0 0 0 S 0.0 0.0 0:00.21 watchdog/1
14 root rt 0 0 0 0 S 0.0 0.0 0:00.11 migration/1
15 root 20 0 0 0 0 S 0.0 0.0 0:01.14 ksoftirqd/1
17 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kworker/1:0H
18 root 20 0 0 0 0 S 0.0 0.0 0:22.05 rcuos/1
19 root 20 0 0 0 0 S 0.0 0.0 0:00.00 rcuob/1
20 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 khelper
21 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kdevtmpfs
22 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 netns
23 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 perf
24 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 writeback
25 root 25 5 0 0 0 S 0.0 0.0 0:00.00 ksmd
26 root 39 19 0 0 0 S 0.0 0.0 0:00.00 khugepaged
27 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 crypto
28 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kintegrityd
29 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 bioset
30 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kblockd
top.out
-- Backtrace (Reduced):
#5 0x00007f434b8f84ac in brw_meta_fast_clear () at /usr/lib64/dri/i965_dri.so
#6 0x00007f434b8838dc in brw_clear () at /usr/lib64/dri/i965_dri.so
#7 0x0000003db11263fa in QSGBatchRenderer::Renderer::renderBatches() () at /lib64/libQt5Quick.so.5
#8 0x0000003db112bde2 in QSGBatchRenderer::Renderer::render() () at /lib64/libQt5Quick.so.5
#9 0x0000003db1137adf in QSGRenderer::renderScene(QSGBindable const&) () at /lib64/libQt5Quick.so.5
#6 0x00007f04cf0008dc in brw_clear () from /usr/lib64/dri/i965_dri.so This is crashing in your graphic driver which we can't do much about. Please upgrade/downgrade your version of mesa. See information (including a workaround) in the linked report *** This bug has been marked as a duplicate of bug 349519 *** I am fully updated and still get this error. I do not believe this has been fixed as is noted on the duplicate bug. (In reply to Josh from comment #3) > I am fully updated and still get this error. I do not believe this has been > fixed as is noted on the duplicate bug. *Also, I am not using Mesa, I am using Nouveau. >*Also, I am not using Mesa, I am using Nouveau.
You're clearly not
#6 0x00007f04cf0008dc in brw_clear () from /usr/lib64/dri/i965_dri.so
i965 is an intel driver
Then I am confused. Why did you tell me to upgrade my version of Mesa? I'm not exactly sure what to do or if this is a KDE problem or a driver problem. well I'm confused too. You claim you're using Nouveau The trace you included shows that you are not. Either you're wrong about what driver you're using, or that trace isn't right. When my system boots, right before the login screen comes up, I get a few messages from nouveau about not being able to create something, but they go away so quick that I can't read them. I never installed anything other than some dev tools and web browsers after installing my system and I haven't changed anything else outside of removing kwallet and gnomekeyring. Just tell me which logs to post and I'll post them up. On a side note, this crash has happened a couple of other times as well, but I did not want to post more bug reports. When I tried to select this bug report and just add another trace to it, the bug reporter just wanted to continue along posting the new bug report instead of tacking it onto this one, so I exited from it. Created attachment 94399 [details]
Another crash. Opened firefox and clicked network status icon to check network connection and it crashed.
Created attachment 94402 [details]
New crash information added by DrKonqi
plasmashell (5.3.2) using Qt 5.5.0
- What I was doing when the application crashed: nothing. Plasma is crashing every few seconds
-- Backtrace (Reduced):
#5 0x00007f9aed02c4ac in brw_meta_fast_clear () at /usr/lib64/dri/i965_dri.so
#6 0x00007f9aecfb78dc in brw_clear () at /usr/lib64/dri/i965_dri.so
#7 0x000000346b7263fa in QSGBatchRenderer::Renderer::renderBatches() () at /lib64/libQt5Quick.so.5
#8 0x000000346b72bde2 in QSGBatchRenderer::Renderer::render() () at /lib64/libQt5Quick.so.5
#9 0x000000346b737adf in QSGRenderer::renderScene(QSGBindable const&) () at /lib64/libQt5Quick.so.5
It seems to happen when I click on a new window, or when I click on the K-Menu button. Could it be compiz (?) or special effects that are enabled as the windows are transitioning? I never happens when I am working within an application, it's usually when something on the screen changes, or I change it by clicking on something. it happens quite often. often, no interaction is required for the segfault to occur If you're getting the same crash as comment #1, this is the bug I am marking this a duplicate of. That contains 3 different workarounds. *** This bug has been marked as a duplicate of bug 349519 *** Each of those workarounds turns my desktop effects off or forces software rendering. I don't want either of those. All I want is for my desktop effects to work, full hardware acceleration to work, and for there to be no crashing. When will this be fixed so that this is the case, and what can I do in the mean time to mitigate the problem? It's a bug in Mesa, it will be fixed when mesa is fixed in your distribution. I've added another workaround as one of the main comments to the other bug report which shouldn't have ill effects. |