Am 20.04.23 um 06:03 schrieb Vagrant Cascadian:
On 2023-04-19, Felix Lechner via wrote:
Given the broad popularity of LUKS full-disk encryption among our
fellow Guix users, I thought the community might appreciate reading
about potentially weak key-derivation functions in older LUKS
installation
Hi,
I installed flameshot, but it doesn’t open.
I tried it beforehand with guix shell flameshot and it worked not
completely, but somehow.
But now, after installation it doesn’t open at all.
Do you have guix system or are you on an other distro?
Am 17.04.23 um 20:32 schrieb Sergiu Ivanov:
Hi
Hi Gottfried,
Gottfried [2023-04-20T12:11:16+0200]:
> [[PGP Signed Part:Undecided]]
> Hi,
>
> I installed flameshot, but it doesn’t open.
> I tried it beforehand with guix shell flameshot and it worked not
> completely, but somehow.
> But now, after installation it doesn’t open at all.
When run
Hi,
thanks for help.
it works,
When run without any command line arguments, Flameshot installs a tray
icon, near the volume icon and the Network Manager icon in my case.
To make a screenshot, I click on the icon, which dims the screen and
allows me to draw a rectangle to show the region I wan
Hi Denis,
Denis 'GNUtoo' Carikli writes:
> On Tue, 18 Apr 2023 09:03:51 +0200
> Andreas Enge wrote:
>
>> So in a first step, if I am limited to sudo, I do "sudo su -" to
>> become root.
> Thanks a lot, that seems to work: I don't have the same errors anymore
> (I've other errors related to i686
Hello,
Saku Laesvuori writes:
> Running `guix system image image-minimal.scm` fails with the following
> build log:
>
> ```build log for partition.img.drv
> copying 340 store items | [progress bar animation]
> registering 337 items | [progress bar animation, fails before end]
> Backtrace:
> In i
Hi,
gfp@Tuxedo ~$ ps $(ps -p $(pidof Xorg) -o ppid=)
PID TTY STAT TIME COMMAND
1114 tty8 Ssl+ 0:00
/gnu/store/58hc6rh72z3r6zqazmavjnwbcyy6gkps-gdm-42.0/libexec/gd
it shows gdm-42.0 as my display manager
.
Hi Kyle,
Kyle Andrews writes:
> Dear Guix,
>
> The (many) shell scripts in my software depend on bashisms. In the
> code right now I typically use /usr/bin/env bash since I had read that
> was the most portable way of referencing a shell. However, I really
> don't think I have a good handle on w
Gottfried [2023-04-20T13:28:05+0200]:
> [[PGP Signed Part:Undecided]]
> Hi,
>
> thanks for help.
>
> it works,
Great news!
> Near the volume icon there appear two icons, both are flameshot.
> I didn’t see those icons earlier, because they are in grey colour
> without anything on them, so they do
On 4/20/23 05:39, Attila Lendvai wrote:
While recent grub2 finally has limited support for luks2, it only
supports the weaker KDF (key derivation function) (PBKDF2?), as I
understand it, though would be happy to be proven wrong!
i have just spent half an hour reading the linked PR's and patch
Hi,
Am 20.04.23 um 14:52 schrieb Gottfried:
Hi,
gfp@Tuxedo ~$ ps $(ps -p $(pidof Xorg) -o ppid=)
PID TTY STAT TIME COMMAND
1114 tty8 Ssl+ 0:00
/gnu/store/58hc6rh72z3r6zqazmavjnwbcyy6gkps-gdm-42.0/libexec/gd
it shows gdm-42.0 as my display manager
.
Small correction to the mail I just sent:
Instead of
env - bash -l
you might need to use
env - $(which bash) -l
It would probably be doable to run a very small Linux EFI stub as a
bootloader on x86, that way you can side-step the lacking grub support.
Integrating it with Guix would surely be a bit harder though.
kiasoc5 writes:
> Argon2 support was slated to be in the next release of Grub (2.12) but
> ap
Hey :)
While slightly of topic, I have to wonder about:
On 2023-04-19 06:18:33 +, Kyle Andrews wrote:
> The main bashism I use is default environment variables ${FOO:-bar}.
I'm pretty sure that is just regular POSIX compatible syntax no? At least if I
read [0] correctly.
0:
https://pubs.op
"(" writes:
> Kyle writes:
>> The context is that my R package calls a bunch of shell scripts stored
>> inside it. I am getting errors about
>> /usr/bin/env not being available (e.g. bad interpreter: no such file or
>> directory), so was thinking that their
>> shebangs were not getting patch
Kyle Andrews writes:
> You are right about this. I created a minimal reproducible R package with a
> basic shell script included and the shebangs were patched. I'm still trying
> to figure out the actual cause of my shell errors.
Perhaps try using ``shellcheck''.
16 matches
Mail list logo