[digikam] [Bug 459157] New: Open in a File Manager
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 Priority: NOR Component: Albums-MainView Assignee: digikam-bugs-n...@kde.org Reporter: bugzi...@kgb.ovh Target Milestone: --- SUMMARY STEPS TO REPRODUCE 0. You may have a different default file manager than Windows File Explorer. In my case it’s Directory Opus. I only use the latter because it’s the most feature‐rich one (far from the stock one). Other people use Total commander, Xplorer², Q-Dir, Files… 1. In digikam, right click on a photograph and select “Open in a File Manager”. OBSERVED RESULT Although many other software open the default explorer (whatever it is) pointing to the file, digikam assumes it has to be Windows File Explorer and nothing else. EXPECTED RESULT It should open the default file manager that you have and point to the file. In my case it should have opened Directory Opus. SOFTWARE/OS VERSIONS Windows: 7 Home ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 459160] New: Geolocation Editor maps don’t zoom enough
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: normal Priority: NOR Component: Geolocation-Osm Assignee: digikam-bugs-n...@kde.org Reporter: bugzi...@kgb.ovh Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. In digikam, select one or several photographs. 2. Use the Edit Geolocation / Geolocation Editor function. 3. Make sure you use OpenStreetMap as a map provider. OBSERVED RESULT Although OSM provides tiles up to zoom 19, digikam only gets to zoom level 10 or so, then stretches these tiles to the point where they are useless. It’s hard to map anything accurately on such low‐detail maps — many roads and map elements aren’t shown on this view. See my screen capture. Another surprise is that some areas get more detail than others (Paris but not London). And there, some tiles are outdated. EXPECTED RESULT Like other geomapping software (let’s say GeoSetter, even it’s now unmaintained), download and show OSM tiles up to zoom level 19 for an accurate geolocation. SOFTWARE/OS VERSIONS Windows: 7 Home ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 459160] Geolocation Editor maps don’t zoom enough
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.
[digikam] [Bug 459163] New: Geolocation Editor difficult to use
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: normal Priority: NOR Component: Geolocation-Workflow Assignee: digikam-bugs-n...@kde.org Reporter: bugzi...@kgb.ovh Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Try to geolocate a photograph in the Geolocation Editor. OBSERVED RESULT Totally unintuitive. There are buttons for everything but to pin your images to the map. To locate your photograph, you either have to type the coordinates on the right (then what is the map for ?) or click on the map, Copy coordinates and then… If you happen to use a different decimal separator than the dot (many countries use a comma), then you can’t even paste that on the right side! digikam is not compatible with itself! EXPECTED RESULT Like other geolocation editors, keep things simple and don’t clutter it. Who needs to calculate directions from here to there in the Geolocation editor (to give just an example)? The most important function here is to pin your photograph on the map. Look how simple it is in Google Maps, GeoSetter (unmaintained), OpenStreetMap,… Don’t abusively block pasting into the coordinates fields on the right. Let the user fix it first and if there is an error, then let the user know when they click on Apply. SOFTWARE/OS VERSIONS Windows: 7 Home ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 459163] Geolocation Editor difficult to use
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 are watching all bug changes.
[digikam] [Bug 459163] Geolocation Editor difficult to use
https://bugs.kde.org/show_bug.cgi?id=459163 maison changed: What|Removed |Added Status|RESOLVED|REPORTED Resolution|DUPLICATE |--- --- Comment #4 from maison --- (In reply to Maik Qualmann from comment #2) > Whether comma or point for coordinates is fixed in current digiKam versions, > the respectively set locale is used. Your digiKam 7.4.0 version is older. > > Maik 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. However your answer about locales seems peremptory. Copy then immediately paste coordinates doesn’ț work inside digiKam / Geolocation Editor if the separator is comma in the case I described. Any logical reason why it shouldn’t ? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 459160] Geolocation Editor maps don’t zoom enough
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 are watching all bug changes.
[digikam] [Bug 459160] Geolocation Editor maps don’t zoom enough
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 latest tile in
C:\Users\{myaccount}\AppData\Local\.marble\data\maps\earth\openstreetmap was on
2022-07-22, which is the time I updated digiKam from 7.6.0 to 7.7.0.
But there are recent files in
C:\Users\{myaccount}\AppData\Local\.marble\data\maps\earth\vectorosm that I
used recently.
--
You are receiving this mail because:
You are watching all bug changes.
[digikam] [Bug 459160] Geolocation Editor maps don’t zoom enough
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}\AppData\Local\digikam
C:\Users\{account}\AppData\Local\kxmlgui5
C:\Users\{account}\AppData\Local\digikam_systemrc
C:\Users\{account}\AppData\Local\digikamrc
Then I used the Geolocation Editor, but I get just a black grid with no map!
--
You are receiving this mail because:
You are watching all bug changes.
[digikam] [Bug 459160] Geolocation Editor maps don’t zoom enough
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.
[digikam] [Bug 459163] Geolocation Editor difficult to use
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.
[digikam] [Bug 459163] Geolocation Editor difficult to use
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.
[digikam] [Bug 459160] Geolocation Editor maps don’t zoom enough
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.
[digikam] [Bug 459163] Geolocation Editor difficult to use
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.
[digikam] [Bug 459160] Geolocation Editor maps don’t zoom enough
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.
[digikam] [Bug 459160] Geolocation Editor maps don’t zoom enough
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.
[digikam] [Bug 459160] Geolocation Editor maps don’t zoom enough
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.
[digikam] [Bug 459160] Geolocation Editor maps don’t zoom enough
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.
[digikam] [Bug 459160] Geolocation Editor maps don’t zoom enough
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 that were
in the first screen shot I showed were the ones that were downloaded before
upgrading.
If I remove the old content of that folder, as I mentioned, then I get a black
grid instead of a map.
So the problem is not the zoom, it’s that maps are not downloaded at all on
digikam ≥ 7.7.0.
--
You are receiving this mail because:
You are watching all bug changes.
[digikam] [Bug 459157] Open in a File Manager
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.
[digikam] [Bug 459157] Open in a File Manager
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.
[digikam] [Bug 470066] New: Dark themes make impossible to see if a photograph is geo‐located
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 OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Usability-Themes Assignee: digikam-bugs-n...@kde.org Reporter: bugzi...@kgb.ovh Target Milestone: --- STEPS TO REPRODUCE 1. Set one of the several dark or grey themes. 2. Look at the main interface on the thumbnails of images that have a geocoding tag globe icon. OBSERVED RESULT It’s nearly impossible to see this globe; it’s too dim. EXPECTED RESULT Like in the default white interface, make the globe visible in the right upper corner. SOFTWARE/OS VERSIONS Windows: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 470066] Dark themes make it impossible to see if a photograph is geo‐located
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 photograph is |impossible to see if a |geo‐located |photograph is geo‐located -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 470066] Dark themes make it impossible to see if a photograph is geo‐located
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.
[digikam] [Bug 470566] New: Metadata not updated
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 Severity: normal Priority: NOR Component: Metadata-Engine Assignee: digikam-bugs-n...@kde.org Reporter: bugzi...@kgb.ovh Target Milestone: --- Created attachment 159418 --> https://bugs.kde.org/attachment.cgi?id=159418&action=edit screen capture SUMMARY Difficult to update an image. STEPS TO REPRODUCE 1. Outside digiKam 8.0.0, modify some information about some images. For example, use exiftool directly to add geo‐location to a photograph. Or change the timestamp of a file (I’m not speaking about the Exif time, although the result should be the same). 2. Rescan your image (after a digiKam restart or manually refresh a folder). OBSERVED RESULT Metadata is usually not updated in digiKam. After the metadata update, I tried many things to force digiKam to update the metadata: - restart digKam to force it to update the files, - delete the files then restore them, - rescan the folder, - rename the files, - have a new identical copy in the system file manager. They all fail. In the screen capture, you can see that digiKam actually updates something, but not all. − The geo‐location appears in the Metadata pane, but the globe icon is not presented for any of these photographs. - I can’t upload these files to iNaturalist because they are “not located”. - However the Geolocation Editor can pin the photograph where it belongs. EXPECTED RESULT The metadata should be updated. SOFTWARE/OS VERSIONS Windows: 7 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 470566] Metadata not updated
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. The globe is not present, but the GPS data is somehow detected. Then the other consequences should be as in the original description. Attached the sample working image and the debug log as requested. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 470566] Metadata not updated
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.
[digikam] [Bug 470566] Metadata not updated
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.
[digikam] [Bug 470566] Metadata not updated
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.
[digikam] [Bug 470566] Metadata not updated
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.
[digikam] [Bug 470566] Metadata not updated
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.
[digikam] [Bug 470566] Metadata not updated
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 complete as possible. Both show the same problem. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 470566] Metadata not updated
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 more > note about screenshot, until before digiKam-8.0.0 digiKam would not have > accepted the GPS information without AltitudeRef. Please upload the correct > sample image. > > Maik Did you try to reproduce the external geo‐location addition and rescan? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 470566] Metadata not updated
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. Again, the last test was just a quick test and can’t draw detailed conclusions. Going back at the original example, thanks for trying, but I still think we are not on the right track yet. As I said, it’s not the specific file, it’s how digiKam 8.0.0 manages the file updates. I didn’t notice this flaw in 7.* versions. Here are two captures from my main profile and two GPS locations. They have the same data structure, but one has been updated before and the one that has been updated while being known by digiKam makes digiKam not handle its metadata correctly. The proof that it’s not the file itself is that if I start a new profile from scratch, then every file is new and then the same files are considered valid (last screen capture). -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 470566] Metadata not updated
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: You are watching all bug changes.
[digikam] [Bug 470566] Metadata not updated
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 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 470566] Metadata not updated
https://bugs.kde.org/show_bug.cgi?id=470566 maison changed: What|Removed |Added Attachment #159451|0 |1 is obsolete|| -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 470566] Metadata not updated
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 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 470566] Metadata not updated
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, therefore the same “faulty” files are not a problem at all -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 470566] Metadata not updated
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 GPSAltitude and GPSAltitudeRef if the altitude is known. > --- > > Also read this thread: > > https://exiftool.org/forum/index.php?topic=8443.0 > > Without this information it is not a valid GPS. digiKam does nothing wrong > here. As an irrelevant reply for this side subject, I update my files externally with exiftool because I geo‐locate them with a .nmea file which is not supported by digiKam (only gpx, although it shouldn’t make any difference for digiKam if it only transfers it to exiftool in the back). For someone who doesn’t know, nmea is the most complete GPS capture, therefore all the possible information is there and the relevant ones are then transferred to the photographs. OK, let’s go back to the bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 470566] Metadata not updated
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 since it presents it in the panel. But it only half updates it, because there is no globe and it confuses other functions (like update to iNaturalist), by letting them think there is no geo‐location. And the log provided didn’t seem to show where in digiKam the bug is located. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 470566] Metadata not updated
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 bug changes.
[digikam] [Bug 470566] Metadata not updated
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 > support in Windows is broken. If your image path contains characters that > are outside of the current Windows code page, problems may arise. Check this > out, please. > Otherwise we need the image with the problem and a real log (not a log from > a test collection) when updating the metadata of the corresponding image. If > not publicly possible, to my private mail. > > Maik Thanks Maik for trying to reproduce. I’m convinced it’s not a problem with the image files (they are scanned fine if they are new to a new digiKam profile) and it’s not because of Unicode characters (some of them do have Unicode and some don’t, and again, both are scanned fine if digiKam doesn’t know them in advance). The Unicode exiv2 discussion might be a different subject than this bug — to be confirmed. But because you’re asking I’m going to send you the files. BTW, I still use Windows 7 because I’ve never had the time to reinstall all my software on Windows 10. Maybe next winter. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 470566] Metadata not updated
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 from exiftool. Then I rescanned the folder in digiKam. Surprise (or not so much anymore): these jpegs are still presented at the wrong date in the Date selection tree and keep that date underneath in Digikam. So I tried the brutal method again: I created a new digiKam profile. Surprise (or not): these files now have the date they deserve in digiKam. As a side note, these files are named nothing fancy, like 24.jpg. No extra Unicode. Maybe more importantly I should add, my exiftool pre‐made commands bear the flags -overwrite_original -P , which shouldn’t be a problem for digiKam as it used to rescan the files correctly on demand in the past. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 470566] Metadata not updated
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 updates files at startup, but I also waited 3 minutes and I forced a rescan of the folder which contains the files with updated CreateDate. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 457072] Refined map feature
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 include both : bug 459163 lists what doesn’t work, whereas this one concentrates mainly on Geolocation Editor improvements. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 470566] Metadata not updated
https://bugs.kde.org/show_bug.cgi?id=470566 maison changed: What|Removed |Added Attachment #159498|0 |1 is obsolete|| -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 470566] Metadata not updated
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 bug changes.
[digikam] [Bug 459163] Geolocation Editor difficult to use
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 > > And on your last comment, I don't see any features that are useless or that > we should remove. > > Maik Thank you for clarifying some things; your screen cast does help and I understand it better. I find it’s less intuitive to copy coordinates and then paste them rather than pin the image like other software does (drag and drop is less precise). It also shows that some things evolved between v. 7.* and 8.0.0. But if one needs a video, it still means the interface is unintuitive. For example, you pasted your coordinates on the left. As I said, since the coordinate edit fields are on the right, that’s where I used to paste my data. The Paste coordinates option still doesn’t work there; it only works field by field. Interesting that you pasted your data as latitude longitude in degrees, whereas when I copy coordinates in digiKam they are formatted as 2° 47' 41,4"E, 48° 20' 40,3"N Minor annoyances: Why are two Apply buttons in addition to the Close button that will ask to apply anyway? Who needs a compass when there is no way to turn the map? Who needs the speed gauge and itinerary calculator? What’s the purpose of having two maps shown at the same time? Copy reference URL: “geo” is still broken. It feels that I’m repeating myself a lot here. I hope this answers your question on what to remove or to repair. Thanks for considering it. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 470566] Metadata not updated
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 > important in your case, however, so that a changed file is completely > rescanned. This also works with the ExifTool "-P" option, since the file > size is always changing. > > Then they probably pressed F5. And this is where many people have a > misunderstanding. The "F5" function would find new items and always > recreates all thumbnails. However, it does not update changed files. > To re-read changed files Menu::Album->Reread Metadata From Files - or - > Menu::Item->Reread Metadata From File. > > Maik Thank you Maik for your analysis. Indeed, I didn’t know about that option that is not active by default. With it, the files now have the full detail. I still think that it’s very strange that the data was correct in the metadata panel but not in the main view. Something to reconsider probably. Indeed, when I asked digiKam to refresh, I right clicked on the file folder and selected the refresh option. The nuance with the Reread option was too subtle. For clarity, maybe call that option Scan for new files? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 470566] Metadata not updated
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.
[digikam] [Bug 459163] Geolocation Editor difficult to use
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 the moment. > The context menu above the map also comes from Marble here. We disabled it a > long time ago, but users wanted us to enable it again to be able to measure > distances etc. The compass can be disabled if they don't want it, like any > other overlay item that could be enabled. The Geo:Url function works, it > copies the location to the Clipboard. This Geo:Url is understood by the > digiKam "paste" function as well as by other programs that support this > format. > > Maik Thank you Maik for the explanations. Indeed, the Geo: URL function works, although not compatible with the Windows clipboard. I’m still puzzled by the other surprises as mentioned in comment 18. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 459163] Geolocation Editor difficult to use
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 Paste button doesn’t work… You can’t pin an image, but you have to drag and drop it, which is much more imprecise… There are input fields that lead the user to think that they are interactive, but they are not… Two Apply buttons for what? Most of the buttons don’t do anything… You click on an image from the main interface and press the Change location button and most of the interface is useless because the image you preselected in the main interface is NOT preselected in the Geolocation editor… However this one is bloated with functions like itinerary or show TWO maps (seriously?), measure distances… It’s like someone copied it from a totally different project without adapting it to the new context. At least if the Geolocation editor is not repaired, then remove the functions that don’t work, starting with the Paste coordinates button, so that we don’t mislead users. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 469384] Export to iNaturalist tool do not respond.
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.
[digikam] [Bug 472529] New: File names are truncated on only one line
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 Status: REPORTED Severity: normal Priority: NOR Component: Thumbs-IconView Assignee: digikam-bugs-n...@kde.org Reporter: bugzi...@kgb.ovh Target Milestone: --- Created attachment 160464 --> https://bugs.kde.org/attachment.cgi?id=160464&action=edit File name truncated - e.g. you can’t see the subspecies SUMMARY STEPS TO REPRODUCE 1. Have file names with > 26 characters in the default thumbnail view. OBSERVED RESULT File names are truncated to one line, although there is enough space underneath for at least a line or two. Useful space is wasted. Also, there is no option to allow it. EXPECTED RESULT If there is information to show and available space, use it. SOFTWARE/OS VERSIONS Windows: 7 ADDITIONAL INFORMATION One can argue that if the thumbnails are bigger, there would be a few more letters on one line… Needless to say, this is a solution that works only on one file, therefore not a good one. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 472529] File names are truncated on only one line
https://bugs.kde.org/show_bug.cgi?id=472529 maison changed: What|Removed |Added Ever confirmed|0 |1 Resolution|INTENTIONAL |--- Status|RESOLVED|REOPENED --- Comment #2 from maison --- Mark, I have to differ: the extra tags just push the frame lower, but the same amount of space is unused. See the new screen capture. Also, the file properties doesn’t seem to have an option to show full names (or path, whatever). See the other new screen capture: it still wastes space whereas the important data is not complete. The multiple line text should exist there too. Then you will say that you can resize the properties panel for each individual file, as you browse them, but that is not a good solution as explained in the “Additional information” section. You can still not easily see more information if you want to select files from the thumbnail view. So, I’m not saying to make anything bigger; only that there is wasted space that can be used wisely with multiple lines when available. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 472529] File names are truncated on only one line
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 watching all bug changes.
[digikam] [Bug 472529] File names are truncated on only one line
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.
[digikam] [Bug 472529] File names are truncated on only one line
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 comment — see the new screen capture. Maybe you want to reconsider the situation. Also, how do you get the full name listed in the properties sidebar as you mentioned? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 470566] Metadata not updated
https://bugs.kde.org/show_bug.cgi?id=470566 maison changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #51 from maison --- We can close this bug for now, unless other people have the same needs for clarification. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 459163] Geolocation Editor difficult to use
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://files.kde.org/digikam/ > > This new bundle is based on last Qt framework 5.15.11 and KDE framework > 5.110. > > Thanks in advance > > Gilles Caulier Well, maybe a developer can take it for a future version then. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 459163] Geolocation Editor difficult to use
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 changes.
[digikam] [Bug 470066] Dark themes make it impossible to see if a photograph is geo‐located
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.
[digikam] [Bug 470066] Dark themes make it impossible to see if a photograph is geo‐located
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.
[digikam] [Bug 470066] Dark themes make it impossible to see if a photograph is geo‐located
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 bug changes.
[digikam] [Bug 470066] Dark themes make it impossible to see if a photograph is geo‐located
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.
[digikam] [Bug 469384] Export to iNaturalist tool do not respond.
https://bugs.kde.org/show_bug.cgi?id=469384 maison changed: What|Removed |Added CC||bugzi...@kgb.ovh --- Comment #2 from maison --- Compared to the upload interface of the iNaturalist website, this add‐on is unfortunately way behind. It should allow to select images for several observations. Just one, like we have now, would be acceptable if the the workflow was seamless. The initial dialogue box asks to confirm the account that you use (for each observation, as said earlier!). This is unnecessary for the vast majority users, except for the very few that use several accounts. Either remove this confirmation or have a check box to use one account only or, if possible, select your account (and remember the last one used) rather on the main upload interface, especially that it’s already reminded there. Now, if you have set an account, to make things worse, you have to click with the mouse on OK to confirm the account. If you hit the Enter key (which would be much faster), you are caught in a trap: add another account. Needless. Even if there is the initial dialogue box, the Enter key should be the default so that you quickly move to the upload window. At the very least there should be a shortcut key. If you do something else (click the Close button or even click on the × in the window bar to close it), it asks you to add an account. Why? Then on the main interface, there is enough space. Let options visible, like the possibility to add a comment, don’t hide them. Also, the cursor should be already on the required field; that is the species name. The Start updoad button is so slow (sometimes almost one minute, even with a good connection, whereas the direct upload on the iNaturalist website is instantaneous) and you can’t do anything during that time. Why so long and why are we blocked? After a while it finished uploading and the Close button silently appears. Why not just close the window since you can’t do anything else anyway, that is combine Send and Close? It would be easier to spot when it finished. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 469384] Export to iNaturalist tool do not respond.
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 because: You are watching all bug changes.
[digikam] [Bug 469384] Export to iNaturalist tool do not respond.
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 something while it’s doing something… Maybe the upload window should invite you to drag and drop other images in the mean time, otherwise most users won’t know. But it’s still one observation at a time. But honestly, after trying both the digiKam export and the iNaturalist web interface today, the latter is so simple and efficient, but I can’t say it about the former. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 459160] Geolocation Editor maps don’t zoom enough
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.
[digikam] [Bug 459160] Geolocation Editor maps don’t zoom enough
https://bugs.kde.org/show_bug.cgi?id=459160 maison changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #17 from maison --- Thanks Mark for confirming. However, I can’t find any change about this in the announcement page https://www.digikam.org/news/2022-06-26-7.7.0_release_announcement/ Also, if the system certificates are expired, then how does v. 7.6.0 still download maps correctly? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 459160] Geolocation Editor maps don’t zoom enough
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 bug changes.
[digikam] [Bug 459160] Geolocation Editor maps don’t zoom enough
https://bugs.kde.org/show_bug.cgi?id=459160 maison changed: What|Removed |Added Ever confirmed|1 |0 Status|CONFIRMED |REPORTED --- Comment #20 from maison --- The test result with Marble is : OSM maps are still lousy, but OSM vector maps load fine (although they are slow to download). -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 459160] Geolocation Editor maps don’t zoom enough
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.
[digikam] [Bug 459160] Geolocation Editor maps don’t zoom enough
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.
[digikam] [Bug 459160] Geolocation Editor maps don’t zoom enough
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.
[digikam] [Bug 459157] Open in a File Manager
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.
[digikam] [Bug 459157] Open in a File Manager
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 confusion. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 459157] Open in a File Manager
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.
[digikam] [Bug 459163] Geolocation Editor difficult to use
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.
[digikam] [Bug 459163] Geolocation Editor difficult to use
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 the map or from an image context menu. However, that one copies coordinates as longitude and latitude in degrees, minutes and seconds whereas the coordinate list on the right (the one that only accepts Paste, but not Paste coordinates) has latitude THEN longitude in degrees ONLY. So pasting coordinates to an image simply doesn’t work, whether it is because of commas or because internal incompatibility. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 459163] Geolocation Editor difficult to use
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 changes.
[digikam] [Bug 459160] Geolocation Editor maps don’t zoom enough
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.
[digikam] [Bug 506457] New: The help window blocks digikam@
https://bugs.kde.org/show_bug.cgi?id=506457 Bug ID: 506457 Summary: The help window blocks digikam@ Classification: Applications Product: digikam Version First 8.7.0 Reported In: Platform: Other OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: bugzi...@kgb.ovh Target Milestone: --- STEPS TO REPRODUCE 1. After the update to digiKam 8.7.0, at the first run, it offers to download additional features. 2. Since these features are not well explained (especially the first memory hog called “Use automatic AI tools”), I clicked on the Help button in the dialog to find out more in order to decide. 3. In a second or so, the help window goes in the background, digiKam goes in the front but it’s uselessly blocked by the unreachable open dialog that automatically opened at step 1. OBSERVED RESULT digiKam is shown on the screen, but no longer usable: clicks are transformed by Windows in warning sounds as something is wrong. EXPECTED RESULT Keep digiKam in the background, let the dialog open, let the help window open and then let the user choose what to install. SOFTWARE/OS VERSIONS Windows: 10 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 506457] The help window blocks digiKam at downloading AI models stage.
https://bugs.kde.org/show_bug.cgi?id=506457 --- Comment #2 from maison --- Resolved incredibly fast. Thank you Maik! I’m looking forward to seeing it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408641] New: Plasma crash
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 Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: weisswilly1...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.12.7) Qt Version: 5.9.5 Frameworks Version: 5.44.0 Operating System: Linux 4.15.0-51-generic x86_64 Distribution: Ubuntu 18.04.2 LTS -- Information about the crash: - What I was doing when the application crashed: -Just spending time over the internet, using Chromium Browser - Unusual behavior I noticed: Every time when the system LOG OUT and LOG BACK IN, the plasma crash. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f42dedf9800 (LWP 1579))] Thread 12 (Thread 0x7f41e7fff700 (LWP 1989)): [KCrash Handler] #6 0x7f42dc830640 in QSGSimpleTextureNode::texture() const () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7f42266e6963 in () at /usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kquickcontrolsaddons/libkquickcontrolsaddonsplugin.so #8 0x7f42d8ce96cf in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f42dc8b2a30 in QQuickWindowPrivate::renderSceneGraph(QSize const&) () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #10 0x7f42dc85dbbc in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #11 0x7f42dc862ac8 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #12 0x7f42d8adc16d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7f42d7c5d6db in start_thread (arg=0x7f41e7fff700) at pthread_create.c:463 #14 0x7f42d83d788f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 11 (Thread 0x7f42010da700 (LWP 1905)): #0 0x7f42d7c639f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x5629a4937d00) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f42d7c639f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x5629a4937cb0, cond=0x5629a4937cd8) at pthread_cond_wait.c:502 #2 0x7f42d7c639f3 in __pthread_cond_wait (cond=0x5629a4937cd8, mutex=0x5629a4937cb0) at pthread_cond_wait.c:655 #3 0x7f42d8add59b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f42dc8626a8 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7f42dc862b0a in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f42d8adc16d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f42d7c5d6db in start_thread (arg=0x7f42010da700) at pthread_create.c:463 #8 0x7f42d83d788f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 10 (Thread 0x7f4202770700 (LWP 1895)): #0 0x7f42d83d1839 in syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x7f422f56d445 in () at /usr/lib/x86_64-linux-gnu/libGLX_nvidia.so.0 #2 0x7f422f56d0d3 in () at /usr/lib/x86_64-linux-gnu/libGLX_nvidia.so.0 #3 0x7f422e8104fd in () at /usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.390.116 #4 0x7f422e7bd9cc in () at /usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.390.116 #5 0x7f422e6de97e in () at /usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.390.116 #6 0x7f422f56bdb1 in () at /usr/lib/x86_64-linux-gnu/libGLX_nvidia.so.0 #7 0x7f42c39e88f2 in () at /usr/lib/x86_64-linux-gnu/qt5/plugins/xcbglintegrations/libqxcb-glx-integration.so #8 0x7f42d954000a in QOpenGLContext::swapBuffers(QSurface*) () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #9 0x7f42dc85dc03 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #10 0x7f42dc862ac8 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #11 0x7f42d8adc16d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f42d7c5d6db in start_thread (arg=0x7f4202770700) at pthread_create.c:463 #13 0x7f42d83d788f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 9 (Thread 0x7f420ab32700 (LWP 1853)): #0 0x7f42d2f333bb in g_main_context_acquire () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f42d2f34385 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f42d2f345dc in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f42d8d1390b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f42d8cb89ea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f42d8ad722a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f420d48e747 in KCupsConn
