I know, theoretical I should move to KDE 4.x, but KDE 4 runs too much slow on my hardware ... Maybe I will change platform in two or three months.

Well, every time I change apps on kontact, i.e. from KMail to Kalender, kontact crashes down and gives out a short report (look at the bottom).

Could you please help me for fixing this item?
Have you an idea, what is the cause of theese crashes?

Many thanks !!

Linux Kernel: 2.6.25.20-0.6-default i686
OS: openSUSE 11.0
KDE: 3.5.9 "release 49.2"
Kontact Container: 1.2.9
KMail: 1.9.9
K-Addressbook: 3.5.9
KOrganizer: 3.5.9

Here the last crash report:

[?1034h(no debugging symbols found)
(no debugging symbols found)
...
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb5fd76d0 (LWP 3713)]
[New Thread 0xb34c4b90 (LWP 3717)]
[New Thread 0xb3cc5b90 (LWP 3716)]
[New Thread 0xb44c6b90 (LWP 3715)]
[New Thread 0xb4cc7b90 (LWP 3714)]
(no debugging symbols found)
...
(no debugging symbols found)
[KCrash handler]
#6 0x00000000 in ?? ()

Upgrading to KDE 3.5.10 is strongly recommended for those remaining with the KDE 3.5 series.

bcooksley wrote:Upgrading to KDE 3.5.10 is strongly recommended for those remaining with the KDE 3.5 series.

I'm updating to 3.5.10 now. If kontact no chraches anymore, I'll set this thread to solved, otherwise I'll give the new crash report.

Thanks for the suggestion. Actually I did not know about the 10th version!!

System is now updated to 3.5.10 but Kontact crashes unfortunately like before. This time it crashes while changing from KMail to overview, after a free crash switch from address book.

Because I added a tool ikone to KMail, before the first crash, I suppose, it could depend on it ... But why ??

The new crash report:

[?1034h(no debugging symbols found)
(no debugging symbols found)
...
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb5eba6d0 (LWP 3718)]
[New Thread 0xb330db90 (LWP 3722)]
[New Thread 0xb3b0eb90 (LWP 3721)]
[New Thread 0xb430fb90 (LWP 3720)]
[New Thread 0xb4b10b90 (LWP 3719)]
(no debugging symbols found)
...
(no debugging symbols found)
[KCrash handler]
#6 0x00000000 in ?? ()
#7 0xb74e9491 in KXMLGUI::ContainerNode::unplugClient ()
from /opt/kde3/lib/libkdeui.so.4
#8 0xb74e9a6c in KXMLGUI::ContainerNode::unplugActions ()
from /opt/kde3/lib/libkdeui.so.4
#9 0xb74e9ad2 in KXMLGUI::ContainerNode::destruct ()
from /opt/kde3/lib/libkdeui.so.4
#10 0xb74ea02a in KXMLGUI::ContainerNode::destructChildren ()
from /opt/kde3/lib/libkdeui.so.4
#11 0xb74e9ac0 in KXMLGUI::ContainerNode::destruct ()
from /opt/kde3/lib/libkdeui.so.4
#12 0xb75901b0 in KXMLGUIFactory::removeClient ()
from /opt/kde3/lib/libkdeui.so.4
#13 0xb79f999a in KParts::MainWindow::createGUI ()
from /opt/kde3/lib/libkparts.so.2
#14 0x08062121 in ?? ()
#15 0x080655b2 in ?? ()
#16 0xb6bcb98a in QObject::activate_signal ()
from /usr/lib/qt3/lib/libqt-mt.so.3
#17 0x080665fd in ?? ()
#18 0x08066661 in ?? ()
#19 0xb6bcb9cf in QObject::activate_signal ()
from /usr/lib/qt3/lib/libqt-mt.so.3
#20 0x08066ccd in ?? ()
#21 0xb6cac7d2 in QListBox::mousePressEventEx ()
from /usr/lib/qt3/lib/libqt-mt.so.3
#22 0xb6cacd94 in QListBox::mousePressEvent ()
from /usr/lib/qt3/lib/libqt-mt.so.3
#23 0xb6c06936 in QWidget::event () from /usr/lib/qt3/lib/libqt-mt.so.3
#24 0xb6b665bd in QApplication::internalNotify ()
from /usr/lib/qt3/lib/libqt-mt.so.3
#25 0xb6b677c6 in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3
#26 0xb72564c2 in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4
#27 0xb6b00aee in QApplication::sendSpontaneousEvent ()
from /usr/lib/qt3/lib/libqt-mt.so.3
#28 0xb6afd910 in QETWidget::translateMouseEvent ()
from /usr/lib/qt3/lib/libqt-mt.so.3
#29 0xb6afcbad in QApplication::x11ProcessEvent ()
from /usr/lib/qt3/lib/libqt-mt.so.3
#30 0xb6b10d54 in QEventLoop::processEvents ()
from /usr/lib/qt3/lib/libqt-mt.so.3
#31 0xb6b7ef00 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3
#32 0xb6b7ed96 in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#33 0xb6b66c4f in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#34 0x0805b9a4 in ?? ()
#35 0xb670c5f5 in __libc_start_main () from /lib/libc.so.6
#36 0x0805add1 in ?? ()

Unfortunately that looks like a crash in KDELibs. You may be able to use the Enterprise3 branch, which the PIM devs still support, primarily due to usage by commerical clients, which may have that bug fixed.

bcooksley wrote:Unfortunately that looks like a crash in KDELibs. You may be able to use the Enterprise3 branch, which the PIM devs still support, primarily due to usage by commerical clients, which may have that bug fixed.

It looks like strange, what you wrote. I don't think I am able to use this "Enterprise3 branch".
What ist that at all? How can you get it? Does it belong to Suse or Kde?.

By the way, after update to 3.5.10 KMail doesn't load down new mails ...

I suggest you contact the kdepim-users@kde.org mailing list in this case, as I haven't run KDE 3.5 for a very long time and do not know much regarding troubleshooting it.

Hi bcooksley!

Because I had the suspect of Kernel and KDE basic files corruption, I decided to backup the /home-files and to re-install the openSUSE 11.0.

Now I'm recovering my Data back in the /home-Directory an I have a question about >> Maybe can you help me ...

Due to the mentioned corruption I wouldn't restore the entire /.kde direcrtory "on block". Instead I'd like to do that stepwise, in order to control effects and results.

So I thougt, maybe can you suggest me a KDE update tutorial, where all the single files are listed, which have to be saved before an update. If it possible, the tutorial should also explain the function of these files.

I.e.: /.kde/cache-dhcppc0/kpc must be absolutely saved and is used to ...
or : The categories of Kalender are set on <FILENAME>, the relative colours are set on <FILENAME>

Do you know any one?

Thanks a lot.

You are wise to do it this way. There is no guide as such, but I can offer some general guidance.

First, make a list of the applications that you use most, and tackle those one application at a time, testing each one to make sure that everything is still OK. If you do hit a problem, at least you know that just removing that change will bring things back to normal.

Don't overwrite any files. When you want to restore a config file, for instance, rename the existing one to filename.orig and then bring in the backup one to be the new config. Don't forget to always make sure that the relevant application is closed when you do it, as many applications save their config on closing.

For most applications it will be quite clear which files and folders you need, from the directories ~/.kde/share/apps and ~/.kde/share/config (some distros use .kde4). For email there are a few additional files that you need - you'll find them listed at http://userbase.kde.org/KMail/FAQs_Hint ... #Migration

I doubt if any files with 'cache' in the name should be copied, especially if 'dhcp' is there - they probably refer to your session at the time.

annew wrote:You are wise to do it this way. There is no guide as such, but I can offer some general guidance.

First, make a list of the applications that you use most, and tackle those one application at a time, testing each one to make sure that everything is still OK. If you do hit a problem, at least you know that just removing that change will bring things back to normal.

Don't overwrite any files. When you want to restore a config file, for instance, rename the existing one to filename.orig and then bring in the backup one to be the new config. Don't forget to always make sure that the relevant application is closed when you do it, as many applications save their config on closing.

For most applications it will be quite clear which files and folders you need, from the directories ~/.kde/share/apps and ~/.kde/share/config (some distros use .kde4). For email there are a few additional files that you need - you'll find them listed at http://userbase.kde.org/KMail/FAQs_Hint ... #Migration

I doubt if any files with 'cache' in the name should be copied, especially if 'dhcp' is there - they probably refer to your session at the time.

That has been exactly my re-install and recover strategy!
There is no accurate migration guideline? What a pity!
However thanks all you very much for supprt and for the link to KMail FAQs.
The atrikel seems good, I hope it helps me.

I set the thread to solved.
Bye