Version: (using KDE 4.2.2) Compiler: GCC OS: Linux Installed from: Debian testing/unstable Packages Hello, When trying to edit my privacy settings in Kopete (Settings->Configure->Accounts->Modify Account->Privacy) the app received the SIGSEGV signal, producing the following debugging information: Application: Kopete (kopete), signal SIGSEGV [Current thread is 0 (LWP 6541)] Thread 2 (Thread 0xb2789b90 (LWP 6575)): #0 0xb7fd0424 in __kernel_vsyscall () #1 0xb5e10fb5 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i686/cmov/libpthread.so.0 #2 0xb634d05d in pthread_cond_wait () from /lib/i686/cmov/libc.so.6 #3 0xb6ef5822 in QWaitCondition::wait () from /usr/lib/libQtCore.so.4 #4 0xb5e9ffd2 in ?? () from /usr/lib/libQtNetwork.so.4 #5 0xb6ef480e in ?? () from /usr/lib/libQtCore.so.4 #6 0xb5e0d4e5 in start_thread () from /lib/i686/cmov/libpthread.so.0 #7 0xb633e21e in clone () from /lib/i686/cmov/libc.so.6 Thread 1 (Thread 0xb56ec710 (LWP 6541)): #0 0xb7fd0424 in __kernel_vsyscall () #1 0xb62fa376 in nanosleep () from /lib/i686/cmov/libc.so.6 #2 0xb62fa18e in sleep () from /lib/i686/cmov/libc.so.6 #3 0xb75bb738 in ?? () from /usr/lib/libkdeui.so.5 #4 0x00000000 in ?? () It only happened once, it's probably not reproducible, yet having experienced various problems with Kopete and KDE in previous versions of the desktop environment, I thought it might've been useful to file this report. Regards, Jason
Unfortunately, the backtrace is not useful. If you can reproduce this bug, please install the debug package and paste a better one. More informations on this page: http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports
What type of account were you trying to edit?
We need more information to reproduce and fix this bug. If you could provide the information requested in the previous comments and then reopen this bug, we'll take another look at fixing it.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!