KDE keyboard switching/selection does not work with 4.3.0-0pre1v1 xlibs packages
Hi, when using KDE (current sid packages) with two keyboard layouts (english and german), I have no problems switching between the two of them when using for instance sid's xlibs-4.2.1-9 package. When exchanging it with the current experimental (4.3.0-0pre1v1) packages, it no longer works (it displays the switch but does not change the layout from the english one I defined for it in the XFree config file, i.e. the key strokes are recorded as if the keyboard were an english one when the german layout should be used. Since appearence of the bug depends on the 4.3.0 xlibs packages I sent this report to this mailing list. Best regards, Ralf -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
[no subject]
Good morning sir With this letter, the L.A.S.P. System will inform you then we that we will be present to the Equipe' Hotels fair, from the 28 settmbre to 3 October at Parigi France in the stand N140 padiglione 4 corsia C. We expose the new system M.A.N.T.T.®. System of telescopic coverages isolated with snow melting system incorporated. We manufacture and install covers for: 1.Hotel. 2.Restaurant. 3.Terraces. 4.swimming pool. Your visit will be a lot appreciate. Special jobs upon request In hoping to add you between our customers we augur them good job. Distinti saluti L.A.S.P. System Italia visit ours internet site: http://www.laspsystem.com email: [EMAIL PROTECTED] telephone: 0039-348-2631521
Re: DVI output of Radeon 9200 still doesn't work -- despite newXFree86 4.3 (fwd)
On Mon, 2003-08-25 at 09:59, ERDI Gergo wrote: On Mon, 25 Aug 2003, Michel [ISO-8859-1] Dnzer wrote: On Sat, 2003-08-23 at 22:31, ERDI Gergo wrote: However, using the DVI port of my Radeon 9200, I get no output as soon as XFree86 is started. You may want to try xserver-xfree86-dri-trunk (see http://dri.sourceforge.net/snapshots/README.Debian), which has a CVS snapshot of the radeon driver. Thanks -- I was under the impression that the dri-trunk packages are based on the CVS development between 4.2 and 4.3 (and thus 4.3 would be more up-to-date). That's still true for the woody packages, but hasn't been for a while for the sid packages. I've just tried dri-trunk, and here's what I get: 1. With 4.3.0-0pre1v1 and dri-trunk installed: (II) Module bitmap: vendor=The XFree86 Project compiled for 4.3.0, module version = 1.0.0 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.4 (EE) module ABI minor version (4) is newer than the server's version (3) (II) UnloadModule: bitmap (II) Unloading /usr/X11R6/lib/modules/fonts/libbitmap.a Remove ModulePath /usr/X11R6/lib/modules from your XF86Config-4, it's redundant at best and harmful in this case. The ABI mismatch also indicates that you seem to be using the woody packages. -- Earthling Michel Dnzer \ Debian (powerpc), XFree86 and DRI developer Software libre enthusiast \ http://svcs.affero.net/rm.php?r=daenzer -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
GTK2 thinks X is buggy
Hi, whenever I launch a GTK2 app, it outputs: Gdk-WARNING **: The X server advertises that RENDER support is present, but fails to supply the necessary pixmap support. In other words, it is buggy. I have a Xinerama setup, with a r128 and a TNT2. I'm currently using X4.3-pre, but I think it was already the case with X4.2. Log/config files on request (log says DRI is disabled because of Xinerama, dunno if it's related). Any hint on how to really enable RENDER on my setup ? Thanks, Xav -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#207159: does not take any CorePointer automaticaly
Package: xserver-xfree86 Version: 4.3.0-0pre1v1 Severity: minor Tags: experimental upstream Hello, I tried to make a XF86Config-4 for a system where any time the mouse device changes (see below). To make X always start, I did not want to set a certain device as CorePointer but expected X to choose one, as described in XF86Config-4(5x), line 386. However, it does not choose any but fails to start if the CorePointer option is not set on some device. Next thing I looked for is an option to force X start without a Core input device (I remember there was some) but the manpage does not contain any info about it, not does README.mouse.gz. MfG, Eduard. -- Package-specific info: 01:00.0 VGA compatible controller: nVidia Corporation NV17 [GeForce4 420 Go] (rev a3) 01:00.0 Class 0300: 10de:0175 (rev a3) # Edit this file with caution, and see the XF86Config-4 manual page. # (Type man XF86Config-4 at the shell prompt.) # # If you want your changes to this file preserved by dexconf, only make changes # before the ### BEGIN DEBCONF SECTION line above, and/or after the # ### END DEBCONF SECTION line below. # # To change things within the debconf section, run the command: # dpkg-reconfigure xserver-xfree86 # as root. Also see How do I add custom sections to a dexconf-generated # XF86Config or XF86Config-4 file? in /usr/share/doc/xfree86-common/FAQ.gz. Section Files FontPathunix/:7100# local font server # if the local font server has problems, we can fall back on these FontPath/usr/lib/X11/fonts/100dpi FontPath/usr/lib/X11/fonts/75dpi 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/cyrillic EndSection Section Module LoadGLcore Loadbitmap Loaddbe Loadddc Loaddri Loadextmod Loadfreetype Loadglx Loadint10 Loadrecord Loadspeedo Loadtype1 Loadvbe EndSection Section InputDevice Identifier Generic Keyboard Driver keyboard Option CoreKeyboard Option XkbRules xfree86 Option XkbModel pc105 Option XkbLayout de,ru Option XkbVariantnodeadkeys,phonetic Option XKbOptions grp:alt_shift_toggle EndSection Section InputDevice # for kernel 2.4 Identifier ps2 Driver mouse # Option CorePointer true Option SendCoreEventstrue Option Device/dev/psaux Option Protocol ImPS/2 Option ZAxisMapping 4 5 EndSection Section InputDevice # the old serial mice Identifier ps2gpm Driver mouse Option SendCoreEventstrue Option Device/dev/gpmdata Option Protocol ImPS/2 Option ZAxisMapping 4 5 EndSection Section InputDevice Identifier Generic Mouse Driver mouse Option SendCoreEventstrue Option Device/dev/input/mice Option Protocol ImPS/2 Option ZAxisMapping 4 5 EndSection Section Device Identifier 420go Driver nv EndSection Section Monitor Identifier TFT HorizSync 28-49 VertRefresh 43-72 Option DPMS EndSection Section Screen Identifier Default Screen Device 420go Monitor TFT DefaultDepth24 SubSection Display Depth 1 Modes 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 4 Modes 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 8 Modes 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 15 Modes 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 16 Modes 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 24 Modes 1024x768 800x600 640x480 EndSubSection EndSection Section ServerLayout Identifier Default Layout Screen Default Screen InputDevice Generic Keyboard InputDevice ps2
Bug#207159: does not take any CorePointer automaticaly
On Mon, 2003-08-25 at 16:13, Eduard Bloch wrote: I tried to make a XF86Config-4 for a system where any time the mouse device changes (see below). To make X always start, I did not want to set a certain device as CorePointer but expected X to choose one, as described in XF86Config-4(5x), line 386. However, it does not choose any but fails to start if the CorePointer option is not set on some device. Next thing I looked for is an option to force X start without a Core input device (I remember there was some) but the manpage does not contain any info about it, not does README.mouse.gz. Are you looking for Option AllowMouseOpenFail, which is documented in the XF86Config-4 manpage? Alternatives would be making /dev/input/mice the core pointer, or using the void driver for it. -- Earthling Michel Dnzer \ Debian (powerpc), XFree86 and DRI developer Software libre enthusiast \ http://svcs.affero.net/rm.php?r=daenzer -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#207159: does not take any CorePointer automaticaly
#include hallo.h * Michel Dänzer [Mon, Aug 25 2003, 04:44:30PM]: but fails to start if the CorePointer option is not set on some device. Next thing I looked for is an option to force X start without a Core input device (I remember there was some) but the manpage does not contain any info about it, not does README.mouse.gz. Are you looking for Option AllowMouseOpenFail, which is documented in the XF86Config-4 manpage? Alternatives would be making /dev/input/mice the core pointer, or using the void driver for it. Thanks, I somehow did not find out. However, the option does not help, X still fails when CorePointer is not set anywhere. And what I used now, is setting one /dev/input/mice profile as CorePointer and setting X11_USBMICE_HACK=true in the hotplug configuration. So X does not fail and USB mice work when I attach them after X start. But is still not works automaticaly as described in XF86Config-4 manpage. Another glitch: the manpage does not list mouse(4x) in the list or references but it would make sence. MfG, Eduard. -- Wie man sein Kind nicht nennen sollte: Urs Sächlich -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#206832: xlib6-altdev: xpm library and dev stuff missing
On Mon, Aug 25, 2003 at 10:21:18AM +0200, Francesco P. Lovergine wrote: Anyway, some old cards are (well|only)-supported in 3.3.6. IMHO old xfree86 should be removed from the archives, but here again we could get a lots of complaints from users. They ask yet for libc5 support which is more buggy :-/ What are those 'xpm libc5 compatibility packages'? I think they were called libxpm4.7. -- G. Branden Robinson| You don't just decide to break Debian GNU/Linux | Kubrick's code of silence and then [EMAIL PROTECTED] | get drawn away from it to a http://people.debian.org/~branden/ | discussion about cough medicine. pgp0.pgp Description: PGP signature
XFree86 4.3 going to make it into testing ?
I was wondering if XFree86 4.3 was going to make it into testing before the September freeze. Have tried out the 4.3 in experimental (works for me), but didn't know if this implied if it would be able to make it. Just curious, geoff Brimhall [EMAIL PROTECTED] __ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
[no subject]
Good morning sir With this letter, the L.A.S.P. System will inform you then we that we will be present to the Equipe' Hotels fair, from the 28 settmbre to 3 October at Parigi France in the stand N140 padiglione 4 corsia C. We expose the new system M.A.N.T.T.®. System of telescopic coverages isolated with snow melting system incorporated. We manufacture and install covers for: 1.Hotel. 2.Restaurant. 3.Terraces. 4.swimming pool. Your visit will be a lot appreciate. Special jobs upon request In hoping to add you between our customers we augur them good job. Distinti saluti L.A.S.P. System Italia visit ours internet site: http://www.laspsystem.com email: [EMAIL PROTECTED] telephone: 0039-348-2631521
Re: DVI output of Radeon 9200 still doesn't work -- despite new XFree86 4.3 (fwd)
On Mon, 25 Aug 2003, Michel [ISO-8859-1] Dänzer wrote: On Sat, 2003-08-23 at 22:31, ERDI Gergo wrote: However, using the DVI port of my Radeon 9200, I get no output as soon as XFree86 is started. You may want to try xserver-xfree86-dri-trunk (see http://dri.sourceforge.net/snapshots/README.Debian), which has a CVS snapshot of the radeon driver. Thanks -- I was under the impression that the dri-trunk packages are based on the CVS development between 4.2 and 4.3 (and thus 4.3 would be more up-to-date). I've just tried dri-trunk, and here's what I get: 1. With 4.3.0-0pre1v1 and dri-trunk installed: (II) Module bitmap: vendor=The XFree86 Project compiled for 4.3.0, module version = 1.0.0 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.4 (EE) module ABI minor version (4) is newer than the server's version (3) (II) UnloadModule: bitmap (II) Unloading /usr/X11R6/lib/modules/fonts/libbitmap.a (EE) Failed to load module bitmap (module requirement mismatch, 0) (II) LoadModule: pcidata (II) Loading /usr/X11R6/lib/modules/libpcidata.a (II) Module pcidata: vendor=The XFree86 Project compiled for 4.3.0, module version = 1.0.0 ABI class: XFree86 Video Driver, version 0.6 Fatal server error: Unable to load required base modules, Exiting... 2. With 4.2.1 and dri-trunk: (II) Module pcidata: vendor=The XFree86 Project compiled for 4.2.1.1, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.5 *** If unresolved symbols were reported above, they might not *** be the reason for the server aborting. Fatal server error: Caught signal 11. Server aborting I've uploaded the full logs to http://cactus.rulez.org/files/ Thanks, Gergo -- .--= ULLA! =-. `We are not here to give users what \ http://cactus.rulez.org \ they want' -- RMS, at GUADEC 2001 `---= [EMAIL PROTECTED] =---' Me and you and a Borg named Hugh...
Bug#206832: xlib6-altdev: xpm library and dev stuff missing
On Sat, Aug 23, 2003 at 03:24:48PM -0500, Branden Robinson wrote:
On Sat, Aug 23, 2003 at 10:29:48AM +0200, Francesco P. Lovergine wrote:
Package: xlib6-altdev
Version: 3.3.6-44
Severity: normal
I'm interesting to use multiplane in Xaw3d lib. Is there a reason to have
not it included
in the oldlib?
See the version number. The xlib6 and xlib6-altdev packages are based
upon the XFree86 3.3.6 sources, which did not contain the Xpm libraries.
Your bug would be better filed against the xpm libc5 compatibility
packages, if they still exist.
If they don't, it's probably one more reason to consider pulling the
plug on xlib6{,-altdev}. An even better reason is that there have been,
ahem, security bugs fixed in the X libraries in XFree86 4.x but not
backported to the XFree86 3.3.6, which is not maintained upstream.
Anyway, some old cards are (well|only)-supported in 3.3.6.
IMHO old xfree86 should be removed from the archives,
but here again we could get a lots of complaints from users.
They ask yet for libc5 support which is more buggy :-/
What are those 'xpm libc5 compatibility packages'?
--
Francesco P. Lovergine
Bug#206907: xserver-xfree86: hangs on screensaver
Sven Luther [EMAIL PROTECTED] writes: Well, that certainly looks like a good way to fuck yourself. Whoever wrote this code has a lot of confidence in the underlying hardware. Since I happen to know that Sven Luther does a lot of glint driver work, I'm CCing him on this message. Yep, i did write part of this code, altough i mostly worked for the permedia3, but it is the same code. Could you try building the glint module with the DEBUG #define at the start of pm2_accel.c set to 1, in order to see the call trace in the /var/log/XFree86.0.log. I don't have the X sources or bandwidth to sit around compiling this stuff, but I will test out glint.o's that you guys send me. What is happening is that the Permedia2Sync function is sending the sync command to the chip, to synchronize the pipeline, probably between accel drawing and software drawing, since the permedia2 cannot accel some of the function (notably lines). The sync tag should be read back once the sync command has reached the bottom of the graphic pipeline, and every accel drawing has been commited to the framebuffer. Since no sync tag is read back, this can be for various reasons : o the sync command never reached the chip, because of of bus hogging or somethign such. o the graphic pipe did fail to synchronize, or dies for whatever reason. This means the problem is not in the sync call, but with whatever was done previously. o naturally, the random crashing could hint at hardware problem or bus problems, a more complete of your exact card (with lspci -v output maybe and/or lspci -vn too) would be welcome, as well as on what arch it is, and what kind of bus it is connected. Information on the motherboard would be welcome too, altough i doubt it is relevant here. Something I failed to mention in my original bug report is that this machine has always worked just fine in the past. I don't think it's a hardware problem unless it just started for some weird reason. eugene:~# lspci -nv 00:00.0 Class 0600: 8086:7190 (rev 03) Subsystem: 1028:0080 Flags: bus master, medium devsel, latency 64 Memory at f000 (32-bit, prefetchable) [size=64M] Capabilities: [a0] AGP version 1.0 00:01.0 Class 0604: 8086:7191 (rev 03) Flags: bus master, 66Mhz, medium devsel, latency 64 Bus: primary=00, secondary=01, subordinate=01, sec-latency=64 Memory behind bridge: fb00-fdff Prefetchable memory behind bridge: f600-f6ff 00:07.0 Class 0601: 8086:7110 (rev 02) Flags: bus master, medium devsel, latency 0 00:07.1 Class 0101: 8086:7111 (rev 01) (prog-if 80 [Master]) Flags: bus master, medium devsel, latency 64 I/O ports at ffa0 [size=16] 00:07.2 Class 0c03: 8086:7112 (rev 01) Flags: bus master, medium devsel, latency 64, IRQ 14 I/O ports at dce0 [size=32] 00:07.3 Class 0680: 8086:7113 (rev 02) Flags: medium devsel, IRQ 9 00:11.0 Class 0200: 10b7:9055 Subsystem: 1028:0080 Flags: bus master, medium devsel, latency 64, IRQ 14 I/O ports at dc00 [size=128] Memory at fe00 (32-bit, non-prefetchable) [size=128] Expansion ROM at f800 [disabled] [size=128K] Capabilities: [dc] Power Management version 1 00:13.0 Class 0604: 1011:0024 (rev 03) Flags: bus master, medium devsel, latency 64 Bus: primary=00, secondary=02, subordinate=02, sec-latency=64 I/O behind bridge: e000-efff Memory behind bridge: f900-faff Prefetchable memory behind bridge: f500-f5f0 Capabilities: [dc] Power Management version 1 01:00.0 Class 0380: 104c:3d07 (rev 01) Subsystem: 1092:0149 Flags: 66Mhz, medium devsel, IRQ 11 Memory at fcfe (32-bit, non-prefetchable) [size=128K] Memory at fc00 (32-bit, non-prefetchable) [size=8M] Memory at fb80 (32-bit, non-prefetchable) [size=8M] Expansion ROM at 8000 [disabled] [size=64K] Capabilities: [40] AGP version 1.0 02:0a.0 Class 0100: 9005:001f Subsystem: 1028:0080 Flags: bus master, medium devsel, latency 64, IRQ 10 BIST result: 00 I/O ports at ec00 [disabled] [size=256] Memory at f9fff000 (64-bit, non-prefetchable) [size=4K] Expansion ROM at fa00 [disabled] [size=128K] Capabilities: [dc] Power Management version 1 02:0e.0 Class 0100: 9004:8078 (rev 01) Subsystem: 9004:7880 Flags: bus master, medium devsel, latency 64, IRQ 10 I/O ports at e800 [disabled] [size=256] Memory at f9ffe000 (32-bit, non-prefetchable) [size=4K] Expansion ROM at fa00 [disabled] [size=64K] Capabilities: [dc] Power Management version 1 Here is lspci -v for this device: 01:00.0 Display controller: Texas Instruments TVP4020 [Permedia 2] (rev 01) Subsystem: Diamond Multimedia Systems
Processed: upgrading severity
Processing commands for [EMAIL PROTECTED]: severity 180679 serious Bug#180679: binutils: libraries not correctly linked Severity set to `serious'. severity 187344 serious Bug#187344: libvorbisfile3: libraries not correctly linked Severity set to `serious'. severity 187348 serious Bug#187348: libvorbisenc2: libraries not correctly linked Severity set to `serious'. severity 187349 serious Bug#187349: gnome-media: libraries not correctly linked Severity set to `serious'. severity 187350 serious Bug#187350: libbonobo2: libraries not correctly linked Severity set to `serious'. severity 187354 serious Bug#187354: libesmtp5: libraries not correctly linked Severity set to `serious'. severity 187356 serious Bug#187356: libbonobo-conf0: libraries not correctly linked Severity set to `serious'. severity 187357 serious Bug#187357: libglade-gnome0: libraries not correctly linked Severity set to `serious'. severity 187364 serious Bug#187364: libnautilus2-2: libraries not correctly linked Severity set to `serious'. severity 187365 serious Bug#187365: xlibmesa3-glu: libraries not correctly linked Severity set to `serious'. severity 187366 serious Bug#187366: libsigc++0c102: libraries not correctly linked Severity set to `serious'. severity 187367 serious Bug#187367: librsvg2-2: libraries not correctly linked Severity set to `serious'. severity 187370 serious Bug#187370: libgdk-pixbuf-gnome2: libraries not correctly linked Severity set to `serious'. severity 187372 serious Bug#187372: libperl5.8: libraries not correctly linked Severity set to `serious'. severity 187374 serious Bug#187374: xlibs: libraries not correctly linked Severity set to `serious'. severity 187375 serious Bug#187375: libsdl1.2debian-oss: libraries not correctly linked Severity set to `serious'. -- Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Bug#206907: xserver-xfree86: hangs on screensaver
On Mon, Aug 25, 2003 at 11:24:24AM +0200, David N. Welton wrote: Sven Luther [EMAIL PROTECTED] writes: Well, that certainly looks like a good way to fuck yourself. Whoever wrote this code has a lot of confidence in the underlying hardware. Since I happen to know that Sven Luther does a lot of glint driver work, I'm CCing him on this message. Yep, i did write part of this code, altough i mostly worked for the permedia3, but it is the same code. Could you try building the glint module with the DEBUG #define at the start of pm2_accel.c set to 1, in order to see the call trace in the /var/log/XFree86.0.log. I don't have the X sources or bandwidth to sit around compiling this stuff, but I will test out glint.o's that you guys send me. Ok, i will see what i can do, what X are you using ? Mmm, forget thta, i will find it from your original bugreport. (BTW, one more reason for us to ship the SDK package, that way people could easily rebuild the drivers, without needing the whole X server tree, and the hours of compile time, not counting the 4+ Go needed to build the debian packages. Something I failed to mention in my original bug report is that this machine has always worked just fine in the past. I don't think it's a hardware problem unless it just started for some weird reason. Well, i suppose that the hardware could start failing after a period of time or somethign such, it is rather old hardware anyway. Or maybe you added another pci card or something, which eats your bandwith away, or you have a faster processor which fills the fifo queue quickly or something. My pm2 board used to work fine for month, and now i have duplication of the mouse cursor after rebooting it. But then, it is this funny bvision, which is found in my apus amiga which was not really designed for such additional expansions. Over heating and failing powersupply may also cause this kind of problems. One thing you could do is check if there is the possibility of using the pciretry option, and if it changes anything to your behavior. pci retry or pci disconnect it is called i think, not sure, read the glint manpage, it should disable the pci bus when the fifo is full. 01:00.0 Class 0380: 104c:3d07 (rev 01) Subsystem: 1092:0149 Flags: 66Mhz, medium devsel, IRQ 11 Memory at fcfe (32-bit, non-prefetchable) [size=128K] Memory at fc00 (32-bit, non-prefetchable) [size=8M] Memory at fb80 (32-bit, non-prefetchable) [size=8M] Expansion ROM at 8000 [disabled] [size=64K] Capabilities: [40] AGP version 1.0 Huh ? What is that, do you have a second pci bus or something ? 02:0a.0 Class 0100: 9005:001f 02:0e.0 Class 0100: 9004:8078 (rev 01) Here is lspci -v for this device: 01:00.0 Display controller: Texas Instruments TVP4020 [Permedia 2] (rev 01) Subsystem: Diamond Multimedia Systems FIRE GL 1000 PRO Flags: 66Mhz, medium devsel, IRQ 11 Memory at fcfe (32-bit, non-prefetchable) [size=128K] Memory at fc00 (32-bit, non-prefetchable) [size=8M] Memory at fb80 (32-bit, non-prefetchable) [size=8M] Expansion ROM at 8000 [disabled] [size=64K] Capabilities: [40] AGP version 1.0 Ok, so you have a TI permedia2, in an agp slot. My first guess would either be a previous call did make the graphic pipeline die, or maybe even hog the bus. Does the machine stay accessible under ssh or something, i guess yes since you were able to to gdb work on it. What happens if you kill and restart the X server, which should reinitialize the pipeline. Killing and restarting the X server doesn't seem to do anything. I still have a blank screen, and I haven't been able to get the hardware 'back to normal' without rebooting. You are correct in assuming that the machine itself is not hanging, the load goes to one and X is dead but I am able to ssh just fine. Mmm, strange, the driver should be able to reinitialize the whole graphic pipeline, my diagnostic is that the card is deadlocked somehow, and that only a resest can revive it. I don't know if we are able to revive it without rebooting, but anyway, best let us try to solve the problem instead. Sven, any ideas? I hope this gives some ideas, altough the randomness of this happening might well be the input fifo overflowing and thus loosing the sync command or something such. Tricky thing to hunt down if this is the case. Well, I'm willing to try stuff out for you guys, but I would like to avoid downloading and compiling X. I don't really have the time for that. I will try to build a debugging glint.o this evening. That said, you will not be able to gdb it, since the debugging server is statically built, err, that is not using the module loader. As for the machine itself: Linux eugene 2.4.21 #2 Fri Jun 27 15:58:56 CEST 2003 i686 GNU/Linux Although I thought that stuff was in the
Re: DVI output of Radeon 9200 still doesn't work -- despite new XFree86 4.3 (fwd)
On Mon, 2003-08-25 at 09:59, ERDI Gergo wrote: On Mon, 25 Aug 2003, Michel [ISO-8859-1] Dänzer wrote: On Sat, 2003-08-23 at 22:31, ERDI Gergo wrote: However, using the DVI port of my Radeon 9200, I get no output as soon as XFree86 is started. You may want to try xserver-xfree86-dri-trunk (see http://dri.sourceforge.net/snapshots/README.Debian), which has a CVS snapshot of the radeon driver. Thanks -- I was under the impression that the dri-trunk packages are based on the CVS development between 4.2 and 4.3 (and thus 4.3 would be more up-to-date). That's still true for the woody packages, but hasn't been for a while for the sid packages. I've just tried dri-trunk, and here's what I get: 1. With 4.3.0-0pre1v1 and dri-trunk installed: (II) Module bitmap: vendor=The XFree86 Project compiled for 4.3.0, module version = 1.0.0 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.4 (EE) module ABI minor version (4) is newer than the server's version (3) (II) UnloadModule: bitmap (II) Unloading /usr/X11R6/lib/modules/fonts/libbitmap.a Remove ModulePath /usr/X11R6/lib/modules from your XF86Config-4, it's redundant at best and harmful in this case. The ABI mismatch also indicates that you seem to be using the woody packages. -- Earthling Michel Dänzer \ Debian (powerpc), XFree86 and DRI developer Software libre enthusiast \ http://svcs.affero.net/rm.php?r=daenzer
GTK2 thinks X is buggy
Hi, whenever I launch a GTK2 app, it outputs: Gdk-WARNING **: The X server advertises that RENDER support is present, but fails to supply the necessary pixmap support. In other words, it is buggy. I have a Xinerama setup, with a r128 and a TNT2. I'm currently using X4.3-pre, but I think it was already the case with X4.2. Log/config files on request (log says DRI is disabled because of Xinerama, dunno if it's related). Any hint on how to really enable RENDER on my setup ? Thanks, Xav
Bug#206929: Module loader broken on ia64
On Sun, Aug 24, 2003 at 07:54:52PM -0500, Branden Robinson wrote: Okay. Thanks a lot! So... I edited the 'loaderdiff' to apply cleanly to 4.2.1 and added relocation 79. This makes the server start up cleanly. However, it doesn't actually *work* -- things head south after Radeon decides to load int10. 4.3 actually does work, at least well enough for my tastes. Given that, I don't have too much enthusiasm for trying to debug 4.2.1 further. In case anybody else does, I've uploaded the patch to http://people.debian.org/~willy/xfree86/454_ia64_relocation_types_79_134_and_135.diff -- It's not Hollywood. War is real, war is primarily not about defeat or victory, it is about death. I've seen thousands and thousands of dead bodies. Do you think I want to have an academic debate on this subject? -- Robert Fisk
Bug#206900: X dropped my custom config
Hi Branden and DebianXers, I just rebooted my desktop and discovered my CUSTOM SECTION in XF86Config-4 was gone, and my mouse wasn't doing left-handed goodness anymore. In your reply to Eloy, you tell him to read /usr/share/doc/xfree86-common/NEWS.Debian 5 times. The problem is, I don't have this file in my system, and that explains why I didn't remember seeing a NEWS section in the apt-listchanges run which upgraded X. 65541:[EMAIL PROTECTED]:/usr/share/doc$ find -name NEWS.Debian* ./libinline-perl/NEWS.Debian.gz ./alsa-base/NEWS.Debian.gz ./dpatch/NEWS.Debian.gz ./epiphany-browser/NEWS.Debian.gz Going back to my specific problem, my old configuration was moved to .dpkg-old and the newly generated one didn't respect my custom section which defined a mouse with 7 buttons. Isn't this a bug? Of the three conditions to not overwrite my configuration file, I think I must have met the missing checksum condition, as I was upgrading from -9 to -10. In short, should my configuration be overwritten in my case? Why is NEWS.Debian missing? (Ah, Branden, look at the FAQ, entry How do I add custom sections to a dexconf generated XF86Config or XF86Config-4 file; 3 lines after the answer starts there's 8 lines of rubbish.) Jordi -- Jordi Mallach Pérez -- Debian developer http://www.debian.org/ [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.sindominio.net/ GnuPG public key information available at http://oskuro.net/~jordi/ pgpHYpJYWdGSz.pgp Description: PGP signature
Re: keyboard manpage in 4.3
On Wed, 2003-08-20 at 18:23, Branden Robinson wrote: On Tue, Aug 19, 2003 at 11:51:21AM +0200, Michel Dänzer wrote: (BTW, heads up to XSF: the keyboard manpage is still missing) File a bug, please; or, since you *do* have commit access to the repository, could you consider trying a fix yourself? True, but it's not as if I'm bored or something... Anyway, here's a patch I'll commit to branches/4.3.0/sid if nobody objects. This doesn't warrant a changelog entry, does it? -- Earthling Michel Dänzer \ Debian (powerpc), XFree86 and DRI developer Software libre enthusiast \ http://svcs.affero.net/rm.php?r=daenzer Index: debian/xserver-xfree86.install.hurd-i386 === --- debian/xserver-xfree86.install.hurd-i386 (revision 436) +++ debian/xserver-xfree86.install.hurd-i386 (working copy) @@ -150,6 +150,7 @@ usr/X11R6/man/man4/imstt.4x usr/X11R6/man/man4/js_x.4x usr/X11R6/man/man4/kbd.4x +usr/X11R6/man/man4/keyboard.4x usr/X11R6/man/man4/mga.4x usr/X11R6/man/man4/microtouch.4x usr/X11R6/man/man4/mouse.4x Index: debian/xserver-xfree86.install.ia64 === --- debian/xserver-xfree86.install.ia64 (revision 436) +++ debian/xserver-xfree86.install.ia64 (working copy) @@ -153,6 +153,7 @@ usr/X11R6/man/man4/imstt.4x usr/X11R6/man/man4/js_x.4x usr/X11R6/man/man4/kbd.4x +usr/X11R6/man/man4/keyboard.4x usr/X11R6/man/man4/mga.4x usr/X11R6/man/man4/microtouch.4x usr/X11R6/man/man4/mouse.4x Index: debian/xserver-xfree86.install.i386 === --- debian/xserver-xfree86.install.i386 (revision 436) +++ debian/xserver-xfree86.install.i386 (working copy) @@ -158,6 +158,7 @@ usr/X11R6/man/man4/glide.4x usr/X11R6/man/man4/js_x.4x usr/X11R6/man/man4/kbd.4x +usr/X11R6/man/man4/keyboard.4x usr/X11R6/man/man4/mga.4x usr/X11R6/man/man4/microtouch.4x usr/X11R6/man/man4/mouse.4x Index: debian/xserver-xfree86.install.mipsel === --- debian/xserver-xfree86.install.mipsel (revision 436) +++ debian/xserver-xfree86.install.mipsel (working copy) @@ -15,6 +15,7 @@ usr/X11R6/man/man4/glint.4x usr/X11R6/man/man4/js_x.4x usr/X11R6/man/man4/kbd.4x +usr/X11R6/man/man4/keyboard.4x usr/X11R6/man/man4/mga.4x usr/X11R6/man/man4/microtouch.4x usr/X11R6/man/man4/mouse.4x Index: debian/xserver-xfree86.install.hppa === --- debian/xserver-xfree86.install.hppa (revision 436) +++ debian/xserver-xfree86.install.hppa (working copy) @@ -15,6 +15,7 @@ usr/X11R6/man/man4/glint.4x usr/X11R6/man/man4/js_x.4x usr/X11R6/man/man4/kbd.4x +usr/X11R6/man/man4/keyboard.4x usr/X11R6/man/man4/mga.4x usr/X11R6/man/man4/microtouch.4x usr/X11R6/man/man4/mouse.4x Index: debian/xserver-xfree86.install.mips === --- debian/xserver-xfree86.install.mips (revision 436) +++ debian/xserver-xfree86.install.mips (working copy) @@ -15,6 +15,7 @@ usr/X11R6/man/man4/glint.4x usr/X11R6/man/man4/js_x.4x usr/X11R6/man/man4/kbd.4x +usr/X11R6/man/man4/keyboard.4x usr/X11R6/man/man4/mga.4x usr/X11R6/man/man4/microtouch.4x usr/X11R6/man/man4/mouse.4x Index: debian/xserver-xfree86.install.powerpc === --- debian/xserver-xfree86.install.powerpc (revision 436) +++ debian/xserver-xfree86.install.powerpc (working copy) @@ -126,6 +126,7 @@ usr/X11R6/man/man4/imstt.4x usr/X11R6/man/man4/js_x.4x usr/X11R6/man/man4/kbd.4x +usr/X11R6/man/man4/keyboard.4x usr/X11R6/man/man4/mga.4x usr/X11R6/man/man4/microtouch.4x usr/X11R6/man/man4/mouse.4x Index: debian/xserver-xfree86.install.arm === --- debian/xserver-xfree86.install.arm (revision 436) +++ debian/xserver-xfree86.install.arm (working copy) @@ -121,6 +121,7 @@ usr/X11R6/man/man4/glint.4x usr/X11R6/man/man4/js_x.4x usr/X11R6/man/man4/kbd.4x +usr/X11R6/man/man4/keyboard.4x usr/X11R6/man/man4/mga.4x usr/X11R6/man/man4/microtouch.4x usr/X11R6/man/man4/mouse.4x Index: debian/xserver-xfree86.install.alpha === --- debian/xserver-xfree86.install.alpha (revision 436) +++ debian/xserver-xfree86.install.alpha (working copy) @@ -127,6 +127,7 @@ usr/X11R6/man/man4/glint.4x usr/X11R6/man/man4/js_x.4x usr/X11R6/man/man4/kbd.4x +usr/X11R6/man/man4/keyboard.4x usr/X11R6/man/man4/mga.4x usr/X11R6/man/man4/microtouch.4x usr/X11R6/man/man4/mouse.4x Index: debian/xserver-xfree86.install.sparc === --- debian/xserver-xfree86.install.sparc (revision 436) +++ debian/xserver-xfree86.install.sparc (working copy) @@ -149,6 +149,7 @@ usr/X11R6/man/man4/imstt.4x usr/X11R6/man/man4/js_x.4x
Bug#207159: does not take any CorePointer automaticaly
Package: xserver-xfree86 Version: 4.3.0-0pre1v1 Severity: minor Tags: experimental upstream Hello, I tried to make a XF86Config-4 for a system where any time the mouse device changes (see below). To make X always start, I did not want to set a certain device as CorePointer but expected X to choose one, as described in XF86Config-4(5x), line 386. However, it does not choose any but fails to start if the CorePointer option is not set on some device. Next thing I looked for is an option to force X start without a Core input device (I remember there was some) but the manpage does not contain any info about it, not does README.mouse.gz. MfG, Eduard. -- Package-specific info: 01:00.0 VGA compatible controller: nVidia Corporation NV17 [GeForce4 420 Go] (rev a3) 01:00.0 Class 0300: 10de:0175 (rev a3) # Edit this file with caution, and see the XF86Config-4 manual page. # (Type man XF86Config-4 at the shell prompt.) # # If you want your changes to this file preserved by dexconf, only make changes # before the ### BEGIN DEBCONF SECTION line above, and/or after the # ### END DEBCONF SECTION line below. # # To change things within the debconf section, run the command: # dpkg-reconfigure xserver-xfree86 # as root. Also see How do I add custom sections to a dexconf-generated # XF86Config or XF86Config-4 file? in /usr/share/doc/xfree86-common/FAQ.gz. Section Files FontPathunix/:7100# local font server # if the local font server has problems, we can fall back on these FontPath/usr/lib/X11/fonts/100dpi FontPath/usr/lib/X11/fonts/75dpi 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/cyrillic EndSection Section Module LoadGLcore Loadbitmap Loaddbe Loadddc Loaddri Loadextmod Loadfreetype Loadglx Loadint10 Loadrecord Loadspeedo Loadtype1 Loadvbe EndSection Section InputDevice Identifier Generic Keyboard Driver keyboard Option CoreKeyboard Option XkbRules xfree86 Option XkbModel pc105 Option XkbLayout de,ru Option XkbVariantnodeadkeys,phonetic Option XKbOptions grp:alt_shift_toggle EndSection Section InputDevice # for kernel 2.4 Identifier ps2 Driver mouse # Option CorePointer true Option SendCoreEventstrue Option Device/dev/psaux Option Protocol ImPS/2 Option ZAxisMapping 4 5 EndSection Section InputDevice # the old serial mice Identifier ps2gpm Driver mouse Option SendCoreEventstrue Option Device/dev/gpmdata Option Protocol ImPS/2 Option ZAxisMapping 4 5 EndSection Section InputDevice Identifier Generic Mouse Driver mouse Option SendCoreEventstrue Option Device/dev/input/mice Option Protocol ImPS/2 Option ZAxisMapping 4 5 EndSection Section Device Identifier 420go Driver nv EndSection Section Monitor Identifier TFT HorizSync 28-49 VertRefresh 43-72 Option DPMS EndSection Section Screen Identifier Default Screen Device 420go Monitor TFT DefaultDepth24 SubSection Display Depth 1 Modes 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 4 Modes 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 8 Modes 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 15 Modes 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 16 Modes 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 24 Modes 1024x768 800x600 640x480 EndSubSection EndSection Section ServerLayout Identifier Default Layout Screen Default Screen InputDevice Generic Keyboard InputDevice ps2
Bug#207159: does not take any CorePointer automaticaly
On Mon, 2003-08-25 at 16:13, Eduard Bloch wrote: I tried to make a XF86Config-4 for a system where any time the mouse device changes (see below). To make X always start, I did not want to set a certain device as CorePointer but expected X to choose one, as described in XF86Config-4(5x), line 386. However, it does not choose any but fails to start if the CorePointer option is not set on some device. Next thing I looked for is an option to force X start without a Core input device (I remember there was some) but the manpage does not contain any info about it, not does README.mouse.gz. Are you looking for Option AllowMouseOpenFail, which is documented in the XF86Config-4 manpage? Alternatives would be making /dev/input/mice the core pointer, or using the void driver for it. -- Earthling Michel Dänzer \ Debian (powerpc), XFree86 and DRI developer Software libre enthusiast \ http://svcs.affero.net/rm.php?r=daenzer
Bug#207159: does not take any CorePointer automaticaly
#include hallo.h * Michel Dänzer [Mon, Aug 25 2003, 04:44:30PM]: but fails to start if the CorePointer option is not set on some device. Next thing I looked for is an option to force X start without a Core input device (I remember there was some) but the manpage does not contain any info about it, not does README.mouse.gz. Are you looking for Option AllowMouseOpenFail, which is documented in the XF86Config-4 manpage? Alternatives would be making /dev/input/mice the core pointer, or using the void driver for it. Thanks, I somehow did not find out. However, the option does not help, X still fails when CorePointer is not set anywhere. And what I used now, is setting one /dev/input/mice profile as CorePointer and setting X11_USBMICE_HACK=true in the hotplug configuration. So X does not fail and USB mice work when I attach them after X start. But is still not works automaticaly as described in XF86Config-4 manpage. Another glitch: the manpage does not list mouse(4x) in the list or references but it would make sence. MfG, Eduard. -- Wie man sein Kind nicht nennen sollte: Urs Sächlich
Bug#206900: X dropped my custom config
On Mon, Aug 25, 2003 at 02:15:14PM +0200, Jordi Mallach wrote: In short, should my configuration be overwritten in my case? Why is NEWS.Debian missing? Because debhelper ignores files called NEWS.Debian. (Ah, Branden, look at the FAQ, entry How do I add custom sections to a dexconf generated XF86Config or XF86Config-4 file; 3 lines after the answer starts there's 8 lines of rubbish.) Both of these problems have already been reported and resolved in SVN. See URL: http://necrotic.deadbeast.net/xfree86/trunk-debian-2003.08.25/ . -- G. Branden Robinson|Somewhere, there is a .sig so funny Debian GNU/Linux |that reading it will cause an [EMAIL PROTECTED] |aneurysm. This is not that .sig. http://people.debian.org/~branden/ | pgp8hFRuCqK9Q.pgp Description: PGP signature
Bug#206929: Module loader broken on ia64
On Mon, Aug 25, 2003 at 12:30:31PM +0100, Matthew Wilcox wrote: I edited the 'loaderdiff' to apply cleanly to 4.2.1 and added relocation 79. This makes the server start up cleanly. However, it doesn't actually *work* -- things head south after Radeon decides to load int10. 4.3 actually does work, at least well enough for my tastes. Given that, I don't have too much enthusiasm for trying to debug 4.2.1 further. Okay. That makes the loadable server work just as well (poorly) as the debugging on on IA64, then. This only affects some ATI cards, but there are a limited number of IA-64 configurations in the world, and this int10 problem seems to affect a lot of them. The real fix, it seems, is to get 4.3.0 into sarge. Thanks a lot for your efforts. -- G. Branden Robinson|Fair use is irrelevant and Debian GNU/Linux |improper. [EMAIL PROTECTED] |-- Asst. U.S. Attorney Scott http://people.debian.org/~branden/ |Frewing, explaining the DMCA pgpSxxMgA5aMo.pgp Description: PGP signature
Bug#206832: xlib6-altdev: xpm library and dev stuff missing
On Mon, Aug 25, 2003 at 10:21:18AM +0200, Francesco P. Lovergine wrote: Anyway, some old cards are (well|only)-supported in 3.3.6. IMHO old xfree86 should be removed from the archives, but here again we could get a lots of complaints from users. They ask yet for libc5 support which is more buggy :-/ What are those 'xpm libc5 compatibility packages'? I think they were called libxpm4.7. -- G. Branden Robinson| You don't just decide to break Debian GNU/Linux | Kubrick's code of silence and then [EMAIL PROTECTED] | get drawn away from it to a http://people.debian.org/~branden/ | discussion about cough medicine. pgpqDSKm8xKAh.pgp Description: PGP signature
Bug#207229: xfree86-common: [FAQ] Remove cruft from `dexconf-generated XF86Config' section
Package: xfree86-common Version: 4.2.1-10 Severity: minor Tags: sid There are few junk lines in FAQ file shipped with this version. From `/usr/share/doc/xfree86-common/FAQ.gz' (line numbers added): 1475 *) How do I add custom sections to a dexconf-generated XF86Config or 1476 XF86Config-4 file? 1477 1478 For XF86Config files used by the Debian packages of the XFree86 3.x servers, 1479 the dexconf utility only writes to part of the X server configuration file, 1480 instead of claiming the entire file for itself. (dexconf will change in 1481 j 1482 o 1483 o 1484 7P 1485 7P 1486 7P 1487 7P 1488 7P 1489 future to work for XF86Config files just as it does for XF86Config-4 files.) 1490 Best regards, Danilo Piazzalunga -- System Information: Debian Release: testing/unstable Architecture: i386 Kernel: Linux debian 2.4.20-3-686 #1 Sat Jun 7 22:34:55 EST 2003 i686 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] Versions of packages xfree86-common depends on: ii debconf 1.3.8 Debian configuration management sy ii debianutils 2.5.4 Miscellaneous utilities specific t -- debconf information excluded
Bug#207239: xfree86: French debconf templates translation
Package: xfree86 Version: N/A Severity: wishlist Tags: patch Please find attached the french debconf templates update, proofread by the debian-l10n-french mailing list contributors. -- System Information: Debian Release: testing/unstable Architecture: i386 Kernel: Linux mykerinos 2.4.21 #1 jeu jui 24 08:36:17 CEST 2003 i686 Locale: LANG=fr_FR.ISO-8859-1, LC_CTYPE=fr_FR.ISO-8859-1 (ignored: LC_ALL set to fr_FR) # xfree86 debconf template strings # Copyright (C) 2000--2003 Branden Robinson # This file is distributed under the same license as the xfree86 package. # Branden Robinson [EMAIL PROTECTED], 2000. # #Translators, if you are not familiar with the PO format, gettext #documentation is worth reading, especially sections dedicated to #this format, e.g. by running: # info -n '(gettext)PO Files' # info -n '(gettext)Header Entry' # #Some information specific to po-debconf are available at #/usr/share/doc/po-debconf/README-trans # or http://www.debian.org/intl/l10n/po-debconf/README-trans # #Developers do not need to manually edit POT or PO files. # msgid msgstr Project-Id-Version: xfree86 4.2.1-6 2nd version\n POT-Creation-Date: 2003-08-24 03:52-0500\n PO-Revision-Date: 2003-08-24 09:57+0100\n Last-Translator: Christian Perrier [EMAIL PROTECTED]\n Language-Team: Debiand french translation team [EMAIL PROTECTED] debian.org\n MIME-Version: 1.0\n Content-Type: text/plain; charset=ISO-8859-15\n Content-Transfer-Encoding: 8bit\n #. Description #: ../xdm.templates:4 msgid Select the desired default display manager. msgstr Choisissez le gestionnaire graphique de session par défaut #. Description #: ../xdm.templates:4 msgid A display manager is a program that provides graphical login capabilities for the X Window System. msgstr Un gestionnaire graphique de session est un programme qui permet de se connecter à la machine depuis le système X Window. #. Description #: ../xdm.templates:4 msgid Only one display manager can manage a given X server, but multiple display manager packages are installed. Please select which display manager should run by default. msgstr Un seul gestionnaire graphique de session peut s'occuper d'un serveur X donné, bien que plusieurs gestionnaires puissent être installés simultanément. Veuillez choisir celui qui sera utilisé par défaut. #. Description #: ../xdm.templates:4 msgid (Multiple display managers can run simultaneously if they are configured to manage different servers; to achieve this, configure the display managers accordingly, edit each of their init scripts in /etc/init.d, and disable the check for a default display manager.) msgstr Plusieurs gestionnaires graphiques peuvent être lancés en même temps, s'ils gèrent des serveurs X différents ; pour cela, configurez correctement chacun des gestionnaires graphiques, modifiez leurs scripts de lancement dans /etc/ init.d, et enlevez le test de gestionnaire graphique par défaut. #. Description #: ../xdm.templates:26 msgid Do you wish to stop the xdm daemon? msgstr Souhaitez-vous arrêter le démon xdm ? #. Description #: ../xdm.templates:26 msgid The X display manager (xdm) daemon is typically stopped on package upgrade and removal, but it appears to be managing at least one running X session. If xdm is stopped now, any X sessions it manages will be terminated. Otherwise you may leave xdm running, and the new version will take effect the next time the daemon is restarted. msgstr Le gestionnaire de sessions X (xdm) est généralement arrêté lors de la mise à jour ou de la suppression du paquet. Cependant, il semble qu'il gère actuellement encore au moins une session X. Si xdm est arrêté maintenant, toutes les sessions X qu'il gère seront terminées. Une autre possibilité est de laisser fonctionner xdm, la nouvelle version ne devenant active qu'au prochain redémarrage du démon. #. Description #: ../xfree86-common.templates:3 msgid experimental version of XFree86 packages msgstr Version expérimentale des paquets XFree86 #. Description #: ../xfree86-common.templates:3 msgid You are using an experimental version of XFree86 packages for Debian. Please do not file bugs with the Debian Bug Tracking System against this version of the packages, since they have not been released to the Debian distribution yet. msgstr Vous utilisez une version expérimentale des paquets XFree86 pour Debian. Veuillez éviter d'envoyer des rapports de bogues au système de gestion des bogues Debian pour cette version des paquets. En effet, ces paquets n'ont pas encore été intégrés dans la distribution Debian. #. Description #: ../xfree86-common.templates:3 msgid If you experience problems with these packages or would like to submit patches, please send mail to the Debian X mailing list. You can read more about this mailing list on the World Wide Web:\n http://lists.debian.org/debian-x/; msgstr Si vous rencontrez des problèmes avec ces paquets ou souhaitez
X Strike Force SVN commit: rev 437 - branches/4.3.0/sid/debian
Author: branden Date: 2003-08-25 17:46:33 -0500 (Mon, 25 Aug 2003) New Revision: 437 Modified: branches/4.3.0/sid/debian/changelog branches/4.3.0/sid/debian/xserver-xfree86.install.alpha branches/4.3.0/sid/debian/xserver-xfree86.install.arm branches/4.3.0/sid/debian/xserver-xfree86.install.hppa branches/4.3.0/sid/debian/xserver-xfree86.install.hurd-i386 branches/4.3.0/sid/debian/xserver-xfree86.install.i386 branches/4.3.0/sid/debian/xserver-xfree86.install.ia64 branches/4.3.0/sid/debian/xserver-xfree86.install.mips branches/4.3.0/sid/debian/xserver-xfree86.install.mipsel branches/4.3.0/sid/debian/xserver-xfree86.install.powerpc branches/4.3.0/sid/debian/xserver-xfree86.install.sparc Log: debian/xserver-xfree86.install.*: ship keyboard(4x) manpage (thanks, Michel D?\195?\164nzer) Modified: branches/4.3.0/sid/debian/changelog === --- branches/4.3.0/sid/debian/changelog 2003-08-24 20:10:52 UTC (rev 436) +++ branches/4.3.0/sid/debian/changelog 2003-08-25 22:46:33 UTC (rev 437) @@ -39,8 +39,11 @@ - add xlibmesa3, xlibmesa3-dbg, and xlibmesa-dev pseudopackages (merged from trunk and updated) to smooth upgrades from woody - -- Branden Robinson [EMAIL PROTECTED] Sat, 2 Aug 2003 14:41:27 -0500 + * debian/xserver-xfree86.install.*: ship keyboard(4x) manpage (thanks, +Michel D�nzer) + -- Branden Robinson [EMAIL PROTECTED] Mon, 25 Aug 2003 17:45:54 -0500 + xfree86 (4.3.0-0pre1v1) experimental; urgency=low * new upstream release Modified: branches/4.3.0/sid/debian/xserver-xfree86.install.alpha === --- branches/4.3.0/sid/debian/xserver-xfree86.install.alpha 2003-08-24 20:10:52 UTC (rev 436) +++ branches/4.3.0/sid/debian/xserver-xfree86.install.alpha 2003-08-25 22:46:33 UTC (rev 437) @@ -127,6 +127,7 @@ usr/X11R6/man/man4/glint.4x usr/X11R6/man/man4/js_x.4x usr/X11R6/man/man4/kbd.4x +usr/X11R6/man/man4/keyboard.4x usr/X11R6/man/man4/mga.4x usr/X11R6/man/man4/microtouch.4x usr/X11R6/man/man4/mouse.4x Modified: branches/4.3.0/sid/debian/xserver-xfree86.install.arm === --- branches/4.3.0/sid/debian/xserver-xfree86.install.arm 2003-08-24 20:10:52 UTC (rev 436) +++ branches/4.3.0/sid/debian/xserver-xfree86.install.arm 2003-08-25 22:46:33 UTC (rev 437) @@ -121,6 +121,7 @@ usr/X11R6/man/man4/glint.4x usr/X11R6/man/man4/js_x.4x usr/X11R6/man/man4/kbd.4x +usr/X11R6/man/man4/keyboard.4x usr/X11R6/man/man4/mga.4x usr/X11R6/man/man4/microtouch.4x usr/X11R6/man/man4/mouse.4x Modified: branches/4.3.0/sid/debian/xserver-xfree86.install.hppa === --- branches/4.3.0/sid/debian/xserver-xfree86.install.hppa 2003-08-24 20:10:52 UTC (rev 436) +++ branches/4.3.0/sid/debian/xserver-xfree86.install.hppa 2003-08-25 22:46:33 UTC (rev 437) @@ -15,6 +15,7 @@ usr/X11R6/man/man4/glint.4x usr/X11R6/man/man4/js_x.4x usr/X11R6/man/man4/kbd.4x +usr/X11R6/man/man4/keyboard.4x usr/X11R6/man/man4/mga.4x usr/X11R6/man/man4/microtouch.4x usr/X11R6/man/man4/mouse.4x Modified: branches/4.3.0/sid/debian/xserver-xfree86.install.hurd-i386 === --- branches/4.3.0/sid/debian/xserver-xfree86.install.hurd-i386 2003-08-24 20:10:52 UTC (rev 436) +++ branches/4.3.0/sid/debian/xserver-xfree86.install.hurd-i386 2003-08-25 22:46:33 UTC (rev 437) @@ -150,6 +150,7 @@ usr/X11R6/man/man4/imstt.4x usr/X11R6/man/man4/js_x.4x usr/X11R6/man/man4/kbd.4x +usr/X11R6/man/man4/keyboard.4x usr/X11R6/man/man4/mga.4x usr/X11R6/man/man4/microtouch.4x usr/X11R6/man/man4/mouse.4x Modified: branches/4.3.0/sid/debian/xserver-xfree86.install.i386 === --- branches/4.3.0/sid/debian/xserver-xfree86.install.i386 2003-08-24 20:10:52 UTC (rev 436) +++ branches/4.3.0/sid/debian/xserver-xfree86.install.i386 2003-08-25 22:46:33 UTC (rev 437) @@ -158,6 +158,7 @@ usr/X11R6/man/man4/glide.4x usr/X11R6/man/man4/js_x.4x usr/X11R6/man/man4/kbd.4x +usr/X11R6/man/man4/keyboard.4x usr/X11R6/man/man4/mga.4x usr/X11R6/man/man4/microtouch.4x usr/X11R6/man/man4/mouse.4x Modified: branches/4.3.0/sid/debian/xserver-xfree86.install.ia64 === --- branches/4.3.0/sid/debian/xserver-xfree86.install.ia64 2003-08-24 20:10:52 UTC (rev 436) +++ branches/4.3.0/sid/debian/xserver-xfree86.install.ia64 2003-08-25 22:46:33 UTC (rev 437) @@ -153,6 +153,7 @@ usr/X11R6/man/man4/imstt.4x usr/X11R6/man/man4/js_x.4x usr/X11R6/man/man4/kbd.4x +usr/X11R6/man/man4/keyboard.4x usr/X11R6/man/man4/mga.4x usr/X11R6/man/man4/microtouch.4x usr/X11R6/man/man4/mouse.4x Modified: branches/4.3.0/sid/debian/xserver-xfree86.install.mips
Re: keyboard manpage in 4.3
On Mon, Aug 25, 2003 at 03:44:27PM +0200, Michel Dänzer wrote: On Wed, 2003-08-20 at 18:23, Branden Robinson wrote: On Tue, Aug 19, 2003 at 11:51:21AM +0200, Michel Dänzer wrote: (BTW, heads up to XSF: the keyboard manpage is still missing) File a bug, please; or, since you *do* have commit access to the repository, could you consider trying a fix yourself? True, but it's not as if I'm bored or something... Anyway, here's a patch I'll commit to branches/4.3.0/sid if nobody objects. This doesn't warrant a changelog entry, does it? Yes; it's user-visible. Committed as 437. Thanks! -- G. Branden Robinson| Suffer before God and ye shall be Debian GNU/Linux | redeemed. God loves us, so He [EMAIL PROTECTED] | makes us suffer Christianity. http://people.debian.org/~branden/ | -- Aaron Dunsmore pgp5f54mAEGd1.pgp Description: PGP signature
XFree86 4.3 going to make it into testing ?
I was wondering if XFree86 4.3 was going to make it into testing before the September freeze. Have tried out the 4.3 in experimental (works for me), but didn't know if this implied if it would be able to make it. Just curious, geoff Brimhall [EMAIL PROTECTED] __ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com
Re: X Strike Force SVN commit: rev 432 - branches/4.3.0/sid/debian
On Mon, Aug 25, 2003 at 08:58:14AM +1000, Daniel Stone wrote: OK, I can do this, and will mail in some changes in a couple of days. * new Savage driver (version 1.1.27t): patch #063. (Closes: #110974, #112703, #115223, #128125, #145420, #148008, #152796, #154641, #185443, #194144, #194351, #191915, #197058, #112703, #110974) + XXX: DESCRIBE EACH OF THESE, AND MERGE THE REDUNDANT ONES, PLEASE These are all different bugs, fixed by the new driver. Do you want me to enumerate each fix individually? Yes, please. Each bug that we close in the changelog must have an associated explanation. If the bug subjects are coherent (they should be if I've had a change to correct them from the it dont work idiocy so many bugs start as), then it's okay to just copy the bit after xserver-xfree86: [savage], like this: * patch #063: new Savage driver (version 1.1.27t); resolves the following problems: - driver zigs when it should zag (Closes: #112703) - XVideo windows are blue, and so am I (Closes: #115223) ...and so forth. - new 'Option ForceInit' for forcing full initilization of consoles (Closes: #117454, #129216) + XXX: DESCRIBE EACH OF THESE, AND MERGE THE REDUNDANT ONES, PLEASE Ugh. Those are both artefacts of not doing proper initialization, with radically different symptoms (IIRC). Should they still be merged? Hmm, no. It's possible I merged some bugs in error. Thanks for looking into this! -- G. Branden Robinson| One doesn't have a sense of humor. Debian GNU/Linux | It has you. [EMAIL PROTECTED] | -- Larry Gelbart http://people.debian.org/~branden/ | pgpp6ThfKwQtP.pgp Description: PGP signature
Re: dpkg-reconfigure xserver-xfree86 fails.
On Sun, Aug 24, 2003 at 05:29:25PM +0300, Giannis Georgalis wrote: Hello, 'dpkg-reconfigure xserver-xfree86' fails with the following error message: Note: not updating /etc/X11/X; no stored MD5 checksum available. Note: not updating /etc/X11/XF86Config-4; file does not exist. Those aren't error messages; they're notes. If the command failed, it failed for some other reason, which should be reported. Note that I'm running debian unstable on an ix86 (with a today's dist-upgrade). This was the first time I decided to install xfree4 (I am currently running xfree3). Should this be reported as a bug, or is it a consequence of a misconfiguration on my pc ? If there's no error message, and the command exited with a zero exit status, it's neither. What happens if you do this?: # dpkg-reconfigure xserver-xfree86 echo there was no error -- G. Branden Robinson| We either learn from history or, Debian GNU/Linux | uh, well, something bad will [EMAIL PROTECTED] | happen. http://people.debian.org/~branden/ | -- Bob Church pgp8Qu4yt66QS.pgp Description: PGP signature
