Version: (using KDE 4.2.2) Installed from: Debian testing/unstable Packages From: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=523752 Reported by: "Mario R. Carro" <mcarro@gmx.net> After upgrading from KDE 3.5 some contacts appear without any label in the roster. If I edit the properties of one (or more) of those contact and change the "Display Name Source" property from "From Contact" (that appears empty, why? But that should be another bugreport I guess) to "Use addressbook name (needs addressbook link)" the contact name reappears in the roster, but when I close Kopete a fatal error msg box is shown, with the following backtrace: Application: Kopete (kopete), signal SIGSEGV Thread 1 (Thread 0xb584e920 (LWP 1971)): #0 0xb7fb8424 in __kernel_vsyscall () #1 0xb63eb350 in nanosleep () from /lib/i686/cmov/libc.so.6 #2 0xb63eb18e in sleep () from /lib/i686/cmov/libc.so.6 #3 0xb759c738 in ?? () from /usr/lib/libkdeui.so.5 #4 0x00000000 in ?? () and the changes made to the contact are lost. Thanks...
Unfortunately, there's not a lot here that we can go on. If you can reproduce the crash at will, please read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and post a complete backtrace here? Thanks :)
Original submitter contacted. If he doesn't replies in two weeks, I'll close this bug in Debian's BTS and ask the same here. Regards, Lisandro.
I repeated the process I outlined and no crash ocurred. It is off course not the same situation: The problem appeared when I tried to manipulate the contact list migrated from v3.5, but out of frustration I ended clearing up the whole list and reentering all the contacts again... so it's different experiment. All I can confirm is that with the new contacts created with v4.2 this problem does not appear. Excuse me for not following the bug. At that moment I was very busy, so after I reported it I forgot completely about it... Anyway, I'm on KDE 4.3.1 now, Kopete is working OK again, everyone is happy, you can close the bug. Thanks...
Thank you very much for following up with the extra information.