Date: Tue, 29 May 2012 10:32:55 -0500 From: "Conrad J. Sabatier" <conrads@cox.net> To: Daniel Nebdal <dnebdal@gmail.com> Cc: freebsd-ports@freebsd.org Subject: Re: Continual error dialogs since upgrading some ports Message-ID: <20120529103255.6ccb8c6c@serene.no-ip.org> In-Reply-To: <CA%2Bt49PLJpXzAdCdc3QN3ta4ZO7wYXmuqh328RtzWyuNoQpOPqA@mail.gmail.com> References: <20120528052938.7a449c63@serene.no-ip.org> <CA%2Bt49PLJpXzAdCdc3QN3ta4ZO7wYXmuqh328RtzWyuNoQpOPqA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 29 May 2012 16:04:40 +0200 Daniel Nebdal <dnebdal@gmail.com> wrote: > On Mon, May 28, 2012 at 12:29 PM, Conrad J. Sabatier > <conrads@cox.net> wrote: > > Since upgrading a number of ports yesterday, I'm now being hounded > > continually with error dialogs popping up with the message: > > > > "An internal system error has occurred > > > > A problem that we were not expecting has occurred. > > Please report this bug in your distribution bugtracker with > > the error description." > > > > The dialog is adorned with that little "lifesaver" image used by the > > GNOME help system, as well as a "Show details" button. > > =A0Unfortunately, the details provided are a little vague, popping up > > another dialog showing the same message as the initial dialog, but > > with a "More details" dropdown button. =A0"More details" provides > > only the following: > > > > "The backend exited unexpectedly. =A0This is a serious error as the > > spawned backend did not complete the pending transaction." > > > > Nowhere to be seen is any mention of exactly what program is > > spawning these error dialogs. =A0Anyone ever seen these and/or have > > any idea where they might be coming from? > > > > Thanks! >=20 >=20 > It seems to be a PackageKit thing - do you have a "check for new > updates"-applet running, or something like that? > (ref http://forums.freebsd.org/showthread.php?t=3D23959 ) >=20 Hmm, not sure about that. Will have to check. Thanks for the link, though. I'm currently running vtwm, and haven't seen the error, so it's definitely something going on in my GNOME environment. We'll see what I can find out. --=20 Conrad J. Sabatier conrads@cox.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120529103255.6ccb8c6c>