Bug#535516: Please add /usr/lib32/X11/locale to search path on i386
Package: libx11-6 Version: 2:1.2.1-1 Severity: wishlist File: /usr/lib/libX11.so.6.2.0 Hi, when running 32bit application on amd64 the 32bit locales can not be used. The reason for this is that libX11 only searches the following dirs: % strings /usr/lib32/libX11.so.6.2.0 | grep locale setlocale /usr/share/X11/locale /usr/lib/X11/locale It would be real nice if /usr/lib32/X11/locale could be included on i386 and /usr/lib64/X11/locale (for running 64bit binaries on i386). MfG Goswin -- System Information: Debian Release: squeeze/sid APT prefers transitional-i386 APT policy: (500, 'transitional-i386'), (500, 'unstable'), (400, 'unstable-i386'), (1, 'experimental-i386'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.29.4-frosties-1 Locale: LANG=C, LC_CTYPE=de_DE (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages libx11-6 depends on: ii libc6 2.9-18 GNU C Library: Shared libraries ii libx11-data 2:1.2.1-1 X11 client-side library ii libxcb1 1.3-2 X C Binding libx11-6 recommends no packages. libx11-6 suggests no packages. -- debconf information excluded -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#375541: Fails to upgarde with qvwm installed
Package: x11-common Version: 1:7.0.22 Severity: normal Hi, I just wanted to let you know that x11-common doesn't upgrade with qvwm installed. Unpacking x11-common (from .../x11-common_1%3a7.0.22_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/x11-common_1%3a7.0.22_amd64.deb (--unpack): trying to overwrite `/usr/X11R6/bin', which is also in package qvwm MfG Goswin -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-rc4-xen Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages x11-common depends on: ii debconf [debconf-2.0] 1.5.2 Debian configuration management sy ii debianutils 2.13.2 Miscellaneous utilities specific t ii lsb-base 3.1-10 Linux Standard Base 3.1 init scrip x11-common recommends no packages. -- debconf information excluded -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#366018: pre-installation script returned error exit status 10
Package: xserver-xorg Version: 1:7.0.15 Severity: grave Hi, installing xserver-xorg always fails in the DEBIAN/config script: Unpacking xserver-xorg (from .../xserver-xorg_1%3a7.0.15_all.deb) ... dpkg: error processing /var/cache/apt/archives/xserver-xorg_1%3a7.0.15_all.deb (--unpack): subprocess pre-installation script returned error exit status 10 Errors were encountered while processing: /var/cache/apt/archives/xserver-xorg_1%3a7.0.15_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) The reason for this is that set -e is set and a lot of db_get calls are missing a || true behind them and abort the script if the value is unset. Adding || true to all db_get, db_fget and db_getmeta calls makes the script work. MfG Goswin -- System Information: Debian Release: 3.1 Architecture: amd64 (x86_64) Kernel: Linux 2.6.16-rc4-xen Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#268461: xfree86: FBTFS: wrong Build-Depends libstdc++-5-dev
Package: xfree86 Version: 4.3.0.dfsg.1-4 Severity: serious Justification: no longer builds from source Hi, the gcc in sarge no longer builds libstdc++-5-dev but only libstdc++-5-3.3-dev. This causes the primary Build-Depends in xfree86 to fail and apt-get build-dep doesn't take the alternative. Please note that libstdc++5-3.3-dev is already build-essential: build-essental - g++ - g++-3.3 - libstdc++5-3.3-dev Removing the Build-Depends on libstdc++ completly sounds like the right thing to do. MfG Goswin -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.5-amd64 Locale: LANG=C, LC_CTYPE=de_DE
Bug#207537: xserver-xfree86: autodetection is not used
Package: xserver-xfree86 Version: 4.2.1-10 Severity: normal Hi, despite what you told me on irc before ignoring me none of the autodetection works. The reason for this becomes obvious when reading the config script. You only ever run the autodetection on an initial install. What you fail to see is that people upgrading or reconfiguring might still want to use this method. It would also be good to keep the previous selected values of any questions as default (thats rather a must) and to mark the probed values (or mention them in the text) for reference. Here is the log from a config run: == xserver-xfree86 config debug: Configuring xserver-xfree86. xserver-xfree86 config debug: X server symlink exists and points to executable X server; capping X server question priority at medium. xserver-xfree86 config debug: $OWNERS has only one value; shared/default-x-server will not be asked xserver-xfree86 config debug: not prompting for video card autodetection; reconfiguring xserver-xfree86 config debug: seen flag of shared/default-x-server is false xserver-xfree86 config debug: db_input medium shared/default-x-server xserver-xfree86 config debug: auto_answer() db_input medium shared/default-x-server with default xserver-xfree86 xserver-xfree86 config debug: auto_answer: (reconfiguring) preserving existing answer xserver-xfree86 xserver-xfree86 config debug: auto_answer: shared/default-x-server is not being asked xserver-xfree86 config debug: auto_answer: shared/default-x-server is xserver-xfree86 xserver-xfree86 config debug: /etc/X11/XF86Config-4 file exists; capping configuration question priority at medium. xserver-xfree86 config debug: user declined video card autodetection (driver) xserver-xfree86 config debug: auto_answer() db_input medium xserver-xfree86/config/device/driver with default vesa xserver-xfree86 config debug: auto_answer: (reconfiguring) preserving existing answer ati xserver-xfree86 config debug: auto_answer: asking xserver-xfree86/config/device/driver xserver-xfree86 config debug: auto_answer: xserver-xfree86/config/device/driver is ati xserver-xfree86 config debug: auto_answer() validate_string_db_input medium xserver-xfree86/config/device/identifier with default Generic Video Card xserver-xfree86 config debug: auto_answer: (reconfiguring) preserving existing answer Generic Video Card xserver-xfree86 config debug: auto_answer: asking xserver-xfree86/config/device/identifier xserver-xfree86 config debug: auto_answer: xserver-xfree86/config/device/identifier is Generic Video Card xserver-xfree86 config debug: auto_answer() validate_string_db_input medium xserver-xfree86/config/inputdevice/keyboard/rules with default xfree86 xserver-xfree86 config debug: auto_answer: (reconfiguring) preserving existing answer xfree86 xserver-xfree86 config debug: auto_answer: asking xserver-xfree86/config/inputdevice/keyboard/rules xserver-xfree86 config debug: auto_answer: xserver-xfree86/config/inputdevice/keyboard/rules is xfree86 xserver-xfree86 config debug: auto_answer() validate_string_db_input medium xserver-xfree86/config/inputdevice/keyboard/model with default pc104 xserver-xfree86 config debug: auto_answer: (reconfiguring) preserving existing answer pc105 xserver-xfree86 config debug: auto_answer: asking xserver-xfree86/config/inputdevice/keyboard/model xserver-xfree86 config debug: auto_answer: xserver-xfree86/config/inputdevice/keyboard/model is pc105 xserver-xfree86 config debug: auto_answer() validate_string_db_input medium xserver-xfree86/config/inputdevice/keyboard/layout with default us xserver-xfree86 config debug: auto_answer: (reconfiguring) preserving existing answer de xserver-xfree86 config debug: auto_answer: asking xserver-xfree86/config/inputdevice/keyboard/layout xserver-xfree86 config debug: auto_answer: xserver-xfree86/config/inputdevice/keyboard/layout is de xserver-xfree86 config debug: not prompting for mouse autodetection; reconfiguring xserver-xfree86 config debug: auto_answer() db_input medium xserver-xfree86/config/inputdevice/mouse/port with default /dev/misc/psaux xserver-xfree86 config debug: auto_answer: (reconfiguring) preserving existing answer /dev/misc/psaux xserver-xfree86 config debug: auto_answer: asking xserver-xfree86/config/inputdevice/mouse/port xserver-xfree86 config debug: auto_answer: xserver-xfree86/config/inputdevice/mouse/port is /dev/misc/psaux xserver-xfree86 config debug: auto_answer() db_input medium xserver-xfree86/config/inputdevice/mouse/protocol with default PS/2 xserver-xfree86 config debug: auto_answer: (reconfiguring) preserving existing answer ImPS/2 xserver-xfree86 config debug: auto_answer: asking xserver-xfree86/config/inputdevice/mouse/protocol xserver-xfree86 config debug: auto_answer: xserver-xfree86/config/inputdevice/mouse/protocol is ImPS/2 xserver-xfree86 config debug: xserver-xfree86/config/monitor/identifier is already
Bug#207537: xserver-xfree86: autodetection is not used
Package: xserver-xfree86 Version: 4.2.1-10 Severity: normal Hi, despite what you told me on irc before ignoring me none of the autodetection works. The reason for this becomes obvious when reading the config script. You only ever run the autodetection on an initial install. What you fail to see is that people upgrading or reconfiguring might still want to use this method. It would also be good to keep the previous selected values of any questions as default (thats rather a must) and to mark the probed values (or mention them in the text) for reference. Here is the log from a config run: == xserver-xfree86 config debug: Configuring xserver-xfree86. xserver-xfree86 config debug: X server symlink exists and points to executable X server; capping X server question priority at medium. xserver-xfree86 config debug: $OWNERS has only one value; shared/default-x-server will not be asked xserver-xfree86 config debug: not prompting for video card autodetection; reconfiguring xserver-xfree86 config debug: seen flag of shared/default-x-server is false xserver-xfree86 config debug: db_input medium shared/default-x-server xserver-xfree86 config debug: auto_answer() db_input medium shared/default-x-server with default xserver-xfree86 xserver-xfree86 config debug: auto_answer: (reconfiguring) preserving existing answer xserver-xfree86 xserver-xfree86 config debug: auto_answer: shared/default-x-server is not being asked xserver-xfree86 config debug: auto_answer: shared/default-x-server is xserver-xfree86 xserver-xfree86 config debug: /etc/X11/XF86Config-4 file exists; capping configuration question priority at medium. xserver-xfree86 config debug: user declined video card autodetection (driver) xserver-xfree86 config debug: auto_answer() db_input medium xserver-xfree86/config/device/driver with default vesa xserver-xfree86 config debug: auto_answer: (reconfiguring) preserving existing answer ati xserver-xfree86 config debug: auto_answer: asking xserver-xfree86/config/device/driver xserver-xfree86 config debug: auto_answer: xserver-xfree86/config/device/driver is ati xserver-xfree86 config debug: auto_answer() validate_string_db_input medium xserver-xfree86/config/device/identifier with default Generic Video Card xserver-xfree86 config debug: auto_answer: (reconfiguring) preserving existing answer Generic Video Card xserver-xfree86 config debug: auto_answer: asking xserver-xfree86/config/device/identifier xserver-xfree86 config debug: auto_answer: xserver-xfree86/config/device/identifier is Generic Video Card xserver-xfree86 config debug: auto_answer() validate_string_db_input medium xserver-xfree86/config/inputdevice/keyboard/rules with default xfree86 xserver-xfree86 config debug: auto_answer: (reconfiguring) preserving existing answer xfree86 xserver-xfree86 config debug: auto_answer: asking xserver-xfree86/config/inputdevice/keyboard/rules xserver-xfree86 config debug: auto_answer: xserver-xfree86/config/inputdevice/keyboard/rules is xfree86 xserver-xfree86 config debug: auto_answer() validate_string_db_input medium xserver-xfree86/config/inputdevice/keyboard/model with default pc104 xserver-xfree86 config debug: auto_answer: (reconfiguring) preserving existing answer pc105 xserver-xfree86 config debug: auto_answer: asking xserver-xfree86/config/inputdevice/keyboard/model xserver-xfree86 config debug: auto_answer: xserver-xfree86/config/inputdevice/keyboard/model is pc105 xserver-xfree86 config debug: auto_answer() validate_string_db_input medium xserver-xfree86/config/inputdevice/keyboard/layout with default us xserver-xfree86 config debug: auto_answer: (reconfiguring) preserving existing answer de xserver-xfree86 config debug: auto_answer: asking xserver-xfree86/config/inputdevice/keyboard/layout xserver-xfree86 config debug: auto_answer: xserver-xfree86/config/inputdevice/keyboard/layout is de xserver-xfree86 config debug: not prompting for mouse autodetection; reconfiguring xserver-xfree86 config debug: auto_answer() db_input medium xserver-xfree86/config/inputdevice/mouse/port with default /dev/misc/psaux xserver-xfree86 config debug: auto_answer: (reconfiguring) preserving existing answer /dev/misc/psaux xserver-xfree86 config debug: auto_answer: asking xserver-xfree86/config/inputdevice/mouse/port xserver-xfree86 config debug: auto_answer: xserver-xfree86/config/inputdevice/mouse/port is /dev/misc/psaux xserver-xfree86 config debug: auto_answer() db_input medium xserver-xfree86/config/inputdevice/mouse/protocol with default PS/2 xserver-xfree86 config debug: auto_answer: (reconfiguring) preserving existing answer ImPS/2 xserver-xfree86 config debug: auto_answer: asking xserver-xfree86/config/inputdevice/mouse/protocol xserver-xfree86 config debug: auto_answer: xserver-xfree86/config/inputdevice/mouse/protocol is ImPS/2 xserver-xfree86 config debug: xserver-xfree86/config/monitor/identifier is already
Re: Debconf and XFree86 X servers
Branden Robinson [EMAIL PROTECTED] writes: [Please direct any XFree86-specific followup to debian-x.] On Sat, Jul 05, 2003 at 08:46:00AM -0400, Theodore Ts'o wrote: Yet another reasons for wanting to decouple installation and configuration is if some hardware company (such as VA^H^H Emperor Linux) wishes to ship Debian pre-installed on the system. In that case, installation happens at the factory, and not when the user receives it in his/her hot little hands. So they should just provide a setup.sh script that calls dpkg-reconfigure for relevant packages again. Otherwise just type in dpkg-reconfigure --all and spend hours configuring your system as much as you like. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debconf and XFree86 X servers
Branden Robinson [EMAIL PROTECTED] writes: [Please direct any XFree86-specific followup to debian-x.] On Sat, Jul 05, 2003 at 08:46:00AM -0400, Theodore Ts'o wrote: Yet another reasons for wanting to decouple installation and configuration is if some hardware company (such as VA^H^H Emperor Linux) wishes to ship Debian pre-installed on the system. In that case, installation happens at the factory, and not when the user receives it in his/her hot little hands. So they should just provide a setup.sh script that calls dpkg-reconfigure for relevant packages again. Otherwise just type in dpkg-reconfigure --all and spend hours configuring your system as much as you like. MfG Goswin
Re: Bug#77130: dexter is not devfs ready
[EMAIL PROTECTED] (Branden Robinson) writes: On Mon, Nov 20, 2000 at 02:45:47PM +0100, Goswin Brederlow wrote: [EMAIL PROTECTED] (Branden Robinson) writes: On Mon, Nov 20, 2000 at 03:36:53AM +0100, Goswin Brederlow wrote: PS/2 is in /dev/misc/psaux. Serials are in /dev/tts/[0-9]*. Ah, you mean the exact paths I've been using since 4.0.1-2. Oh, so that should be fixed. Doesn't look right to me: % dpkg -l | grep xfree ii xfree86-common 4.0.1-2X Window System (XFree86) infrastructure ii xserver-xfree8 4.0.1-2the XFree86 X server % cat /proc/filesystems ... nodev devfs % mount ... none on /dev type devfs (rw) ... I check for a mounted devfs using a check given to me. How about reading the source of dexter and telling me what's wrong with it? The check looks right but doesn't work: # grep '\/dev\.*devfs' /proc/mounts # grep '/dev\.*devfs' /proc/mounts # grep '\/dev.*devfs' /proc/mounts # grep '/dev.*devfs' /proc/mounts none /dev devfs rw 0 0 # grep ' /dev .*devfs' /proc/mounts none /dev devfs rw 0 0 # grep '/dev.*devfs' /proc/mounts | hexdump %07.7_ 6f6e 656e 2f20 6564 2076 6564 6676 2073 %07.7_ 7772 3020 3020 000a %07.7_ You might want to check for instead of word start and end to circumvent the problem. MfG Goswin PS: You might also check for existing devices when using devfs. I don't have a /dev/tts/3, so theres no point giving me the choise. Altough care must be taken to handle not yet loaded modules. I might fill this as wishlist, since has nothing to do with this bug.
using old config for information [Was: Re: Bug#77130: dexter is not devfs ready]
"Zephaniah E. Hull" [EMAIL PROTECTED] writes: On Mon, Nov 20, 2000 at 03:36:53AM +0100, Goswin Brederlow wrote: snip Goswin PS: Using the old V3 config file for defaults and the console keymap would be a good wishlist thing as well. Ow ow ow ow ow. No, you /really/ don't want those 'features'. Whats wrong with using the same device for the mouse and the same keyboard as in the V3 config file as defaults? (Wheres the keyboard selection anyway in dexter?) Why not look at the console keymap to guess what keymap to use for X when no old config is found? I'm not talking about skipping the question in dexter. But dexter could position the cursor in the mouse selection on the mouse device that was used in the old confg file. May the Source be with you. Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#77130: dexter is not devfs ready
[EMAIL PROTECTED] (Branden Robinson) writes: On Mon, Nov 20, 2000 at 03:36:53AM +0100, Goswin Brederlow wrote: PS/2 is in /dev/misc/psaux. Serials are in /dev/tts/[0-9]*. Ah, you mean the exact paths I've been using since 4.0.1-2. Oh, so that should be fixed. Doesn't look right to me: % dpkg -l | grep xfree ii xfree86-common 4.0.1-2X Window System (XFree86) infrastructure ii xserver-xfree8 4.0.1-2the XFree86 X server % cat /proc/filesystems ... nodev devfs % mount ... none on /dev type devfs (rw) ... % dexter Dexter -- Debian X Server Configurator qq lqq Mouse Port Selection qqk x x x Please choose your mouse port. x x x x lqqk x x x /dev/psaux PS/2 port x x x x /dev/ttyS0 Serial port COM1x x x x /dev/ttyS1 Serial port COM2x x x x /dev/ttyS2 Serial port COM3x x x x /dev/ttyS3 Serial port COM4x x x x /dev/input/mice USB mouse x x x x /dev/atibm Bus / inport mouse x x x x /dev/gpmdata gpm repeaterx x x mqqj x tqqu x OK x mqqj On my system none of those even exist. MfG Goswin
using old config for information [Was: Re: Bug#77130: dexter is not devfs ready]
Zephaniah E. Hull [EMAIL PROTECTED] writes: On Mon, Nov 20, 2000 at 03:36:53AM +0100, Goswin Brederlow wrote: snip Goswin PS: Using the old V3 config file for defaults and the console keymap would be a good wishlist thing as well. Ow ow ow ow ow. No, you /really/ don't want those 'features'. Whats wrong with using the same device for the mouse and the same keyboard as in the V3 config file as defaults? (Wheres the keyboard selection anyway in dexter?) Why not look at the console keymap to guess what keymap to use for X when no old config is found? I'm not talking about skipping the question in dexter. But dexter could position the cursor in the mouse selection on the mouse device that was used in the old confg file. May the Source be with you. Goswin
Re: Bug#77131: xserver-xfree86 hangs itself
[EMAIL PROTECTED] (Branden Robinson) writes: On Mon, Nov 20, 2000 at 04:11:04AM +0100, Goswin Brederlow wrote: I tried the ati server again and without the faulty font entry that actually works. The font entry is not faulty. How about actually reading the bug reports I tell you to consult? Bad English, sorry. Anyway, the line is the reason it didn't start and crashed the console, even after killing it. MfG Goswin
Re: Bug#77130: dexter is not devfs ready
[EMAIL PROTECTED] (Branden Robinson) writes: On Wed, Nov 15, 2000 at 09:55:30PM +0100, Goswin Brederlow wrote: All suggestions for the mouse device use the old device names, devfs has them in subdirectories. Please use the new names when devfs is used. You're going to have to tell me what these are. I asked on IRC what I should use, and I used what I was told. Have a look at the documentation about the devfs in linux/Documentation/filesystems/devfs/ PS/2 is in /dev/misc/psaux. Serials are in /dev/tts/[0-9]*. Framebuffer in /dev/fb/[0-9]*. Also for framebuffer the framebuffer to be used should be choosable, i.e. which of /dev/fb/* to use. This is a wishlist item and I'll get to it when I can. I don't even know how to get X to use the second framebuffer, never had a second one. MfG Goswin PS: Using the old V3 config file for defaults and the console keymap would be a good wishlist thing as well.
