kportage seg fault

[lodger]

I unmerged and re-emerged kportage-0.6.1 against python-2.2.3.
(See bug #22660)
When I start kportage I get a seg fault from kde as follows-

(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...[New Thread 16384 (LWP 24353)]
0x410bd1c7 in waitpid ()
from /lib/libpthread.so.0
#0 0x410bd1c7 in waitpid () from /lib/libpthread.so.0
#1 0x406fd0ac in KCrash::defaultCrashHandler(int) ()
from /usr/kde/3.1/lib/libkdecore.so.4
#2 0x410bc03c in __pthread_sighandler () from /lib/libpthread.so.0
#3 <signal handler called>
#4 0x080a8ba3 in PortagePython::stringFromClassMethod(char*, char*, _object*)
()
#5 0x080a8f12 in PortagePython::readConfig() ()
#6 0x080c2924 in ParseMakeConfs::readConfig() ()
#7 0x080c20af in ParseMakeConfs::ParseMakeConfs(QMap<QString, QString>*) ()
#8 0x080b6c2c in Config::Config() ()
#9 0x080b6f26 in Config::instance() ()
#10 0x0808952e in KPortageApp::initActions() ()
#11 0x08086b43 in KPortageApp::KPortageApp(QWidget*, char const*) ()
#12 0x0808f31e in main ()
#13 0x4114b7a7 in __libc_start_main () from /lib/libc.so.6
All my other apps seem to be working just fine but this kportage/python
difficulty persists.
Any ideas?

[Carlo]

Does it segfault directly on start? I had this problem a while ago. In the end it turns out that ~/.kde/share/apps/kportage/map was corrupted.
Removing the file solved the problem.


Carlo

[lodger]

I tried that but it didn't work.
So deleted the ~/.kde/share/apps/kportage and unmerge kportage and am
now reemerging it. We shall see.

[lodger]

Well, that didn't work. I still get the seg fault.