Re: [un peu HS] Compresser un DVD en divX avec les menus

[didier . gaumet]

Je n'ai jamais fait et je n'utilise pas divx/xvid, donc prends mes propos avec 
la prudence nécessaire

divx ayant comme les dvd une structure de menus, je *suppose* que ripper un dvd 
en divx préserve les menus (éventuellement en activant les bonnes options)

empaquetés dans Debian, les paquets suivants pourraient peut-être convenir
en GUI, vlc et handbrake
en CLI ffmpeg et mencoder
(liste non limitative: je connais mal le sujet)

Re: Unable to boot new buster installation

[Marco Möller]

On 08.06.20 01:49, Gary L. Roach wrote:

On 6/7/20 12:14 PM, Gary L. Roach wrote:

Hi all,

I recently up graded this system to Bullseye and then ran into trouble 
with the lack of Qt4  and had to re-install Buster. The installation 
went fine until kde desktop tried to start. The system froze with the 
following message:


The current input timing is not supported by the monitor display. 
Pleas change your input timing to 1920x1200@60Hz or any other monitor 
listed timing as per the monitor specifications.


I'm using a Dell U2412M monitor on an AMD 64 4 core system. The 
monitor worked fine before and still works fine on another computer. I 
tried both xrandr and compiz in Recovery Mode. In both cases I got 
"Can't open display".


I have full access to the file system in Recovery Mode.

Any suggestions will be sincerely appreciated.

Gary R





Unfortunately I have no idea about how to solve your problem. You maybe 
want to ask also on this list as well:  debian-...@lists.debian.org ?

Good Luck! Marco.

Re: Unable to boot new buster installation

[mick crane]

On 2020-06-07 20:14, Gary L. Roach wrote:

Hi all,

I recently up graded this system to Bullseye and then ran into trouble
with the lack of Qt4  and had to re-install Buster. The installation
went fine until kde desktop tried to start. The system froze with the
following message:

The current input timing is not supported by the monitor
display. Pleas change your input timing to 1920x1200@60Hz or any other
monitor listed timing as per the monitor specifications.

I'm using a Dell U2412M monitor on an AMD 64 4 core system. The
monitor worked fine before and still works fine on another computer. I
tried both xrandr and compiz in Recovery Mode. In both cases I got
"Can't open display".

I have full access to the file system in Recovery Mode.

Any suggestions will be sincerely appreciated.

Gary R


I'd start here.
https://wiki.debian.org/Xorg#Edit_xorg.conf

mick

--
Key ID4BFEBB31

Re: KDE run Dolphin as root?

[Andrei POPESCU]

On Du, 07 iun 20, 21:21:07, Marco Möller wrote:
> 
> Yes, design options exist. However, I never tried out if the user root could
> be blocked by the graphical session manager only, in the case of KDE usually
> sddm is in use. But I know that the login of user root can be blocked in
> general: when nowadays installing Debian, then there is offered to keep the
> root account deactivated, which is achieved by simply not assigning it a
> password but to leave the root's password empty and then activating the sudo
> mechanism for the during installation created normal user. Then the login as
> user root is disabled in general, not applying only to GUI login but also to
> text terminal login. As a consequence it is always required to log in as a
> normal user and using the command sudo would be the way to run commands with
> root permissions. The deactivation of the root account could also be
> achieved later on, any time, not only during installation of the system, by
> changing the password of user root to an empty string.

Careful, an empty password is not the same as a disabled password (see 
'man shadow'). The command 'passwd' will not even accept to change a 
password to an empty one.

To lock the password for an account use 'passwd -l'.

> But I am afraid that
> you then will have to care yourself to set up sudo properly when still
> possible to do so as user root.

In Debian's default configuration members of group 'sudo' have sudo 
access, so all you need is:

adduser my_user_name sudo

As far as I know the installer does the equivalent of that.

> Interestingly, although having disabled the root account during installation
> and having sudo automatically configured during installation, it by default
> appears to still be allowed to run command "sudo su -", which still lets you
> run a root terminal once you have been logged in as the normal user and
> knowing the user's password needed to use sudo! 

Warning, useless use of 'sudo su -' :)

There is no need for that, use 'sudo -i' ;)

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: why !oh why Debian and application list

[Andrei POPESCU]

On Du, 07 iun 20, 19:23:24, Seeds Notoneofmy wrote:
> Well, as the subject suggests, I'm a bit fed up with the logic behind
> how installed programs are sorted out in the Applications menu.
> 
> The need to go hunt down an installed application seems yester century.
> 
> I just installed Picard, and it does not show up in Sound and Video,
> where logic would suggest it be.
> 
> I had to dial it up from the command line.
> 
> I'm willing and ready to be educated on why things are such with Debian.

Debian does very little customization of the various Desktop 
Environments, you are experiencing upstream's take on usability.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: Zoom- best practice?

[Anastasios Lisgaras]

On 6/8/20 12:06 AM, Nicolas George wrote:

Open Source is not enough.

I did not think it would be necessary to explain why Libre Software is
important here. It is not just a matter of possible malicious in the
code, it is a matter of being able to change it to suit our needs, to
fix it if there are bugs, to include parts into other projects. If all
of this is not possible, it is a dead-end project, a waste of energy,
only marginally better than closed-source surveillanceware.

Regards,


An interesting point of view that I agree with.
It is a very delicate and important piece, which some consider a detail 
or do not pay attention to. But personally I agree with you, it matters.


But, do you mention this because of the jitsi license that is *Apache 
License 2.0 ?

https://github.com/jitsi/jitsi-videobridge

--
Kind regards,
Anastasios Lisgaras

USB HDD issue with buster-backports kernel

[Christopher David Howie]

Hello,

I recently upgraded to the buster-backports kernel (5.5.17).  After this 
upgrade I needed to prepare an external HDD (WD Elements 2TB) for 
encryption and so I used the "write zeroes to a plain crypto container" 
approach:


# cryptsetup open --type plain -d /dev/urandom /dev/sde1 to_be_wiped
# dd if=/dev/zero of=/dev/mapper/to_be_wiped bs=64K status=progress

I verified that the container was properly aligned.  I had drastically 
different results on the 5.5 kernel versus the buster 4.19 kernel:


* On the 4.19 kernel, I was getting throughput between 30MB/sec and 
50MB/sec.  The operation completed successfully.


* On the 5.5 kernel, I was getting throughput between 10MB/sec and 
20MB/sec.  At apparently random points, dd would stop reporting any 
progress and a "usb-storage" process in top would be consuming 100% CPU. 
 Any commands against the HDD (even smartctl) would hang until the 
device was physically replugged.


Since everything seems to work fine on 4.19 I do not suspect any issues 
with the drive itself.  It seems there is some problem with the 5.5 
kernel?  What can I do to further troubleshoot this?


-- lsusb --
Bus 005 Device 002: ID 8087:8000 Intel Corp.
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 003: ID 1058:25a2 Western Digital Technologies, Inc. 
Elements 25A2
Bus 004 Device 002: ID 1058:25a2 Western Digital Technologies, Inc. 
Elements 25A2

Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 004: ID 1058:1042 Western Digital Technologies, Inc. 
Elements SE Portable (WDBPCK)

Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
---

The device in question is device 2 on bus 4.

Buster kernel uname:

Linux liz 4.19.0-9-amd64 #1 SMP Debian 4.19.118-2 (2020-04-29) x86_64 
GNU/Linux


Buster-backports kernel uname:

Linux liz 5.5.0-0.bpo.2-amd64 #1 SMP Debian 5.5.17-1~bpo10+1 
(2020-04-23) x86_64 GNU/Linux


--
Chris Howie
http://www.chrishowie.com
http://en.wikipedia.org/wiki/User:Crazycomputers

If you correspond with me on a regular basis, please read this document: 
http://www.chrishowie.com/email-preferences/


PGP fingerprint: 2B7A B280 8B12 21CC 260A DF65 6FCE 505A CF83 38F5


IMPORTANT INFORMATION/DISCLAIMER

This document should be read only by those persons to whom it is 
addressed.  If you have received this message it was obviously addressed 
to you and therefore you can read it.


Additionally, by sending an email to ANY of my addresses or to ANY 
mailing lists to which I am subscribed, whether intentionally or 
accidentally, you are agreeing that I am "the intended recipient," and 
that I may do whatever I wish with the contents of any message received 
from you, unless a pre-existing agreement prohibits me from so doing.


This overrides any disclaimer or statement of confidentiality that may 
be included on your message.

Re: [un peu HS] Compresser un DVD en divX avec les menus

[Pierre Malard]

Bonjour,

Personnellement je tiens une bibliothèque de mes DVD rippés au format m4v avec 
VLC comme gestionnaire des médias. Du coup je ne m’occupe pas des menus et 
autres choses bien que ce soit possible aussi mais c’est du même genre. Voici 
la chaîne :
MakeMKV (http://www.makemkv.com ) : pour copier in 
extenso le DVD/Blu-ray au format Matroska mais sans les DRM (hè oui, il y en 
a). Je ne sais pas si il existe un dépôt Debian ou Ubuntu 
(https://www.makemkv.com/forum/viewtopic.php?f=3=224)
HandBrake (https://handbrake.fr ) : en standard dans la 
distribution standard Debian - Conversion du MKV en M4V
Subler MacOSX (https://subler.org) : pour éditer les TAG mp4 en vue d’une 
meilleure gestion du catalogue et, surtout, ré-intégrer les sous-titres au 
format SRT dans le M4V. Mais ça doit bien exister aussi sous Linux…
VLC (ou autre) : pour gérer la bibliothèque de vidéo.
Juste un petit hic, il faut

--
πr

À propos de nos chers économistes :
«Les habiles, dans notre siècle, se sont décernés a eux-mêmes la
qualification d’homme d’état. [...] ces politiques, ingénieux
a mettre aux fictions profitables un masque de nécessité.»
 Victor Hugo : “Les misérables”, La pléiade, Gallimard, P. 843

   |\  _,,,---,,_
   /,`.-'`'-.  ;-;;,_
  |,4-  ) )-,_. ,\ (  `'-'
 '---''(_/--'  `-'\_)   πr

perl -e '$_=q#: 3|\ 5_,3-3,2_: 3/,`.'"'"'`'"'"' 5-.  ;-;;,_:  |,A-  ) )-,_. ,\ 
(  `'"'"'-'"'"': '"'"'-3'"'"'2(_/--'"'"'  `-'"'"'\_): 
24πr::#;y#:#\n#;s#(\D)(\d+)#$1x$2#ge;print'
- --> Ce message n’engage que son auteur <--

> Le 8 juin 2020 à 09:37, didier.gau...@gmail.com a écrit :
> 
> 
> Je n'ai jamais fait et je n'utilise pas divx/xvid, donc prends mes propos 
> avec la prudence nécessaire
> 
> divx ayant comme les dvd une structure de menus, je *suppose* que ripper un 
> dvd en divx préserve les menus (éventuellement en activant les bonnes options)
> 
> empaquetés dans Debian, les paquets suivants pourraient peut-être convenir
> en GUI, vlc et handbrake
> en CLI ffmpeg et mencoder
> (liste non limitative: je connais mal le sujet)
> 



signature.asc
Description: Message signed with OpenPGP

No software raid and no LVM with netinstaller 10.04

[Bernd Recktor]

Hello again,

same error with netinstaller 10.04




.Hello,
.
.md/raid0:md0:cannot assamble multi_zone RAID0 with default_layot settings
.md/raid0:md0: please set raid0.default_layout to 1 or 2
.
.this is fatal if You use to have the rootfs on a RAID0
.
.since Debian 10.3 there is no way to create a software raid during 
installing with the net install cd.

.
.
.best regards, Bernd

Re: [Stretch] i915 plantage de l'affichage

[Daniel Caillibaud]

Le 07/06/20 à 08:48, Frederic Robert  a écrit :
> On 6/4/20 11:20 PM, Gaëtan Perrier wrote:
> 
> > J'ai un Lenovo T420 en CG Intel seule, sous testing et je n'ai jamais 
> > rencontré
> > de problème ...  
> 
> Bonjour Gaëtan et à la liste,
> 
> Je testerai bien testing mais toujours peur lol. Merci pour l'information.

Tu peux prendre un noyau plus récent (qui vient avec ses drivers vidéo) dans 
testing (voir sid)
tout en restant en stable (je tourne en stable avec un noyau 5.6 de sid 
récupéré manuellement
via https://packages.debian.org/sid/linux-image-amd64, mais maintenant y'a le 
même sur
https://packages.debian.org/bullseye/linux-image-amd64)

Mais désormais y'a du 5.5 sur 
https://packages.debian.org/buster-backports/linux-image-amd64
tu peux donc ajouter le dépôt et mettre à jour le noyau via ta gestion 
habituelle de paquets
(sans passer par télécharger puis `dpkg -i …`).

-- 
Daniel

Une erreur peut devenir exacte, selon que celui qui l'a commise 
s'est trompé ou non.
Pierre Dac

Re: Firefox over JACK in Debian Testing

[Christopher David Howie]

On 6/6/2020 11:25 PM, riveravaldez wrote:

Hi, here's the thing:

AFAIK Firefox lacks JACK support (in the sense that you can start
JACK and then Firefox and then, automatically, all I/O audio-ports
Firefox generated, appear as available JACK connections, let's say)

Is there any Debian package that can serve this purpose?
I have a JACK setup that runs all audio through Ardour so I can perform 
compression and EQ either system-wide or per-application.  I accomplish 
this by using pulseaudio.


If JACK is already running when pulseaudio starts, pulseaudio will 
create a single JACK sink and JACK source that redirects audio to/from a 
matching JACK source/sink.


I then use the following script to create additional sinks in PA that 
each have an independent source in JACK:


--
#!/bin/sh

exec pactl load-module module-jack-sink \
  client_name=pulse_sink_"$1" \
  connect=no \
  channels=2
--

Run like "./make-jack-sink music" which gives me a "music" PA sink 
connected to the "music" JACK source.


You don't automatically get a JACK port per audio stream, but you can 
make as many separate PA sinks as your system can handle and use the PA 
volume control application to switch audio streams between different PA 
sinks (and therefore JACK sources).


Then you can wire everything up on the JACK side, as usual.

--
Chris Howie
http://www.chrishowie.com
http://en.wikipedia.org/wiki/User:Crazycomputers

If you correspond with me on a regular basis, please read this document: 
http://www.chrishowie.com/email-preferences/


PGP fingerprint: 2B7A B280 8B12 21CC 260A DF65 6FCE 505A CF83 38F5


IMPORTANT INFORMATION/DISCLAIMER

This document should be read only by those persons to whom it is 
addressed.  If you have received this message it was obviously addressed 
to you and therefore you can read it.


Additionally, by sending an email to ANY of my addresses or to ANY 
mailing lists to which I am subscribed, whether intentionally or 
accidentally, you are agreeing that I am "the intended recipient," and 
that I may do whatever I wish with the contents of any message received 
from you, unless a pre-existing agreement prohibits me from so doing.


This overrides any disclaimer or statement of confidentiality that may 
be included on your message.

Jitsi can be built

[John ff]

A local member of the LUG here built jitsi from sources and he is not an IT 
professional.  From that I infer that it is possible.

⁣Sent from TypeApp ​

Re: Jitsi can be built

[Nicolas George]

John ff (12020-06-08):
> A local member of the LUG here built jitsi from sources and he is not
> an IT professional.  From that I infer that it is possible.

Thanks for the information. Do you have details? Was it all the
sub-projects or only some? Did they write a blog post or something
explaining how they did?

Regards,

-- 
  Nicolas George


signature.asc
Description: PGP signature

Re: Finding application's description

[Brian]

On Mon 08 Jun 2020 at 07:17:17 -0400, Greg Wooledge wrote:

> On Sat, Jun 06, 2020 at 06:08:48PM +0300, Andrei POPESCU wrote:
> > As per the description, gdebi is for local (i.e. downloaded .deb files) 
> > so it provides a function that synaptic does not.
> 
> For the record, gdebi is basically obsolete these days.  Its main
> feature ("install a local .deb plus all of its dependencies") has
> been incorporated into apt-get and apt.
> 
> apt install ./some-local-file.deb
> 
> Don't forget the leading ./ characters.  They are required so that apt
> knows this is a pathname rather than a packagename.  You're also allowed
> to specify a pathname with leading / or leading ../ characters.

Many users find gdebi very convenient to use, partularly when it is
associated with a double-click on a filename.

-- 
Brian.

Re: USB HDD issue with buster-backports kernel

[Andrei POPESCU]

On Lu, 08 iun 20, 10:56:41, Christopher David Howie wrote:
> 
> * On the 5.5 kernel, I was getting throughput between 10MB/sec and 20MB/sec.
> At apparently random points, dd would stop reporting any progress and a
> "usb-storage" process in top would be consuming 100% CPU.  Any commands
> against the HDD (even smartctl) would hang until the device was physically
> replugged.

What about dmesg?

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: Jitsi can be built

[tomas]

On Mon, Jun 08, 2020 at 02:17:27PM +0100, John ff wrote:
> A local member of the LUG here built jitsi from sources and he is not an IT 
> professional.  From that I infer that it is possible.

Thanks for this data point. I assumed as much.

Cheers
-- t


signature.asc
Description: Digital signature

Re: Jitsi can be built

[Reco]

Hi.

On Mon, Jun 08, 2020 at 02:17:27PM +0100, John ff wrote:
> A local member of the LUG here built jitsi from sources and he is not
> an IT professional.  From that I infer that it is possible.

I will assume that the build process was similar to described at [1].
A quick look at so-called "sources", i.e. [2] reveals us:

1) Multiple *jar files of unknown content.
2) Pre-built *so files without sources, and without any visible
licences.
3) Build-dependency on non-free Oracle JDK and pre-built Apache ANT.
4) Possible (too lazy to check it) arbitrary file downloads during the
build process - ant in (in)famous for it.


Proper building from the source would require (some steps omitted for
simplicity):

1) Building openjdk from the source (Debian does it, so that's easy).
2) Building ant from the source (ditto).
3) Re-building all those *jar blobs (possible, given that those are
popular java libraries).
4) Re-building from the source all those *so files.
5) Fixing build.xml to prevent it from downloading random *jars from all
the Internet (may be impossible).
6) De-composing the resulting *jar(s) and replacing bundled *jars with
proper Debian dependencies.

And last, but not least:
7) Repeat build process once jitsi source is updated.

Points from 3 to 7 inclusive require one to be an "IT professional" IMO.
Somehow I doubt that aforementioned local member of LUG followed the
latter process, most possibly it was former. I.e. - not real BTS at all.

Reco

[1] https://desktop.jitsi.org/Documentation/RetrievingAndBuildingTheSources
[2] http://download.jitsi.org/jitsi/src/jitsi-src-2.10.5550.zip

Re: consulta X-Forwarded-For de Apache

[miguel angel gonzalez]

Hola Ángel,

Justo es lo que comento, sólo como prueba:
Con remoteip añadir ese servidor a un listado* (sólo como prueba porque no
es un servidor confiable por lo menos no nos pertenece a nosotros)*
La idea no es mía, es necesario ya que se procesa el fichero después por
otra aplicación, es decir, sólo necesito la ip final del cliente no por los
servidores que pasa.

@camaleon:
¿No sería más conveniente guardar la IP del cliente y la de los
proxies, y procesar/filtrar después ese registro para que te muestre
sólo la IP que quieres?

Pues si no encuentro otra solución va a ser la opción.

Sigo buscando porque la opción que comentas de «%h» por «%a» la probé y no
es exactamente lo que busco.

Gracias, un saludo.

El lun., 8 jun. 2020 a las 4:53, Ángel (<
debian-user-span...@debian.16bits.net>) escribió:

> On 2020-06-07 at 18:03 +0200, miguel angel gonzalez wrote:
> > Localizado donde está el problema, esa ip de la derecha es un proxy
> > por el que pasa pero en el log necesito que sólo registre la del
> > cliente final, la de la izquierda.
>
> No. Lo que pretendes hacer es muy mala idea.
>
> Lo que deberías hacer es, o bien guardar las dos direcciones IP (o tres,
> o cinco...), indicando que la conexión vino de X, que afirmó estar
> haciendo de proxy para Y. O guardar solo la IP de ese proxy desconocido.
>
> El motivo es muy simple. Si te fias de cualquiera que diga ser un proxy,
> y le crees el cliente que afirma ser el responsable e la petición, es
> posible falsear la dirección de origen. Solo debes creerte la cabecera
> de X-Forwarded-For si la dirección anterior de la que te viene (sea de
> esa cabecera, o la ip que se conecta) es de un proxy de confianza (por
> ejemplo, sabes que tu balanceador te da la dirección real).
>
> Un saludo
>
>

-- 
/m.a.

Re: Finding application's description

[Greg Wooledge]

On Sun, Jun 07, 2020 at 10:07:18PM +1000, David wrote:
> $ apt show gdebi
> [...]
> Description: simple tool to view and install deb files - GNOME GUI
>  gdebi lets you install local deb packages resolving and installing
>  its dependencies. apt does the same, but only for remote (http, ftp)
>  located packages.

That last sentence is out of date.  apt does that for local files now.

Re: Finding application's description

[Greg Wooledge]

On Sat, Jun 06, 2020 at 06:08:48PM +0300, Andrei POPESCU wrote:
> As per the description, gdebi is for local (i.e. downloaded .deb files) 
> so it provides a function that synaptic does not.

For the record, gdebi is basically obsolete these days.  Its main
feature ("install a local .deb plus all of its dependencies") has
been incorporated into apt-get and apt.

apt install ./some-local-file.deb

Don't forget the leading ./ characters.  They are required so that apt
knows this is a pathname rather than a packagename.  You're also allowed
to specify a pathname with leading / or leading ../ characters.

Re: KDE run Dolphin as root?

[Greg Wooledge]

On Mon, Jun 08, 2020 at 09:07:58AM +0300, Andrei POPESCU wrote:
> In Debian's default configuration members of group 'sudo' have sudo 
> access, so all you need is:
> 
> adduser my_user_name sudo

(and then log out and back in)

> As far as I know the installer does the equivalent of that.

If you enter an empty root password, yes, I've been told that it does.
If you enter a non-empty root password, then it doesn't.

Re: why !oh why Debian and application list

[Peter Ehlert]

On 6/7/20 11:20 PM, Andrei POPESCU wrote:

On Du, 07 iun 20, 19:23:24, Seeds Notoneofmy wrote:

Well, as the subject suggests, I'm a bit fed up with the logic behind
how installed programs are sorted out in the Applications menu.

The need to go hunt down an installed application seems yester century.

I just installed Picard, and it does not show up in Sound and Video,
where logic would suggest it be.

I had to dial it up from the command line.

I'm willing and ready to be educated on why things are such with Debian.

Debian does very little customization of the various Desktop
Environments, you are experiencing upstream's take on usability.

My personal perception/observation:
the individuals that bundle the DEs configure them differently.
some are "pimped out", some are spartan, by design.

for example, the Mate DE is very spartan... a bit of effort is needed to 
make it My Way.

this is Good. less cruft, and much better for the low resource machines.


Kind regards,
Andrei

Re: Jitsi can be built

[Reco]

Hi.

On Mon, Jun 08, 2020 at 06:25:57PM +0200, to...@tuxteam.de wrote:
> On Mon, Jun 08, 2020 at 05:28:06PM +0300, Reco wrote:
> > Hi.
> > 
> > On Mon, Jun 08, 2020 at 02:17:27PM +0100, John ff wrote:
> > > A local member of the LUG here built jitsi from sources and he is not
> > > an IT professional.  From that I infer that it is possible.
> > 
> > I will assume
>  ^^
> Aha.

OP lacked the details, it's all we can do - to assume and to guess.


> > 4) Possible (too lazy to check it) arbitrary file downloads during the
>   
> I think it's a bit unfair to state such assumptions without really
> checking in-depth.

Point taken. I'm still lazy to check it out, so disregard this one.


> I've had a look at the jitsi-desktop environment, and the couple
> of .jar I saw are more or less standard Java components.

No. They are just called like that. One should not trust the contents of
those jars more than the random executable from the nearest warez dump.
There's also a matter of bundled *so files.


> A clean Debian packaging would try to replace those components by
> library packages to depend on. And so on.

No. A proper Debian packaging *must* replace all blobs that come with
the source, unless maintainer is content with the package ending in
non-free archive. Either it can be built from the source from the bottom
to the top or it's non-DFSG compliant. Simple as that.


> But jumping to the conclusion that the thing is "not really free"
> is a big jump to do.

I'm merely applying Debian policy to the build process here, and I even
did not applied all of it.


> And saying that "non-professionals" (what's this, anyway?) can't do
> this is downright wrong.

Nope. It takes a professional to distinguish barely outlined upstream
"build process" from a proper one, and it takes it again to follow a
proper process. Nobody requires that from the beginner, of course, these
things can be learned, but learning them takes time and effort.

What's really wrong is to mistake a zip archive full of blobs which
should be built with non-free toolset with the proper libre source
tarball which should built with libre tools.
But then again, it's Java we're talking about here, and living in
proprietary ecosystem breeds strange habits.

Reco

Re: Jitsi can be built

[tomas]

On Mon, Jun 08, 2020 at 05:28:06PM +0300, Reco wrote:
>   Hi.
> 
> On Mon, Jun 08, 2020 at 02:17:27PM +0100, John ff wrote:
> > A local member of the LUG here built jitsi from sources and he is not
> > an IT professional.  From that I infer that it is possible.
> 
> I will assume
 ^^
Aha.

> 4) Possible (too lazy to check it) arbitrary file downloads during the
      
I think it's a bit unfair to state such assumptions without really
checking in-depth.

I've had a look at the jitsi-desktop environment, and the couple
of .jar I saw are more or less standard Java components.

Of course, it's an anti-pattern (quite widespread, alas) to ingest
external components into a repo. And the buildery in the Java world
is... well, I lack polite terms for that.

A clean Debian packaging would try to replace those components by
library packages to depend on. And so on.

But jumping to the conclusion that the thing is "not really free"
is a big jump to do. And saying that "non-professionals" (what's
this, anyway?) can't do this is downright wrong.

Cheers
-- t


signature.asc
Description: Digital signature

Re: USB HDD issue with buster-backports kernel

[Christopher David Howie]

On 6/8/2020 11:38 AM, Andrei POPESCU wrote:
> What about dmesg?

Sorry, yes... I forgot to mention.  dmesg was absolutely silent when the
drive stopped responding.  After unplugging it, I of course got a flood
of errors from dm-crypt about being unable to write to the disk.

-- 
Chris Howie
http://www.chrishowie.com
http://en.wikipedia.org/wiki/User:Crazycomputers

If you correspond with me on a regular basis, please read this document:
http://www.chrishowie.com/email-preferences/

PGP fingerprint: 2B7A B280 8B12 21CC 260A DF65 6FCE 505A CF83 38F5


IMPORTANT INFORMATION/DISCLAIMER

This document should be read only by those persons to whom it is
addressed.  If you have received this message it was obviously addressed
to you and therefore you can read it.

Additionally, by sending an email to ANY of my addresses or to ANY
mailing lists to which I am subscribed, whether intentionally or
accidentally, you are agreeing that I am "the intended recipient," and
that I may do whatever I wish with the contents of any message received
from you, unless a pre-existing agreement prohibits me from so doing.

This overrides any disclaimer or statement of confidentiality that may
be included on your message.



signature.asc
Description: OpenPGP digital signature

Re: Installation d'une webcam Logitech sur Buster

[Olivier]

Le paquet uvccapture n'est pas installé sur ma machine.
Ce paquet est-il nécessaire ?

Le ven. 5 juin 2020 à 21:35, Gaëtan Perrier  a
écrit :

> Le vendredi 05 juin 2020 à 19:22 +0200, Olivier a écrit :
> > Bonjour,
> >
> > J'ai récupéré une webcam Logitech assez ancienne.
> > Je souhaite l'utiliser sur un portable sous Buster.
> >
> > La caméra me semble bien détectée mais aucune n'est visible ni dans
> Alsa, ni
> > avec Cheese.
> > J'ai :
> >
> > [ 3106.490546] usb 5-2: USB disconnect, device number 5
> > [ 3110.874470] usb 5-1: new full-speed USB device number 6 using uhci_hcd
> > [ 3111.092529] usb 5-1: New USB device found, idVendor=046d,
> idProduct=092f,
> > bcdDevice= 0.00
> > [ 3111.092534] usb 5-1: New USB device strings: Mfr=1, Product=2,
> > SerialNumber=0
> > [ 3111.092537] usb 5-1: Product: Camera
> > [ 3111.092539] usb 5-1: Manufacturer:
> > [ 3111.097335] gspca_main: spca561-2.14.0 probing 046d:092f
> > [ 3111.154709] input: spca561 as /devices/pci:00/:00:1d.3/usb5/5-
> > 1/input/input12
> >
> > Que faire ?
> >
> > Slts
> >
>
> Salut,
>
> Ça c'est la détection USB, ça ne veut pas dire qu'ensuite un pilote a pu la
> prendre en charge. Je ne sais pas quel type de webcam c'est mais par
> exemple si
> c'est une webcam au standard UVC tu devrais avoir plus loin dans les log un
> truc de ce genre:
>
> uvcvideo: Found UVC 1.00 device Philips SPC 1300NC Webcam (0471:0331)
> uvcvideo 2-1.3:1.0: Entity type for entity Extension 5 was not initialized!
> uvcvideo 2-1.3:1.0: Entity type for entity Extension 4 was not initialized!
> uvcvideo 2-1.3:1.0: Entity type for entity Processing 3 was not
> initialized!
> uvcvideo 2-1.3:1.0: Entity type for entity Camera 1 was not initialized!
> input: Philips SPC 1300NC Webcam as
> /devices/pci:00/:00:1d.0/usb2/2-
> 1/2-1.3/2-1.3:1.0/input/input24
> usbcore: registered new interface driver uvcvideo
> USB Video Class driver (1.1.1)
>
> Gaëtan
>

Re: Installation d'une webcam Logitech sur Buster

[Olivier]

Le ven. 5 juin 2020 à 21:35, Gaëtan Perrier  a
écrit :

> Le vendredi 05 juin 2020 à 19:22 +0200, Olivier a écrit :
> > Bonjour,
> >
> > J'ai récupéré une webcam Logitech assez ancienne.
> > Je souhaite l'utiliser sur un portable sous Buster.
> >
> > La caméra me semble bien détectée mais aucune n'est visible ni dans
> Alsa, ni
> > avec Cheese.
> > J'ai :
> >
> > [ 3106.490546] usb 5-2: USB disconnect, device number 5
> > [ 3110.874470] usb 5-1: new full-speed USB device number 6 using uhci_hcd
> > [ 3111.092529] usb 5-1: New USB device found, idVendor=046d,
> idProduct=092f,
> > bcdDevice= 0.00
> > [ 3111.092534] usb 5-1: New USB device strings: Mfr=1, Product=2,
> > SerialNumber=0
> > [ 3111.092537] usb 5-1: Product: Camera
> > [ 3111.092539] usb 5-1: Manufacturer:
> > [ 3111.097335] gspca_main: spca561-2.14.0 probing 046d:092f
> > [ 3111.154709] input: spca561 as /devices/pci:00/:00:1d.3/usb5/5-
> > 1/input/input12
> >
> > Que faire ?
> >
> > Slts
> >
>
> Salut,
>
> Ça c'est la détection USB, ça ne veut pas dire qu'ensuite un pilote a pu la
> prendre en charge. Je ne sais pas quel type de webcam c'est mais par
> exemple si
> c'est une webcam au standard UVC tu devrais avoir plus loin dans les log un
> truc de ce genre:
>
> uvcvideo: Found UVC 1.00 device Philips SPC 1300NC Webcam (0471:0331)
> uvcvideo 2-1.3:1.0: Entity type for entity Extension 5 was not initialized!
> uvcvideo 2-1.3:1.0: Entity type for entity Extension 4 was not initialized!
> uvcvideo 2-1.3:1.0: Entity type for entity Processing 3 was not
> initialized!
> uvcvideo 2-1.3:1.0: Entity type for entity Camera 1 was not initialized!
> input: Philips SPC 1300NC Webcam as
> /devices/pci:00/:00:1d.0/usb2/2-
> 1/2-1.3/2-1.3:1.0/input/input24
> usbcore: registered new interface driver uvcvideo
> USB Video Class driver (1.1.1)
>
> Gaëtan
>

Question subsidiaire:
où lire ces lignes de log (uvcvideo ...) ? avec dmesg ? dans
/var/log/syslog ?

Re: Jitsi can be built

[David Anthony]

Unsubscribe
 Please remove me from this mailing list.  Thanks

On Mon, Jun 8, 2020 at 7:23 AM John ff  wrote:

> A local member of the LUG here built jitsi from sources and he is not an
> IT professional.  From that I infer that it is possible.
>
> ⁣Sent from TypeApp ​
>
>

-- 
*David Anthony*

Church Service Missionary
33 Centerville Commons Way
Centerville, UT 84014
Cell-801-360-4 <801-709-9430>950

Re: Installation d'une webcam Logitech sur Buster

[Olivier]

Le ven. 5 juin 2020 à 20:39, Frederic MASSOT <
frede...@juliana-multimedia.com> a écrit :

> Le 05/06/2020 à 19:22, Olivier a écrit :
> > Bonjour,
> >
> > J'ai récupéré une webcam Logitech assez ancienne.
> > Je souhaite l'utiliser sur un portable sous Buster.
> >
> > La caméra me semble bien détectée mais aucune n'est visible ni dans
> > Alsa, ni avec Cheese.
> > J'ai :
> >
> > [ 3106.490546] usb 5-2: USB disconnect, device number 5
> > [ 3110.874470] usb 5-1: new full-speed USB device number 6 using uhci_hcd
> > [ 3111.092529] usb 5-1: New USB device found, idVendor=046d,
> > idProduct=092f, bcdDevice= 0.00
> > [ 3111.092534] usb 5-1: New USB device strings: Mfr=1, Product=2,
> > SerialNumber=0
> > [ 3111.092537] usb 5-1: Product: Camera
> > [ 3111.092539] usb 5-1: Manufacturer:
> > [ 3111.097335] gspca_main: spca561-2.14.0 probing 046d:092f
> > [ 3111.154709] input: spca561 as
> > /devices/pci:00/:00:1d.3/usb5/5-1/input/input12
> >
> > Que faire ?
>
>
> Que donne un lsusb -v ?
>
>
>
Bus 005 Device 002: ID 046d:092f Logitech, Inc. QuickCam Express Plus
Couldn't open device, some information will be missing
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   1.10
  bDeviceClass  255 Vendor Specific Class
  bDeviceSubClass   255 Vendor Specific Subclass
  bDeviceProtocol 0
  bMaxPacketSize0 8
  idVendor   0x046d Logitech, Inc.
  idProduct  0x092f QuickCam Express Plus
  bcdDevice0.00
  iManufacturer   1
  iProduct2
  iSerial 0

Re: Installation d'une webcam Logitech sur Buster

[Gaëtan Perrier]

Le lundi 08 juin 2020 à 20:57 +0200, Olivier a écrit :
> Le ven. 5 juin 2020 à 20:39, Frederic MASSOT  > a écrit :
> > Le 05/06/2020 à 19:22, Olivier a écrit :
> > 
> > > Bonjour,
> > 
> > > 
> > 
> > > J'ai récupéré une webcam Logitech assez ancienne.
> > 
> > > Je souhaite l'utiliser sur un portable sous Buster.
> > 
> > > 
> > 
> > > La caméra me semble bien détectée mais aucune n'est visible ni dans 
> > 
> > > Alsa, ni avec Cheese.
> > 
> > > J'ai :
> > 
> > > 
> > 
> > > [ 3106.490546] usb 5-2: USB disconnect, device number 5
> > 
> > > [ 3110.874470] usb 5-1: new full-speed USB device number 6 using uhci_hcd
> > 
> > > [ 3111.092529] usb 5-1: New USB device found, idVendor=046d, 
> > 
> > > idProduct=092f, bcdDevice= 0.00
> > 
> > > [ 3111.092534] usb 5-1: New USB device strings: Mfr=1, Product=2, 
> > 
> > > SerialNumber=0
> > 
> > > [ 3111.092537] usb 5-1: Product: Camera
> > 
> > > [ 3111.092539] usb 5-1: Manufacturer:
> > 
> > > [ 3111.097335] gspca_main: spca561-2.14.0 probing 046d:092f
> > 
> > > [ 3111.154709] input: spca561 as 
> > 
> > > /devices/pci:00/:00:1d.3/usb5/5-1/input/input12
> > 
> > > 
> > 
> > > Que faire ?
> > 
> > 
> > 
> > 
> > 
> > Que donne un lsusb -v ?
> > 
> > 
> > 
> > 
> 
> Bus 005 Device 002: ID 046d:092f Logitech, Inc. QuickCam Express Plus
> Couldn't open device, some information will be missing
> Device Descriptor:
>   bLength18
>   bDescriptorType 1
>   bcdUSB   1.10
>   bDeviceClass  255 Vendor Specific Class
>   bDeviceSubClass   255 Vendor Specific Subclass
>   bDeviceProtocol 0 
>   bMaxPacketSize0 8
>   idVendor   0x046d Logitech, Inc.
>   idProduct  0x092f QuickCam Express Plus
>   bcdDevice0.00
>   iManufacturer   1 
>   iProduct2 
>   iSerial 0 

Peux-tu mettre le résultat en entier stp ?

Gaëtan


signature.asc
Description: This is a digitally signed message part

Re: Installation d'une webcam Logitech sur Buster

[Gaëtan Perrier]

Non. Je ne l'ai pas non plus.

Gaêtan

Le lundi 08 juin 2020 à 20:56 +0200, Olivier a écrit :
> Le paquet uvccapture n'est pas installé sur ma machine.
> Ce paquet est-il nécessaire ?
> 
> Le ven. 5 juin 2020 à 21:35, Gaëtan Perrier  a
> écrit :
> > Le vendredi 05 juin 2020 à 19:22 +0200, Olivier a écrit :
> > 
> > > Bonjour,
> > 
> > > 
> > 
> > > J'ai récupéré une webcam Logitech assez ancienne.
> > 
> > > Je souhaite l'utiliser sur un portable sous Buster.
> > 
> > > 
> > 
> > > La caméra me semble bien détectée mais aucune n'est visible ni dans Alsa,
> > ni
> > 
> > > avec Cheese.
> > 
> > > J'ai :
> > 
> > > 
> > 
> > > [ 3106.490546] usb 5-2: USB disconnect, device number 5
> > 
> > > [ 3110.874470] usb 5-1: new full-speed USB device number 6 using uhci_hcd
> > 
> > > [ 3111.092529] usb 5-1: New USB device found, idVendor=046d,
> > idProduct=092f,
> > 
> > > bcdDevice= 0.00
> > 
> > > [ 3111.092534] usb 5-1: New USB device strings: Mfr=1, Product=2,
> > 
> > > SerialNumber=0
> > 
> > > [ 3111.092537] usb 5-1: Product: Camera
> > 
> > > [ 3111.092539] usb 5-1: Manufacturer: 
> > 
> > > [ 3111.097335] gspca_main: spca561-2.14.0 probing 046d:092f
> > 
> > > [ 3111.154709] input: spca561 as /devices/pci:00/:00:1d.3/usb5/5-
> > 
> > > 1/input/input12
> > 
> > > 
> > 
> > > Que faire ?
> > 
> > > 
> > 
> > > Slts
> > 
> > > 
> > 
> > 
> > 
> > Salut,
> > 
> > 
> > 
> > Ça c'est la détection USB, ça ne veut pas dire qu'ensuite un pilote a pu la
> > 
> > prendre en charge. Je ne sais pas quel type de webcam c'est mais par
> > exemple si
> > 
> > c'est une webcam au standard UVC tu devrais avoir plus loin dans les log un
> > 
> > truc de ce genre:
> > 
> > 
> > 
> > uvcvideo: Found UVC 1.00 device Philips SPC 1300NC Webcam (0471:0331)
> > 
> > uvcvideo 2-1.3:1.0: Entity type for entity Extension 5 was not initialized!
> > 
> > uvcvideo 2-1.3:1.0: Entity type for entity Extension 4 was not initialized!
> > 
> > uvcvideo 2-1.3:1.0: Entity type for entity Processing 3 was not
> > initialized!
> > 
> > uvcvideo 2-1.3:1.0: Entity type for entity Camera 1 was not initialized!
> > 
> > input: Philips SPC 1300NC Webcam as
> > /devices/pci:00/:00:1d.0/usb2/2-
> > 
> > 1/2-1.3/2-1.3:1.0/input/input24
> > 
> > usbcore: registered new interface driver uvcvideo
> > 
> > USB Video Class driver (1.1.1)
> > 
> > 
> > 
> > Gaëtan
> > 
> 
> 



signature.asc
Description: This is a digitally signed message part

Re: Jitsi can be built

[David Wright]

On Mon 08 Jun 2020 at 20:02:38 (+0300), Reco wrote:
> On Mon, Jun 08, 2020 at 06:25:57PM +0200, to...@tuxteam.de wrote:
> > On Mon, Jun 08, 2020 at 05:28:06PM +0300, Reco wrote:
> > > On Mon, Jun 08, 2020 at 02:17:27PM +0100, John ff wrote:
> > > > A local member of the LUG here built jitsi from sources and he is not
> > > > an IT professional.  From that I infer that it is possible.
> > > 
> > > I will assume
> >  ^^
> > Aha.
> 
> OP lacked the details, it's all we can do - to assume and to guess.

I agree. And where's the evidence that the OP used to infer anything.

> > And saying that "non-professionals" (what's this, anyway?) can't do
> > this is downright wrong.

[I'm assuming that the OP mother-tongue is English.]

Saying "and he is not an IT professional" like that
carries the implication that it's really not difficult.

Cheers,
David.

Re: Return a Debian system to a pristine state

[David Wright]

On Fri 05 Jun 2020 at 13:04:08 (+0200), Marco Möller wrote:
> On 04.06.20 21:46, The Wanderer wrote:
> > On 2020-06-04 at 10:30, David Wright wrote:
> > > On Mon 01 Jun 2020 at 12:15:02 (+0200), Marco Möller wrote:
> > 
> > > > The short answer to this thread is that unfortunately Debian is
> > > > not prepared with a simple solution for this simple task, but
> > > > sophisticated workarounds are needed.
> > > 
> > > As has been explained, it's not so simple, because *your* focus is
> > > solely on the last apt command that you typed, whereas the package
> > > management system is concerned with the whole system. Apt deals with
> > > the system as a current state, and not as a chance sequence of
> > > commands in reaching that state which must be reversible and
> > > replayable, back and forth.
> > > 
> > > When you install some packages and change your mind, just copy and
> > > paste the line from /var/log/apt/history.log, replacing install with
> > > remove (or purge). Sophisticated?
> > 
> > Doesn't that fail to address the exact Recommends-related scenario which
> > was his original complaint?

Yes, sorry, I should have added the packages in the next line too
(which involves a little more deletion of extraneous matter).

[snipped example]

> Thank You! You perfectly understood me and put it into clear words.
> 
> 
> > He appears to argue (if not all that clearly) that the package manager
> > should be tracking "install Recommends?" status on a per-package basis
> > (i.e., probably in /var/lib/dpkg/status), such that only packages for
> > which that flag is true will be considered as preventing a Recommended
> > package from being autoremoved, even when Recommends are configured to
> > be important. This would then let those two scenarios produce the same
> > result, which could be argued to be valuable for "least surprise"
> > consistency reasons.

Well, it might be the least surprise for someone who has just
installed a package that comes with a number of Recommends, and
then removes it straight afterwards. But it's not least surprise
for someone who's actually concerned about the current state of
the whole package list, and the "top-level" package being removed
has been installed for a longer period.

> > Given the existence of the ability to configure Suggests as important,
> > presumably an analogous flag would then need to be tracked per-package
> > for Suggests as well.
> > 
> > Structurally this doesn't even seem too difficult to design, at a naive
> > outsider's glance, but how practical it would be to implement - both in
> > terms of code, and in terms of the data that would have to be tracked
> > and stored, as well as in terms of implementing both on top of the
> > existing stored data which does not track this - may be quite another
> > story.

[snipped more complex example]

> > I don't see as simple or straightforward a way to design around that
> > problem. At that point, I think you would indeed have to start tracking
> > the installation history in tree fashion, and I don't even know what the
> > data structures or the necessary stored data for handling that elegantly
> > or cleanly would need to look like.
> 
> Because of this more complex scenario I suspected that not simply a
> flag might suffice and therefore suggested that a tracking list would
> be needed for registering exactly by WHICH other package a certain
> package became recommended and drawn in. This list would get longer if
> more than one package would have asked for the recommended, certain
> package, and if this certain package specific list would result empty
> again then this would flag it for allowed autoremoval. Of course the
> certain package should not be an essential package like installed
> during the intial Debian installation, but this requirement is what
> the current apt is already considering for all packages anyway.
> 
> After your post nicely confirmed that my idea was perfectly
> understood, I will leave it here in the thread as it is. In the near
> future I will organize my words, probably copying some of the
> statements from this thread, and send it as a feature request to the
> apt developers. I think there is not more which we can do as simple
> users at this point.

I don't think a reply loaded with "would"s confirms that it's
perfectly understood at all.

On Sat 06 Jun 2020 at 12:36:51 (+0300), Andrei POPESCU wrote:
> 
> Something that should be much easier to implement would be for the 
> Debian Installer to save a list of installed packages and auto/manual 
> state (maybe also versions, just for good measure) after finishing the 
> installation.
> 
> That would provide a good base to create a "remove everything I 
> installed since" script.

Well, Marco is keen to file a severe bug; perhaps a wishlist item will
suffice instead. Ironically, the d-i already stores a copy of the
status file, but it's the one for the d-i itself, rather than the one
for the /target system.

For those who want this 

Re: Return a Debian system to a pristine state

[David Wright]

On Sat 06 Jun 2020 at 12:24:51 (+0300), Andrei POPESCU wrote:
> On Jo, 04 iun 20, 09:32:48, David Wright wrote:
> > On Sun 31 May 2020 at 18:43:46 (+0100), Michael Howard wrote:
> > > 
> > > Well then it's not pristine, which is what the OP wanted.
> > 
> > That begs the question of what pristine means, because it has never
> > been defined even by the OP. Their closest attempt at a definition
> > was the "first boot experience" but, unless you install a system as
> > soon as a release is released, you can't return to that configuration
> > without downgrading packages. That would make no sense at all,
> > especially for someone with a serious concern about scanning for
> > vulnerabilities.
> 
> I don't recall anyone in the thread asking for exact versions at the 
> time of installation, just the same package set.
> 
> This would also require exceptions for ABI changes (libfoo1 replaced by 
> libfoo2 or linux-image-x.y.z-1-amd64 replaced by 
> linux-image-x.y.z-2-amd64). These should be rare on stable + 
> stable-security and can be handled with the manual/auto installed 
> mechanism.

I'm quite happy to accept that. As I run stable, I'm unlikely to run
into complications concerning versions, but those running newer suites
might have that problem where the functionality of a group of packages
gets refactorised, so that some versions of A might break other versions
of B.

So the OP is happy with defining "pristine" as the original package
set, and has realised that their life would have been made easier if
they'd made a timely record. Or made a backup, in which case they
could just grep /var/lib/dpkg/status.

If they didn't, they might have to rely on the method I outlined to
Marco (which The Wanderer corrected), using apt's history.log file.

I did try out returning a system to its initial state, admittedly
under favourable circumstances. After installing with the d-i, there
were 531 packages installed. I ran my usual script that installs
"all the rest" of my typical system, requesting 287 packages and,
with their Depends and Recommends, installing about 2050.

I then tac'd my script, edited all the installs to removes, and ran
it. As it progressed, the proffered list of suggestions for
autoremoval got longer and longer, so that by the time the script
was finished, a simple autoremove command wiped out 885 packages.

The system still had plenty of Recommends left installed, as one would
expect, so I diff'd the list of post-installer packages with the
current version to produce a 495-package purge command. (Because I
had removed rather than purged packages, there were plenty of
"rc"-status packages still installed, as well as the Recommends.
That script removed virtually all the packages I had installed myself.

I write "virtually" because, as I was doing all this casually,
I had to reinstall aptitude twice (along with its Depends and
Recommends) in order to run its "why" command, so I ended up
with those extra packages still installed.

I was impressed by apt-get's performance, probably because of dim
memories of how dpkg would react on being asked to install ~2000
packages at once. The latter doesn't have the logic for sorting
operations into a sequence that preserves an unbroken system.

Cheers,
David.

Re: actualizar youtube-dl de Buster a Bullseye en estable.

[JavierDebian]

El 7/6/20 a las 12:17, Rupert escribió:

Buen día,
La version de youtube-dl disponible en Buster, 2019.01.17-1.1,  parece
estar corrupta/dañada ya que al intentar utilizarla recibía este
mensaje de error: "youtube says: video not available" trate de
actualizarla via via el comando "youtube-dl -U" pero recibí este
error:"youtube-dl: error: youtube-dl's self-update mechanism is
disabled on Debian. Please update youtube-dl using apt(8). See
https://packages.debian.org/sid/youtube-dl for the latest packaged
version." Al intentar con apt resultó que la version instalada era la
mas reciente por lo que descargué la version disponible en
Bullseye, 2020.05.08-1, en su formato .deb, lo instalé,
afortunadamente sin errores, tampoco fue modificado/actualizado
ningún otro paquete y el archivo sources.list no sufrió
modificación alguna. Por lo que me pregunto si es posible que la versión
del paquete youtube-dl de Bullseye sea incluido como una actualización
regular via apt-update && upgrade en Buster? No se si esto sea
posible y/o recomendable o si se aplica a los procedimientos
para incluir nuevos paquetes en estable, en todo caso, la
version de youtube-dl en Buster no funciona correctamente y
debe ser reparada/actualizada.
Version de Debian: 10.4 (Buster/Stable)
paquete: youtube-dl
version: 2019.01.17-1.1
síntoma: No funciona correctamente y al intentar
utilizarla devuelve el siguiente mensaje de error: "youtube says:video
not available"
sugerencia: actualizar youtube-dl a la version disponible en
Bullseye, 2020.05.08-1 la cual funciona sin problema alguno.

NOTA: Ya que esta es mi primera vez usando este servicio
espero haberlo conforme a los lineamientos para el mismo.




Agrega el repositorio

deb https://www.deb-multimedia.org buster main non-free

(Sigue las instrucciones de aquí)

Actualiza  youtube-dl con todas las librerías que le dependen.

Se solucionan los problemas de multimedia en todo.

JAP

Re: Installation d'une webcam Logitech sur Buster

[Gaëtan Perrier]

Le lundi 08 juin 2020 à 20:59 +0200, Olivier a écrit :
> 
> 
> Le ven. 5 juin 2020 à 21:35, Gaëtan Perrier  a
> écrit :
> > Le vendredi 05 juin 2020 à 19:22 +0200, Olivier a écrit :
> > 
> > > Bonjour,
> > 
> > > 
> > 
> > > J'ai récupéré une webcam Logitech assez ancienne.
> > 
> > > Je souhaite l'utiliser sur un portable sous Buster.
> > 
> > > 
> > 
> > > La caméra me semble bien détectée mais aucune n'est visible ni dans Alsa,
> > ni
> > 
> > > avec Cheese.
> > 
> > > J'ai :
> > 
> > > 
> > 
> > > [ 3106.490546] usb 5-2: USB disconnect, device number 5
> > 
> > > [ 3110.874470] usb 5-1: new full-speed USB device number 6 using uhci_hcd
> > 
> > > [ 3111.092529] usb 5-1: New USB device found, idVendor=046d,
> > idProduct=092f,
> > 
> > > bcdDevice= 0.00
> > 
> > > [ 3111.092534] usb 5-1: New USB device strings: Mfr=1, Product=2,
> > 
> > > SerialNumber=0
> > 
> > > [ 3111.092537] usb 5-1: Product: Camera
> > 
> > > [ 3111.092539] usb 5-1: Manufacturer: 
> > 
> > > [ 3111.097335] gspca_main: spca561-2.14.0 probing 046d:092f
> > 
> > > [ 3111.154709] input: spca561 as /devices/pci:00/:00:1d.3/usb5/5-
> > 
> > > 1/input/input12
> > 
> > > 
> > 
> > > Que faire ?
> > 
> > > 
> > 
> > > Slts
> > 
> > > 
> > 
> > 
> > 
> > Salut,
> > 
> > 
> > 
> > Ça c'est la détection USB, ça ne veut pas dire qu'ensuite un pilote a pu la
> > 
> > prendre en charge. Je ne sais pas quel type de webcam c'est mais par
> > exemple si
> > 
> > c'est une webcam au standard UVC tu devrais avoir plus loin dans les log un
> > 
> > truc de ce genre:
> > 
> > 
> > 
> > uvcvideo: Found UVC 1.00 device Philips SPC 1300NC Webcam (0471:0331)
> > 
> > uvcvideo 2-1.3:1.0: Entity type for entity Extension 5 was not initialized!
> > 
> > uvcvideo 2-1.3:1.0: Entity type for entity Extension 4 was not initialized!
> > 
> > uvcvideo 2-1.3:1.0: Entity type for entity Processing 3 was not
> > initialized!
> > 
> > uvcvideo 2-1.3:1.0: Entity type for entity Camera 1 was not initialized!
> > 
> > input: Philips SPC 1300NC Webcam as
> > /devices/pci:00/:00:1d.0/usb2/2-
> > 
> > 1/2-1.3/2-1.3:1.0/input/input24
> > 
> > usbcore: registered new interface driver uvcvideo
> > 
> > USB Video Class driver (1.1.1)
> > 
> > 
> > 
> > Gaëtan
> 
> Question subsidiaire: 
> où lire ces lignes de log (uvcvideo ...) ? avec dmesg ? dans  /var/log/syslog
> ?
> 
> 

Dans /var/log/messages

Gaëtan


signature.asc
Description: This is a digitally signed message part

Re: consulta X-Forwarded-For de Apache

[Camaleón]

El 2020-06-08 a las 12:17 +0200, miguel angel gonzalez escribió:

(...)

> @camaleon:
> ¿No sería más conveniente guardar la IP del cliente y la de los
> proxies, y procesar/filtrar después ese registro para que te muestre
> sólo la IP que quieres?
> 
> Pues si no encuentro otra solución va a ser la opción.

Por aquí¹ indican esa vía pero sobre un servidor Nginx, quizá te dé 
alguna pista. Básicamente proponen hacer un «grep» de la variable que 
contiene las IP en formato de lista separada por comas y mapear la 
nueva variable al log combinado con el resultado de la extracción.

> Sigo buscando porque la opción que comentas de «%h» por «%a» la probé y no
> es exactamente lo que busco.

El tutorial que has seguido lo que permite es que la IP del cliente se 
registre tembién en el log de Apache, y eso es precisamente lo que has 
conseguido... pero no es lo que buscabas :-)

¹ 

Saludos,

-- 
Camaleón 

How long will this take?

[Matthew Campbell]

I bought a new 4 terrabyte hard drive that is connected with a USB cable using 
USB2. It took about 32 hours to read every sector on the drive to look for bad 
sectors. I started blanking the sectors using /dev/zero last Friday night. It 
still isn't done. Is there a way I can find out how much data a particular 
process has written to the disk? I'm using Debian 10.4.

dd if=/dev/zero of=/dev/sdb ibs=4096 count=976754646

name=Matthew%20Campbell=trenix25%40pm.me

Re: How long will this take?

[deloptes]

Dan Ritter wrote:

> USB2 disks are good for about 25MB/s.
> 

Where do you have those numbers?

USB 2.0 standard can theoretically transfer data at a very high 480 megabits
per second (mbps), or 60 megabytes per second (MBps) [for example in
wikipedia).

but as you say it is slowing down at some point. It is not working at max
anyway - some people say it will not increase above 20MB/s anyway.

I suggest add  to dd   status=progress

  The LEVEL of information to print to stderr; 'none' suppresses
everything but error messages, 'noxfer' suppresses the final transfer sta-
  tistics, 'progress' shows periodic transfer statistics

And honestly I do not think 4TB disks were meant to be used via USB2 - think
of using eSATA.

Re: How long will this take?

[Nicolas George]

Matthew Campbell (12020-06-08):
> Is that in bytes?

You can compare with the stats presented by USR1 to be sure.

> stdin and stderr both show a position of zero.

You can look in /proc/$PID/fd to see where the various fd points. I
guess 0 will point to /dev/zero, 1 to the hard drive and 2 to the tty.

Regards,

-- 
  Nicolas George


signature.asc
Description: PGP signature

Re: USB HDD issue with buster-backports kernel

[Christopher David Howie]

On 6/8/2020 10:56 AM, Christopher David Howie wrote:
> * On the 5.5 kernel, I was getting throughput between 10MB/sec and 
> 20MB/sec.  At apparently random points, dd would stop reporting any 
> progress and a "usb-storage" process in top would be consuming 100%
> CPU. Any commands against the HDD (even smartctl) would hang until
> the device was physically replugged.
Also, I should mention: I only got this behavior when using the crypt
container.  If I ran dd with /dev/urandom against the raw partition, the
throughput was much closer to 30MB/sec and the device never stopped
responding.

-- 
Chris Howie
http://www.chrishowie.com
http://en.wikipedia.org/wiki/User:Crazycomputers

If you correspond with me on a regular basis, please read this document:
http://www.chrishowie.com/email-preferences/

PGP fingerprint: 2B7A B280 8B12 21CC 260A DF65 6FCE 505A CF83 38F5


IMPORTANT INFORMATION/DISCLAIMER

This document should be read only by those persons to whom it is
addressed.  If you have received this message it was obviously addressed
to you and therefore you can read it.

Additionally, by sending an email to ANY of my addresses or to ANY
mailing lists to which I am subscribed, whether intentionally or
accidentally, you are agreeing that I am "the intended recipient," and
that I may do whatever I wish with the contents of any message received
from you, unless a pre-existing agreement prohibits me from so doing.

This overrides any disclaimer or statement of confidentiality that may
be included on your message.

Re: How long will this take?

[Matthew Campbell]

# cat /proc/24283/fdinfo/1
pos: 877106917376
flags: 011
mnt_id: 21
#

Is that in bytes?

stdin and stderr both show a position of zero.

name=Matthew%20Campbell=trenix25%40pm.me

 Original Message 
On Jun 8, 2020, 1:32 PM, Nicolas George wrote:

> Matthew Campbell (12020-06-08): > I bought a new 4 terrabyte hard drive that 
> is connected with a USB > cable using USB2. It took about 32 hours to read 
> every sector on the > drive to look for bad sectors. I started blanking the 
> sectors using > /dev/zero last Friday night. It still isn't done. Is there a 
> way I can > find out how much data a particular process has written to the 
> disk? > I'm using Debian 10.4. Sending a USR1 signal to a running 'dd' 
> process makes it print I/O sta‐ tistics to standard error and then resume 
> copying. Fron dd(1). Also, you can go read /proc/$(pidof dd)/fdinfo, it 
> contains the information too. Note that it becomes much slower as it nears 
> the center of the disk. Regards, -- Nicolas George

Re: Zoom- best practice?

[Tom Dial]

On 6/7/20 14:14, Russell L. Harris wrote:
> On Sun, Jun 07, 2020 at 03:56:17PM -0400, The Wanderer wrote:
>> Yeah, but that's not building Jitsi; that's installing a prebuilt Jitsi,
>> as shipped in those packages.
>>
>> Presumably, as those packages are for download from the authors'
>> Website, the authors are the ones who built them. Thus, this doesn't
>> demonstrate that anyone other than the authors have been able to build
>> Jitsi.
> 
> So? It is an open-source alternative to Zoom, and it works.  Of
> course, if you are worried that the builders put in something
> malicious or dangerous which is not in the open source repository,
> then you can turn to Zoom, or build your own, or do without...
> 
> Though objectivity is prudent, we ought be promoting alternatives to
> Zoom, rather than torpedoing them.

If you cannot build an executable from source, you do not know whether
the binary you downloaded represents the source faithfully. Even if you
have the source, it would take great effort and use of some fairly
esoteric tools to verify that the product is what it says it is, and
does what it says it does (and no more).

As I understand, that is a primary goal of Debian's fairly extensive
effort to ensure that builds for its packages are reproducible.


Building from source is not the only requisite for such assurance,
however. Ken Thompson's ACM Turing Award lecture, "Reflections on
Trusting Trust" [1] is an interesting take on this aspect of security.


Free (or even open source) is a good software characteristic, but it is
not the only one that counts, or even the most important one. Sometimes,
as it may be with Zoom, a closed source commercial product is better
than free alternatives. Even where that is not so such a product may, as
Zoom is, be so much more widely used that it is much more useful as a
general matter.

Regards
Tom Dial

[1] https://dl.acm.org/doi/10.1145/358198.358210

> 
> RLH

Re: How long will this take?

[Dan Ritter]

deloptes wrote: 
> Dan Ritter wrote:
> 
> > USB2 disks are good for about 25MB/s.
> > 
> 
> Where do you have those numbers?
> 
> USB 2.0 standard can theoretically transfer data at a very high 480 megabits
> per second (mbps), or 60 megabytes per second (MBps) [for example in
> wikipedia).

Yes, that's the theory. In years of running several USB 2.0
attached disks, I found that they were actually good for about
25MB/s long-term. Bursts to 37MB/s were not uncommon.

The USB mass storage protocol forces a queue depth of 1: one
request, one response, nothing else until it's done. 

The OP's 4K writes will be particularly badly performing.

-dsr-

Re: Why do I have so many packages to upgrade with Debian 10.4?

[l0f4r0]

Hi,

Thank you  all (with delay) for your answers.

11 mai 2020 à 19:49 de didier.gau...@gmail.com:

> Le 11/05/2020 à 19:12, l0f...@tuta.io a écrit :
>
>> Isn't proposed-updates designed to containing packages that should reach 
>> stable-updates afterward?
>>
> from what I understand (perhaps wrongly) from the above link, no, it
> would mean that stable-proposed-updates packages are bugfixes to be
> included in stable at the next point release date"...
>
> stable-updates contains bugfixes that cannot wait next point release:
> https://wiki.debian.org/SourcesList
>
11 mai 2020 à 23:10 de deb...@lionunicorn.co.uk:

> I think the intention is that proposed-updates is for software fixes
> that need testing before being accepted into stable, whereas
> stable-updates is for updates in information like virus patterns,
> dates when clocks change, and so on, that can go straight in.
> So most 'ornery' people will follow the latter but not the former.
>
I think we can summarize this way:
* stable: contains packages for new releases (10 currently) and new point 
releases (10.4 currently)
* stable/updates: security updates, some(/all?) of them are incorporated into 
stable-proposed-updates
* stable-proposed-updates: packages (bugfixes + SECURITY patches) that are 
being prepared for the next point release, some of them are incorporated into 
stable-updates
* stable-updates: urgent fixes

In other words, stable + stable/updates + stable-updates should be sufficient 
generally.
stable-proposed-updates offers packages for people who want to be ahead of 
point release schedule (beware of the quality as it's not fully stable yet).

Debian Wiki contains an instructive diagram: 
https://wiki.debian.org/DebianReleases

So to answer my own question, I think indeed that all the new packages I saw on 
my screen were those of stable-proposed-updates discharged into stable (that 
were not security packages nor urgent ones) + maybe some latest packages from 
stable/updates and stable-updates that were just released around the same time.

12 mai 2020 à 09:25 de andreimpope...@gmail.com:

> Nothing unusual. You also have i386 packages installed so this will also
> increase the number of updates.
>
Good catch! :)

Best regards,
l0f4r0

Re: How long will this take?

[Dan Ritter]

Matthew Campbell wrote: 
> I bought a new 4 terrabyte hard drive that is connected with a USB cable 
> using USB2. It took about 32 hours to read every sector on the drive to look 
> for bad sectors. I started blanking the sectors using /dev/zero last Friday 
> night. It still isn't done. Is there a way I can find out how much data a 
> particular process has written to the disk? I'm using Debian 10.4.
> 
> dd if=/dev/zero of=/dev/sdb ibs=4096 count=976754646

USB2 disks are good for about 25MB/s.

4 seconds gets you 100MB.

40 seconds gets you 1000MB.

4000 * 40 seconds is 16 seconds, so that's not quite two
days.

Is something wrong? Based on current news reports, I would say
you accidentally purchased an SMR disk. (By accidentally, I mean
that the box didn't say, the ad didn't say, and the manufacturer
might even have lied to you for a while.)

https://www.ixsystems.com/community/resources/list-of-known-smr-drives.141/

Is it one of those?

If so, return it. Tell the store that it's an unlabelled SMR
drive. They'll take it back.

-dsr-

Re: How long will this take?

[Nicolas George]

Matthew Campbell (12020-06-08):
> I bought a new 4 terrabyte hard drive that is connected with a USB
> cable using USB2. It took about 32 hours to read every sector on the
> drive to look for bad sectors. I started blanking the sectors using
> /dev/zero last Friday night. It still isn't done. Is there a way I can
> find out how much data a particular process has written to the disk?
> I'm using Debian 10.4.

   Sending a USR1 signal to a running 'dd' process makes it print I/O sta‐
   tistics to standard error and then resume copying.

Fron dd(1).

Also, you can go read /proc/$(pidof dd)/fdinfo, it contains the
information too.

Note that it becomes much slower as it nears the center of the disk.

Regards,

-- 
  Nicolas George


signature.asc
Description: PGP signature

re: How long will this take?

[Jude DaShiell]

Does any optimal formula exist based on hard drive size which minimizes
time needed for checking and blanking hard drives in connection with the
block size value?



--

Re: How long will this take?

[Christopher David Howie]

On 6/8/2020 11:01 PM, David Wright wrote:

I, too, determine progress with
# kill -USR1 


I'd suggest simply adding "status=progress" which gives you a summary 
every second including bytes written, elapsed time, and average transfer 
rate.


--
Chris Howie
http://www.chrishowie.com
http://en.wikipedia.org/wiki/User:Crazycomputers

If you correspond with me on a regular basis, please read this document: 
http://www.chrishowie.com/email-preferences/


PGP fingerprint: 2B7A B280 8B12 21CC 260A DF65 6FCE 505A CF83 38F5


IMPORTANT INFORMATION/DISCLAIMER

This document should be read only by those persons to whom it is 
addressed.  If you have received this message it was obviously addressed 
to you and therefore you can read it.


Additionally, by sending an email to ANY of my addresses or to ANY 
mailing lists to which I am subscribed, whether intentionally or 
accidentally, you are agreeing that I am "the intended recipient," and 
that I may do whatever I wish with the contents of any message received 
from you, unless a pre-existing agreement prohibits me from so doing.


This overrides any disclaimer or statement of confidentiality that may 
be included on your message.

Re: actualizar youtube-dl de Buster a Bullseye en estable.

[Germán Avendaño Ramírez]

JavierDebian writes:

> Agrega el repositorio
>
> deb https://www.deb-multimedia.org buster main non-free
>
> (Sigue las instrucciones de aquí)
>
> Actualiza  youtube-dl con todas las librerías que le dependen.
>
> Se solucionan los problemas de multimedia en todo.
>
> JAP

Se puede instalar youtube-dl usando las instrucciones de la página del
proyecto. Aquí también se dan instrucciones para usar pip (python)

Instrucciones https://ytdl-org.github.io/youtube-dl/download.html

Atentamente,

-- 
Germán Avendaño Ramírez
Lic. Mat. U.D., M.Sc. U.N

Re: Debian rolling release

[paulo . p . oliveira]

Exacto. É o quanto basta.Em 08/06/2020 11:35 da tarde, riesdra  escreveu:Olá, me tirem uma duvida, hoje uso debian bullseye, se eu mudar o sources para testing, terei um sistema rolling release.É necessário fazer algo mais? Ou isto não é possível?desde já agradeço a atenção de todos.--Ricardo Libanio

Re: How long will this take?

[Dan Ritter]

Jude DaShiell wrote: 
> Does any optimal formula exist based on hard drive size which minimizes
> time needed for checking and blanking hard drives in connection with the
> block size value?

If the disk firmware offers it, a SMART long read/verify test
should be close to optimal. Consult smartctl and the disk manufacturer
for details.

For conventional spinning hard disks, the optimal write size would be
a complete cylinder at a time. That varies across the radius of the disk,
and may not be made available to the OS. 

In lieue of knowing that, writes which are reasonable integer
multiples of the sector size are very good. 1 MB is probably
good for most drives.

For SMR spinning disks,the optimal write size is one complete
write zone. I've heard that this is standardizing at 256MB, but
I would want to confirm with the manufacturer. There are a lot
of interactions with PMR caches. 

For SSD, writing wears out the storage mechanism. A write-all
test won't test reliability; flaws will be detected and remapped
without letting the host know.

-dsr-

Trouble with 2011 iMac Sound Card On Debian

[Keifer Bly]

Hi all,

So I installed Debian on a 2011 iMac and it is working ok, except for the
sound. There is no sound from either the speaker or the headphone jack.

When I go to the system settings, the volum option is completely greyed out.

Running cat /proc/asound/cards in UXTerm returned this:

0  [PCH ]:HDA-Intel - HDA Intel PCH
   HDA Intel PCH at 0xa890 irq 47
1 [HDMI]: HDA-Intel - HDA ATI HDMI
HDA ATI HDMI at 0xa884 irq 48

I am wondering why the speaker and headphone jack would not work when the
sound card is recognized? Thanks very much.

[image: debian sund card info.PNG]
--Keifer


Virus-free.
www.avast.com

<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

Re: Debian rolling release

[Leandro Guimarães Faria Corcete DUTRA]

Le lundi 08 juin 2020 à 20:35 -0300, riesdra a écrit :
> hoje uso debian bullseye, se eu mudar o sources para testing, terei
> um sistema rolling release.

Por aí.


> É necessário fazer algo mais?

Claro que precisará duma atualização do bullseye para testing.  O
mais prudente seria seguir o manual.


-- 
/¯\ skype:leandro.gfc.dutra?chat  Yahoo!: ymsgr:sendIM?lgcdutra
\ / +55 (61) 3546 7191 xmpp:leand...@jabber.org
 X  +55 (61) 99302 2691   ICQ/AIM: aim:GoIM?screenname=61287803
/ \ BRAZIL GMT−3  https://useplaintext.email/#why-plaintext

Debian rolling release

[riesdra]

Olá, me tirem uma duvida, hoje uso debian bullseye, se eu mudar o sources para 
testing, terei um sistema rolling release.

É necessário fazer algo mais? Ou isto não é possível?



desde já agradeço a atenção de todos.


--
Ricardo Libanio

Re: Debian rolling release

[Daniel Lenharo de Souza]

Olá

Em 08/06/2020 20:35, riesdra escreveu:
> Olá, me tirem uma duvida, hoje uso debian bullseye, se eu mudar o sources 
> para testing, terei um 
sistema rolling release.
> É necessário fazer algo mais? Ou isto não é possível?
> 

Debian não é rolling release. O mais perto que poderia se chegar é utilizando a 
versão SID, mas mesmo 
assim não será uma rolling release

-- 
Daniel Lenharo de Souza
Curitiba - Brasil



signature.asc
Description: OpenPGP digital signature

Re: How long will this take?

[Jude DaShiell]

People are suing Western Digital for sneaking those SMR disks into their
supply chain.  They're supposed to be red in color if what I read in the
news is correct.

On Mon, 8 Jun 2020, Dan Ritter wrote:

> Date: Mon, 8 Jun 2020 16:33:29
> From: Dan Ritter 
> To: Matthew Campbell 
> Cc: Debian User Support 
> Subject: Re: How long will this take?
> Resent-Date: Mon,  8 Jun 2020 20:33:43 + (UTC)
> Resent-From: debian-user@lists.debian.org
>
> Matthew Campbell wrote:
> > I bought a new 4 terrabyte hard drive that is connected with a USB cable 
> > using USB2. It took about 32 hours to read every sector on the drive to 
> > look for bad sectors. I started blanking the sectors using /dev/zero last 
> > Friday night. It still isn't done. Is there a way I can find out how much 
> > data a particular process has written to the disk? I'm using Debian 10.4.
> >
> > dd if=/dev/zero of=/dev/sdb ibs=4096 count=976754646
>
> USB2 disks are good for about 25MB/s.
>
> 4 seconds gets you 100MB.
>
> 40 seconds gets you 1000MB.
>
> 4000 * 40 seconds is 16 seconds, so that's not quite two
> days.
>
> Is something wrong? Based on current news reports, I would say
> you accidentally purchased an SMR disk. (By accidentally, I mean
> that the box didn't say, the ad didn't say, and the manufacturer
> might even have lied to you for a while.)
>
> https://www.ixsystems.com/community/resources/list-of-known-smr-drives.141/
>
> Is it one of those?
>
> If so, return it. Tell the store that it's an unlabelled SMR
> drive. They'll take it back.
>
> -dsr-
>
>

-- 

Re: How long will this take?

[David Wright]

On Mon 08 Jun 2020 at 20:22:39 (+), Matthew Campbell wrote:
> I bought a new 4 terrabyte hard drive that is connected with a USB cable 
> using USB2. It took about 32 hours to read every sector on the drive to look 
> for bad sectors.

I recently ran

# badblocks -c 1024 -s -w -t random -v /dev/sdz

on a 2TB disk with a USB2 connection. The whole process, writing and
checking, took 33⅓ hours. (The disk now holds an encrypted ext4 filesystem.)

> I started blanking the sectors using /dev/zero last Friday night. It still 
> isn't done. Is there a way I can find out how much data a particular process 
> has written to the disk? I'm using Debian 10.4.

I'm not sure why you'd do that. I've only zeroed disks to erase them
before I return them to the owner. (They're inside loaned computers.)

> dd if=/dev/zero of=/dev/sdb ibs=4096 count=976754646

… And I'd be using bs=1M and no count. I, too, determine progress with
# kill -USR1 

Cheers,
David.