Fwd: Wayland and NVidia driver conflict

[Luna Jernberg]

-- Forwarded message -
Från: inkrm 
Date: tors 13 juli 2023 kl 23:48
Subject: Wayland and NVidia driver conflict
To: 


Hi
I just installed Debian 12 'Bookworm' with KDE Plasma 5.27.5 , and I
installed NVidia driver on my machine, following the official guide
(https://wiki.debian.org/NvidiaGraphicsDrivers#Debian_12_.22Bookworm.22).
When I rebooted my machine, I logged in Wayland, but it threw me back
into login manager.
I honestly prefer Wayland because it has better compatibility with 4K
HiDPI displays (which I have), but I can't use it properly, and
instead I have to use X11.
I searched on web but didn't find anything, so I am writing this
email, to ask what do I do.
I'm gonna be very pleased to read your response.

Kind regards, inkrm
--
Sent with Tutanota

Re: Migrating system from u-sd to nvme memory on arm64's?

[gene heskett]

On 7/13/23 09:21, Stefan Monnier wrote:

I'm not sure that this is correct. I have several SSDs around here, all
several years old, all with swap partitions and all in daily use. None
has failed me yet.

Most modern SBC images for Debian and Armbian don't have a swap
partition. It's not usually necessary and it provides a vector for wear on
the device.


Images for SBCs are fairly different from typical desktop/laptop
circumstances: there is no real "SSD" in most SBCs.  Instead they
typically have a small eMMC (if it all) that might hold the OS but not
much more and then the image itself is often expected to be on
a µSD card.

Putting swap on a µSD is often a bad idea because those cards are often
slow and they wear-endurance is rarely advertised (and apparently often
poor).


 Stefan
My own experience with u-sd's is that while an 8gb card will hold the 
average desktop install, it's failure rate is pretty bad.  Up it to 16gb 
and it lives a LOT longer, a year or more. Taking the hint, I've yet to 
find a failed 64gb and one of mine running linuxcnc with a light load 
there but contains a complete buildbot for linuxcnc and its realtime 
kernels on plugged in SSD's, is now 8 years old, it started with a 
wheezy install from raspios, now buster, and still working well.  My 
theory is that the more empty room the u-sd has to attend to its 
internal housekeeping, the longer it will live. Slower than the SSD's by 
 a 30/1 difference, but serviceable.  The SSD's, plugged into the 
rpi4b's usb3 ports, checks out at around 600mb/sec, while the u-sd's are 
12 to 20 mb/sec. Boringly slow, but still working with df showing full 
capacity.


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: Migrating system from u-sd to nvme memory on arm64's?

[Stefan Monnier]

> root@sentinel:/var/s3# sudo nvme smart-log /dev/nvme0n1

Aha, apparently the trick is to use NVMe drives, where the SMART data is
more readable than for (S)ATA drives.

Thanks,


Stefan

Re: Trouble with nvidia drivers in Debian 12 Bookworm

[Sam Clearman]

Solved my own problem: I had to do `apt install
linux-headers-cloud-amd64` instead of `apt install
linux-headers-amd64`

On Thu, Jul 13, 2023 at 2:28 PM Sam Clearman  wrote:
>
> Hi,
> I'm trying to get a Tesla T4 working under Debian 12.
>
> So far I've tried two approaches:
> 1. Using the Debian provided drivers, per
> https://wiki.debian.org/NvidiaGraphicsDrivers
> 2. Using the nVidia provided drivers installed via runfile, per
> https://docs.nvidia.com/datacenter/tesla/tesla-installation-notes/index.html
>
> For 1 (installing the drivers in the debian nonfree repository),
> everything seems to install fine but the drivers don't load properly.
> Systemctl returns the following:
>
> $ systemctl status systemd-modules-load
> × systemd-modules-load.service - Load Kernel Modules
>  Loaded: loaded (/lib/systemd/system/systemd-modules-load.service; static)
>  Active: failed (Result: exit-code) since Thu 2023-07-13 21:05:08
> UTC; 18min ago
>Docs: man:systemd-modules-load.service(8)
>  man:modules-load.d(5)
> Process: 220 ExecStart=/lib/systemd/systemd-modules-load
> (code=exited, status=1/FAILURE)
>Main PID: 220 (code=exited, status=1/FAILURE)
> CPU: 29ms
>
> Jul 13 21:05:08 localhost systemd-modules-load[226]: modprobe: ERROR:
> could not insert 'nvidia': Invalid argument
> Jul 13 21:05:08 localhost systemd-modules-load[230]: modprobe: FATAL:
> Module nvidia-current-modeset not found in directory
> /lib/modules/6.1.0-10-cloud-amd64
> Jul 13 21:05:08 localhost systemd-modules-load[223]: modprobe: ERROR:
> ../libkmod/libkmod-module.c:1047 command_do() Error running install
> command 'modprobe nvidia ; modprobe -i nvidia-current-modeset ' for m>
> Jul 13 21:05:08 localhost systemd-modules-load[223]: modprobe: ERROR:
> could not insert 'nvidia_modeset': Invalid argument
> Jul 13 21:05:08 localhost systemd-modules-load[232]: modprobe: FATAL:
> Module nvidia-current-drm not found in directory
> /lib/modules/6.1.0-10-cloud-amd64
> Jul 13 21:05:08 localhost systemd-modules-load[220]: Error running
> install command 'modprobe nvidia-modeset ; modprobe -i
> nvidia-current-drm ' for module nvidia_drm: retcode 1
> Jul 13 21:05:08 localhost systemd-modules-load[220]: Failed to insert
> module 'nvidia_drm': Invalid argument
> Jul 13 21:05:08 localhost systemd[1]: systemd-modules-load.service:
> Main process exited, code=exited, status=1/FAILURE
> Jul 13 21:05:08 localhost systemd[1]: systemd-modules-load.service:
> Failed with result 'exit-code'.
> Jul 13 21:05:08 localhost systemd[1]: Failed to start
> systemd-modules-load.service - Load Kernel Modules.
>
> When I try to use the runfile (specifically, this file:
> https://us.download.nvidia.com/tesla/535.54.03/NVIDIA-Linux-x86_64-535.54.03.run)
> it is unable to read the kernel headers that I have installed (if I
> don't specify a location, it says it can't find them, no matter which
> location I specify, it finds something unexpected about what's there).
>
> Any help is appreciated!
>
> PS: Secureboot is disabled, I get the following from mokutil:
> $ mokutil --sb-state
> SecureBoot disabled

Re: Convert PostScript .pfa to .pfb?

[Tom Browder]

On Thu, Jul 13, 2023 at 17:06 Dan Ritter  wrote:

> Tom Browder wrote:


> https://fontforge.org/docs/faq.html#faq-outline-conversion


Yes, Dan, I'm using that for the .pfb conversion since they show that. And
I do plan to try with .t1/.pfa after I get my .pfb converter working. I was
hoping someone had already tried it.

Thanks.

-Tom

Re: Migrating system from u-sd to nvme memory on arm64's?

[jeremy ardley]

On 14/7/23 06:25, Stefan Monnier wrote:

It's not obvious how to translate that to "30%".
Jeremy?  Do you remember what data made it possible to get this 30% estimate?



Further to my previous reply, I ran this on my SBC lan server. I'm 
certain the power on hours is wrong as it's been 100% for 2-3 years. Not 
that is does much other than handle mail and act as a DNS secondary so 
0% wear (100% available spare)



sudo nvme list
Node SN Model    Namespace 
Usage  Format   FW Rev
  
 - 
--  
/dev/nvme0n1 S4EUNJ0N451054H  Samsung SSD 970 EVO Plus 
250GB   1  26.86  GB / 250.06  GB    512   B +  0 B   
2B2QEXM7

root@sentinel:/var/s3# sudo nvme smart-log /dev/nvme0n1
Smart Log for NVME device:nvme0n1 namespace-id:
critical_warning            : 0
temperature                : 40 C
available_spare                : 100%
available_spare_threshold        : 10%
percentage_used                : 0%
endurance group critical warning summary: 0
data_units_read                : 196,248
data_units_written            : 1,441,922
host_read_commands            : 2,719,492
host_write_commands            : 73,956,721
controller_busy_time            : 119
power_cycles                : 37
power_on_hours                : 373
unsafe_shutdowns            : 18
media_errors                : 0
num_err_log_entries            : 35
Warning Temperature Time        : 0
Critical Composite Temperature Time    : 0
Temperature Sensor 1   : 40 C
Temperature Sensor 2   : 41 C
Thermal Management T1 Trans Count    : 0
Thermal Management T2 Trans Count    : 0
Thermal Management T1 Total Time    : 0
Thermal Management T2 Total Time    : 0

Re: Migrating system from u-sd to nvme memory on arm64's?

[jeremy ardley]

On 14/7/23 06:25, Stefan Monnier wrote:

It's not obvious how to translate that to "30%".
Jeremy?  Do you remember what data made it possible to get this 30% estimate?



sudo apt-get install nvme-cli

sudo nvme list
Node  Generic   SN 
Model    Namespace 
Usage  Format   FW Rev
- -  
 - 
--  
/dev/nvme0n1  /dev/ng0n1    S6P7NS0T202023W Samsung SSD 
970 EVO Plus 1TB 1 296.43  GB / 1.00  TB    512   B 
+  0 B   4B2QEXM7


sudo nvme smart-log /dev/nvme0n1
Smart Log for NVME device:nvme0n1 namespace-id:
critical_warning            : 0
temperature                : 30°C (303 Kelvin)
available_spare                : 100%
available_spare_threshold        : 10%
percentage_used                : 1%
endurance group critical warning summary: 0
Data Units Read                : 1,616,249 (827.52 GB)
Data Units Written            : 11,171,611 (5.72 TB)
host_read_commands            : 11,720,983
host_write_commands            : 193,399,215
controller_busy_time            : 2,314
power_cycles                : 17
power_on_hours                : 1,729
unsafe_shutdowns            : 13
media_errors                : 0
num_err_log_entries            : 0
Warning Temperature Time        : 0
Critical Composite Temperature Time    : 0
Temperature Sensor 1   : 30°C (303 Kelvin)
Temperature Sensor 2   : 35°C (308 Kelvin)
Thermal Management T1 Trans Count    : 0
Thermal Management T2 Trans Count    : 0
Thermal Management T1 Total Time    : 0
Thermal Management T2 Total Time    : 0

Re: Migrating system from u-sd to nvme memory on arm64's?

[Stefan Monnier]

> smartctl -a /dev/whatever produces SMART data which may include
> things like:
>
> 233 Media_Wearout_Indicator 0x0032   002   002   000Old_age   Always  
>  -   0
>  or
>
> 241 Total_LBAs_Written  0x0032   099   099   000Old_age   Always  
>  -   7395041209
>  or
>
> 177 Wear_Leveling_Count 0x0013   099   099   000Pre-fail  Always  
>  -   4
>
> Each of which tells you relevant things without being perfect
> predictors.

Any idea what those numbers actually mean?  Like what kind of units?
Is the `Wear_Leveling_Count` an approximation of the average number of
times are block has been (re)written?
Is an "LBA" a 512B block or a 4kB block or ...?

It's not obvious how to translate that to "30%".
Jeremy?  Do you remember what data made it possible to get this 30% estimate?

FWIW, here's the smartctl data on my current 12 year old 256GB SSD, with
swap on it (until 2 years ago, with a measly 4GB of RAM, now with 16GB):

  1 Raw_Read_Error_Rate 0x002f   199   199   000Pre-fail  Always   
-   9952
  5 Reallocated_Sector_Ct   0x0033   098   098   000Pre-fail  Always   
-   103
  9 Power_On_Hours  0x0032   098   098   000Old_age   Always   
-   9586
 12 Power_Cycle_Count   0x0032   076   076   000Old_age   Always   
-   23891
169 Unknown_Attribute   0x0013   253   253   010Pre-fail  Always   
-   8324191885568
173 Unknown_Attribute   0x0032   174   174   100Old_age   Always   
-   2431002739356
175 Program_Fail_Count_Chip 0x0032   098   098   010Old_age   Always   
-   72
176 Erase_Fail_Count_Chip   0x0032   100   100   010Old_age   Always   
-   0
177 Wear_Leveling_Count 0x0013   084   084   017Pre-fail  Always   
-   566
178 Used_Rsvd_Blk_Cnt_Chip  0x0013   076   076   010Pre-fail  Always   
-   1004
179 Used_Rsvd_Blk_Cnt_Tot   0x0013   076   076   010Pre-fail  Always   
-   1938
180 Unused_Rsvd_Blk_Cnt_Tot 0x0013   076   076   010Pre-fail  Always   
-   6382
181 Program_Fail_Cnt_Total  0x0032   098   098   010Old_age   Always   
-   103
182 Erase_Fail_Count_Total  0x0032   100   100   010Old_age   Always   
-   0
183 Runtime_Bad_Block   0x0013   098   098   010Pre-fail  Always   
-   103
187 Reported_Uncorrect  0x0032   090   090   000Old_age   Always   
-   9952
192 Power-Off_Retract_Count 0x0032   095   095   000Old_age   Always   
-   22568
194 Temperature_Celsius 0x0022   059   059   000Old_age   Always   
-   41 (Min/Max 15/63)
195 Hardware_ECC_Recovered  0x001a   001   001   000Old_age   Always   
-   9952
197 Current_Pending_Sector  0x0013   100   100   000Pre-fail  Always   
-   0
198 Offline_Uncorrectable   0x0030   100   100   000Old_age   Offline  
-   0
199 UDMA_CRC_Error_Count0x003e   253   253   000Old_age   Always   
-   0

Apparently it's been ON for the equivalent of only 1 year :-)
Not sure what those `Unknown_Attribute` represent: the numbers are large
enough to suggest it could count the total amount written, but if it's
counted in blocks, it seems very high, so it would have to be counted in
bytes, but 8TB sounds a bit low.


Stefan

Re: Convert PostScript .pfa to .pfb?

[Dan Ritter]

Tom Browder wrote: 
> I know the binary version of the PS fonts can be converted to TrueType by
> FontForge.
> 
> However, is there a way to convert from the PS ASCII version .pfa file to
> the binary .pfb file?

I think that fontforge can do it. Worth trying; it's packaged.

https://fontforge.org/docs/faq.html#faq-outline-conversion

-dsr-

Re: Migrating system from u-sd to nvme memory on arm64's?

[Stefan Monnier]

>> I'm not sure that this is correct. I have several SSDs around here, all
>> several years old, all with swap partitions and all in daily use. None
>> has failed me yet.
> Most modern SBC images for Debian and Armbian don't have a swap
> partition. It's not usually necessary and it provides a vector for wear on
> the device.

BTW, another data point: all(?) the macOS devices sold in the last 10
years have swap on an SSD :-)


Stefan

Re: Convert PostScript .pfa to .pfb?

[James H. H. Lampert]

On 7/13/23 2:28 PM, Tom Browder wrote:

I know the binary version of the PS fonts can be converted to TrueType by
FontForge.

However, is there a way to convert from the PS ASCII version .pfa file to
the binary .pfb file?


I have a very old font editor, that I used briefly (on a neighbor's 
WinDoze box -- I don't allow WinDoze in my house), circa 20 years ago (I 
don't recall of the top of my head what it was called), and I think it 
could convert PS Type 3 to PS Type 1.


So assuming my memory isn't playing tricks on me, it's been done. No 
idea, however, what will do it, that's currently available. You don't 
see much PS Type 3 any more, I'm afraid.


--
JHHL

Trouble with nvidia drivers in Debian 12 Bookworm

[Sam Clearman]

Hi,
I'm trying to get a Tesla T4 working under Debian 12.

So far I've tried two approaches:
1. Using the Debian provided drivers, per
https://wiki.debian.org/NvidiaGraphicsDrivers
2. Using the nVidia provided drivers installed via runfile, per
https://docs.nvidia.com/datacenter/tesla/tesla-installation-notes/index.html

For 1 (installing the drivers in the debian nonfree repository),
everything seems to install fine but the drivers don't load properly.
Systemctl returns the following:

$ systemctl status systemd-modules-load
× systemd-modules-load.service - Load Kernel Modules
 Loaded: loaded (/lib/systemd/system/systemd-modules-load.service; static)
 Active: failed (Result: exit-code) since Thu 2023-07-13 21:05:08
UTC; 18min ago
   Docs: man:systemd-modules-load.service(8)
 man:modules-load.d(5)
Process: 220 ExecStart=/lib/systemd/systemd-modules-load
(code=exited, status=1/FAILURE)
   Main PID: 220 (code=exited, status=1/FAILURE)
CPU: 29ms

Jul 13 21:05:08 localhost systemd-modules-load[226]: modprobe: ERROR:
could not insert 'nvidia': Invalid argument
Jul 13 21:05:08 localhost systemd-modules-load[230]: modprobe: FATAL:
Module nvidia-current-modeset not found in directory
/lib/modules/6.1.0-10-cloud-amd64
Jul 13 21:05:08 localhost systemd-modules-load[223]: modprobe: ERROR:
../libkmod/libkmod-module.c:1047 command_do() Error running install
command 'modprobe nvidia ; modprobe -i nvidia-current-modeset ' for m>
Jul 13 21:05:08 localhost systemd-modules-load[223]: modprobe: ERROR:
could not insert 'nvidia_modeset': Invalid argument
Jul 13 21:05:08 localhost systemd-modules-load[232]: modprobe: FATAL:
Module nvidia-current-drm not found in directory
/lib/modules/6.1.0-10-cloud-amd64
Jul 13 21:05:08 localhost systemd-modules-load[220]: Error running
install command 'modprobe nvidia-modeset ; modprobe -i
nvidia-current-drm ' for module nvidia_drm: retcode 1
Jul 13 21:05:08 localhost systemd-modules-load[220]: Failed to insert
module 'nvidia_drm': Invalid argument
Jul 13 21:05:08 localhost systemd[1]: systemd-modules-load.service:
Main process exited, code=exited, status=1/FAILURE
Jul 13 21:05:08 localhost systemd[1]: systemd-modules-load.service:
Failed with result 'exit-code'.
Jul 13 21:05:08 localhost systemd[1]: Failed to start
systemd-modules-load.service - Load Kernel Modules.

When I try to use the runfile (specifically, this file:
https://us.download.nvidia.com/tesla/535.54.03/NVIDIA-Linux-x86_64-535.54.03.run)
it is unable to read the kernel headers that I have installed (if I
don't specify a location, it says it can't find them, no matter which
location I specify, it finds something unexpected about what's there).

Any help is appreciated!

PS: Secureboot is disabled, I get the following from mokutil:
$ mokutil --sb-state
SecureBoot disabled

Convert PostScript .pfa to .pfb?

[Tom Browder]

I know the binary version of the PS fonts can be converted to TrueType by
FontForge.

However, is there a way to convert from the PS ASCII version .pfa file to
the binary .pfb file?

Thanks.

-Tom

Re: Migrating system from u-sd to nvme memory on arm64's?

[jeremy ardley]

On 14/7/23 04:39, jeremy ardley wrote:


On the topic of a swap partition, that is usually absent, as is the 
partitioning of the drive into various parts for O/S, user data etc. 
That's a 50 year old relic for use cases where you are running a 
timesharing server for multiple users with limited RAM and disk.



I omitted to mention, there is a modern use case for a swap partition. 
That is on a micro cloud server with only 1GB RAM


This is one of my Linode systems

root@localhost:~# swapon -s
Filename                Type        Size    Used    Priority
/dev/sdb   partition    524284 108052    -2
/swapfile  file        2097148 752    -3

And also a correction to my previous post about standard debian. The 
desktop version does come with a swap partition


root@client:~# swapon -s
Filename                Type        Size        Used Priority
/dev/nvme0n1p3  partition    1000444     
742724        -2

Re: Migrating system from u-sd to nvme memory on arm64's?

[jeremy ardley]

On 13/7/23 21:20, Stefan Monnier wrote:

Images for SBCs are fairly different from typical desktop/laptop
circumstances: there is no real "SSD" in most SBCs.  Instead they
typically have a small eMMC (if it all) that might hold the OS but not
much more and then the image itself is often expected to be on
a µSD card.



In my experience, eMMC was a rare and expensive add-on. SBCs usually ran 
on CF or SD, neither of which are 100% 'reliable' as in they can be 
trashed at any time for obscure reasons.


Later SBCs often have an option for eMMC but also have an SD slot. More 
modern SBCs have an M.2 PCIe slot, and even more modern SBC's can boot 
off the M.2 PCie device.


On the topic of a swap partition, that is usually absent, as is the 
partitioning of the drive into various parts for O/S, user data etc. 
That's a 50 year old relic for use cases where you are running a 
timesharing server for multiple users with limited RAM and disk.



Comparing partitions, this is my new out-of-the box Debian 12 system 
using defaults


root@client:~# df
Filesystem 1K-blocks  Used Available Use% Mounted on
udev    16366160 0  16366160   0% /dev
tmpfs    3279236  1952   3277284   1% /run
/dev/nvme0n1p2 958802032 259428436 650595408  29% /
tmpfs   16396176    188196  16207980   2% /dev/shm
tmpfs   5120    24  5096   1% /run/lock
/dev/nvme0n1p1    523248  5972    517276   2% /boot/efi
tmpfs    3279232  4988   3274244   1% /run/user/1000

And this is a new NanoPC-T6 SBC also running Debian 12 but with 
manufacturer customization and running of a SD card though it also has 
an unused M.2 PCIe drive


root@NanoPC-T6:~# df
Filesystem 1K-blocks    Used Available Use% Mounted on
udev 3981908   8   3981900   1% /dev
tmpfs 810964    1916    809048   1% /run
overlay 56020612 5976312  47191236  12% /
tmpfs    4057064   0   4057064   0% /dev/shm
tmpfs   5120   4  5116   1% /run/lock
tmpfs 811412 108    811304   1% /run/user/1001
/dev/mmcblk0p1   3838960 3838960 0 100% /media/jeremy/Debian 
12.0.0 amd64 1

tmpfs 811412  64    811348   1% /run/user/0

I don't see a swap partition in either of them, let alone the usual 
ancient partitioning.


(NB the NanoPC-T6 is an ARM device. I'm not sure where the amd64 bit 
comes from)

tightvnc vs. tigervnc vs. ?

[roger . tarani]

Bonjour, 

debian 11 ou 12 

Pour pouvoir utiliser avec n'importe quel client vnc (dont realvnc client assez 
utilisé), quel serveur vnc faut-il privilégier ? 
Je connais tightvnc et tigervnc. 
J'ai déjà installé tigervnc il y a 3-4 ans et me souviens d'un problème 
d'incompatibilité ou de difficulté à configurer un client realvnc. 

VNC est un protocole, mais l'implémentation peut varier... 
Surtout, quel DE faut-il utiliser ? Je vois divers tutos en ligne qui utilse 
xfce4. 

Sinon, avez-vous déjà essayé le protocole RDP, avec Xrdp ? (pareil ; le client 
RDP semble répandu) 
Est-ce pareil, mieux, moins bien que VNC ? 

Merci 

Re: getmail problem

[Christoph Brinkhaus]

Am Thu, Jul 13, 2023 at 08:18:07PM +0200 schrieb Pierre Frenkiel:

Hi Pierre,

> hi,
> 
> the problem with getmail is that it ignores my .getmailrc file:
> it is configured with gmail:
> 
> server = imap.gmail.com
> ...
> poll imap.gmail.com with proto IMAP auth password
> 
> but the getmail command gives:
>     SimpleIMAPRetriever:p.frenk...@imap.laposte.net:143:
> 
>    getmailrc: credential/login error (LOGIN command error: BAD [b'invalid
> command'])
> 
> ( my config is  in ~.getmailrc and .getmail/getmailrc )
> 
> has anybody an explanation?

Just a short in the dark - can it be that gmail does not accept imap on
port 143 anymore? Instead of imap please try imaps on port 993.

Kind regards,
Christoph


signature.asc
Description: PGP signature

Re: Debian 12 problema con Español de Argentina

[Marcelo Eduardo Giordano]

El 13/7/23 a las 14:10, JavierDebian escribió:

Fijate ésto:
# cat /etc/default/locale

Debería responder:
#  File generated by update-locale
LANG="es_AR.UTF-8"
LANGUAGE="es_AR:es" 

Efectivamente dice eso mismo.
Pero en moneda me sale euro y en Idioma me sale español de españa.
Lo que hice para solucionarlo en cambiar a mano, en opciones de idioma 
de kde (graficamente) la moneda y listo.

No era la solución que yo quería.
Gracias amigo--

RE: Mensaje de error en inicio

[alberto moreno martinez]

Bueno Señores.

la primera opción que amablemente me sugirió Gerardo la ejecuté con éxito pero 
no me funcionó.

para segunda:
Lo que me pide Camaleon:
Mi tarjeta gráfica es una GeForce RTX 3070 y tiene el driver Nvidia versión 
525.105.17
El comando lsmod | grep video arroja este resulatdo:
video  65536  2 asus_wmi,nvidia_modeset
wmi36864  5 
video,intel_wmi_thunderbolt,asus_wmi,wmi_bmof,mxm_wmi

Me gustaría saber porque no tengo el archivo 
"xorg.conf.nvidia-xconfig-original" y en su lugar tengo esa carpeta de vacía de 
nombre "xorg.conf.d"
Gracias.

De: Camaleón 
Enviado: jueves, 13 de julio de 2023 8:09 a. m.
Para: debian-user-spanish 
Asunto: Re: Mensaje de error en inicio

El 2023-07-12 a las 20:34 +, alberto moreno martinez escribió:

(corrijo el top-posting, con el indentado no puedo hacer nada :-()
> 
> De: Camaleón 
> Enviado: miércoles, 12 de julio de 2023 8:15 a. m.
> Para: debian-user-spanish@lists.debian.org 
> 
> Asunto: Re: Mensaje de error en inicio
>
> El 2023-07-11 a las 19:56 +, alberto moreno martinez escribió:
>
> > Hola muchachos.
> > Hace unos días redimensioné la partición home de mi Debian, y desde 
> > entonces tengo unos mensajes en el inicio y el final del sistema. Los que 
> > más que inquietan son los del inicio. En el inicio aparece 11 veces el 
> > mensaje "EDAC skx: ECC is disabled on mic 0"
> > Antes había más y lo solucioné agregando al fichero "fstab" la UUID 
> > correcta de la SWAP; las demás UUID están correctas.
> > investigando he encontrado que puede ser un problema con la configuración 
> > del fichero "xorg.conf" que tiene que ver con la gráfica, pero no me atrevo 
> > a tocar esto así nomas y quedarme sin entorno gráfico o romper alguna otra 
> > cosa.
>
> En principio, y salvo que no puedas iniciar el sistema y trabajar con
> normalidad, o tengas algún otro problema, la presencia de ese mensaje
> (que nada tiene que ver con el particionado sino como bien dices, con
> la el controlador gráfico de nvidia) no debería tener mayor importancia.
>
> > Según este foro:
> >
> > https://stackoverflow.com/questions/63383981/error-edac-skx-ecc-is-disabled-on-imc-0-on-ubuntu-20-04
> >
> > la solución pasa por hacer esto:
> >
> > Go to tty mode and type following commands:
> >
> > cp /etc/X11/xorg.conf.nvidia-xconfig-original /etc/X11/xorg.conf
> > reboot
> >
> > Prefiero tener la opinión de ustedes antes de hacer cualquier cosa. Adjunto 
> > fotos del inicio, cierre y características del sistema, así como sus 
> > características principales. Mi tarjeta gráfica es una EVGA GeForce RTX 
> > 3070 con el último driver propietario.
> > Gracias por la colaboración.
>
> ¿Qué controlador gráfico usas? ¿El propietario de nvidia o nouveau?
>
> Lo que hace esa orden es restaurar el archivo de configuración original
> del servidor gráfico Xorg, pero no sé si con eso será suficiente para
> que error desaparezca.
>
> Probarlo no te va a doler, lo único que puede suceder es que no
> funcione, o que al reiniciar no se cargue el entorno gráfico, para lo
> cual, y como prevención, antes de ejecutar la orden puedes copiar a otro
> sitio el archivo xorg.conf original, si es que existe en tu sistema
> porque hace años que no lo veo ni se genera de manera predeterminada :-)

> Hola señores.
>
>  La primera opción
> >Creas un archivo nombre.conf en /etc/modprobe.d con la siguiente linea.
> >blacklist edac_core
> No me funcionó. el sistema no me permite crear tal archivo y tanpoco me 
> permite editar un archivo parecido que hay en /etc/modprobe.d llamado 
> "nvidia-blacklists-nouveau.conf"

A esto ya te han repsondido :-)

> En la segunda opción:
>
> "cp /etc/X11/xorg.conf.nvidia-xconfig-original /etc/X11/xorg.conf"
>
> Tampoco pude ejecutarla, ya que no tengo el archivo o carpeta 
> "xorg.conf.nvidia-xconfig-original" para reemplazarlo por "xorg.conf"
> Lo que tengo en "X11" es una carpeta de vacía de nombre "xorg.conf.d"
>
> Asi que estoy un poco perdido.

Todavía no nos has dicho qué controlador gráfico carga tu sistema para
la tarjeta gráfica. Ejecuta esta orden y manda la salida:

lsmod | grep video

> Por cierto, ya no recuerdo como es la forma correcta de responder a un hilo 
> sin que le llegue solo a uno de los que me responde y no sea visible para 
> todos. hice lo que creí correcto con las opciones que me da Outlook.
> Si me lo quieren recordar, gracias también.

Pues es sencillo: botón de «responder a la lista» >:-)

Si no existe esa opción en tu cliente de correo, cambia de cliente de
correo (ahora Thunderbird se ha puesto de gala con la nueva versión 115)
o emula el resultado manualmente, es decir, en el campo Para, pones la
dirección de la lista.

Saludos

--
Camaleón

getmail problem

[Pierre Frenkiel]

hi,

the problem with getmail is that it ignores my .getmailrc file:
it is configured with gmail:

server = imap.gmail.com
...
poll imap.gmail.com with proto IMAP auth password

but the getmail command gives:
    SimpleIMAPRetriever:p.frenk...@imap.laposte.net:143:

   getmailrc: credential/login error (LOGIN command error: BAD 
[b'invalid command'])


( my config is  in ~.getmailrc and .getmail/getmailrc )

has anybody an explanation?

best regards

Pierre Frenkiel

Re: Migrating system from u-sd to nvme memory on arm64's?

[Dan Ritter]

Charles Curley wrote: 
> On Thu, 13 Jul 2023 13:41:35 +0800
> jeremy ardley  wrote:
> 
> > In my personal experience, I ran a 500GB WD NVME drive on my
> > workstation without a swap partition and no surveillance. After 3
> > years It had worn it down 30%. Not a drama as I was swapping it out,
> > but surprising for just a workstation.
> 
> Interesting. Is there any way to tell the wear on an SSD, so one can
> replace it in a timely manner?

Yes, though it varies by particular disks.

smartctl -a /dev/whatever produces SMART data which may include
things like:

233 Media_Wearout_Indicator 0x0032   002   002   000Old_age   Always   
-   0
 or

241 Total_LBAs_Written  0x0032   099   099   000Old_age   Always   
-   7395041209
 or

177 Wear_Leveling_Count 0x0013   099   099   000Pre-fail  Always   
-   4

Each of which tells you relevant things without being perfect
predictors.


-dsr-

Re: Debian 12 problema con Español de Argentina

[JavierDebian]

El 13/7/23 a las 13:40, Marcelo Eduardo Giordano escribió:



# export LANGUAGE=es_AR.UTF-8
# export LANG=es_AR.UTF-8
# export LC_ALL=es_AR.UTF-8
# locale-gen es_AR.UTF-8
# dpkg-reconfigure locales

JAP


Tampoco funcionó...




Raro.

locale-gen y dpkg-reconfigure locales son EL método para fijar el lenguaje.

Fijate ésto:
# cat /etc/default/locale

Debería responder:
#  File generated by update-locale
LANG="es_AR.UTF-8"
LANGUAGE="es_AR:es"

Fijate acá:
https://wiki.debian.org/Locale

Se puede también en ~/.profile fijar la variable de entorno 
LC_ALL=es_AR.UTF-8, pero NO es aconsejable.


Si usás plasma:
$ cat ~/.config/plasma-localerc

debería ser:
[Formats]
LANG=es_AR.UTF-8

Y:
$ cat ~/.config/user-dirs.locale

debe ser:
es_AR

JAP

Re: Debian 12 problema con Español de Argentina

[Marcelo Eduardo Giordano]

# export LANGUAGE=es_AR.UTF-8
# export LANG=es_AR.UTF-8
# export LC_ALL=es_AR.UTF-8
# locale-gen es_AR.UTF-8
# dpkg-reconfigure locales

JAP


Tampoco funcionó...

Re: Bullseye upgrade - Mate desktop - Caja - por ssh no previsualiza jpg ni png.

[jacsenred]

> El 2023-07-10 a las 22:57 +, jacsenred escribió:

> Si antes te funcionaba y ahora no, la única diferencia parece el cambio
> de versiones tras actualizar el sistema. Es raro, sí...

Seguramente sea algo en la configuracion de caja, en $home/.config
Si encuentro la solucion la posteare.

> Mira ver qué sucede con ssh (esto funcionará siempre y cuando en el
> servidor tengas un entono gráfico instalado con Mate, si no es así,
> descártalo).
>
> Desde el cliente, lanza una terminal gráfica y ejecuta:
> ssh -X usuario_remoto@IP
>
> Y una vez dentro, ejecuta Caja, a ver si carga las miniaturas.

Si, he probado, pero caja no se abre...
Sin embargo pluma y/o xclock si lo hacen.

> Y en local supongo que te funciona sin problemas ¿no?

Si, efectivamente, en local no hay problema.

> > Me sucede que al loguearme en un primer momento en el TTY1, 2, 3, etc. no 
> > me carga el .bashrc.
> > Pasa tanto como root o como usuario.
> >
> > Eso si, si despues de logearme como usuario o como root lanzo una sesion 
> > embebida... ($su user) entonces ahora si lo carga!
>
> Mira a ver si se trata de un intérprete de inicio de sesión o no.
> Una vez dentro, ejecuta:
>
> echo $0
>
> Dependiendo del tipo de shell que hayas iniciado, leerá el archivo
> bashrc o profile en primer lugar.

Esto ya esta solucionado.
Me habia cepillado los archivo .profile, los he recuperado y ya esta 
solucionado.

Saludos a tod@s!
Y muchas gracias de nuevo Camaleon!

Re: Debian 12 problema con Español de Argentina

[Marcelo Eduardo Giordano]

En principio todo parece correcto.

¿Qué síntomas tienes, exactamente?

¿Aparecen mensajes en español de España en KDE o también desde la consola
o terminal?


Lo que aparece es la moneda Euro y en idioma en el escritorio me dice 
"Español de España"





Mira a ver qué te devuelve la orden «locale».

locale
LANG=es_ES.UTF-8
LANGUAGE=es
LC_CTYPE="es_ES.UTF-8"
LC_NUMERIC="es_ES.UTF-8"
LC_TIME="es_ES.UTF-8"
LC_COLLATE="es_ES.UTF-8"
LC_MONETARY="es_ES.UTF-8"
LC_MESSAGES="es_ES.UTF-8"
LC_PAPER="es_ES.UTF-8"
LC_NAME="es_ES.UTF-8"
LC_ADDRESS="es_ES.UTF-8"
LC_TELEPHONE="es_ES.UTF-8"
LC_MEASUREMENT="es_ES.UTF-8"
LC_IDENTIFICATION="es_ES.UTF-8"
LC_ALL=



Y acuérdate de reiniciar el sistema para que se apliquen los cambios que
hayas hecho tras añadir algún idioma o reconfigurar la localización.

Saludos,


Estoy reiniciando

Wifi getting disconnected

[Unni]

Hello,

I am using latest debian

--

# lsb_release -a
No LSB modules are available.
Distributor ID:    Debian
Description:    Debian GNU/Linux 12 (bookworm)
Release:    12
Codename:    bookworm

--


I've upgraded it from previous version recently. I started facing a 
network issue few days back. Wifi getting disconnected randomly and I've 
to access gnome network manager and disable/enable wifi to get it 
working. The log shows some module/kernel crash.



full log at http://paste.debian.net/hidden/72a8bc0c/

--

2023-07-13T20:42:02.872844+05:30 unni-debian 
google-chrome.desktop[3048]: Fontconfig error: Cannot load default 
config file: No such file: (null)
2023-07-13T20:42:06.273457+05:30 unni-debian systemd[1654]: Started 
app-gnome-org.gnome.Settings-7291.scope - Application launched by 
gnome-shell.
2023-07-13T20:42:06.735886+05:30 unni-debian gnome-shell[2288]: Window 
manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a 
timestamp of 0 for 0x3a4
2023-07-13T20:42:06.826057+05:30 unni-debian wpa_supplicant[842]: 
wlp9s0: CTRL-EVENT-SCAN-FAILED ret=-5
2023-07-13T20:42:06.829142+05:30 unni-debian kernel: [ 4671.249314] 
iwlwifi :09:00.0: Scan failed! ret -5

2023-07-13T20:42:06.835422+05:30 unni-debian geoclue[1173]: WiFi scan failed
2023-07-13T20:42:09.942165+05:30 unni-debian NetworkManager[839]: 
  [1689261129.9418] device (wlp9s0): state change: activated -> 
deactivating (reason 'new-activation', sys-iface-state: 'managed')
2023-07-13T20:42:09.942299+05:30 unni-debian NetworkManager[839]: 
  [1689261129.9421] manager: NetworkManager state is now DISCONNECTING
2023-07-13T20:42:09.943353+05:30 unni-debian NetworkManager[839]: 
  [1689261129.9432] device (wlp9s0): disconnecting for new 
activation request.
2023-07-13T20:42:09.943435+05:30 unni-debian NetworkManager[839]: 
  [1689261129.9433] audit: op="connection-activate" 
uuid="8c51ed15-cec5-4471-be62-3241bda6d6a3" name="JioFiber-velnix" 
pid=7291 uid=1000 result="success"
2023-07-13T20:42:09.945574+05:30 unni-debian dbus-daemon[773]: [system] 
Activating via systemd: service name='org.freedesktop.nm_dispatcher' 
unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.11' 
(uid=0 pid=839 comm="/usr/sbin/NetworkManager --no-daemon")
2023-07-13T20:42:09.993690+05:30 unni-debian systemd[1]: Starting 
NetworkManager-dispatcher.service - Network Manager Script Dispatcher 
Service...
2023-07-13T20:42:09.998223+05:30 unni-debian dbus-daemon[773]: [system] 
Successfully activated service 'org.freedesktop.nm_dispatcher'
2023-07-13T20:42:09.998425+05:30 unni-debian systemd[1]: Started 
NetworkManager-dispatcher.service - Network Manager Script Dispatcher 
Service.
2023-07-13T20:42:10.001135+05:30 unni-debian kernel: [ 4674.422848] 
wlp9s0: deauthenticating from 8c:a3:99:59:31:0c by local choice (Reason: 
3=DEAUTH_LEAVING)
2023-07-13T20:42:10.001141+05:30 unni-debian kernel: [ 4674.422863] 
iwlwifi :09:00.0: Failed to send MAC context (action:2): -5
2023-07-13T20:42:10.001142+05:30 unni-debian kernel: [ 4674.422867] 
iwlwifi :09:00.0: failed to update MAC 14:f6:d8:d7:fd:c5
2023-07-13T20:42:10.001142+05:30 unni-debian kernel: [ 4674.422870] 
iwlwifi :09:00.0: failed to update power mode
2023-07-13T20:42:10.025166+05:30 unni-debian kernel: [ 4674.444599] 
iwlwifi :09:00.0: Failed to send flush command (-5)
2023-07-13T20:42:10.025178+05:30 unni-debian kernel: [ 4674.444602] 
iwlwifi :09:00.0: flush request fail
2023-07-13T20:42:10.025179+05:30 unni-debian kernel: [ 4674.444643] 
[ cut here ]
2023-07-13T20:42:10.025181+05:30 unni-debian kernel: [ 4674.444644] 
WARNING: CPU: 10 PID: 842 at 
drivers/net/wireless/intel/iwlwifi/mvm/../iwl-trans.h:1354 
iwl_mvm_wait_sta_queues_empty+0x8e/0xc0 [iwlmvm]
2023-07-13T20:42:10.025182+05:30 unni-debian kernel: [ 4674.444661] 
Modules linked in: ctr ccm rfcomm cmac algif_hash algif_skcipher af_alg 
snd_seq_dummy snd_hrtimer snd_seq snd_seq_device qrtr bnep 
nvidia_drm(POE) binfmt_misc nls_ascii nls_cp437 vfat fat drm_kms_helper 
nvidia_modeset(POE) intel_rapl_msr intel_rapl_common edac_mce_amd 
kvm_amd kvm irqbypass nvidia(POE) iwlmvm btusb btrtl btbcm btintel btmtk 
mac80211 bluetooth snd_hda_codec_realtek snd_hda_codec_generic libarc4 
snd_hda_codec_hdmi snd_hda_intel iwlwifi snd_intel_dspcfg 
snd_intel_sdw_acpi snd_hda_codec jitterentropy_rng eeepc_wmi rapl 
snd_hda_core asus_wmi cfg80211 snd_hwdep drbg platform_profile snd_pcm 
battery sparse_keymap ledtrig_audio ansi_cprng snd_timer sp5100_tco ccp 
wmi_bmof video snd pcspkr rng_core watchdog ecdh_generic soundcore 
k10temp rfkill ecc acpi_cpufreq joydev sg evdev msr parport_pc ppdev lp 
parport drm fuse dm_mod loop efi_pstore configfs ip_tables x_tables 
autofs4 ext4 crc16 mbcache jbd2 btrfs blake2b_generic zstd_compress 
efivarfs raid10 raid456
2023-07-13T20:42:10.025187+05:30 unni-debian kernel: [ 4674.444718]  
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 

Re: Migrating system from u-sd to nvme memory on arm64's?

[Charles Curley]

On Thu, 13 Jul 2023 13:41:35 +0800
jeremy ardley  wrote:

> In my personal experience, I ran a 500GB WD NVME drive on my
> workstation without a swap partition and no surveillance. After 3
> years It had worn it down 30%. Not a drama as I was swapping it out,
> but surprising for just a workstation.

Interesting. Is there any way to tell the wear on an SSD, so one can
replace it in a timely manner?

-- 
Does anybody read signatures any more?

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

Re: Migrating system from u-sd to nvme memory on arm64's?

[Dan Ritter]

jeremy ardley wrote: 
> 
> On 13/7/23 19:00, debian-u...@howorth.org.uk wrote:
> > jeremy ardley  wrote:
> > 
> > > In the same vein, it's really a bad idea to run video surveillance on
> > > a SSD as overwriting the complete SSD every couple of weeks will
> > > trash it in no time. There are probably SSDs that boast to do this,
> > > but the standard now is using carefully designed spinning drives
> > > optimised for surveillance.
> > So all dashcams are junk?
> > 
> 
> I think you'll find dashcams have a removable CF card that can be replaced.
> Secondly dashcams don't routinely write to flash. They require a trigger
> such as a user input or collision detection to write the last few minutes to
> flash from RAM.
> 
> There will possibly be use-cases where a dashcam records continuously for
> extended periods but they are very unlikely to use a commodity CF card.

All the dashcams I am aware of write in N-minute chunks to their commodity
SD or microSD card, deleting the oldest when some number of chunks have been 
written,
unless a trigger causes them to mark the chunks for long-term storage.

I have owned five dashcams, all of which worked this way. The
RAM-to-disk-on-trigger functionality you are talking about is called
"parking mode", and is usually but not ubiquitously available.

Yes, dashcams wear out flash cards. Replace them annually.

-dsr-

Re: Migrating system from u-sd to nvme memory on arm64's?

[Stefan Monnier]

>> I'm not sure that this is correct. I have several SSDs around here, all
>> several years old, all with swap partitions and all in daily use. None
>> has failed me yet.
> Most modern SBC images for Debian and Armbian don't have a swap
> partition. It's not usually necessary and it provides a vector for wear on
> the device.

Images for SBCs are fairly different from typical desktop/laptop
circumstances: there is no real "SSD" in most SBCs.  Instead they
typically have a small eMMC (if it all) that might hold the OS but not
much more and then the image itself is often expected to be on
a µSD card.

Putting swap on a µSD is often a bad idea because those cards are often
slow and they wear-endurance is rarely advertised (and apparently often
poor).


Stefan

Re: Migration Bullseye vers Bookworm : échec lors du reboot

[ajh-valmer]

On Thursday 13 July 2023 08:54:54 Sébastien NOBILI wrote:
> Le 2023-07-13 01:03, Jean-Michel OLTRA a écrit :
> > Regarder les logs /var/log/Xorg.0.log ?
> > Vérifier que la version de Trinity est correcte pour Bookworm ?
> En plus de tout ça, vérifier si ça démarre avec un des bureaux fournis
> par Debian (Gnome par exemple).

J'ai résolu les problèmes lors du boot,exceptée la carte graphique,
qui maintenant n'est plus reconnue par bookworm, noyau 6.10.
Avec le noyau 5.22, ça marche mais sans souris ni clavier.

Quasi à chaque nouvelle version de Debian, le X graphique ne fonctionne plus.
Je dois souvent racheter une autre carte vidéo...
"nvidia-detect" a répondu que le pilote à installer 
est "nvidia-driver-370-tesla",
mais niet, refusé par le système au reboot.

Je cherche la méthode didactique avec "xserver-org-nouveau",
merci.

A. Valmer

Re: Migrating system from u-sd to nvme memory on arm64's?

[Stefan Monnier]

>> In either case they are detected as ordinary HDD drives and you need
>> do  nothing out of the ordinary other than it's preferable to not put
>> a swap  partition on them for wear reasons.
> Now you tell me . . . 

Don't worry: it's a sorely outdated recommendation.

There can still be circumstances where putting swap on an SSD is a bad
idea, but these are rare enough nowadays that it's not worth
a special mention.


Stefan

(deb-cat) Mida de blocs per a RAID de programari

[Narcis Garcia]

Bona tarda,

De vegades faig una instal·lació de Debian en un ordinador amb varis 
discs durs de mida similar i, apart d'una partició per a /boot al disc 
d'arrencada, amb la resta dels espais estableixo un conjunt RAID de 
programari.

Sovint estableixo RAID0 per accelerar equips antics o dispositius lents.

Hi ha controladors RAID de maquinari que pregunten de quina mida haurien 
de ser els blocs de dades a distribuir, però actualment això no ho veig 
al DebianInstaller.

Em sorgeixen 2 dubtes:
1. Com esbrinar la mida mínima de bloc que llegeix o escriu un disc dur.
2. Com variar aquesta mida de bloc del RAID amb el DebianInstaller.

Gràcies.

--

Narcis Garcia

__
I'm using this dedicated address because personal addresses aren't 
masked enough at this mail public archive. Public archive administrator 
should fix this against automated addresses collectors.

Re: Debian 12 problema con Español de Argentina

[JavierDebian]

El 12/7/23 a las 18:44, Marcelo Eduardo Giordano escribió:


El 12/7/23 a las 11:11, JavierDebian escribió:

Buen día.

# export LANGUAGE=es_ES.UTF-8
# export LANG=es_ES.UTF-8
# export LC_ALL=es_ES.UTF-8
# locale-gen es_ES.UTF-8
# dpkg-reconfigure locales


Javier:
Gracias por responder.
Prefiero preguntar antes de modificar algo.
Con esos comando vuelvo todo a español Argentina? eso quiero 
hacer... porque me parece que debería ser asi


# export LANGUAGE=es_AR.UTF-8
# export LANG=es_AR.UTF-8
# export LC_ALL=es_AR.UTF-8
# locale-gen es_ES.UTF-8
# dpkg-reconfigure locales

Corregime si me equivoco




Buen día.

Sí, casi, casi así para español de este bendito país.

# export LANGUAGE=es_AR.UTF-8
# export LANG=es_AR.UTF-8
# export LC_ALL=es_AR.UTF-8
# locale-gen es_AR.UTF-8
# dpkg-reconfigure locales

JAP

Re: Migrating system from u-sd to nvme memory on arm64's?

[jeremy ardley]

On 13/7/23 19:00, debian-u...@howorth.org.uk wrote:

jeremy ardley  wrote:


In the same vein, it's really a bad idea to run video surveillance on
a SSD as overwriting the complete SSD every couple of weeks will
trash it in no time. There are probably SSDs that boast to do this,
but the standard now is using carefully designed spinning drives
optimised for surveillance.

So all dashcams are junk?



I think you'll find dashcams have a removable CF card that can be 
replaced. Secondly dashcams don't routinely write to flash. They require 
a trigger such as a user input or collision detection to write the last 
few minutes to flash from RAM.


There will possibly be use-cases where a dashcam records continuously 
for extended periods but they are very unlikely to use a commodity CF card.

Re: Migrating system from u-sd to nvme memory on arm64's?

[debian-user]

jeremy ardley  wrote:

> In the same vein, it's really a bad idea to run video surveillance on
> a SSD as overwriting the complete SSD every couple of weeks will
> trash it in no time. There are probably SSDs that boast to do this,
> but the standard now is using carefully designed spinning drives
> optimised for surveillance.

So all dashcams are junk?

Re: xrdp and KDE Plasma desktop

[Max Nikulin]

On 12/07/2023 20:51, Petric Frank wrote:

If i look at the nmcli general permissions for the id i get:

   org.freedesktop.NetworkManager.network-control  auth

If i log in locally i get:

   org.freedesktop.NetworkManager.network-control  yes

It seems that something goes wrong - but what and how to fix it ?
I use the same userid both times.


Perhaps it is polkit that grants to local users more privileges than to 
remote ones, e.g. to reboot or to power off. Moreover, it (or some other 
daemon) may pass access e.g. to sound card on switch of currently active 
session when several local users are logged in.


Likely it is possible to change default policy to give more rights to a 
specific user even when a remote session is started.

Re: file descriptor VS file handle

[Thomas Schmitt]

Hi,

i wrote:
> > Why there are two sets of file accessing system calls must have historical
> > reasons.

to...@tuxteam.de wrote:
> [...] file descriptor is a
> kernel thing, FILE* is libc, i.e. userspace [1] (I know *you* know it,
> but it might be interesting for others).

Well, at least it did not come to me as explanation why there is FILE *.


Have a nice day :)

Thomas

Re: Feuille de calcul web + outil de sondage web

[RogerT]

Bonjour,

Ça a l’air très complet et surtout ergonomique (ex : changer la couleur d’une 
cellule en un clic comme dans un tableur ordinaire auquel on est habitués).

Ça offre le chiffrement de bout en bout en même temps que la collaboration. 
Pour ça, je lis qu’ils intègrent le client d’OnlyOffice Spreadsheets avec un 
serveur maison. 
https://docs.cryptpad.org/en/FAQ.html

S’il y avait une API, alors ce serait formidable. 

Merci.

> Le 13 juil. 2023 à 08:58, Sébastien NOBILI 
>  a écrit :
> 
> Bonjour,
> 
> Le 2023-07-12 18:26, RogerT a écrit :
>> A-t-on un logiciel alternatif un peu plus sympa pour l’utilisateur ?
>> Sondage « autre » : trop basique (oui/non/si nécessaire/ne se
> 
> Tu trouveras peut-être ton bonheur là : https://cryptpad.fr/
> 
> C'est libre et auto-hébergeable.
> 
> Sébastien
> 

Re: file descriptor VS file handle

[Nicolas George]

cor...@free.fr (12023-07-13):
> In linux systems, are file descriptor and file handle meaning the same
> stuff?

File descriptors are the standards Unix file descriptors.

In the Unix specification, the word handle is used to designate either a
file descriptor or a FILE * pointer of the stdio subsystem of the libc.

Regards,

-- 
  Nicolas George


signature.asc
Description: PGP signature

Re: file descriptor VS file handle

[tomas]

On Thu, Jul 13, 2023 at 08:49:38AM +0200, Thomas Schmitt wrote:
> Hi,
> 
> cor...@free.fr wrote:
> > In linux systems, are file descriptor and file handle meaning the same
> > stuff?
> 
> In the programming language C on Linux (more generally: on POSIX systems)
> "File descriptor" is an integer number handed out by system calls like
> open(2), pipe(2), socket(2), and others. It can be used by calls like
> read(2), write(2), recv(2), send(2) to get or to deliver data.
> (Execute e.g.
>man 2 open
> to get the manual page of the desired system call.)

Exactly.

> I am not aware that "file handle" has such a well defined meaning in
> POSIX. To my understanding it just means a programming object that can be
> used for similar activities as a file descriptor (and possibly for more
> file related activities).

In the Unix-ish C world it plainly doesn't exist. It is customary
in Perl to designate a data structure wrapping (among other things)
a file descriptor, but also buffers and things. Akin to a FILE * in
(POSIX-ish) C.

> Maybe you mean "file pointer", which usually refers to the return value
> "FILE *" of fopen(3) and can be used by calls like fread(3), fscanf(3),
> fwrite(3), or fprintf(3). This is implemented on top of file descriptor.
> The call fileno(3) can obtain the file descriptor of a file pointer, so
> that the above calls of man chapter 2 can be used.
> The call fdopen(3) can create a file pointer from a file descriptor.

Yep. This is the C "moral equivalent" to a Perl "file handle". I don't
know any other context where this is used (but it probably resonates
with the Windows folks, for whom "everything is a window handle" since
times Windows 3.1 immemorial(.

> Why there are two sets of file accessing system calls must have historical
> reasons. They were already present in the mid 1980s. But obviously file
> descriptor is the more fundamental one.

I think they just have different uses. Plus, file descriptor is a
kernel thing, FILE* is libc, i.e. userspace [1] (I know *you* know it,
but it might be interesting for others).

Cheers

[1] "God made the integers, all else is the work of man"
https://en.wikipedia.org/wiki/Leopold_Kronecker
-- 
t


signature.asc
Description: PGP signature

Re: Feuille de calcul web + outil de sondage web

[Sébastien NOBILI]

Bonjour,

Le 2023-07-12 18:26, RogerT a écrit :

A-t-on un logiciel alternatif un peu plus sympa pour l’utilisateur ?

Sondage « autre » : trop basique (oui/non/si nécessaire/ne se


Tu trouveras peut-être ton bonheur là : https://cryptpad.fr/

C'est libre et auto-hébergeable.

Sébastien

Re: Migration Bullseye vers Bookworm : échec lors du reboot

[Sébastien NOBILI]

Bonjour,

Le 2023-07-13 01:03, Jean-Michel OLTRA a écrit :

Regarder les logs /var/log/Xorg.0.log ?
Vérifier que la version de Trinity est correcte pour Bookworm ?
https://wiki.trinitydesktop.org/Debian_Trinity_Repository_Installation_Instructions
Lancer un `startx` à la main pour voir ce que ça raconte ?


En plus de tout ça, vérifier si ça démarre avec un des bureaux fournis
par Debian (Gnome par exemple).

Sébastien

Re: file descriptor VS file handle

[Thomas Schmitt]

Hi,

cor...@free.fr wrote:
> In linux systems, are file descriptor and file handle meaning the same
> stuff?

In the programming language C on Linux (more generally: on POSIX systems)
"File descriptor" is an integer number handed out by system calls like
open(2), pipe(2), socket(2), and others. It can be used by calls like
read(2), write(2), recv(2), send(2) to get or to deliver data.
(Execute e.g.
   man 2 open
to get the manual page of the desired system call.)

I am not aware that "file handle" has such a well defined meaning in
POSIX. To my understanding it just means a programming object that can be
used for similar activities as a file descriptor (and possibly for more
file related activities).

Maybe you mean "file pointer", which usually refers to the return value
"FILE *" of fopen(3) and can be used by calls like fread(3), fscanf(3),
fwrite(3), or fprintf(3). This is implemented on top of file descriptor.
The call fileno(3) can obtain the file descriptor of a file pointer, so
that the above calls of man chapter 2 can be used.
The call fdopen(3) can create a file pointer from a file descriptor.

Why there are two sets of file accessing system calls must have historical
reasons. They were already present in the mid 1980s. But obviously file
descriptor is the more fundamental one.
A possible motivation to have FILE * is given in
  
https://www.gnu.org/software/libc/manual/html_node/Streams-and-File-Descriptors.html


Have a nice day :)

Thomas

Re: Debian 12 problema con Español de Argentina

[Camaleón]

El 2023-07-12 a las 07:22 -0300, Marcelo Eduardo Giordano escribió:

> Borré haciendo algunas pruebas el idioma español de argentina y ahora no
> puedo recuperarlo, no puedo configurarlo nuevamente.
> 
> Probé con dpkg-reconfigure locales. Me sale el idioma que yo quiero pero el
> sistema me sigue saliendo en español de españa
> 
> Les paso algunos logs
> 
> cat /etc/default/locale
> #  File generated by update-locale
> LANG=es_AR.UTF-8
> LANGUAGE="es_AR:es"
> 
> cat  /etc/locale.gen

(...)

> es_AR.UTF-8 UTF-8

> # generated by KDE Plasma Region & Language KCM
> es_US.UTF-8 UTF-8
> es_ES.UTF-8 UTF-8

En principio todo parece correcto.

¿Qué síntomas tienes, exactamente? 

¿Aparecen mensajes en español de España en KDE o también desde la consola 
o terminal?

Mira a ver qué te devuelve la orden «locale».

Y acuérdate de reiniciar el sistema para que se apliquen los cambios que 
hayas hecho tras añadir algún idioma o reconfigurar la localización.

Saludos,

-- 
Camaleón 

Re: Mensaje de error en inicio

[Camaleón]

El 2023-07-12 a las 20:34 +, alberto moreno martinez escribió:

(corrijo el top-posting, con el indentado no puedo hacer nada :-()
> 
> De: Camaleón 
> Enviado: miércoles, 12 de julio de 2023 8:15 a. m.
> Para: debian-user-spanish@lists.debian.org 
> 
> Asunto: Re: Mensaje de error en inicio
> 
> El 2023-07-11 a las 19:56 +, alberto moreno martinez escribió:
> 
> > Hola muchachos.
> > Hace unos días redimensioné la partición home de mi Debian, y desde 
> > entonces tengo unos mensajes en el inicio y el final del sistema. Los que 
> > más que inquietan son los del inicio. En el inicio aparece 11 veces el 
> > mensaje "EDAC skx: ECC is disabled on mic 0"
> > Antes había más y lo solucioné agregando al fichero "fstab" la UUID 
> > correcta de la SWAP; las demás UUID están correctas.
> > investigando he encontrado que puede ser un problema con la configuración 
> > del fichero "xorg.conf" que tiene que ver con la gráfica, pero no me atrevo 
> > a tocar esto así nomas y quedarme sin entorno gráfico o romper alguna otra 
> > cosa.
> 
> En principio, y salvo que no puedas iniciar el sistema y trabajar con
> normalidad, o tengas algún otro problema, la presencia de ese mensaje
> (que nada tiene que ver con el particionado sino como bien dices, con
> la el controlador gráfico de nvidia) no debería tener mayor importancia.
> 
> > Según este foro:
> >
> > https://stackoverflow.com/questions/63383981/error-edac-skx-ecc-is-disabled-on-imc-0-on-ubuntu-20-04
> >
> > la solución pasa por hacer esto:
> >
> > Go to tty mode and type following commands:
> >
> > cp /etc/X11/xorg.conf.nvidia-xconfig-original /etc/X11/xorg.conf
> > reboot
> >
> > Prefiero tener la opinión de ustedes antes de hacer cualquier cosa. Adjunto 
> > fotos del inicio, cierre y características del sistema, así como sus 
> > características principales. Mi tarjeta gráfica es una EVGA GeForce RTX 
> > 3070 con el último driver propietario.
> > Gracias por la colaboración.
> 
> ¿Qué controlador gráfico usas? ¿El propietario de nvidia o nouveau?
> 
> Lo que hace esa orden es restaurar el archivo de configuración original
> del servidor gráfico Xorg, pero no sé si con eso será suficiente para
> que error desaparezca.
> 
> Probarlo no te va a doler, lo único que puede suceder es que no
> funcione, o que al reiniciar no se cargue el entorno gráfico, para lo
> cual, y como prevención, antes de ejecutar la orden puedes copiar a otro
> sitio el archivo xorg.conf original, si es que existe en tu sistema
> porque hace años que no lo veo ni se genera de manera predeterminada :-)

> Hola señores.
> 
>  La primera opción
> >Creas un archivo nombre.conf en /etc/modprobe.d con la siguiente linea.
> >blacklist edac_core
> No me funcionó. el sistema no me permite crear tal archivo y tanpoco me 
> permite editar un archivo parecido que hay en /etc/modprobe.d llamado 
> "nvidia-blacklists-nouveau.conf"

A esto ya te han repsondido :-)
 
> En la segunda opción:
> 
> "cp /etc/X11/xorg.conf.nvidia-xconfig-original /etc/X11/xorg.conf"
> 
> Tampoco pude ejecutarla, ya que no tengo el archivo o carpeta 
> "xorg.conf.nvidia-xconfig-original" para reemplazarlo por "xorg.conf"
> Lo que tengo en "X11" es una carpeta de vacía de nombre "xorg.conf.d"
> 
> Asi que estoy un poco perdido.

Todavía no nos has dicho qué controlador gráfico carga tu sistema para 
la tarjeta gráfica. Ejecuta esta orden y manda la salida:

lsmod | grep video
 
> Por cierto, ya no recuerdo como es la forma correcta de responder a un hilo 
> sin que le llegue solo a uno de los que me responde y no sea visible para 
> todos. hice lo que creí correcto con las opciones que me da Outlook.
> Si me lo quieren recordar, gracias también.

Pues es sencillo: botón de «responder a la lista» >:-)

Si no existe esa opción en tu cliente de correo, cambia de cliente de 
correo (ahora Thunderbird se ha puesto de gala con la nueva versión 115) 
o emula el resultado manualmente, es decir, en el campo Para, pones la 
dirección de la lista.

Saludos

-- 
Camaleón