https://bugs.kde.org/show_bug.cgi?id=368703
Boudewijn Rempt changed:
What|Removed |Added
Resolution|--- |FIXED
https://bugs.kde.org/show_bug.cgi?id=368703
--- Comment #15 from Patrice Kouame ---
understood.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=368703
--- Comment #14 from Boudewijn Rempt ---
On OSX, with git master, you must have Qt 5.7 patched with the patch in the
ext_qt folder.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=368703
--- Comment #13 from Patrice Kouame ---
Hey Nim -
Yes, I fully understand that and usually turn off openGL when playing around
with master. Setting back to 2.1 is just a quick workaround to look at other
things. Not meant as a
https://bugs.kde.org/show_bug.cgi?id=368703
--- Comment #12 from nimth...@gmail.com ---
Hi Pkouame,
The problem you face with that crash is that bleeding edge master now requires
a patched Qt5.7 until Qt adds my changes. Using an unpatched Qt5.7 breaks
everything because we ask for a 3.2 Core
https://bugs.kde.org/show_bug.cgi?id=368703
--- Comment #11 from Patrice Kouame ---
Created attachment 101203
--> https://bugs.kde.org/attachment.cgi?id=101203=edit
shader compiler errors
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=368703
--- Comment #10 from Patrice Kouame ---
NOTE: Whereas the crash is fixed. The shader loader is still not happy. Check
out my attached log.
Missing version strings in shaders this time around...
For me, running bleeding edge krita
https://bugs.kde.org/show_bug.cgi?id=368703
Patrice Kouame changed:
What|Removed |Added
CC||pkou...@mac.com
--- Comment
https://bugs.kde.org/show_bug.cgi?id=368703
--- Comment #8 from n7d...@gmail.com ---
terrific thanks
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=368703
--- Comment #7 from nimth...@gmail.com ---
Hi n7down, your problem should already be fixed in the latest master.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=368703
--- Comment #6 from n7d...@gmail.com ---
Sorry about the mistake, should I create another bug? Or will those changes be
submitted to this bug report?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=368703
--- Comment #5 from nimth...@gmail.com ---
I had to change 150 core to 130 for this Qt5.6 dilemma. I guess we need another
#ifdef to put in 150 core on OS X instead. Will fix that, different problem
than the bugreport though.
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=368703
Boudewijn Rempt changed:
What|Removed |Added
Ever confirmed|0 |1
https://bugs.kde.org/show_bug.cgi?id=368703
--- Comment #3 from n7d...@gmail.com ---
I am experience a similar (if not the same) issue with Krita 3.0.2 on OSX
10.11.6. Krita was working fine for a couple of hours then then it started to
give an throw an message which says: "Krita could not
https://bugs.kde.org/show_bug.cgi?id=368703
--- Comment #2 from n7d...@gmail.com ---
Created attachment 101133
--> https://bugs.kde.org/attachment.cgi?id=101133=edit
error message
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=368703
--- Comment #1 from n7d...@gmail.com ---
Created attachment 101130
--> https://bugs.kde.org/attachment.cgi?id=101130=edit
error-report
this is the error-report produced after krita crashes
--
You are receiving this mail because:
You are watching
https://bugs.kde.org/show_bug.cgi?id=368703
n7d...@gmail.com changed:
What|Removed |Added
CC||n7d...@gmail.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=368703
nimth...@gmail.com changed:
What|Removed |Added
Assignee|krita-bugs-n...@kde.org |b...@valdyas.org
--
You are receiving
18 matches
Mail list logo