Bug 162057 - Kopete crashes after accepting file transfer request from jabber-contact
Summary: Kopete crashes after accepting file transfer request from jabber-contact
Status: RESOLVED DUPLICATE of bug 160702
Alias: None
Product: kopete
Classification: Unmaintained
Component: general (show other bugs)
Version: 0.50.1
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-05-13 19:45 UTC by Yuri Pikin
Modified: 2008-07-07 05:22 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Crash log (5.80 KB, text/plain)
2008-05-13 19:46 UTC, Yuri Pikin
Details
Crash log with dbg-libs (394 bytes, text/plain)
2008-05-15 20:38 UTC, Yuri Pikin
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Yuri Pikin 2008-05-13 19:45:41 UTC
Version:           0.50.1 (using KDE 4.0.3)
Installed from:    Ubuntu Packages
OS:                Linux

Kubuntu 8.04 + KDE4.0.3 + Kopete 0.50.1

Kopete falls down after accepting file transfer request from jabber-contact.
Comment 1 Yuri Pikin 2008-05-13 19:46:12 UTC
Created attachment 24752 [details]
Crash log
Comment 2 FiNeX 2008-05-13 20:44:56 UTC
Hi, you should follow this guide to provide an useful backtrace:

http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

Thanks a lot!
Comment 3 Alexey Chernov 2008-05-13 20:57:32 UTC
I suffer this problem, too. When clicking 'Network' on 'Places' bar and choosing 'Samba resources' in the window it throws the message, while with direct IP it works perfect.
Comment 4 Alexey Chernov 2008-05-13 21:08:25 UTC
Ohhh, sorry, I completely mixed up the bug numbers. Never mind the previous message. Shame on me..
Comment 5 Yuri Pikin 2008-05-15 20:38:38 UTC
Created attachment 24781 [details]
Crash log with dbg-libs
Comment 6 Matt Rogers 2008-07-07 05:22:44 UTC
backtrace indicate the problem is in QCA, an external library that Kopete uses. Please refer to bug #160702 which this bug is a duplicate of

*** This bug has been marked as a duplicate of 160702 ***