From owner-freebsd-ports@FreeBSD.ORG Sun Jun 8 07:57:01 2003 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7430837B401 for ; Sun, 8 Jun 2003 07:57:01 -0700 (PDT) Received: from mail.gmx.net (imap.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 4EC3443F75 for ; Sun, 8 Jun 2003 07:57:00 -0700 (PDT) (envelope-from blueeskimo@gmx.net) Received: (qmail 25970 invoked by uid 65534); 8 Jun 2003 14:56:58 -0000 Received: from dsl-cust-203.openweb.ca (EHLO [64.39.186.203]) (64.39.186.203) by mail.gmx.net (mp025) with SMTP; 08 Jun 2003 16:56:58 +0200 From: Adam To: freebsd-ports@FreeBSD.org Content-Type: text/plain Organization: Message-Id: <1055084216.77753.5.camel@jake> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.4 Date: 08 Jun 2003 10:56:56 -0400 Content-Transfer-Encoding: 7bit Subject: Recent licq weirdness (possible QT problem with mouse click) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Jun 2003 14:57:01 -0000 I've been having some strange 'issues' with licq on my FreeBSD 4.8-STABLE box over the past week or so. Sometimes (seemingly randomly), my licq interface gets incredibly laggy on double-clicking my mouse. For example, double-clicking on a contact to bring up the message dialog takes about 3-4 seconds to finish. Middle-clicking on the contact takes the same amount of time. However, if I right-click on the contact and go to 'Send->Send Message', the message dialog pops up immediately. I tried recompiling licq-base and licq-qt-plugin, but it had no effect. However, restarting X consistently fixed the problem. I spoke with emostar on #licq (irc.freenode.net), and he assured me that no one else has reported this problem. This leads me to believe it might be FreeBSD-specific. Like I said, its only been happening in the last week. Perhaps this is a problem with a recent update of QT? Has anyone else experienced this problem with licq, or other apps with QT interface? Any ideas how to further troubleshoot this? Thanks, -- Adam