Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 176082 - gaim quits when trying to open chat window
gaim quits when trying to open chat window
Status: CLOSED DUPLICATE of bug 169631
Product: Fedora
Classification: Fedora
Component: gaim (Show other bugs)
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Warren Togami
Depends On:
  Show dependency treegraph
Reported: 2005-12-19 00:28 EST by Jerry
Modified: 2007-11-30 17:11 EST (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-12-19 22:34:21 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jerry 2005-12-19 00:28:44 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050922 Fedora/1.0.7-1.1.fc4 Firefox/1.0.7

Description of problem:
When I use gaim to chat in AIM mode and click on buddy to upen chat window, gaim exits.  This just started today after I did yum update and several other apps updated.  gaim was not touched directly so i suspect a library or utility changed.

Version-Release number of selected component (if applicable):
latest updates released version

How reproducible:

Steps to Reproduce:
1.Open gaim
2.Select from buddy list 
3.gaim exits

Actual Results:  bombino

Expected Results:  should run

Additional info:
Comment 1 Brandon Amaro 2005-12-19 22:11:20 EST
I have the same problem.  When I launch it from command line, I get this error:
Creating link /home/omega13a/.kde/socket-localhost.localdomain.
can't create mcop directory

I started having problems with GAIM after installing the update packets for KDE
if that is of any help.
Comment 2 Warren Togami 2005-12-19 22:34:21 EST

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

Note You need to log in before you can comment on or make changes to this bug.