Re: Adduser only one or. two users

[Ishaan Mahajan]

Sorry for another email but this is what it looks like now - RUN sudo
adduser --shell $USERSHELLPATH --disabled-password $USERNAME && \
However, I am still running into the same problem.

Thanks,
Ishaan

On Thu, Aug 4, 2022 at 10:53 PM Dan Ritter  wrote:

> Ishaan Mahajan wrote:
> > Hi,
> >
> > This is the line I have got - RUN sudo adduser --shell $USERSHELLPATH
> > --disabled-password --gecos "" $USERNAME && \
> > echo "$USERNAME ALL=(ALL) NOPASSWD: ALL" > /etc/sudoers.d/$USERNAME && \
> > chmod 0440 /etc/sudoers.d/USERNAME
> > However, I keep getting the error,
> > adduser: Only one or two names allowed.--
> > How do I get around this?
>
> sudo adduser --shell $USERSHELLPATH --disabled-password --gecos ""
> $USERNAME
>
> That's your first command line. --gecos expects a value. You are
> literally supplying no value.
>
> Why don't you leave the --gecos "" out entirely, if you aren't
> going to populate it with a human-readable name?
>
> -dsr-
>
>

-- 
Have a great day ahead!

Best,
Ishaan Mahajan

Re: There is a big bug in auto update in debian 11

[Timothy M Butterworth]

On Thu, Aug 4, 2022 at 7:51 PM Mid Mes Fair  wrote:

> There is a big bug in auto update in debian 11.
> I have turned off the auto checking feature but it still checking and
> appear on the notification section in the software
>

We need more info. To start with:
What Desktop Environment are you using?
What point release are you patched up to `cat /etc/debian_version`?

-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄⠀⠀

Area parameter of Wacom CTL 6100

[Pankaj Jangid]

I had this issue long back, when my wacom ctl-6100 was far exceeding my
4k display. But then it got fixed automatically with some software
upgrade in Debian 11 bullseye.

But recently, I plugged it in again to sign a few documents and found
that the problem has reappeared.

Can someone guide me how to diagnose, where the problem is? Here is what
I did,

Since Wayland is now default, xsetwacom doesn't show any
device. Although the tablet works. To debug, I disabled Wayland in
/etc/gdm3/daemon.conf and then tried to set Area parameter using
xsetwacom. But it did not help.

libwacom-list-local-devices command's output shows that the system is
picking up /usr/share/libwacom/intuos-m-p3-android.tablet and setting
Width=3 and Height=5. Ideally, it should pick
/usr/share/libwacom/intuos-m-p3.tablet which has Width=9 and Height=5.

BTW, libwacom-list-local-devices command works in Wayland as well.

Any further clues would be great help.

Regards
Pankaj

Re: VFAT vs. umask.

[David Wright]

On Thu 04 Aug 2022 at 13:27:34 (-0400), gene heskett wrote:
> On 8/4/22 10:47, pe...@easthope.ca wrote:
> >  From: Charles Curley 
> >  Date: Sat, 30 Jul 2022 13:39:00 -0600
> > > The preparation of any storage medium requires at least two steps. To
> > > format means ...
> > > 
> > > In another step one lays down a file system: ...
> > Understood, at a superficial level at least.  Haven't invented or
> > implemented a file system.
> > 
> > > Microsoft conflated the two, leading to much confusion over the
> > > years.
> > Even prominent software uses "format" loosely.  Eg. Gparted >
> > Partition > Format to > ... .

I searched my way through
https://gparted.org/display-doc.php?name=help-manual
and couldn't find any ambiguity. They use the term to mean what you
want to call a "high-level format", "laying down a filesystem", or
some neologism.

> > If we really want to improve terminology we need to
> > (1) understand intimately software such as gparted,
> > (2) find or invent terms more specific than "format",
> > (3) convince maintainers to fix the bugs (adopt the new terms) and
> > (4) take credit for the revolutionary improvements.  =8~)
> > 
> > > Try mounting it from the command line, and watch the output. That will
> > > show you whether it is being fscked. However, FAT has no ability to
> > > store when it was last fscked, so I would wonder why it was being
> > > fscked at all.
> > In further observations, the problem is primarily in the old Fedora
> > based OLPC XO system.  Debian Bullseye usually recognizes and mounts
> > the f.s. on the SD card with no difficulty.  Rather than troubleshoot
> > the obsolete system I'll continue an effort to make DebXO work on the
> > XO 1.5 machine.

Is this the X/Y problem's Z?

> Having worked on a couple filesystems in a past life, all I can do is
> say +100 Peter.
> "format" is one of the most overloaded words in our vocabulary.

Really?

https://en.wiktionary.org/wiki/format
https://en.wiktionary.org/wiki/set

Cheers,
David.

Re: VFAT vs. umask.

[David Wright]

On Wed 03 Aug 2022 at 08:37:24 (-0700), pe...@easthope.ca wrote:
> From: David Wright 
> Date: Sun, 31 Jul 2022 14:15:26 -0500

> > So "primary store" probably means Master Copy of Your Data. 
> 
> https://en.wiktionary.org/wiki/primary#Adjective  sense 2.
> https://en.wiktionary.org/wiki/master#Adjective  sense 2.
> https://en.wiktionary.org/wiki/store#Noun  sense 4.

Yes, that last one is no help, usually triggering a HelpDesk-type
explanation of the difference between memory and storage.
As for primary store, the primary location for my photographs is
an SD card, but the first thing I do is transfer it to the master
location on spinning rust, check it, and back it up, before deleting
the primary store to avoid a "Memory Full" (sic) incident occurring
later, in the field.

So rather than a back and forth at cross-purposes (like that with
NAT and IPv6), I stated what /I/ thought your description meant.

> > ... copy it off the SD onto a hard drive to work on it, then put it 
> > back (hopefully with care, not overwriting, and thorough flushing¹).
> 
> I never do that.  I use a file on the SD just as if it's on a spinning 
> hdd.

OK, now we know where we stand. Your working methods and priorities
are so different from mine that it's easy to end up with crossed lines.
I run one system where the main drive is an SSD, but I've only run a
system on a flash drive (it was a USB rather than an SD) once, and
just as an experiment, for the challenge of installing an EFI bootable
system. That's a far worse case, of course, because it puts / onto the
flash drive, whereas presumably yours only involves a subdirectory.

> > ... reformat the card to an ext format and you can forget about that.
> 
> According to several other messages alignment and block size are 
> concerns in reformatting.

I'm using format in the sense used by the rest of the world, which you
and Charles would call a "high-level format" judging from posts like:
https://lists.debian.org/debian-user/2022/07/msg00768.html
https://lists.debian.org/debian-user/2022/07/msg00743.html
IOW, I meant what's done by mkfs.foo, except I was assuming that
you'd make an adjustment to the Partition Type first.

So I hadn't envisaged your considering a change in the partition's
/alignment/, which appears to be perfect, both at the beginning and,
more unusually, the end.

As for block size, yes, there are advantages to matching the
filesystem parameters with the underlying firmware's allocation
and erase units, but AFAICT the only way to reliably determine
the latter is by running timing experiments on the specific type
of device.

Much of this might be moot: allegedly there are design decisions
in how the cards operate that may be more important in determining
how fast the card is in use, particularly with different
filesystems, like FAT and ext, eg using a different strategy for
handling the start of the card, assumed to be the location of the
FAT's file allocation table itself.

As I pointed out, this might not make such a huge difference for the
use I thought you were making of the card, but I haven't a clue what
the effect might be when it's the file storage being used by your
programs while they're executing. That would require knowing how
the programs used it.

So it's quite possible that sticking with FAT is a better bet.
It was never clear to me what your permission problem with using
FAT actually was in the first place. Your OP read like some sort
of riddle or paradox that we were meant to solve, which we did.
(It's the driver wotduzit.)

Cheers,
David.

Re: Unsolicited GNU bc patch

[SDA]

On Sat, Jul 30, 2022 at 07:29:23AM +, Thomas DiModica wrote:

Hi, Thomas. I'd send this to the debian-developer email list rather than 
this user list. Not sure if any developers are lurking here ...

> Greetings,
> 
> I don't remember how or why I initially stumbled across this bug report 
> (https://bugs.launchpad.net/ubuntu/+source/bc/+bug/1775776), but, given that 
> I have some familiarity with GNU bc, I decided to fix some of the issues. 
> Turns out, this also seems to fix the crashes reported here 
> (https://www.openwall.com/lists/oss-security/2018/11/28/1). I think it would 
> be a lot more useful to share this, as there isn't a lot to review. There are 
> three bug fixes and some self-defensive checks in the runtime for malformed 
> bytecode. Address Sanitizer tells me that these previously invalid memory 
> references now just leak memory. I don't appear to have broken anything in 
> the process, either.
> 
> Just trying to be somewhat helpful,
> Thomas DiModica

> From 3ecfe21c965956f3913e9bc340df729234e4453b Mon Sep 17 00:00:00 2001
> From: Thomas DiModica 
> Date: Tue, 19 Jul 2022 19:28:12 -0600
> Subject: [PATCH] Resolving the crashes found through fuzz testing by
>  HongxuChen.
> 
> ---
>  bc/execute.c | 54 +---
>  bc/storage.c | 38 ++--
>  bc/util.c|  2 +-
>  3 files changed, 71 insertions(+), 23 deletions(-)
> 
> diff --git a/bc/execute.c b/bc/execute.c
> index 256e4b7..d30c6f5 100644
> --- a/bc/execute.c
> +++ b/bc/execute.c
> @@ -130,7 +130,7 @@ execute (void)
> gp = functions[pc.pc_func].f_label;
> l_gp  = label_num >> BC_LABEL_LOG;
> l_off = label_num % BC_LABEL_GROUP;
> -   while (l_gp-- > 0) gp = gp->l_next;
> +   while ((l_gp-- > 0) && (gp != NULL)) gp = gp->l_next;
>if (gp)
>  pc.pc_addr = gp->l_adrs[l_off];
>else {
> @@ -146,6 +146,13 @@ execute (void)
>   if ((new_func & 0x80) != 0) 
> new_func = ((new_func & 0x7f) << 8) + byte();
>  
> + /* Check to make sure it is valid. */
> + if (new_func >= f_count)
> +   {
> + rt_error ("Internal error.");
> + break;
> +   }
> +
>   /* Check to make sure it is defined. */
>   if (!functions[new_func].f_defined)
> {
> @@ -204,25 +211,32 @@ execute (void)
>  
>case 'O' : /* Write a string to the output with processing. */
>   while ((ch = byte()) != '"')
> -   if (ch != '\\')
> - out_schar (ch);
> -   else
> - {
> -   ch = byte();
> -   if (ch == '"') break;
> -   switch (ch)
> - {
> - case 'a':  out_schar (007); break;
> - case 'b':  out_schar ('\b'); break;
> - case 'f':  out_schar ('\f'); break;
> - case 'n':  out_schar ('\n'); break;
> - case 'q':  out_schar ('"'); break;
> - case 'r':  out_schar ('\r'); break;
> - case 't':  out_schar ('\t'); break;
> - case '\\': out_schar ('\\'); break;
> - default:  break;
> - }
> - }
> +   {
> + if (pc.pc_addr == functions[pc.pc_func].f_code_size)
> +   {
> + rt_error ("Broken String.");
> + break;
> +   }
> + if (ch != '\\')
> +   out_schar (ch);
> + else
> +   {
> + ch = byte();
> + if (ch == '"') break;
> + switch (ch)
> +   {
> +   case 'a':  out_schar (007); break;
> +   case 'b':  out_schar ('\b'); break;
> +   case 'f':  out_schar ('\f'); break;
> +   case 'n':  out_schar ('\n'); break;
> +   case 'q':  out_schar ('"'); break;
> +   case 'r':  out_schar ('\r'); break;
> +   case 't':  out_schar ('\t'); break;
> +   case '\\': out_schar ('\\'); break;
> +   default:  break;
> +   }
> +   }
> +   }
>   fflush (stdout);
>   break;
>  
> diff --git a/bc/storage.c b/bc/storage.c
> index c79db82..28e933b 100644
> --- a/bc/storage.c
> +++ b/bc/storage.c
> @@ -349,6 +349,7 @@ get_var (int var_name)
>  {
>var_ptr = variables[var_name] = bc_malloc (sizeof (bc_var));
>bc_init_num (_ptr->v_value);
> +  var_ptr->v_next = NULL;
>  }
>return var_ptr;
>  }
> @@ -370,6 +371,12 @@ get_array_num (int var_index, unsigned long idx)
>unsigned int ix, ix1;
>int sub [NODE_DEPTH];
>  
> +  if (var_index >= a_count)
> +{
> +  rt_error ("Internal Error.");
> +  return NULL;
> +}
> +
>/* Get the array entry. */
>ary_ptr = arrays[var_index];
>if (ary_ptr == NULL)
> @@ -588,6 +595,12 @@ store_array (int var_name)
>bc_num *num_ptr;
>long idx;
>  
> +  if (var_name >= a_count)
> +{
> +  rt_error ("Internal Error.");
> +  return;
> +}
> +
>if 

Re: adduser

[Sabri KHEMISSA]

Bonjour,

adduser est normalement dans le répertoire /usr/sbin/

Si adduser est installé, as-tu vérifié que ce répertoire est dans le path
de l'utilisateur qui lance la commande ?

Le jeu. 4 août 2022 à 19:10, Alex PADOLY  a
écrit :

> Bonsoir à tous,
>
>
> Alors que sous Debian 8, je pouvais ajouter des utilisateurs avec la
> commande adduser en mode console.
>
> Sous Debian 8 avec le bureau LXQT, ce n'est pas possible, la commande
> adduser n'est pas reconnu en mode console.
>
>
> *Il faut passer par une petite application LXQT-paramétrage du système
> puis utilisateurs et groupes.*
>
>
> Quelqu'un d'entre, vous connait-il, la raison de cette restriction.
>
> Merci pour vos précisions.
>
>
> Alex
>

Re: Adduser only one or. two users

[tomas]

On Thu, Aug 04, 2022 at 12:17:54PM -0600, Charles Curley wrote:
> On Thu, 4 Aug 2022 13:23:11 -0400
> Dan Ritter  wrote:
> 
> > sudo adduser --shell $USERSHELLPATH --disabled-password --gecos ""
> > $USERNAME
> > 
> > That's your first command line. --gecos expects a value. You are
> > literally supplying no value.
> > 
> > Why don't you leave the --gecos "" out entirely, if you aren't
> > going to populate it with a human-readable name?
> 
> I'll second this one, and add, you should quote variable names in order
> to avoid spaces in the variables screwing things up. So: "$USERNAME",
> not $USERNAME. What happens if the user name is Fred Flintstone?

This is very good advice. The variable values get expanded in-place,
so a white space in the value will wreak havoc.

Folks, always quote your variables :-)

Same goes for $USERSHELLPATH, it should be "$USERSHELLPATH".

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: Adduser only one or. two users

[Charles Curley]

On Thu, 4 Aug 2022 13:23:11 -0400
Dan Ritter  wrote:

> sudo adduser --shell $USERSHELLPATH --disabled-password --gecos ""
> $USERNAME
> 
> That's your first command line. --gecos expects a value. You are
> literally supplying no value.
> 
> Why don't you leave the --gecos "" out entirely, if you aren't
> going to populate it with a human-readable name?

I'll second this one, and add, you should quote variable names in order
to avoid spaces in the variables screwing things up. So: "$USERNAME",
not $USERNAME. What happens if the user name is Fred Flintstone?

Of course we don't see how, if at all, you've qualified your inputs so
this suggestion may be moot.

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

Re: Gestion du ventilateur sur un PC portable.

[Étienne Mollier]

benoit, on 2022-08-04:
> Le jeudi 4 août 2022 à 19:39, Étienne Mollier  a écrit 
> :
> > Bonjour,
> >
> > Par le plus grand des hasards, est ce que le paquet de
> > micrologiciels non-free intel-microcodes est installé ?
> 
> Non je n'ai pas non-free dans mon source.list
> 
> Mais je peux essayer

Je dirais même, intel-microcode au singulier.

Erratum,
-- 
Étienne Mollier 
Fingerprint:  8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
Sent from /dev/pts/4, please excuse my verbosity.


signature.asc
Description: PGP signature

Re: adduser

[benoit]

Mais tu l'as installé ?

adduser/stable,now 3.118 all [installé]
Ajouter ou supprimer des utilisateurs ou groupes

Envoyé avec la messagerie sécurisée [Proton Mail](https://proton.me/).

--- Original Message ---
Le jeudi 4 août 2022 à 19:09, Alex PADOLY  a écrit :

> Bonsoir à tous,
>
> Alors que sous Debian 8, je pouvais ajouter des utilisateurs avec la commande 
> adduser en mode console.
>
> Sous Debian 8 avec le bureau LXQT, ce n'est pas possible, la commande adduser 
> n'est pas reconnu en mode console.
>
> Il faut passer par une petite application LXQT-paramétrage du système puis 
> utilisateurs et groupes.
>
> Quelqu'un d'entre, vous connait-il, la raison de cette restriction.
>
> Merci pour vos précisions.
>
> Alex

Re: Gestion du ventilateur sur un PC portable.

[Étienne Mollier]

benoit, on 2022-08-04:
> Le jeudi 4 août 2022 à 19:45, Étienne Mollier  a écrit 
> :
> > BERTRAND Joël, on 2022-08-04:
> > > Un composant grand comme un Atom N270 doit pouvoir dissiper 2,5W dans
> > > le plan de masse sans même avoir besoin d'un radiateur passif. Je fais
> > > cela à longueur de journée. Le simple fait que le CPU soit muni d'un
> > > ventilateur montre qu'il peut consommer largement plus que les 2,5W
> > > annoncés.
> >
> > Oui, il doit y avoir un truc. J'ai un Atom N2600 annoncé à 3,5W
> > de PDT, et à part par forte chaleur où il peut atteindre 80°C en
> > pleine charge, je n'ai jamais eu de problèmes particuliers avec.
> > Il est refroidi « dans le plan de masse ».
> 
> Là au moment du pic de chaleur de ce début de soirée il est à 52°, mais il ne 
> fait rien.

Ça me paraît cohérent, j'ai 55°C idle à l'instant t sans
dissipation active.
-- 
Étienne Mollier 
Fingerprint:  8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
Sent from /dev/pts/4, please excuse my verbosity.


signature.asc
Description: PGP signature

Re: adduser

[benoit]

Le jeudi 4 août 2022 à 19:47, benoit  a écrit :

> Le jeudi 4 août 2022 à 19:09, Alex PADOLY  a écrit :
>
>> Bonsoir à tous,
>>
>> Alors que sous Debian 8, je pouvais ajouter des utilisateurs avec la 
>> commande adduser en mode console.
>>
>> Sous Debian 8 avec le bureau LXQT, ce n'est pas possible, la commande 
>> adduser n'est pas reconnu en mode console.
>>
>> Il faut passer par une petite application LXQT-paramétrage du système puis 
>> utilisateurs et groupes.
>>
>> Quelqu'un d'entre, vous connait-il, la raison de cette restriction.
>>
>> Merci pour vos précisions.
>
> Bonjour,
>
> Je viens de tester en root ca fonctionne, mais je lui préfère useradd, c'est 
> interactif.

Oups c'est bien adduser qui est interactif !

Benoit

>

Re: Gestion du ventilateur sur un PC portable.

[benoit]

Le jeudi 4 août 2022 à 19:45, Étienne Mollier  a écrit :


> Bonjour Joël,
>
> BERTRAND Joël, on 2022-08-04:
>
> > Un composant grand comme un Atom N270 doit pouvoir dissiper 2,5W dans
> > le plan de masse sans même avoir besoin d'un radiateur passif. Je fais
> > cela à longueur de journée. Le simple fait que le CPU soit muni d'un
> > ventilateur montre qu'il peut consommer largement plus que les 2,5W
> > annoncés.
>
>
> Oui, il doit y avoir un truc. J'ai un Atom N2600 annoncé à 3,5W
> de PDT, et à part par forte chaleur où il peut atteindre 80°C en
> pleine charge, je n'ai jamais eu de problèmes particuliers avec.
> Il est refroidi « dans le plan de masse ».
>
Là au moment du pic de chaleur de ce début de soirée il est à 52°, mais il ne 
fait rien.

Re: Adduser only one or. two users

[Greg Wooledge]

On Thu, Aug 04, 2022 at 01:24:04PM -0400, Cindy Sue Causey wrote:
> On 8/4/22, Ishaan Mahajan  wrote:
> > Hi,
> >
> > This is the line I have got - RUN sudo adduser --shell $USERSHELLPATH
> > --disabled-password --gecos "" $USERNAME && \
> > echo "$USERNAME ALL=(ALL) NOPASSWD: ALL" > /etc/sudoers.d/$USERNAME && \
> > chmod 0440 /etc/sudoers.d/USERNAME
> > However, I keep getting the error,
> > adduser: Only one or two names allowed.--
> > How do I get around this?
> > Have a great day ahead!
> 
> 
> Does this line:
> 
> chmod 0440 /etc/sudoers.d/USERNAME
> 
> Need to continue using "$" as part of its variable?
> 
> That stood out as different. If that's not it, I'm totally out on a
> very thin limb (beyond my payscale) here. :)

You're correct.  That's one error, but not the one causing the message.

In order to find the other errors, we would need to know the contents
of the $USERSHELLPATH and $USERNAME variables.

Also, those should be "double quoted".  "$USERNAME" in every instance.

Finally, this thing is using sudo to run adduser, but afterward it's
attempting to write to /etc/sudoers.d/$USERNAME without using sudo.
So, either that write is going to fail, or the sudo wasn't needed in
the first place.

Re: Gestion du ventilateur sur un PC portable.

[benoit]

Le jeudi 4 août 2022 à 19:39, Étienne Mollier  a écrit :


> Bonjour,
>
>
> Par le plus grand des hasards, est ce que le paquet de
> micrologiciels non-free intel-microcodes est installé ?
>

Non je n'ai pas non-free dans mon source.list

Mais je peux essayer

--
Benoit

Re: adduser

[benoit]

Le jeudi 4 août 2022 à 19:09, Alex PADOLY  a écrit :

> Bonsoir à tous,
>
> Alors que sous Debian 8, je pouvais ajouter des utilisateurs avec la commande 
> adduser en mode console.
>
> Sous Debian 8 avec le bureau LXQT, ce n'est pas possible, la commande adduser 
> n'est pas reconnu en mode console.
>
> Il faut passer par une petite application LXQT-paramétrage du système puis 
> utilisateurs et groupes.
>
> Quelqu'un d'entre, vous connait-il, la raison de cette restriction.
>
> Merci pour vos précisions.

Bonjour,

Je viens de tester en root ca fonctionne, mais je lui préfère useradd, c'est 
interactif.

Benoit

Re: Gestion du ventilateur sur un PC portable.

[Étienne Mollier]

Bonjour Joël,

BERTRAND Joël, on 2022-08-04:
>   Un composant grand comme un Atom N270 doit pouvoir dissiper 2,5W dans
> le plan de masse sans même avoir besoin d'un radiateur passif. Je fais
> cela à longueur de journée. Le simple fait que le CPU soit muni d'un
> ventilateur montre qu'il peut consommer largement plus que les 2,5W
> annoncés.

Oui, il doit y avoir un truc.  J'ai un Atom N2600 annoncé à 3,5W
de PDT, et à part par forte chaleur où il peut atteindre 80°C en
pleine charge, je n'ai jamais eu de problèmes particuliers avec.
Il est refroidi « dans le plan de masse ».

Bonne journée,
-- 
Étienne Mollier 
Fingerprint:  8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
Sent from /dev/pts/2, please excuse my verbosity.


signature.asc
Description: PGP signature

Re: Gestion du ventilateur sur un PC portable.

[Étienne Mollier]

Bonjour,

Dethegeek, on 2022-08-04:
> C'est assez énervant ces stratégies marketing. Ca en devient mensonger.
> 
> Le chipset de la machine est de Intel Il ne doit pas y avoir grand chose à
> bidouiller, ca me semble bien supporté par linux, et il ne doit pas y avoir
> grand chose à améliorer, non ?

Par le plus grand des hasards, est ce que le paquet de
micrologiciels non-free intel-microcodes est installé ?

En espérant que ça aide,
-- 
Étienne Mollier 
Fingerprint:  8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
Sent from /dev/pts/2, please excuse my verbosity.


signature.asc
Description: PGP signature

Re: Adduser only one or. two users

[Dan Ritter]

Ishaan Mahajan wrote: 
> Hi,
> 
> This is the line I have got - RUN sudo adduser --shell $USERSHELLPATH
> --disabled-password --gecos "" $USERNAME && \
> echo "$USERNAME ALL=(ALL) NOPASSWD: ALL" > /etc/sudoers.d/$USERNAME && \
> chmod 0440 /etc/sudoers.d/USERNAME
> However, I keep getting the error,
> adduser: Only one or two names allowed.--
> How do I get around this?

sudo adduser --shell $USERSHELLPATH --disabled-password --gecos "" $USERNAME

That's your first command line. --gecos expects a value. You are
literally supplying no value.

Why don't you leave the --gecos "" out entirely, if you aren't
going to populate it with a human-readable name?

-dsr-

Re: VFAT vs. umask.

[gene heskett]

On 8/4/22 10:47, pe...@easthope.ca wrote:

 From: Charles Curley 
 Date: Sat, 30 Jul 2022 13:39:00 -0600

The preparation of any storage medium requires at least two steps. To
format means ...

In another step one lays down a file system: ...

Understood, at a superficial level at least.  Haven't invented or
implemented a file system.


Microsoft conflated the two, leading to much confusion over the
years.

Even prominent software uses "format" loosely.  Eg. Gparted >
Partition > Format to > ... .

If we really want to improve terminology we need to
(1) understand intimately software such as gparted,
(2) find or invent terms more specific than "format",
(3) convince maintainers to fix the bugs (adopt the new terms) and
(4) take credit for the revolutionary improvements.  =8~)


Try mounting it from the command line, and watch the output. That will
show you whether it is being fscked. However, FAT has no ability to
store when it was last fscked, so I would wonder why it was being
fscked at all.

In further observations, the problem is primarily in the old Fedora
based OLPC XO system.  Debian Bullseye usually recognizes and mounts
the f.s. on the SD card with no difficulty.  Rather than troubleshoot
the obsolete system I'll continue an effort to make DebXO work on the
XO 1.5 machine.

Thx,   ... P.
Having worked on a couple filesystems in a past life, all I can do is 
say +100 Peter.

"format" is one of the most overloaded words in our vocabulary.

Take care and stay well.


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

Re: Adduser only one or. two users

[Cindy Sue Causey]

On 8/4/22, Ishaan Mahajan  wrote:
> Hi,
>
> This is the line I have got - RUN sudo adduser --shell $USERSHELLPATH
> --disabled-password --gecos "" $USERNAME && \
> echo "$USERNAME ALL=(ALL) NOPASSWD: ALL" > /etc/sudoers.d/$USERNAME && \
> chmod 0440 /etc/sudoers.d/USERNAME
> However, I keep getting the error,
> adduser: Only one or two names allowed.--
> How do I get around this?
> Have a great day ahead!


Does this line:

chmod 0440 /etc/sudoers.d/USERNAME

Need to continue using "$" as part of its variable?

That stood out as different. If that's not it, I'm totally out on a
very thin limb (beyond my payscale) here. :)

Cindy :)
-- 
Talking Rock, Pickens County, Georgia, USA
* runs with birdseed *

Re: Nouveau Is (was: Nvidia + Plasma + Keyboard)

[gene heskett]

On 8/4/22 10:41, Felix Miata wrote:

This is valuable info Felix, thank you.

Andrew M.A. Cater composed on 2022-08-04 10:20 (UTC):
...

nouveau is a good and supported way forward.

NouveauS are.

It's deleterious to omit the fact that there are two separate functionality FOSS
Nouveaus, one of which, the Nouveau X display driver (DDX: Device Dependent X), 
is

reverse-engineered
old technology
non-functional, absent the other being loaded
optional (as in not needed, except for seriously ancient GPUs, mainly 
AGP)

The other is the kernel's Nouveau device driver, which provides KMS 
functionality
that the DDX, and the newer technology DIX (Device Independent X: Modesetting;
upstream default), and Mesa, depend on.

Given the kernel will load its Nouveau module automatically when an NVidia GPU 
is
present (and the Nouveau module is not blocked from loading), and the conceptual
superiority of the DIX over the DDX, it's probably better to mention Nouveau 
only
as the inferior option when discussing DIX suitability to task.



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

Re: problema con Processing, Java y OpenGL

[Daniel]

Hola. Para los que tengan problema similar (los script de Processing 
3.5.5 en 3D funcionan desde el fuente con el IDE andando pero no el 
ejecutable) (en Linux 64 con Debian 11 y Java: openJRE 
11.0.16+8-1~deb11u1). Las soluciones propuestas en:


https://wiki.controlonline.net:1029/doku.php?id=tutorials:processing:19_3d

no me funcionaron.

En mi caso dejo allí la cosa pues el script es de uso sólo didáctico así 
que no afecta el IDE presente pero el tema de los ejecutables queda 
irresuelto hasta donde sé.


Tampoco, como se comentó, funciona setear las variables de entorno:

_JAVA_OPTIONS="-Djogl.disable.openglcore=false"

y/o

LIBGL_ALWAYS_SOFTWARE=1

Saludos desde el sur!

Daniel


El 2/8/22 a las 04:33, Camaleón escribió:

El 2022-08-02 a las 03:27 -0300, Daniel escribió:

Buf... quito el formato html, mi pobre Mutt sólo ve una morcilla.

(...)


   Resumiendo: la misma aplicación/script hecha en Processing (y
   ejemplos similares que usan OpenGL) funciona perfecto desde el
   fuente, con el IDE de Processing corriendo (ejecutado usando la
   sintaxis con la variable de entorno antes ya comentada). Pero el
   ejecutable compilado no funciona si usa "P2D" o "P3D" (incluso
   seteando la variable de entorno que soluciona todo corriendo
   Processing).

(...)

Prueba con algunas de las opciones que indican por aquí:

3D amb processing
https://wiki.controlonline.net:1029/doku.php?id=tutorials:processing:19_3d

Principalmente, introducir dentro del código de la aplicación la opción
para desactivar «openglcore», porque entiendo que las otras dos
opciones ya las has probado sin éxito.

La página está en valenciano, si quieres traducirla con Google elige
la pareja Catalán a Español.

Saludos,

adduser

[Alex PADOLY]

Bonsoir à tous,

Alors que sous Debian 8, je pouvais ajouter des utilisateurs avec la 
commande adduser en mode console.


Sous Debian 8 avec le bureau LXQT, ce n'est pas possible, la commande 
adduser n'est pas reconnu en mode console.


Il faut passer par une petite application LXQT-paramétrage du système 
puis utilisateurs et groupes.


Quelqu'un d'entre, vous connait-il, la raison de cette restriction.

Merci pour vos précisions.

Alex

Adduser only one or. two users

[Ishaan Mahajan]

Hi,

This is the line I have got - RUN sudo adduser --shell $USERSHELLPATH
--disabled-password --gecos "" $USERNAME && \
echo "$USERNAME ALL=(ALL) NOPASSWD: ALL" > /etc/sudoers.d/$USERNAME && \
chmod 0440 /etc/sudoers.d/USERNAME
However, I keep getting the error,
adduser: Only one or two names allowed.--
How do I get around this?
Have a great day ahead!

Best,
Ishaan Mahajan

Re: Debian testing op de desktop bij Google

[Paul van der Vlis]

Op 04-08-2022 om 15:15 schreef hanbenes:


Stapt Debian helemaal over op rolling?


Nee, stable blijft bestaan, en dat is niet rolling. ( Behalve een paar 
pakketten zoals Thunderbird, Firefox, en Chromium. Deze bleken niet goed 
te handhaven als stable pakket, de security fixes waren te moeilijk. )


Naast stable heb je echter ook "unstable" en "testing", die twee zijn 
wel rolling.


"Rolling" betekent dat je elke keer nieuwe versies krijgt van allerlei 
programma's. Daarbij kan meer mis gaan dan bij "stable", waar dat niet 
zo is.


Groet,
Paul.


--
Paul van der Vlis Linux systeembeheer Groningen
https://vandervlis.nl/

Re: Debian testing op de desktop bij Google

[Geert Stappers]

On Thu, Aug 04, 2022 at 01:15:53PM +, hanbenes wrote:
> Op donderdag 4 augustus 2022 om 11:35 schreef Paul van der Vlis:
> > Hoi,
> >
> > Ik dacht altijd dat Google Ubuntu gebruikte op de desktop. Ze blijken
> > dat echter vervangen te hebben door Debian testing. Ik vond onderstaande
> > een interessant verhaal:
> >
> > https://cloud.google.com/blog/topics/developers-practitioners/how-google-got-to-rolling-linux-releases-for-desktops
> >
> 
> Stapt Debian helemaal over op rolling?
> 

Verzoek: vermijd ja-nee-vragen
 

> > Zelf vind ik het ook wel een boel gedoe, steeds die upgrades om de twee
> > jaar, dus ik vind er wel wat inzitten.

Ja, met "testing" is de computer bij-de-tijd en heb geen grote sprongen
in updates.



Groeten
Geert Stappers
-- 
Silence is hard to parse

Re: VFAT vs. umask.

[peter]

From: Charles Curley 
Date: Sat, 30 Jul 2022 13:39:00 -0600
> The preparation of any storage medium requires at least two steps. To 
> format means ...
> 
> In another step one lays down a file system: ...

Understood, at a superficial level at least.  Haven't invented or 
implemented a file system.

> Microsoft conflated the two, leading to much confusion over the 
> years.

Even prominent software uses "format" loosely.  Eg. Gparted > 
Partition > Format to > ... .

If we really want to improve terminology we need to 
(1) understand intimately software such as gparted, 
(2) find or invent terms more specific than "format",
(3) convince maintainers to fix the bugs (adopt the new terms) and 
(4) take credit for the revolutionary improvements.  =8~)

> Try mounting it from the command line, and watch the output. That will
> show you whether it is being fscked. However, FAT has no ability to
> store when it was last fscked, so I would wonder why it was being
> fscked at all.

In further observations, the problem is primarily in the old Fedora 
based OLPC XO system.  Debian Bullseye usually recognizes and mounts 
the f.s. on the SD card with no difficulty.  Rather than troubleshoot 
the obsolete system I'll continue an effort to make DebXO work on the 
XO 1.5 machine.

Thx,   ... P.




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

Re: Nouveau Is (was: Nvidia + Plasma + Keyboard)

[Felix Miata]

Andrew M.A. Cater composed on 2022-08-04 10:20 (UTC):
...
> nouveau is a good and supported way forward.

NouveauS are.

It's deleterious to omit the fact that there are two separate functionality FOSS
Nouveaus, one of which, the Nouveau X display driver (DDX: Device Dependent X), 
is

reverse-engineered
old technology
non-functional, absent the other being loaded
optional (as in not needed, except for seriously ancient GPUs, mainly 
AGP)

The other is the kernel's Nouveau device driver, which provides KMS 
functionality
that the DDX, and the newer technology DIX (Device Independent X: Modesetting;
upstream default), and Mesa, depend on.

Given the kernel will load its Nouveau module automatically when an NVidia GPU 
is
present (and the Nouveau module is not blocked from loading), and the conceptual
superiority of the DIX over the DDX, it's probably better to mention Nouveau 
only
as the inferior option when discussing DIX suitability to task.
-- 
Evolution as taught in public schools is, like religion,
based on faith, not based on science.

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

Felix Miata

Re: Debian testing op de desktop bij Google

[hanbenes]

Verzonden met Proton Mail beveiligde e-mail.

--- Original Message ---
Op donderdag 4 augustus 2022 om 11:35 schreef Paul van der Vlis 
:


> Hoi,
>
> Ik dacht altijd dat Google Ubuntu gebruikte op de desktop. Ze blijken
> dat echter vervangen te hebben door Debian testing. Ik vond onderstaande
> een interessant verhaal:
>
> https://cloud.google.com/blog/topics/developers-practitioners/how-google-got-to-rolling-linux-releases-for-desktops
>

Stapt Debian helemaal over op rolling?


> Zelf vind ik het ook wel een boel gedoe, steeds die upgrades om de twee
> jaar, dus ik vind er wel wat inzitten.
>
> Ook hun servers schijnen Debian-based te zijn heb ik ooit gelezen,
> echter heel veel is aangepast.
>
> Groeten,
> Paul
>
>
> --
> Paul van der Vlis Linux systeembeheer Groningen
> https://vandervlis.nl/

Re: Re: No upgrade from 11.3 to 11.4 with apt update/upgrade

[Johan Kröckel]

Hi Klaus,

thank you but dist-upgrade had the same result.

'~# rm -R /var/lib/apt/lists/*; apt update; apt upgrade' worked.

Still don't know what was wrong...

Thanks again

Johan

Re: Re: Re: No upgrade from 11.3 to 11.4 with apt update/upgrade

[Johan Kröckel]

Thank you very much!

2) ~# rm -R /var/lib/apt/lists/* did the trick!

Btw:
1) That's not Ubuntu but the Signal desktop client and the correct
repository. Confuses me all the time as well.

Re: Re: No upgrade from 11.3 to 11.4 with apt update/upgrade

[Greg Wooledge]

On Thu, Aug 04, 2022 at 01:27:21PM +0200, Johan Kröckel wrote:
> ~# date; cat /etc/apt/sources.list;apt update; apt upgrade; apt-cache
> policy base-files
[...]
> OK:1 http://security.debian.org/debian-security bullseye-security InRelease
> OK:2 http://packages.microsoft.com/repos/code stable InRelease
> 
> 
> OK:3 https://updates.signal.org/desktop/apt xenial InRelease
> 
> 
> OK:4 https://deb.debian.org/debian-security bullseye-security InRelease
> 
> 
> OK:5 https://deb.debian.org/debian bullseye InRelease
> 
> OK:6 https://dl.google.com/linux/chrome/deb stable InRelease
> 
> OK:7 https://packages.microsoft.com/repos/microsoft-debian-bullseye-prod
> bullseye InRelease
> OK:8 https://deb.debian.org/debian bullseye-updates InRelease
> OK:9 https://deb.debian.org/debian bullseye-backports InRelease

You've got other entries in /etc/apt/sources.list.d/ that you haven't
shown, and at least one of them contains Ubuntu packages (xenial).

>   Installiert:   11.1+deb11u3
>   Installationskandidat: 11.1+deb11u3
>   Versionstabelle:
>  *** 11.1+deb11u3 500
> 500 https://deb.debian.org/debian bullseye/main amd64 Packages
> 100 /var/lib/dpkg/status
> 
> Hope, this is complete enough.

I can only think of three things here.

1) Maybe that xenial line is breaking something.  I would definitely not
   have ANYTHING from Ubuntu on a Debian system.  That said, I don't know
   precisely how it would break things without leaving visible traces.

2) Maybe your lists (in /var/lib/apt/lists/) are wrong somehow, in a way
   that's preventing "apt update" from retrieving the current ones.  You
   could try removing the deb.debian.org_* lists, and re-running apt
   update.

3) Maybe deb.debian.org keeps giving you a mirror that isn't in sync.
   You could try a country-specific mirror instead.

Re: No upgrade from 11.3 to 11.4 with apt update/upgrade

[Klaus Singvogel]

Johan Kröckel wrote:
> Hi,
> I think I am missing something minor but I don't get it.

Whereas I missed: apt-get dist-upgrade

Best regards,
Klaus.
-- 
Klaus Singvogel
GnuPG-Key-ID: 1024R/5068792D  1994-06-27

Re: Re: No upgrade from 11.3 to 11.4 with apt update/upgrade

[Johan Kröckel]

Sorry, that was misunderstandable. I run apt update/apt upgrade daily.

~# date; cat /etc/apt/sources.list;apt update; apt upgrade; apt-cache
policy base-files
Do 4. Aug 13:25:38 CEST 2022
deb https://deb.debian.org/debian-security bullseye-security main contrib
non-free
deb-src https://deb.debian.org/debian-security bullseye-security main
contrib non-free

deb https://deb.debian.org/debian/ bullseye main non-free contrib
deb-src https://deb.debian.org/debian/ bullseye main non-free contrib

#deb http://deb.debian.org/debian/ bullseye main non-free contrib
#deb-src http://deb.debian.org/debian/ bullseye main non-free contrib

deb http://security.debian.org/debian-security bullseye-security main
contrib non-free
deb-src http://security.debian.org/debian-security bullseye-security main
contrib non-free

deb https://deb.debian.org/debian/ bullseye-updates main contrib non-free
deb-src https://deb.debian.org/debian/ bullseye-updates main contrib
non-free

deb https://deb.debian.org/debian/ bullseye-backports main contrib non-free
deb-src https://deb.debian.org/debian/ bullseye-backports main contrib
non-free
OK:1 http://security.debian.org/debian-security bullseye-security InRelease
OK:2 http://packages.microsoft.com/repos/code stable InRelease


OK:3 https://updates.signal.org/desktop/apt xenial InRelease


OK:4 https://deb.debian.org/debian-security bullseye-security InRelease


OK:5 https://deb.debian.org/debian bullseye InRelease

OK:6 https://dl.google.com/linux/chrome/deb stable InRelease

OK:7 https://packages.microsoft.com/repos/microsoft-debian-bullseye-prod
bullseye InRelease
OK:8 https://deb.debian.org/debian bullseye-updates InRelease
OK:9 https://deb.debian.org/debian bullseye-backports InRelease
Paketlisten werden gelesen… Fertig
Abhängigkeitsbaum wird aufgebaut… Fertig
Statusinformationen werden eingelesen… Fertig
Alle Pakete sind aktuell.
Paketlisten werden gelesen… Fertig
Abhängigkeitsbaum wird aufgebaut… Fertig
Statusinformationen werden eingelesen… Fertig
Paketaktualisierung (Upgrade) wird berechnet… Fertig
Das folgende Paket wurde automatisch installiert und wird nicht mehr
benötigt:
  linux-image-5.10.0-14-amd64
Verwenden Sie »apt autoremove«, um es zu entfernen.
0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
base-files:
  Installiert:   11.1+deb11u3
  Installationskandidat: 11.1+deb11u3
  Versionstabelle:
 *** 11.1+deb11u3 500
500 https://deb.debian.org/debian bullseye/main amd64 Packages
100 /var/lib/dpkg/status

Hope, this is complete enough.

Re: Gestion du ventilateur sur un PC portable.

[Dethegeek]

C'est assez énervant ces stratégies marketing. Ca en devient mensonger.

Le chipset de la machine est de Intel Il ne doit pas y avoir grand chose à
bidouiller, ca me semble bien supporté par linux, et il ne doit pas y avoir
grand chose à améliorer, non ?

Le jeu. 4 août 2022 à 13:08, Rand Pritelrohm  a
écrit :

> Donc à voir du côté des pilotes (firmwares de la mobo, essayer avec une
> autre distro) et de la dissipation thermique (pâte, débourrage des
> ventilos etc.).
>
> J'imagine que la vérification a été faite, mais reste-t-il des
> processus zombies ou des tâches de type cron qui pourraient solliciter
> le CPU ?
>
> On Thu, 04 Aug 2022 10:36:12 +
> benoit  wrote:
>
> >Le jeudi 4 août 2022 à 10:20, Rand Pritelrohm
> > a écrit :
> >
> >
> >Bonjour,
> >>
> >>
> >> En consultant la documentation de Debian, il semblerait que "cpufreq"
> >> soit obsolète. Il est recommandé de passer sur "cpupower".
> >>
> >
> >Voilà j'ai changé
> >cpupower -c all frequency-set --governor powersave
> >
> >D'après powertop, les 2 cœurs font dodo
> >
> >CPU 0   CPU 1
> >1,60 GHz 0,0%0,0%
> >1333 MHz 0,0%0,0%
> >1067 MHz 0,0%0,0%
> >800 MHz 0,0%0,0%
> >Idle   100,0%  100,0%
> >
>
>
>
> --
> Rand Pritelrohm
>
>

Re: No upgrade from 11.3 to 11.4 with apt update/upgrade

[Greg Wooledge]

On Thu, Aug 04, 2022 at 12:23:26PM +0200, Johan Kröckel wrote:
> My sources.list is:
> 
> [...]
> deb https://deb.debian.org/debian/ bullseye main non-free contrib

Looks good.

> apt update; apt-cache policy base-files gives me:
> 
> base-files:
>   Installiert:   11.1+deb11u3
>   Installationskandidat: 11.1+deb11u3
>   Versionstabelle:
>  *** 11.1+deb11u3 500
> 500 https://deb.debian.org/debian bullseye/main amd64 Packages
> 100 /var/lib/dpkg/status
> 
> Shouldn't base-files (11.1+deb11u4) be already installed automatically?

Well, you didn't run anything that would have *installed* it, but it
should appear in the *** line under the version table.

Show us the output of "apt update" -- maybe it's encountering errors.

Re: Gestion du ventilateur sur un PC portable.

[Rand Pritelrohm]

Donc à voir du côté des pilotes (firmwares de la mobo, essayer avec une
autre distro) et de la dissipation thermique (pâte, débourrage des
ventilos etc.).

J'imagine que la vérification a été faite, mais reste-t-il des
processus zombies ou des tâches de type cron qui pourraient solliciter
le CPU ?

On Thu, 04 Aug 2022 10:36:12 +
benoit  wrote:

>Le jeudi 4 août 2022 à 10:20, Rand Pritelrohm
> a écrit :
>
>
>Bonjour,
>>
>>
>> En consultant la documentation de Debian, il semblerait que "cpufreq"
>> soit obsolète. Il est recommandé de passer sur "cpupower".
>>  
>
>Voilà j'ai changé
>cpupower -c all frequency-set --governor powersave
>
>D'après powertop, les 2 cœurs font dodo
>
>CPU 0   CPU 1
>1,60 GHz 0,0%0,0%
>1333 MHz 0,0%0,0%
>1067 MHz 0,0%0,0%
>800 MHz 0,0%0,0%
>Idle   100,0%  100,0%
>



-- 
Rand Pritelrohm

Re: Gestion du ventilateur sur un PC portable.

[benoit]

Le jeudi 4 août 2022 à 10:20, Rand Pritelrohm  a écrit 
:


Bonjour,
>
>
> En consultant la documentation de Debian, il semblerait que "cpufreq"
> soit obsolète. Il est recommandé de passer sur "cpupower".
>

Voilà j'ai changé
cpupower -c all frequency-set --governor powersave

D'après powertop, les 2 cœurs font dodo

CPU 0   CPU 1
1,60 GHz 0,0%0,0%
1333 MHz 0,0%0,0%
1067 MHz 0,0%0,0%
800 MHz 0,0%0,0%
Idle   100,0%  100,0%

No upgrade from 11.3 to 11.4 with apt update/upgrade

[Johan Kröckel]

Hi,
I think I am missing something minor but I don't get it.

My sources.list is:

deb https://deb.debian.org/debian-security bullseye-security main contrib
non-free
deb-src https://deb.debian.org/debian-security bullseye-security main
contrib non-free

deb https://deb.debian.org/debian/ bullseye main non-free contrib
deb-src https://deb.debian.org/debian/ bullseye main non-free contrib

#deb http://deb.debian.org/debian/ bullseye main non-free contrib
#deb-src http://deb.debian.org/debian/ bullseye main non-free contrib

deb http://security.debian.org/debian-security bullseye-security main
contrib non-free
deb-src http://security.debian.org/debian-security bullseye-security main
contrib non-free

deb https://deb.debian.org/debian/ bullseye-updates main contrib non-free
deb-src https://deb.debian.org/debian/ bullseye-updates main contrib
non-free

deb https://deb.debian.org/debian/ bullseye-backports main contrib non-free
deb-src https://deb.debian.org/debian/ bullseye-backports main contrib
non-free

apt update; apt-cache policy base-files gives me:

base-files:
  Installiert:   11.1+deb11u3
  Installationskandidat: 11.1+deb11u3
  Versionstabelle:
 *** 11.1+deb11u3 500
500 https://deb.debian.org/debian bullseye/main amd64 Packages
100 /var/lib/dpkg/status

Shouldn't base-files (11.1+deb11u4) be already installed automatically?

Thank you

Johan

Re: Nvidia + Plasma + Keyboard

[Andrew M.A. Cater]

On Thu, Aug 04, 2022 at 04:12:23AM -0400, Felix Miata wrote:
> Marco composed on 2022-08-04 06:51 (UTC):
> 
> > Thu, 04 Aug 2022 06:37:31 + Hans composed:
>  
> >> Did I miss telling it? On T520 it is GF119 (NVS4200) and in the
> >> Aspire it is GF-86M, both need *-340xx-* legacy drivers.
>  
> > For this generation of cards, nouveau works fine. I am running it with a
> > GeForce 210.
> > Please remove the proprietary driver and make sure you have
> > xserver-xorg-video-nouveau installed.
>  
> A GF119 GPU needs neither NVidia's proprietary driverS, nor the FOSS
> display driver provided by the xserver-xorg-video-nouveau package:
> # dpkg -l | grep veau
> ii  libdrm-nouveau2:amd64 2.4.112-3  amd64  Userspace interface to 
> nouveau-specific kernel DRM services -- runtime
> # inxi -GSaz --vs
> inxi 3.3.20-00 (2022-07-27)
> System:
>   Kernel: 5.18.0-3-amd64 arch: x86_64 bits: 64 compiler: gcc v: 11.3.0
> parameters: ro root=LABEL= ipv6.disable=1 net.ifnames=0
> selinux=0 plymouth.enable=0 consoleblank=0 vga=791
>   Desktop: Trinity v: R14.0.13 tk: Qt v: 3.5.0 info: kicker wm: Twin v: 3.0
> vt: 7 dm: 1: TDM 2: XDM Distro: Debian GNU/Linux bookworm/sid
> Graphics:
>   Device-1: NVIDIA GF119 [NVS 310] vendor: Hewlett-Packard driver: nouveau
> v: kernel non-free: series: 390.xx+ status: legacy-active (EOL~late 2022)
> arch: Fermi code: GF1xx process: 40/28nm built: 2010-16 pcie: gen: 1
> speed: 2.5 GT/s lanes: 16 ports: active: DP-1,DP-2 empty: none
> bus-ID: 01:00.0 chip-ID: 10de:107d class-ID: 0300
>   Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: modesetting
> unloaded: fbdev,vesa gpu: nouveau display-ID: :0 screens: 1
>   Screen-1: 0 s-res: 2560x2640 s-dpi: 120 s-size: 540x557mm (21.26x21.93")
> s-diag: 776mm (30.54")
>   Monitor-1: DP-1 pos: primary,bottom model: Acer K272HUL serial: 
> built: 2018 res: 2560x1440 hz: 60 dpi: 109 gamma: 1.2
> size: 598x336mm (23.54x13.23") diag: 686mm (27") ratio: 16:9 modes:
> max: 2560x1440 min: 720x400
>   Monitor-2: DP-2 pos: primary,top model: NEC EA243WM serial: 
> built: 2011 res: 1920x1200 hz: 60 dpi: 94 gamma: 1.2
> size: 519x324mm (20.43x12.76") diag: 612mm (24.1") ratio: 16:10 modes:
> max: 1920x1200 min: 640x480
>   OpenGL: renderer: NVD9 v: 4.3 Mesa 22.0.5 direct render: Yes
> #
> As evidenced above, the FOSS nouveau device driver provided by each kernel,
> and the FOSS modesetting display driver provided by xserver-xorg-core, are
> sufficient support for at least two displays using GF119 on Bookworm.
> -- 
> Evolution as taught in public schools is, like religion,
>   based on faith, not based on science.
> 
>  Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
> 
> Felix Miata
>

If these are laptops with dual chipsets, then nouveau can sometimes lock up.

You want bumblebee https://wiki.debian.org/Bumblebee and that should have
the appropriate mechanics to cope or Optimus.

Hope this helps - nouveau is a good and supported way forward.

All the very best, as ever,

Andy Cater

Re: Gestion du ventilateur sur un PC portable.

[benoit]

Le jeudi 4 août 2022 à 09:09, Dethegeek  a écrit :

> Bonjour,
>
> Pour creuser ce point il faudrait connaître le modèle exact du portable.

Bonjour,

C'est un Samsung NC10
Fiche technique :
Caractéristiques techniques
Type(s) Mini portable (Netbook)
Processeur Intel Atom N270
Fréquence processeur 1,6 GHz
Mémoire vive (RAM) 1 Go
# en fait j'en ai mi 4 Go de récup quand je l'utilisait avec un environnement 
de bureau
Type de mémoire vive DDR2-SDRAM
Capacité de stockage principal 160 Go
Type de stockage principal 5400tr/mn
# Changé pour un SSD

Interface stockage principal Serial ATA
Résolution WebCam 1,3 Mpx
Affichage
Taille d'écran 10,2 "
Format de l'écran 16:9
Définition de l'écran 1024 x 600
Puce graphique Intel Graphics Media Accelerator 950
Quantité de mémoire graphique Partagée 128 Mo
Cartes mémoire supportées
SD / MMC Oui
MicroSD Non
Entrées & sorties
Nombre de ports USB 2.0 3
Nombre de ports USB 3.0 0
Ports Thunderbolt 0
Support du Wi-Fi Wi-Fi 802.11b, Wi-Fi 802.11g
# je l'ai enlevée

Ethernet 10/100 Oui
Ethernet 100/1000 Non
Sortie son 2.0
Sortie S/PDIF Non
Sortie DisplayPort Non
Sortie HDMI Non

> Le jeu. 4 août 2022 à 08:31, Jean-Marc  a écrit :
>
>> J'ai eu un problème similaire avec un vieux HP.
>>
>> Le soucis de surchauffe venait de l'absence de micrologiciel non-libre
>>
>> pour la carte graphique.

C'est le GPU du CPU

Re: Gestion du ventilateur sur un PC portable.

[BERTRAND Joël]

benoit a écrit :
> Le mardi 2 août 2022 à 13:59, Rand Pritelrohm  a 
> écrit :
> 
>> Elle peut se gérer notamment via l'outil "cpupower" entièrement en
>> ligne de commande.
>>
> 
> Bonjour,
> 
> J'utilise cpufreqd est que ça fait la même chose ?
> D'après powertop il ne fait pas grand chose :
> 
> 1,60 GHz 0,0%
> 1333 MHz 0,0%
> 1067 MHz 0,0%
>  800 MHz 0,0%
> Idle   100,0%
> 
> 
> Ce qui est normal, je m'en sert pour faire du NAT, comme client VPN et 
> serveur nfs, pour les deux PC de la maison, autant dire qu'il n'a rien à 
> faire.
> C'est un Atom N270 @ 1.60GHz, ça ne dissipe presque rien : Typical TDP: 2.5 W
> Cf.
> https://www.cpubenchmark.net/cpu.php?cpu=Intel+Atom+N270+%40+1.60GHz=614

Typical TDP, c'est du marketing. Ça veut simplement dire que le CPU
consomme 2,5W pour une utilisation 'typique' d'après le fondeur. Autant
dire, un peu de bureautique sous Windows où le CPU est IDLE la plupart
du temps. Dans la vraie vie, il peu consommer beaucoup plus.

Un composant grand comme un Atom N270 doit pouvoir dissiper 2,5W dans
le plan de masse sans même avoir besoin d'un radiateur passif. Je fais
cela à longueur de journée. Le simple fait que le CPU soit muni d'un
ventilateur montre qu'il peut consommer largement plus que les 2,5W
annoncés.

JKB

Debian testing op de desktop bij Google

[Paul van der Vlis]

Hoi,

Ik dacht altijd dat Google Ubuntu gebruikte op de desktop. Ze blijken 
dat echter vervangen te hebben door Debian testing. Ik vond onderstaande 
een interessant verhaal:


https://cloud.google.com/blog/topics/developers-practitioners/how-google-got-to-rolling-linux-releases-for-desktops

Zelf vind ik het ook wel een boel gedoe, steeds die upgrades om de twee 
jaar, dus ik vind er wel wat inzitten.


Ook hun servers schijnen Debian-based te zijn heb ik ooit gelezen, 
echter heel veel is aangepast.


Groeten,
Paul


--
Paul van der Vlis Linux systeembeheer Groningen
https://vandervlis.nl/

Re: Gestion du ventilateur sur un PC portable.

[Rand Pritelrohm]

Bonjour,

Il faudrait également tester avec les différents "governor". Il y a la
théorie et le constaté.

En consultant la documentation de Debian, il semblerait que "cpufreq"
soit obsolète. Il est recommandé de passer sur "cpupower".


On Wed, 03 Aug 2022 18:56:18 +
benoit  wrote:

>Le mardi 2 août 2022 à 13:59, Rand Pritelrohm
> a écrit :
>
>> Elle peut se gérer notamment via l'outil "cpupower" entièrement en
>> ligne de commande.
>>  
>
>Bonjour,
>
>J'utilise cpufreqd est que ça fait la même chose ?
[…]


-- 
Rand Pritelrohm

Re: Nvidia + Plasma + Keyboard

[Felix Miata]

Marco composed on 2022-08-04 06:51 (UTC):

> Thu, 04 Aug 2022 06:37:31 + Hans composed:
 
>> Did I miss telling it? On T520 it is GF119 (NVS4200) and in the
>> Aspire it is GF-86M, both need *-340xx-* legacy drivers.
 
> For this generation of cards, nouveau works fine. I am running it with a
> GeForce 210.
> Please remove the proprietary driver and make sure you have
> xserver-xorg-video-nouveau installed.
 
A GF119 GPU needs neither NVidia's proprietary driverS, nor the FOSS
display driver provided by the xserver-xorg-video-nouveau package:
# dpkg -l | grep veau
ii  libdrm-nouveau2:amd64 2.4.112-3  amd64  Userspace interface to 
nouveau-specific kernel DRM services -- runtime
# inxi -GSaz --vs
inxi 3.3.20-00 (2022-07-27)
System:
  Kernel: 5.18.0-3-amd64 arch: x86_64 bits: 64 compiler: gcc v: 11.3.0
parameters: ro root=LABEL= ipv6.disable=1 net.ifnames=0
selinux=0 plymouth.enable=0 consoleblank=0 vga=791
  Desktop: Trinity v: R14.0.13 tk: Qt v: 3.5.0 info: kicker wm: Twin v: 3.0
vt: 7 dm: 1: TDM 2: XDM Distro: Debian GNU/Linux bookworm/sid
Graphics:
  Device-1: NVIDIA GF119 [NVS 310] vendor: Hewlett-Packard driver: nouveau
v: kernel non-free: series: 390.xx+ status: legacy-active (EOL~late 2022)
arch: Fermi code: GF1xx process: 40/28nm built: 2010-16 pcie: gen: 1
speed: 2.5 GT/s lanes: 16 ports: active: DP-1,DP-2 empty: none
bus-ID: 01:00.0 chip-ID: 10de:107d class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: modesetting
unloaded: fbdev,vesa gpu: nouveau display-ID: :0 screens: 1
  Screen-1: 0 s-res: 2560x2640 s-dpi: 120 s-size: 540x557mm (21.26x21.93")
s-diag: 776mm (30.54")
  Monitor-1: DP-1 pos: primary,bottom model: Acer K272HUL serial: 
built: 2018 res: 2560x1440 hz: 60 dpi: 109 gamma: 1.2
size: 598x336mm (23.54x13.23") diag: 686mm (27") ratio: 16:9 modes:
max: 2560x1440 min: 720x400
  Monitor-2: DP-2 pos: primary,top model: NEC EA243WM serial: 
built: 2011 res: 1920x1200 hz: 60 dpi: 94 gamma: 1.2
size: 519x324mm (20.43x12.76") diag: 612mm (24.1") ratio: 16:10 modes:
max: 1920x1200 min: 640x480
  OpenGL: renderer: NVD9 v: 4.3 Mesa 22.0.5 direct render: Yes
#
As evidenced above, the FOSS nouveau device driver provided by each kernel,
and the FOSS modesetting display driver provided by xserver-xorg-core, are
sufficient support for at least two displays using GF119 on Bookworm.
-- 
Evolution as taught in public schools is, like religion,
based on faith, not based on science.

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

Felix Miata

Re: Gestion du ventilateur sur un PC portable.

[Dethegeek]

Bonjour,

Pour creuser ce point il faudrait connaître le modèle exact du portable.


Le jeu. 4 août 2022 à 08:31, Jean-Marc  a écrit :

> J'ai eu un problème similaire avec un vieux HP.
>
> Le soucis de surchauffe venait de l'absence de micrologiciel non-libre
> pour la carte graphique.
>
> Sans ce micrologiciel, l'O/S n'arrivait pas à gérer correctement la
> carte et le PC surchauffait au point de s'éteindre.
>
> Une fois installé, plus de soucis.
>
> Peut-être est-ce une piste.
>
> Mes 2 centimes.
>
> Le 3/08/22 à 20:56, benoit a écrit :
> > Le mardi 2 août 2022 à 13:59, Rand Pritelrohm 
> a écrit :
> >
> >> Elle peut se gérer notamment via l'outil "cpupower" entièrement en
> >> ligne de commande.
> >>
> >
> > Bonjour,
> >
> > J'utilise cpufreqd est que ça fait la même chose ?
> > D'après powertop il ne fait pas grand chose :
> >
> > 1,60 GHz 0,0%
> > 1333 MHz 0,0%
> > 1067 MHz 0,0%
> >   800 MHz 0,0%
> > Idle   100,0%
> >
> >
> > Ce qui est normal, je m'en sert pour faire du NAT, comme client VPN et
> serveur nfs, pour les deux PC de la maison, autant dire qu'il n'a rien à
> faire.
> > C'est un Atom N270 @ 1.60GHz, ça ne dissipe presque rien : Typical TDP:
> 2.5 W
> > Cf.
> >
> https://www.cpubenchmark.net/cpu.php?cpu=Intel+Atom+N270+%40+1.60GHz=614
> >
> >
> > Et d'après sensors il est à +48.0°C par cette chaleur ça me paraît bien.
> >
> > --
> > Benoit
> >
>
> --
> Jean-Marc
>

AW: Re: Nvidia + Plasma + Keyboard

[hans . ullrich]

Nope, to understand, I want the proprietry driver, because the nouveau driver 
is too slow. Otherwise I could use the cpu inbuilt graphics chip, which is 
I915, but also slow.

My mail should also be seen as an info mail, not as a bugreport.

As I know about the issue, I am running every game or application, which needs 
speed, in XFCE or similar and not in plasma5.

However, I thought, I should tell you about the issue, because other might 
people might run into this issue too and wonder, what is responsibl.

Best

Hans



Am Thu, 4 Aug 2022 06:51:04 +, Marco  schrieb:

Am Thu, 04 Aug 2022 06:37:31 +
schrieb hans.ullr...@loop.de:

> Did I miss telling it? On T520 it is GF119 (NVS4200) and in the
> Aspire it is GF-86M, both need *-340xx-* legacy drivers.

For this generation of cards, nouveau works fine. I am running it with a
GeForce 210.
Please remove the proprietary driver and make sure you have
xserver-xorg-video-nouveau installed.
 

Re: Nvidia + Plasma + Keyboard

[Marco]

Am Thu, 04 Aug 2022 06:37:31 +
schrieb hans.ullr...@loop.de:

> Did I miss telling it? On T520 it is GF119 (NVS4200) and in the
> Aspire it is GF-86M, both need *-340xx-* legacy drivers.

For this generation of cards, nouveau works fine. I am running it with a
GeForce 210.
Please remove the proprietary driver and make sure you have
xserver-xorg-video-nouveau installed.

AW: Re: Nvidia + Plasma + Keyboard

[hans . ullrich]

Did I miss telling it? On T520 it is GF119 (NVS4200) and in the Aspire it is 
GF-86M, both need *-340xx-* legacy drivers.

Best regards

Hans



Am Thu, 4 Aug 2022 04:50:22 +, Marco  schrieb:

Am Wed, 03 Aug 2022 21:56:31 +0200
schrieb Hans :

> I am talking about the proprietary nvidia driver, nouveau is dead, as
> it is not more developed since a long time.

Which is wring, see the feature matrix there:
https://nouveau.freedesktop.org/FeatureMatrix.html

Please tell us, which GPU you have.
 

Re: Gestion du ventilateur sur un PC portable.

[Jean-Marc]

J'ai eu un problème similaire avec un vieux HP.

Le soucis de surchauffe venait de l'absence de micrologiciel non-libre 
pour la carte graphique.


Sans ce micrologiciel, l'O/S n'arrivait pas à gérer correctement la 
carte et le PC surchauffait au point de s'éteindre.


Une fois installé, plus de soucis.

Peut-être est-ce une piste.

Mes 2 centimes.

Le 3/08/22 à 20:56, benoit a écrit :

Le mardi 2 août 2022 à 13:59, Rand Pritelrohm  a écrit 
:


Elle peut se gérer notamment via l'outil "cpupower" entièrement en
ligne de commande.



Bonjour,

J'utilise cpufreqd est que ça fait la même chose ?
D'après powertop il ne fait pas grand chose :

1,60 GHz 0,0%
1333 MHz 0,0%
1067 MHz 0,0%
  800 MHz 0,0%
Idle   100,0%


Ce qui est normal, je m'en sert pour faire du NAT, comme client VPN et serveur 
nfs, pour les deux PC de la maison, autant dire qu'il n'a rien à faire.
C'est un Atom N270 @ 1.60GHz, ça ne dissipe presque rien : Typical TDP: 2.5 W
Cf.
https://www.cpubenchmark.net/cpu.php?cpu=Intel+Atom+N270+%40+1.60GHz=614


Et d'après sensors il est à +48.0°C par cette chaleur ça me paraît bien.

--
Benoit



--
Jean-Marc


OpenPGP_signature
Description: OpenPGP digital signature