| Summary: | KMail got signal 11 (Crashing) | ||
|---|---|---|---|
| Product: | [Applications] kontact | Reporter: | Ron Eggler <ron.eggler> |
| Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | ingo.gb |
| Priority: | NOR | ||
| Version: | 1.2 | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
|
Description
Ron Eggler
2008-07-20 04:11:43 UTC
must have updated my kdelibs but not my kdebase packages. On KDE restart I couldn't fire KDE back-0up so I updated kdelibs as well as kdebase what let me login again and Kontact was working just fine! :) You may wanna think about a better error message? (Maybe one showing up in a lil KDE message box?) :) I'm on ArchLinux using vanilla kde and I get this: toad@deskarch 999\1 ~ > kontact Calling appendChild() on a null node does nothing. Calling appendChild() on a null node does nothing. Calling appendChild() on a null node does nothing. Calling appendChild() on a null node does nothing. Calling appendChild() on a null node does nothing. Calling appendChild() on a null node does nothing. Calling appendChild() on a null node does nothing. Calling appendChild() on a null node does nothing. Calling appendChild() on a null node does nothing. Calling appendChild() on a null node does nothing. Calling appendChild() on a null node does nothing. Calling appendChild() on a null node does nothing. Calling appendChild() on a null node does nothing. Object::connect: No such signal Akregator::SubscriptionListView::signalDropped (KUrl::List &, Akregator::TreeNode*, Akregator::Folder*) Object::connect: (sender name: 'feedtree') Object::connect: (receiver name: 'akregator_view') Object::connect: No such signal Akregator::Part::showPart() Object::connect: (receiver name: 'akregator') <unknown program name>(5911)/ main: Unknown resource type: "notes" toad@deskarch 999\2 ~ > *** KMail got signal 11 (Crashing) KCrash: Application 'kontact' crashing... sock_file=/home/toad/.kde4/socket-deskarch/kdeinit4__0 toad@deskarch 999\2 ~ > kde4-config --version Qt: 4.5.3 KDE: 4.3.4 (KDE 4.3.4) kde4-config: 1.0 I had to use the reset button following a virtualbox disaster while akregator was active. Since then the above happened. Renaming ~/.kde4/share/apps/akregator to ~/.kde4/share/apps/akregator~ resolved the issue. Now I've just got to find the corrupted file in akregator... Okay, the offending data was in ~/.kde4/share/apps/akregator/data/feeds.opml When I delete that file, the old akregator folder can be used. |