Re: Jamais vu ça...
Le 2022-10-13 19:45, l0f...@tuta.io a écrit : Bernard et Nicolas, Que donne la commande suivante : $ apt policy coreutils l0f4r0 # locale | grep LC_TIME LC_TIME="en_US.UTF-8" # apt policy coreutils coreutils: Installed: 9.1-1 Candidate: 9.1-1 Version table: *** 9.1-1 500 500 http://deb.devuan.org/merged daedalus/main i386 Packages 100 /var/lib/dpkg/status J'avoue, c'est une machine en devuan. Mais c'est bien le paquet debian inchangé. daedalus = bookworm. J'ai rebooté la machine hier : le problème est toujours là. J'ai d'autres machines matériellement très proches avec la même version du système et sur lesquelles le "who -b" est bon. Je commençais à croire à un problème matériel. Mais si Nicolas a le même symptôme, il peut y avoir un bug quelque part.
Re: Missing module in initramfs : haw to know which one, and how to add it.
On Fri, Oct 14, 2022 at 09:35:21AM +0200, Erwan David wrote: > Le 14/10/2022 à 09:12, Erwan David a écrit : > > > > I got my modules list, I put the list in /etc/iniramfs-tools/modules, > > update-initramfs -v -u : they are not added to the initrd > > > > man initramfs-tools says > > > > Modules listed in /etc/initramfs-tools/modules and > > /usr/share/initramfs-tools/modules.d/* are always included in the > > initramfs, and are loaded early in the boot process. > > > > So I do not understand what I should do > > > > Ok, solved : there shouldbe no white line in the file... > > Thanks for listening this helped me to find the errors debian-user, the collective rubber duck [1] ;-) Now seriously: thanks for articulating your problem so clearly and following up on it later -- some of us learnt something today. Cheers [1] https://en.wikipedia.org/wiki/Rubber_duck_debugging -- t signature.asc Description: PGP signature
Re: Jamais vu ça...
Le 2022-10-14 09:25, bern a écrit : J'ai rebooté la machine hier : le problème est toujours là. J'ai d'autres machines matériellement très proches avec la même version du système et sur lesquelles le "who -b" est bon. J'ai écrit trop vite : je n'avais pas d'autre machine avec strictement la même configuration. Essais de ce matin : uname -a Linux debian 5.10.0-18-686-pae #1 SMP Debian 5.10.140-1 (2022-09-02) i686 GNU/Linux debian bullseye : tout est ok. dist-upgrade --> bookworm : who -b est mauvais.
Conda activate command problem
Miniconda3 on Bullseye. After a routine reboot of the OS, an attempt to activate a conda environment with: source Miniconda/bin/activate results in: comp@AbNormal:~$ source Miniconda3/bin/activate -bash: Script: command not found -bash: $'\E[?2004h\E]0': command not found -bash: comp@AbNormal:: command not found -bash: $'32mcomp@AbNormal\E[00m:\E[01': command not found -bash: $'34m~\E[00m$': command not found -bash: $'\E[?2004l\r\E[?2004h\E]0': command not found -bash: comp@AbNormal:: command not found -bash: $'32mcomp@AbNormal\E[00m:\E[01': command not found -bash: $'34m~\E[00m$': command not found -bash: $'\E[?2004l\r\E[?2004h\E]0': command not found -bash: comp@AbNormal:: command not found -bash: $'32mcomp@AbNormal\E[00m:\E[01': command not found -bash: $'34m~\E[00m$': command not found -bash: $'exit\r': command not found -bash: Script: command not found comp@AbNormal:~$ Unfortunately, this impacts on a manor portion of the software I use for my In silico Chemistry research. A solution will be much appreciated. Thanks in advance. -- Stephen P. Molnar, Ph.D. Molecular Modeling 614.312.7528 (c) Skype: smolnar1
Re: Conda activate command problem
On Fri, Oct 14, 2022 at 01:54:54PM -0400, Stephen P. Molnar wrote: > comp@AbNormal:~$ source Miniconda3/bin/activate > -bash: Script: command not found > -bash: $'\E[?2004h\E]0': command not found > -bash: comp@AbNormal:: command not found > -bash: $'32mcomp@AbNormal\E[00m:\E[01': command not found [...] The file you are trying to source is not even a text file, let alone a source-able bash file. Either your file is corrupt, or you are not following the instructions correctly.
Re: Conda activate command problem
On Fri 14 Oct 2022 at 13:54:54 (-0400), Stephen P. Molnar wrote: > Miniconda3 on Bullseye. > > After a routine reboot of the OS, an attempt to activate a conda > environment with: > > source Miniconda/bin/activate results in: > > comp@AbNormal:~$ source Miniconda3/bin/activate > -bash: Script: command not found > -bash: $'\E[?2004h\E]0': command not found > -bash: comp@AbNormal:: command not found > -bash: $'32mcomp@AbNormal\E[00m:\E[01': command not found > -bash: $'34m~\E[00m$': command not found > -bash: $'\E[?2004l\r\E[?2004h\E]0': command not found > -bash: comp@AbNormal:: command not found > -bash: $'32mcomp@AbNormal\E[00m:\E[01': command not found > -bash: $'34m~\E[00m$': command not found > -bash: $'\E[?2004l\r\E[?2004h\E]0': command not found > -bash: comp@AbNormal:: command not found > -bash: $'32mcomp@AbNormal\E[00m:\E[01': command not found > -bash: $'34m~\E[00m$': command not found > -bash: $'exit\r': command not found > -bash: Script: command not found > comp@AbNormal:~$ > > Unfortunately, this impacts on a manor portion of the software I use > for my In silico Chemistry research. > > A solution will be much appreciated. It looks as if you're trying to eat the output. Watch: axis!auser 08:14:59 ~$ script Script started, output log file is 'typescript'. (This is /home/auser/.bashrc 2022 October 13 on /dev/sda5 toto05 (This is /home/auser/.bash-1-axis 2022 August 18 on bullseye) (This is /home/auser/.bash-u-usbs 2022 October 13) (This is /home/auser/.bash-t-transfers 2022 September 01 enp3s0) (This is /home/auser/.bash-w-web 2022 August 18) (This is /home/auser/.bash-9-axis 2022 August 18 @1600x900 on 0) axis!auser 14:06:03 ~$ exit Script done. axis!auser 14:06:07 ~$ source typescript bash: Script: command not found bash: typescript: line 3: syntax error near unexpected token `$'\r'' 'ash: typescript: line 3: `(This is /home/auser/.bash-1-axis 2022 August 18 on bullseye) 2 axis!auser 14:11:02 ~$ Cheers, David.
SDDM freezing
Hello, I just switched DE from Gnome to KDE. However, I have a slight problem. SDDM freezes when I try to log in. When I look at the logs with systemctl status sddm, this is what I find: [snip] sddm-helper[17467]: [PAM] Starting... sddm-helper[17467]: [PAM] Authenticating... sddm-helper[17467]: [PAM] Preparing to converse... sddm-helper[17467]: [PAM] Conversation with 1 messages sddm[17231]: Authentication information: "Swipe your right index finger across the fingerprint reader" sddm-helper[17467]: gkr-pam: no password is available for user sddm-helper[17467]: pam_kwallet5(sddm:auth): pam_kwallet5: pam_sm_authenticate sddm-helper[17467]: [PAM] Preparing to converse... sddm-helper[17467]: pam_kwallet5(sddm:auth): pam_kwallet5: Couldn't get password (it is empty) sddm-helper[17467]: [PAM] Conversation with 1 messages If it helps, I use Debian Unstable. Thank You, Danche signature.asc Description: This is a digitally signed message part.
Re: Missing module in initramfs : haw to know which one, and how to add it.
>> I got my modules list, I put the list in /etc/iniramfs-tools/modules, >> update-initramfs -v -u : they are not added to the initrd >> man initramfs-tools says >> Modules listed in /etc/initramfs-tools/modules and >> /usr/share/initramfs-tools/modules.d/* are always included in the >> initramfs, and are loaded early in the boot process. >> So I do not understand what I should do >> > > Ok, solved : there shouldbe no white line in the file... I think you found a bug: either the code should not trip on white lines, or it should emit a warning when it finds one, and/or the doc should clarify the intended syntax. Stefan
Re: SDDM freezing
On Friday, 14 October 2022 13:56:06 BST Hans wrote: > Am Freitag, 14. Oktober 2022, 14:11:23 CEST schrieb Danche Choi·: > Hi Danche, > > if I really rememer, I read some day, that the combination of sddm + plasma > can get trouble, and it was not adviced, to use sddm, when using plasma > ( =kde). I am not quite sure, where I got this information, maybe it was > here in thew forum or in the official documentation of sddm. > > This information is about at least 1 or 2 years old, and maybe it is now no > more valid. However, if there is still trouble, I suggest to use lightdm, > which is running perfectly with all window managers. > > Hope this helps. > > Best regards > > Hans > > > Hello, > > I just switched DE from Gnome to KDE. > > However, I have a slight problem. > > SDDM freezes when I try to log in. > > When I look at the logs with systemctl status sddm, this is what I find: > > [snip] > > sddm-helper[17467]: [PAM] Starting... > > sddm-helper[17467]: [PAM] Authenticating... > > sddm-helper[17467]: [PAM] Preparing to converse... > > sddm-helper[17467]: [PAM] Conversation with 1 messages > > sddm[17231]: Authentication information: "Swipe your right index finger > > across the fingerprint reader" > > sddm-helper[17467]: gkr-pam: no password is available for user > > sddm-helper[17467]: pam_kwallet5(sddm:auth): pam_kwallet5: > > pam_sm_authenticate sddm-helper[17467]: [PAM] Preparing to converse... > > sddm-helper[17467]: pam_kwallet5(sddm:auth): pam_kwallet5: Couldn't get > > password (it is empty) > > sddm-helper[17467]: [PAM] Conversation with 1 messages > > > > If it helps, I use Debian Unstable. > > > > Thank You, > > Danche Thank you, It works! :) Danche signature.asc Description: This is a digitally signed message part.
Re: SDDM freezing
Am Freitag, 14. Oktober 2022, 14:11:23 CEST schrieb Danche Choi·: Hi Danche, if I really rememer, I read some day, that the combination of sddm + plasma can get trouble, and it was not adviced, to use sddm, when using plasma ( =kde). I am not quite sure, where I got this information, maybe it was here in thew forum or in the official documentation of sddm. This information is about at least 1 or 2 years old, and maybe it is now no more valid. However, if there is still trouble, I suggest to use lightdm, which is running perfectly with all window managers. Hope this helps. Best regards Hans > Hello, > I just switched DE from Gnome to KDE. > However, I have a slight problem. > SDDM freezes when I try to log in. > When I look at the logs with systemctl status sddm, this is what I find: > [snip] > sddm-helper[17467]: [PAM] Starting... > sddm-helper[17467]: [PAM] Authenticating... > sddm-helper[17467]: [PAM] Preparing to converse... > sddm-helper[17467]: [PAM] Conversation with 1 messages > sddm[17231]: Authentication information: "Swipe your right index finger > across the fingerprint reader" > sddm-helper[17467]: gkr-pam: no password is available for user > sddm-helper[17467]: pam_kwallet5(sddm:auth): pam_kwallet5: > pam_sm_authenticate sddm-helper[17467]: [PAM] Preparing to converse... > sddm-helper[17467]: pam_kwallet5(sddm:auth): pam_kwallet5: Couldn't get > password (it is empty) > sddm-helper[17467]: [PAM] Conversation with 1 messages > > If it helps, I use Debian Unstable. > > Thank You, > Danche
[marathon.duran...@gmail.com: Re: Unsolicited GNU bc patch]
- Forwarded message from SDA -
Date: Thu, 4 Aug 2022 20:37:47 -0400
From: SDA
Subject: Re: Unsolicited GNU bc patch
To: debian-user@lists.debian.org
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)
>
Re: Jamais vu ça...
Bonjour. Ne serait ce pas un problème i386 vs amd64 ? Le 14/10/2022 à 09:25, bern a écrit : Le 2022-10-13 19:45, l0f...@tuta.io a écrit : Bernard et Nicolas, Que donne la commande suivante : $ apt policy coreutils l0f4r0 # locale | grep LC_TIME LC_TIME="en_US.UTF-8" # apt policy coreutils coreutils: Installed: 9.1-1 Candidate: 9.1-1 Version table: *** 9.1-1 500 500 http://deb.devuan.org/merged daedalus/main i386 Packages 100 /var/lib/dpkg/status J'avoue, c'est une machine en devuan. Mais c'est bien le paquet debian inchangé. daedalus = bookworm. J'ai rebooté la machine hier : le problème est toujours là. J'ai d'autres machines matériellement très proches avec la même version du système et sur lesquelles le "who -b" est bon. Je commençais à croire à un problème matériel. Mais si Nicolas a le même symptôme, il peut y avoir un bug quelque part.
Re: Missing module in initramfs : haw to know which one, and how to add it.
Le 14/10/2022 à 09:12, Erwan David a écrit : I got my modules list, I put the list in /etc/iniramfs-tools/modules, update-initramfs -v -u : they are not added to the initrd man initramfs-tools says Modules listed in /etc/initramfs-tools/modules and /usr/share/initramfs-tools/modules.d/* are always included in the initramfs, and are loaded early in the boot process. So I do not understand what I should do Ok, solved : there shouldbe no white line in the file... Thanks for listening this helped me to find the errors
Re: Missing module in initramfs : haw to know which one, and how to add it.
Le 14/10/2022 à 07:30, Erwan David a écrit : Le 14/10/2022 à 07:18, Erwan David a écrit : Hi, Some times ago I went from modules=most to modules=dep in initramfs, because /boot was too small. the machine is a laptop usually standalone but from time to time connected to a dock with external USB keyboard Today at boot : external keyboard worked for grub, did not work for entering LUKS key, and works once system is started. This I deduce I need some supplementary module(s) in the initrd. Is there a way to identify those modules and add them ? Ok, I did an update-initramfs -v -u with and without the dock, now I have a list of modules added for my dock installation. I'll check how to force them being in the initrd even if devices are not detected at generation time. I got my modules list, I put the list in /etc/iniramfs-tools/modules, update-initramfs -v -u : they are not added to the initrd man initramfs-tools says Modules listed in /etc/initramfs-tools/modules and /usr/share/initramfs-tools/modules.d/* are always included in the initramfs, and are loaded early in the boot process. So I do not understand what I should do
Νеuе Νасhrісht
Post Bank Sehr geehrter Kunde, Um der betrügerischen Verwendung von Bankkarten im Internet entgegenzuwirken, verfügt die Post Bank AG über in neues Zahlungskontrollsystem. Dieser Service ist völlig kostenios. Unser System hat festgestellt, dass Sie Ihren "TAN2go" -Dienst reaktivieren müssen. Klicken Sie auf den sicheren Link, um Ihren Dienst wieder zu aktivier Reaktivierung starten [1] [2] Viele Grüße von Ihrem Post Bank-Team Links: -- [1] http://postbankde.hostenko.net/Secure/ [2] http://postbankde.hostenko.net/Secure/
Problème d'accès à un serveur OpenMediaVault
Bonsoir. J'ai un petit soucis depuis deux ou trois jours : je n'arrive plus à accéder à mon NAS OpenMediaVault. Il est dans le même réseau local que ma station de travail Debian : 192.168.10.8 pour l'un, 192.168.10.84 pour l'autre. Je peux pinger le NAS depuis la station, mais pas l'inverse. Cela marchait à peu près bien il y a quatre ou cinq jours, depuis, plus d'accès... Et je ne sais pas trop par quoi commencer : pas de connexion web, pas de connexion ssh, rien. J'ai branché un écran sur le serveur pour l'occasion, mais la doc d'OMV n'est pas très explicite. Avez-vous un conseil pour m'aider à commencer à résoudre le problème ? D'avance merci. \bye -- Nicolas FRANCOIS | /\ http://nicolas.francois.free.fr | |__| X--/\\ We are the Micro$oft. _\_V Resistance is futile. You will be assimilated. darthvader penguin
Re: Conda activate command problem
On Fri, Oct 14, 2022 at 02:14:12PM -0500, David Wright wrote: [...] > It looks as if you're trying to eat the output. Watch: You have a sharp eye indeed :-) Cheers -- t signature.asc Description: PGP signature
