low density, low visibility default vtty fonts /during/ installation

2019-11-21 Thread Felix Miata
Unlike non-Debian distros like Fedora, Mageia and openSUSE, which during init 
and
continuing afterward, all Debians I've used configure a font for vttys that
differs from the nice weighty high visibility font compiled into the kernels. I
know how to reverse this with dkpg-reconfigure console-setup for installed
systems. What can I put on kernel cmdline to block this switchover to low
visibility fonts from happening in text mode installation environments?

Live Clonezilla is an easier test for this than Debian installation media, since
it allows access to a multi-vtty environment relatively quickly. Clonezilla
apparently tries to mitigate by using a bigger font, but it too is ugly low
density hard-to-see, which if configures via live_console_font_size=16x32 on 
cmdline.
-- 
Evolution as taught in public schools is religion, not science.

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/



Re : [testing] problème détection frappe clavier

2019-11-21 Thread nicolas . patrois
Le 22/11/2019 01:01:27, Gaëtan Perrier a écrit :

> Bonjour,

> Depuis quelques temps j'ai des problèmes de détection de frappes de
> certaines touches, notamment les touches accentuées ou utilisant SHIFT ou ALT
> GR.
> Je ne sais pas comment vérifier si c'est un problème du clavier
> lui-même ou si c'est ma debian qui est en cause.
> Déjà une piste serait de savoir si je suis le seul à rencontrer ce
> problème ou non?

Chez moi, quand je tape « bonjour » alors que l’ordinateur rame, je vois 
parfois « bnojruo ».
Je me demande si je n’ai pas le même problème de détection des touches, j’y 
ferai attention.
Je pense que c’est depuis qu’IBus est installé.

nicolas patrois : pts noir asocial
-- 
RÉALISME

M : Qu'est-ce qu'il nous faudrait pour qu'on nous considère comme des humains ? 
Un cerveau plus gros ?
P : Non... Une carte bleue suffirait...



Re: [testing] problème détection frappe clavier

2019-11-21 Thread Sébastien Dinot
Gaëtan Perrier a écrit :
> Depuis quelques temps j'ai des problèmes de détection de frappes de
> certaines touches, notamment les touches accentuées ou utilisant SHIFT
> ou ALT GR. Je ne sais pas comment vérifier si c'est un problème du
> clavier lui-même ou si c'est ma debian qui est en cause.
>
> Déjà une piste serait de savoir si je suis le seul à rencontrer ce
> problème ou non?

Hum, je ne serais donc pas le seul. :)

Moi aussi, depuis quelques semaines, j'ai constaté des problèmes de
détection de frappe. Je le rencontre essentiellement avec la séquence
Ctrl-C / Ctrl-V. J'ai démonté les touches de mon clavier en pensant
trouver de la saleté accumulée ou une trace d'usure, mais rien de tout
cela. Du coup, je vais tester un autre clavier pour évacuer la piste
matérielle avant d'incriminer le système pour un bogue aussi surprenant
(pourquoi affecterait-il une ou deux touches en particulier ?)

Car je crains que ce problème ne soit comme moult autres anomalies ou
dysfonctionnements susceptibles d'affecter indépendamment un grand
nombre d'utilisateurs : quelque soit le moment où l'on demande
« observez-vous ce phénomène en ce moment ? », on trouve toujours
quelqu'un pour vous répondre en toute honnêteté « oui,
à l'instant ! ». :)

Sébastien

-- 
Sébastien Dinot, sebastien.di...@free.fr
http://sebastien.dinot.free.fr/
Ne goûtez pas au logiciel libre, vous ne pourriez plus vous en passer !



Re: Booting Debian 10 installer ISO from USB

2019-11-21 Thread Pascal Hambourg

Le 21/11/2019 à 19:08, pru...@finsakxim.com.mx a écrit :


Now, my last issue is: quick scan always fails, looking only in "common 
places". So perhaps the location in the USB sdb3/boot/isos is not 
considered a "common place" and thus only full search can find it here. 


The quick scan only searches in top-level directories.


Can this behavior be changed?


Try iso-scan/ask_second_pass=true.


For this matter, why isn't iso-scan/filename actually working?


It does not seem to be an input but an output.



Re: get an alert when a mail arrives from certain addresses

2019-11-21 Thread 0...@caiway.net
On Fri, 22 Nov 2019 04:37:21 +0100
"sp...@caiway.net"  wrote:

> 
> > You want to use a mail filtering program. Usually people
> > recommend procmail, but honestly, everyone who used procmail
> > whom I have introduced to the maildrop mailfilter has switched
> > over.
> > 
> > sudo apt install maildrop

Thanks again, my searx search engine did not not give any hints in 40 or
so hits.
I am in virgin waters probably

-- 
Thanks!



Re: get an alert when a mail arrives from certain addresses

2019-11-21 Thread sp...@caiway.net


> You want to use a mail filtering program. Usually people
> recommend procmail, but honestly, everyone who used procmail
> whom I have introduced to the maildrop mailfilter has switched
> over.
> 
> sudo apt install maildrop
> 
> -dsr-
> 
Thanks for the suggestion!
Could you tell a bit more on how to integrate this with Claws
Mail?
I am used to Claws Mail, I love it,  but my domoticz software sends
urgent alerts, I want to be announced directly.

Or should I use search engine searx?

 
-- 
Thanks!



Re: minissdpd failure in update

2019-11-21 Thread isaac
 minissdpd.service - keep memory of all UPnP devices that announced
themselves
   Loaded: loaded (/lib/systemd/system/minissdpd.service; enabled;
vendor preset: enabled)
   Active: failed (Result: exit-code) since Thu 2019-11-21 22:54:39
AEDT; 12ms ago
 Docs: man:minissdpd(1)
  Process: 4312 ExecStart=/usr/lib/minissdpd/minissdpd-systemd-wrapper
${MiniSSDPd_INTERFACE_ADDRESS} $MiniSSDPd_OTHER_OPTIONS (code=exited,
status=1/FAILURE)

Nov 21 22:54:39 Isaac systemd[1]: Starting keep memory of all UPnP
devices that announced themselves...
Nov 21 22:54:39 Isaac minissdpd-systemd-wrapper[4312]: Usage:
/usr/sbin/minissdpd [-d] [-6] [-s socket] [-p pidfile] [-t TTL] [-f
device] -i  [-i ] ...
Nov 21 22:54:39 Isaac minissdpd-systemd-wrapper[4312]:is
either an IPv4 address with mask such as
Nov 21 22:54:39 Isaac minissdpd-systemd-
wrapper[4312]:   192.168.1.42/255.255.255.0, or an interface name such
as eth0.
Nov 21 22:54:39 Isaac minissdpd-systemd-wrapper[4312]:   By default,
socket will be open as /var/run/minissdpd.sock
Nov 21 22:54:39 Isaac minissdpd-systemd-wrapper[4312]:   and pid
written to file /var/run/minissdpd.pid
Nov 21 22:54:39 Isaac systemd[1]: minissdpd.service: Control process
exited, code=exited, status=1/FAILURE
Nov 21 22:54:39 Isaac systemd[1]: minissdpd.service: Failed with result
'exit-code'.
Nov 21 22:54:39 Isaac systemd[1]: Failed to start keep memory of all
UPnP devices that announced themselves.
dpkg: error processing package minissdpd (--configure):
 installed minissdpd package post-installation script subprocess
returned error exit status 1
Errors were encountered while processing:
 minissdpd
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@Isaac:/home/isaac# 

can you help me why this error please



Re: get an alert when a mail arrives from certain addresses

2019-11-21 Thread Dan Ritter
sp...@caiway.net wrote: 
> Hello,
> 
> I am using Claws Mail since ages. Very good!
> Now I want to get an alert when a mail arrives from certain addresses.
> Studied the preferences I don't find an option.
> I guess I have to take a look at a command line solution.
> Check mail every minute, check the sender, Alert
> 
> Any advice is welcome!

You want to use a mail filtering program. Usually people
recommend procmail, but honestly, everyone who used procmail
whom I have introduced to the maildrop mailfilter has switched
over.

sudo apt install maildrop

-dsr-



get an alert when a mail arrives from certain addresses

2019-11-21 Thread sp...@caiway.net
Hello,

I am using Claws Mail since ages. Very good!
Now I want to get an alert when a mail arrives from certain addresses.
Studied the preferences I don't find an option.
I guess I have to take a look at a command line solution.
Check mail every minute, check the sender, Alert

Any advice is welcome!
-- 
Thanks!



[testing] problème détection frappe clavier

2019-11-21 Thread Gaëtan Perrier
Bonjour,

Depuis quelques temps j'ai des problèmes de détection de frappes de certaines
touches, notamment les touches accentuées ou utilisant SHIFT ou ALT GR.
Je ne sais pas comment vérifier si c'est un problème du clavier lui-même ou si
c'est ma debian qui est en cause.
Déjà une piste serait de savoir si je suis le seul à rencontrer ce problème ou
non?

A+

Gaëtan


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


Re: Debian Buster and NetworkManager

2019-11-21 Thread Jonas Smedegaard
Quoting Levente (2019-11-21 22:16:44)
> BTW... are there any low-tech, debian specific network manager out 
> there possibly with a GUI that can bring up/down interfaces just like 
> ifup/down?

Not sure what you are really asking: To me "low-tech" and "with a GUI" 
contradicts each other.

Ignoring "with a GUI", arguably "ifu/ifdown" _is_ the Debian-specific 
low-tech "manager" - the package is called "ifupdown".

Ignoring "low-tech" and "Debian specific", there are several network 
managers with GUI, most complete competitor to Network Manager probably 
being ConnMan, and a new interesting wifi-only one being IWD.

There are more...:

  apt install apt-xapian-index
  update-apt-xapian-index
  axi-cache search network::configuration AND interface::x11
  axi-cache search network::configuration AND interface::graphical
  axi-cache --all search network::configuration | less

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature


Re: Debian Buster and NetworkManager

2019-11-21 Thread Dan Ritter
Levente wrote: 
> BTW... are there any low-tech, debian specific network manager out there
> possibly with a GUI that can bring up/down interfaces just like ifup/down?

Not Debian specific, but available in Debian: wicd.

[wicd-cli, wcid-curses, wicd-gtk] and wicd-daemon can
handle wired and wireless interfaces, offer up options,
control DNS, and all the other usual things. As a bonus
it's much less complicated than Network Manager.

-dsr-



Re: Debian Buster and NetworkManager

2019-11-21 Thread Levente
BTW... are there any low-tech, debian specific network manager out there
possibly with a GUI that can bring up/down interfaces just like ifup/down?

On Thu, Nov 21, 2019, 19:43 Greg Wooledge  wrote:

> On Thu, Nov 21, 2019 at 11:14:12AM -0500, Celejar wrote:
> > I'm not disagreeing with anything you write here, but I just want to
> > note that I was recently rather surprised to discover that (FWIW) the
> > official Debian Reference manual calls the systemd method the "modern
> > network configuration" method, and the ifupdown method the "legacy
> > network connection and configuration" method.
> >
> >
> https://www.debian.org/doc/manuals/debian-reference/ch05.en.html#_the_modern_network_configuration_without_gui
>
> Well, as long as the people writing the reference manual are working
> in a vacuum and have no impact on the rest of us, everyone can be
> happy.
>
>


Q: how to stop konsole hiding cursor in buster/stable?

2019-11-21 Thread D. R. Evans
After five seconds, konsole hides the cursor if it's within the window
boundary. Can anyone tell me where the setting is to stop the cursor from
being hidden?

  Doc

-- 
Web:  http://enginehousebooks.com/drevans



signature.asc
Description: OpenPGP digital signature


RE: MEXICO, el pais donde es mas dificil encontrar talento de todo Latinoamerica

2019-11-21 Thread Gabriela Ortiz Olmos

Según datos de la OEA, México tiene una de las tasas de desempleo más alta de 
LA.

RECLUTAMIENTO Y SELECCIÓN 4.0
- Nuevos Mecanismos para Encontrar Talento Humano -

Ciudad de México / 02 de Diciembre 2019
Monterrey, N.L. / 09 de Diciembre 2019

¿ROTACIÓN? ¿CADA VEZ TE CUESTA MÁS TRABAJO ENCONTRAR CANDIDATOS CALIFICADOS? 
¿SOLAMENTE RECLUTAS EN OCC, COMPUTRABAJO Y LINKEDIN?

Si te identificaste con alguna de estas preguntas, definitivamente este 
Workshop es para ti. Conoce los mejores mecanismos y motores de búsqueda para 
reclutar y seleccionar candidatos 100% calificados. 


Favor de enviar mayores informes respecto al Workshop RECLUTAMIENTO Y SELECCIÓN 
4.0 - Nuevos Mecanismos para Encontrar Talento Humano – con atención a:

Nombre:
Empresa:
Teléfono:
Sede de su preferencia:
(  ) Ciudad de México / 02 de Diciembre 2019
(  ) Monterrey, N.L. / 09 de Diciembre 2019
Número de personas interesadas:


O comuníquese con alguno de nuestros ejecutivos al: 800 890 86 65 / 55 2450 
6187 / 33 3632 6541






























Este boletín informativo tiene como objetivo crear valor en usted y en su 
Compañía. Si usted desea dejar de recibir este tipo de información favor de 
contestar con la palabra BAJASELECCION700. O en su defecto en el siguiente 
enlace: unsubscribe from this list



Re: Debian Buster and NetworkManager

2019-11-21 Thread Greg Wooledge
On Thu, Nov 21, 2019 at 11:14:12AM -0500, Celejar wrote:
> I'm not disagreeing with anything you write here, but I just want to
> note that I was recently rather surprised to discover that (FWIW) the
> official Debian Reference manual calls the systemd method the "modern
> network configuration" method, and the ifupdown method the "legacy
> network connection and configuration" method.
> 
> https://www.debian.org/doc/manuals/debian-reference/ch05.en.html#_the_modern_network_configuration_without_gui

Well, as long as the people writing the reference manual are working
in a vacuum and have no impact on the rest of us, everyone can be
happy.



Re: Debian Buster and NetworkManager

2019-11-21 Thread Celejar
On Thu, 21 Nov 2019 13:05:38 +0100
Jonas Smedegaard  wrote:

...

> Network Manager is an _alternative_ network management tool - which 
> happens to be tightly integrated with several of the most popular 
> _desktop_ systems offered by Debian, and therefore easily mistaken as 
> replacing other tools.
> 
> The _default network management tool continues to be ifupdown.
> 
> Network Manager, and systemd-networkd, and other network managers, each 
> integrate or coordinate (or back off) in the presence of ifupdown - to 
> varying ways.
> 
> 
> > Can someone explain in which case NM is better vs interfaces speaking 
> > of server and workstation with multiple bridge?
> 
> The main benefit of Network Manager is its user-friendly interface.
> 
> If you want efficient _programming_ of complex network setups, then you 
> are likely better off using ifupdown or systemd-networkd.
> 
> Not necessarily, only likely.  YMMV.  Debian offers choices here.

I'm not disagreeing with anything you write here, but I just want to
note that I was recently rather surprised to discover that (FWIW) the
official Debian Reference manual calls the systemd method the "modern
network configuration" method, and the ifupdown method the "legacy
network connection and configuration" method.

https://www.debian.org/doc/manuals/debian-reference/ch05.en.html#_the_modern_network_configuration_without_gui

Celejar



Re: Booting Debian 10 installer ISO from USB

2019-11-21 Thread prueba

I think I sorted out part of my problem.
For those who I made them lost, a summary of what I'm trying to do.

I'm trying to boot Debian 10 via Grub's loopback device, in order to 
make a multiboot USB with several Linux distros by copying just the 
ISOs.


I already read Debian installer CD has an initrd with no iso-scan 
package, so won't work out of the box and must use hd-media initrd and 
vmlinuz to make it work.


So I downloaded, renamed, and placed them in same directory as Debian 
installer ISO, in the USB partition. Then created grub.cfg config in 
USB:


iso_path=/boot/iso/debian-10.2.0-amd64-xfce-CD-1.iso
export iso_path
search --set=root --file "$iso_path"
loopback loop "$iso_path"
menuentry "Graphical install" {
   bootoptions="iso-scan/filename=$iso_path desktop=xfce vga=788 --- 
quiet"

   linux /boot/iso/DebianVmlinuz $bootoptions
   initrd /boot/iso/debianGtkInitrd.gz
}

Then tested booting from USB, and the graphical installer does start, 
but after selecting language, locale and keyboard, I got this message:
"The quick scan for installer ISO images, which looks only in common 
places, did not find an installer ISO image. It's possible that a more 
thorough search will find the ISO image, but it may take a long time. Do 
you wish to do a full scan?"


Now, my recent problem was that even by answering yes, it didn't find 
the installer ISO which is right there in the USB.
How sorted? It turned people here were right: I needed to update both 
initrd and installer ISO, since version 10.2 was released just 5 days 
ago...


Having done this I retried. Still get the above message, but now 
thorough search is able to find and use the installer ISO.


Now, my last issue is: quick scan always fails, looking only in "common 
places". So perhaps the location in the USB sdb3/boot/isos is not 
considered a "common place" and thus only full search can find it here. 
Can this behavior be changed?
Maybe somehow telling quick scan to search in custom directories in 
grub.cfg?

For this matter, why isn't iso-scan/filename actually working?

Thanks.



Dongle USB Bluetooth pour Debian ?

2019-11-21 Thread Frédéric MASSOT
Bonjour,

Je recherche un dongle USB Bluetooth qui fonctionne sans problème avec
la Debian même en installant des paquets non-free.

C'est pour faire de la téléphonie avec des casques Bluetooth.

Avez-vous des références de produits ?

J'avais trouvé l'Asus bt400, mais il semble que le firmware du BCM2070
n'est pas distribué dans le paquet bluez-firmware :
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801084



Merci.
-- 
==
|  FRÉDÉRIC MASSOT   |
| http://www.juliana-multimedia.com  |
|   mailto:frede...@juliana-multimedia.com   |
| +33.(0)2.97.54.77.94  +33.(0)6.67.19.95.69 |
===Debian=GNU/Linux===



Re: minissdpd failure in update

2019-11-21 Thread Curt
On 2019-11-21, isaac  wrote:
>  minissdpd
> E: Sub-process /usr/bin/dpkg returned an error code (1)
> root@Isaac:/home/isaac# 
>
> can you help me why minissdpd is not working.

You might try

 dpkg-reconfigure minissdpd

and if that fails, the Reddit fellow below purged the package,
reinstalled it, and then it worked again. Granted, it's a crude method,
and thoroughly unenlightening.

https://www.reddit.com/r/debian/comments/ba05b5/buster_minissdpd/

There's an outstanding bug for minissdpd concerning IPV6, now apparently
switched on by default, creating failures in systems where that protocol
is disabled.

> Thank you Isaac
>
>


-- 
“The cradle rocks above an abyss, and common sense tells us that our existence
is but a brief crack of light between two eternities of darkness.” 
"Speak, Memory," Vladimir Nabokov



Re: virtio bridge no funciona al pasar de Debian Jessie a Debian Stretch

2019-11-21 Thread Galvatorix Torixgalva
Hola,

un update del sistema operativo puede llevarse cosas por delante, sobretodo
cuando son cambios tan importantes (cambiar de una version a otra de la
forma en la que tu lo has hecho).

Podria ser un cambio interno, es decir: funcionar funciona, pero de una
forma diferente.

Te has leido la documentacion del update?, ahi podria haber informacion que
te ayude.

Otra opcion, mas drastica pero que podria tambien funcionar, es eliminar la
instalacion actual del win y crearla de nuevo desde cero.

Un saludo


Re: Dudas con la descarga de paquetes

2019-11-21 Thread Dan Ritter
to...@tuxteam.de wrote: 
> On Wed, Nov 20, 2019 at 08:21:42PM -0600, leonel tejada wrote:
> > buenas noches comunidad de Debian.
> 
> buenos d??as.
> 
> Para discutir temas sobre Debian en espa??ol, recomiendo la lista
> en espa??ol:
> 
>   https://lists.debian.org/debian-user-spanish/
> 
> Aqu??, casi todo el mundo habla ingl??s...
> 

https://debian-handbook.info/browse/es-ES/stable/ might be
useful.

-dsr-



Re: Debian Buster and NetworkManager

2019-11-21 Thread Alessandro Baggi



On 21/11/19 13:05, Jonas Smedegaard wrote:

Quoting Alessandro Baggi (2019-11-21 12:46:53)

I installed KDE and I tried to configure the network using
NetworkManager (nmcli).

[ snipped many nmcli commands to program a complex network setup]


On a notebook, desktop or workstation with simple ethernet/wifi
connection this could be useful but on workstation with non classic
configuration or on a server I could not see how NM complexity could
give some benefit.
I found interfaces method more readable, simpler to write, simpler to
manage and more "ready to work".

NM is a replace of ifconfig,brctl,route command?

Network Manager is an _alternative_ network management tool - which
happens to be tightly integrated with several of the most popular
_desktop_ systems offered by Debian, and therefore easily mistaken as
replacing other tools.

The _default network management tool continues to be ifupdown.

Network Manager, and systemd-networkd, and other network managers, each
integrate or coordinate (or back off) in the presence of ifupdown - to
varying ways.



Can someone explain in which case NM is better vs interfaces speaking
of server and workstation with multiple bridge?

The main benefit of Network Manager is its user-friendly interface.

If you want efficient _programming_ of complex network setups, then you
are likely better off using ifupdown or systemd-networkd.

Not necessarily, only likely.  YMMV.  Debian offers choices here.


  - Jonas


Hi Jonas,
thank you for your answer.



Re: minissdpd failure in update

2019-11-21 Thread Greg Wooledge
On Thu, Nov 21, 2019 at 11:03:42PM +1100, isaac wrote:
>  minissdpd.service - keep memory of all UPnP devices that announced
> themselves
>Loaded: loaded (/lib/systemd/system/minissdpd.service; enabled;
> vendor preset: enabled)
>Active: failed (Result: exit-code) since Thu 2019-11-21 22:54:39
> AEDT; 12ms ago
>  Docs: man:minissdpd(1)
>   Process: 4312 ExecStart=/usr/lib/minissdpd/minissdpd-systemd-wrapper
> ${MiniSSDPd_INTERFACE_ADDRESS} $MiniSSDPd_OTHER_OPTIONS (code=exited,
> status=1/FAILURE)
> 
> Nov 21 22:54:39 Isaac systemd[1]: Starting keep memory of all UPnP
> devices that announced themselves...
> Nov 21 22:54:39 Isaac minissdpd-systemd-wrapper[4312]: Usage:
> /usr/sbin/minissdpd [-d] [-6] [-s socket] [-p pidfile] [-t TTL] [-f
> device] -i  [-i ] ...

Looks like systemd tried to run the daemon with the wrong arguments,
which triggered this usage error message.

Has this package previously been installed on your system, or have
you copied over a configuration file for this package from another
system, or has anything else occurred which might have left a broken
configuration file lying around?  If so, either fix the configuration
file by hand, or purge the package (along with any remaining config
files), and try reinstalling it.

If that's not it, then this sounds like a bug in the package.  You
could look for existing bug reports, and see if anyone else has
encountered it and has a workaround.  Or, you could analyze the systemd
unit file and any configuration files that it reads, find out where
the problem is, and then report the bug yourself.



Re: minissdpd failure in update

2019-11-21 Thread isaac
 minissdpd.service - keep memory of all UPnP devices that announced
themselves
   Loaded: loaded (/lib/systemd/system/minissdpd.service; enabled;
vendor preset: enabled)
   Active: failed (Result: exit-code) since Thu 2019-11-21 22:54:39
AEDT; 12ms ago
 Docs: man:minissdpd(1)
  Process: 4312 ExecStart=/usr/lib/minissdpd/minissdpd-systemd-wrapper
${MiniSSDPd_INTERFACE_ADDRESS} $MiniSSDPd_OTHER_OPTIONS (code=exited,
status=1/FAILURE)

Nov 21 22:54:39 Isaac systemd[1]: Starting keep memory of all UPnP
devices that announced themselves...
Nov 21 22:54:39 Isaac minissdpd-systemd-wrapper[4312]: Usage:
/usr/sbin/minissdpd [-d] [-6] [-s socket] [-p pidfile] [-t TTL] [-f
device] -i  [-i ] ...
Nov 21 22:54:39 Isaac minissdpd-systemd-wrapper[4312]:is
either an IPv4 address with mask such as
Nov 21 22:54:39 Isaac minissdpd-systemd-
wrapper[4312]:   192.168.1.42/255.255.255.0, or an interface name such
as eth0.
Nov 21 22:54:39 Isaac minissdpd-systemd-wrapper[4312]:   By default,
socket will be open as /var/run/minissdpd.sock
Nov 21 22:54:39 Isaac minissdpd-systemd-wrapper[4312]:   and pid
written to file /var/run/minissdpd.pid
Nov 21 22:54:39 Isaac systemd[1]: minissdpd.service: Control process
exited, code=exited, status=1/FAILURE
Nov 21 22:54:39 Isaac systemd[1]: minissdpd.service: Failed with result
'exit-code'.
Nov 21 22:54:39 Isaac systemd[1]: Failed to start keep memory of all
UPnP devices that announced themselves.
dpkg: error processing package minissdpd (--configure):
 installed minissdpd package post-installation script subprocess
returned error exit status 1
Errors were encountered while processing:
 minissdpd
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@Isaac:/home/isaac# 

can you help me why minissdpd is not working.

Thank you Isaac



Re: Problem to locate bug

2019-11-21 Thread Jonas Smedegaard
Hi Julian,

Quoting sj...@uranus.uni-freiburg.de (2019-11-21 11:39:14)
> if it (from around June 28th) still matters for somebody: I 
> re-installed my whole system and I couldn't re-recognise the behaviour 
> described. I also can't remember having changed anything in the 
> "deeper settings of the system"…

Thanks for sharing.

In future, however, please strongly consider debbugs to, well, track 
bugs: https://www.debian.org/Bugs/Reporting


Debbugs is kinda designed for that, unlike this mailinglist which is not 
very good for tracking issues and triangulating them with time and 
dependencies and versions and other states.


Thanks for considering, and sincerely hope you enjoy Debian,

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature


Re: Debian Buster and NetworkManager

2019-11-21 Thread Jonas Smedegaard
Quoting Alessandro Baggi (2019-11-21 12:46:53)
> I installed KDE and I tried to configure the network using 
> NetworkManager (nmcli).

[ snipped many nmcli commands to program a complex network setup]

> On a notebook, desktop or workstation with simple ethernet/wifi 
> connection this could be useful but on workstation with non classic 
> configuration or on a server I could not see how NM complexity could 
> give some benefit.
> I found interfaces method more readable, simpler to write, simpler to 
> manage and more "ready to work".
> 
> NM is a replace of ifconfig,brctl,route command?

Network Manager is an _alternative_ network management tool - which 
happens to be tightly integrated with several of the most popular 
_desktop_ systems offered by Debian, and therefore easily mistaken as 
replacing other tools.

The _default network management tool continues to be ifupdown.

Network Manager, and systemd-networkd, and other network managers, each 
integrate or coordinate (or back off) in the presence of ifupdown - to 
varying ways.


> Can someone explain in which case NM is better vs interfaces speaking 
> of server and workstation with multiple bridge?

The main benefit of Network Manager is its user-friendly interface.

If you want efficient _programming_ of complex network setups, then you 
are likely better off using ifupdown or systemd-networkd.

Not necessarily, only likely.  YMMV.  Debian offers choices here.


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature


Debian Buster and NetworkManager

2019-11-21 Thread Alessandro Baggi

Hi list,

I've recently upgraded my stretch to buster (fresh install).

I installed KDE and I tried to configure the network using 
NetworkManager (nmcli).
On my workstation I have 2 bridges (br0 for lan vms and br1 for dmz on 
demand vms).
br0 have a static address to permit navigation on my workstation and br1 
does not have any address assigned.
Using interfaces old method all work very well but using NM things are 
bad. I configured my net devices like this:


# nmcli connection delete enp0s31f6
# nmcli connection delete enp7s0
# nmcli device disconnect enp0s31f6
# nmcli device disconnect enp7s0

# nmcli connection add type bridge con-name br0 ifname br0
# nmcli connection add type bridge-slave con-name enp0s31f6 ifname 
enp0s31f6 master br0
# nmcli connection modify br0 ipv4.address x.x.x.x/16 ipv4.method manual 
ipv4.gateway x.x.x.x ipv4.dns x.x.x.x

# nmcli connection modify br0 ipv6.method ignore bridge.stp no
# nmcli connection add type bridge con-name br1 ifname br1
# nmcli connection add type bridge-slave con-name enp7s0 ifname enp7s0 
master br1
# nmcli connection modify br1 ipv4.method disabled ipv6.method ignore 
bridge.stp no


# nmcli connection up enp0s31f6
# nmcli connection up enp7s0
# nmcli connection up br0
# nmcli connection up br1
# nmcli connection reload

With all these previous commands network is available. On a system 
reboot network is up.


On a notebook, desktop or workstation with simple ethernet/wifi 
connection this could be useful but on workstation with non classic 
configuration or on a server I could not see how NM complexity could 
give some benefit.
I found interfaces method more readable, simpler to write, simpler to 
manage and more "ready to work".


NM is a replace of ifconfig,brctl,route command?

Can someone explain in which case NM is better vs interfaces speaking of 
server and workstation with multiple bridge?


Thanks in advance.





Re: Problem to locate bug

2019-11-21 Thread sj126
Hi,
if it (from around June 28th) still matters for somebody: I re-installed my 
whole system and I couldn't re-recognise the behaviour described. I also can't 
remember having changed anything in the "deeper settings of the system"…

However, best regards,
 Julian Schreck
--
> Hi,
> 
> Julian Schreck wrote:
> > I could narrow it down to lxterminal (autostarted),
> 
> You could start another terminal program from the lxterminal and then
> end the lxterminal. (I use "xterm", the old and sparse one.)
> You could also check whether the lxterm menus give you an opportunity
> to disable any fancy dynamic effects.
> 
> 
> > openbox or an automatically started process.
> 
> An automatic process as culprit seems somewhat far-fetched. I understand
> that you do not see a clear time pattern with the system freezes.
> With an automat i'd expect some regularity.
> 
> Did you already find out whether the whole system freezes or whether it's
> only about graphics and/or local user interaction ?
> 
> 
> > Any other advice than changing the window manager
> > (in case that was suggested/your intention)?
> 
> The window manager and its interaction with the system appears as first
> suspect, when i ask the web.
> 
> 
> > description: Desktop Computer
> >description: Motherboard
> >vendor: ASRock
> >product: Z270M Pro4
> > *-display
> > description: VGA compatible controller
> > product: Intel Corporation
> > vendor: Intel Corporation
> 
> ASRock says the mainboard has AMD/ATI "Quad CrossfireX".
> Am i mistaken if i assume that you currently use a plugged-in graphics
> board ?
> 
> 
> Have a nice day :)
> 
> Thomas



Re: Dudas con la descarga de paquetes

2019-11-21 Thread tomas
On Wed, Nov 20, 2019 at 08:21:42PM -0600, leonel tejada wrote:
> buenas noches comunidad de Debian.

buenos días.

Para discutir temas sobre Debian en español, recomiendo la lista
en español:

  https://lists.debian.org/debian-user-spanish/

Aquí, casi todo el mundo habla inglés...

> el motivo de mi presente correo ... es por el hecho que estoy utilizando
> Debia 10 para  un proyecto universitario, en el cual queremos instalarle
> unos servers para dicho cometido, pero tengo ciertas dudas con el
> funcionamiento del mismo.
> 
> he intentado con todos los comandos:
> 
> -aptitude
> -apt
> -apt-get
> -apt-get install
> -install

No comprendo qué ha intentado con los comandos. ¿Cómo los ha invocado?
¿Qué es ol que quería instalar con ellos?

> ... sin resultado satisfactorio alguno.

¿Cuál es el resultado que Vd. esperaba?

Saludos
-- tomás


signature.asc
Description: Digital signature