[Bug 584101] New: Digikam crashes with "Segmentation Fault" since update to KDE 4.3.5
http://bugzilla.novell.com/show_bug.cgi?id=584101 http://bugzilla.novell.com/show_bug.cgi?id=584101#c0 Summary: Digikam crashes with "Segmentation Fault" since update to KDE 4.3.5 Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86-64 OS/Version: openSUSE 11.2 Status: NEW Severity: Critical Priority: P5 - None Component: KDE4 Applications AssignedTo: kde-maintainers@suse.de ReportedBy: ch_belle@web.de QAContact: qa@suse.de Found By: --- Blocker: --- Created an attachment (id=345474) --> (http://bugzilla.novell.com/attachment.cgi?id=345474) The Digikam / Bugreporter crash report. User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; de; rv:1.9.2.0) Gecko/20100115 SUSE/3.6.0-1.2 Firefox/3.6 Lately Digikam is basically unusable: it constantly crashes, preferred when I try to save a photo. Digikam is version 0.10.0 KDE is version 4.3.5 Kernel is version 2.6.31.8-0.1-desktop (Version 2.6.31.12-0.1-desktop gets stuck when doing a shutdown) OS is OpenSUSE 11.2 for 64 bit Intel Reproducible: Always Steps to Reproduce: 1. Open Digikam 2. Edit a few photos & seve the changes 3. It will crash within three photos. Actual Results: Segmentation Fault. Crash report Expected Results: Saved the photo and allowed me to edit the next one. The crash is so frequent that Digikam is unusable until it is fixed. As I suspect the 4.3.5 packages I have tried to revert Kwin,KDEPIM and KDEBASE to the 4.3.1 versions, but this did not help. I have not yet tried to update KDE to the 4.4 factory version yet. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=584101 http://bugzilla.novell.com/show_bug.cgi?id=584101#c1 --- Comment #1 from Christian Belle <ch_belle@web.de> 2010-02-28 20:37:15 UTC --- *** Bug 584102 has been marked as a duplicate of this bug. *** http://bugzilla.novell.com/show_bug.cgi?id=584102 -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=584101 http://bugzilla.novell.com/show_bug.cgi?id=584101#c2 Christian Trippe <ctrippe@gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |ctrippe@gmx.net Info Provider| |ch_belle@web.de --- Comment #2 from Christian Trippe <ctrippe@gmx.net> 2010-03-04 19:39:23 UTC --- Can you please try, to get a more useful backtrace, see http://en.opensuse.org/Bugs:KDE#Useful_Crash_Reports For the updated KDE packages you have to add http://download.opensuse.org/debug/update/11.2/ to ge the corresponding debuginfo packages. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=584101 http://bugzilla.novell.com/show_bug.cgi?id=584101#c3 Christian Belle <ch_belle@web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|ch_belle@web.de | --- Comment #3 from Christian Belle <ch_belle@web.de> 2010-03-04 21:32:36 UTC --- Created an attachment (id=346665) --> (http://bugzilla.novell.com/attachment.cgi?id=346665) New zipped crash report. Added debuginfo packages for: digikam libqt4 libasound2 libkde4 libglib2 According to the crash reporter this debug file should be useful. Please request more info if I should install additional debug packages. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=584101 http://bugzilla.novell.com/show_bug.cgi?id=584101#c4 --- Comment #4 from Christian Belle <ch_belle@web.de> 2010-03-04 21:34:11 UTC --- Last lines from Digikam (run from console) before crashing: adding container: "boundaryplacemarks" true starting parser for "boundaryplacemarks" "Loading Default Placemark Cache File:/usr/share/kde4/apps/marble/data/placemarks/boundaryplacemarks.cache" newGeoDataDocumentAdded "boundaryplacemarks" Loading ended true placemarksLoaded THEME CHANGED: *** "earth/srtm/srtm.dgml" Style reset requested. QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified Containername: "baseplacemarks" to be finalized: false 6 Containername: "elevplacemarks" to be finalized: false 5 Containername: "otherplacemarks" to be finalized: false 3 Containername: "boundaryplacemarks" to be finalized: false 2 newGeoDataDocumentAdded "cityplacemarks" Loading ended true placemarksLoaded Containername: "cityplacemarks" to be finalized: true 1 Style reset requested. KCrash: Application 'digikam' crashing... sock_file=/home/nutzer/.kde4/socket-linux-djj6/kdeinit4__0 [1]- Angehalten digikam [2]+ Angehalten digikam -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=584101 http://bugzilla.novell.com/show_bug.cgi?id=584101#c Christian Trippe <ctrippe@gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P1 - Urgent -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=584101 http://bugzilla.novell.com/show_bug.cgi?id=584101#c5 --- Comment #5 from Christian Belle <ch_belle@web.de> 2010-03-21 19:16:47 UTC --- The bug still occurs with digikam version 0.10.0-7.36. I have uploaded a new crash report. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=584101 http://bugzilla.novell.com/show_bug.cgi?id=584101#c6 --- Comment #6 from Christian Belle <ch_belle@web.de> 2010-03-21 19:20:27 UTC --- Created an attachment (id=349669) --> (http://bugzilla.novell.com/attachment.cgi?id=349669) New crash file for 0.10.0-7.36 New crash report. According to http://www.linuxforen.de/forums/showthread.php?t=266936&highlight=digikam this seems to also hold true for the 4.4.1 KDE version. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=584101 http://bugzilla.novell.com/show_bug.cgi?id=584101#c7 --- Comment #7 from Christian Belle <ch_belle@web.de> 2010-03-22 20:51:09 UTC --- I have updated to kernel 2.6.31-12-0.2.1 (the clock-shutdown bug was fixed) and updated to the latest kde 4.3.5 packets. The Digikam Crash bug still persists. => You can reproduce it with the most current "stable" release. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=584101 http://bugzilla.novell.com/show_bug.cgi?id=584101#c8 --- Comment #8 from Christian Belle <ch_belle@web.de> 2010-04-21 17:17:46 UTC --- I asked Gilles Caulier for a comment, he was very friendly and answered as follows: Hi, Very easy and already reported in KDE bugzilla. Your crash log said : [KCrash Handler] #5 ref (this=<value optimized out>) at /usr/include/QtCore/qatomic_x86_64.h:121 #6 QList (this=<value optimized out>) at /usr/include/QtCore/qlist.h:111 #7 QForeachContainer (this=<value optimized out>) at /usr/include/QtCore/qglobal.h:2055 #8 KDirWatchPrivate::Entry::propagate_dirty (this=<value optimized out>) at /usr/src/debug/kdelibs-4.3.5/kio/kio/kdirwatch.cpp:399 #9 0x00007f6362e9bc8b in KDirWatchPrivate::Entry::propagate_dirty (this=<value optimized out>) at /usr/src/debug/kdelibs-4.3.5/kio/kio/kdirwatch.cpp:404 #10 0x00007f6362ea545f in KDirWatchPrivate::slotRescan (this=0x7f6350000a30) at /usr/src/debug/kdelibs-4.3.5/kio/kio/kdirwatch.cpp:1275 #11 0x00007f6362ea60c4 in KDirWatchPrivate::qt_metacall (this=0x7f6350000a30, _c=InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff061136b0) at /usr/src/debug/kdelibs-4.3.5/build/kio/kdirwatch_p.moc:73 Which is KDirWatch API from KDELibs. It's KDE 4.4.x problem. You must update KDELibs to solve it. digiKam use KDirwatch class to handle changes from folders/files, in live. http://api.kde.org/4.x-api/kdelibs-apidocs/kio/html/classKDirWatch.html Look this entry for the story : https://bugs.kde.org/show_bug.cgi?id=222974 Best Gilles Caulier Help! Could please someone do a backport to the KDE 4.3.5 library ? I am pretty sure that I am not the only Linux Beginner who frequently uses Photo processing software .... -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=584101 http://bugzilla.novell.com/show_bug.cgi?id=584101#c9 --- Comment #9 from Christian Belle <ch_belle@web.de> 2010-04-27 21:35:30 UTC --- After Gilles' comment I have updated to KDE 4.4.2 and Digikam 1.2.1. Meanwhile I have edited about 200 Photos without a single crash. KDE Update with Digikam update to 1.2.1 results in a very stable Digikam installation ! -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=584101 http://bugzilla.novell.com/show_bug.cgi?id=584101#c10 Stephen Dunn <nzlbob2332@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |nzlbob2332@gmail.com Resolution| |FIXED --- Comment #10 from Stephen Dunn <nzlbob2332@gmail.com> 2010-06-06 11:50:22 UTC --- Resolved as per comment 9 Thanks Steve -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com