https://bugs.kde.org/show_bug.cgi?id=420032
Bug Janitor Service changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
https://bugs.kde.org/show_bug.cgi?id=420032
--- Comment #38 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=420032
vanyossi changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|REOPENED
https://bugs.kde.org/show_bug.cgi?id=420032
--- Comment #36 from Yu-Hsuan Lai ---
Created attachment 129593
--> https://bugs.kde.org/attachment.cgi?id=129593=edit
crash log from lldb
I got this crash while changing some shortcuts.
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=420032
--- Comment #35 from vanyossi ---
Hi, im sorry to hear its still present, but luckily we can work on finding the
cause and maybe a solution. Please attach the crash log when this happens, so i
cna start investigating (old logs won't not work as code
https://bugs.kde.org/show_bug.cgi?id=420032
Yu-Hsuan Lai changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|FIXED
https://bugs.kde.org/show_bug.cgi?id=420032
vanyossi changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://bugs.kde.org/show_bug.cgi?id=420032
--- Comment #32 from Yu-Hsuan Lai ---
I've been using 4.3.0-beta1 for a while (30+ hrs) and this hasn't happened.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=420032
--- Comment #31 from vanyossi ---
if $.3.0 deps were compiled from 4.3 branch the Qt used is:
Qt
Version (compiled): 5.12.7
Version (loaded): 5.12.7
You can check on Help -> Show system information for bug reports.
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=420032
--- Comment #30 from Yu-Hsuan Lai ---
This particular bug doesn't seem to happen with 4.3.0. It might just be a
placebo effect though. Does 4.3.0(2bae978) uses a different Qt version than
4.2.9?
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=420032
wolthera changed:
What|Removed |Added
Ever confirmed|0 |1
CC|
https://bugs.kde.org/show_bug.cgi?id=420032
--- Comment #29 from Yu-Hsuan Lai ---
(In reply to vanyossi from comment #28)
> Hi! going trouhgh the logs and the info provided I did not find anything
> conclusive, but I have some ideas. Another contributor helped set a better
> isolation
https://bugs.kde.org/show_bug.cgi?id=420032
vanyossi changed:
What|Removed |Added
Assignee|krita-bugs-n...@kde.org |ghe...@gmail.com
CC|
https://bugs.kde.org/show_bug.cgi?id=420032
--- Comment #27 from Boudewijn Rempt ---
Hm, it shouldn't matter... You can give it a try, but it's very puzzling. And
I've never seen crashes like this before, either. I'll ask Ivan to chime in.
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=420032
--- Comment #26 from Yu-Hsuan Lai ---
(In reply to Boudewijn Rempt from comment #25)
> Yes... It's pretty similar. Qt wants to put a dialog on screen, and then
> there's a crash deep in cocoa.
Oh wait, I have "Enable native file dialogs" enabled. Do
https://bugs.kde.org/show_bug.cgi?id=420032
--- Comment #25 from Boudewijn Rempt ---
Yes... It's pretty similar. Qt wants to put a dialog on screen, and then
there's a crash deep in cocoa.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=420032
--- Comment #24 from Yu-Hsuan Lai ---
Created attachment 127603
--> https://bugs.kde.org/attachment.cgi?id=127603=edit
system.log is the crash log shown by the OS.
Another similar crash. It happened when I pressed shift+Cmd+S to save a file
under
https://bugs.kde.org/show_bug.cgi?id=420032
--- Comment #23 from Boudewijn Rempt ---
Why are we packaging QtPrintSupport... Krita doesn't support printing. But it
is present, so that's not the problem.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=420032
--- Comment #22 from Yu-Hsuan Lai ---
(In reply to Boudewijn Rempt from comment #21)
> It might be worth it to investiage libqcocoa, since that's where the crash
> happens. https://forum.qt.io/topic/34280/solved-qt5-and-mac-libqcocoa/3
> suggests
https://bugs.kde.org/show_bug.cgi?id=420032
--- Comment #21 from Boudewijn Rempt ---
It might be worth it to investiage libqcocoa, since that's where the crash
happens. https://forum.qt.io/topic/34280/solved-qt5-and-mac-libqcocoa/3
suggests running otool -L on libqcocoa.dylib . Maybe that has
https://bugs.kde.org/show_bug.cgi?id=420032
--- Comment #20 from Yu-Hsuan Lai ---
Created attachment 127561
--> https://bugs.kde.org/attachment.cgi?id=127561=edit
Krita Usage Log 2
Krita usage log. There isn't much to see tho, except this time it correctly
reports Krita version of 4.2.9
--
https://bugs.kde.org/show_bug.cgi?id=420032
--- Comment #19 from Yu-Hsuan Lai ---
Well... the same kind of crash (same stack dump in system log) still happens
even without home-built Krita.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=420032
--- Comment #18 from Yu-Hsuan Lai ---
(In reply to Boudewijn Rempt from comment #17)
> And is it more stable?
No crash yet, but it's hard to tell for now because it only crashed one or two
times a day before.
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=420032
--- Comment #16 from Yu-Hsuan Lai ---
After removing the half-ass-home-built Krita, now both the "About Krita" and
"Show system information" windows report Krita version 4.2.9.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=420032
--- Comment #17 from Boudewijn Rempt ---
And is it more stable?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=420032
--- Comment #15 from Boudewijn Rempt ---
It would if cmake finds that version of Qt first and tries to build against it.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=420032
--- Comment #14 from Yu-Hsuan Lai ---
(In reply to Boudewijn Rempt from comment #13)
> Yes, it should correctly build all dependencies in the framework. I haven't
> managed to talk to Ivan for some days (he's in mexico, and his internet
> connection
https://bugs.kde.org/show_bug.cgi?id=420032
--- Comment #13 from Boudewijn Rempt ---
Yes, it should correctly build all dependencies in the framework. I haven't
managed to talk to Ivan for some days (he's in mexico, and his internet
connection was flaky) and I'm in the Netherlands and was
https://bugs.kde.org/show_bug.cgi?id=420032
--- Comment #12 from Yu-Hsuan Lai ---
(In reply to Boudewijn Rempt from comment #11)
> Yes, something is definitely too weird for words there. I'd make the
> home-built Krita inaccessible to start with, and maybe test with a clean
> test user.
The
https://bugs.kde.org/show_bug.cgi?id=420032
--- Comment #11 from Boudewijn Rempt ---
Yes, something is definitely too weird for words there. I'd make the home-built
Krita inaccessible to start with, and maybe test with a clean test user.
--
You are receiving this mail because:
You are watching
https://bugs.kde.org/show_bug.cgi?id=420032
--- Comment #9 from Yu-Hsuan Lai ---
Created attachment 127540
--> https://bugs.kde.org/attachment.cgi?id=127540=edit
same krita instance, contradict info
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=420032
--- Comment #10 from Yu-Hsuan Lai ---
Created attachment 127541
--> https://bugs.kde.org/attachment.cgi?id=127541=edit
same krita instance, contradict info
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=420032
--- Comment #8 from Yu-Hsuan Lai ---
(In reply to Boudewijn Rempt from comment #7)
> Hm, could it be that there are bits and pieces of your self-compiled Krita
> in
> /Users/raincole/github/krita_buildroot/i/bin/krita.app/Contents/MacOS/krita
> in the
https://bugs.kde.org/show_bug.cgi?id=420032
--- Comment #7 from Boudewijn Rempt ---
Hm, could it be that there are bits and pieces of your self-compiled Krita in
/Users/raincole/github/krita_buildroot/i/bin/krita.app/Contents/MacOS/krita in
the path? What we're seeing are crashes deep in Qt
https://bugs.kde.org/show_bug.cgi?id=420032
--- Comment #6 from Yu-Hsuan Lai ---
Attached. I'm not sure if this usage log covers the random crash shown in
system.log tho. It might be two different crashes.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=420032
--- Comment #5 from Yu-Hsuan Lai ---
Created attachment 127537
--> https://bugs.kde.org/attachment.cgi?id=127537=edit
System information
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=420032
--- Comment #4 from Yu-Hsuan Lai ---
Created attachment 127536
--> https://bugs.kde.org/attachment.cgi?id=127536=edit
Krita Usage Log
This is my Krita Usage Log, but I'm not sure where the useful information is.
It crashed once at:
KRITA DID NOT
https://bugs.kde.org/show_bug.cgi?id=420032
Boudewijn Rempt changed:
What|Removed |Added
CC||b...@valdyas.org
--- Comment #3 from
https://bugs.kde.org/show_bug.cgi?id=420032
--- Comment #2 from Yu-Hsuan Lai ---
Created attachment 127507
--> https://bugs.kde.org/attachment.cgi?id=127507=edit
terminal.log is the log shown in terminal where the Krita was launched
--
You are receiving this mail because:
You are watching
https://bugs.kde.org/show_bug.cgi?id=420032
--- Comment #1 from Yu-Hsuan Lai ---
Created attachment 127506
--> https://bugs.kde.org/attachment.cgi?id=127506=edit
system.log is the crash log shown by the OS.
--
You are receiving this mail because:
You are watching all bug changes.
40 matches
Mail list logo
