Date: Mon, 9 Feb 2004 11:13:32 -0800 (PST) From: Doug White <dwhite@gumbysoft.com> To: Jesse Guardiani <jesse@wingnet.net> Cc: freebsd-current@freebsd.org Subject: Re: kdesu crash under 5.2-RELEASE with libkse via libmap.conf Message-ID: <20040209110901.W48001@carver.gumbysoft.com> In-Reply-To: <200402071438.21289.jesse@wingnet.net> References: <bvs595$p9e$1@sea.gmane.org> <20040206185032.L20313@carver.gumbysoft.com> <200402071438.21289.jesse@wingnet.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 7 Feb 2004, Jesse Guardiani wrote: > On Friday 06 February 2004 21:52, Doug White wrote: > > On Wed, 4 Feb 2004, Jesse Guardiani wrote: > > > If I run this: > > > > > > /usr/local/bin/kdesu --nonewdcop '/usr/local/bin/kcmshell clock --lang > > > en_US' I tried this on my amd64 -CURRENT box and did experience some unusual behavior. After closing the clock change dialog, the process stuck in select(). I kill -9'd it and it went into a 100% CPU loop. Another kill -9 made it go away. Considering this works when called from the GUI, either from the clock's context menu or the Control Center, I'm not inclined to track this further, and defer it to a KDE bug. I'm using libpthread with everything, rebuilt on Friday. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040209110901.W48001>