From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jack Hill Subject: Re: Color calibrating scanner with GNOME Date: Sat, 16 Mar 2019 22:45:02 -0400 (EDT) Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Return-path: Received: from eggs.gnu.org ([209.51.188.92]:44341) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1h5Lyo-0007W2-3G for help-guix@gnu.org; Sat, 16 Mar 2019 22:56:54 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1h5LnM-0007t9-63 for help-guix@gnu.org; Sat, 16 Mar 2019 22:45:04 -0400 Received: from minsky.hcoop.net ([104.248.1.95]:42268) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1h5LnL-0007sR-VQ for help-guix@gnu.org; Sat, 16 Mar 2019 22:45:04 -0400 Received: from marsh.hcoop.net ([45.55.52.66]) by minsky.hcoop.net with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1h5LnK-0007BT-F0 for help-guix@gnu.org; Sat, 16 Mar 2019 22:45:02 -0400 In-Reply-To: List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org Sender: "Help-Guix" To: help-guix@gnu.org On Sat, 16 Mar 2019, Jack Hill wrote: > On Guix, when the scanner is connected via USB it cannot be found by my > user's scanning programs (or, therefore, the GNOME hardware/calibration > dialog). However, it can be found as root. I suspect the problem is a missing > udev rule. What is the right way to proceed? Indeed, it was a udev problem. Adding: (simple-service 'sane-udev-rules udev-service-type (list sane-backends)) to my services solves the problem and I can see the scanner from my unprivileged user, and it shows up the the GNOME hardware/calibration dialog. Unfortunately, clicking on the "calibrate" button does nothing. On Debian buster with GNOME 3.30, doing so brings up a calibration wizard. I also noticed since adding this rule that, I get messages like: udevd[3658]: specified group 'scanner' unknown in dmesg. Should adding the sane udev rules also create a scanner POSIX group? Thoughts? I'll have to check out how Debian handles this. Best, Jack