Process kill on logout

[Alan Chandler]

I have just upgraded from Jessie to Stretch and my arrangement where I 
logout and then mythtv shuts my computer down and sets a wakeup time 
just before the next recording time has stopped working.  In the past 
when that happens I have set up "screen", and entered an used "sleep 1m 
&& who -u" to find out why its not detecting me as logged out.  I set 
that command running, detach from screen, logout, ensure the minute is 
up, log back in and re-enter my screen session to see what it made of 
things.


That no longer works.  It appears that systemd now kills off all 
processess associated with the user - or rather I found a bug report 
that said that had happened about a year ago as the default had changed. 
That bug report said that /etc/systemd/logind.conf should allow you to 
change that default behaviour by setting KillUserProcesses=no.



Firstly, although commented out, that setting is already showing "no", 
which is supposed to mean that this is the default value anyway.  
Secondly setting it explicitly to "no" doesn't work, screen sessions 
still appear to have been wiped out by the act of logging out.


Can anyone tell me what to do to allow screen sessions to survive logout.




--
Alan Chandler
http://www.chandlerfamily.org.uk

Re: konsole blinking screen with irssi when ssh'd to NetBSD

[Glenn Holmer]

On 06/25/2017 02:34 PM, Darac Marjal wrote:
> On Sun, Jun 25, 2017 at 01:51:01PM -0500, Glenn Holmer wrote:
>> I've got a freeshell.org account, and they're running NetBSD. When I SSH
>> into that account, the terminal looks fine, but when I start irssi, the
>> entire screen blinks on and off about once a second. This is from my
>> Debian Stretch box running KDE, with konsole as terminal and bash as
>> shell.
>>
>> I've got another machine here that runs GNOME (under Fedora); I tried
>> the same thing using gnome-terminal and the screen didn't blink when I
>> started irssi.
>>
>> Can anyone offer some suggestions to solve this?
> 
> It might be as simple as a bad terminal description. What is $TERM set
> to? Try setting it to something different (TERM=xterm irssi -or-
> TERM=vt100 irssi) and see if that fixes things.

Sorry, answer was supposed to go to the list:

Thanks, that worked (SSH to freeshell.org, then "TERM=xterm irssi").

-- 
Glenn Holmer (Linux registered user #16682)
"After the vintage season came the aftermath -- and Cenbe."

Re: Recommended Items Missing From Base Install

[Sven Joachim]

On 2017-06-25 20:54 -0400, James Kruth wrote:

> I’ve been working with minimal Debian installs for a bit and have
> noticed something that seems odd. After installing a very minimal
> system (just base, system utils, and SSH server), the following
> recommended packages are not installed in Debian 9:
>
> firmware-linux-free (recommended by linux-image)
> gnupg-l10n (recommended by gnupg)
> irqbalance (recommended by linux-image)
> libatm1 (recommended by iproute2)
> libcap2-bin (recommended by iputils-ping)
> libgpm2 (recommended by libncurses5 and libncursesw5)
> publicsuffix (recommended by libpsl5)
> uuid-runtime (recommended by libuuid1)
>
> I was surprised to see this as apt (or apt-get) seems to install
> recommended packages by default. It’s not as if this is causing me a
> problem. Mostly I’m just curious if anyone knows why certain
> recommended packages are not installed as part of the base system,
> especially when it seems to be standard policy to install recommended
> packages once the system is installed. Thanks!

I think the answer is that the recommending packages have been installed
by debootstrap which has its own very limited dependency resolver that
ignores Recommends.  Before apt can do its work on the installed system,
the base packages need to be installed somehow, and the tool doing this
is debootstrap.

Cheers,
   Sven

Re: light-locker (was Stretch upgrade from Jessie -- several issues)

[Mike Kupfer]

Ralph Katz wrote:

> While purging xscreensaver removed 2 or 3 packages, installing now would
> bring in a host of packages, for whatever reason.  I don't need a
> screensaver as much as I need the lock.

Take a look at /usr/bin/xflock4.  It's just a script that runs through a
fixed list of lock programs until it finds one that runs successfully.
Maybe you can install one of the other commands that it tries.

mike

Re: Actualización del repositorio trajo errores

[Esteban Monge]

Parece como que estuviera detrás de un proxy... podrias validar la hora del 
sistema operativo. 

On June 25, 2017 7:45:30 PM CST, Miguel Matos  wrote:
>Muy buenas, quise aprovechar en realizar el update masivo luego de que
>ya salió la nueva versión de Debian. Y al hacerlo me arrojó tamaños
>errores, ¡más de uno!
>Acá el resultado por terminal:
>Err:72 http://ftp.cl.debian.org/debian testing/main Sources
>  Writing more data than expected (6984840 > 6984328)
>  Hashes of expected file:
>   - Filesize:6984328 [weak]
>-
>SHA256:a8777e22b39c4cebcc2155e92960e9fda36695653a2237067dbdfb58dbb3d1bf
>   - MD5Sum:73a8a9e421b1c8adb04ea76c892561a3 [weak]
>  Release file created at: Sun, 25 Jun 2017 08:28:51 +
>Descargados 286 kB en 1min 43s (2.774 B/s)
>Leyendo lista de paquetes... Hecho
>W: El repositorio «https://dl.winehq.org/wine-builds/debian stable
>Release» no tiene un fichero de Publicación.
>N: Los datos de un repositorio como este no se pueden autenticar y por
>tanto su uso es potencialmente peligroso.
>N: Vea la página de manual apt-secure(8) para los detalles sobre la
>creación de repositorios y la configuración de usuarios.
>E: Fallo al obtener
>https://dl.winehq.org/wine-builds/debian/dists/stable/main/binary-i386/Packages
> 403  Forbidden
>E: Fallo al obtener
>http://ftp.cl.debian.org/debian/dists/testing/main/source/Sources.xz
>Writing more data than expected (6984840 > 6984328)
>   Hashes of expected file:
>- Filesize:6984328 [weak]
>-
>SHA256:a8777e22b39c4cebcc2155e92960e9fda36695653a2237067dbdfb58dbb3d1bf
>- MD5Sum:73a8a9e421b1c8adb04ea76c892561a3 [weak]
>   Release file created at: Sun, 25 Jun 2017 08:28:51 +
>E: Fallo al obtener
>http://ftp.cl.debian.org/debian/dists/testing/main/binary-i386/Packages.xz
> 404  Not Found
>E: No se han podido descargar algunos archivos de índice, se han
>omitido, o se han utilizado unos antiguos en su lugar.
>
>Mi distribución la he etiquetado como "testing", y acá mi sources.list
>en la actualidad:
>## Repositorio Oficial
>deb http://ftp.cl.debian.org/debian/ testing main contrib non-free
>deb-src http://ftp.cl.debian.org/debian/ testing main contrib non-free
>
>deb http://security.debian.org/ testing/updates main contrib non-free
>deb-src http://security.debian.org/ testing/updates main contrib
>non-free
>
># testing-updates, previously known as 'testing', and previously known
>as 'volatile'
>deb http://ftp.cl.debian.org/debian/ testing-updates main contrib
>non-free
>deb-src http://ftp.cl.debian.org/debian/ testing-updates main contrib
>non-free
>
># testing-actualizaciones-sistema
>deb http://mirrors.kernel.org/debian/ testing-updates main contrib
>non-free
>deb-src http://mirrors.kernel.org/debian/ testing-updates main contrib
>non-free
>
># testing-backports
># deb http://mirrors.kernel.org/debian/ testing-backports main contrib
>non-free
># deb-src http://mirrors.kernel.org/debian/ testing-backports main
>contrib non-free
>
>#
># Aquí se agregan los repositorios de aplicaciones externas a los de
>Debian
>#
>
># deb-multimedia
># apt-get install deb-multimedia-keyring
>deb http://www.deb-multimedia.org/ testing main non-free
>deb-src http://www.deb-multimedia.org/ testing main non-free
>
># Wine Repository
>deb https://dl.winehq.org/wine-builds/debian/ stable main
>
>¿Debo continuar con el apt-get dist-upgrade sin problemas? Aunque
>capaz surgirán problemas por dependencias sin cumplir que estén atadas
>a estos repositorios... ¿O será conveniente primero solucionar esto?
>Voy a indagar con google la primera de las fallas, pero igual les
>escribo para saber si pasaron por lo mismo que yo.
>
>-- 
>
>Ayuda para hacer preguntas inteligentes: http://is.gd/NJIwRz

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Actualización del repositorio trajo errores

[Miguel Matos]

Muy buenas, quise aprovechar en realizar el update masivo luego de que
ya salió la nueva versión de Debian. Y al hacerlo me arrojó tamaños
errores, ¡más de uno!
Acá el resultado por terminal:
Err:72 http://ftp.cl.debian.org/debian testing/main Sources
  Writing more data than expected (6984840 > 6984328)
  Hashes of expected file:
   - Filesize:6984328 [weak]
   - SHA256:a8777e22b39c4cebcc2155e92960e9fda36695653a2237067dbdfb58dbb3d1bf
   - MD5Sum:73a8a9e421b1c8adb04ea76c892561a3 [weak]
  Release file created at: Sun, 25 Jun 2017 08:28:51 +
Descargados 286 kB en 1min 43s (2.774 B/s)
Leyendo lista de paquetes... Hecho
W: El repositorio «https://dl.winehq.org/wine-builds/debian stable
Release» no tiene un fichero de Publicación.
N: Los datos de un repositorio como este no se pueden autenticar y por
tanto su uso es potencialmente peligroso.
N: Vea la página de manual apt-secure(8) para los detalles sobre la
creación de repositorios y la configuración de usuarios.
E: Fallo al obtener
https://dl.winehq.org/wine-builds/debian/dists/stable/main/binary-i386/Packages
 403  Forbidden
E: Fallo al obtener
http://ftp.cl.debian.org/debian/dists/testing/main/source/Sources.xz
Writing more data than expected (6984840 > 6984328)
   Hashes of expected file:
- Filesize:6984328 [weak]
- SHA256:a8777e22b39c4cebcc2155e92960e9fda36695653a2237067dbdfb58dbb3d1bf
- MD5Sum:73a8a9e421b1c8adb04ea76c892561a3 [weak]
   Release file created at: Sun, 25 Jun 2017 08:28:51 +
E: Fallo al obtener
http://ftp.cl.debian.org/debian/dists/testing/main/binary-i386/Packages.xz
 404  Not Found
E: No se han podido descargar algunos archivos de índice, se han
omitido, o se han utilizado unos antiguos en su lugar.

Mi distribución la he etiquetado como "testing", y acá mi sources.list
en la actualidad:
## Repositorio Oficial
deb http://ftp.cl.debian.org/debian/ testing main contrib non-free
deb-src http://ftp.cl.debian.org/debian/ testing main contrib non-free

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

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

# testing-actualizaciones-sistema
deb http://mirrors.kernel.org/debian/ testing-updates main contrib non-free
deb-src http://mirrors.kernel.org/debian/ testing-updates main contrib non-free

# testing-backports
# deb http://mirrors.kernel.org/debian/ testing-backports main contrib non-free
# deb-src http://mirrors.kernel.org/debian/ testing-backports main
contrib non-free

#
# Aquí se agregan los repositorios de aplicaciones externas a los de Debian
#

# deb-multimedia
# apt-get install deb-multimedia-keyring
deb http://www.deb-multimedia.org/ testing main non-free
deb-src http://www.deb-multimedia.org/ testing main non-free

# Wine Repository
deb https://dl.winehq.org/wine-builds/debian/ stable main

¿Debo continuar con el apt-get dist-upgrade sin problemas? Aunque
capaz surgirán problemas por dependencias sin cumplir que estén atadas
a estos repositorios... ¿O será conveniente primero solucionar esto?
Voy a indagar con google la primera de las fallas, pero igual les
escribo para saber si pasaron por lo mismo que yo.

-- 

Ayuda para hacer preguntas inteligentes: http://is.gd/NJIwRz

Re: [WARNING] Intel Skylake/Kaby Lake processors: broken hyper-threading

[Henrique de Moraes Holschuh]

Minor update on the issue:

The check command provided in the advisory to test for hyper-threading
doesn't work: it will always report hyper-theading as enabled.  A better
command is provided below.

Note: this also means the perl script will give some false-positives.
I apologise for the inconvenience.


On Sun, 25 Jun 2017, Henrique de Moraes Holschuh wrote:
> Once you know your processor model name, you can check the two lists
> below:
> 
>   * List of Intel processors code-named "Skylake":
> http://ark.intel.com/products/codename/37572/Skylake
> 
>   * List of Intel processors code-named "Kaby Lake":
> http://ark.intel.com/products/codename/82879/Kaby-Lake
> 
> Some of the processors in these two lists are not affected because they
> lack hyper-threading support.  Run the command below in a command line
> shell (e.g. xterm), and it will output a message if hyper-threading is
> supported/enabled:
> 
>   grep -q '^flags.*[[:space:]]ht[[:space:]]' /proc/cpuinfo && \
>   echo "Hyper-threading is supported"

The above test (using "grep") does not work, and will always report that
hyper-threading is enabled.

Please use the "lscpu" utility from the util-linux package in a command
line shell (e.g.  xterm):

lscpu

If the lscpu output reports: "Thread(s) per core: 2", that means
hyper-threading is enabled and supported.

If the lscpu output reports: "Thread(s) per core: 1", that means
hyper-threading either disabled or not supported.  In this case, the
specific defect mentioned in the advisory will not trigger.

-- 
  Henrique Holschuh

Re: Stretch upgrade from Jessie -- several issues

[Ralph Katz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 06/25/2017 04:22 PM, Floris wrote:
> 
> Op Sun, 25 Jun 2017 19:10:40 +0200 schreef Ralph Katz 
> :
>> 
>>> 3) The sound volume up/down function keys [Fn up/down arrow] no
>>> longer respond (xfce4).  However the screen brightness keys
>>> function normally [Fn left/right arrow].  The mute sound
>>> function key is also ignored [Fn F8].  I can control volume
>>> with the mouse using pavucontrol or gkrellm-volume.
>> 
>> No progress.
> 
> if the keys are recognized by the kernel, then you can remap them
> with an udev hwdb rule.
> 
> Test with evtest if the keys get a scancode and a keycode.
> Something like: type 4 (EV_MSC), code 4 (MSC_SCAN), value 700e0 
> type 1 (EV_KEY), code 29 (KEY_LEFTCTRL), value 1 In this case I
> pressed the Left Ctrl key, which has a value of 700e0
> 
> Create a new rule in /etc/udev/hwdb.d with something like:
> 
> evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn* 
> KEYBOARD_KEY_ed=volumeup KEYBOARD_KEY_ee=volumedown etc...
> 
> use evemu-describe to find your evdev:... line
> 
> also read: 
> https://wiki.archlinux.org/index.php/Map_scancodes_to_keycodes 
> https://wiki.archlinux.org/index.php/Extra_keyboard_keys 
> /lib/udev/hwdb.d/60-keyboard.hwdb for more information and
> examples
> 
> Floris

Thanks Floris!  I will look into this, but I am confounded as to why
on jessie and previous versions, recognizing these sound keys was
automatic.

Ralph


-BEGIN PGP SIGNATURE-
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIzBAEBCgAdFiEEJQZ8vK6BnmDiW8fZyAJ5DhtfJxAFAllQYhEACgkQyAJ5Dhtf
JxDH/w/+MWl/hFM7ZmLjqElEJIrKIDiYwcQM93/DqyP4UwJObt8lGoyTyfDkdOF+
fiEPWw3yd3IDAJ/abMUzyQMiFP/1hDW/Orm8MWCXRS+cBihmibkWJ3VtDglq/8yk
bXTEavSCS8r/EhmHvGlg0XnlKoyC6ZSl3Anb0IsGEkqFRR3H1QektSPeoFIVUyW7
QQdIPOOEZXRujbiIkd1+zRo2vIVpeaLC9sgpj5quktlH4ZU3CT6OUe3xiXPE9c0E
iOGxu2zihw+8VReUhwG2raFLRvRHIl1p02aQHZjZ0i9VaS1usxlZFMDYRVmku7cI
1fIsww9J8e31xAlVLsZkoJE6gJPwYNUAHTPKfojH49mGCa4fXMWnaK4Hk2uy9BNT
hIeXO7mTzzzyQz05HEFDiEH8ydwHbVTLYo5Dgs1V9wRNbr9UPZGKMTHCG+LdaM4z
Je/Z5YM1oVS0gvoh8MBmbOQi9Y/J4yxZSUfcR2CfxKpNs5Q8vfskOnUx3mWgS54J
ZUUnB330OUHsqespCDdKqBi6L3h7HGvM7+eKeQC4GyQj5Qxb94AwVPyk4PkhtFIv
zgF4gnEmKkdDqrjaAyTQA2I4Z7r642Bes74vyYjGKZ57IoThh8g8HFQ7Bypn2U7j
oaItnz2gHGMTI7fY249MyrAyJiQvexKUzWHdEw6bGOdApiPo7Ec=
=YzSP
-END PGP SIGNATURE-

Re: light-locker (was Stretch upgrade from Jessie -- several issues)

[Ralph Katz]

On 06/25/2017 05:18 PM, Mike Kupfer wrote:
> Ralph Katz wrote:
> 
>> Yes!  apt history shows light-locker was installed by the dist-upgrade.
>>  I've just purged xscreensaver and can confirm that the time-out errors
>> in syslog occur on resume from screen blanking.
> 
> Did you also kill the xscreensaver daemon?  You might have been getting
> odd behavior due to xscreensaver and light-locker/lightdm fighting over
> the display.

Yes, apt-get purge killed the daemon as well.

> I don't know enough about X to know whether those timeout errors are
> important.  When I've used light-locker, the display would typically
> blank briefly before showing the lightdm screen.  (That's how
> light-locker works: it starts a lightdm instance, which you "log in" to
> in order to unlock the session.)

Yes, but resuming from blank causes the kernel errors in syslog.

> 
>> Other than pushing out the screen lock time which I've done in xfce
>> settings, or disabling the lock, what do you suggest?  light-locker is a
>> "depends" of task-xfce-desktop so not removable.
> 
> If light-locker running by itself still isn't behaving properly, you
> could disable the daemon via the Xfce session control panel.  Untick the
> box in the list of startup applications, and make sure it's not listed
> in the list of currently running applications.
> 
> That would leave you without a screen lock, but I suppose you could
> reinstall xscreensaver.

While purging xscreensaver removed 2 or 3 packages, installing now would
bring in a host of packages, for whatever reason.  I don't need a
screensaver as much as I need the lock.

Ralph




signature.asc
Description: OpenPGP digital signature

Re: su won't work from a debian live USB install

[Phil Wyett]

On Sun, 2017-06-25 at 19:20 -0400, daniel theobald wrote:
> I installed the Debian 9 from a Debian live amd64 image I downloaded
> today.  Everything works great, but I can't su to apt-get anything
> new.
> 
> theo@debian:~$ su
> Password: 
> su: Authentication failure
> 
> I have reinstalled twice, being super careful to get the password
> right, etc.  But it simply doesn't seem to work on this version. 
> Anyone else seeing this problem?
> 
> Thanks,
> Daniel
> 

Hi,

I have seen this issue too.

I have not had time to look into this issue, but believe it maybe
related to a known issue No. 3 on:

https://cdimage.debian.org/debian-cd/9.0.1-live/amd64/iso-hybrid/

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864955

After the live 9.0.0 ISO failed early in install and now the 'su'
issue. This raises questions about the testing and QA of of the live
ISO images, both pre release and at release time that need to be
discussed and addressed in-order to avoid them in the future.

Regards

Phil

-- 
Playing the game for the games sake.

Web: https://kathenas.org

Twitter: kathenasorg

Instagram: kathenasorg

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

Recommended Items Missing From Base Install

[James Kruth]

Hi,

I’ve been working with minimal Debian installs for a bit and have
noticed something that seems odd. After installing a very minimal
system (just base, system utils, and SSH server), the following
recommended packages are not installed in Debian 9:

firmware-linux-free (recommended by linux-image)
gnupg-l10n (recommended by gnupg)
irqbalance (recommended by linux-image)
libatm1 (recommended by iproute2)
libcap2-bin (recommended by iputils-ping)
libgpm2 (recommended by libncurses5 and libncursesw5)
publicsuffix (recommended by libpsl5)
uuid-runtime (recommended by libuuid1)

I was surprised to see this as apt (or apt-get) seems to install
recommended packages by default. It’s not as if this is causing me a
problem. Mostly I’m just curious if anyone knows why certain
recommended packages are not installed as part of the base system,
especially when it seems to be standard policy to install recommended
packages once the system is installed. Thanks!

- James

Re: off topic! What is the error in this script

[Dominic Knight]

On Sun, 2017-06-25 at 18:30 +0300, Teemu Likonen wrote:
> Dominic Knight [2017-06-25 15:35:46+01] wrote:
> 
> > To convert a series of .flac files to .mp3 files I attempted to use
> > the
> > following line;
> > 
> > > $ find -name "*.flac" -exec bash -c 'ffmpeg -i "{}" -y -acodec
> > 
> > libmp3lame -ab 320k "${0/.flac}.mp3"' {} \;
> 
> The arguments for "bash -c" go like this:
> 
> bash -c '...' name one two three
> 
> And in '...' the arguments are in variables $0 (=name), $1 (=one), $2
> (=two), $3 (=three) etc. So:
> 
> find -name "*.flac" -exec \
> bash -c 'ffmpeg -i file:"$1" -c:a libmp3lame -ab 320k -y
> file:"${1%.flac}.mp3"' \
> foo {} \;
> 
Thanks Teemu that works perfectly some nicely converted radio shows
now, cheers.

> Note the "foo": it is saved to $0 ("shell's name") and and then the
> actual filename is in usual first positional parameter $1. We also
> want
> to have explicitl "file:" protocol with ffmpeg so that any
> "something:"
> prerix in filename is not interpreted as a protocol name. (See "man
> ffmpeg-protocols".)
> 
I never realised ffmpeg was as capable as that - impressive.

> But here's another way without double quoting:
> 
> while read -r -d $'\0' input; do
> ffmpeg -i file:"$input" -c:a libmp3lame -ab 320k \
> -y file:"${input%.flac}.mp3"
> done < <(find . -name '*.flac' -print0)
> 
This however doesn't work, what this snippet does is write the first 20
seconds of one of the .flacs to an mp3 (this is also the endpoint of
the opening jingle and so very short break/space in the track, as
produced by audacity - it may work on individual music tracks - not
tested that yet) and then goes off into CPU wonderland tying the
processors up at 100% until killed.

Cheers for the first one though I think I get what is happening in my
first attempt now, bash -c $0 always returned the same name to ffmpeg
for conversion.

Dom.

Re: su won't work from a debian live USB install

[Jim Ohlstein]

Hello,

On 06/25/2017 07:20 PM, daniel theobald wrote:
I installed the Debian 9 from a Debian live amd64 image I downloaded 
today.  Everything works great, but I can't su to apt-get anything new.


theo@debian:~$ su
Password:
su: Authentication failure

I have reinstalled twice, being super careful to get the password right, 
etc.  But it simply doesn't seem to work on this version.  Anyone else 
seeing this problem?


Assuming sudo is working properly, try resetting the root password:

$ sudo passwd root

--
Jim Ohlstein
Profesional Mailman Hosting
https://mailman-hosting.com

su won't work from a debian live USB install

[daniel theobald]

I installed the Debian 9 from a Debian live amd64 image I downloaded
today.  Everything works great, but I can't su to apt-get anything new.

theo@debian:~$ su
Password:
su: Authentication failure

I have reinstalled twice, being super careful to get the password right,
etc.  But it simply doesn't seem to work on this version.  Anyone else
seeing this problem?

Thanks,
Daniel

Re: Jessie --> Stretch upgrade, apt question

[Mark Fletcher]

On Sun, Jun 25, 2017 at 12:29:27PM -0700, Cousin Stanley wrote:
> Mark Fletcher wrote:
> 
> > 
> > I do wish apt show made it easier to tell 
> > if a package is installed 
> > 
> 
>   $ apt policy some-pkg-name
> 
> which evolved from
> 
>   $ apt-cache policy pkg-name
> 
> 
>   will display installation status
>   of some-pkg-name
> 
Thanks all for the replies. Thanks to your help I have made progress and 
found what dependency issue is causing the problem. Unfortunately I am 
running late for work now so will reply later with more detail on which 
solution helped me with what, for the record.

Thanks again

Mark

light-locker (was Stretch upgrade from Jessie -- several issues)

[Mike Kupfer]

Ralph Katz wrote:

> Yes!  apt history shows light-locker was installed by the dist-upgrade.
>  I've just purged xscreensaver and can confirm that the time-out errors
> in syslog occur on resume from screen blanking.

Did you also kill the xscreensaver daemon?  You might have been getting
odd behavior due to xscreensaver and light-locker/lightdm fighting over
the display.

I don't know enough about X to know whether those timeout errors are
important.  When I've used light-locker, the display would typically
blank briefly before showing the lightdm screen.  (That's how
light-locker works: it starts a lightdm instance, which you "log in" to
in order to unlock the session.)

> Other than pushing out the screen lock time which I've done in xfce
> settings, or disabling the lock, what do you suggest?  light-locker is a
> "depends" of task-xfce-desktop so not removable.

If light-locker running by itself still isn't behaving properly, you
could disable the daemon via the Xfce session control panel.  Untick the
box in the list of startup applications, and make sure it's not listed
in the list of currently running applications.

That would leave you without a screen lock, but I suppose you could
reinstall xscreensaver.

mike

Re: Stretch upgrade from Jessie -- several issues

[Floris]

Op Sun, 25 Jun 2017 19:10:40 +0200 schreef Ralph Katz  
:



3) The sound volume up/down function keys [Fn up/down arrow] no longer
respond (xfce4).  However the screen brightness keys function normally
[Fn left/right arrow].  The mute sound function key is also ignored [Fn
F8].  I can control volume with the mouse using pavucontrol or
gkrellm-volume.


No progress.


if the keys are recognized by the kernel, then you can remap them with an  
udev hwdb rule.


Test with evtest if the keys get a scancode and a keycode. Something like:
type 4 (EV_MSC), code 4 (MSC_SCAN), value 700e0
type 1 (EV_KEY), code 29 (KEY_LEFTCTRL), value 1
In this case I pressed the Left Ctrl key, which has a value of 700e0

Create a new rule in /etc/udev/hwdb.d with something like:

evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn*
 KEYBOARD_KEY_ed=volumeup
 KEYBOARD_KEY_ee=volumedown
 etc...

use evemu-describe to find your evdev:... line

also read:
https://wiki.archlinux.org/index.php/Map_scancodes_to_keycodes
https://wiki.archlinux.org/index.php/Extra_keyboard_keys
/lib/udev/hwdb.d/60-keyboard.hwdb
for more information and examples

Floris

Re: flash in stretch again

[Maureen L Thomas]

On 06/25/2017 05:18 PM, Dan Norton wrote:



On 06/25/2017 03:42 PM, Patrick Bartek wrote:

On Sat, 24 Jun 2017 22:17:13 -0400 Maureen L Thomas
 wrote:



On 06/24/2017 07:29 PM, The Wanderer wrote:

On 2017-06-24 at 18:56, Maureen L Thomas wrote:


As a last desperate attempt I completely removed firefox-esr and
reinstalled it.  I opened it up and the first game actually came
up. But the next two games again stated that I needed flash.  So I
shut down thinking that firefox had a problem and restarted it and
none of the games will run.  I am at a complete loss. What the
hell could be going on?

What does about:plugins report for Flash?

I also have a niggling idea related to the Firefox click-to-activate
model and the sometimes-missable "doorhanger" drop-down prompt
related to that model, but I'm not sure how to express the question
about that much less how to recommend checking into it.


The plugin says it is not there.  All the others are there except for
flash.  It has to be something with where libflashplayer.so is but I
have no idea where to start?  I am seriously considering going to a
different distro.  I really hate that idea but this is just to damn
much for me to figure out.  At 67 I just want to browse and play my
damn games.

Just install the flash plugin manually.  That's what I do and have done
so since I started using Linux 15+ years ago.

In firefox-esr, go to www.adobe.com.  Make sure that's all that's in
the URL.  (It may take you to the Adobe Cloud app page.)  Toward the
bottom of the page, right hand side, you should see listed Adobe
Reader, Flash Player, etc.  Click Flash Player and you should be taken
to the Download Page. The OS should say Linux, if not change it to.  The
player version should be 26.something.  Using the Type dropdown menu,
select tar.gz. NOT .DEB! Click Download.  Don't do any of the following
"install" steps. This is a manaul install, remember.  Plus, the
auto-install never worked for me.  Check if the download suceeded.
Depending on how you've got firefox-esr configured, the file should be
in Downloads in your home directory or possibly on your Desktop.  Using
a file manager, exact the tar.gz file to the same place it was
downloaded. The only file you need be concerned with is
libflashplayer.so  As root, using a terminal (or if your filemanager is
able to switch to root priviledge), copy libflashplayer.so
to /usr/lib/mozilla/plugins/

Restart firefox-esr, do the about:plugin thing and see if FlashPlayer
is there and enabled.  Also, by entering about: in the URL line, see if
firefox-esr version is 52.2.something.  That's the lastest version of
esr.


Test if it works with your game sites, etc.
Thank you, Patrick! You would not believe how much time I have wasted 
trying to install this thing (hmm... maybe you would). Manual 
installation rocks and it works for Jessie and FF 45.9.0.


 - Dan

FWIW, you said you were "upgraded" to Stretch automatically.  From
Jessie, I assume.  This was most likely caused by your Debian
Repositories being set to "Stable."  I had this happen 10+ years ago
when I first tried Debian (Sarge).  I was "upgraded" to Etch, IIRC, and
it caused problems since it was a improper upgrade with a bastard
system mix of Sarge and Etch.  To make a long story short, the fix was
a clean install.  You may have to do that (clean install of either
Jessie or Stretch), too, to get things working properly.  If everything
was working with Jessie, I suggest you install that.  With Debian's Long
Term Support, Jessie will be supported for another 3 years or so.

Good Luck.

B




So I was playing around trying to figure this crap out and I installed 
Opera and my games work in that browser.  They still do NOT work in 
Firefox ESR.  I would use Opera but none of the movie things will play.  
So how is that for screwed up.  I am going to download Stretch and do a 
clean install and then see how that goes. Thanks everyone for all the help.

Re: flash in stretch again

[Dan Norton]

On 06/25/2017 03:42 PM, Patrick Bartek wrote:

On Sat, 24 Jun 2017 22:17:13 -0400 Maureen L Thomas
 wrote:



On 06/24/2017 07:29 PM, The Wanderer wrote:

On 2017-06-24 at 18:56, Maureen L Thomas wrote:


As a last desperate attempt I completely removed firefox-esr and
reinstalled it.  I opened it up and the first game actually came
up. But the next two games again stated that I needed flash.  So I
shut down thinking that firefox had a problem and restarted it and
none of the games will run.  I am at a complete loss.  What the
hell could be going on?

What does about:plugins report for Flash?

I also have a niggling idea related to the Firefox click-to-activate
model and the sometimes-missable "doorhanger" drop-down prompt
related to that model, but I'm not sure how to express the question
about that much less how to recommend checking into it.


The plugin says it is not there.  All the others are there except for
flash.  It has to be something with where libflashplayer.so is but I
have no idea where to start?  I am seriously considering going to a
different distro.  I really hate that idea but this is just to damn
much for me to figure out.  At 67 I just want to browse and play my
damn games.

Just install the flash plugin manually.  That's what I do and have done
so since I started using Linux 15+ years ago.

In firefox-esr, go to www.adobe.com.  Make sure that's all that's in
the URL.  (It may take you to the Adobe Cloud app page.)  Toward the
bottom of the page, right hand side, you should see listed Adobe
Reader, Flash Player, etc.  Click Flash Player and you should be taken
to the Download Page. The OS should say Linux, if not change it to.  The
player version should be 26.something.  Using the Type dropdown menu,
select tar.gz. NOT .DEB! Click Download.  Don't do any of the following
"install" steps. This is a manaul install, remember.  Plus, the
auto-install never worked for me.  Check if the download suceeded.
Depending on how you've got firefox-esr configured, the file should be
in Downloads in your home directory or possibly on your Desktop.  Using
a file manager, exact the tar.gz file to the same place it was
downloaded. The only file you need be concerned with is
libflashplayer.so  As root, using a terminal (or if your filemanager is
able to switch to root priviledge), copy libflashplayer.so
to /usr/lib/mozilla/plugins/

Restart firefox-esr, do the about:plugin thing and see if FlashPlayer
is there and enabled.  Also, by entering about: in the URL line, see if
firefox-esr version is 52.2.something.  That's the lastest version of
esr.


Test if it works with your game sites, etc.
Thank you, Patrick! You would not believe how much time I have wasted 
trying to install this thing (hmm... maybe you would). Manual 
installation rocks and it works for Jessie and FF 45.9.0.


 - Dan

FWIW, you said you were "upgraded" to Stretch automatically.  From
Jessie, I assume.  This was most likely caused by your Debian
Repositories being set to "Stable."  I had this happen 10+ years ago
when I first tried Debian (Sarge).  I was "upgraded" to Etch, IIRC, and
it caused problems since it was a improper upgrade with a bastard
system mix of Sarge and Etch.  To make a long story short, the fix was
a clean install.  You may have to do that (clean install of either
Jessie or Stretch), too, to get things working properly.  If everything
was working with Jessie, I suggest you install that.  With Debian's Long
Term Support, Jessie will be supported for another 3 years or so.

Good Luck.

B

Re: Stretch upgrade from Jessie -- several issues

[Ralph Katz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 06/25/2017 02:39 PM, Mike Kupfer wrote:
> Ralph Katz wrote:
> 
>>> 2) Returning from xscreensaver screen blanking sometimes shows the
>>> lightdm log in screen.  Ctrl-alt-F7 once or twice can get my session
>>> back after an annoying pause.  This never happened on jessie.
> 
> This is a bit of a shot in the dark, but is light-locker running?
> 
> mike

Yes!  apt history shows light-locker was installed by the dist-upgrade.
 I've just purged xscreensaver and can confirm that the time-out errors
in syslog occur on resume from screen blanking.

Other than pushing out the screen lock time which I've done in xfce
settings, or disabling the lock, what do you suggest?  light-locker is a
"depends" of task-xfce-desktop so not removable.

Thanks Mike!

-BEGIN PGP SIGNATURE-
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIzBAEBCgAdFiEEJQZ8vK6BnmDiW8fZyAJ5DhtfJxAFAllQL5AACgkQyAJ5Dhtf
JxByHxAAlXe8K3sdXhIjkYekTbTfgVt8a0A9/i2zv2nQN/UuR3+Xg8zaQrp2HLxM
2yZPawxhgp9/pfs4oNs55s+u+KEt3CaGrnR8EKesA0z+bpQQ3WWJrl243wmgromT
QP2f0yOFJYcq0IvTOW/dROTWctLkAkAOjY+6O30tyEVe3+xcfAiqLVuvsFrB59ik
4GGII3cu6c8A+V4iHavk3oQIC078Mzo/CLQPknRN+sUa3c/HS7buVetIVM2eLueA
3MkmvVd0uldndYEbijb6cYpmaLWH7trV0aChdvME/4s51VYLxcxZMUQFM3E2zrfC
KDePTkv8qPXziW9cY6/UdZuUMyJKTzHYdOODZAgONrlDY95meggpIIXO/ieorkf/
KsuBpyH3NKrtVfDEP1sfPJMedk3fTUmKoRh+Pw8CKP67VoAyCpomc4t9qcKIPbKl
rd/snLH6s5u6VinHsQyaH64XEpCK1IWcy6nC5uGNyh2eRmpkB5byl+kxithfXTi5
03Z9EcoAy1iKMbacOlhx50fTfsTFEkdHsOW7rrpuxXrgvbWuhQLgEYRy0uQkFzit
EiurSUDoPUnDIol1GFh6SbN1FGqJmHYhgsErsywRpIa41mw5/NoDfly5HJeg4Kx/
toX+2YEGAa3UjU+jJsckMi0jXbdK19UwSNKsmWcKiKN0RYV27EE=
=uf7s
-END PGP SIGNATURE-

Re: Stretch upgrade from Jessie -- several issues

[Mike Kupfer]

Ralph Katz wrote:

> > 2) Returning from xscreensaver screen blanking sometimes shows the
> > lightdm log in screen.  Ctrl-alt-F7 once or twice can get my session
> > back after an annoying pause.  This never happened on jessie.

This is a bit of a shot in the dark, but is light-locker running?

mike

firewall rules for NAT

[Lucio Crusca]

I have a server with Debian GNU/Linux as host system.

The host runs several guest virtual machines, but it has only one public 
IP address.


Each virtual machine is a QEMU/KVM Debian GNU/Linux system that runs 
some specific service (so I have one for websites, one for mail, one for 
database, one for ssh connections, and so on).


One of the virtual machines is the router: the host system forwards any 
incoming connection to it and the router forwards the connection to the 
correct VM based on the TCP destination port.


The host system forwards connections to the router with these iptables 
rules (1.2.3.4 stands for the public IP address):


# Generated by iptables-save v1.4.21 on Sun Jun 25 22:33:39 2017
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [86517:5472157]
:OUTPUT ACCEPT [32635:3750271]
-A INPUT -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -p icmp -m icmp --icmp-type 8 -m conntrack --ctstate NEW -j ACCEPT
-A INPUT -p tcp -m tcp --dport 31222 --tcp-flags FIN,SYN,RST,ACK SYN -m 
conntrack --ctstate NEW -j ACCEPT

-A INPUT -i virbr10 -p udp -m udp -m multiport --dports 53,67 -j ACCEPT
-A INPUT -i virbr10 -p tcp -m tcp -m multiport --dports 53,67 -j ACCEPT
-A INPUT -m conntrack --ctstate INVALID -j DROP
-A INPUT -p tcp -m tcp -j REJECT --reject-with tcp-reset
-A INPUT -j REJECT --reject-with icmp-port-unreachable
-A FORWARD -d 10.7.33.0/24 -o virbr10 -m conntrack --ctstate 
RELATED,ESTABLISHED -j ACCEPT

-A FORWARD -s 10.7.33.0/24 -i virbr10 -j ACCEPT
-A FORWARD -i virbr10 -o virbr10 -j ACCEPT
-A FORWARD -d 10.7.33.100/32 -o virbr10 -p tcp -m tcp --dport 1:31221 
--tcp-flags FIN,SYN,RST,ACK SYN -m conntrack --ctstate NEW -j ACCEPT

-A FORWARD -i virbr10 -j REJECT --reject-with icmp-port-unreachable
-A FORWARD -o virbr10 -j REJECT --reject-with icmp-port-unreachable
COMMIT
# Completed on Sun Jun 25 22:33:39 2017
# Generated by iptables-save v1.4.21 on Sun Jun 25 22:33:39 2017
*nat
:PREROUTING ACCEPT [265547:18746839]
:INPUT ACCEPT [7946:621443]
:OUTPUT ACCEPT [44:3768]
:POSTROUTING ACCEPT [737574:41994020]
-A PREROUTING -d 1.2.3.4/32 -p tcp -m tcp --dport 1:31221 --tcp-flags 
FIN,SYN,RST,ACK SYN -j DNAT --to-destination 10.7.33.100

-A POSTROUTING -s 10.7.33.0/24 -d 224.0.0.0/24 -j RETURN
-A POSTROUTING -s 10.7.33.0/24 -d 255.255.255.255/32 -j RETURN
-A POSTROUTING -s 10.7.33.0/24 ! -d 10.7.33.0/24 -p tcp -j MASQUERADE 
--to-ports 1024-65535
-A POSTROUTING -s 10.7.33.0/24 ! -d 10.7.33.0/24 -p udp -j MASQUERADE 
--to-ports 1024-65535

-A POSTROUTING -s 10.7.33.0/24 ! -d 10.7.33.0/24 -j MASQUERADE
COMMIT
# Completed on Sun Jun 25 22:33:39 2017
# Generated by iptables-save v1.4.21 on Sun Jun 25 22:33:39 2017
*mangle
:PREROUTING ACCEPT [32568589:28152102128]
:INPUT ACCEPT [65809:5372699]
:FORWARD ACCEPT [32502779:28146729377]
:OUTPUT ACCEPT [56541:5855271]
:POSTROUTING ACCEPT [32535420:28150481592]
-A POSTROUTING -o virbr10 -p udp -m udp --dport 68 -j CHECKSUM 
--checksum-fill

COMMIT
# Completed on Sun Jun 25 22:33:39 2017

Then the router has its own set of iptables rules (I report only a few 
here):


# Generated by iptables-save v1.4.21 on Sun Jun 25 22:41:19 2017
*filter
:INPUT ACCEPT [114664:5730467]
:FORWARD ACCEPT [20388771:18133798388]
:OUTPUT ACCEPT [112664:4594474]
-A INPUT -s 10.7.33.101/32 -p tcp -m tcp --sport 29101 -j LOG
COMMIT
# Completed on Sun Jun 25 22:41:19 2017
# Generated by iptables-save v1.4.21 on Sun Jun 25 22:41:19 2017
*nat
:PREROUTING ACCEPT [108899:5217224]
:INPUT ACCEPT [108899:5217224]
:OUTPUT ACCEPT [2734:162786]
:POSTROUTING ACCEPT [2734:162786]
-A PREROUTING -p tcp -m tcp --dport 29101 -j DNAT --to-destination 
10.7.33.101

-A PREROUTING -p tcp -m tcp --dport 80 -j DNAT --to-destination 10.7.33.101
-A PREROUTING -p tcp -m tcp --dport 443 -j DNAT --to-destination 10.7.33.101
-A PREROUTING -p tcp -m tcp --dport 25 -j DNAT --to-destination 10.7.33.109
-A POSTROUTING -d 10.7.33.101/32 -p tcp -m tcp --dport 29101 -j SNAT 
--to-source 10.7.33.100
-A POSTROUTING -d 10.7.33.101/32 -p tcp -m tcp --dport 80 -j SNAT 
--to-source 10.7.33.100
-A POSTROUTING -d 10.7.33.101/32 -p tcp -m tcp --dport 443 -j SNAT 
--to-source 10.7.33.100
-A POSTROUTING -d 10.7.33.109/32 -p tcp -m tcp --dport 25 -j SNAT 
--to-source 10.7.33.100

COMMIT
# Completed on Sun Jun 25 22:41:19 2017

It works like a charm, but there is one problem: my mail server receives 
all the connections from the router, which has its own private IP 
address (10.7.33.100), so the mail server can't enforce SPF policies nor 
DNS RBL rules on incoming mail connections.


Is there a way to forward packets from the host to the router and from 
the router to the correct virtual server keeping the original source IP 
address?

Re: Jessie --> Stretch upgrade, apt question

[Cousin Stanley]

Mark Fletcher wrote:

> 
> I do wish apt show made it easier to tell 
> if a package is installed 
> 

  $ apt policy some-pkg-name

which evolved from

  $ apt-cache policy pkg-name


  will display installation status
  of some-pkg-name



-- 
Stanley C. Kitching
Human Being
Phoenix, Arizona

Re: flash in stretch again

[Carl Fink]

On 06/25/2017 03:42 PM, Patrick Bartek wrote:

... The only file you need be concerned with is
libflashplayer.so As root, using a terminal (or
if your filemanager is able to switch to root
priviledge), copy libflashplayer.so to
/usr/lib/mozilla/plugins/


One thing that has bitten me when doing this and things
like it: make sure the library is world-readable.

--
Carl Fink  c...@finknetwork.com
Thinking and logic and stuff at Reasonably Literate
http://reasonablyliterate.com

Re: flash in stretch again

[Patrick Bartek]

On Sat, 24 Jun 2017 22:17:13 -0400 Maureen L Thomas
 wrote:

> 
> 
> On 06/24/2017 07:29 PM, The Wanderer wrote:
> > On 2017-06-24 at 18:56, Maureen L Thomas wrote:
> >
> >> As a last desperate attempt I completely removed firefox-esr and
> >> reinstalled it.  I opened it up and the first game actually came
> >> up. But the next two games again stated that I needed flash.  So I
> >> shut down thinking that firefox had a problem and restarted it and
> >> none of the games will run.  I am at a complete loss.  What the
> >> hell could be going on?
> > What does about:plugins report for Flash?
> >
> > I also have a niggling idea related to the Firefox click-to-activate
> > model and the sometimes-missable "doorhanger" drop-down prompt
> > related to that model, but I'm not sure how to express the question
> > about that much less how to recommend checking into it.
> >
> The plugin says it is not there.  All the others are there except for 
> flash.  It has to be something with where libflashplayer.so is but I 
> have no idea where to start?  I am seriously considering going to a 
> different distro.  I really hate that idea but this is just to damn
> much for me to figure out.  At 67 I just want to browse and play my
> damn games.

Just install the flash plugin manually.  That's what I do and have done
so since I started using Linux 15+ years ago.

In firefox-esr, go to www.adobe.com.  Make sure that's all that's in
the URL.  (It may take you to the Adobe Cloud app page.)  Toward the
bottom of the page, right hand side, you should see listed Adobe
Reader, Flash Player, etc.  Click Flash Player and you should be taken
to the Download Page. The OS should say Linux, if not change it to.  The
player version should be 26.something.  Using the Type dropdown menu,
select tar.gz. NOT .DEB! Click Download.  Don't do any of the following
"install" steps. This is a manaul install, remember.  Plus, the
auto-install never worked for me.  Check if the download suceeded.
Depending on how you've got firefox-esr configured, the file should be
in Downloads in your home directory or possibly on your Desktop.  Using
a file manager, exact the tar.gz file to the same place it was
downloaded. The only file you need be concerned with is
libflashplayer.so  As root, using a terminal (or if your filemanager is
able to switch to root priviledge), copy libflashplayer.so
to /usr/lib/mozilla/plugins/

Restart firefox-esr, do the about:plugin thing and see if FlashPlayer
is there and enabled.  Also, by entering about: in the URL line, see if
firefox-esr version is 52.2.something.  That's the lastest version of
esr.


Test if it works with your game sites, etc. 

FWIW, you said you were "upgraded" to Stretch automatically.  From
Jessie, I assume.  This was most likely caused by your Debian
Repositories being set to "Stable."  I had this happen 10+ years ago
when I first tried Debian (Sarge).  I was "upgraded" to Etch, IIRC, and
it caused problems since it was a improper upgrade with a bastard
system mix of Sarge and Etch.  To make a long story short, the fix was
a clean install.  You may have to do that (clean install of either
Jessie or Stretch), too, to get things working properly.  If everything
was working with Jessie, I suggest you install that.  With Debian's Long
Term Support, Jessie will be supported for another 3 years or so.

Good Luck.

B

Re: konsole blinking screen with irssi when ssh'd to NetBSD

[Darac Marjal]

On Sun, Jun 25, 2017 at 01:51:01PM -0500, Glenn Holmer wrote:

I've got a freeshell.org account, and they're running NetBSD. When I SSH
into that account, the terminal looks fine, but when I start irssi, the
entire screen blinks on and off about once a second. This is from my
Debian Stretch box running KDE, with konsole as terminal and bash as shell.

I've got another machine here that runs GNOME (under Fedora); I tried
the same thing using gnome-terminal and the screen didn't blink when I
started irssi.

Can anyone offer some suggestions to solve this?


It might be as simple as a bad terminal description. What is $TERM set
to? Try setting it to something different (TERM=xterm irssi -or-
TERM=vt100 irssi) and see if that fixes things.

Ideally, TERM should indicate what terminal (or terminal emulator)
you're using. But the TERM variable works with the local system's
terminfo database. That says things like "For italic text, send this
code.", "This terminal cannot clear individual characters, only whole
lines" etc. If the database is broken somehow, or doesn't know exactly
how to manage your terminal, then it may be sending the wrong sequences.



--
Glenn Holmer (Linux registered user #16682)
"After the vintage season came the aftermath -- and Cenbe."



--
For more information, please reread.


signature.asc
Description: PGP signature

Re: Stretch estable desde testing?

[Abogado]

El 23/06/17 a las 14:32, JAP escribió:
> El 23/06/17 a las 09:42, Ignacio Martirén escribió:
>> Hola amigos de la lista. Soy usuario Debian, pero manejo poco el tema.
>> Instalé hace bastante tiempo el testing Stretch. Ahora que llegó a la
>> etapa de estable instalaré el próximo testing que sigue en la partición
>> que ahora tengo con Jessie, ya que me gusta tener un estable y el
>> testing en la máquina. Pregunto, ¿la instalación testing que yo tengo,
>> ya la tengo como estable pasada automáticamente desde repositorios al
>> hacer update && upgrade?
>>
>> -- 
>> */  _Ignacio_/*
>> */_
>> _/*
>> */_
>> _/*
>
> No es tan así, y todo depende.
>
> Abre el archivo /etc/apt/mirror.list
>
> Si tu partición "stable" apunta a, por ejemplo,
> deb http://ftp.debian.org/debian/ stable main contrib non-free
> no debes hacer nada, dado que seguirá en "stable", pero ahora se
> llamará Stretch en vez de Jessie
>
> Si por el contrario, apunta a
> deb http://ftp.debian.org/debian/ jessie main contrib non-free
> deberás cambiar la palabra "jessie" por "stretch" y hacer una
> actualización.
>
> ¡ATENCIÓN!
> Cualquiera sean los dos casos, antes de hacer
> # apt-get dist-upgrade
> lee este tutorial,
> https://www.debian.org/releases/stable/amd64/release-notes/ch-upgrading.es.html
>
> porque pasar de una estable a otra nueva estable, suele tener algunos
> dimes y diretes.
>
> En el caso de la partición "testing", es conveniente tener el archivo
> /etc/apt/mirror.list apuntando siempre a "testing", de la siguiente
> manera:
> deb http://ftp.debian.org/debian/ testing main contrib non-free
> De esta manera, como ahora, el paso de Stretch a Buster, es totalmente
> transparente.
>
> JAP
>
> PD: Si tenés una instalación de 32 bits, el enlace es
> https://www.debian.org/releases/stable/i386/release-notes/ch-upgrading.es.html
>
>
>
>
>
>
>
>
Hola

Aunque tenga puesto stable puede dar problemas, en mi caso fue un caos
incluido perdida del entorno gráfico, al final tuve que hace una
instalación bajándome un DVD desde la página de Debian y manteniendo la
partición /home e instalando de nuevo todos los programas que tenia.

-- 
Un saludo,
José Manuel
Gran Canaria/España

Si vas a escribir.. piensa en esto:
no digas nada que no sea mas precioso que el silencio!!!

konsole blinking screen with irssi when ssh'd to NetBSD

[Glenn Holmer]

I've got a freeshell.org account, and they're running NetBSD. When I SSH
into that account, the terminal looks fine, but when I start irssi, the
entire screen blinks on and off about once a second. This is from my
Debian Stretch box running KDE, with konsole as terminal and bash as shell.

I've got another machine here that runs GNOME (under Fedora); I tried
the same thing using gnome-terminal and the screen didn't blink when I
started irssi.

Can anyone offer some suggestions to solve this?

-- 
Glenn Holmer (Linux registered user #16682)
"After the vintage season came the aftermath -- and Cenbe."

Re: Stretch upgrade from Jessie -- several issues

[Ralph Katz]

On 06/24/2017 09:48 AM, Ralph Katz wrote:
...
> At your suggestion, I'm re-doing my firefox setup, re-install, fresh
> profile, eliminate extensions, etc.  Report to follow.

Update report (quoting original thread post):

> Since upgrading my old Acer laptop from jessie to stretch this week, I
> have several unresolved issues.  Any help would be appreciated.
> 
> 1)  Sometimes unresponsive.  In up-to-date jessie, I could have two
> instances of firefox-esr open with multiple tabs and get reasonable
> response.  In stretch, sometimes performance is completely normal, but
> at random intervals, the desktop becomes unresponsive as disk activity
> takes over.  Top shows firefox very active and ps shows a number of
> kworker processes recently started.  But closing one browser and
> reducing open tabs does not seem to matter.  How can I identify the
> offending processes?  No hints appear in log files using the Linux 3.16
> kernel.

Firefox fix:  Went back to Linux 4.09 kernel. Moved ~/.mozilla/ out of
the way, removed all firefox non-debian extensions (ghostery, noscript,
adblock), reinstalled firefox-esr and flashplayer-mozilla, installed
xul-ext-noscript and xul-ext-ublock-origin, manually reset preferences,
imported old bookmarks, history, passwords, noscript whitelist, etc.
Load average in top has gone from an unusable 2,3,5 even 7 to under .50.

> 2) Returning from xscreensaver screen blanking sometimes shows the
> lightdm log in screen.  Ctrl-alt-F7 once or twice can get my session
> back after an annoying pause.  This never happened on jessie.

This problem got worse, so rebooted into Linux 4.09 kernel to work it
out and maintain a supportable security os.  I've uploaded logs as follows:

kernel errors on boot, *ERROR* [CRTC:29:pipe B] flip_done timed out:
syslog:  http://paste.debian.net/973246/

Xorg.0.log:  http://paste.debian.net/973247/

lightdm.log: http://paste.debian.net/973248/

> 3) The sound volume up/down function keys [Fn up/down arrow] no longer
> respond (xfce4).  However the screen brightness keys function normally
> [Fn left/right arrow].  The mute sound function key is also ignored [Fn
> F8].  I can control volume with the mouse using pavucontrol or
> gkrellm-volume.

No progress.

Thanks again for any help.

Ralph




signature.asc
Description: OpenPGP digital signature

Re: Upgrade de Jessie

[Pierre L.]

Voilà qui devrait apaiser quelques esprits ;)

Peace!

Le 24/06/2017 à 21:01, andre_deb...@numericable.fr a écrit :
> "Laisser le soin aux cobayes" étaient à prendre au second 
> degré, étant conscient et admiratif du formidable travail accompli 
> durant toutes ces années par l'équipe technique de Debian pour 
> chaque nouvelle version.
>
> Bonne soirée,
>
> André
>




signature.asc
Description: OpenPGP digital signature

Re: off topic! What is the error in this script

[Teemu Likonen]

Dominic Knight [2017-06-25 15:35:46+01] wrote:

> To convert a series of .flac files to .mp3 files I attempted to use the
> following line;
>
>> $ find -name "*.flac" -exec bash -c 'ffmpeg -i "{}" -y -acodec
> libmp3lame -ab 320k "${0/.flac}.mp3"' {} \;

The arguments for "bash -c" go like this:

bash -c '...' name one two three

And in '...' the arguments are in variables $0 (=name), $1 (=one), $2
(=two), $3 (=three) etc. So:

find -name "*.flac" -exec \
bash -c 'ffmpeg -i file:"$1" -c:a libmp3lame -ab 320k -y 
file:"${1%.flac}.mp3"' \
foo {} \;

Note the "foo": it is saved to $0 ("shell's name") and and then the
actual filename is in usual first positional parameter $1. We also want
to have explicitl "file:" protocol with ffmpeg so that any "something:"
prerix in filename is not interpreted as a protocol name. (See "man
ffmpeg-protocols".)

But here's another way without double quoting:

while read -r -d $'\0' input; do
ffmpeg -i file:"$input" -c:a libmp3lame -ab 320k \
-y file:"${input%.flac}.mp3"
done < <(find . -name '*.flac' -print0)

-- 
/// Teemu Likonen   - .-..    //
// PGP: 4E10 55DC 84E9 DFF6 13D7 8557 719D 69D3 2453 9450 ///


signature.asc
Description: PGP signature

Re: He

[Leandro Henrique Stein]

Ao "responder à todos" você acabou de confirmar mais um email, o seu, para
o spammer.


-- 
Leandro Henrique Stein
Analista de Informática
Claro: (41) 9935-9960
Skype: leandro.h.stein
Twitter: @leandrohstein

"Desculpar-se é um sinal de fraqueza. Exceto entre amigos" - Leroy Jethro
Gibbs

Em 16 de jun de 2017 10:29 AM, "Gilberto F da Silva" 
escreveu:

> On Mon, Jun 12, 2017 at 12:07:51AM -0700, Brittany Barnard wrote:
> >
> >
> > Sent from my iPhone
> >
>
>
>   Qual o sentido de alguém mandar uma mensagem assim?
>
>   Alguém vai dizer que é spammer mas não há texto além da indicação do
>   dispositivo usado.
>
> --
>
> Gilberto F da Silva - gfs1...@mandic.com.br - ICQ 136.782.571
> Stela dato:2.457.921,055  Loka tempo:2017-06-16 10:19:29 Vendredo
> -==-
> Tudo o que puder dar errado, dará errado.
>

Re: off topic! What is the error in this script

[Wellington Terumi Uemura]

I would do something like...

for f in *.flac; do something $f; done

It will find all your flac files and do whatever.



Em 25 de jun de 2017 11:51, "Dominic Knight" 
escreveu:

> To convert a series of .flac files to .mp3 files I attempted to use the
> following line;
>
> > $ find -name "*.flac" -exec bash -c 'ffmpeg -i "{}" -y -acodec
> libmp3lame -ab 320k "${0/.flac}.mp3"' {} \;
>
> which I expected to find each flac and convert it to a corresponding
> .mp3 however, it reads the first .flac only and rewrites it to all .mp3
> files ie;
>
> for flacs (a1 > a9) it reads a .flac and outputs mp3's (a1 > a9) but
> all mp3's contain the original content of only a1.flac
>
> Where have I gone wrong?
>
> Cheers,
> Dom.
>
>

off topic! What is the error in this script

[Dominic Knight]

To convert a series of .flac files to .mp3 files I attempted to use the
following line;

> $ find -name "*.flac" -exec bash -c 'ffmpeg -i "{}" -y -acodec
libmp3lame -ab 320k "${0/.flac}.mp3"' {} \;

which I expected to find each flac and convert it to a corresponding
.mp3 however, it reads the first .flac only and rewrites it to all .mp3
files ie;

for flacs (a1 > a9) it reads a .flac and outputs mp3's (a1 > a9) but
all mp3's contain the original content of only a1.flac

Where have I gone wrong?

Cheers,
Dom.

Re: sftp en ligne de commande

[Jean-Marc]

Sun, 25 Jun 2017 15:13:08 +0200 (CEST)
bernard.schoenac...@free.fr écrivait :

> bonjour,

salut,

> 
> 
> merci pour la réponse, mais serait il possible de fournir un exemple ?

$ sftp user@host

> 
> la page de man sftp n'est pas explicite

sftp> help
Available commands:
byeQuit sftp
cd pathChange remote directory to 'path'
chgrp grp path Change group of file 'path' to 'grp'
chmod mode pathChange permissions of file 'path' to 'mode'
chown own path Change owner of file 'path' to 'own'
df [-hi] [path]Display statistics for current directory or
   filesystem containing 'path'
exit   Quit sftp
get [-afPpRr] remote [local]   Download file
reget [-fPpRr] remote [local]  Resume download file
reput [-fPpRr] [local] remote  Resume upload file
help   Display this help text
lcd path   Change local directory to 'path'
lls [ls-options [path]]Display local directory listing
lmkdir pathCreate local directory
ln [-s] oldpath newpathLink remote file (-s for symlink)
lpwd   Print local working directory
ls [-1afhlnrSt] [path] Display remote directory listing
lumask umask   Set local umask to 'umask'
mkdir path Create remote directory
progress   Toggle display of progress meter
put [-afPpRr] local [remote]   Upload file
pwdDisplay remote working directory
quit   Quit sftp
rename oldpath newpath Rename remote file
rm pathDelete remote file
rmdir path Remove remote directory
symlink oldpath newpathSymlink remote file
versionShow SFTP version
!command   Execute 'command' in local shell
!  Escape to local shell
?  Synonym for help

> 
> slt
> bernard


Jean-Marc 


pgp_vBHI4zP55.pgp
Description: PGP signature

Re: sftp en ligne de commande

[bernard . schoenacker]

- Mail original -
> De: "Jean-Marc" 
> À: debian-user-french@lists.debian.org
> Envoyé: Dimanche 25 Juin 2017 11:39:11
> Objet: Re: sftp en ligne de commande
> 
> Sun, 25 Jun 2017 11:35:05 +0200 (CEST)
> bernard.schoenac...@free.fr écrivait :
> 
> > bonjour,
> 
> salut Bernard,
> 
> > 
> > je recherche un moyen d'employer sftp en ligne de commande
> > pour transférer des fichiers ...
> 
> Il existe une commade .
> 
> > [...]
> > slt
> > bernard
> 
> Jean-Marc 
> 

bonjour,


merci pour la réponse, mais serait il possible de fournir un exemple ?

la page de man sftp n'est pas explicite

slt
bernard

Re: [WARNING] Intel Skylake/Kaby Lake processors: broken hyper-threading

[Henrique de Moraes Holschuh]

For the record: the email with the perl script doesn't contain malware.

The "malware" alert came from an extremely badly configured system that
violates every best practice in the field: it sends email to every
original recipient (and not just to local users), and it FORGES its
headers to look like it was sent by the original sender.

-- 
  Henrique Holschuh


signature.asc
Description: Digital signature

Re: [WARNING] Intel Skylake/Kaby Lake processors: broken hyper-threading

[Henrique de Moraes Holschuh]

On Sun, 25 Jun 2017, Henrique de Moraes Holschuh wrote:
> This warning advisory is relevant for users of systems with the Intel
> processors code-named "Skylake" and "Kaby Lake".  These are: the 6th and
> 7th generation Intel Core processors (desktop, embedded, mobile and
> HEDT), their related server processors (such as Xeon v5 and Xeon v6), as
> well as select Intel Pentium processor models.

Attached, you will find a perl script that can help detect if your
system is affected or not.  Many thanks to Uwe Kleine-König for
suggesting, and writing this script.

-- 
  Henrique Holschuh


Unsupported File Types Alert.txt
Description: Unsupported File Types Alert.txt

Re: [WARNING] Intel Skylake/Kaby Lake processors: broken hyper-threading

[Henrique de Moraes Holschuh]

On Sun, 25 Jun 2017, Henrique de Moraes Holschuh wrote:
> This warning advisory is relevant for users of systems with the Intel
> processors code-named "Skylake" and "Kaby Lake".  These are: the 6th and
> 7th generation Intel Core processors (desktop, embedded, mobile and
> HEDT), their related server processors (such as Xeon v5 and Xeon v6), as
> well as select Intel Pentium processor models.

Attached, you will find a perl script that can help detect if your
system is affected or not.  Many thanks to Uwe Kleine-König for
suggesting, and writing this script.

-- 
  Henrique Holschuh
#!/usr/bin/perl
# Copyright 2017 Uwe Kleine-König
#
# This program is free software; you can redistribute it and/or modify it under
# the terms of the GNU General Public License version 2 as published by the
# Free Software Foundation.

open(my $cpuinfo, ") {
	if (/^$/) {
		print "cpu $cpunum: ";
		if ($vendor eq "GenuineIntel" and $family == 6) {
			if ($model == 78 or $model == 94) {
if ($stepping eq "3") {
	print "Your CPU is affected, ";
	if (hex($microcoderev) >= 0xb9) {
		print "but your microcode is new enough\n";
	} elsif ($hyperthreading ne "on") {
		print "but hyper threading is off, which works around the problem\n";
	} else {
		print "you should install the latest intel-microcode\n";
	}
} else {
	print "You may need a BIOS/UEFI update (unknown Skylake-Y/H/U/S stepping)\n";
}
			} elsif ($model == 85 or $model == 142 or $model == 158) {
print "You may need a BIOS/UEFI update (Kaby Lake, or Skylake-X processor)\n";
			} else {
print "You're likely not affected\n";
			}
		} else {
			print "You're not affected\n";
		}

		$cpunum = undef;
		$vendor = undef;
		$family = undef;
		$stepping = undef;
		$microcoderev = undef;
		$hyperthreading = undef;

		next;
	}

	$cpunum = $1 if /^processor\s*:\s(.*)/;
	$vendor = $1 if /^vendor_id\s*:\s(.*)/;
	$family = $1 if /^cpu family\s*:\s(.*)/;
	$model = $1 if /^model\s*:\s(.*)/;
	$stepping = $1 if /^stepping\s*:\s(.*)/;
	$microcoderev = $1 if /^microcode\s*:\s(.*)/;

	if (/^flags\s*:/) {
		if (/^flags\s*:.*\bht\b/) {
			$hyperthreading = "on";
		} else {
			$hyperthreading = "off";
		}
	}
}

[WARNING] Intel Skylake/Kaby Lake processors: broken hyper-threading

[Henrique de Moraes Holschuh]

This warning advisory is relevant for users of systems with the Intel
processors code-named "Skylake" and "Kaby Lake".  These are: the 6th and
7th generation Intel Core processors (desktop, embedded, mobile and
HEDT), their related server processors (such as Xeon v5 and Xeon v6), as
well as select Intel Pentium processor models.

TL;DR: unfixed Skylake and Kaby Lake processors could, in some
situations, dangerously misbehave when hyper-threading is enabled.
Disable hyper-threading immediately in BIOS/UEFI to work around the
problem.  Read this advisory for instructions about an Intel-provided
fix.


SO, WHAT IS THIS ALL ABOUT?
---

This advisory is about a processor/microcode defect recently identified
on Intel Skylake and Intel Kaby Lake processors with hyper-threading
enabled.  This defect can, when triggered, cause unpredictable system
behavior: it could cause spurious errors, such as application and system
misbehavior, data corruption, and data loss.

It was brought to the attention of the Debian project that this defect
is known to directly affect some Debian stable users (refer to the end
of this advisory for details), thus this advisory.

Please note that the defect can potentially affect any operating system
(it is not restricted to Debian, and it is not restricted to Linux-based
systems).  It can be either avoided (by disabling hyper-threading), or
fixed (by updating the processor microcode).

Due to the difficult detection of potentially affected software, and the
unpredictable nature of the defect, all users of the affected Intel
processors are strongly urged to take action as recommended by this
advisory.


DO I HAVE AN INTEL SKYLAKE OR KABY LAKE PROCESSOR WITH HYPER-THREADING?
---

The earliest of these Intel processor models were launched in September
2015.  If your processor is older than that, it will not be an Skylake
or Kaby Lake processor and you can just ignore this advisory.

If you don't know the model name of your processor(s), the command below
will tell you their model names.  Run it in a command line shell (e.g.
xterm):

grep name /proc/cpuinfo | sort -u

Once you know your processor model name, you can check the two lists
below:

  * List of Intel processors code-named "Skylake":
http://ark.intel.com/products/codename/37572/Skylake

  * List of Intel processors code-named "Kaby Lake":
http://ark.intel.com/products/codename/82879/Kaby-Lake

Some of the processors in these two lists are not affected because they
lack hyper-threading support.  Run the command below in a command line
shell (e.g. xterm), and it will output a message if hyper-threading is
supported/enabled:

  grep -q '^flags.*[[:space:]]ht[[:space:]]' /proc/cpuinfo && \
echo "Hyper-threading is supported"

Alternatively, use the processor lists above to go to that processor's
information page, and the information on hyper-threading will be there.

If your processor does not support hyper-threading, you can ignore this
advisory.


WHAT SHOULD I DO IF I DO HAVE SUCH PROCESSORS?
--

Kaby Lake:

Users of systems with Intel Kaby Lake processors should immediately
*disable* hyper-threading in the BIOS/UEFI configuration.  Please
consult your computer/motherboard's manual for instructions, or maybe
contact your system vendor's support line.

The Kaby Lake microcode updates that fix this issue are currently only
available to system vendors, so you will need a BIOS/UEFI update to get
it.  Contact your system vendor: if you are lucky, such a BIOS/UEFI
update might already be available, or undergoing beta testing.

You want your system vendor to provide a BIOS/UEFI update that fixes
"Intel processor errata KBL095, KBW095 or the similar one for my Kaby
Lake processor".

We strongly recommend that you should not re-enable hyper-threading
until you install a BIOS/UEFI update with this fix.


Skylake:

Users of systems with Intel Skylake processors may have two choices:

1. If your processor model (listed in /proc/cpuinfo) is 78 or 94, and
   the stepping is 3, install the non-free "intel-microcode" package
   with base version 3.20170511.1, and reboot the system.  THIS IS
   THE RECOMMENDED SOLUTION FOR THESE SYSTEMS, AS IT FIXES OTHER
   PROCESSOR ISSUES AS WELL.

   Run this command in a command line shell (e.g. xterm) to know the
   model numbers and steppings of your processor.  All processors must
   be either model 78 or 94, and stepping 3, for the intel-microcode fix
   to work:

 grep -E 'model|stepping' /proc/cpuinfo | sort -u

   If you get any lines with a model number that is neither 78 or 94, or
   the stepping is not 3, you will have to disable hyper-threading as
   described on choice 2, below.

   Refer to the section "INSTALLING THE MICROCODE UPDATES FROM NON-FREE"
   for instructions on how to install the intel-microcode package.

2. For other 

Re: WLAN laufende Qualitaetsmessung

[Curt]

On 2017-06-25, Hans  wrote:
> I read the original post now (in German, and as I am German, no problem).
> In his case I think "kismet" is a good start. So he can see, if there are 
> other AP on the same frequency. I also suggest "wavemon", which shows all AP 
> and its strenth.
>
> If the neighbour is sending weired pckages (maybe with aireplay-ng, who 
> knows), then wireshark or tshark is working fine for it. Also you have then 
> evidence for his doings, which is illegal (here in Germany). 
>
> Maybe also the package "horst" is also helpful, which is designed for 
> excactly 
> these issues: check your traffic. (I have never used it for now).

Was ist mit den hunden? 

> Hope this helps
>
> Best regards
>
> Hans
>
>
>
>


-- 
"It might be a vision--of a shell, of a wheelbarrow, of a fairy kingdom on the
far side of the hedge; or it might be the glory of speed; no one knew." --Mrs.
Ramsay, speculating on why her little daughter might be dashing about, in "To
the Lighthouse," by Virginia Woolf.

Re: Jessie --> Stretch upgrade, apt question

[Curt]

On 2017-06-25, Mark Fletcher  wrote:
>
> My question is that since the upgrade chromium is held back from 
> upgrading, and in this new world I don't know how to find out why. In 
> aptitude I would have done aptitude why-not chromium and it would most 
> likely have told me something useful about its dependencies. How can I 
> get apt to do similar? Or what tool should I use?
>

'apt-get install ' will tell you why a package is being held
back (or, as discussed in another thread, will ask your permission to
install an extra package--or packages--in order to meet its dependencies).

-- 
"It might be a vision--of a shell, of a wheelbarrow, of a fairy kingdom on the
far side of the hedge; or it might be the glory of speed; no one knew." --Mrs.
Ramsay, speculating on why her little daughter might be dashing about, in "To
the Lighthouse," by Virginia Woolf.

Re: (deb-cat) sources.list i base.list

[Jordi Boixader]

Vaig canviar el nom: mv /etc/apt/trusted.gpg /etc/apt/trusted.gpg.jordi i
ja no surten aquells avisos.

jordi@debian9:~$ find /etc/apt
/etc/apt
/etc/apt/sources.list.d
/etc/apt/sources.list.d/google-chrome.list.save
/etc/apt/sources.list.d/google-chrome.list
/etc/apt/trusted.gpg
/etc/apt/listchanges.conf
/etc/apt/trusted.gpg.jordi
/etc/apt/sources.list
/etc/apt/apt.conf.d
/etc/apt/apt.conf.d/00trustcdrom
/etc/apt/apt.conf.d/60plasma-discover
/etc/apt/apt.conf.d/01autoremove
/etc/apt/apt.conf.d/50appstream
/etc/apt/apt.conf.d/20listchanges
/etc/apt/apt.conf.d/20auto-upgrades
/etc/apt/apt.conf.d/00CDMountPoint
/etc/apt/apt.conf.d/01autoremove-kernels
/etc/apt/apt.conf.d/50unattended-upgrades
/etc/apt/apt.conf.d/70debconf
/etc/apt/apt.conf.d/20packagekit
/etc/apt/apt.conf.d/60apper
/etc/apt/sources.list~
/etc/apt/trusted.gpg.d
/etc/apt/trusted.gpg.d/debian-archive-jessie-automatic.gpg
/etc/apt/trusted.gpg.d/debian-archive-jessie-stable.gpg
/etc/apt/trusted.gpg.d/debian-archive-wheezy-automatic.gpg
/etc/apt/trusted.gpg.d/debian-archive-stretch-security-automatic.gpg
/etc/apt/trusted.gpg.d/debian-archive-stretch-stable.gpg
/etc/apt/trusted.gpg.d/debian-archive-jessie-security-automatic.gpg
/etc/apt/trusted.gpg.d/debian-archive-wheezy-stable.gpg
/etc/apt/trusted.gpg.d/debian-archive-stretch-automatic.gpg
/etc/apt/preferences.d
/etc/apt/trusted.gpg~
/etc/apt/sources.list.save
jordi@debian9:~$

El dia 25 de juny de 2017 a les 9:36, Narcis Garcia 
ha escrit:

> Prova a veure què et surt amb la comanda:
>
> $ find /etc/apt
>
>
> __
> I'm using this express-made address because personal addresses aren't
> masked enough at this list's archives. Mailing lists service
> administrator should fix this.
> El 24/06/17 a les 20:39, Jordi Boixader ha escrit:
> > Ara encara surten mes W:
> >
> >
> > root@debian9:/etc/apt# apt-get update
> > Ign:1 http://ftp.es.debian.org/debian stretch InRelease
> > Obj:2 http://security.debian.org/debian-security stretch/updates
> InRelease
> > Obj:4 http://ftp.es.debian.org/debian stretch Release
> > Bai:3 http://ftp.es.debian.org/debian stretch-updates InRelease [88,5
> kB]
> > Err:2 http://security.debian.org/debian-security stretch/updates
> InRelease
> >  Les signatures següents no s'han pogut verificar perquè la clau pública
> > no està disponible: NO_PUBKEY 9D6D8F6BC857C906 NO_PUBKEY 8B4
> > 8AD6246925553
> > Err:5 http://ftp.es.debian.org/debian stretch Release.gpg
> >  Les signatures següents no s'han pogut verificar perquè la clau pública
> > no està disponible: NO_PUBKEY 8B48AD6246925553 NO_PUBKEY 763
> > 8D0442B90D010 NO_PUBKEY CBF8D6FD518E17E1 NO_PUBKEY EF0F382A1A7B6500
> > Err:3 http://ftp.es.debian.org/debian stretch-updates InRelease
> >  Les signatures següents no s'han pogut verificar perquè la clau pública
> > no està disponible: NO_PUBKEY 8B48AD6246925553 NO_PUBKEY 763
> > 8D0442B90D010
> > S'ha baixat 88,5 kB en 0s (89,3 kB/s)
> > S'està llegint la llista de paquets… Fet
> > W: S'ha produït un error durant la verificació de la signatura. El
> > repositori no està actualitzat i s'emprarà el fitxer d'índex anteri
> > or. Error del GPG: http://security.debian.org/debian-security
> > stretch/updates InRelease: Les signatures següents no s'han pogut verifi
> > car perquè la clau pública no està disponible: NO_PUBKEY
> > 9D6D8F6BC857C906 NO_PUBKEY 8B48AD6246925553
> > W: S'ha produït un error durant la verificació de la signatura. El
> > repositori no està actualitzat i s'emprarà el fitxer d'índex anteri
> > or. Error del GPG: http://ftp.es.debian.org/debian stretch Release: Les
> > signatures següents no s'han pogut verificar perquè la clau pú
> > blica no està disponible: NO_PUBKEY 8B48AD6246925553 NO_PUBKEY
> > 7638D0442B90D010 NO_PUBKEY CBF8D6FD518E17E1 NO_PUBKEY EF0F382A1A7B6500
> > W: S'ha produït un error durant la verificació de la signatura. El
> > repositori no està actualitzat i s'emprarà el fitxer d'índex anteri
> > or. Error del GPG: http://ftp.es.debian.org/debian stretch-updates
> > InRelease: Les signatures següents no s'han pogut verificar perquè
> > la clau pública no està disponible: NO_PUBKEY 8B48AD6246925553 NO_PUBKEY
> > 7638D0442B90D010
> > W: No s'ha pogut obtenir
> > http://security.debian.org/debian-security/dists/stretch/
> updates/InRelease
> >  Les signatures següents no s'han
> > pogut verificar perquè la clau pública no està disponible: NO_PUBKEY
> > 9D6D8F6BC857C906 NO_PUBKEY 8B48AD6246925553
> > W: No s'ha pogut obtenir
> > http://ftp.es.debian.org/debian/dists/stretch-updates/InRelease  Les
> > signatures següents no s'han pogut verif
> > icar perquè la clau pública no està disponible: NO_PUBKEY
> > 8B48AD6246925553 NO_PUBKEY 7638D0442B90D010
> > W: No s'ha pogut obtenir
> > http://ftp.es.debian.org/debian/dists/stretch/Release.gpg  Les
> > signatures següents no s'han pogut verificar p
> > erquè la clau pública no està disponible: NO_PUBKEY 8B48AD6246925553
> > NO_PUBKEY 7638D0442B90D010 NO_PUBKEY 

Re: System locks up while moving file

[Reco]

Hi.

On Sun, 25 Jun 2017 19:54:17 +1000
John Elliot V  wrote:

> There seems to be plenty of RAM available, and plenty of CPU. So must be
> some I/O thing..? Anyway, I'm a bit stumped. I haven't tried running the
> mv command with nice, because it doesn't seem to be a CPU thing... but
> maybe I should..? Anyone got any ideas about how to keep my system
> responsive while the mv command is processed?

A known problem aka Linux 12309 bug.

Try this:

sysctl -w vm.dirty_ratio=5
sysctl -w vm.dirty_background_ratio=5

If it helps, put these kernel tunables into /etc/sysctl.d somewhere.

Reco

Re: System locks up while moving file

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Sun, Jun 25, 2017 at 07:54:17PM +1000, John Elliot V wrote:
> Hey there. Maybe someone can help me with this.
> 
> I'm running Debian 9.0 (stretch). I have a few scripts which
> periodically create and then move a file from my 1TB M.2 drive to a MD
> RAID1 device comprised of 2x 6TB Seagate IronWolf drives. Full details
> are here [1].

[...]

> There seems to be plenty of RAM available, and plenty of CPU. So must be
> some I/O thing..? Anyway, I'm a bit stumped. I haven't tried running the
> mv command with nice, because it doesn't seem to be a CPU thing... but

You might try to play around with ionice. Something along the lines of

  ionice -c 3  mv /this/path /that/path

This would start the mv in the "idle" class (3), meaning it gets the
I/O breadcrumbs other processes leave on the table. More or less.

All of course untested. Consult the man page and move your pets to
a safe place first :)

Cheers
- -- tomás
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAllPjN8ACgkQBcgs9XrR2kbDNQCfY3LVfiYJ91Yz18quc56c98Zy
USQAnRITcx01FZnlPltPGg6xmCrR+qzE
=Q1vL
-END PGP SIGNATURE-

System locks up while moving file

[John Elliot V]

Hey there. Maybe someone can help me with this.

I'm running Debian 9.0 (stretch). I have a few scripts which
periodically create and then move a file from my 1TB M.2 drive to a MD
RAID1 device comprised of 2x 6TB Seagate IronWolf drives. Full details
are here [1].

My disks look something like this:

jj5@tact:~$ df -h
Filesystem  Size  Used Avail Use% Mounted on
/dev/md0469G   86G  378G  19% /
/dev/md15.5T  4.0T  1.6T  73% /data
/dev/nvme0n1p1  931G   78G  853G   9% /data/fast

An example of the move command which locks everything up is:

 mv /data/fast/temp/blob-tact.tgz \
/data/temp/blob-tact.tgz.8157-12003.tmp

So while this mv command is being processed my mouse doesn't respond, my
KDE Plasma session locks up, everything grinds to a halt.

There seems to be plenty of RAM available, and plenty of CPU. So must be
some I/O thing..? Anyway, I'm a bit stumped. I haven't tried running the
mv command with nice, because it doesn't seem to be a CPU thing... but
maybe I should..? Anyone got any ideas about how to keep my system
responsive while the mv command is processed?

Regards,
John Elliot V

[1] https://www.jj5.net/sixsigma/Workstation#Disk

-- 
E: j...@jj5.net
P: +61 4 3505 7839
W: https://www.jj5.net/
<>

Re: sftp en ligne de commande

[Étienne Mollier]

On 06/25/2017 11:44 AM, Erwan David wrote:
> Le 06/25/17 à 11:35, bernard.schoenac...@free.fr a écrit :
>> bonjour,
>>
>> je recherche un moyen d'employer sftp en ligne de commande
>> pour transférer des fichiers ...
>>
>> actuellement mc est inutilisable (segfault erreur -31) pour sftp
>>
>> en mode graphique j'emploie filezilla, mais quelles sont les solutions pour
>> soit télécharger ou téléverser ?
>>
>>
>> slt
>> bernard
>>
> 
> sftp tout simplement. (doit être dans openssh-client)
> Sinon lftp connaît le protocole aussi.
> 

Bonjour Bernard,

La commande `rsync` est aussi une solution valide.  La syntaxe
suivante utilisera le serveur SSH qui tourne sur l'hôte en
utilisant le protocole SFTP pour naviguer dans le système de
fichier (pas forcément très pratique, sans configuration adéquate,
il faut retaper le mot de passe à chaque exécution):

rsync hote:

Pour télécharger:

rsync -aSH hote:/source/fichier /cible/fichier
rsync -aSH hote:/source/repertoire/ /cible/repertoire/

Pour téléverser:

rsync -aSH /source/fichier hote:/cible/fichier
rsync -aSH /source/repertoire/ hote:/cible/repertoire/

Ce n'est pas la première commande qui vient en tête, mais elle
est assez pratique.  En prime, si les copies sont récurrentes,
sur la base de la date de dernière modification « mtime » de
chaque fichier, seuls ceux ayant été modifiés sont transférés.

À plus,
-- 
Étienne Mollier 

procés emacs fora de control

[Ernest Adrogué]

Hola,

Cada cop que instal·lo o desinstal·lo un paquet relacionat amb emacs,
per exemple maxima-emacs, en finalitzar l'apt-get em queda un procés
emacs funcionant amb utilització de CPU del 100%...

$ ps -eao pid,user,pcpu,comm | awk 'NR == 1 || /emacs/'
  PID USER %CPU COMMAND
 7483 root 89.6 emacs25

només para si mato el procés.  A algú més li passa?

Salut.

Re: sftp en ligne de commande

[Jean-Marc]

Sun, 25 Jun 2017 11:35:05 +0200 (CEST)
bernard.schoenac...@free.fr écrivait :

> bonjour,

salut Bernard,

> 
> je recherche un moyen d'employer sftp en ligne de commande
> pour transférer des fichiers ...

Il existe une commade .

> [...]
> slt
> bernard

Jean-Marc 


pgprgyI_XBgOf.pgp
Description: PGP signature

Re: sftp en ligne de commande

[Erwan David]

Le 06/25/17 à 11:35, bernard.schoenac...@free.fr a écrit :
> bonjour,
> 
> je recherche un moyen d'employer sftp en ligne de commande
> pour transférer des fichiers ...
> 
> actuellement mc est inutilisable (segfault erreur -31) pour sftp
> 
> en mode graphique j'emploie filezilla, mais quelles sont les solutions pour
> soit télécharger ou téléverser ?
> 
> 
> slt
> bernard
> 

sftp tout simplement. (doit être dans openssh-client)
Sinon lftp connaît le protocole aussi.

sftp en ligne de commande

[bernard . schoenacker]

bonjour,

je recherche un moyen d'employer sftp en ligne de commande
pour transférer des fichiers ...

actuellement mc est inutilisable (segfault erreur -31) pour sftp

en mode graphique j'emploie filezilla, mais quelles sont les solutions pour
soit télécharger ou téléverser ?


slt
bernard

Re: flash in stretch again

[Curt]

On 2017-06-24, Maureen L Thomas  wrote:
>
>
> It returns /usr/lib/flashplugin-nonfree/libflashplayer.so
> it also return one for gnash.  could this be the problem or confusion?
>
>

I think it is (although that path is compliant with the Debian wiki on
the matter). On my machine, 'about:plugins' reveals that Firefox-esr
searches the following paths for the flash plugin:

/usr/lib/mozilla/plugins/libflashplayer.so
and
/home/curty/.mozilla/plugins/libflashplayer.so

We could always experiment by copying the libflashplayer.so file as
indicated above (or merely into you're home directory) and then

update-alternatives --quiet --install /usr/lib/mozilla/plugins/flash-mozilla.so 
flash-mozilla.so /home/'your user name'/.mozilla/plugins/libflashplayer.so

However, I will now admit that I'm a little confused about the whole
deal. I do not use the flash-installer; I just go to Adobe and extract
the libflashplayer.so file from the tar.gz archive and copy it to both
/usr/lib/mozilla/plugins/libflashplayer.so and 
/home/curty/.mozilla/plugins/libflashplayer.so.

update-alternatives --list flash-mozilla.so 
returns
/home/curty/.mozilla/plugins/libflashplayer.so
/usr/lib/gnash/libgnashplugin.so

on my machine.

Good luck.






-- 
"It might be a vision--of a shell, of a wheelbarrow, of a fairy kingdom on the
far side of the hedge; or it might be the glory of speed; no one knew." --Mrs.
Ramsay, speculating on why her little daughter might be dashing about, in "To
the Lighthouse," by Virginia Woolf.

Re: Jessie --> Stretch upgrade, apt question

[Dejan Jocic]

On 25-06-17, Mark Fletcher wrote:
> Hello the list!
> 
> I have upgraded this weekend from Jessie to Stretch. All went, overall, 
> reasonably smoothly -- the documentation around releases is getting 
> better and better. I plan to write a full report of the upgrade and 
> share it here shortly. In the meantime I have one question.
> 
> It seems like aptitude is falling out of favour in stretch, and apt as a 
> command line tool as opposed to the name for the general entire package 
> management system is being recommended these days. I've never been a 
> huge fan of apt-get (although to be fair that means little more than I 
> settled on aptitude [command-line version not ncurses version] and 
> learned its quirks a long time ago) and so I am, somewhat reluctantly, 
> making the switch to apt from aptitude. apt has a couple of features I 
> really like, but I do wish apt show made it easier to tell if a package 
> is installed -- you have to read a lot further down the info to find 
> out.
> 
> My question is that since the upgrade chromium is held back from 
> upgrading, and in this new world I don't know how to find out why. In 
> aptitude I would have done aptitude why-not chromium and it would most 
> likely have told me something useful about its dependencies. How can I 
> get apt to do similar? Or what tool should I use?
> 
> I'm aware that apt-cache depends chromium will tell me what it depends 
> on, but that doesn't tell me what is stopping it from being upgraded.
> 
> sudo apt upgrade and sudo apt full-upgrade both just tell me chromium 
> has been kept back, but not why.
> 
> sudo apt --fix-broken install finds nothing to do.
> 
> Suggestions would be much appreciated.
> 
> Mark
> 

In short, use aptitude for why and why-not. Closest thing apt-get and
friends have would be apt-cache --important depends/rdepends. But,
aptitude is much better suited for that task. And for all other tasks
that involve advanced searching, as far as I could tell. As for apt
itself, would not know exactly, I refuse to use tool with man page that
treats me like an idiot, while not giving me anything new and important
compared to apt-get and friends. But guess would be that it is apt
--important depends/rdepends. And probably not more helpful than
apt-cache variant.

Re: apt-get upgrade problem

[Curt]

On 2017-06-25, David Wright  wrote:
> On Thu 22 Jun 2017 at 19:44:27 (+), Curt wrote:
>> On 2017-06-22, Mike McClain  wrote:
>> >
>> > Rather than telling me why FF was held back it just went ahead and
>> > installed it.
>> >
>> 
>> Is that the complete description of what you observed? You're not
>> leaving anything out, are you? 
>> 
>> -- 
>> "It might be a vision--of a shell, of a wheelbarrow, of a fairy kingdom on 
>> the
>> far side of the hedge; or it might be the glory of speed; no one knew."
>
> It doesn't seem likely that any of those would appear.

What?

> I think perhaps you're soliciting remarks re "It should tell you why
> it's held back." Is that going to happen when you install rather than
> upgrade? I thought it would take "install" as an instruction to include
> all the dependencies automatically (and mark them so).

No, it is not automatic. For instance in my case, on Wheezy, apt held
firefox-esr back because it will not install an extra package unless
explicitly given permission to do so. This was revealed when I
executed the 'apt-get install firefox-esr' command, at which point apt
asked me to reply yes or no to the installation of a new package (the
name of which escapes me) and the updating of the package firefox-esr.

Because of the pedagogical interest of the thing, for those who come
after us, for posterity's sake, I wanted the OP to give us a complete
description of what occurred, rather than a misleading one (for we are
left wondering why FF was held back in the first place, if an 'apt-get
install' simply "went ahead and installed it."

> Cheers,
> David.
>
>


-- 
"It might be a vision--of a shell, of a wheelbarrow, of a fairy kingdom on the
far side of the hedge; or it might be the glory of speed; no one knew." --Mrs.
Ramsay, speculating on why her little daughter might be dashing about, in "To
the Lighthouse," by Virginia Woolf.

Re: WLAN laufende Qualitaetsmessung

[Hans]

I read the original post now (in German, and as I am German, no problem).
In his case I think "kismet" is a good start. So he can see, if there are 
other AP on the same frequency. I also suggest "wavemon", which shows all AP 
and its strenth.

If the neighbour is sending weired pckages (maybe with aireplay-ng, who 
knows), then wireshark or tshark is working fine for it. Also you have then 
evidence for his doings, which is illegal (here in Germany). 

Maybe also the package "horst" is also helpful, which is designed for excactly 
these issues: check your traffic. (I have never used it for now).

Hope this helps

Best regards

Hans

Re: WLAN laufende Qualitaetsmessung

[Thomas Schmitt]

Hi,

Reco wrote:
> Using aireplay-ng for the purpose of lowering signal quality
> for neighbor WiFi can be subject to criminal penalties

That would be a good catch in a neighborhood feud which normally is
rather faught by unnecessary lawn mowing, loud music, stinking garbage
cans, or obscene garden gnomes. (The use of song loving roosters is
widely banned.)

I rather imagined a radio noise generator like
  
https://commons.wikimedia.org/wiki/File:BWB_23342_ARTUS_Radaranlage_Typ_ME_0632.jpg


Have a nice day :)

Thomas

Jessie --> Stretch upgrade, apt question

[Mark Fletcher]

Hello the list!

I have upgraded this weekend from Jessie to Stretch. All went, overall, 
reasonably smoothly -- the documentation around releases is getting 
better and better. I plan to write a full report of the upgrade and 
share it here shortly. In the meantime I have one question.

It seems like aptitude is falling out of favour in stretch, and apt as a 
command line tool as opposed to the name for the general entire package 
management system is being recommended these days. I've never been a 
huge fan of apt-get (although to be fair that means little more than I 
settled on aptitude [command-line version not ncurses version] and 
learned its quirks a long time ago) and so I am, somewhat reluctantly, 
making the switch to apt from aptitude. apt has a couple of features I 
really like, but I do wish apt show made it easier to tell if a package 
is installed -- you have to read a lot further down the info to find 
out.

My question is that since the upgrade chromium is held back from 
upgrading, and in this new world I don't know how to find out why. In 
aptitude I would have done aptitude why-not chromium and it would most 
likely have told me something useful about its dependencies. How can I 
get apt to do similar? Or what tool should I use?

I'm aware that apt-cache depends chromium will tell me what it depends 
on, but that doesn't tell me what is stopping it from being upgraded.

sudo apt upgrade and sudo apt full-upgrade both just tell me chromium 
has been kept back, but not why.

sudo apt --fix-broken install finds nothing to do.

Suggestions would be much appreciated.

Mark

Re: WLAN laufende Qualitaetsmessung

[Reco]

Hi.

On Sun, 25 Jun 2017 10:06:38 +0200
Hans  wrote:

> I believe tshark (and wireshark of course) is also be capable of showing bad 
> or corrupted traffic. You can set filters, i.e. to filter out rejects and 
> similar, 
> and if they are abnormal high, you know, something is bad.
> 
> Just an idea...

It's complex at best. While tshark, wireshark or plain tcpdump can be
used for this purpose, it would take a non-trivial post-processing to
show signal quality/junk ratio grouped by APs.

An invocation of 'airmon-ng wlan0' is much simpler IMO.


Of course, if neighbor in question actually managed to connect to OP's
APs, and wreaking havoc from inside the OP's LAN - then wireshark would
be priceless.

Reco

Re: WLAN laufende Qualitaetsmessung

[Hans]

I believe tshark (and wireshark of course) is also be capable of showing bad 
or corrupted traffic. You can set filters, i.e. to filter out rejects and 
similar, 
and if they are abnormal high, you know, something is bad.

Just an idea...

Best 

Hans

Re: WLAN laufende Qualitaetsmessung

[Reco]

On Sun, 25 Jun 2017 11:00:28 +0300
Reco  wrote:

>   Hi.
> 
> On Sun, 25 Jun 2017 09:36:57 +0200
> "Thomas Schmitt"  wrote:
> 
> > Hi,
> > 
> > debian-user ist englischsprachig. Probier's mal auf dem deutschen Ableger:
> >   debian-user-ger...@lists.debian.org
> > 
> > 
> > Just in case somebody knows a program for WLAN quality surveillance:
> > 
> > The OP suspects that his neighbor after annoying the dogs has now
> > taken measures to hamper the WLAN. The question is whether there are
> > programs which can diagnose WLAN quality problems and identify potential
> > causes.
> 
> airodump-ng from aircrack-ng will solve this with ease.
> kismet will too.
> 
> Just observe which WiFi channels are most crowded and switch own
> Access Point (s) to a least crowded one.
> 
> Repeat as needed.

Followup. Using aireplay-ng for the purpose of lowering signal quality
for neighbor WiFi can be subject to criminal penalties and therefore is
not recommended.

Reco

Re: WLAN laufende Qualitaetsmessung

[Reco]

Hi.

On Sun, 25 Jun 2017 09:36:57 +0200
"Thomas Schmitt"  wrote:

> Hi,
> 
> debian-user ist englischsprachig. Probier's mal auf dem deutschen Ableger:
>   debian-user-ger...@lists.debian.org
> 
> 
> Just in case somebody knows a program for WLAN quality surveillance:
> 
> The OP suspects that his neighbor after annoying the dogs has now
> taken measures to hamper the WLAN. The question is whether there are
> programs which can diagnose WLAN quality problems and identify potential
> causes.

airodump-ng from aircrack-ng will solve this with ease.
kismet will too.

Just observe which WiFi channels are most crowded and switch own
Access Point (s) to a least crowded one.

Repeat as needed.

Reco

Re: WLAN laufende Qualitaetsmessung

[Thomas Schmitt]

Hi,

debian-user ist englischsprachig. Probier's mal auf dem deutschen Ableger:
  debian-user-ger...@lists.debian.org


Just in case somebody knows a program for WLAN quality surveillance:

The OP suspects that his neighbor after annoying the dogs has now
taken measures to hamper the WLAN. The question is whether there are
programs which can diagnose WLAN quality problems and identify potential
causes.


Have a nice day :)

Thomas

Re: (deb-cat) sources.list i base.list

[Narcis Garcia]

Prova a veure què et surt amb la comanda:

$ find /etc/apt


__
I'm using this express-made address because personal addresses aren't
masked enough at this list's archives. Mailing lists service
administrator should fix this.
El 24/06/17 a les 20:39, Jordi Boixader ha escrit:
> Ara encara surten mes W:
> 
> 
> root@debian9:/etc/apt# apt-get update
> Ign:1 http://ftp.es.debian.org/debian stretch InRelease
> Obj:2 http://security.debian.org/debian-security stretch/updates InRelease
> Obj:4 http://ftp.es.debian.org/debian stretch Release
> Bai:3 http://ftp.es.debian.org/debian stretch-updates InRelease [88,5 kB]
> Err:2 http://security.debian.org/debian-security stretch/updates InRelease
>  Les signatures següents no s'han pogut verificar perquè la clau pública
> no està disponible: NO_PUBKEY 9D6D8F6BC857C906 NO_PUBKEY 8B4
> 8AD6246925553
> Err:5 http://ftp.es.debian.org/debian stretch Release.gpg
>  Les signatures següents no s'han pogut verificar perquè la clau pública
> no està disponible: NO_PUBKEY 8B48AD6246925553 NO_PUBKEY 763
> 8D0442B90D010 NO_PUBKEY CBF8D6FD518E17E1 NO_PUBKEY EF0F382A1A7B6500
> Err:3 http://ftp.es.debian.org/debian stretch-updates InRelease
>  Les signatures següents no s'han pogut verificar perquè la clau pública
> no està disponible: NO_PUBKEY 8B48AD6246925553 NO_PUBKEY 763
> 8D0442B90D010
> S'ha baixat 88,5 kB en 0s (89,3 kB/s)
> S'està llegint la llista de paquets… Fet
> W: S'ha produït un error durant la verificació de la signatura. El
> repositori no està actualitzat i s'emprarà el fitxer d'índex anteri
> or. Error del GPG: http://security.debian.org/debian-security
> stretch/updates InRelease: Les signatures següents no s'han pogut verifi
> car perquè la clau pública no està disponible: NO_PUBKEY
> 9D6D8F6BC857C906 NO_PUBKEY 8B48AD6246925553
> W: S'ha produït un error durant la verificació de la signatura. El
> repositori no està actualitzat i s'emprarà el fitxer d'índex anteri
> or. Error del GPG: http://ftp.es.debian.org/debian stretch Release: Les
> signatures següents no s'han pogut verificar perquè la clau pú
> blica no està disponible: NO_PUBKEY 8B48AD6246925553 NO_PUBKEY
> 7638D0442B90D010 NO_PUBKEY CBF8D6FD518E17E1 NO_PUBKEY EF0F382A1A7B6500
> W: S'ha produït un error durant la verificació de la signatura. El
> repositori no està actualitzat i s'emprarà el fitxer d'índex anteri
> or. Error del GPG: http://ftp.es.debian.org/debian stretch-updates
> InRelease: Les signatures següents no s'han pogut verificar perquè
> la clau pública no està disponible: NO_PUBKEY 8B48AD6246925553 NO_PUBKEY
> 7638D0442B90D010
> W: No s'ha pogut obtenir
> http://security.debian.org/debian-security/dists/stretch/updates/InRelease
>  Les signatures següents no s'han
> pogut verificar perquè la clau pública no està disponible: NO_PUBKEY
> 9D6D8F6BC857C906 NO_PUBKEY 8B48AD6246925553
> W: No s'ha pogut obtenir
> http://ftp.es.debian.org/debian/dists/stretch-updates/InRelease  Les
> signatures següents no s'han pogut verif
> icar perquè la clau pública no està disponible: NO_PUBKEY
> 8B48AD6246925553 NO_PUBKEY 7638D0442B90D010
> W: No s'ha pogut obtenir
> http://ftp.es.debian.org/debian/dists/stretch/Release.gpg  Les
> signatures següents no s'han pogut verificar p
> erquè la clau pública no està disponible: NO_PUBKEY 8B48AD6246925553
> NO_PUBKEY 7638D0442B90D010 NO_PUBKEY CBF8D6FD518E17E1 NO_PUBKEY E
> F0F382A1A7B6500
> W: Alguns índex no s'han pogut baixar. S'han descartat, o en el seu lloc
> s'han emprat els antics.
> 
> 
> Poc que en sé... i cada vegada ho compliquen més XDDD
> 
> 
> El dia 24 de juny de 2017 a les 19:25, Narcis Garcia
> > ha escrit:
> 
> Doncs semblaria tenir relació (o més aviat semblança), perquè a Debian 8
> ja semblarien haver-se eliminat /etc/apt/trustdb.gpg i
> /etc/apt/trusted.gpg i només deixat fitxers a /etc/apt/trusted.gpg.d/
> 
> Si tens un fitxer /etc/apt/trusted.gpg jo provaria a donar-li permisos
> de lectura per tothom:
> $ sudo chmod a+r /etc/apt/trusted.gpg
> I si no el tens m'estranya perquè jo he provat un apt-get update en un
> «Live» sense el fitxer i no es queixa.
> 
> 
> __
> I'm using this express-made address because personal addresses aren't
> masked enough at this list's archives. Mailing lists service
> administrator should fix this.
> El 24/06/17 a les 15:45, Jordi Boixader ha escrit:
> > No se si és un Off-topic...
> >
> > A mi, un cop instal·lat de cero si vaig al Gestor de programari
> (apper)
> > a Opcions, Origen de programari, i marco els contrib i non-free, els
> > Security updates i Recommended updates, i em deixa el seguent
> sources.list
> >
> > deb  http://ftp.es.debian.org/debian/
>  stretch main contrib non-free
> > deb-scr http://ftp.es.debian.org/debian/
>  stretch main contrib 

Re: ponto de montagem

[André]

Mude a permissão depois que o dispositivo estiver montado. Dessa forma ficará 
permanente e não será necessário utilizar parâmetros.

On Tue, 20 Jun 2017 14:58:11 -0300
Caio Ferreira  wrote:

> Prezado Ricardo
> 
> Se por acaso eu monto utilizando o comando abaixo, funciona normalmente.
> 
> sudo mount -o gid=users,fmask=113,dmask=002 /dev/sdc1 /mnt/usb/
> 
> No caso, eu estou forçando a mascara em relação ao arquivo e diretorio. Eu
> nunca precisei fazer isso.
> 
> Desde já obrigado.
> 
>  .''`.   Caio Abreu Ferreira
> : :'  :  abreuf...@gmail.com
> `. `'`   Debian User
>   `-
> 
> 2017-06-20 14:38 GMT-03:00 Ricardo Ramos :
> 
> > Boa noite Caio,
> >
> > Isso acontece com outros dispositivos?
> >
> > Quando você monta outros dispositivos o user e grupo root ficam com as
> > permissões?
> >
> > Caso tenha necessidade de montar o sistema de arquivos com um
> > grupo/utilizador específico tente utilizar a opção "gid" ou "uid"
> >
> > Ex: # mount -t fat32 -o gui=500 /Dev/sdc1 /mnt/USB
> >
> > Espero ter ajudado.
> > Um abraço
> >
> > A Ter, 20 de jun de 2017, 18:25, Caio Ferreira 
> > escreveu:
> >
> >> Lista
> >>
> >> Eu estou utilizando a versão 8.8 do Debian.
> >>
> >> Esta ocorrendo algo estranho com o diretorio que eu utilizo para montar
> >> o meu pendrive.
> >>
> >> # visualizar permissao
> >> #
> >> cosmo@workstation:~$ ls -l /mnt/
> >> drwxrwxr-x 2 root users 4096 Jun 19 15:07 usb
> >>
> >> O usuario é "root" e o grupo é "users".
> >>
> >> # comando para montar
> >> #
> >> cosmo@workstation:~$ sudo mount /dev/sdc1 /mnt/usb/
> >>
> >> # visualizar permissao
> >> #
> >> cosmo@workstation:~$ ls -l /mnt/
> >> drwxr-xr-x 6 root root  4096 Dec 31  1969 usb
> >>
> >> O usuario é "root" e o grupo é "root".
> >>
> >> cosmo@workstation:~$ sudo umount /mnt/usb/
> >> cosmo@workstation:~$ ls -l /mnt/
> >> drwxrwxr-x 2 root users 4096 Jun 20 14:15 usb
> >>
> >> Depois que eu desmonto o dispositivo, volta para o normal.
> >>
> >> Eu já utilizei o cmod e o chown para fazer as devidas alterações
> >> mas não surte nenhum tipo de efeito.
> >>
> >> Por acaso alguem teria alguma ideia do que esta ocorrendo?
> >>
> >> Desde já obrigado,
> >>
> >>  .''`.   Caio Abreu Ferreira
> >> : :'  :  abreuf...@gmail.com
> >> `. `'`   Debian User
> >>   `-
> >>
> > --
> >
> > Ricardo Ramos
> > Tel: +244 927 953 770
> > Email: cesar.ricki...@gmail.com
> > Website: www.rickinho.com
> > Técnico de Informática
> >


-- 
André