FS#18927 - [digikam] crashes in startup

Attached to Project: Arch Linux
Opened by Simone Lazzaris (ziopera) - Friday, 02 April 2010, 12:55 GMT
Last edited by Giovanni Scafora (giovanni) - Saturday, 03 April 2010, 08:30 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Tobias Powalowski (tpowa)
Giovanni Scafora (giovanni)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Digikam 1.2.0 crashes on my system in startup.
I've using on a AMD64 (x86_64) system with kde 4.4.2.

The bug is already fixed upstream (see bug 232628), but a 1.2.1 version is not around the corner.
The respose I've got in the kde bugzilla is to nag the distro mantainer to apply this patch:
http://cvs.fedoraproject.org/viewvc/rpms/digikam/devel/digikam-1.2.0-kde232628.patch?revision=1.1&view=markup

So here I am :)
This task depends upon

Closed by  Giovanni Scafora (giovanni)
Saturday, 03 April 2010, 08:30 GMT
Reason for closing:  Fixed
Comment by Simone Lazzaris (ziopera) - Friday, 02 April 2010, 12:59 GMT
Here is the kde bugzilla entry for this bug.

https://bugs.kde.org/show_bug.cgi?id=232628
Comment by Giovanni Scafora (giovanni) - Friday, 02 April 2010, 13:02 GMT
I'm using it on a x86_64 system with kde 4.4.2, and it works fine.
No crashes in startup for me.
Comment by Simone Lazzaris (ziopera) - Friday, 02 April 2010, 13:10 GMT
Fine, maybe it's dependent on by configuration, but as you can see it's beek acknowledged and fixed upstream.
The patch is a one-liner, can we just apply it ?

If anyone want feedback, I can test the patch and see if it fixes my problem.
Comment by Giovanni Scafora (giovanni) - Friday, 02 April 2010, 13:15 GMT
I'm working on it.
BTW, if you can test the patch is better..
Comment by Giovanni Scafora (giovanni) - Friday, 02 April 2010, 13:31 GMT
I'm building digikam with your patch, but I cannot reproduce your issue on my system because digikam works fine here.
Let me know if you solved with that patch, so I upload in [extra] a patched version of digikam as soon as possible.
Comment by Simone Lazzaris (ziopera) - Friday, 02 April 2010, 13:42 GMT
I'm building the SVN trunk version (with the patch) right now.
Comment by Giovanni Scafora (giovanni) - Friday, 02 April 2010, 13:47 GMT
I'm ready, I already built packages (1.2.0 with your patch) for both architectures.
Please, don't build from svn, but applying the above patch on 1.2.0 version.
I'll wait your feedback, before uploading new packages in extra.
Comment by Simone Lazzaris (ziopera) - Friday, 02 April 2010, 13:57 GMT
I wasn't able to find the 1.2.0 source; the build instruction on the digikam site mentioned only the svn version.

Anyway, I'll try the svn version with and without the patch (manually removing the test that was added) to see if it fixes my behaviour.
Specifically, I'll check that without the patch I'll get the crash and that with the patch the program starts.

If you can point me to the 1.2.0 source, I also can test that.
Comment by Giovanni Scafora (giovanni) - Friday, 02 April 2010, 14:07 GMT
http://downloads.sourceforge.net/project/digikam/digikam/1.2.0/digikam-1.2.0.tar.bz2
In extra we are using the 1.2.0 version, then feedback from svn are useless.
Please, test the stable 1.2.0 version and let me know if you solve with the above patch.
If so, I upload new patched packages to the extra repo.
Comment by Simone Lazzaris (ziopera) - Friday, 02 April 2010, 14:09 GMT
I can confirm that the trunk version, WITHOUT the patch crashes on my setup, while the very same version, WITH the patch will start without troubles.

Now, just to be safe, I'm reverting the svn code to the 1.2.0 version to try also that.
Comment by Giovanni Scafora (giovanni) - Friday, 02 April 2010, 14:16 GMT
OK, I will be waiting for your feedback, before uploading new packages in extra.
Comment by Simone Lazzaris (ziopera) - Friday, 02 April 2010, 14:40 GMT
Ok, I've build the 1.2.0 plain and the crash was there.
Added the patch, and the crash was gone.

(That was the expected behaviour, but first-hand testing is always the right thing to do).

So, I can confirm that the patch fixes the problem in the 1.2.0 version. Please upload the new version to the extra repo.
Thanks for the immediate response and feedback
Comment by Giovanni Scafora (giovanni) - Friday, 02 April 2010, 14:48 GMT
I just pushed them to the extra repo (with the above patch).
Please, wait for mirror sync, then try digikam-1.2.0-2 and report me your feedback, so I can close this bug report.
Thanks a lot for your contribution.

Loading...