batch process crashes digiKam

[Daniel Bauer-2]

Hi,

When I want to add a new batch-list ("Warteschlange") while another one is
already running, digiKam crashes completely.

Is this my machine or has anybody else experienced this, too?

What I did:

- mark all images (approx. 50) in an album, right click, add to new batch,
click "convert to png" in the batch window an start the batch process.
- go to another album, mark all images (again, approx. 50), again right click
and say "add to new batch" - digikam disappears, flup. The batch process was
killed, too...

This is reproducible here, happened every time I tried to add a new batch when
one is already running.

I guess the report that comes after the crash is not of interest, because I
have only the openSuse rpm (digiKam 1.0.0, KDE 4.3.4), no debuggging stuff...

Is this a known bug?

regards

Daniel
--
Daniel Bauer photographer Basel Barcelona
professional photography: http://www.daniel-bauer.com
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Gilles Caulier-4]

Can you provide a gdb backtrace to hack ?

Gilles Caulier

2010/1/26 Daniel Bauer <[hidden email]>:

> Hi,
>
> When I want to add a new batch-list ("Warteschlange") while another one is
> already running, digiKam crashes completely.
>
> Is this my machine or has anybody else experienced this, too?
>
> What I did:
>
> - mark all images (approx. 50) in an album, right click, add to new batch,
> click "convert to png" in the batch window an start the batch process.
> - go to another album, mark all images (again, approx. 50), again right click
> and say "add to new batch" - digikam disappears, flup. The batch process was
> killed, too...
>
> This is reproducible here, happened every time I tried to add a new batch when
> one is already running.
>
> I guess the report that comes after the crash is not of interest, because I
> have only the openSuse rpm (digiKam 1.0.0, KDE 4.3.4), no debuggging stuff...
>
> Is this a known bug?
>
> regards
>
> Daniel
> --
> Daniel Bauer photographer Basel Barcelona
> professional photography: http://www.daniel-bauer.com
> _______________________________________________
> Digikam-users mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-users
>

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Daniel Bauer-2]

On Thursday 28 January 2010 08:42:07, Gilles Caulier wrote:
> Can you provide a gdb backtrace to hack ?
>
> Gilles Caulier
>
Bonjour Gilles,

I guess I can't, unless you tell me how... :-)

I tried to start like that:
-----------
daniel@venus:~> gdb digikam > ~/Desktop/digikam.txt

warning: the debug information found in
"/usr/lib/debug//usr/bin/digikam.debug" does not match "/usr/bin/digikam" (CRC
mismatch).

warning: the debug information found in "/usr/lib/debug/usr/bin/digikam.debug"
does not match "/usr/bin/digikam" (CRC mismatch).

Missing separate debuginfo for /usr/bin/digikam
Try: zypper install -C "debuginfo(build-
id)=1bd92d17d11377c547a4a7cc50a7823adf8fdda0"
---------

so I switched to root and tried:
----------
venus:~ # zypper install -C "debuginfo(build-
id)=1bd92d17d11377c547a4a7cc50a7823adf8fdda0"
Loading repository data...
Reading installed packages...
'debuginfo(build-id)=1bd92d17d11377c547a4a7cc50a7823adf8fdda0' not found.
Resolving package dependencies...

Nothing to do.
---------

I installed all digikam rpms available at openSuse (incl. devel). Is there
another way to provide useful info? Sorry, I cannot compile digikam myself, I
don't have the time...

Daniel
--
Daniel Bauer photographer Basel Barcelona
professional photography: http://www.daniel-bauer.com
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Gilles Caulier-4]

Install debug digikam package, and follow instruction there :

http://www.digikam.org/drupal/contrib

Gilles

2010/1/28 Daniel Bauer <[hidden email]>:

> On Thursday 28 January 2010 08:42:07, Gilles Caulier wrote:
>> Can you provide a gdb backtrace to hack ?
>>
>> Gilles Caulier
>>
> Bonjour Gilles,
>
> I guess I can't, unless you tell me how... :-)
>
> I tried to start like that:
> -----------
> daniel@venus:~> gdb digikam > ~/Desktop/digikam.txt
>
> warning: the debug information found in
> "/usr/lib/debug//usr/bin/digikam.debug" does not match "/usr/bin/digikam" (CRC
> mismatch).
>
> warning: the debug information found in "/usr/lib/debug/usr/bin/digikam.debug"
> does not match "/usr/bin/digikam" (CRC mismatch).
>
> Missing separate debuginfo for /usr/bin/digikam
> Try: zypper install -C "debuginfo(build-
> id)=1bd92d17d11377c547a4a7cc50a7823adf8fdda0"
> ---------
>
> so I switched to root and tried:
> ----------
> venus:~ # zypper install -C "debuginfo(build-
> id)=1bd92d17d11377c547a4a7cc50a7823adf8fdda0"
> Loading repository data...
> Reading installed packages...
> 'debuginfo(build-id)=1bd92d17d11377c547a4a7cc50a7823adf8fdda0' not found.
> Resolving package dependencies...
>
> Nothing to do.
> ---------
>
> I installed all digikam rpms available at openSuse (incl. devel). Is there
> another way to provide useful info? Sorry, I cannot compile digikam myself, I
> don't have the time...
>
> Daniel
> --
> Daniel Bauer photographer Basel Barcelona
> professional photography: http://www.daniel-bauer.com
> _______________________________________________
> Digikam-users mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-users
>

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Daniel Bauer-2]

ok, there was a version mismatch...

this is what came after "backtrace":
----------------
(gdb) backtrace
#0  0x08201891 in setIcon (aicon=<value optimized out>, this=<value optimized
out>, column=<value optimized out>)
    at /usr/include/QtGui/qtreewidget.h:230
#1  Digikam::AssignedListViewItem::setProgressIcon (aicon=<value optimized
out>, this=<value optimized out>, column=<value optimized out>)
    at
/usr/src/debug/digikam-1.0.0/utilities/queuemanager/assignedlist.cpp:106
#2  0x08209785 in Digikam::QueueMgrWindow::slotProgressTimerDone
(this=0xc1a2fb0)
    at
/usr/src/debug/digikam-1.0.0/utilities/queuemanager/queuemgrwindow.cpp:1020
#3  0x0821379d in Digikam::QueueMgrWindow::qt_metacall (this=0xc1a2fb0,
_c=InvokeMetaMethod, _id=65, _a=0xbfffe3fc)
    at /usr/src/debug/digikam-1.0.0/build/digikam/queuemgrwindow.moc:127
#4  0xb585f864 in QMetaObject::activate (sender=0xc1fc090,
from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3113
#5  0xb5860585 in QMetaObject::activate (sender=0xc1fc090, m=0xb593c904,
local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3187
#6  0xb589b715 in QTimer::timeout (this=0xc1fc090) at .moc/release-
shared/moc_qtimer.cpp:128
#7  0xb5865196 in QTimer::timerEvent (this=0xc1fc090, e=0xbfffe884) at
kernel/qtimer.cpp:261
#8  0xb585951b in QObject::event (this=0xc1fc090, e=0xbfffe884) at
kernel/qobject.cpp:1075
#9  0xb5d4f8fc in QApplicationPrivate::notify_helper (this=0x8502d40,
receiver=0xc1fc090, e=0xbfffe884) at kernel/qapplication.cpp:4065
#10 0xb5d5734e in QApplication::notify (this=0xbfffebe8, receiver=0xc1fc090,
e=0xbfffe884) at kernel/qapplication.cpp:3605
#11 0xb67d1451 in KApplication::notify (this=0xbfffebe8, receiver=0xc1fc090,
event=0xbfffe884)
    at /usr/src/debug/kdelibs-4.3.4/kdeui/kernel/kapplication.cpp:302
#12 0xb584932e in QCoreApplication::notifyInternal (this=0xbfffebe8,
receiver=0xc1fc090, event=0xbfffe884) at kernel/qcoreapplication.cpp:610
#13 0xb5878356 in sendEvent (event=<value optimized out>, receiver=<value
optimized out>) at kernel/qcoreapplication.h:213
#14 QTimerInfoList::activateTimers (event=<value optimized out>,
receiver=<value optimized out>) at kernel/qeventdispatcher_unix.cpp:594
#15 0xb5875325 in timerSourceDispatch (source=0x8505f70) at
kernel/qeventdispatcher_glib.cpp:184
#16 idleTimerSourceDispatch (source=0x8505f70) at
kernel/qeventdispatcher_glib.cpp:231
#17 0xb3b814c2 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#18 0xb3b84d98 in ?? () from /usr/lib/libglib-2.0.so.0
#19 0xb3b84ebe in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#20 0xb5875011 in QEventDispatcherGlib::processEvents (this=0x84dd0e8,
flags=...) at kernel/qeventdispatcher_glib.cpp:407
#21 0xb5df129a in QGuiEventDispatcherGlib::processEvents (this=0x84dd0e8,
flags=...) at kernel/qguieventdispatcher_glib.cpp:202
#22 0xb584798d in QEventLoop::processEvents (this=0xbfffeb34, flags=DWARF-2
expression error: DW_OP_reg operations must be used either alone or in
conjuction with DW_OP_piece.
) at kernel/qeventloop.cpp:149
#23 0xb5847dd9 in QEventLoop::exec (this=0xbfffeb34, flags=...) at
kernel/qeventloop.cpp:201
#24 0xb584a270 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#25 0xb5d4f774 in QApplication::exec () at kernel/qapplication.cpp:3525
#26 0x083d847b in main (argc=1, argv=0xbffff044) at
/usr/src/debug/digikam-1.0.0/digikam/main.cpp:195
------------------

I've put the full gdb output here:
http://www.daniel-bauer.com/test/digikam.txt

What I did:

- as user daniel: gdb digikam >& ~/Desktop/digikam.txt
- after appearing of digikam:
  - click an album, mark all images, add to new batch, "convert from jpg to
png", start batch
  - click another album, mark all images, add to new batch - crash

If you need more info, please tell me how to get it...

have a nice day

Daniel


On Thursday 28 January 2010 10:28:09, Gilles Caulier wrote:

> Install debug digikam package, and follow instruction there :
>
> http://www.digikam.org/drupal/contrib
>
> Gilles
>
> 2010/1/28 Daniel Bauer <[hidden email]>:
> > On Thursday 28 January 2010 08:42:07, Gilles Caulier wrote:
> >> Can you provide a gdb backtrace to hack ?
> >>
> >> Gilles Caulier
> >
> > Bonjour Gilles,
> >
> > I guess I can't, unless you tell me how... :-)
> >
> > I tried to start like that:
> > -----------
> > daniel@venus:~> gdb digikam > ~/Desktop/digikam.txt
> >
> > warning: the debug information found in
> > "/usr/lib/debug//usr/bin/digikam.debug" does not match "/usr/bin/digikam"
> > (CRC mismatch).
> >
> > warning: the debug information found in
> > "/usr/lib/debug/usr/bin/digikam.debug" does not match "/usr/bin/digikam"
> > (CRC mismatch).
> >
> > Missing separate debuginfo for /usr/bin/digikam
> > Try: zypper install -C "debuginfo(build-
> > id)=1bd92d17d11377c547a4a7cc50a7823adf8fdda0"
> > ---------
> >
> > so I switched to root and tried:
> > ----------
> > venus:~ # zypper install -C "debuginfo(build-
> > id)=1bd92d17d11377c547a4a7cc50a7823adf8fdda0"
> > Loading repository data...
> > Reading installed packages...
> > 'debuginfo(build-id)=1bd92d17d11377c547a4a7cc50a7823adf8fdda0' not found.
> > Resolving package dependencies...
> >
> > Nothing to do.
> > ---------
> >
> > I installed all digikam rpms available at openSuse (incl. devel). Is
> > there another way to provide useful info? Sorry, I cannot compile digikam
> > myself, I don't have the time...
> >
> > Daniel
> > --
> > Daniel Bauer photographer Basel Barcelona
> > professional photography: http://www.daniel-bauer.com
> > _______________________________________________
> > Digikam-users mailing list
> > [hidden email]
> > https://mail.kde.org/mailman/listinfo/digikam-users
>
> _______________________________________________
> Digikam-users mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-users
>

--
Daniel Bauer photographer Basel Barcelona
professional photography: http://www.daniel-bauer.com
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Gilles Caulier-4]

No need more info.

I'm not sure, but i think it's fixed in current implementation from
svn. Anyway, i cannot reproduce the crash here.

It's will be nice to checkout code from svn trunk (future 1.1.0
release) and compile/install it yourself.

Anyway, 1.1 will be released this week end.

Gilles Caulier



2010/1/28 Daniel Bauer <[hidden email]>:

> ok, there was a version mismatch...
>
> this is what came after "backtrace":
> ----------------
> (gdb) backtrace
> #0  0x08201891 in setIcon (aicon=<value optimized out>, this=<value optimized
> out>, column=<value optimized out>)
>    at /usr/include/QtGui/qtreewidget.h:230
> #1  Digikam::AssignedListViewItem::setProgressIcon (aicon=<value optimized
> out>, this=<value optimized out>, column=<value optimized out>)
>    at
> /usr/src/debug/digikam-1.0.0/utilities/queuemanager/assignedlist.cpp:106
> #2  0x08209785 in Digikam::QueueMgrWindow::slotProgressTimerDone
> (this=0xc1a2fb0)
>    at
> /usr/src/debug/digikam-1.0.0/utilities/queuemanager/queuemgrwindow.cpp:1020
> #3  0x0821379d in Digikam::QueueMgrWindow::qt_metacall (this=0xc1a2fb0,
> _c=InvokeMetaMethod, _id=65, _a=0xbfffe3fc)
>    at /usr/src/debug/digikam-1.0.0/build/digikam/queuemgrwindow.moc:127
> #4  0xb585f864 in QMetaObject::activate (sender=0xc1fc090,
> from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3113
> #5  0xb5860585 in QMetaObject::activate (sender=0xc1fc090, m=0xb593c904,
> local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3187
> #6  0xb589b715 in QTimer::timeout (this=0xc1fc090) at .moc/release-
> shared/moc_qtimer.cpp:128
> #7  0xb5865196 in QTimer::timerEvent (this=0xc1fc090, e=0xbfffe884) at
> kernel/qtimer.cpp:261
> #8  0xb585951b in QObject::event (this=0xc1fc090, e=0xbfffe884) at
> kernel/qobject.cpp:1075
> #9  0xb5d4f8fc in QApplicationPrivate::notify_helper (this=0x8502d40,
> receiver=0xc1fc090, e=0xbfffe884) at kernel/qapplication.cpp:4065
> #10 0xb5d5734e in QApplication::notify (this=0xbfffebe8, receiver=0xc1fc090,
> e=0xbfffe884) at kernel/qapplication.cpp:3605
> #11 0xb67d1451 in KApplication::notify (this=0xbfffebe8, receiver=0xc1fc090,
> event=0xbfffe884)
>    at /usr/src/debug/kdelibs-4.3.4/kdeui/kernel/kapplication.cpp:302
> #12 0xb584932e in QCoreApplication::notifyInternal (this=0xbfffebe8,
> receiver=0xc1fc090, event=0xbfffe884) at kernel/qcoreapplication.cpp:610
> #13 0xb5878356 in sendEvent (event=<value optimized out>, receiver=<value
> optimized out>) at kernel/qcoreapplication.h:213
> #14 QTimerInfoList::activateTimers (event=<value optimized out>,
> receiver=<value optimized out>) at kernel/qeventdispatcher_unix.cpp:594
> #15 0xb5875325 in timerSourceDispatch (source=0x8505f70) at
> kernel/qeventdispatcher_glib.cpp:184
> #16 idleTimerSourceDispatch (source=0x8505f70) at
> kernel/qeventdispatcher_glib.cpp:231
> #17 0xb3b814c2 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
> #18 0xb3b84d98 in ?? () from /usr/lib/libglib-2.0.so.0
> #19 0xb3b84ebe in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
> #20 0xb5875011 in QEventDispatcherGlib::processEvents (this=0x84dd0e8,
> flags=...) at kernel/qeventdispatcher_glib.cpp:407
> #21 0xb5df129a in QGuiEventDispatcherGlib::processEvents (this=0x84dd0e8,
> flags=...) at kernel/qguieventdispatcher_glib.cpp:202
> #22 0xb584798d in QEventLoop::processEvents (this=0xbfffeb34, flags=DWARF-2
> expression error: DW_OP_reg operations must be used either alone or in
> conjuction with DW_OP_piece.
> ) at kernel/qeventloop.cpp:149
> #23 0xb5847dd9 in QEventLoop::exec (this=0xbfffeb34, flags=...) at
> kernel/qeventloop.cpp:201
> #24 0xb584a270 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
> #25 0xb5d4f774 in QApplication::exec () at kernel/qapplication.cpp:3525
> #26 0x083d847b in main (argc=1, argv=0xbffff044) at
> /usr/src/debug/digikam-1.0.0/digikam/main.cpp:195
> ------------------
>
> I've put the full gdb output here:
> http://www.daniel-bauer.com/test/digikam.txt
>
> What I did:
>
> - as user daniel: gdb digikam >& ~/Desktop/digikam.txt
> - after appearing of digikam:
>  - click an album, mark all images, add to new batch, "convert from jpg to
> png", start batch
>  - click another album, mark all images, add to new batch - crash
>
> If you need more info, please tell me how to get it...
>
> have a nice day
>
> Daniel
>
>
> On Thursday 28 January 2010 10:28:09, Gilles Caulier wrote:
>> Install debug digikam package, and follow instruction there :
>>
>> http://www.digikam.org/drupal/contrib
>>
>> Gilles
>>
>> 2010/1/28 Daniel Bauer <[hidden email]>:
>> > On Thursday 28 January 2010 08:42:07, Gilles Caulier wrote:
>> >> Can you provide a gdb backtrace to hack ?
>> >>
>> >> Gilles Caulier
>> >
>> > Bonjour Gilles,
>> >
>> > I guess I can't, unless you tell me how... :-)
>> >
>> > I tried to start like that:
>> > -----------
>> > daniel@venus:~> gdb digikam > ~/Desktop/digikam.txt
>> >
>> > warning: the debug information found in
>> > "/usr/lib/debug//usr/bin/digikam.debug" does not match "/usr/bin/digikam"
>> > (CRC mismatch).
>> >
>> > warning: the debug information found in
>> > "/usr/lib/debug/usr/bin/digikam.debug" does not match "/usr/bin/digikam"
>> > (CRC mismatch).
>> >
>> > Missing separate debuginfo for /usr/bin/digikam
>> > Try: zypper install -C "debuginfo(build-
>> > id)=1bd92d17d11377c547a4a7cc50a7823adf8fdda0"
>> > ---------
>> >
>> > so I switched to root and tried:
>> > ----------
>> > venus:~ # zypper install -C "debuginfo(build-
>> > id)=1bd92d17d11377c547a4a7cc50a7823adf8fdda0"
>> > Loading repository data...
>> > Reading installed packages...
>> > 'debuginfo(build-id)=1bd92d17d11377c547a4a7cc50a7823adf8fdda0' not found.
>> > Resolving package dependencies...
>> >
>> > Nothing to do.
>> > ---------
>> >
>> > I installed all digikam rpms available at openSuse (incl. devel). Is
>> > there another way to provide useful info? Sorry, I cannot compile digikam
>> > myself, I don't have the time...
>> >
>> > Daniel
>> > --
>> > Daniel Bauer photographer Basel Barcelona
>> > professional photography: http://www.daniel-bauer.com
>> > _______________________________________________
>> > Digikam-users mailing list
>> > [hidden email]
>> > https://mail.kde.org/mailman/listinfo/digikam-users
>>
>> _______________________________________________
>> Digikam-users mailing list
>> [hidden email]
>> https://mail.kde.org/mailman/listinfo/digikam-users
>>
>
>
> --
> Daniel Bauer photographer Basel Barcelona
> professional photography: http://www.daniel-bauer.com
> _______________________________________________
> Digikam-users mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-users
>

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users