Summary: | Crashes when looking at pictures / AkonadiResource crashed opening vcf-file recouce properties in KAddressBook [QList, KDirWatchPrivate::Entry::propagate_dirty, ..., KDirWatchPrivate::slotRescan] | ||
---|---|---|---|
Product: | [Unmaintained] kio | Reporter: | Xosé <xosecalvo> |
Component: | general | Assignee: | David Faure <faure> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | AndreasBank, andresbajotierra, caulier.gilles, christopher.tanner, digikam-bugs-null, edmon, florian.reinhard, gkourtev, izartova, johann-nikolaus, Julien, kde, kde, luc, mabrand, michael.hagmann, mike.hind, qwertzmd, Rudolf.Leitgeb, simon.lewis, sinozzuke, vb2013 |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
patched version of 4.3.5 release of kio/kio/kdirwatch.cpp
patched version of 4.3.5 release of kio/kio/kdirwatch.h patched version of 4.3.5 release of kio/kio/kdirwatch_p.h patch for kde4libs on Ubuntu 9.10 |
Description
Xosé
2010-01-13 15:15:05 UTC
This looks like a KIO issue, which could be related to bug 208486. Regards *** Bug 222550 has been marked as a duplicate of this bug. *** From bug 222709: -- Information about the crash: on KAddressBook (Kontact) * couldn't edit a contact * opened the properties for the corresponding addressbook (vcf file resource) * saw read only is not checked * tried to edit againm didn't work * opened the properties dialog once again => crash *** Bug 222709 has been marked as a duplicate of this bug. *** From bug 223584: -- Information about the crash: I "svn reverted" a file, that was opened in kate. When I tried to close the file in kate (the file, not kate completely), kate crashed *** Bug 223584 has been marked as a duplicate of this bug. *** From bug 223614: -- Information about the crash: This is what I was doing 1- Select 1 photo 2- Change some Levels and color. 3- Push Save button. 4- You got your shine crash *** Bug 223614 has been marked as a duplicate of this bug. *** *** Bug 225038 has been marked as a duplicate of this bug. *** *** Bug 225263 has been marked as a duplicate of this bug. *** From bug 226171: -- What I was doing when the application crashed: I changed a file under subversion control and commited it As the commit changes certain information in the file (svn properties - Author, Id etc) the file was marked with a red cross. When I then attempted to close the file Kate then exited with a Segmentation fault rather then just closing the file. *** Bug 226171 has been marked as a duplicate of this bug. *** Steps to reproduce: - Start KWrite - Write a dummy text and save the file to disk - Externally remove the file ("rm foobar", from Konsole) - In the first KWrite warning about the changed file select "Cancel" - Try to save the file - In the second KWrite warning select "Cancel" - Go to the KWrite Settings - In the third KWrite warning select "Cancel" - Externally recreate the file ("touch foobar" from Konsole) Here using: Qt: 4.6.1 (kde-qt master commit 46ef51d8bf520bda3eea9e996349694ce1ff3959 Date: Sat Jan 30 02:23:21 2010 +0100) KDE Development Platform: 4.4.63 (KDE 4.4.63 (KDE 4.5 >= 20100209)) kdelibs svn rev. 1090634 / kdebase svn rev. 1090635 on ArchLinux i686 - Kernel 2.6.32.8 SVN commit 1090729 by dfaure: Fix the "kdirwatch crash on re-entrancy from the slots" by emitting the signals in a delayed manner. Fixed for: 4.4.1 BUG: 224229 208486 226674 222547 M +21 -9 kdirwatch.cpp M +20 -16 kdirwatch.h M +2 -0 kdirwatch_p.h WebSVN link: http://websvn.kde.org/?view=rev&revision=1090729 *** Bug 208486 has been marked as a duplicate of this bug. *** *** Bug 227253 has been marked as a duplicate of this bug. *** *** Bug 227220 has been marked as a duplicate of this bug. *** *** Bug 227902 has been marked as a duplicate of this bug. *** Created attachment 41015 [details]
patched version of 4.3.5 release of kio/kio/kdirwatch.cpp
Created attachment 41016 [details]
patched version of 4.3.5 release of kio/kio/kdirwatch.h
Created attachment 41017 [details]
patched version of 4.3.5 release of kio/kio/kdirwatch_p.h
I have applied this patch to Ubuntu's KDE 4.3.5 release (had to modify some line numbers) and it seems to work for right now. Could any of the KDE experts confirm that this patch has no side effects if applied to KDE 4.3.5? It would be very helpful if this patch made it into the main Ubuntu distro as crashing applications are a major annoyance. I had digiKam crashing regularly before I applied the patch. In order to help you speed up things I attached the three affected files which I patched manually. To all those who want to try out the patched files: These are kio/kio/kdirwatch.cpp, kio/kio/kdirwatch.h and kio/kio/kdirwatch_p.h The patched source deb compiles file and produces working libraries and executables, however, I would like to point out that I'm not familiar with the KDE code base and have done little testing with the patched KDE libs so far. Full files are not useful and impossible to review, better post a patch that applies to the 4.3.5 sources. Created attachment 41038 [details]
patch for kde4libs on Ubuntu 9.10
This patch is supposed to do the same thing for Ubuntu's version of the KDE (4.3.5) what the original patch does for KDE 4.4. I have used digiKam without crashes after applying this patch to the source deb. Please note that you need to go to the kio sub directory (not kio/kio !) before applying this patch!
*** Bug 228788 has been marked as a duplicate of this bug. *** Thanks,
Chris
On February 27, 2010 01:14:09 pm Dario Andres wrote:
> https://bugs.kde.org/show_bug.cgi?id=222547
>
>
> Dario Andres <andresbajotierra@gmail.com> changed:
>
> What |Removed |Added
> ---------------------------------------------------------------------------
> - CC| |christopher.tanner@sympatic
>
> | |o.ca
>
> --- Comment #25 from Dario Andres <andresbajotierra gmail com> 2010-02-27
> 19:14:03 --- *** Bug 228788 has been marked as a duplicate of this bug.
> ***
*** Bug 229857 has been marked as a duplicate of this bug. *** *** Bug 230346 has been marked as a duplicate of this bug. *** *** Bug 230268 has been marked as a duplicate of this bug. *** *** Bug 230531 has been marked as a duplicate of this bug. *** *** Bug 230755 has been marked as a duplicate of this bug. *** *** Bug 230799 has been marked as a duplicate of this bug. *** *** Bug 230897 has been marked as a duplicate of this bug. *** *** Bug 231868 has been marked as a duplicate of this bug. *** *** Bug 231866 has been marked as a duplicate of this bug. *** *** Bug 233195 has been marked as a duplicate of this bug. *** |