[kdeconnect] [Bug 442782] KDE Connect is draining battery

https://bugs.kde.org/show_bug.cgi?id=442782 --- Comment #4 from Jaroslav Skarvada --- +1, please add option to disable and manual enable only when needed. Otherwise it's unusable for me. Moreover, it's better for security not to run services you don't need at the moment. -- You are receiving

[kdeconnect] [Bug 442782] KDE Connect is draining battery

https://bugs.kde.org/show_bug.cgi?id=442782 Jaroslav Skarvada changed: What|Removed |Added CC||jskar...@redhat.com -- You are receiving

[digikam] [Bug 398166] Import from camera doesn't find path

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

[digikam] [Bug 398166] Import from camera doesn't find path

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

[digikam] [Bug 398166] Import from camera doesn't find path

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

[digikam] [Bug 398166] Import from camera doesn't find path

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/ &g

[digikam] [Bug 398166] Import from camera doesn't find path

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

[digikam] [Bug 398166] Import from camera doesn't find path

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

[digikam] [Bug 398166] Import from camera doesn't find path

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 libgphoto

[digikam] [Bug 398166] Import from camera doesn't find path

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: &

[digikam] [Bug 398166] Import from camera doesn't find path

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.img

[digikam] [Bug 398166] Import from camera doesn't find path

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

[digikam] [Bug 398166] Import from camera doesn't find path

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

[digikam] [Bug 398166] Import from camera doesn't find path

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/di

[digikam] [Bug 398166] Import from camera doesn't find path

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.

[digikam] [Bug 398166] Import from camera doesn't find path

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

[digikam] [Bug 398166] Import from camera doesn't find path

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.

[digikam] [Bug 398166] Import from camera doesn't find path

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

[digikam] [Bug 398166] Import from camera doesn't find path

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.

[digikam] [Bug 398166] Import from camera doesn't find path

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 p

[digikam] [Bug 398166] Import from camera doesn't find path

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.

[digikam] [Bug 398166] Import from camera doesn't find path

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

[digikam] [Bug 398166] Import from camera doesn't find path

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.

[digikam] [Bug 398166] Import from camera doesn't find path

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

[digikam] [Bug 398166] Import from camera doesn't find path

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

[digikam] [Bug 398166] Import from camera doesn't find path

https://bugs.kde.org/show_bug.cgi?id=398166 Jaroslav Skarvada changed: What|Removed |Added CC||jskar...@redhat.com --- Comment #16 from

[valgrind] [Bug 438984] Uncomplete report with C++ and --track-origins=yes

https://bugs.kde.org/show_bug.cgi?id=438984 --- Comment #1 from Jaroslav Skarvada --- The reproducer should be: valgrind --log-file=/var/tmp/log --trace-origins=yes powertop -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 438984] New: Uncomplete report with C++ and --track-origins=yes

https://bugs.kde.org/show_bug.cgi?id=438984 Bug ID: 438984 Summary: Uncomplete report with C++ and --track-origins=yes Product: valgrind Version: unspecified Platform: Other OS: Linux Status: REPORTED