I uninstalled OpenMediaVault (because totally overkill for me) and replaced it with borgbackup and rsync

2023-08-31 Thread Jason

Hi

I was a user of OpenMediaVault for several years. I even donated money 
to the developer.


But very provocatively OpenMediaVault is bloatware, way too big. The 
only thing I need is a reliable backup.


I had pure Debian (minimal installation, very few packages) installed 
with borgbackup and rsync.


I am now very satisfied, much more streamlined than OpenMediaVault.

Am I wrong, are my statements completely off?

Or how does your backup look like?

cheers
Jason


OpenPGP_0x0D0C34B5DF58FE9D.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature


Re: Emacsclient bug in sid

2023-08-31 Thread John Hasler
> I would use the emacsclient command in the terminal. `emacsclient -c
> -a ""` somehow does the work, but it occupies the terminal until the
> new emacsclient frame is killed,

Try
emacsclient -c -a "" &
-- 
John Hasler 
j...@sugarbit.com
Elmwood, WI USA



Re: Emacsclient bug in sid

2023-08-31 Thread Wang Yizhen

> > After upgraded to emacs 29.1+1-5, I found that the emacsclient
> > command is not working. More specifically, the following command
> > hangs emacs in daemon forever and no emacs frame pops up:
> >
> >
> > ```
> >
> > emacsclient -c -a "" -n
> >
> > ```
>
> What exactly are you trying to do?
>
> The customary way to run emacs is to have it open on your desktop. Edit
> away. Leave it open so you can come back to it. You generally shouldn't
> have more than one emacs process per user.
>
> Having set up to use emacsclient, you (or more likely, programs
> you use such as a mail reader) can then call emacsclient so you can then
> edit files from that program in emacs. If you do it that way, you don't
> get (or need) an instance of emacs in daemon mode.
>
> 
https://www.gnu.org/software/emacs/manual/html_node/emacs/Emacs-Server.html


Thanks for reply. Well, actually what I try to do is to keep an emacs 
daemon in the background. Whenever I finished editing, I would delete 
the frame while keeping the emacs running as daemon in the background. 
And next time when I wish to edit anything, I would use the emacsclient 
command in the terminal. `emacsclient -c -a ""` somehow does the work, 
but it occupies the terminal until the new emacsclient frame is killed, 
and that is the reason why I added the `-n` flag.



Best regards,

Yizhen



Re: Emacsclient bug in sid

2023-08-31 Thread Wang Yizhen

> After upgraded to emacs 29.1+1-5, I found that the emacsclient
> command is not working. More specifically, the following command
> hangs emacs in daemon forever and no emacs frame pops up:
> 
> 
> ```
> 
> emacsclient -c -a "" -n
> 
> ```


What exactly are you trying to do?

The customary way to run emacs is to have it open on your desktop. Edit
away. Leave it open so you can come back to it. You generally shouldn't
have more than one emacs process per user.

Having set up to use emacsclient, you (or more likely, programs
you use such as a mail reader) can then call emacsclient so you can then
edit files from that program in emacs. If you do it that way, you don't
get (or need) an instance of emacs in daemon mode.

https://www.gnu.org/software/emacs/manual/html_node/emacs/Emacs-Server.html


Thanks for reply. Well, actually what I try to do is to keep an emacs 
daemon in the background. Whenever I finished editing, I would delete 
the frame while keeping the emacs running as daemon in the background. 
And next time when I wish to edit anything, I would use the emacsclient 
command in the terminal. `emacsclient -c -a ""` somehow does the work, 
but it occupies the terminal until the new emacsclient frame is killed, 
and that is the reason why I added the `-n` flag.



Best regards,

Yizhen


Re: Emacsclient bug in sid

2023-08-31 Thread Max Nikulin

On 01/09/2023 00:10, Wang Yizhen wrote:

emacsclient -c -a "" -n


Instead of --alternate-editor= I would consider socket activation by 
systemd user session. It ensures that emacs server process is started in 
controlled environment that does not depend on caller process.


You may try to add explicit option --display="$DISPLAY" (I am unsure 
concerning WAYLANDDISPLAY and pgtk emacs builds). Its effect is a bit 
different from standard X11 -display option and it is a reason why it is 
used in emacs .desktop files


grep Exec /usr/share/applications/emacsclient*.desktop

However I have not tried emacs-29 and it may have new bugs.



Re: Sleep: out of control

2023-08-31 Thread The Wanderer
On 2023-08-31 at 13:03, zithro wrote:

> On 31 Aug 2023 14:17, Tom Browder wrote:
>
>> Note:  The systemd "/etc/systemd/sleep.conf" file has all entries commented
>> out.
> 
> Take care, commenting may NOT be the same as disabling/setting to NO !
> 
> Each software has its own rules, but _usually_ when you comment out the
> lines, the app built-in defaults will be used (like openssh).
> Systemd behaves like that, at least that's what I observed after
> commenting out the NTP server lines of systemd-timesync.

In this case, on my system, the file in question begins with a comment
that includes the following lines:

# Entries in this file show the compile time defaults.
# You can change settings by editing this file.
# Defaults can be restored by simply deleting this file.

In other words: the commented-out entries are present to document both
what the available configuration settings are, and what values will be
used for those settings if you do not set them to something else.

Leaving them commented does not set them, so unless they are somehow set
elsewhere, that means that the value shown in the comment will be used.

(Assuming that the component which handles those settings is going to
run at all, that is. As has been suggested, masking / etc. the
appropriate service would probably prevent that.)

Tom, does your version of that file not include a comment with that same
information?

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw



signature.asc
Description: OpenPGP digital signature


Re: Sleep: out of control

2023-08-31 Thread Tom Browder
On Thu, Aug 31, 2023 at 16:20 zithro  wrote:

> On 31 Aug 2023 14:17, Tom Browder wrote:
> > Note:  The systemd "/etc/systemd/sleep.conf" file has all entries
> commented
> > out.
>
> Take care, commenting may NOT be the same as disabling/setting to NO !
>
> Each software has its own rules, but _usually_ when you comment out the
> lines, the app built-in defaults will be used (like openssh).
> Systemd behaves like that, at least that's what I observed after
> commenting out the NTP server lines of systemd-timesync.
>
> You should uncomment and specify NO like what Michel Verdier posted.
> Ofc, if the units are masked/disabled, I guess those values are not
> used/read.
> But you never know, so belts and suspenders !


Yes, I agree, and I have already done that. Thanks!

-Tom

P.S. I rely on you experts because I know how much I don't know, and I
can't even guess how much else there is to know. Thanks for covering for me!

>
>


Re: Emacsclient bug in sid

2023-08-31 Thread Charles Curley
On Thu, 31 Aug 2023 23:59:11 +0200
Michel Verdier  wrote:

> According to your link and what I do myself I think you need to have a
> daemon running. And emacsclient -a="" launches it if it's missing.

You need an emacs process running in order to use emacsclient. It need
not be a daemon. -a="" will launch a daemon process if there isn't a
process already running, daemon or otherwise.

I think the main distinction between daemon and non-daemon is that in
daemon mode emacs may be running as a background task waiting for
connections over a socket, and with nothing on the display. Non-daemon
mode always has something on the display, even if minimized.

So, basically, yes. The technical writer's demand for precise language
came out.

-- 
Does anybody read signatures any more?

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



Re: Emacsclient bug in sid

2023-08-31 Thread Michel Verdier
On 2023-08-31, Charles Curley wrote:

> Having set up to use emacsclient, you (or more likely, programs
> you use such as a mail reader) can then call emacsclient so you can then
> edit files from that program in emacs. If you do it that way, you don't
> get (or need) an instance of emacs in daemon mode.
>
> https://www.gnu.org/software/emacs/manual/html_node/emacs/Emacs-Server.html

According to your link and what I do myself I think you need to have a
daemon running. And emacsclient -a="" launches it if it's missing.



Re: Emacsclient bug in sid

2023-08-31 Thread Cindy Sue Causey
On 8/31/23, Wang Yizhen  wrote:
>
> I recently noticed a bug for the emacs package in sid. I have not
> reported a bug before, so I wrote this email to seek for help.
>
> After upgraded to emacs 29.1+1-5, I found that the emacsclient command
> is not working. More specifically, the following command hangs emacs in
> daemon forever and no emacs frame pops up:
>
> ```
>
> emacsclient -c -a "" -n
>
> ```
>
> However, `emacsclient -c -a ""` summons the emacs frame properly
> although it occupies the terminal.


Hi, Yizhen. I don't have experience with emacs, am just chiming in to
rule out a long shot causative. Do you type that command by hand or
maybe arrow up and down through existing terminal history to find that
same line to reuse it all the time?

Or do you copy that line off of something that might not be using plain text?

The reason I ask is that on rare occasions, copy-and-pasting from
something like an Internet webpage or an advanced features text editor
can unintentionally introduce funky (fancy "curly") quotation marks
and parentheses [0]. Those curly things can break scripts because a
terminal can and will interpret curlies as a separate character from
the "straight" ones.

How a terminal can interpret those differently, I don't know. I just
know firsthand that it can and does. I once spent MANY HOURS fighting
a compiling failure or similar over this very thing. I finally
stumbled upon the difference in those marks' appearances when two
lines were visually different lengths in my terminal window.

The difference in my case was that I had copied a command off the
Internet and then manually retyped it later while trying to
personalize the affected command to fit my setup.

Note: The additional reason I stepped out here to ask is because those
quotation marks are in front of that "-n" [flag]. It comes to mind to
think that curly quotes could possibly mangle a flag following them,
but a terminal command could simply ignore curlies when nothing comes
after them. Hope that rationale makes at least a little sense. It does
"BKAC" (between keyboard and chair).

Afterthought: The reason something like curly quotes might suddenly
become an issue after years of no problems is that our operating
systems' code is getting "tighter" every year, i.e. less forgiving of
things that really shouldn't have ever worked in the first place.
That's a good thing that reflects on how Developers are perennially
honing their combined skills while presenting the most dependable
software packages possible... at any given nanosecond in Time.

Cindy :)

[0] https://chrisbracco.com/curly-quotes/
-- 
Talking Rock, Pickens County, Georgia, USA
* runs with birdseed *



Re: systemd service user uit configuratie bestand indirect zoeken

2023-08-31 Thread Geert Stappers
On Wed, Aug 30, 2023 at 07:43:30PM +0200, Geert Stappers wrote:
> Hoi,
> 
> Hoe in systemd service bestand de waarde voor 'User' zetten
> met wat nog opgezocht moet worden?
> 

Dus dat hetzelfde systemd service bestand op verschillende computers
gebruikt kan worden. (Zo als dat gaat met Debian packages.)

> 
> Lange versie van dezelfde vraag:
> 
> Er is bestand  `/etc/foo/config` met een inhoud als:
> 
> ```yaml
> foo:
>   topdir: /srv/foo
>   interval: 3600
> ```
> 
> Command `ls -ld /srv/foo/` geeft
> ```text
> drwxr-xr-x 3 baz www-data 4096 27 aug 10:26 /srv/foo/
> ```
> 
> Het is die `baz`, eigenaar van "topdir", die op de plaats van de puntjes
> in systemd service unit zou moeten komen.
> ```text
> [Unit]
> Description=Foo-tastic
> 
> [Service]
> ExecStart=/usr/bin/foo/etc/foo/config
> User=
> 
> [Install]
> WantedBy=multi-user.target
> ```
> 
> Hoe zou dat kunnen?
> 

Voor wat het waard is:

Het nieuwe inzicht is om een user aan te maken.
Zo dat in de systemd service file naam van die user staat.


 
Groeten
Geert Stappers
-- 
Silence is hard to parse



Re: Emacsclient bug in sid

2023-08-31 Thread Charles Curley
On Fri, 1 Sep 2023 01:10:46 +0800
Wang Yizhen  wrote:

> After upgraded to emacs 29.1+1-5, I found that the emacsclient
> command is not working. More specifically, the following command
> hangs emacs in daemon forever and no emacs frame pops up:
> 
> 
> ```
> 
> emacsclient -c -a "" -n
> 
> ```

What exactly are you trying to do?

The customary way to run emacs is to have it open on your desktop. Edit
away. Leave it open so you can come back to it. You generally shouldn't
have more than one emacs process per user.

Having set up to use emacsclient, you (or more likely, programs
you use such as a mail reader) can then call emacsclient so you can then
edit files from that program in emacs. If you do it that way, you don't
get (or need) an instance of emacs in daemon mode.

https://www.gnu.org/software/emacs/manual/html_node/emacs/Emacs-Server.html

-- 
Does anybody read signatures any more?

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



Re: Sleep: out of control

2023-08-31 Thread Tom Browder
On Thu, Aug 31, 2023 at 11:50 AM Michel Verdier  wrote:
> On 2023-08-31, Tom Browder wrote:
> > Is there a way to definitely deactivate all OS-related power changes so the
> > power button has only two functions (on/off)?
>
> To disable all sleep/suspend/hibernation I put in /etc/systemd/sleep.conf
>
> [Sleep]
> AllowSuspend=no
> AllowHibernation=no
> AllowSuspendThenHibernate=no
> AllowHybridSleep=no

Adding that, too, thanks.

-Tom



Re: Emacsclient bug in sid

2023-08-31 Thread Michael Kjörling
On 1 Sep 2023 01:10 +0800, from wang1zhe...@gmail.com (Wang Yizhen):
> I recently noticed a bug for the emacs package in sid. I have not reported a
> bug before, so I wrote this email to seek for help.

See https://www.debian.org/Bugs/ for information on the Debian bug
tracking process, including the proper process for reporting a
suspected bug. Thanks for helping to make Debian better!

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



Re: Fallos en mi Debian

2023-08-31 Thread Camaleón
El 2023-08-31 a las 17:19 +0100, José Manuel (Abogado) escribió:
> 
> El 30/8/23 a las 7:58, Camaleón escribió:

(...)
> > > Gracias por contestar a Fran y Camaleón
> > > 
> > > Poniendo los comandos que me indicas sale lo siguiente:
> > > 
> > > eb8cxw@debianPAPA:~$ systemctl list-units --failed
> > >   UNIT    LOAD   ACTIVE SUB    DESCRIPTION
> > > ● accounts-daemon.service loaded failed failed Accounts Service
> > > 
> > > LOAD   = Reflects whether the unit definition was properly loaded.
> > > ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
> > > SUB    = The low-level unit activation state, values depend on unit type.
> > > 1 loaded units listed.
> > 
> > Hum... no sé qué hace ese servicio. De hecho no tengo instalado el paquete, 
> > voy a
> > instruirme...
> > 
> > ***
> > https://packages.debian.org/bookworm/accountsservice
> > 
> > Package: accountsservice (22.08.8-6)
> > query and manipulate user account information
> > 
> > The AccountService project provides a set of D-Bus interfaces for
> > querying and manipulating user account information and an
> > implementation of these interfaces, based on the useradd, usermod and
> > userdel commands.
> > ***
> > 
> > Pues muy bien (me quedo igual) :-)
> > 
> > Pero bueno, ahora que ya sabes cuál falla, y siempre que quieras
> > invocar a la bestia, intenta iniciar el servicio para ver qué te dice:
> > 
> > systemctl restart accounts-daemon
> 
> No hace nada:
> 
> eb8cxw@debianPAPA:~$  systemctl restart accounts-daemon
> eb8cxw@debianPAPA:~$

¿Y ejecutado como root?

> > Si no saca nada, revisa el registro con:
> > 
> > journalctl -n
> > 
> > Y manda la salida.
> 
> Esto es lo que sale:
> 
> eb8cxw@debianPAPA:~$ journalctl -n
> Hint: You are currently not seeing messages from other users and the system.
>  Users in the 'systemd-journal' group can see all messages. Pass -q to
>  turn off this notice.

(...)

Ejecuta esta orden también como root, mejor. No vaya a ser que nos 
estemos perdiendo lo sustancial :-)

> ago 31 17:11:15 debianPAPA polkit-kde-authentication-agent-1[1528]:> 
> Finishing obtaining privileges
> ago 31 17:11:15 debianPAPA polkit-kde-authentication-agent-1[1528]: Listener 
> adapter polkit_qt_listener_initi>
> ago 31 17:11:15 debianPAPA polkit-kde-authentication-agent-1[1528]: 
> polkit_qt_listener_initiate_authenticatio>
> ago 31 17:11:15 debianPAPA polkit-kde-authentication-agent-1[1528]: Finish 
> obtain authorization: true
> ago 31 17:11:15 debianPAPA kwin_x11[1483]: kwin_core: XCB error: 152 
> (BadDamage), sequence: 41240, resource i>
> ago 31 17:11:42 debianPAPA kwin_x11[1483]: qt.qpa.xcb: QXcbConnection: XCB 
> error: 3 (BadWindow), sequence: 48>
> ago 31 17:11:52 debianPAPA kwin_x11[1483]: qt.qpa.xcb: QXcbConnection: XCB 
> error: 3 (BadWindow), sequence: 52>
> ago 31 17:13:16 debianPAPA plasmashell[1509]: Could not find the Plasmoid for 
> Plasma::FrameSvgItem(0x55aacb88>
> ago 31 17:13:16 debianPAPA plasmashell[1509]: Could not find the Plasmoid for 
> Plasma::FrameSvgItem(0x55aacb88>
> ago 31 17:13:21 debianPAPA kwin_x11[1483]: qt.qpa.xcb: QXcbConnection: XCB 
> error: 3 (BadWindow), sequence: 10 lines 1-10/10 (END)

(...)

> > > ago 29 16:46:47 debianPAPA plasmashell[4181]: libva error:> 
> > > /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
> > > ago 29 16:47:38 debianPAPA plasmashell[4181]: libva error:  
> > > /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
> > > ago 29 16:47:39 debianPAPA plasmashell[4181]: libva error: 
> > > /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
> > > ago 29 16:48:42 debianPAPA plasmashell[4181]: libva error: 
> > > /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
> > > ago 29 16:49:02 debianPAPA plasmashell[4181]: libva error: 
> > > /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
> > > 
> > > No entiendo mucho pero parece que esta en el vídeo, ya me diréis,
> > Sí, esto parece más importante.
> > 
> > Ese archivo que falla al inicializar está en el paquete
> > «intel-media-va-driver» y también en «intel-media-va-driver-non-free»
> > que es para la aceleración de la gráfica (Intel).
> > 
> > Veo varios bugs abiertos en Ubuntu, Archlinux, Fedora... con ese mismo
> > error que te aparece, pero mi recomendación es que si no experimentas
> > ningún problema evidente y efectivo (más allá del mensaje), si no notas
> > mal rendimiento en el sistema gráfico ni se bloquea el equipo o las
> > aplicaciones, esperes a que lo corrijan en una actualización de la
> > versión de los paquetes (falla en la 23.1.1+dfsg1-1, corregido en la
> > 23.2.3+dfsg1):

> Salvo los que  indique al inicio de este hilo no he notada de momento nada
> más
> > libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init
> > failed
> > https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1966571

Entonces mejor espera. 

Si ves alguna actualización del paquete cuando te lo notifique Debian, 
una vez que se actualice 

Emacsclient bug in sid

2023-08-31 Thread Wang Yizhen

Dear Debian-user group:


I recently noticed a bug for the emacs package in sid. I have not 
reported a bug before, so I wrote this email to seek for help.



After upgraded to emacs 29.1+1-5, I found that the emacsclient command 
is not working. More specifically, the following command hangs emacs in 
daemon forever and no emacs frame pops up:



```

emacsclient -c -a "" -n

```


However, `emacsclient -c -a ""` summons the emacs frame properly 
although it occupies the terminal.



Thanks for your help.


Best regards,

Yizhen



Re: Sleep: out of control

2023-08-31 Thread zithro

On 31 Aug 2023 14:17, Tom Browder wrote:

Note:  The systemd "/etc/systemd/sleep.conf" file has all entries commented
out.


Take care, commenting may NOT be the same as disabling/setting to NO !

Each software has its own rules, but _usually_ when you comment out the 
lines, the app built-in defaults will be used (like openssh).
Systemd behaves like that, at least that's what I observed after 
commenting out the NTP server lines of systemd-timesync.


You should uncomment and specify NO like what Michel Verdier posted.
Ofc, if the units are masked/disabled, I guess those values are not 
used/read.

But you never know, so belts and suspenders !


--
++
zithro / Cyril



Re: Fallos en mi Debian

2023-08-31 Thread Abogado


El 30/8/23 a las 7:58, Camaleón escribió:

El 2023-08-29 a las 20:01 +0100, José Manuel (Abogado) escribió:

El 29/8/23 a las 7:29, Camaleón escribió:

El 2023-08-28 a las 20:51 +0100, José Manuel (Abogado) escribió:


Me aparecen dos fallos que no se porque sucede, por lo que me dirijo a
ustedes por si me pueden orientar, cosa que les agradezco de antemano.

Tengo Debian Bookworm

Primer fallo, en el arranque me aparece la palabra fallo en rojo pero al ser
rápido no me da tiempo a saber que lo que pone

Añado a lo ya indicado por Fran.

La orden «systemctl list-units --failed» te permite enumerar los
servicios fallidos.

Y con «journalctl -b | grep -i -e fallo -e failed» también podrás ver los 
registros
del arranque actual con la palabra «fallo» o «failed».

Segundo fallo por consola, al actualizar algún paquete al terminar a través
de sudo me aparece lo siguiente en las últimas líneas:

...

libdvd-pkg: Checking orig.tar integrity...
/usr/src/libdvd-pkg/libdvdcss_1.4.3.orig.tar.bz2: La suma coincide
libdvd-pkg: `apt-get check` failed, you may have broken packages.
Aborting...

No sé si has probado a reconfigurar el paquete con la orden «dpkg-reconfigure
libdvd-pkg».



Hola

Gracias por contestar a Fran y Camaleón

Poniendo los comandos que me indicas sale lo siguiente:

eb8cxw@debianPAPA:~$ systemctl list-units --failed
  UNIT    LOAD   ACTIVE SUB    DESCRIPTION
● accounts-daemon.service loaded failed failed Accounts Service

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.
1 loaded units listed.


Hum... no sé qué hace ese servicio. De hecho no tengo instalado el paquete, voy 
a
instruirme...

***
https://packages.debian.org/bookworm/accountsservice

Package: accountsservice (22.08.8-6)
query and manipulate user account information

The AccountService project provides a set of D-Bus interfaces for
querying and manipulating user account information and an
implementation of these interfaces, based on the useradd, usermod and
userdel commands.
***

Pues muy bien (me quedo igual) :-)

Pero bueno, ahora que ya sabes cuál falla, y siempre que quieras
invocar a la bestia, intenta iniciar el servicio para ver qué te dice:

systemctl restart accounts-daemon


No hace nada:

eb8cxw@debianPAPA:~$  systemctl restart accounts-daemon
eb8cxw@debianPAPA:~$


Si no saca nada, revisa el registro con:

journalctl -n

Y manda la salida.


Esto es lo que sale:

eb8cxw@debianPAPA:~$ journalctl -n
Hint: You are currently not seeing messages from other users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
ago 31 17:11:15 debianPAPA polkit-kde-authentication-agent-1[1528]: 
Finishing obtaining privileges
ago 31 17:11:15 debianPAPA polkit-kde-authentication-agent-1[1528]: 
Listener adapter polkit_qt_listener_initi>
ago 31 17:11:15 debianPAPA polkit-kde-authentication-agent-1[1528]: 
polkit_qt_listener_initiate_authenticatio>
ago 31 17:11:15 debianPAPA polkit-kde-authentication-agent-1[1528]: 
Finish obtain authorization: true
ago 31 17:11:15 debianPAPA kwin_x11[1483]: kwin_core: XCB error: 152 
(BadDamage), sequence: 41240, resource i>
ago 31 17:11:42 debianPAPA kwin_x11[1483]: qt.qpa.xcb: QXcbConnection: 
XCB error: 3 (BadWindow), sequence: 48>
ago 31 17:11:52 debianPAPA kwin_x11[1483]: qt.qpa.xcb: QXcbConnection: 
XCB error: 3 (BadWindow), sequence: 52>
ago 31 17:13:16 debianPAPA plasmashell[1509]: Could not find the 
Plasmoid for Plasma::FrameSvgItem(0x55aacb88>
ago 31 17:13:16 debianPAPA plasmashell[1509]: Could not find the 
Plasmoid for Plasma::FrameSvgItem(0x55aacb88>
ago 31 17:13:21 debianPAPA kwin_x11[1483]: qt.qpa.xcb: QXcbConnection: 
XCB error: 3 (BadWindow), sequence: 10>

lines 1-10/10 (END)



eb8cxw@debianPAPA:~$ journalctl -b | grep -i -e fallo -e failed
Hint: You are currently not seeing messages from other users and the system.
  Users in the 'systemd-journal' group can see all messages. Pass -q to
  turn off this notice.
ago 29 15:45:45 debianPAPA wireplumber[1584]: Failed to set scheduler settings: 
Operación no permitida
ago 29 15:45:46 debianPAPA wireplumber[1584]:  
failed to activate item: Object activation aborted: proxy destroyed
ago 29 15:45:55 debianPAPA org_kde_powerdevil[1766]: org.kde.powerdevil: 
org.kde.powerdevil.chargethresholdhel per.getthreshold failed "Charge thresholds are 
not supported by the kernel for this hardware"
ago 29 15:45:55 debianPAPA org_kde_powerdevil[1766]: org.kde.powerdevil: 
org.kde.powerdevil.backlighthelper.brightness failed
ago 29 15:45:57 debianPAPA org_kde_powerdevil[1766]: org.kde.powerdevil: 
org.kde.powerdevil.chargethresholdhelper.getthreshold failed "Charge thresholds are 
not supported by the kernel for this hardware"
ago 29 15:45:57 debianPAPA kwin_x11[1715]: kf.config.core: "\"fsrestore1\" - 

Re: Mise à jours et Update Stretch - Problème de dépôt

2023-08-31 Thread Daniel SAUVARD

Bonjour.

Depuis l'année dernière, Debian n'assure plus le support de Stretch (fin 
du support LTS). Un support partiel reste possible via le projet 
Extended Long Term Support (ELTS, https://wiki.debian.org/LTS/Extended ; 
pour 5 ans, soit jusqu'au 2027-06-30). Il faut supprimer les dépôts 
Debian (qui ne sont à priori plus accessibles) et les remplacer par ceux 
de Freexian).


En pratique :
- Éditer le fichier source.list et désactiver les dépôts Debian.
- Ajouter la clé de l'archive Freexian.
# wget 
https://deb.freexian.com/extended-lts/pool/main/f/freexian-archive-keyring/freexian-archive-keyring_2022.06.08_all.deb 
&& dpkg -i freexian-archive-keyring_2022.06.08_all.deb
  Contrôler la clé avec « # apt-key finger | less », en comparant 
l'empreinte avec celle indiquée sur la page 
https://www.freexian.com/lts/extended/docs/how-to-use-extended-lts/.
- Activer les dépôts Freexian, par exemple en créant le fichier 
/etc/apt/sources.list.d/extended-lts.list, contenant :

# ELTS archive
deb http://deb.freexian.com/extended-lts stretch-lts main
  Nota Le serveur n'utilise pas les dépôts contrib et non-free.
- Mettre à jour du système :
# apt update
# apt upgrade
  Redémarrer le système si le noyau a été mis à jour.

Cordialement,
Daniel Sauvard



Le 29/08/2023 à 13:53, Hugues MORIN-TRENEULE a écrit :

Salut à tous

J'ai fait une boulette, je n'ai pas upgradé .
A force de me procrastiner l'upgrade d'une machine sous Stretch dont je 
me sers occasionnellement, je me trouve un peu embêter aujourd'hui.


En voulant faire un petit check des mises à jour, je me suis aperçu que 
les dépôts Stretch enregistrés dans mon source.list n'existe plus:
# deb cdrom:[Debian GNU/Linux 9.2.1 _Stretch_ - Official amd64 NETINST 
20171013-13:07]/ stretch main


#deb cdrom:[Debian GNU/Linux 9.2.1 _Stretch_ - Official amd64 NETINST 
20171013-13:07]/ stretch main


deb http://ftp.fr.debian.org/debian/  
stretch main contrib non-free
deb-src http://ftp.fr.debian.org/debian/ 
 stretch main contrib non-free


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


# stretch-updates, previously known as 'volatile'
deb http://ftp.fr.debian.org/debian/  
stretch-updates main contrib non-free
deb-src http://ftp.fr.debian.org/debian/ 
 stretch-updates main contrib non-free


J'aimerai upgrader cette machine (tout d'abord vers buster) mais avant 
cela il faudrait que je mette à jours les paquets de stretch pour ne pas 
avoir de soucis avec les upgrade a venir.


Pour le dépot principal (http://ftp.fr.debian.org/debian/ 
 stretch) , en cherchant, j'ai trouvé 
le depot archive Debian: http://archive.debian.org/debian 

Est ce que vous pourriez me confirmer qu'il me permettra de mettre les 
paquets de stretch à jours jusqu'à leur dernière version.


Concernant les dépôts "security" et "volatile", existe-t-il aussi des 
dépôts archive que je pourrai utiliser?


Je ne maitrise pas bien tout ce qui est en lien avec les dépôts et les 
mise à jours donc je suis ouvert à vos suggestions et conseils.


Bonne journée
Cordialement
Hugues







Re: Sleep: out of control

2023-08-31 Thread Tom Browder
On Thu, Aug 31, 2023 at 08:12 Marco  wrote:

> Am 31.08.2023 schrieb Tom Browder :
>
> > Is there a way to definitely deactivate all OS-related power changes
> > so the power button has only two functions (on/off)?
>
> You can disable sleep/hibernate at all.
>
> sudo systemctl mask sleep.target suspend.target hibernate.target
> hybrid-sleep.target


Thanksso much, Marco, I'll give that a try and report back in a couple of
days.

-Tom


Re: Sleep: out of control

2023-08-31 Thread Michel Verdier
On 2023-08-31, Tom Browder wrote:

> Is there a way to definitely deactivate all OS-related power changes so the
> power button has only two functions (on/off)?

To disable all sleep/suspend/hibernation I put in /etc/systemd/sleep.conf

[Sleep]
AllowSuspend=no
AllowHibernation=no
AllowSuspendThenHibernate=no
AllowHybridSleep=no



Re: Sleep: out of control

2023-08-31 Thread Marco
Am 31.08.2023 schrieb Tom Browder :

> Is there a way to definitely deactivate all OS-related power changes
> so the power button has only two functions (on/off)?

You can disable sleep/hibernate at all.

sudo systemctl mask sleep.target suspend.target hibernate.target 
hybrid-sleep.target



Re: door bell like sound effect

2023-08-31 Thread songbird
Karl Vogel wrote:
> On Wed, Aug 30, 2023 at 07:55:14AM -0400, songbird wrote:
>> Karl Vogel wrote:
>> ...
>> > If nothing else, it's faster to run "locate" and look for file extensions;
>> > running "file" on that much crap took nearly 9 hours.
>> 
>> do you have SSDs or spinning rust?
>
>   I have a 256-Gb SSD and two mirrored Western Digital Blue 1.8-Tb drives.
>   About 2 million files are on SSD and the rest are on rust.
>
>   I used "file" v5.45 built from source, which does a nice job but is IO-
>   and CPU-intensive.

  mirroring is going to be quite a difference, especially 
if you are updating each file's access time (see below).


>> when i just did this:
>> # find / -type f | wc -l
>> it took all of 24 seconds for the 2.4 million files found.
>
>   Generating hashes for SSD files is faster than getting the filetype;
>   it takes about 17 minutes for 3.6 million files (153 Gbytes).  I like
>   the Blake-2 hash cuz it's fast as hell, among other things:
>
> #!/bin/ksh
> #
> export PATH=/usr/local/bin:/bin:/usr/bin
> tag=${0##*/}
> set -o nounset
> umask 022
>
> logmsg () { logger -t "$tag" "$@"; }
> die (){ logmsg "FATAL: $@"; exit 1; }
>
> work=$(mktemp -q "/tmp/$tag.work.XX")
> case "$?" in
> 0)  test -f "$work" || die "$work: tmp list file not found" ;;
> *)  die "can't create work file" ;;
> esac
>
> # Get a list of all regular files on SSD.
>
> mount | grep '^zroot' | awk '{print $3}' |
>   while read dataset
>   do
>   logmsg "listing $dataset"
>   find "$dataset" -xdev -type f -print0 >> $work
>   done
>
> # Store hashes for SSD datasets.
> # The hash file is sorted by filename to make comparisons easier.
>
> logmsg "running b2sum"
> fdbdir=$(date '+/var/fdb/%Y/%m%d')
> sort -z $work | xargs -0r b2sum -l 128 > "$fdbdir/zroot.sum"
> rm $work
> exit 0
>
>   Useful for finding changed files -- security, backups, etc.
>
>> what script did you use?
>
> #!/bin/ksh
> #
> export PATH=/usr/local/bin:/bin:/usr/bin
> set -o nounset
> tag=${0##*/}
> umask 022
>
> logmsg () { logger -t "$tag" "$@"; }
>
> work="/tmp/$tag.$$"
> fsys="/ /doc /home /usr/local /search /usr/src /dist /src"
>
> logmsg start
> find $fsys -xdev -print0 | xargs -0 file -N --mime-type > $work
> logmsg finish
>
> mv $work filetypes
> exit 0

  interesting and thanks for that.  :)

  my comments that follow are geared towards finding the
files that have been referenced and changed only in recent
times so that you are not having to process the entire 
file system.

  so the find statement would be adjusted to use -cmin or 
-amin (depending upon if i want to find changes or accessed 
files) and the file command would include the parameter 
flag -p to avoid updating the access time.


  as for the other topic of finding changed files and using
hashes is a whole different topic and one that i don't need.
this is the sort of thing that git can do so i would not
want to reinvent that if i don't really need to (which at
present i don't).  i keep track of certain directories and
that's all i need.  for directories or file systems that i
need read only i use the read only mount feature or set
permissions.


  songbird



Sleep: out of control

2023-08-31 Thread Tom Browder
My main Debian host is going to sleep and I can't awaken it without
holdiing the power button down for some period.

We have had some neighborhood power issues recently, and I have been
manually powering down while away for a few short trips (no UPS yet,
either, but my Windows box next to the Debian host [same power source] is
solidly running).

A search of the logs shows entries for power from various system sources on
a daily basis (syslog)::, but I haven't seen anything about overheating or
such. I know the internal motherboard thermal sensors work (don't ask), so
I'm not worried about real overheating.

Is there a way to definitely deactivate all OS-related power changes so the
power button has only two functions (on/off)?

Note:  The systemd "/etc/systemd/sleep.conf" file has all entries commented
out.

Thanks for any ideas.

-Tom


Re: muis /sys/devices/platform/i8042/serio1/ "speed" ontbreekt

2023-08-31 Thread Gijs Hillenius
On 31 August 2023 10:19 Paul van der Vlis, wrote:

> Op 31-08-2023 om 09:53 schreef Gijs Hillenius:
>> [...]
>> 
>>>
>>> Standaard staat hij tegenwoordig wel erg langzaam inderdaad.
>> xinput --set-prop "TPPS/2 Elan TrackPoint" "libinput Accel Speed" 1
>> Als het een Elan Trackpoint is dan is - volgens mij - op dit moment
>> het
>> enige wat ik kan instellen. In Gnome toont ie dan in de settings:
>> "fast".
>
> Dit blijkt een ALPS trackpoint te zijn, dus inderdaad een andere.

Exact! dat is de andere. Die is echt supersnel/soepel.

> Overigens had ik eerder gezegd dat ik testte met een Thinkpad T480s,
> dat was een vergissing, het is een T490. Wat voor machine gebruik jij?

Een X1 Carbon uit 2020 (7th Gen).



Re: muis /sys/devices/platform/i8042/serio1/ "speed" ontbreekt

2023-08-31 Thread Paul van der Vlis

Op 31-08-2023 om 09:53 schreef Gijs Hillenius:


[...]



Standaard staat hij tegenwoordig wel erg langzaam inderdaad.


xinput --set-prop "TPPS/2 Elan TrackPoint" "libinput Accel Speed" 1


Als het een Elan Trackpoint is dan is - volgens mij - op dit moment het
enige wat ik kan instellen. In Gnome toont ie dan in de settings:
"fast".


Dit blijkt een ALPS trackpoint te zijn, dus inderdaad een andere.

Overigens had ik eerder gezegd dat ik testte met een Thinkpad T480s, dat 
was een vergissing, het is een T490. Wat voor machine gebruik jij?



Het mag echt nog wel sneller, om een kromme muisvinger te
voorkomen, maar affijn. Er zijn belangrijker dingen

Mocht je het willen weten:

Ik heb met deze trackpad ook af en toe last van een wegdrijvende
muis-aanwijzer (Lenovo erkent dat dit gebeurt... er zijn wel eens
bugfixes voor die "Fixed long drift issue of ELAN TrackPoint".

Dat is dat de muispointer helemaal vanzelf en zeer halstarrig naar links
(of rechts) schuift. Moet je ff wachten tot het stopt, of naar een
andere desktop springen.


Dat heb ik ook weleens gehad met een laptop. Ik weet alleen niet meer zo 
goed wat ik ertegen gedaan heb. Waarschijnlijk een paar keer flink alle 
kanten op bewogen, of het rubbertje vervangen.



Mijn backup-laptop, vorige generatie uit dezelfde serie, heeft een
andere Trackpoint. Die is zo snel ..


Wellicht gebruik je een nieuwe laptop, met kans op kinderziektes.

Wellicht zou je het backports kernel kunnen proberen dan, wellicht is 
het probleem daar opgelost.


Groet,
Paul



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



Re: door bell like sound effect

2023-08-31 Thread Michel Verdier
On 2023-08-30, Karl Vogel wrote:

> logmsg "running b2sum"
> fdbdir=$(date '+/var/fdb/%Y/%m%d')
> sort -z $work | xargs -0r b2sum -l 128 > "$fdbdir/zroot.sum"
> rm $work
> exit 0
>
>   Useful for finding changed files -- security, backups, etc.

tripwire from local host and stealth from remote host do this more
securely. Both are packaged.



Re: muis /sys/devices/platform/i8042/serio1/ "speed" ontbreekt

2023-08-31 Thread Gijs Hillenius


[...]

>
> Standaard staat hij tegenwoordig wel erg langzaam inderdaad.

xinput --set-prop "TPPS/2 Elan TrackPoint" "libinput Accel Speed" 1


Als het een Elan Trackpoint is dan is - volgens mij - op dit moment het
enige wat ik kan instellen. In Gnome toont ie dan in de settings:
"fast".

Het mag echt nog wel sneller, om een kromme muisvinger te
voorkomen, maar affijn. Er zijn belangrijker dingen

Mocht je het willen weten:

Ik heb met deze trackpad ook af en toe last van een wegdrijvende
muis-aanwijzer (Lenovo erkent dat dit gebeurt... er zijn wel eens
bugfixes voor die "Fixed long drift issue of ELAN TrackPoint".

Dat is dat de muispointer helemaal vanzelf en zeer halstarrig naar links
(of rechts) schuift. Moet je ff wachten tot het stopt, of naar een
andere desktop springen.

Mijn backup-laptop, vorige generatie uit dezelfde serie, heeft een
andere Trackpoint. Die is zo snel .. 





-- 
It is better to have loved and lost -- much better.



Re: Grub

2023-08-31 Thread Camaleón
El 2023-08-30 a las 16:50 -0700, latin...@vcn.bc.ca escribió:

> Necesito instalar Grub u otro Boot Loader, en /dev/sda2, como se hace por
> favor?

Desde un sistema arrancable:

grub-install /dev/sda2

Desde un sistema que no inicia, recomiendo Super Grub2 Disk¹ o alguna 
versión LiveCD de linux para instatarlo desde línea de órdenes, ya que 
de manera predeterminada (si no se especifica nada), se suele instalar 
en el sector de arranque del disco marcado como de inicio, no en la 
partición, que es lo que buscas.

Antes de hacer nada, a tener en cuenta varias cosas, como si se trata 
de un sistema con BIOS o UEFI, si hay otros sistemas operativos o 
discos, si hay RAID (hardware o software), volúmenes (LVM), cifrado, 
etc²...

¹https://www.supergrubdisk.org/super-grub2-disk/
²https://wiki.archlinux.org/title/GRUB#Install_grub2-bios_package

Saludos,

-- 
Camaleón