bug#43013: System reconfigure: expection reached when executing `start` on "file-system-/sys/kernel/debug" // and an unrelated "nouveau"-bug?

2020-08-24 Thread o . rojon
Hello everyone, I'm recently running into problems updating my system. I had not reconfigured for a while (1~2 months) and now, when I reconfigure, I get the error message below. At first I thought it might be related to a specific guix commit, but I have now tried four times over the course

bug#41715: The program '/gnu/store/foobar/compute-guix-derivation' failed to compute the derivation for guix

2020-06-11 Thread o . rojon
Hej Ludo, crazy, I wouldn't have thought it would go as deep as gdb as quickly ;-) I followed the steps you mentioned, the results you find here: https://www.mediafire.com/file/g5yz8f3pput8f3w/gdb-output/file . The only part I omitted from the gdb output is the first lines mentioned the

bug#41715: The program '/gnu/store/foobar/compute-guix-derivation' failed to compute the derivation for guix

2020-06-08 Thread o . rojon
Hi Ludo, here is the log uploaded on mediafire: http://www.mediafire.com/file/ldqoi68y88rzrn9/log.bz2/file (note that if you can recommend another uploading service, feel free to!) Since the log is in german, let me specify at least two of the recurrent phrases in english: "Datei oder

bug#41715: The program '/gnu/store/foobar/compute-guix-derivation' failed to compute the derivation for guix

2020-06-05 Thread o . rojon
Hi Ludo, guix pull --roll-back did not solve the issue. The only thing I believe to have changed is the "host version" portion of the error message. 'which guix' actually points to ~/.configu/guix/current/bin/guix. Should this command yield a different value? I have actually not done

bug#41715: The program '/gnu/store/foobar/compute-guix-derivation' failed to compute the derivation for guix

2020-06-05 Thread o . rojon
Just to follow up: a roll-back does NOT solve the issue. What I have tried: 1) roll-back via guix system roll-back (to the generation that was created upon system installation) 2) roll-back via guix package --roll-back (same) 3) (1) + (2) combined 4) boot into the generation created upon

bug#41715: The program '/gnu/store/foobar/compute-guix-derivation' failed to compute the derivation for guix

2020-06-05 Thread o . rojon
Hej Ludo, thanks for the quick reply! I just tried to pull again and yielded the same result. Actually, no, there is nothing above these lines. Yet, let me copy/paste the whole command in/output. It is in german but I guess the steps are so common by now that it shouldnt be a problem to

bug#41715: The program '/gnu/store/foobar/compute-guix-derivation' failed to compute the derivation for guix

2020-06-04 Thread o . rojon
Hello everyone, on a freshly installed and reconfigured machine, I receive the following error: # guix pull: error: You found a bug: the program '/gnu/store/kpxami25fi3mrxb37sfbbx2s366chpk5-compute-guix-derivation' # failed to compute the derivation for Guix (version:

bug#41121: (Keyboard-layout) form does not work "across the board"

2020-05-07 Thread o . rojon
Hej guys, so I hope this actually is a bug and not something not yet implemented or a misunderstanding on my part. In the process of changing my login manager to slim (over gdm), I noticed that the (keyboard-layout ...) form does not work the same way in the

bug#39527: A new information on LXQt DE not "logging in"

2020-05-07 Thread o . rojon
Hello guys, I have come to realise something which might be of interest, but which might also be something which is well known to you. When trying to launch LXQt from the GDM login/session manager, the screen just went blank and nothing happened. This is why I assumed "it simply doesnt

bug#39527: Cannot log into LXQt DE

2020-02-09 Thread o . rojon
Hello everyone, as the title says, I am (no longer) able to log into the LXQt DE. When I first installed it system-wide, I was able to log in. Later, I deleted it from my os-config and reconfigured. Later again, I re-added it to my os config and reconfigured. Now I have tried a couple of this

bug#37897: Bug: Resetting locale settings

2019-11-14 Thread o . rojon
Hello ludo, hey guys, here you go. I took the liberty to anonymize and to skip the package modules and packages sections. I realised that when I dont specify WHICH KIND of german keyboard layout I have, the problem does not occur. That is, if I use the (keyboard-layout (keyboard-layout

bug#37897: Bug: Resetting locale settings

2019-10-26 Thread o . rojon
Hello Ludo, maybe I have been a bit unprecise in my wording, Im rather new to that level of configurability. So I was talking about the keyboard layout all along. Not only was my locale set to "de_DE.utf8", but my keyboard configuration is set to "de-latin1-nodeadkeys". Interestingly, the

bug#37896: setxkbmap has worked

2019-10-23 Thread o . rojon
Hello everyone, just a quickie: I noticed that even though loadkeys doesnt work, setxkbmap does. Sorry, just read the setxkbmap and figured how to use it properly. Yet, this doesnt explain why, on each startup, my keyboard configuration seems to be set to the us layout, even though I have

bug#37897: Bug: Resetting locale settings

2019-10-23 Thread o . rojon
Hello guix, I believe that a locale-related bug has slipped in somewhere in the last two-three weeks. During installation and in my configuration file, I have specified de_DE specified as locale, which should translate to a german keyboard layout. But since said two-three weeks, I startup

bug#37896: Bug: Cannot use `guix pull`

2019-10-23 Thread o . rojon
Hello everyone, after some time of not upgrading, I have been unable to guix pull and thus to upgrade my system. Find below what has occurred after I ran `guix pull` hapster@guixter ~$ guix pull Kanal „guix-gaming-games“ wird vom Git-Repository auf