https://bugs.kde.org/show_bug.cgi?id=459157
Bug ID: 459157
Summary: Open in a File Manager
Product: digikam
Version: 7.4.0
Platform: Other
OS: Microsoft Windows
Status: REPORTED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=459160
Bug ID: 459160
Summary: Geolocation Editor maps don’t zoom enough
Product: digikam
Version: 7.4.0
Platform: Other
OS: Microsoft Windows
Status: REPORTED
Severity
https://bugs.kde.org/show_bug.cgi?id=459160
--- Comment #1 from maison ---
Created attachment 152077
--> https://bugs.kde.org/attachment.cgi?id=152077&action=edit
Geolocation Editor
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=459163
Bug ID: 459163
Summary: Geolocation Editor difficult to use
Product: digikam
Version: 7.4.0
Platform: Other
OS: Microsoft Windows
Status: REPORTED
Severity: norm
https://bugs.kde.org/show_bug.cgi?id=459163
maison changed:
What|Removed |Added
Version|7.4.0 |7.8.0
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=459163
maison changed:
What|Removed |Added
Status|RESOLVED|REPORTED
Resolution|DUPLICATE
https://bugs.kde.org/show_bug.cgi?id=459160
maison changed:
What|Removed |Added
Version|7.4.0 |7.8.0
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=459160
--- Comment #3 from maison ---
Sorry for the confusion about the version (I’ve just updated LibreOffice and
had that in mind). I use the latest digiKam 7.8.0.
OSM is my main map provider.
Anyway, I looked into the computer cache and noticed that the
https://bugs.kde.org/show_bug.cgi?id=459160
--- Comment #4 from maison ---
I removed all the configuration of digiKam to start with a new profile, namely:
C:\Users\{account}\AppData\Roaming\digikam
C:\Users\{account}\AppData\Local\.marble
C:\Users\{account}\AppData\Local\cache
C:\Users\{account
https://bugs.kde.org/show_bug.cgi?id=459160
--- Comment #5 from maison ---
I downgraded to digiKam 7.6.0 and surprise, maps are shown correctly to the
most detailed zoom!
This proves a regression in 7.7.0.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=459163
--- Comment #5 from maison ---
It looks like every time I update the digiKam, I get a warning (see
screenshot), even though I didn’t change anything about the computer locale.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=459163
--- Comment #6 from maison ---
Created attachment 152160
--> https://bugs.kde.org/attachment.cgi?id=152160&action=edit
warning on version update
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=459160
--- Comment #6 from maison ---
Indeed, I tried also 7.7.0, but with no success.
Then I reverted to 7.6.0 and the geolocation works.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=459163
--- Comment #7 from maison ---
After I downgraded to 7.6.0, I can move the pin on the map again.
Maybe this bug is related to bug 459160.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=459160
--- Comment #8 from maison ---
OK, in your case it works and in my case it doesn’t. How are we going to make
progress in debugging?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=459160
--- Comment #10 from maison ---
No special configuration, just Windows 7 home 64 bits.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=459160
--- Comment #11 from maison ---
Windows Defender by default.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=459160
--- Comment #12 from maison ---
Any news on your test ?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=459160
--- Comment #14 from maison ---
Then wow can we log and debug this?
Recap: when I checked the tiles in
C:\Users\{myaccount}\AppData\Local\.marble\data\maps\earth\openstreetmap, it
appears that digiKam 7.8.0 or 7.7.0 don’t download any map! The ones
https://bugs.kde.org/show_bug.cgi?id=459157
--- Comment #10 from maison ---
I can confirm that I tested dK 8.0.0 with Directory Opus and now it works.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=459157
--- Comment #11 from maison ---
Thank you Maik for providing a good solution.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=470066
Bug ID: 470066
Summary: Dark themes make impossible to see if a photograph is
geo‐located
Classification: Applications
Product: digikam
Version: 8.0.0
Platform: Other
https://bugs.kde.org/show_bug.cgi?id=470066
maison changed:
What|Removed |Added
Summary|Dark themes make impossible |Dark themes make it
|to see if a
https://bugs.kde.org/show_bug.cgi?id=470066
--- Comment #8 from maison ---
Thanks Gilles! This is the quickest fix I’ve ever seen on the bug reports I
submitted for any software.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=470566
Bug ID: 470566
Summary: Metadata not updated
Classification: Applications
Product: digikam
Version: 8.0.0
Platform: Other
OS: Microsoft Windows
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=470566
--- Comment #3 from maison ---
So, I started a new digikam profile and a test folder with one geo‐located (see
the globe for that one) and one not. I worked on a copy of the latter, added
geo‐location externally with exiftool, then rescanned the folder
https://bugs.kde.org/show_bug.cgi?id=470566
--- Comment #4 from maison ---
Created attachment 159439
--> https://bugs.kde.org/attachment.cgi?id=159439&action=edit
Debug log
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=470566
--- Comment #5 from maison ---
Created attachment 159440
--> https://bugs.kde.org/attachment.cgi?id=159440&action=edit
Sample image not geo‐located
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=470566
--- Comment #6 from maison ---
Created attachment 159441
--> https://bugs.kde.org/attachment.cgi?id=159441&action=edit
relevant screen capture
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=470566
--- Comment #8 from maison ---
That’s what I said I’ve done. Feel free to add GPS data with exiftool and
rescan it.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=470566
--- Comment #10 from maison ---
No, as I said, I modified the copy myself, so if you want to retest the new
metadata you have to work from the original again.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=470566
--- Comment #11 from maison ---
Maybe the log shows no problem, but the screen shots each show the same
problem, including the original one with altitude.
The last test was a quick test with dummy GPS data, but the original screen
capture is as
https://bugs.kde.org/show_bug.cgi?id=470566
--- Comment #12 from maison ---
(In reply to Maik Qualmann from comment #9)
> I suspect you uploaded the wrong image, in your log and screenshot the image
> has the addition "Copie". By the way, the log shows no problems. One m
https://bugs.kde.org/show_bug.cgi?id=470566
--- Comment #16 from maison ---
(In reply to Maik Qualmann from comment #15)
> Why no GPS icon is displayed in your first screenshot because it contains
> Ref values cannot be judged without the sample image.
>
> Maik
Thanks for checking
https://bugs.kde.org/show_bug.cgi?id=470566
--- Comment #17 from maison ---
Created attachment 159450
--> https://bugs.kde.org/attachment.cgi?id=159450&action=edit
Screen capture with main software profile, a file that has been accepted
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=470566
--- Comment #18 from maison ---
Created attachment 159451
--> https://bugs.kde.org/attachment.cgi?id=159451&action=edit
Screen capture with main software profile, a file that digiKam doesn’t update
because it’s been updated externally
--
https://bugs.kde.org/show_bug.cgi?id=470566
maison changed:
What|Removed |Added
Attachment #159451|0 |1
is obsolete
https://bugs.kde.org/show_bug.cgi?id=470566
--- Comment #19 from maison ---
Created attachment 159452
--> https://bugs.kde.org/attachment.cgi?id=159452&action=edit
Screen capture with main software profile, a file that digiKam doesn’t update
because it’s been updated externally
--
https://bugs.kde.org/show_bug.cgi?id=470566
--- Comment #20 from maison ---
Created attachment 159454
--> https://bugs.kde.org/attachment.cgi?id=159454&action=edit
Screen capture with a new digikam profile, therefore every file is new,
therefore file updates haven’t been performed, th
https://bugs.kde.org/show_bug.cgi?id=470566
--- Comment #21 from maison ---
(In reply to Maik Qualmann from comment #14)
> When adding GPS information to an image, it is important to set all of the
> following tags: GPSLatitude, GPSLatitudeRef, GPSLongitude, GPSLongitudeRef,
> and GP
https://bugs.kde.org/show_bug.cgi?id=470566
--- Comment #23 from maison ---
Yes we are coming back to the same report: remember I used many ways to force
digiKam to update its data (probably all the possible imaginable ways).
Remember also that it did read the metadata after the external update
https://bugs.kde.org/show_bug.cgi?id=470566
--- Comment #25 from maison ---
No, I don’t use extra metadata files. Most of the photographs are JPEG,
therefore there is no need for xmp files since metadata can stay in the very
file.
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=470566
--- Comment #38 from maison ---
(In reply to Maik Qualmann from comment #26)
> So, after various tests on Windows, I can't reproduce the problem. There is
> one more thing, since the last versions of Exiv2 (also 0.27.5) the Unicode
> supp
https://bugs.kde.org/show_bug.cgi?id=470566
--- Comment #43 from maison ---
This bug is not only about geo‐location.
I’ve just discovered a few files that happened to have no CreateDate field
(which forced digiKam to use the DateTimeCreated field). I updated them through
the -csv=csv file option
https://bugs.kde.org/show_bug.cgi?id=470566
--- Comment #44 from maison ---
Created attachment 159498
--> https://bugs.kde.org/attachment.cgi?id=159498&action=edit
Log for comment 43
Here is the log for the last updated files. I opened the main digiKam profile
which automatically
https://bugs.kde.org/show_bug.cgi?id=457072
--- Comment #14 from maison ---
Any news for this bug or bug 459163, that have been open for many months?
There are many things in these bug reports. I don’t think this is a duplicate
of bug 459163, but they are rather complementary. Make sure you
https://bugs.kde.org/show_bug.cgi?id=470566
maison changed:
What|Removed |Added
Attachment #159498|0 |1
is obsolete
https://bugs.kde.org/show_bug.cgi?id=470566
--- Comment #46 from maison ---
Sorry, I forgot to set the option in the main profile (too much profile
fiddling). I sent you the new full debug log privately. I hope this finally
helps.
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=459163
--- Comment #18 from maison ---
(In reply to Maik Qualmann from comment #17)
> Here is a screencast showing how to paste coordinates.
>
> https://drive.google.com/file/d/1neXbiHV6anwPuka5sKTGNWxbDhRsWxE6/
> view?usp=sharing
>
>
https://bugs.kde.org/show_bug.cgi?id=470566
--- Comment #48 from maison ---
(In reply to Maik Qualmann from comment #47)
> Your log doesn't show any errors. However, it seems that you have not
> activated the metadata option "Rescan file when files are modified". This is
>
https://bugs.kde.org/show_bug.cgi?id=470566
--- Comment #49 from maison ---
Also as I said, I don’t think I encountered the metadata not refreshing in
digikam 7, so it might be something new in v. 8.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=459163
--- Comment #20 from maison ---
(In reply to Maik Qualmann from comment #19)
> Well, the actual map view comes from the program Marble, which is quite well
> known in the Linux world. Unfortunately, the development is somewhat dormant
> at t
https://bugs.kde.org/show_bug.cgi?id=459163
--- Comment #16 from maison ---
(In reply to caulier.gilles from comment #15)
> What's the status of this file ? To be closed as intentional ?
No. It’s hard to find such a confusing interface elsewhere. You can Copy
coordinates but the Past
https://bugs.kde.org/show_bug.cgi?id=469384
--- Comment #10 from maison ---
For now, I count on Patrick to check.
I haven’t migrated to Windows 10 yet, so I can’t verify.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=472529
Bug ID: 472529
Summary: File names are truncated on only one line
Classification: Applications
Product: digikam
Version: 8.1.0
Platform: Other
OS: Microsoft Windows
St
https://bugs.kde.org/show_bug.cgi?id=472529
maison changed:
What|Removed |Added
Ever confirmed|0 |1
Resolution|INTENTIONAL
https://bugs.kde.org/show_bug.cgi?id=472529
--- Comment #3 from maison ---
Created attachment 160465
--> https://bugs.kde.org/attachment.cgi?id=160465&action=edit
space is not really reserved for other tags; space is still squandered
--
You are receiving this mail because:
You are w
https://bugs.kde.org/show_bug.cgi?id=472529
--- Comment #4 from maison ---
Created attachment 160466
--> https://bugs.kde.org/attachment.cgi?id=160466&action=edit
the properties panel has the same design flaw
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=472529
--- Comment #7 from maison ---
Created attachment 160467
--> https://bugs.kde.org/attachment.cgi?id=160467&action=edit
example with title and comment
Thanks, I checked that again and there is still a lot of unused space, even
with title and
https://bugs.kde.org/show_bug.cgi?id=470566
maison changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=459163
--- Comment #22 from maison ---
(In reply to caulier.gilles from comment #21)
> @maison,
>
> This problem still reproducible with the new digiKam 8.2.0 pre-release
> Windows
> installer available at usual place:
>
> https://
https://bugs.kde.org/show_bug.cgi?id=459163
--- Comment #24 from maison ---
Then if the QT and KDE frameworks are updated but not Marble, will this change
anything in the Geolocation editor? If no, then we can leave the bug open.
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=470066
--- Comment #9 from maison ---
Created attachment 160227
--> https://bugs.kde.org/attachment.cgi?id=160227&action=edit
default
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=470066
--- Comment #10 from maison ---
Created attachment 160228
--> https://bugs.kde.org/attachment.cgi?id=160228&action=edit
black body
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=470066
--- Comment #11 from maison ---
Unfortunately this bug is still not resolved in 8.1.0.
Compare the default theme with some dark ones. Most of the dark ones still have
unnoticeable icons.
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=470066
--- Comment #13 from maison ---
Indeed, thanks Mark for reminding me what the dialogue box was indicating.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=469384
maison changed:
What|Removed |Added
CC||bugzi...@kgb.ovh
--- Comment #2 from maison
https://bugs.kde.org/show_bug.cgi?id=469384
--- Comment #4 from maison ---
Thanks Gilles for the explanation. It might be useful for Linux users.
In my case, the upload delay is with Windows.
And I suppose that all the other quirks I described are OS‐independent.
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=469384
--- Comment #6 from maison ---
Indeed, that helps to do things faster. This is totally unintuitive because the
export window takes the front of the screen and if you click in the main
digiKam window, you lose the upload window. At least you can do
https://bugs.kde.org/show_bug.cgi?id=459160
--- Comment #15 from maison ---
?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=459160
maison changed:
What|Removed |Added
Status|REPORTED|CONFIRMED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=459160
--- Comment #18 from maison ---
Also, only digiKam seems to have this problem. Other software, including
Firefox, JOSM, GeoSetter, Mobile Atlas Creator… have no problem downloading
maps.
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=459160
maison changed:
What|Removed |Added
Ever confirmed|1 |0
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=459160
--- Comment #21 from maison ---
Created attachment 153187
--> https://bugs.kde.org/attachment.cgi?id=153187&action=edit
Marble OSM
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=459160
--- Comment #22 from maison ---
Created attachment 153188
--> https://bugs.kde.org/attachment.cgi?id=153188&action=edit
Marble vector OSM
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=459160
--- Comment #25 from maison ---
Thanks Mark. Let’s hope this tracks down the problem and will allow a solution
for 7.9.0
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=459157
--- Comment #1 from maison ---
Any news?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=459157
--- Comment #4 from maison ---
Thanks Maik.
Let me know if I can help with the test of other file managers.
At the bare minimum, the right click menu should be renamed Open in Windows
File Explorer (for the Windows version of course), to avoid
https://bugs.kde.org/show_bug.cgi?id=459157
--- Comment #8 from maison ---
Good news, thanks Maik!
I hope it’s more general so that it’s applicable to whatever file manager the
user has.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=459163
--- Comment #9 from maison ---
Hi. Do we have any news for the GPS location format not being compatible within
digiKam?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=459163
--- Comment #11 from maison ---
Mark, I’m not sure what Paste coordinates function you mean. Drag and drop a
position from the map doesn’t work because it drags the map instead.
Anyway, as I mentioned, there is a function to Copy coordinates, both from
https://bugs.kde.org/show_bug.cgi?id=459163
--- Comment #13 from maison ---
Or rather we are not speaking about the same thing. The panel on the RIGHT is
the problem, not the panel at the bottom. The one that has edit fields.
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=459160
--- Comment #41 from maison ---
Great news: I can confirm this problem is solved in 7.9.0. Thank you!
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=408641
Bug ID: 408641
Summary: Plasma crash
Product: plasmashell
Version: 5.12.7
Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severi
84 matches
Mail list logo
