From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 104806] plasmashell and other KDE binaries start to segfault after updating Mesa to 18.0.0 (radeon)
Date: Sat, 27 Jan 2018 08:39:29 +0000 [thread overview]
Message-ID: <bug-104806-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2016 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=104806
Bug ID: 104806
Summary: plasmashell and other KDE binaries start to segfault
after updating Mesa to 18.0.0 (radeon)
Product: Mesa
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
Assignee: dri-devel@lists.freedesktop.org
Reporter: ao@thurston.ru
QA Contact: dri-devel@lists.freedesktop.org
With Mesa 18.0.0 'plasmashell', 'ksplashqml' and 'kmail' binaries segfault
right after logging in into Plasma session, leaving coredumps behind.
If I downgrade Mesa package back to 17.3.3, everything works again.
I'm running Gentoo.
Video card:
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM]
Kernel driver: nouveau
X.Org driver: radeon
Something happens in r600_dri.so:
Core was generated by `/usr/bin/kmail -session
10dcd7cfcb000147846248200000156710141_1483955504_762746'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00007f37f999af50 in raise () from /lib64/libc.so.6
[Current thread is 1 (Thread 0x7f37fc86ea40 (LWP 892))]
(gdb) bt
#0 0x00007f37f999af50 in raise () from /lib64/libc.so.6
#1 0x00007f37fbb9f727 in KCrash::defaultCrashHandler(int) () from
/usr/lib64/libKF5Crash.so.5
#2 <signal handler called>
#3 0x00007f37f9a0d4f3 in ?? () from /lib64/libc.so.6
#4 0x00007f37bb154094 in ?? () from /usr/lib64/dri/r600_dri.so
#5 0x000055c4ec9e5de0 in ?? ()
#6 0x000055c4ec9d7fe0 in ?? ()
#7 0x000055c4ec9e5de0 in ?? ()
#8 0x00007f37bb254e2b in ?? () from /usr/lib64/dri/r600_dri.so
#9 0x0000000000000003 in ?? ()
#10 0x00007fff107efa90 in ?? ()
#11 0x0000000000000000 in ?? ()
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3417 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2018-01-27 8:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-27 8:39 bugzilla-daemon [this message]
2018-01-27 8:40 ` [Bug 104806] plasmashell and other KDE binaries start to segfault after updating Mesa to 18.0.0 (radeon) bugzilla-daemon
2018-01-27 11:35 ` bugzilla-daemon
2018-01-27 19:19 ` bugzilla-daemon
2018-01-28 7:53 ` bugzilla-daemon
2018-01-28 18:32 ` bugzilla-daemon
2018-01-28 18:34 ` bugzilla-daemon
2018-01-28 18:47 ` bugzilla-daemon
2018-01-28 18:49 ` bugzilla-daemon
2018-01-29 11:03 ` bugzilla-daemon
2018-01-29 23:30 ` bugzilla-daemon
2018-01-30 7:58 ` bugzilla-daemon
2018-01-30 8:00 ` bugzilla-daemon
2018-01-30 8:11 ` bugzilla-daemon
2018-01-30 8:43 ` bugzilla-daemon
2018-01-30 9:18 ` bugzilla-daemon
2018-01-30 9:22 ` bugzilla-daemon
2018-01-30 9:25 ` bugzilla-daemon
2018-01-30 19:13 ` bugzilla-daemon
2018-01-31 8:35 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-104806-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox