Kleene, Steven (kleenesj) composed on 2022-12-02 02:41 (UTC):
...
Your old Xorg.0.logs differ significantly from your current ones, and my
own on a similar Intel GPU. In what follows, the current ones and the old
ones omit everything between the first and last lines:
*
[ 2059.607] (II)
On Thursday, December 1, 2022, 10:12:21 PM GMT+1, Andrew M.A. Cater
wrote:
On Thu, Dec 01, 2022 at 08:43:29PM +, L Dimov wrote:
> On Thursday, December 1, 2022 at 03:28:33 PM EST, Andrew M.A. Cater
> wrote:
>
> On Thu, Dec 01, 2022 at 06:58:11PM +, L Dimov wrote:
>
Kleene, Steven (kleenesj) composed on 2022-12-02 02:41 (UTC):
See if adding the following file helps:
---
# cat /etc/X11/xorg.conf.d/25-intelExtra.conf
Section "Device"
Identifier "IntelKludges"
Option "ReprobeOutputs" "on" # default off
EndSection
---
"(WW) VGA
Le 02/12/2022 à 12:19, Pierre Couderc a écrit :
Merci, en fait , je n'en suis pas encore là, j'en suis à comprendre
pouruqoi mon interface que je trouve dans lspci, n'est pas listé par
iwlist...
Je prefere ne pas utiliser network-manager mais seulement wpa-supplicant.
Mais il fuat que
On Sat, Dec 3, 2022 at 12:42 PM Alain D D Williams wrote:
>
> I am running Debian 10 (buster). I generated a new key that I wanted to
> upload,
> but it fails:
>
> $ gpg --send-keys 0xBA366B977C06BAF7
> gpg: sending key 0xBA366B977C06BAF7 to hkps://keys.openpgp.org
> gpg: keyserver send failed:
On Sat, 2022-12-03 at 12:09 -0700, Casey Deccio wrote:
>
> > On Dec 3, 2022, at 9:22 AM, Andre Rodier wrote:
> >
> > > ssh -o VerifyHostKeyDNS=yes main.homebox.world
> >
> > Yes, this is the default option in my ssh/config file.
> >
> > I tried on the command line as well, but same result:
>
On December 1, 2022 9:41 PM, I wrote:
>> Out of the blue today, my usual screen resolution (1920x1200) became
>> unavailable. ...
On December 3, 2022 1:23 PM, Felix Miata wrote:
> This and http://paste.debian.net/1262700/ are the same log created Sat Jul 3
> 16:37:19 2021 using kernel
> On Dec 3, 2022, at 9:22 AM, Andre Rodier wrote:
>
>> ssh -o VerifyHostKeyDNS=yes main.homebox.world
>
> Yes, this is the default option in my ssh/config file.
>
> I tried on the command line as well, but same result:
It could be that your default DNS resolver is not validating. ssh
On Sat 03 Dec 2022 at 08:19:48 (+0100), Loïc Grenié wrote:
> On Sat Dec, 3, 2022 at 04:03, David Wright wrote:
> > Yes, hence my comment on potential interactions between different
> > packages. The OP mentioned udev, but in their OP they talked about
> > manually restarting systemd services. I
Kleene, Steven (kleenesj) composed on 2022-12-03 14:15 (UTC):
> For Xorg.0.log,
> http://paste.debian.net/1262735/
This and http://paste.debian.net/1262700/ are the same log created
Sat Jul 3 16:37:19 2021 using kernel 4.19.0-17-amd64. If these are from
/var/log/
then look in
I am running Debian 10 (buster). I generated a new key that I wanted to upload,
but it fails:
$ gpg --send-keys 0xBA366B977C06BAF7
gpg: sending key 0xBA366B977C06BAF7 to hkps://keys.openpgp.org
gpg: keyserver send failed: Server indicated a failure
gpg: keyserver send failed: Server indicated a
On Sat, 2022-12-03 at 09:19 -0700, Casey Deccio wrote:
> ssh -o VerifyHostKeyDNS=yes main.homebox.world
Yes, this is the default option in my ssh/config file.
I tried on the command line as well, but same result:
> ssh -o VerifyHostKeyDNS=yes main.homebox.world
> The authenticity of host
> On Dec 3, 2022, at 8:30 AM, Andre Rodier wrote:
>
> Where am I making a mistake, please ?
The DNSSEC looks fine. That is, there is a secure chain from the root to the
SSHFP record (see below).
Have you tried adding the VerifyHostKeyDNS=yes option?
ssh -o VerifyHostKeyDNS=yes
On Sat 03 Dec 2022 at 10:37:50 (+), Ottavio Caruso wrote:
> $ uname -a
> Linux t440 6.0.0-0.deb11.2-amd64 #1 SMP PREEMPT_DYNAMIC Debian
> 6.0.3-1~bpo11+1 (2022-10-29) x86_64 GNU/Linux
>
> I have two scripts that enable/disable touchpad that I mapped to some
> keyboard shortcuts:
>
> $ cat
On Sat, 2022-12-03 at 15:48 +, John Scott wrote:
> > Where am I making a mistake, please ?
>
> I think I know the problem. On the client machine, by default glibc
> doesn't indicate to applications that DNS records were signed via
> DNSSEC. This is because, how is glibc to know whether the
> Where am I making a mistake, please ?
I think I know the problem. On the client machine, by default glibc doesn't
indicate to applications that DNS records were signed via DNSSEC. This is
because, how is glibc to know whether the DNS servers it's getting its records
from is supposed to be
Hello, all.
I have implemented DNSSEC successfully (apparently) on a test box
(using PowerDNS, btw). We can see the test here:
https://dnssec-debugger.verisignlabs.com/homebox.world
I have set my SSHFP records correctly (I think):
> dig +dnssec -t SSHFP main.homebox.world @1.1.1.1
On December 1, 2022 9:41 PM, I wrote:
>>> Out of the blue today, my usual screen resolution (1920x1200) became
>>> unavailable. ...
On December 2, 2022 10:12 AM, Felix Miata wrote:
>> ... run
>> inxi -U
>> to upgrade, and post here output from within an X terminal:
>> inxi -GSaz
* Ottavio Caruso [22-12/03=Sa 10:37 +]:
> $ uname -a
> Linux t440 6.0.0-0.deb11.2-amd64 #1 SMP PREEMPT_DYNAMIC Debian
> 6.0.3-1~bpo11+1 (2022-10-29) x86_64 GNU/Linux
>
> I have two scripts that enable/disable touchpad
> [running the commands]
> xinput enable "SynPS/2 Synaptics TouchPad"
>
19 matches
Mail list logo
