Mailinglist Archive: opensuse-bugs (4173 mails)

< Previous Next >
[Bug 514736] New: Kopete crash with gadu gadu protocol when try to login
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Fri, 19 Jun 2009 07:56:19 -0600
  • Message-id: <bug-514736-21960@xxxxxxxxxxxxxxxxxxxxxxxx/>
http://bugzilla.novell.com/show_bug.cgi?id=514736


Summary: Kopete crash with gadu gadu protocol when try to login
Classification: openSUSE
Product: openSUSE 11.1
Version: Final
Platform: i686
OS/Version: openSUSE 11.1
Status: NEW
Severity: Critical
Priority: P5 - None
Component: KDE4 Applications
AssignedTo: kde-maintainers@xxxxxxx
ReportedBy: benjamin.nagel@xxxxxxxxxxxxxxxxxxx
QAContact: qa@xxxxxxx
Found By: ---


User-Agent: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.9.0.11)
Gecko/2009060200 SUSE/3.0.11-0.1.1 Firefox/3.0.11

When trying to login with an gado gadu account kopete freeze or crash. When it
crash it still work and i can write messages with this protocol.

Maybe there is still a problem solving (see at "Additional Information")

Reproducible: Always

Steps to Reproduce:
create a account for the protocol gadu-gadu
add this account in kopete


When I try to login with gadu-gadu, icq, yahoo and goole-talk with the "login
all"-function kopete crashes totally.
When I try to login only with gadu-gadu protocol and not with the "login
all"-function kopete also crashes and the KDE 4 crash-manager appear. When I
use the restart application button the crashed kopete is still visible and the
"restated" application is the old "crashed" instance of kopete.

And when I check the status of my gadu-gadu account i see that I'm online, and
i can write messages to people on my contact list.




Qt: 4.5.1
KDE: 4.2.90 (KDE 4.2.90 (KDE 4.3 Beta2)) "release 138"
Kopete: 0.70.90
kernel: 2.6.27.23-0.1-pae

maybe the libgadu is compiled wrong:
here is the KDE Bug report for it https://bugs.kde.org/show_bug.cgi?id=193957

--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

< Previous Next >
This Thread
  • No further messages