all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Marius Bakke <mbakke@fastmail.com>
To: guix-devel@gnu.org
Subject: Re: udev on 'core-updates' does not register new devices
Date: Tue, 08 Aug 2017 23:13:25 +0200	[thread overview]
Message-ID: <87wp6depai.fsf@fastmail.com> (raw)
In-Reply-To: <87poc6rjwu.fsf@fastmail.com>

[-- Attachment #1: Type: text/plain, Size: 1102 bytes --]

Marius Bakke <mbakke@fastmail.com> writes:

> Hello!
>
> I tried plugging in a USB drive on a GuixSD desktop system running from
> the 'core-updates' branch and get this in dmesg:
>
> [198220.121488] udevd[173]: RUN{builtin}: 'uaccess' unknown /gnu/store/cfs89vshgfzxr9rr311pf2y6cifyjq4l-udev-rules/lib/udev/rules.d/73-seat-late.rules:15
> [198300.595192] udevd[173]: RUN{builtin}: 'uaccess' unknown /gnu/store/cfs89vshgfzxr9rr311pf2y6cifyjq4l-udev-rules/lib/udev/rules.d/73-seat-late.rules:15
>
> And no new device node is created.
>
> The offending file is here:
> <https://github.com/elogind/elogind/blob/master/src/login/73-seat-late.rules.in>
>
> I also found this: <https://github.com/gentoo/eudev/issues/145>
>
> ...but I'm not sure what to do about it. Should we just delete this
> file, since it's seemingly unused on GuixSD?

I tried simply deleting it, but now *nothing* is registered when
plugging in a USB device. And I'm not sure why this problem occurs to
begin with, the changes since eudev 3.2.1 seem mostly harmless:

https://github.com/gentoo/eudev/commits/master

To be continued..

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  reply	other threads:[~2017-08-08 21:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-08  0:18 udev on 'core-updates' does not register new devices Marius Bakke
2017-08-08 21:13 ` Marius Bakke [this message]
2017-08-09  4:22 ` Mark H Weaver
2017-08-09 21:15   ` Marius Bakke

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

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

  git send-email \
    --in-reply-to=87wp6depai.fsf@fastmail.com \
    --to=mbakke@fastmail.com \
    --cc=guix-devel@gnu.org \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.