https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #108 from caulier.gil...@gmail.com ---
Qt 6.6.2 is planed for the 17 january:
https://wiki.qt.io/Qt_6.6_Release
As usual Qt team delay a little bit the release date. Also, Qt 6.6.2 must be
updated to VCPKG. This will delay again the usage
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #107 from Maik Qualmann ---
Qt has closed the bug (https://bugreports.qt.io/browse/QTBUG-120285) for
version 6.6.2. Qt added a cache for the timezone. I'll test the performance,
maybe we'll go back to a local datetime internally.
Maik
--
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #106 from ivar.ek...@gmail.com ---
Ok, so this must be different then. I created bug 479148 with full my log.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #105 from Peter ---
(In reply to ivar.ekman from comment #103)
> digiKam-8.3.0-20231228T113341-Win64-debug.exe is still fails to start
> identically as version 8.2.0 for me on Windows 10 with the splash stating
> "Loading tools..." This
https://bugs.kde.org/show_bug.cgi?id=477853
Maik Qualmann changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REOPENED
https://bugs.kde.org/show_bug.cgi?id=477853
ivar.ek...@gmail.com changed:
What|Removed |Added
Status|RESOLVED|REOPENED
CC|
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #102 from Peter ---
(In reply to caulier.gilles from comment #101)
> I'm not sure that root file messages are forwarded to all peoples in all
> duplicates... I will post a message in all files tomorrow when next
> installer will be ready
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #101 from caulier.gil...@gmail.com ---
I'm not sure that root file messages are forwarded to all peoples in all
duplicates... I will post a message in all files tomorrow when next installer
will be ready to test.
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #100 from Maik Qualmann ---
I always thought that all duplicate bugs also receive the messages?
Maik
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=477853
Maik Qualmann changed:
What|Removed |Added
Version Fixed In||8.3.0
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #99 from caulier.gil...@gmail.com ---
Hi Maik,
I will rebuild the Windows installer tomorrow morning.
What's about the duplicates bugs ? Perhaps we can forward the information about
these changes to see the side-effects.
Best
Gilles
--
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #98 from Maik Qualmann ---
This is a relatively big change, I'm sure I may have missed something. It will
be further stabilized over the next few weeks.
We don't need to convert the database and can even work with a mix of local
time and
https://bugs.kde.org/show_bug.cgi?id=477853
Maik Qualmann changed:
What|Removed |Added
Latest Commit||https://invent.kde.org/grap
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #96 from Peter ---
Created attachment 164438
--> https://bugs.kde.org/attachment.cgi?id=164438=edit
digiKam 8.3 log
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #95 from Maik Qualmann ---
@Peter, can you post a debug log to see how the DatesJob time changes?
This is also just a test, the date display may differ in the Dates View
depending on whether the UTC date <-> local date falls on a different
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #94 from Peter ---
Excellent work! digiKam is now working fast again!
Thank You Maik and Gilles!
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #93 from Peter ---
(In reply to caulier.gilles from comment #92)
> Peter,
>
> The new 8.3.0 Windows installer is updated at usual place.
>
> Have an happy Christmas time.
>
> Gilles Caulier
Thanks Gilles,
I'll test it right away.
Merry
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #92 from caulier.gil...@gmail.com ---
Peter,
The new 8.3.0 Windows installer is updated at usual place.
Have an happy Christmas time.
Gilles Caulier
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=477853
Bug Janitor Service changed:
What|Removed |Added
Priority|NOR |HI
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=477853
caulier.gil...@gmail.com changed:
What|Removed |Added
CC||hannesjaag...@gmail.com
--- Comment
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #90 from Maik Qualmann ---
Git commit 19be2e0a54364bc5bf23a446e1f84bc0d187fa22 by Maik Qualmann.
Committed on 25/12/2023 at 09:35.
Pushed by mqualmann into branch 'master'.
for a test use UTC for the DatesJob
M +1-1
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #89 from caulier.gil...@gmail.com ---
Hi Maik,
First, have an happy Christmas time with your family.
Here with my i9 32 cores + 64 Gb, it take 4 hours. QtWebEngine is the most
consuming part to build. with MSVC, 2 hours to build the no
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #88 from Maik Qualmann ---
Gilles,
I think not much will change at the moment when switching to Qt-6.6.1 and the
current KF6.
I suspect it will take hours to compile, if you have the time feel free to do
so.
But I'm afraid that the bug
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #87 from caulier.gil...@gmail.com ---
Maik,
Even if the Qt bug is not yet fixed in 6.6.1, perhaps it's the good moment to
rebuild the VCPKG installation on my Windows 10 VM ? This will update Qt to
6.6.1 and KDE frameworks. What do you
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #86 from Peter ---
(In reply to Maik Qualmann from comment #85)
> I'm sure this Qt bug is the cause as it only affects Windows. What time zone
> do you live in?
>
> https://bugreports.qt.io/browse/QTBUG-120285
>
> Maik
I live in Central
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #85 from Maik Qualmann ---
I'm sure this Qt bug is the cause as it only affects Windows. What time zone do
you live in?
https://bugreports.qt.io/browse/QTBUG-120285
Maik
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #84 from Peter ---
Created attachment 164422
--> https://bugs.kde.org/attachment.cgi?id=164422=edit
A log on the same computer, in digiKam 8.2.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #83 from Peter ---
Created attachment 164421
--> https://bugs.kde.org/attachment.cgi?id=164421=edit
I disabled the "Find new items" and restarted digiKam.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #82 from Peter ---
Created attachment 164420
--> https://bugs.kde.org/attachment.cgi?id=164420=edit
"Find new items" is completed
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #81 from Peter ---
(In reply to Maik Qualmann from comment #80)
> What surprises me about your logs is that you have activated the initial
> scan:
>
> 16.33045959 [7800] digikam.general: scan mode: ScanDeferredFiles
> 18.13652802
https://bugs.kde.org/show_bug.cgi?id=477853
Erik Herlé changed:
What|Removed |Added
CC|erik.herle+...@mailbox.org |
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #80 from Maik Qualmann ---
What surprises me about your logs is that you have activated the initial scan:
16.33045959 [7800] digikam.general: scan mode: ScanDeferredFiles
18.13652802 [7800] digikam.general: total scan value :
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #79 from Peter ---
Created attachment 164419
--> https://bugs.kde.org/attachment.cgi?id=164419=edit
digiKam-8.3.0-20231224T080451-Win64.exe
Tested: digiKam-8.3.0-20231224T080451-Win64.exe
Unfortunately, the situation is not better. :-(
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #78 from caulier.gil...@gmail.com ---
Note : digiKam 8.3.0 pre-release Windows installer updated at usual place with
last Maik changes and ready for testing...
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #77 from Maik Qualmann ---
Git commit f637ec4c07185389b18872150511f55b3ba7e389 by Maik Qualmann.
Committed on 24/12/2023 at 08:00.
Pushed by mqualmann into branch 'master'.
for a test force raster widgets
M +6-0
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #76 from Maik Qualmann ---
For the trash problem, check for bug 478722.
Before you delete the trash, wait for the next digiKam test version.
A test here shows a slowdown of 1.3 seconds when calculating the size of the
trash with my slow
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #75 from Peter ---
(In reply to Peter from comment #73)
> (In reply to Maik Qualmann from comment #72)
> > @Peter, do you have a “full” trash with lots of files in your collections?
> >
> > Maik
>
> Yes!
The collection is owned by a
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #74 from caulier.gil...@gmail.com ---
>> Maik,
>>
>> Depending of the next debugview results and the my free time while this week
>> end, i will plan this week end a major update of the Win10 VM to rebuild
>> VCPKG from scratch. This will
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #73 from Peter ---
(In reply to Maik Qualmann from comment #72)
> @Peter, do you have a “full” trash with lots of files in your collections?
>
> Maik
Yes!
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #72 from Maik Qualmann ---
@Peter, do you have a “full” trash with lots of files in your collections?
Maik
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #71 from Peter ---
(In reply to caulier.gilles from comment #62)
> Maik,
>
> Depending of the next debugview results and the my free time while this week
> end, i will plan this week end a major update of the Win10 VM to rebuild
> VCPKG
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #70 from caulier.gil...@gmail.com ---
But one Q is : why this time latency do not appears in Qt5 version ?
Gilles
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #69 from Maik Qualmann ---
I think we can solve the biggest timing problem if we disable sorting while
adding date items to the date list view. So that the list view is not sorted
again every time an item is added.
Maik
--
You are
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #68 from Maik Qualmann ---
I think this confirms my suspicion.
About 9 seconds to collect the date information and count. This still happens
in the JobThread. But 95 seconds to create the date map in the GuiThread is
extreme
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #67 from Peter ---
(In reply to Peter from comment #65)
> Created attachment 164179 [details]
> A log the after "configure digiKam..." opening/closing/opening
Oops, the first 'A log the after "configure digiKam..."
opening/closing/opening'
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #66 from Peter ---
Created attachment 164180
--> https://bugs.kde.org/attachment.cgi?id=164180=edit
A log the after "configure digiKam..." opening/closing/opening
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #65 from Peter ---
Created attachment 164179
--> https://bugs.kde.org/attachment.cgi?id=164179=edit
A log the after "configure digiKam..." opening/closing/opening
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #64 from Peter ---
Created attachment 164178
--> https://bugs.kde.org/attachment.cgi?id=164178=edit
20231215_debugview_log
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #63 from Peter ---
(In reply to caulier.gilles from comment #62)
> Maik,
>
> Depending of the next debugview results and the my free time while this week
> end, i will plan this week end a major update of the Win10 VM to rebuild
> VCPKG
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #62 from caulier.gil...@gmail.com ---
Maik,
Depending of the next debugview results and the my free time while this week
end, i will plan this week end a major update of the Win10 VM to rebuild VCPKG
from scratch. This will include a bump
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #61 from Maik Qualmann ---
The commit doesn't fix the problem either. He adds timers to try to identify
which process is causing the slowdown. So now I need a new DebugView Log where
the problem occurs.
Maik
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #60 from Peter ---
(In reply to Maik Qualmann from comment #56)
> @Gilles, can you please create a new Windows bundle, I want to exclude the
> DatesJob or not.
>
> @Peter, as a test you can sort your albums and items by name/path instead
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #59 from caulier.gil...@gmail.com ---
Maik,
New Windows bundle is online
Gilles
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #58 from Maik Qualmann ---
Git commit 13b7cb786389e7ac05fc86533f7b498ed335b05e by Maik Qualmann.
Committed on 14/12/2023 at 20:52.
Pushed by mqualmann into branch 'master'.
add a timer to each Action Thread job
M +9-5
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #57 from caulier.gil...@gmail.com ---
Maik, sure this evening I think
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #56 from Maik Qualmann ---
@Gilles, can you please create a new Windows bundle, I want to exclude the
DatesJob or not.
@Peter, as a test you can sort your albums and items by name/path instead of by
date. Does it make a difference?
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #55 from caulier.gil...@gmail.com ---
Maik,
Currently the Qt version used by digiKam through VCPKG under Windows is the
6.6.0. The last 6.6.1 is out in VCPKG. Perhaps this can fix the problem.
Another improvement can be the massive update
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #54 from Peter ---
(In reply to Peter from comment #53)
> (In reply to Peter from comment #52)
> > Created attachment 164149 [details]
> > Qt6Core.dll
>
> Here is a video of the entire start process in process explorer
>
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #53 from Peter ---
(In reply to Peter from comment #52)
> Created attachment 164149 [details]
> Qt6Core.dll
Here is a video of the entire start process in process explorer
https://youtu.be/ocgNrsmGUiw
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #52 from Peter ---
Created attachment 164149
--> https://bugs.kde.org/attachment.cgi?id=164149=edit
Qt6Core.dll
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #51 from Peter ---
I took a screenshot in process explorer while my digiKam is not responding.
digikam seems to closing Qt6Core threads. When you're done, digiKam will start
working again.
Maybe this info will help...
--
You are
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #50 from Peter ---
(In reply to caulier.gilles from comment #49)
> Hi Peter,
>
> Today i made an important change in the Windows native version based on Qt6.
> I dropped the internal legacy video player based on QtAV framework.
>
> I
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #49 from caulier.gil...@gmail.com ---
Hi Peter,
Today i made an important change in the Windows native version based on Qt6. I
dropped the internal legacy video player based on QtAV framework.
I would to know if the current 8.3.0 Windows
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #48 from Maik Qualmann ---
When I look at the DebugVew logs, it seems to be something related to the
DatesJob. There are these bug reports and slow QDateTime comparisons.
Note the post from KPhotAlbum:
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #47 from caulier.gil...@gmail.com ---
MAik,
With Qt6, under Linux, i can reproduce a time latency at startup. It's happen
when QtAV try to init the audio output on the system.
Typically, We don't needs QtAV at all with Qt6, even if
https://bugs.kde.org/show_bug.cgi?id=477853
Maik Qualmann changed:
What|Removed |Added
CC||joachim.kroe...@gmx.net
--- Comment #46 from
https://bugs.kde.org/show_bug.cgi?id=477853
caulier.gil...@gmail.com changed:
What|Removed |Added
CC||lothar-muel...@web.de
--- Comment
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #44 from Peter ---
(In reply to Maik Qualmann from comment #26)
> Please compare it again with this current version:
>
> https://files.kde.org/digikam/digiKam-8.3.0-20231205T055434-Win64.exe
>
> Maik
Hi Maik,
I downloaded
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #43 from nono...@gmail.com ---
The Configure Digikam window seems to open fine for me.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #42 from Peter ---
(In reply to nonobio from comment #41)
> Hi,
>
> I'm not sure if it is the same issue but I have a lot of time latency with
> the" Digikam not responding" message since I installed Digikam 8.3.0, not at
> startup but
https://bugs.kde.org/show_bug.cgi?id=477853
nono...@gmail.com changed:
What|Removed |Added
CC||nono...@gmail.com
--- Comment #41 from
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #40 from Peter ---
Created attachment 163935
--> https://bugs.kde.org/attachment.cgi?id=163935=edit
Versions currently available in Windows
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #39 from Peter ---
(In reply to Maik Qualmann from comment #31)
> As a note to everyone for whom our current digiKam version, created with Qt6
> and Microsoft Komplier, is too slow, here is a version that was created as
> before:
>
>
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #38 from Maik Qualmann ---
Afterwards, the application path is only in the 7th position, but before the
system directory.
https://learn.microsoft.com/en-us/windows/win32/dlls/dynamic-link-library-search-order
Maik
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #37 from caulier.gil...@gmail.com ---
By experience, the dlls search path priority under Windows is local application
path first and after system path. This allows to mix different versions of dlls
without conflict.
Gilles
--
You are
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #36 from Maik Qualmann ---
Hmm, why 2015 good question, it's the version, if I see it correctly, that also
applies to 2022.
I think that our DLLs in the digiKam path will not be used if they are already
installed in the system. So we would
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #35 from caulier.gil...@gmail.com ---
This is the list of redistributable dlls :
https://learn.microsoft.com/en-us/cpp/windows/determining-which-dlls-to-redistribute?view=msvc-170
Included in digiKam bundle are Intel 64 bits files with non
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #34 from caulier.gil...@gmail.com ---
MSVC redistributable notice :
https://learn.microsoft.com/en-us/cpp/windows/redistributing-visual-cpp-files?view=msvc-170
Gilles
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #33 from caulier.gil...@gmail.com ---
Another point about redistributable Dlls from M$ (that i never understand why
these files are not included as well in Windows update) is the performance and
architecture support:
- arm | intel
- single
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #32 from caulier.gil...@gmail.com ---
>I therefore suspect that it may be related to runtime libraries that users
>have previously installed. I therefore ask you to install/update the "Visual
>C++ Redistributable for Visual Studio 2015".
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #31 from Maik Qualmann ---
As a note to everyone for whom our current digiKam version, created with Qt6
and Microsoft Komplier, is too slow, here is a version that was created as
before:
https://bugs.kde.org/show_bug.cgi?id=477853
Maik Qualmann changed:
What|Removed |Added
CC||erik.herle+digi...@gmail.co
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #29 from Maik Qualmann ---
*** Bug 478075 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #28 from Peter ---
(In reply to Maik Qualmann from comment #26)
> Please compare it again with this current version:
>
> https://files.kde.org/digikam/digiKam-8.3.0-20231205T055434-Win64.exe
>
> Maik
Unfortunately, there is no change in
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #27 from Peter ---
> Does this version run normally again for you?
Yes! This works very well!
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #26 from Maik Qualmann ---
Please compare it again with this current version:
https://files.kde.org/digikam/digiKam-8.3.0-20231205T055434-Win64.exe
Maik
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #25 from IvorJ ---
Yes, it's fine
On Tue, 5 Dec 2023 at 08:43, Maik Qualmann wrote:
> https://bugs.kde.org/show_bug.cgi?id=477853
>
> Maik Qualmann changed:
>
>What|Removed |Added
>
>
https://bugs.kde.org/show_bug.cgi?id=477853
Maik Qualmann changed:
What|Removed |Added
CC||metzping...@gmail.com
--- Comment #24 from
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #23 from Peter ---
I don't know how important this information is...
-- The newly released 8.2.0 also contains this bug
-- Versions of 8.2.0 released at the beginning of November (weekly snapshots)
did not yet contain this bug
--
You are
https://bugs.kde.org/show_bug.cgi?id=477853
IvorJ changed:
What|Removed |Added
CC||ivorwjo...@googlemail.com
--- Comment #22 from IvorJ
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #21 from Maik Qualmann ---
Git commit 11883c4309073cd7f0236b58453b60dcc3e45dd0 by Maik Qualmann.
Committed on 03/12/2023 at 13:48.
Pushed by mqualmann into branch 'master'.
reset a commit to the refresh timers
M +8-2
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #20 from Peter ---
Created attachment 163812
--> https://bugs.kde.org/attachment.cgi?id=163812=edit
This log was created while digiKam was running when I clicked on the Configure
digiKam menu item.
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #19 from Peter ---
Created attachment 163811
--> https://bugs.kde.org/attachment.cgi?id=163811=edit
2023.12.03. DebugLog
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #18 from Peter ---
(In reply to caulier.gilles from comment #16)
> Peter,
>
> The 8.3.0 pre-release installer is updated online with the last changes from
> Mail to add more debug trace in debugview at startup.
>
> Please install file
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #17 from caulier.gil...@gmail.com ---
Maik,
For info in the "legacy" sub directory, i upload the cross-compiled version of
pre-release of digiKam, if we needs to compare with the native version:
https://files.kde.org/digikam/legacy/
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #16 from caulier.gil...@gmail.com ---
Peter,
The 8.3.0 pre-release installer is updated online with the last changes from
Mail to add more debug trace in debugview at startup.
Please install file and report: https://files.kde.org/digikam/
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #15 from Maik Qualmann ---
Git commit c4f76622403f36f0543b2d6ca7996354eb45e98a by Maik Qualmann.
Committed on 03/12/2023 at 10:29.
Pushed by mqualmann into branch 'master'.
more test debug output for ActionThreadBase
M +4-4
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #14 from caulier.gil...@gmail.com ---
But it's not a duplicate, as the origin of the time latency at startup is not
clearly identified.
As you have already write in this file, the Marble blank dialog is not the
really problem.
Gilles
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #13 from Peter ---
I thought this ticket (477853) was a duplicate, that's why I wrote that it can
be closed.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=477853
--- Comment #12 from caulier.gil...@gmail.com ---
>-- I did it. I hide geolocation view (I never use these anyway)
>-- Close digiKam
>-- Restart digiKam
>Unfortunately, it didn't solve the problem
>"The blank dialog problem from Marble is know:"
>Ok.
1 - 100 of 112 matches
Mail list logo
