Bug#233202: xserver-xfree86: xvideo extensions not working after resume
On Mon, Feb 23, 2004 at 05:27:08PM +0100, Cristiano De Michele wrote: On Mon, 2004-02-23 at 17:13, Branden Robinson wrote: On Mon, Feb 23, 2004 at 04:11:13PM +0100, Cristiano De Michele wrote: actually I have 4.3.0-2 install and it shows up same output that is strings /usr/X11R6/lib/modules/drivers/radeon_drv.o | grep RADEONDRIResume RADEONDRIResume is that ok? Probably, yes. Our object files are going to differ a little because I'm on PowerPC and you're on x86. But I don't think the symbol name showing up twice vs. once is a cause for concern. no no it shows up once because the former line has been broken... /me smacks forehead Oh. Duh. :) Maybe this DRI resume patch doesn't work as well as was thought? anyway I fixed the problem using hibernate script of swsusp2 (swsusp.sf.net) with the following option: SWSUSP_LEAVE_X_BEFORE_SUSPEND=nvidia that works for my ati IGP320 card as well, Glad to hear of the workaround. -- G. Branden Robinson| The National Security Agency is Debian GNU/Linux | working on the Fourth Amendment [EMAIL PROTECTED] | thing. http://people.debian.org/~branden/ | -- Phil Lago, Deputy XD, CIA signature.asc Description: Digital signature
Bug#234085: x-window-system-core: xmodmap Happy Hacker keyboard doesn
On Mon, Feb 23, 2004 at 06:23:18PM +0100, Jacob Kolding wrote: On Sun, 2004-02-22 at 23:49, Branden Robinson wrote: On Sun, Feb 22, 2004 at 11:02:32AM +0100, Jacob Kolding wrote: The problem still exist with xfree86 4.3.-2 packages. Okay. Can you please mail [EMAIL PROTECTED] the contents of your /etc/X11/XF86Config-4 file? I'd like to see how XKB is configured. [...] Section InputDevice Identifier Generic Keyboard Driver keyboard Option CoreKeyboard Option XkbRules xfree86 Option XkbModel pc104 Option XkbLayout us_intl EndSection What happens if you replace us_intl with dk? -- 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 signature.asc Description: Digital signature
Bug#233569: xlibs: raise the number of maximum clients to 512
On Tue, Feb 24, 2004 at 12:56:21AM +0100, Michel Dänzer wrote: On Sat, 2004-02-21 at 19:12, Branden Robinson wrote: On Fri, Feb 20, 2004 at 11:05:55PM -0500, xavier wrote: Is there a drawback in doing such thing ? I don't know. Possibly resource consumption in the X server, but most machines today have a lot more to spare in the way of resources than machines did when this limit was probably initially set. If not, do you think there might be a possibility for debian to compile it with 512 max clients ? I do think it's a possibility yes. I just want to find out from someone who knows whether there would be any serious drawbacks to doing so. See http://www.mail-archive.com/devel@xfree86.org/msg01104.html (Start of thread: http://www.mail-archive.com/devel@xfree86.org/msg01095.html) Sounds like they think it's a bad idea. That changing MAXCLIENTS breaks module compatibility is a bit of a concern. -- G. Branden Robinson|Kissing girls is a goodness. It is Debian GNU/Linux |a growing closer. It beats the [EMAIL PROTECTED] |hell out of card games. http://people.debian.org/~branden/ |-- Robert Heinlein signature.asc Description: Digital signature
Re: Changed library interface causing FTBFS of cernlib?
Branden Robinson [EMAIL PROTECTED] writes: On Mon, Feb 23, 2004 at 06:24:31AM -0500, Kevin B. McCarty wrote: Hi, I've gotten a bunch of FTBFSes for cernlib 2003.09.03-4 which I assume are related to the new X release. The problem is that when linking a program with these flags, Yes, I'm getting a few strange reports like this. To be honest I don't yet know if it's a package bug or some sort of weirdness inflicted on the buildds due to kludge necessary to work around the fact that xlibs-dev is now an architecture-independent pseudopackage. Err, the kludge was simply making xlibs-dev from 4.2.1 available to the buildds and hiding the arch:all 4.3.0 version. I can't conceive how that would cause any problems - never mind something like this. I haven't looked at the log, but I suspect this is probably just more fallout from the hanging postrm bug that's in -2[1]. -- James [1] As I explained on IRC: sbuild installs new X library packages, builds package, tries to remove them, postrm hangs due to missing argument to grep, sbuild times out and kills the dpkg process, dpkg gets confused and thinks the library package it was in the process of removing is still installed but with no files... next package that tries to use that library fails (often in bizarre ways) because the library's not actually there.
Processed: reassign 234342 to xserver-xfree86 ...
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.7.95.1 reassign 234342 xserver-xfree86 Bug#234342: =?iso-8859-15?q?xfree86-common=3A_X_doesn=27t_restore_proper_text_mode_on?= =?iso-8859-15?q?_=7Bexit=2Cconsole_switch=7D=0D=0Ai_have_installed_svgatextm?= =?iso-8859-15?q?ode_=5B1=5D=2C_so_that_my_console_is_set_to_a=0D=0Anon-stand?= =?iso-8859-15?q?ard_100x37_text_mode_during_system_initialization?= Bug reassigned from package `xfree86-common' to `xserver-xfree86'. retitle 234342 xserver-xfree86: text VT restoration broken when svgatextmode used Bug#234342: =?iso-8859-15?q?xfree86-common=3A_X_doesn=27t_restore_proper_text_mode_on?= =?iso-8859-15?q?_=7Bexit=2Cconsole_switch=7D=0D=0Ai_have_installed_svgatextm?= =?iso-8859-15?q?ode_=5B1=5D=2C_so_that_my_console_is_set_to_a=0D=0Anon-stand?= =?iso-8859-15?q?ard_100x37_text_mode_during_system_initialization?= Changed Bug title. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Processed: severity of 233933 is wishlist, reassign 233933 to xfree86 ...
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.7.95.1 severity 233933 wishlist Bug#233933: document that use of ImPS/2+gpmdata with imps2+raw causes pauses Severity set to `wishlist'. reassign 233933 xfree86 Bug#233933: document that use of ImPS/2+gpmdata with imps2+raw causes pauses Bug reassigned from package `xserver-xfree86' to `xfree86'. retitle 233933 xfree86 xfree86: document what protocols not to use with /dev/gpmdata in NEWS file Bug#233933: document that use of ImPS/2+gpmdata with imps2+raw causes pauses Changed Bug title. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Re: nice xserver
On Mon, Feb 23, 2004 at 07:35:11PM -0800, Nano Nano wrote:
Last summer there was a priority=low debconf question to nice -10 the X
server. It appears to be gone.
I ask because in top XFree86 seems to be one of the top programs.
Where did it go and do I want it?
Still there as far as I know. Attaching evidence thereof.
--
G. Branden Robinson| You are not angry with people when
Debian GNU/Linux | you laugh at them. Humor teaches
[EMAIL PROTECTED] | them tolerance.
http://people.debian.org/~branden/ | -- W. Somerset Maugham
#!/bin/sh
# Debian xserver-common package configuration script
# Copyright 2000--2003 Branden Robinson.
# Licensed under the GNU General Public License, version 2. See the file
# /usr/share/common-licenses/GPL or http://www.gnu.org/copyleft/gpl.txt.
# $Id: xserver-common.config.in 1044 2004-02-16 17:40:33Z branden $
set -e
# source debconf library
. /usr/share/debconf/confmodule
THIS_PACKAGE=xserver-common
THIS_SCRIPT=config
#INCLUDE_SHELL_LIB#
CONFIG_DIR=/etc/X11
XWRAPPER_CONFIG=$CONFIG_DIR/Xwrapper.config
OLD_CONFIG_FILE=$CONFIG_DIR/Xserver
allowed_users_english_to_actual () {
case $1 in
Root Only)
echo rootonly
;;
Console Users Only)
echo console
;;
Anybody)
echo anybody
;;
*)
# garbage input; return default
observe allowed_users_english_to_actual(): unrecognized input \$1\; \
using default
echo console
;;
esac
}
allowed_users_actual_to_english () {
case $1 in
rootonly)
echo Root Only
;;
console)
echo Console Users Only
;;
anybody)
echo Anybody
;;
*)
# garbage input; return default
observe allowed_users_actual_to_english(): unrecognized input \$1\; \
using default
echo Console Users Only
;;
esac
}
validate_nice_value () {
local retval
retval=1
# first, try to subtract number from itself to validate numeric input
# (expr is noisy, always throw away its output)
set +e
expr $1 - $1 /dev/null 21
if [ $? -ne 2 ]; then
# now check for valid range
if expr $1 = -20 /dev/null 21
expr $1 = 19 /dev/null 21; then
retval=0
fi
fi
set -e
return $retval
}
# set the default nice value based on what Linux kernel version is being used;
# the new process scheduler in 2.5, to be released in 2.6, makes a default of
# -10 a bad idea; with that scheduler, the X server should run with priority 0
NICE_DEFAULT=-10
if [ $(uname -s) = Linux ]; then
LINUX_KERNEL_FLAVOR=$(uname -r)
LINUX_KERNEL_VERSION=${LINUX_KERNEL_FLAVOR%%-*}
# it kinda sucks that I have to use dpkg for this
if dpkg --compare-versions $LINUX_KERNEL_VERSION gt 2.5; then
observe Linux kernel 2.5 detected; using 0 as default nice value
NICE_DEFAULT=0
fi
fi
# debconf is not a registry; use the current contents of the default display
# manager to pre-answer the question if possible
CURRENT_ALLOWED_USERS=
CURRENT_NICE_VALUE=
# scan the X wrapper config file for existing settings, if it exists
if [ -e $XWRAPPER_CONFIG ]; then
if MATCHES=$(grep ^allowed_users=.\+ $XWRAPPER_CONFIG); then
CURRENT_ALLOWED_USERS=$(echo ${MATCHES##*=} | head -n 1)
fi
if MATCHES=$(grep ^nice_value=.\+ $XWRAPPER_CONFIG); then
CURRENT_NICE_VALUE=$(echo ${MATCHES##*=} | head -n 1)
fi
else
# if upgrading from xserver-common prior to 4.0.1-6, scan old wrapper config
# file for a default setting of allowed users (nice value support wasn't
# implemented back then)
if dpkg --compare-versions $2 lt 4.1.0-6; then
if [ -e $OLD_CONFIG_FILE ]; then
CURRENT_ALLOWED_USERS=$(sed -n '2p' $OLD_CONFIG_FILE |
tr '[[:upper:]]' '[[:lower:]]')
fi
fi
fi
if [ -n $CURRENT_ALLOWED_USERS ]; then
observe setting xserver-common/xwrapper/allowed_users from configuration \
file
safe_debconf db_set xserver-common/xwrapper/allowed_users \
$(allowed_users_actual_to_english \
$CURRENT_ALLOWED_USERS)
fi
if [ -n $CURRENT_NICE_VALUE ]; then
observe setting xserver-common/xwrapper/nice_value from configuration file
if validate_nice_value $CURRENT_NICE_VALUE; then
safe_debconf db_set xserver-common/xwrapper/nice_value \
$CURRENT_NICE_VALUE
fi
fi
safe_debconf db_input low xserver-common/xwrapper/allowed_users
safe_debconf db_go
RET=
if db_get xserver-common/xwrapper/allowed_users; then
if [ -n $RET ]; then
safe_debconf db_set xserver-common/xwrapper/actual_allowed_users \
$(allowed_users_english_to_actual $RET)
fi
fi
# next question requires input validation; assume safe valid value already
# present (possibly the template default)
SAFE=
if db_get xserver-common/xwrapper/nice_value; then
SAFE=$RET
fi
# make sure it's really safe; if not, use the default
if !
Bug#234496: xserver-xfree86: xserver freeze all input devices randomely
-BEGIN PGP SIGNED MESSAGE- Package: xserver-xfree86 Version: 4.3.0-2 Severity: important Tags: sid I have a radeon card. But this bug seams to be in other driver. The system freeze the mouse and the keyboard (together) randomely. All other like opening windows (remotely) or the normal displayfunktionality works on. I only have no control over it. I can also not switch to a console so I have to login from remote and kill the xserver with loosing all open windows. - -- Package-specific info: 01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility M6 LY 01:00.0 Class 0300: 1002:4c59 # (Type man XF86Config at the shell prompt.) # Section Files #FontPath unix/:7100# local font server FontPathunix/:7110# local font server # if the local font server has problems, we can fall back on these FontPath/var/lib/defoma/x-ttcidfont-conf.d/dirs/CID FontPath/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType FontPath/usr/X11R6/lib/X11/fonts/misc FontPath/usr/X11R6/lib/X11/fonts/100dpi/:unscaled FontPath/usr/X11R6/lib/X11/fonts/75dpi/:unscaled FontPath/usr/X11R6/lib/X11/fonts/Type1 FontPath/usr/X11R6/lib/X11/fonts/Speedo FontPath/usr/X11R6/lib/X11/fonts/100dpi FontPath/usr/X11R6/lib/X11/fonts/75dpi FontPath/usr/local/StarOffice52/share/fonts/75dpi/:unscaled FontPath/usr/local/StarOffice52/share/fonts/type1 FontPath/usr/local/StarOffice52/share/fonts/75dpi EndSection Section Module LoadGLcore Loadbitmap Loaddbe Loadddc Loaddri Loadextmod Loadfreetype Loadglx Loadspeedo Loadtype1 Loadvbe Loadwacom EndSection Section InputDevice Identifier Keyboard Driver keyboard Option CoreKeyboard Option XkbRules xfree86 Option XkbModel pc102 Option XkbLayout de EndSection Section InputDevice Identifier Trackpoint Driver mouse Option CorePointer Option Device/dev/psaux Option Protocol PS/2 EndSection Section InputDevice Identifier USB Mouse Driver mouse Option SendCoreEventstrue Option Device/dev/input/mice Option Protocol ImPS/2 Option Buttons 5 Option ZAxisMapping 4 5 EndSection Section InputDevice Identifier Stift 1 Driver wacom Option Device/dev/input/event0 Option Type stylus Option Mode absolute Option USB on Option Tilt on Option ResolutionX 1270 Option ResolutionY 1270 EndSection Section InputDevice Identifier Stift 2 Driver wacom Option Device/dev/input/event0 Option Type stylus Option Mode absolute Option USB on Option Tilt on EndSection Section InputDevice Identifier Radierer 1 Driver wacom Option Device/dev/input/event0 Option Type eraser Option Mode absolute Option USB on Option Tilt on Option ResolutionX 1270 Option ResolutionY 1270 EndSection Section InputDevice Identifier Radierer 2 Driver wacom Option Device/dev/input/event0 Option Type eraser Option Mode absolute Option USB on Option Tilt on EndSection Section InputDevice Identifier Maus 1 Driver wacom Option SendCoreEventstrue Option Device/dev/input/event0 Option Type cursor Option Mode relative Option USB on EndSection Section Device Identifier ATI Radeon Mobility M6 LY 0 Driver radeon BusID PCI:1:0:0
Bug#234388: xserver-xfree86: [tdfx] X server refuses to use DRI at 1280x960 resolution
On Mon, Feb 23, 2004 at 03:47:23PM +, Claudio Martins wrote: Package: xserver-xfree86 Version: 4.3.0-2 Severity: important Tags: sid XFree86 refuses to use DRI at resolutions higher than 1024x768 on a 3dfx Voodoo Banshee and complains with this message on the logs: (WW) TDFX(0): [dri] To use DRI, with a 16Mb Voodoo 3 or Banshee card, you must invoke the server using a maximum resolution of 1024x768 or lower. I think this behaviour is not justified by any technical reason, This seems a hasty conclusion to reach if you're not very familiar with the driver code and the video hardware. nor does it make any sense, since this card has functioned correctly using DRI and OpenGL at resolutions as high as 1280x960, up to XFree86 version 4.2.x. Even if running certain OpenGL apps at 1280x960 would be too slow (like quake3), switching to lower res. modes like 1024x768 or 800x600 used to work okay, but now with this version the X server simply refuses to use DRI and the kernel doesn't even automatically load the drm module like it used to. Perhaps you could review the changes made to the tdfx driver between XFree86 4.2.1 and 4.3.0 (the tdfx driver has not, to date, been changed on xf-4_3-branch). It looks to me like the error message you're complaining of was not added in 4.3.0. xfree86/cvs/HEAD/xc % cvs diff -u -r xf-4_2_1 -r xf-4_3_0 programs/Xserver/hw/xfree86/drivers/tdfx Index: programs/Xserver/hw/xfree86/drivers/tdfx/Imakefile === RCS file: /cvs/xc/programs/Xserver/hw/xfree86/drivers/tdfx/Imakefile,v retrieving revision 1.21 retrieving revision 1.22 diff -u -u -r1.21 -r1.22 --- programs/Xserver/hw/xfree86/drivers/tdfx/Imakefile 21 May 2001 21:43:55 - 1.21 +++ programs/Xserver/hw/xfree86/drivers/tdfx/Imakefile 17 Feb 2003 17:06:44 - 1.22 @@ -1,4 +1,4 @@ -XCOMM $XFree86: xc/programs/Xserver/hw/xfree86/drivers/tdfx/Imakefile,v 1.21 2001/05/21 21:43:55 dawes Exp $ +XCOMM $XFree86: xc/programs/Xserver/hw/xfree86/drivers/tdfx/Imakefile,v 1.22 2003/02/17 17:06:44 dawes Exp $ XCOMM XCOMM This is the Imakefile for the TDFX driver. XCOMM @@ -36,7 +36,7 @@ -I$(XF86SRC)/xaa -I$(XF86SRC)/rac -I$(XF86SRC)/int10 \ -I$(SERVERSRC)/fb -I$(XF86SRC)/xaa -I$(XF86SRC)/ramdac \ -I$(XF86SRC)/vgahw -I$(XF86SRC)/ddc -I$(XF86SRC)/i2c \ - -I$(XF86SRC)/ddc -I$(XF86OSSRC)/vbe -I$(SERVERSRC)/Xext \ + -I$(XF86SRC)/ddc -I$(XF86SRC)/vbe -I$(SERVERSRC)/Xext \ -I$(FONTINCSRC) -I$(SERVERSRC)/include -I$(XINCLUDESRC) \ -I$(EXTINCSRC) -I$(SERVERSRC)/render \ $(DRIINCLUDES) Index: programs/Xserver/hw/xfree86/drivers/tdfx/tdfx.h === RCS file: /cvs/xc/programs/Xserver/hw/xfree86/drivers/tdfx/tdfx.h,v retrieving revision 1.25 retrieving revision 1.27 diff -u -u -r1.25 -r1.27 --- programs/Xserver/hw/xfree86/drivers/tdfx/tdfx.h 18 Aug 2001 02:51:13 - 1.25 +++ programs/Xserver/hw/xfree86/drivers/tdfx/tdfx.h 17 Oct 2002 01:02:08 - 1.27 @@ -5,7 +5,7 @@ Copyright: 1998,1999 */ -/* $XFree86: xc/programs/Xserver/hw/xfree86/drivers/tdfx/tdfx.h,v 1.25 2001/08/18 02:51:13 dawes Exp $ */ +/* $XFree86: xc/programs/Xserver/hw/xfree86/drivers/tdfx/tdfx.h,v 1.27 2002/10/17 01:02:08 dawes Exp $ */ #ifndef _TDFX_H_ #define _TDFX_H_ @@ -138,7 +138,7 @@ unsigned char *MMIOBase[MAXCHIPS]; unsigned char *FbBase; unsigned char *myFbBase; - unsigned int PIOBase[MAXCHIPS]; + IOADDRESS PIOBase[MAXCHIPS]; long FbMapSize; int pixelFormat; int stride; @@ -219,6 +219,8 @@ int videoKey; void (*VideoTimerCallback)(ScrnInfoPtr, Time); FBLinearPtr overlayBuffer; + FBLinearPtr overlayBuffer2; /* for double-buffering */ + int whichOverlayBuffer; /* flip-flop */ FBAreaPtr textureBuffer; Bool TextureXvideo; XF86VideoAdaptorPtr overlayAdaptor; Index: programs/Xserver/hw/xfree86/drivers/tdfx/tdfx_dri.c === RCS file: /cvs/xc/programs/Xserver/hw/xfree86/drivers/tdfx/tdfx_dri.c,v retrieving revision 1.23 retrieving revision 1.25 diff -u -u -r1.23 -r1.25 --- programs/Xserver/hw/xfree86/drivers/tdfx/tdfx_dri.c 21 May 2001 21:43:55 - 1.23 +++ programs/Xserver/hw/xfree86/drivers/tdfx/tdfx_dri.c 8 Feb 2003 21:26:59 - 1.25 @@ -1,4 +1,4 @@ -/* $XFree86: xc/programs/Xserver/hw/xfree86/drivers/tdfx/tdfx_dri.c,v 1.23 2001/05/21 21:43:55 dawes Exp $ */ +/* $XFree86: xc/programs/Xserver/hw/xfree86/drivers/tdfx/tdfx_dri.c,v 1.25 2003/02/08 21:26:59 dawes Exp $ */ #include xf86.h #include xf86_OSproc.h @@ -195,7 +195,7 @@ else pConfigs[i].doubleBuffer = FALSE; pConfigs[i].stereo = FALSE; - pConfigs[i].bufferSize = 16; + pConfigs[i].bufferSize = (pScrn-bitsPerPixel==32) ? 32 : 24;
Bug#233202: marked as done (xserver-xfree86: [ati/radeon] XVideo does not work after suspend/resume cycle on Radeon chipsets)
Your message dated Tue, 24 Feb 2004 02:25:16 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#233202: xserver-xfree86: xvideo extensions not working after resume 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; 17 Feb 2004 11:39:45 + From [EMAIL PROTECTED] Tue Feb 17 03:39:45 2004 Return-path: [EMAIL PROTECTED] Received: from piro.phys2.uniroma1.it [151.100.123.25] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1At3Zo-0007es-00; Tue, 17 Feb 2004 03:39:44 -0800 Received: from demichel by piro.phys2.uniroma1.it with local (Exim 3.36 #1 (Debian)) id 1At3Zl-YA-00; Tue, 17 Feb 2004 12:39:41 +0100 Content-Type: text/plain; charset=us-ascii MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Cristiano De Michele [EMAIL PROTECTED] To: Debian Bug Tracking System [EMAIL PROTECTED] Subject: xserver-xfree86: xvideo extensions not working after resume X-Mailer: reportbug 2.47 Date: Tue, 17 Feb 2004 12:39:41 +0100 Message-Id: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_02_16 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-5.0 required=4.0 tests=HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2004_02_16 X-Spam-Level: Package: xserver-xfree86 Version: 4.3.0-0pre1v5 Severity: grave Tags: experimental Justification: renders package unusable I have a 2.4.24 kernel + swsusp2.0 + acpi + cpufreq on a Compaq evo N1015v with AMD 2000+ and Ati IGP 320M graphic adapter. Xvideo extensions (2D acceleration) work perfectly but if I perform a suspend/resume cycle, they do not work anymore and if I try for example to watch a movie I get only vertical multicolor bands... -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.4.24-swsusp2.0 Locale: LANG=C, LC_CTYPE=C Versions of packages xserver-xfree86 depends on: ii debconf1.4.10Debian configuration management sy ii libc6 2.3.2.ds1-11 GNU C Library: Shared libraries an ii xserver-common 4.3.0-0pre1v5 files and utilities common to all ii zlib1g 1:1.2.1-4 compression library - runtime -- debconf information: xserver-xfree86/config/device/identifier: Generic Video Card 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: true xserver-xfree86/config/device/bus_id: * xserver-xfree86/config/inputdevice/keyboard/layout: it * xserver-xfree86/config/monitor/horiz-sync: 28-50 xserver-xfree86/config/monitor/identifier: Generic Monitor 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: true 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: pc104 xserver-xfree86/config/write_dri_section: true * xserver-xfree86/config/device/driver: ati * xserver-xfree86/config/monitor/vert-refresh: 43-75 * xserver-xfree86/config/display/default_depth: 24 xserver-xfree86/config/inputdevice/mouse/zaxismapping: true * xserver-xfree86/config/display/modes: 1024x768, 800x600, 640x480 xserver-xfree86/config/device/bus_id_error: xserver-xfree86/config/modules: GLcore, bitmap, dbe, ddc, dri, extmod, freetype, glx, int10, record, speedo, type1, vbe * xserver-xfree86/config/inputdevice/keyboard/options: xserver-xfree86/config/nonnumeric_string_error: * xserver-xfree86/config/inputdevice/mouse/protocol: PS/2 shared/multiple_possible_x-servers: xserver-xfree86/config/null_string_error: xserver-xfree86/config/monitor/range_input_error: xserver-xfree86/autodetect_video_card: true * xserver-xfree86/config/inputdevice/keyboard/variant: * xserver-xfree86/config/inputdevice/mouse/port: /dev/psaux xserver-xfree86/config/write_files_section: true
Processed: retitle 234388 to xserver-xfree86: [tdfx] want DRI support at 1280x960 on Voodoo Banshee rev 3 ... ...
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.7.95.1 retitle 234388 xserver-xfree86: [tdfx] want DRI support at 1280x960 on Voodoo Banshee rev 3 Bug#234388: xserver-xfree86: [tdfx] X server refuses to use DRI at 1280x960 resolution Changed Bug title. severity 234388 normal Bug#234388: xserver-xfree86: [tdfx] want DRI support at 1280x960 on Voodoo Banshee rev 3 Severity set to `normal'. tags 234388 + upstream Bug#234388: xserver-xfree86: [tdfx] want DRI support at 1280x960 on Voodoo Banshee rev 3 Tags were: sid 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#234444: xserver-xfree86: dri doesn't seem to work
reassign 23 xlibmesa-dri retitle 23 xlibmesa-dri: DRI-based hardware 3D acceleration broken due to missing sse_test_dummy symbol tag 23 - sid merge 23 229984 thanks On Mon, Feb 23, 2004 at 11:36:41PM +0100, Michal Cihar wrote: Package: xserver-xfree86 Version: 4.3.0-2 Severity: important Tags: sid dri doesn't seem to work after update to 4.3.0-2, the version from experimental worked fine (after some tweaks, see Bug#225759) with same configuration and hardware. This bug has already been filed five times. [The following is a form letter.] Hello, You recently filed a duplicate bug report against a Debian package; that is, the problem had already been reported. While there is often nothing inherently wrong with doing so, the filing of duplicate reports can cause Debian package maintainers to spend time performing triage and maintenance operations on bug reports (e.g., instructing the Debian Bug Tracking System to merge the duplicates) that could otherwise be spent resolving problems and doing other work on the package. One very good way to file bugs with the Debian Bug Tracking System is to use the reportbug package and command of the same name. A very nice feature of reportbug is that, if the machine where you run it has network access to the World Wide Web, it can query the Debian Bug Tracking System and show you existing reports. This reduces the chance that you'll file a duplicate report, and offers you the option of adding follow-up information to an existing bug report. This is especially valuable if you have unique information to add to an existing report, because this way information relevant to the problem is gathered together in one place as opposed to being scattered among multiple, duplicate bug reports where some facts may be overlooked by the package maintainers. The reportbug program also does a lot of automatic information-gathering that helps package maintainers to understand your system configuration, and also ensures that your message to the Debian Bug Tracking System is well-formed so that it is processed correctly by the automated tools that manage the reports. (If you've ever gotten a bounce message from the Debian Bug Tracking System that tells you your message couldn't be processed, you might appreciate this latter feature.) Therefore, I strongly urge you to give reportbug a try as your primary bug reporting tool for the Debian System. One way to install reportbug is with apt-get; for example: # apt-get install reportbug The reportbug command has a few different modes that cater to different levels of user expertise. If this message has contained a lot of jargon that is unfamiliar to you, you likely want to use reportbug's novice mode; here's one way to do that. $ reportbug --mode=novice Please enter the name of the package in which you have found a problem, or type 'other' to report a more general problem. If you're more sophisticated, or if you are not using the released version of Debian (stable), but instead Debian testing or unstable, you should use reportbug's standard mode. $ reportbug Please enter the name of the package in which you have found a problem, or type 'other' to report a more general problem. The reportbug command is extensively documented in its usage message and manual page. Commands to view these pieces of documentation are: $ reportbug --help | more $ man reportbug (The output of the above commands has been omitted from this message.) Thanks for using the Debian system! -- G. Branden Robinson|People are equally horrified at Debian GNU/Linux |hearing the Christian religion [EMAIL PROTECTED] |doubted, and at seeing it http://people.debian.org/~branden/ |practiced. -- Samuel Butler signature.asc Description: Digital signature
Bug#234093: xvattr
On Mon, Feb 23, 2004 at 11:11:06PM +0100, Michal Čihař wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi I had simmilar problem and it was caused by bad XVideo setting, check output of xvattr, most values on 0 are best to start with. Did you mean to send this to the bug submitter? If so, you need to use the [EMAIL PROTECTED] address. -- G. Branden Robinson| The noble soul has reverence for Debian GNU/Linux | itself. [EMAIL PROTECTED] | -- Friedrich Nietzsche http://people.debian.org/~branden/ | signature.asc Description: Digital signature
Processed: Re: Bug#234444: xserver-xfree86: dri doesn't seem to work
Processing commands for [EMAIL PROTECTED]: reassign 23 xlibmesa-dri Bug#23: xserver-xfree86: dri doesn't seem to work Bug reassigned from package `xserver-xfree86' to `xlibmesa-dri'. retitle 23 xlibmesa-dri: DRI-based hardware 3D acceleration broken due to missing sse_test_dummy symbol Bug#23: xserver-xfree86: dri doesn't seem to work Changed Bug title. tag 23 - sid Bug#23: xlibmesa-dri: DRI-based hardware 3D acceleration broken due to missing sse_test_dummy symbol Tags were: sid Tags removed: sid merge 23 229984 Bug#229984: xlibmesa-dri: DRI-based hardware 3D acceleration broken due to missing sse_test_dummy symbol Bug#23: xlibmesa-dri: DRI-based hardware 3D acceleration broken due to missing sse_test_dummy symbol Bug#233582: xlibmesa-dri: DRI-based hardware 3D acceleration broken due to missing sse_test_dummy symbol Bug#233670: xlibmesa-dri: DRI-based hardware 3D acceleration broken due to missing sse_test_dummy symbol Bug#233743: xlibmesa-dri: DRI-based hardware 3D acceleration broken due to missing sse_test_dummy symbol Bug#233780: xlibmesa-dri: DRI-based hardware 3D acceleration broken due to missing sse_test_dummy symbol Merged 229984 233582 233670 233743 233780 23. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Processed: tagging 234452
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.7.95.1 # I could use some assistance on this one tags 234452 + help Bug#234452: [libx11-6]: libX11.so.6: failed to map segment from shared object: Cannot allocate memory There were no tags set. Tags added: help End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Bug#234073: Crashes machine on startup on Alpha with Radeon 7500
On Sun, Feb 22, 2004 at 02:03:27PM +0100, Falk Hueffner wrote:
Branden Robinson [EMAIL PROTECTED] writes:
10 is R_ALPHA_SREL32, I guess I could come up with a simple patch
but I assume this is already fixed upstream, maybe you could check
that.
It doesn't look good:
[0] [EMAIL
PROTECTED]:~/packages/xfree86/cvs/HEAD/xc/programs/Xserver/hw/xfree86/loader
% grep R_ALPHA_SREL32 *
elf.h:#define R_ALPHA_SREL3210 /* PC relative 32 bit */
[0] [EMAIL
PROTECTED]:~/packages/xfree86/cvs/HEAD/xc/programs/Xserver/hw/xfree86/loader
%
That's it...
Hm. Here's a totally untested patch (sorry, I don't have much time
right now):
--- /cvs/xc/programs/Xserver/hw/xfree86/loader/elfloader.c 2004-02-21
19:14:05.0 +0100
+++ elfloader.c 2004-02-22 13:56:39.0 +0100
@@ -1596,6 +1596,20 @@
break;
}
+case R_ALPHA_SREL32:
+ {
+ dest32 = (unsigned int *)(secp + rel-r_offset);
+ symval += rel-r_addend;
+ symval -= (unsigned long) dest32;
+ if ((long)symval = 0x8000
+ || (long)symval -(long)0x8000)
+ FatalError(R_ALPHA_SREL32 overflow for %s: %lx\n,
+ ElfGetSymbolName(elffile, ELF_R_SYM(rel-r_info)),
+ symval);
+ *dest32 = symval;
+ break;
+ }
+
#endif /* alpha */
#if defined(__mc68000__)
case R_68K_32:
In the meantime, does xserver-xfree86-dbg work?
No, same effect; it seems the relocation errors don't really have
anything to do with it.
Okay. I'm going to apply this patch, but because the elfloader object
isn't even in the debugging server (because the modules are linked
directly into the huge XFree86-debug object), this isn't the real
problem you're seeing.
It may be necessary to attach gdb to the XFree86-debug server from a
remote terminal to locate the source of the problem.
Unless you can ulimit -c unlimited and get a good backtrace off the core
from XFree86-debug?
--
G. Branden Robinson|It's like I have a shotgun in my
Debian GNU/Linux |mouth, I've got my finger on the
[EMAIL PROTECTED] |trigger, and I like the taste of
http://people.debian.org/~branden/ |the gunmetal. -- Robert Downey, Jr.
signature.asc
Description: Digital signature
Bug#234025: Fwd: Re: Bug#234025: xserver-xfree86: ati/radeon : dist-upgrade to xfree 4.3, display almost unreadable
Moritz Muehlenhoff wrote: [Forwarding my post to debian-x@ into the bug tracking system] From: Moritz Muehlenhoff [EMAIL PROTECTED] Newsgroups: gmane.linux.debian.devel.x Subject: Re: Bug#234025: xserver-xfree86: ati/radeon : dist-upgrade to xfree 4.3, display almost unreadable Merwan wrote: After a dist-upgrade under sid which resulted into an upgrade of xfree to 4.3, the display brightness is very high and it's difficult to see anything. There were no problems with the last version of xfree (4.2.?) My video card is an AIW Radeon 7500. Does your card have an S-Video connector? I had the same problem with my Radeon 7500 (plain, without AIW) with 4.2.* and 4.3pre* if I had booted with the S-Video cable plugged into the card, but not in the TV, so I guess that's an upstream/hardware related problem. The XFree bug tracking system doesn't list this bug, though. Actually, I tried to start Xfree with the S-Video cable unplugged from the PC and... it works ! With the previous version of XFree, there was no problem if the TV was plugged but now there is. So, maybe it is possible to do something to avoid this in the code ? Anyway, thanks a lot for your help.
Bug#234073: Crashes machine on startup on Alpha with Radeon 7500
Branden Robinson [EMAIL PROTECTED] writes: It may be necessary to attach gdb to the XFree86-debug server from a remote terminal to locate the source of the problem. Unless you can ulimit -c unlimited and get a good backtrace off the core from XFree86-debug? Given that it kills the kernel, both methods don't seem very viable... the best I could try is redirect the log to the networks somehow and see what occurs last. Do you have any recommendation how to do so? In case the console output of the X process contains everything /var/log/XFree.log contains, I could just use ssh. -- Falk
X Strike Force XFree86 SVN commit: r1105 - in trunk/debian: . patches
Author: branden
Date: 2004-02-24 03:51:51 -0500 (Tue, 24 Feb 2004)
New Revision: 1105
Added:
trunk/debian/patches/202_alpha_elfloader_support_R_ALPHA_SREL32.diff
Modified:
trunk/debian/changelog
trunk/debian/patches/303_arm_cache_flush.diff
Log:
Add support for R_ALPHA_SREL32 relocations in XFree86 X server's ELF
object loader; fixes Elf_RelocateEntry() Unsupported relocation type 10
warnings on Alpha; see #234073 (thanks, Falk Hueffner!).
Modified: trunk/debian/changelog
===
--- trunk/debian/changelog 2004-02-23 23:03:30 UTC (rev 1104)
+++ trunk/debian/changelog 2004-02-24 08:51:51 UTC (rev 1105)
@@ -130,8 +130,14 @@
- debian/xlibs.bug: new file
- debian/rules: ship bug script as part of xlibs package
- -- Branden Robinson [EMAIL PROTECTED] Mon, 23 Feb 2004 17:59:44 -0500
+ * Add support for R_ALPHA_SREL32 relocations in XFree86 X server's ELF
+object loader; fixes Elf_RelocateEntry() Unsupported relocation type 10
+warnings on Alpha; see #234073 (thanks, Falk Hueffner!).
+- debian/patches/202_alpha_elfloader_support_R_ALPHA_SREL32.diff: new file
+- debian/patches/303_arm_cache_flush.diff: resynced
+ -- Branden Robinson [EMAIL PROTECTED] Tue, 24 Feb 2004 03:49:00 -0500
+
xfree86 (4.3.0-2) unstable; urgency=low
* The It's like I have a shotgun in my mouth, I've got my finger on the
Added: trunk/debian/patches/202_alpha_elfloader_support_R_ALPHA_SREL32.diff
===
--- trunk/debian/patches/202_alpha_elfloader_support_R_ALPHA_SREL32.diff
2004-02-23 23:03:30 UTC (rev 1104)
+++ trunk/debian/patches/202_alpha_elfloader_support_R_ALPHA_SREL32.diff
2004-02-24 08:51:51 UTC (rev 1105)
@@ -0,0 +1,30 @@
+$Id$
+
+Fix spew from XFree86 ELF loader on Alpha: Elf_RelocateEntry() Unsupported
+relocation type 10. See Debian #234073.
+
+This patch by Falk Hueffner.
+
+--- xc/programs/Xserver/hw/xfree86/loader/elfloader.c~ 2004-02-24
03:18:23.0 -0500
xc/programs/Xserver/hw/xfree86/loader/elfloader.c 2004-02-24
03:21:14.0 -0500
+@@ -1612,6 +1612,20 @@
+ break;
+ }
+
++ case R_ALPHA_SREL32:
++ {
++ dest32 = (unsigned int *)(secp + rel-r_offset);
++ symval += rel-r_addend;
++ symval -= (unsigned long) dest32;
++ if ((long)symval = 0x8000
++ || (long)symval -(long)0x8000)
++ FatalError(R_ALPHA_SREL32 overflow for %s: %lx\n,
++ ElfGetSymbolName(elffile,
ELF_R_SYM(rel-r_info)),
++ symval);
++ *dest32 = symval;
++ break;
++ }
++
+ #endif /* alpha */
+ #if defined(__mc68000__)
+ case R_68K_32:
Property changes on:
trunk/debian/patches/202_alpha_elfloader_support_R_ALPHA_SREL32.diff
___
Name: svn:keywords
+ Id
Modified: trunk/debian/patches/303_arm_cache_flush.diff
===
--- trunk/debian/patches/303_arm_cache_flush.diff 2004-02-23 23:03:30 UTC
(rev 1104)
+++ trunk/debian/patches/303_arm_cache_flush.diff 2004-02-24 08:51:51 UTC
(rev 1105)
@@ -4,8 +4,8 @@
off?
--- xc/programs/Xserver/hw/xfree86/loader/elfloader.c~ 2003-09-18
12:13:12.0 -0500
-+++ xc/programs/Xserver/hw/xfree86/loader/elfloader.c 2003-09-18
12:13:19.0 -0500
-@@ -2424,9 +2424,7 @@
xc/programs/Xserver/hw/xfree86/loader/elfloader.c 2004-02-24
03:30:10.0 -0500
+@@ -2438,9 +2438,7 @@
val = symval - (unsigned long)dest32 + val;
val = 2;
*dest32 = (*dest32 0xff00) | (val 0x00ff);
X Strike Force XFree86 SVN commit: r1106 - trunk/debian
Author: branden
Date: 2004-02-24 03:52:34 -0500 (Tue, 24 Feb 2004)
New Revision: 1106
Modified:
trunk/debian/TODO
Log:
Add items.
Modified: trunk/debian/TODO
===
--- trunk/debian/TODO 2004-02-24 08:51:51 UTC (rev 1105)
+++ trunk/debian/TODO 2004-02-24 08:52:34 UTC (rev 1106)
@@ -52,6 +52,11 @@
* steal {U,}XTerm* app-defaults updates from HEAD and resync patches
* Ensure all patches in debian/patches are properly annotated.
* Fix #231589: call PAM modules appropriately from xdm
+* Fix #233933: add NEWS file entry telling gpmdata users to use only
+ IntelliMouse protocol due to rewrite of mouse driver; force migration in
+ debconf for /dev/gpmdata port users; make IntelliMouse only choice for
+ /dev/gpmdata port, eliminating question
+* Add NEWS item describing package split. Cover the xlib6g situation.
Probably for 4.4.0
==
Processed: retitle 233933 to xfree86: document what protocols not to use with /dev/gpmdata in NEWS file ...
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.7.95.1 retitle 233933 xfree86: document what protocols not to use with /dev/gpmdata in NEWS file Bug#233933: xfree86 xfree86: document what protocols not to use with /dev/gpmdata in NEWS file Changed Bug title. tags 233933 - wontfix Bug#233933: xfree86: document what protocols not to use with /dev/gpmdata in NEWS file Tags were: wontfix upstream Tags removed: wontfix End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Re: Bug#233867: I already know about Netscape 4.7x security issues, thank you
On Mon, 2004-02-23 at 14:14, Martin-Éric Racine wrote: To Andreas, Ondøej and other smart asses: If that broken but immensely usefull website accepted anything newer than 4.77, I would have bothered upgrading a LONG time ago. Heck, for that matter, current Mozilla builds would also work, if that was the case. No need to be rude! Our advice was to install netscape to /usr/local/ if you need to use it. There is no need to keep obsolete xlib6g in archives. -- Ondřej Surý [EMAIL PROTECTED]
Bug#234113: I have the same bug, XF86Config-4 included
Hi, I have got the same problem with my debian sid after apt-get update/upgrade. I am using the dri-trunk from http://people.debian.org/~daenzer/dri-trunk-sid/ on a i686 pc. Here is my XF86Config-4: Section InputDevice Identifier Generic Keyboard Driver keyboard Option CoreKeyboard Option XkbRules xfree86 Option XkbModel pc105 # tested also pc104 Option XkbLayout de Option XkbVariantnodeadkeys Option XkbOptionsctrl:nocaps EndSection -- Beste Gruesse / Best regards Markus Meissner
Bug#116507: (no subject)
Bug#234530: setxkbmap -layout us,lt assigns Alt_R to modifiers Mod1 and Mod5
Package: xbase-clients
Version: 4.3.0-2
If you put in XF86Config4
XkbOption XkbLayout us,lt
or change the keyboard layout directly with
setxkbmap -layout us,lt -option grp:ctrl_shift_toggle
xmodmap -pm prints
shift Shift_L (0x32), Shift_R (0x3e)
lockCaps_Lock (0x42)
control Control_L (0x25), Control_R (0x6d)
mod1Alt_L (0x40), Alt_R (0x71)
mod2Num_Lock (0x4d)
mod3
mod4Super_L (0x73), Super_R (0x74)
mod5Alt_R (0x71)
Thus Alt_R is modifier mod1 and mod5. Such situation renders xemacs21 pretty
unusuable. When pressing Alt it the issues warning
(1) (key-mapping/warning) XEmacs: Alt_R (0x71) generates both Mod1 and Mod5,
which is nonsensical.
so you practically can't use any meta key shortcuts in xemacs21 and that means
that you can't practicaly use xemacs.
With such configuration setxkbmap -print produces
xkb_keymap {
xkb_keycodes { include xfree86+aliases(qwerty) };
xkb_types { include complete };
xkb_compat{ include complete };
xkb_symbols { include pc/pc(pc105)+pc/us+pc/lt:2+group
(ctrl_shift_toggle) };
xkb_geometry { include pc(pc105) };
};
Looking at the file /etc/X11/xkb/symbols/pc you can find lines
default
xkb_symbols pc104 {
include pc/pc(basic)
key LALT { [ Alt_L, Meta_L ] };
key RALT { [ Alt_R, Meta_R ] };
key LWIN { [ Super_L ] };
key RWIN { [ Super_R ] };
key MENU { [ Menu] };
// modifier mappings
modifier_map Mod1 { Alt_L, Alt_R, Meta_L, Meta_R };
modifier_map Mod4 { Super_L, Super_R };
};
xkb_symbols pc105 {
include pc/pc(pc104)
key LSGT { type[Group1] = FOUR_LEVEL,
[ less,greater, bar,brokenbar ] };
};
In the file /etc/X11/xkb/symbols/lt there are lines
...skipped
partial default alphanumeric_keys modifier_keys
xkb_symbols basic {
...skipped
key RALT { type[Group1]=TWO_LEVEL,
[ ISO_Level3_Shift, Multi_key ] };
modifier_map Mod5 { RALT };
};
...skipped
Thus key RALT or Alt_R in lt layout is assigned to modifier Mod5 and thus the
confusion is created.
I am pointing out the problem with lt layout, yet this problem may occur using
other layouts.
Solutions to the problem:
1. Use setxkbmap -layout lt,us (us and lt interchanged places, this fixes
the problem)
2. Comment lines
key RALT { type[Group1]=TWO_LEVEL,
[ ISO_Level3_Shift, Multi_key ] };
modifier_map Mod5 { RALT };
3. Use setxkbmap -layout lt(lt_us),lt.
in file /etc/X11/xkb/symbols/lt since in the basic lt keyboard variant no
third level letters are used.
I use up to date Debian Sid with kernel 2.4.22
Mpiktas
pgpbCmhcFCTLg.pgp
Description: PGP signature
Bug#234355: xlibs: .../locale/en_US.UTF-8/Compose: dead_diaeresis space produces a diaeresis
Package: xlibs Version: 4.3.0-2 Severity: normal This is very annoying! I can no longer get a quotedbl () by pressing dead_diaeresis space, as it was always. Why this change? A diaeresis can still be produced with dead_diaeresis dead_diaeresis, should anybody need it (!?). I suggest you to apply the following patch. I hope there's no plans to change dead_acute space to produce an useles acute instead of an apostrophe... Why do people change things they don't use?? I am sorry, but I am reluctant to break with upstream practice on this issue without understanding the underlying issue a little better. Well, what can I tell you... There are people who have a keyboard with US layout, but need to type non-ascii latin characters. For example, Germans living in the US will likely have an US keyboard, but they still need to write umlauts when they write in German. Or people living in countries where keyboards are imported... sometimes keyboard availability depends on internacional prices, and there are times when you can only get an US keyboard, other times only an es-ES keyboard, and others only the ill-designed es-LA one. Anyway, these people use an US keyboard and need to input diacritics. The standard, intuitive and historical way is to use the keys labeled with symbols resembling the diacritics to input them. Thus, pressing the apostrophe key produces a dead_acute, the quote a dead_diaeresis, the circumflex a dead_circumflex, etc. The next pressed key will result in an appropiately diacriticalised(?) letter. So far, so good. But how to input the apostrophe, quotedbl, and asciicircum? The historical way was to press the key followed by a space. This is was they broke with the new en_US.UTF-8/Compose. Why dead_diaeresis space should produce quotedbl: 1. Ability to produce quotedbl. When these people decided to improve the rules file, they took out the iso9995-3 symbols from the layout pc*, variant us_intl. So, people using UTF-8 locale, and using that layout/variant combination can no longer type a quotedbl (us_intl maps the quote key to dead_diaeresis). 2. Historical/backwards compatibility. Compatiblity with *me*, the dead_diaeresis user. I'm used to type a quote that way. I'm so used to it that I always type ' ' when I use a pure US keyboard layout, and need to backspace. It's frustrating to have one's keyboard change its behaviour according to the academic theories of the last XKB commiter. 3. Compatibility with other pseudo-diacritical keys. I'm afraid of saying that, should they inutilise their composing sequences too... dead_acute space: apostrophe, dead_tilde sp: asciitilde, dead_grave sp: grave. 4. It doesn't make sense. Maybe these people thought: We were doing it wrong all the time! dead_diaeresis + space should produce a diacriticalised(?) space! That's the logical thing to do! Well, there is no such thing as SPACE WITH DIAERESIS, and that key combination only produces a DIAERESIS. Ok, their reasoning is not too far-fetched, but there's already a way to produce a lone diacritic: pressing the key two times; and see next item. 5. WHY WOULD ANYBODY WANT TO PRODUCE A DIAERESIS? I can only think of one context: when you are talking about diaeresises. Like: The diaeresis (¨) ..., or dead_diaeresis space produces '¨'!. The ratio of usage of quotedbl vs. diaeresis, I think, must be infinity to one. Even if you have a keyboard with both a quotedbl and a diaeresis key, if you press dead_diaeresis space, the most likely thing is that you want a quotedbl. I think Windows applies the same line of reasoning that the XKB people, because many times I have seen mails in which the sender quoted ¨like this¨ or ´like this´. They are obviously searching for the quote or apostrophe keys, and settle for the nearest similar-looking one. Of course they don't want the diacriticals but the quotes, because ... (see beginning of paragraph). As an addition, I think the compose sequences should be consistent across locales, but maybe I'm mistaken. And, in any case, I think the consistency trend should be in the opposite direction (there are already 9 locales with the wrong composing sequence (en_US.UTF-8 is modified by me)). $ grep ^dead_diaeresis space */Compose | expand -t1 el_GR.UTF-8/Compose:dead_diaeresis space : ¨ U00a8 el_GR.UTF-8/Compose:dead_diaeresis space : ¨ diaeresis en_US.UTF-8/Compose:dead_diaeresis space : \ quotedbl iso8859-15/Compose:dead_diaeresis space : \ quotedbl iso8859-1/Compose:dead_diaeresis space : \ quotedbl iso8859-2/Compose:dead_diaeresis space : \250 diaeresis iso8859-3/Compose:dead_diaeresis space : \250 diaeresis iso8859-7/Compose:dead_diaeresis space : \250 diaeresis iso8859-7/Compose:dead_diaeresis space : \250 diaeresis iso8859-9/Compose:dead_diaeresis space : \250 diaeresis iso8859-9e/Compose:dead_diaeresis space : \250 diaeresis
Bug#234535: xserver dies if I start gimp with LANG=no_NO.UTF-8
Package: xserver-xfree86 Version: 4.2.1-12.1 Severity: important I've tried to use UTF-8 recently. If I run localeconf, then utf-8 locales are the only ones available. But having LANG=no_NO.UTF-8 makes X crash when I run gimp and quite a few other apps too. It doen't matter what locale the xserver runs under, it is the locale setting for gimp that cause the crash. So export LANG=no_NO.UTF-8 ; gimp will kill X, no matter wheter the X server runs with LANG=no_NO or LANG=no_NO.UTF-8. My only guess is that gimp tries to render some odd strings/characters when using UTF-8. This shouldn't kill the x server though. I first saw this with the experimental xserver-xfree86-dri-trunk, but the same happens with the standard xserver in testing. This happens with several different hw drivers, both radeon, matrox, and unaccelerated framebuffer. I have also reported this bug against locales, because I don't know wheter it is a locales bug or a xserver-xfree86 bug. I'm running both xfs and xfstt. I used important severity because the effect is quite bad, still the package isn't completely unuseable. rxvt seems to work fine without taking down X. The easy workaround is to use LANG=no_NO (without the UTF-8 part) Nothing crashes in that case, but I'd like to use UTF-8 I can do some further testing (if directed), and also provide an account for further investigation. Helge Hafting
Bug#234532: xserver-xfree86: DRI doesn't work on Matrox G450 because of missing symbols
Package: xserver-xfree86 Version: 4.3.0-2 Severity: important -- Package-specific info: 01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G400 AGP (rev 82) 01:00.0 Class 0300: 102b:0525 (rev 82) # File generated by xf86config. # # Copyright (c) 1999 by The XFree86 Project, Inc. # # Permission is hereby granted, free of charge, to any person obtaining a # copy of this software and associated documentation files (the Software), # to deal in the Software without restriction, including without limitation # the rights to use, copy, modify, merge, publish, distribute, sublicense, # and/or sell copies of the Software, and to permit persons to whom the # Software is furnished to do so, subject to the following conditions: # # The above copyright notice and this permission notice shall be included in # all copies or substantial portions of the Software. # # THE SOFTWARE IS PROVIDED AS IS, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR # IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, # FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL # THE XFREE86 PROJECT BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, # WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF # OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE # SOFTWARE. # # Except as contained in this notice, the name of the XFree86 Project shall # not be used in advertising or otherwise to promote the sale, use or other # dealings in this Software without prior written authorization from the # XFree86 Project. # # ** # Refer to the XF86Config(4/5) man page for details about the format of # this file. # ** # ** # Module section -- this section is used to specify # which dynamically loadable modules to load. # ** # Section Module # This loads the DBE extension module. Loaddbe # Double buffer extension # This loads the miscellaneous extensions module, and disables # initialisation of the XFree86-DGA extension within that module. SubSection extmod Optionomit xfree86-dga # don't initialise the DGA extension EndSubSection # This loads the Type1 and FreeType font modules Loadtype1 Loadfreetype # This loads the GLX module Load glx Load drm Load dri #Load GLcore EndSection # ** # Files section. This allows default font and rgb paths to be set # ** Section Files # The location of the RGB database. Note, this is the name of the # file minus the extension (like .txt or .db). There is normally # no need to change the default. RgbPath /usr/X11R6/lib/X11/rgb # Multiple FontPath entries are allowed (which are concatenated together), # as well as specifying multiple comma-separated entries in one FontPath # command (or a combination of both methods) # # If you don't have a floating point coprocessor and emacs, Mosaic or other # programs take long to start up, try moving the Type1 and Speedo directory # to the end of this list (or comment them out). # FontPath /usr/X11R6/lib/X11/fonts/local/ FontPath /usr/X11R6/lib/X11/fonts/misc:unscaled 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/share/fonts/truetype/ FontPath /usr/X11R6/lib/X11/fonts/bitstream-vera/ FontPath /usr/X11R6/lib/X11/fonts/artwiz-fonts FontPath /usr/X11R6/lib/X11/fonts/freefont # The module search path. The default path is shown here. #ModulePath /usr/X11R6/lib/modules EndSection # ** # Server flags section. # ** Section ServerFlags # Uncomment this to cause a core dump at the spot where a signal is # received. This may leave the console in an unusable state, but may # provide a better stack trace in the core dump to aid in debugging #Option NoTrapSignals # Uncomment this to disable the server abort sequence # This allows clients to receive this key event. #Option DontZap # Uncomment this to disable the / mode switching # sequences. This allows clients to receive these key events. #Option Dont Zoom # Uncomment this to disable tuning with the xvidtune client. With # it the client can still run and fetch card and monitor attributes, # but it will not be
Bug in xbase-clients_4.1.0-16woody3_ia64.deb
Hi, during the latest apt-get update ; apt-get upgrade I got the following Messages, which I should report to that mail-adress: [...] Preparing to replace xfonts-scalable 4.1.0-16woody1 (using .../xfonts-scalable_4.1.0-16woody3_all.deb) ... Unpacking replacement xfonts-scalable ... (Reading database ... 66177 files and directories currently installed.) Preparing to replace xbase-clients 4.1.0-16woody1 (using .../xbase-clients_4.1.0-16woody3_ia64.deb) ... Warning: /etc/X11/xkb/compiled symbolic link points to the wrong place. Removing. ERROR: /etc/X11/xkb/xkbcomp exists and is not a symbolic link. This package cannot be installed until this file is removed. Aborting installation of xbase-clients package. dpkg: error processing /var/cache/apt/archives/xbase-clients_4.1.0-16woody3_ia64.deb (--unpack): subprocess pre-installation script returned error exit status 1 Analyzing /etc/X11/xkb/compiled: drwxr-xr-x 73 root root 4096 Feb 3 11:24 /etc drwxr-xr-x 19 root root 4096 Feb 24 13:45 /etc/X11 drwxr-xr-x 10 root root 4096 Feb 24 13:45 /etc/X11/xkb /etc/X11/xkb/compiled: nonexistent ERROR: /etc/X11/xkb/compiled symbolic link does not exist. Either the package didn't ship the symbolic link (a bug in the package), or dpkg failed to unpack it to the filesystem (a bug in dpkg). Please report the package name, version, and the text of the above error message(s) to debian-x@lists.debian.org. I believe, that will not cause many problems here, we use that machine usually remote and a local X-Server is not often used, but it seems, that there is an bug in an debian-Package (at least in the ia64-Version). If you need more information - just send me a mail). Bye, Wolfgang -- FH JOANNEUM / Fahrzeugtechnik Automotive Engineering Railway Engineering Austria, 8010 Graz, Alte Poststrasse 149, Tel: ++43/(0)316/5453-8418 http://www.fh-joanneum.at/fzt/
Bug#233924: xserver-xfree86: [radeon] ignoring HorizSync causes low resolution
On Fri, 2004-02-20 at 20:10, Tom Epperly wrote: I just apt-get upgrade'd to 4.3.0-2 from 4.2. Now my X11 server is coming up in a ridiculously low resolution. It's either 640x480 or 320x240 when the LCD display can do 1400x1050. By looking at /var/log/XFree86.0.log, it appears that it is ignoring my HorizSync and VertRefresh from my XF86Config-4 file. [...] (II) RADEON(0): Clone modes validation -- (WW) RADEON(0): Generic Monitor: Using default hsync range of 28.00-33.00kHz (WW) RADEON(0): Generic Monitor: using default vrefresh range of 43.00-72.00Hz The Monitor Section only applies to the primary head. For the second head, see the radeon manpage about the Clone... options. -- Earthling Michel Dänzer | Debian (powerpc), X and DRI developer Libre software enthusiast| http://svcs.affero.net/rm.php?r=daenzer
Processed: Re: Bug#234119: The standard xserver fares no better than the dri-trunk one
Processing commands for [EMAIL PROTECTED]: reassign 234119 xserver-xfree86 Bug#234119: Setting LANG=no_NO.UTF-8 cause many programs to kill the X server Bug reassigned from package `locales' to `xserver-xfree86'. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Bug#234556: xlibs random crashes with an ATI Rage Mobility
Package: xlibs Version: 4.3.0-2 Priority: standard At random time my laptop refuse to start X and the only way to fix it is to reboot. This problem seems to be related to the graphic card : ATI Rage Mobility M6 LY Other people seems to have experimented this problem on other distributions. See: http://www.linuxquestions.org/questions/archive/14/2004/01/1/116108 The most interesting erro message that I get is from my ~/.xsession-errors file. = /etc/gdm/PreSession//Default: Registering your session with wtmp and utmp /etc/gdm/PreSession//Default: running: sessreg -a -w /var/log/wtmp -u /var/run/utmp -x /var/lib/gdm/:0.Xservers -h -l :0 fleury /etc/gdm/Sessions//Gnome: checking /etc/login.defs for option UMASK /etc/gdm/Sessions//Gnome: /etc/login.defs: UMASK is 022 /etc/gdm/Sessions//Gnome: checking /etc/login.defs for option ULIMIT /etc/gdm/Sessions//Gnome: checking /etc/login.defs for option MAIL_DIR /etc/gdm/Sessions//Gnome: /etc/login.defs: MAIL_DIR is /var/mail /etc/gdm/Sessions//Gnome: using /etc/X11/Xsession.options for options SESSION_MANAGER=local/hermes:/tmp/.ICE-unix/692 The program 'gnome-panel' received an X Window System error. This probably reflects a bug in the program. The error was 'BadLength (poly request too large or internal Xlib length erro'. (Details: serial 33 error_code 16 request_code 18 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Bug in window manager: Unexpected X error: BadLength (poly request too large or internal Xlib length erro serial 592 error_code 16 request_code 18 minor_code 0) The program 'metacity' received an X Window System error. This probably reflects a bug in the program. The error was 'BadLength (poly request too large or internal Xlib length erro'. (Details: serial 33 error_code 16 request_code 18 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) The program 'nautilus' received an X Window System error. This probably reflects a bug in the program. The error was 'BadLength (poly request too large or internal Xlib length erro'. (Details: serial 33 error_code 16 request_code 18 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) The program 'battstat-applet-2' received an X Window System error. This probably reflects a bug in the program. The error was 'BadLength (poly request too large or internal Xlib length erro'. (Details: serial 33 error_code 16 request_code 18 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) The program 'gnome-terminal' received an X Window System error. This probably reflects a bug in the program. The error was 'BadLength (poly request too large or internal Xlib length erro'. (Details: serial 33 error_code 16 request_code 18 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) The program 'evolution-alarm-notify' received an X Window System error. This probably reflects a bug in the program. The error was 'BadLength (poly request too large or internal Xlib length erro'. (Details: serial 33 error_code 16 request_code 18 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) = The problem seems to be related to this: serial 33 error_code 16 request_code 18 minor_code 0 As far as I got it: error_code 16: XProtoError.16
Bug#234556: xlibs random crashes with an ATI Rage Mobility
I found another debian bug which seems to be related to mine: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=216933 http://lists.debian.org/debian-x/2004/debian-x-200401/msg00656.html In matter of fact I have a transmeta Crusoe in my laptop. But, I'm really in doubt that the on-the-fly optimizer can produce bad code that get stuck in the memory. It seems that the error occur at boot time. I really would like to dig more this problem. If anybody can help me out, I would be really pleased. Regards -- Emmanuel Fleury Computer Science Department, | Office: B1-201 Aalborg University, | Phone: +45 96 35 72 23 Fredriks Bajersvej 7E, | Fax:+45 98 15 98 89 9220 Aalborg East, Denmark | Email: [EMAIL PROTECTED]
Bug#234556: xlibs random crashes with an ATI Rage Mobility
merge 216933 234556 thanks On Tue, 2004-02-24 at 16:09, Emmanuel Fleury wrote: At random time my laptop refuse to start X and the only way to fix it is to reboot. This bug has already been reported as #216933. Please search the bug database for existing reports before entering a new one. This problem seems to be related to the graphic card : ATI Rage Mobility M6 LY As I have pointed out in the other bug, the code which generates this error is nowhere near the graphics chip, so this is unlikely. The only striking coincidence between all people seeing the problem so far has been that they're all running Transmeta CPUs. Is that the case for you as well? -- Earthling Michel Dänzer | Debian (powerpc), X and DRI developer Libre software enthusiast| http://svcs.affero.net/rm.php?r=daenzer
Processed: Re: Bug#234556: xlibs random crashes with an ATI Rage Mobility
Processing commands for [EMAIL PROTECTED]: merge 216933 234556 Bug#216933: xlibs: many clients get BadLength error from X_ChangeProperty request Bug#234556: xlibs random crashes with an ATI Rage Mobility Merged 216933 234556. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Bug#234556: xlibs random crashes with an ATI Rage Mobility
On Tue, 2004-02-24 at 16:35, Emmanuel Fleury wrote: In matter of fact I have a transmeta Crusoe in my laptop. But, I'm really in doubt that the on-the-fly optimizer can produce bad code that get stuck in the memory. It seems that the error occur at boot time. Can you elaborate on this? Doesn't it only start a while after bootup? -- Earthling Michel Dänzer | Debian (powerpc), X and DRI developer Libre software enthusiast| http://svcs.affero.net/rm.php?r=daenzer
Bug#233924: xserver-xfree86: [radeon] ignoring HorizSync causes low resolution
Michel Dänzer wrote: On Fri, 2004-02-20 at 20:10, Tom Epperly wrote: I just apt-get upgrade'd to 4.3.0-2 from 4.2. Now my X11 server is coming up in a ridiculously low resolution. It's either 640x480 or 320x240 when the LCD display can do 1400x1050. By looking at /var/log/XFree86.0.log, it appears that it is ignoring my HorizSync and VertRefresh from my XF86Config-4 file. [...] (II) RADEON(0): Clone modes validation -- (WW) RADEON(0): Generic Monitor: Using default hsync range of 28.00-33.00kHz (WW) RADEON(0): Generic Monitor: using default vrefresh range of 43.00-72.00Hz The Monitor Section only applies to the primary head. For the second head, see the radeon manpage about the Clone... options. Thanks for the suggestion. I was able to get it working with the following: Section Device Identifier Radeon Mobility M6 Driver radeon VideoRam16384 BusID PCI:01:00:00 Option dpms on Option CloneHSync31.5-80 Option CloneVRefresh 56-76 Option CloneMode 1600x1200 Option PanelOff true EndSection Tom
Bug#226430: wokraround: disable use of agpgart module
After some tests with different kernels (2.6.3, 2.4.25-1(debian package), 2.4.25 (plain kernel.org), we found out, that disabling the agpgart modules (e.g. by renaming it) prevented the Xserver from segfaulting at startup on different machines with i865G chipset. - Christian
Bug#234575: ati mobility radeon 9000 igp
Package: xserver-xfree86 Version: 4.3.0-2 I have notebook,ati mobility radeon 9000 igp and instaled fglrx driver (it load cleanly) my lspci is 00:00.0 Host bridge: ATI Technologies Inc: Unknown device 5833 (rev 02) 00:01.0 PCI bridge: ATI Technologies Inc: Unknown device 5838 00:13.0 USB Controller: ATI Technologies Inc: Unknown device 4347 (rev 01) 00:13.1 USB Controller: ATI Technologies Inc: Unknown device 4348 (rev 01) 00:14.0 SMBus: ATI Technologies Inc: Unknown device 4353 (rev 16) 00:14.1 IDE interface: ATI Technologies Inc: Unknown device 4349 00:14.3 ISA bridge: ATI Technologies Inc: Unknown device 434c 00:14.4 PCI bridge: ATI Technologies Inc: Unknown device 4342 00:14.5 Multimedia audio controller: ATI Technologies Inc: Unknown device 4341 00:14.6 Modem: ATI Technologies Inc: Unknown device 434d (rev 01) 01:05.0 VGA compatible controller: ATI Technologies Inc: Unknown device 5835 02:00.0 FireWire (IEEE 1394): Texas Instruments TSB43AB21 IEEE-1394a-2000 Controller (PHY/Link) 02:02.0 Network controller: Broadcom Corporation BCM94306 802.11g (rev 03) 02:03.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) 02:04.0 CardBus bridge: Texas Instruments: Unknown device ac54 (rev 01) 02:04.1 CardBus bridge: Texas Instruments: Unknown device ac54 (rev 01) 02:04.2 System peripheral: Texas Instruments: Unknown device 8201 (rev 01) 02:07.0 USB Controller: NEC Corporation USB (rev 43) 02:07.1 USB Controller: NEC Corporation USB (rev 43) 02:07.2 USB Controller: NEC Corporation USB 2.0 (rev 04) and /var/log/XFree86.0.log is 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-2 20040218145349 [EMAIL PROTECTED]) Release Date: 15 August 2003 X Protocol Version 11, Revision 0, Release 6.6 Build Operating System: Linux 2.4.23-1-k7 i686 [ELF] Build Date: 18 February 2004 Before reporting problems, check http://www.XFree86.Org/ to make sure that you have the latest version. Module Loader present OS Kernel: Linux version 2.6.2 ([EMAIL PROTECTED]) (gcc version 3.3.3 (Debian)) #1 Tue Feb 24 01:24:44 EST 2004 Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/XFree86.0.log, Time: Tue Feb 24 11:30:53 2004 (==) 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 xfree86 (**) XKB: rules: xfree86 (**) Option XkbModel pc104 (**) XKB: model: pc104 (**) Option XkbLayout us (**) XKB: layout: us (==) Keyboard: CustomKeycode disabled (**) |--Input Device Configured Mouse (**) |--Input Device Generic Mouse (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. (**) FontPath set to unix/:7100,/usr/lib/X11/fonts/misc,/usr/lib/X11/fonts/100dpi/:unscaled,/usr/lib/X11/fonts/75dpi/:unscaled,/usr/lib/X11/fonts/Type1,/usr/lib/X11/fonts/Speedo,/usr/lib/X11/fonts/100dpi,/usr/lib/X11/fonts/75dpi (==) RgbPath set to /usr/X11R6/lib/X11/rgb (==) ModulePath set to /usr/X11R6/lib/modules (--) using VT number 7 (WW) Open APM failed (/dev/apm_bios) (No such device) (II) Module ABI versions: XFree86 ANSI C Emulation: 0.2 XFree86 Video Driver: 0.6 XFree86 XInput driver : 0.4 XFree86 Server Extension : 0.2 XFree86 Font Renderer : 0.4 (II) Loader running on linux (II) LoadModule: bitmap (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a (II) Module bitmap: vendor=The XFree86 Project compiled for 4.3.0.1, module version = 1.0.0 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.4 (II) Loading font Bitmap (II) LoadModule: pcidata (II) Loading /usr/X11R6/lib/modules/libpcidata.a (II) Module pcidata: vendor=The XFree86 Project compiled for 4.3.0.1, module version = 1.0.0 ABI class: XFree86 Video Driver, version 0.6 (II) PCI: Probing config type using method 1 (II) PCI: Config type is 1 (II) PCI: stages = 0x03, oldVal1 = 0x803c, mode1Res1 = 0x8000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 1002,5833 card 1002,1234 rev 02 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 1002,5838 card 1002,5838 rev 00 class 06,04,00 hdr 01 (II) PCI: 00:13:0: chip 1002,4347 card 1002,434c rev 01 class 0c,03,10 hdr 80 (II) PCI: 00:13:1: chip 1002,4348 card 1002,434c rev 01 class 0c,03,10 hdr 00
Re: via_drv.o - A Backported XFree86 4.3.x/Debian Driver for VIA Video Chipsets
On Fri, 2004-02-20 at 19:14, David Martínez Moreno wrote: Speaking before really looking into the sources, I tended to think that the SDK should be a collection of files extracted from the tree, but from sparse digging in the list archives it seems that: 1) the word SDK appears a lot in the sources...it seems that there is some support in the tree for this beast. 2) Sven Luther already build such ball of files, but I haven't found any evidence of his work/fault (again, please don't be too harsh, it was a *sparse* digging). Correct on both counts AFAIK, I think you should get in touch with Sven about it. In fact, I wonder why he hasn't followed up to this, I guess it doesn't help that you don't really seem to value his work... -- Earthling Michel Dänzer | Debian (powerpc), X and DRI developer Libre software enthusiast| http://svcs.affero.net/rm.php?r=daenzer
Bug#234556: xlibs random crashes with an ATI Rage Mobility
On Tue, 2004-02-24 at 17:12, Michel Dänzer wrote: On Tue, 2004-02-24 at 16:35, Emmanuel Fleury wrote: In matter of fact I have a transmeta Crusoe in my laptop. But, I'm really in doubt that the on-the-fly optimizer can produce bad code that get stuck in the memory. It seems that the error occur at boot time. Can you elaborate on this? Doesn't it only start a while after bootup? Yes sure. In my very specific case, I noticed this bug because at boot time the desktop refuse to run. In fact, I have installed GDM and I am opening the X server directly on my account in graphical mode (I know it's bad). So, at boot time the sequence should be: X server -- GDM -- Desktop (Gnome2) But, this bug (when it occurs) seems to stop the process always at the exact same point which is when starting the Desktop (gnome-panel and so on). At this point, the mouse pointer is still active and the X server as well (I can only move the mouse, not really useful indeed). If I stop the X server and try to restart, I can't. I get the exact same error than for the gnome-panel but for the X server (I guess, I have to investigate this a little bit more now that I better know what is going on). My point is that it seems to be extremely consistant when it occurs. So, I think that there is some determinism inside this bug since it started. The theory of the wrong code being remanent in the processor does not really satisfy me because we have no real evidence of it (how could we dump the registers of the processor or the cache memory ?). The problem is that I do not exactly understand everything and I have to investigate a lot before reporting. I'll try to do some investigations and I'll probably come back with a summary of my though. I guess that I have to add this to the follow-up to the bug #216933 as it was the first. It seems to be a very interesting bug. And, actually it crash my X about one time out of three boots, so I would be very happy to get rid of it. Regards -- Emmanuel Fleury Computer Science Department, | Office: B1-201 Aalborg University, | Phone: +45 96 35 72 23 Fredriks Bajersvej 7E, | Fax:+45 98 15 98 89 9220 Aalborg East, Denmark | Email: [EMAIL PROTECTED]
Bug#234575: marked as done (ati mobility radeon 9000 igp)
Your message dated Tue, 24 Feb 2004 18:22:08 +0100 with message-id [EMAIL PROTECTED] and subject line Bug#234575: ati mobility radeon 9000 igp 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; 24 Feb 2004 16:34:17 + From [EMAIL PROTECTED] Tue Feb 24 08:34:17 2004 Return-path: [EMAIL PROTECTED] Received: from tomts20-srv.bellnexxia.net [209.226.175.74] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1AvfVh-Jt-00; Tue, 24 Feb 2004 08:34:17 -0800 Received: from [192.168.1.101] ([65.94.37.232]) by tomts20-srv.bellnexxia.net (InterMail vM.5.01.06.05 201-253-122-130-105-20030824) with ESMTP id [EMAIL PROTECTED] for [EMAIL PROTECTED]; Tue, 24 Feb 2004 11:34:07 -0500 From: Christian Bellemare [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: ati mobility radeon 9000 igp Date: Tue, 24 Feb 2004 11:34:17 -0500 User-Agent: KMail/1.5.4 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_02_22 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-4.5 required=4.0 tests=HAS_PACKAGE, MAILTO_TO_SPAM_ADDR autolearn=no version=2.60-bugs.debian.org_2004_02_22 X-Spam-Level: Package: xserver-xfree86 Version: 4.3.0-2 I have notebook,ati mobility radeon 9000 igp and instaled fglrx driver (it= =20 load cleanly) my lspci is 00:00.0 Host bridge: ATI Technologies Inc: Unknown device 5833 (rev 02) 00:01.0 PCI bridge: ATI Technologies Inc: Unknown device 5838 00:13.0 USB Controller: ATI Technologies Inc: Unknown device 4347 (rev 01) 00:13.1 USB Controller: ATI Technologies Inc: Unknown device 4348 (rev 01) 00:14.0 SMBus: ATI Technologies Inc: Unknown device 4353 (rev 16) 00:14.1 IDE interface: ATI Technologies Inc: Unknown device 4349 00:14.3 ISA bridge: ATI Technologies Inc: Unknown device 434c 00:14.4 PCI bridge: ATI Technologies Inc: Unknown device 4342 00:14.5 Multimedia audio controller: ATI Technologies Inc: Unknown device 4= 341 00:14.6 Modem: ATI Technologies Inc: Unknown device 434d (rev 01) 01:05.0 VGA compatible controller: ATI Technologies Inc: Unknown device 5835 02:00.0 FireWire (IEEE 1394): Texas Instruments TSB43AB21 IEEE-1394a-2000=20 Controller (PHY/Link) 02:02.0 Network controller: Broadcom Corporation BCM94306 802.11g (rev 03) 02:03.0 Ethernet controller: Realtek Semiconductor Co., Ltd.=20 RTL-8139/8139C/8139C+ (rev 10) 02:04.0 CardBus bridge: Texas Instruments: Unknown device ac54 (rev 01) 02:04.1 CardBus bridge: Texas Instruments: Unknown device ac54 (rev 01) 02:04.2 System peripheral: Texas Instruments: Unknown device 8201 (rev 01) 02:07.0 USB Controller: NEC Corporation USB (rev 43) 02:07.1 USB Controller: NEC Corporation USB (rev 43) 02:07.2 USB Controller: NEC Corporation USB 2.0 (rev 04) and /var/log/XFree86.0.log is 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-2 20040218145349=20 [EMAIL PROTECTED]) Release Date: 15 August 2003 X Protocol Version 11, Revision 0, Release 6.6 Build Operating System: Linux 2.4.23-1-k7 i686 [ELF] Build Date: 18 February 2004 Before reporting problems, check http://www.XFree86.Org/ to make sure that you have the latest version. Module Loader present OS Kernel: Linux version 2.6.2 ([EMAIL PROTECTED]) (gcc version 3.3.3 (Debian)) #1 = Tue=20 =46eb 24 01:24:44 EST 2004 Markers: (--) probed, (**) from config file, (=3D=3D) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (=3D=3D) Log file: /var/log/XFree86.0.log, Time: Tue Feb 24 11:30:53 2004 (=3D=3D) Using config file: /etc/X11/XF86Config-4 (=3D=3D) ServerLayout Default Layout (**) |--Screen Default Screen (0) (**) | |--Monitor Generic Monitor (**) | |--Device Generic Video Card (**) |--Input Device Generic Keyboard (**) Option XkbRules xfree86 (**) XKB: rules: xfree86 (**) Option XkbModel pc104 (**) XKB: model: pc104 (**) Option XkbLayout us (**) XKB: layout: us
Bug#234355: xlibs: .../locale/en_US.UTF-8/Compose: dead_diaeresis space produces a diaeresis
On Tue, Feb 24, 2004 at 02:03:12PM +0100, Carlos wrote: I am sorry, but I am reluctant to break with upstream practice on this issue without understanding the underlying issue a little better. [...] Why dead_diaeresis space should produce quotedbl: 1. Ability to produce quotedbl. When these people decided to improve the rules file, they took out the iso9995-3 symbols from the layout pc*, variant us_intl. So, people using UTF-8 locale, and using that layout/variant combination can no longer type a quotedbl (us_intl maps the quote key to dead_diaeresis). So, it's your contention that the new UTF-8 Compose maps break conformance with ISO 9995-3? -- G. Branden Robinson| To be is to do -- Plato Debian GNU/Linux | To do is to be -- Aristotle [EMAIL PROTECTED] | Do be do be do -- Sinatra http://people.debian.org/~branden/ | signature.asc Description: Digital signature
Bug#234113: I have the same bug, XF86Config-4 included
On Tue, Feb 24, 2004 at 12:09:06PM +0100, Markus Meissner wrote: Hi, I have got the same problem with my debian sid after apt-get update/upgrade. I am using the dri-trunk from http://people.debian.org/~daenzer/dri-trunk-sid/ on a i686 pc. Here is my XF86Config-4: Section InputDevice Identifier Generic Keyboard Driver keyboard Option CoreKeyboard Option XkbRules xfree86 Option XkbModel pc105 # tested also pc104 Option XkbLayout de Option XkbVariantnodeadkeys Option XkbOptionsctrl:nocaps EndSection Thanks. Please send you /var/log/XFree86.0.log file so we can see if there were any errors from the X server while attempting to compile your keyboard definition. Also, have you modified any of the XKB conffiles in /etc/X11/xkb? -- G. Branden Robinson| I came, I saw, she conquered. Debian GNU/Linux | The original Latin seems to have [EMAIL PROTECTED] | been garbled. http://people.debian.org/~branden/ | -- Robert Heinlein signature.asc Description: Digital signature
Bug#233933: X server 4.3 stalls for a few seconds when switching from console back to X
[Zephaniah E. Hull] [...] this is a perfect example of why trying to use a bi-directional protocol over a fifo DOES NOT WORK. [Michel Dänzer] Then why does GPM accept such protocols for the repeater in the first place? *shrug* It doesn't have such protocols. It has raw - as in, pass the data through raw. This could be useful for esoteric protocols, I suppose, and it's easy enough to implement in gpm ... but i do have to wonder if having that option (so often abused) does more harm than good. Peter signature.asc Description: Digital signature
Bug#234335: Problem on german layout fixed
Hi, the described problem appears on the german keyboard layout, too. Changing XkbModel from pc104 to pc105 fixed this for me. Robert -- Join the Debian community- http://www.debian.org ! Packages available from http://debian.physik.rub.de/debian[-non-US|-security] --- Computers are like air conditioners- they stop working properly if you open windows.
Re: Changed library interface causing FTBFS of cernlib?
On Tue, Feb 24, 2004 at 07:24:23AM +, James Troup wrote: Branden Robinson [EMAIL PROTECTED] writes: Yes, I'm getting a few strange reports like this. To be honest I don't yet know if it's a package bug or some sort of weirdness inflicted on the buildds due to kludge necessary to work around the fact that xlibs-dev is now an architecture-independent pseudopackage. Err, the kludge was simply making xlibs-dev from 4.2.1 available to the buildds and hiding the arch:all 4.3.0 version. I can't conceive how that would cause any problems - never mind something like this. I haven't looked at the log, but I suspect this is probably just more fallout from the hanging postrm bug that's in -2[1]. [...] [1] As I explained on IRC: sbuild installs new X library packages, builds package, tries to remove them, postrm hangs due to missing argument to grep, sbuild times out and kills the dpkg process, dpkg gets confused and thinks the library package it was in the process of removing is still installed but with no files... next package that tries to use that library fails (often in bizarre ways) because the library's not actually there. Thanks for the clarification. -- 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/ | signature.asc Description: Digital signature
Bug#234085: x-window-system-core: xmodmap Happy Hacker keyboard doesn
On Tue, 2004-02-24 at 07:59, Branden Robinson wrote: On Mon, Feb 23, 2004 at 06:23:18PM +0100, Jacob Kolding wrote: On Sun, 2004-02-22 at 23:49, Branden Robinson wrote: On Sun, Feb 22, 2004 at 11:02:32AM +0100, Jacob Kolding wrote: The problem still exist with xfree86 4.3.-2 packages. Okay. Can you please mail [EMAIL PROTECTED] the contents of your /etc/X11/XF86Config-4 file? I'd like to see how XKB is configured. [...] Section InputDevice Identifier Generic Keyboard Driver keyboard Option CoreKeyboard Option XkbRules xfree86 Option XkbModel pc104 Option XkbLayout us_intl EndSection What happens if you replace us_intl with dk? then my keyboard layout becomes all messed up and the xmodmap stuff still doesnt work
Processed: Re: Bug#233924: xserver-xfree86: [radeon] ignoring HorizSync causes low resolution
Processing commands for [EMAIL PROTECTED]: retitle 233924 xserver-xfree86: [ati/radeon] driver ignores HorizSync and VertRefresh settings from XF86Config-4 file on secondary head of Radeon Mobility M6 LY rev 0 Bug#233924: xserver-xfree86: [ati/radeon] driver ignores HorizSync and VertRefresh settings from XF86Config-4 file on Radeon Mobility M6 LY rev 0 Changed Bug title. tag 233924 - help Bug#233924: xserver-xfree86: [ati/radeon] driver ignores HorizSync and VertRefresh settings from XF86Config-4 file on secondary head of Radeon Mobility M6 LY rev 0 Tags were: help upstream Tags removed: help thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Bug#234496: xserver-xfree86: xserver freeze all input devices randomely
On Tue, 2004-02-24 at 08:27, Klaus Ethgen wrote: The system freeze the mouse and the keyboard (together) randomely. All other like opening windows (remotely) or the normal displayfunktionality works on. I only have no control over it. I can also not switch to a console so I have to login from remote and kill the xserver with loosing all open windows. [...] (EE) xf86OpenSerial: Cannot open device /dev/input/event0 No such device. I wonder if it's related to these errors about /dev/input/event0? -- Earthling Michel Dänzer | Debian (powerpc), X and DRI developer Libre software enthusiast| http://svcs.affero.net/rm.php?r=daenzer
Bug#234073: Crashes machine on startup on Alpha with Radeon 7500
On Tue, Feb 24, 2004 at 09:51:10AM +0100, Falk Hueffner wrote: Branden Robinson [EMAIL PROTECTED] writes: It may be necessary to attach gdb to the XFree86-debug server from a remote terminal to locate the source of the problem. Unless you can ulimit -c unlimited and get a good backtrace off the core from XFree86-debug? Given that it kills the kernel, both methods don't seem very viable... the best I could try is redirect the log to the networks somehow and see what occurs last. Do you have any recommendation how to do so? In case the console output of the X process contains everything /var/log/XFree.log contains, I could just use ssh. Falk and I discussed this on IRC. I suggested he pass -verbose 3 to the X server so that everything that would go to the log file goes to stdout as well. That may identify the module that causes the problem, and an appropriate breakpoint can be set within one of that module's functions to trace the server (remotely) until it dies. -- G. Branden Robinson|The basic test of freedom is Debian GNU/Linux |perhaps less in what we are free to [EMAIL PROTECTED] |do than in what we are free not to http://people.debian.org/~branden/ |do. -- Eric Hoffer signature.asc Description: Digital signature
Bug#234057: xlibs-data: cursor themes don't work on sparc
On Sat, 2004-02-21 at 17:10, Daniel van Eeden wrote: I've pointed /etc/alternatives/x-cursor-theme at /etc/X11/cursors/redglass.theme but my cursor stays black. I tried to s/core/redglass/ in /usr/X11R6/lib/X11/icons/default/index.theme but nothing changes. The requirements for cursor themes to work are: * libx11-6 = 4.3.0-1 * libxcursor1 * running X server = 4.3.0 Do you meet all of these? -- Earthling Michel Dänzer | Debian (powerpc), X and DRI developer Libre software enthusiast| http://svcs.affero.net/rm.php?r=daenzer
Bug#234066: xserver-xfree86: XF86Config-4 file not being used correctly
retitle 234066 xserver-xfree86: [ati/radeon] driver ignores HorizSync and VertRefresh settings from XF86Config-4 file on secondary head of Radeon Mobility M6 LY rev 0 close 234066 tag 234066 - help merge 234066 233924 thanks This bug is a duplicate of #233924, and I am closing it. Please see URL: http://bugs.debian.org/233924 for the resolution of this problem. -- G. Branden Robinson| The noble soul has reverence for Debian GNU/Linux | itself. [EMAIL PROTECTED] | -- Friedrich Nietzsche http://people.debian.org/~branden/ | signature.asc Description: Digital signature
Re: Bug#234531: lintian: Check for (build-)dep on xlibs(-dev)
On Tue, Feb 24, 2004 at 02:15:40PM +0100, Jeroen van Wolffelaar wrote: Package: lintian Version: 1.22.11 Severity: wishlist A check should be made for (build-)dependencies on xlibs and xlibs-dev, because they are transitional meta packages including all X libraries, while they are now properly split up. Fixing dependencies will make it possible to not need to install all those X libs. At the same time, lintian should also check for maintainers adding ALL xlibs(-dev) dependencies, as this is very likely incorrect. Reminder to self: Don't forget to exclude xlibs(-dev) itself from this check... This wishlist request has my whole-hearted support. Thank you! :) -- G. Branden Robinson| Debian GNU/Linux | Music is the brandy of the damned. [EMAIL PROTECTED] | -- George Bernard Shaw http://people.debian.org/~branden/ | signature.asc Description: Digital signature
Bug#233924: marked as done (xserver-xfree86: [ati/radeon] driver ignores HorizSync and VertRefresh settings from XF86Config-4 file on secondary head of Radeon Mobility M6 LY rev 0)
Your message dated Tue, 24 Feb 2004 18:28:30 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#233924: xserver-xfree86: [radeon] ignoring HorizSync causes low resolution 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; 20 Feb 2004 19:10:45 + From [EMAIL PROTECTED] Fri Feb 20 11:10:45 2004 Return-path: [EMAIL PROTECTED] Received: from smtp-4.llnl.gov [128.115.41.84] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1AuG2u-4t-00; Fri, 20 Feb 2004 11:10:45 -0800 Received: from driftcreek.llnl.gov (localhost [127.0.0.1]) by smtp-4.llnl.gov (8.12.3p2-20030917/8.12.3/LLNL evision: 1.13 $) with ESMTP id i1KJA91w007160; Fri, 20 Feb 2004 11:10:09 -0800 (PST) Message-Id: [EMAIL PROTECTED] Content-Type: text/plain; charset=us-ascii MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Tom Epperly [EMAIL PROTECTED] To: Debian Bug Tracking System [EMAIL PROTECTED] Subject: xserver-xfree86: [radeon] ignoring HorizSync causes low resolution X-Mailer: reportbug 2.48 Date: Fri, 20 Feb 2004 11:10:54 -0800 Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_02_18 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-3.5 required=4.0 tests=DATING,HAS_PACKAGE, MAILTO_TO_SPAM_ADDR autolearn=no version=2.60-bugs.debian.org_2004_02_18 X-Spam-Level: Package: xserver-xfree86 Version: 4.3.0-2 Severity: normal I just apt-get upgrade'd to 4.3.0-2 from 4.2. Now my X11 server is coming up in a ridiculously low resolution. It's either 640x480 or 320x240 when the LCD display can do 1400x1050. By looking at /var/log/XFree86.0.log, it appears that it is ignoring my HorizSync and VertRefresh from my XF86Config-4 file. -- Package-specific info: 01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility M6 LY 01:00.0 Class 0300: 1002:4c59 ### BEGIN DEBCONF SECTION # XF86Config-4 (XFree86 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.) # # 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/misc FontPath/usr/lib/X11/fonts/cyrillic FontPath/usr/lib/X11/fonts/100dpi/:unscaled FontPath/usr/lib/X11/fonts/75dpi/:unscaled FontPath/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType FontPath/var/lib/defoma/x-ttcidfont-conf.d/dirs/CID FontPath/usr/lib/X11/fonts/Type1 FontPath/usr/lib/X11/fonts/Speedo FontPath/usr/lib/X11/fonts/100dpi FontPath/usr/lib/X11/fonts/75dpi 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 pc104 Option XkbLayout us # Option XkbOptionsctrl:swapcaps EndSection Section InputDevice Identifier Configured Mouse Driver mouse Option CorePointer Option Device/dev/psaux Option Protocol ImPS/2 Option Emulate3Buttons true Option ZAxisMapping 4 5 EndSection Section InputDevice Identifier Generic Mouse Driver mouse Option
Re: Bug in xbase-clients_4.1.0-16woody3_ia64.deb
On Tue, Feb 24, 2004 at 02:29:21PM +0100, Wolfgang Dautermann wrote: Hi, during the latest apt-get update ; apt-get upgrade I got the following Messages, which I should report to that mail-adress: [...] Preparing to replace xfonts-scalable 4.1.0-16woody1 (using .../xfonts-scalable_4.1.0-16woody3_all.deb) ... Unpacking replacement xfonts-scalable ... (Reading database ... 66177 files and directories currently installed.) Preparing to replace xbase-clients 4.1.0-16woody1 (using .../xbase-clients_4.1.0-16woody3_ia64.deb) ... Warning: /etc/X11/xkb/compiled symbolic link points to the wrong place. Removing. ERROR: /etc/X11/xkb/xkbcomp exists and is not a symbolic link. This package cannot be installed until this file is removed. Aborting installation of xbase-clients package. dpkg: error processing /var/cache/apt/archives/xbase-clients_4.1.0-16woody3_ia64.deb (--unpack): subprocess pre-installation script returned error exit status 1 Analyzing /etc/X11/xkb/compiled: drwxr-xr-x 73 root root 4096 Feb 3 11:24 /etc drwxr-xr-x 19 root root 4096 Feb 24 13:45 /etc/X11 drwxr-xr-x 10 root root 4096 Feb 24 13:45 /etc/X11/xkb /etc/X11/xkb/compiled: nonexistent ERROR: /etc/X11/xkb/compiled symbolic link does not exist. Either the package didn't ship the symbolic link (a bug in the package), or dpkg failed to unpack it to the filesystem (a bug in dpkg). Please report the package name, version, and the text of the above error message(s) to debian-x@lists.debian.org. I believe, that will not cause many problems here, we use that machine usually remote and a local X-Server is not often used, but it seems, that there is an bug in an debian-Package (at least in the ia64-Version). If you need more information - just send me a mail). Thanks for the report. Does the package install successfully if you use the following command?: dpkg -i --force-confmiss xbase-clients_4.1.0-16woody3_all.deb -- G. Branden Robinson| When dogma enters the brain, all Debian GNU/Linux | intellectual activity ceases. [EMAIL PROTECTED] | -- Robert Anton Wilson http://people.debian.org/~branden/ | signature.asc Description: Digital signature
Processed: Re: Bug#234066: xserver-xfree86: XF86Config-4 file not being used correctly
Processing commands for [EMAIL PROTECTED]: retitle 234066 xserver-xfree86: [ati/radeon] driver ignores HorizSync and VertRefresh settings from XF86Config-4 file on secondary head of Radeon Mobility M6 LY rev 0 Bug#234066: xserver-xfree86: [ati/radeon] driver ignoring configured HorizSync and VertRefresh on Radeon RV100 QY [Radeon 7000/VE] rev 0 Changed Bug title. close 234066 Bug#234066: xserver-xfree86: [ati/radeon] driver ignores HorizSync and VertRefresh settings from XF86Config-4 file on secondary head of Radeon Mobility M6 LY rev 0 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Luke Schierer [EMAIL PROTECTED] tag 234066 - help Bug#234066: xserver-xfree86: [ati/radeon] driver ignores HorizSync and VertRefresh settings from XF86Config-4 file on secondary head of Radeon Mobility M6 LY rev 0 Tags were: help upstream Tags removed: help merge 234066 233924 Bug#233924: xserver-xfree86: [ati/radeon] driver ignores HorizSync and VertRefresh settings from XF86Config-4 file on secondary head of Radeon Mobility M6 LY rev 0 Bug#234066: xserver-xfree86: [ati/radeon] driver ignores HorizSync and VertRefresh settings from XF86Config-4 file on secondary head of Radeon Mobility M6 LY rev 0 Merged 233924 234066. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Processed: retitle 234025 to xserver-xfree86: [ati/radeon] display brightness too high when X server started with S-Video cable connected on Radeon RV200 QW [Radeon 7500] rev 0
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.7.95.1 retitle 234025 xserver-xfree86: [ati/radeon] display brightness too high when X server started with S-Video cable connected on Radeon RV200 QW [Radeon 7500] rev 0 Bug#234025: xserver-xfree86: [ati/radeon] display brightness excessively high (gamma problem?) on Radeon RV200 QW [Radeon 7500] rev 0 [regression from 4.2.1] Changed Bug title. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Bug#234556: xlibs random crashes with an ATI Rage Mobility
On Tue, 2004-02-24 at 18:05, Emmanuel Fleury wrote: If I stop the X server and try to restart, I can't. I get the exact same error than for the gnome-panel but for the X server (I guess, I have to investigate this a little bit more now that I better know what is going on). The X server itself can't encounter this error, probably the display manager does. My point is that it seems to be extremely consistant when it occurs. So, I think that there is some determinism inside this bug since it started. It doesn't seem even as deterministic as that for others... doesn't the problem go away for you if you 'do something else' for a while? The theory of the wrong code being remanent in the processor does not really satisfy me because we have no real evidence of it (how could we dump the registers of the processor or the cache memory ?). It's the only theory I've seen so far which could explain the semi-deterministic nature of the problem. I'll try to do some investigations and I'll probably come back with a summary of my though. I guess that I have to add this to the follow-up to the bug #216933 as it was the first. Yes, unfortunately the BTS doesn't seem to forward comments to both bugs even though I merged them. -- Earthling Michel Dänzer | Debian (powerpc), X and DRI developer Libre software enthusiast| http://svcs.affero.net/rm.php?r=daenzer
Bug#234532: xserver-xfree86: DRI doesn't work on Matrox G450 because of missing symbols
reassign 234532 xlibmesa-dri retitle 234532 xlibmesa-dri: DRI-based hardware 3D acceleration broken due to missing sse_test_dummy symbol merge 234532 229984 thanks On Tue, Feb 24, 2004 at 03:18:35PM +0200, [EMAIL PROTECTED] wrote: Package: xserver-xfree86 Version: 4.3.0-2 Severity: important [The following is a form letter.] Hello, You recently filed a duplicate bug report against a Debian package; that is, the problem had already been reported. While there is often nothing inherently wrong with doing so, the filing of duplicate reports can cause Debian package maintainers to spend time performing triage and maintenance operations on bug reports (e.g., instructing the Debian Bug Tracking System to merge the duplicates) that could otherwise be spent resolving problems and doing other work on the package. One very good way to file bugs with the Debian Bug Tracking System is to use the reportbug package and command of the same name. A very nice feature of reportbug is that, if the machine where you run it has network access to the World Wide Web, it can query the Debian Bug Tracking System and show you existing reports. This reduces the chance that you'll file a duplicate report, and offers you the option of adding follow-up information to an existing bug report. This is especially valuable if you have unique information to add to an existing report, because this way information relevant to the problem is gathered together in one place as opposed to being scattered among multiple, duplicate bug reports where some facts may be overlooked by the package maintainers. The reportbug program also does a lot of automatic information-gathering that helps package maintainers to understand your system configuration, and also ensures that your message to the Debian Bug Tracking System is well-formed so that it is processed correctly by the automated tools that manage the reports. (If you've ever gotten a bounce message from the Debian Bug Tracking System that tells you your message couldn't be processed, you might appreciate this latter feature.) Therefore, I strongly urge you to give reportbug a try as your primary bug reporting tool for the Debian System. One way to install reportbug is with apt-get; for example: # apt-get install reportbug The reportbug command has a few different modes that cater to different levels of user expertise. If this message has contained a lot of jargon that is unfamiliar to you, you likely want to use reportbug's novice mode; here's one way to do that. $ reportbug --mode=novice Please enter the name of the package in which you have found a problem, or type 'other' to report a more general problem. If you're more sophisticated, or if you are not using the released version of Debian (stable), but instead Debian testing or unstable, you should use reportbug's standard mode. $ reportbug Please enter the name of the package in which you have found a problem, or type 'other' to report a more general problem. The reportbug command is extensively documented in its usage message and manual page. Commands to view these pieces of documentation are: $ reportbug --help | more $ man reportbug (The output of the above commands has been omitted from this message.) Thanks for using the Debian system! -- G. Branden Robinson| Never attribute to conspiracy that Debian GNU/Linux | which can be adequately explained [EMAIL PROTECTED] | by economics. http://people.debian.org/~branden/ | signature.asc Description: Digital signature
Processed: Re: Bug#234532: xserver-xfree86: DRI doesn't work on Matrox G450 because of missing symbols
Processing commands for [EMAIL PROTECTED]: reassign 234532 xlibmesa-dri Bug#234532: xserver-xfree86: DRI doesn't work on Matrox G450 because of missing symbols Bug reassigned from package `xserver-xfree86' to `xlibmesa-dri'. retitle 234532 xlibmesa-dri: DRI-based hardware 3D acceleration broken due to missing sse_test_dummy symbol Bug#234532: xserver-xfree86: DRI doesn't work on Matrox G450 because of missing symbols Changed Bug title. merge 234532 229984 Bug#229984: xlibmesa-dri: DRI-based hardware 3D acceleration broken due to missing sse_test_dummy symbol Bug#234532: xlibmesa-dri: DRI-based hardware 3D acceleration broken due to missing sse_test_dummy symbol Bug#233582: xlibmesa-dri: DRI-based hardware 3D acceleration broken due to missing sse_test_dummy symbol Bug#233670: xlibmesa-dri: DRI-based hardware 3D acceleration broken due to missing sse_test_dummy symbol Bug#233743: xlibmesa-dri: DRI-based hardware 3D acceleration broken due to missing sse_test_dummy symbol Bug#233780: xlibmesa-dri: DRI-based hardware 3D acceleration broken due to missing sse_test_dummy symbol Bug#23: xlibmesa-dri: DRI-based hardware 3D acceleration broken due to missing sse_test_dummy symbol Merged 229984 233582 233670 233743 233780 23 234532. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Bug#234335: xserver-xfree86: Angle brackets (, ) were droped on spanish keyboard layout
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Dimarts 24 Febrer 2004 01:10, Branden Robinson wrote: tag 234335 + moreinfo thanks On Mon, Feb 23, 2004 at 10:02:46AM +0100, David García Garzón wrote: Package: xserver-xfree86 Version: 4.3.0-2 Severity: important There are some keys lost on the spanish (es) keyboard layout. While caracters like the n tilde, accents and ç (c,) are working properly, the angle brackets and are not working well in X. (Obviously i am typing that from a virtual console) Some backported xfree 4.3 unofficial packages, that i tested on a different host, had also that error and they get fixed but i don't remember where they came from. Can you please mail this bug your /etc/X11/XF86Config-4 and /var/log/XFree86.0.log files? Please ensure that your XkbModel in XF86Config-4 is pc105 and not pc104. You are right, that was the problem. The keyboard model was pc104. How this configuration file worked for the 4.2 version is a mistery for me. kxconfig is a useful tool for checking and solving on realtime this kind of errors but maybe some information should be droped for unexperienced users. Some other Spanish users at my workplace had the same problem when updating to 4.3. First with experimental packages and now in sid. - -- David (Vokimon) García Garzón (Work) dgarcia at iua dot upf anotherdot es (Home) vokimon at telefonica adot net http://www.salleurl.edu/~is04069 -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAO/cDAZlZIrnDW2ERAmYIAJ475dEcdXhIDfO++vbRUwwQP8cY+wCfTLpa NlTPabPlG5/DOMbXhAyRUeI= =ha40 -END PGP SIGNATURE-
Bug#116507: chicagoan ackerman micronesia guidance jigging urania bleary phosphorus tx yokuts protuberant abel nylon bullhead debugger cretaceous horseshoe hugging embroider
Cialis is known as a Super-Víagra or Weekend-Víagra because its effects start sooner and last much longer. Best Prlce on Internet Fast And Free Shlpplng http://drlaurent.com/sv/index.php?pid=eph2660 Visit Our Site Today
Bug#126519: butch amorphous comprehend mist onomatopoeic exclude blutwurst reprisal essex hireling smooch gimpy meetinghouse chomp quiver deborah aptitude alley giddap betel antiphonal gloom baltimore hobo fancy edwina dryden billie cosec chromic haitian besiege dress counterman
Cialis is known as a Super-Víagra or Weekend-Víagra because its effects start sooner and last much longer. Best Prlce on Internet Fast And Free Shlpplng http://drlaurent.com/sv/index.php?pid=eph2660 Visit Our Site Today
Bug#234066: xserver-xfree86: XF86Config-4 file not being used correctly
Um, i really really don't like this as you merged it into a closed bug, and my problem isn't fixed at all. that bug got fixed by changing to use clone lines, but would that apply to me, with my single monitor system? luke On Tue, Feb 24, 2004 at 06:30:55PM -0500, Branden Robinson wrote: retitle 234066 xserver-xfree86: [ati/radeon] driver ignores HorizSync and VertRefresh settings from XF86Config-4 file on secondary head of Radeon Mobility M6 LY rev 0 close 234066 tag 234066 - help merge 234066 233924 thanks This bug is a duplicate of #233924, and I am closing it. Please see URL: http://bugs.debian.org/233924 for the resolution of this problem. -- G. Branden Robinson| The noble soul has reverence for Debian GNU/Linux | itself. [EMAIL PROTECTED] | -- Friedrich Nietzsche http://people.debian.org/~branden/ | -- -This email is made of 100% recycled electrons.
