Re: trixie update/upgrade strangeness

2023-10-11 Thread Jeffrey Walton
On Wed, Oct 11, 2023 at 10:49 PM Andy Smith  wrote:
>
> On Wed, Oct 11, 2023 at 04:25:58PM -0500, Mark Copper wrote:
> > suddenly, all files created on /dev/sda1 for the last 27 days have
> > disappeared, even files I edited this morning before restarting. Like the
> > clock was turned back a month. The disk, a new 18 TB, passed the test
>
> This happened to a customer of mine once, and they asked me to look
> into it. When I did I found that:
>
> - they were using LVM
> - they'd taken a snapshot of their root fs
> - they were finding and mounting their root fs by fs UUID
> - snapshot obviously had same fs UUID
> - the kernel was finding the snapshot first at boot
>
> Could anything like that be happening?

That's devious.

I can't help but wonder how many hundreds or thousands of man hours
were wasted because LVM was not designed to avoid the problem by
default.

Jeff



Re: W: Possible missing firmware /lib/firmware/brand/yada*

2023-10-11 Thread Felix Miata
Sven Joachim composed on 2023-04-29 09:02 (UTC+0200):

> On 2023-04-28 21:30 -0400, Felix Miata wrote:

>> # inxi -Gxx
>> Graphics:
>>   Device-1: Intel 82Q963/Q965 Integrated Graphics vendor: Dell driver: i915
>> v: kernel arch: Gen-4 ports: active: DVI-D-1 empty: VGA-1 bus-ID: 00:02.0
>> chip-ID: 8086:2992   # aka ancient
>> # grep MODULES /etc/initramfs-tools/initramfs.conf
>> # MODULES: [ most | netboot | dep | list ]
>> MODULES=dep
>> #

>> These many per transaction $SUBJECT initrd construction messages have been 
>> routine
>> for a long time in Bullseye and Bookworm regardless of active GPU installed, 
>> and
>> whether or not a firmware-brand-graphics .deb exists and is installed
>> for it.

> It would be useful to give an example of these messages, as well as a
> list of firmware packages you have installed.

https://forums.debian.net/viewtopic.php?t=156340 shows same thing, and reports
problem is old and unfixable.

Apparently it must only happen with certain CPU/GPU families, which is why it 
took
a while for me to notice.

>> Is there something that can be done to avoid this screen and log
>> litter?

> Install the package that contains the firmware files.  For Intel and
> NVidia graphics that is firmware-misc-nonfree, for AMD it is
> firmware-amd-graphics.

>> Can anyone
>> point to an existing meta-bug report on the subject of stopping the litter?
>> Searching seems to find only reports pointing to particular GPUs, e.g.
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016286

> It's the same for any GPUs, as well as for other hardware.  The
> update-initramfs script runs modinfo(8) to find out which firmware files
> a loaded module might request and issues a warning for any such file
> which is not there.  You can check the code for yourself[1].

> 1. https://sources.debian.org/src/initramfs-tools/0.142/hook-functions/#L109
-- 
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: Qt6 Location for Debian 12

2023-10-11 Thread Petric Frank
Hello,

Am Mittwoch, 11. Oktober 2023, 19:00:19 CEST schrieb Patrick Franz:
> Hej,
>
> Am Mittwoch, 11. Oktober 2023, 16:52:24 CEST schrieb Petric Frank:
> > Hello,
> >
> > is there a *.deb for Qt6 Location (-dev) module ?
> >
> > I have seen there is one for Qt6 Positioning in the stable repository
> > but i miss the above one.
> >
> > Or do i have to compile the Qt6 system myself ?
>
> There is no Location module for Qt 6.4. It never existed. However, it
> got reintroduced as a tech preview for 6.5.

I got a hint on a git project where Qt6Location was compiled for older Qt
Versions (< 6.5):
  https://github.com/ntadej/qtlocation

Maybe the 6.4.2 release of it could be a candidate for being repackaged as
*.deb ?

He made also a Qt Location plugin for maplibre-native-qt (open source fork/
rewrite of mapbox gl). It can be used accessing a versatiles mapping server.





Re: trixie update/upgrade strangeness

2023-10-11 Thread Andy Smith
Hello,

On Wed, Oct 11, 2023 at 04:25:58PM -0500, Mark Copper wrote:
> suddenly, all files created on /dev/sda1 for the last 27 days have
> disappeared, even files I edited this morning before restarting. Like the
> clock was turned back a month. The disk, a new 18 TB, passed the test

This happened to a customer of mine once, and they asked me to look
into it. When I did I found that:

- they were using LVM
- they'd taken a snapshot of their root fs
- they were finding and mounting their root fs by fs UUID
- snapshot obviously had same fs UUID
- the kernel was finding the snapshot first at boot

Could anything like that be happening?

Thanks,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting



trixie update/upgrade strangeness

2023-10-11 Thread Mark Copper
Yesterday, an attempt to install topcat package failed. So I ran "apt
update" and "apt upgrade".

The first surprise was the extent upgrade, it was much more extensive than
I would have expected.

After the upgrade the X terminal crashed.

Today wifi started misbehaving so I rebooted the box.

Now, suddenly, all files created on /dev/sda1 for the last 27 days have
disappeared, even files I edited this morning before restarting. Like the
clock was turned back a month. The disk, a new 18 TB, passed the test

sudo smartctl -a /dev/sda

There is nothing in dmesg or syslog to indicate a problem. And

fsck /dev/sda1

is clean.

Strange, no?


Re: Qemu vraagje, 100GB disken van een paar kilo Byte

2023-10-11 Thread Paul van der Vlis

Op 11-10-2023 om 22:06 schreef Geert Stappers:

On Wed, Oct 11, 2023 at 09:34:19PM +0200, Paul van der Vlis wrote:

Hallo,

Als ik een virtuele disk aanmaak met:
qemu-img create -f qcow2 /path/naam.qcow2 1000G
Dan krijg ik een disk die volgens "ls" maar een paar KB groot is, en die
groeit naarmate ik hem gebruik.
Die disk kan ik gebruiken met het commando "virt-install".

Maar ik ben nu bezig met virt-manager.

Als ik een virtuele disk aanmaak met virt-manager, dan is zo'n disk van
1000GB volgens "ls" opeens 1000GB groot. Die ruimte neemt het niet echt in
beslag, want volgens "du" is hij veel kleiner.

Ik ben gewend om via "ls" te kijken hoe groot een bestand is, daarom vind ik
het niet prettig hoe virt-manager disks aanmaakt. Verder vind ik het raar,
ik zou denken dat het ook "qemu-img" gebruikt.

Kan iemand me misschien uitleggen waarom het aanmaken van een disk via
virt-manager anders is?  En of hier misschien iets aan te doen is?



Het wordt "sparse file" genoemd.

Wat ik van de e-mail begrijp, maakt qemu-img default sparse files aan.
En is de wens dat virt-manager dat ook doet. Ik weet echter niet hoe.
Mijn staat iets bij dat ik ooit een "checkbox"  ( "vinkje" ) voor gezien
heb.  (En voor meer heb ik geen tijd.)


Bedankt dat je toch even wou reageren.

Wat je bedoeld is waarschijnlijk de checkbox "allocate entire volume 
now". Dit plaatje vond ik daarover op internet:

https://postimg.cc/ctBrm5C5
Maar dat is juist niet wat ik wil. En heb ik dus ook niet aangevinkt.

Groet,
Paul


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



Re: Does the debian kernel sends the gratuitous arp ?

2023-10-11 Thread Geert Stappers
On Mon, Oct 09, 2023 at 10:15:38PM +0200, Geert Stappers wrote:
> On Mon, Oct 09, 2023 at 08:39:02PM +0530, Balaji G wrote:
> > Hi Geert,
> 
> Hello mailinglist (archive )readers of debian-user@lists.debian.org
> 

Hello again,


> 
> > >>> During `ip link set down dev eno5np0` and `ip link set up dev eno5np0`
> > >>> are NO IP-addresses involved.
> >
> > This interface eno5np0 is configured with the ip addresses(10.45.10.4 ).
> >
> > # ifconfig
> }( mismatch between `ifconfig` command expected `ifconfig` output )
> > eno5np0: flags=4163  mtu 1500
> > inet 10.45.10.4  netmask 255.255.255.0  broadcast 10.45.10.255
> > ether 88:e9:a4:49:18:48  txqueuelen 1000  (Ethernet)
> > RX packets 2967346895  bytes 4417546189260 (4.0 TiB)
> > RX errors 0  dropped 1  overruns 0  frame 0
> > TX packets 1634521866  bytes 2220475762246 (2.0 TiB)
> > TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
> 
> 
> I did missed  "LOWER_UP", then I noticed that `ifconfig` is used. More
> on that later.  Back to 'Subject: Re: Does the debian kernel sends the
> gratuitous arp ?'
> 
> To me is the answer "Yes, Debian kernel sends gratuitous ARP when it
> supposed to do".  But we, this mailinglist, have this discussion because
> somewhere is the gratuitous ARP missing.  What triggered the "I wonder
> why there is no gratuitous ARP?" is yet unknown.
> 
> Let me try to capture a gratuitous ARP.  I will be using only one
> interface  (it is OK if the computer has many other network interfaces)
> Using two logins as root, one for "tcpdump", the other "set address".
> 
> In "tcpdump session"
> 
>   tcpdump -n -i eth0  arp
> 
> 
> In "set address session"
> 
>   sudo ip address add 198.51.100.23/24 dev eth0
> 
> 
> Back to "tcpdump session".
> 
> And to my surprise:   **no** gratuitous ARP !
> 
> It should be there.  I even tried after:
> 
> $ cat /proc/sys/net/ipv4/conf/eth0/arp_notify
> 0
> $ echo 1 | sudo tee -a /proc/sys/net/ipv4/conf/eth0/arp_notify
> 1
> $ cat /proc/sys/net/ipv4/conf/eth0/arp_notify
> 1
> $
> 
> 
> I'm gonna sleep about it.  Expect me back over 48 hours.
 
  :-)
 
 
> > Thanks,
> 
> Yeah, thanks for the good question.
> 

It did learn me that things have changes.
I hope it is the improvement that was aimed for.

No, I have no idea if the H.A., High Available, setup  I did build
for a previous employer are effected.

> > Balaji
> 
> Groeten
> Geert Stappers
> 
> 
> About ifconfig :
>   
> https://serverfault.com/questions/633087/where-is-the-statement-of-deprecation-of-ifconfig-on-linux
> 

a.k.a.   use   `ip addres`,  `ip a` for short.


Groeten
Geert Stappers
-- 
Silence is hard to parse



Re: Qemu vraagje, 100GB disken van een paar kilo Byte

2023-10-11 Thread Geert Stappers
On Wed, Oct 11, 2023 at 09:34:19PM +0200, Paul van der Vlis wrote:
> Hallo,
> 
> Als ik een virtuele disk aanmaak met:
> qemu-img create -f qcow2 /path/naam.qcow2 1000G
> Dan krijg ik een disk die volgens "ls" maar een paar KB groot is, en die
> groeit naarmate ik hem gebruik.
> Die disk kan ik gebruiken met het commando "virt-install".
> 
> Maar ik ben nu bezig met virt-manager.
> 
> Als ik een virtuele disk aanmaak met virt-manager, dan is zo'n disk van
> 1000GB volgens "ls" opeens 1000GB groot. Die ruimte neemt het niet echt in
> beslag, want volgens "du" is hij veel kleiner.
> 
> Ik ben gewend om via "ls" te kijken hoe groot een bestand is, daarom vind ik
> het niet prettig hoe virt-manager disks aanmaakt. Verder vind ik het raar,
> ik zou denken dat het ook "qemu-img" gebruikt.
> 
> Kan iemand me misschien uitleggen waarom het aanmaken van een disk via
> virt-manager anders is?  En of hier misschien iets aan te doen is?


Het wordt "sparse file" genoemd.

Wat ik van de e-mail begrijp, maakt qemu-img default sparse files aan.
En is de wens dat virt-manager dat ook doet. Ik weet echter niet hoe.
Mijn staat iets bij dat ik ooit een "checkbox"  ( "vinkje" ) voor gezien
heb.  (En voor meer heb ik geen tijd.)


Groeten
Geert Stappers
-- 
Silence is hard to parse



Qemu vraagje

2023-10-11 Thread Paul van der Vlis

Hallo,

Als ik een virtuele disk aanmaak met:
qemu-img create -f qcow2 /path/naam.qcow2 1000G
Dan krijg ik een disk die volgens "ls" maar een paar KB groot is, en die 
groeit naarmate ik hem gebruik.

Die disk kan ik gebruiken met het commando "virt-install".

Maar ik ben nu bezig met virt-manager.

Als ik een virtuele disk aanmaak met virt-manager, dan is zo'n disk van 
1000GB volgens "ls" opeens 1000GB groot. Die ruimte neemt het niet echt 
in beslag, want volgens "du" is hij veel kleiner.


Ik ben gewend om via "ls" te kijken hoe groot een bestand is, daarom 
vind ik het niet prettig hoe virt-manager disks aanmaakt. Verder vind ik 
het raar, ik zou denken dat het ook "qemu-img" gebruikt.


Kan iemand me misschien uitleggen waarom het aanmaken van een disk via 
virt-manager anders is?  En of hier misschien iets aan te doen is?


( Het is me (nog) niet gelukt om een disk aan te maken met "qemu-img" en 
deze dan te gebruiken in virt-manager. )


Groet,
Paul

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



Re: Message d'erreur au boot sur disque dur

2023-10-11 Thread Informatique BILLARD

Bonsoir,

Oui je l'ai fait mais il me faudra approfondir l'analyse des résultats.

Cordialement

François-Marie

Le 11/10/2023 à 09:49, Basile Starynkevitch a écrit :


On 10/11/23 08:55, Informatique BILLARD wrote:

Bonjour

j'ai parfois ce message au boot sur un portable, quand il est en 
autonomie sur la batterie.


COMRESET failed (errno=-16)

Ce problème semble ne pas apparaître quand il est sur le secteur.

Dois-je m’inquiéter quand à la santé de mon disque dur SSD.



L'utilitaire à installer et à lancer (de temps en temps) est smartctl. 
Voir


https://lecrabeinfo.net/verifier-etat-de-sante-tester-secteurs-defectueux-disque-dur-ssd-sur-linux.html 



Librement.


PS. Je cherche des contributeurs ou des suggestions d'exemples au 
moteur d'inférences libre https://github.com/RefPerSys/RefPerSys/






Re: Help fixing package dependencies

2023-10-11 Thread Timothy M Butterworth
On Wed, Oct 11, 2023 at 9:39 AM Rishikesh Kakade <1rishikaka...@gmail.com>
wrote:

> Hi!
>
> I am trying to upgrade my system from Debian 11 to Debian 12. When I run
> sudo apt full-upgrade,
>
> λ ~/ main* sudo apt full-upgrade
>
> Reading package lists... Done
> Building dependency tree... Done
> Reading state information... Done
> Calculating upgrade... Error!
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
>
> The following packages have unmet dependencies:
> libboost-thread1.74.0 : Breaks: libboost-regex1.74.0-icu67
> libc6-dev : Breaks: libnetcdf-dev (<= 1:4.9.0-3) but 1:4.7.4-1 is to be
> installed
> libgirepository-1.0-1 : Breaks: libgjs0g (< 1.68.4-1+b1) but 1.66.2-1 is
> to be installed
> E: Error, pkgProblemResolver::Resolve generated breaks, this may be
> caused by held packages.
>
>
>
> I am afraid that I will break my system if I attempt to solve it alone.
> Can anyone help me figure out how to fix the dependency issue?
>
> Rishi
>

First run:
sudo apt update
sudo apt upgrade
sudo apt full-upgrade

Second if that does not work then check your repose. You should have
something similar to:

less /etc/apt/sources.list
deb http://deb.debian.org/debian/ bookworm main non-free contrib
non-free-firmware
deb http://security.debian.org/debian-security bookworm-security main
contrib non-free non-free-firmware

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


Re: apt error, fresh install Debian 12/Dell desktop

2023-10-11 Thread Bob Crochelt


On Tue, Oct 10, 2023, at 15:52, Eddie wrote:
> 
> 
> On 10/10/23 14:41, Bob Crochelt wrote:
> > 
> > 
> > On Tue, Oct 10, 2023, at 08:11, Anders Andersson wrote:
> >> On Tue, Oct 10, 2023 at 1:19 PM Bob Crochelt  >> > wrote:
> >> >
> >> > Hi:
> >> > Fresh install Debian 12.  All seems well.  However, when I install a 
> >> new package, in this case fvwm, the package installs fine, but there 
> >> is an error at the end...
> >> >
> >> > dpkg: dependency problems prevent configuration of linux-image-amd64:
> >> > linux-image-amd64 depends on linux-image-6.1.0-12-amd64 (= 
> >> 6.1.52-1); however:
> >> >   Package linux-image-6.1.0-12-amd64 is not configured yet.
> >> >
> >> > dpkg: error processing package linux-image-amd64 (--configure):
> >> > dependency problems - leaving unconfigured
> >> > Processing triggers for libc-bin (2.36-9+deb12u3) ...
> >> > Processing triggers for man-db (2.11.2-2) ...
> >> > Processing triggers for initramfs-tools (0.142) ...
> >> > update-initramfs: Generating /boot/initrd.img-6.1.0-12-amd64
> >> > raspi-firmware: missing /boot/firmware, did you forget to mount it?
> >> > run-parts: /etc/initramfs/post-update.d//z50-raspi-firmware exited 
> >> with return code 1
> >> > dpkg: error processing package initramfs-tools (--configure):
> >> > installed initramfs-tools package post-installation script 
> >> subprocess returned error exit status 1
> >> > Errors were encountered while processing:
> >> > linux-image-6.1.0-12-amd64
> >> > linux-image-amd64
> >> > initramfs-tools
> >> > E: Sub-process /usr/bin/dpkg returned an error code (1)
> >> >
> >> > So far all the packages I have installed have worked fine...
> >> >
> >> > Should I ignore this or do something?
> >>
> >> This is a bit crazy. It can't be a "fresh install" if you have the
> >> amd64 kernel trying to configure the closed firmware for a raspberry
> >> pi. Why is "raspi-firmware" installed? What's your actual computer and
> >> how did you install debian?
> > Installed Debian from Debian 12.0 disk.
> > Thanks
> > Bob
> I had EXACTLY this when I installed Bookworm 12 live when it first came 
> out. Dumped "raspi-firmware" and purged. All started to finish their 
> upgrade while dpkg was running. All ok since.
> 
> Lucky Eddie !
> 
Yes working fine here now. Appreciate all the help
Bob

Missing application menu in TB 115.3.1 (32-bit)

2023-10-11 Thread skoric
Hi,

After recent upgrade of Thunderbird in Buster, I noticed that there is no
applications menu on the right side anymore. I found that menu useful to
close several mails if opened in the same time. Now they need to be closed
one by one. Is there a way to have that menu where it was on the right
side again?

Misko



Re: Qt6 Location for Debian 12

2023-10-11 Thread Patrick Franz
Hej,

Am Mittwoch, 11. Oktober 2023, 16:52:24 CEST schrieb Petric Frank:
> Hello,
> 
> is there a *.deb for Qt6 Location (-dev) module ?
> 
> I have seen there is one for Qt6 Positioning in the stable repository
> but i miss the above one.
> 
> Or do i have to compile the Qt6 system myself ?

There is no Location module for Qt 6.4. It never existed. However, it 
got reintroduced as a tech preview for 6.5.


-- 
Med vänliga hälsningar

Patrick Franz




Re: Debian live boot corrupting secure boot

2023-10-11 Thread Valerio Vanni

Il 11/10/2023 04:13, Max Nikulin ha scritto:

On 11/10/2023 08:46, Valerio Vanni wrote:

Now I've tried Fedora live: it doesn't act like Debian. After it,
I can still boot old Clonezilla. Not only at grub page: I can also 
load live environment.


If the Fedora image is fresh enough


Yes, it's version 38.
I add that I tried to make it resident (install on internal disk), and 
neither this way it changes anything.


It satisfies Secure Boot requirements, but it doesn't blacklist anything.
So it doesn't seem true what whas said (don't remember by who) at the 
start of this thread, that if a system supports SB blacklists older 
images for sure.


It seems a choice. A bad choice for a live environment.


then there are some patches either in Fedora or in Debian. Perhaps
the following one

https://sources.debian.org/src/shim/15.7-1/debian/patches/block-grub-sbat3-debian.patch/


> You may check changelog, closed debian bugs, messages in developer
mailing lists for the shim package (shim-signed and shim-unsigned) 
and may try to discuss the issue with shim maintainers.


With Fedora Live I could see the difference, using
# mokutil --list-sbat-revocations.

When the system is in one of these states:
-new
-reflashed
-after old clonezilla (grub entries) load
-after Fedora live load or Fedora install

This list is
sbat,1,202103218

After load of grub page of a new Clonezilla (or live Debian) the list 
becomes:


sbat,1,2022052400
grub,2



Qt6 Location for Debian 12

2023-10-11 Thread Petric Frank
Hello,

is there a *.deb for Qt6 Location (-dev) module ?

I have seen there is one for Qt6 Positioning in the stable repository but i
miss the above one.

Or do i have to compile the Qt6 system myself ?

kind regards
  Petric





Re: Plus d'hibernate depuis bookworm

2023-10-11 Thread Sébastien NOBILI

Bonjour,

Le 2023-10-10 11:43, Daniel Caillibaud a écrit :

Une commande à lancer permettant de débugger ce qui se passe ?


As-tu essayé avec `systemctl hibernate` ?
Ça ne donnera pas plus d'infos de debug, je ne sais pas bien si ça
fera différemment de ce que tu as fait précédemment mais c'est la
commande que j'utilise et ça fonctionne bien (dans mon cas).

Sébastien



Re: Message d'erreur au boot sur disque dur

2023-10-11 Thread Informatique BILLARD

Bonjour

merci je vais effectuer quelques tests pour approfondir l'analyse.

François-Marie

Le 11/10/2023 à 09:25, David P. a écrit :

Bonjour,
Il y a plusieurs cas possibles pour avoir ce message.
Sinon devant le peu d'informations, je ne peux que mettre un lien d'un 
forum : https://forum-francophone-linuxmint.fr/viewtopic.php?t=9772
Une check-list sera donc nécessaire pour pouvoir cibler le pb précis, 
par ex, si multiboot grub, les MàJ windows sont souvent la raison 
après upgrade.

À suivre donc...
Librement vôtre,
David P.



Le 11 oct. 2023, à 09:05, Informatique BILLARD 
 a écrit:


Bonjour

j'ai parfois ce message au boot sur un portable, quand il est en
autonomie sur la batterie.

COMRESET failed (errno=-16)

Ce problème semble ne pas apparaître quand il est sur le secteur.

Dois-je m’inquiéter quand à la santé de mon disque dur SSD.

Merci

François-Marie



te invitamos a escuchar "Respira": la canción que te hará vibrar.

2023-10-11 Thread Nacidos de la Tierra
te invitamos a escuchar "Respira": la canción que te hará vibrar.

‍¡Hola ‍ ‍!

Esperamos que estés teniendo un día maravilloso. Queríamos escribirte para 
compartir contigo algo muy especial que nos hace muchísima ilusión: ¡nuestra 
última canción, "Respira"! 

‍"Respira" es una canción que nos llena de energía y positivismo porque creemos 
firmemente que cada persona tiene el poder de liberarse y encontrar la 
felicidad, es nuestra forma de decirte que te tomes tu tiempo y que confíes en 
tu camino.

La canción es una combinación del afrobeat creado por El Expecialista con las 
letras y rimas únicas de Kasú y Meser. Queremos que la escuches y que sientas 
la energía de la música y como las letras te inspiran a tomar el control de tu 
vida.

Además acabamos de lanzar también el lyric video con el que pretendemos 
trasladar el mensaje de una forma más directa, puedes verlo en nuestro canal de 
YouTube (aprovecha para suscribirte si no lo has hecho todavía, no te cuesta 
nada y a nosotros nos ayuda muchísimo)

Sería increíble si pudieras dedicar unos minutos para escuchar la canción y 
contarnos qué te ha parecido en la sección de comentarios del vídeo de YouTube, 
y si te gusta tanto como a nosotros, puedes agregarla a tus playlists favoritas 
para escucharla siempre que quieras y por supuesto compartirla con quien tú 
quieras.

A parte de en YouTube, también la tienes disponible en todas las principales 
plataformas de música en streaming, como Spotify, Tidal, Deezer, Apple Music y 
Google Play, simplemente búscala como “Nacidos de la Tierra Respira” y 
aparecerá, aunque para hacértelo más fácil puedes encontrar los enlaces 
directos a las plataformas en la página que hemos creado especialmente para 
esta canción: https://respira.nacidosdelatierra.com  ( 
https://nacidosdelatierra.com/index.php?option=com_acym=fronturl=click=18=700046=35
 )

Si deseas saber más sobre nosotros, nuestros últimos lanzamientos y 
actividades, puedes visitar nuestra página web oficial en 
https://www.nacidosdelatierra.com ( 
https://nacidosdelatierra.com/index.php?option=com_acym=fronturl=click=19=700046=35
 )

También puedes seguirnos (y etiquetarnos) en las redes:
- Instagram (https://instagram.com/nacidosdelatierra ( 
https://nacidosdelatierra.com/index.php?option=com_acym=fronturl=click=13=700046=35
 ))
- Facebook (https://www.facebook.com/nacidosdelatierra ( 
https://nacidosdelatierra.com/index.php?option=com_acym=fronturl=click=20=700046=35
 ))
- Twitter (https://twitter.com/HipHopNacidos ( 
https://nacidosdelatierra.com/index.php?option=com_acym=fronturl=click=21=700046=35
 ))

Te agradecemos de todo corazón por ser parte de nuestra familia y por tu apoyo 
incondicional. ¡Esperamos que "Respira" te inspire y te llene de positivismo!

‍Este mensaje se dirige exclusivamente a debian-user-spanish@lists.debian.org ‍ 
y puede contener información privilegiada o confidencial. Si ha recibido este 
mensaje por error, le rogamos que nos lo comunique inmediatamente por esta 
misma vía y proceda a su destrucción. De acuerdo con la nueva ley Ley de 
Servicios de la Sociedad de la Información y Comercio Electrónico aprobada por 
el parlamento español y de lo establecido en el Reglamento (UE) 2016/679 del 
Parlamento Europeo de Protección de Datos de Carácter Personal, le comunicamos 
que su dirección de Correo electrónico forma parte de un tratamiento 
automatizado, teniendo usted derecho de oposición, acceso, rectificación, 
cancelación, y portabilidad de sus datos, dirigiendo su petición contestando 
este e-mail, asimismo, podrá dirigirse a la Autoridad de Control competente 
para presentar la reclamación que considere oportuna.

MEDIO AMBIENTE:
Por favor, antes de imprimir este correo electrónico considere su aportación a 
la conservación del medio ambiente por la reduccion de consumo de papel.


Re: Help fixing package dependencies during Debian 11 -> 12 upgrade

2023-10-11 Thread Michael Kjörling
On 11 Oct 2023 11:08 +0530, from 1rishikaka...@gmail.com (Rishikesh Kakade):
> I am trying to upgrade my system from Debian 11 to Debian 12.

Okay.

First things first: did you read through and follow the upgrade
preparation portions of the Bookworm release notes? Going straight for
`apt full-upgrade` _might_ work but is not the recommended upgrade
method for going from one major release to the next.

> When I run sudo apt full-upgrade,
> [...]
> libc6-dev : Breaks: libnetcdf-dev (<= 1:4.9.0-3) but 1:4.7.4-1 is to be
> installed

I didn't check the other ones, but this doesn't seem right. For that
package, Bullseye is at package version 1:4.7.4-1, but Bookworm is at
1:4.9.0-3+b1, so apt _shouldn't_ try to install 1:4.7.4-1 as part of
an upgrade to Bookworm.

My guess would be that you have some stale Bullseye repository in your
apt sources list, either from Debian or some third-party repository.
See 
https://www.debian.org/releases/bookworm/amd64/release-notes/ch-upgrading.en.html#system-status

Please share the output of: grep -r -v '^#' /etc/apt/sources.list*

Please take care to not introduce any line breaks in that output which
are not in the original.

-- 
Michael Kjörling  https://michael.kjorling.se
“Remember when, on the Internet, nobody cared that you were a dog?”



Re: Message d'erreur au boot sur disque dur

2023-10-11 Thread Basile Starynkevitch



On 10/11/23 08:55, Informatique BILLARD wrote:

Bonjour

j'ai parfois ce message au boot sur un portable, quand il est en 
autonomie sur la batterie.


COMRESET failed (errno=-16)

Ce problème semble ne pas apparaître quand il est sur le secteur.

Dois-je m’inquiéter quand à la santé de mon disque dur SSD.



L'utilitaire à installer et à lancer (de temps en temps) est smartctl. Voir

https://lecrabeinfo.net/verifier-etat-de-sante-tester-secteurs-defectueux-disque-dur-ssd-sur-linux.html

Librement.


PS. Je cherche des contributeurs ou des suggestions d'exemples au moteur 
d'inférences libre https://github.com/RefPerSys/RefPerSys/


--
Basile Starynkevitch
 
(only mine opinions / les opinions sont miennes uniquement)
92340 Bourg-la-Reine, France
web page: starynkevitch.net/Basile/



Re: Message d'erreur au boot sur disque dur

2023-10-11 Thread David P.
Bonjour,
Il y a plusieurs cas possibles pour avoir ce message.
Sinon devant le peu d'informations, je ne peux que mettre un lien d'un forum : 
https://forum-francophone-linuxmint.fr/viewtopic.php?t=9772
Une check-list sera donc nécessaire pour pouvoir cibler le pb précis, par ex, 
si multiboot grub, les MàJ windows sont souvent la raison après upgrade.
À suivre donc...
Librement vôtre,
David P.





Le 11 oct. 2023 à 09:05, à 09:05, Informatique BILLARD 
 a écrit:
>Bonjour
>
>j'ai parfois ce message au boot sur un portable, quand il est en
>autonomie sur la batterie.
>
>COMRESET failed (errno=-16)
>
>Ce problème semble ne pas apparaître quand il est sur le secteur.
>
>Dois-je m’inquiéter quand à la santé de mon disque dur SSD.
>
>Merci
>
>François-Marie


Message d'erreur au boot sur disque dur

2023-10-11 Thread Informatique BILLARD

Bonjour

j'ai parfois ce message au boot sur un portable, quand il est en 
autonomie sur la batterie.


COMRESET failed (errno=-16)

Ce problème semble ne pas apparaître quand il est sur le secteur.

Dois-je m’inquiéter quand à la santé de mon disque dur SSD.

Merci

François-Marie




Re: Help fixing package dependencies

2023-10-11 Thread David
On Wed, 2023-10-11 at 11:08 +0530, Rishikesh Kakade wrote:
> Hi!
> 
> I am trying to upgrade my system from Debian 11 to Debian 12. When I
> run
> sudo apt full-upgrade,

Well, to start with what appears to be the obvious, did you begin with
`apt-get update' first?
The, `apt-get full-upgrade'.

It's important to establish the current state of your system first.
Cheers!

> λ ~/ main* sudo apt full-upgrade
> Reading package lists... Done
> Building dependency tree... Done
> Reading state information... Done
> Calculating upgrade... Error!
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
> libboost-thread1.74.0 : Breaks: libboost-regex1.74.0-icu67
> libc6-dev : Breaks: libnetcdf-dev (<= 1:4.9.0-3) but 1:4.7.4-1 is to
> be
> installed
> libgirepository-1.0-1 : Breaks: libgjs0g (< 1.68.4-1+b1) but 1.66.2-1
> is to
> be installed
> E: Error, pkgProblemResolver::Resolve generated breaks, this may be
> caused
> by held packages.
> 
> 
> 
> I am afraid that I will break my system if I attempt to solve it
> alone. Can
> anyone help me figure out how to fix the dependency issue?
> 
> Rishi

-- 
`I intend to live forever,
or die trying'.

--Groucho Marx