Re: KDE Crashing - Sarge

Hi there. I had the same problem. The cause was that I had a half-finished install of the Nvidia GPU drivers, and glx (the module Nvidia uses to "talk 3D" to X) was conflicting with the OpenGL and dri modules, thus not loading and making *all* of KDE's apps to cry on exit. I don't have what have

forcedeth driver always loads

Hey all, I'm trying to set up the binary NVIDIA nforce drivers on a sarge machine. I was successfully able to install the binary drivers for the nforce board, but the forcedeth driver keeps loading on startup, which conflicts with the nvidia ethernet driver. I added a "skip forcedeth" line

Re: xemacs21 package missing in testing

On Mon, 16 Aug 2004 11:54:26 +0200 Patric Ljung <[EMAIL PROTECTED]> wrote: >Hi there, > >when I look at the package listings for xemacs21, xemacs21-bin >it is not present anymore in testing/sarge. Is there any good >reason for it and should I use stable or unstable dists to get it? > >/ Patric > >

xemacs21 package missing in testing

Hi there, when I look at the package listings for xemacs21, xemacs21-bin it is not present anymore in testing/sarge. Is there any good reason for it and should I use stable or unstable dists to get it? / Patric -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble?

Re: dpkg available parse error

Hi, On Mon, Aug 16, 2004 at 11:18:29AM +1000, Lewis Shobbrook wrote: > [...] > Looks like a comma got replaced by a full stop. > > The following error is currently live for unstable... > > [...] > Conflicts: gnome-panel (<= 2.0.0). gnome-core (<< 1.5), gnome-help (<< > 1.5) > Should read ... >