https://bugs.kde.org/show_bug.cgi?id=383681
Bug Janitor Service changed:
What|Removed |Added
Resolution|WAITINGFORINFO |WORKSFORME
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=383681
--- Comment #22 from Bug Janitor Service ---
Dear Bug Submitter,
This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular
https://bugs.kde.org/show_bug.cgi?id=383681
Justin Zobel changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=383681
Michael Palimaka changed:
What|Removed |Added
CC||kensing...@gentoo.org
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=383681
--- Comment #20 from Martin Flöser ---
(In reply to Markus Heß from comment #19)
> Ok, I only noticed crashes of kscreenlocker. Everything else is working fine
> so far, so I assumed that this is related to this bug. Do you know if there
> is already an
https://bugs.kde.org/show_bug.cgi?id=383681
--- Comment #19 from Markus Heß ---
Ok, I only noticed crashes of kscreenlocker. Everything else is working fine so
far, so I assumed that this is related to this bug. Do you know if there is
already an open issue or should I create a new one? Is this a
https://bugs.kde.org/show_bug.cgi?id=383681
--- Comment #18 from Martin Flöser ---
@Markus: your issue is different. Many applications started to crash with that
driver update with similar backtrace as yours. But it's clearly a different
issue! We can see this that your system crashed in Thread 5
https://bugs.kde.org/show_bug.cgi?id=383681
Markus Heß changed:
What|Removed |Added
CC||hess...@googlemail.com
--- Comment #17 from Markus
https://bugs.kde.org/show_bug.cgi?id=383681
--- Comment #16 from Jerrod Frost ---
I'm not the one with the intel card, thats another member. I only have AMD
cards and one old nvidia (nouveau) card.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=383681
Arthur Țițeică changed:
What|Removed |Added
CC||arthur+...@cloud.titeica.ro
--
You are receiv
https://bugs.kde.org/show_bug.cgi?id=383681
Fabian Vogt changed:
What|Removed |Added
CC||fab...@ritter-vogt.de
--- Comment #15 from Fabian
https://bugs.kde.org/show_bug.cgi?id=383681
--- Comment #14 from Martin Flöser ---
(In reply to Jerrod Frost from comment #12)
> appears related to this?
>
> https://lists.fedoraproject.org/archives/list/k...@lists.fedoraproject.org/
> thread/P3GKSSLCV2YZT4UTFDHCP6S4CQ453J35/
No, that's about t
https://bugs.kde.org/show_bug.cgi?id=383681
--- Comment #13 from Jerrod Frost ---
I can't seem to find a way to see what flags were used to compile Suse
Tumbleweed's packages..
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=383681
--- Comment #12 from Jerrod Frost ---
appears related to this?
https://lists.fedoraproject.org/archives/list/k...@lists.fedoraproject.org/thread/P3GKSSLCV2YZT4UTFDHCP6S4CQ453J35/
--
You are receiving this mail because:
You are watching all bug change
https://bugs.kde.org/show_bug.cgi?id=383681
--- Comment #11 from Martin Flöser ---
This seems to work on openSUSE Tumbleweed - we did not get any complaints so
far. Could you please compare whether there are differences in how packages
like e.g. Mesa are compiled?
There must be an important diff
https://bugs.kde.org/show_bug.cgi?id=383681
--- Comment #10 from Jerrod Frost ---
Yes, both default and custom have the issue. I've even wiped out all KDE
settings and started over only to see the same issue.
On Sun, Aug 20, 2017, 12:07 PM Martin Flöser
wrote:
> https://bugs.kde.org/show_bug.c
https://bugs.kde.org/show_bug.cgi?id=383681
--- Comment #9 from Martin Flöser ---
Better disable seccomp than dri3.
Nevertheless I would like to figure out what is different in the case of
Sabayon. We shipped 5.10 in June and this is the first report of it not
working. Other distributions also u
https://bugs.kde.org/show_bug.cgi?id=383681
--- Comment #8 from Jerrod Frost ---
There are 2 ways to work around this problem:
1. use -seccomp USE flag at compile time
2. disable DRI3
1. removes seccomp flag, but keeps DRI3 and Vulkan and fixes both Intel and AMD
2. removes vulkan and DRI3 but
https://bugs.kde.org/show_bug.cgi?id=383681
--- Comment #7 from Jerrod Frost ---
Created attachment 107407
--> https://bugs.kde.org/attachment.cgi?id=107407&action=edit
machine overview
View of GCC, mesa, kernel, kscreenlocker USE flags and compile output.
--
You are receiving this mail bec
https://bugs.kde.org/show_bug.cgi?id=383681
--- Comment #6 from Martin Flöser ---
OK, so we need to figure out what is different in your distribution to all
other distributions. Obvious things first: this works on other distributions.
KScreenlocker saw some changes in Plasma 5.10, but no other d
https://bugs.kde.org/show_bug.cgi?id=383681
--- Comment #5 from Jerrod Frost ---
All we did is upgraded plasma 5.9.5 to 5.10.4
Intel is also affected. I'm part of the Sabayon Linux software testing team.
We've located the issue. It's 100% with DRI3. Once we downgrade to DRI2.
Everything works i
https://bugs.kde.org/show_bug.cgi?id=383681
--- Comment #4 from Martin Flöser ---
>From the backtrace it looks like a crash in radeon driver called from Qt. Could
it be that you also updated either Qt or driver or kernel?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=383681
--- Comment #3 from Jerrod Frost ---
jcfrosty@CtrlZ ~ $ sudo coredumpctl gdb /usr/lib64/libexec/kscreenlocker_greet
PID: 4124 (kscreenlocker_g)
UID: 1002 (jcfrosty)
GID: 1003 (jcfrosty)
Signal: 11 (SEGV)
Ti
https://bugs.kde.org/show_bug.cgi?id=383681
--- Comment #2 from Jerrod Frost ---
Yeah, I'm fighting to use gdb right now. Wish I understood what I was doing
more... I'll get it to you as soon as I can. I can definitely say this issue
didn't exist in plasma 5.9.5 .
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=383681
--- Comment #1 from Martin Flöser ---
Could you please run kscreenlocker_greet through Feb and attach the backtrace?
--
You are receiving this mail because:
You are watching all bug changes.
25 matches
Mail list logo
