[digikam] [Bug 349528] New: After viewing only a handful of photos, digikam crashes

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

            Bug ID: 349528
           Summary: After viewing only a handful of photos, digikam
                    crashes
           Product: digikam
           Version: 4.2.0
          Platform: Ubuntu Packages
                OS: Linux
            Status: UNCONFIRMED
          Severity: crash
          Priority: NOR
         Component: Usability
          Assignee: [hidden email]
          Reporter: [hidden email]

To reproduce:
1. Start digikam
2. Click on a photo
3. Click next 4 or 5 times
4. => crash



Reproducible: Always

Steps to Reproduce:
To reproduce:
1. Start digikam
2. Click on a photo
3. Click next 4 or 5 times
4. => crash


Actual Results:  
Application: digiKam (digikam), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
[Current thread is 1 (Thread 0x7f2998b78a00 (LWP 6062))]

Thread 5 (Thread 0x7f297622d700 (LWP 6063)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x00007f2992dcf4db in wait (time=18446744073709551615, this=0x21f85c0) at
thread/qwaitcondition_unix.cpp:86
#2  QWaitCondition::wait (this=<optimized out>, mutex=0x21f84b8,
time=18446744073709551615) at thread/qwaitcondition_unix.cpp:158
#3  0x00000000005ca1d0 in Digikam::ScanController::run (this=0x21f8250) at
/build/buildd/digikam-2.5.0/core/digikam/database/scancontroller.cpp:647
#4  0x00007f2992dcefcb in QThreadPrivate::start (arg=0x21f8250) at
thread/qthread_unix.cpp:298
#5  0x00007f298d90ce9a in start_thread (arg=0x7f297622d700) at
pthread_create.c:308
#6  0x00007f2991ff938d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#7  0x0000000000000000 in ?? ()

Thread 4 (Thread 0x7f2975a2c700 (LWP 6064)):
#0  0x00007f2991fed9d3 in __GI___poll (fds=<optimized out>, nfds=<optimized
out>, timeout=<optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00007f298b559ff6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f298b55a124 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f2992efd426 in QEventDispatcherGlib::processEvents
(this=0x7f29680008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#4  0x00007f2992eccc82 in QEventLoop::processEvents (this=<optimized out>,
flags=...) at kernel/qeventloop.cpp:149
#5  0x00007f2992ecced7 in QEventLoop::exec (this=0x7f2975a2bb50, flags=...) at
kernel/qeventloop.cpp:204
#6  0x00007f2992dcbfa7 in QThread::exec (this=<optimized out>) at
thread/qthread.cpp:501
#7  0x00007f2992eac9ff in QInotifyFileSystemWatcherEngine::run (this=0x21e9550)
at io/qfilesystemwatcher_inotify.cpp:248
#8  0x00007f2992dcefcb in QThreadPrivate::start (arg=0x21e9550) at
thread/qthread_unix.cpp:298
#9  0x00007f298d90ce9a in start_thread (arg=0x7f2975a2c700) at
pthread_create.c:308
#10 0x00007f2991ff938d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#11 0x0000000000000000 in ?? ()

Thread 3 (Thread 0x7f2967497700 (LWP 6067)):
#0  0x00007f2991fed9d3 in __GI___poll (fds=<optimized out>, nfds=<optimized
out>, timeout=<optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00007f298b559ff6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f298b55a124 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f2992efd426 in QEventDispatcherGlib::processEvents
(this=0x7f29600008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#4  0x00007f2992eccc82 in QEventLoop::processEvents (this=<optimized out>,
flags=...) at kernel/qeventloop.cpp:149
#5  0x00007f2992ecced7 in QEventLoop::exec (this=0x7f2967496b50, flags=...) at
kernel/qeventloop.cpp:204
#6  0x00007f2992dcbfa7 in QThread::exec (this=<optimized out>) at
thread/qthread.cpp:501
#7  0x00007f2992eac9ff in QInotifyFileSystemWatcherEngine::run (this=0x2806f50)
at io/qfilesystemwatcher_inotify.cpp:248
#8  0x00007f2992dcefcb in QThreadPrivate::start (arg=0x2806f50) at
thread/qthread_unix.cpp:298
#9  0x00007f298d90ce9a in start_thread (arg=0x7f2967497700) at
pthread_create.c:308
#10 0x00007f2991ff938d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#11 0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7f292b7fe700 (LWP 6117)):
[KCrash Handler]
#6  Digikam::DImg::rotate (this=0x7791680, angle=<optimized out>) at
/build/buildd/digikam-2.5.0/core/libs/dimg/dimg.cpp:2294
#7  0x00007f2995fd6257 in Digikam::DImg::rotateAndFlip (this=0x7791680,
orientation=<optimized out>) at
/build/buildd/digikam-2.5.0/core/libs/dimg/dimg.cpp:2636
#8  0x00007f2996193d99 in Digikam::LoadSaveThread::exifRotate (image=...,
filePath=...) at
/build/buildd/digikam-2.5.0/core/libs/threadimageio/loadsavethread.cpp:276
#9  0x00007f29961aa245 in Digikam::PreviewLoadingTask::execute (this=0x7791480)
at /build/buildd/digikam-2.5.0/core/libs/threadimageio/previewtask.cpp:185
#10 0x00007f299619368e in Digikam::LoadSaveThread::run (this=0x2807cf0) at
/build/buildd/digikam-2.5.0/core/libs/threadimageio/loadsavethread.cpp:118
#11 0x00007f29961d8ece in Digikam::DynamicThread::DynamicThreadPriv::run
(this=0x2808570) at
/build/buildd/digikam-2.5.0/core/libs/threads/dynamicthread.cpp:328
#12 0x00007f2992dc24f2 in QThreadPoolThread::run (this=0x6ce9610) at
concurrent/qthreadpool.cpp:107
#13 0x00007f2992dcefcb in QThreadPrivate::start (arg=0x6ce9610) at
thread/qthread_unix.cpp:298
#14 0x00007f298d90ce9a in start_thread (arg=0x7f292b7fe700) at
pthread_create.c:308
#15 0x00007f2991ff938d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#16 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f2998b78a00 (LWP 6062)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x00007f2992dcf4db in wait (time=18446744073709551615, this=0x2565240) at
thread/qwaitcondition_unix.cpp:86
#2  QWaitCondition::wait (this=<optimized out>, mutex=0x2565148,
time=18446744073709551615) at thread/qwaitcondition_unix.cpp:158
#3  0x00007f2992dc1c7e in QThreadPoolPrivate::waitForDone (this=0x25650c0,
msecs=-1) at concurrent/qthreadpool.cpp:298
#4  0x00007f2992dc36a4 in QThreadPool::~QThreadPool (this=0x25650a0,
__in_chrg=<optimized out>) at concurrent/qthreadpool.cpp:440
#5  0x00007f2992dc36e9 in QThreadPool::~QThreadPool (this=0x25650a0,
__in_chrg=<optimized out>) at concurrent/qthreadpool.cpp:442
#6  0x00007f2992ee0935 in QObjectPrivate::deleteChildren (this=0x2564cd0) at
kernel/qobject.cpp:1908
#7  0x00007f2992ee6b9c in QObject::~QObject (this=0x2563dc0,
__in_chrg=<optimized out>) at kernel/qobject.cpp:927
#8  0x00007f29961d5ea7 in ~ThreadManagerCreator (this=0x2563dc0,
__in_chrg=<optimized out>) at
/build/buildd/digikam-2.5.0/core/libs/threads/threadmanager.cpp:236
#9  destroy () at
/build/buildd/digikam-2.5.0/core/libs/threads/threadmanager.cpp:241
#10 0x00007f2991f415b1 in __run_exit_handlers (status=1, listp=0x7f29922bd688,
run_list_atexit=true) at exit.c:78
#11 0x00007f2991f41635 in __GI_exit (status=<optimized out>) at exit.c:100
#12 0x00007f29939335e8 in qt_xio_errhandler () at
kernel/qapplication_x11.cpp:780
#13 0x00007f29945ff6b8 in KApplication::xioErrhandler (this=0x7ffed2bc82f0,
dpy=0x201e0c0) at ../../kdeui/kernel/kapplication.cpp:419
#14 0x00007f29905082be in _XIOError () from
/usr/lib/x86_64-linux-gnu/libX11.so.6
#15 0x00007f299050624b in _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
#16 0x00007f29904fbcf9 in XQueryPointer () from
/usr/lib/x86_64-linux-gnu/libX11.so.6
#17 0x00007f29939500ff in QCursor::pos () at kernel/qcursor_x11.cpp:162
#18 0x00007f29938c8c15 in QApplicationPrivate::sendSyntheticEnterLeave
(this=<optimized out>, widget=0x47d08a0) at kernel/qapplication.cpp:3234
#19 0x00007f299391ab12 in QWidget::setVisible (this=0x47d08a0,
visible=<optimized out>) at kernel/qwidget.cpp:7767
#20 0x00007f29798ac8ac in ?? () from /usr/lib/kde4/plugins/styles/oxygen.so
#21 0x00007f29798ac3ef in ?? () from /usr/lib/kde4/plugins/styles/oxygen.so
#22 0x00007f2992ee2281 in QMetaObject::activate (sender=0x47c89b0, m=<optimized
out>, local_signal_index=<optimized out>, argv=0x7ffed2bc6f90) at
kernel/qobject.cpp:3547
#23 0x00007f2993ce7cf2 in QLineEdit::textChanged (this=<optimized out>,
_t1=...) at .moc/release-shared/moc_qlineedit.cpp:264
#24 0x00007f2993ce7f99 in QLineEdit::qt_static_metacall (_o=<optimized out>,
_c=<optimized out>, _id=<optimized out>, _a=<optimized out>) at
.moc/release-shared/moc_qlineedit.cpp:140
#25 0x00007f2992ee2281 in QMetaObject::activate (sender=0x47c8db0, m=<optimized
out>, local_signal_index=<optimized out>, argv=0x7ffed2bc7100) at
kernel/qobject.cpp:3547
#26 0x00007f2993f5abb5 in QLineControl::textChanged (this=<optimized out>,
_t1=...) at .moc/release-shared/moc_qlinecontrol_p.cpp:148
#27 0x00007f2993cecbbb in QLineControl::finishChange (this=0x47c8db0,
validateFromState=-1, update=<optimized out>, edited=false) at
widgets/qlinecontrol.cpp:660
#28 0x00007f2993cece50 in QLineControl::internalSetText (this=0x47c8db0,
txt=..., pos=<optimized out>, edited=false) at widgets/qlinecontrol.cpp:692
#29 0x00007f2993caf7a1 in QComboBoxPrivate::setCurrentIndex (this=0x47c7bf0,
mi=...) at widgets/qcombobox.cpp:2041
#30 0x00007f2993caf8f7 in QComboBox::setCurrentIndex (this=<optimized out>,
index=-1) at widgets/qcombobox.cpp:2022
#31 0x00007f29961efc8f in Digikam::DZoomBar::setZoom (this=0x47c4b30,
zoom=<optimized out>, zmin=<optimized out>, zmax=<optimized out>) at
/build/buildd/digikam-2.5.0/core/libs/widgets/common/dzoombar.cpp:227
#32 0x00007f2992ee2281 in QMetaObject::activate (sender=0x43c6a90, m=<optimized
out>, local_signal_index=<optimized out>, argv=0x7ffed2bc74a0) at
kernel/qobject.cpp:3547
#33 0x00007f29962bec5b in Digikam::EditorStackView::signalZoomChanged
(this=<optimized out>, _t1=false, _t2=false, _t3=0.22649793388429751) at
/build/buildd/digikam-2.5.0/obj-x86_64-linux-gnu/core/digikam/editorstackview.moc:115
#34 0x00007f2992ee2281 in QMetaObject::activate (sender=0x43d8a70, m=<optimized
out>, local_signal_index=<optimized out>, argv=0x7ffed2bc7600) at
kernel/qobject.cpp:3547
#35 0x00007f29962b0980 in Digikam::Canvas::signalZoomChanged (this=<optimized
out>, _t1=0.22649793388429751) at
/build/buildd/digikam-2.5.0/obj-x86_64-linux-gnu/core/digikam/canvas.moc:213
#36 0x00007f29962b4fec in Digikam::Canvas::slotImageLoaded (this=0x43d8a70,
filePath=..., success=true) at
/build/buildd/digikam-2.5.0/core/utilities/imageeditor/canvas/canvas.cpp:275
#37 0x00007f2992ee2281 in QMetaObject::activate (sender=0x43665c0, m=<optimized
out>, local_signal_index=<optimized out>, argv=0x7ffed2bc77e0) at
kernel/qobject.cpp:3547
#38 0x00007f29962a4366 in Digikam::DImgInterface::signalImageLoaded
(this=<optimized out>, _t1=..., _t2=true) at
/build/buildd/digikam-2.5.0/obj-x86_64-linux-gnu/core/digikam/dimginterface.moc:177
#39 0x00007f29962a520c in Digikam::DImgInterface::slotImageLoaded
(this=0x43665c0, loadingDescription=..., img=...) at
/build/buildd/digikam-2.5.0/core/utilities/imageeditor/canvas/dimginterface.cpp:450
#40 0x00007f2992ee7446 in QObject::event (this=0x43665c0, e=<optimized out>) at
kernel/qobject.cpp:1195
#41 0x00007f29938c7894 in notify_helper (e=0x7f29180720c0, receiver=0x43665c0,
this=0x2001290) at kernel/qapplication.cpp:4559
#42 QApplicationPrivate::notify_helper (this=0x2001290, receiver=0x43665c0,
e=0x7f29180720c0) at kernel/qapplication.cpp:4531
#43 0x00007f29938cc713 in QApplication::notify (this=0x7ffed2bc82f0,
receiver=0x43665c0, e=0x7f29180720c0) at kernel/qapplication.cpp:4420
#44 0x00007f29946013f6 in KApplication::notify (this=0x7ffed2bc82f0,
receiver=0x43665c0, event=0x7f29180720c0) at
../../kdeui/kernel/kapplication.cpp:311
#45 0x00007f2992ecde9c in QCoreApplication::notifyInternal
(this=0x7ffed2bc82f0, receiver=0x43665c0, event=0x7f29180720c0) at
kernel/qcoreapplication.cpp:876
#46 0x00007f2992ed1c6a in sendEvent (event=0x7f29180720c0, receiver=0x43665c0)
at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#47 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0,
data=0x1f98070) at kernel/qcoreapplication.cpp:1500
#48 0x00007f2992efcf93 in sendPostedEvents () at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236
#49 postEventSourceDispatch (s=<optimized out>) at
kernel/qeventdispatcher_glib.cpp:279
#50 0x00007f298b559d13 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#51 0x00007f298b55a060 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#52 0x00007f298b55a124 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#53 0x00007f2992efd3bf in QEventDispatcherGlib::processEvents (this=0x1f99950,
flags=...) at kernel/qeventdispatcher_glib.cpp:424
#54 0x00007f299396fd9e in QGuiEventDispatcherGlib::processEvents
(this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#55 0x00007f2992eccc82 in QEventLoop::processEvents (this=<optimized out>,
flags=...) at kernel/qeventloop.cpp:149
#56 0x00007f2992ecced7 in QEventLoop::exec (this=0x7ffed2bc8170, flags=...) at
kernel/qeventloop.cpp:204
#57 0x00007f2992ed1f67 in QCoreApplication::exec () at
kernel/qcoreapplication.cpp:1148
#58 0x000000000048bc5d in main (argc=5, argv=<optimized out>) at
/build/buildd/digikam-2.5.0/core/digikam/main/main.cpp:232


Expected Results:  
The software should just have continued working... :-)

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

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

Gilles Caulier <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |UNMAINTAINED
            Version|4.2.0                       |unspecified
                 CC|                            |[hidden email]
             Status|UNCONFIRMED                 |RESOLVED

--- Comment #1 from Gilles Caulier <[hidden email]> ---
You use digiKam 2.5.0, which is not maintained since a while.

Please update to last 4.11.0 and try again.

Gilles Caulier

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

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

--- Comment #2 from Alain Knaff <[hidden email]> ---
Can you point me to a place where I can download a .deb of Digikam version
4.11.0 for Ubuntu?

Thanks,

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

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

--- Comment #3 from Gilles Caulier <[hidden email]> ---
https://launchpad.net/~philip5/+archive/ubuntu/extra

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

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

--- Comment #4 from Alain Knaff <[hidden email]> ---
After futzing around for 2 hours, I managed to install 4.11 , and now I can say
that it no longer crashes... but only because now it has become impossible to
move to the next image in the Image Editor.

Or is there a way to re-enable the thumbbar and/or the next image functionality
in the image editor? The thumb-bar is there, but it now only contains the image
that is being currently viewed, rather than all images in the folder.

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

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

Gilles Caulier <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
     Ever confirmed|0                           |1
         Resolution|UNMAINTAINED                |---

--- Comment #5 from Gilles Caulier <[hidden email]> ---
The editor thumbbar must work as expected. The rules still the same with album
contains.

Just start with a new account, create a new collection by importing images and
open an album in editor.

If thumbbar is populated with album contains, well i suspect a problem with
your database file from your original account.

Gilles Caulier

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

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

--- Comment #6 from Alain Knaff <[hidden email]> ---
The problem also shows up with a brand new account

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

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

Gilles Caulier <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Version|unspecified                 |4.11.0

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

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

--- Comment #7 from Gilles Caulier <[hidden email]> ---
I just tested here and thumbbar from editor can be shown from view menu and is
populated with current album items.

can you take a video of the dysfunction ?

gilles caulier

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

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

--- Comment #8 from Alain Knaff <[hidden email]> ---
For some reason, I don't have the Image Editor in the view menu. I usually open
it via its toolbar button. And when I do that, I only get a single image in the
Image Editor's thumb bar, rather than the entire album, as before.

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

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

--- Comment #9 from Alain Knaff <[hidden email]> ---
However, I noticed that when I select multiple images (using rubber band, or
shift-click), I do get them into the Image Editor's thumb bar.

Is there maybe a setting somewhere to get back the old behaviour? (get entire
album into the thumb bar)

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

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

--- Comment #10 from Gilles Caulier <[hidden email]> ---
No, there no settings for that : nothing has changed.

To open editor from album view just double clicl on icon item from an album.

To show thumbbar or not from editor, go to view menu from editor !

GIlles Caulier

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

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

--- Comment #11 from Alain Knaff <[hidden email]> ---
What is "icon item" in an album? It tried setting one of the pictures of the
album as as "Album Thumbnail", then this picture does indeed appear in the left
sidebar where usually the album's folder icon would be. But when I then
doubleclick on that icon, nothing happens...

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

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

Gilles Caulier <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
   Version Fixed In|                            |4.12.0
             Status|REOPENED                    |RESOLVED

--- Comment #12 from Gilles Caulier <[hidden email]> ---
What is "icon item" in an album ? => items from album... no more. See my video
demo :

http://youtu.be/NNQbRqcTRWM

files are open in editor with double click over icon item. Look thumbbar in
editor are populated with album contents. This is the default behavior and
nothing has changed here...

As the original problem reported here is fixed i close this file now

Gilles Caulier

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

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

--- Comment #13 from Gilles Caulier <[hidden email]> ---
Sorry wrong video demo link...

http://youtu.be/g5EqwajZ7fE

Gilles Caulier

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[bugzilla_noreply]

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

[hidden email] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|Usability                   |Portability

--
You are receiving this mail because:
You are the assignee for the bug.