Bug#226703: xprt: XFS-XTT & XPrint doesn't work together
Package: xprt
Version: 4.2.1-15
Severity: normal
Tags: patch
Hello,
When starting xprint, at boot time, i always get an error :
"cat: /usr/X11R6/lib/X11/fs/config: No such file or directory"
The error comes from the fact that i use xfs-xtt instead of xfs, so it
install config in fs-xtt/config.
The patch is simple and is attached.
Kind regard
Sylvain LE GALL
ps : i also get an annoying /etc/rc2.d/S20xprint: ## WARNING: Can't find
"/usr/X11R6/lib/X11/fonts/encodings/encodings.dir", TrueType font
support disabled, because
/usr/X11R6/lib/X11/fonts/encodings/encodings.dir has been removed by
someone ( not me ), do you where the error comes from ?
*** xprint.diff
--- /etc/init.d/xprint 2004-01-07 11:40:29.0 +0100
+++ xprint 2004-01-07 11:39:35.0 +0100
@@ -242,8 +242,6 @@
else
if [ -r "/etc/X11/fs/config" ] ; then
XFS_CONFIG_FILE="/etc/X11/fs/config"
- elif [ -r "/etc/X11/fs-xtt/config" ]; then
- XFS_CONFIG_FILE="/etc/X11/fs-xtt/config"
else
XFS_CONFIG_FILE="${XPROJECTROOT}/lib/X11/fs/config"
fi
-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux grand 2.6.0 #4 Tue Jan 6 21:05:29 CET 2004 i686
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED]
Versions of packages xprt depends on:
ii libc62.3.2.ds1-10GNU C Library: Shared libraries an
ii xprt-common 0.0.9.cvs20031220-1 Xprint - the X11 print system (con
ii zlib1g 1:1.2.1-3 compression library - runtime
-- no debconf information
Bug#226623: xserver-xfree86: Xvideo broken on Radeon M6 LY
Michel Dänzer wrote: The Xvideo support for my ATI Mobility Radeon LY seems to be broken in 4.3.0-pre1v5. Instead of the video playback, I only get a blue window. On which head? Cool. You just pointed me to a workaround for the problem ;-) If an external CRT is attached at boot time, the notebook automagically disables it's internal LCD screen and uses the CRT only. This is the setup that doesn't show video. If I boot up without CRT attached, Xvideo works for the LCD head (and on the CRT if it is attached later). -Alwin Meschede
Problems using a second text encoding in X
My computer is running Debian (Sarge) and XFce4 (built from the tarball). There are no Sid packages, no experimental packages, no Woody backports installed. My native language is English (US), but I want to be able to read and write in Russian using koi8-r encoding. I was able to do this in 2002 when I was running Woody, but my procedure doesn't work in Sarge and I don't know why. The following is my procedure. Following that is a copy of /etc/X11/XF86Config-4. Please review and let me know if you see a problem. All help is greatly appreciated. - Harold ## # Configuration Procedure. ## * Step 1: Install koi8-r fonts * apt-get install xfonts-cyrillic I then used gtkfontsel to verify that koi8r-encoded fonts are available. * Step 2: Build locale * /etc/locale.gen initially contained one line; I added the second line. en_US ISO-8859-1 ru_RU KOI8-R After adding the second line, I ran the executable "locale-gen," which successfully generated the locales files. * Step 3: Modify the Bash environment * I added the following line to /etc/profile: export LC_CTYPE=ru_RU.KOI8-R Then, as root, I sourced the file. . /etc/profile * Step 4: Modify /etc/X11/XF86Config-4 * I added the bottom two lines to the "InputDevice" section Section "InputDevice" Identifier "Default Keyboard" Driver "keyboard" Option "CoreKeyboard" Option "XkbRules" "xfree86" Option "XkbModel" "pc104" Option "XkbLayout" "us" Option "Xkblayout" "ru" Option "XkbOptions" "grp:ctrl_shift_toggle,grp_led:scroll" EndSection At this point a year ago, pressing the key combination toggled the keyboard between the encodings, and the scroll LED was lit when the Russian layout was active. Pressing now does nothing. ?!?!?!?! ## # XFree86 configuration for version XFree86 4.2.1 ## Section "Files" FontPath "unix/:7100" FontPath "/usr/lib/X11/fonts/misc" FontPath "/usr/lib/X11/fonts/cyrillic" FontPath "/usr/lib/X11/fonts/75dpi/:unscaled" FontPath "/usr/lib/X11/fonts/Type1" FontPath "/usr/lib/X11/fonts/TrueType" FontPath "/usr/lib/X11/fonts/Speedo" FontPath "/usr/lib/X11/fonts/75dpi" FontPath "/usr/share/fonts/truetype" FontPath "/usr/share/fonts/truetype/openoffice" EndSection Section "ServerFlags" EndSection Section "Module" Load "ddc" Load "GLcore" Load "dbe" Load "dri" Load "extmod" Load "glx" Load "pex5" Load "record" Load "xie" Load "bitmap" Load "freetype" Load "speedo" Load "type1" Load "vbe" Load "int10" EndSection Section "InputDevice" Identifier "Default Keyboard" Driver "keyboard" Option "CoreKeyboard" Option "XkbRules" "xfree86" Option "XkbModel" "pc104" Option "XkbLayout" "us" Option "Xkblayout" "ru" Option "XkbOptions" "grp:ctrl_shift_toggle,grp_led:scroll" EndSection Section "InputDevice" Identifier "Default Mouse" Driver "mouse" Option "CorePointer" Option "Device" "/dev/psaux" Option "Protocol" "PS/2" Option "Emulate3Buttons" "true" Option "ZAxisMapping" "4 5" EndSection Section "Device" Identifier "Selected Driver" Driver "ati" EndSection Section "Monitor" VendorName "Optiquest" ModelName "Optiquest Q71-5" Identifier "Optiquest Q71-5" HorizSync 30-70 VertRefresh 50-120 # 640x480, 60.0Hz; hfreq=31.469000, vfreq=59.93 ModeLine "640x480" 25.17 640 648 744 784 480 482 484 509 -hsync -vsync # 640x480, 72.0Hz; hfreq=37.861000, vfreq=72.808998 ModeLine "640x480" 31.50 640 656 696 816 480 481 484 504 -hsync -vsync # 640x480, 75.0Hz; hfreq=37.50, vfreq=75.00 ModeLine "640x480" 31.50 640 656 720 840 480 481 484 500 -hsync -vsync # 640x480, 85.0Hz; hfreq=43.269001, vfreq=85.008003 ModeLine "640x480" 36.00 640 696 752 832 480 481 484 509 -hsync -vsync # 800x600, 56.0Hz; hfreq=35.155998, vfreq=56.25 ModeLine "800x600" 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync # 800x600, 60.0Hz; hfreq=37.879002, vfreq=60.317001 ModeLine "800x600" 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync # 800x600, 75.0Hz; hfreq=46.875000, vfreq=75.00 ModeLine "800x600" 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync # 800x600, 85.0Hz; hfreq=53.674000, vfreq=85.060997 ModeLine "800x600" 56.25 800 832 896 1048 600 601 604 631 +hsync +vsync # 1024x768, 60.0Hz; hfreq=48.362999, vfreq=60.004002 ModeLine "1024x768" 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync # 1024x768, 70.0Hz; hfreq=56.476002, vfreq=70.069000 ModeLine "1024x768" 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsy
Bug#226623: xserver-xfree86: Xvideo broken on Radeon M6 LY
On Wed, 2004-01-07 at 16:39, Alwin Meschede wrote: > > The Xvideo support for my ATI Mobility Radeon LY seems to be broken in > 4.3.0-pre1v5. Instead of the video playback, I only get a blue window. On which head? -- Earthling Michel Dänzer | Debian (powerpc), X and DRI developer Software libre enthusiast| http://svcs.affero.net/rm.php?r=daenzer
Bug#225759: xlibmesa-dri: Radeon 9200 SE (RV280 5964) not detected for DRI
On Tue, Jan 06, 2004 at 04:24:00PM -0500, Branden Robinson wrote: > On Thu, Jan 01, 2004 at 08:17:54PM +0100, Michal ??iha?? wrote: > > On Thursday 01 of January 2004 18:52, Michel Dänzer wrote: > > > The attached patch should fix this. Please try appending it to > > > debian/patches/030b_radeon_rv280_support.diff (or adding it as a > > > separate patch) and rebuilding xserver-xfree86. > > > > Sorry, I can't download 50 MB sources now, maybe on monday... > > How's this coming along? Mmm, i am encountering the same problem with the same kind of card. Doing the ChipID stuff didn't help, and i didn't yet try out to rebuild the server packages with Michel's patch. Also, even normal X seems to trigger this problem when moving windows for example. That said, i still need to fix some stuff concerning my northbridge and the two pci controller, so it might be related to that, not sure if it would have an influence though. This is on powerpc/pegasos 2, using the Marvell Discovery northbridge, falling back to pcigart, and with stock 4.3.0-0pre1v5. Friendly, Sven Luther
Bug#225762: marked as done (xserver-xfree86: want magic key sequences to restore video mode, kill grabs, etc.)
Your message dated Wed, 7 Jan 2004 01:18:37 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#225762: xserver-xfree86: Another magic key sequence to restore video mode etc. 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; 1 Jan 2004 16:39:40 + >From [EMAIL PROTECTED] Thu Jan 01 10:39:37 2004 Return-path: <[EMAIL PROTECTED]> Received: from aoi.dyndns.org [69.17.34.240] by master.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1Ac3pY-0001EM-00; Thu, 01 Jan 2004 08:29:44 -0600 Received: by aoi.dyndns.org (Postfix, from userid 1001) id B7C58BE400C; Thu, 1 Jan 2004 06:29:27 -0800 (PST) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Alexander Hvostov <[EMAIL PROTECTED]> To: Debian Bug Tracking System <[EMAIL PROTECTED]> Subject: xserver-xfree86: Another magic key sequence to restore video mode etc. X-Mailer: reportbug 2.37 Date: Thu, 01 Jan 2004 06:29:26 -0800 Message-Id: <[EMAIL PROTECTED]> Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-master.debian.org_2003_11_25-bugs.debian.org_2003_12_29 (1.212-2003-09-23-exp) on master.debian.org X-Spam-Status: No, hits=-3.9 required=4.0 tests=HAS_PACKAGE, MAILTO_TO_SPAM_ADDR autolearn=no version=2.60-master.debian.org_2003_11_25-bugs.debian.org_2003_12_29 X-Spam-Level: Package: xserver-xfree86 Version: 4.2.1-14 Severity: wishlist -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sometimes, an X client will screw up various things on the server, like grabbing the mouse without releasing it, changing the video mode and not changing it back, and so forth. While it would be useful for the server to clean up after such a client if it disconnects, it would be useful in any case to have another magic button (along the lines of ctrl-alt-backspace) to forcibly restore sanity. In particular, it should: * Release the mouse cursor if it was grabbed. * Restore the mouse cursor bitmap/whatever to the standard arrow cursor. * Release the keyboard. * Restore the video mode to what it was when the server was started. Perhaps there are other necessary cleanups I forgot, but you get the idea. It would also be nice to have another magic key combination that starts an arbitrary program as specified in the configuration file, regardless of what any of the running X clients might think of that. Then this program could provide some functionality akin to the window one gets when pushing ctrl-alt-delete on Microsoft Windows 2000, or the Force Quit window on Mac OS X. The addition of such a feature should go a long way toward removing the need to ssh in to kill the X server if some application goes awry. - -- Package-specific info: 01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G400 AGP (rev 04) 01:00.0 Class 0300: 102b:0525 (rev 04) Section "ServerLayout" Identifier "Default Layout" Screen 0 "Hi-Res Screen" 0 0 InputDevice"Mouse1" "CorePointer" InputDevice"Keyboard1" "CoreKeyboard" EndSection Section "ServerFlags" Option "BlankTime" "off" Option "StandbyTime" "10" Option "SuspendTime" "off" Option "OffTime" "30" EndSection Section "Files" RgbPath "/usr/X11R6/lib/X11/rgb" FontPath "/usr/X11R6/lib/X11/fonts/local/" FontPath "/usr/X11R6/lib/X11/fonts/misc/" FontPath "/usr/X11R6/lib/X11/fonts/75dpi/:unscaled" FontPath "/usr/X11R6/lib/X11/fonts/100dpi/:unscaled" FontPath "/usr/X11R6/lib/X11/fonts/Type1/" FontPath "/usr/X11R6/lib/X11/fonts/Speedo/" FontPath "/usr/X11R6/lib/X11/fonts/75dpi/" FontPath "/usr/X11R6/lib/X11/fonts/100dpi/" FontPath "/usr/X11R6/lib/X11/fonts/TrueType/" FontPath "/usr/X11R6/lib/X11/fonts/freefont/" FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/CID" FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType" ModulePath "/usr/X11R6/lib/modules" EndSection Section "Module" Load "dbe" SubSection "extmod" Option "omit xfree86-dga" EndSubSection Load "type1" Load "freetype" Load "glx" Load "dri" EndSection Section "InputDevice" Identifier "Keyboard1" Driver "Keyb
Bug#11147: Re
This link can change your life clic this link below >> http://pharm56fr.com/host/default.asp?id=az <<
X Strike Force XFree86 SVN commit: rev 882 - branches/4.3.0/sid/debian
Author: branden Date: 2004-01-07 12:40:52 -0500 (Wed, 07 Jan 2004) New Revision: 882 Modified: branches/4.3.0/sid/debian/changelog Log: (cosmetic) Copyedit ISHIKAWA Mutsumi's changelog entry from r881. Modified: branches/4.3.0/sid/debian/changelog === --- branches/4.3.0/sid/debian/changelog 2004-01-07 13:25:22 UTC (rev 881) +++ branches/4.3.0/sid/debian/changelog 2004-01-07 17:40:52 UTC (rev 882) @@ -24,16 +24,20 @@ server build in build-server target (thanks, David Schmitt). - debian/rules - * Fix link problem of libXrender and libXft [ISHIKAWA Mutsumi]: + * Search for external Xrender and Xft libraries in /usr/lib instead of +/usr/X11R6/lib when symlinking them to the local exports directory for +build purposes. Update build-dependencies on these libraries' -dev +packages to ensure their files are where we expect them. +[ISHIKAWA Mutsumi] - debian/rules: - + libXrender.* moved from /usr/X11R6/lib to /usr/lib after 0.8.3-1, -generateing symlink in debian/rules refrect this change. - + libXrender.* moved from /usr/X11R6/lib to /usr/lib after 2.1.2-1, -generateing symlink in debian/rules refrect this change. -- debian/control - + Build-Depend update to adapt above changes + + symlink libXrender.* from /usr/lib instead of /usr/X11R6/lib + + symlink libXft.* from /usr/lib instead of /usr/X11R6/lib +- debian/control: + + update build-dependency from libxft2-dev to libxft-dev (>= 2.1.2) + + update build-dependency from libxrender-dev to libxrender-dev +(>= 0.8.3) - -- Branden Robinson <[EMAIL PROTECTED]> Thu, 1 Jan 2004 03:44:45 -0500 + -- Branden Robinson <[EMAIL PROTECTED]> Wed, 7 Jan 2004 12:38:20 -0500 xfree86 (4.3.0-0pre1v5) experimental; urgency=low
Bug#226430: SEGV with i865 on 4.3.0-0pre1v5
Thus spake Michel Dänzer: > Does removing ddc from this list make a difference? Upon closer investigation, even when I remove the line to load the ddc module, it still appears to load it right before the crash; this is the last thing before the server aborts: (II) I810(0): Currently active displays on Pipe A: (II) I810(0): CRT (II) Loading sub module "ddc" (II) LoadModule: "ddc" (II) Loading /usr/X11R6/lib/modules/libddc.a (II) Module ddc: vendor="The XFree86 Project" compiled for 4.3.0.1, module version = 1.0.0 ABI class: XFree86 Video Driver, version 0.6 When I also remove GLcore, glx, and dri, I get: (II) I810(0): Currently active displays on Pipe A: (II) I810(0): CRT (II) Loading sub module "ddc" (II) LoadModule: "ddc" (II) Loading /usr/X11R6/lib/modules/libddc.a (II) Module ddc: vendor="The XFree86 Project" compiled for 4.3.0.1, module version = 1.0.0 ABI class: XFree86 Video Driver, version 0.6 (II) I810(0): Will use BIOS call 0x5f05 to set refresh rates for CRTs. (II) I810(0): Will use BIOS call 0x5f64 to enable displays. (--) I810(0): Maximum space available for video modes: 8000 kByte However, removing further modules results in no longer getting those last 3 lines. Any suggestions for other things to try? -- Nathan Poznick <[EMAIL PROTECTED]> Government investigations have always contributed more to our amusement than they have to our knowledge. -Will Rogers signature.asc Description: Digital signature
Bug#226623: xserver-xfree86: Xvideo broken on Radeon M6 LY
Subject: xserver-xfree86: Xvideo broken on Radeon M6 LY Package: xserver-xfree86 Version: 4.3.0-0pre1v5 Severity: normal Tags: experimental The Xvideo support for my ATI Mobility Radeon LY seems to be broken in 4.3.0-pre1v5. Instead of the video playback, I only get a blue window. Please let me know if I should provide further information. -Alwin Meschede -- Package-specific info: 01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility M6 LY 01:00.0 Class 0300: 1002:4c59 # 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/cyrillic" 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" "de" 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 "Generic Mouse" Driver "mouse" Option "SendCoreEvents" "true" Option "Device" "/dev/input/mice" Option "Protocol""ImPS/2" Option "ZAxisMapping""4 5" EndSection Section "Device" Identifier "ATI Radeon M6C" Driver "ati" BusID "AGP:1:0:0" EndSection Section "Monitor" Identifier "Samtron 71s" HorizSync 30-60 VertRefresh 50-75 Option "DPMS" EndSection Section "Screen" Identifier "Default Screen" Device "ATI Radeon M6C" Monitor "Samtron 71s" DefaultDepth16 SubSection "Display" Depth 1 Modes "1024x768" EndSubSection SubSection "Display" Depth 4 Modes "1024x768" EndSubSection SubSection "Display" Depth 8 Modes "1024x768" EndSubSection SubSection "Display" Depth 15 Modes "1024x768" EndSubSection SubSection "Display" Depth 16 Modes "1024x768" EndSubSection SubSection "Display" Depth 24 Modes "1024x768" EndSubSection EndSection Section "ServerLayout" Identifier "Default Layout" Screen "Default Screen" InputDevice "Generic Keyboard" InputDevice "Configured Mouse" InputDevice "Generic Mouse" EndSection Section "DRI" Mode0666 EndSection 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.3.0.1 (Debian 4.3.0-0pre1v5 20031207095205 [EMAIL PROTECTED]) Release Date: 15 A
xmodmap Problem
Hello, I am loading an xmodmap using $ xmodmap .Xmodmap and .Xmodmap looks like this $ cat .Xmodmap ! The first four keysyms are reached as follows: ! 1. The decision between keysym1 or keysym2 (and keysym3 or keysym4) !is done by the key with the keysym Shift_[LR] (or maybe by the key !with the modifier bit keysym ! 2. The decision between the keysym1/keysym2 and keysym3/keysym4 group is !done by the key with generates the Mode_switch keysym (which is in this !case the left Alt key). keycode 30 = u U udiaeresis keycode 32 = o O odiaeresis keycode 38 = a A adiaeresis keycode 39 = s S ssharp keycode 0x1A = e E EuroSign cent keycode 113 = Mode_switch $ This worked for years now very reliable, now I have a system for which it does not work any more since today. I ran xkeycaps and it shows that the xmodmap command changed the keymaps, but it simply does not work, when I am using it in X. I have not a good idea how to debug this... My system is woody, with a standard woody X 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.4.20-8um i686 [ELF] Any input is welcome Thanks, Rainer
Bug#225759: xlibmesa-dri: Radeon 9200 SE (RV280 5964) not detected for DRI
On Tue, 2004-01-06 at 22:24, Branden Robinson wrote: > On Thu, Jan 01, 2004 at 08:17:54PM +0100, Michal Čihař wrote: > > On Thursday 01 of January 2004 18:52, Michel Dänzer wrote: > > > The attached patch should fix this. Please try appending it to > > > debian/patches/030b_radeon_rv280_support.diff (or adding it as a > > > separate patch) and rebuilding xserver-xfree86. > > > > Sorry, I can't download 50 MB sources now, maybe on monday... > > How's this coming along? The submitter has verified the patch to fix the problem, and I hope to get around to integrate it later this week. -- Earthling Michel Dänzer | Debian (powerpc), X and DRI developer Software libre enthusiast| http://svcs.affero.net/rm.php?r=daenzer
Bug#11147: Re
This link can change your life clic this link below >> http://pharm56fr.com/host/default.asp?id=az <<
X Strike Force XFree86 SVN commit: rev 881 - branches/4.3.0/sid/debian
Author: ishikawa Date: 2004-01-07 08:25:22 -0500 (Wed, 07 Jan 2004) New Revision: 881 Modified: branches/4.3.0/sid/debian/changelog branches/4.3.0/sid/debian/control branches/4.3.0/sid/debian/rules Log: * Fix link problem of libXrender and libXft: - debian/rules: + libXrender.* moved from /usr/X11R6/lib to /usr/lib after 0.8.3-1, generateing symlink in debian/rules refrect this change. + libXrender.* moved from /usr/X11R6/lib to /usr/lib after 2.1.2-1, generateing symlink in debian/rules refrect this change. - debian/control + Build-Depend update to adapt above changes Modified: branches/4.3.0/sid/debian/changelog === --- branches/4.3.0/sid/debian/changelog 2004-01-01 08:45:56 UTC (rev 880) +++ branches/4.3.0/sid/debian/changelog 2004-01-07 13:25:22 UTC (rev 881) @@ -24,6 +24,15 @@ server build in build-server target (thanks, David Schmitt). - debian/rules + * Fix link problem of libXrender and libXft [ISHIKAWA Mutsumi]: +- debian/rules: + + libXrender.* moved from /usr/X11R6/lib to /usr/lib after 0.8.3-1, +generateing symlink in debian/rules refrect this change. + + libXrender.* moved from /usr/X11R6/lib to /usr/lib after 2.1.2-1, +generateing symlink in debian/rules refrect this change. +- debian/control + + Build-Depend update to adapt above changes + -- Branden Robinson <[EMAIL PROTECTED]> Thu, 1 Jan 2004 03:44:45 -0500 xfree86 (4.3.0-0pre1v5) experimental; urgency=low Modified: branches/4.3.0/sid/debian/control === --- branches/4.3.0/sid/debian/control 2004-01-01 08:45:56 UTC (rev 880) +++ branches/4.3.0/sid/debian/control 2004-01-07 13:25:22 UTC (rev 881) @@ -4,7 +4,7 @@ Maintainer: Debian X Strike Force Uploaders: Branden Robinson <[EMAIL PROTECTED]> Standards-Version: 3.6.1 -Build-Depends: dpkg (>= 1.7.0), cpp-3.2, flex, bison, bsdmainutils, groff, zlib1g-dev | libz-dev, libncurses5-dev | libncurses-dev, libpam0g-dev | libpam-dev, libfreetype6-dev, libpaperg, libstdc++5-dev | libstdc++-dev, tetex-bin, po-debconf, debhelper (>= 4.1.16), html2text, libglide2-dev (>> 2001.01.26) [i386], libglide3-dev (>= 2002.04.10-3) [i386 alpha], kernel-headers-2.4 [alpha arm hppa i386 ia64 m68k mips mipsel powerpc s390 sh sparc], libpng12-0-dev | libpng-dev (>= 1.2.1), libexpat1-dev, libfontconfig1-dev, fontconfig, bzip2, libxft2-dev, libxrender-dev, libxcursor-dev, dbs, m4 +Build-Depends: dpkg (>= 1.7.0), cpp-3.2, flex, bison, bsdmainutils, groff, zlib1g-dev | libz-dev, libncurses5-dev | libncurses-dev, libpam0g-dev | libpam-dev, libfreetype6-dev, libpaperg, libstdc++5-dev | libstdc++-dev, tetex-bin, po-debconf, debhelper (>= 4.1.16), html2text, libglide2-dev (>> 2001.01.26) [i386], libglide3-dev (>= 2002.04.10-3) [i386 alpha], kernel-headers-2.4 [alpha arm hppa i386 ia64 m68k mips mipsel powerpc s390 sh sparc], libpng12-0-dev | libpng-dev (>= 1.2.1), libexpat1-dev, libfontconfig1-dev, fontconfig, bzip2, libxft-dev (>= 2.1.2), libxrender-dev (>= 0.8.3), libxcursor-dev, dbs, m4 Build-Conflicts: gcc-3.3 (<< 1:3.3.2-0pre1) Package: lbxproxy Modified: branches/4.3.0/sid/debian/rules === --- branches/4.3.0/sid/debian/rules 2004-01-01 08:45:56 UTC (rev 880) +++ branches/4.3.0/sid/debian/rules 2004-01-07 13:25:22 UTC (rev 881) @@ -208,11 +208,11 @@ # not limited to, -I/usr/include). mkdir -p debian/local/exports/lib mkdir -p debian/local/exports/include/X11/extensions - ln -s /usr/X11R6/lib/libXft* debian/local/exports/lib + ln -s /usr/lib/libXft* debian/local/exports/lib rm -f debian/local/exports/lib/libXft.so.1* debian/local/exports/lib/libXft1* ln -s /usr/include/X11/Xft debian/local/exports/include/X11 # Xrender - ln -s /usr/X11R6/lib/libXrender.* debian/local/exports/lib + ln -s /usr/lib/libXrender.* debian/local/exports/lib ln -s /usr/include/X11/extensions/Xrender.h debian/local/exports/include/X11/extensions # Xcursor ln -s /usr/lib/libXcursor.* debian/local/exports/lib
Processed: Re: Bug#226296: xserver-xfree86: [savage] flickering screen, low resolution on thinkpad t23 w/1400x1050 panel
Processing commands for [EMAIL PROTECTED]: > tag 226296 + moreinfo Bug#226296: xserver-xfree86: [savage] flickering screen, low resolution on thinkpad t23 w/1400x1050 panel Tags were: experimental Tags added: moreinfo > severity 226296 normal Bug#226296: xserver-xfree86: [savage] flickering screen, low resolution on thinkpad t23 w/1400x1050 panel Severity set to `normal'. > retitle 226296 xserver-xfree86: [savage] flickering screen and low resolution > on SuperSavage IX/C SDR rev 5 Bug#226296: xserver-xfree86: [savage] flickering screen, low resolution on thinkpad t23 w/1400x1050 panel Changed Bug title. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Bug#226296: xserver-xfree86: [savage] flickering screen, low resolution on thinkpad t23 w/1400x1050 panel
tag 226296 + moreinfo severity 226296 normal retitle 226296 xserver-xfree86: [savage] flickering screen and low resolution on SuperSavage IX/C SDR rev 5 thanks On Mon, Jan 05, 2004 at 02:06:21PM -0600, Andrew Lusk wrote: > Package: xserver-xfree86 > Version: 4.3.0-0pre1v5 > Severity: important > Tags: experimental > > With the new 4.3.0-0pre1v5 packages, I can't start X at any resolution > higher than 640x480. Also, when the server does start, the screen > flickers a lot, headache-inducingly badly, also mouse movement is jerky > and slow. I'm running 2.6.0 on a Thinkpad T23 laptop, model 2647-5RU > (with the 1400x1050 panel). > > Let me know if I can provide any more information. Is this a regression from a previous version of the XFree86 Debian packages? -- G. Branden Robinson| Debian GNU/Linux | Ignorantia judicis est calamitas [EMAIL PROTECTED] | innocentis. http://people.debian.org/~branden/ | signature.asc Description: Digital signature
Re: Processed: Tough bug
Branden Robinson writes: > As usual, nobody explains to the poor victim package maintainer what > the hell has been reassigned to him, or why. I explained it in the last mail I sent to the bug report, which was the same mail I sent to [EMAIL PROTECTED] to reassign the bug. cheers domi
Re: Machine hangs/screen hangs with newer kernels + GL screensavers
Hi Michel,
thanks a lot for your prompt answer :-)
> > both on my desktop and my laptop i am getting strange hangs when
> > running XFree packages (both debian testing/unstable, 4.2.1-{12.1,15})
> > with the newer linux kernels. This happens for me since one of the
> > 2.5.5* kernels (and it still happens with 2.6.0) and now i also
> > checked the same happens with 4.2.23 (but doesn't happen with 4.2.22).
> > With the 2.5/2.6 kernels i checked the same happens with acpi
> > disabled.
>
> Sounds like it's related to the newer DRM.
bingo, yes, i made a test with the newer kernels + the old xfree 4.2 but
disabling dri (taking out the dri module line in the XFree86 config file)
and it worked ok (quite slow of course but that was to be expected ;-)
> FWIW, I can run all screensavers from the kscreensaver package from sid
> on my TiBook with a Mobility Radeon 9000 running a 2.6 kernel with my
> DRI snapshot packages described in
> http://dri.sourceforge.net/snapshots/README.Debian without problems. The
> XFree86 4.3 packages in experimental may also work better.
I tried your packages but they do not have MIT-AUTH support compiled in
(that is a small ("non-free") extra patch if i remember correctly) so i
decided to try first the XFree4.3 debian-experimental packages and they
work flawlessly :-)
(btw, didn't try that before because the experimental area is still
unavailable, now i found a mirror...)
Thanks for your help,
Ariel
Bug#226365: selection-method question should not be displayed at high priority
retitle 226365 xserver-xfree86: [debconfage rewrite] selection-method question should be displayed at high priority under fewer circumstances thanks On Sun, Jan 04, 2004 at 05:46:46PM -0500, Joey Hess wrote: > Package: xserver-xfree86 > Version: 4.2.1-14 > Severity: normal > > If my debconf priority is high, I do not want to be bothered by > questions that have a reasonable default. In my opinion, monitor configuration *doesn't* have a reasonable default if nothing can be autodetected. Also, the "simple" method gives extremely poor (read: terrible, often unusable) results with LCD screens. So I stand by my decision that this question needs to be high priority under *some* circumstances. Naturally I'm interested in minimizing those. > This is the definition of the priority. So it is annoying to have this > package's monitor/selection-method question displayed at high > priority. It should default to "simple" at high priority. (If simple > is not available, as it is not here due to mdetect breaking, it should > default to medium.). I don't understand what mdetect has to do with monitor detection. Have you read its manpage, or tried running it? :) > Also, there is currently no default for this question at all, as you > will see if you reconfigure xserver-xfree86 using debconf's readline > frontend. See my response to first of your bugs of this nature. -- G. Branden Robinson|I'm sorry if the following sounds Debian GNU/Linux |combative and excessively personal, [EMAIL PROTECTED] |but that's my general style. http://people.debian.org/~branden/ |-- Ian Jackson signature.asc Description: Digital signature
Bug#226210: priority inflation and bad default mouse port with mdetect
On Mon, Jan 05, 2004 at 12:22:17AM -0500, Joey Hess wrote: > Joey Hess wrote: > > Despite the availability of this information, xserver-xfree86's > > configure script persists in prompting for the mouse port, at an > > inflated debconf priority (high). The priority should be low, as there > > is a reasonable default value. > > > > It also neglects to select the /dev/psaux item in the debconf question > > about the mouse port. This is not obvious if the dialog frontend is > > used, since "/dev/psaux" happens to be at the top of the list and so is > > the implicit default, but in the text frontend, there is no default > > selected. > > And it doesn't make the very simple inference that /dev/psaux is always > a PS/2 mouse type, and prompts me for mouse type as well, also at an > inflated debconf priority. Well, that inference would be wrong. Quoting mouse(4x): Option "Protocol" "string" Specify the mouse protocol. Valid protocol types include: Auto, Microsoft, MouseSystems, MMSeries, Log‐ itech, MouseMan, MMHitTab, GlidePoint, Intel‐ liMouse, ThinkingMouse, AceCad, PS/2, ImPS/2, ExplorerPS/2,ThinkingMousePS/2, MouseMan‐ PlusPS/2, GlidePointPS/2, NetMousePS/2, NetScrollPS/2, BusMouse, SysMouse, WSMouse, USB, Xqueue. /dev/psaux could be any of PS/2, ImPS/2, ExplorerPS/2, ThinkingMousePS/2, MouseManPlusPS/2, GlidePointPS/2, NetMousePS/2, or NetScrollPS/2. ...and those are in fact the choices the config script offers. Guys like Zephanaiah Hull will scream at you long and loud if they can't use all 206 of the the buttons on their NetGlideScrollExplorerThinkingPS/2 (Plus!). And they might put out a bona fit HIT on you if they can't use all 43 wheels on their pointing device. -- G. Branden Robinson| The last Christian died on the Debian GNU/Linux | cross. [EMAIL PROTECTED] | -- Friedrich Nietzsche http://people.debian.org/~branden/ | signature.asc Description: Digital signature
Processed: Re: Bug#226365: selection-method question should not be displayed at high priority
Processing commands for [EMAIL PROTECTED]: > retitle 226365 xserver-xfree86: [debconfage rewrite] selection-method > question should be displayed at high priority under fewer circumstances Bug#226365: selection-method question should not be displayed at high priority Changed Bug title. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Processed: tagging 225839
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.7.95.1 > tags 225839 + upstream Bug#225839: xserver-xfree86: typo in manpage XQueryBestCursor(3x) Tags were: experimental Tags added: upstream > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Bug#226545: XFree86 cursor themes not working
Package: libxcursor1 Version: 1.0.2-4 Hi folks, to make xcursor themes working I had to manually run ln -s libXcursor.so.1.0.1 /usr/lib/libXcursor.so to add a missing symbolic link. Shouldn't this link be included in libxcursor1? Regards Harri
Bug#226292: xdm: can't reconfigure default window manager
On Tue, Jan 06, 2004 at 09:19:54PM -0500, Branden Robinson wrote: > tag 226292 + moreinfo > thanks > > On Sun, Jan 04, 2004 at 11:20:18PM +, Julian Gilbey wrote: > > Package: xdm > > Version: 4.2.1-15 > > > > I have been unable to reconfigure the default window manager using > > dpkg-reconfigure xdm. For some reason, I am not offered the > > possibility of setting the debconf setting > > shared/default-x-display-manager. And since I had no file > > /etc/X11/default-window-manager either, and there wasn't a setting of > > the debconf variable, it is somewhat "random" which window manager is > > used, xdm or kdm. I don't know where the bug lies. > > You can perhaps help me to find out. > > Please show me (er, well, mail this bug) the output of the misbehaving > dpkg-reconfigure command after doing this: > > # export DEBUG_XFREE86_PACKAGE=yes polya2:~ # export DEBUG_XFREE86_PACKAGE=yes polya2:~ # dpkg-reconfigure xdm debconf: unable to initialize frontend: Dialog debconf: (Dialog frontend will not work on a dumb terminal, an emacs shell buffer, or without a controlling terminal.) debconf: falling back to frontend: Readline System startup links for /etc/init.d/xdm already exist. polya2:~ # Not so much info there, I'm afraid :-( Julian -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Julian Gilbey, website: http://www.polya.uklinux.net/ Debian GNU/Linux Developer, see: http://people.debian.org/~jdg/ Visit http://www.thehungersite.com/ to help feed the hungry
Bug#225811: Should depend on exact versions
On Tue, Jan 06, 2004 at 05:00:33PM -0500, Branden Robinson wrote: > You can add the following to your apt preferences file > (/etc/apt/preferences): > > Package: * > Pin: release a=xfree86 > Pin-Priority: 1002 > > Please let me know if this solution satisfies your needs. Isn't it 'release a=experimental'? Also, there's this: for package in $(apt-cache showsrc xfree86 | grep ^Binary | cut -f2- -d: | tr -d ,); do printf "Package: %s\nPin: release a=experimental\nPin-Priority: 600\n\n" "$package"; done >> /etc/apt/preferences The script comes from David B. Harris. Cheers. :) -- Daniel Stone<[EMAIL PROTECTED]> Debian X Strike Force:http://people.debian.org/~branden/xsf/ pgp1B1JJmTbyw.pgp Description: PGP signature
Bug#226180: not ameanable to configuration with readline frontend; lack of defaults
retitle 226180: xserver-xfree86: [debconfage rewrite] not ameanable to configuration with readline frontend; lack of defaults thanks On Sun, Jan 04, 2004 at 05:13:17PM -0500, Joey Hess wrote: > Package: xserver-xfree86 > Version: 4.2.1-14 > Severity: normal > > The debconf configuration for xserver-xfree86 has a large number of > questions that are missing any default option. Some of these are not > obvious when xserver-xfree86 is configured using debconf's dialog > frontend. For example: > > Note that mouse buttons in excess of five (counting a scroll wheel as two > buttons, one each for "up" and "down", and a third if the wheel "clicks") > are > not yet supported with this configuration tool. > > :-) Emulate 3 button mouse? > :-) Emulate 3 button mouse? > > There is no reason why there cannot be a default value for this question. > Moreover, there _is_ an implicit default, when using the dialog frontend: > Whatever button dialog decides to highlight when it's not specified. Only > with the text frontend do boolean and select questions have no default > value. So you should go through and add reasonable defaults for all such > things. I used to have them. I had to rip them all out when I added the autodetection code. My testing experience showed me that I couldn't both do autodetection cleanly and have defaults in the debconf database. I forget what all the scenarios were, but it was very frustrating to write, as you can probably see from the amount of indirection and messiness in the current xserver-xfree86.config script. I think that script is in a hopeless state and it needs to be rewritten from scratch. > Here is another one, using the string type: > > Users of U.S. English keyboards should generally enter "pc104". > > :-) Please select your keyboard model. > > Please enter a value for the entry. > > A null entry is not permitted. > > As opposed to only part of it? How would I accomplish that without yet another template? Wouldn't omitting the long description be a frontend decision? > Users of U.S. English keyboards should generally enter "pc104". > > :-) Please select your keyboard model. > > So, why not use "pc104" as a default. Better, why not come up with a > good default based on the selected keymap in console-tools. Or, you could > try to get the value of debian-installer/keymap, which will be available > in the debconf db on systems installed by debian-installer. Anyway, > there should be a reasonable default provided. Ooh, debian-installer/keymap. That sounds nice. I've seen you complaining about 1 billion different packages that ask what country people live in, too. You should probably mail debian-devel-announce a heads up to people regarding what configuration data is available in debian-installer debconf templates. Once a few people have moved on this (you have my support, FWIW), you can say its current practice and ram a Policy proposal through. Perhaps in the release *after* sarge we can get some stuff nicely centralized. And I hope that d-i absolutely, unconditionally, always always always sets the hostname. Everybody seems to assume it's set, and nobody *EVER* bothers to do any error handling if it isn't. They're wrong, but they're also terminally lazy and we'll never get them all fixed. -- G. Branden Robinson| The last Christian died on the Debian GNU/Linux | cross. [EMAIL PROTECTED] | -- Friedrich Nietzsche http://people.debian.org/~branden/ | signature.asc Description: Digital signature
Bug#226193: card driver default
Branden Robinson wrote: > On Tue, Jan 06, 2004 at 12:52:36AM +0100, Michel Dänzer wrote: > > On Sun, 2004-01-04 at 23:34, Joey Hess wrote: > > > > > > If read-edid fails to determine the card type, the question, in > > > debconf's default dialog frontend, defaults to the first item in the > > > list, "apm". This does not seem like a good fallback default. Perhaps > > > "vesa" or "vga" would be a reasonable thing to default to if the card > > > cannot be detected; something that will probably work, even if not that > > > well, if the user takes the default. > > > > Beware that neither of these work on Macs, nor on most non-PC hardware I > > suspect. fbdev is another fallback for when /proc/fb exists (and is > > non-empty?). > > Don't worry; in debian-installer land, all the world's an i386. :) Well, in my world at least, scripts are allowed to check the architecture of the host they are running on. -- see shy jo signature.asc Description: Digital signature
Processed: Re: Bug#225526, PCI domains.
Processing commands for [EMAIL PROTECTED]: > severity 225526 important Bug#225526: xserver-xfree86: [pciprobe] Newer 2.6 kernels on sparc have changed some file names. Severity set to `important'. > tag 225526 + moreinfo Bug#225526: xserver-xfree86: [pciprobe] Newer 2.6 kernels on sparc have changed some file names. There were no tags set. Tags added: moreinfo > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Bug#226210: priority inflation and bad default mouse port with mdetect
retitle 226210 xserver-xfree86: [debconfage rewrite] mouse port/protocol
question priorities too high when autodetected
thanks
On Sun, Jan 04, 2004 at 05:40:56PM -0500, Joey Hess wrote:
> Package: xserver-xfree86
> Version: 4.2.1-14
> Severity: normal
>
> mdetect is easily able to detect the internal ps2 pointing device on my
> LC2000 laptop. It reports:
>
> /dev/psaux
> psaux
>
> Despite the availability of this information, xserver-xfree86's
> configure script persists in prompting for the mouse port, at an
> inflated debconf priority (high). The priority should be low, as there
> is a reasonable default value.
Hmm. I thought I did this.
Actually, I do. Except I'm asking at medium, not high. It's a "normal
item that has a reasonable default" (see debconf-devel(7)). A correct
answer is important for the user to have a good computing experience, so
it cannot be low priority ("Very trivial items that have defaults that
will work in the vast majority of cases; only control freaks see
these.").
Perhaps you can help me find the bug in the following:
738 # mouse device detection
739
740 # priority of xserver-xfree86/config/inputdevice/mouse/{port,protocol}
741 PRIORITY=high
742 AUTODETECTED_PORT=
743 AUTODETECTED_PROTOCOL=
744
745 # determine if we're using devfs
746 if [ -c /dev/.devfsd ]; then
747 USING_DEVFS=true
748 else
749 USING_DEVFS=
750 fi
751
752 if [ -n "$USING_DEVFS" ]; then
753 MOUSE_PORT_CHOICES="/dev/misc/psaux, /dev/tts/0, /dev/tts/1,
/dev/tts/2, /dev/tts/3, /dev/input/mice, /dev/misc/atixl, /dev/gpmdata"
754 DEFAULT_PORT="/dev/misc/psaux"
755 else
756 MOUSE_PORT_CHOICES="/dev/psaux, /dev/ttyS0, /dev/ttyS1, /dev/ttyS2,
/dev/ttyS3, /dev/input/mice, /dev/atibm, /dev/sunmouse, /dev/gpmdata"
757 DEFAULT_PORT="/dev/psaux"
758 fi
759
760 # if configuring for the first time, ask if user wants to autodetect
761 if [ -z "$RECONFIGURE" ]; then
762 while :; do
763 # bail out if autodetection tool not available
764 which mdetect > /dev/null 2>&1 || break
765 auto_answer db_input "$(priority_ceil $PRIORITY)"
xserver-xfree86/autodetect_mouse "false"
766 db_get xserver-xfree86/autodetect_mouse
767 if [ "$RET" = "true" ]; then
768 set +e
769 MDETECT_OUTPUT=$(mdetect -x)
770 set -e
771 if [ -n "$MDETECT_OUTPUT" ]; then
772 if [ $(echo "$MDETECT_OUTPUT" | wc -l) -ne 2 ]; then
773 debug_echo "bug in mdetect; did not return two lines of
output"
774 break
775 fi
776 AUTODETECTED_PORT=$(echo "$MDETECT_OUTPUT" | head -n 1)
777 AUTODETECTED_PROTOCOL=$(echo "$MDETECT_OUTPUT" | tail -n 1)
778 debug_echo "mdetect returned port \"$AUTODETECTED_PORT\";
protocol \"$AUTODETECTED_PROTOCOL\""
779 if [ -n "$AUTODETECTED_PORT" ]; then
780 # /dev/input/mouse* means we autodetected a USB pointer; we
will
781 # store /dev/input/mice instead.
782 if expr "$AUTODETECTED_PORT" : "/dev/input/mouse.*" >
/dev/null 2>&1; then
783 AUTODETECTED_PORT="/dev/input/mice"
784 fi
785 else
786 debug_echo "bug in mdetect: returned nothing for mouse port"
787 break
788 fi
789 if [ -z "$AUTODETECTED_PROTOCOL" ]; then
790 debug_echo "bug in mdetect: returned nothing for mouse
protocol"
791 break
792 fi
793 else
794 debug_echo "mdetect returned no output; unable to autodetect
mouse"
795 # permit user to retry, but set to false in the case question
doesn't
796 # get asked (for noninteractive configuration)
797 db_set xserver-xfree86/autodetect_mouse "false"
798 fi
799 if [ -n "$AUTODETECTED_PORT" -a -n "$AUTODETECTED_PROTOCOL" ];
then
800 PRIORITY=medium
801 break # port and protocol determined
802 fi
803 else
804 debug_echo "user declined mouse autodetection"
805 break # bail out; autodetection not desired
806 fi
807 done
808 else
809 debug_echo "not prompting for mouse autodetection; reconfiguring"
810 fi
811
812 db_subst xserver-xfree86/config/inputdevice/mouse/port choices
$MOUSE_PORT_CHOICES
813 auto_answer db_input "$(priority_ceil $PRIORITY)"
xserver-xfree86/config/inputdevice/mouse/port
"${AUTODETECTED_PORT:-$DEFAULT_PORT}"
> It also neglects to select the /dev/psaux item in the debconf question
> about the mouse port. This is not obvious if the dialog frontend is
> used, since "/dev/psaux" happens to be at the top of the list and so is
> the implicit default, but in the text frontend, there is no default
> selected.
See my reply to another recent bug of yours regarding autoconfig
Bug#225526: , PCI domains.
severity 225526 important tag 225526 + moreinfo thanks On Thu, Jan 01, 2004 at 04:02:19PM -0800, Mike Mestnik wrote: > Well it dosen't matter, I discussed this on the xfree86 mailing list > this is what they had to say. What doesn't matter? > http://marc.theaimsgroup.com/?l=xfree86&w=2&r=1&s=pci+domains&q=b > > It dose seam to be a long standing bug in Xfree86 and now the DBTS is > more complete. For normalization's sake I don't see any reason to > have copies of other bugs here, just links too other sources of > information. The Debian Bug Tracking System is not a normalized database, especially with respect to the contents of a user's complaint. Your bug report needs to contain enough information for the package maintainer to meaningfully act on it. That doesn't mean giving the package maintainer orders and declaring things broken; it means giving the him or her enough information that he or she can independently reach a solution. > BOTTOM LINE, debian can not release xfree86 for sparc64 with this bug. That doesn't make the bug "grave", that makes it "important". We do not hold up an entire release because of hardware-specific bugs. > An easy way to fix this problem is to build all the kernels with > pci_domains not set. That is not my decision to make. I do not maintain any Debian packages of the Linux kernel. You are going to have to direct this suggestion elsewhere, as I have already told you. It is not germane to any bug report against the Debian packages of XFree86. > This will require a little bit of kernel > patching as well as making the correct config changes. It's not the > best policy for packages to force the kernel to be configured or built > in a certain way. As noted above, this is irrelevant to a report against the Debian packages of XFree86. "For normalization's sake", if nothing else, you should not be repeating it. > I attached my config and logs when I first opened this bug, I will not > continue to do so. Please see > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=225526 for this > information. My apologies; I overlooked that. > pciprobe, I apologize for being so vague and inaccurate. I was just > trying to refer to the xfree86 code responsible for finding pci > devices. This is not a big deal; your failure to reply to Message-ID: <[EMAIL PROTECTED]> is more important, and why this bug should continue to have the "moreinfo" tag, which you removed. Please do not interfere with my use of the "moreinfo" tag. The "moreinfo" tag is defined as follows in the Debian BTS documentation: moreinfo This bug can't be addressed until more information is provided by the submitter. The bug will be closed if the submitter doesn't provide more information in a reasonable (few months) timeframe. This is for bugs like "It doesn't work". What doesn't work? This is not a determination for the submitter to make. It is the province of a package maintainer or developer working on the bug to set or clear this flag. Please do not fool with it any more. > I have posted a bug against 2.6-test11, giving a pointer to this bug. > The kernel is actually correct, but for now it is to be reconfigured > to get around this bug. I'll have to take your word for it. As I said before, I do not maintain any Debian packages of the Linux kernel. > Divid S. Miller has told me that his work is incomplete. This may > mean however that it may be continued by any one with the skill and > time. Therefor his CVS commit may be a good place to start. This bug is not going to be resolvable until someone has done that work. And that work cannot commence until more information about the problem is known. (I could probably write a patch myself if I were given enough information.) This is another reason the package should retain the "moreinfo" tag. Please do not manipulate this bug any further. I request that you reply to the particulars to Message-ID: <[EMAIL PROTECTED]>. If you are able to supply the requisite information for writing a patch to complete Mr. Miller's work, that would be good as well. -- G. Branden Robinson| I suspect Linus wrote that in a Debian GNU/Linux | complicated way only to be able to [EMAIL PROTECTED] | have that comment in there. http://people.debian.org/~branden/ | -- Lars Wirzenius signature.asc Description: Digital signature
Processed: Re: Bug#226210: priority inflation and bad default mouse port with mdetect
Processing commands for [EMAIL PROTECTED]: > retitle 226210 xserver-xfree86: [debconfage rewrite] mouse port/protocol > question priorities too high when autodetected Bug#226210: priority inflation and bad default mouse port with mdetect Changed Bug title. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
