Bug#295175: xfree86-common faild to purge, breaking buildds in interesting ways

2005-02-13 Thread Adam Conrad
Package: xfree86-common Version: 4.3.0.dfsg.1-11 Severity: grave xfree86-common fails to purge, leaving it in state 'pi', and breaking builds left, right, and center. A transcript of the puge, with -x follows: lucifer:~# dpkg --purge xfree86-common (Reading database ... 7815

Bug#234067: xrestop does not catch all memory

2005-02-13 Thread Amit Shah
Hi Alban, > This is a followup for: > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=234067 > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=245026 > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=279940 [...] > Amit , i have found your kde bug report (though it was not an > easy task by i

Re: Joystick & xserver-xfree86/unstable?

2005-02-13 Thread Hanno Mueller
Hi, Do you know of an alternative? Maybe a user space program that converts joystick parameters to XF86 mouse input? Heh, that sums up the problem with X. People would rather go try something else than fix things. Well, when it comes to X, I'm more user than developer and don't really feel that

Running startx doesn't run Xsession

2005-02-13 Thread Jeffrey Chimene
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, The following was cross-posted on debian-x For some reason, the /etc/X11/xsession (4.3.0.dfsg.1-10)) stuff isn't running. For example, the ssh agent isn't started. To test this, I modified the file /etc/X11/xinit/xinitrc as follows: #!/bin/sh # $Xor

X Strike Force XFree86 SVN commit: r2194 - trunk/debian

2005-02-13 Thread X Strike Force SVN Repository Admin
Author: branden Date: 2005-02-13 04:02:31 -0500 (Sun, 13 Feb 2005) New Revision: 2194 Modified: trunk/debian/CHANGESETS trunk/debian/changelog Log: (cosmetic) Fix character-transposition typo. Modified: trunk/debian/CHANGESETS ===

Bug#289328: Bug #289328 - xserver-xfree86: DRI disabled despite it would work

2005-02-13 Thread Fabien COUTANT
On Sunday, 13 February 2005, you ([EMAIL PROTECTED]) wrote: > Would you mind providing seom more details ? of course, here we go... > i saw an error message: > > (II) TDFX(0): [dri] VideoRAM = 16384, VirtualXres = 1408, VirtualYres= 1056, > (WW) TDFX(0): [dri] To use DRI, with a 16Mb Voodoo 3 or