https://bugs.kde.org/show_bug.cgi?id=444280
--- Comment #43 from caulier.gil...@gmail.com ---
As Maik said in comment #16, it crash in Libraw function
LibRaw::convert_to_rgb(). The function is here in digiKam core:
https://bugs.kde.org/show_bug.cgi?id=444280
--- Comment #42 from caulier.gil...@gmail.com ---
Under MacOS, i do not crash too:
https://i.imgur.com/PQupipP.png
Gilles
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=444280
--- Comment #41 from caulier.gil...@gmail.com ---
Note this crash in libraw with Raw profile output is specific to Microsoft. I
cannot reproduce the crash under Linux:
https://i.imgur.com/DYpjDZo.png
Gilles
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=444280
--- Comment #40 from caulier.gil...@gmail.com ---
Maik,
Can you reproduce the crash too by tuning this setting on your computer ?
Gilles
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=444280
--- Comment #39 from caulier.gil...@gmail.com ---
Ok, i found the problem.
In your debug view trace we have :
-- RAW DECODING SETTINGS
058838.80609131 [19228] -- autoBrightness: true
https://bugs.kde.org/show_bug.cgi?id=444280
--- Comment #38 from caulier.gil...@gmail.com ---
Can you take a screenshot of the Setup/Editor/Raw Behavior/Default Settings
view, with all settings visible ? I want to know if something special is
configured here.
Gilles
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=444280
--- Comment #37 from fri...@bluemail.ch ---
(In reply to caulier.gilles from comment #36)
> Yes, you right, there is no 8/16 bits choice in default settings.
>
> And yes, in the default settings view, change one parameter, as for ex the
> Quality which
https://bugs.kde.org/show_bug.cgi?id=444280
--- Comment #36 from caulier.gil...@gmail.com ---
Yes, you right, there is no 8/16 bits choice in default settings.
And yes, in the default settings view, change one parameter, as for ex the
Quality which must be bilinear. Use AAHD instead for ex.
https://bugs.kde.org/show_bug.cgi?id=444280
--- Comment #35 from fri...@bluemail.ch ---
(In reply to caulier.gilles from comment #34)
> Ok fine, at least it homogeneous.
>
> Now go back to Setup/Editor/Raw Behavior/Default Settings, change 8 bits to
> 16 bits demosaicing. Re-open Raw Import tool
https://bugs.kde.org/show_bug.cgi?id=444280
--- Comment #34 from caulier.gil...@gmail.com ---
Ok fine, at least it homogeneous.
Now go back to Setup/Editor/Raw Behavior/Default Settings, change 8 bits to 16
bits demosaicing. Re-open Raw Import tool with ARW file and press Use Default.
It crash
https://bugs.kde.org/show_bug.cgi?id=444280
--- Comment #33 from fri...@bluemail.ch ---
(In reply to caulier.gilles from comment #32)
> Ok, now turn on again the Setup/Editor/Raw Behavior/Use RawImport tool.
>
> Load the ARW image in editor. Import Tool appear. On the bottom of the right
>
https://bugs.kde.org/show_bug.cgi?id=444280
--- Comment #32 from caulier.gil...@gmail.com ---
Ok, now turn on again the Setup/Editor/Raw Behavior/Use RawImport tool.
Load the ARW image in editor. Import Tool appear. On the bottom of the right
sidebar, you have a button named "Use Default". If
https://bugs.kde.org/show_bug.cgi?id=444280
--- Comment #31 from fri...@bluemail.ch ---
(In reply to caulier.gilles from comment #29)
> Ok great advancement.
>
> So i can conclude that crash only happen when you go back to the
> "Setup/Editor/Raw Behavior/Fast and Simple in 8 bits". Right ?
>
>
https://bugs.kde.org/show_bug.cgi?id=444280
--- Comment #30 from caulier.gil...@gmail.com ---
Note, here under Windows, trying to open the ARW test file with the 8 bits or
the 16 bits default settings do not crash digiKam...
Best
Gilles Caulier
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=444280
--- Comment #29 from caulier.gil...@gmail.com ---
Ok great advancement.
So i can conclude that crash only happen when you go back to the
"Setup/Editor/Raw Behavior/Fast and Simple in 8 bits". Right ?
If yes, can you also reproduce the crash when you
https://bugs.kde.org/show_bug.cgi?id=444280
--- Comment #28 from fri...@bluemail.ch ---
Hi Gilles
I worked through your suggestions.
Results:
Test 1
- closed FastRawViewer
- Renamed FastRawViewer Installattion directory from C:\Program Files\LibRaw to
C:\Program Files\LibRaw-temp
- start
https://bugs.kde.org/show_bug.cgi?id=444280
--- Comment #27 from caulier.gil...@gmail.com ---
Hi Frizzo,
The Raw Image Editor settings is located to Settings dialog from digiKam.
Go to Settings/Configure digiKam/ImageEditor page :
https://i.imgur.com/E4qu9nR.png
Raw Behavior tab allow to set
https://bugs.kde.org/show_bug.cgi?id=444280
--- Comment #26 from fri...@bluemail.ch ---
Gilles,
firstly, thanks for taking your time to look into this issue.
To answer: No special settings - that is intentionally. I installed V7.4,
select the image and F4. Where should I check for special
https://bugs.kde.org/show_bug.cgi?id=444280
--- Comment #25 from caulier.gil...@gmail.com ---
H Frizzo,
No problem to open the ARW file here under Windows :
https://i.imgur.com/6BpAeXJ.png
Did you use a specific settings for the demosaicing ?
Best
Gilles
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=444280
--- Comment #24 from fri...@bluemail.ch ---
Gilles,
I am just opening a local copy of the test image
https://www.imaging-resource.com/PRODS/sony-a7r-iii/Y-35MM-DSC01650.ARW.HTM
without any processing. The image is in sRGB color mode.
FRizzo
--
You are
https://bugs.kde.org/show_bug.cgi?id=444280
--- Comment #23 from caulier.gil...@gmail.com ---
Frizzo,
Did you use Color Management i digiKam ? If yes, did you use a specific color
profile to convert ARW to RGB color space ?
Best
Gilles Caulier
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=444280
--- Comment #22 from fri...@bluemail.ch ---
FYI: I tried the last build of v 7.4.0 as per 2021-12-11-Win64 and the issue
still persists.
FRizzo
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=444280
caulier.gil...@gmail.com changed:
What|Removed |Added
Version|7.3.0 |7.4.0
https://bugs.kde.org/show_bug.cgi?id=444280
caulier.gil...@gmail.com changed:
What|Removed |Added
CC||caulier.gil...@gmail.com
--- Comment
https://bugs.kde.org/show_bug.cgi?id=444280
--- Comment #20 from fri...@bluemail.ch ---
Mike,
thanks for your effort!
I will also install digikam on a second notebook which has much less additional
SW installed than my desktop. Just in case there are some side-effects very
deep under the hood.
https://bugs.kde.org/show_bug.cgi?id=444280
--- Comment #19 from Maik Qualmann ---
I organized a somewhat older notebook with an Intel Core I5 in order to be able
to test the Windows version even better in the future. A fresh Windows 10 with
all updates is installed. I cannot reproduce the
https://bugs.kde.org/show_bug.cgi?id=444280
--- Comment #18 from fri...@bluemail.ch ---
(In reply to R Ramina from comment #14)
> Same issue here, using windos 64 bit version of DK 7.3 and Canon R6 and M6
> cameras, CR2 and CR3 files. I also tried open CR2 files from Canon G12 and
> it also
https://bugs.kde.org/show_bug.cgi?id=444280
--- Comment #17 from fri...@bluemail.ch ---
I tried digiKam-7.4.0-2023T144931-Win64. Unfortunately it crashes too. I am
still using the test image Y-35MM-DSC01650.ARW. The stack trace also looks the
same.
Running on:
Processor Intel(R)
https://bugs.kde.org/show_bug.cgi?id=444280
--- Comment #16 from Maik Qualmann ---
The last digiKam function in the trace is from LibRaw::convert_to_rgb(). Just
why can't I reproduce it? Processor dependent?
If you make a backup of your database, you are welcome to test the pre-release
of
https://bugs.kde.org/show_bug.cgi?id=444280
--- Comment #15 from fri...@bluemail.ch ---
How can we proceed to pinpoint the root cause?
This is an excerpt of a C:\Users\xxxAppData\Local\CrashDumps dmp file .
Loading unloaded module list
...
This dump file has an exception of
https://bugs.kde.org/show_bug.cgi?id=444280
R Ramina changed:
What|Removed |Added
CC||rhram...@gmail.com
--- Comment #14 from R Ramina
https://bugs.kde.org/show_bug.cgi?id=444280
--- Comment #13 from fri...@bluemail.ch ---
(In reply to Maik Qualmann from comment #9)
> No, logging a TIFF file does not help. I see the messages for the first time
> in a DebugView log that was sent to us. You have a program that "monitors"
> or
https://bugs.kde.org/show_bug.cgi?id=444280
--- Comment #12 from fri...@bluemail.ch ---
(In reply to Maik Qualmann from comment #11)
> Do you have a Wacom tablet? The reports could come from Wacom and would then
> be uncritical.
>
> Maik
Yes, I have a tablet connected.
FRizzo
--
You are
https://bugs.kde.org/show_bug.cgi?id=444280
--- Comment #11 from Maik Qualmann ---
Do you have a Wacom tablet? The reports could come from Wacom and would then be
uncritical.
Maik
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=444280
--- Comment #10 from fri...@bluemail.ch ---
I started it with the icon pointing to "C:\Program Files\digiKam\digikam.exe"
FRizzo
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=444280
--- Comment #9 from Maik Qualmann ---
No, logging a TIFF file does not help. I see the messages for the first time in
a DebugView log that was sent to us. You have a program that "monitors" or
"accompanies" the digiKam process. Was digiKam started via
https://bugs.kde.org/show_bug.cgi?id=444280
--- Comment #8 from fri...@bluemail.ch ---
(In reply to Maik Qualmann from comment #7)
Krita does not ring a bell and is not installed.
Antivirus: I just have Windows Defender on this machine.
I could post a second log of opening a tiff file which
https://bugs.kde.org/show_bug.cgi?id=444280
--- Comment #7 from Maik Qualmann ---
I see some messages that do not come from digiKam, but seem to interact with
digiKam:
COsInterface::SetApp: set Instance = 0x4b1c (19228), AppID = 0, Name =
digikam()
https://bugs.kde.org/show_bug.cgi?id=444280
--- Comment #6 from fri...@bluemail.ch ---
Created attachment 142811
--> https://bugs.kde.org/attachment.cgi?id=142811=edit
output of DebugView64
Hi Maik
I have attached DebugView64 output X99Pro-1.log. At the end I appended the
entry from the
https://bugs.kde.org/show_bug.cgi?id=444280
--- Comment #5 from fri...@bluemail.ch ---
Mi Maik
I tested with your image and digKam also crashed. So this suggests an
installation specific issue on my end. I will install the DebugView tomorrow
and send the log.
Your image is an uncompressed ARW
https://bugs.kde.org/show_bug.cgi?id=444280
--- Comment #4 from Maik Qualmann ---
I tested it with this web sample:
https://www.imaging-resource.com/PRODS/sony-a7r-iii/Y-35MM-DSC01650.ARW.HTM
Download DebugView from Microsoft, we may already find an answer in our debug
logs (Debug environment
https://bugs.kde.org/show_bug.cgi?id=444280
--- Comment #3 from fri...@bluemail.ch ---
(In reply to Maik Qualmann from comment #1)
> With a test sample of this Sony camera from the web, I can neither reproduce
> a problem under Linux nor under a Windows10 or Windows11 VM.
> We may need a test
https://bugs.kde.org/show_bug.cgi?id=444280
--- Comment #2 from fri...@bluemail.ch ---
(In reply to Maik Qualmann from comment #1)
> With a test sample of this Sony camera from the web, I can neither reproduce
> a problem under Linux nor under a Windows10 or Windows11 VM.
> We may need a test
https://bugs.kde.org/show_bug.cgi?id=444280
Maik Qualmann changed:
What|Removed |Added
CC||metzping...@gmail.com
--- Comment #1 from Maik
44 matches
Mail list logo
