[digikam] [Bug 458143] Opening a picture using OpenGL viewer generates an OpenGL error then digikam crashes

2022-08-22 Thread Jean-Fred
https://bugs.kde.org/show_bug.cgi?id=458143

--- Comment #4 from Jean-Fred  ---
Maik,

More investigation results on my side.
I did a few experiments to address the folowing things:
1 - About the missing libEGL.dll lib:
I copied a few ANGLE related dlls from Chrome in to digiKam dir (It
seems ANGLE comes from Google...)
That changes things quite a bit:
I first get a different error message telling that GL_ARB_texture is
not managed.
(This is confirmed by DebugView log: "1756  47.07304001 [13568]
digikam.dplugin.generic: GL_ARB_texture_rectangle not supported.")
Process explorer shows that ligEGL.dll, d3compiler_47.dll and d3d11.dll
(the one I copied) are loaded when OpenGL viewer is called.
When clicking OK in error window no crash any more but a black OpenGL
Viewer window.
From the info I found, ANGLE seems not to support
GL_ARB_texture_rectangle extension => consistent with behavior described above.
2 - About the missing opengl32sw.dll lib:
Was no able to find an opengl32sw.dll lib that works if libEGL is not
there... Probably need to match library Qt5 was linked against...
3 - About understanding why my openGL seems not to work with digiKam:
Looking to Qt5 doc, there is a way to force the use of desktop OpenGL
driver through the use of an env. var.
I tried this from a command prompt: "set QT_OPENGL=desktop" then start
digiKam from same prompt.
Doing so digiKam OpenGL viewer operates flawlessly - no doubt that
display is hardware acelerated considering how fast display refreshes.
(Whether the extra libegl:... libraries are in digiKam dir or not does
not chnage anything.)
I guess that the way Qt5 manages OpenGL is that it first checks if a desktop
openGL driver is available if not it tries ANGLE (which will fail if libegl and
its dependencies are not there) and finally tries openGL software emulation
(which fails if opengl32sw is not there).
On my system, not sure why, it seems Qt5 fails to detect if an openGL desktop
driver is there...
To conclude with this, I added QT_OPENGL in my environment variable and that
works.
However I think that's not very clean as this may interfere with other Qt
apps...
Maybe there are other ways to force Qt using desktop driver usage from inside
the app, that may allow implementation of a "OpenGL driver" checkbox/combobox
inside digiKam config.
Not sure why Qt5 does fail detecting my openGL driver (a bug?).
As a side note, maybe libegl and related libs as well as opengl32sw lib need to
be added to the window bundle (even though libegl does not help) to get all
dependencies fullfilled?

Regards,

Jean-Fred

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 458143] Opening a picture using OpenGL viewer generates an OpenGL error then digikam crashes

2022-08-21 Thread Jean-Fred
https://bugs.kde.org/show_bug.cgi?id=458143

--- Comment #3 from Jean-Fred  ---
Hi Maik,

Yes, latest Intel driver was installed for MS update, and no, Intel does not
provide directly any W10 driver pack for this (pretty old) adapter.
As a matter of fact, the driver pack provided by MS update seems to be coming
directly from Intel (driver dialog reports Package provider = Intel Corp.) - MS
seems to only take care of package signature.
To verify nothing is obviously wrong with my system, I ran OpenGL Extensions
Viewer on my system to see what level of OpenGL is fully supported by my
system. It report OpenGL 2.1 is 100% supported which should be fine for Qt5 I
think.
The interesting thing is that when digiKam is running normally (i.e. before
calling OpenGL viewer), Process Explorer reports it is dynamically linking
opengl32.dll, which probably means OpenGL Viewer and/or other part of digiKam
is using openGL through "desktop" OpenGL driver I guess.
Not sure however why digiKam/Qt requires libEGL.dll/opengl32ws.dll if a valid
openGL driver is already present on the system as from what I understand those
dlls are related to software and/or directx emulation of openGL calls...

Regards,

Jean-Fred

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 458143] Opening a picture using OpenGL viewer generates an OpenGL error then digikam crashes

2022-08-21 Thread Jean-Fred
https://bugs.kde.org/show_bug.cgi?id=458143

--- Comment #1 from Jean-Fred  ---
More info...

Looking to DebugView log, it seems that digiKam/Qt does not manage to find a
few DLLs:
...
064434.28241348 [9392] digikam.dplugin.generic: 145 images
loaded   
064534.63073349 [9392] Failed to load libEGL (Le module
spécifié est introuvable.)  
064634.63084412 [9392] create: Failed to load and resolve
libEGL functions  
064734.63422012 [9392] Failed to load opengl32sw.dll (Le module
spécifié est introuvable.)  
064834.63431931 [9392] Failed to load and resolve WGL/OpenGL
functions  
...

>From the info I was able to gather, those also seems to be part of Mesa3d
and/or angle.
Unsurprinsingly, I was not able to find any of those library anywhere on my
system...
Should those libraries be part of the Windows bundle or be already part of the
system?

Regards,

JF

Thanks!

JF

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 458145] Geolocation editor works properly when opened from ShowFoto but not when opened from digiKam

2022-08-21 Thread Jean-Fred
https://bugs.kde.org/show_bug.cgi?id=458145

--- Comment #5 from Jean-Fred  ---
Hi again Maik,

Thanks A LOT!
That was it... Now things work smoothly and I can edit picture Geolocation
directly from DigiKam.

... not sure where those double slashes are coming from in my config. I'm using
same database from years, and this slash thing sems to only affect Geolocation
Editor (I juts tried it recently).
Quick question: my understanding is that Geolocation Editor directly add/edit
GPS EXIF tags in picture files, not only in DigiKam database (independantly of
how digiKam is configured). Is that a correct understanding?

Thanks again for your time and help with this!

Regards,

Jean-Fred

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 458145] Geolocation editor works properly when opened from ShowFoto but not when opened from digiKam

2022-08-21 Thread Jean-Fred
https://bugs.kde.org/show_bug.cgi?id=458145

--- Comment #3 from Jean-Fred  ---
Hi Maik,

Here is the DebugView log.
The file referenced in the log on line 539 of the log really exits and can be
openend correctly (this is the exact one ShowFoto manages to deal with).
Regards,

JF

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 458145] Geolocation editor works properly when opened from ShowFoto but not when opened from digiKam

2022-08-21 Thread Jean-Fred
https://bugs.kde.org/show_bug.cgi?id=458145

--- Comment #2 from Jean-Fred  ---
Created attachment 151480
  --> https://bugs.kde.org/attachment.cgi?id=151480=edit
digiKam DebugView output from digiKam restart to opening GeolocationEditor.

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 458145] New: Geolocation editor works properly when opened from ShowFoto but not when opened from digiKam

2022-08-21 Thread Jean-Fred
https://bugs.kde.org/show_bug.cgi?id=458145

Bug ID: 458145
   Summary: Geolocation editor works properly when opened from
ShowFoto but not when opened from digiKam
   Product: digikam
   Version: 7.7.0
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Plugin-Generic-GeolocationEdit
  Assignee: digikam-bugs-n...@kde.org
  Reporter: jf...@free.fr
  Target Milestone: ---

Created attachment 151478
  --> https://bugs.kde.org/attachment.cgi?id=151478=edit
GeolocationEditor picture list when called from DigiKam (left) and showFoto
(right)

SUMMARY
Geolocation editor does not behave correctly when opened from digiKam: in the
picture list below the map, none of the field is populated properly. Oddly,
when call from ShowFoto on same picture everything works fine...


STEPS TO REPRODUCE
1. Select a picture in thumbnail view
2. Open Geolocation Editor from DigiKam menu
3. 

OBSERVED RESULT
Geolocation editor correctly opens.
However, in geolocation editor picture list (below the map) thumbnail appears
empty and none of the other fields is correctly populated. Date/Time displays
as "unavailable".
Odd thing is that when the Geolocation editor is called for the same picture
from ShowFoto, everything looks fine - see attached pictures.

EXPECTED RESULT
Geolocation editor should behave the same when called from DigiKam than it
behaves when caled from ShowFoto.

SOFTWARE/OS VERSIONS
Windows: Windows 10 Professionnel 64bits 21H2 - Build 19044.1889
Qt Version: 5.15.5

ADDITIONAL INFORMATION
DigiKam is installed from Windows bundle found on digiKam web site
(digiKam-7.7.0-Win64.exe).
Tried with many different pictures from different cameras: same behavior.
Note that digiKam 6.4.0 was also behaving the same on my system. So that may be
system related, like some sort of system specific thing that is not managed
correctly by digiKam/Qt/... - I was however never able to find exactly what may
be wrong on the system side. Any clue?
Let me know how/if I can help with this.

Thanks!

JF

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 458143] New: Opening a picture using OpenGL viewer generates an OpenGL error then digikam crashes

2022-08-21 Thread Jean-Fred
https://bugs.kde.org/show_bug.cgi?id=458143

Bug ID: 458143
   Summary: Opening a picture using OpenGL viewer generates an
OpenGL error then digikam crashes
   Product: digikam
   Version: 7.7.0
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: Plugin-Generic-GLViewer
  Assignee: digikam-bugs-n...@kde.org
  Reporter: jf...@free.fr
  Target Milestone: ---

SUMMARY
On my system, OpenGL image viewer does not work and results in systematic
digiKam crash.
It looks like OpenGL context cannot initialize properly for some reason.

STEPS TO REPRODUCE
1. Select a picture.
2. Open OpenGL viewer from menubar.
3. 

OBSERVED RESULT
In a first time an error window shows up with message like "No OpenGL context
found"
Clicking on "OK" closes the error windows.
As soon as digiKam main window is clicked, it freezes briefly then exits
abruptly.

EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: Windows 10 Professionnel 64bits 21H2 - Build 19044.1889
Qt Version: 5.15.5

ADDITIONAL INFORMATION
DigiKam is installed from Windows bundle found on digiKam web site
(digiKam-7.7.0-Win64.exe).
System display adapter (Intel HD Graphics) supports OpenGL up to 2.1 included.

Thanks!
JF

-- 
You are receiving this mail because:
You are watching all bug changes.