Summary: | digikam crash select new download | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Mr. Gil <mrgil23> |
Component: | Import-Gphoto2 | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | abasoloisasa, guazzo, jfberkhout, juergen.keppner, kdeuser, kukepoiss_85, mking24, pereirafeitosa, Siegfried.Maier |
Priority: | HI | ||
Version: | 1.0.0 | ||
Target Milestone: | --- | ||
Platform: | Unlisted Binaries | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 1.0.0 | |
Sentry Crash Report: |
Description
Mr. Gil
2009-10-13 19:49:37 UTC
From bug 210496: What I was doing when the application crashed: I've been using digikam for a couple of months reading and downloading pics from a 4GB SDHC card. Now I have this problem, and it happens either trying to download all the pics and videos (mov, actually I've done that before also) or trying to download a subset of them. *** Bug 210496 has been marked as a duplicate of this bug. *** *** Bug 210522 has been marked as a duplicate of this bug. *** The bug *might* have been fixed now, we double check every pointer before returning from the selectAlbum() method. I couldn't confirm the bug before and so I couldn't now, but: Mr. Gil, can you try the latest SVN checkout and make sure the issue has been fixed? Andi Hi, Andi, I will check, but it will have to be later today, maybe 12 hours from now... Thanks! *** Bug 210569 has been marked as a duplicate of this bug. *** *** Bug 210569 has been marked as a duplicate of this bug. *** I'm trying to build the SVN version of digiKam from instructions here: http://www.digikam.org/drupal/download/KDE4 and when I get to this step: cmake -DCMAKE_BUILD_TYPE=debugfull -DCMAKE_INSTALL_PREFIX=`kde4-config --prefix` ../../graphics there are a lot of libraries not found, but I have the latest versions of all the libraries it's looking for (i.e. libkipi6, libjasper1, libgphoto2-2, libkdcraw7). Is there a reason the cmake command is looking for different versions of libjasper, libkipi, libgphoto, libkdcraw, etc.? I would certainly like to build and test the svn digiKam, but so far I can't. Look in README file and install devel headers file from libraries packages. Gilles Caulier Thanks, Gilles, loading the -dev libraries allowed me to complete the build. I tested digikam version 1.0.0-beta6 (rev.: 1035415) and my pictures downloaded perfectly. Thanks to everyone who helped! *** Bug 210854 has been marked as a duplicate of this bug. *** *** Bug 210906 has been marked as a duplicate of this bug. *** *** Bug 210963 has been marked as a duplicate of this bug. *** *** Bug 211017 has been marked as a duplicate of this bug. *** *** Bug 211308 has been marked as a duplicate of this bug. *** *** Bug 211561 has been marked as a duplicate of this bug. *** *** Bug 211608 has been marked as a duplicate of this bug. *** *** Bug 211665 has been marked as a duplicate of this bug. *** *** Bug 211966 has been marked as a duplicate of this bug. *** *** Bug 211960 has been marked as a duplicate of this bug. *** *** Bug 212092 has been marked as a duplicate of this bug. *** *** Bug 212131 has been marked as a duplicate of this bug. *** *** Bug 212152 has been marked as a duplicate of this bug. *** *** Bug 212156 has been marked as a duplicate of this bug. *** *** Bug 212203 has been marked as a duplicate of this bug. *** *** Bug 212496 has been marked as a duplicate of this bug. *** *** Bug 212588 has been marked as a duplicate of this bug. *** *** Bug 212584 has been marked as a duplicate of this bug. *** *** Bug 212657 has been marked as a duplicate of this bug. *** *** Bug 212765 has been marked as a duplicate of this bug. *** *** Bug 212734 has been marked as a duplicate of this bug. *** *** Bug 212906 has been marked as a duplicate of this bug. *** *** Bug 212943 has been marked as a duplicate of this bug. *** *** Bug 213029 has been marked as a duplicate of this bug. *** *** Bug 213075 has been marked as a duplicate of this bug. *** *** Bug 213153 has been marked as a duplicate of this bug. *** *** Bug 213290 has been marked as a duplicate of this bug. *** *** Bug 213377 has been marked as a duplicate of this bug. *** *** Bug 213497 has been marked as a duplicate of this bug. *** I just experienced the same bug on kubuntu 9.10 while trying to import pictures from SD card. This is key functionality of digikam and therefore so many duplicate bug reports. Is the next beta planned to be released soon with a fix to at least this issue? *** Bug 213692 has been marked as a duplicate of this bug. *** Well as you can see, the report has been marked as FIXED, so sure the new beta will have this fix in it. Also notice that digiKam-1.0.0-beta6 has been released today :-) *** Bug 212665 has been marked as a duplicate of this bug. *** many thanks *** Bug 214031 has been marked as a duplicate of this bug. *** *** Bug 214132 has been marked as a duplicate of this bug. *** *** Bug 214119 has been marked as a duplicate of this bug. *** *** Bug 214144 has been marked as a duplicate of this bug. *** *** Bug 214261 has been marked as a duplicate of this bug. *** *** Bug 214293 has been marked as a duplicate of this bug. *** *** Bug 214310 has been marked as a duplicate of this bug. *** Test packages for Ubuntu Karmic are available in my PPA: https://launchpad.net/~lure/+archive/ppa The problem is that if Ubuntu is not updating the package, most users might not be aware of the new beta versions. Having new versions in an PPA is nice, but will users use it? I doubt it. I still hope Ubuntu will update the digiKam package themselves, they can't just add a beta version and keep it as the official stable digiKam release in their branch. The plan is to get this to standard Karmic backports repository, so it will be easy to get it for users. PPA is only for testing. I agree that shipping beta version is bad, but this is also due to release plans for digikam being changed - at the beginning of the cycle it looked like digikam 1.0.0 might be just in time for Karmic (this is why somebody merged beta from debian unstable), but then this has changed. Before Karmic release I could only update to latest beta5, as going back to 0.10.0 was not much better decision either. I hope we can control the grief with regular updates through backports. And BTW, even with Beta6, there is report that at least one import crasher is still there: https://bugs.edge.launchpad.net/ubuntu/+source/digikam/+bug/454113/comments/11 But this crash is not related, at least not to the problem described in here. We had a bad pointer for the SelectAlbum dialog, but the one you just mentioned is something totally different and might even be unrelated to importing images at all (just a coincidence). I tested importing so many times now, imported 20.000 images from a harddisk folder (to test threading problems), imported images from my NikonD50 with PTP and from my cardreader, all works fine here. The link you gave looks more like a general memory problem, I see a lot of malloc problems in there. Hey guys, Should I use the PPA packages, look for an update from backports, look for an official ubuntu update, do nothing, or stop using the program? Just throwing it out there, I wasn't importing anything, I was trying to tag a bunch of pictures. Not sure that is a duplicate of this bug? Not sure if it is related to the original bug but it does work ok with Picasa. Looking forward to a fix for this, I like Digikam... D --- On Fri, 11/13/09, Andi Clemens <andi.clemens@gmx.net> wrote: From: Andi Clemens <andi.clemens@gmx.net> Subject: [Bug 210462] digikam crash select new download To: playinguitar2007@yahoo.com Date: Friday, November 13, 2009, 3:54 AM https://bugs.kde.org/show_bug.cgi?id=210462 --- Comment #55 from Andi Clemens <andi clemens gmx net> 2009-11-13 09:54:22 --- But this crash is not related, at least not to the problem described in here. We had a bad pointer for the SelectAlbum dialog, but the one you just mentioned is something totally different and might even be unrelated to importing images at all (just a coincidence). I tested importing so many times now, imported 20.000 images from a harddisk folder (to test threading problems), imported images from my NikonD50 with PTP and from my cardreader, all works fine here. The link you gave looks more like a general memory problem, I see a lot of malloc problems in there. *** Bug 214732 has been marked as a duplicate of this bug. *** *** Bug 214778 has been marked as a duplicate of this bug. *** *** Bug 214763 has been marked as a duplicate of this bug. *** *** Bug 214883 has been marked as a duplicate of this bug. *** *** Bug 214988 has been marked as a duplicate of this bug. *** *** Bug 214999 has been marked as a duplicate of this bug. *** *** Bug 215005 has been marked as a duplicate of this bug. *** *** Bug 214874 has been marked as a duplicate of this bug. *** *** Bug 215021 has been marked as a duplicate of this bug. *** *** Bug 215330 has been marked as a duplicate of this bug. *** *** Bug 215524 has been marked as a duplicate of this bug. *** *** Bug 215100 has been marked as a duplicate of this bug. *** *** Bug 215622 has been marked as a duplicate of this bug. *** *** Bug 215679 has been marked as a duplicate of this bug. *** *** Bug 215695 has been marked as a duplicate of this bug. *** *** Bug 215697 has been marked as a duplicate of this bug. *** *** Bug 215955 has been marked as a duplicate of this bug. *** *** Bug 215981 has been marked as a duplicate of this bug. *** *** Bug 216024 has been marked as a duplicate of this bug. *** *** Bug 216131 has been marked as a duplicate of this bug. *** *** Bug 216151 has been marked as a duplicate of this bug. *** *** Bug 216172 has been marked as a duplicate of this bug. *** *** Bug 216206 has been marked as a duplicate of this bug. *** *** Bug 216257 has been marked as a duplicate of this bug. *** *** Bug 216311 has been marked as a duplicate of this bug. *** *** Bug 216373 has been marked as a duplicate of this bug. *** *** Bug 216389 has been marked as a duplicate of this bug. *** *** Bug 216523 has been marked as a duplicate of this bug. *** *** Bug 216571 has been marked as a duplicate of this bug. *** PLEEEEEEEEEEEEAAAAAAAAAAAAAAASEEEEEEEEEEEEE UBUNTU: If you decide to add a beta version into your stable release, PLEEEAAAAAAAAASE at least update the packages now. Beta6 has been released nearly three weeks ago. I'm really annoyed marking this bug 10 times a day as a duplicate... I guess I will post this in Ubuntu's bugtracker now... *** Bug 216646 has been marked as a duplicate of this bug. *** *** Bug 216697 has been marked as a duplicate of this bug. *** On Saturday 28 November 2009 10:39:44 pm Andi Clemens wrote:
> https://bugs.kde.org/show_bug.cgi?id=210462
>
>
>
>
>
> --- Comment #87 from Andi Clemens <andi clemens gmx net> 2009-11-28
> 23:39:34 --- PLEEEEEEEEEEEEAAAAAAAAAAAAAAASEEEEEEEEEEEEE UBUNTU:
> If you decide to add a beta version into your stable release,
> PLEEEAAAAAAAAASE at least update the packages now. Beta6 has been released
> nearly three weeks ago.
> I'm really annoyed marking this bug 10 times a day as a duplicate...
> I guess I will post this in Ubuntu's bugtracker now...
>
I totaly agree with you......
:)
Lisandro.
*** Bug 216755 has been marked as a duplicate of this bug. *** (In reply to comment #87) > PLEEEEEEEEEEEEAAAAAAAAAAAAAAASEEEEEEEEEEEEE UBUNTU: > If you decide to add a beta version into your stable release, PLEEEAAAAAAAAASE > at least update the packages now. Beta6 has been released nearly three weeks > ago. > I'm really annoyed marking this bug 10 times a day as a duplicate... > I guess I will post this in Ubuntu's bugtracker now... i help you i ask for Mandriva team to update to 1.0.0b6 they already udpated to kipi-plugins 0.8 but curiously not digikam see my report https://qa.mandriva.com/show_bug.cgi?id=56078 thanks for your work i will update to RC when available --- Nicolas Lécureuil Mandriva KDE Team (In reply to comment #93) > i will update to RC when available > > --- > Nicolas Lécureuil > Mandriva KDE Team ok thanks *** Bug 217085 has been marked as a duplicate of this bug. *** *** Bug 217421 has been marked as a duplicate of this bug. *** *** Bug 217458 has been marked as a duplicate of this bug. *** *** Bug 217496 has been marked as a duplicate of this bug. *** *** Bug 217514 has been marked as a duplicate of this bug. *** *** Bug 217708 has been marked as a duplicate of this bug. *** *** Bug 217915 has been marked as a duplicate of this bug. *** *** Bug 218137 has been marked as a duplicate of this bug. *** FWIW, there has been a backport of the recent RC to Karmic, so the Ubuntu users who are bitten by this bug should enable backports, that is, have this in their /etc/apt/sources.list deb http://no.archive.ubuntu.com/ubuntu/ karmic-backports main restricted universe multiverse deb-src http://no.archive.ubuntu.com/ubuntu/ karmic-backports main restricted universe multiverse I personally think it should be in an karmic-update also, since that is seen by more people without any action. I plan to ask Ubuntu release team for exception for 1.0.0 final release to get it into karmic-updates. Problem is that they will need to bend the rules a bit to allow to get it through: https://wiki.ubuntu.com/StableReleaseUpdates I am sorry that Digikam 1.0.0 release plan was shifted in a way that did not work for Ubuntu 9.10 and that we did not switch back to 0.10 before release. *** Bug 218160 has been marked as a duplicate of this bug. *** *** Bug 218518 has been marked as a duplicate of this bug. *** *** Bug 216940 has been marked as a duplicate of this bug. *** *** Bug 218669 has been marked as a duplicate of this bug. *** *** Bug 219088 has been marked as a duplicate of this bug. *** *** Bug 219416 has been marked as a duplicate of this bug. *** After updating digikam problem solved. *** Bug 220046 has been marked as a duplicate of this bug. *** *** Bug 220089 has been marked as a duplicate of this bug. *** *** Bug 220099 has been marked as a duplicate of this bug. *** *** Bug 221283 has been marked as a duplicate of this bug. *** *** Bug 221368 has been marked as a duplicate of this bug. *** *** Bug 221861 has been marked as a duplicate of this bug. *** *** Bug 222778 has been marked as a duplicate of this bug. *** *** Bug 223059 has been marked as a duplicate of this bug. *** *** Bug 223507 has been marked as a duplicate of this bug. *** *** Bug 223535 has been marked as a duplicate of this bug. *** *** Bug 223732 has been marked as a duplicate of this bug. *** *** Bug 223879 has been marked as a duplicate of this bug. *** *** Bug 224066 has been marked as a duplicate of this bug. *** Can somebody familiar with the digikam source code point out a small/simple/self-contained patch that can be added to the Ubuntu package that will fix this bug? Or at least, does anyone know which specific checkin to digikam resolved this? (Yes, I agree that it's retarded Ubuntu won't upgrade from the beta version, but if the individual patch for this bug is small enough, perhaps it can be applied to the beta version and at least you'll stop getting so many dup reports...) As an aside, I wonder if the KDE license should be altered to require packagers not to package beta versions, or to force them to update? It seems that the commits that modified the code mentioned in this bug are: http://websvn.kde.org/?view=revision&revision=1035079 http://websvn.kde.org/?view=revision&revision=1035122 The last one fixes the cast, so It should be related to the issue. *** Bug 224468 has been marked as a duplicate of this bug. *** Dario, thanks for trying to help me out. Unfortunately, neither of those changes solve the problem. The place where the crash is happening /is/ right where those changes were made. However, the problem isn't simply dereferencing a NULL pointer. In particular, this line crashes: return (dynamic_cast<PAlbum*>(item->album())); and gdb says: (gdb) p item $1 = (class Digikam::TreeAlbumItem *) 0xc828820 (gdb) p item->album() $2 = (class Digikam::Album *) 0x30 So, the pointer isn't NULL, which is why the additional NULL checks didn't help, but the pointer also doesn't look valid. Since the album() function is trivial (just returning a member variable), I guess there's some kind of general memory corruption. This is especially true, since anywhere that m_album is set in treefolderitem.cpp, the code immediately indirects through it, so the value must have been valid at some time, then become trashed later. :-( Then I guess you should wait for the Digikam devs to look at this, or search the commits near the ones I posted. Regards *** Bug 224852 has been marked as a duplicate of this bug. *** *** Bug 224911 has been marked as a duplicate of this bug. *** *** Bug 225000 has been marked as a duplicate of this bug. *** *** Bug 225015 has been marked as a duplicate of this bug. *** *** Bug 225017 has been marked as a duplicate of this bug. *** *** Bug 225060 has been marked as a duplicate of this bug. *** *** Bug 225197 has been marked as a duplicate of this bug. *** *** Bug 225919 has been marked as a duplicate of this bug. *** *** Bug 227013 has been marked as a duplicate of this bug. *** *** Bug 227102 has been marked as a duplicate of this bug. *** *** Bug 228744 has been marked as a duplicate of this bug. *** *** Bug 229674 has been marked as a duplicate of this bug. *** *** Bug 230464 has been marked as a duplicate of this bug. *** *** Bug 230464 has been marked as a duplicate of this bug. *** *** Bug 230761 has been marked as a duplicate of this bug. *** *** Bug 230837 has been marked as a duplicate of this bug. *** *** Bug 231332 has been marked as a duplicate of this bug. *** *** Bug 231481 has been marked as a duplicate of this bug. *** *** Bug 231798 has been marked as a duplicate of this bug. *** *** Bug 232488 has been marked as a duplicate of this bug. *** *** Bug 233228 has been marked as a duplicate of this bug. *** *** Bug 234043 has been marked as a duplicate of this bug. *** *** Bug 242411 has been marked as a duplicate of this bug. *** |