unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: nee <nee@cock.li>
Cc: help-guix@gnu.org
Subject: Re: I installed GuixSD on my laptop
Date: Sun, 4 Jun 2017 13:15:40 +0200	[thread overview]
Message-ID: <20170604111537.GB4279@floriannotebook> (raw)
In-Reply-To: <86942c60-38fb-7cd4-7162-72705c50c15a@cock.li>

On Sat, Jun 03, 2017 at 10:53:24PM +0200, nee wrote:
> Hello everyone, a few months ago I installed GuixSD 0.12 in a luks
> encrypted partition on my laptop. Here are some problems I have with it
> so far.
>
> […]
> 
> 5. I've been using thunderbird with Enigmail previously. I think I read
> on irc that icedove would be the way to go, and that it hasn't been
> packaged yet.
> Enigmail is really neat, so I wouldn't want to be without it.
>

I tried to package Evolution once, but I had problems: It only worked
when it was the last installed package. I believe it’s not the only
GNOME package sufering from this issue. I still want to try again when
I have some more time to learn Guix…

That said, I switched to Mutt and am happy with it. Seems much better
than Enigmail because it makes clear which parts of a message are
signed. I’m not sure though if Thunderbird Enigmail can spit out this
information somehow too.

> 
> * An unrelated story:
> I had to install GuixSD twice, because I forgot to punch "(dependencies
> mapped-devices)" into my file-system configuration.
> So shepard would not boot up properly and after some time I got a guile
> debug repl.
> I see that this is my own fault, for not reading the docs properly.
> I hope the new ncurses installer will help to prevent such mistakes.
> 

Probably this should be verified by Guix before GuixSD gets installed.

> * Not a problem: Touchpad works different
> My first observation was that the touchpad was not working correctly.
> The touchpad only works for mouse movement.
> Clicking by tapping any point on the pad does not work.
> Scrolling by moving down/up the right edge does not work.
> 
> I use the hardware buttons below it for clicking, but I wonder, aren't
> there some laptops without those?
> Later I found out that scrolling works with two fingers and this whole
> setup is actually much better, since I do way less misclicks that way!
> 
> * xf86-input-synaptics?
> Because I previously tried nixos I directly installed
> xf86-input-synaptics with my installation. I never tried to use my
> system without it. If it is required it should be mentioned in the docs.
>

No. Libinput should be used. Not Synaptics. Synaptics is
obsolete. Libinput does not get used on my GuixSD GNOME either though;
I believe it still uses Synaptics. My GNOME also does not use Wayland
yet, but Xfce does not even support Wayland AFAIK…

Regards,
Florian

  parent reply	other threads:[~2017-06-04 11:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-03 20:53 I installed GuixSD on my laptop nee
2017-06-03 22:57 ` ng0
2017-06-04  0:32 ` someone
2017-06-05 19:48   ` Ludovic Courtès
2017-06-04 11:15 ` pelzflorian (Florian Pelz) [this message]
2017-06-04 19:35 ` Arun Isaac
2017-06-05 19:53 ` Ludovic Courtès

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=20170604111537.GB4279@floriannotebook \
    --to=pelzflorian@pelzflorian.de \
    --cc=help-guix@gnu.org \
    --cc=nee@cock.li \
    /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).