abrt version: 1.1.13 architecture: x86_64 Attached file: backtrace cmdline: /usr/libexec/telepathy-haze component: telepathy-haze crash_function: media_channel_request_streams executable: /usr/libexec/telepathy-haze kernel: 2.6.35.4-28.fc14.x86_64 package: telepathy-haze-0.4.0-1.fc14 rating: 4 reason: Process /usr/libexec/telepathy-haze was killed by signal 11 (SIGSEGV) release: Fedora release 14 (Laughlin) time: 1285425937 uid: 500 comment ----- Trying to do an audio chat over yahoo crashes telepathy-haze. Perhaps this isn't available yet but we should plug up this option to prevent a crash if it isn't implemented. How to reproduce ----- 1. Connect to yahoo 2. Right Click on a Friend 3. Select Audio Chat 4. Crash
Created attachment 449603 [details] File: backtrace
This was discussed at the 2010-10-01 blocker review meeting. We decided it isn't quite a release blocker as audio chat does not count as 'basic functionality' per the relevant criterion ("All applications listed under the Applications menu must withstand a basic functionality test and not crash after a few minutes of normal use. They must also have working Help and Help -> About menu items"). However, we accept it as a nice-to-have as it would be good to avoid this problem on the live images.
Package: telepathy-haze-0.4.0-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Tried to make a video call 2. 3.
Removing F14 NTH status as F14 is now out. Remaining open nice-to-have issues do NOT automatically become nice-to-have issues for Fedora 15. If you believe a Fedora 14 issue which was accepted as nice-to-have but not resolved in time for release should also qualify for nice-to-have status for Fedora 15, please re-propose it as nice-to-have for Fedora 15. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Package: telepathy-haze-0.4.0-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) Comment ----- I tried making an audio call to another icq user, I think she is using pidgin. I can reproduce this, even when audio calling myself
Package: telepathy-haze-0.4.0-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Click video call 2. Crash and burn 3.
Package: telepathy-haze-0.4.0-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- Yahoo Messenger, begin Video Call.
Package: telepathy-haze-0.4.0-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Add a SIP account to Empathy 2. Attempt to place a call
Package: telepathy-haze-0.4.0-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) Comment ----- Attempting a video call with an AIM account.
This bug wasn't listed in the latest Bodhi update-testing release, but I think this crash issue has been plugged up by the latest release here: https://admin.fedoraproject.org/updates/telepathy-haze-0.4.0-2.fc14?_csrf_token=c712193ed8a71a39f0d6c055cfcd34d81c17c493. Other could test it out and comment if they wish.
Package: telepathy-haze-0.4.0-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Login to Empathy Messenger (configured to connect to Yahoo IM). 2. Click on the webcam symbol next to a friend's name. 3. Click Video Call. Comment ----- The application crashes and then reconnects to Yahoo, the friend's list is displayed again. I've tried clicking on video call option for two friends and have hit the same problem. So far I've reproduced it thrice - twice with same friend and once with another.
Package: telepathy-haze-0.4.0-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Selected friend in Yahoo messenger friend list. 2. Right click, select Video Call. 3. BOOM!
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Backtrace analysis found this bug to be similar to bug #649205, closing as duplicate. Bugs which were found to be similar to this bug: bug #649205, bug #656185 This comment is automatically generated. *** This bug has been marked as a duplicate of bug 649205 ***