unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: wisdomlight@protonmail.com
Cc: "help-guix@gnu.org" <help-guix@gnu.org>
Subject: Re: Mouse issue
Date: Wed, 15 Jan 2020 18:24:09 +0100	[thread overview]
Message-ID: <20200115172409.utxv5qgrxhqqlvsp@pelzflorian.localdomain> (raw)
In-Reply-To: <m_uGGb58zz1Nd6yvFqVaUYgzOKGnOjU067wzYRpzle1bxWR3g1hl34aP5BqpKgeLGoGIJ4Pua5LhBVqd5EjofbRI__eFKRUrIDKBocsLv0o=@protonmail.com>

On Wed, Jan 15, 2020 at 04:32:30PM +0000, wisdomlight--- via wrote:
> Guix on my MacBook Air 13”
> 
> most times of booting the system the mouse goes only up and down.
> It is stuck on the right side of the screen and just goes up and down.

Ohh I thought I was the only one with that issue.  Are you using a
Macbook too?  I investigated long ago and had patched Guix to enable
debugging for udev.  Maybe it was this patch?

diff --git a/gnu/services/base.scm b/gnu/services/base.scm
index b1eff89ecc..11509aaff3 100644
--- a/gnu/services/base.scm
+++ b/gnu/services/base.scm
@@ -2054,7 +2054,7 @@ item of @var{packages}."
                     (make-static-device-nodes directory))
                   (umask old-umask))
 
-                (let ((pid (fork+exec-command (list udevd))))
+                (let ((pid (fork+exec-command (list udevd "--debug") #:log-file "/var/log/udevd")))
                   ;; Wait until udevd is up and running.  This appears to
                   ;; be needed so that the events triggered below are
                   ;; actually handled.

But why did I set the log-file?  I don’t remember.

Whatever.  Back then I found that only on bad boots the trackpad is
detected as a Mouse and therefore is not treated as a trackpad.

root@florianmacbook /var/log/gdm# cat greeter.log.2 | grep Apple | grep tagged
(II) event4  - Apple Inc. Apple Internal Keyboard / Trackpad: is tagged by udev as: Keyboard
(II) event4  - Apple Inc. Apple Internal Keyboard / Trackpad: is tagged by udev as: Keyboard
(II) event14 - Apple Inc. Apple Internal Keyboard / Trackpad: is tagged by udev as: Mouse
(II) event14 - Apple Inc. Apple Internal Keyboard / Trackpad: is tagged by udev as: Mouse
(II) event15 - Apple Computer, Inc. IR Receiver: is tagged by udev as: Keyboard
(II) event15 - Apple Computer, Inc. IR Receiver: is tagged by udev as: Keyboard
root@florianmacbook /var/log/gdm# cat greeter.log.1 | grep Apple | grep tagged
(II) event4  - Apple Inc. Apple Internal Keyboard / Trackpad: is tagged by udev as: Keyboard
(II) event4  - Apple Inc. Apple Internal Keyboard / Trackpad: is tagged by udev as: Keyboard
(II) event12 - Apple Computer, Inc. IR Receiver: is tagged by udev as: Keyboard
(II) event12 - Apple Computer, Inc. IR Receiver: is tagged by udev as: Keyboard

I had not investigated further what is responsible for this trackpad
detection.  I suppose there is some difference between the udev setup
used by Guix and the udev setup used by others.

Regards,
Florian

  reply	other threads:[~2020-01-15 17:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-15 16:32 Mouse issue wisdomlight--- via
2020-01-15 17:24 ` pelzflorian (Florian Pelz) [this message]
2020-02-07 15:21 ` Joshua Branson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200115172409.utxv5qgrxhqqlvsp@pelzflorian.localdomain \
    --to=pelzflorian@pelzflorian.de \
    --cc=help-guix@gnu.org \
    --cc=wisdomlight@protonmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).