Date: Tue, 7 Sep 2004 04:16:40 GMT From: Axel Gonzalez <loox@e-shell.net> To: freebsd-gnats-submit@FreeBSD.org Subject: ports/71446: (KDE) KLoginManager goes to 100% CPU on amd64 Message-ID: <200409070416.i874GeSb001876@www.freebsd.org> Resent-Message-ID: <200409070420.i874KJ0N033507@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 71446 >Category: ports >Synopsis: (KDE) KLoginManager goes to 100% CPU on amd64 >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-ports-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Sep 07 04:20:19 GMT 2004 >Closed-Date: >Last-Modified: >Originator: Axel Gonzalez >Release: 6.0-CURRENT >Organization: >Environment: FreeBSD moonlight.e-shell.net 6.0-CURRENT FreeBSD 6.0-CURRENT #8: Mon Sep 6 01:37:24 CDT 2004 root@moonlight.e-shell.net:/usr/obj/usr/src/sys/LXAMD64 amd64 >Description: On KDE LoginManager when you try to make any change, and the click Apply (or Ok), cpu usage goes to 100%, with the KLoginManager window not responding anymore. Memory usage seems to remain the same, and changes are not saved after kill the process. Problem is the same logged as user and KDE su, or logged in as root. ports installed: qt-3.3.3 kdelibs-3.3.0_1 kdebase-3.3.0_1 (Was same problem in kde 3.2.3) >How-To-Repeat: Go:System Administration -> Login Manager Change any setting Hit Apply (or Ok) >Fix: no idea >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200409070416.i874GeSb001876>