Ubuntu
digikam package

digikam 1.2 crashes on kubuntu 10.04

Bug #565604 reported by gyanny
4
This bug affects 1 person
Affects Status Importance Assigned to Milestone
digiKam
Fix Released
High
digikam (Ubuntu)
Fix Released
Undecided
Alessandro Ghersi
Nominated for Lucid by Alessandro Ghersi

Bug Description

Binary package hint: digikam

gianni@Amilo-Lucid:~$ digikam
digikam(1938) Phonon::KdePlatformPlugin::createBackend: using backend: "Xine"
Time elapsed: 31 ms
Time elapsed: 16 ms
Model: Time elapsed: 95 ms
TextureColorizer: Time elapsed: 49 ms
Time elapsed: 13 ms
Time elapsed: 16 ms
Model: Time elapsed: 52 ms
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Nessun file o directory
QFileSystemWatcher: failed to add paths: /home/gianni/.config/ibus/bus
Bus::open: Can not get ibus-daemon's address.
IBusInputContext::createInputContext: no connection to ibus-daemon
digikam(1938)/digikam (core): ThumbnailLoadThread::load: No thumbnail size specified. Refusing to load thumbnail.
KCrash: Application 'digikam' crashing...
sock_file=/home/gianni/.kde/socket-Amilo-Lucid/kdeinit4__0
QSocketNotifier: Invalid socket 40 and type 'Read', disabling...

[1]+ Fermato digikam

See original description
Tags: kubuntu
Revision history for this message
In , X-wstephenson (x-wstephenson) wrote :
Download full text (5.7 KiB)

Version: (using Devel)
Installed from: Compiled sources

Crashes just after displaying the album contents on startup. 1.2.0 on KDE 4.4.2.

Backtrace follows

==2493== Thread 1:
==2493== Invalid read of size 8
==2493== at 0xA2D9401: QTimeLine::stop() (qtimeline.h:139)
==2493== by 0x6DD13B: Digikam::RatingWidget::setFadingValue(int) (ratingwidget.cpp:170)
==2493== by 0x6BB034: Digikam::ImageRatingOverlay::slotEntered(QModelIndex const&) (imageratingoverlay.cpp:126)
==2493== by 0x76255F5: Digikam::AbstractWidgetDelegateOverlay::qt_metacall(QMetaObject::Call, int, void**) (imagedelegateoverlay.moc:151)
==2493== by 0x6BB66F: Digikam::ImageRatingOverlay::qt_metacall(QMetaObject::Call, int, void**) (imageratingoverlay.moc:74)
==2493== by 0xA38D78E: QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (qobject.cpp:3293)
==2493== by 0x9581A74: QAbstractItemView::entered(QModelIndex const&) (in /usr/lib64/libQtGui.so.4.6.2)
==2493== by 0x6A851A: Digikam::ImageCategorizedView::slotDelayedEnter() (imagecategorizedview.cpp:408)
==2493== by 0x6AA28B: Digikam::ImageCategorizedView::qt_metacall(QMetaObject::Call, int, void**) (imagecategorizedview.moc:107)
==2493== by 0x692E8F: Digikam::DigikamImageView::qt_metacall(QMetaObject::Call, int, void**) (digikamimageview.moc:113)
==2493== by 0xA38D78E: QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (qobject.cpp:3293)
==2493== by 0xA38A3E2: QObject::event(QEvent*) (qobject.cpp:1212)
==2493== Address 0x8 is not stack'd, malloc'd or (recently) free'd
==2493==
KCrash: Application 'digikam' crashing...

Thread 1 (Thread 0x7f9e61f4c860 (LWP 1373)):
[KCrash Handler]
#5 d_func (this=<value optimized out>) at tools/qtimeline.h:139
#6 QTimeLine::stop (this=<value optimized out>) at tools/qtimeline.cpp:723
#7 0x00000000006dd13c in Digikam::RatingWidget::setFadingValue (this=0xe3fc30, value=255) at /usr/src/debug/digikam-1.2.0/digikam/ratingwidget.cpp:170
#8 0x00000000006bb035 in Digikam::ImageRatingOverlay::slotEntered (this=0xe3f320, index=...) at /usr/src/debug/digikam-1.2.0/digikam/imageratingoverlay.cpp:126
#9 0x00007f9e5f4a15f6 in Digikam::AbstractWidgetDelegateOverlay::qt_metacall (this=0xe3f320, _c=InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffd3407730)
    at /usr/src/debug/digikam-1.2.0/build/digikam/imagedelegateoverlay.moc:151
#10 0x00000000006bb670 in Digikam::ImageRatingOverlay::qt_metacall (this=0x0, _c=255, _id=14764688, _a=0xfffffffffff6938a) at /usr/src/debug/digikam-1.2.0/build/digikam/imageratingoverlay.moc:74
#11 0x00007f9e5c6c678f in QMetaObject::activate (sender=0xd32470, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0xfffffffffff6938a) at kernel/qobject.cpp:3293
#12 0x00007f9e5d773a75 in QAbstractItemView::entered(QModelIndex const&) () from /usr/lib64/libQtGui.so.4
#13 0x00007f9e5d777f28 in ?? () from /usr/lib64/libQtGui.so.4
#14 0x00007f9e5d77f158 in QAbstractItemView::mouseMoveEvent(QMouseEvent*) () from /usr/lib64/libQtGui.so.4
#15 0x00007f9e5d796ce1 in QListView::mouseMoveEvent(QMouseEvent*) () from /usr/lib64/libQtGui.so.4
#16 0x00007f9e5f4ac73c in KCategorizedView::mouseMove...

Read more...

Revision history for this message
In , Caulier-gilles-9 (caulier-gilles-9) wrote :

Marcel, Johannes,

Sound like a problem from model view port. Right?

Gilles Caulier

Revision history for this message
In , Johannes Wienke (languitar) wrote :

Hm I don't think so. This looks like a crash directly in the rating widget in setFadingValue. Can anything strange happen there if value is 255?

Revision history for this message
In , X-wstephenson (x-wstephenson) wrote :

Last night it just looked like the fading animation had not yet been instantiated when setFadingValue was called from that code path.

Revision history for this message
In , Kevin-kofler (kevin-kofler) wrote :

Changing the if (d->fadingValue >= 255) at digikam/ratingwidget.cpp:168 to if (d->fadingValue >= 255 && d->fadingTimeLine) should fix this crash.

Revision history for this message
In , Johannes Wienke (languitar) wrote :

*** Bug 232734 has been marked as a duplicate of this bug. ***

Revision history for this message
In , Johannes Wienke (languitar) wrote :

SVN commit 1109177 by jwienke:

Fix crash in rating widget.

Thanks for the hint.

BUG: 232628

 M +2 -2 NEWS
 M +1 -1 digikam/ratingwidget.cpp

WebSVN link: http://websvn.kde.org/?view=rev&revision=1109177

Revision history for this message
In , Julien (julien-narboux) wrote :

What is the impact of this bug ? maybe a 1.2.1 would be nice to have ? because it may take time before the new database features in 1.3.0 branch are stable.

Revision history for this message
In , U-simone (u-simone) wrote :

(In reply to comment #7)
> What is the impact of this bug ? maybe a 1.2.1 would be nice to have ? because
> it may take time before the new database features in 1.3.0 branch are stable.

I vote for a 1.2.1! Right now I can't use digikam (without downgrading, that is) and it's one of the my favourite applications - and one of the best features of kde!

Revision history for this message
In , Kevin-kofler (kevin-kofler) wrote :

Just apply this patch:
http://cvs.fedoraproject.org/viewvc/rpms/digikam/devel/digikam-1.2.0-kde232628.patch?revision=1.1&view=markup
or nag your distributor to apply it if you're using binary packages.

Revision history for this message
In , Neoclust-kde (neoclust-kde) wrote :

*** Bug 234469 has been marked as a duplicate of this bug. ***

Revision history for this message
In , Caulier-gilles-9 (caulier-gilles-9) wrote :

*** Bug 234516 has been marked as a duplicate of this bug. ***

Revision history for this message
In , Neoclust-kde (neoclust-kde) wrote :

*** Bug 234586 has been marked as a duplicate of this bug. ***

Revision history for this message
gyanny (gyanny) wrote :
Revision history for this message
Christian Mangold (neversfelde) wrote :

Thanks for reporting this bug. This is probably related to https://bugs.kde.org/show_bug.cgi?id=232628 . I still cannot reproduce, so if you have more details for me to recreate the crash please post them here.

Revision history for this message
gyanny (gyanny) wrote :

Thanks for your interest. Unfortunately, in addition to the backtrace that I attached, I can not provide other data, because the crashes occur immediately after the start without giving me time to do anything. But I feel that the problem is related to thumbsnails, because if I remove the folders and files digikam in ~ / .kde / share / apps and ~ / .kde / share / config as well as albums, digikam starts and allows me to perform all configuration and creating the albums, going to crash when I see the thumbsnails

Christian Mangold (neversfelde)
Changed in digikam (Ubuntu):
assignee: nobody → Christian Mangold (neversfelde)
Revision history for this message
Alessandro Ghersi (alessandro-ghersi) wrote :

I'm building the package with a patch for testing here:
https://edge.launchpad.net/~alessandro-ghersi/+archive/staging/+packages

Revision history for this message
gyanny (gyanny) wrote :

well, when it becomes available I will test and report back here

Revision history for this message
Alessandro Ghersi (alessandro-ghersi) wrote :

It's available now, put this in the sources.list:
deb http://ppa.launchpad.net/alessandro-ghersi/staging/ubuntu lucid main

and upgrade. Thanks

Revision history for this message
gyanny (gyanny) wrote :

So, I tried the patch proposed by Alessandro Ghersi, e... it works! digikam now returned to work perfectly.
many thanks for support. you really are a magnificent team. This was my first bug report and was fixed in a few hours. great job.
Thanks again to everyone and especially to Alessandro Ghersi for the early intervention and for always providing unparalleled support to the Italian community of kubuntu users.

gyanny (gyanny)
Changed in digikam (Ubuntu):
status: New → Fix Released
description: updated
Revision history for this message
Alessandro Ghersi (alessandro-ghersi) wrote :

Please don't change the status, it's not yet fix released ;)

Changed in digikam (Ubuntu):
status: Fix Released → New
Alessandro Ghersi (alessandro-ghersi)
Changed in digikam (Ubuntu):
assignee: Christian Mangold (neversfelde) → Alessandro Ghersi (alessandro-ghersi)
status: New → Fix Committed
tags: added: kubuntu
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package digikam - 2:1.2.0-0ubuntu2

---------------
digikam (2:1.2.0-0ubuntu2) lucid; urgency=low

  * Add kubuntu_01_fix_crash_startup_in_ratingwidget.diff (LP: #565604)
  * Add quilt to build-depends
  * Add include /usr/share/cdbs/1/rules/patchsys-quilt.mk in debian/rules
 -- Alessandro Ghersi <email address hidden> Sun, 18 Apr 2010 11:06:03 +0200

Changed in digikam (Ubuntu):
status: Fix Committed → Fix Released
Bug Watch Updater (bug-watch-updater)
Changed in digikam:
status: Unknown → Fix Released
Revision history for this message
In , der_FeniX (kofenix) wrote :

Created attachment 43277
New crash information added by DrKonqi

Crash. Just open, select an album and open preview or simply wait a few seconds.

Revision history for this message
In , Caulier-gilles-9 (caulier-gilles-9) wrote :

Fenix,

This file is fixed in current code from svn trunk (next digiKam 1.3.0)

Gilles Caulier

Revision history for this message
In , Mark Purcell (msp) wrote :

*** Bug 236930 has been marked as a duplicate of this bug. ***

Revision history for this message
In , Caulier-gilles-9 (caulier-gilles-9) wrote :

*** Bug 236989 has been marked as a duplicate of this bug. ***

Revision history for this message
In , Caulier-gilles-9 (caulier-gilles-9) wrote :

*** Bug 236621 has been marked as a duplicate of this bug. ***

Revision history for this message
In , Caulier-gilles-9 (caulier-gilles-9) wrote :

*** Bug 237161 has been marked as a duplicate of this bug. ***

Revision history for this message
In , Johannes Wienke (languitar) wrote :

*** Bug 237979 has been marked as a duplicate of this bug. ***

Revision history for this message
In , Caulier-gilles-9 (caulier-gilles-9) wrote :

*** Bug 237981 has been marked as a duplicate of this bug. ***

Revision history for this message
In , Johannes Wienke (languitar) wrote :

*** Bug 238605 has been marked as a duplicate of this bug. ***

Revision history for this message
In , Caulier-gilles-9 (caulier-gilles-9) wrote :

*** Bug 238962 has been marked as a duplicate of this bug. ***

Revision history for this message
In , Johannes Wienke (languitar) wrote :

*** Bug 240436 has been marked as a duplicate of this bug. ***

Revision history for this message
In , Johannes Wienke (languitar) wrote :

*** Bug 247413 has been marked as a duplicate of this bug. ***

Revision history for this message
In , Marcel-wiesweg (marcel-wiesweg) wrote :

*** Bug 246369 has been marked as a duplicate of this bug. ***

Revision history for this message
In , Marcel-wiesweg (marcel-wiesweg) wrote :

*** Bug 246534 has been marked as a duplicate of this bug. ***

Revision history for this message
In , Neoclust-kde (neoclust-kde) wrote :

*** Bug 246846 has been marked as a duplicate of this bug. ***

Revision history for this message
In , Neoclust-kde (neoclust-kde) wrote :

*** Bug 246899 has been marked as a duplicate of this bug. ***

Bug Watch Updater (bug-watch-updater)
Changed in digikam:
importance: Unknown → High
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.