https://bugs.kde.org/show_bug.cgi?id=398166
testdr...@arcor.de changed:
What|Removed |Added
CC||testdr...@arcor.de
--
You are receiving th
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #66 from Jean-Pierre Boucher ---
It' a good news, Frank Zappa said “*A mind is like a parachute. It doesn't
work if it is not open*.”
Keep progressing digikam for a long time...
Jean-Pierre Boucher
Le lun. 30 oct. 2023 à 14:22, a écrit :
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #65 from caulier.gil...@gmail.com ---
We currently switch from MXE to VCPKG framework to build digiKam for Windows.
The port is under progress. I hope finalize this step in next week.
In VCPKG project i see this entry about Gphoto2 under Wi
https://bugs.kde.org/show_bug.cgi?id=398166
caulier.gil...@gmail.com changed:
What|Removed |Added
CC||jp.bouch...@gmail.com
--- Comment #64
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #63 from Jaroslav Skarvada ---
(In reply to Jaroslav Skarvada from comment #62)
> Regarding the libwdi, I could try to get it into the MXE, but it seems it
> needs bundling of the libusb windriver which I currently don't know whether
> it's
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #62 from Jaroslav Skarvada ---
Regarding the libwdi, I could try to get it into the MXE, but it seems it needs
bundling of the libusb windriver which I currently don't know whether it's
possible from the MXE, but I will check it. Then it sho
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #61 from Jaroslav Skarvada ---
I built the git head (at the time I started with it it was
v7.5.0-322-gb6a672426b) and it works for me. This time it was nearly
straightforward experience, I only hit one MXE FTBFS bug and created PR for it
(ht
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #60 from Jaroslav Skarvada ---
(In reply to caulier.gilles from comment #59)
> Hi Jaroslav,
>
> New 7.6.0 pre-release Windows installer is online with last libgphoto2
> 2.2.58.
>
> https://files.kde.org/digikam/
>
> List of drivers still
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #59 from caulier.gil...@gmail.com ---
Hi Jaroslav,
New 7.6.0 pre-release Windows installer is online with last libgphoto2 2.2.58.
https://files.kde.org/digikam/
List of drivers still empty in config dialog :
https://i.imgur.com/9MVKfXr.p
https://bugs.kde.org/show_bug.cgi?id=398166
caulier.gil...@gmail.com changed:
What|Removed |Added
Component|Import-MainView |Import-WIA
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #58 from caulier.gil...@gmail.com ---
Hi Jaroslav,
I don't take a care about the comment #34. To automatize the process, we need
to do the following steps to be able to use libgphoto2 in digiKam under Windows
:
1/ checkout and cross-compile
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #57 from Jaroslav Skarvada ---
You also need to follow the steps from the comment 34, because normally the
windows mass storage or PTP driver will take over the libgphoto2/libusb
drivers.
--
You are receiving this mail because:
You are wat
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #56 from Jaroslav Skarvada ---
You may also try rebuilding the libgphoto2 with the legacy libusb enabled (i.e
try dropping the --with-libusb=no from the mxe). Maybe there is some wrong
ifdef in the code.
--
You are receiving this mail beca
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #55 from Jaroslav Skarvada ---
(In reply to caulier.gilles from comment #54)
> Hi Jaroslav,
>
> I rebuild libexif + libgphoto with the update of MXE, rebuild the digiKam
> installer.
> But, no chance, the list of libgphoto2 drivers still em
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #54 from caulier.gil...@gmail.com ---
Hi Jaroslav,
I rebuild libexif + libgphoto with the update of MXE, rebuild the digiKam
installer.
But, no chance, the list of libgphoto2 drivers still empty in setup dialog.
So an update of MXE libgphot
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #53 from caulier.gil...@gmail.com ---
Right, MXE update is required first :
-- Updating MXE
Depuis https://github.com/mxe/mxe
21ff2254..5e2f623d master -> origin/master
Mise à jour 21ff2254..5e2f623d
Fast-forward
src/libexif
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #52 from caulier.gil...@gmail.com ---
Hum 13 hours ago the commit to MXE repository.
So, i will try to update MXE packages installation now to see if it fix the
problem.
Gilles
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #51 from caulier.gil...@gmail.com ---
Hi Jaroslav,
The libusb fix must be included in my MXE installation, as i just rebuild all
from scratch 2 days ago.
Also, the way to list all gphoto2 camera drivers in digiKam do not depand of
libusb. T
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #50 from Jaroslav Skarvada ---
(In reply to Jaroslav Skarvada from comment #49)
> Thanks for applying the patches. So does it work now? IIRC there was some
> problem with the libusb on the MXE side, but it should be solved soon:
> https://gi
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #49 from Jaroslav Skarvada ---
(In reply to caulier.gilles from comment #48)
> Hi Jaroslav,
>
> Correction. I upgraded libgphoto2 under MacOS from 2.5.27 to 2.5.28, and now
> problem disappear :
>
> https://i.imgur.com/elfzIcG.png
>
> Per
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #48 from caulier.gil...@gmail.com ---
Hi Jaroslav,
Correction. I upgraded libgphoto2 under MacOS from 2.5.27 to 2.5.28, and now
problem disappear :
https://i.imgur.com/elfzIcG.png
Perhaps the problem is the same under Windows and MXE packa
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #47 from caulier.gil...@gmail.com ---
Hi Jaroslav,
I just compiled a Windows installer including Gphoto2 support. It's here :
https://files.kde.org/digikam/experimental/digiKam-7.6.0-20220125T171219-Win64-Gphoto2.exe.mirrorlist
Gilles Caul
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #46 from caulier.gil...@gmail.com ---
Hi Jaroslav,
I applied all your patches in git/master. Next digiKam 7.6.0 will support
officially Gphoto2 under Windows... but, no Gphoto2 camera driver is listed in
setup dialog if i want to select one
https://bugs.kde.org/show_bug.cgi?id=398166
caulier.gil...@gmail.com changed:
What|Removed |Added
CC||matthias.jo...@gmail.com
--- Comment
https://bugs.kde.org/show_bug.cgi?id=398166
caulier.gil...@gmail.com changed:
What|Removed |Added
CC||alain.pouchard1...@free.fr
--- Commen
https://bugs.kde.org/show_bug.cgi?id=398166
caulier.gil...@gmail.com changed:
What|Removed |Added
CC||wpvk...@gmail.com
--- Comment #43 fro
https://bugs.kde.org/show_bug.cgi?id=398166
caulier.gil...@gmail.com changed:
What|Removed |Added
Status|ASSIGNED|CONFIRMED
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #42 from caulier.gil...@gmail.com ---
All patches from Jaroslav Skarvada are applied. MXE build system need to be
rebuild to include libgphoto2. This will be done in few days.
Gilles Caulier
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #41 from caulier.gil...@gmail.com ---
Git commit 900e6e71de416481061762541b8ccb73764b6a55 by Gilles Caulier.
Committed on 20/01/2022 at 08:58.
Pushed by cgilles into branch 'master'.
Apply patch from Jaroslav Škarvada to enable libgphoto2 un
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #40 from caulier.gil...@gmail.com ---
Git commit fef060f7cae15b12b9553d0cb0d24b3b5b61d3a4 by Gilles Caulier.
Committed on 20/01/2022 at 08:11.
Pushed by cgilles into branch 'master'.
Apply patch from Jaroslav Škarvada silent marble libraries
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #39 from caulier.gil...@gmail.com ---
Git commit debfe81f73f2099537d479059a0c58d15667a83b by Gilles Caulier.
Committed on 20/01/2022 at 08:04.
Pushed by cgilles into branch 'master'.
Apply patch from Jaroslav Škarvada to fix unzip arguments
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #38 from caulier.gil...@gmail.com ---
Git commit 445e681592c2c7893af72bbcf1ce8ec5f42bae74 by Gilles Caulier.
Committed on 20/01/2022 at 07:59.
Pushed by cgilles into branch 'master'.
add url alternative for annonymous access to git repositor
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #37 from caulier.gil...@gmail.com ---
Apply patch from Jaroslav Škarvada to fix broken compilation under Fedora 33
CCMAIL: jskar...@redhat.com
FIXED-IN: 7.6.0
M +4-5core/libs/dngwriter/extra/xmp_sdk/XMPCore/source/XMPUtils.cpp
http
https://bugs.kde.org/show_bug.cgi?id=398166
caulier.gil...@gmail.com changed:
What|Removed |Added
Blocks||388137
Referenced Bugs:
https://bug
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #36 from Jaroslav Skarvada ---
digiKam PR:
https://invent.kde.org/graphics/digikam/-/merge_requests/136
Unofficial unsupported build for testing (it's built from the v7.3.0 tag):
https://jskarvad.fedorapeople.org/digiKam/digiKam-7.3.0-Win64
https://bugs.kde.org/show_bug.cgi?id=398166
Bug Janitor Service changed:
What|Removed |Added
Status|REPORTED|ASSIGNED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #34 from Jaroslav Skarvada ---
I got it working even for non-admin user. I also tried the libusb-win32 driver,
but it's crashing during download of the photos. The WinUSB driver seems to
work the most reliable way.
Steps how to install it:
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #33 from Jaroslav Skarvada ---
(In reply to caulier.gilles from comment #32)
> To implement a Windows native support in digiKam import tool, this interface
> must be re-implemented :
>
> https://invent.kde.org/graphics/digikam/-/blob/master
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #32 from caulier.gil...@gmail.com ---
To implement a Windows native support in digiKam import tool, this interface
must be re-implemented :
https://invent.kde.org/graphics/digikam/-/blob/master/core/utilities/import/backend/dkcamera.h
As it
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #31 from Jaroslav Skarvada ---
Also probably dupes (maybe there are more):
https://bugs.kde.org/show_bug.cgi?id=398061
https://bugs.kde.org/show_bug.cgi?id=379970
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #30 from Jaroslav Skarvada ---
I finally got it working, gphoto2 upstream bug:
https://github.com/gphoto/libgphoto2/issues/706
TLDR the digiKam has to be running under the admin account and I had to replace
the windows PTP drivers for all d
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #29 from Jaroslav Skarvada ---
I finally cross-compiled gphoto2 in the mxe with some effort, spotted gphoto2
bug:
https://github.com/gphoto/gphoto2/issues/448
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #28 from caulier.gil...@gmail.com ---
yes, digiKam is only compiled in 64 bits now under Windows, as 32 bits is
limited with memory allocation and introduce dysfunctions with large memory
usage features, as face workflow for example.
Gilles
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #27 from Jaroslav Skarvada ---
(In reply to Jaroslav Skarvada from comment #26)
> FTR I am testing on the Windows 10, the latest stable build. I am using the
> latest master of the digiKam.
64 bit Windows 10, 64 bit digiKam/libraries build.
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #26 from Jaroslav Skarvada ---
FTR I am testing on the Windows 10, the latest stable build. I am using the
latest master of the digiKam.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #25 from Jaroslav Skarvada ---
(In reply to caulier.gilles from comment #23)
> I think that libgphoto2 needs libusb1 at run time (or something like that).
>
Yep, I already had it (libusb1). I verified it's bundled and loaded (I patched
the b
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #24 from Jaroslav Skarvada ---
Another libgphoto2 PR:
https://github.com/gphoto/libgphoto2/pull/705/
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=398166
caulier.gil...@gmail.com changed:
What|Removed |Added
Version|6.0.0 |7.4.0
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=398166
caulier.gil...@gmail.com changed:
What|Removed |Added
CC||mar...@jet.franken.de
--- Comment #23
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #22 from Jaroslav Skarvada ---
The camera is detected fine, but I am getting: GP_ERROR_IO_USB_CLAIM (Could not
claim the USB device -53) from the libgphoto2 when trying to access it. I tried
multiple cameras, but it's still the same. Running
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #21 from Jaroslav Skarvada ---
Another digiKam PR:
https://invent.kde.org/graphics/digikam/-/merge_requests/135
libexif mxe PR:
https://github.com/mxe/mxe/pull/2700
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #20 from Jaroslav Skarvada ---
Related digiKam PR (just for the reference, it's unrelated to the comment 19):
https://invent.kde.org/graphics/digikam/-/merge_requests/133
--
You are receiving this mail because:
You are watching all bug cha
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #19 from Jaroslav Skarvada ---
It seems I am slowly progressing. There were several problems. I will PR more
patches to mxe, libgphoto2 upstreams and also to digiKam.
At the moment under Win 10 it successfully detects the camera and adds it
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #18 from caulier.gil...@gmail.com ---
Look the list of files installed by libgphoto2 under Centos 8 (last section on
the bottom):
http://rpmfind.net/linux/RPM/centos/8-stream/appstream/x86_64/Packages/libgphoto2-2.5.16-3.el8.x86_64.html
Don
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #17 from caulier.gil...@gmail.com ---
Hi, great to see a MinGW support of libgphoto.
Check if config files are not missing after installation. Look how RPM under
linux install files on the system from this library, and try to reproduce it
un
https://bugs.kde.org/show_bug.cgi?id=398166
Jaroslav Skarvada changed:
What|Removed |Added
CC||jskar...@redhat.com
--- Comment #16 from Ja
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #15 from caulier.gil...@gmail.com ---
Git commit cdee9fb951c3f1b3aa354535174eb7c232a241eb by Gilles Caulier.
Committed on 10/01/2021 at 16:02.
Pushed by cgilles into branch 'master'.
Solid info dialog: add new tab with hotplug device events.
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #14 from caulier.gil...@gmail.com ---
Git commit 1d69260946da53b92067105224468723482e2f8c by Gilles Caulier.
Committed on 09/01/2021 at 19:20.
Pushed by cgilles into branch 'master'.
Solid Hardware resume dialog. Use real tree-view to displa
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #13 from caulier.gil...@gmail.com ---
Git commit c3077451a517fb160e0e25a9991a279948610500 by Gilles Caulier.
Committed on 08/01/2021 at 15:58.
Pushed by cgilles into branch 'master'.
Add new dialog with all devices detected by KF5::Solid har
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #12 from Jan van Bekkum ---
Created attachment 130875
--> https://bugs.kde.org/attachment.cgi?id=130875&action=edit
Cannot connect
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #11 from Jan van Bekkum ---
Created attachment 130874
--> https://bugs.kde.org/attachment.cgi?id=130874&action=edit
Smartphone not visible
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #10 from Jan van Bekkum ---
Created attachment 130873
--> https://bugs.kde.org/attachment.cgi?id=130873&action=edit
Smartphone visible
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #9 from Jan van Bekkum ---
I did the following tests:
NOKIA SMARTPHONE
Steps:
1. Connect Nokia 8.1 smartphone via USB to Windows 10 PC. In Windows explorer
the smartphone is visible (image 1)
2. In Digikam select Import>Cameras>Add camera m
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #8 from caulier.gil...@gmail.com ---
digiKam 7.0.0 stable release is now published and now available as FlatPak:
https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/
We need a fresh feedback on this file using this version.
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #7 from caulier.gil...@gmail.com ---
Git commit e46413392f880991744ba3e88a67a24afb8484a2 by Gilles Caulier.
Committed on 03/09/2018 at 15:36.
Pushed by cgilles into branch 'master'.
update bundle to last stable libgphoto2 2.5.19
enable libgp
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #6 from caulier.gil...@gmail.com ---
Good news : the last stable libgphoto2 2.5.18 cross compile file with MXE for
windows target. So i will include the library in next installer and recompile
whole digiKam with gphoto2 support.
Gilles Cauli
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #5 from Jan van Bekkum ---
I understand, thanks.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=398166
caulier.gil...@gmail.com changed:
What|Removed |Added
CC||caulier.gil...@gmail.com
--- Comment
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #3 from Jan van Bekkum ---
I tried with a path (N:\Pictures Margriet\2007 05 06)only (not selecting USB or
any of the other options, but the result was the same. And again when I
selected Edit all settings were gone.
--
You are receiving t
https://bugs.kde.org/show_bug.cgi?id=398166
Maik Qualmann changed:
What|Removed |Added
CC||metzping...@gmail.com
--- Comment #2 from Maik
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #1 from Jan van Bekkum ---
Created attachment 114748
--> https://bugs.kde.org/attachment.cgi?id=114748&action=edit
Camera settings screen (image 2)
See previous comment
--
You are receiving this mail because:
You are watching all bug ch
71 matches
Mail list logo