From owner-freebsd-ports Sat Jan 26 14:17:12 2002 Delivered-To: freebsd-ports@freebsd.org Received: from freebsd.tekrealm.net (dsl081-247-162.sfo1.dsl.speakeasy.net [64.81.247.162]) by hub.freebsd.org (Postfix) with ESMTP id C36B737B404 for ; Sat, 26 Jan 2002 14:17:09 -0800 (PST) Received: (from root@localhost) by freebsd.tekrealm.net (8.11.6/8.11.4) id g0QMH9232203 for freebsd-ports@freebsd.org; Sat, 26 Jan 2002 14:17:09 -0800 (PST) (envelope-from elitetek@tekrealm.net) Received: (from elitetek@localhost) by freebsd.tekrealm.net (8.11.6/8.11.4av) id g0QMH8632195 for freebsd-ports@freebsd.org; Sat, 26 Jan 2002 14:17:08 -0800 (PST) (envelope-from elitetek@tekrealm.net) X-Authentication-Warning: freebsd.tekrealm.net: elitetek set sender to elitetek@tekrealm.net using -f Date: Sat, 26 Jan 2002 14:17:08 -0800 From: Andrew Stuart To: freebsd-ports@freebsd.org Subject: licq 1.0.4 + qt-qui-1.0.4 Message-ID: <20020126141708.A31997@freebsd.tekrealm.net> Reply-To: elitetek@tekrealm.net Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i X-Virus-Scanned: by AMaViS perl-11 Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I am currious as to why the qt-gui was updated, since it is broken on most freebsd systems. this is also noted in several of the news groups/forums/etc on licq.org all it does when licq loads it, is hits 100% cpu usage, and if you let it sit long enough it will error out, otherwise you have to kill the process. from what i read, this appears to be a problem with qt23, the fix is to use qt3, but alas we only have 2.3. shouldnt this port be marked as broken? until a fix found. (hense also why green dropped maintainership? is because he couldnt get it to work) -- Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message