Date: 27 Feb 2003 12:51:04 -0500 From: Joe Marcus Clarke <marcus@marcuscom.com> To: Robert English <drakcap@pacbell.net> Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Runaway Galeon! Message-ID: <1046368264.305.39.camel@gyros> In-Reply-To: <000b01c2de88$0e44bea0$0701a8c0@desk> References: <000b01c2de88$0e44bea0$0701a8c0@desk>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-EtorG8VUvFbl4AAvLWhG Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Thu, 2003-02-27 at 12:45, Robert English wrote: > I've had a functioning Galeon 1.2.8 (on FreeBSD 4.7 from a buildworld on = Feb > 11, using KDE 3.1), even after the "Xft" upgrade some days ago now, until > last night. After what was apparently a successful run of Galeon, and > shutting down the browser but leaving the KDE desktop running, I left the > terminal for about two hours; when I came back I found the text-terminal > log-in prompt waiting for me - it had spontaneously rebooted itself about > thirty minutes after I left it, judging from the uptime reading I got aft= er > I logged in. After starting another X session and getting my KDE desktop > back, I started Galeon again and it started continuously opening windows = for > itself. Right-clicking on the taskbar and choosing "close all" took it b= ack > to the first window but it would start building up windows again. I have > never had to use the "kill process" option before, but had to with this t= o > get it to stop. (It reached 110 open instances at one point.) >=20 > Mozilla doesn't start at all now - after logging out of KDE I see the err= or > message that Mozilla left, which is the same one that others have been > getting about no open window found. >=20 > I'm in the process of reinstalling Mozilla, which will take a couple of > hours of compile time, but don't know if this is going to fix the problem= or > not. I'll report back with what I find. >=20 > Anyone else have this happen? I recall someone reported this a while ago, but I was never able to reproduce it, and I think a rebuild of the relevant ports corrected the problem. You may want to comb the gnome@ archives. Joe >=20 >=20 >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message --=20 PGP Key : http://www.marcuscom.com/pgp.asc --=-EtorG8VUvFbl4AAvLWhG Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQA+XlAIb2iPiv4Uz4cRArd+AJ9oNla+DdIaP3Wb5aC5XvvtANIjfQCgnxgi Apm4bWUvFeNsEbaVO7Qerhk= =6/8I -----END PGP SIGNATURE----- --=-EtorG8VUvFbl4AAvLWhG-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1046368264.305.39.camel>