[digikam] [Bug 470391] Cannot uninstall or update Nightly build
https://bugs.kde.org/show_bug.cgi?id=470391 --- Comment #30 from Judah Richardson --- (In reply to caulier.gilles from comment #29) > Judah, > > The new Windows installer is online. You can process the Check for Update by > now. > > Best > > Gilles Caulier Tried it just now and it worked flawlessly. Thanks very much! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 470391] Cannot uninstall or update Nightly build
https://bugs.kde.org/show_bug.cgi?id=470391 --- Comment #27 from Judah Richardson --- The latest installer seems to be tripping over itself. I get the same error message before, but Process Explorer shows that the offending C:\Program Files\digiKam\uninstall.exe process being started by the installer. So basically the installer starts a process, then complains it can't proceed because that process is running. Anyway, after experiencing the above, I uninstalled the existing instance and ran the new installer. It completed successfully. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 470391] Cannot uninstall or update Nightly build
https://bugs.kde.org/show_bug.cgi?id=470391 --- Comment #25 from Judah Richardson --- (In reply to caulier.gilles from comment #23) > Hi, > > The only process orphaned when digiKam crash due to dysfunction is > exiftool.exe and the QtWebEngineProcess.exe. The first one must be killed by > the installer, the second one not yet. I will fix it. At least > > The old orphaned processes sound come from the cross compiled version wich > is deprecated now. The new application installer is a native Windows 10 > version now. > > So, killing all digiKam stuff with the Windows process manager must be > enough. Here i never faced this kind of problem under Windows 10. > > To be clear i recommend : > > 1/ To uninstall properly digiKam from Windows control panel / Application > section. Thi include to kill exiftool.exe and QtWebEngineProcess.exe > 2/ To install the 8.2.0 pre-release from Windows. > 3/ Wait some days. We recompile and publish online the pre-release installer > every day. > 4/ Start digiKam and go to Help/Check for new version menu. If a new > installer is available online, this must stop properly the current digiKam > session and start the installer after downloading file. > > Best > > Gilles Caulier Thanks! Let me know when the new version with the fix you mentioned is available. I'll try again then. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 470391] Cannot uninstall or update Nightly build
https://bugs.kde.org/show_bug.cgi?id=470391 --- Comment #22 from Judah Richardson --- (In reply to caulier.gilles from comment #21) > Judah, > > Please try the new Windows installer 8.2.0 pre-release build under Windows > with VCPKG toolchain and MSVC. This one is not cross compiled : > > https://files.kde.org/digikam/ > > Gilles Caulier Well, some progress in this one: I actually did get past the UAC prompt to the installer. However, it suffers from the orphan process bug too, and this time I can't find any way to get around it. After killing all the rogue digiKam processes as described previously (the installer's kill option doesn't work, just as before), I get an error message saying: "You have C:\Program Files\digiKam\uninstall.exe running in C:\Program Files\digiKam. Select "Yes" to kill the process(es), "No" to retry or "Cancel" to quit." Clicking "Yes" dumps the installer back to digiKam 8.2.0 initial setup dialog, where clicking "Yes" presents the error message above all over again. Killing the rogue uninstall.exe process above doesn't fix or change any of the above. As before, I had to use Process Explorer to kill the rogue processes. I'm still confused as to how/why digiKam leaves orphan processes after exit 路♂️ So, in summary: different variation of the same problem, with the same result. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 470391] Cannot uninstall or update Nightly build
https://bugs.kde.org/show_bug.cgi?id=470391 --- Comment #20 from Judah Richardson --- OK. Well, the signed Win64 builds are the only ones I can test because they're the only ones I can install at all -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 470391] Cannot uninstall or update Nightly build
https://bugs.kde.org/show_bug.cgi?id=470391 --- Comment #18 from Judah Richardson --- @Gilles: Thanks for your efforts to fix this. Unfortunately this build suffers from the UAC installation failure bug (https://bugs.kde.org/show_bug.cgi?id=464084). Do the signed Nightly builds contain the fix? I may be able to test that (can't guarantee a timeline). -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 471310] digiKam 8.1.0 Win64 Nightly build fails to folderize imported PNG & HEIC files
https://bugs.kde.org/show_bug.cgi?id=471310 Judah Richardson changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #14 from Judah Richardson --- False alarm: was using a portable nightly build and not the stable build as I'd thought. Stable build doesn't have the issue. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 471310] digiKam 8.1.0 Win64 Nightly build fails to folderize imported PNG & HEIC files
https://bugs.kde.org/show_bug.cgi?id=471310 Judah Richardson changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- Ever confirmed|0 |1 --- Comment #13 from Judah Richardson --- Reopening this ... -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 471310] digiKam 8.1.0 Win64 Nightly build fails to folderize imported PNG & HEIC files
https://bugs.kde.org/show_bug.cgi?id=471310 --- Comment #12 from Judah Richardson --- (In reply to Judah Richardson from comment #9) > No worries, I was able to find and kill the orphan process using Process > Explorer. I've switched to portable digiKam release now. It appears to > support HEIC files as you promised. I'll see how the next import attempt > goes. Thanks! So I tried importing a few JPGs into the portable stable 8.1.0 version of digiKam just now and folderization failed there too despite the ISO standard option being checked. Any ideas? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 471310] digiKam 8.1.0 Win64 Nightly build fails to folderize imported PNG & HEIC files
https://bugs.kde.org/show_bug.cgi?id=471310 --- Comment #11 from Judah Richardson --- You said "yet", so I'm optimistic. Cautiously, haha. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 471310] digiKam 8.1.0 Win64 Nightly build fails to folderize imported PNG & HEIC files
https://bugs.kde.org/show_bug.cgi?id=471310 --- Comment #9 from Judah Richardson --- No worries, I was able to find and kill the orphan process using Process Explorer. I've switched to portable digiKam release now. It appears to support HEIC files as you promised. I'll see how the next import attempt goes. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 470391] Cannot uninstall or update Nightly build
https://bugs.kde.org/show_bug.cgi?id=470391 --- Comment #16 from Judah Richardson --- Process Explorer to the rescue again. It appears that whatever the orphan processes are, they are difficult to find. Process Explorer requires at least 2 attempts per orphan process to kill it. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 471310] digiKam 8.1.0 Win64 Nightly build fails to folderize imported PNG & HEIC files
https://bugs.kde.org/show_bug.cgi?id=471310 --- Comment #7 from Judah Richardson --- Aaaack. Now I can't uninstall the Nightly build due to https://bugs.kde.org/show_bug.cgi?id=470391 *sigh* -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 470391] Cannot uninstall or update Nightly build
https://bugs.kde.org/show_bug.cgi?id=470391 --- Comment #15 from Judah Richardson --- (In reply to caulier.gilles from comment #10) > @Judah Richardson > > Are you sure to need to use process-explorer for that. The process tab from > the task manager do not allows to see the defective process which still in > background ? > > https://superuser.com/a/268234 > > Gilles Caulier I tried this just now while trying to uninstall the Nightly build I installed in this bug https://bugs.kde.org/show_bug.cgi?id=471310 Unfortunately it doesn't work, as even though `tasklist | more` shows digikam.exe on PID 284, `taskkill /f /pid 284` give the following error: ERROR: The process with PID 284 could not be terminated. Reason: There is no running instance of the task. So the solution here is definitely to stop digiKam from leaving orphan processes after being closed. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 471310] digiKam 8.1.0 Win64 Nightly build fails to folderize imported PNG & HEIC files
https://bugs.kde.org/show_bug.cgi?id=471310 --- Comment #6 from Judah Richardson --- Ah nvm. I just realized the folder you linked to has portable builds in it. So I'll just have to manually install it to my user folder. Thanks for the details! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 471310] digiKam 8.1.0 Win64 Nightly build fails to folderize imported PNG & HEIC files
https://bugs.kde.org/show_bug.cgi?id=471310 --- Comment #5 from Judah Richardson --- (In reply to Maik Qualmann from comment #4) > The Nightly build from https://binary-factory.kde.org is a pure test version > and not recommended for productive use. Although this version has a valid > signature due to the compilation with the MSVC compiler and the KDE > infrastructure.. But it is a fully automatic build with many missing > functions. No HEIF or JPEG2000 support, no MySQL support and much more. > > We strongly recommend using digiKam from here: https://files.kde.org/digikam/ > > The defender message can be ignored, there was a problem with users who > downloaded the debug version not starting. The problem is solved and the > debug version is not needed for log messages. > > Maik Thanks Maik, but as I said the problem with the builds you linked to is they require admin authority on the target PC for installation. Is there any way to install them under non-admin permissions, perhaps to %appdata% instead? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 471310] digiKam 8.1.0 Win64 Nightly build fails to folderize imported PNG & HEIC files
https://bugs.kde.org/show_bug.cgi?id=471310 --- Comment #3 from Judah Richardson --- (In reply to caulier.gilles from comment #1) > Where did you take the Windows installer exactly ? >From the Nightly builds page you previously linked me to on a different bug ;) https://binary-factory.kde.org/view/Windows%2064-bit/job/Digikam_Nightly_win64/ I chose the Nightly build as the regular release needs admin permissions for installation on Windows, and I don't have admin permissions on the affected PC. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 471310] New: digiKam 8.1.0 Win64 Nightly build revision b25f356ce93e108f6f206f0be68735633dcbe560 fails to folderize imported PNG & HEIC files
https://bugs.kde.org/show_bug.cgi?id=471310 Bug ID: 471310 Summary: digiKam 8.1.0 Win64 Nightly build revision b25f356ce93e108f6f206f0be68735633dcbe560 fails to folderize imported PNG & HEIC files Classification: Applications Product: digikam Version: 8.1.0 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Import-PostProcessing Assignee: digikam-bugs-n...@kde.org Reporter: judahrichard...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Install the nightly build as a normal, non-admin user on Windows 10 x64 21H2 2. Assemble source folder containing JPG, PNG, and HEIC files 3. Attempt to import the above via Import -> Add Images... 4. In the import Settings, request folderization via ISO standard OBSERVED RESULT All files will be imported, but only the JPGs will be folderized. EXPECTED RESULT All files should be imported and folderized. SOFTWARE/OS VERSIONS Windows: 10 21H2 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 470391] Cannot uninstall or update Nightly build
https://bugs.kde.org/show_bug.cgi?id=470391 --- Comment #14 from Judah Richardson --- (In reply to caulier.gilles from comment #13) > Maik, > > Do you know why a zombie process under Windows will not visible in Process > Manager and appears in Process Explorer freeware ? It's a question of right, > as admin only can see this kind of executable on the system ? > > Judah, > > Windows provides a CLI tool named tasklist: > > https://superuser.com/questions/914782/how-do-you-list-all-processes-on-the- > command-line-in-windows > > Do you seen the same results than Process explorer with this command line > tool ? > > Gilles Caulier Gilles: thanks for the information. I don't have the time in the near term to test tasklist. Process Explorer is a GUI tool provided by Microsoft & is much easier to use. In any case, me testing would not address the issue that digiKam on Windows leaves orphaned processes running after the user closes the application. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 470391] Cannot uninstall or update Nightly build
https://bugs.kde.org/show_bug.cgi?id=470391 --- Comment #12 from Judah Richardson --- (In reply to Judah Richardson from comment #11) > (In reply to caulier.gilles from comment #10) > > @Judah Richardson > > > > Are you sure to need to use process-explorer for that. The process tab from > > the task manager do not allows to see the defective process which still in > > background ? > > > > https://superuser.com/a/268234 > > > > Gilles Caulier > > Neither digikam.exe nor exiftool.exe have ever never shown up in Task > Manager whenever I look for them there, so I use Process Explorer 路♂️ *have ever shown up in -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 470391] Cannot uninstall or update Nightly build
https://bugs.kde.org/show_bug.cgi?id=470391 --- Comment #11 from Judah Richardson --- (In reply to caulier.gilles from comment #10) > @Judah Richardson > > Are you sure to need to use process-explorer for that. The process tab from > the task manager do not allows to see the defective process which still in > background ? > > https://superuser.com/a/268234 > > Gilles Caulier Neither digikam.exe nor exiftool.exe have ever never shown up in Task Manager whenever I look for them there, so I use Process Explorer 路♂️ -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 470391] Cannot uninstall or update Nightly build
https://bugs.kde.org/show_bug.cgi?id=470391 --- Comment #8 from Judah Richardson --- (In reply to caulier.gilles from comment #1) > Run the Windows tasks manager and kill all digikam.exe and exiftool.exe > which still in background. > > Gilles Caulier I actually couldn't find digikam.exe anywhere in Task Manager. I had to use Process Explorer (https://learn.microsoft.com/en-us/sysinternals/downloads/process-explorer) to find it. Anyway, once I found it and killed it (it took 3 consecutive kill commands) I was able to uninstall and install as normal. I'd highly suggest digiKam *not* keep running in the background by default after exiting. Is there some way to change this behavior, or is it a bug? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 470391] New: Cannot uninstall or update Nightly build
https://bugs.kde.org/show_bug.cgi?id=470391 Bug ID: 470391 Summary: Cannot uninstall or update Nightly build Classification: Applications Product: digikam Version: 7.7.0 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Bundle-Windows Assignee: digikam-bugs-n...@kde.org Reporter: judahrichard...@gmail.com Target Milestone: --- Created attachment 159307 --> https://bugs.kde.org/attachment.cgi?id=159307=edit Installer error message. SUMMARY *** When trying to uninstall or update the nightly Win64 build from https://binary-factory.kde.org/view/Windows%2064-bit/job/Digikam_Nightly_win64/, I get the error `You have C:Program Files\bin\digikam.exe running in C:\Program Files\digikam. Select "Yes" to kill the process(es), "No" to retry or "Cancel" to quit.` I checked Task Manager and no such process is running. I also tried renaming the `digikam.exe` files in the installation folder, to no effect. *** STEPS TO REPRODUCE 1. Assuming you already have a nightly build installed, launch the installer for a subsequent version 2. Choose to install digikam for everyone on this computer 3. Click "Next" OBSERVED RESULT Error message described above appears. EXPECTED RESULT digikam installs completely. SOFTWARE/OS VERSIONS Windows: 10 64-bit macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 464084] After showing User Access Control prompt, installer fails to launch on Windows 10 22H2.
https://bugs.kde.org/show_bug.cgi?id=464084 --- Comment #7 from Judah Richardson --- (In reply to caulier.gilles from comment #4) > You can try the signed version compiled under Windows and MSVC here, just to > try installer. but do not claim that you lost features compared to the non > signed version cross compiled under Linux. > > https://binary-factory.kde.org/view/Windows%2064-bit/job/ > Digikam_Nightly_win64/ > > Gilles Caulier Update: The problem has persisted through the latest stable release, so I tried the signed Nighly Win64 build. It installed perfectly with no loss of the features I use. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 464084] After showing User Access Control prompt, installer fails to launch on Windows 10 22H2.
https://bugs.kde.org/show_bug.cgi?id=464084 --- Comment #6 from Judah Richardson --- (In reply to caulier.gilles from comment #4) > You can try the signed version compiled under Windows and MSVC here, just to > try installer. but do not claim that you lost features compared to the non > signed version cross compiled under Linux. > > https://binary-factory.kde.org/view/Windows%2064-bit/job/ > Digikam_Nightly_win64/ > > Gilles Caulier The installer launches just fine on that one, so it seems the signature really is the difference there. I think I'll wait for the next digiKam build to fix the issue since, as I said, I've never had this issue with digiKam previously. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 464084] After showing User Access Control prompt, installer fails to launch on Windows 10 22H2.
https://bugs.kde.org/show_bug.cgi?id=464084 --- Comment #5 from Judah Richardson --- (In reply to caulier.gilles from comment #3) > Signing installer introduce limitation and complexity. See the story here : > > https://bugs.kde.org/show_bug.cgi?id=398582 > > In others words, you must use Windows system to compile whole digiKam, and > you lost the Mysql/MariaDb support, ... and more... > > Gilles Caulier Ah, I see -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 464084] After showing User Access Control prompt, installer fails to launch on Windows 10 22H2.
https://bugs.kde.org/show_bug.cgi?id=464084 --- Comment #2 from Judah Richardson --- I'm aware it's an unsigned package; I've never had an issue installing it previously. This is the 1st build I've had problems with. I use Windows Defender and the protection log shows no corresponding entry. Same issue on a separate Windows 10 machine, also running 22H2 (19045.2486, to be precise) & Windows Defender. Even the in-app updater fails. FWIW the project should sign its installer. The fact that it's FLOSS is no excuse: OBS Studio is FLOSS and its installer is signed. In the same manner one would not expect Linux users to install binaries from an unsigned repo, Windows users should not be forced to run unsigned installers. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 464084] New: After showing UAC prompt, installer fails to launch on Windows 10 22H2
https://bugs.kde.org/show_bug.cgi?id=464084 Bug ID: 464084 Summary: After showing UAC prompt, installer fails to launch on Windows 10 22H2 Classification: Applications Product: digikam Version: 7.9.0 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Bundle-Windows Assignee: digikam-bugs-n...@kde.org Reporter: judahrichard...@gmail.com Target Milestone: --- SUMMARY After showing UAC prompt, installer fails to launch on Windows 10 22H2 STEPS TO REPRODUCE 1. Download installer 2. Double-click installer .exe file 3. Click Yes on UAC prompt OBSERVED RESULT Nothing happens. EXPECTED RESULT Installation proceeds. SOFTWARE/OS VERSIONS Windows: 10 22H2 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 448432] Importing images to be folderized by date causes them to be folderized by import date, not the date the picture was taken
https://bugs.kde.org/show_bug.cgi?id=448432 --- Comment #3 from Judah Richardson --- That worked, thanks! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 448432] New: Importing images to be folderized by date causes them to be folderized by import date, not the date the picture was taken
https://bugs.kde.org/show_bug.cgi?id=448432 Bug ID: 448432 Summary: Importing images to be folderized by date causes them to be folderized by import date, not the date the picture was taken Product: digikam Version: 7.4.0 Platform: Other OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Import-Albums Assignee: digikam-bugs-n...@kde.org Reporter: judahrichard...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Open digiKam 2. Attempt to import all the images from a folder with date-based sub-albums enabled 3. Import the images. OBSERVED RESULT All the imported images will be placed in a folder corresponding to the import date, not the date the picture was taken EXPECTED RESULT All the imported images should be placed in a folder corresponding to the date the picture was taken SOFTWARE/OS VERSIONS Windows: 10 x64 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
