https://bugs.kde.org/show_bug.cgi?id=361374
Paul Konecny changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
https://bugs.kde.org/show_bug.cgi?id=361374
--- Comment #13 from farid ---
I just tested again and this is an NVIDIA issue so it would be OK to close it i
guess.
I have reported it in phabricator in a thread about NVIDIA related issues:
https://phabricator.kde.org/T2908
https://bugs.kde.org/show_bug.cgi?id=361374
Paul Konecny changed:
What|Removed |Added
Flags||MOVIT+
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=361374
--- Comment #12 from Paul Konecny ---
Update:
Radeonsi, R600g and Intel are still unaffected by this bug.
Should we change it to Resolved / Upstream?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=361374
farid changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=361374
--- Comment #10 from Paul Konecny ---
Created attachment 101451
--> https://bugs.kde.org/attachment.cgi?id=101451=edit
Backtrace master branch 5b7908a
I just tried 5b7908a from master and still get the crash. Backtrace attached.
https://bugs.kde.org/show_bug.cgi?id=361374
--- Comment #9 from Paul Konecny ---
Farid can you confirm this only happens on nvidia with the proprietary driver?
I tested this on radeonsi, Intel and r600g and didn't get this SIGABRT.
My guess it is a driver bug with nvidia's non
https://bugs.kde.org/show_bug.cgi?id=361374
--- Comment #8 from farid ---
I confirm:
(gdb) thread apply all bt
Thread 23 (Thread 0x7fff76ffc700 (LWP 8192)):
#0 0x7fffefdbe04f in raise () from /usr/lib/libc.so.6
#1 0x7fffefdbf47a in abort () from
https://bugs.kde.org/show_bug.cgi?id=361374
--- Comment #7 from Paul Konecny ---
Created attachment 99478
--> https://bugs.kde.org/attachment.cgi?id=99478=edit
NVIDIA log after master-bbe25c0
Hi J-B I tried these fixes
https://bugs.kde.org/show_bug.cgi?id=361374
--- Comment #6 from Paul Konecny ---
Just messed around on r600g hardware for 15 minutes and could not reproduce
this issue.
I'll try radeonsi and Intel and report back in a few days.
Maybe the remaining crash is due to a driver bug
https://bugs.kde.org/show_bug.cgi?id=361374
--- Comment #5 from Paul Konecny ---
Created attachment 98259
--> https://bugs.kde.org/attachment.cgi?id=98259=edit
Backtrace #2 16.04-3936976
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=361374
--- Comment #4 from Paul Konecny ---
Created attachment 98258
--> https://bugs.kde.org/attachment.cgi?id=98258=edit
Screencast of the issue #2
Unfortunately I still get the issue with 16.04-3936976
This is without any project
https://bugs.kde.org/show_bug.cgi?id=361374
--- Comment #3 from Jean-Baptiste Mardelle ---
Git commit fc6ba6fc2505a360c67ef7ccd7e75446102f3154 by Jean-Baptiste Mardelle.
Committed on 05/04/2016 at 18:08.
Pushed by mardelle into branch 'Applications/16.04'.
Fix Movit crashes,
https://bugs.kde.org/show_bug.cgi?id=361374
farid changed:
What|Removed |Added
CC||snd.no...@gmail.com
--- Comment
https://bugs.kde.org/show_bug.cgi?id=361374
--- Comment #1 from Paul Konecny ---
Created attachment 98240
--> https://bugs.kde.org/attachment.cgi?id=98240=edit
SIGABRT on monitor detach
--
You are receiving this mail because:
You are watching all bug changes.
15 matches
Mail list logo