[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#385078: marked as done (xserver-xorg: impossible mouse configuration other than /dev/input/mice)

Your message dated Sat, 7 Oct 2006 14:31:24 +0200
with message-id <20061007123124.GA28442@darkside.22.kls.lan>
and subject line Bug#385078 closed by David Nusinow <dnusinow@debian.org> (Bug#385078: fixed in xorg 1:7.1.0-3)
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: xserver-xorg
Version: 1:7.0.23
Severity: serious

Hello,

upgrading xserver-xorg from 6.9.0.dfsg.1-6 to 1:7.0.23 broke my
previously running X:

	No core pointer

	Fatal server error:
	failed to initialize core devices

This is because xserver-xorg.config forces mouse port to /dev/input/mice
while it was /dev/gpmdata before. And since /dev/input/mice just doesn't
exist, startx fails.
I think this is because xserver-xorg.config seems to hardcode the mouse
port to /dev/input/mice currently:

xserver-xorg.config:2022:AUTODETECTED_PORT="/dev/input/mice"
xserver-xorg.config:2023:AUTODETECTED_PROTOCOL="ImPS/2"
xserver-xorg.config:2024:
xserver-xorg.config:2025:db_subst xserver-xorg/config/inputdevice/mouse/port choices $AUTODETECTED_PORT
xserver-xorg.config:2026:auto_answer db_input "$(priority_ceil low)" xserver-xorg/config/inputdevice/mouse/port "${AUTODETECTED_PORT}"
xserver-xorg.config:2027:
xserver-xorg.config:2028:db_get xserver-xorg/config/inputdevice/mouse/port

And because I always configured X via xserver-xorg, the config entry has
the seen flag set and is not shown again. I'm not even able to change it
via dpkg-reconfigure :/ Yes, my debconf/priority is set to low, but also
an explicit dpkg-reconfigure -plow doesn't show it.

I don't know why you think you need to hardcode things this way - okay,
the mouse autodetection didn't work well with 6.9 (especially with gpm
running it left the mouse in some strange state), but IMHO asking users
then would be a better option.

Since for most users /dev/input/mice should be available, I don't set
the bug's severity to grave. However, I don't think the package is
suitable for release with this behaviour. Especially because the package
currently breaks previously running systems this way.

My X was always configured via the package's config-interface. This is
currently impossible - I have to manually fix my xorg.conf since the
package doesn't leave me another chance :/


regards
   Mario
-- 
It is practically impossible to teach good programming style to students
that have had prior exposure to BASIC: as potential programmers they are
mentally mutilated beyond hope of regeneration.  -- Dijkstra

Attachment: signature.asc
Description: Digital signature


--- End Message ---
--- Begin Message --- 
On Fri, Oct 06, 2006 at 02:59:29PM +0200, Mario 'BitKoenig' Holbe wrote:
> I cannot confirm that. Neither `dpkg-reconfigure xserver-xorg' nor
> `dpkg-reconfigure -phigh xserver-xorg' nor `dpkg-reconfigure -plow
> xserver-xorg' asks me about the mouse-device. It always fixes it to
> /dev/input/mice.

I'm sorry, I was too early. I got the close-mail and at the same day
there was an update of xserver-xorg, so I thought this would be the
right version. However, this update was to 1:7.1.0-2, so one too early
for me to check.

Today I got 1:7.1.0-3 and now it lets me choose the mouse device, so
everything appears to be okay.


Sorry & thanks for your work
   Mario
-- 
I thought the only thing the internet was good for was porn.  -- Futurama

Attachment: signature.asc
Description: Digital signature


--- End Message ---
Reply to: