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

Bug#239179: x-window-system-core: XFree86 shouldn't access hardware directly



reassign 239179 xserver-xfree86
retitle 239179 xserver-xfree86: kernel says 'This is an XFree86 bug. It shouldn't access hardware directly.'
severity 239179 normal
merge 224909 239179
thanks

On Sun, Mar 21, 2004 at 12:22:07PM +0100, José Pelegrín wrote:
> Package: x-window-system-core
> Version: 4.3.0-7
> Severity: important
> Tags: sid
> 
> I found at my '/var/log/messages' this messages:
> 
>   Mar 21 12:07:14 hank vmunix: atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
>   Mar 21 12:07:14 hank vmunix: atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly.
> 
> It happens when start my X session. Also I see another similar messages
> related to keyboard when I press any of the multimedia keys:
> 
>   Mar 21 12:09:14 hank vmunix: atkbd.c: Unknown key pressed (translated set 2, code 0x81 on isa0060/serio0).
>   Mar 21 12:09:14 hank vmunix: atkbd.c: Use 'setkeycodes e001 <keycode>' to make it known.
> 
> Any of the aboves messages doesn't appear when using this version of the XFree
> (4.3.0-7) but with kernel 2.4.

[The following is a form letter.]

Hello,

You recently filed a duplicate bug report against a Debian package; that
is, the problem had already been reported.

While there is often nothing inherently wrong with doing so, the filing of
duplicate reports can cause Debian package maintainers to spend time
performing triage and maintenance operations on bug reports (e.g.,
instructing the Debian Bug Tracking System to merge the duplicates) that
could otherwise be spent resolving problems and doing other work on the
package.

One very good way to file bugs with the Debian Bug Tracking System is to
use the "reportbug" package and command of the same name.  A very nice
feature of reportbug is that, if the machine where you run it has network
access to the World Wide Web, it can query the Debian Bug Tracking System
and show you existing reports.  This reduces the chance that you'll file a
duplicate report, and offers you the option of adding follow-up information
to an existing bug report.  This is especially valuable if you have unique
information to add to an existing report, because this way information
relevant to the problem is gathered together in one place as opposed to
being scattered among multiple, duplicate bug reports where some facts may
be overlooked by the package maintainers.  The reportbug program also does
a lot of automatic information-gathering that helps package maintainers to
understand your system configuration, and also ensures that your message to
the Debian Bug Tracking System is well-formed so that it is processed
correctly by the automated tools that manage the reports.  (If you've ever
gotten a "bounce" message from the Debian Bug Tracking System that tells
you your message couldn't be processed, you might appreciate this latter
feature.)

Therefore, I strongly urge you to give "reportbug" a try as your primary
bug reporting tool for the Debian System.

One way to install reportbug is with "apt-get"; for
example:

  # apt-get install reportbug

The "reportbug" command has a few different modes that cater to different
levels of user expertise.  If this message has contained a lot of jargon
that is unfamiliar to you, you likely want to use reportbug's "novice"
mode; here's one way to do that.

  $ reportbug --mode=novice
  Please enter the name of the package in which you have found a problem,
  or type 'other' to report a more general problem.
  >

If you're more sophisticated, or if you are not using the released version
of Debian ("stable"), but instead Debian "testing" or "unstable", you
should use reportbug's standard mode.

  $ reportbug
  Please enter the name of the package in which you have found a problem,
  or type 'other' to report a more general problem.
  >

The reportbug command is extensively documented in its usage message and
manual page.  Commands to view these pieces of documentation are:

  $ reportbug --help | more
  $ man reportbug

(The output of the above commands has been omitted from this message.)

Thanks for using the Debian system!

-- 
G. Branden Robinson                |    Half of being smart is knowing what
Debian GNU/Linux                   |    you're dumb at.
branden@debian.org                 |    -- David Gerrold
http://people.debian.org/~branden/ |

Attachment: signature.asc
Description: Digital signature


Reply to: