https://bugs.kde.org/show_bug.cgi?id=498218
--- Comment #7 from HubMiner <[email protected]> --- Greetings Giles! TLDR: Still an issue. Just for my favorite app team, I got on my knees and switched video cable just for the test! :) # Versions Digikam: 8.8.0 Windows: 11 / 24H2 26100.7462 Nvidia driver: recent: 581.80 # Hardware setup: - Primary monitor is connected to CPU-integratred video. - Secondary monitor is connected to NVidia GPU. - No graphics issues with any other apps. # TEST 1: Open Nvidia Control Panel. * As intended, it shows only one monitor connected to the Nvidia GPU. PC is under a light load. Start Digikam. * Digikam opened on my default monitor that was connected to CPU-integratred video. Observed for a few minutes: working fine, finished startup scan. I dragged DK window to the secondary monitor (connected to NVidia GPU), idle for a few minutes. * no issues. While DK was on secondary monitor, I closed it (hoping to save its window position). * no issues. # TEST 2A: Start DK (after it was closed on secondary/Nvidia monitor). * DK window started on the secondary monitor. I didn't interact with the window. * After a few seconds, Windows crashed. # TEST 2B: Start DK again. * Crashed again. Approximate message: your device ran into problem and needs to restart... * The message dissapeared too fast - I could not catch the driver name. # TEST 3: Reconnect both monitors to NVidia GPU and verify their visibility with NVidia Control Panel. * success. Start DK. * success, the initial scan completed, running for 30 seconds. Move DK to the primary window and close (to save position). Start DK. * success, the initial scan completed, running for 30 seconds. An observation: while DK was starting, I was staring at Process Explorer. It showed "C:\Program Files\digiKam\snoretoast.exe" ran for a few seconds and closed. Probably some magic DK does under the hood. Windows EventLog mentions log files around the same time - possibly related. Please let me know if I can email them to you (I prefer not to post them in a public way). I can try to record DubugView trace if it helps. Thank you! -- You are receiving this mail because: You are watching all bug changes.
