Am running ubuntu 12.o4 LTS, when i run konversation and then go on the view of all the nicknames and scroll while the pointer is focussed on the nickname view, the application crashes suddenly, and does not even open up the report bug window, neither does it give any failure trace when i run it in terminal, finnally after reproducing the issue for many times, i have decided to add the backtrace details below; Reproducible: Always Steps to Reproduce: 1.open konversation 2.join a channel/network, and then join a channel i.e #konversation 3.move the pointer over the nicknames available on the channel and then sroll over them, I have experienced this on linux ubuntu 12.04 LTS 32-bit Actual Results: the following is the backtrace generated after the apllication crashes Application: Konversation (konversation), signal: Segmentation fault Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0xb4267780 (LWP 7103))] Thread 3 (Thread 0xb1e89b40 (LWP 7104)): #0 0xb775a424 in __kernel_vsyscall () #1 0xb54ca5f0 in poll () from /lib/i386-linux-gnu/libc.so.6 #2 0xb4ef3a7b in g_poll () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0xb4ee60ae in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0xb4ee656b in g_main_loop_run () from /lib/i386-linux-gnu/libglib-2.0.so.0 #5 0xb1e8e134 in ?? () from /usr/lib/i386-linux-gnu/gio/modules/libdconfsettings.so #6 0xb4f096b3 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #7 0xb4e74d4c in start_thread () from /lib/i386-linux-gnu/libpthread.so.0 #8 0xb54d8d3e in clone () from /lib/i386-linux-gnu/libc.so.6 Thread 2 (Thread 0xb14ffb40 (LWP 7105)): #0 0xb4f250d7 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #1 0xb4f25408 in g_mutex_unlock () from /lib/i386-linux-gnu/libglib-2.0.so.0 #2 0xb4ee609b in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0xb4ee656b in g_main_loop_run () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0xb46eb1ba in ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 #5 0xb4f096b3 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #6 0xb4e74d4c in start_thread () from /lib/i386-linux-gnu/libpthread.so.0 #7 0xb54d8d3e in clone () from /lib/i386-linux-gnu/libc.so.6 Thread 1 (Thread 0xb4267780 (LWP 7103)): [KCrash Handler] #7 0x00000000 in ?? () Expected Results: the software should at no point crash suddenly
Created attachment 80562 [details] backtrace generated at the crashing of konversation
The backtrace is not helpful. Please install debug symbols for at least konversation (maybe also for Qt and kdelibs) and generate a new backtrace. Please also add the kde version, Qt version, if you are using konversation under kde or (for example) gnome, and the theme you are using (oxygen for example). If the crash window does not show up, please run konversation in gdb.
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!
Dear Bug Submitter, 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!