Bug 167759

Summary:	Crashes when logging in jabber with ICQ online
Product:	[Unmaintained] kopete	Reporter:	MIMI KOKO <doughnut>
Component:	general	Assignee:	Kopete Developers <kopete-bugs-null>
Status:	RESOLVED NOT A BUG
Severity:	crash	CC:	finex
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description MIMI KOKO 2008-07-30 18:21:14 UTC

Version:            (using KDE 4.1.0)
Installed from:    SuSE RPMs
OS:                Linux

Aplikace: Kopete (kopete), signál SIGSEGV
[?1034h(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)
(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)
(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)
[Thread debugging using libthread_db enabled]
[New Thread 0xb5d3f6d0 (LWP 3330)]
[New Thread 0xb2aa8b90 (LWP 5105)]
[New Thread 0xb3351b90 (LWP 4835)]
(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)
(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)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6  0xb6222776 in memcpy () from /lib/libc.so.6
#7  0x00000000 in ?? ()
#0  0xffffe430 in __kernel_vsyscall ()

Comment 1 Médéric Boquien 2008-07-30 18:39:35 UTC

Hello. Thanks for you report. Unfortunately the backtrace does not contain enough informations to understand the crash. Instructions to obtain a better backtrace are provided in this page. http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports . Thank you very much.

Comment 2 Dominik Tritscher 2008-07-31 19:44:02 UTC

Couldn't reproduce that. Could you give us more details on how to reproduce that bug?
Thats what I tried:
1. Logged in with my ICQ account
2. Logged in with my Jabber account that has the same ICQ account configured with the ICQ transport
I just got the regular message "You're signed in with multiple clients..." and everything worked as it should.

Comment 3 Matt Rogers 2008-11-18 03:29:26 UTC

No information with which to reproduce and one of our testers could not reproduce. Closing.