help-guix
[Top][All Lists]
Advanced

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

Re: Trouble configuring guix


From: Yasuaki Kudo
Subject: Re: Trouble configuring guix
Date: Sun, 20 Feb 2022 18:27:29 +0900
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.6.1

Hi Julien,

I have just suggested something similar on our Guix Development mailing list - to solve this problem, we need to create a parallel, downgraded community with higher tolerance for corruption.  It serves no one that people are kept in the dark about alternatives to the GNU Purity world.

While I do support the GNU principles and this being one of the main selling points of Guix, I would rather stay with Guix with corrupt packages than to go back to Windows and other proprietary-tolerant Linux distributions.

I have my distaste of Actually-Existing-Capitalism and its natural extension, the 'Proprietary Software', but my approach is to beat them by creating better alternatives, winning over the 99% of the population that don't give a damn about Proprietary or Free Software debate, who just want something that works well.

In that pursuit, I have no problem, at least temporarily, in taking full advantage of the proprietary software, preferably managed under the reliable Free Software systems.   That's what makes Guix my ideal choice.

We can create the Vernacular Guix Community and happily coexist 😁

-Yasu


On 2/20/22 16:27, Julien Lepiller wrote:
Hi Yasuaki,

That's great to hear about why you came to guix, but please don't advertise for 
non-free software on guix mailing lists :)

On February 20, 2022 3:03:07 AM GMT+01:00, Yasuaki Kudo <yasu@yasuaki.com> 
wrote:
Hi!,

I just wanted to let you know I came to Guix for the exact same reason -
Nix was way too cryptic for me 😅

I don't have any answer (sorry I am not familiar with what you
mentioned) but here's my configuration (I use Wayland and "Corrupt"
(meaning non-deblobbed, I guess) Linux)

https://github.com/yugawara/workers-cafe/tree/main/workers-memo/guix

-Yasu

On 2/20/22 09:33, Cássio Tavares wrote:
Hello there!

Well, I need help...

## Context:

    * I have just a little familiarity with Guile Scheme, because I'm a
      LilyPond user;
    * I finally have a desktop that doesn't need non-libre drivers;
    * Although I'm not in the Tech world, I love GNU's (and the FSF's)
      philosophy;
    * I have been playing with Nix, but find it very cryptic -- not easy
      to understand at all.

    So, Guix seems to be the path I'm on now.

## Situation:

    I have several problems to fix, but the most important right now is
    to get my keyboard to work with sddm, and I need sddm for
    Wayland. So, without sddm, this works:

```
      ...

      (define %this-keyboard  (keyboard-layout "br" "abnt2"))

      ...

      (operating-system
        ...

        (keyboard-layout  %this-keyboard)

        ... )

```

    But `guix system reconfigure /etc/config.scm` fails when this is this:

```
      (use-modules
        (gnu)
        (gnu system nss)
        (gnu services networking)
        (gnu services sddm)
        (gnu services cups)
        (gnu services desktop)
        (gnu services ssh)
        (gnu services xorg))

      ...

      (define %this-keyboard (keyboard-layout  "br" "abnt2"))

      ...

      (operating-system
        ...

        (keyboard-layout  %this-keyboard)

        ...

        (services
          (append
            (list
              (service dhcp-client-service-type)
              (service ntp-service-type)
              (service gpm-service-type)
              (service cups-service-type)
              (service elogind-service-type)
              (service sddm-service-type
                (sddm-configuration
                  (display-server "wayland")
                  (numlock "on")
                  (theme "guix-simplyblack-sddm-theme")
                  (xorg-configuration
                    (keyboard-layout %this-keyboard)))))
            %base-services))

        ... )

```

    Then, when I try to run `guix system reconfigure /etc/config.scm`, I
    get this backtrace:

root@udu ~#
    > Backtrace:
    >           19 (primitive-load "/root/.config/guix/current/bin/guix")
    > In guix/ui.scm:
    >    2229:7 18 (run-guix . _)
    >   2192:10 17 (run-guix-command _ . _)
    > In ice-9/boot-9.scm:
    >   1752:10 16 (with-exception-handler _ _ #:unwind? _ # _)
    > In guix/status.scm:
    >     829:3 15 (_)
    >     809:4 14 (call-with-status-report _ _)
    > In guix/scripts/system.scm:
    >    1256:4 13 (_)
    > In ice-9/boot-9.scm:
    >   1752:10 12 (with-exception-handler _ _ #:unwind? _ # _)
    > In guix/store.scm:
    >    658:37 11 (thunk)
    >    1320:8 10 (call-with-build-handler #<procedure 7faf357d0060 at g…> …)
    >   2129:25  9 (run-with-store #<store-connection 256.99 7faf38008190> …)
    > In guix/scripts/system.scm:
    >     827:2  8 (_ _)
    >     703:8  7 (_ #<store-connection 256.99 7faf38008190>)
    > In gnu/system.scm:
    >   1227:19  6 (operating-system-derivation _)
    >    748:11  5 (operating-system-services #<<operating-system> kernel:…>)
    >    782:20  4 (services _)
    > In /etc/config.scm:
    >    185:14  3 (services #<<operating-system> kernel: #<package linux-…>)
    >    185:14  2 (services #<<keyboard-layout> name: "br" variant: "abnt…>)
    > In ice-9/boot-9.scm:
    >   1685:16  1 (raise-exception _ #:continuable? _)
    >   1685:16  0 (raise-exception _ #:continuable? _)
    >
    > ice-9/boot-9.scm:1685:16: In procedure raise-exception:
    > Wrong type to apply: #<<keyboard-layout> name: "br" variant:
"abnt2" model: #f options: ()>

## Conclusion:

    Two things tell me that the problem is really in the keyboard
    configuration within the configuration of the sddm service:

    * When I remove the `xorg-configuration` from the `sddm-configuration`,
      the reconfiguration returns no error, and the sddm service works
      normally.
    * And in this setup, the keyboard works on the console, just not on the
      desktop environment.

Best regards,
And thank you.

Cassio




reply via email to

[Prev in Thread] Current Thread [Next in Thread]