gmane.comp.kde.digikam.devel

[digikam] [Bug 320185] New: Compatibility issue with hierarchical tags between Digikam and WLPG (and perhaps other software).

2013-05-23T20:55:15

https://bugs.kde.org/show_bug.cgi?id=320185

            Bug ID: 320185
           Summary: Compatibility issue with hierarchical tags between
                    Digikam and WLPG (and perhaps other software).
    Classification: Unclassified
           Product: digikam
           Version: unspecified
          Platform: Ubuntu Packages
                OS: Linux
            Status: UNCONFIRMED
          Severity: wishlist
          Priority: NOR
         Component: Metadata
          Assignee: digikam-devel-RoXCvvDuEio< at >public.gmane.org
          Reporter: kavish-FeDmaE5TyfFmR6Xm/wNWPw< at >public.gmane.org

I'm using digikam 2.5.0 in Ubuntu 12.04 LTS (meanwhile changed to Kubuntu). My
wife is keeping the same photo collection on a MS Windows box in WLPG. When I
create hierarchical tags in Digikam, e.g. "people/Peter", this will show up in
WLPG as a non hierarchical tag ("Peter"). When I go the other way around and
create the tags in WLPG, everything is fine in Digikam. This forces me to do
all editing and tagging on the Windows box, although I prefer to use Digikam.

After some more investigation I found that the problem might be in the Dublin
Core xmp tags. Digikam is not saving the hierarchy in there. MS does, but that
might be a MS specific way of doing. When googling on this, I found that some
photo managers are doing the same, others with a different syntax and others
just like Digikam.

So, perhaps this is not really a "bug" in Digikam, but just the result of using
a standard (xmp) that leaves too much options for vendors to lock their users
to their products. But knowing that doesn't solve the problem.

I would like to suggest to create a solution that allows to customize the way
Digikam is using metadata tags. I realize that it wouldn't be a good idea to
just open it for free manual editing, but how about a menu that allows the user
to choose metadata compatibility with WLPG, Photo Shop or any other great
photomanager, including the default "Digikam"? And perhaps also the same choice
when exporting / importing photo's?

Reproducible: Always

Steps to Reproduce:
1. Create hierarchical tags on photos in Digikam.
2. Load the photos into WLPG and check the tags.
3. Try also to create such tags in WLPG see how that shows up in Digikam.
Actual Results:  
The best option to use both is editing all tags in WLPG only. When creating
hierarchical tags in Digikam, the hierarchy is lost when the photos are loaded
into WLPG.

Expected Results:  
Compatibility between both.

I'm not using the latest version of Digikam, but I didn't find any information
that might suggest that this problem is solved meanwhile.

[digikam] [Bug 320156] New: Settings don't have adefault button

Axel Krebs — 2013-05-23T06:57:59

https://bugs.kde.org/show_bug.cgi?id=320156

            Bug ID: 320156
           Summary: Settings don't have a default button
    Classification: Unclassified
           Product: digikam
           Version: 3.1.0
          Platform: Ubuntu Packages
                OS: Linux
            Status: UNCONFIRMED
          Severity: wishlist
          Priority: NOR
         Component: setup
          Assignee: digikam-devel-RoXCvvDuEio< at >public.gmane.org
          Reporter: axel.krebs-zqRNUXuvxA0b1SvskN2V4Q< at >public.gmane.org

When settings some features to active (or passive), it would be helpful to have
default settings within submenus of settings

In ideal case, there should be a CONFIG-file in txt-format(?), users can adjust
manually 

Reproducible: Always



Expected Results:  
I like to have settings, I would restore to some basics settings, working moste
stable and reliable.

[digikam] [Bug 320154] New: digiKam crashed at the end of the diaporama.

Peter Potrowl — 2013-05-23T04:59:54

https://bugs.kde.org/show_bug.cgi?id=320154

            Bug ID: 320154
           Summary: digiKam crashed at the end of the diaporama.
    Classification: Unclassified
           Product: digikam
           Version: 3.1.0
          Platform: Mageia RPMs
                OS: Linux
            Status: UNCONFIRMED
          Severity: crash
          Priority: NOR
         Component: general
          Assignee: digikam-devel-RoXCvvDuEio< at >public.gmane.org
          Reporter: peter017-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org

Application: digikam (3.1.0)
KDE Platform Version: 4.10.2
Qt Version: 4.8.4
Operating System: Linux 3.8.13-desktop-1.mga3 x86_64
Distribution: "Mageia 3"

[digikam] [Bug 320121] New: if running maintenance, "rebuild thumbnails", digiKam hangs endlessly

Axel Krebs — 2013-05-22T02:40:46

https://bugs.kde.org/show_bug.cgi?id=320121

            Bug ID: 320121
           Summary: if running maintenance, "rebuild thumbnails", digiKam
                    hangs endlessly
    Classification: Unclassified
           Product: digikam
           Version: 3.1.0
          Platform: Ubuntu Packages
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: Maintenance
          Assignee: digikam-devel-RoXCvvDuEio< at >public.gmane.org
          Reporter: axel.krebs-zqRNUXuvxA0b1SvskN2V4Q< at >public.gmane.org

From time to time, I do maintennce on my pics collection. 

If I run "rebuild thumbnails", digiKam hangs (more than half a day) without any
progress.

I set "skip existing pictures" (or so) to save time

Other submenus within maintenance tool seem to work properly

Reproducible: Always

Steps to Reproduce:
1. start digiKam
2. run maintenance, rebuild all thumbnails (skip checked directories or so)
3. do something nice: otherwise you'd to wait endlessly to finish the thumbnail
process.
Actual Results:  
- hangers
- waste of time, but not success
- meagre usability beacuse of missing feedback information from
sub-processes!!!

Expected Results:  
thumbnails-maintenace should rung run through reliably in background, using as
less as possible resources

Review Request 110559: Button for resetting curvein RAW import tool

Dmitry Ashkadov — 2013-05-20T15:21:13

-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/110559/
-----------------------------------------------------------

Review request for Digikam and Gilles Caulier.


Description
-------

Button for resetting curve to linear is too small, so, it's difficalt to find it (if user don't know where the button is located). This patch makes button bigger.


Diffs
-----

  utilities/imageeditor/rawimport/rawsettingsbox.cpp aa1238d 

Diff: http://git.reviewboard.kde.org/r/110559/diff/


Testing
-------


Thanks,

Dmitry Ashkadov

_______________________________________________
Digikam-devel mailing list
Digikam-devel-RoXCvvDuEio< at >public.gmane.org
https://mail.kde.org/mailman/listinfo/digikam-devel

[digikam] [Bug 320049] New: libkdcraw is crashing on decoding some sigma raw files

Manfred Usselmann — 2013-05-20T13:28:58

https://bugs.kde.org/show_bug.cgi?id=320049

            Bug ID: 320049
           Summary: libkdcraw is crashing on decoding some sigma raw files
    Classification: Unclassified
           Product: digikam
           Version: unspecified
          Platform: Ubuntu Packages
                OS: Linux
            Status: UNCONFIRMED
          Severity: crash
          Priority: NOR
         Component: libkdcraw
          Assignee: digikam-devel-RoXCvvDuEio< at >public.gmane.org
          Reporter: usselmann.m-awEjIhkY1Lo5WgrkcBd8vg< at >public.gmane.org

libkdcraw is crashing on decoding some files. At least Sigma.x3f from
Image-ExifTool-5.72 test files. I experienced this with KPhotoAlbum, but it is
not only KPA but at least dngconverter crashes as well.

Reproducible: Always

Steps to Reproduce:
1. Move Sigma.x3f from Image-ExifTool-5.72 to a directory indexed by
KPhotoAlbum
2. Start KPA
3. KPA crashes immediately
Actual Results:  
Executable: kphotoalbum PID: 26516 Signal: Aborted (6)

Application: KPhotoAlbum (kphotoalbum), signal: Aborted

Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f6bab295800 (LWP 26516))]

Thread 6 (Thread 0x7f6b93c3c700 (LWP 26519)):
#0 0x00007f6b9b7c843d in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#1 0x00007f6ba3646618 in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x00007f6ba3646cab in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x00007f6ba36471e2 in g_main_loop_run () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4 0x00007f6b9b8254a6 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#5 0x00007f6ba366a645 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#6 0x00007f6ba6cc1e9a in start_thread () from
/lib/x86_64-linux-gnu/libpthread.so.0
#7 0x00007f6ba6fcaccd in clone () from /lib/x86_64-linux-gnu/libc.so.6
#8 0x0000000000000000 in ?? ()

Thread 5 (Thread 0x7f6b9443d700 (LWP 26538)):
#0 0x00007f6ba6cc3f69 in pthread_mutex_lock () from
/lib/x86_64-linux-gnu/libpthread.so.0
#1 0x00007f6ba3683e21 in g_mutex_lock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x00007f6ba3646623 in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x00007f6ba3646cab in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4 0x00007f6ba3646ea4 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5 0x00007f6ba7c51c46 in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#6 0x00007f6ba7c222ef in
QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#7 0x00007f6ba7c22578 in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#8 0x00007f6ba7b23b40 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#9 0x00007f6ba7c029df in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#10 0x00007f6ba7b26b1c in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#11 0x00007f6ba6cc1e9a in start_thread () from
/lib/x86_64-linux-gnu/libpthread.so.0
#12 0x00007f6ba6fcaccd in clone () from /lib/x86_64-linux-gnu/libc.so.6
#13 0x0000000000000000 in ?? ()

Thread 4 (Thread 0x7f6b890ce700 (LWP 26553)):
#0 0x00007f6ba6fbd6dd in open64 () from /lib/x86_64-linux-gnu/libc.so.6
#1 0x00007f6ba7bf9805 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#2 0x00007f6ba7bf137f in QFSFileEngine::open(QFlags<QIODevice::OpenModeFlag>)
() from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#3 0x00007f6ba7baed2e in QFile::open(QFlags<QIODevice::OpenModeFlag>) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#4 0x00007f6ba89489e8 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#5 0x00007f6ba89495a0 in QImageReader::read(QImage*) () from
/usr/lib/x86_64-linux-gnu/libQtGui.so.4
#6 0x00007f6ba894976f in QImageReader::read() () from
/usr/lib/x86_64-linux-gnu/libQtGui.so.4
#7 0x00007f6ba893ea11 in QImage::load(QString const&, char const*) () from
/usr/lib/x86_64-linux-gnu/libQtGui.so.4
#8 0x00000000004ef670 in ?? ()
#9 0x00000000004efc43 in ?? ()
#10 0x00007f6ba7b26b1c in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#11 0x00007f6ba6cc1e9a in start_thread () from
/lib/x86_64-linux-gnu/libpthread.so.0
#12 0x00007f6ba6fcaccd in clone () from /lib/x86_64-linux-gnu/libc.so.6
#13 0x0000000000000000 in ?? ()

Thread 3 (Thread 0x7f6b888cd700 (LWP 26554)):
[KCrash Handler]
#5 0x00007f6ba6f0d425 in raise () from /lib/x86_64-linux-gnu/libc.so.6
#6 0x00007f6ba6f10b8b in abort () from /lib/x86_64-linux-gnu/libc.so.6
#7 0x00007f6ba6f4b39e in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#8 0x00007f6ba6f55b96 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#9 0x00007f6baa297fae in ?? () from /usr/lib/libkdcraw.so.21
#10 0x00007f6baa299a87 in ?? () from /usr/lib/libkdcraw.so.21
#11 0x00007f6baa28186d in KDcrawIface::KDcraw::loadHalfPreview(QImage&, QString
const&) () from /usr/lib/libkdcraw.so.21
#12 0x00000000004f176e in ?? ()
#13 0x00000000004f127c in ?? ()
#14 0x00000000004ef603 in ?? ()
#15 0x00000000004efc43 in ?? ()
#16 0x00007f6ba7b26b1c in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#17 0x00007f6ba6cc1e9a in start_thread () from
/lib/x86_64-linux-gnu/libpthread.so.0
#18 0x00007f6ba6fcaccd in clone () from /lib/x86_64-linux-gnu/libc.so.6
#19 0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7f6b7ffff700 (LWP 26555)):
#0 0x00007f6ba6fbd8cd in read () from /lib/x86_64-linux-gnu/libc.so.6
#1 0x00007f6ba7bf2468 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#2 0x00007f6ba7bf9eae in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#3 0x00007f6ba7baf9c6 in QFile::readData(char*, long long) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#4 0x00007f6ba7bb586d in QIODevice::read(char*, long long) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#5 0x00007f6b8b3cc4b5 in ?? () from
/usr/lib/x86_64-linux-gnu/qt4/plugins/imageformats/libqjpeg.so
#6 0x00007f6baa9e9bee in jpeg_fill_bit_buffer () from
/usr/lib/x86_64-linux-gnu/libjpeg.so.8
#7 0x00007f6baa9ea187 in ?? () from /usr/lib/x86_64-linux-gnu/libjpeg.so.8
#8 0x00007f6baa9e7459 in ?? () from /usr/lib/x86_64-linux-gnu/libjpeg.so.8
#9 0x00007f6baa9ebdc2 in ?? () from /usr/lib/x86_64-linux-gnu/libjpeg.so.8
#10 0x00007f6baa9e6490 in jpeg_read_scanlines () from
/usr/lib/x86_64-linux-gnu/libjpeg.so.8
#11 0x00007f6b8b3ccc0a in ?? () from
/usr/lib/x86_64-linux-gnu/qt4/plugins/imageformats/libqjpeg.so
#12 0x00007f6b8b3ce242 in ?? () from
/usr/lib/x86_64-linux-gnu/qt4/plugins/imageformats/libqjpeg.so
#13 0x00007f6ba894922d in QImageReader::read(QImage*) () from
/usr/lib/x86_64-linux-gnu/libQtGui.so.4
#14 0x00007f6ba894976f in QImageReader::read() () from
/usr/lib/x86_64-linux-gnu/libQtGui.so.4
#15 0x00007f6ba893ea11 in QImage::load(QString const&, char const*) () from
/usr/lib/x86_64-linux-gnu/libQtGui.so.4
#16 0x00000000004ef670 in ?? ()
#17 0x00000000004efc43 in ?? ()
#18 0x00007f6ba7b26b1c in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#19 0x00007f6ba6cc1e9a in start_thread () from
/lib/x86_64-linux-gnu/libpthread.so.0
#20 0x00007f6ba6fcaccd in clone () from /lib/x86_64-linux-gnu/libc.so.6
#21 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f6bab295800 (LWP 26516)):
#0 0x00007f6ba6fbd6dd in open64 () from /lib/x86_64-linux-gnu/libc.so.6
#1 0x00007f6ba7bf9805 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#2 0x00007f6ba7bf137f in QFSFileEngine::open(QFlags<QIODevice::OpenModeFlag>)
() from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#3 0x00007f6ba7baed2e in QFile::open(QFlags<QIODevice::OpenModeFlag>) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#4 0x00000000004f50b4 in ?? ()
#5 0x00000000004f027c in ?? ()
#6 0x00007f6ba7c384cc in QObject::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#7 0x00007f6ba8881e9c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#8 0x00007f6ba888630a in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQtGui.so.4
#9 0x00007f6ba958aad6 in KApplication::notify(QObject*, QEvent*) () from
/usr/lib/libkdeui.so.5
#10 0x00007f6ba7c2359e in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#11 0x00007f6ba7c27421 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#12 0x00007f6ba7c51a93 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#13 0x00007f6ba3646ab5 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#14 0x00007f6ba3646de8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0

#15 0x00007f6ba3646ea4 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#16 0x00007f6ba7c51c26 in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#17 0x00007f6ba8926c1e in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#18 0x00007f6ba7c278cf in
QCoreApplication::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#19 0x000000000051394e in ?? ()
#20 0x0000000000513f5f in ?? ()
#21 0x0000000000513f5f in ?? ()
#22 0x0000000000513f5f in ?? ()
#23 0x0000000000516754 in ?? ()
#24 0x0000000000510b3e in ?? ()
#25 0x000000000051120e in ?? ()
#26 0x00007f6ba7c3846e in QObject::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#27 0x00007f6ba8881e9c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#28 0x00007f6ba888630a in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQtGui.so.4
#29 0x00007f6ba958aad6 in KApplication::notify(QObject*, QEvent*) () from
/usr/lib/libkdeui.so.5
#30 0x00007f6ba7c2359e in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#31 0x00007f6ba7c27421 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#32 0x00007f6ba7c51a93 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#33 0x00007f6ba3646ab5 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#34 0x00007f6ba3646de8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#35 0x00007f6ba3646ea4 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#36 0x00007f6ba7c51c26 in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#37 0x00007f6ba8926c1e in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#38 0x00007f6ba7c222ef in
QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#39 0x00007f6ba7c22578 in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#40 0x00007f6ba7c27738 in QCoreApplication::exec() () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#41 0x000000000043b2cd in ?? ()
#42 0x00007f6ba6ef876d in __libc_start_main () from
/lib/x86_64-linux-gnu/libc.so.6
#43 0x0000000000445051 in _start ()

Expected Results:  
No crash

Application: kphotoalbum (4.4)
KDE Platform Version: 4.10.2
Qt Version: 4.8.3
Operating System: Linux 3.5.0-28-generic x86_64
Distribution: Ubuntu 12.10

[digikam] [Bug 320039] New: EXIF will be lost if user tries to convert DNG to JPEG

Dmitry — 2013-05-20T07:40:33

https://bugs.kde.org/show_bug.cgi?id=320039

            Bug ID: 320039
           Summary: EXIF will be lost if user tries to convert DNG to JPEG
    Classification: Unclassified
           Product: digikam
           Version: 3.3.0
          Platform: Other
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: Metadata
          Assignee: digikam-devel-RoXCvvDuEio< at >public.gmane.org
          Reporter: dmitry.ashkadov-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org

Hello!

If I try to edit imported DNG, import it  into image editor and then save new
version as JPEG, all metadata will be lost. But If I try to save in JPEG2000
then all metada will be preserved.

Thank you.

Reproducible: Always

Steps to Reproduce:
1. Import some DNG image containing some metadata
2. Right click on DNG image and choose "edit.." (F4)
3. Click "import" button to import image into image editor
4. Save in format JPEG or JPEG2000.
Actual Results:  
If user saves in JPEG then metadata will be lost. If user save in JPEG2000 then
the metadata is preserved.

Expected Results:  
Preserved metadata

[digikam] [Bug 320029] New: Digikam crash - Map

federbear — 2013-05-19T21:07:55

https://bugs.kde.org/show_bug.cgi?id=320029

            Bug ID: 320029
           Summary: Digikam crash - Map
    Classification: Unclassified
           Product: digikam
           Version: 3.2.0
          Platform: openSUSE RPMs
                OS: Linux
            Status: UNCONFIRMED
          Severity: crash
          Priority: NOR
         Component: general
          Assignee: digikam-devel-RoXCvvDuEio< at >public.gmane.org
          Reporter: federbear-Y8qEzhMunLyT9ig0jae3mg< at >public.gmane.org

Application: digikam (3.2.0)
KDE Platform Version: 4.10.3 "release 563"
Qt Version: 4.8.4
Operating System: Linux 3.4.33-2.24-default x86_64
Distribution: "openSUSE 12.2 (x86_64)"

[digikam] [Bug 320016] New: Full-screen options are not applied after restarting digikam

Romain Henriet — 2013-05-19T16:12:56

https://bugs.kde.org/show_bug.cgi?id=320016

            Bug ID: 320016
           Summary: Full-screen options are not applied after restarting
                    digikam
    Classification: Unclassified
           Product: digikam
           Version: 3.2.0
          Platform: openSUSE RPMs
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: Albums GUI
          Assignee: digikam-devel-RoXCvvDuEio< at >public.gmane.org
          Reporter: romain.pub-QFKgK+z4sOrR7s880joybQ< at >public.gmane.org

When opening digikam and switching to full-screen view, side bars and toolbar
are shown and thumbnail bar is hidden, despite what is checked in configuration
dialog.
If you (un)check one of the "Hide ..." box of "Full-screen options", then
full-screen view is like you want.

Reproducible: Always

Steps to Reproduce:
1. Run Digikam
2. Open Configuration dialog
3. In Album View, check "Hide toolbars" and "Hide sidebars", and uncheck "Hide
thumbbar"
4. Close dialog
5. Open full-screen view : Toolbars are hidden, sidebars are hidden, thumbbar
is shown :-)
6. Restart Digikam
7. Open full-screen view : Toolbars are shown, sidebars are shown, thumbbar is
hidden :-(
Actual Results:  
Full-screen view is different from what is checked in configuration dialog

[digikam] [Bug 319985] New: Creating a tag produces an error: puting tag to database failed (translation)

Chris — 2013-05-18T16:02:23

https://bugs.kde.org/show_bug.cgi?id=319985

            Bug ID: 319985
           Summary: Creating a tag produces an error: puting tag to
                    database failed (translation)
    Classification: Unclassified
           Product: digikam
           Version: unspecified
          Platform: Ubuntu Packages
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: Tags
          Assignee: digikam-devel-RoXCvvDuEio< at >public.gmane.org
          Reporter: i-mehl0815-zqRNUXuvxA0b1SvskN2V4Q< at >public.gmane.org

Digikam works well, database (SQLite) ist running. I create a tag and after
pressing ENTER an error appears that tells me, that digikam is not able to
write the tag to the database. I'm the owner of the database and have rw
rights. In every menu, where you can place a tag-input, same reaction.


Reproducible: Always




I'm using Mint13 Cin. and Digikam 2.5, Kernel 3.2.0-41 generic, 32bit system.

[digikam] [Bug 319948] New: Crash after savingmodified picture

Luc Sierens — 2013-05-17T14:43:55

https://bugs.kde.org/show_bug.cgi?id=319948

            Bug ID: 319948
           Summary: Crash after saving modified picture
    Classification: Unclassified
           Product: digikam
           Version: 3.0.0
          Platform: Ubuntu Packages
                OS: Linux
            Status: UNCONFIRMED
          Severity: crash
          Priority: NOR
         Component: general
          Assignee: digikam-devel-RoXCvvDuEio< at >public.gmane.org
          Reporter: luc-aabbJEYCifpBDgjK7y7TUQ< at >public.gmane.org

Application: digikam (3.0.0)
KDE Platform Version: 4.8.5 (4.8.5)
Qt Version: 4.8.1
Operating System: Linux 3.2.0-23-generic i686
Distribution: Linux Mint 13 Maya

[digikam] [Bug 319921] New: Audio files not shown in any of the views

Michael G. Hansen — 2013-05-16T20:22:14

https://bugs.kde.org/show_bug.cgi?id=319921

            Bug ID: 319921
           Summary: Audio files not shown in any of the views
    Classification: Unclassified
           Product: digikam
           Version: 3.3.0
          Platform: Other
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: digikam-devel-RoXCvvDuEio< at >public.gmane.org
          Reporter: mike-pHpZSc5jsJMb1SvskN2V4Q< at >public.gmane.org

Both digikam 3.1.0 and digikam git master do not display audio files on my
system. I tried flac, wav and mp3 files. In the album tree, however, the item
count still counts these files. See the attached screenshot showing both
digikam`s icon view and dolphin. digikam git and 3.1.0 run on different user
profiles, and the git version is compiled against exiv2 trunk.

Michael

Reproducible: Always

[digikam] [Bug 319892] New: cannot delete selected files in album view

Axel Krebs — 2013-05-16T04:28:40

https://bugs.kde.org/show_bug.cgi?id=319892

            Bug ID: 319892
           Summary: cannot delete selected files in album view
    Classification: Unclassified
           Product: digikam
           Version: 3.1.0
          Platform: Ubuntu Packages
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: Albums GUI
          Assignee: digikam-devel-RoXCvvDuEio< at >public.gmane.org
          Reporter: axel.krebs-zqRNUXuvxA0b1SvskN2V4Q< at >public.gmane.org

If right-clicking on a file in album view, one can delete files usually just by
clicking "delete"

In this case, the delete-function does not work anymore.

Reproducible: Always

Steps to Reproduce:
1. open album view
2. selects one or more pics
3. try to delete these pics
4. there occurs a long waiting period, but nothing happens

[digikam] [Bug 319882] New: Crash when stitching apanorama

Axel Krebs — 2013-05-15T19:34:04

https://bugs.kde.org/show_bug.cgi?id=319882

            Bug ID: 319882
           Summary: Crash when stitching a panorama
    Classification: Unclassified
           Product: digikam
           Version: 3.1.0
          Platform: Ubuntu Packages
                OS: Linux
            Status: UNCONFIRMED
          Severity: crash
          Priority: NOR
         Component: general
          Assignee: digikam-devel-RoXCvvDuEio< at >public.gmane.org
          Reporter: axel.krebs-zqRNUXuvxA0b1SvskN2V4Q< at >public.gmane.org

Application: digikam (3.1.0)
KDE Platform Version: 4.10.3
Qt Version: 4.8.4
Operating System: Linux 3.8.0-21-generic x86_64
Distribution: Ubuntu 13.04

[digikam] [Bug 319876] New: Panels state changed after exit from full screen mode

nucleo — 2013-05-15T17:59:58

https://bugs.kde.org/show_bug.cgi?id=319876

            Bug ID: 319876
           Summary: Panels state changed after exit from full screen mode
    Classification: Unclassified
           Product: digikam
           Version: 3.2.0
          Platform: Fedora RPMs
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: digikam-devel-RoXCvvDuEio< at >public.gmane.org
          Reporter: nucleo-rxtnV0ftBwyoClj4AeEUq9i2O/JbrIOy< at >public.gmane.org

Left and right side panels such as albums browser and file properties always
opened after exit from full screen mode even if they was closed before
switching to full screen.

Reproducible: Always

Steps to Reproduce:
1. Start digiKam.
2. Open Album.
3. Close Albums browser panel at left and File properties at right.
4. Switch to full screen mode Ctrl+Shift+F
5. Switch back with Ctrl+Shift+F
Actual Results:  
Album and file properties panel opened after exit from full screen.

Expected Results:  
Panels state after exit from fullscreen mode should be the same as before
switching to full screen.

In digiKam 3.1.0 fullscreen mode was with closed left and right side panels,
but in 3.2.0 if panels was opened before full screen they stay opened also
after Ctrl+Shift+F.

digiKam Software Collection 3.2.0 is out...

Gilles Caulier — 2013-05-15T16:07:02

Dear all digiKam fans and users!

The digiKam development team is happy to release the new digiKam Software
Collection 3.2.0. For more details, see announcement on digikam.org:

http://www.digikam.org/drupal/node/694

Release plan is listed here :

http://www.digikam.org/about/releaseplan

Best

Gilles Caulier
_______________________________________________
Digikam-devel mailing list
Digikam-devel-RoXCvvDuEio< at >public.gmane.org
https://mail.kde.org/mailman/listinfo/digikam-devel

[digikam] [Bug 319859] New: Import curves settingsin Batch Q

2013-05-15T06:45:49

https://bugs.kde.org/show_bug.cgi?id=319859

            Bug ID: 319859
           Summary: Import curves settings in Batch Q
    Classification: Unclassified
           Product: digikam
           Version: 3.0.0
          Platform: Ubuntu Packages
                OS: Linux
            Status: UNCONFIRMED
          Severity: wishlist
          Priority: NOR
         Component: Batch Queue Manager
          Assignee: digikam-devel-RoXCvvDuEio< at >public.gmane.org
          Reporter: eric.jacolin-GANU6spQydw< at >public.gmane.org

It would be very useful to be able to import a curves setting file to the
Curves Adjust step of a batch queue workflow

Reproducible: Always

[digikam] [Bug 319853] New: Untranslatable stringsin timeline tab

André Marcelo Alvarenga — 2013-05-15T02:22:28

https://bugs.kde.org/show_bug.cgi?id=319853

            Bug ID: 319853
           Summary: Untranslatable strings in timeline tab
    Classification: Unclassified
           Product: digikam
           Version: 3.1.0
          Platform: Ubuntu Packages
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: Time Line
          Assignee: digikam-devel-RoXCvvDuEio< at >public.gmane.org
          Reporter: alvarenga-RoXCvvDuEio< at >public.gmane.org

There are 3 strings untranslatable:

Start:
End:
%1 items 

See screenshot.

Reproducible: Always

Bug#708067: digikam: Include package systemsettings as rec or sug to allow changing text colour in gnome environment

Holger Burkhardt — 2013-05-12T21:06:45

Package: digikam
Version: 4:2.6.0-1+b2
Severity: wishlist

Dear Maintainer,

   * What led up to the situation?
I upgraded from squeeze to wheezy, having a gnome environment with digikam
installed.
Tooltips and the info when hovering over the preview pictures were white text
on light blue background after the upgrade, thus being unreadable. (It worked
fine before!)

   * What exactly did you do (or not do) that was effective (or
     ineffective)?
I did not find out why the text/background colour of the tooltips have changed.
I found out in exchange that one should be able to change the colours via
Settings->Design->Settings.

   * What was the outcome of this action?
Clicking on Settings->Design->Settings did not have any effect!

   * What outcome did you expect instead?
An option to change the design of digikam.

-> I found out that I had to install the package "systemsettings" to be able to
use the above mentioned menu entry of digikam. I suppose that the
systemsettings package is installed by default in a kde-environment. I would
suggest that a dependency (recommendation or suggestion) should be added to the
digikam package to allow adjusting the desing in non-kde-environments.

[digikam] [Bug 319762] New: Starting up crashes

Axel Krebs — 2013-05-13T04:18:20

https://bugs.kde.org/show_bug.cgi?id=319762

            Bug ID: 319762
           Summary: Starting up crashes
    Classification: Unclassified
           Product: digikam
           Version: 3.1.0
          Platform: Ubuntu Packages
                OS: Linux
            Status: UNCONFIRMED
          Severity: crash
          Priority: NOR
         Component: general
          Assignee: digikam-devel-RoXCvvDuEio< at >public.gmane.org
          Reporter: axel.krebs-zqRNUXuvxA0b1SvskN2V4Q< at >public.gmane.org

Application: digikam (3.1.0)
KDE Platform Version: 4.10.3
Qt Version: 4.8.4
Operating System: Linux 3.8.0-20-generic x86_64
Distribution: Ubuntu 13.04

[digikam] [Bug 319745] New: Digikam crashes after using the space bar in image editor to jump to next image

Matthias Adrian Mendler — 2013-05-12T19:53:22

https://bugs.kde.org/show_bug.cgi?id=319745

            Bug ID: 319745
           Summary: Digikam crashes after using the space bar in image
                    editor to jump to next image
    Classification: Unclassified
           Product: digikam
           Version: 3.1.0
          Platform: Ubuntu Packages
                OS: Linux
            Status: UNCONFIRMED
          Severity: crash
          Priority: NOR
         Component: general
          Assignee: digikam-devel-RoXCvvDuEio< at >public.gmane.org
          Reporter: matthias.mendler-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org

Application: digikam (3.1.0)
KDE Platform Version: 4.10.2
Qt Version: 4.8.4
Operating System: Linux 3.8.0-19-generic x86_64
Distribution: Ubuntu 13.04