[digikam] [Bug 451545] Strange tagging after building a new database

2022-03-16 Thread Markus Kempf
https://bugs.kde.org/show_bug.cgi?id=451545

--- Comment #7 from Markus Kempf  ---
I have recovered the "old" database and the tags looks like expected. Do you
recommend a special procedure to adjust the "old" database with the images on
the new hard disk?

Can you give some hints how to avoid such strange tagging in the future?
E.g. delete all tags in the pictures and transfer the db tags to the pictures?
(is it possible?) Or is the order in advanced metadata settings sufficient (it
seems not to be)

Best regards,

Markus

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 451545] Strange tagging after building a new database

2022-03-15 Thread Markus Kempf
https://bugs.kde.org/show_bug.cgi?id=451545

--- Comment #6 from Markus Kempf  ---
(In reply to Maik Qualmann from comment #5)
> A new database and add folders, scans all images and creates a new tag tree
> from the image metadata.
> And now the question arises, is the Xmp.digiKam.TagsList present in all
> images?

How is it checked if the tagslist is present in all images? 
> 
> If not, see what metadata in the images contain a full tag tree and set this
> to the top in the advanced metadata settings.
> 
> You could have continued to use the "old" database.
> 
> Maik

You are right - "new" doesn't mean "better" in all cases. Unfortunatly I have
to recover the backup.

Markus

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 451545] Strange tagging after building a new database

2022-03-15 Thread Markus Kempf
https://bugs.kde.org/show_bug.cgi?id=451545

--- Comment #4 from Markus Kempf  ---
(In reply to Maik Qualmann from comment #2)
> If "Ubuntu Packages" is the Snap package? Numerous problems are now known.
> Snap packages use a sandbox and are unusable for use with digiKam.
> 
> I understand correctly that they rebuilt the database from the image
> metadata?
> 
> In order for this to work without problems, the digiKam tags metadata must
> be present in all images. Reading the digiKam tags must be the top priority
> in the advanced metadata settings.
> 
> Otherwise, building up the tags tree is just a matter of luck, depending on
> which images the scanning process reads first.
> 
> Maik

I have installed the latest appimage.
I didn't rebuilt the tags directly - I created a new database, added my picture
folder and waited - slowly the thumbnails appear and the number of pictures in
the collections incremented, then I checked the tags and was surprised.

Xmp.digiKam.TagsList is the uppest line in advanced metadata settings.

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 451545] Strange tagging after building a new database

2022-03-15 Thread Markus Kempf
https://bugs.kde.org/show_bug.cgi?id=451545

--- Comment #3 from Markus Kempf  ---
(In reply to caulier.gilles from comment #1)
> which kind of database type did you use exactly ?
> 
> Gilles Caulier

I am using SQlite

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 451545] Strange tagging after building a new database

2022-03-15 Thread Markus Kempf
https://bugs.kde.org/show_bug.cgi?id=451545

Markus Kempf  changed:

   What|Removed |Added

 CC||mke...@pigfy.de

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 451545] New: Strange tagging after building a new database

2022-03-15 Thread Markus Kempf
https://bugs.kde.org/show_bug.cgi?id=451545

Bug ID: 451545
   Summary: Strange tagging after building a new database
   Product: digikam
   Version: 7.6.0
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Tags-Keywords
  Assignee: digikam-bugs-n...@kde.org
  Reporter: mke...@pigfy.de
  Target Milestone: ---

Created attachment 147518
  --> https://bugs.kde.org/attachment.cgi?id=147518=edit
the tree structure of the tags is puzzled

I upgraded my hard disk to a higher volume version. After moving the pictures
to the new disk I started a new database. I have checked the tags and the
result is strange: the tree structure is puzzled (see attachment).

The original tree is partially visible, a lot of "leaves" moved to the first
rank, some virtual subsubsubsub branches are created with one leave - really
strange.

And it is not the first time. I changed the database several month ago and I
got a similar result. 

Any hints? Correct the tag tree, delete the tags in the pictures and move the
database tags to the pictures?


Linux/KDE Plasma: ubuntu 20.04.4 LTS
GNOME 3.36.8
X11

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 382818] Rotating a picture ends in crash

2017-10-31 Thread Markus Kempf
https://bugs.kde.org/show_bug.cgi?id=382818

Markus Kempf <mke...@pigfy.de> changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #14 from Markus Kempf <mke...@pigfy.de> ---
I updated to ubuntu 17.10 and installed digikam 5.6.0 - and it works.
So the problem seems solved.

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 382818] Rotating a picture ends in crash

2017-08-09 Thread Markus Kempf
https://bugs.kde.org/show_bug.cgi?id=382818

--- Comment #13 from Markus Kempf <mke...@pigfy.de> ---
Today I installed digikam 5.4 from the ubuntu package - and this version works!
Rotating withoud crash is possible. Reinstalling digikam 5.6 - the problem is
back: rotating creates a crash

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 382818] Rotating a picture ends in crash

2017-08-01 Thread Markus Kempf
https://bugs.kde.org/show_bug.cgi?id=382818

--- Comment #12 from Markus Kempf <mke...@pigfy.de> ---
The digikam component info shows

LibJPEG: 80

ubuntu 17.04 installs 
libjpeg8
JPEG-Laufzeitbibliothek der »Independent JPEG Group« (Abhängigkeitspaket)

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 382818] Rotating a picture ends in crash

2017-08-01 Thread Markus Kempf
https://bugs.kde.org/show_bug.cgi?id=382818

--- Comment #10 from Markus Kempf <mke...@pigfy.de> ---
Created attachment 107018
  --> https://bugs.kde.org/attachment.cgi?id=107018=edit
created jpg during the crash

During rotating and crashing of pic 107016 the attached digikamtempfile is
created...

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 382818] Rotating a picture ends in crash

2017-08-01 Thread Markus Kempf
https://bugs.kde.org/show_bug.cgi?id=382818

--- Comment #9 from Markus Kempf <mke...@pigfy.de> ---
Created attachment 107016
  --> https://bugs.kde.org/attachment.cgi?id=107016=edit
rotating this picture results in a crash

Rotating this picture ends in a crash of digikam. The picture comes from
rawtherapee, is cropped by imagemagick and stored as 85% jpg via gimp. Normally
I use 100% jpg but I have to reduce the image size.
Interesting point - after the crash there is a new jpg created in the folder. I
will attach it, too.

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 382818] Rotating a picture ends in crash

2017-07-31 Thread Markus Kempf
https://bugs.kde.org/show_bug.cgi?id=382818

--- Comment #7 from Markus Kempf <mke...@pigfy.de> ---
I don't understand the last comment "relevant part for duplicate searches".

I tried to rotate pictures coming from different sources. It seems that
jpg-pictures from the camera don't crash during the roting (imported via the
import tool), but pictures exported by rawtherapee or cropped by imagemagick
show the crashes (created in the folder structure of the digikam).

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 382818] Rotating a picture ends in crash

2017-07-28 Thread Markus Kempf
https://bugs.kde.org/show_bug.cgi?id=382818

--- Comment #4 from Markus Kempf <mke...@pigfy.de> ---
Created attachment 106914
  --> https://bugs.kde.org/attachment.cgi?id=106914=edit
gdb export after crash and bt

This time after bt in gdb

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 382818] Rotating a picture ends in crash

2017-07-28 Thread Markus Kempf
https://bugs.kde.org/show_bug.cgi?id=382818

--- Comment #2 from Markus Kempf <mke...@pigfy.de> ---
Created attachment 106913
  --> https://bugs.kde.org/attachment.cgi?id=106913=edit
gdb export after crash

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 382818] New: Rotating a picture ends in crash

2017-07-27 Thread Markus Kempf
https://bugs.kde.org/show_bug.cgi?id=382818

Bug ID: 382818
   Summary: Rotating a picture ends in crash
   Product: digikam
   Version: 5.6.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: AlbumsView
  Assignee: digikam-de...@kde.org
  Reporter: mke...@pigfy.de
  Target Milestone: ---

If I rotate an image (clicking the button) it works one, two times. The next
rotation of an image ends in a sudden crash, digikam closes without any bug
description or hint. 

It is possible to rotate pictures in the ImageEditor-Tool.

I am using ubuntu 17.04 and unity and with the package source of
http://ppa.launchpad.net/philip5/extra/ubuntu

-- 
You are receiving this mail because:
You are watching all bug changes.