Re: how do I stop FF from jumping workspaces when I click on a linkin t-bird

[Tom Dial]

On 1/8/23 17:08, gene heskett wrote:

On 1/8/23 13:42, David Wright wrote:

On Sun 08 Jan 2023 at 12:40:05 (-0500), gene heskett wrote:

it is most inconvenient to have it jump workspaces and open the link
on top of the tbird screen.


You might try Edit → Settings, and check the
   Open links in tabs instead of new windows
box under Tabs.


It is in the Firefox settings, in the General section under "Tabs."

Regards,
Tom Dial



not found in settings of the version I have in an uptodate bullseye. 102.6.0 
(64-bit) (tbird)
And that option is already set in firefox.


Cheers,
David.


Thanks David.

Cheers, Gene Heskett.

Why Debian packaging structure is so difficult

[Sadhu Santh]

Hi,

I am hosting a local Debian mirror for my LAN. This helps in low 
internet bandwidth use.


I keep only the required distributions (past five years and testing 
release).


Compared to other distributions such ArchLinux/RockyLinux (single line 
Rsync can do the job), the partial mirroring over Rsync in Debian is a 
complex process.


I use ftpsync, which can run on any Linux distribution.

Is there any simple set of Rsync commands to sync a particular version 
of the platform (e.g. x86) of Debian? If not, why the upstream structure 
is not made simpler?


Thanks for your guidance on the matter.


Regards,

SS

Re: How can I check (and run) if an *.exe is a DOS or a Windowsprogram?

[gene heskett]

On 1/8/23 16:04, Roy J. Tellason, Sr. wrote:

On Saturday 07 January 2023 03:27:31 pm gene heskett wrote:

That DOS was not the least bit
entertaining. :(> That was the best reason to skip it, I went from
amigados 3.9 to rh5.0, never regretted missing the DOS experience, I got
my fill of it as the CE at a tv station back in the day.



I remember getting a mailing (don't know how I ended up on that mailing list) 
where they wanted to sell me a development kit for windoze,  which at that time 
hadn't even been released yet,  or if it had it was a very buggy and clunky 
preliminary version.

They wanted me to pay something like $3000.00 for the privilege of developing 
software for their new platform.

I found this most entertaining,  and laughed like hell before I got around to 
tossing that mailing in the trash.

At the time I got a similar msg was only a week or 2 after I'd been 
called a pie-rat by somebody in the support line in Redmond. My laugh 
was as evil as I could manage as I hit the delete key.


The audacity of that outfit and its owner knows no bounds.
Now he & A.F.wants to kill off 98% of us.

Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: how do I stop FF from jumping workspaces when I click on a linkin t-bird

[gene heskett]

On 1/8/23 14:12, Andreas Ronnquist wrote:

On Sun, 8 Jan 2023 12:40:05 -0500,
gene heskett wrote:


it is most inconvenient to have it jump workspaces and open the link on top of 
the tbird screen.



Which desktop environment are you on? - I think I might have seen
somewhere that you are on Xfce (but I am not sure) -

in that case - see

https://docs.xfce.org/xfce/xfwm4/faq#firefox_jumps_between_workspaces_why

which might be the cause of your problems. Change that setting to something you 
want.

The suggested query line in that link generated errors. but nano fixed 
the file. Do I have to reboot? Logging out reboots it. Or is there some 
other way to bring it into effect.


-- Andreas Rönnquist
mailingli...@gusnan.se
andr...@ronnquist.net


Thank you Andreas.

.


Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: how do I stop FF from jumping workspaces when I click on a linkin t-bird

[gene heskett]

On 1/8/23 13:42, David Wright wrote:

On Sun 08 Jan 2023 at 12:40:05 (-0500), gene heskett wrote:

it is most inconvenient to have it jump workspaces and open the link
on top of the tbird screen.


You might try Edit → Settings, and check the
   Open links in tabs instead of new windows
box under Tabs.


not found in settings of the version I have in an uptodate bullseye. 
102.6.0 (64-bit) (tbird)

And that option is already set in firefox.


Cheers,
David.


Thanks David.

Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: How can I check (and run) if an *.exe is a DOS or a Windows program?

[Jeffrey Walton]

On Sat, Jan 7, 2023 at 6:43 PM Miguel A. Vallejo  wrote:
>
> If I remember correctly, all Windows EXE have an string saying:
>
> This program cannot be run in DOS mode.

A couple of small nits...

They are called PE/PE+ programs. The string "This program cannot be
run in DOS mode" is called the MS-DOS Stub. It may or may not be
present. Most of the time it is present, but it is possible to build
an exe using the assembler without the message.

The first part of a PE program usually includes a DOS 2.0 header. The
DOS header allows the program to display the stub message under DOS
and exit.

Also see https://learn.microsoft.com/en-us/windows/win32/debug/pe-format.

Jeff

Re: How can I check (and run) if an *.exe is a DOS or a Windowsprogram?

[Roy J. Tellason, Sr.]

On Saturday 07 January 2023 03:27:31 pm gene heskett wrote:
> That DOS was not the least bit 
> entertaining. :(> That was the best reason to skip it, I went from 
> amigados 3.9 to rh5.0, never regretted missing the DOS experience, I got 
> my fill of it as the CE at a tv station back in the day.
> 

I remember getting a mailing (don't know how I ended up on that mailing list) 
where they wanted to sell me a development kit for windoze,  which at that time 
hadn't even been released yet,  or if it had it was a very buggy and clunky 
preliminary version.

They wanted me to pay something like $3000.00 for the privilege of developing 
software for their new platform.

I found this most entertaining,  and laughed like hell before I got around to 
tossing that mailing in the trash.

-- 
Member of the toughest, meanest, deadliest, most unrelenting -- and
ablest -- form of life in this section of space,  a critter that can
be killed but can't be tamed.  --Robert A. Heinlein, "The Puppet Masters"
-
Information is more dangerous than cannon to a society ruled by lies. --James 
M Dakin

Re: SID Xorg Erreur Segmentation

[Basile Starynkevitch]

On 08/01/2023 19:49, Orion wrote:

merci pour vos réponses!
je pense que didier gaumet qui a la meilleure piste, ça peut venir de 
mesa,

j'ai cherché sur apt-list-bug mais c'est pas concluant,
apparemment apt ne garde pas mes réponses suite à ses mises en garde.
lspci
00:00.0 Host bridge: Intel Corporation 8th Gen Core Processor Host 
Bridge/DRAM Registers (rev 07)
00:01.0 PCI bridge: Intel Corporation 6th-10th Gen Core Processor PCIe 
Controller (x16) (rev 07)
00:02.0 VGA compatible controller: Intel Corporation CoffeeLake-S GT2 
[UHD Graphics 630]
00:14.0 USB controller: Intel Corporation 200 Series/Z370 Chipset 
Family USB 3.0 xHCI Controller
00:16.0 Communication controller: Intel Corporation 200 Series PCH 
CSME HECI #1
00:17.0 SATA controller: Intel Corporation 200 Series PCH SATA 
controller [AHCI mode]
00:1b.0 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root 
Port #17 (rev f0)
00:1c.0 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root 
Port #1 (rev f0)
00:1c.3 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root 
Port #4 (rev f0)
00:1d.0 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root 
Port #9 (rev f0)
00:1d.4 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root 
Port #13 (rev f0)

00:1f.0 ISA bridge: Intel Corporation Z370 Chipset LPC/eSPI Controller
00:1f.2 Memory controller: Intel Corporation 200 Series/Z370 Chipset 
Family Power Management Controller

00:1f.3 Audio device: Intel Corporation 200 Series PCH HD Audio
00:1f.4 SMBus: Intel Corporation 200 Series/Z370 Chipset Family SMBus 
Controller
01:00.0 VGA compatible controller: *NVIDIA Corporation TU106 [GeForce 
RTX 2070 Rev. A]* (rev a1)
01:00.1 Audio device: NVIDIA Corporation TU106 High Definition Audio 
Controller (rev a1)
01:00.2 USB controller: NVIDIA Corporation TU106 USB 3.1 Host 
Controller (rev a1)
01:00.3 Serial bus controller: NVIDIA Corporation TU106 USB Type-C 
UCSI Controller (rev a1)
04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)




Donc une carte  NVIDIA récente: je suggère alors soit d'utiliser Nouveau 
(pour les libristes convaincus) via


aptitude install libdrm-nouveau2 nouveau-firmware xserver-xorg-video-nouveau

soit d'accepter le compromis de télécharger puis d'installer un pilote 
NVIDIA propriétaire: https://www.nvidia.com/fr-fr/drivers/unix/ donc en 
janvier 2023 
https://www.nvidia.fr/content/DriverDownloads/confirmation.php?url=/XFree86/Linux-x86_64/525.78.01/NVIDIA-Linux-x86_64-525.78.01.run=fr=TITAN 



et il faudra bien sûr rebooter, et préalablement avoir installer le code 
source du noyau (nécessaire à Nvidia, si j'ai bonne mémoire) ou au moins 
les paquets linux-headers


--
Basile Starynkevitch
(only mine opinions / les opinions sont miennes uniquement)
92340 Bourg-la-Reine, France
web page: starynkevitch.net/Basile/

Re: SID Xorg Erreur Segmentation

[Klaus Becker]

Am 08/01/2023 um 19:49 schrieb Orion:

merci pour vos réponses!




J'ai un peu de mal à m'en souvenir, mais il me semble avoir eu le même 
problème sous unstable il y a qq semaines, et la solution était de

revenir à une version antérieure de xorg.

Mais le problème a peut-être était résolu depuis, au moins sous 
unstable. Il me semble qu'il y avait un report de bug, ça doit se 
trouver facilement.


J'ai

~$ apt-cache policy xserver-xorg
xserver-xorg:
  Installé: 1:7.7+23
  Candidat: 1:7.7+23
  Versionstabelle:
 *** 1:7.7+23 500
500 http://ftp.halifax.rwth-aachen.de/debian unstable/main 
amd64 Packages

100 /var/lib/dpkg/status

bye
Klaus

Re: how do I stop FF from jumping workspaces when I click on a link in t-bird

[Andreas Ronnquist]

On Sun, 8 Jan 2023 12:40:05 -0500,
gene heskett wrote:

>it is most inconvenient to have it jump workspaces and open the link on top of 
>the tbird screen.
>

Which desktop environment are you on? - I think I might have seen
somewhere that you are on Xfce (but I am not sure) -

in that case - see

https://docs.xfce.org/xfce/xfwm4/faq#firefox_jumps_between_workspaces_why

which might be the cause of your problems. Change that setting to something you 
want.


-- Andreas Rönnquist
mailingli...@gusnan.se
andr...@ronnquist.net

Re: Disable systemd RDRAND usage

[Greg Wooledge]

On Sun, Jan 08, 2023 at 07:06:03PM +0100, 
operation.privacyenforcem...@secure.mailbox.org wrote:
> Hello,
> 
> I want to set SYSTEMD_RDRAND=0 as implemented here
> https://github.com/systemd/systemd/issues/17112
> 
> How can this be done on Debian and how can this be tested?

 claims that all internal
use of RDRAND by systemd has been removed as of version 251.

Bullseye has version 247, but bullseye-backports appears to have 251.
See 

and the Debian backports instructions at
.

Re: SID Xorg Erreur Segmentation

[Orion]

merci pour vos réponses!
je pense que didier gaumet qui a la meilleure piste, ça peut venir de mesa,
j'ai cherché sur apt-list-bug mais c'est pas concluant,
apparemment apt ne garde pas mes réponses suite à ses mises en garde.
mon xorg log :

X.Org X Server 1.21.1.6
X Protocol Version 11, Revision 0
[79.378] Current Operating System: Linux debian 6.0.0-6-amd64 #1 SMP
PREEMPT_DYNAMIC Debian 6.0.12-1 (2022-12-09) x86_64
[79.378] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.0.0-6-amd64
root=UUID=1083d7f2-5605-4c39-b74e-987011602c8e ro single
[79.380] xorg-server 2:21.1.6-1 (https://www.debian.org/support)
[79.381] Current version of pixman: 0.42.2
[79.384] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[79.384] Markers: (--) probed, (**) from config file, (==) default
setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[79.389] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Jan  8
16:25:51 2023
[79.390] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[79.390] (==) No Layout section.  Using the first Screen section.
[79.390] (==) No screen section available. Using defaults.
[79.390] (**) |-->Screen "Default Screen Section" (0)
[79.390] (**) |   |-->Monitor ""
[79.390] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[79.390] (==) Automatically adding devices
[79.390] (==) Automatically enabling devices
[79.390] (==) Automatically adding GPU devices
[79.390] (==) Automatically binding GPU devices
[79.390] (==) Max clients allowed: 256, resource mask: 0x1f
[79.390] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not
exist.
[79.390] Entry deleted from font path.
[79.390] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins
[79.390] (==) ModulePath set to "/usr/lib/xorg/modules"
[79.390] (II) The server relies on udev to provide the list of input
devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[79.390] (II) Loader magic: 0x556d58f82f00
[79.390] (II) Module ABI versions:
[79.390] X.Org ANSI C Emulation: 0.4
[79.390] X.Org Video Driver: 25.2
[79.390] X.Org XInput driver : 24.4
[79.390] X.Org Server Extension : 10.0
[79.390] (EE) dbus-core: error connecting to system bus:
org.freedesktop.DBus.Error.FileNotFound (Failed to connect to socket
/run/dbus/system_bus_socket: No such file or directory)
[79.390] (--) using VT number 2

[79.390] (II) systemd-logind: logind integration requires -keeptty and
-keeptty was not provided, disabling logind integration
[79.391] (II) xfree86: Adding drm device (/dev/dri/card0)
[79.391] (II) Platform probe for
/sys/devices/pci:00/:00:01.0/:01:00.0/drm/card0
[79.392] (II) xfree86: Adding drm device (/dev/dri/card1)
[79.392] (II) Platform probe for
/sys/devices/pci:00/:00:02.0/drm/card1
[79.399] (--) PCI:*(0@0:2:0) 8086:3e92:1043:8694 rev 0, Mem @
0xf500/16777216, 0xd000/268435456, I/O @ 0xf000/64, BIOS @
0x/131072
[79.399] (--) PCI: (1@0:0:0) 10de:1f07:1043:866d rev 161, Mem @
0xf600/16777216, 0xe000/268435456, 0xf000/33554432, I/O @
0xe000/128, BIOS @ 0x/524288
[79.399] (II) LoadModule: "glx"
[79.399] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[79.400] (II) Module glx: vendor="X.Org Foundation"
[79.400] compiled for 1.21.1.6, module version = 1.0.0
[79.400] ABI class: X.Org Server Extension, version 10.0
[79.466] (==) Matched modesetting as autoconfigured driver 0
[79.466] (==) Matched fbdev as autoconfigured driver 1
[79.466] (==) Matched vesa as autoconfigured driver 2
[79.466] (==) Assigned the driver to the xf86ConfigLayout
[79.466] (II) LoadModule: "modesetting"
[79.466] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[79.466] (II) Module modesetting: vendor="X.Org Foundation"
[79.466]* compiled for 1.21.1.6, module version = 1.21.1*
[79.466] Module class: X.Org Video Driver
[79.466] *ABI class: X.Org Video Driver, version 25.2*
[79.466] (II) LoadModule: "fbdev"
[79.467] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[79.467] (II) Module fbdev: vendor="X.Org Foundation"
[79.467] compiled for 1.21.1.3, module version = 0.5.0
[79.467] Module class: X.Org Video Driver
[79.467] ABI class: X.Org Video Driver, version 25.2
[79.467] (II) LoadModule: "vesa"
[79.467] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[79.467] (II) Module vesa: vendor="X.Org Foundation"
[79.467] *compiled for 1.21.1.3, module version = 2.5.0*
[

Re: how do I stop FF from jumping workspaces when I click on a link in t-bird

[David Wright]

On Sun 08 Jan 2023 at 12:40:05 (-0500), gene heskett wrote:
> it is most inconvenient to have it jump workspaces and open the link
> on top of the tbird screen.

You might try Edit → Settings, and check the
  Open links in tabs instead of new windows
box under Tabs.

Cheers,
David.

Disable systemd RDRAND usage

[operation . privacyenforcement]

Hello,

I want to set SYSTEMD_RDRAND=0 as implemented here
https://github.com/systemd/systemd/issues/17112

How can this be done on Debian and how can this be tested?

Best regards
operation privacyenforcement

Re: Bootcamp et Linux ?

[Hugues Larrive]

Bonjour,

Je connais un peu l'affaire, j'avais fait un triple boot osx win debian sur un 
des premier macbook intel pour une amie et un dual boot osx debian il y a 5 ou 
6 ans pour un collègue...

À l'époque (2006) windows ne gérait pas l'efi et encore moins le 
partitionnement GPT qui va avec. Une des fonctionnalité de bootcamp était de 
faire un partitionnement hybride DOS/GPT : techniquement le premier secteur 
d'un disque partitionné en GPT contient une table de partition MSDOS classique 
avec une seule partition de type GPT qui occupe tout le disque, cela afin que 
les outils qui ne supportent pas GPT ne considère pas le disque comme vierge. 
Bootcamp réduisait cette partition (qui pouvait alors être considérée comme un 
genre de slice BSD pour osx, afin de pouvoir créer une partition pour windows à 
la suite dans la table de partition MSDOS. Ce mécanisme était inutile pour 
linux qui gérait déjà EFI et GPT nativement. Bootcamp créait aussi un media 
contenant les drivers nécessaires pour windows, etc. À l'époque on utilisait 
rEFIt pour booter linux. La difficulté pour le triple boot à l'époque c'est que 
les outils linux considéraient la table de partition hybride comme corrompue et 
avaient tendance à la corriger ce qui cassait l'installation de windows si on 
installait windows avant, et que les partitions linux et rEFIt empêchait 
Bootcamp de fonctionner si on faisait dans l'ordre inverse et j'avais dû finir 
ça à l’éditeur hexadécimal...

La 2ème fois le mac de mon collègue était de la génération avec un EFI 32 bits 
ce qui nécessitait de patcher l'iso d'installation de debian pour remplacer son 
EFI 64 bits par un EFI 32 bits.

Quoi qu'il en soit ni le chargeur de macos, ni celui de windows ne sont 
capables de charger un noyau linux donc il est nécessaire d'installer un 
chargeur (lilo ou grub) dans le premier secteur de la partition linux.

Dans la page du wiki concernant tes mac book air, il est expliqué que son 
chargeur ne permet pas le boot sur USB, donc il est nécessaire d'installer un 
autre chargeur depuis mac os
en premier lieu car il n'est pas possible de l'utiliser directement depuis une 
clé USB comme sur les autres modèles et la procédure est donnée. Cette 
procédure concerne rEFIt (ancien nom de rEFInd) mais devrait pouvoir facilement 
s'adapter pour ce dernier.

Si le mac a été mis à jour en Mac OS >= 10.11, il se peut qu'il soit nécessaire 
de désactiver le SIP (system integrity protection) avant de pouvoir effectuer 
des opérations comme celle-ci : démarrer sur la partition de restauration 
(commande + R) au démarrage, lancer le terminal et passer la commande csrutil 
disable.

Une fois rEFI[t|nd] installé, il devrait être facile de booter sur n'importe 
quelle clé USB bootable.

Enfin la page du wiki n'explique pas comment réduire la partition OSX (qui 
n'est pas conservée) et c'est peut-être pour ça, je pense, que tu t'es orienté 
vers bootcamp. Il n'y a pas
d'outils de redimensionnement dans hfsprogs sous linux et bien que parted 
semble en être capable, je ne m'y risquerait pas vu les limitations du support 
hfs+ sous linux (nécessite la désactivation du journal pour le support en 
écriture). Je ne crois pas non plus que cette fonctionnalité soit accessible 
depuis l'Utilitaire disque GUI de macos, elle est pourtant implémenté dans le 
backend diskutil, pour bootcamp justement : c'est la commande diskutil 
resizeVolume. Il me semble que ça fonctionne à chaud, sinon il faudra le faire 
depuis l'environnement de récupération comme pour csrutil. Cette opération sur 
la partition de démarrage de macos casse le boot qu'il est nécessaire de 
rétablir avec la commande bless d'après le manuel, mais je pense qu'on est pas 
concerné si rEFInd a été installé au préalable.



--- Original Message ---
Le samedi 7 janvier 2023 à 23:17, err...@free.fr  a écrit :


> 

> 

> On 1/7/23 18:09, ptilou wrote:
> 

> > Le jeudi 5 janvier 2023 à 18:40:03 UTC+1, Samy (Zaclys) a écrit :
> > 

> > > Le 05/01/2023 à 18:00, ptilou a écrit :
> > > 

> > > > Le jeudi 5 janvier 2023 à 17:10:04 UTC+1, LaFartre a écrit :
> > > > 

> > > > > Le 05/01/2023 à 15:39, ptilou a écrit :
> > > > > 

> > > > > > Je me dis tiens pour quoi ne pas installer Linux Debian via 
> > > > > > Bootcamp, probleme il ne voit pas la cles usb uefi, il dit Mac OS 
> > > > > > X, je ne trouve pas de partition d’installation Windows !
> > > > > 

> > > > > https://fr.wikipedia.org/wiki/Boot_Camp_(logiciel)
> > > > > Ça ne répond pas à la question !
> > > > > Ah pardon, c'est écrit à la ligne 3, excuse-moi de ne pas t'avoir
> > > > > aiguillé, c'est vrai que c'est long à lire.
> > > 

> > > Si jamais tu arrêtes de t'entêter à utiliser Boot Camp, il y a ces pages
> > > fort utiles à lire, mais y arriveras-tu ? Tu vas boire du ptilait avec ça…
> > > 

> > > https://wiki.debian.org/InstallingDebianOn/Apple
> > 

> > Je te remerci, donc je vais utiliser une cles usb pour booter, et je 
> > cherche, un qui sait s’en servir, 

Disable RDRAND RDSEED VAES AES-NI via OPENSSL_ia32cap

[operation . privacyenforcement]

Hello,

I want to disable RDRAND RDSEED VAES AES-NI via OPENSSL_ia32cap.
Which parameters do I need to set in which file to apply the 
configuration system wide? 
https://www.openssl.org/docs/man1.1.1/man3/OPENSSL_ia32cap.html


How can multiple variables applied systemwide and how can this be tested 
after reboot?


Best regards
operation privacyenforcement

how do I stop FF from jumping workspaces when I click on a link in t-bird

[gene heskett]

it is most inconvenient to have it jump workspaces and open the link on 
top of the tbird screen.


Thank you

Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: [OT] coo, was Re: Debian release criteria.

[Curt]

On 2023-01-08, Charlie Gibbs  wrote:
>
> To heck with it, let's just fall back on Allan Sherman's
> description of a dejected man from Mars searching for his
> girlfriend, who's...
>
>  Eight foot two, solid blue
>  Five transistors in each shoe
>  Has anybody seen my gal?
>
>  Lucite nose, rustproof toes
>  And when her antenna glows
>  She's the cutest Martian gal
>
>You know she promised me, recently
>She wouldn't stray
>But came the dawn, she was gone
>Eighteen billion miles away
>
>  Her steering wheel has sex appeal
>  Her evening gown is stainless steel
>  Has anybody seen my gal?
>
>
>  How I miss all the bliss
>  Of her sweet hydraulic kiss
>  Has anybody seen my gal?
>
>  Lovely shape, custom built
>  Squeeze her wrong and she says TILT
>  Has anybody seen my gal?
>
>She does the cutest tricks with her six
>Stereo ears
>When she walks by, spacemen cry
>'Specially when she shifts her gears
>
>  If she's found, run like mad
>  Put her on a launching pad
>  Down at Cape Can-av-er-al
>  And shoot me back my cutie
>  My supersonic beauty
>  Send me back my Martian gal

I don't remember that one. But I do remember:

 Hello Muddah, hello Faddah
 Here I am at Camp Grenada
 Camp is very entertaining
 And they say we'll have some fun if it stops raining...

I don't why, but I get a kick out of that. I personally went to Wally
Moon's Baseball Camp in Covina when I was a kid. Didn't get much rain
there.  In fact, I recall it being quite hot and dusty.

Re: SID Xorg Erreur Segmentation

[didier gaumet]

Le 08/01/2023 à 11:47, Orion a écrit :

Bonjour,

Suite à une mise à jour autour du 31/12, Xorg ne démarre plus, je me 
souviens d'un message d'alerte d'apt list bug lors de la maj parlant 
d'un risque de segmentation error mais je me pensais sous Wayland et non 
concerné.


Quelqu'un a t il peut être vu le message et a un lien vers une solution?

Merci


- Solution? Je ne suis as sûr, à part attendre que le bug soit corrigé 
dans Sid ou réinstaller une version antérieure à condition de ne pas 
avoir purgé (tu peux aussi trouver des versions particulières des 
exécutables sur https://snapshot.debian.org/ )


- le dépistage peut probablement s'effectuer en cherchant (mots clé xorg 
et xserver) les paquets xorg installés sur ton système et en cherchant 
pour chacun d'eux les bugs sur le site https://www.debian.org/Bugs/ . Tu 
devrais pouvoir obtenir en local le même résultat par la commande 
apt-listbugs list paquet_à_vérifier.

Re (2): firefox resource hog

[peter]

From: Stefan Monnier 
Date: Fri, 06 Jan 2023 19:41:16 -0500
> ... (after all, nowadays web browsers are just VMs running 
> Javascript applications downloaded from hundreds of servers around 
> the world).

Thanks Stefan.

JavaScript might be OK for phenomena such as Youtube.

Meticulous and thorough as JavaScript developers are, I'd prefer my 
credit union calculate on their server. Then only HTML or HTML5 for 
customer systems. 
https://en.wikipedia.org/wiki/JavaScript#Security

Regards,  ... P.

- 
mobile: +1 778 951 5147
  VoIP: +1 604 670 0140
https://en.wikibooks.org/wiki/User:PeterEasthope

Re: Web functionality; was Re: Debian release criteria.

[tomas]

On Sun, Jan 08, 2023 at 07:53:11AM -0800, pe...@easthope.ca wrote:
> David & all,
> 
> Earlier from peter,
> > > Bulk of the software and frequent updates are evident but what changes 
> > > in functionality?  The Web site of my credit union works as it did 
> > > five years ago.
> 
> From: David Wright 
> Date: Wed, 4 Jan 2023 21:46:39 -0600
> > What's that got to do with Firefox? OK, it's good that the CU hasn't
> > run with every fad that some web developers seem to want, so that
> > they get what I call a high "coo-rating". (Coo, look at that.)
> 
> Yes, good that the CU Web site is relatively stable.  That was a 
> secondary point.
> 
> My primary interest: if many Web sites appear and perform as five 
> years ago, what is the need for the frequent updates?  A bug needs 
> repair a.s.a.p.  A bug compromising security needs repair sooner.  
> Are most Firefox updates security critical?

Don't forget that HTML5 is a "living standard" -- the WHATWG euphemism
for "we change the standard from under your bottom whenever one of
our more powerful members feels like it".

If Firefox wants to call itself standards compliant, it has to follow
suit. If it isn't standadts compliant, we are left with one choice:
Chrome (I don't count Apple, that's even worse).

I do disagree with much of what the Mozilla foundation does, and at
the end, they see the world through ad-industry coloured goggles, but
they are the last credible ditch we have. Google has succeeded in
cornering the Internet -- and the worst: many people seem to enjoy
it.

You thought the situation with Microsoft and computing in the 1980s
and 1990s was grotesque? It's much, much worse these days. The
difference is that the monopoly watchdogs are fast asleep at the
wheel these days.

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: [OT] coo, was Re: Debian release criteria.

[David Wright]

On Sat 07 Jan 2023 at 17:52:43 (-), Curt wrote:
> On 2023-01-07, Greg Wooledge  wrote:
> >
> > To an American audience, the meaning is quite different.  We only use
> > "coo" to describe the noise made by a dove, or as an (urban) slang
> > term which is a shortened form of "cool".
> >
> 
> I haven't been following,

… which might mean you missed the ² in
coo² (slang) interjection

> but coo to me is the sound a pigeon makes,

… which, of course, is coo¹, the first headword.

Cheers,
David.

Re: [OT] coo, was Re: Debian release criteria.

[David Wright]

On Fri 06 Jan 2023 at 23:41:25 (-0500), Greg Wooledge wrote:
> > > On Fri, Jan 06, 2023 at 01:26:54PM -0600, David Wright wrote:
> > > > Rather,
> > > > 
> > > >   coo² (slang) interjection, expressive of surprise. (Chambers)
> > > > 
> > > > and this has been around far longer than my lifetime.
> 
> > > When using slang, the current meaning is the one that will be understood
> > > by your audience.  Not some archaic meaning.
> > 
> > Err, where did you get the idea that coo is archaic?
> 
> The part where you said this particular usage is older than yourself.

Yes, it joins the 99.9% of the words we use, whose current usage
predates our own generation, and yet are not archaic.

> > We Brits use the word "Coo"; I guess the equivalent here is "Gee",
> > which sounds very American to British ears of my generation.
> 
> Ahhh, it's a regional usage, then.  My mistake.
> 
> To an American audience, the meaning is quite different.  We only use
> "coo" to describe the noise made by a dove, or as an (urban) slang
> term which is a shortened form of "cool".
> 
> https://www.urbandictionary.com/define.php?term=coo

So I'm expected to check my use of slang against a dictionary that's
receiving over 2000 entries per day at times, and where most of the
definitions are not expected to appear in standard dictionaries.
This ultra-contemporary slang, much of which I neither hear nor read,
is supposed to be more familiar to people here for whom English is a
second language. OTOH, reputable, edited dictionaries, printed and
online, are unlikely to be consulted by such people, yes?

>   A slightly shortened version of "cool"
>   used by only the cooest people, coo is the best way to describe
↑↑
>   something that is completely awesome.
> 
> And so on.

Ah, awesome, another word that has had all meaning drained from it
by overuse.

  Receptionist: Do you have your insurance card with you?
Me: Let's see … ah, yes, here it is.
  Receptionist: Awesome!
  (uttered 2022-12-28 ~16:00)

Cheers,
David.

Re: Web functionality; was Re: Debian release criteria.

[David Wright]

On Sun 08 Jan 2023 at 07:53:11 (-0800), pe...@easthope.ca wrote:

> My primary interest: if many Web sites appear and perform as five 
> years ago, what is the need for the frequent updates?  A bug needs 
> repair a.s.a.p.  A bug compromising security needs repair sooner.  
> Are most Firefox updates security critical?

Judge for yourself:

$ zcat /usr/share/doc/firefox-esr/changelog.Debian.gz | head -n 240 | grep -e 
CVE -e '^ --'
CVE-2022-46880, CVE-2022-46872, CVE-2022-46881, CVE-2022-46874,
CVE-2022-46882, CVE-2022-46878.
 -- Mike Hommey   Wed, 14 Dec 2022 07:48:39 +0900
CVE-2022-45403, CVE-2022-45404, CVE-2022-45405, CVE-2022-45406,
CVE-2022-45408, CVE-2022-45409, CVE-2022-45410, CVE-2022-45411,
CVE-2022-45412, CVE-2022-45416, CVE-2022-45418, CVE-2022-45420,
CVE-2022-45421.
 -- Mike Hommey   Wed, 16 Nov 2022 06:20:30 +0900
CVE-2022-42927, CVE-2022-42928, CVE-2022-42929, CVE-2022-42932.
 -- Mike Hommey   Wed, 19 Oct 2022 05:04:39 +0900
CVE-2022-40959, CVE-2022-40960, CVE-2022-40958, CVE-2022-40956,
CVE-2022-40957, CVE-2022-40962.
 -- Mike Hommey   Wed, 21 Sep 2022 06:58:15 +0900
CVE-2022-38472, CVE-2022-38473, CVE-2022-38477, CVE-2022-38478.
 -- Mike Hommey   Wed, 24 Aug 2022 06:35:58 +0900
 -- Mike Hommey   Mon, 15 Aug 2022 15:46:49 +0900
CVE-2022-36319, CVE-2022-36318, CVE-2022-36315, CVE-2022-36316,
CVE-2022-36320, CVE-2022-2505.
 -- Mike Hommey   Sun, 14 Aug 2022 16:59:19 +0900
CVE-2022-34479, CVE-2022-34470, CVE-2022-34468, CVE-2022-34482,
CVE-2022-34483, CVE-2022-34476, CVE-2022-34481, CVE-2022-34474,
CVE-2022-34471, CVE-2022-34472, CVE-2022-2200, CVE-2022-34480,
CVE-2022-34477, CVE-2022-34475, CVE-2022-34473, CVE-2022-34484,
CVE-2022-34485.
 -- Mike Hommey   Wed, 29 Jun 2022 07:41:32 +0900
 -- Mike Hommey   Fri, 10 Jun 2022 06:24:01 +0900
CVE-2022-31736, CVE-2022-31737, CVE-2022-31738, CVE-2022-31740,
CVE-2022-31741, CVE-2022-31742, CVE-2022-31743, CVE-2022-31744,
CVE-2022-31745, CVE-2022-1919, CVE-2022-31747, CVE-2022-31748.
 -- Mike Hommey   Wed, 01 Jun 2022 06:07:37 +0900
  * Fixes for mfsa2022-19, also known as CVE-2022-1802 and CVE-2022-1529.
 -- Mike Hommey   Sat, 21 May 2022 07:32:04 +0900
CVE-2022-29914, CVE-2022-29909, CVE-2022-29916, CVE-2022-29911,
CVE-2022-29912, CVE-2022-29915, CVE-2022-29917, CVE-2022-29918.
 -- Mike Hommey   Wed, 04 May 2022 08:48:41 +0900
CVE-2022-1097, CVE-2022-28281, CVE-2022-28282, CVE-2022-28283,
CVE-2022-28284, CVE-2022-28285, CVE-2022-28286, CVE-2022-28287,
CVE-2022-24713, CVE-2022-28289, CVE-2022-28288.
 -- Mike Hommey   Wed, 06 Apr 2022 09:04:22 +0900
 -- Mike Hommey   Thu, 10 Mar 2022 09:09:43 +0900
CVE-2022-26383, CVE-2022-26384, CVE-2022-26387, CVE-2022-26381,
CVE-2022-26382, CVE-2022-26385, CVE-2022-0843.
  * Fixes for mfsa2022-09, also known as: CVE-2022-26485, CVE-2022-26486.
 -- Mike Hommey   Wed, 09 Mar 2022 07:09:27 +0900
CVE-2022-22754, CVE-2022-22755, CVE-2022-22756, CVE-2022-22759,
CVE-2022-22760, CVE-2022-22761, CVE-2022-22764, CVE-2022-0511.
 -- Mike Hommey   Wed, 09 Feb 2022 07:53:42 +0900
 -- Mike Hommey   Mon, 31 Jan 2022 06:21:31 +0900
 -- Mike Hommey   Sat, 15 Jan 2022 07:41:14 +0900
CVE-2022-22743, CVE-2022-22742, CVE-2022-22741, CVE-2022-22740,
CVE-2022-22738, CVE-2022-22737, CVE-2021-4140, CVE-2022-22748,
CVE-2022-22745, CVE-2022-22747, CVE-2022-22739, CVE-2022-22751,
CVE-2022-22752.
 -- Mike Hommey   Wed, 12 Jan 2022 08:03:30 +0900
$ 

Cheers,
David.

Web functionality; was Re: Debian release criteria.

[peter]

David & all,

Earlier from peter,
> > Bulk of the software and frequent updates are evident but what changes 
> > in functionality?  The Web site of my credit union works as it did 
> > five years ago.

From: David Wright 
Date: Wed, 4 Jan 2023 21:46:39 -0600
> What's that got to do with Firefox? OK, it's good that the CU hasn't
> run with every fad that some web developers seem to want, so that
> they get what I call a high "coo-rating". (Coo, look at that.)

Yes, good that the CU Web site is relatively stable.  That was a 
secondary point.

My primary interest: if many Web sites appear and perform as five 
years ago, what is the need for the frequent updates?  A bug needs 
repair a.s.a.p.  A bug compromising security needs repair sooner.  
Are most Firefox updates security critical?

Bigger software has more opportunities for security compromise.  A 
genuine interest in security should motivate a lean browser for 
security critical purposes.  I'd prefer to access the CU with Dillo.   
Unfortunately it gets ... no response.  =8~/

> Sure, [Wikipedia pages] tend to be no more complex than required for 
> what's being displayed. I assume that's their policy, very sensible.

Wikimedia and Debian get gold stars for keeping their Web sites "in 
house". They don't invoke background access to 3rd party pages far and 
wide.  The policy deserves acknowledgement.

Thx, ... P.

- 
mobile: +1 778 951 5147
  VoIP: +1 604 670 0140
https://en.wikibooks.org/wiki/User:PeterEasthope

Re: Bootcamp et Linux ?

[Samy (Zaclys)]

  
  
Le 07/01/2023 à 18:09, ptilou a écrit :


  Je te remerci,  donc je vais utiliser une cles usb pour booter, et je cherche, un qui sait s’en servir, comme quand j’étais à Paris.
Dois y avoir une solution sans Bootcamp, et sans refit, avoir un volume *.dmg et que tu boot, comme si tu as plusieurs système Mac OS X ?




De mieux en mieux… Toujours aussi confus. Tu mélanges tout.

Bref, pour clore cette demande pathétique, 2 solutions :
- double démarrage macOS / Debian géré par exemple avec rEFInd
  (mais tu peux essayer Grub2)

- démarrage sur hôte macOS, et installation d'un système invité
  Debian avec Qemu (qui gère des images au format qcow2, vmdk, img)
  via l'interface virt-manager
https://wiki.qemu.org/Hosts/Mac

https://www.arthurkoziel.com/running-virt-manager-and-libvirt-on-macos/
https://stackoverflow.com/questions/53778106/how-to-enable-kvm-on-a-mac-for-qemu



Avec ça, tu as assez de lecture pour nous laisser tranquilles.

  

Re: SID Xorg Erreur Segmentation

[Basile Starynkevitch]

On 08/01/2023 11:47, Orion wrote:

Bonjour,

Suite à une mise à jour autour du 31/12, Xorg ne démarre plus, je me 
souviens d'un message d'alerte d'apt list bug lors de la maj parlant 
d'un risque de segmentation error mais je me pensais sous Wayland et 
non concerné.


Quelqu'un a t il peut être vu le message et a un lien vers une solution?



Sans aucune garantie que ça marche (car Xorg comme Wayland dépend du 
matériel, c'est différent avec un contrôleur graphique NVIDIA et avec 
une carte graphique AMD) je vous invite à faire (sous root, en console - 
il faut peut être booter en mode rescue) les commandes suivantes et à en 
poster sur debian-user-french les effets.



mise à jour des paquets et installation de xfce4

aptitude update

aptitude upgrade

aptitude install xfce4-session

redemarrage

reboot

interrogation du matériel

lspci

lscpu

tentative de redemarrage du serveur Xorg

startx /usr/bin/xfce4-session

regarder avec less /var/log/Xorg.0.log les messages d'erreurs puis

grep -ni5 error /var/log/Xorg.0.log


Pour ma part, je vous souhaite une bonne année 2023 et cherche des 
partenaires intéressés par /RefPerSys/ en http://refpersys.org/



Bonne fin de weekend

--
Basile Starynkevitch
(only mine opinions / les opinions sont miennes uniquement)
92340 Bourg-la-Reine, France
web page: starynkevitch.net/Basile/

Re : Re: Fuite de DNS avec mon client VPN

[benoit]

Le dimanche 8 janvier 2023 à 07:03, Olivier Back my spare 
 a écrit :

> Je vais encore en fâcher plus d'un mais bon...

Fâcher peut-être pas, mais agacer,  ça se pourrait !

> Expressvpn dit que le premier élément qui est la cause des fuites DNS,
> c'est le webrtc. Pourtant je croyais que vous aviez lu leur doc.
> 

J'ai fait un test de fuites DNS et le webrtc est peut-être un autre problème.

> Là, vous affirmez à l'aide d'un wiki douteux que le problème se situe au
> niveau de /etc/resolv.conf.
> 

Ca n'a rien de douteux, je m'en suis rendu compte hier, l'installation 
d'openvpn installe un script /etc/openvpn/update-resolv-conf, qui, s'il n'est 
pas appelé pour modifier /etc/resolv.conf, ça va laisser /etc/resolv.conf avec 
l'ip du serveur DNS de la box du FAI.
Donc je passais par un VPN en continuant à interroger le serveur DNS de la box 
du FAI.
C'est pas une fuite de DNS, c'est juste une erreur de config de ne pas avoir 
veillé à appeler /etc/openvpn/update-resolv-conf qui lui-même fait appel à 
/sbin/resolvconf et met à jour /etc/resolv.conf.



> Jamais de la vie je ne toucherais en profondeur quelque chose qui n'est
> même pas documenté dans ma distrib qui fait un bon 600 pages et encore
> moins sur des wiki comme celui d'ubuntu, Debian ou Fedora.
> 

C'est pas toucher en profondeur que faire en sorte de veiller à ce que le 
script /etc/openvpn/update-resolv-conf soit bien appelé et qu'il dispose de 
/sbin/resolvconf, de façon à ce que /etc/resolv.conf soit bien mi à jour au 
démarrage du démon VPN.


Après avoir veillé à cela, il y a un avant et un après.
Avant :
www.dnsleaktest.com  affichait le DNS de mon FAI ce qui est logique puisque 
c'est le DNS qui était affecté à nameserver /etc/resolv.conf.
Après il ne pouvait plus le voir, car nameserver reçoit le DNS du VPN.

Si vous avez des conseils à me donner pour faire en sorte que ma résolution de 
nom de domaine soit bien configurée par openvpn, sans faire cette manip, ils 
sont les bien venus.
Cette manip n'est peut-être pas la façon la plus appropriée d'y parvenir.
Mais ma config d'avant, qui consistait à continuer à interroger le DNS du FAI 
dans /etc/resolv.conf, plutôt que celui du VPN, n'était certainement 
appropriée. 
Et j'en ai la preuve par un teste www.dnsleaktest.com, avant et après. 


> 
> Vous ne cherchez pas comment fonctionne le VPN pour résoudre le
> problème. Vous bidouillez sans savoir ce que vous faites pour un
> nonsenese problème pour une nonsense raison. La sécurité comme vous le
> prétendez n'est qu'un prétexte. Privacytools.io a tout ce que vous
> voulez mais il semble que votre kif soit de surfer en se faisant passer
> pour un autre.
> 

Vos conseil pour bien configurer un client openvpn sous GNU/Linux Debian sont 
les bienvenus!
Mais s'il vous plaît, tenons nous en au sujet : 
la config d'un client openvpn sur une distribution GNU/Linux Debian afin 
d'éviter une fuite de DNS. 
Et ne divaguez sur des théories psychologisantes de comptoir.

Merci d'avance

--
Benoît

Re: why some memory are missing

[lsg]

On 1/8/23 17:36, hede wrote:


I'm pretty sure it can address 2^32 bit aka 4 GB. But within this 
range there is the PCI address space.  PCI cards are memory mapped. To 
access memory regions on PCI devices you can simply access main 
memory. But you cannot access PCI devices AND use full 4 GB of 
physical main memory within the 2^32 bit range.


Typically Chipsets/BIOS can map the missing memory somewhere above 4 
GB but not every Chipset/BIOS does this. Then even in 64 Bit mode 
you'll lose memory in the range of the PCI address space. If, on the 
other side, the Chipset/BIOS maps those memory regions above 4 GB then 
even in 32 Bit Mode Linux can use this memory (via PAE).


hede


Thank hede! you solved my problem! i enable Memory hole Remapping in 
bios, memtest86+ shows 4095M memory now! top in buster for 686 shows 
3029.6M while top in bullseye for amd shows 3930.9M. Thanks!

SID Xorg Erreur Segmentation

[Orion]

Bonjour,

Suite à une mise à jour autour du 31/12, Xorg ne démarre plus, je me
souviens d'un message d'alerte d'apt list bug lors de la maj parlant d'un
risque de segmentation error mais je me pensais sous Wayland et non
concerné.

Quelqu'un a t il peut être vu le message et a un lien vers une solution?

Merci

Re: why some memory are missing

[hede]

Am 08.01.2023 00:30, schrieb Jeremy Hendricks:

I imagine it’s a bios limitation and it cannot address the full 4GB
even though it’s a 64bit CPU. This was common with the Intel 925/945
chipsets even through they supported Intel 64bit CPUs of the time.


I'm pretty sure it can address 2^32 bit aka 4 GB. But within this range 
there is the PCI address space.  PCI cards are memory mapped. To access 
memory regions on PCI devices you can simply access main memory. But you 
cannot access PCI devices AND use full 4 GB of physical main memory 
within the 2^32 bit range.


Typically Chipsets/BIOS can map the missing memory somewhere above 4 GB 
but not every Chipset/BIOS does this. Then even in 64 Bit mode you'll 
lose memory in the range of the PCI address space. If, on the other 
side, the Chipset/BIOS maps those memory regions above 4 GB then even in 
32 Bit Mode Linux can use this memory (via PAE).


hede