Bug#822835: closed by Jeremy Bicha <jbi...@linux.com> ()

[Wouter Verhelst]

Hi Jeremy,

On Sat, Jun 11, 2016 at 11:21:04PM +, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the xserver-xorg-input-synaptics package:
> 
> #822835: Driver doesn't seem to load anymore
> 
> It has been closed by Jeremy Bicha .
> 
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Jeremy Bicha 
>  by
> replying to this email.
> 
> 
> -- 
> 822835: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822835
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems

> Date: Sat, 11 Jun 2016 19:18:26 -0400
> From: Jeremy Bicha 
> To: 822835-d...@bugs.debian.org
> Subject: 
> X-Spam-Checker-Version: SpamAssassin 3.4.0-bugs.debian.org_2005_01_02
>  (2014-02-07) on buxtehude.debian.org
> X-Spam-Level: 
> X-Spam-Status: No, score=-2.1 required=4.0 tests=BAYES_00,
>  FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM,HEADER_FROM_DIFFERENT_DOMAINS,
>  NOSUBJECT,RCVD_IN_DNSWL_LOW,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_PASS,
>  TVD_SPACE_RATIO,VERSION autolearn=no autolearn_force=no
>  version=3.4.0-bugs.debian.org_2005_01_02
> Message-ID: 
> 

Bug#822835: Driver doesn't seem to load anymore

[Wouter Verhelst]

Package: xserver-xorg-input-synaptics
Version: 1.8.3-1+b1
Severity: normal

Hi,

Since a few days, when I try to run synclient to configure the touchpad
on my laptop, I get the following message:

wouter@gangtai:~$ synclient TapButton1=1 TapButton2=2 HorizTwoFingerScroll=1 
ClickPad=1 PalmDetect=true
Couldn't find synaptics properties. No synaptics driver loaded?

Not sure what changed. If you need any further input, please do ask.

-- Package-specific info:
X server symlink status:

lrwxrwxrwx. 1 root root 13 Mar 11  2015 /etc/X11/X -> /usr/bin/Xorg
-rwxr-xr-x. 1 root root 274 Apr  5 09:05 /usr/bin/Xorg

VGA-compatible devices on PCI bus:
--
00:02.0 VGA compatible controller [0300]: Intel Corporation 4th Gen Core 
Processor Integrated Graphics Controller [8086:0416] (rev 06)

/etc/X11/xorg.conf does not exist.

/etc/X11/xorg.conf.d does not exist.

KMS configuration files:

/etc/modprobe.d/radeon-kms.conf:
  options radeon modeset=1

Kernel version (/proc/version):
---
Linux version 4.5.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 5.3.1 
20160409 (Debian 5.3.1-14) ) #1 SMP Debian 4.5.1-1 (2016-04-14)

Xorg X server log files on system:
--
-rw-r--r--. 1 root root 24199 Apr 28 09:38 /var/log/Xorg.0.log

Contents of most recent Xorg X server log file (/var/log/Xorg.0.log):
-
[ 8.365] 
X.Org X Server 1.18.3
Release Date: 2016-04-04
[ 8.365] X Protocol Version 11, Revision 0
[ 8.365] Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian
[ 8.365] Current Operating System: Linux gangtai 4.5.0-1-amd64 #1 SMP 
Debian 4.5.1-1 (2016-04-14) x86_64
[ 8.366] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.5.0-1-amd64 
root=UUID=eb72ef37-ca28-45df-8d86-191350525cdc ro selinux=1 security=selinux 
quiet
[ 8.366] Build Date: 05 April 2016  07:00:43AM
[ 8.366] xorg-server 2:1.18.3-1 (http://www.debian.org/support) 
[ 8.366] Current version of pixman: 0.33.6
[ 8.366]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 8.366] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 8.366] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Apr 28 09:38:53 
2016
[ 8.374] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 8.379] (==) No Layout section.  Using the first Screen section.
[ 8.379] (==) No screen section available. Using defaults.
[ 8.379] (**) |-->Screen "Default Screen Section" (0)
[ 8.379] (**) |   |-->Monitor ""
[ 8.380] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 8.380] (==) Automatically adding devices
[ 8.380] (==) Automatically enabling devices
[ 8.380] (==) Automatically adding GPU devices
[ 8.380] (==) Max clients allowed: 256, resource mask: 0x1f
[ 8.385] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[ 8.385]Entry deleted from font path.
[ 8.385] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist.
[ 8.385]Entry deleted from font path.
[ 8.385] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
[ 8.385]Entry deleted from font path.
[ 8.385] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist.
[ 8.385]Entry deleted from font path.
[ 8.385] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist.
[ 8.385]Entry deleted from font path.
[ 8.386] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/Type1,
built-ins
[ 8.386] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 8.386] (II) The server relies on udev to provide the list of input 
devices.
If no devices become available, reconfigure udev or disable 
AutoAddDevices.
[ 8.386] (II) Loader magic: 0x5565a93c4dc0
[ 8.386] (II) Module ABI versions:
[ 8.386]X.Org ANSI C Emulation: 0.4
[ 8.386]X.Org Video Driver: 20.0
[ 8.386]X.Org XInput driver : 22.1
[ 8.386]X.Org Server Extension : 9.0
[ 8.387] (++) using VT number 7

[ 8.387] (II) systemd-logind: logind integration requires -keeptty and 
-keeptty was not provided, disabling logind integration
[ 8.388] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 8.390] (--) PCI:*(0:0:2:0) 8086:0416:10cf:17aa rev 6, Mem @ 
0xf000/4194304, 0xe000/268435456, I/O @ 0x3000/64
[ 8.390] (II) LoadModule: "glx"
[ 8.398] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 8.448] (II) Module glx: vendor="X.Org Foundation"
[ 8.448]compiled for 1.18.3, module version = 

Bug#784791: Haswell integrated graphics output confusion

[Wouter Verhelst]

Package: xserver-xorg-video-intel
Version: 2:2.21.15-2+b2
Severity: normal

Hi,

At home, I have 1920x1200 monitor which I connect to my laptop using a
port replicator and a DVI cable.

At work, I have a 1920x1080 monitor which I connect to my laptop using a
port replicator and a VGA cable.

If I restart the laptop or the X server between undocking at home and
re-docking at work, everything works fine. If I undock the laptop at
home, suspend it, and re-dock at work, then this is not the case, with
the X server confused as to what to do. I've seen various types of
confusion, including:

- The laptop screen and external monitor being set to the correct
  resolution, but the --left-of option being set on the laptop not being
  respected
- The laptop screen and external monitor being set to the same
  resolution
- The external monitor being set to an incorrect resolution (i.e.,
  something smaller than 1920x1080), but the rest of the 1920x1080
  screen size being included in the virtual desktop as a sort of gap
  between the external monitor and internal monitor (i.e., the internal
  screen would still be at the offset as expected for a FullHD
  resolution, but the external monitor would not be at a FullHD
  resolution).
- When accidentally calling the script for my home setup at work (even
  if no DVI connection is hooked up to the port replicator at work),
  similar confusion would occur.

If you need any further information, please ask.

-- Package-specific info:
X server symlink status:

lrwxrwxrwx 1 root root 13 Mar 11 17:53 /etc/X11/X - /usr/bin/Xorg
-rwxr-xr-x 1 root root 2401376 Feb 11 01:35 /usr/bin/Xorg

VGA-compatible devices on PCI bus:
--
00:02.0 VGA compatible controller [0300]: Intel Corporation 4th Gen Core 
Processor Integrated Graphics Controller [8086:0416] (rev 06)

/etc/X11/xorg.conf does not exist.

/etc/X11/xorg.conf.d does not exist.

KMS configuration files:

/etc/modprobe.d/radeon-kms.conf:
  options radeon modeset=1

Kernel version (/proc/version):
---
Linux version 3.16.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 
4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt9-3 (2015-04-23)

Xorg X server log files on system:
--
-rw-r--r-- 1 root root 35221 May  7 08:55 /var/log/Xorg.0.log

Contents of most recent Xorg X server log file (/var/log/Xorg.0.log):
-
[  1269.779] 
X.Org X Server 1.16.4
Release Date: 2014-12-20
[  1269.779] X Protocol Version 11, Revision 0
[  1269.779] Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian
[  1269.779] Current Operating System: Linux gangtai 3.16.0-4-amd64 #1 SMP 
Debian 3.16.7-ckt9-3 (2015-04-23) x86_64
[  1269.779] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-amd64 
root=UUID=eb72ef37-ca28-45df-8d86-191350525cdc ro quiet
[  1269.779] Build Date: 11 February 2015  12:32:02AM
[  1269.779] xorg-server 2:1.16.4-1 (http://www.debian.org/support) 
[  1269.779] Current version of pixman: 0.32.6
[  1269.779]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[  1269.779] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[  1269.779] (==) Log file: /var/log/Xorg.0.log, Time: Thu May  7 08:53:24 
2015
[  1269.779] (==) Using system config directory /usr/share/X11/xorg.conf.d
[  1269.779] (==) No Layout section.  Using the first Screen section.
[  1269.779] (==) No screen section available. Using defaults.
[  1269.779] (**) |--Screen Default Screen Section (0)
[  1269.779] (**) |   |--Monitor default monitor
[  1269.779] (==) No monitor specified for screen Default Screen Section.
Using a default monitor configuration.
[  1269.779] (==) Automatically adding devices
[  1269.779] (==) Automatically enabling devices
[  1269.779] (==) Automatically adding GPU devices
[  1269.779] (WW) The directory /usr/share/fonts/X11/cyrillic does not exist.
[  1269.779]Entry deleted from font path.
[  1269.779] (WW) The directory /usr/share/fonts/X11/100dpi/ does not exist.
[  1269.779]Entry deleted from font path.
[  1269.779] (WW) The directory /usr/share/fonts/X11/75dpi/ does not exist.
[  1269.779]Entry deleted from font path.
[  1269.779] (WW) The directory /usr/share/fonts/X11/100dpi does not exist.
[  1269.779]Entry deleted from font path.
[  1269.779] (WW) The directory /usr/share/fonts/X11/75dpi does not exist.
[  1269.779]Entry deleted from font path.
[  1269.779] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/Type1,
built-ins
[  1269.779] (==) ModulePath set to /usr/lib/xorg/modules
[  1269.779] (II) The server relies on udev to provide the list of input 

Bug#637448: xserver-xorg-video-intel: X server crashes after starting the same wine application twice

[Wouter Verhelst]

forwarded 637448 https://bugs.freedesktop.org/show_bug.cgi?id=41211
thanks

On Sun, Sep 25, 2011 at 12:11:16PM +0200, Julien Cristau wrote:
 tag 637448 moreinfo
 kthxbye
 
 On Thu, Aug 11, 2011 at 16:35:20 +0200, Wouter Verhelst wrote:
 
  Package: xserver-xorg-video-intel
  Version: 2:2.15.0-3
  Severity: important
  
  Hi,
  
  I've got this game that I run under wine. When I run it the first time,
  everything is fine. If I then quit the application and start it again
  without restarting the X server, it segfaults.
  
  If you need any further info, just let me know.
  
 Is this still an issue with X 1.11 and intel 2.16?

Yes.

 If yes please get a backtrace from gdb and report to bugs.freedesktop.org per
 http://intellinuxgraphics.org/how_to_report_bug.html.

Done.

-- 
The volume of a pizza of thickness a and radius z can be described by
the following formula:

pi zz a



-- 
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110926074949.ga4...@grep.be

Bug#637448: xserver-xorg-video-intel: X server crashes after starting the same wine application twice

[Wouter Verhelst]

Package: xserver-xorg-video-intel
Version: 2:2.15.0-3
Severity: important

Hi,

I've got this game that I run under wine. When I run it the first time,
everything is fine. If I then quit the application and start it again
without restarting the X server, it segfaults.

If you need any further info, just let me know.

-- Package-specific info:
X server symlink status:

lrwxrwxrwx 1 root root 13 Jun 23 17:15 /etc/X11/X - /usr/bin/Xorg
-rwxr-xr-x 1 root root 1957696 Aug  7 20:47 /usr/bin/Xorg

VGA-compatible devices on PCI bus:
--
00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core 
Processor Family Integrated Graphics Controller [8086:0126] (rev 09)

Xorg X server configuration file status:

-rw-r--r-- 1 root root 3204 Jun 23 18:03 /etc/X11/xorg.conf

Contents of /etc/X11/xorg.conf:
---
Section InputDevice
Identifier  Keyboard0
Driver  kbd
Option  XkbModel  pc105
Option  XkbLayout be
EndSection

Section InputDevice
Identifier  Mouse0
Driver  mouse
Option  Protocol auto
Option  Device /dev/input/mice
Option  ZAxisMapping 4 5 6 7
EndSection

Section Monitor
Identifier   Monitor0
VendorName   Monitor Vendor
ModelNameMonitor Model
EndSection

Section Monitor
Identifier   Monitor1
VendorName   Monitor Vendor
ModelNameMonitor Model
EndSection

Section Device
### Available Driver options are:-
### Values: i: integer, f: float, bool: True/False,
### string: String, freq: f Hz/kHz/MHz,
### percent: f%
### [arg]: arg optional
#Option AccelMethod   # [str]
#Option DRI   # [bool]
#Option ColorKey  # i
#Option VideoKey  # i
#Option FallbackDebug # [bool]
#Option Tiling# [bool]
#Option LinearFramebuffer # [bool]
#Option Shadow# [bool]
#Option SwapbuffersWait   # [bool]
#Option XvPreferOverlay   # [bool]
#Option DebugFlushBatches # [bool]
#Option DebugFlushCaches  # [bool]
#Option DebugWait # [bool]
#Option HotPlug   # [bool]
#Option RelaxedFencing# [bool]
Identifier  Card0
Driver  intel
BusID   PCI:0:2:0
EndSection

Section Device
### Available Driver options are:-
### Values: i: integer, f: float, bool: True/False,
### string: String, freq: f Hz/kHz/MHz,
### percent: f%
### [arg]: arg optional
#Option ShadowFB  # [bool]
#Option Rotate# str
#Option fbdev # str
#Option debug # [bool]
Identifier  Card1
Driver  fbdev
BusID   PCI:0:2:0
EndSection

Section Screen
Identifier Screen0
Device Card0
MonitorMonitor0
SubSection Display
Viewport   0 0
Depth 1
EndSubSection
SubSection Display
Viewport   0 0
Depth 4
EndSubSection
SubSection Display
Viewport   0 0
Depth 8
EndSubSection
SubSection Display
Viewport   0 0
Depth 15
EndSubSection
SubSection Display
Viewport   0 0
Depth 16
EndSubSection
SubSection Display
Viewport   0 0
Depth 24
EndSubSection
EndSection

Section Screen
Identifier Screen1
Device Card1
MonitorMonitor1
SubSection Display
Viewport   0 0
Depth 1
EndSubSection
SubSection Display
Viewport   0 0
Depth 4
EndSubSection
SubSection Display
Viewport   0 0
Depth 8
EndSubSection
SubSection Display
Viewport   0 0
Depth 15
EndSubSection
SubSection Display
Viewport   0 0
Depth 16
EndSubSection
SubSection Display
Viewport   0 0
Depth 24
EndSubSection
EndSection


/etc/X11/xorg.conf.d does not exist.

KMS configuration files:

/etc/modprobe.d/i915-kms.conf:
  options i915 modeset=1
/etc/modprobe.d/radeon-kms.conf:
  options radeon modeset=1

Kernel version (/proc/version):

Bug#544518: A way for --prop to not take half a second

[Wouter Verhelst]

Package: x11-xserver-utils
Version: 7.4+2
Severity: wishlist
File: /usr/bin/xrandr

Hi,

wou...@celtic:~$ time xrandr --prop
[...xrandr output snipped...]
real0m0.444s
user0m0.004s
sys 0m0.008s

I currently have a shell script that does the following:

  BL=$(xrandr --prop|awk '/BACKLIGHT:/{print $2}')

with the intention of then being able to use that to compute stuff and
set the new value, and hook that to the XF86MonBrightnessDown and ...Up
keys as a hotkey.

However, due to the fact that xrandr spends almost half a second waiting
on the X server for information that I don't need, and combined with the
fact that I don't see any way for me to change the set of data that
xrandr requests from the X server, this script is nearly unusable.

There could be alternate solutions to this wishlist item; e.g., it would
help if I would be able to tell xrandr that the X server has to increase
the value of a property relative to its current value with a value
relative to its valid range, or some such (say, a command similar to
'increase the value of the BACKLIGHT property on the LVDS output by 10%
of the total range).

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.30-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=nl_BE.UTF-8, LC_CTYPE=nl_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages x11-xserver-utils depends on:
ii  cpp   4:4.3.3-9  The GNU C preprocessor (cpp)
ii  libc6 2.9-25 GNU C Library: Shared libraries
ii  libice6   2:1.0.5-1  X11 Inter-Client Exchange library
ii  libsm62:1.1.1-1  X11 Session Management library
ii  libx11-6  2:1.2.2-1  X11 client-side library
ii  libxau6   1:1.0.4-2  X11 authorisation library
ii  libxaw7   2:1.0.6-1  X11 Athena Widget library
ii  libxext6  2:1.0.4-1  X11 miscellaneous extension librar
ii  libxi62:1.2.1-2  X11 Input extension library
ii  libxmu6   2:1.0.4-2  X11 miscellaneous utility library
ii  libxmuu1  2:1.0.4-2  X11 miscellaneous micro-utility li
ii  libxrandr22:1.3.0-2  X11 RandR extension library
ii  libxrender1   1:0.9.4-2  X Rendering Extension client libra
ii  libxt61:1.0.6-1  X11 toolkit intrinsics library
ii  libxtrap6 2:1.0.0-5  X11 event trapping extension libra
ii  libxxf86misc1 1:1.0.1-3  X11 XFree86 miscellaneous extensio
ii  libxxf86vm1   1:1.0.2-1  X11 XFree86 video mode extension l
ii  x11-common1:7.4+4X Window System (X.Org) infrastruc

x11-xserver-utils recommends no packages.

Versions of packages x11-xserver-utils suggests:
pn  cairo-5c  none (no description available)
pn  nicklenone (no description available)

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#529651: Should have means of generating xorg.conf file for those who dislike automatic stuff

[Wouter Verhelst]

Package: xserver-xorg
Version: 7.4
Severity: wishlist

Hi,

Subject says it all, really.

I'm sure the userfriendly police believes that getting rid of
configuration and letting the computer guess everything is the right
thing to do, but it is not.

Case in point: Xorg 7.4 autodetects my display card just fine, however
whenever I run

xrandr --output VGA --auto --above LVDS

it will tell me that the virtual size is not large enough. I know what
the problem is, and how to fix it: just edit /etc/X11/xorg.conf, find
where it says 

Section Display

and add a SubSection of the correct name where you say Virtual 3000 2000
or some such -- it just needs to be large enough, really.

However, with Xorg 7.4, there is no xorg.conf, so I have to either read
the manpages for whatever makes xorg decide where to fetch its
configuration at this point in time (not really an improvement to the
previous situation, really) or I have to write an xorg.conf _from
scratch_ without any help from the xserver-xorg package (*definitely*
not an improvement).

The file /usr/share/xserver-xorg/examples/xorg.conf is no help, since it
does not match my hardware, and therefore I have to guess what the right
driver is.

I tried running 'X -configure', but the file it generates is not what it
uses when I run X without xorg.conf (for starters, the keyboard layout
says 'us', while it *should* say 'be').

I've now been trying to come up with a working xorg.conf for the past
few hours, and haven't made much progress.

Please do not tell your power users to go fuck themselves because you
think that making life easier for users who're afraid of config files
(and therefore couldn't care less about whether configuration is in an
XML file, in /etc/X11/xorg.conf, or somplace else) is a good thing.

kthxbye.



-- 
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#443503: AOL

[Wouter Verhelst]

I'm seeing that behaviour too; /dev/input/mice presents two ButtonPress
events and two ButtonRelease events.

If it matters, I'm on powerpc.

-- 
Lo-lan-do Home is where you have to wash the dishes.
  -- #debian-devel, Freenode, 2004-09-22



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#366355: libx11: ssh -X between Sarges XF86 and Sids Xorg7 broken

[Wouter Verhelst]

On Mon, Feb 12, 2007 at 08:08:15AM +0100, Brice Goglin wrote:
 Hi Guys,
 
 About 8 months ago, you reported (a replied to a bug) in the Debian BTS
 regarding ssh -X problems between sarge and sid machines. I just want to
 know whether it still occurs with latest packages nowadays, especially
 Sarge-Etch. Thanks,

Seems to work here now.

-- 
Lo-lan-do Home is where you have to wash the dishes.
  -- #debian-devel, Freenode, 2004-09-22


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Scary message on new installations

[Wouter Verhelst]

On Sun, Jul 02, 2006 at 11:43:27PM -0700, Steve Langasek wrote:
 appropriate here than in other cases.  Is there some concern about
 apt-listchanges not listing NEWS files for newly-installed packages?

IME, it only lists NEWS.Debian files on upgrades...

-- 
Fun will now commence
  -- Seven Of Nine, Ashes to Ashes, stardate 53679.4


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#364489: xkbcomp looks for files in the wrong directory

[Wouter Verhelst]

Package: xbase-clients
Version: 1:7.0.0-4
Severity: normal

Hi,

(filing this on xbase-clients rather than xorg-xserver-core, since
according to strace, xkbcomp is the thing that actually looks at the
files)

Since the move to X11R7, I had issues with my laptop's keyboard (an
Apple PowerBook). Being lazy (and not in the vicinity of another system
to fix the laptop, should I fuck up the keyboard), I didn't check it out
until today.

My X keyboard definition looks like this:

Section InputDevice
Identifier  Generic Keyboard
Driver  keyboard
Option  CoreKeyboard
Option  XkbRules  xfree86
Option  XkbModel  macintosh
Option  XkbLayout wouter
EndSection

Which should mean that X would look for a keymap with the macintosh
geometry, and the wouter layout. Indeed, with previous versions of X,
and my keymap in /etc/X11/xkb/symbols/macintosh/wouter, this used to
work correctly; however, for it to work with current versions of X, it
only works if I put my modified keymap in
/usr/share/X11/xkb/symbols/wouter, rather than in
/usr/share/X11/xkb/symbols/macintosh_vndr/wouter, as I would expect.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: powerpc (ppc)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-1-powerpc
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)

Versions of packages xbase-clients depends on:
ii  libc6   2.3.6-7  GNU C Library: Shared libraries
ii  libfontconfig1  2.3.2-5.1generic font configuration library
ii  libfreetype62.1.10-3 FreeType 2 font engine, shared lib
ii  libfs6  2:1.0.0-3X11 Font Services library
ii  libgl1-mesa-glx [libgl1]6.4.1-0.4A free implementation of the OpenG
ii  libice6 1:1.0.0-3X11 Inter-Client Exchange library
ii  libpng12-0  1.2.8rel-5.1 PNG library - runtime
ii  libsm6  1:1.0.0-4X11 Session Management library
ii  libx11-62:1.0.0-6X11 client-side library
ii  libxau6 1:1.0.0-3X11 authorisation library
ii  libxaw7 1:1.0.1-5X11 Athena Widget library
ii  libxcursor1 1.1.5.2-5X cursor management library
ii  libxext61:1.0.0-4X11 miscellaneous extension librar
ii  libxft2 2.1.8.2-6FreeType-based font drawing librar
ii  libxi6  1:1.0.0-5X11 Input extension library
ii  libxkbfile1 1:1.0.2-3X11 keyboard file manipulation lib
ii  libxmu6 1:1.0.1-3X11 miscellaneous utility library
ii  libxmuu11:1.0.1-3X11 miscellaneous micro-utility li
ii  libxrandr2  2:1.1.0.2-4  X11 RandR extension library
ii  libxrender1 1:0.9.0.2-4  X Rendering Extension client libra
ii  libxss1 1:1.0.1-4X11 Screen Saver extension library
ii  libxt6  1:1.0.0-4X11 toolkit intrinsics library
ii  libxtrap6   1:1.0.0-3X11 event trapping extension libra
ii  libxtst61:1.0.1-3X11 Testing -- Resource extension 
ii  libxv1  1:1.0.1-3X11 Video extension library
ii  libxxf86dga12:1.0.0-3X11 Direct Graphics Access extensi
ii  libxxf86vm1 1:1.0.0-4X11 XFree86 video mode extension l
ii  x11-common  1:7.0.10 X Window System (X.Org) infrastruc
ii  zlib1g  1:1.2.3-11   compression library - runtime

xbase-clients recommends no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#364489: xkbcomp looks for files in the wrong directory

[Wouter Verhelst]

reopen 364489
thanks

On Sun, Apr 23, 2006 at 08:55:59PM +0100, Daniel Stone wrote:
 On Sun, Apr 23, 2006 at 08:21:41PM +0200, Wouter Verhelst wrote:
  Which should mean that X would look for a keymap with the macintosh
  geometry,
 
 You're confusing model and geometry.

If I am, that's only because XKB uses confusing terminology.

There's XkbLayout in xorg.conf, which maps to a directory called
symbols, XkbModel which maps to keymap, and so on. It'd probably
be better if those terms would be unified.

  and the wouter layout. Indeed, with previous versions of X,
  and my keymap in /etc/X11/xkb/symbols/macintosh/wouter, this used to
  work correctly; however, for it to work with current versions of X, it
  only works if I put my modified keymap in
  /usr/share/X11/xkb/symbols/wouter, rather than in
  /usr/share/X11/xkb/symbols/macintosh_vndr/wouter, as I would expect.
 
 Correct.  The pc/, macintosh/, *_vndr/ directories under symbols are
 deprecated.  The fix is to write keyboard layouts that are portable
 across models, for the general case.

That's simply impossible. An apple ADB keyboard as it appears on their
laptops lacks a whole bunch of keys that a regular PC keyboard does
have; the keys RALT, and INS are not available on my laptop, and some of
the other keys (e.g., DELE) are only available through awkward key
combinations involving Fn.

My own keyboard mapping therefore does some things that would be very
strange indeed on 'regular' keyboard (one with the normal lay-out) but
that are good (and wanted) on an apple keyboard.

Moreover, Apple has a different idea about what a Belgian keyboard is
than most PC keyboards do. If I use a Belgian PC keyboard layout on my
macintosh laptop, I don't get the characters that are printed on the
keys.

This way lies madness.

 Closing as invalid, since this is a user configuration issue.

Then at the very minimum this should be documented. Rather than having a
non-working macintosh_vndr directory, it should either work, or be
documented that it needs to be enabled somehow (by an option in
xorg.conf, I guess?), or be removed.

A directory on disk with keymaps that cannot ever possibly be used is a
bug in my book.

-- 
Fun will now commence
  -- Seven Of Nine, Ashes to Ashes, stardate 53679.4


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#296876: xvfb-run: does not properly look for xauth

[Wouter Verhelst]

Package: xvfb
Version: 4.3.0.dfsg.1-10
Severity: normal

I have a cron job that needs an X server to be present, so wanted to use
xvfb-run to make this work. However, there's an issue; my cron output
looks like this:

xvfb-run: error: xauth command not found

even though xbase-clients is installed. This seems to be because
xvfb-run looks for xauth using 'which', while xauth is installed in
/usr/bin/X11/xauth; using which will thus work if that directory is in
$PATH, but that is not usually the case when something is being called
from cron.

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.8.1
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=UTF-8)

Versions of packages xvfb depends on:
ii  libc6   2.3.2.ds1-20 GNU C Library: Shared libraries an
ii  libfreetype62.1.7-2.3FreeType 2 font engine, shared lib
ii  zlib1g  1:1.2.2-3compression library - runtime

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#274607: xserver-xfree86: problems with XKB settings on a Sun type5/type6 keyboard

[Wouter Verhelst]

On Thu, Oct 07, 2004 at 09:45:35PM +0200, Denis Barbier wrote:
 I just committed a fix, but would like to check something.
 Could you please run
   $ xkbcomp :0
 and send me the two server-0.xkb files generated by this command, with
 and without loading srvr_ctrl?

http://users.pandora.be/wouter.verhelst/server-0.xkb-us and ...-us+srvr_ctrl

-- 
 EARTH
 smog  |   bricks
 AIR  --  mud  -- FIRE
soda water |   tequila
 WATER
 -- with thanks to fortune


signature.asc
Description: Digital signature

Bug#274607: xserver-xfree86: problems with XKB settings on a Sun type5/type6 keyboard

[Wouter Verhelst]

On Sun, Oct 03, 2004 at 09:13:20AM +0200, Denis Barbier wrote:
 On Sun, Oct 03, 2004 at 02:33:28AM +0200, Wouter Verhelst wrote:
  Package: xserver-xfree86
  Version: 4.3.0.dfsg.1-4
  Severity: normal
  
  Hi,
  
  As discussed on IRC today:
  
  There seems to be a problem with the XKB map on a Sun Type5 (or Type6,
  which is hardware-compatible) keyboard. Everything is mapped correctly
  for 'normal' work, but special key sequences (I currently tested
  ctrl-alt-bksp (to kill the server) and ctrl-alt-function key (to
  switch to a different virtual console)) don't work by default.
  
  This can be worked around by using 'us+srvr_ctrl' as a keymap instead of
  plainly 'us'.
 
 There is no problem with F1-F12 function keys, but for the keypad
 Ctrl+Alt+KP_Divide and Ctrl+Alt+KP_Multiply are assigned to
 F25 and F26 respectively, whereas loading srvr_ctrl redefines
 them to XF86_Ungrab and XF86_ClearGrab.
 Can we assume that those definitions were seldom used and override
 them with standard XFree86 ones?

There is no function key above F12 on my keyboard. This could be just
me, dunno; perhaps I have to use one of the bucky bit keys to reach F25.
But if not, then it's probably indeed better to put them on the standard
XFree86 ones.

-- 
 EARTH
 smog  |   bricks
 AIR  --  mud  -- FIRE
soda water |   tequila
 WATER
 -- with thanks to fortune


signature.asc
Description: Digital signature

Bug#274607: xserver-xfree86: problems with XKB settings on a Sun type5/type6 keyboard

[Wouter Verhelst]

Package: xserver-xfree86
Version: 4.3.0.dfsg.1-4
Severity: normal

Hi,

As discussed on IRC today:

There seems to be a problem with the XKB map on a Sun Type5 (or Type6,
which is hardware-compatible) keyboard. Everything is mapped correctly
for 'normal' work, but special key sequences (I currently tested
ctrl-alt-bksp (to kill the server) and ctrl-alt-function key (to
switch to a different virtual console)) don't work by default.

This can be worked around by using 'us+srvr_ctrl' as a keymap instead of
plainly 'us'.

-- Package-specific info:
Contents of /var/lib/xfree86/X.roster:
xserver-xfree86

/etc/X11/X target unchanged from checksum in /var/lib/xfree86/X.md5sum.

X server symlink status:
lrwxr-xr-x  1 root root 20 2004-09-21 00:53 /etc/X11/X - /usr/bin/X11/XFree86
-rwxr-xr-x  1 root root 1782824 2004-05-29 21:04 /usr/bin/X11/XFree86

Contents of /var/lib/xfree86/XF86Config-4.roster:
xserver-xfree86

VGA-compatible devices on PCI bus:
:01:02.0 VGA compatible controller: ATI Technologies Inc 3D Rage Pro 215GP 
(rev 5c)

/etc/X11/XF86Config-4 does not match checksum in 
/var/lib/xfree86/XF86Config-4.md5sum.

XFree86 X server configuration file status:
-rw-r--r--  1 root root 2879 2004-10-03 02:21 /etc/X11/XF86Config-4

Contents of /etc/X11/XF86Config-4:
# XF86Config-4 (XFree86 X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the XF86Config-4 manual page.
# (Type man XF86Config-4 at the shell prompt.)
#
# This file is automatically updated on xserver-xfree86 package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xfree86
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following commands as root:
#
#   cp /etc/X11/XF86Config-4 /etc/X11/XF86Config-4.custom
#   md5sum /etc/X11/XF86Config-4  /var/lib/xfree86/XF86Config-4.md5sum
#   dpkg-reconfigure xserver-xfree86
Section Files
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/usr/lib/X11/fonts/Type1
FontPath/usr/lib/X11/fonts/CID
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  sun
Option  XkbModel  type5
Option  XkbLayout us+srvr_ctrl
EndSection
Section InputDevice
Identifier  Configured Mouse
Driver  mouse
Option  CorePointer
Option  Device/dev/sunmouse
Option  Protocol  BusMouse
EndSection

Section InputDevice
Identifier  Generic Mouse
Driver  mouse
Option  SendCoreEventstrue
Option  Device/dev/input/mice
Option  Protocol  ImPS/2
EndSection
Section Device
Identifier  Generic Video Card
Driver  sunffb
EndSection
Section Monitor
Identifier  Generic Monitor
#HorizSync  28-50
#VertRefresh43-75
Option  DPMS
Mode 1024x768
# D: 100.000 MHz, H: 97.656 kHz, V: 127.157 Hz
DotClock 100.001
HTimings 1024 1024 1024 1024
VTimings 768 768 768 768
Flags-HSync -VSync# Warning: XFree86 doesn't 
support accel
EndMode
EndSection
Section Screen
Identifier  Default Screen
Device  Generic Video Card
Monitor Generic Monitor
DefaultDepth24
SubSection Display
Depth   24
Modes   1024x768
EndSubSection
EndSection
Section ServerLayout
Identifier  Default Layout
Screen  Default Screen
InputDevice Generic Keyboard
InputDevice Configured Mouse
InputDevice Generic Mouse
EndSection
Section DRI
Mode0666
EndSection


XFree86 X server log files on system:
-rw-r--r--  1 root root 23382 

Re: mouse for x

[Wouter Verhelst]

On Sun, Aug 22, 2004 at 12:02:16AM -0500, Branden Robinson wrote:
 On Sat, Aug 21, 2004 at 07:22:31AM +0200, Erik C.J. Laan wrote:
  Tony Pitman wrote:
  Joel,
  
  That worked. I wonder why the ADB mouse is not part of the config. Maybe 
  someone can fix that.
  
  That is probaby because there is only 1 set of X packages for the m68k 
  architecture because only a few files need sub-architecture specific. 
  /dev/adbmouse is definetely Mac specific, because the ADB bus is. But 
  Brandon Robinson is the one to know if different default config's per 
  subarchitecture can be used, as he makes the X packages.
 
 Sure; someone just needs to tell me what to grep for in /proc/cpuinfo for
 the various sub-architectures.

Better use /proc/hardware

[EMAIL PROTECTED]:~$ cat /proc/hardware
Model:  Motorola MVME167
[...]

[EMAIL PROTECTED]:~$ cat /proc/hardware
Model:  Macintosh Quadra 840AV
[...]

and so on. /proc/hardware is an m68k-specific file which contains
information about the hardware you're running on. It needs to be enabled
in the kernel (CONFIG_PROC_HARDWARE), but all Debian-provided kernels
have that (at least all Debian-provided kernels I've seen).

What you need to grep for is Macintosh for mac hardware, Amiga for
amiga, or Atari for atari. VME doesn't support X AFAIK, and Debian
doesn't support any of the other m68k subarchitectures.

-- 
 EARTH
 smog  |   bricks
 AIR  --  mud  -- FIRE
soda water |   tequila
 WATER
 -- with thanks to fortune


signature.asc
Description: Digital signature

Re: mouse for x

[Wouter Verhelst]

On Sun, Aug 22, 2004 at 02:46:31PM +0200, Christian T. Steigies wrote:
 On Sun, Aug 22, 2004 at 02:26:46PM +0200, Wouter Verhelst wrote:
  What you need to grep for is Macintosh for mac hardware, Amiga for
  amiga, or Atari for atari. VME doesn't support X AFAIK, and Debian
  doesn't support any of the other m68k subarchitectures.
 
 We have Q40 kernels since 2.4.26 IIRC,

Oh, we do?

 they should run on Q40 and Q60. Roman Zippel should be able to say how
 /proc/hardware looks like for those machines.

Reading the kernel source, I think that'll always be Q40, even on Q60.

-- 
 EARTH
 smog  |   bricks
 AIR  --  mud  -- FIRE
soda water |   tequila
 WATER
 -- with thanks to fortune

Re: Future of X packages in Debian

[Wouter Verhelst]

On Fri, Jun 18, 2004 at 04:31:58PM -0700, Matt Zimmerman wrote:
 On Fri, Jun 18, 2004 at 09:49:44PM +0200, Wouter Verhelst wrote:
  On Fri, Jun 18, 2004 at 09:02:50AM +0200, Fabio Massimo Di Nitto wrote:
   Our questions to the community are:
   
   * What kinds of X packages would you like to see in the future?
  
  Working ones. With as few (upstream and debian-specific) bugs as
  possible.
  
  Case at hand: I have yet to see the first XFree86 (server|module) and
  graphics board combination that
  * supports the full potential of the board
  * does not reproducably receive SIGSEGV
  * is free
  
  This is, of course, not the fault of the Debian X strike force, but it's
  painful none the less.
 
 I don't think that Fabio's message was an invitation to complain about X,
 but a request for input on maintaining Debian's X packages in the future.

I know, and I gave input. The above was an example to explain my point,
not a complaint (if I thought I had to complain, I'd have done so a long
time ago).

The point was that I think if there's two competing X implementations,
the X strike force should choose the one with the highest quality, not
the one with the most features.

-- 
 EARTH
 smog  |   bricks
 AIR  --  mud  -- FIRE
soda water |   tequila
 WATER
 -- with thanks to fortune


signature.asc
Description: Digital signature

Re: Future of X packages in Debian

[Wouter Verhelst]

On Fri, Jun 18, 2004 at 09:02:50AM +0200, Fabio Massimo Di Nitto wrote:
 Our questions to the community are:
 
 * What kinds of X packages would you like to see in the future?

Working ones. With as few (upstream and debian-specific) bugs as
possible.

Case at hand: I have yet to see the first XFree86 (server|module) and
graphics board combination that
* supports the full potential of the board
* does not reproducably receive SIGSEGV
* is free

This is, of course, not the fault of the Debian X strike force, but it's
painful none the less.

 * Should we regard X.Org or FreeDesktop.Org as our upstream source?

Whichever of the two helps further the above goal.

 * Should we go our own way starting from the sanitized XFree86 CVS
   snapshot we've prepared?

If you think you can do a better job than both of the two upstreams, I'd
say go for it; but I think that's a huge job.

 * Should we ensure that multiple implementations of the X Window System
   are packaged, or standardize on just one?

It would be great if we would have the man power to support two
(or more) competing X Window System implementations, but wouldn't it be
more prudent to start off with one and add more if people seem to be
doing nothing?

 * If we standardize on just one, which one should it be?

The one that will, in your opinion, serve our users best.

I'm deliberately not choosing sides here, even though I know you're
asking for people to choose sides. IMO, however, you (the X Strike
Force) are best qualified to choose which way to go from now. I
therefore suggest you consider the above guidelines (and add some of
your own), and make the decision for yourself.

After all, _you_ will be the one people will yell at when you chose the
X Window System with the most features (because people like features)
but with the most bugs, too.

-- 
 EARTH
 smog  |   bricks
 AIR  --  mud  -- FIRE
soda water |   tequila
 WATER
 -- with thanks to fortune


signature.asc
Description: Digital signature

Bug#236132: libx11-6 postrm bug prevents removal of package

[Wouter Verhelst]

Op do 04-03-2004, om 14:57 schreef Michael Schmitz:
 I'll shut my autobuilder down for the time being, until after 4.3.0-3 has
 been installed.

That's not necessary. If you preinstall the b0rken packages (using
apt-get --reinstall install foo bar baz should do it), you can
continue to build. I've done that on quickstep, seems to work.

(alternatively, you could just dep-wait everything on xserver-xfree86
( 4.3.0-2) ...)

-- 
Wouter Verhelst
Debian GNU/Linux -- http://www.debian.org
Nederlandstalige Linux-documentatie -- http://nl.linux.org
Most people have two reasons for doing anything -- a good reason, and
the real reason

Re: XFree86's HasLinuxInput symbol and m68k

[Wouter Verhelst]

On Thu, Jun 12, 2003 at 08:01:24AM +0200, Christoph Hellwig wrote:
 On Wed, Jun 11, 2003 at 10:55:24AM -0400, Christian T. Steigies wrote:
  No USB on m68k as far as I know (I can hear already the shouts but there
  is this cool USB Adapter for Amiga), so this should never be executed on
  m68k. Maybe not even compiled (I did not read the code too thoroughly).
 
 Can't you just plug an pci usb card into a hades?

Sure, although that's more of an exception than a rule.

Not sure whether the uhci- or ohci-drivers would work on m68k, though.

-- 
Wouter Verhelst
Debian GNU/Linux -- http://www.debian.org
Nederlandstalige Linux-documentatie -- http://nl.linux.org
An expert can usually spot the difference between a fake charge and a
full one, but there are plenty of dead experts. 
  -- National Geographic Channel, in a documentary about large African beasts.


pgp0.pgp
Description: PGP signature

Bug#197180: [s3virge] xine makes my X server segfault

[Wouter Verhelst]

Package: xserver-xfree86
Version: 4.2.1-8
Severity: normal

Hi

If I ever try to fire up xine, my X server will segfault in
seconds. It happens most of all when I try to use xine at full screen,
but that is not required to make the server go down.

I ran xine in the X server from the package 'xserver-xfree86-dbg',
twice. This produced the following two backtraces:

(gdb) where
#0  0x40073a41 in kill () from /lib/libc.so.6
#1  0x40073862 in raise () from /lib/libc.so.6
#2  0x40074976 in abort () from /lib/libc.so.6
#3  0x0824b5f9 in ddxGiveUp () at xf86Init.c:1094
#4  0x082b2520 in AbortServer () at utils.c:436
#5  0x082b37a5 in FatalError (f=0x85a1640 Caught signal %d.  Server
aborting\n) at utils.c:1399
#6  0x0825c9e6 in xf86SigHandler (signo=11) at xf86Events.c:1085
#7  signal handler called
#8  0x081c5032 in XAAPaintWindow (pWin=0x8a16790, prgn=0xb850,
what=0) at xaaPaintWin.c:109
#9  0x08372eb8 in miSpritePaintWindowBackground (pWin=0x8a16790,
pRegion=0xb850, what=0) at misprite.c:844
#10 0x08358a97 in miClearToBackground (pWin=0x8a16790, x=0, y=0, w=0,
h=0, generateExposures=0) at miwindow.c:131
#11 0x08373153 in miSpriteClearToBackground (pWin=0x8a16790, x=0, y=0,
w=0, h=0, generateExposures=0) at misprite.c:947
#12 0x0828f3b4 in ProcClearToBackground (client=0x88a4a58) at
dispatch.c:1722
#13 0x0828d549 in Dispatch () at dispatch.c:462
#14 0x0829d468 in main (argc=1, argv=0xbda4, envp=0xbdac) at
main.c:488

and the second:

(gdb) where
#0  0x40073a41 in kill () from /lib/libc.so.6
#1  0x40073862 in raise () from /lib/libc.so.6
#2  0x40074976 in abort () from /lib/libc.so.6
#3  0x0824b5f9 in ddxGiveUp () at xf86Init.c:1094
#4  0x082b2520 in AbortServer () at utils.c:436
#5  0x082b37a5 in FatalError (f=0x85a1640 Caught signal %d.  Server
aborting\n) at utils.c:1399
#6  0x0825c9e6 in xf86SigHandler (signo=11) at xf86Events.c:1085
#7  signal handler called
#8  0x081b4841 in XAADestroyPixmap (pPix=0x8afac08) at xaaInit.c:585
#9  0x08390818 in XvDestroyPixmap (pPix=0x8afac08) at xvmain.c:392
#10 0x08377eba in ShmDestroyPixmap (pPixmap=0x8afac08) at shm.c:317
#11 0x082a4cd1 in ChangeWindowAttributes (pWin=0x89ad0a0, vmask=1,
vlist=0x89474dc, client=0x8a8bd48) at window.c:1085
#12 0x0828d80b in ProcChangeWindowAttributes (client=0x8a8bd48) at
dispatch.c:561
#13 0x0828d549 in Dispatch () at dispatch.c:462
#14 0x0829d468 in main (argc=1, argv=0xba64, envp=0xba6c) at
main.c:488

The log which is part of this bugreport is the one that was produced
as a result of the second attempt. I have no log from the first one
anymore.

-- Package-specific info:
01:00.0 VGA compatible controller: S3 Inc. 86c368 [Trio 3D/2X] (rev 02)
01:00.0 Class 0300: 5333:8a13 (rev 02)

### 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/Type1
FontPath/usr/lib/X11/fonts/CID
FontPath/usr/lib/X11/fonts/Speedo
FontPath/usr/lib/X11/fonts/misc
FontPath/usr/lib/X11/fonts/cyrillic
FontPath/usr/lib/X11/fonts/100dpi
FontPath/usr/lib/X11/fonts/75dpi
EndSection

Section Module
LoadGLcore
Loadbitmap
Loaddbe
Loadddc
Loaddri
Loadextmod
Loadfreetype
Loadglx
Loadint10
Loadrecord
Loadspeedo
Loadtype1
Loadvbe
EndSection

Section InputDevice
Identifier  Generic Keyboard
Driver  keyboard
Option  CoreKeyboard
Option  XkbRules  xfree86
Option  XkbModel  pc105
Option  XkbLayout be
EndSection

Section InputDevice
Identifier  Configured Mouse
Driver  mouse
Option  CorePointer
Option  Device/dev/psaux
Option  Protocol  ImPS/2
Option  ZAxisMapping  4 5
EndSection

Section InputDevice
Identifier  Generic Mouse
Driver  mouse
Option  SendCoreEvents

Bug#197180: [s3virge] xine makes my X server segfault

[Wouter Verhelst]

Package: xserver-xfree86
Version: 4.2.1-8
Severity: normal

Hi

If I ever try to fire up xine, my X server will segfault in
seconds. It happens most of all when I try to use xine at full screen,
but that is not required to make the server go down.

I ran xine in the X server from the package 'xserver-xfree86-dbg',
twice. This produced the following two backtraces:

(gdb) where
#0  0x40073a41 in kill () from /lib/libc.so.6
#1  0x40073862 in raise () from /lib/libc.so.6
#2  0x40074976 in abort () from /lib/libc.so.6
#3  0x0824b5f9 in ddxGiveUp () at xf86Init.c:1094
#4  0x082b2520 in AbortServer () at utils.c:436
#5  0x082b37a5 in FatalError (f=0x85a1640 Caught signal %d.  Server
aborting\n) at utils.c:1399
#6  0x0825c9e6 in xf86SigHandler (signo=11) at xf86Events.c:1085
#7  signal handler called
#8  0x081c5032 in XAAPaintWindow (pWin=0x8a16790, prgn=0xb850,
what=0) at xaaPaintWin.c:109
#9  0x08372eb8 in miSpritePaintWindowBackground (pWin=0x8a16790,
pRegion=0xb850, what=0) at misprite.c:844
#10 0x08358a97 in miClearToBackground (pWin=0x8a16790, x=0, y=0, w=0,
h=0, generateExposures=0) at miwindow.c:131
#11 0x08373153 in miSpriteClearToBackground (pWin=0x8a16790, x=0, y=0,
w=0, h=0, generateExposures=0) at misprite.c:947
#12 0x0828f3b4 in ProcClearToBackground (client=0x88a4a58) at
dispatch.c:1722
#13 0x0828d549 in Dispatch () at dispatch.c:462
#14 0x0829d468 in main (argc=1, argv=0xbda4, envp=0xbdac) at
main.c:488

and the second:

(gdb) where
#0  0x40073a41 in kill () from /lib/libc.so.6
#1  0x40073862 in raise () from /lib/libc.so.6
#2  0x40074976 in abort () from /lib/libc.so.6
#3  0x0824b5f9 in ddxGiveUp () at xf86Init.c:1094
#4  0x082b2520 in AbortServer () at utils.c:436
#5  0x082b37a5 in FatalError (f=0x85a1640 Caught signal %d.  Server
aborting\n) at utils.c:1399
#6  0x0825c9e6 in xf86SigHandler (signo=11) at xf86Events.c:1085
#7  signal handler called
#8  0x081b4841 in XAADestroyPixmap (pPix=0x8afac08) at xaaInit.c:585
#9  0x08390818 in XvDestroyPixmap (pPix=0x8afac08) at xvmain.c:392
#10 0x08377eba in ShmDestroyPixmap (pPixmap=0x8afac08) at shm.c:317
#11 0x082a4cd1 in ChangeWindowAttributes (pWin=0x89ad0a0, vmask=1,
vlist=0x89474dc, client=0x8a8bd48) at window.c:1085
#12 0x0828d80b in ProcChangeWindowAttributes (client=0x8a8bd48) at
dispatch.c:561
#13 0x0828d549 in Dispatch () at dispatch.c:462
#14 0x0829d468 in main (argc=1, argv=0xba64, envp=0xba6c) at
main.c:488

The log which is part of this bugreport is the one that was produced
as a result of the second attempt. I have no log from the first one
anymore.

-- Package-specific info:
01:00.0 VGA compatible controller: S3 Inc. 86c368 [Trio 3D/2X] (rev 02)
01:00.0 Class 0300: 5333:8a13 (rev 02)

### 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/Type1
FontPath/usr/lib/X11/fonts/CID
FontPath/usr/lib/X11/fonts/Speedo
FontPath/usr/lib/X11/fonts/misc
FontPath/usr/lib/X11/fonts/cyrillic
FontPath/usr/lib/X11/fonts/100dpi
FontPath/usr/lib/X11/fonts/75dpi
EndSection

Section Module
LoadGLcore
Loadbitmap
Loaddbe
Loadddc
Loaddri
Loadextmod
Loadfreetype
Loadglx
Loadint10
Loadrecord
Loadspeedo
Loadtype1
Loadvbe
EndSection

Section InputDevice
Identifier  Generic Keyboard
Driver  keyboard
Option  CoreKeyboard
Option  XkbRules  xfree86
Option  XkbModel  pc105
Option  XkbLayout be
EndSection

Section InputDevice
Identifier  Configured Mouse
Driver  mouse
Option  CorePointer
Option  Device/dev/psaux
Option  Protocol  ImPS/2
Option  ZAxisMapping  4 5
EndSection

Section InputDevice
Identifier  Generic Mouse
Driver  mouse
Option  SendCoreEvents

Re: review wanted of new Debian X FAQ entry

[Wouter Verhelst]

Op di 04-03-2003, om 22:24 schreef Geert Uytterhoeven:
[added [EMAIL PROTECTED] to the Cc list; -x and -powerpc should
probably be removed, so setting reply-to]
  There are actually some 2.4 kernels available for m68k, but due to an
  issue related to glibc[1] that started somewhere in the glibc-2.2 area,
  they don't boot.
  
  There used to be a bug report on glibc regarding that issue, which was
  rather quickly reassigned to the kernel-patch-2.4.7-m68k package. Since,
  to date, nobody ever solved the issue, the latter package has now been
  removed from the archive.
 
 What's the real problem? I'm running 2.4.20 (from Linux/m68k CVS) on my Amiga,
 with glibc-2.2.5-3? Or is this version glibc too old to exhibit the problem?

No, it is not; according to the bug report, problems started with glibc
2.2.4.

I must admit that I personally never tried running a 2.4 kernel on my
m68k box, since I did not find the time back then to try it out, and did
not hear any success reports from people running 2.4 on m68k (not on
[EMAIL PROTECTED], on [EMAIL PROTECTED], or in
comp.os.linux.m68k). In fact, yours is the first success report I ever
heard. Also, I vaguely remember something about this bug being
Mac-specific, but I might have been dreaming about that part.

Are you running Debian on that particular box? If not, the problems
could be Debian-specific...

-- 
wouter at grep dot be
An expert can usually spot the difference between a fake charge and a
full one, but there are plenty of dead experts. 
  -- National Geographic Channel, in a documentary about large African beasts.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: review wanted of new Debian X FAQ entry

[Wouter Verhelst]

Op di 04-03-2003, om 22:24 schreef Geert Uytterhoeven:
[added [EMAIL PROTECTED] to the Cc list; -x and -powerpc should
probably be removed, so setting reply-to]
  There are actually some 2.4 kernels available for m68k, but due to an
  issue related to glibc[1] that started somewhere in the glibc-2.2 area,
  they don't boot.
  
  There used to be a bug report on glibc regarding that issue, which was
  rather quickly reassigned to the kernel-patch-2.4.7-m68k package. Since,
  to date, nobody ever solved the issue, the latter package has now been
  removed from the archive.
 
 What's the real problem? I'm running 2.4.20 (from Linux/m68k CVS) on my Amiga,
 with glibc-2.2.5-3? Or is this version glibc too old to exhibit the problem?

No, it is not; according to the bug report, problems started with glibc
2.2.4.

I must admit that I personally never tried running a 2.4 kernel on my
m68k box, since I did not find the time back then to try it out, and did
not hear any success reports from people running 2.4 on m68k (not on
[EMAIL PROTECTED], on [EMAIL PROTECTED], or in
comp.os.linux.m68k). In fact, yours is the first success report I ever
heard. Also, I vaguely remember something about this bug being
Mac-specific, but I might have been dreaming about that part.

Are you running Debian on that particular box? If not, the problems
could be Debian-specific...

-- 
wouter at grep dot be
An expert can usually spot the difference between a fake charge and a
full one, but there are plenty of dead experts. 
  -- National Geographic Channel, in a documentary about large African beasts.

Re: review wanted of new Debian X FAQ entry

[Wouter Verhelst]

Op ma 03-03-2003, om 23:45 schreef Branden Robinson:
 On Mon, Mar 03, 2003 at 11:15:03AM +0100, Xavier Bestel wrote:
  Le lun 03/03/2003 ? 01:36, Branden Robinson a ?crit :
  
  To date, no kernels with the feature of sending Linux keycodes exist for
  m68k-based Macintoshes.
  
  You should perhaps indicate the date and kernel version this refers to.
 
 If someone could clarify the situation with kernel 2.4 on m68k, I'd
 appreciate it.

There are actually some 2.4 kernels available for m68k, but due to an
issue related to glibc[1] that started somewhere in the glibc-2.2 area,
they don't boot.

There used to be a bug report on glibc regarding that issue, which was
rather quickly reassigned to the kernel-patch-2.4.7-m68k package. Since,
to date, nobody ever solved the issue, the latter package has now been
removed from the archive.

[1] note that I'm not pointing fingers here, I'm not skilled enough in
that area to tell who's fault it is.

-- 
wouter at grep dot be
An expert can usually spot the difference between a fake charge and a
full one, but there are plenty of dead experts. 
  -- National Geographic Channel, in a documentary about large African beasts.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: review wanted of new Debian X FAQ entry

[Wouter Verhelst]

Op ma 03-03-2003, om 23:45 schreef Branden Robinson:
 On Mon, Mar 03, 2003 at 11:15:03AM +0100, Xavier Bestel wrote:
  Le lun 03/03/2003 ? 01:36, Branden Robinson a ?crit :
  
  To date, no kernels with the feature of sending Linux keycodes exist 
   for
  m68k-based Macintoshes.
  
  You should perhaps indicate the date and kernel version this refers to.
 
 If someone could clarify the situation with kernel 2.4 on m68k, I'd
 appreciate it.

There are actually some 2.4 kernels available for m68k, but due to an
issue related to glibc[1] that started somewhere in the glibc-2.2 area,
they don't boot.

There used to be a bug report on glibc regarding that issue, which was
rather quickly reassigned to the kernel-patch-2.4.7-m68k package. Since,
to date, nobody ever solved the issue, the latter package has now been
removed from the archive.

[1] note that I'm not pointing fingers here, I'm not skilled enough in
that area to tell who's fault it is.

-- 
wouter at grep dot be
An expert can usually spot the difference between a fake charge and a
full one, but there are plenty of dead experts. 
  -- National Geographic Channel, in a documentary about large African beasts.

Re: review wanted of new Debian X FAQ entry

[Wouter Verhelst]

Op ma 03-03-2003, om 01:36 schreef Branden Robinson:
 Hi folks,
 
 I'm adding the following FAQ entry to the Debian X FAQ.

You have a FAQ? Nice. Didn't know. Where can I find it?

 I would very much appreciate correction of any factual errors I have
 made.

As far as I'm concerned (m68k-side of things), I could not find any
obvious errors.

However, I'd like to suggest adding another entry, regarding the fact
that on (at least) m68k-macs, it is *impossible* to switch the color
depth or screen resolution of the display under Linux; one has to choose
the display depth which is chosen under MacOS, and use a line such as

Mode Default

in the correct SubSection for the display.

If a question such as this one is not already in your FAQ, that is...

-- 
wouter at grep dot be
An expert can usually spot the difference between a fake charge and a
full one, but there are plenty of dead experts. 
  -- National Geographic Channel, in a documentary about large African beasts.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: review wanted of new Debian X FAQ entry

[Wouter Verhelst]

Op ma 03-03-2003, om 01:36 schreef Branden Robinson:
 Hi folks,
 
 I'm adding the following FAQ entry to the Debian X FAQ.

You have a FAQ? Nice. Didn't know. Where can I find it?

 I would very much appreciate correction of any factual errors I have
 made.

As far as I'm concerned (m68k-side of things), I could not find any
obvious errors.

However, I'd like to suggest adding another entry, regarding the fact
that on (at least) m68k-macs, it is *impossible* to switch the color
depth or screen resolution of the display under Linux; one has to choose
the display depth which is chosen under MacOS, and use a line such as

Mode Default

in the correct SubSection for the display.

If a question such as this one is not already in your FAQ, that is...

-- 
wouter at grep dot be
An expert can usually spot the difference between a fake charge and a
full one, but there are plenty of dead experts. 
  -- National Geographic Channel, in a documentary about large African beasts.