Updating kernels impossible when /boot is getting full

[Ilkka Huotari]

Hi,

I'm using Ubuntu 21. My /boot partition size is 500M and it's getting full:

/dev/sda1   446M  352M   61M  86% /boot

What's taking space are mainly these:

-rw-r--r--  1 root root 153M heinä  10 14:22 initrd.img-5.11.0-22-generic
-rw-r--r--  1 root root 151M heinä  23 13:13 initrd.img-5.11.0-25-generic

apt-get upgrade fails:

update-initramfs: Generating /boot/initrd.img-5.11.0-25-generic
Error 24 : Write error : cannot write compressed block
E: mkinitramfs failure cpio 141 lz4 -9 -l 24
update-initramfs: failed for /boot/initrd.img-5.11.0-25-generic with 1.
dpkg: error processing package initramfs-tools (--configure):
 installed initramfs-tools package post-installation script subprocess
returned error exit status 1
Errors were encountered while processing:
 initramfs-tools
E: Sub-process /usr/bin/dpkg returned an error code (1)

Resizing the partitions is very complicated because I'm using an encrypted
partition ( https://help.ubuntu.com/community/ResizeEncryptedPartitions ).
So that's really not an option for me.

How to fix this:

I suggest that apt-get/dpkg handles upgrading outside /boot. Two kernels
seem to fit there if the updating is done cleverly. Or if only one kernel
fits, then keep only on kernel in /boot.

Thanks,
Ilkka

Re: Google sites don't work

[Greg Wooledge]

On Sat, Jul 31, 2021 at 08:54:12PM +, Kleene, Steven (kleenesj) wrote:
> My home desktop is running Buster (4.19.0-17-amd64) and firefox-esr
> 78.12.0esr-1~deb10u1.  Neither translate.google.com nor images.google.com
> functions properly.  If I go to Google Translate and enter "je ne sais pas"
> in the left window, nothing happens.  It should automatically show a
> translation at the right.  If I go to Google Images and search for
> "solenodon", I get a full page of fine pictures of solenodons.  But there are
> two problems.  If I put the cursor over an image, I get a pointing finger
> icon.  (No, not that finger.)  But if I click, nothing happens.

My guess is that you somehow disabled Javascript, either by clicking
something in the configuration screen (or fat-fingering some magical
keyboard equivalent), or by installing an add-on like NoScript.

Re: Youtube-dl ya no me funciona.

[Mancho]

Cordial saludo

Recomiendo instalar youtube-dl siguiendo las pautas de su página web, porque la 
versión en los repositorios debian está atrasada respecto a la versión última, 
que corrige y se adapta a los constantes cambios de plataformas como YouTube.

http://ytdl-org.github.io/youtube-dl/download.html
-- 
Germán Avendaño Ramírez
Lic. Mat. U.D., M.Sc. U.N.
Delegado ADE
Cel: 3005512546
Canal Telegram: 
https://t.me/ManchoDistritoProfes

Google sites don't work

[Kleene, Steven (kleenesj)]

My home desktop is running Buster (4.19.0-17-amd64) and firefox-esr
78.12.0esr-1~deb10u1.  Neither translate.google.com nor images.google.com
functions properly.  If I go to Google Translate and enter "je ne sais pas"
in the left window, nothing happens.  It should automatically show a
translation at the right.  If I go to Google Images and search for
"solenodon", I get a full page of fine pictures of solenodons.  But there are
two problems.  If I put the cursor over an image, I get a pointing finger
icon.  (No, not that finger.)  But if I click, nothing happens.  It should
open up a window at the right to lead me to the source of that image.
Furthermore, if I scroll down, all the images below the first page appear
just as rectangles filled with some solid color (most being brownish).  The
tests were done with firefox in standard security mode (not strict), and not
using a private browsing window or any add-ons.  I haven't noticed problems
with any other websites.

Some history and other evidence...
1. I ran Stretch on this PC for about three years, and this all worked until
   one day a few months ago when it didn't.  I upgraded to Buster hoping that
   would fix it, but it hasn't.
2. On a Stretch machine at work, this all works well.
3. I just removed my whole ~/.mozilla filesystem and did a clean start of
   firefox.  The sites still failed.  So it doesn't seem to be peculiar to my
   personal firefox configuration.
4. On my other browser (torbrowser), the sites work well.  So the hardware
   can do it.

I'd appreciate any suggestions on how to get this working.  Thanks.

Re: exim4 as a smarthost with TLS

[rudu]

Guys, guess what ?

I received my test mails !!!

Reco, thank you very much, Sven also for your input.

Rudu

Youtube-dl ya no me funciona.

[Aristobulo Pinzon]

Hola amigos de la lista.
Instalé youtube-dl con apt-get,y al correlo me dio semejánte negativa:

youtube-dl https://www.youtube.com/watch?v=vla1Pp1IB7E
[youtube] vla1Pp1IB7E: Downloading webpage
[youtube] vla1Pp1IB7E: Downloading video info webpage
WARNING: unable to download video info webpage: HTTP Error 410: Gone
WARNING: unable to download video info webpage: HTTP Error 410: Gone
WARNING: unable to download video info webpage: HTTP Error 410: Gone
WARNING: unable to download video info webpage: HTTP Error 410: Gone
WARNING: unable to download video info webpage: HTTP Error 410: Gone
Traceback (most recent call last):
  File "/usr/lib/python2.7/runpy.py", line 174, in _run_module_as_main
"__main__", fname, loader, pkg_name)
  File "/usr/lib/python2.7/runpy.py", line 72, in _run_code
exec code in run_globals
  File "bin+/youtube-dl/__main__.py", line 19, in 
  File "bin+/youtube-dl/youtube_dl/__init__.py", line 465, in main
  File "bin+/youtube-dl/youtube_dl/__init__.py", line 455, in _real_main
  File "bin+/youtube-dl/youtube_dl/YoutubeDL.py", line 1927, in download
  File "bin+/youtube-dl/youtube_dl/YoutubeDL.py", line 762, in extract_info
  File "bin+/youtube-dl/youtube_dl/extractor/common.py", line 433, in extract
  File "bin+/youtube-dl/youtube_dl/extractor/youtube.py", line 1526,
in _real_extract
TypeError: argument of type 'NoneType' is not iterable

Que pudo suceder?...
Muchas gracias.

-- 
Que es Dios?
Dios es la inteligencia suprema, causa primera de todas las cosas.

Re: exim4 as a smarthost with TLS

[rudu]

Reco, Sven, thank you for your help, my next steps below :

Le 31/07/2021 à 16:24, Reco a écrit :

On Sat, Jul 31, 2021 at 04:03:43PM +0200, Sven Hartge wrote:

Reco  wrote:

On Sat, Jul 31, 2021 at 02:45:34PM +0200, Sven Hartge wrote:

Reco  wrote:


Seems straightforward enough.
Edit /etc/exim4/exim4.conf.template, you'll need to comment out a block
similar to this:
  .ifndef REMOTE_SMTP_SMARTHOST_TLS_VERIFY_HOSTS
    REMOTE_SMTP_SMARTHOST_TLS_VERIFY_HOSTS = *
  .endif
Do not touch second block (starting with .ifdef
REMOTE_SMTP_SMARTHOST_TLS_VERIFY_HOSTS).
Execute /usr/sbin/update-exim4.conf.
Bounce exim4.
Smarthost certificate verification should be disabled after this.

Wouldn't it be easier to just create /etc/exim4/exim4.conf.localmacros
and put

  REMOTE_SMTP_SMARTHOST_TLS_VERIFY_HOSTS = !*

in it?

Could be. Will exim4.conf.localmacros apply to non-split exim config?

It will *only* apply to a non-split config.

Agreed. There's nothing wrong in trying
REMOTE_SMTP_SMARTHOST_TLS_VERIFY_HOSTS = !* as far as I'm concerned.

What I just did :
# nano /etc/exim4/exim4.conf.template
I commented out this :
#.ifndef REMOTE_SMTP_SMARTHOST_TLS_VERIFY_HOSTS
#  REMOTE_SMTP_SMARTHOST_TLS_VERIFY_HOSTS = *
#.endif

Then
# update-exim4.conf
# systemctl restart exim4.service
# rm /var/spool/exim4/db/retry*
# rm /var/spool/exim4/db/wait-remote_smtp_smarthost*
# tail -f /var/log/exim4/mainlog
Then in a user terminal :
$ mail -s test my.n...@provider.fr

The log :
2021-08-01 00:33:34 1m9xXy-00035e-PB <= my.n...@provider.fr U=rudu 
P=local S=463
2021-08-01 00:33:35 1m9xXy-00035e-PB H=smtpauth.provider.fr 
[185.204.xxx.xxx]: SMTP error from remote mail server after AUTH PLAIN 
: 454 4.7.0 
Temporary authentication failure: Connection lost to authentication server
2021-08-01 00:33:35 1m9xXy-00035e-PB == my.n...@provider.fr R=smarthost 
T=remote_smtp_smarthost defer (0) H=smtpauth.provider.fr 
[185.204.xxx.xxx]: SMTP error from remote mail server after AUTH PLAIN 
: 454 4.7.0 
Temporary authentication failure: Connection lost to authentication server


Sorry to be so lost, but really I can't figure out what all this means ...
But that's sort of new kind of mainlog from exim4 ...

Rings some bell ?

Thanks in advance
Rudu

Re: burn iso to usb

[Stefan Monnier]

>> > cp /path/to/file.iso /dev/sdX
>> dd if=whatever.iso of=/dev/sdX  
> It's up to taste.

Not at all.  The only right answer is:

pv -parIe /dev/sdX

Anyone who says otherwise is trying to trick you,


Stefan

Re: [SOLVED] Radeon 6800 XT: 100% GPU core usage & 74 Watts when idle

[piorunz]

Debian 11 patched kernel is out!
That will fix everyone who have been affected and they didn't switched 
to older kernel or compiled their own.



linux-signed-amd64 (5.10.46+3) unstable; urgency=medium

  * Sign kernel from linux 5.10.46-3

  * [armhf] Add mdio-aspeed to nic-modules.
Thanks to Joel Stanley  (Closes: #991262)
  * Revert "drm/amdgpu/gfx9: fix the doorbell missing when in CGPG issue."
(Closes: #990312)
  * Revert "drm/amdgpu/gfx10: enlarge CP_MEC_DOORBELL_RANGE_UPPER to 
cover full

doorbell." (Closes: #990312)
  * Input: joydev - prevent use of not validated data in JSIOCSBTNMAP ioctl
(CVE-2021-3612)
  * sctp: validate from_addr_param return (CVE-2021-3655)
  * sctp: add size validation when walking chunks (CVE-2021-3655)
  * [s390x] sclp_vt220: fix console name to match device (Closes: #961056)
  * block: return the correct bvec when checking for gaps
  * sctp: fix return value check in __sctp_rcv_asconf_lookup

 -- Salvatore Bonaccorso   Wed, 28 Jul 2021 07:55:40 
+0200


On 24/07/2021 04:32, piorunz wrote:

On 23/07/2021 23:44, The Wanderer wrote:

https://gitlab.freedesktop.org/drm/amd/-/issues/1632  as being an
upstream(?) bug report which covers it. Not sure how directly applicable
those are, but just in case...


That escalated very quickly :D This bug is responsible for this. And 
patch works.


I compiled my own 5.10 kernel using Debian source, and I patched that 
one line in drivers/gpu/drm/amd/amdgpu/gfx_v10_0.c file. Now I rebooted 
to my custom 5.10 kernel and it works :)


Let's see - before:

$ sensors
(...)
amdgpu-pci-0900
(...)
power1:   74.00 W  (cap = 272.00 W)

gpu-mon (from rickslab-gpu-utils)
┌─┬┐
│Card #   │card0   │
├─┼┤
│Model    │ Navi 21 RX │
│GPU Load %   │99  │
│Mem Load %   │0   │
│VRAM Usage % │4.839   │
│GTT Usage %  │0.802   │
│Power (W)    │75.0    │
│Power Cap (W)│272.0   │
│Energy (kWh) │0.0 │
│T (C)    │53.0    │
│VddGFX (mV)  │1143    │
│Fan Spd (%)  │0   │
│Sclk (MHz)   │2470    │
│Sclk Pstate  │1   │
│Mclk (MHz)   │1000    │
│Mclk Pstate  │3   │
│Perf Mode    │0-BOOTUP_DEFAULT    │
└─┴┘

And after:

$ sensors
(...)
amdgpu-pci-0900
(...)
power1:   34.00 W  (cap = 272.00 W)

┌─┬┐
│Card #   │card0   │
├─┼┤
│Model    │ Navi 21 RX │
│GPU Load %   │0   │
│Mem Load %   │0   │
│VRAM Usage % │6.109   │
│GTT Usage %  │1.147   │
│Power (W)    │35.0    │
│Power Cap (W)│272.0   │
│Energy (kWh) │0.004   │
│T (C)    │54.0    │
│VddGFX (mV)  │856 │
│Fan Spd (%)  │0   │
│Sclk (MHz)   │500 │
│Sclk Pstate  │0   │
│Mclk (MHz)   │1000    │
│Mclk Pstate  │3   │
│Perf Mode    │0-BOOTUP_DEFAULT    │
└─┴┘

0% GPU core use, 0% memory use, core clock is 500 MHz instead of maxed 
out at 2470 Mhz. Success!

Power usage is on par with Windows.
However, I still have 34W even if I disconnect second monitor. On 
Windows, with one monitor only power goes down to 10W and core is 10 
MHz. But my default setup it 2 monitors so I don't worry too much anyway :)





--

With kindest regards, piorunz.

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

Re: New video card, how to deal?

[Anssi Saari]

Felix Miata  writes:

>   Modesetting DIX driver
>
> (Device Independent X driver)
>
> as opposed to Device Dependent X drivers Amdgpu, Intel, Nouveau & Radeon.

OK. Well, the man page says it's a driver for KMS devices? A raw Nvidia
chip with no supporting kernel driver isn't going to present itself as
KMS. So as far as I understand it, this can't work.

I did try the modesetting driver it and it works with the builtin Intel
I have. I got into running a compositor with my wm to get vsync support
so now enjoying some transparency effects. Video decode is maybe a bit
faster than with the Intel driver.

Anyways, I found out there's an unblock request for nvidia-driver so
that the version in sid (460.91) will be migrated. So it might get into
Bullseye for release and presumably Buster backports soon after that.

Re: burn iso to usb

[Thomas Schmitt]

Hi,

was
  https://www.debian.org/CD/faq/#write-usb
already mentioned in this thread ?
Besides the already mentioned Unix methods it gives advise for users of
MS-Windows, to which i would add program Rufus and its "dd" mode.


Greg Wooledge wrote:
> > If you're going to use dd for this, be sure to increase the block size
> > from the default 512 bytes to something more appropriate in this century.

to...@tuxteam.de wrote:
> Absolutely. I actually run some tests from time to time, and the
> general pattern is a very flat maximum somewhere beyond 64 and
> below 1G. I tend to use 1M, because it's easy to memorise :)

For the finer operations with ISO images i prefer bs=2048, because that
is the natural granularity of ISO 9660 filesystems.


Stefan Monnier wrote:
> pv -parIe /dev/sdX

cat(1) on steroids :))


Have a nice day :)

Thomas

Re: burn iso to usb

[tomas]

On Sat, Jul 31, 2021 at 02:34:14PM -0400, Stefan Monnier wrote:
> >> > cp /path/to/file.iso /dev/sdX
> >> dd if=whatever.iso of=/dev/sdX  
> > It's up to taste.
> 
> Not at all.  The only right answer is:
> 
> pv -parIe /dev/sdX

I had to look /that/ up, and I consider myself a command-line junkie.

Thanks for this one
 - t


signature.asc
Description: Digital signature

Re (2): Persistent names for audio devices.

[peter]

From: Reco 
Date: Fri, 30 Jul 2021 19:37:49 +0300
> Aha. So, will this work?
> aplay -d dmix:CARD=Set,DEV=0 /usr/share/sounds/alsa/Noise.wav

peter@joule:/home/peter$ aplay -d dmix:CARD=Set,DEV=0 
/usr/share/sounds/alsa/Noise.wav
aplay: main:653: invalid duration argument 'dmix:CARD=Set,DEV=0'

peter@joule:/home/peter$ aplay -D dmix:CARD=Set,DEV=0 
/usr/share/sounds/alsa/Noise.wav
Playing WAVE '/usr/share/sounds/alsa/Noise.wav' : Signed 16 bit Little Endian, 
Rate 48000 Hz, Mono
aplay: set_params:1345: Channels count non available

peter@joule:/home/peter$ aplay -D dmix:CARD=Set,DEV=0 -c 1 
/usr/share/sounds/alsa/Noise.wav
Playing WAVE '/usr/share/sounds/alsa/Noise.wav' : Signed 16 bit Little Endian, 
Rate 48000 Hz, Mono
aplay: set_params:1345: Channels count non available

No sound.  Channels (or channels) has me stumped for now.

> Or this:
> aplay -D plughw:CARD=Set,DEV=0 /usr/share/sounds/alsa/Noise.wav

Gives the noise.  Good.  I guess hw = hardware.  No explanation of 
plughw in the aplay manual but google found a few remarks. 

Conclusion for users who want sound and don't care about channels: try plughw.
 
> And likewise:
> aplay -D dmix:CARD=U0x46d0x807,DEV=0 /usr/share/sounds/alsa/noise.wav
> aplay -D plughw:CARD=U0x46d0x807,DEV=0 /usr/share/sounds/alsa/noise.wav

peter@joule:/home/peter$ aplay -D dmix:CARD=U0x46d0x807,DEV=0 
/usr/share/sounds/alsa/noise.wav
ALSA lib pcm_dmix.c:1108:(snd_pcm_dmix_open) unable to open slave
aplay: main:828: audio open error: No such file or directory

peter@joule:/home/peter$ aplay -D plughw:CARD=U0x46d0x807,DEV=0 
/usr/share/sounds/alsa/noise.wav
aplay: main:828: audio open error: No such file or directory

main:828?  What is that?

> I'm unsure what should "usbstream:CARD=Set" do, but try it as well.

peter@joule:/home/peter$ aplay -D usbstream:CARD=Set 
/usr/share/sounds/alsa/Noise.wav
ALSA lib pcm_usb_stream.c:508:(_snd_pcm_usb_stream_open) Unknown field hint
aplay: main:828: audio open error: Invalid argument

These three give noise.

peter@joule:/home/peter$ aplay -D default:CARD=ICH5 
/usr/share/sounds/alsa/Noise.wav
Playing WAVE '/usr/share/sounds/alsa/Noise.wav' : Signed 16 bit Little Endian, 
Rate 48000 Hz, Mono

peter@joule:/home/peter$ aplay -D sysdefault:CARD=ICH5 
/usr/share/sounds/alsa/Noise.wav
Playing WAVE '/usr/share/sounds/alsa/Noise.wav' : Signed 16 bit Little Endian, 
Rate 48000 Hz, Mono

peter@joule:/home/peter$ aplay -D surround21:CARD=ICH5,DEV=0 
/usr/share/sounds/alsa/Noise.wav
Playing WAVE '/usr/share/sounds/alsa/Noise.wav' : Signed 16 bit Little Endian, 
Rate 48000 Hz, Mono

peter@joule:/home/peter$ aplay -D front:CARD=ICH5,DEV=0 
/usr/share/sounds/alsa/Noise.wav
Playing WAVE '/usr/share/sounds/alsa/Noise.wav' : Signed 16 bit Little Endian, 
Rate 48000 Hz, Mono

The "front" device gives silence.  A cable inside the box is not 
connected to the system board?  Will check when there is time.

Try a voice message.

peter@joule:/home/peter$ aplay -D plughw:CARD=ICH5,DEV=0 m94.WAV
aplay: test_wavefile:1054: can't play WAVE-file format 0x0031 which is not PCM 
or FLOAT encoded

So try play.  It lacks the -D parameter.  Two commands required.  =8~(

peter@joule:/home/peter$ set AUDIODEV=plughw:CARD=ICH5,DEV=0; play m94.WAV
play WARN alsa: can't encode 0-bit Unknown or not applicable

In spite of the warning, sound is produced.  Good!  Might have a 
reliable way to hear voice messages.

CONCLUSIONS

Audio messages can be interpreted.  Eg.,
set AUDIODEV=plughw:CARD=ICH5,DEV=0; play m94.WAV

"aplay -L" reported approximately 61 devices.  A few hours of trial 
and error (and note writing) got sound from four. Terrible odds.  
(Computing is so much more productive when based upon reason rather 
than guesswork.)

The best alsa documentation I've found in debian.org is 
https://wiki.debian.org/ALSA .  In my view, the first sentence should 
direct the reader to learn basics at 
https://alsa-project.org/wiki/Main_Page . Even so crucial gaps are 
obvious.  What exactly is a channel?  A reader should be wary of any 
document containing undefined terms.

Thanks for the help,   ... P.

-- 
48.7693 N 123.3053 W
tel: +1 604 670 0140

Re: burn iso to usb

[tomas]

On Sat, Jul 31, 2021 at 01:34:31PM -0400, Greg Wooledge wrote:
> On Sat, Jul 31, 2021 at 07:30:42PM +0200, to...@tuxteam.de wrote:
> > On Sat, Jul 31, 2021 at 06:42:50PM +0200, Hans wrote:
> > > Am Samstag, 31. Juli 2021, 14:05:59 CEST schrieb Nicolas George:
> > > > Gunnar Gervin (12021-07-31):
> > > 
> > > > Just:
> > > > 
> > > > cp /path/to/file.iso /dev/sdX
> > > > 
> > > 
> > > Hi,
> > > 
> > > isn't it just:
> > > 
> > > dd if=whatever.iso of=/dev/sdX  
> > 
> > It's up to taste. Some get worked up one way or the other.
> > This discussion comes around cyclically :)
> > 
> > Personally, I settled on dd, mainly because oflag=sync and
> > status=progress. But I'm OK with others using copy, cat or
> > whatever :)
> 
> If you're going to use dd for this, be sure to increase the block size
> from the default 512 bytes to something more appropriate in this century.

Absolutely. I actually run some tests from time to time, and the
general pattern is a very flat maximum somewhere beyond 64 and
below 1G. I tend to use 1M, because it's easy to memorise :)

Cheers
 - t


signature.asc
Description: Digital signature

Re: burn iso to usb

[Greg Wooledge]

On Sat, Jul 31, 2021 at 07:30:42PM +0200, to...@tuxteam.de wrote:
> On Sat, Jul 31, 2021 at 06:42:50PM +0200, Hans wrote:
> > Am Samstag, 31. Juli 2021, 14:05:59 CEST schrieb Nicolas George:
> > > Gunnar Gervin (12021-07-31):
> > 
> > > Just:
> > > 
> > > cp /path/to/file.iso /dev/sdX
> > > 
> > 
> > Hi,
> > 
> > isn't it just:
> > 
> > dd if=whatever.iso of=/dev/sdX  
> 
> It's up to taste. Some get worked up one way or the other.
> This discussion comes around cyclically :)
> 
> Personally, I settled on dd, mainly because oflag=sync and
> status=progress. But I'm OK with others using copy, cat or
> whatever :)

If you're going to use dd for this, be sure to increase the block size
from the default 512 bytes to something more appropriate in this century.

Re: burn iso to usb

[tomas]

On Sat, Jul 31, 2021 at 06:42:50PM +0200, Hans wrote:
> Am Samstag, 31. Juli 2021, 14:05:59 CEST schrieb Nicolas George:
> > Gunnar Gervin (12021-07-31):
> 
> > Just:
> > 
> > cp /path/to/file.iso /dev/sdX
> > 
> 
> Hi,
> 
> isn't it just:
> 
> dd if=whatever.iso of=/dev/sdX  

It's up to taste. Some get worked up one way or the other.
This discussion comes around cyclically :)

Personally, I settled on dd, mainly because oflag=sync and
status=progress. But I'm OK with others using copy, cat or
whatever :)

Cheers
 - t


signature.asc
Description: Digital signature

Re: what binds to port

[Brian]

On Sat 31 Jul 2021 at 17:17:29 +0100, mick crane wrote:

> On 2021-07-31 16:32, Brian wrote:
> 
> >   grep scanner /etc/groups
> >   cat /etc/default/saned
> > 
> I keep thinking it should be groups and not group as well.

An embarassing typo :).

> me and saned are in scanner group
> /etc/default/saned
> RUN_AS_USER=saned

You do not need to be in the scanner group. This requirement disappeared
years ago but it still gets repeated (ad nauseam). See

  https://wiki.debian.org/Scanner#perms

> > > How to find which is the scanner in /dev if it is supposed to be
> > > there?
> > > Xsane works fine.
> > 
> > I thought it was /dev/sg2.
> I said I thought it might be sg2 and wondered how to find out.

Scanners are treated as SCSI devices and therefore come under /dev/sg*.
Look for the + and use getfacl.

As a really naff method, move the device file out of the way and see
whether you can scan.

-- 
Brian.

Re: burn iso to usb

[Nicolas George]

Hans (12021-07-31):
> isn't it just:
> 
> dd if=whatever.iso of=/dev/sdX  

No. cp is more efficient by default, and this case does not need the
fine control offered by dd.

Regards,

-- 
  Nicolas George


signature.asc
Description: PGP signature

Re: burn iso to usb

[Hans]

Am Samstag, 31. Juli 2021, 14:05:59 CEST schrieb Nicolas George:
> Gunnar Gervin (12021-07-31):

> Just:
> 
> cp /path/to/file.iso /dev/sdX
> 

Hi,

isn't it just:

dd if=whatever.iso of=/dev/sdX  

Best

Hans



signature.asc
Description: This is a digitally signed message part.

Re: what binds to port

[Brian]

On Sat 31 Jul 2021 at 16:57:53 +0100, mick crane wrote:

> On 2021-07-31 14:37, mick crane wrote:
> when I say Xsane works fine.
> All I've deleted as far as I know are the .conf files for scanners I don't
> have.
> 
> In /etc/sane.d/dll.conf
> I removed all scanner names except
> net
> fujitsu
> #escl

That's OK.
 
> running Xsane I get to select
> fujitsu or net:localhost.. both of which work

I'd expect this too.

> but if I comment out fujitsu Xsane says "no devices available"
> /etc/sane.d/net.conf
> connect_timeout = 3
> localhost
> 
> Which I'm not understanding.

the net backend is for accessing another backend, either remotely or
on localhost. If you comment out fujitsu on localhost, there isn't
any suitable backend on localhost to contact and use the scanner.

-- 
Brian.

Re: what binds to port

[mick crane]

On 2021-07-31 16:32, Brian wrote:


  grep scanner /etc/groups
  cat /etc/default/saned


I keep thinking it should be groups and not group as well.
me and saned are in scanner group
/etc/default/saned
RUN_AS_USER=saned

How to find which is the scanner in /dev if it is supposed to be 
there?

Xsane works fine.


I thought it was /dev/sg2.

I said I thought it might be sg2 and wondered how to find out.
mick
--
Key ID4BFEBB31

Re: what binds to port

[mick crane]

On 2021-07-31 14:37, mick crane wrote:
when I say Xsane works fine.
All I've deleted as far as I know are the .conf files for scanners I 
don't have.


In /etc/sane.d/dll.conf
I removed all scanner names except
net
fujitsu
#escl

running Xsane I get to select
fujitsu or net:localhost.. both of which work
but if I comment out fujitsu Xsane says "no devices available"
/etc/sane.d/net.conf
connect_timeout = 3
localhost

Which I'm not understanding.

mick
--
Key ID4BFEBB31

Re: what binds to port

[Brian]

On Sat 31 Jul 2021 at 14:37:49 +0100, mick crane wrote:

> On 2021-07-31 13:18, Brian wrote:
> > On Sat 31 Jul 2021 at 10:20:43 +0100, mick crane wrote:
> > 
> > > On 2021-07-30 18:30, Brian wrote:
> > > <...>
> > > >   https://wiki.debian.org/SaneOverNetwork#escl
> > > looking at those informative pages I think /dev/sg2 is the scanner
> > > should that not be in group scanner ?
> > > 
> > > root@pumpkin:/# ls -l /dev |grep cdrom
> > > lrwxrwxrwx  1 root root   3 Jul 30 17:36 cdrom -> sr0
> > > crw-rw+ 1 root cdrom21,   2 Jul 30 17:36 sg2
> > > brw-rw+ 1 root cdrom11,   0 Jul 30 17:36 sr0
> > 
> > I don't see why it should be. I too have
> > 
> >   crw-rw+ 1 root cdrom21,   2 Jul 30 17:36 sg1
> > 
> > on bullseye. Note the +. Its an ACL. systemd, and libpam-systemd have
> > taken care of the correct permissions on the scanner device file. Try
> > 
> >   getfacl /dev/sg2
> > 
> > (Did you ever say in this thread what the printer/scanner is?)
> 
> I thought it was in there, it's fujitsu fi-5750c

Thanks. The device appears to date from about 2007. I am surprised
that SANE's escl backend detects it and that scanning with

  xsane "escl:fi-5750Cdj:107245"

is possible. (Just a comment and nothing to do with your issues).

> The scanbd.conf says
> user saned
> group scanner

It is the saned user that has to be in the scanner group, not your
user.

  grep scanner /etc/groups
  cat /etc/default/saned

> I'm wondering if this is why I'm having difficulty saving scans anywhere
> other than /tmp
> and getting permission denied writing to a file with a script both in
> /etc/scanbd/scripts called from scanbd.conf

Probably not.

> How to find which is the scanner in /dev if it is supposed to be there?
> Xsane works fine.

I thought it was /dev/sg2.

-- 
Brian.

Re: exim4 as a smarthost with TLS

[Reco]

On Sat, Jul 31, 2021 at 04:03:43PM +0200, Sven Hartge wrote:
> Reco  wrote:
> > On Sat, Jul 31, 2021 at 02:45:34PM +0200, Sven Hartge wrote:
> >> Reco  wrote:
> >> 
> >> > Seems straightforward enough.
> >> > Edit /etc/exim4/exim4.conf.template, you'll need to comment out a block
> >> > similar to this:
> >> 
> >> >  .ifndef REMOTE_SMTP_SMARTHOST_TLS_VERIFY_HOSTS
> >> >    REMOTE_SMTP_SMARTHOST_TLS_VERIFY_HOSTS = *
> >> >  .endif
> >> 
> >> > Do not touch second block (starting with .ifdef
> >> > REMOTE_SMTP_SMARTHOST_TLS_VERIFY_HOSTS).
> >> 
> >> > Execute /usr/sbin/update-exim4.conf.
> >> > Bounce exim4.
> >> 
> >> > Smarthost certificate verification should be disabled after this.
> >> 
> >> Wouldn't it be easier to just create /etc/exim4/exim4.conf.localmacros
> >> and put 
> >> 
> >>  REMOTE_SMTP_SMARTHOST_TLS_VERIFY_HOSTS = !*
> >> 
> >> in it?
> 
> > Could be. Will exim4.conf.localmacros apply to non-split exim config?
> 
> It will *only* apply to a non-split config.

Agreed. There's nothing wrong in trying
REMOTE_SMTP_SMARTHOST_TLS_VERIFY_HOSTS = !* as far as I'm concerned.

Reco

Re: Mensajes con msmtp

[Josu Lazkano]

El sáb, 31 jul 2021 a las 9:00, Camaleón () escribió:

> El 2021-07-30 a las 23:51 +0200, Josu Lazkano escribió:
>
> > Hola,
> >
> > Estoy probando la aplicación msmtp en Debian.
> >
> > He configurado una cuenta de Outlook de esta forma:
> >
> > $ cat .msmtprc
> > defaults
> > auth on
> > tls on
> > tls_trust_file /etc/ssl/certs/ca-certificates.crt
> > logfile ~/.msmtp.log
> >
> > account outlook
> > host smtp.office365.com
> > port 587
> > from myu...@outlook.com
> > user my...@outlook.com
> > password mypass
> >
> > account default : outlook
> >
> >
> > El problema que tengo es que los correos llegan sin el cuerpo:
> >
> > echo "Mensaje de prueba" | msmtp micor...@gmail.com
> >
> >
> > ¿Alguien tiene experiencia con msmtp?
>
> Normalmente, cuando dialogas con un servidor de correo «a lo bruto»,
> tienes que mantener el protocolo, lo que traducido al cristiano quiere
> decir que es posible que se queje por el formato (p. ej., el punto «.»
> al final del mensaje, para indicarle al servidor que ya has finalizado
> el texto):
>
> echo "Mensaje de prueba." | msmtp micor...@gmail.com
>^
>
> En cualquier caso, para ver qué hace, activa la depuración (echo... |
> msmtp
> --debug ...).
>
>
> Saludos,
>
> --
> Camaleón
>
>
Muchas gracias!

Si, era un tema de final de lineas, asi funciona:

echo -e "Subject: Asunto\r\n\r\nTexto del mensaje" | msmtp
micor...@gmail.com

Un saludo.

-- 
Josu Lazkano

Re: exim4 as a smarthost with TLS

[Sven Hartge]

Reco  wrote:
> On Sat, Jul 31, 2021 at 02:45:34PM +0200, Sven Hartge wrote:
>> Reco  wrote:
>> 
>> > Seems straightforward enough.
>> > Edit /etc/exim4/exim4.conf.template, you'll need to comment out a block
>> > similar to this:
>> 
>> >  .ifndef REMOTE_SMTP_SMARTHOST_TLS_VERIFY_HOSTS
>> >    REMOTE_SMTP_SMARTHOST_TLS_VERIFY_HOSTS = *
>> >  .endif
>> 
>> > Do not touch second block (starting with .ifdef
>> > REMOTE_SMTP_SMARTHOST_TLS_VERIFY_HOSTS).
>> 
>> > Execute /usr/sbin/update-exim4.conf.
>> > Bounce exim4.
>> 
>> > Smarthost certificate verification should be disabled after this.
>> 
>> Wouldn't it be easier to just create /etc/exim4/exim4.conf.localmacros
>> and put 
>> 
>>  REMOTE_SMTP_SMARTHOST_TLS_VERIFY_HOSTS = !*
>> 
>> in it?

> Could be. Will exim4.conf.localmacros apply to non-split exim config?

It will *only* apply to a non-split config.

For the split config you need to create a file like
/etc/exim4/conf.d/main/000_localconfig instead.

Documentation says:

,[ /usr/share/doc/exim4-base/README.Debian.gz
|For split configuration, you can drop the local configuration file
|anywhere in /etc/exim4/conf.d/main. Just make sure it gets read
|before the macro is first used. 000_localmacros is a possible name,
|guaranteeing first order. For a non-split configuration,
|/etc/exim4/exim4.conf.localmacros gets read before
|/etc/exim4/exim4.conf.template.
`

S°

-- 
Sigmentation fault. Core dumped.

Re: what binds to port

[mick crane]

On 2021-07-31 13:18, Brian wrote:

On Sat 31 Jul 2021 at 10:20:43 +0100, mick crane wrote:


On 2021-07-30 18:30, Brian wrote:
<...>
>   https://wiki.debian.org/SaneOverNetwork#escl
looking at those informative pages I think /dev/sg2 is the scanner
should that not be in group scanner ?

root@pumpkin:/# ls -l /dev |grep cdrom
lrwxrwxrwx  1 root root   3 Jul 30 17:36 cdrom -> sr0
crw-rw+ 1 root cdrom21,   2 Jul 30 17:36 sg2
brw-rw+ 1 root cdrom11,   0 Jul 30 17:36 sr0


I don't see why it should be. I too have

  crw-rw+ 1 root cdrom21,   2 Jul 30 17:36 sg1

on bullseye. Note the +. Its an ACL. systemd, and libpam-systemd have
taken care of the correct permissions on the scanner device file. Try

  getfacl /dev/sg2

(Did you ever say in this thread what the printer/scanner is?)


I thought it was in there, it's fujitsu fi-5750c
The scanbd.conf says
user saned
group scanner

I'm wondering if this is why I'm having difficulty saving scans anywhere 
other than /tmp
and getting permission denied writing to a file with a script both in 
/etc/scanbd/scripts called from scanbd.conf

How to find which is the scanner in /dev if it is supposed to be there?
Xsane works fine.

mick

--
Key ID4BFEBB31

Re: exim4 as a smarthost with TLS

[Reco]

On Sat, Jul 31, 2021 at 02:45:34PM +0200, Sven Hartge wrote:
> Reco  wrote:
> 
> > Seems straightforward enough.
> > Edit /etc/exim4/exim4.conf.template, you'll need to comment out a block
> > similar to this:
> 
> >  .ifndef REMOTE_SMTP_SMARTHOST_TLS_VERIFY_HOSTS
> >    REMOTE_SMTP_SMARTHOST_TLS_VERIFY_HOSTS = *
> >  .endif
> 
> > Do not touch second block (starting with .ifdef
> > REMOTE_SMTP_SMARTHOST_TLS_VERIFY_HOSTS).
> 
> > Execute /usr/sbin/update-exim4.conf.
> > Bounce exim4.
> 
> > Smarthost certificate verification should be disabled after this.
> 
> Wouldn't it be easier to just create /etc/exim4/exim4.conf.localmacros
> and put 
> 
>  REMOTE_SMTP_SMARTHOST_TLS_VERIFY_HOSTS = !*
> 
> in it?

Could be. Will exim4.conf.localmacros apply to non-split exim config?

Reco

gnome-shell freezing

[Sylvain Archenault]

Hi

Recently, my gnome session has been freezing a bit randomly - but it
seems to happen quite often when i open a link in thunderbird or use the
app "grisbi"

I'm running SID with the last kernel: 5.10.46-3 and recent nvidia
driver: 460.91.03-1 or 470.57.02-1

I'm struggling to find something interesting in any log file though.
When the freeze happens, the mouse is still moving, I can go to a tty
and sometimes I'm able to recover by restarting gdm.

Do you have any idea what I could do / look at to get more information
about the "freeze"?

Thank you
Sylvain

Re: exim4 as a smarthost with TLS

[Sven Hartge]

Reco  wrote:

> Seems straightforward enough.
> Edit /etc/exim4/exim4.conf.template, you'll need to comment out a block
> similar to this:

>  .ifndef REMOTE_SMTP_SMARTHOST_TLS_VERIFY_HOSTS
>    REMOTE_SMTP_SMARTHOST_TLS_VERIFY_HOSTS = *
>  .endif

> Do not touch second block (starting with .ifdef
> REMOTE_SMTP_SMARTHOST_TLS_VERIFY_HOSTS).

> Execute /usr/sbin/update-exim4.conf.
> Bounce exim4.

> Smarthost certificate verification should be disabled after this.

Wouldn't it be easier to just create /etc/exim4/exim4.conf.localmacros
and put 

 REMOTE_SMTP_SMARTHOST_TLS_VERIFY_HOSTS = !*

in it? That way you don't need to edit the template (causing a merge
prompt on the next exim4 update).

This is also the way the README.Debian suggest doing this.

S°

-- 
Sigmentation fault. Core dumped.

Re: burn iso to usb

[tomas]

On Sat, Jul 31, 2021 at 02:05:59PM +0200, Nicolas George wrote:
> Gunnar Gervin (12021-07-31):
> > How mount iso to usb in terminal? (Debian 10.10 i386 32 bit)
> 
> Mount? or "burn"? I'll assume the later.
> 
> Just:
> 
> cp /path/to/file.iso /dev/sdX

...but make sure /dev/sdX is not mounted. Otherwise hilarity ensues.

Cheers
 - t


signature.asc
Description: Digital signature

Re: what binds to port

[Brian]

On Sat 31 Jul 2021 at 10:20:43 +0100, mick crane wrote:

> On 2021-07-30 18:30, Brian wrote:
> <...>
> >   https://wiki.debian.org/SaneOverNetwork#escl
> looking at those informative pages I think /dev/sg2 is the scanner
> should that not be in group scanner ?
> 
> root@pumpkin:/# ls -l /dev |grep cdrom
> lrwxrwxrwx  1 root root   3 Jul 30 17:36 cdrom -> sr0
> crw-rw+ 1 root cdrom21,   2 Jul 30 17:36 sg2
> brw-rw+ 1 root cdrom11,   0 Jul 30 17:36 sr0

I don't see why it should be. I too have

  crw-rw+ 1 root cdrom21,   2 Jul 30 17:36 sg1

on bullseye. Note the +. Its an ACL. systemd, and libpam-systemd have
taken care of the correct permissions on the scanner device file. Try

  getfacl /dev/sg2

(Did you ever say in this thread what the printer/scanner is?)

-- 
Brian.

Re: exim4 as a smarthost with TLS

[Reco]

On Sat, Jul 31, 2021 at 01:03:18PM +0200, rudu wrote:
> Le 31/07/2021 à 08:25, Reco a écrit :
> > On Sat, Jul 31, 2021 at 09:21:02AM +0300, Reco wrote:
> > > > > grep split /etc/exim4/update-exim4.conf.conf
> > > > # grep split /etc/exim4/update-exim4.conf.conf
> > > > dc_use_split_config='false'
> > > And this part shows that to change this you have to edit files at
> > > /etc/exim4/conf.d.
> > Damn. I need to think more before I send e-mails.
> > Of course this part shows that you lack a split exim4 config, so we'll
> > have to edit /etc/exim4/exim4.conf.template.
> > 
> > So, in addition to:
> > 
> > grep -R REMOTE_SMTP_SMARTHOST_TLS_VERIFY_HOSTS /etc/exim4/conf.d
> # grep -R REMOTE_SMTP_SMARTHOST_TLS_VERIFY_HOSTS /etc/exim4/conf.d
> /etc/exim4/conf.d/transport/30_exim4-config_remote_smtp_smarthost:.ifdef 
> REMOTE_SMTP_SMARTHOST_TLS_VERIFY_HOSTS
> /etc/exim4/conf.d/transport/30_exim4-config_remote_smtp_smarthost: 
> tls_verify_hosts = REMOTE_SMTP_SMARTHOST_TLS_VERIFY_HOSTS
> /etc/exim4/conf.d/transport/10_exim4-config_transport-macros:.ifndef 
> REMOTE_SMTP_SMARTHOST_TLS_VERIFY_HOSTS
> /etc/exim4/conf.d/transport/10_exim4-config_transport-macros: 
> REMOTE_SMTP_SMARTHOST_TLS_VERIFY_HOSTS = *
> 
> > Please also post this:
> > 
> > grep REMOTE_SMTP_SMARTHOST_TLS_VERIFY_HOSTS /etc/exim4/exim4.conf.template
> # grep REMOTE_SMTP_SMARTHOST_TLS_VERIFY_HOSTS /etc/exim4/exim4.conf.template
> .ifndef REMOTE_SMTP_SMARTHOST_TLS_VERIFY_HOSTS
>   REMOTE_SMTP_SMARTHOST_TLS_VERIFY_HOSTS = *
> .ifdef REMOTE_SMTP_SMARTHOST_TLS_VERIFY_HOSTS
>   tls_verify_hosts = REMOTE_SMTP_SMARTHOST_TLS_VERIFY_HOSTS

Seems straightforward enough.
Edit /etc/exim4/exim4.conf.template, you'll need to comment out a block
similar to this:

 .ifndef REMOTE_SMTP_SMARTHOST_TLS_VERIFY_HOSTS
   REMOTE_SMTP_SMARTHOST_TLS_VERIFY_HOSTS = *
 .endif

Do not touch second block (starting with .ifdef
REMOTE_SMTP_SMARTHOST_TLS_VERIFY_HOSTS).

Execute /usr/sbin/update-exim4.conf.
Bounce exim4.

Smarthost certificate verification should be disabled after this.


If you ever need to reenable it - just uncomment the ifndef block, and
execute /usr/sbin/update-exim4.conf once more.

Reco

Re: burn iso to usb

[Andrew M.A. Cater]

On Sat, Jul 31, 2021 at 01:59:48PM +0200, Gunnar Gervin wrote:
> How mount iso to usb in terminal? (Debian 10.10 i386 32 bit)
> 
> Multiwriter does not work;
> Debian Mate answers in the red: "Cannot find program".
> 
> Terminal is also difficult; "cannot find or open file" etc, but at least
> responds a little
> 
> geg

Gunnar,

As suggested _don't_ use just the i386 medium - do try the multiarch .iso
found at 
https://cdimage.debian.org/debian-cd/current/multi-arch/iso-cd/debian-10.10.0-amd64-i386-netinst.iso

If you plug in the USB flash disk, it should show up somewhere: if you plug
it in and then run the command dmesg as root equivalent, what does the last 
line or so say?

All the very best, as ever,

Andy Cater

Re: burn iso to usb

[Nicolas George]

Gunnar Gervin (12021-07-31):
> How mount iso to usb in terminal? (Debian 10.10 i386 32 bit)

Mount? or "burn"? I'll assume the later.

Just:

cp /path/to/file.iso /dev/sdX

where sdX is the device for your USB drive. You will need to make sure
you have the permissions for the devices; I advise it over using rood
privileges for the cp: you could wipe your install if you get the device
wrong.

But if your goal is to also learn, there is a better way, and one that
lets you keep using the USB drive normally. I have written an old and a
newer tutorial:

http://nsup.org/~george/comp/live_iso_usb/
http://nsup.org/~george/comp/live_iso_usb/grub_hybrid.html

Regards,

-- 
  Nicolas George


signature.asc
Description: PGP signature

burn iso to usb

[Gunnar Gervin]

How mount iso to usb in terminal? (Debian 10.10 i386 32 bit)

Multiwriter does not work;
Debian Mate answers in the red: "Cannot find program".

Terminal is also difficult; "cannot find or open file" etc, but at least
responds a little

geg

Re: what binds to port

[Thomas Schmitt]

Hi,

mick crane wrote:
> looking at those informative pages I think /dev/sg2 is the scanner
> should that not be in group scanner ?
> lrwxrwxrwx  1 root root   3 Jul 30 17:36 cdrom -> sr0
> crw-rw+ 1 root cdrom21,   2 Jul 30 17:36 sg2
> brw-rw+ 1 root cdrom11,   0 Jul 30 17:36 sr0

/dev/sg2 might be the generic SCSI device to which /dev/sr0 is connected.

Each drive operation of sr is performed by the SCSI transaction facility
of sg (reachable from userspace by ioctl(SG_IO)).

If sg2 is an optical drive, then xorriso will accept it as SCSI-MMC drive:

  $ xorriso -no_rc -outdev /dev/sg4 -toc
  ...
  Drive type   : vendor 'HL-DT-ST' product 'BD-RE GGW-H20L' revision 'YL03'
  ...

If it is not an optical drive then the output is rather

  xorriso : FAILURE : Drive address '/dev/sg8' rejected because: not MMC
  and -drive_class 'caution' '/dev'

If you don't have rw-access permission you get in both cases

  libburn : FAILURE : Cannot access '/dev/sg8' as SG_IO CDROM drive


Have a nice day :)

Thomas

Re: exim4 as a smarthost with TLS

[rudu]

Hi Reco,

Le 31/07/2021 à 08:25, Reco a écrit :

On Sat, Jul 31, 2021 at 09:21:02AM +0300, Reco wrote:

grep split /etc/exim4/update-exim4.conf.conf

# grep split /etc/exim4/update-exim4.conf.conf
dc_use_split_config='false'

And this part shows that to change this you have to edit files at
/etc/exim4/conf.d.

Damn. I need to think more before I send e-mails.
Of course this part shows that you lack a split exim4 config, so we'll
have to edit /etc/exim4/exim4.conf.template.

So, in addition to:

grep -R REMOTE_SMTP_SMARTHOST_TLS_VERIFY_HOSTS /etc/exim4/conf.d

# grep -R REMOTE_SMTP_SMARTHOST_TLS_VERIFY_HOSTS /etc/exim4/conf.d
/etc/exim4/conf.d/transport/30_exim4-config_remote_smtp_smarthost:.ifdef 
REMOTE_SMTP_SMARTHOST_TLS_VERIFY_HOSTS
/etc/exim4/conf.d/transport/30_exim4-config_remote_smtp_smarthost: 
tls_verify_hosts = REMOTE_SMTP_SMARTHOST_TLS_VERIFY_HOSTS
/etc/exim4/conf.d/transport/10_exim4-config_transport-macros:.ifndef 
REMOTE_SMTP_SMARTHOST_TLS_VERIFY_HOSTS
/etc/exim4/conf.d/transport/10_exim4-config_transport-macros: 
REMOTE_SMTP_SMARTHOST_TLS_VERIFY_HOSTS = *



Please also post this:

grep REMOTE_SMTP_SMARTHOST_TLS_VERIFY_HOSTS /etc/exim4/exim4.conf.template

# grep REMOTE_SMTP_SMARTHOST_TLS_VERIFY_HOSTS /etc/exim4/exim4.conf.template
.ifndef REMOTE_SMTP_SMARTHOST_TLS_VERIFY_HOSTS
  REMOTE_SMTP_SMARTHOST_TLS_VERIFY_HOSTS = *
.ifdef REMOTE_SMTP_SMARTHOST_TLS_VERIFY_HOSTS
  tls_verify_hosts = REMOTE_SMTP_SMARTHOST_TLS_VERIFY_HOSTS


Thank you
Rudu

Re: what binds to port

[mick crane]

On 2021-07-30 18:30, Brian wrote:
<...>

  https://wiki.debian.org/SaneOverNetwork#escl

looking at those informative pages I think /dev/sg2 is the scanner
should that not be in group scanner ?

root@pumpkin:/# ls -l /dev |grep cdrom
lrwxrwxrwx  1 root root   3 Jul 30 17:36 cdrom -> sr0
crw-rw+ 1 root cdrom21,   2 Jul 30 17:36 sg2
brw-rw+ 1 root cdrom11,   0 Jul 30 17:36 sr0

mick
--
Key ID4BFEBB31

Re: Package: libspeexdsp1 (1.2~rc1.2-1.1)

[Robbi Nespu]

On 7/31/21 6:26 AM, Stuart Naylor wrote:

Package: Package: libspeexdsp1

   Version: (1.2~rc1.2-1.1)

   This version has been outdated for some time and when compiling 
alsa-plugins it causes the them to be excluded from the compile as they 
reference the release 1.2 not the rc


   I have tried several times to inform the maintainer Ron Lee and not 
sure why Debain continues to publish the RC


   Can someone just forward this to who or where ever and just include 
the release which is now several years old?



Checked bugs.d.o and no one send report about it. Since you know better, 
can you send a report? I prepare a template for you here 
https://paste.debian.net/plain/1206140 , just modify per need and send 
to sub...@bugs.debian.org




Stuart

Sent from Mail  for 
Windows 10





--
Robbi Nespu 
D311 B5FF EEE6 0BE8 9C91 FA9E 0C81 FA30 3B3A 80BA
https://robbinespu.gitlab.io | https://mstdn.social/@robbinespu

Re: Mensajes con msmtp

[Camaleón]

El 2021-07-30 a las 23:51 +0200, Josu Lazkano escribió:

> Hola,
> 
> Estoy probando la aplicación msmtp en Debian.
> 
> He configurado una cuenta de Outlook de esta forma:
> 
> $ cat .msmtprc
> defaults
> auth on
> tls on
> tls_trust_file /etc/ssl/certs/ca-certificates.crt
> logfile ~/.msmtp.log
> 
> account outlook
> host smtp.office365.com
> port 587
> from myu...@outlook.com
> user my...@outlook.com
> password mypass
> 
> account default : outlook
> 
> 
> El problema que tengo es que los correos llegan sin el cuerpo:
> 
> echo "Mensaje de prueba" | msmtp micor...@gmail.com
> 
> 
> ¿Alguien tiene experiencia con msmtp?

Normalmente, cuando dialogas con un servidor de correo «a lo bruto», 
tienes que mantener el protocolo, lo que traducido al cristiano quiere 
decir que es posible que se queje por el formato (p. ej., el punto «.»
al final del mensaje, para indicarle al servidor que ya has finalizado
el texto):

echo "Mensaje de prueba." | msmtp micor...@gmail.com
   ^

En cualquier caso, para ver qué hace, activa la depuración (echo... | msmtp 
--debug ...).


Saludos,

-- 
Camaleón 

Re: exim4 as a smarthost with TLS

[Reco]

On Sat, Jul 31, 2021 at 09:21:02AM +0300, Reco wrote:
> > > grep split /etc/exim4/update-exim4.conf.conf
> > # grep split /etc/exim4/update-exim4.conf.conf
> > dc_use_split_config='false'
> 
> And this part shows that to change this you have to edit files at
> /etc/exim4/conf.d.

Damn. I need to think more before I send e-mails.
Of course this part shows that you lack a split exim4 config, so we'll
have to edit /etc/exim4/exim4.conf.template.

So, in addition to:

grep -R REMOTE_SMTP_SMARTHOST_TLS_VERIFY_HOSTS /etc/exim4/conf.d

Please also post this:

grep REMOTE_SMTP_SMARTHOST_TLS_VERIFY_HOSTS /etc/exim4/exim4.conf.template

Reco

Re: exim4 as a smarthost with TLS

[Reco]

Hi.

On Sat, Jul 31, 2021 at 01:08:19AM +0200, rudu wrote:
> Thank you Reco, see below
> 
> Le 30/07/2021 à 18:27, Reco a écrit :
> > On Fri, Jul 30, 2021 at 07:25:34PM +0300, Reco wrote:
> > >   Hi.
> > > 
> > > On Fri, Jul 30, 2021 at 03:35:28PM +0200, rudu wrote:
> > > > Still, a simple :
> > > > $ mail -s test my.n...@provider.fr
> > > > ... ends up to show in # tail -f /var/log/exim4/mainlog :
> > > > 2021-07-30 10:58:09 1m9OLJ-000cAf-Ss <= my.n...@provider.fr U=rudu 
> > > > P=local S=461
> > > > 2021-07-30 10:58:10 1m9OLJ-000cAf-Ss == my.n...@provider.fr R=smarthost 
> > > > T=remote_smtp_smarthost defer (-37) H=smtpauth.provider.fr 
> > > > [185.204.xxx.xxx]: TLS
> > > > session: (certificate verification failed): certificate invalid
> > > Your exim certificate has nothing to do with this.
> > > But your smarthost certificate certainly does.
> > > 
> > > Every time you try to send a mail, your exim checks certificate of
> > > remote MTA, and it does not like what it sees.
> > > 
> > > > So, when I ran the command :
> > > > # bash /usr/share/doc/exim4-base/examples/exim-gencert
> > > > ... did I miss something that should be there ?
> > > It's possible. Please provide an output of:
> > > 
> > > grep -i 'tls_.*verify' /var/lib/exim4/config.autogenerated
> > > 
> > > grep split exim4/update-exim4.conf.conf
> > A typo.
> > 
> > grep -i 'tls_.*verify' /var/lib/exim4/config.autogenerated
> # grep -i 'tls_.*verify' /var/lib/exim4/config.autogenerated
> .ifndef MAIN_TLS_VERIFY_CERTIFICATES
> MAIN_TLS_VERIFY_CERTIFICATES = ${if 
> exists{/etc/ssl/certs/ca-certificates.crt}\
> tls_verify_certificates = MAIN_TLS_VERIFY_CERTIFICATES
> .ifdef MAIN_TLS_VERIFY_HOSTS
> tls_verify_hosts = MAIN_TLS_VERIFY_HOSTS
> .ifdef MAIN_TLS_TRY_VERIFY_HOSTS
> tls_try_verify_hosts = MAIN_TLS_TRY_VERIFY_HOSTS
> .ifndef REMOTE_SMTP_SMARTHOST_TLS_VERIFY_HOSTS
>   REMOTE_SMTP_SMARTHOST_TLS_VERIFY_HOSTS = *
> .ifdef REMOTE_SMTP_SMARTHOST_TLS_VERIFY_CERTIFICATES
>   tls_verify_certificates = REMOTE_SMTP_SMARTHOST_TLS_VERIFY_CERTIFICATES
> .ifdef REMOTE_SMTP_SMARTHOST_TLS_VERIFY_HOSTS
>   tls_verify_hosts = REMOTE_SMTP_SMARTHOST_TLS_VERIFY_HOSTS

This part of exim4 config shows that it has certificate verification
enabled. And it does this for smarthosts too, which corresponds to
REMOTE_SMTP_SMARTHOST_TLS_VERIFY_HOSTS = *.


> > grep split /etc/exim4/update-exim4.conf.conf
> # grep split /etc/exim4/update-exim4.conf.conf
> dc_use_split_config='false'

And this part shows that to change this you have to edit files at
/etc/exim4/conf.d.


The only question left is - which particular macro defines
REMOTE_SMTP_SMARTHOST_TLS_VERIFY_HOSTS, because it certainly does not
happen here (exim4-daemon-heavy, buster, but I don't use "satellite"
configuration).

Therefore,

grep -R REMOTE_SMTP_SMARTHOST_TLS_VERIFY_HOSTS /etc/exim4/conf.d

Reco