Bug#270561: marked as done (xserver-xfree86: [nv] SEGV on NV20 [GeForce3 Ti 200] rev 163)
Your message dated Fri, 31 Dec 2004 00:04:17 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#270561: xserver-xfree86: Fatal server error: Caught signal 11 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; 7 Sep 2004 23:43:09 + >From [EMAIL PROTECTED] Tue Sep 07 16:43:09 2004 Return-path: <[EMAIL PROTECTED]> Received: from edoras.nas.com [66.114.32.34] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1C4pcC-0003VA-00; Tue, 07 Sep 2004 16:43:08 -0700 Received: from localhost (localhost [127.0.0.1]) by edoras.nas.com (Postfix) with ESMTP id 6A195EB49A; Tue, 7 Sep 2004 16:43:04 -0700 (PDT) Received: from edoras.nas.com ([127.0.0.1]) by localhost (edoras.nas.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 90075-04; Tue, 7 Sep 2004 16:43:03 -0700 (PDT) Received: from debian1.loaner.com (dsl-47-134.nas.com [66.114.47.134]) by edoras.nas.com (Postfix) with ESMTP id 3CB02EB453; Tue, 7 Sep 2004 16:43:01 -0700 (PDT) Received: from kingsley by debian1.loaner.com with local (Exim 3.36 #1 (Debian)) id 1C4pc9-0008WB-00; Tue, 07 Sep 2004 16:43:05 -0700 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Kingsley G. Morse Jr." <[EMAIL PROTECTED]> To: Debian Bug Tracking System <[EMAIL PROTECTED]> Subject: xserver-xfree86: Fatal server error: Caught signal 11. Server aborting X-Mailer: reportbug 2.43 Date: Tue, 07 Sep 2004 16:43:05 -0700 Message-Id: <[EMAIL PROTECTED]> Sender: "Kingsley G. Morse Jr." <[EMAIL PROTECTED]> X-Virus-Scanned: by amavisd-new at nas.com Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2004_03_25 X-Spam-Level: Package: xserver-xfree86 Version: 4.3.0.dfsg.1-6 Severity: normal Tags: sid Thanks for maintaining Debian's xserver-xfree86 package. It's important. The main reason I'm writing is to report that its intermittently crashing. The last error message it reports in /var/log/XFree86.0.log.old is Fatal server error: Caught signal 11. Server aborting The contents of the whoe file are included below. -- Package-specific info: -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.4.27-1-k7 Locale: LANG=C, LC_CTYPE=C Versions of packages xserver-xfree86 depends on: ii debconf 1.2.12 Debian configuration management sy ii libc6 2.3.2.ds1-16 GNU C Library: Shared libraries an ii xserver-common4.3.0.dfsg.1-6 files and utilities common to all ii zlib1g1:1.2.1-2 compression library - runtime -- debconf information: * xserver-xfree86/config/device/identifier: Visiontek GEForce3 model TI200 xserver-xfree86/config/monitor/screen-size: 17 inches (430 mm) xserver-xfree86/config/device/use_fbdev: * xserver-xfree86/config/monitor/selection-method: Advanced xserver-xfree86/config/doublequote_in_string_error: shared/default-x-server: xserver-xfree86 * xserver-xfree86/config/inputdevice/mouse/emulate3buttons: false * xserver-xfree86/config/device/bus_id: * xserver-xfree86/config/inputdevice/keyboard/layout: us * xserver-xfree86/config/monitor/horiz-sync: 30-95 * xserver-xfree86/config/monitor/identifier: Viewsonic P810 shared/no_known_x-server: xserver-xfree86/autodetect_mouse: true * xserver-xfree86/config/device/video_ram: xserver-xfree86/config/monitor/mode-list: 1280x960 @ 60Hz * xserver-xfree86/config/monitor/lcd: false xserver-xfree86/config/inputdevice/keyboard/internal: * xserver-xfree86/config/inputdevice/keyboard/rules: xfree86 xserver-xfree86/multiple_possible_x-drivers: * xserver-xfree86/config/inputdevice/keyboard/model: pc101 * xserver-xfree86/config/write_dri_section: true * xserver-xfree86/config/device/driver: nvidia * xserver-xfree86/config/monitor/vert-refresh: 50-160 * xserver-xfree86/config/display/default_depth: 24 * xserver-xfree86/config/inputdevice/mouse/zaxismapping: false * xserver-xfree86/config/display/modes: 1600x1200, 800x600, 640x480 xserver-xfree86/config/device/bus_id_error: * xserver-xfree86/config/modules: bitmap, dbe, ddc, extmod, freetype, glx, int10,
Processed: Re: Bug#270561: xserver-xfree86: Fatal server error: Caught signal 11
Processing commands for [EMAIL PROTECTED]: > tag 270561 = unreproducible Bug#270561: xserver-xfree86: [nv] SEGV on NV20 [GeForce3 Ti 200] rev 163 Tags were: moreinfo upstream sid Tags set to: unreproducible > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Re: dri_util.c:157: warning: pointer targets differ in signedness.
> > > I know, this causes a problem for any one building Xfree86 DRI. We need > to fold the DRI xc tree into Xfree86 or stop using Xfree86 alltogether. > I'm talking about 2d Xdrivers, where current MergedFB is built. I think > these can be built with the Mesa/lib/r200_dri.so files that live in > X11R6/lib/modules/dri/r200_dri.so? here you are talking about 2D drivers, mergedfb is a 2D thing really, it's been merged into Xorg, but not XFree86, take it up with XFree86, Alanh merges DRI changes into the XFree86 tree still on a regular basis, but mergedfb isn't really a DRI change it was just developed in the DRI tree as the XFree86 tree was too closed shop for anyone to use... so I don't think he can merge it into the XFree86 tree (I've no idea how their developers work or don't...) Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie pam_smb / Linux DECstation / Linux VAX / ILUG person
Re: dri_util.c:157: warning: pointer targets differ in signedness.
--- Dave Airlie <[EMAIL PROTECTED]> wrote: > > > > > > I know, this causes a problem for any one building Xfree86 DRI. We > need > > to fold the DRI xc tree into Xfree86 or stop using Xfree86 > alltogether. > > > I'm talking about 2d Xdrivers, where current MergedFB is built. I > think > > these can be built with the Mesa/lib/r200_dri.so files that live in > > X11R6/lib/modules/dri/r200_dri.so? > > here you are talking about 2D drivers, mergedfb is a 2D thing really, > it's > been merged into Xorg, but not XFree86, take it up with XFree86, > > Alanh merges DRI changes into the XFree86 tree still on a regular basis, > but mergedfb isn't really a DRI change it was just developed in the DRI > tree as the XFree86 tree was too closed shop for anyone to use... so I > don't think he can merge it into the XFree86 tree (I've no idea how > their > developers work or don't...) > This unfortunatly will not help with snapshots or Debian. When Debian's next realese sarge is frozen no more upgrades from the Xfree86 tree will be made. Untill recent changes to the Mesa tree have made building the DRI xc tree next to imposible this has not been a problem. Now that the "xc tree is dead" Debian users who wish to run DRI snapshots are left with ought any *GOOD* way of doing so. > Dave. > > -- > David Airlie, Software Engineer > http://www.skynet.ie/~airlied / airlied at skynet.ie > pam_smb / Linux DECstation / Linux VAX / ILUG person > > __ Do you Yahoo!? Yahoo! Mail - Easier than ever with enhanced search. Learn more. http://info.mail.yahoo.com/mail_250
Accepted xfree86 4.1.0-16woody5 (powerpc all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 2 Dec 2004 00:04:22 -0500 Source: xfree86 Binary: xserver-common xlibs-dev xfs xfree86-common xfonts-pex x-window-system xlibmesa-dev xspecs xlibmesa3 xfonts-cyrillic xlibmesa3-dbg xserver-xfree86 xlibs-dbg libxaw6 libxaw7 xterm xvfb xfonts-scalable xfonts-75dpi xlib6g proxymngr libxaw6-dev xlibs-pic libdps1-dbg xlib6g-dev xfonts-base xutils libxaw7-dev xnest xlibs libxaw6-dbg xmh lbxproxy libxaw7-dbg xfonts-base-transcoded xbase-clients xprt xlibosmesa3 x-window-system-core xlibosmesa-dev twm xfwp xfonts-100dpi-transcoded xlibosmesa3-dbg xfonts-100dpi xdm libdps-dev xfonts-75dpi-transcoded libdps1 Architecture: source all powerpc Version: 4.1.0-16woody5 Distribution: stable-security Urgency: low Maintainer: Branden Robinson <[EMAIL PROTECTED]> Changed-By: Branden Robinson <[EMAIL PROTECTED]> Description: lbxproxy - Low Bandwidth X (LBX) proxy server libdps-dev - Display PostScript (DPS) client library development files libdps1- Display PostScript (DPS) client library libdps1-dbg - Display PostScript (DPS) client library (unstripped) libxaw6- X Athena widget set library (version 6) libxaw6-dbg - X Athena widget set library (version 6) (unstripped) libxaw6-dev - X Athena widget set library development files (version 6) libxaw7- X Athena widget set library libxaw7-dbg - X Athena widget set library (unstripped) libxaw7-dev - X Athena widget set library development files proxymngr - X proxy services manager twm- Tab window manager x-window-system - X Window System x-window-system-core - X Window System core components xbase-clients - miscellaneous X clients xdm- X display manager xfonts-100dpi - 100 dpi fonts for X xfonts-100dpi-transcoded - 100 dpi fonts for X (transcoded from ISO 10646-1) xfonts-75dpi - 75 dpi fonts for X xfonts-75dpi-transcoded - 75 dpi fonts for X (transcoded from ISO 10646-1) xfonts-base - standard fonts for X xfonts-base-transcoded - standard fonts for X (transcoded from ISO 10646-1) xfonts-cyrillic - Cyrillic fonts for X xfonts-pex - fonts for minimal PEX support in X xfonts-scalable - scalable fonts for X xfree86-common - X Window System (XFree86) infrastructure xfs- X font server xfwp - X firewall proxy server xlib6g - pseudopackage providing X libraries xlib6g-dev - pseudopackage providing X library development files xlibmesa-dev - XFree86 version of Mesa 3D graphics library development files xlibmesa3 - XFree86 version of Mesa 3D graphics library xlibmesa3-dbg - XFree86 version of Mesa 3D graphics library (unstripped) xlibosmesa-dev - Mesa/XFree86 off-screen rendering library development files xlibosmesa3 - Mesa/XFree86 off-screen rendering library xlibosmesa3-dbg - Mesa/XFree86 off-screen rendering library (unstripped) xlibs - X Window System client libraries xlibs-dbg - X Window System client libraries (unstripped) xlibs-dev - X Window System client library development files xlibs-pic - X Window System client extension library PIC archives xmh- X interface to the MH mail system xnest - nested X server xprt - X print server xserver-common - files and utilities common to all X servers xserver-xfree86 - the XFree86 X server xspecs - X protocol, extension, and library technical specifications xterm - X terminal emulator xutils - X Window System utility programs xvfb - virtual framebuffer X server Changes: xfree86 (4.1.0-16woody5) stable-security; urgency=low . * Security update release. Resolves the following issue: + CAN-2004-0914: memory leak, improper use of signed integers, and overflow corrections in the Xpm library * Resync offset in patch #400. Files: 826f911016453d6f512fac4494b48c58 1512 x11 optional xfree86_4.1.0-16woody5.dsc ea7a32e6a81a850e9f19428f3104c300 54433247 x11 optional xfree86_4.1.0.orig.tar.gz ad4dc77a8dbde56fc7a3d06f774f3d40 1617667 x11 optional xfree86_4.1.0-16woody5.diff.gz af90af3a2500549ea49db4c37ef2adf5 141796 x11 optional lbxproxy_4.1.0-16woody5_powerpc.deb c4c1c910e9b3112a18fccbab90a6a2bf 188316 libs optional libdps1_4.1.0-16woody5_powerpc.deb 9db98e2ac4fc03e5c391202db13bc46f 446414 devel extra libdps1-dbg_4.1.0-16woody5_powerpc.deb ceed56b48d4d6492a64a6cd7c37ae276 260446 devel optional libdps-dev_4.1.0-16woody5_powerpc.deb f1a3945302d420228e2e7c698db150c8 179294 libs optional libxaw6_4.1.0-16woody5_powerpc.deb b23fbf21e340abf25566c5481c1f16cd 356586 devel extra libxaw6-dbg_4.1.0-16woody5_powerpc.deb d669dc6f8e53a3b6b9f862b5de215206 331430 devel extra libxaw6-dev_4.1.0-16woody5_powerpc.deb 01fef63045dd0fdde21d83d442063e54 232846 libs optional libxaw7_4.1.0-16woody5_powerpc.deb 7d4fe3c9c2b59ed926689e377589f47f 469786 devel extra libxaw7-dbg_4.1.0-16woody5_powerpc.deb fcf6b59428396fe12617145c7cab8d54 331324 devel optional libxaw7-dev_4.1.0-16woody5_powerpc.deb 3033a37fd98e592e62d30c01c4bca1
Re: dri_util.c:157: warning: pointer targets differ in signedness.
Sorry about the re-post, some mail servers didn't like my previous mail-header. --- Michel Dänzer <[EMAIL PROTECTED]> wrote: On Wed, 2004-12-29 at 17:46 -0800, Mike Mestnik wrote: > --- Philip Armstrong <[EMAIL PROTECTED]> wrote: > > > On Tue, Dec 28, 2004 at 06:41:38PM -0600, John Lightsey wrote: > > > First let me say that if anyone would like to take over updating the > > > dri-trunk-sid packages on a semi-regular basis, I'd really appreciate > > > it. I don't track the Debian X or DRI mailing lists closely enough to > > > keep up with changes. > > > > I'd like to, but I'm not sure I have the time. I'll pull the sources > > over sometime over the new year and take a look. > > > This might not be posible untill there is a sutable Xserver avalable !with > out! using DRI's old xc tree, read below. The DRI xc tree is dead, it's been folded into the X.Org tree. I know, this causes a problem for any one building Xfree86 DRI. We need to fold the DRI xc tree into Xfree86 or stop using Xfree86 alltogether. > > > On Tue, 2004-12-28 at 15:00 -0800, Mike Mestnik wrote: > > > > At this time Xorg is used for most of the DRI development. It also > > seams > > > > that the dri, glx, and opengl Xdrivers can be built in the Mesa tree > > with > > > > libGL and the dri_ Xdrivers. Since Mesa is now able to build > > against > > > > Xfree86 and Xorg this would seam to fix most of the problems. > > > > > > > > > > This is news to me. I thought the current recommended way of doing > > > things was to build an Xorg xserver, glx, and libgl, then build the 3D > > > drivers in Mesa. > > > > Maybe he's referring to embedded Mesa? > > > No, the current unofficial pkgs use the OLD xc tree to build Mesa and we > also need to build X from that tree. Since the Mesa tree has changed the > xc tree is now totaly bittroten, with no reason to correct this. I don't > think it will be posible to build the Xserver binary w/o using a(read as > any) xc tree. The only solution I see is to port the needed, if any, > changes to a working and maintained xc tree. > > When this is done the only problem that remains is the 2d Xdrivers, as I > woulden't expect any one to pickup the MeargedFB code. The DRI xc tree has been folded into the X.Org tree, including MergedFB etc.; it's dead. Read Above. > I think with little effort the Mesa tree can be made to build a wider > veriaty of Xdrivers since currenty the 3d Xdrivers are built in this tree. What 'veriaty of Xdrivers' are you talking about, in particular, what's a '3d Xdriver'? If you mean DDX drivers, I don't think those will ever build in the Mesa tree. I'm talking about 2d Xdrivers, where current MergedFB is built. I think these can be built with the Mesa/lib/r200_dri.so files that live in X11R6/lib/modules/dri/r200_dri.so? > I think this is the best way to get the Debian DRI pkgs building again. I > would hope that some one familure with Mesa builds would atleast create > the makefiles and symlinked headers for the 2d Xdrivers to build on. FWIW, if I had the time to work on those packages again, I'd do it along the lines of: * DRM packages from the directory du jour of the mess that is the DRI CVS drm module. * libGL and 3D drivers from the Mesa tree (building libGL requires adding glxproto.h to the tree though). * X server from the X.Org tree. Will building the X.Org binarys and puting them on a system expecting Xfree86 binarys work? When sarge is released there will be ppl(like me) not willing to run Xorg, since it's not shiped with sarge. > The real problem is how to get the changes out of the old xc tree, this I > can't solve but I know it must be done, if it must be done. Repeat after me: The DRI xc tree has been folded into the X.Org tree; it's dead. The... The DRI xc tree has been folded into the X.Org tree; it's dead. Ohh, lord what will we do? -- Earthling Michel Dänzer | Debian (powerpc), X and DRI developer Libre software enthusiast| http://svcs.affero.net/rm.php?r=daenzer __ Do you Yahoo!? Take Yahoo! Mail with you! Get it on your mobile phone. http://mobile.yahoo.com/maildemo
Bug#287900: xlibs: Want us_intl without deadkeys
Package: xlibs Version: 4.3.0.dfsg.1-10 Severity: normal Tags: l10n patch In the Netherlands all (well probably > 99%) of the pc users have a US international keyboard, they also do want to type the Euro character. The pc/us(intl) and pc/us_intl (and pc/us(alt-intl) which is identical) layouts give you that, but they also gives you very annoying deadkeys. At the moment there is no easy way (other then editing one of these files oneself) to get a functional Euro key on a US-intl keyboard _without_ deadkeys. I added a very small patch that adds this possibility. One can then use layout = us_intl, variant = nodeadkeys to get such a layout. grts Tim -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (900, 'testing'), (60, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.9 Locale: LANG=C, LC_CTYPE=C (charmap=ISO-8859-15) (ignored: LC_ALL set to [EMAIL PROTECTED]) Versions of packages xlibs depends on: ii libice6 4.3.0.dfsg.1-8 Inter-Client Exchange library ii libsm64.3.0.dfsg.1-8 X Window System Session Management ii libx11-6 4.3.0.dfsg.1-8 X Window System protocol client li ii libxext6 4.3.0.dfsg.1-8 X Window System miscellaneous exte ii libxft1 4.3.0.dfsg.1-8 FreeType-based font drawing librar ii libxi64.3.0.dfsg.1-8 X Window System Input extension li ii libxmu6 4.3.0.dfsg.1-8 X Window System miscellaneous util ii libxmuu1 4.3.0.dfsg.1-8 lightweight X Window System miscel ii libxp64.3.0.dfsg.1-8 X Window System printing extension ii libxpm4 4.3.0.dfsg.1-8 X pixmap library ii libxrandr24.3.0.dfsg.1-8 X Window System Resize, Rotate and ii libxt64.3.0.dfsg.1-8 X Toolkit Intrinsics ii libxtrap6 4.3.0.dfsg.1-8 X Window System protocol-trapping ii libxtst6 4.3.0.dfsg.1-8 X Window System event recording an ii xlibs-data4.3.0.dfsg.1-8 X Window System client data -- no debconf information --- etc/X11/xkb/symbols/pc/us_intl.orig 2004-12-15 20:13:32.0 +0100 +++ etc/X11/xkb/symbols/pc/us_intl 2004-12-30 20:22:17.0 +0100 @@ -52,3 +52,11 @@ include "level3(ralt_switch)" }; + +xkb_symbols "nodeadkeys" { + + include "pc/en_US(nodeadkeys)" + key { [ 5, percent, EuroSign] }; + key { [ e, E, EuroSign, cent ] }; + +};
Bug#287876: /etc/X11/Xsession: File $HOME/.xsession-errors grows very large
Package: xfree86-common Version: 4.3.0.dfsg.1-8 Severity: normal File: /etc/X11/Xsession The file $HOME/.xsession-errors contains stdout and stderr of all programs that are started through the graphical user interface, e.g. through KDE. On my notebook this file is now more than 370 MB large. (This is mostly because many KDE programs output many warning messages.) This is bad, because this file is invisible, and it is a surprise that this file should grow so large. This is a serious disk space hog! This file should be automatically truncated when a new X session is started. Maybe one older version could be kept. I looked at the script /etc/X11/Xsession which redirects stdout and stderr. There is no hook to truncate $HOME/.xsession-errors. The user's startup script $HOME/.xsession is only called later, and truncating then is too late, i.e., it would already delete information from the current session. -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (990, 'testing'), (600, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.9-1-686 Locale: LANG=C, [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages xfree86-common depends on: ii debconf 1.4.30.11 Debian configuration management sy ii debianutils 2.8.4 Miscellaneous utilities specific t -- debconf information: xfree86-common/experimental_packages:
Re: minimal x11 for sarge?
Am 2004-12-29 06:21:24, schrieb Jacob Johnson: > What packages are needed for a bare bones working XFree86 4.3 on Sarge? I'm > trying to trim down my testing system as it will eventually be used as the > master image in a netboot situation for many public kiosks. apt-get install x-window-system-core twm > Thanks in advance for any pointers. I know this is a dev list, but I figure > you folks probably know this beast inside and out! Greetings Michelle -- Linux-User #280138 with the Linux Counter, http://counter.li.org/ Michelle Konzack Apt. 917 ICQ #328449886 50, rue de Soultz MSM LinuxMichi 0033/3/8845235667100 Strasbourg/France IRC #Debian (irc.icq.com) signature.pgp Description: Digital signature
Processed: Re: Processed: Re: Bug#287810: xlibs: syntax error in /etc/X11/xkb/symbols/sun/us prevents xkbcomp from working
Processing commands for [EMAIL PROTECTED]: > severity 287810 important Bug#287810: xlibs: syntax error in /etc/X11/xkb/symbols/sun/us prevents xkbcomp from working Severity set to `important'. > merge 286268 287810 Bug#286268: xlibs: sun keyboard not working, error in xkb symbols file Bug#287810: xlibs: syntax error in /etc/X11/xkb/symbols/sun/us prevents xkbcomp from working Merged 286268 287810. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Bug#287810: xlibs: syntax error in /etc/X11/xkb/symbols/sun/us prevents xkbcomp from working
merge 287810 286268 thanks On Thu, Dec 30, 2004 at 10:26:39AM +0100, Henrik Enberg wrote: > Package: xlibs > Version: 4.3.0.dfsg.1-10 > Severity: normal > > the three occurances of 'include "srvr_ctrl(xfree86)";' in > /etc/X11/xkb/symbols/sun/us causes a syntax error in xkbcomp on X > startup, causing X to revert to whatever the standard keymap is. Please read already reported bugs in order to prevent duplicates, see http://bugs.debian.org/286268 A patch has been committed to the SVN repository, this bug will be fixed by the next upload. Denis
Bug#287810: xlibs: syntax error in /etc/X11/xkb/symbols/sun/us prevents xkbcomp from working
Package: xlibs Version: 4.3.0.dfsg.1-10 Severity: normal the three occurances of 'include "srvr_ctrl(xfree86)";' in /etc/X11/xkb/symbols/sun/us causes a syntax error in xkbcomp on X startup, causing X to revert to whatever the standard keymap is. commenting out each such line in the file makes it work as it should. Here are the relevant lines from my XF86Config-4: Section "InputDevice" Identifier "Generic Keyboard" Driver "keyboard" Option "CoreKeyboard" Option "XkbRules" "sun" Option "XkbModel" "type6" Option "XkbLayout" "us" EndSection -- Package-specific info: Keyboard-related contents of XFree86 X server log file /var/log/XFree86.0.log: (==) Using config file: "/etc/X11/XF86Config-4" (==) ServerLayout "Default Layout" (**) |-->Screen "Default Screen" (0) (**) | |-->Monitor "Generic Monitor" (**) | |-->Device "Generic Video Card" (**) |-->Input Device "Generic Keyboard" (**) Option "XkbRules" "sun" (**) XKB: rules: "sun" (**) Option "XkbModel" "type6" (**) XKB: model: "type6" (**) Option "XkbLayout" "us" (**) XKB: layout: "us" (==) Keyboard: CustomKeycode disabled (**) |-->Input Device "Generic Mouse" (WW) The directory "/usr/lib/X11/fonts/cyrillic" does not exist. Entry deleted from font path. (WW) The directory "/usr/lib/X11/fonts/CID" does not exist. Entry deleted from font path. -- (II) RADEON(0): Direct rendering disabled (==) RandR enabled (II) Initializing built-in extension MIT-SHM (II) Initializing built-in extension XInputExtension (II) Initializing built-in extension XTEST (II) Initializing built-in extension XKEYBOARD (II) Initializing built-in extension LBX (II) Initializing built-in extension XC-APPGROUP (II) Initializing built-in extension SECURITY (II) Initializing built-in extension XINERAMA (II) Initializing built-in extension XFree86-Bigfont (II) Initializing built-in extension RENDER (II) Initializing built-in extension RANDR (II) Keyboard "Generic Keyboard" handled by legacy driver (**) Option "Protocol" "ImPS/2" (**) Generic Mouse: Protocol: "ImPS/2" (**) Option "SendCoreEvents" "true" (**) Generic Mouse: always reports core events (**) Option "CorePointer" XFree86 X server log files on system: -rw-r--r-- 1 root root 43232 2004-12-30 10:10 /var/log/XFree86.0.log Compiled XKB description for X server ":0.0": xkb_keymap { xkb_keycodes "sun(type6)" { minimum = 8; maximum = 255; = 9; = 10; = 11; = 12; = 13; = 14; = 15; = 16; = 17; = 18; = 19; = 20; = 21; = 22; = 23; = 24; = 25; = 26; = 27; = 28; = 29; = 30; = 31; = 32; = 33; = 34; = 35; = 36; = 37; = 38; = 39; = 40; = 41; = 42; = 43; = 44; = 45; = 46; = 47; = 48; = 49; = 50; = 51; = 52; = 53; = 54; = 55; = 56; = 57; = 58; = 59; = 60; = 61; = 62; = 63; = 64; = 65; = 66; = 67; = 68; = 69; = 70; = 71; = 72; = 73; = 74; = 75; = 76; = 77; = 78; = 79; = 80; = 81; = 82; = 83; = 84; = 85; = 86; = 87; = 88; = 89; = 90; = 91; = 95; = 96; = 97; = 98; = 99; = 100; = 102; = 103; = 104; = 105; = 106; = 107; = 108; = 110; = 111; = 112; = 113; = 115; = 116; = 117; = 158; = 159; = 160; = 165; = 222; = 223; = 224; = 225; = 226; = 227; = 228; = 229; = 230; = 231; = 232; indicator 1 = "Caps Lock"; indicator 2 = "Num Lock"; indicator 3 = "Scroll Lock"; virtual indicator 4 = "Shift Lock"; virtual indicator 5 = "Group 2"; virtual indicator 6 = "Mouse Keys"; alias = ; }; xkb_types "complete" { virtual_modifiers NumLock,Alt,LevelThree,AltGr,Meta,Super,Hyper,ScrollLock; type "ONE_LEVEL" { modifiers= none; level_name[Level1]= "Any"; }; type "TWO_LEVEL" { modifiers= Shift; map[Shift]= Level2; level_name[Level1]= "Base"; level_name[Level2]= "Shift"; }; type "ALPHABETIC" { modifiers= Shift+Lock; map[Shift]= Level2; map[Lock]= Level1; preserve[Lock]= Lock; level_name[Level1]= "Base"; level_name[Level2]= "Caps"; }; type "KEYPAD" { modifiers= Shift+NumLock; map[Shift]= Level2; map[NumLock]= Level2; level_name[Level1]= "Base"; level_name[Level2]= "Number"; }; type "SHIFT+ALT" { modifiers= Shift+Alt; map[Shift+Alt]= Level2; level_name[Level1]= "Base"; level_name[Level2]= "Shift+Alt"; };
Re: dri_util.c:157: warning: pointer targets differ in signedness.
On Wed, 2004-12-29 at 17:46 -0800, Mike Mestnik wrote: > --- Philip Armstrong <[EMAIL PROTECTED]> wrote: > > > On Tue, Dec 28, 2004 at 06:41:38PM -0600, John Lightsey wrote: > > > First let me say that if anyone would like to take over updating the > > > dri-trunk-sid packages on a semi-regular basis, I'd really appreciate > > > it. I don't track the Debian X or DRI mailing lists closely enough to > > > keep up with changes. > > > > I'd like to, but I'm not sure I have the time. I'll pull the sources > > over sometime over the new year and take a look. > > > This might not be posible untill there is a sutable Xserver avalable !with > out! using DRI's old xc tree, read below. The DRI xc tree is dead, it's been folded into the X.Org tree. > > > On Tue, 2004-12-28 at 15:00 -0800, Mike Mestnik wrote: > > > > At this time Xorg is used for most of the DRI development. It also > > seams > > > > that the dri, glx, and opengl Xdrivers can be built in the Mesa tree > > with > > > > libGL and the dri_ Xdrivers. Since Mesa is now able to build > > against > > > > Xfree86 and Xorg this would seam to fix most of the problems. > > > > > > > > > > This is news to me. I thought the current recommended way of doing > > > things was to build an Xorg xserver, glx, and libgl, then build the 3D > > > drivers in Mesa. > > > > Maybe he's referring to embedded Mesa? > > > No, the current unofficial pkgs use the OLD xc tree to build Mesa and we > also need to build X from that tree. Since the Mesa tree has changed the > xc tree is now totaly bittroten, with no reason to correct this. I don't > think it will be posible to build the Xserver binary w/o using a(read as > any) xc tree. The only solution I see is to port the needed, if any, > changes to a working and maintained xc tree. > > When this is done the only problem that remains is the 2d Xdrivers, as I > woulden't expect any one to pickup the MeargedFB code. The DRI xc tree has been folded into the X.Org tree, including MergedFB etc.; it's dead. > I think with little effort the Mesa tree can be made to build a wider > veriaty of Xdrivers since currenty the 3d Xdrivers are built in this tree. What 'veriaty of Xdrivers' are you talking about, in particular, what's a '3d Xdriver'? If you mean DDX drivers, I don't think those will ever build in the Mesa tree. > I think this is the best way to get the Debian DRI pkgs building again. I > would hope that some one familure with Mesa builds would atleast create > the makefiles and symlinked headers for the 2d Xdrivers to build on. FWIW, if I had the time to work on those packages again, I'd do it along the lines of: * DRM packages from the directory du jour of the mess that is the DRI CVS drm module. * libGL and 3D drivers from the Mesa tree (building libGL requires adding glxproto.h to the tree though). * X server from the X.Org tree. > The real problem is how to get the changes out of the old xc tree, this I > can't solve but I know it must be done, if it must be done. Repeat after me: The DRI xc tree has been folded into the X.Org tree; it's dead. The... -- Earthling Michel Dänzer | Debian (powerpc), X and DRI developer Libre software enthusiast| http://svcs.affero.net/rm.php?r=daenzer
Bug#287798: config script for xserver-xfree86 limits refresh rates
Package:xserver-xfree86 Version: 4.3.0.dfsg.1-8_i386 xserver-xfree86_4.3.0.dfsg.1-8_i386.deb Linux 2.6.8-1-k7 i686 GNU/Linux libc6 Version: 2.3.2.ds1-18 The config script for xserver-xfree86 has a Design, which makes it impossible to get maximal/optimal HorizSync/VertRefresh ranges. "/var/lib/dpkg/info/xserver-xfree86.config" has limitation of 75 Hz @ 1024x768, why it gets 85 Hz I don't know, but my *Reflex FX*7200 model 1792E [approx. ~ CTX-1785GM] monitor can do 117 Hz. "xvidtune" picks up a max of 105 Hz: Vendor: , Model: Num hsync: 1, Num vsync: 1 hsync range 0: 30.00 - 95.00 vsync range 0: 50.00 - 105.00 "1024x768"113.31 1024 1096 1208 1392768 769 772 814 -hsync +vsync