https://bugs.kde.org/show_bug.cgi?id=339144
Rex Dieter <[hidden email]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED Latest Commit| |http://commits.kde.org/libk | |exiv2/25ad41274d0f408455479 | |4ee91e183accfce781f Version Fixed In| |4.14.2 Resolution|--- |FIXED --- Comment #16 from Rex Dieter <[hidden email]> --- Git commit 25ad41274d0f4084554794ee91e183accfce781f by Rex Dieter, on behalf of Gilles Caulier. Committed on 02/09/2014 at 12:04. Pushed by rdieter into branch 'KDE/4.14'. Prevent crash if index if out of QList range. FIXED-IN: 4.14.2 M +23 -4 libkexiv2/kexiv2previews.cpp http://commits.kde.org/libkexiv2/25ad41274d0f4084554794ee91e183accfce781f -- 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 |
In reply to this post by DrSlony-4
https://bugs.kde.org/show_bug.cgi?id=339144
Gilles Caulier <[hidden email]> changed: What |Removed |Added ---------------------------------------------------------------------------- Version Fixed In|4.14.2 |4.4.0 --- Comment #17 from Gilles Caulier <[hidden email]> --- Note : fixed in libkexiv2 through kdegraphics/libs version 4.14.2 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 |
In reply to this post by DrSlony-4
https://bugs.kde.org/show_bug.cgi?id=339144
--- Comment #18 from Rex Dieter <[hidden email]> --- If you want mention of this bugfix included in the 4.14.2 release announcement, I think it needs to say 4.14.2 , but I'll leave that to you. :) -- 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 |
In reply to this post by DrSlony-4
https://bugs.kde.org/show_bug.cgi?id=339144
--- Comment #19 from Gilles Caulier <[hidden email]> --- Rex, I use fixed in tag to register all files closed between digiKam release. All files closed can be listed quickly through bugzilla database : https://bugs.kde.org/buglist.cgi?f1=cf_versionfixedin&list_id=1124467&o1=equals&product=digikam&product=digikamimageplugins&product=kipiplugins&product=showfoto&query_format=advanced&v1=4.4.0 Libkexiv2 is also published into digiKam SC tarball, but disabled by default at compile time... Gilles -- 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 |
In reply to this post by DrSlony-4
https://bugs.kde.org/show_bug.cgi?id=339144
--- Comment #20 from Gilles Caulier <[hidden email]> --- Note : the version ID of the report use digiKam release, as libkexiv2 is included in digiKam section from bugzilla. So we must still homogeneous here between report version and fixed version... Gilles -- 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 |
In reply to this post by DrSlony-4
https://bugs.kde.org/show_bug.cgi?id=339144
Gilles Caulier <[hidden email]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |christian.gottschall@univie | |.ac.at --- Comment #21 from Gilles Caulier <[hidden email]> --- *** Bug 339217 has been marked as a duplicate of this bug. *** -- 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 |
In reply to this post by DrSlony-4
https://bugs.kde.org/show_bug.cgi?id=339144
Christian <[hidden email]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[hidden email] --- Comment #22 from Christian <[hidden email]> --- Request for help: --------------------------- Please inform repobuilders to provide digikam 4.2 as package as soon as possible, e.g. Stephan Kulow from openSuse. Stephan, like many others provides early factory builds of digikam, because digikam 3.5 is still the official openSuse build. I cannot go back to 3.5, and Stephan removed all earlier packages from the web. 4.3 package crashes. My suggestion: Please provide the 4.2 version till the bug is fixed in the various distros. To give an example what happened to me this morning: ---------------------------------------------------------------------------------- I end up with no digikam on two workstations for production. In my second office there are still valid 4.2 installations and i can get the package files out of the yum cache, but this office is 200 km away from here. : ( -- 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 |
In reply to this post by DrSlony-4
https://bugs.kde.org/show_bug.cgi?id=339144
Gilles Caulier <[hidden email]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[hidden email] | |g --- Comment #23 from Gilles Caulier <[hidden email]> --- *** Bug 339269 has been marked as a duplicate of this bug. *** -- 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 |
In reply to this post by DrSlony-4
https://bugs.kde.org/show_bug.cgi?id=339144
[hidden email] changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[hidden email] --- Comment #24 from [hidden email] --- Is there some work around for this bug? Or is the only option waiting another months for Digikam 4.4 and KDE 4.14.2 and hoping no new bug is introduced? Sorry for the bluntness, I love Digikam but hate this policy of not releasing bugfixes until the next version. 4.2 was unusable for me for some other bug, now 4.3, and the last available version for *buntu is 4.0, so I'm back there right now. -- 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 |
In reply to this post by DrSlony-4
https://bugs.kde.org/show_bug.cgi?id=339144
Kenneth Ingham <[hidden email]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[hidden email] --- Comment #25 from Kenneth Ingham <[hidden email]> --- I second the comment from [hidden email]. -- 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 |
In reply to this post by DrSlony-4
https://bugs.kde.org/show_bug.cgi?id=339144
Gilles Caulier <[hidden email]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[hidden email] --- Comment #26 from Gilles Caulier <[hidden email]> --- *** Bug 339309 has been marked as a duplicate of this bug. *** -- 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 |
In reply to this post by DrSlony-4
https://bugs.kde.org/show_bug.cgi?id=339144
--- Comment #27 from Thomas Arend <[hidden email]> --- 4.2 hangs up during the working and produces no crashed report. Tried the same with 4.3 and could not force a crash. It crashes when (sometimes) when I close the program. But I don't care much about crashes when closing an program. :-) So going back to 4.2 is not a solution. I don't need the worse bug back. -- 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 |
In reply to this post by DrSlony-4
https://bugs.kde.org/show_bug.cgi?id=339144
--- Comment #28 from Gilles Caulier <[hidden email]> --- I want to be clear about this file. Bug is in libkexiv2 and fixed after digiKam 4.3.0. libkexiv2 patch have been back-ported from master to stable KDE branch. This want mean that bug will be fixed at next KDE 4.14.2 or using an update of KDE > 4.14.2 where patch can be back-ported by distro packagers. -- 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 |
For those using my kubuntu-backports PPA with digikam 4.3.0 for ubuntu 14.04 with the kubuntu teams PPA with KDE 4.14.x I have updated my digikam 4.3.0 packages with the libkexiv2 fix. Hopefully that solves this bug for some users until the fix have found itself to upstream releases. On Mon, Sep 22, 2014 at 10:58 PM, Gilles Caulier <[hidden email]> wrote: https://bugs.kde.org/show_bug.cgi?id=339144 _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by DrSlony-4
https://bugs.kde.org/show_bug.cgi?id=339144
--- Comment #29 from Philip Johnsson <[hidden email]> --- For those using my kubuntu-backports PPA with digikam 4.3.0 for ubuntu 14.04 with the kubuntu teams PPA with KDE 4.14.x I have updated my digikam 4.3.0 packages with the libkexiv2 fix. Hopefully that solves this bug for some users until the fix have found itself to upstream releases. On Mon, Sep 22, 2014 at 10:58 PM, Gilles Caulier <[hidden email]> wrote: > https://bugs.kde.org/show_bug.cgi?id=339144 > > --- Comment #28 from Gilles Caulier <[hidden email]> --- > I want to be clear about this file. > > Bug is in libkexiv2 and fixed after digiKam 4.3.0. > > libkexiv2 patch have been back-ported from master to stable KDE branch. > This > want mean that bug will be fixed at next KDE 4.14.2 or using an update of > KDE > > 4.14.2 where patch can be back-ported by distro packagers. > > -- > 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 > -- 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 |
In reply to this post by DrSlony-4
https://bugs.kde.org/show_bug.cgi?id=339144
--- Comment #30 from Christian <[hidden email]> --- (In reply to Thomas Arend from comment #27) > So going back to 4.2 is not a solution. I don't need the worse bug back. You are refering to your distribution - but don't forget there are many others out there. The last 4.x build for openSuse is 4.3, which crashes, while 4.2 was working fine, but is not on the net any more. Therefore I repeat my Request for help: ------------------------------------------------------------ Please inform repobuilders to check their latest digikam packages as soon as possible, e.g. Stephan Kulow from openSuse. I am not the only one who have NO digikam available for a whole working day till now on several workstations: http://forums.opensuse.org/showthread.php/501064-digikam-4-3-0 Please be aware of the users perspective: '''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' I use digikam in production. It is good news that the source of the bug is known and resolved. But this DOES NOT HELP ME in the situation, where NO working package of digikam is available at all, because my auto-update script installed the bad release on two workstations. It is a NO GO from user perspective, that there is no working release online, because the repo-builder are not informed that he/she might have build dead software. Christian ________________ PS: I am fully aware that this is an openSuse issue, because release 3.5 (stone age) is the official supported version. So I am forced to use an early adopters releases in production without any support ... and no regular way to contact the builder. -- 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 |
In reply to this post by DrSlony-4
https://bugs.kde.org/show_bug.cgi?id=339144
--- Comment #31 from Gilles Caulier <[hidden email]> --- The next digiKam release 4.4.0 is planed at 10 october 2014 This version will include all fix to prevent this crash. 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 |
In reply to this post by DrSlony-4
https://bugs.kde.org/show_bug.cgi?id=339144
--- Comment #32 from Gilles Caulier <[hidden email]> --- Git commit 573069e8cd3b7155582e0c7be3625c0cc4879619 by Gilles Caulier. Committed on 23/09/2014 at 07:49. Pushed by cgilles into branch 'master'. Handle right libkexiv2 version to extract preview and prevent crash in Exiv2 preview extractor. M +6 -0 libs/threadimageio/thumbnailcreator.cpp http://commits.kde.org/digikam/573069e8cd3b7155582e0c7be3625c0cc4879619 -- 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 |
In reply to this post by DrSlony-4
https://bugs.kde.org/show_bug.cgi?id=339144
--- Comment #33 from Gilles Caulier <[hidden email]> --- To all packagers, Patch from comment #32 prevent digiKam crash if libkexiv2 version is not right one. You can backport this patch to 4.3.0 source code. 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 |
In reply to this post by DrSlony-4
https://bugs.kde.org/show_bug.cgi?id=339144
--- Comment #34 from Gilles Caulier <[hidden email]> --- Git commit e2eeb730d02aad858f15c6f35f2a6b6beb38acf5 by Gilles Caulier. Committed on 23/09/2014 at 08:28. Pushed by cgilles into branch 'master'. Another place where we need to handle right libkexiv2 version to extract preview and prevent crash in Exiv2 preview extractor. M +5 -1 libs/threadimageio/previewtask.cpp http://commits.kde.org/digikam/e2eeb730d02aad858f15c6f35f2a6b6beb38acf5 -- 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 |
Free forum by Nabble | Edit this page |