Bug#22506: Package Status, Shipping Number : 56PT9gn36W
Information Here: cov2pa.com/track.php?cg=1&c=c Those news announcers aren't practicing shaving next to the police station right at this time.
Bug#291404: xserver-xfree86: DRIScreenInit fails with dual seession setup (radeon)
On Wed, 2005-01-19 at 10:06 +0100, Dominique Dumont wrote: > > With a Radeon 9200, kdm and a dual session setup, DRIscreenInit fails: > (EE) RADEON(0): [dri] DRIScreenInit failed. Disabling DRI. Is this the case for both sessions? It's a limitation of the DRI that it can only be enabled on one session at a time. > As a consequence, a lot of games are unplayable. For instance > gravitywars is very slow and the load of my machine goes up to 20. That sounds weird; for one, the DRI mostly makes a difference for OpenGL, does gravitywars use that? Also, a load of 20 corresponds to 20 processes using as much CPU as they get, which would surprise me with gravitywars under any circumstances. -- Earthling Michel DÃnzer | Debian (powerpc), X and DRI developer Libre software enthusiast| http://svcs.affero.net/rm.php?r=daenzer
Processed: (no subject)
Processing commands for [EMAIL PROTECTED]: > severity 291439 important Bug#291439: gimp: Attempting to save an XPM file fails Severity set to `important'. > reassign 291439 libxpm4 Bug#291439: gimp: Attempting to save an XPM file fails Bug reassigned from package `gimp' to `libxpm4'. > merge 286164 291439 Bug#286164: XPM security fix breaks writing XPM files with absolute path names Bug#291439: gimp: Attempting to save an XPM file fails Merged 286164 291439. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#284764: XFree86 -configure crash
dear People: thank you for your reply. In the meantime, I decided to update my broken system, by doing: dpkg --get-selections on a newly updated Debian system that had a working desk top and dpkg --set-selections on on the broken machine . I guess that this forced the instruction " dpkg-reconfigure -phigh xserver-xfree86" to be performed. my system is now working and the screen looks good. again, thank you for your reply. sandy basickes On Thu, Jan 20, 2005 at 02:47:22AM -0500, Branden Robinson wrote: > retitle 284764 xserver-xfree86: server crashes when "-configure" option > supplied > tag 284764 + woody upstream > thanks > > On Wed, Dec 08, 2004 at 04:03:01AM -0500, sandy basickes wrote: > > Package: XFree86 > > Version: 4.1.0.1 > > > > Linux test 2.4.27 #4 SMP Wed Nov 24 00:10:16 EST 2004 i686 unknown > > 12/08/04 > [...] > > XFree86 Version 4.1.0.1 / X Window System > > (protocol Version 11, revision 0, vendor release 6510) > > Release Date: 21 December 2001 > > If the server is older than 6-12 months, or if your card is > > newer than the above date, look for a newer version before > > reporting problems. (See http://www.XFree86.Org/FAQ) > > In my experience, the -configure option simply does not work well in that > version of XFree86. > > I think it may be somewhat improved in later versions, but still not enough > that I'd trust it. > > I recommend using the xserver-xfree86 debconf interface to configure the X > server, for instance by running the following command as root: > > dpkg-reconfigure -phigh xserver-xfree86 > > I am not sure, however, that the Trident Cyber/BladeXP (the model of > display adapter you appear to have) is well-supported by XFree86 4.1.0. > > I do know that, according to http://www.xfree86.org/4.1.0/Status33.html#33 >, it is *supposed* to be > supported. > > You would, therefore, choose the "trident" driver when prompted for your > X server driver. > > -- > G. Branden Robinson|I must confess to being surprised > Debian GNU/Linux |by the magnitude of incompatibility > [EMAIL PROTECTED] |with such a minor version bump. > http://people.debian.org/~branden/ |-- Manoj Srivastava -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#22506: Fw: shaw
Had this link sent to me on my palm pilot. http://www.dontletthisonepassyouby.com/trave1.html You can just about download any CD album you want to. Not to mention console games and dvd's. I was able to find at least 77 of my favorite CD's Once you've seen it get ahold of me, I want to hear your reaction - you'll go batty I know it. They walk you through the entire process of burning your choices to CD. Upon going over the movie section, you know how I like movies, they have stuff in here still in theates you can download and play on your DVD player - it's nuts. I'll talk to you later. Harvey
Bug#281286: xserver-xfree86: Starting X with USB mouse unpluged hardlocks system when Option "AGPMode" "4" used.
On Thu, 2005-01-20 at 02:27 -0500, Branden Robinson wrote: > On Sun, Jan 16, 2005 at 05:05:59PM -0500, Michel DÃnzer wrote: > > On Sun, 2005-01-09 at 14:52 -0500, Slaven Peles wrote: > > > > > > Perhaps it would be a good idea to put in X documentation that options > > > such as > > > AGPMode, AGPFastWrite and EnablePageFlip are experimental and may cause > > > unpredictable problems when nondefault values are used. > > > > Where did you get the idea that this is _not_ the case for at least the > > majority of X server driver options? There's usually a reason why > > something is an option with a certain default value. > > I didn't think it was quite that bad. *Except* for those in the "Device" > section, most options I see documented in XF86Config-4(5x) shouldn't cause > hardware lockups. I did say 'X server *driver*'. -- Earthling Michel DÃnzer | Debian (powerpc), X and DRI developer Libre software enthusiast| http://svcs.affero.net/rm.php?r=daenzer
Bug#284581: WSXGA screen size missing in config (1680x1050)
i don't have a ModeLine in my XF86Config-4 at all, i've simply added "1680x1050" to the beginning of the Modes lines which are used. unfortunately 1680x1050 doesn't appear to be a VESA standard size, i can only find "GTF" ModeLines for this size of screen. would that be an acceptable substitute, or not? cheers, -duncan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#291404: xserver-xfree86: DRIScreenInit fails with dual seession setup (radeon)
Package: xserver-xfree86 Version: 4.3.0.dfsg.1-10 Severity: normal Hello With a Radeon 9200, kdm and a dual session setup, DRIscreenInit fails: (EE) RADEON(0): [dri] DRIScreenInit failed. Disabling DRI. As a consequence, a lot of games are unplayable. For instance gravitywars is very slow and the load of my machine goes up to 20. If I set only one session, DRI works fine. Here's my /etc/kde3/kdm/Xserver config to set up dual session: :0 [EMAIL PROTECTED] /usr/X11R6/bin/X -nolisten tcp :1 [EMAIL PROTECTED] /usr/X11R6/bin/X -nolisten tcp :1 Feel free to contact me if you need any information Thanks -- Package-specific info: Contents of /var/lib/xfree86/X.roster: xserver-xfree86 xserver-xorg /etc/X11/X target unchanged from checksum in /var/lib/xfree86/X.md5sum. X server symlink status: lrwxrwxrwx 1 root root 20 2004-12-18 13:31 /etc/X11/X -> /usr/bin/X11/XFree86 -rwxr-xr-x 1 root root 1745740 2004-12-15 20:19 /usr/bin/X11/XFree86 Contents of /var/lib/xfree86/XF86Config-4.roster: xserver-xfree86 VGA-compatible devices on PCI bus: :03:00.0 VGA compatible controller: ATI Technologies Inc RV280 [Radeon 9200] (rev 01) /etc/X11/XF86Config-4 does not match checksum in /var/lib/xfree86/XF86Config-4.md5sum. XFree86 X server configuration file status: lrwxrwxrwx 1 root root 21 2004-10-13 20:47 /etc/X11/XF86Config-4 -> XF86Config-4.mono.dri Contents of /etc/X11/XF86Config-4: # XF86Config-4 (XFree86 X server configuration file) generated by dexconf, the # Debian X Configuration tool, using values from the debconf database. # # Edit this file with caution, and see the XF86Config-4 manual page. # (Type "man XF86Config-4" at the shell prompt.) # # This file is automatically updated on xserver-xfree86 package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xfree86 # package. # # If you have edited this file but would like it to be automatically updated # again, run the following commands as root: # # cp /etc/X11/XF86Config-4 /etc/X11/XF86Config-4.custom # md5sum /etc/X11/XF86Config-4 > /var/lib/xfree86/XF86Config-4.md5sum # dpkg-reconfigure xserver-xfree86 Section "Files" FontPath"unix/:7100"# local font server # if the local font server has problems, we can fall back on these FontPath"/usr/lib/X11/fonts/Type1" # FontPath"/usr/lib/X11/fonts/CID" FontPath"/usr/lib/X11/fonts/Speedo" FontPath"/usr/lib/X11/fonts/misc" FontPath"/usr/lib/X11/fonts/100dpi" FontPath"/usr/lib/X11/fonts/75dpi" EndSection Section "Module" Load"GLcore" Load"bitmap" Load"dbe" Load"ddc" Load"dri" Load"extmod" Load"freetype" Load"glx" Load"int10" Load"record" Load"speedo" Load"type1" Load"vbe" EndSection Section "InputDevice" Identifier "Generic Keyboard" Driver "keyboard" Option "CoreKeyboard" Option "XkbRules" "xfree86" Option "XkbModel" "pc104" Option "XkbLayout" "us" Option "XkbOptions""compose:rwin" EndSection Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" Option "CorePointer" Option "Device""/dev/psaux" Option "Protocol" "ImPS/2" Option "ZAxisMapping" "4 5" EndSection Section "InputDevice" Identifier "LIRC-Mouse" Driver "mouse" Option "Device" "/dev/lircm" Option "Protocol" "IntelliMouse" Option "SendCoreEvents" Option "Buttons" "5" Option "ZAxisMapping" "4 5" EndSection Section "Device" Identifier "ATI Technologies, Inc. Radeon RV280 [Radeon 9200]" # With this drivers, X loads radeon, ati and then re-load radeon # and gives lower fps with glxgears (1600 instead of 200fps) # Driver "radeon" Driver "ati" BusId "PCI:03:00:0" Screen 0 #Driver "ati" Option "AGPMode" "4" # always hangs kernel #Option "AGPFastWrite" "Yes" # Option "UseFBDev" "on" Option "EnablePageFlip""Yes" # VideoRam1184 EndSection Section "Monitor" Identifier "Hercules 920Pro" HorizSync 30-80 VertRefresh 50-75 Option "DPMS" EndSection Section "Screen" Identifier "Default Screen" Device "ATI Technologies, Inc. Radeon RV280 [Radeon 9200]" Monitor "Hercules 920Pro" DefaultDepth24
Bug#281050: xserver-common: [i810] Memory leak
Hello, > X footprint keeps growing because of repeatable memory allocations for the > cursor > and gdk_cursor_unref() failures to free that memory. However, this doesn't > happen > with all types of cursors. Only *animated* ones are affected (I base > this hypothesis on my tests). Indeed, I switched to an unanimated cursor theme as a workaround, and the problem seems to have gone away. I owe you one! -- Gintautas Miliauskas signature.asc Description: =?iso-8859-2?Q?=A9i?= =?iso-8859-2?Q?_lai=B9ko?= dalis yra =?iso-8859-2?Q?pasira=B9yta?= skaitmeniniu =?iso-8859-4?Q?b=FEdu?=
Bug#291137: /usr/X11R6/bin/luit: luit sometimes doesn't restore terminal settings or hangs
On Wed, Jan 19, 2005 at 02:58:44PM +0500, "Alexander E. Patrakov" <[EMAIL PROTECTED]> wrote: > > and exits. It looks like there is a race condition inside luit. It is > > likely an upstream issue because similar behaviour can be demonstrated ona > > fedora 3 system. > > Sounds suspiciously similar to this bug: > > http://bugs.xfree86.org/show_bug.cgi?id=1093 > > Does the patch from there help? Indeed, sounds very suspiciously like that bug (and thomas dickey stil assumes that the race in ncurses is a bug elsehwere, argh). I'll try to apply the patch and build luit, but cannot say when I am able to do so :( -- The choice of a -==- _GNU_ ==-- _ generation Marc Lehmann ---==---(_)__ __ __ [EMAIL PROTECTED] --==---/ / _ \/ // /\ \/ / http://schmorp.de/ -=/_/_//_/\_,_/ /_/\_\ XX11-RIPE -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#281050: xserver-common: [i810] Memory leak
On Thu, Jan 20, 2005 at 01:00:02PM +0200, Modestas Vainius wrote: > After a few hours of investigation I've tracked down this bug. At > least I've discovered what code causes Xserver to leak memory, when > the bug is "exploited" by gpdf. It's as simple as the following: Nice work. It explains why I discovered the problem so often by running Firefox, since Firefox will change to the (animated) wait-cursor lots of times. > I've made a simple gtk program, which starts executing the code above > infinite number times once you press the "Test memleak!" button (thus > you will need to use CTRL+C or `kill` to terminate the program). Here > it's the step-by-step guide to reproduce the memleak: Yup, running for 30 seconds its enough to bring my system to swapping, and pmap shows: [EMAIL PROTECTED] ~]# pmap -x $(pidof X) [...] 0a512000 360896 - - - rw---[ anon ] [...] With that I guess that bugs should be fixed soon, thanks again. Regards, Matthias pgpQXcxNaGdwd.pgp Description: PGP signature
Bug#281050: xserver-common: [i810] Memory leak
Hello,
After a few hours of investigation I've tracked down this bug. At least I've
discovered what code causes Xserver to leak memory, when the bug is
"exploited" by gpdf. It's as simple as the following:
cursor = gdk_cursor_new_for_display(display, GDK_WATCH);
// ... //
gdk_cursor_unref(cursor);
This code gets repeated approx. twice as many times as there are pages in the
pdf (when processing both bookmarks and thumbnails). While this is the bug in
the gpdf itself (the cursor should not be set so many times), it reveals
the bug in the X server. X footprint keeps growing because of repeatable
memory allocations for the cursor and gdk_cursor_unref() failures to free that
memory. However, this doesn't happen with all types of cursors. Only
*animated* ones are affected (I base this hypothesis on my tests). Memory
occupied by static cursors gets freed properly by the gdk_cursor_unref()
routine. This explains why other people are not suffering from this bug.
I've made a simple gtk program, which starts executing the code above infinite
number times once you press the "Test memleak!" button (thus you will need to
use CTRL+C or `kill` to terminate the program). Here it's the step-by-step
guide to reproduce the memleak:
1. Make sure your "watch" cursor is the animated one or change the argument 2
of the gdk_cursor_new_for_display() accordingly to the cursor which is
animated in the theme you're using. If neither is animated, you can obtain one
from [1] or other source. I extracted the "watch" cursor from this theme and
put it on my web site[2]. Simply place it into ~/.icons//cursors/watch This should be
enough to reproduce the bug without restarting X.
2. Compile memleak.c from [3] with the following command (you will need
libgtk2.0-dev and its dependences for this):
gcc memleak.c -o memleak -I/usr/include/gtk-2.0 -I/usr/include/glib-2.0
-I/usr/lib/gtk-2.0/include -I/usr/lib/glib-2.0/include
-I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -L/usr/lib -lgtk-x11-2.0
and start the program.
3. Press the "Test memleak!" button in the GUI and observe X server memory
usage ("RES" field with `top`). If you have a fast pc, X should consume
hundreds MBs of memory *very* quickly.
4. To kill the program use CTRL+C or `kill` (it's my first gtk program ever,
so I haven't invested more time in making termination more sophisticated)
Another interesting thing is that X seems to reuse the allocated memory for
sequent cursor allocations in other programs (like another instance of
`memleak`) once the program triggering the bug gets terminated. Test this by
running several instances of `memleak` one after another.
So for now till someone with more knowlegde of XFree86 code fixes the bug a
simple workaround is to avoid animated cursors. There may be a bug in
gdk_cursor_unref() too, I haven't checked the code. In any case, I think it's
a big (security?) problem in the X server code, because any malicious app can
make X server (which is generally running as root on most systems with DM)
use large amounts of memory by repeatedly allocating memory for the cursor
and not freeing it aftwerwards.
It would be great if someone could test this test case on Xorg. Lots of
distros include animated watch cursors by default these days, and if these
are big, lots of people might be suffering from this bug.
The "fixed" gpdf (with the offensive code commented out) is available here[4]
(the binary for i386, provided there, is compiled w/o optimizations and
debugging symbols are unstripped)
Related bugs in other locations (neither of which is marked as fixed):
https://bugs.freedesktop.org/show_bug.cgi?id=1043
http://bugs.gentoo.org/show_bug.cgi?id=31982
[1]. http://www.kde-look.org/content/show.php?content=18214
[2]. http://mif.vu.lt/~mova3971/xf/watch
[3]. http://mif.vu.lt/~mova3971/xf/memleak.c
[4]. http://mif.vu.lt/~mova3971/xf/gpdf
pgpvX8xz0JQUj.pgp
Description: PGP signature
Bug#291353: xserver-xfree86: locks up
Package: xserver-xfree86 Version: 4.3.0.dfsg.1-10 Severity: normal Sorry about this bad bug report, but perhaps you can make some sense of it... Sometimes around November, I updated the Xserver and after that it started to lock up once per day (previously I rarely had any problems with it and when I did, it crashed completly). The keyboard remained locked so I could not switch to the console for killing the Xserver and restarting it. I noticed that I often got a white pixel randomly added to my xterm windows so I thought it might be a too-high dotclock problem of some kind (I believe nvidia's drivers complained about that when I once tried them). Lowering the resolution to 1024x768 did indeed help and the locking stopped. Now I updated to the latest version of Xfree86-server in sarge and it is even worse when it was previously. When starting firefox and switching between tabs or just using a visual bell in a xterm console often causes the Xserver to lock. The mouse pointer still works, but that is all. When it is locked, it seems to be spinning with 100% CPU usage. I can not have the X server running for more than a few minutes before it locks up. Unfortunally I have no record of what X server version that did work. -- Package-specific info: Contents of /var/lib/xfree86/X.roster: xserver-xfree86 /etc/X11/X target unchanged from checksum in /var/lib/xfree86/X.md5sum. X server symlink status: lrwxrwxrwx 1 root root 20 2003-06-18 19:15 /etc/X11/X -> /usr/bin/X11/XFree86 -rwxr-xr-x 1 root root 1745740 2004-12-15 20:19 /usr/bin/X11/XFree86 Contents of /var/lib/xfree86/XF86Config-4.roster: xserver-xfree86 VGA-compatible devices on PCI bus: :02:00.0 VGA compatible controller: nVidia Corporation NVCrush11 [GeForce2 MX Integrated Graphics] (rev b1) /var/lib/xfree86/XF86Config-4.md5sum does not exist. XFree86 X server configuration file status: -rw-r--r-- 1 root root 6473 2004-12-27 15:18 /etc/X11/XF86Config-4 Contents of /etc/X11/XF86Config-4: Section "ServerLayout" Identifier "XFree86 Configured" Screen 0 "Screen0" 0 0 InputDevice"Keyboard0" "CoreKeyboard" InputDevice"PS/2 Mouse" "CorePointer" EndSection Section "ServerFlags" Option "AllowMouseOpenFail" "true" EndSection Section "Files" RgbPath "/usr/X11R6/lib/X11/rgb" ModulePath "/usr/X11R6/lib/modules" FontPath "unix/:7101" FontPath "/usr/X11R6/lib/X11/fonts/misc:unscaled" FontPath "/usr/X11R6/lib/X11/fonts/misc" FontPath "/usr/X11R6/lib/X11/fonts/75dpi:unscaled" FontPath "/usr/X11R6/lib/X11/fonts/75dpi" FontPath "/usr/X11R6/lib/X11/fonts/100dpi:unscaled" FontPath "/usr/X11R6/lib/X11/fonts/100dpi" FontPath "/usr/X11R6/lib/X11/fonts/Speedo" FontPath "/usr/X11R6/lib/X11/fonts/PEX" # Additional fonts: Locale, Gimp, TTF... FontPath "/usr/X11R6/lib/X11/fonts/cyrillic" # FontPath "/usr/X11R6/lib/X11/fonts/latin2/75dpi" # FontPath "/usr/X11R6/lib/X11/fonts/latin2/100dpi" # True type and type1 fonts are also handled via xftlib, see /etc/X11/XftConfig! FontPath "/usr/X11R6/lib/X11/fonts/Type1" FontPath "/usr/share/fonts/ttf/western" FontPath "/usr/share/fonts/ttf/decoratives" FontPath "/usr/share/fonts/truetype/openoffice" FontPath "/usr/X11R6/lib/X11/fonts/defoma/CID" FontPath "/usr/X11R6/lib/X11/fonts/defoma/TrueType" EndSection Section "Module" Load "ddc" # ddc probing of monitor Load "dbe" Load "extmod" #Load "glx" Load "dri" Load "GLcore" Load "bitmap" # bitmap-fonts Load "speedo" Load "type1" Load "freetype" Load "record" EndSection Section "InputDevice" Identifier "Keyboard0" Driver "keyboard" Option "CoreKeyboard" Option "XkbRules" "xfree86" Option "XkbModel" "pc105" Option "XkbLayout" "se" Option "XkbVariant" "nodeadkeys" EndSection Section "InputDevice" Identifier "Serial Mouse" Driver "mouse" Option "Protocol" "Microsoft" Option "Device" "/dev/ttyS0" Option "Emulate3Buttons" "true" Option "Emulate3Timeout" "70" Option "SendCoreEvents" "true" EndSection Section "InputDevice" Identifier "PS/2 Mouse" Driver "mouse" Option "Protocol" "ImPS/2" Option "Device" "/dev/psaux" Option "Emulate3Buttons" "false" Option "Emulate3Timeout" "70" Option "SendCoreEvents" "true" Option "ZAxisMapping" "4 5" EndSection Section "InputDevice" Identifier "USB Mouse" Driver "mouse" Option "Device""/dev/input/mice" Option "SendCoreEvents"
Bug#285396: [ARM] wide chars don't work
[I am not subscribed to debian-arm.] On Tue, Jan 11, 2005 at 11:03:59PM +, Phil Blundell wrote: > On Tue, 2005-01-11 at 12:37 -0500, Branden Robinson wrote: > > Here are his remarks, recast a bit from IRC-speak into something more > > conventional. > > > > GCC on ARM is doing something different from every other C compiler I've > > seen. It may not deviate from what the C specification allows, but it > > appears to deviate from common practice. The ARM folks would find code > > would work with fewer problems if they fixed GCC to behave like other C > > compilers do. Having an array of structs of a byte each usually forces > > 16 bit alignment only on other compilers I've seen. > > Jim is correct. This behaviour of the ARM compiler seemed like a good > idea in 1988, but subsequent experience has shown that it was a mistake > to pad structs in this way. > > Changing the default behaviour of the compiler definitely would result > in ABI breakage for some programs. We plan to take care of this, and a > variety of other historical goofs, by switching to the new ARM "EABI". > This change will involve a flag day at some point during the next Debian > release cycle, but will result in better performance (by a factor of > more than 10 for some code) and greater compatibility with other > architectures. > > > I'm also curious to know if xterm has always had this problem on Debian > > ARM, or if it has cropped up only with recent revisions of GCC. Can anyone > > tell me? > > I don't have any direct experience of the bug, but from the description > I've seen it sounds like it would always have been this way. GCC's > behaviour certainly hasn't changed recently. Since the discussion seems to have died down: I am reaching the conclusion that I'm going to need to apply the patch more or less as written. It can have a lot of #if guards around it, but it sounds like for GNU C and the ARM architecture until this new "EABI" happens[1], this is just something that will have to be done if we want X to work right on Debian/ARM. Jim, do I read this correctly? [1] ...even then it would no doubt have to be kept around for a while, thanks to people not migrating to the new ABI. -- G. Branden Robinson|Those who fail to remember the laws Debian GNU/Linux |of science are condemned to [EMAIL PROTECTED] |rediscover some of the worst ones. http://people.debian.org/~branden/ |-- Harold Gordon signature.asc Description: Digital signature
Bug#284764: XFree86 -configure crash
retitle 284764 xserver-xfree86: server crashes when "-configure" option supplied tag 284764 + woody upstream thanks On Wed, Dec 08, 2004 at 04:03:01AM -0500, sandy basickes wrote: > Package: XFree86 > Version: 4.1.0.1 > > Linux test 2.4.27 #4 SMP Wed Nov 24 00:10:16 EST 2004 i686 unknown > 12/08/04 [...] > XFree86 Version 4.1.0.1 / X Window System > (protocol Version 11, revision 0, vendor release 6510) > Release Date: 21 December 2001 > If the server is older than 6-12 months, or if your card is > newer than the above date, look for a newer version before > reporting problems. (See http://www.XFree86.Org/FAQ) In my experience, the -configure option simply does not work well in that version of XFree86. I think it may be somewhat improved in later versions, but still not enough that I'd trust it. I recommend using the xserver-xfree86 debconf interface to configure the X server, for instance by running the following command as root: dpkg-reconfigure -phigh xserver-xfree86 I am not sure, however, that the Trident Cyber/BladeXP (the model of display adapter you appear to have) is well-supported by XFree86 4.1.0. I do know that, according to http://www.xfree86.org/4.1.0/Status33.html#33 >, it is *supposed* to be supported. You would, therefore, choose the "trident" driver when prompted for your X server driver. -- G. Branden Robinson|I must confess to being surprised Debian GNU/Linux |by the magnitude of incompatibility [EMAIL PROTECTED] |with such a minor version bump. http://people.debian.org/~branden/ |-- Manoj Srivastava signature.asc Description: Digital signature
Bug#284965: marked as done (Problem with XF86Config )
Your message dated Thu, 20 Jan 2005 02:57:26 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#284965: X11/Mouse Problems Solved has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 9 Dec 2004 20:55:20 + >From [EMAIL PROTECTED] Thu Dec 09 12:55:19 2004 Return-path: <[EMAIL PROTECTED]> Received: from adams.patriot.net [209.249.176.2] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1CcVJn-0007y9-00; Thu, 09 Dec 2004 12:55:19 -0800 Received: from localhost ([EMAIL PROTECTED]) by adams.patriot.net (8.11.6/8.11.6) with ESMTP id iB9KtIg07843 for <[EMAIL PROTECTED]>; Thu, 9 Dec 2004 15:55:18 -0500 X-Authentication-Warning: adams.patriot.net: alan owned process doing -bs Date: Thu, 9 Dec 2004 15:55:18 -0500 (EST) From: Alan McConnell <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Problem with XF86Config Message-ID: <[EMAIL PROTECTED]> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2004_03_25 X-Spam-Level: Package: xserver-xfree86 Version: (I don't know the Version, since I have no --status option on my dpkg program) I have recently installed Debian Woody, after running Mandrake for several years and then experimenting with Red Hat. My one problem with my Debian installation is my X11 display, and I am convinced that the problem lies in my /etc/X11/XF86Config-4, which I have rebuilt many times, with dpkg-reconfigure, using the parameters which I have taken from my Red Hat XF86Config; X11 worked fine in Red Hat. I have an nVidia card and an AOC LM720 monitor. As instructed, I append below my log file of my latest attempt. I may be doing something wrong; any suggestions or assistance will be greatly appreciated. Alan McConnell (start) This is a pre-release version of XFree86, and is not supported in any way. Bugs may be reported to XFree86@XFree86.Org and patches submitted to [EMAIL PROTECTED] Before reporting bugs in pre-release versions, please check the latest version in the XFree86 CVS repository (http://www.XFree86.Org/cvs) XFree86 Version 4.1.0.1 / X Window System (protocol Version 11, revision 0, vendor release 6510) Release Date: 21 December 2001 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/FAQ) Build Operating System: Linux 2.6.9-rc1 i686 [ELF] Module Loader present (==) Log file: "/var/log/XFree86.0.log", Time: Thu Dec 9 14:58:17 2004 (==) Using config file: "/etc/X11/XF86Config-4" Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) ServerLayout "Default Layout" (**) |-->Screen "Default Screen" (0) (**) | |-->Monitor "AOC LM720" (**) | |-->Device "Generic Video Card" (**) |-->Input Device "Generic Keyboard" (**) Option "XkbRules" "xfree86" (**) XKB: rules: "xfree86" (**) Option "XkbModel" "pc104" (**) XKB: model: "pc104" (**) Option "XkbLayout" "us" (**) XKB: layout: "us" (==) Keyboard: CustomKeycode disabled (**) |-->Input Device "Configured Mouse" (**) |-->Input Device "Generic Mouse" (**) FontPath set to "unix/:7100,/usr/lib/X11/fonts/misc,/usr/lib/X11/fonts/cyrillic,/usr/lib/X11/fonts/100dpi/:unscaled,/usr/lib/X11/fonts/75dpi/:unscaled,/usr/lib/X11/fonts/Type1,/usr/lib/X11/fonts/Speedo,/usr/lib/X11/fonts/100dpi,/usr/lib/X11/fonts/75dpi" (==) RgbPath set to "/usr/X11R6/lib/X11/rgb" (==) ModulePath set to "/usr/X11R6/lib/modules" (--) using VT number 7 (WW) Cannot open APM (II) Module ABI versions: XFree86 ANSI C Emulation: 0.1 XFree86 Video Driver: 0.4 XFree86 XInput driver : 0.2 XFree86 Server Extension : 0.1 XFree86 Font Renderer : 0.2 (II) Loader running on linux (II) LoadModule: "bitmap" (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a (II) Module bitmap: vendor="The XFree86 Project" compiled for 4.1.0.1, module version = 1.0.0 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, vers
Processed: Re: Bug#284764: XFree86 -configure crash
Processing commands for [EMAIL PROTECTED]: > retitle 284764 xserver-xfree86: server crashes when "-configure" option > supplied Bug#284764: XFree86 -configure crash Changed Bug title. > tag 284764 + woody upstream Bug#284764: xserver-xfree86: server crashes when "-configure" option supplied There were no tags set. Tags added: woody, upstream > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
