Adam Weremczuk writes:
> The container was running like that for several months until this morning
> when its core service (dhcp) started failing.
Just a wild guess, but do you know what caused dhcp to fail? Was it too
little memory?
>
> I logged in to investigate and noticed 100% of swap be
Haines Brown writes:
> After installing base system (without DE) I install xorg and then
> fluxbox.
>
> Fluxbox gets installed, but no ~/.fluxbox directory shows up.
I haven’t used fluxbox for many years, but I don’t use a DE either. For
what it’s worth, I use i3, which also does not place a
Haines Brown writes:
> On Sat, Apr 02, 2022 at 02:52:59PM +0200, Nathanael Schweers wrote:
>> That’s how most window managers are designed to work. I certainly do
>> something similar with i3.
>
> Nathan I copied over the .fluxbox hierarchy. It turned out this can be
>
David Christensen writes:
> I use the d-i at the simplest level I can (e.g. text "Install" mode from the
> main menu). From what I have observed, d-i detects if the host is using BIOS
> or
> UEFI, and chooses MBR or GPT partitioning accordingly. Assume the host
> firmware
> can operate as UEF
Hello people,
I recently installed Debian Bullseye on my desktop machine, having
previously used Debian sid.
So far it all went well. Yet two days ago, ansible suddenly
reported the following message when attempting to use either the
`apt` or `package` builtin.
fatal: [schweers-pc]: FAILE
> It doesn't look like this exact problem is known at
> https://github.com/search?q=org%3Aansible+X509_V_FLAG_CB_ISSUER_CHECK+is%3Aissue&type=issues,
> but there are a few suggestions among the matching bugs.
> One suggestion appears to be that your python module "cryptography" is too
> new for
> We need to know the versions of the (relevant) packages on your system.
Sorry, I have the ones currently in bullseye. I’m afraid I am not at
said machine at the moment and won’t be for the weekend. I’ll post more
next week.
> BTW you started this thread with "I recently installed Debian Bull
> We also need to know what happened between the "I recently installed Debian"
> statement and your "suddenly 2 days ago Ansible..." statement.
I’m not quite sure I follow. I put that in my message to indicate that
it was running fine on sid. It still is, in fact, on another machine.
Between i
David Wright writes:
On Fri 25 Nov 2022 at 15:13:48 (+0100), Nathanael Schweers
wrote:
> We need to know the versions of the (relevant) packages on
> your system.
Sorry, I have the ones currently in bullseye. I’m afraid I am
not at
said machine at the moment and won’t be for the w
the system
upgrade, I still have access to ~/.gnupg as it was before the upgrade,
should that be necessary.
Does anyone have an idea what the problem might be?
Best regards,
Nathanael Schweers
dir=CVS --exclude-dir=.git --exclude-dir=.hg
--exclude-dir=.svn -i gpg
Also the socket file seems fine:
$ ls -l /run/user/1000/gnupg/S.gpg-agent
srw--- 1 schweers schweers 0 Apr 6 08:54
/run/user/1000/gnupg/S.gpg-agent
On 04/06/2017 10:15 AM, Nicolas George wrote:
> Le septidi 17
Nicolas George writes:
> Le septidi 17 germinal, an CCXXV, Nathanael Schweers a écrit :
>> connect(6, {sa_family=AF_UNIX,
>> sun_path="/run/user/1000/gnupg/S.gpg-agent"}, 34) = 0
>> read(6,
>>
>> It seems to me that strace shouldn’t just stop in the mi
estion:
http://dustymabe.com/2015/07/06/encrypting-more-boot-joins-the-party/
Regards,
Nathanael Schweers
Pascal Hambourg writes:
> The version of GRUB included in Jessie at least can handle an encrypted
> /boot. However the Debian installer does not handle this case correctly.
> You must add the following line in /etc/default/grub in order for
> grub-install to install the core image with crypto
14 matches
Mail list logo
