Bug#446851: xserver-xorg-core: please copy (and improve) x11-input.fdi to /etc/hal/fdi/policy/

2007-10-18 Thread Michel Dänzer

On Wed, 2007-10-17 at 19:16 -0400, David Nusinow wrote:
 On Wed, Oct 17, 2007 at 09:46:54AM -0700, Warren Turkal wrote:
  On 10/17/07, Daniel Stone [EMAIL PROTECTED] wrote:
   Because it's not clearly in the domain of Xorg.  x11-input makes sense,
   but then again, it's largely a system decision.  OTOH, XKB can be used
   in the console, not just in X (hence why it's namespaced input.xkb and
   not input.x11.xkb or so), so that's why.
  
  Okay...so it's the domain of xkb? Even in that case, it seems there is
  a more appropriate place for it than hal.
  
   Also, as Michel mentions, everything else is already in hal-info, so eh.
   The latest release includes it, AIUI.
  
  Well, I really don't care where it comes from, as long as it's included.
 
 I think including it in our package until HAL gets it is probably the right
 move. More package churn on the server is probably going to be a fact of
 life for a while anyway. The reason I haven't really put much work in to
 input hotplug is because I've been focused on getting output autodetection
 in better shape.  Once that's done, I'll get to this if no one else beats
 me to it.

I think it would be better to listen to upstream and reassign this to
hal-info...


-- 
Earthling Michel Dänzer   |  http://tungstengraphics.com
Libre software enthusiast |  Debian, X and DRI developer




Bug#446851: xserver-xorg-core: please copy (and improve) x11-input.fdi to /etc/hal/fdi/policy/

2007-10-18 Thread David Nusinow
reassign 446851 hal
retitle 446851 Please package new upstream version which includes x11-input.fdi
thanks

On Thu, Oct 18, 2007 at 09:45:11AM +0200, Michel Dänzer wrote:
 
 On Wed, 2007-10-17 at 19:16 -0400, David Nusinow wrote:
  On Wed, Oct 17, 2007 at 09:46:54AM -0700, Warren Turkal wrote:
   On 10/17/07, Daniel Stone [EMAIL PROTECTED] wrote:
Because it's not clearly in the domain of Xorg.  x11-input makes sense,
but then again, it's largely a system decision.  OTOH, XKB can be used
in the console, not just in X (hence why it's namespaced input.xkb and
not input.x11.xkb or so), so that's why.
   
   Okay...so it's the domain of xkb? Even in that case, it seems there is
   a more appropriate place for it than hal.
   
Also, as Michel mentions, everything else is already in hal-info, so eh.
The latest release includes it, AIUI.
   
   Well, I really don't care where it comes from, as long as it's included.
  
  I think including it in our package until HAL gets it is probably the right
  move. More package churn on the server is probably going to be a fact of
  life for a while anyway. The reason I haven't really put much work in to
  input hotplug is because I've been focused on getting output autodetection
  in better shape.  Once that's done, I'll get to this if no one else beats
  me to it.
 
 I think it would be better to listen to upstream and reassign this to
 hal-info...

Ok, Daniel's message didn't hit my inbox for some reason, so I just saw
the bit about it being in the new hal version. I'm reassigning this to hal
since it looks like all the .fdi files that hal itself ships belong to that
package, and x11-input.fdi is in that category. Sjoerd can reassign it if I
got it wrong.

 - David Nusinow



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



Bug#446851: xserver-xorg-core: please copy (and improve) x11-input.fdi to /etc/hal/fdi/policy/

2007-10-17 Thread Michel Dänzer

On Tue, 2007-10-16 at 21:46 -0700, Warren Turkal wrote:
 On 10/16/07, Michel Dänzer [EMAIL PROTECTED] wrote:
  AFAIK the reason it isn't installed by upstream is that it's just a stop
  gap until HAL ships its own file(s) for this. Shipping it in X packages
  now would go against this and might cause packaging churn down the road.
 
 Why would hal ship a file that is clearly in the domain of Xorg?

Daniel?

I just notice that with a couple of exceptions, all .fdi files seem
shipped by HAL packages. It might make sense to include x11-input.fdi as
an example though.


-- 
Earthling Michel Dänzer   |  http://tungstengraphics.com
Libre software enthusiast |  Debian, X and DRI developer




Bug#446851: xserver-xorg-core: please copy (and improve) x11-input.fdi to /etc/hal/fdi/policy/

2007-10-17 Thread Warren Turkal
On 10/17/07, Daniel Stone [EMAIL PROTECTED] wrote:
 Because it's not clearly in the domain of Xorg.  x11-input makes sense,
 but then again, it's largely a system decision.  OTOH, XKB can be used
 in the console, not just in X (hence why it's namespaced input.xkb and
 not input.x11.xkb or so), so that's why.

Okay...so it's the domain of xkb? Even in that case, it seems there is
a more appropriate place for it than hal.

 Also, as Michel mentions, everything else is already in hal-info, so eh.
 The latest release includes it, AIUI.

Well, I really don't care where it comes from, as long as it's included.

wt



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



Bug#446851: xserver-xorg-core: please copy (and improve) x11-input.fdi to /etc/hal/fdi/policy/

2007-10-17 Thread David Nusinow
On Wed, Oct 17, 2007 at 09:46:54AM -0700, Warren Turkal wrote:
 On 10/17/07, Daniel Stone [EMAIL PROTECTED] wrote:
  Because it's not clearly in the domain of Xorg.  x11-input makes sense,
  but then again, it's largely a system decision.  OTOH, XKB can be used
  in the console, not just in X (hence why it's namespaced input.xkb and
  not input.x11.xkb or so), so that's why.
 
 Okay...so it's the domain of xkb? Even in that case, it seems there is
 a more appropriate place for it than hal.
 
  Also, as Michel mentions, everything else is already in hal-info, so eh.
  The latest release includes it, AIUI.
 
 Well, I really don't care where it comes from, as long as it's included.

I think including it in our package until HAL gets it is probably the right
move. More package churn on the server is probably going to be a fact of
life for a while anyway. The reason I haven't really put much work in to
input hotplug is because I've been focused on getting output autodetection
in better shape.  Once that's done, I'll get to this if no one else beats
me to it.

 - David Nusinow



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



Bug#446851: xserver-xorg-core: please copy (and improve) x11-input.fdi to /etc/hal/fdi/policy/

2007-10-17 Thread Warren Turkal
On 10/17/07, David Nusinow [EMAIL PROTECTED] wrote:
 I think including it in our package until HAL gets it is probably the right
 move. More package churn on the server is probably going to be a fact of
 life for a while anyway. The reason I haven't really put much work in to
 input hotplug is because I've been focused on getting output autodetection
 in better shape.  Once that's done, I'll get to this if no one else beats
 me to it.

Output hotplug on Intel 915 is pretty terrible right now. It doesn't
appear to probe the connected monitor for the supported modes.
However, starting Xorg with the monitor attached works like a charm.

wt



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



Bug#446851: xserver-xorg-core: please copy (and improve) x11-input.fdi to /etc/hal/fdi/policy/

2007-10-17 Thread David Nusinow
On Wed, Oct 17, 2007 at 04:45:20PM -0700, Warren Turkal wrote:
 On 10/17/07, David Nusinow [EMAIL PROTECTED] wrote:
  I think including it in our package until HAL gets it is probably the right
  move. More package churn on the server is probably going to be a fact of
  life for a while anyway. The reason I haven't really put much work in to
  input hotplug is because I've been focused on getting output autodetection
  in better shape.  Once that's done, I'll get to this if no one else beats
  me to it.
 
 Output hotplug on Intel 915 is pretty terrible right now. It doesn't
 appear to probe the connected monitor for the supported modes.
 However, starting Xorg with the monitor attached works like a charm.

If you could open that as another bug, that'd be much preferrable to
discussing it in this one.

 - David Nusinow



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



Bug#446851: xserver-xorg-core: please copy (and improve) x11-input.fdi to /etc/hal/fdi/policy/

2007-10-17 Thread Warren Turkal
On 10/17/07, David Nusinow [EMAIL PROTECTED] wrote:
 If you could open that as another bug, that'd be much preferrable to
 discussing it in this one.

Fair enough.

wt



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



Bug#446851: xserver-xorg-core: please copy (and improve) x11-input.fdi to /etc/hal/fdi/policy/

2007-10-16 Thread Warren Turkal
Package: xserver-xorg-core
Version: 2:1.4-3
Severity: important

The file xorg-server-1.4/config/x11-input.fdi should be copied to
/etc/hal/fdi/policy/. This will allow hotplug input to work as well as
possible with the current version of xorg.

wt

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

/etc/X11/X target does not match checksum in /var/lib/x11/X.md5sum.

X server symlink status:
lrwxrwxrwx 1 root root 13 2006-08-30 00:29 /etc/X11/X - /usr/bin/Xorg
-rwxr-xr-x 1 root root 1669976 2007-09-29 07:33 /usr/bin/Xorg

Contents of /var/lib/x11/xorg.conf.roster:
xserver-xorg

VGA-compatible devices on PCI bus:
00:02.0 VGA compatible controller: Intel Corporation Mobile
915GM/GMS/910GML Express Graphics Controller (rev 04)

/etc/X11/xorg.conf unchanged from checksum in /var/lib/x11/xorg.conf.md5sum.

Xorg X server configuration file status:
-rw-r--r-- 1 root root 1936 2007-09-27 23:57 /etc/X11/xorg.conf

Contents of /etc/X11/xorg.conf:
# xorg.conf (xorg 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 xorg.conf manual page.
# (Type man xorg.conf at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
#   sudo dpkg-reconfigure -phigh xserver-xorg

Section Files
EndSection

Section InputDevice
Identifier  Generic Keyboard
Driver  kbd
Option  CoreKeyboard
Option  XkbRules  xorg
Option  XkbModel  pc104
Option  XkbLayout us
EndSection

Section InputDevice
Identifier  Configured Mouse
Driver  mouse
Option  CorePointer
Option  Device/dev/input/mice
Option  Protocol  ImPS/2
Option  Emulate3Buttons   true
EndSection

Section InputDevice
Identifier  Synaptics Touchpad
Driver  synaptics
Option  SendCoreEventstrue
Option  Device/dev/psaux
Option  Protocol  auto-dev
Option  HorizScrollDelta  0
EndSection

Section Device
Identifier  Intel Corporation Mobile 915GM/GMS/910GML Express
Graphics Controller
Driver  intel
BusID   PCI:0:2:0
EndSection

Section Monitor
Identifier  Generic Monitor
Option  DPMS
EndSection

Section Screen
Identifier  Default Screen
Device  Intel Corporation Mobile 915GM/GMS/910GML Express 
Graphics Controller
Monitor Generic Monitor
DefaultDepth24
SubSection Display
Modes   1280x768 1024x768 800x600 640x480
EndSubSection
EndSection

Section ServerLayout
Identifier  Default Layout
Screen  Default Screen
InputDevice Generic Keyboard
InputDevice Configured Mouse
InputDevice Synaptics Touchpad
EndSection


Xorg X server log files on system:
-rw-r--r-- 1 root root 39012 2007-06-18 20:20 /var/log/Xorg.1.log
-rw-r--r-- 1 root root 39012 2007-06-18 20:20 /var/log/Xorg.2.log
-rw-r--r-- 1 root root 42370 2007-10-15 23:03 /var/log/Xorg.0.log

Contents of most recent Xorg X server log file
/var/log/Xorg.0.log:

X.Org X Server 1.4.0
Release Date: 5 September 2007
X Protocol Version 11, Revision 0
Build Operating System: Linux Debian (xorg-server 2:1.4-3)
Current Operating System: Linux braindead 2.6.22-2-686 #1 SMP Fri Aug
31 00:24:01 UTC 2007 i686
Build Date: 29 September 2007  04:19:41PM

Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
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/Xorg.0.log, Time: Mon Oct 15 21:01:23 2007
(==) Using config file: /etc/X11/xorg.conf
(==) ServerLayout Default Layout
(**) |--Screen Default Screen (0)
(**) |   |--Monitor Generic Monitor
(**) |   |--Device Intel Corporation Mobile 915GM/GMS/910GML Express
Graphics Controller
(**) |--Input Device Generic Keyboard
(**) |--Input Device Configured Mouse
(**) |--Input Device Synaptics Touchpad
(==) Automatically adding devices
(==) Automatically enabling devices
(WW) The directory /usr/share/fonts/X11/cyrillic does not exist.
Entry deleted from font path.
(==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,

Bug#446851: xserver-xorg-core: please copy (and improve) x11-input.fdi to /etc/hal/fdi/policy/

2007-10-16 Thread Michel Dänzer

On Mon, 2007-10-15 at 23:30 -0700, Warren Turkal wrote:
 Package: xserver-xorg-core
 Version: 2:1.4-3
 Severity: important
 
 The file xorg-server-1.4/config/x11-input.fdi should be copied to
 /etc/hal/fdi/policy/. This will allow hotplug input to work as well as
 possible with the current version of xorg.

AFAIK the reason it isn't installed by upstream is that it's just a stop
gap until HAL ships its own file(s) for this. Shipping it in X packages
now would go against this and might cause packaging churn down the road.


-- 
Earthling Michel Dänzer   |  http://tungstengraphics.com
Libre software enthusiast |  Debian, X and DRI developer




Bug#446851: xserver-xorg-core: please copy (and improve) x11-input.fdi to /etc/hal/fdi/policy/

2007-10-16 Thread Warren Turkal
On 10/16/07, Michel Dänzer [EMAIL PROTECTED] wrote:
 AFAIK the reason it isn't installed by upstream is that it's just a stop
 gap until HAL ships its own file(s) for this. Shipping it in X packages
 now would go against this and might cause packaging churn down the road.

Why would hal ship a file that is clearly in the domain of Xorg?

wt