Re: Us ha fallat l'actualització d'ahir de Debian 12.2 a Debian 12.4 ?

[Griera]

Hola:

Aquest matí s'ha actualitzat a linux-image-6.1.0-16-amd64 (6.1.67-1).

Salut!

On Sat, 16 Dec 2023 00:13:47 +
Carles Pina i Estany  wrote:

> 
> Hola,
> 
> On 15 Dec 2023 at 06:51:29, Àlex wrote:
> > Sembla que aviat tindrem un nou nucli que corregeix el problema, però
> > no ho veuen com a urgent:
> 
> Explicació curta: si voleu tenir la versió que no hi ha problemes (dels
> d'algunes targes Wifi) es pot fer servir bookworm-updates. Com a
> repositoris, per exemple (treieu non-free o non-free-firmware com ho feu
> servir, poso l'example complet em sembla):
> 
> deb http://deb.debian.org/debian bookworm-updates main non-free 
> non-free-firmware contrib
> deb https://deb.debian.org/debian-security bookworm-security main non-free 
> non-free-firmware contrib
> 
> Història sencera, parlo de memòria, espero no equivocar-me:
> 
> El linux-image amb el kernel versió 6.1.65: és la versió amb problemes
> amb el sistema de fitxers ext4. Va entrar a Debian 12.3 i van "anular"
> 12.3.
> 
> (ho miro via "dpkg -l | grep -i linux-image" i miro la columna de la
> versió, no el nom del paquet que és linux-image-6.1.0-16-amd64 i coses
> així)
> 
> El linux-image amb el kernel versió 6.1.66: és el que té problemes amb
> algunes targes de xarxa Wifi que fan el (alguns) sistemes altament
> inusable (fins i tot sense fer servir el Wifi, em sembla).
> 
> Aquesta versió, la 6.1.66, està a la versió de Debian 12.4.
> 
> Si voleu tenir la versió 6.1.67 i estar a Bookworm: es pot tenir via:
> deb http://deb.debian.org/debian bookworm-updates main non-free 
> non-free-firmware contrib
> deb-src http://deb.debian.org/debian bookworm-updates main non-free 
> non-free-firmware contrib
> 
> És a dir, bookworm-updates enlloc de bookworm. Hi ha paquets (només
> alguns) que seran al proper Bookworm (12.5, d'aquí uns dos mesos suposo)
> que ja estan a bookworm-updates. Com el kernel 6.1.67.
> 
> I això ha estat una mala sort impresionant. Pobre "team release" :-(
> 
> Fins aviat, vaig a reiniciar amb el 6.1.67 ara mateix :-)
> 
> -- 
> Carles Pina i Estany
> https://carles.pina.cat

Re: setting IFS to new line doesn't work while searching?

[David Wright]

On Fri 15 Dec 2023 at 08:58:10 (-0500), Greg Wooledge wrote:
> On Fri, Dec 15, 2023 at 02:30:21PM +0100, Nicolas George wrote:
> > Greg Wooledge (12023-12-15):
> > > readarray -d '' fndar < <(
> > > find "$sdir" ... -printf 'stuff\0' |
> > > sort -z --otherflags
> > > )
> 
> > It is possible to do it safely in bash plus command-line tools, indeed.
> > But in such a complex case, it is better to use something with a
> > higher-level interface. I am sure File::Find and Version::Compare can
> > let Perl do the same thing in a much safer way.
> 
> Equally safe, perhaps.  Not safer.  I don't know those particular perl
> modules -- are they included in a standard Debian system, or does
> one need to install optional packages?  And then there's a learning
> curve for them as well.
> 
> By the way, your MUA is adding 1 years to its datestamps.

Don't knock it: beats using the French Republican calendar.
But I miss the hours:minutes used by most MUAs (the minutes
being relatively unaffected by time zones). They can help
with following threads stored in different locations.

Cheers,
David.

[Zapytanie otrzymane przez Elektroda]

[Elektroda]

Otrzymaliśmy Twoje zapytanie nr (9662). Zapoznamy się z nim i udzielimy 
odpowiedzi najszybciej, jak to będzie możliwe.


Jeśli chcesz dodać komentarz, odpowiedz na ten e-mail.


Ten e-mail został wysłany z konta Elektroda.









[V67LJ2-VXVM5]

Re: another possible audience for Debian

[Matt]

I was attempting to connect people to social change. Thank you for replying.

I appreciate this mailing list.

On 12/15/23 23:33, der.hans wrote:

Am 15. Dec, 2023 schwätzte Matt so:

moin moin Matt,

I am a Debian user. An audience for Debian may be the Fediverse 
because the


There are quite a few of us on the Fediverse :).

There's also an account mirroring debian's micronews.

@deb...@framapiaf.org

ciao,

der.hans

Fediverse has a technology focused culture, and its creative 
endeavors could be in the form of developing Debian if many users are 
interested. The biases of Debian vary from topic to topic in great 
depth and detail. That is closely related to the creativity of the 
Fediverse where users communicate inter-personally.

Re: another possible audience for Debian

[der.hans]

Am 15. Dec, 2023 schwätzte Matt so:

moin moin Matt,


I am a Debian user. An audience for Debian may be the Fediverse because the


There are quite a few of us on the Fediverse :).

There's also an account mirroring debian's micronews.

@deb...@framapiaf.org

ciao,

der.hans

Fediverse has a technology focused culture, and its creative endeavors could 
be in the form of developing Debian if many users are interested. The biases 
of Debian vary from topic to topic in great depth and detail. That is closely 
related to the creativity of the Fediverse where users communicate 
inter-personally.




--
#  https://www.SpiralArray.com   https://www.PhxLinux.org
#  When in doubt, choose the interesting. -- der.hans

Re: raid10 is killing me, and applications that aren't willing towaitfor it to respond

[Matt]

Perhaps that is why I run DWM rather than GNOME on this T60 Thinkpad. :p

On 12/15/23 23:23, Greg Wooledge wrote:

On Fri, Dec 15, 2023 at 11:05:41PM -0500, Matt wrote:

I had to go to Wikipedia to understand the context of the discussion. I did
read all the posted emails in the thread.

https://en.wikipedia.org/wiki/RAID

Knowing what RAID is... is good.  But ultimately, the main takeaway from
this thread should be that when diagnosing a problem, you may sometimes
discover that the root of the problem is different from what you thought.

In Gene's case, the problem (long startup time of some applications) does
not appear to be related to his disks, but rather, to something in the
desktop environment or its underlying services.

another possible audience for Debian

[Matt]

I am a Debian user. An audience for Debian may be the Fediverse because 
the Fediverse has a technology focused culture, and its creative 
endeavors could be in the form of developing Debian if many users are 
interested. The biases of Debian vary from topic to topic in great depth 
and detail. That is closely related to the creativity of the Fediverse 
where users communicate inter-personally.

Re: raid10 is killing me, and applications that aren't willing towaitfor it to respond

[Greg Wooledge]

On Fri, Dec 15, 2023 at 11:05:41PM -0500, Matt wrote:
> I had to go to Wikipedia to understand the context of the discussion. I did
> read all the posted emails in the thread.
> 
> https://en.wikipedia.org/wiki/RAID

Knowing what RAID is... is good.  But ultimately, the main takeaway from
this thread should be that when diagnosing a problem, you may sometimes
discover that the root of the problem is different from what you thought.

In Gene's case, the problem (long startup time of some applications) does
not appear to be related to his disks, but rather, to something in the
desktop environment or its underlying services.

Re: raid10 is killing me, and applications that aren't willing towaitfor it to respond

[Matt]

I had to go to Wikipedia to understand the context of the discussion. I 
did read all the posted emails in the thread.


https://en.wikipedia.org/wiki/RAID

Re: raid10 is killing me, and applications that aren't willing towaitfor it to respond

[David Christensen]

On 12/15/23 18:23, gene heskett wrote:
I use the bleeding edge AppImage version of OpenSCAD, heavily, it has no 
such problems.  And no error outputs on the cli, it Just Works.



Thank you for the reply.  :-)


Do you mean the following?

https://openscad.org/downloads.html

*** correction *** OpenSCAD-2023.12.09.ai17758-x86_64.AppImage



QIDISlicer gives these two errors instantly on launch from cli
Cannot register URI scheme wxfs more than once

** (qidi-slicer:24330): CRITICAL **: 12:29:20.900: Cannot register URI 
scheme memory more than once


QIDISlicer has jillions of gtk2 things:
(qidi-slicer:24330): Gtk-CRITICAL **: 12:29:21.017: 
gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkScrollbar


(qidi-slicer:24330): Gtk-CRITICAL **: 04:04:12.705: 
gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkSpinButton
including 50+ of the second, and many more gtk_gedget as it opens and 
works.  And I blame the packager since there is no more gtk2 in the 
debian repo's.



Which QIDISlicer -- e.g. version?

Where did you get it -- e.g. Debian package, AppImage, source tarball, etc.?


Cura, latest 5.5.0 AppImage has a few warnings but opens in about 10 
seconds and works fine from there.



Cura version and source?



There are other AppImages but most either won't run or fail if writing.



We can save those for later.


digiKam v8.2.0 cannot import from my camera because (and this is a swag) 
it cannot get instant write perms. It can see everything in the camera, 
but cannot download anything. And does not report any errors on the cli 
when it fails.  It goes thru te motions, blinking all the lights, but 
gimp cannot find the images it just went thru the motions of downloading.



digiKam version and source?



Shotwell has the delay, and can import from the camera.



Shotwell version and source?



Spectacle works in 5 secs, but kills plasma as it exits.



Spectacle version and source?


Debugging issues for any of the above programs is likely going to 
require duplicating your Debian configuration.   Are you prepared to 
provide these details?



As a alternative to, or in parallel with, duplicating your Debian, 
duplicating your apps, and debugging the combination stack, you might 
want to implement a work-around -- install a hypervisor, pick one 
application, create a virtual machine, install only enough Debian to 
support that application, install that application and nothing else, and 
use the application.  Repeat for each application.  (Of course, this 
presumes you can find a hypervisor that runs without issues on  your 
Debian.)



Another hypervisor idea -- do a fresh install of only enough Debian to 
support a hypervisor, install the hypervisor, then convert your existing 
Debian instance into a VM.



In any case, that NVMe PCIe SSD would be ideal for VM's.


David

Re: raid10 is killing me, and applications that aren't willing towaitfor it to respond

[David Christensen]

On 12/15/23 18:23, gene heskett wrote:
I use the bleeding edge AppImage version of OpenSCAD, heavily, it has no 
such problems.  And no error outputs on the cli, it Just Works.



Thank you for the reply.  :-)


Do you mean the following?

https://openscad.org/downloads.html

OpenSCAD-2021.01-x86_64.AppImage.asc



QIDISlicer gives these two errors instantly on launch from cli
Cannot register URI scheme wxfs more than once

** (qidi-slicer:24330): CRITICAL **: 12:29:20.900: Cannot register URI 
scheme memory more than once


QIDISlicer has jillions of gtk2 things:
(qidi-slicer:24330): Gtk-CRITICAL **: 12:29:21.017: 
gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkScrollbar


(qidi-slicer:24330): Gtk-CRITICAL **: 04:04:12.705: 
gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkSpinButton
including 50+ of the second, and many more gtk_gedget as it opens and 
works.  And I blame the packager since there is no more gtk2 in the 
debian repo's.



Which QIDISlicer -- e.g. version?

Where did you get it -- e.g. Debian package, AppImage, source tarball, etc.?


Cura, latest 5.5.0 AppImage has a few warnings but opens in about 10 
seconds and works fine from there.



Cura version and source?



There are other AppImages but most either won't run or fail if writing.



We can save those for later.


digiKam v8.2.0 cannot import from my camera because (and this is a swag) 
it cannot get instant write perms. It can see everything in the camera, 
but cannot download anything. And does not report any errors on the cli 
when it fails.  It goes thru te motions, blinking all the lights, but 
gimp cannot find the images it just went thru the motions of downloading.



digiKam version and source?



Shotwell has the delay, and can import from the camera.



Shotwell version and source?



Spectacle works in 5 secs, but kills plasma as it exits.



Spectacle version and source?


Debugging issues for any of the above programs is likely going to 
require duplicating your Debian configuration.   Are you prepared to 
provide these details?



As a alternative to, or in parallel with, duplicating your Debian, 
duplicating your apps, and debugging the combination stack, you might 
want to implement a work-around -- install a hypervisor, pick one 
application, create a virtual machine, install only enough Debian to 
support that application, install that application and nothing else, and 
use the application.  Repeat for each application.  (Of course, this 
presumes you can find a hypervisor that runs without issues on  your 
Debian.)



Another hypervisor idea -- do a fresh install of only enough Debian to 
support a hypervisor, install the hypervisor, then convert your existing 
Debian instance into a VM.



In any case, that NVMe PCIe SSD would be ideal for VM's.


David

Re: Slow boot, looks like due to filesystem mounts

[Max Nikulin]

On 16/12/2023 05:08, Jeffrey Walton wrote:

The resize operation included deleting swap
at /dev/sda2, increasing disk size of /dev/sda, extending /dev/sda1,
and recreating swap at the end of /dev/sda as /dev/sda2.

[...]

$ sudo blkid
/dev/sda2: UUID="b05d2596-5301-47d1-b208-95fca81be94e" TYPE="swap"
PARTUUID="872398d9-02"
/dev/sda1: UUID="6da839d7-eace-442d-b267-838637721471"
BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="872398d9-01"

And I updated fstab:


Have you updated initrd (or some packages caused generation of new 
initramfs)? Perhaps kernel waits if a partition with old swap UUID 
requires some time to make device ready.


update-initramfs -u -k all

Re: raid10 is killing me, and applications that aren't willing towaitfor it to respond

[gene heskett]

On 12/15/23 06:17, David Christensen wrote:

On 12/14/23 18:36, gene heskett wrote:

On 12/14/23 16:36, Anssi Saari wrote:

gene heskett  writes:


It repeats per gui access. Starting a gfx program such as OpenSCAD, or
qidislicer from an xfce4 terminal cli, is delayed for this similar but
not always identical lag. And reports odd warnings etc while its
getting ready to open its gui.


Does this happen with common GUI tools too like, say, Firefox? 

firefox, no.
Or XFCE's

file manager, Thunar I believe?
Thunar, yes, but I don't use it, not my cup of tea.  It wants to be a 
replacement for mc, but fails at 90% of what mc can do.



  Or a text editor like Gedit?

Gedit has ben banned from any of my machines for at least 15 years, it 
made scrambled eggs out of of several linuxcnc configuration files I 
had to re-write from scratch, but geany has never done that.  And 
geany is as instant as nano.


  Or even the

XFCE terminal?
Comes up instantly from the menu, I use it heavily because it has 
tabs. I use them much like workspaces.


Is this info helpful?

Thank you Anssi Saari

Cheers, Gene Heskett.



It sounds like OpenSCAD and gidislicer have something in common that is 
causing the issue, while the other apps do not have that something.  So, 
the challenge is finding the shared object files (dynamic linking) 
and/or the source files (static linking) that are present in the 
affected programs and not present in the unaffected programs.



It would be helpful if you posted a list of affected programs and a list 
of unaffected programs to provide alternatives for a search.  Please 
note any programs that you did not install using conventional Debian 
packages (and that may be the root cause of the issue).


I use the bleeding edge AppImage version of OpenSCAD, heavily, it has no 
such problems.  And no error outputs on the cli, it Just Works.


QIDISlicer gives these two errors instantly on launch from cli
Cannot register URI scheme wxfs more than once

** (qidi-slicer:24330): CRITICAL **: 12:29:20.900: Cannot register URI 
scheme memory more than once


QIDISlicer has jillions of gtk2 things:
(qidi-slicer:24330): Gtk-CRITICAL **: 12:29:21.017: 
gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkScrollbar


(qidi-slicer:24330): Gtk-CRITICAL **: 04:04:12.705: 
gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkSpinButton
including 50+ of the second, and many more gtk_gedget as it opens and 
works.  And I blame the packager since there is no more gtk2 in the 
debian repo's.


Cura, latest 5.5.0 AppImage has a few warnings but opens in about 10 
seconds and works fine from there.


There are other AppImages but most either won't run or fail if writing.

digiKam v8.2.0 cannot import from my camera because (and this is a swag) 
it cannot get instant write perms. It can see everything in the camera, 
but cannot download anything. And does not report any errors on the cli 
when it fails.  It goes thru te motions, blinking all the lights, but 
gimp cannot find the images it just went thru the motions of downloading.


Shotwell has the delay, and can import from the camera.

Spectacle works in 5 secs, but kills plasma as it exits.

Thank you David.


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

Re: Is it safe to install Bookworm on a new machine now?

[John Crawley]

On 15/12/2023 13:39, John Crawley wrote:

If you don't want to wait for 6.1.67-1 to arrive in Bookworm stable, it is 
available in bookworm-proposed-updates [1][2], so one workaround would be to 
temporarily add that repository [3] to apt sources before upgrading. Debian 
point release 12.4 has just gone out, so right now there are relatively few 
other packages in bookworm-proposed-updates which might have complicated the 
situation.

[1] 
https://tracker.debian.org/news/1485406/accepted-linux-signed-amd64-61671-source-into-proposed-updates/

[2] https://wiki.debian.org/StableProposedUpdates

[3] deb https://deb.debian.org/debian stable-proposed-updates main contrib 
non-free non-free-firmware



6.1.67-1 is now available from stable-updates, a possibly better option than 
stable-proposed-updates.
https://lists.debian.org/debian-stable-announce/2023/12/msg2.html

--
John

Re: Us ha fallat l'actualització d'ahir de Debian 12.2 a Debian 12.4 ?

[Carles Pina i Estany]

Hola,

On 15 Dec 2023 at 06:51:29, Àlex wrote:
> Sembla que aviat tindrem un nou nucli que corregeix el problema, però
> no ho veuen com a urgent:

Explicació curta: si voleu tenir la versió que no hi ha problemes (dels
d'algunes targes Wifi) es pot fer servir bookworm-updates. Com a
repositoris, per exemple (treieu non-free o non-free-firmware com ho feu
servir, poso l'example complet em sembla):

deb http://deb.debian.org/debian bookworm-updates main non-free 
non-free-firmware contrib
deb https://deb.debian.org/debian-security bookworm-security main non-free 
non-free-firmware contrib

Història sencera, parlo de memòria, espero no equivocar-me:

El linux-image amb el kernel versió 6.1.65: és la versió amb problemes
amb el sistema de fitxers ext4. Va entrar a Debian 12.3 i van "anular"
12.3.

(ho miro via "dpkg -l | grep -i linux-image" i miro la columna de la
versió, no el nom del paquet que és linux-image-6.1.0-16-amd64 i coses
així)

El linux-image amb el kernel versió 6.1.66: és el que té problemes amb
algunes targes de xarxa Wifi que fan el (alguns) sistemes altament
inusable (fins i tot sense fer servir el Wifi, em sembla).

Aquesta versió, la 6.1.66, està a la versió de Debian 12.4.

Si voleu tenir la versió 6.1.67 i estar a Bookworm: es pot tenir via:
deb http://deb.debian.org/debian bookworm-updates main non-free 
non-free-firmware contrib
deb-src http://deb.debian.org/debian bookworm-updates main non-free 
non-free-firmware contrib

És a dir, bookworm-updates enlloc de bookworm. Hi ha paquets (només
alguns) que seran al proper Bookworm (12.5, d'aquí uns dos mesos suposo)
que ja estan a bookworm-updates. Com el kernel 6.1.67.

I això ha estat una mala sort impresionant. Pobre "team release" :-(

Fins aviat, vaig a reiniciar amb el 6.1.67 ara mateix :-)

-- 
Carles Pina i Estany
https://carles.pina.cat


signature.asc
Description: PGP signature

Slow boot, looks like due to filesystem mounts

[Jeffrey Walton]

Hi Everyone,

I'm running Debian Unstable with KDE in one of my Virtual Box VMs. I
had to resize /dev/sda1. The resize operation included deleting swap
at /dev/sda2, increasing disk size of /dev/sda, extending /dev/sda1,
and recreating swap at the end of /dev/sda as /dev/sda2.

I'm now experiencing a long boot time:

$ sudo dmesg
...
[1.449119] sd 1:0:0:0: [sda] Attached SCSI disk
[1.460440] sr 2:0:0:0: [sr0] scsi3-mmc drive: 32x/32x xa/form2 tray
[1.460445] cdrom: Uniform CD-ROM driver Revision: 3.20
[1.646236] sr 2:0:0:0: Attached scsi CD-ROM sr0
[   47.969663] EXT4-fs (sda1): mounted filesystem
6da839d7-eace-442d-b267-838637721471 ro with ordered data mode. Quota
mode: none.
[   48.024530] Not activating Mandatory Access Control as
/sbin/tomoyo-init does not exist.
[   48.145988] systemd[1]: Inserted module 'autofs4'

I used blkid to find UUIDs:

$ sudo blkid
/dev/sda2: UUID="b05d2596-5301-47d1-b208-95fca81be94e" TYPE="swap"
PARTUUID="872398d9-02"
/dev/sda1: UUID="6da839d7-eace-442d-b267-838637721471"
BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="872398d9-01"

And I updated fstab:

$ cat /etc/fstab
...
#
# / was on /dev/sda1 during installation
UUID=6da839d7-eace-442d-b267-838637721471 /   ext4
errors=remount-ro 0   1
# swap was on /dev/sda5 during installation
UUID=b05d2596-5301-47d1-b208-95fca81be94e noneswapsw
   0   0
/dev/sr0/media/cdrom0   udf,iso9660 user,noauto 0   0

The UUIDs match, so I am not sure what to look for next.

I ran systemd-analyze, but I don't see a problem:

$ cat analyze.txt
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.

graphical.target @2.744s
└─multi-user.target @2.744s
  └─exim4.service @2.442s +301ms
└─network-online.target @2.412s
  └─NetworkManager-wait-online.service @1.813s +598ms
└─NetworkManager.service @1.599s +212ms
  └─network-pre.target @1.576s
└─firewalld.service @1.122s +453ms
  └─polkit.service @983ms +136ms
└─basic.target @964ms
  └─sockets.target @964ms
└─dbus.socket @964ms
  └─sysinit.target @959ms
└─swap.target @959ms

└─dev-disk-by\x2duuid-b05d2596\x2d5301\x2d47d1\x2db208\x2d95fca81be94e.swap
@946ms +12ms

└─dev-disk-by\x2duuid-b05d2596\x2d5301\x2d47d1\x2db208\x2d95fca81be94e.device
@910ms

Pressing ESC during boot does not take me to a text output. I can only
switch between a black screen or three dots while this is happening.

Does anyone know what my next step should be?

Thanks in advance.

Re: differences among amd64 and i386

[Michael Stone]

On Fri, Dec 15, 2023 at 09:36:19AM -0500, Jeffrey Walton wrote:

Also see x32, . It takes advantage of
amd64 benefits, and tries to reduce the memory pressures.


x32 hasn't really gone anywhere and is unlikely to at this point; amd64 
is the only reasonable choice today for a normal user who just wants to 
use the computer.

Re: [XFCE] Quel widget a le focus ?

[didier gaumet]

Le 15/12/2023 à 19:43, Pierre ESTREm a écrit :

Didier,

Ca non je connais et je les utilise au sein d'interface graphique tkinter.

Mais c'est au niveau de X11 que j'espère trouver mon bonheur (c-à-d à un 
niveau plus bas).


Peut-être une amorce de solution ici:
https://stackoverflow.com/questions/3130912/how-do-i-detect-the-currently-focused-application

Re: [XFCE] Quel widget a le focus ?

[Pierre ESTREm]

Didier,

Ca non je connais et je les utilise au sein d'interface graphique tkinter.

Mais c'est au niveau de X11 que j'espère trouver mon bonheur (c-à-d à un 
niveau plus bas).


Merci

pierre estrem



Le 15/12/2023 à 19:29, didier gaumet a écrit :


Tout ça m'étant totalement étranger, Je ne sais pas si ça correspond à 
tes attentes mais j'ai trouvé une page web récente (2022, donc à 
priori pas obsolète) en français qui importe tkinter dans Python et 
détaille l'usage de la fonction focus_get() pour déterminer qui a le 
focus:

https://stacklima.com/python-methode-focus_set-et-focus_get/

encore une fois, ça n'est peut-être pas applicable à ta démarche et je 
n'ai peut-être pas bien saisi le contexte.


Bon courage :-)

Re: [XFCE] Quel widget a le focus ?

[didier gaumet]

Tout ça m'étant totalement étranger, Je ne sais pas si ça correspond à 
tes attentes mais j'ai trouvé une page web récente (2022, donc à priori 
pas obsolète) en français qui importe tkinter dans Python et détaille 
l'usage de la fonction focus_get() pour déterminer qui a le focus:

https://stacklima.com/python-methode-focus_set-et-focus_get/

encore une fois, ça n'est peut-être pas applicable à ta démarche et je 
n'ai peut-être pas bien saisi le contexte.


Bon courage :-)

Opencv ?

[ptilou]

Slt,

Je cherche qui a developper des script pour du recadrage d'image pas seulement 
en 2D, mais en 3D, y a un nom de fonction dans Gimps, et donc je cherche du 
processing un script avec if et for ?

Accessoirement tous bon tutos sur la librairie ? (en français )

Merci

-- 
Ptilou

Re: Copier un système (Debian) sur un disque plus grand.

[ptilou]

Le vendredi 15 décembre 2023 à 08:50:04 UTC+1, benoit a écrit :
> Bonjour,
> Je recherche une méthode sûre et facile et un logiciel libre pour copier un 
> système (Debian) sur un disque plus grand.
> J’ai cru comprendre qu’un clonage avec dd ou Clonezilla, va crée des 
> partitions de même tailles du disque source ver le disque cible.
> Les partitions vont laisser une partie du disque cible non partitionné, qu’il 
> faudra ensuite déplacer et redimensionner avec les données. Le peu 
> d’expérience que j’ai de cette étape avec Gparted, c’est que ça prend des 
> heures et que ça n’a pas toujours fonctionné.
> Il me semble que le plus simple serait de faire l’inverse : créer la table de 
> partition sur le disque cible avec cfdisk.
> Mais après je fais comment pour copier les secteurs d’amorçage, la partition 
> EFI, les droits d’accès, les liens symboliques etc ?
> Merci d’avance pour vos conseils.
> --
> Benoît
Tu copie avec dd, le disque complet puis avec fdisk du redimensionne, tu peut 
aussi le faire avec gtparted, disque, etc ...


Newbie, Detected !


-- 
Ptilou

Re: [XFCE] Quel widget a le focus ?

[Pierre ESTREm]

Bonsoir Didier et le reste du Monde,

Merci, c''est déjà une belle piste qu'un module Python existe autour de X11.
Je le sentais plutot bon carr Python est très riche en diversité.

j'espère qu'à l'instar de tkinter je pourrais connaître (les yeux 
fermés) quel widget (icone ou autre) a le focus.


J'ai vu des prototypes de fonctionsxget... et xset... mais je voudrais 
éviter du code C car Python offre plus simplement  la réalisation 
d'interfaces ! :)


Je vous tiens au courant.

pierre estrem



Le 15/12/2023 à 11:10, didier gaumet a écrit :

Le 15/12/2023 à 05:17, Pierre ESTREm a écrit :

Bonjour,

En Bash je voudrais récupérer le ID de l'objet (par exemple icone) 
qui aurait le focus clavier.


En Python y aurait-il un module qui saurait manipuler X (comme on le 
fait avec tkinter) ???


C'est ouf... c'est vrai !

Merci
pierre estrem




Bonjour

Avertissement: je n'y connais vraiment rien de rien, je réponds juste 
parce que ça pourrait très éventuellement te donner une piste


si je comprends correctement (c'est pas certain), le paquet 
pyhton3-xlib de Debian comprend les routines X11 (a priori purement 
X11, pour Wayland peut-être PyWayland dispo sur pypi.org)

Plus d'infos sur python-xlib ici:
https://github.com/python-xlib/python-xlib

et les fonctions X11 pour savoir ou fixer quel est l'objet qui a le 
focus semblent être XISetFocus et XIGetFocus:

https://www.x.org/releases/X11R7.6/doc/man/man3/XISetFocus.3.xhtml

Pour Wayland, peut-être que tu auras une idée ici des fonctions à 
appeler (je suis resté un peu sur ma fain mais je n'y connais rien et 
j'ai survolé à grande vitesse):

https://wayland.freedesktop.org/docs/html/ch04.html

Ne m'en demande pas plus, je serais bien en peine de t'apporter des 
précisions valables. Bon courage :-)

Re: The bug

[Kevin Price]

Am 15.12.23 um 15:47 schrieb Stefan Monnier:
> But that's always true: the GNU/Linux system, like all sufficiently
> complex software systems, is chuck full of bugs, many of which can
> indeed have disastrous effects if they manifest under the
> "right" circumstances.

Here are some foreseeable and preventable ones.

> AFAICT the only thing really different about "the bug"
> (#1057967/#1057969) is that it comes right after a bug that made a lot
> of noise (bug#1057843), so people have temporarily lost faith.

No faith lost on my part. And bugs are not evaluated in the amount of
noise the preceding one made.
-- 
Kevin Price

Re: raid10 is killing me, and applications that aren't willing towait for it to respond

[Stefan Monnier]

> I've no idea how to start debugging this but I feel like the problem

`strace` maybe?


Stefan

Re: The bug

[Stefan Monnier]

> If so, then IIUC the answer is a resounding "YES, it is safe!".
> Safe not to fry your ext4 by Bug#1057843, yes, Stefan.
> Safe in general, as originally asked by Rick?
> He might be lucky, or maybe less so.

But that's always true: the GNU/Linux system, like all sufficiently
complex software systems, is chuck full of bugs, many of which can
indeed have disastrous effects if they manifest under the
"right" circumstances.

AFAICT the only thing really different about "the bug"
(#1057967/#1057969) is that it comes right after a bug that made a lot
of noise (bug#1057843), so people have temporarily lost faith.



Stefan

Re: differences among amd64 and i386

[Jeffrey Walton]

On Thu, Dec 14, 2023 at 6:20 PM Greg Wooledge  wrote:
>
> On Thu, Dec 14, 2023 at 09:54:08PM +, fuf wrote:
> > Near a half month ago I bought a comp. made into 2011 year and didn't knew
> > which Debian12 to put: i386 or amd64?, chose i386 as thought that old comp.
> > didn't take amd64.
> > i386-netinst Debian 12 was being installed perfectly,  and later I could to
> > read a disk owned to the comp.:
> > CPU
> > Support Processor Intel Sandy Bridge (Dual core / Quad core) (optional)
>
> https://en.wikipedia.org/wiki/Sandy_Bridge
>
> Instruction set x86-64
> Instructionsx86, x86-64
>
> You could run amd64 on this machine.  Right now, you have a choice
> between the two, but some distributions have already dropped support
> for i386.  amd64 would be the more future-proof choice.

amd64 is probably the better choice, as Greg points out.

On the good side, amd64 also has twice the registers, and can perform
64-bit math. Both usually make software run faster.

On the downside, 64-bit increases memory pressures.

Also see x32, . It takes advantage of
amd64 benefits, and tries to reduce the memory pressures.

Jeff

Re: Copier un système (Debian) sur un disque plus grand.

[Sébastien NOBILI]

Le 2023-12-15 11:33, benoit a écrit :

En effet, il faudra éditer /etc/fstab
Donner un label au partition en les créant
Aller dans /dev/disk/by-label pour les retrouver
Puis ls -l
/dev/disk/by-uuid/

Pour afficher l'UUID et en faire un copier coller à la place des UUID 
existant dans /etc/fstab


Mais ça c'est pas douloureux, par contre, je crains plus les problèmes 
de config avec GRUB et la partition /boot/efi que je ne maitrise pas du 
tout...


Voilà 
fstab est une chose, mais en tirant la ficelle on attrape aussi grub, 
une éventuelle partition

chiffrée, donc l'initrd, que sais-je…

Ça n'est pas impossible (je l'ai déjà fait plusieurs fois), mais laisser 
gparted faire son
boulot pendant qu'on fait autre chose peut être une option intéressante 



Sébastien

Re: setting IFS to new line doesn't work while searching?

[Nicolas George]

Greg Wooledge (12023-12-15):
> Equally safe, perhaps.  Not safer.  I don't know those particular perl
> modules -- are they included in a standard Debian system, or does
> one need to install optional packages?  And then there's a learning
> curve for them as well.

File::Find is a standard module, Version::Compare is packaged.

I consider it safer because I factor mistakes in my estimate: if you get
the Perl version working without using strange constructs in your code,
the odds that it will break on special characters are vanishingly thin.
With shell, unless we tested for it, there are chances we forgot a
corner case.

> By the way, your MUA is adding 1 years to its datestamps.

It is called the Holocene calendar, the principle being that everything
that happened that might deserve to be expressed as a year in the last
12K years.

See:

https://en.wikipedia.org/wiki/Holocene_calendar

Or possibly:

https://www.youtube.com/watch?v=czgOWmtGVGs

Regards,

-- 
  Nicolas George

Re: setting IFS to new line doesn't work while searching?

[Greg Wooledge]

On Fri, Dec 15, 2023 at 02:30:21PM +0100, Nicolas George wrote:
> Greg Wooledge (12023-12-15):
> > readarray -d '' fndar < <(
> > find "$sdir" ... -printf 'stuff\0' |
> > sort -z --otherflags
> > )

> It is possible to do it safely in bash plus command-line tools, indeed.
> But in such a complex case, it is better to use something with a
> higher-level interface. I am sure File::Find and Version::Compare can
> let Perl do the same thing in a much safer way.

Equally safe, perhaps.  Not safer.  I don't know those particular perl
modules -- are they included in a standard Debian system, or does
one need to install optional packages?  And then there's a learning
curve for them as well.

By the way, your MUA is adding 1 years to its datestamps.

Re: setting IFS to new line doesn't work while searching?

[Nicolas George]

Greg Wooledge (12023-12-15):
> On Fri, Dec 15, 2023 at 01:42:14PM +0100, Nicolas George wrote:
> > Also, note that file names can also contain newlines in general. The
> > only robust delimiter is the NUL character.
> 
> True.  In order to be 100% safe, the OP's code would need to look
> more like this:
> 
> readarray -d '' fndar < <(
> find "$sdir" ... -printf 'stuff\0' |
> sort -z --otherflags
> )
> 
> The -d '' option for readarray requires bash 4.4 or higher.  If this
> script needs to run on bash 4.3 or older, you'd need to use a loop
> instead of readarray.
> 
> This may look a bit inscrutable, but the purpose is to ensure that
> a NUL delimiter is used at every step.  First, find -printf '...\0'
> will print a NUL character after each filename-and-stuff.  Second,
> sort -z uses NUL as its record separator (instead of newline), and
> produces sorted output that also uses NUL.  Finally, readarray -d ''
> uses the NUL character as its record separator.  The final result is
> an array containing each filename-and-stuff produced by find, in the
> order determined by sort, even if some of the filenames contain
> newline characters.

It is possible to do it safely in bash plus command-line tools, indeed.
But in such a complex case, it is better to use something with a
higher-level interface. I am sure File::Find and Version::Compare can
let Perl do the same thing in a much safer way.

Regards,

-- 
  Nicolas George

Re: setting IFS to new line doesn't work while searching?

[Greg Wooledge]

On Fri, Dec 15, 2023 at 01:42:14PM +0100, Nicolas George wrote:
> Also, note that file names can also contain newlines in general. The
> only robust delimiter is the NUL character.

True.  In order to be 100% safe, the OP's code would need to look
more like this:

readarray -d '' fndar < <(
find "$sdir" ... -printf 'stuff\0' |
sort -z --otherflags
)

The -d '' option for readarray requires bash 4.4 or higher.  If this
script needs to run on bash 4.3 or older, you'd need to use a loop
instead of readarray.

This may look a bit inscrutable, but the purpose is to ensure that
a NUL delimiter is used at every step.  First, find -printf '...\0'
will print a NUL character after each filename-and-stuff.  Second,
sort -z uses NUL as its record separator (instead of newline), and
produces sorted output that also uses NUL.  Finally, readarray -d ''
uses the NUL character as its record separator.  The final result is
an array containing each filename-and-stuff produced by find, in the
order determined by sort, even if some of the filenames contain
newline characters.

Re: setting IFS to new line doesn't work while searching?

[Albretch Mueller]

On 12/15/23, Greg Wooledge  wrote:
> More to the point, bash has a 'readarray' command which does what you
> *actually* want:
>
> readarray -t fndar < <(find "$sdir" ...)
>
 Yes, that was what I actually needed!

 lbrtchx

Re: setting IFS to new line doesn't work while searching?

[Nicolas George]

Albretch Mueller (12023-12-15):
> sdir="$(pwd)"
> #fndar=($(IFS=$'\n'; find "$sdir" -type f -printf '%P|%TY-%Tm-%Td
> %TI:%TM|%s\n' | sort --version-sort --reverse))
> #fndar=($(IFS='\n'; find "$sdir" -type f -printf '%P|%TY-%Tm-%Td
> %TI:%TM|%s\n' | sort --version-sort --reverse))
> fndar=($(find "$sdir" -type f -printf '%P|%TY-%Tm-%Td %TI:%TM|%s\n' |
> sort --version-sort --reverse))
> fndarl=${#fndar[@]}
> echo "// __ \$fndarl: |${fndarl}|${fndar[0]}"
> 
> the array construct ($( ... )) is using the space (between the date
> and the time) also to split array elements, but file names and paths
> may contain spaces, so ($( ... )) should have a way to reset its
> parsing metadata, or, do you know of any other way to get each whole
> -printf ... line out of find as part of array elements?

You set IFS in the subshell, but the subshell is doing nothing related
to IFS, it is just calling find and sort. You need to set IFS on the
shell that does the splitting.

Also, note that file names can also contain newlines in general. The
only robust delimiter is the NUL character.

Also, ditch batch. For simple scripts, do standard shell. For complex
scripts and interactive use, zsh rulz:

fndar=(${(f)"$(...)"})
fndar=(${(ps:\0:)"$(...)"})
fndar=(**/*(O))

(I do not think zsh can sort version numbers easily, though.)

Regards,

-- 
  Nicolas George

Re: setting IFS to new line doesn't work while searching?

[Greg Wooledge]

On Fri, Dec 15, 2023 at 12:33:01PM +, Albretch Mueller wrote:
> #fndar=($(IFS=$'\n'; find "$sdir" -type f -printf '%P|%TY-%Tm-%Td
> %TI:%TM|%s\n' | sort --version-sort --reverse))

> the array construct ($( ... )) is using the space (between the date
> and the time) also to split array elements,

Yeah, no.  That's not how it works.

You're setting IFS *inside* the command substitution whose value is
what you're trying to word-split.  It needs to be set outside.

In addition to word splitting, an unquoted command substitution's
output is going to undergo filename expansion (globbing).  So you
would also need to disable that.

More to the point, bash has a 'readarray' command which does what you
*actually* want:

readarray -t fndar < <(find "$sdir" ...)

This avoids all of the issues with word splitting and globbing and
setting/resetting the IFS variable, and is more efficient as well.

BTW, readarray is a synonym for 'mapfile'.  You may use either spelling.

setting IFS to new line doesn't work while searching?

[Albretch Mueller]

sdir="$(pwd)"
#fndar=($(IFS=$'\n'; find "$sdir" -type f -printf '%P|%TY-%Tm-%Td
%TI:%TM|%s\n' | sort --version-sort --reverse))
#fndar=($(IFS='\n'; find "$sdir" -type f -printf '%P|%TY-%Tm-%Td
%TI:%TM|%s\n' | sort --version-sort --reverse))
fndar=($(find "$sdir" -type f -printf '%P|%TY-%Tm-%Td %TI:%TM|%s\n' |
sort --version-sort --reverse))
fndarl=${#fndar[@]}
echo "// __ \$fndarl: |${fndarl}|${fndar[0]}"

the array construct ($( ... )) is using the space (between the date
and the time) also to split array elements, but file names and paths
may contain spaces, so ($( ... )) should have a way to reset its
parsing metadata, or, do you know of any other way to get each whole
-printf ... line out of find as part of array elements?

lbrtchx

Re: raid10 is killing me, and applications that aren't willing towait for it to respond

[Andy Smith]

Hello,

On Fri, Dec 15, 2023 at 12:00:00AM -0800, David Christensen wrote:
> On 12/14/23 18:36, gene heskett wrote:
> > Thunar, yes, but I don't use it, not my cup of tea.

[…]

> It sounds like OpenSCAD and gidislicer have something in common that is
> causing the issue, while the other apps do not have that something.  So, the
> challenge is finding the shared object files (dynamic linking) and/or the
> source files (static linking) that are present in the affected programs and
> not present in the unaffected programs.

I will add that the Thunar file manager was included in Gene's
"affected" list and I think Gene posted some logs before that showed
some dbus timeout.

I've no idea how to start debugging this but I feel like the problem
may exist somewhere in Gene's desktop environment and affect
things that call its file dialog.

Anyway, I think we can all agree at this point that this has got
nothing to do with RAID and mdadm. Though Gene said he has tried to
reinstall several times I think, with the same outcome, so it's not
something that's going to be avoided by another install otherwise I
might suggest that.

Thanks,
Andy

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

Re: differences among amd64 and i386

[Andy Smith]

On Thu, Dec 14, 2023 at 09:54:08PM +, fuf wrote:
> I  don't notice differences among amd64 and i386 but think to pick among
> this. Give advice, what better please?

i386 (or any other 32-bit x86) Linux should generally not ever be
used on any hardware that supports amd64.

The main reason for this is that it is a dying platform not tested
as well or supported as well by upstream Linux kernel. It will have
security bugs that are unfixed and fixes for security bugs take
longer to land than for amd64.

The next Debian release probably will not even haver installer
support for 32-bit x86 - though it will still remain as an
architecture for those who want/need to do multi-arch.

If you have software that for some reason is only available for
32-bit x86 (e.g. proprietary binary that you cannot recompile) you
are advised to run an amd64 OS with support for 32-bit userland
programs, which has been well supported on Debian for ages.

If you have some tiny device with less than 4G RAM and you don't
care about security and you don't care about being able to install
up to date versions of Debian and other Linux OS, then: I guess you
could start wondering about whether the smaller data sizes of 32-bit
code could possibly be more performant but it's tricky to determine
if they really are and generally not worth it given the mentioned
issues of 32-bit Linux.

Thanks,
Andy

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

Re: Copier un système (Debian) sur un disque plus grand.

[Basile Starynkevitch]

On 12/15/23 08:48, benoit wrote:


Bonjour,

Je recherche une méthode sûre et facile et un logiciel libre pour 
copier un système (Debian) sur un disque plus grand.




Je comprends la question de la manière suivante:


Vous disposez d'un PC (probablement un ordinateur fixe, pas un portable) 
sur lequel tourne une Debian. Cet ordinateur a deux disques, qu'on 
suppose ici être /dev/sda pour le plus petit (disque source) et /dev/sdb 
pour le plus gros (disque cible). Le BIOS ou UEFI voit bien les deux 
disques. Vous êtes capable (si besoin était) d'ouvrir le capot de 
l'ordinateur et de débrancher (temporairement) chacun de ces deux 
disques (par exemple leur câble SATA). Vous avez lu la notice du BIOS ou 
UEFI ou de la carte mère. Vous avez confiance dans votre alimentation 
électrique (pas de coupure ou d'orage prévu dans la journée), ou bien 
vous disposez d'un onduleur et d'une clef USB sur laquelle vous pouvez 
télécharger un Debian netinstall. Vous disposez en plus de quelques 
clefs USB en bon état (préférentiellement neuves) d'au moins 8Go (et 
plutôt plus) chacune.


Il reste de la place (quelques gigaoctets de libre dans une partition 
montée donc dans un système de fichier) sur l'ancien disque (sur 
/dev/sda). À vérifier avec la commande "/usr/bin/df -h".


Vous connaissez l'usage de la ligne de commande, le mot de passe root, 
et cet ordinateur est connecté à Internet de façon fiable.


Systématiquement, vous allez explicitement utiliser la commande 
"/usr/bin/sync" ou "/bin/sync" qui vidange les tampons du noyau sur les 
disques. Dans certains cas, elle prend une dizaine de secondes. Il faut 
la faire très souvent.


Vous avez préalablement sauvegardé les données les plus précieuses (ou 
les plus chères) de votre ordinateur. (précaution contre les 
catastrophes ou les fautes de frappe), peut être sur un serveur externe 
à distance ou sur des clefs USB neuves ou sur un disque externe. Vous 
seul savez quelles sont vos données les plus importantes pour vous. Les 
commandes à connaître sont /usr/bin/tar et  /usr/bin/afio et 
/usr/bin/find. Essayez bien sûr "/usr/bin/tar --help" etc.




La première étape est simplement de noter en totalité (sur un cahier, ou 
de prendre en photo avec son smartphone) la sortie des commandes 
"/sbin/fdisk -l /dev/sda" et "/sbin/fdisk -l /dev/sdb" et le contenu du 
fichier /etc/fstab (donc la sortie de "/bin/cat /etc/fstab"); si vous 
disposez d'une imprimante, imprimez ces sorties de fdisk et votre 
(ancien) fichier /etc/fstab ; il est très utile de noter la sortie de 
"/sbin/blkid" sur chacune des partitions visibles par ces commandes. Si 
on dispose de clef USB supplémentaire sauvegarder ces sorties sur une 
clef, ainsi que votre ancien répertoire /etc  et peut-être la liste 
des paquets installés par "/usr/bin/dpkg -l"




=

Ensuite, vous définissez sur papier un schéma de partitionnement du 
disque cible. A minima en respectant les contraintes suivantes:


1. il faut une petite et première partition de boot réservée de quelques 
mégaoctets réservée au BIOS / UEFI. Donc /dev/sdb1 - de nos jours, soyez 
généreux et prévoyez par exemple un demi gigaoctet (qui seront 
"gaspillées").


2. Je recommande une partition pour la racine et les logiciels systèmes 
(/sbin, /bin/, /usr/, /lib/, ) donc /dev/sdb2 - soyez généreux et 
prévoyez large (plus grand que sur le vieux disque /dev/sda). Peut-être 
300Go (mais on peut avoir bien moins, au minimum 60Go).


3. Je recommande une partition d'échange (swap) en /dev/sdb3. Prévoyez 
large, en particulier pour une machine récente que vous envisagerez 
d'améliorer dans un an ou deux par l'achat de barrettes de RAM 
supplémentaires, prévoyez une partition plus grande que la mémoire RAM 
que vous espérez avoir dans deux ans. La commande /usr/bin/free donne la 
mémoire physique actuelle et la taille actuelle de votre zone de swap. 
Une heuristique serait de prévoir pour la partition de swap 50% de plus 
que la mémoire RAM totale envisagée dans deux ans.


4. Selon l'usage de la machine une ou quelques partitions de données. A 
minima une partition pour le futur /home en /dev/sdb4. Il existe des cas 
où avoir deux partitions de données est utile voir nécessaire. Par 
exemple pour la compilation de nombreux logiciels sources, ou pour le 
traitement vidéo ou photo, la sauvegarde périodique (par crontab) de 
fichiers importants. Il existe des cas où avoir une seule partition de 
donnée est bénéfique.


==

La deuxième étape est de se fabriquer ou se procurer une clef USB 
bootable d'installation Debian netinstall. Par exemple en faisant


wget -v 
https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-12.4.0-amd64-netinst.iso


pour obtenir une image ISO d'environ 630Moctets. Ensuite, insérer une 
clef USB neuve, la détecter par la commande /usr/bin/dmesg et 
/usr/bin/df et notez sur papier quelle est cette clef USB et comment 
a-t-elle été montée automatiquement. Je la suppose ici être 

Re: Copier un système (Debian) sur un disque plus grand.

[benoit]

Le vendredi 15 décembre 2023 à 10:58, Sébastien NOBILI 
 a écrit :


> Bonjour,
> 
> Attention, de plus en plus de références aux partitions se font par UUID
> qui vont changer en repartitionnant. Tu auras donc un travail
> (probablement
> lui aussi un peu long et potentiellement douloureux) de recherche et/ou
> réparation de ton système.
> 
> Sébastien

Bonjour,

En effet, il faudra éditer /etc/fstab
Donner un label au partition en les créant
Aller dans /dev/disk/by-label pour les retrouver
Puis ls -l 
/dev/disk/by-uuid/

Pour afficher l'UUID et en faire un copier coller à la place des UUID existant 
dans /etc/fstab

Mais ça c'est pas douloureux, par contre, je crains plus les problèmes de 
config avec GRUB et la partition /boot/efi que je ne maitrise pas du tout... 

--
Benoit

Re: Copier un système (Debian) sur un disque plus grand.

[ajh-valmer]

On Friday 15 December 2023 08:48:52 benoit wrote:
> Bonjour,
> Je recherche une méthode sûre et facile et un logiciel libre pour 
> copier un système (Debian) sur un disque plus grand. 

"rsync" fait ça très bien en root et mode console.
clonage 100%.

> Le peu d’expérience que j’ai de cette étape avec Gparted, 
> c’est que ça prend des heures et que ça n’a pas toujours fonctionné. 

Pour redimensionner les partitions, il ne faut pas qu'elles soient
montées. Gparted le fait aisément, rapidement, ça fonctionne,
et en mode graphique.

Sinon, pour la taille des partitions, il y a le partitionnement en
mode LVM.
On peut modifier la taille des volumes logiques sans perte de 
données, à chaud.

Re: [XFCE] Quel widget a le focus ?

[didier gaumet]

Le 15/12/2023 à 05:17, Pierre ESTREm a écrit :

Bonjour,

En Bash je voudrais récupérer le ID de l'objet (par exemple icone) qui 
aurait le focus clavier.


En Python y aurait-il un module qui saurait manipuler X (comme on le 
fait avec tkinter) ???


C'est ouf... c'est vrai !

Merci
pierre estrem




Bonjour

Avertissement: je n'y connais vraiment rien de rien, je réponds juste 
parce que ça pourrait très éventuellement te donner une piste


si je comprends correctement (c'est pas certain), le paquet pyhton3-xlib 
de Debian comprend les routines X11 (a priori purement X11, pour Wayland 
peut-être PyWayland dispo sur pypi.org)

Plus d'infos sur python-xlib ici:
https://github.com/python-xlib/python-xlib

et les fonctions X11 pour savoir ou fixer quel est l'objet qui a le 
focus semblent être XISetFocus et XIGetFocus:

https://www.x.org/releases/X11R7.6/doc/man/man3/XISetFocus.3.xhtml

Pour Wayland, peut-être que tu auras une idée ici des fonctions à 
appeler (je suis resté un peu sur ma fain mais je n'y connais rien et 
j'ai survolé à grande vitesse):

https://wayland.freedesktop.org/docs/html/ch04.html

Ne m'en demande pas plus, je serais bien en peine de t'apporter des 
précisions valables. Bon courage :-)

Re: Copier un système (Debian) sur un disque plus grand.

[Sébastien NOBILI]

Bonjour,

Le 2023-12-15 08:48, benoit a écrit :

Le peu d’expérience que j’ai de cette étape avec
Gparted, c’est que ça prend des heures et que ça n’a pas
toujours fonctionné.

Il me semble que le plus simple serait de faire l’inverse : créer
la table de partition sur le disque cible avec cfdisk.

Mais après je fais comment pour copier les secteurs d’amorçage, la
partition EFI, les droits d’accès, les liens symboliques etc ?


Attention, de plus en plus de références aux partitions se font par UUID
qui vont changer en repartitionnant. Tu auras donc un travail 
(probablement

lui aussi un peu long et potentiellement douloureux) de recherche et/ou
réparation de ton système.

Sébastien

Re: Copier un système (Debian) sur un disque plus grand.

[benoit]

Le vendredi 15 décembre 2023 à 10:12, benoit  a écrit :

> Le vendredi 15 décembre 2023 à 09:02, Klaus Becker  a écrit 
> :
>
>> Salut,
>>
>> Pour la copie du système, fsarchiver est très bien. Tu peux créer la 
>> partition de démarrage avec cfdisk.
>>
>> Klaus
>
> Merci pour ta réponse,
>
> Je viens de jeter un œil en diagonal sur la doc de fsarchiver, il y a des 
> options pour copier un système monté (It’s called a live backup).
> Mais je n'en vois pas l'intérêt dans ce cas de le faire sur un système non 
> monté. Si on veut changer de disque on le fait avec une live.

Je voulais écrire «je n'en vois pas l'intérêt dans ce cas de le faire sur un 
système monté.»
Désolé...

> Du coup, il me faudrait une live orientée outil de "dépannage" qui inclus 
> fsarchiver et cfdisk.
> Par chance la page de fsarchiver qui traite de copier un système monté (It’s 
> called a live backup).
> https://www.fsarchiver.org/live-backup/
>
> Propose une live avec fsarchiver
>
> https://www.system-rescue.org/
>
> Ce qui me semble parfait pour ce que je veux faire.
>
> Merci
>
> --
> Benoît

Re: Copier un système (Debian) sur un disque plus grand.

[benoit]

Le vendredi 15 décembre 2023 à 09:02, Klaus Becker  a écrit :

> Salut,
>
> Pour la copie du système, fsarchiver est très bien. Tu peux créer la 
> partition de démarrage avec cfdisk.
>
> Klaus

Merci pour ta réponse,

Je viens de jeter un œil en diagonal sur la doc de fsarchiver, il y a des 
options pour copier un système monté (It’s called a live backup).

Mais je n'en vois pas l'intérêt dans ce cas de le faire sur un système non 
monté. Si on veut changer de disque on le fait avec une live.
Du coup, il me faudrait une live orientée outil de "dépannage" qui inclus 
fsarchiver et cfdisk.
Par chance la page de fsarchiver qui traite de copier un système monté (It’s 
called a live backup).
https://www.fsarchiver.org/live-backup/

Propose une live avec fsarchiver

https://www.system-rescue.org/

Ce qui me semble parfait pour ce que je veux faire.

Merci

--
Benoît

Re: Copier un système (Debian) sur un disque plus grand.

[Farget Vincent]

Bonjour,



Le 15/12/2023 à 08:48, benoit a écrit :

Bonjour,

Je recherche une méthode sûre et facile et un logiciel libre pour copier 
un système (Debian) sur un disque plus grand.


J’ai cru comprendre qu’un clonage avec dd ou Clonezilla, va crée des 
partitions de même tailles du disque source ver le disque cible.




Oui, c'est exacte, mais dans un cas comme celui-ci tu peux gérer 
partition par partition (avec Clonezilla ou dd).




Les partitions vont laisser une partie du disque cible non partitionné, 
qu’il faudra ensuite déplacer et redimensionner avec les données. Le peu 
d’expérience que j’ai de cette étape avec Gparted, c’est que ça prend 
des heures et que ça n’a pas toujours fonctionné.




Cela prends du temps de déplacer/pousser le contenu d'une partition, 
mais pas pour juste l'agrandir.


J'ai très très rarement eu des souci avec Gparted.



Il me semble que le plus simple serait de faire l’inverse : créer la 
table de partition sur le disque cible avec cfdisk.




Oui, cela rejoint ma remarque ci-dessus (gérer partition par partition) 
et celle ci-dessous sur la bonne vieille commande "rsync".




Mais après je fais comment pour copier les secteurs d’amorçage, la 
partition EFI, les droits d’accès, les liens symboliques etc ?




Un bon vieux "rsync -aHzv" résoud le problèmes des droits d'accès et 
liens symboliques.





Merci d’avance pour vos conseils.

--

Benoît





Bien cordialement.
-
Vincent.

Copier un système (Debian) sur un disque plus grand.

[Klaus Becker]

Salut,

Pour la copie du système, fsarchiver est très bien.  Tu peux créer la partition 
de démarrage avec cfdisk.

Klaus

Re: raid10 is killing me, and applications that aren't willing towait for it to respond

[David Christensen]

On 12/14/23 18:36, gene heskett wrote:

On 12/14/23 16:36, Anssi Saari wrote:

gene heskett  writes:


It repeats per gui access. Starting a gfx program such as OpenSCAD, or
qidislicer from an xfce4 terminal cli, is delayed for this similar but
not always identical lag. And reports odd warnings etc while its
getting ready to open its gui.


Does this happen with common GUI tools too like, say, Firefox? 

firefox, no.
Or XFCE's

file manager, Thunar I believe?
Thunar, yes, but I don't use it, not my cup of tea.  It wants to be a 
replacement for mc, but fails at 90% of what mc can do.



  Or a text editor like Gedit?

Gedit has ben banned from any of my machines for at least 15 years, it 
made scrambled eggs out of of several linuxcnc configuration files I had 
to re-write from scratch, but geany has never done that.  And geany is 
as instant as nano.


  Or even the

XFCE terminal?
Comes up instantly from the menu, I use it heavily because it has tabs. 
I use them much like workspaces.


Is this info helpful?

Thank you Anssi Saari

Cheers, Gene Heskett.



It sounds like OpenSCAD and gidislicer have something in common that is 
causing the issue, while the other apps do not have that something.  So, 
the challenge is finding the shared object files (dynamic linking) 
and/or the source files (static linking) that are present in the 
affected programs and not present in the unaffected programs.



It would be helpful if you posted a list of affected programs and a list 
of unaffected programs to provide alternatives for a search.  Please 
note any programs that you did not install using conventional Debian 
packages (and that may be the root cause of the issue).



David