https://bugs.kde.org/show_bug.cgi?id=458935
vanyossi changed:
What|Removed |Added
CC||gabrielle.l...@gmail.com
--- Comment #21 from vanyos
https://bugs.kde.org/show_bug.cgi?id=458935
col...@outlook.com changed:
What|Removed |Added
CC||col...@outlook.com
--
You are receiving th
https://bugs.kde.org/show_bug.cgi?id=458935
amyspark changed:
What|Removed |Added
URL||https://github.com/amyspark
|
https://bugs.kde.org/show_bug.cgi?id=458935
--- Comment #19 from David Tschumperlé ---
FYI, nest g'mic version 3.2.5 will be released tomorrow :)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=458935
Halla Rempt changed:
What|Removed |Added
CC||ha...@valdyas.org
--- Comment #18 from Halla Remp
https://bugs.kde.org/show_bug.cgi?id=458935
amyspark changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://bugs.kde.org/show_bug.cgi?id=458935
--- Comment #16 from vanyossi ---
(In reply to amyspark from comment #15)
> Iván, can you check with the amyspark/v3.2.4 branch of
> https://github.com/amyspark/gmic ?
I can happily report that using gmic amyspark/v3.2.4 branch is no longer
crashing
-
https://bugs.kde.org/show_bug.cgi?id=458935
amyspark changed:
What|Removed |Added
Status|REPORTED|ASSIGNED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=458935
Bug Janitor Service changed:
What|Removed |Added
Resolution|BACKTRACE |---
Ever confirmed|1
https://bugs.kde.org/show_bug.cgi?id=458935
--- Comment #13 from vanyossi ---
(In reply to David Tschumperlé from comment #12)
> A note about this : we have recently fixed a bug that could be related from
> G'MIC 2.3.2 to 2.3.3 (current is 2.3.4).
> This was a multi-threading issue (G'MIC was try
https://bugs.kde.org/show_bug.cgi?id=458935
--- Comment #12 from David Tschumperlé ---
A note about this : we have recently fixed a bug that could be related from
G'MIC 2.3.2 to 2.3.3 (current is 2.3.4).
This was a multi-threading issue (G'MIC was trying to decompress its standard
library in mult
https://bugs.kde.org/show_bug.cgi?id=458935
vanyossi changed:
What|Removed |Added
Attachment #158611|0 |1
is obsolete||
https://bugs.kde.org/show_bug.cgi?id=458935
amyspark changed:
What|Removed |Added
Resolution|--- |BACKTRACE
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=458935
vanyossi changed:
What|Removed |Added
CC||irene.roys...@gmail.com
--- Comment #9 from vanyossi
https://bugs.kde.org/show_bug.cgi?id=458935
--- Comment #8 from vanyossi ---
Created attachment 158611
--> https://bugs.kde.org/attachment.cgi?id=158611&action=edit
crash with debug info
Maybe this updated crash log could help find the culprit
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=458935
vanyossi changed:
What|Removed |Added
Ever confirmed|0 |1
Resolution|WAITINGFORINFO |--
https://bugs.kde.org/show_bug.cgi?id=458935
amyspark changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
CC|
https://bugs.kde.org/show_bug.cgi?id=458935
Bug Janitor Service changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Ever confirmed|1
https://bugs.kde.org/show_bug.cgi?id=458935
--- Comment #4 from vanyossi ---
previous ones was using lldb, I wasn't sure why I was not getting the symbols
attached. I "force" patched our version of gmic and got this from
Artistic -> Chalk it up [Fr]
* thread #27, stop reason = EXC_BAD_ACCESS (co
https://bugs.kde.org/show_bug.cgi?id=458935
--- Comment #3 from vanyossi ---
*** Bug 458310 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=458935
amyspark changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=458935
vanyossi changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED|CO
22 matches
Mail list logo