bug#38703: installion cannot be cancelled
Hello, > You mean that Ctrl-C wouldn’t work on the ‘guix system init’ process, > right? Is that behavior controlled by Newt, Mathieu? Before running the guix process, newt is suspended and resumed right after (see run-install-shell procedure). So it should reset the original terminal settings. Maybe it doesn't, or it's an issue with kmscon. I'll try to investigate. Thanks, Mathieu
bug#38804: Samsung Chromebook 3
Hi, On Sun, 29 Dec 2019 20:02:11 -0600 Caleb Herbert wrote: > I tried running the Guix System installer on my Chromebook. I wanted to > try replacing GalliumOS. > > Unsurprisingly, I get many errors do to proprietary firmware. My > keyboard doesn't work, so I can't check what all the messages said If you want, try connecting an usb keyboard in order to find out. It might work. pgpwTglIgy5Fw.pgp Description: OpenPGP digital signature
bug#38829: XmlListModel QML missing from qtdeclarative 5.12.x
In version 5.12.6 of the 'qtdeclarative' package, the 'lib/qt5/qml/QtQuick/XmlListModel' directory is missing (qtdeclarative 5.11.3 had it). It causes run time issues; for example the 'monero-gui' package builds fine but it fails to run: --8<---cut here---start->8--- 2019-12-31 12:50:42.076 W app startd (log: /home/guillaume/.bitmonero/monero-wallet-gui.log) 2019-12-31 12:50:42.077 W Qt:5.12.6 GUI:- | screen: 1920x1080 - dpi: 96.1263 - ratio:0.997092 2019-12-31 12:50:42.179 W QQmlApplicationEngine failed to load component 2019-12-31 12:50:42.179 W qrc:/main.qml:1693 Type WizardLang unavailable 2019-12-31 12:50:42.179 W qrc:/wizard/WizardLang.qml:32 module "QtQuick.XmlListModel" is not installed 2019-12-31 12:50:42.179 E Error: no root objects --8<---cut here---end--->8--- signature.asc Description: PGP signature
bug#38830: tty switching breaks gnome
Hi, While running a GNOME environment, switching TTY with Ctrl+alt+F2 and then switching back to Ctrl+alt+F1 does not work properly (GNOME is no longer visible). In all other distros I used it you could switch between F1 and F2 without problems (F1 would still have GNOME running and visible). Sometimes an app freezes GNOME and you need to go to another TTY to kill it, but you can't return back to GNOME so I usually have to reboot in order to fix this (sudo herd restart xorg-server doesn't really fix this either as I can't use evolution or anything that requires pinentry anymore, and I can't reopen some apps because they're already running, etc.). Thanks, Alex
bug#38831: IceCat: some codecs don't work without workaround
Hello,
I had some problems with video codecs in IceCat 68.3.0-guix0-preview1.
For example, consider this page: http://demo.nimius.net/video_test/. By
default, the videos under the headings H.264 / AAC and MPEG4 don't work
("No video with supported format and MIME type found.").
The following steps make the first of these videos work:
1. Open about:config
2. Click "I accept the risk!"
3. Set security.sandbox.content.read_path_whitelist to /gnu/store/
(the trailing / is important).
The instructions were originally sketched out in this help-guix
message:
https://lists.gnu.org/archive/html/help-guix/2019-12/msg00150.html
I believe it would be beneficial to make this a default.
On IRC, bandali suggested that it would be better to only whitelist the
necessary store subdirectories. I don't know how to gather such a list,
but it it seems like a good idea.
I don't know how about:config entries modified by the user behave when
IceCat is updated, but in some of the behaviors I can imagine, the
config entry stops updating, in which case it would be better to add
the paths to some internal whitelist (I reckon such a whitelist already
exists and contains something like /usr/lib).
Regards,
Jakub Kądziołka
CC: mhw as suggested by nckx
bug#38167: guix pull takes over 8 GiB of memory to finish if there are no substitutes
Hi Ludo, On Sun, 29 Dec 2019 23:41:42 +0100 Ludovic Courtès wrote: > > It could be because my modules in GUIX_PACKAGE_PATH contain an import cycle > > (I don't know whether it does, but I had such a cycle before). > > And that’s definitely a possibility! Can you try unsetting > GUIX_PACKAGE_PATH? Sure, but that will not decide it conclusively. It's pretty rare that guix pull has the problem above (once a week or so), so it could also be that it will work because it got a non-problematic case the same time (but not because of) I unset GUIX_PACKAGE_PATH. pgpXREozbYRNB.pgp Description: OpenPGP digital signature
bug#38804: Samsung Chromebook 3
On 12/31/2019 06:49 AM, Danny Milosavljevic wrote: >> Unsurprisingly, I get many errors do to proprietary firmware. My >> keyboard doesn't work, so I can't check what all the messages said > > If you want, try connecting an usb keyboard in order to find out. It might > work. I would have, if I had one. I'm the only one who uses a real computer here, and it's an X200 laptop. Everyone else uses Swindles and Android for all of their computing. -- Caleb Herbert KE0VVT 816-892-9669 https://bluehome.net/csh <> signature.asc Description: OpenPGP digital signature
bug#38804: Samsung Chromebook 3
On 12/31/2019 06:49 AM, Danny Milosavljevic wrote: > If you want, try connecting an usb keyboard in order to find out. It might > work. Also, I will have to unplug the Wi-Fi adapter to plug in the keyboard. There are only two USB ports, and one of them is the installation medium. I guess I won't need Wi-Fi on a laptop that doesn't even have a functioning keyboard. Although I've heard of RMS using a USB keyboard on top of his laptop because the default one was proprietary. (Isn't that why he used a keyboard on top of his OLPC?) -- Caleb Herbert KE0VVT 816-892-9669 https://bluehome.net/csh <> signature.asc Description: OpenPGP digital signature
bug#38529: Make --ad-hoc the default for guix environment proposed deprecation mechanism
Hi! Ricardo Wurmus skribis: > zimoun writes: [...] >> What about "guix spawn"? > > “spawn” is a very generic verb, much like “enter” (enter what?) or > “make”. “shell” has the awkward property of meaning different things > dependent on how you interpret it: “to shell” means to *remove* an outer > shell (like that of a nut) whereas “guix shell” as a noun would imply > *wrapping“ something in a shell. It sends mixed signals. We’d probably > want people to understand it as ‘spawn a command line shell’, but that’s > really not the primary purpose of ‘guix environment’. Yeah. > Thinking about words some more I started to wonder: do we want verbs or > nouns? I think verbs are preferred, but nouns are accepted. :-) For example, ‘time-machine’ was recently introduced, but I find it nice that way; ’travel-in-time’ wouldn’t be better. It’s much like Scheme APIs: we use nouns for object properties (like ‘commit-parent’) and verbs for things that are best viewed as actions (like ‘fold’). This is all subjective in a functional setting! > If we were looking for verbs that express the idea of creating an > environment or to place a thing inside of an environment we could use > one of these: > >to envelop (envelop what though? This seems to require two objects.) >to arrange (kinda misses the point) >to stage (in the theatric sense) >to frame (not in the criminal sense) >to contain (…the resulting process in a possibly leaky environment) >to join (…all these packages to form a new whole) >to group (…all these packages) > > (As a bonus: ‘to environ’ exists, but it suffers from the same problem > as ‘to envelop’.) > > Here are some nouns that might work: > >scene >frame >context >union > > All of them are shorter than “environment”! :) More data points! :-) --8<---cut here---start->8--- $ wn environment -synsn Synonyms/Hypernyms (Ordered by Estimated Frequency) of noun environment 2 senses of environment Sense 1 environment => situation, state of affairs Sense 2 environment, environs, surroundings, surround => geographical area, geographic area, geographical region, geographic region $ wn environ -synsv Synonyms/Hypernyms (Ordered by Estimated Frequency) of verb environ 1 sense of environ Sense 1 surround, environ, ring, skirt, border => touch, adjoin, meet, contact --8<---cut here---end--->8--- Maybe “union”, “surround”, or… “profile”? (I’d reserve “guix spawn” or “guix run” for the tool that runs commands in a least-authority environment, as we’ve discussed in the past.) Ludo’.
bug#38167: guix pull takes over 8 GiB of memory to finish if there are no substitutes
Hi, Danny Milosavljevic skribis: > On Sun, 29 Dec 2019 23:41:42 +0100 > Ludovic Courtès wrote: > >> > It could be because my modules in GUIX_PACKAGE_PATH contain an import cycle >> > (I don't know whether it does, but I had such a cycle before). >> >> And that’s definitely a possibility! Can you try unsetting >> GUIX_PACKAGE_PATH? > > Sure, but that will not decide it conclusively. > > It's pretty rare that guix pull has the problem above (once a week or so), so > it could also be that it will work because it got a non-problematic case the > same time (but not because of) I unset GUIX_PACKAGE_PATH. If you can reproduce the bug when GUIX_PACKAGE_PATH is unset, I’m happy to investigate further. Otherwise it’s hard to conclude because we’re effectively running arbitrary code so the bug may well have nothing to do with ‘guix pull’ itself. Let me know! Ludo’.
bug#38529: Make --ad-hoc the default for guix environment proposed deprecation mechanism
Ludovic Courtès writes: > Maybe “union”, “surround”, or… “profile”? “profile” is a tempting choice, but it’s treacherous because we might be blinded by the glow of the implementation of environments as volatile profiles. On the other hand: if we could also move some of the features of the “package” sub-command under “profile” (e.g. those that relate to the management of, well, profiles), that could be a winning move. Tricky. > (I’d reserve “guix spawn” or “guix run” for the tool that runs commands > in a least-authority environment, as we’ve discussed in the past.) Same. -- Ricardo
bug#22883: Authenticating Git checkouts: step #1
Hi Guix! Ludovic Courtès wrote: > --8<---cut here---start->8--- > If you want to hack Guix itself, it is recommended to use the latest > version from the Git repository: > > git clone https://git.savannah.gnu.org/git/guix.git > >How do you ensure that you obtained a genuine copy of the repository? > Guix itself provides a tool to “authenticate” your checkout, but you > must first make sure this tool is genuine in order to “bootstrap” the > trust chain. To do that, run: > > git verify-commit `git log --format=%H build-aux/git-authenticate.scm` > >The output must look something like: > > gpg: Signature made Fri 27 Dec 2019 01:27:41 PM CET > gpg:using RSA key > 3CE464558A84FDC69DB40CFB090B11993D9AEBB5 > ... > gpg: Signature made Fri 27 Dec 2019 01:25:22 PM CET > gpg:using RSA key > 3CE464558A84FDC69DB40CFB090B11993D9AEBB5 > ... > > ... meaning that changes to this file are all signed with key > ‘3CE464558A84FDC69DB40CFB090B11993D9AEBB5’ (you may need to fetch this > key from a key server, if you have not done it yet). > >From there on, you can authenticate all the commits included in your > checkout by running: > > make authenticate > >The first run takes a couple of minutes, but subsequent runs are > faster. > > Note: You are advised to run ‘make authenticate’ after every ‘git > pull’ invocation. This ensures you keep receiving valid changes to > the repository > --8<---cut here---end--->8--- Sadly, these instructions don't work from a fresh clone. There is only Makefile.am and no Makefile itself, so you get $ make authenticate make: *** No rule to make target 'authenticate'. Stop. Moreover, I don't think running 'make authenticate' after 'git pull' would really work -- after you pulled, git-authenticate could've been modified, so the verify-commit you did earlier doesn't apply anymore. There's also the issue of trusting pre-inst-env, which is used to run the verification. Should that be passed to 'git log --format=%H' next to git-authenticate.scm? This also applies to any scripts you use to drive this process, like the Makefile. Regards, Kuba
bug#38836: guix refresh: Too many open files
I regularly run this command: ./pre-inst-env guix refresh -t cran,bioconductor -u This makes a lot of HTTP requests to check for updates. It often aborts with this error before it can finish checking for updates of all packages: guix refresh: error: open-file: Too many open files: "/home/rekado/.cache/guix/http/EXpQeEGkSNjRNVeWpGMNV8ENjJfhl2vugsTbrdaTshg=" -- Ricardo
bug#38838: 'whatis' doesn't work
The 'whatis' utility from man-db 2.9.0 doesn't work for me. This includes both my user profile and 'guix environment's. 'apropos' works, so the man database is present and working. $ guix environment --pure --ad-hoc man-db man-pages [env] $ apropos memcpy memcpy (3) - copy memory area wmemcpy (3) - copy an array of wide-characters [env] $ whatis memcpy memcpy: nothing appropriate. Regards, Jakub Kądziołka
