Re: graphic tablet controls

[Bruce Byfield]

"how recent a kernel do you have?  what version of
Debian are you on?  what desktop?"

I'm running stretch, using a 4.9.0-6 kernel. The problem exists on all
the major desktops including GNOME, KDE, Cinammon, and LXDE, so the
problem is unlikely to be the desktop

"First of all check if your Wacom device is supported by linux - not
all of them are.

For more check here

https://www.reddit.com/r/linuxquestions/comments/3yfz1v/wacom_intuos_draw_and_linux/";

Thanks for the link, but I already know that the Intuos Draw is
supported at least partially, because I am using it as a mouse
replacement, and stretch detects it. The question is why the desktop
tools can't detect it.

I found some information on the Arch website that didn't directly help
me (https://wiki.archlinux.org/index.php/Wacom_tablet), but it does
suggest that /dev/input/wacom should have been created -- which, on my
system, didn't happen. Any idea if that file could be created manually
-- and, if so, how?



The Intuos Draw is clearly supported to a degree, because I am using
it as a replacement.

o ___o
Bruce Byfield (on Pacific time) 604-421-7189
Writer of "Designing with LibreOffice"
www.designingwithlibreoffice.com

Re: SSD's and many edits of a single file

[David Christensen]

On 04/09/18 20:58, Gene Heskett wrote:

On Monday 09 April 2018 21:25:34 David Christensen wrote:


On 04/09/18 07:30, Gene Heskett wrote:

On Monday 09 April 2018 09:51:37 Greg Wooledge wrote:

On Mon, Apr 09, 2018 at 09:46:07AM -0400, rhkra...@gmail.com

wrote:

To your original problem, have you tried going to a command line
and throwing in a couple =sync=s?  I would try that, maybe after
saving in your editor, and again maybe after open and / or saving
in the cnc program.


As others have explained, the OS (Linux) keeps a cache of file
contents that have been written by applications, but not yet
committed to permanent storage.  If you "save" from within the text
editor, then the saved contents should be immediately visible to
other processes reading the file, regardless of whether it has been
synced to disk. They'll simply get the cached version.


Which is not happening after several hours and a hundred or more
edits. Which is why its so intermittent.


On 04/09/18 02:53, Gene Heskett wrote:

Lots of people seem to like gedit, but its saves are the cause of
important configuration files being written back to disk with the
line order totally trashed, as if you had thrown it on the floor in
512 byte pieces, then picked it back up and reassembled it in random
order. Then try to recover a 1400 LOC configuration file...

Thats happened using gedit enough, on several different machines ...


One editor failing would also make me suspect the editor.


But two failing editors would make me suspect some common factor, such
as a shared library and/or the kernel.


I'd buy that if the failures were similar.  They are not.


They both seem to involve getting blocks from an app to memory and 
blocks from memory to disk (and/or disk to memory).  They could be 
variations on a theme.



Can you reproduce the bugs on a machine with straight-up Debian (e.g. no 
linuxcnc)?



As a safety net, I would suggest a versioning file system (e.g. similar 
to the versioning feature of VMS).  STFW is pretty thin, but copyfs 
might be worth a try:


https://packages.debian.org/search?keywords=copyfs&searchon=names&suite=all§ion=all


David

Re: No sound in Debian Stretch

[deloptes]

Daniel Bareiro wrote:

> Hi, deloptes.
> 
> On 10/04/18 19:36, deloptes wrote:
> 
>>> Has anyone experienced something like that and has some clue how to fix
>>> it?
> 
>> try
>> alsamixer -c0
>> or
>> amixer -c0
>> and see if something is muted there
>> usually 0 is the alsacard driver - it might be other index for you though
> 
...
> 
> I was also looking at the settings with the ncurses interface provided
> by "alsamixer -c0". "Master", "PCM" and "Speaker" is at maximum, unless
> I'm missing something. Here some screenshots:
> 
> https://ibin.co/3xx7l69DriYy.png
> https://ibin.co/3xx8ERkqHJwW.png
> https://ibin.co/3xx8ac8djtS4.png
> 
> I also tried setting "Internal" to the maximum, but it made no difference.
> 

Automute is enabled - this means when you plug in headphone, speaker is
turned off
Headphone is also muted - no sound

strange that you mention you have no sound at all - without headphones
plugged, it should work.
check also the pavucontrol settings in both cases (the icons for default
device etc)

If nothing helps remove ~/.pulse directory and reboot or login again or kill
pulse server (it should respawn)

regards

Re: No sound in Debian Stretch

[Daniel Bareiro]

Hi, Ben.

On 10/04/18 19:51, Ben Caradoc-Davies wrote:
> On 11/04/18 10:15, Daniel Bareiro wrote:
>>  From one day to the next I ran out of sound in Debian Stretch. It's
>> strange because I don't remember making any changes and everything was
>> running without problem.
>> I installed pavucontrol to see if there is something muted, but that
>> does not seem to be the case. For example when I am playing a Youtube
>> video, in "Firefox: Audiostream" and in "Output devices" (I'm not sure
>> if that's what it says in the English version because I have the
>> interface in Spanish here) I see how the bottom bar fluctuates as if it
>> was reproducing something, but I am not able to hear any sound neither
>> by the speakers nor by the headset.
>> Has anyone experienced something like that and has some clue how to
>> fix it?

> Did the problem start when you plugged in your headset? What happens if
> you unplug your headset? Do you get sound from your speakers? How are
> your speakers connected? Is this a laptop? I have had a laptop with an
> Intel chipset for which headphone autoswitching was broken. I ended up
> disabling (commenting out) the switch-on-port-available module in
> /etc/pulse/default.pa .
> 
> On my current disktop chipset, my headset is detected as line out (not
> headphones). I am using "Analog Stereo Duplex" in Configuration and
> "Line Out" in "Output Devices". Do you have any HDMI devices connected
> or listed as Configuration options?

The computer where I am having this problem is a Thinkpad T530 notebook.
I'm not getting sound at all, whether I have the headset plugged in or not.

Until a few days ago it was working without problems. I don't remember
exactly when I started to experience this. If it was after return the
notebook from sleeping state or at some other time.

This notebook does not have any HDMI port.

Thanks for your interest.

Kind regards,
Daniel



signature.asc
Description: OpenPGP digital signature

Re: No sound in Debian Stretch

[Daniel Bareiro]

Hi, deloptes.

On 10/04/18 19:36, deloptes wrote:

>> Has anyone experienced something like that and has some clue how to fix
>> it?

> try
> alsamixer -c0
> or
> amixer -c0
> and see if something is muted there
> usually 0 is the alsacard driver - it might be other index for you though

This is the output I get with "amixer -c0":

-
Simple mixer control 'Master',0
  Capabilities: pvolume pvolume-joined pswitch pswitch-joined
  Playback channels: Mono
  Limits: Playback 0 - 87
  Mono: Playback 87 [100%] [0.00dB] [on]
Simple mixer control 'Headphone',0
  Capabilities: pvolume pswitch
  Playback channels: Front Left - Front Right
  Limits: Playback 0 - 87
  Mono:
  Front Left: Playback 0 [0%] [-65.25dB] [off]
  Front Right: Playback 0 [0%] [-65.25dB] [off]
Simple mixer control 'Headphone',1
  Capabilities: pswitch
  Playback channels: Front Left - Front Right
  Mono:
  Front Left: Playback [on]
  Front Right: Playback [on]
Simple mixer control 'Speaker',0
  Capabilities: pvolume pswitch
  Playback channels: Front Left - Front Right
  Limits: Playback 0 - 87
  Mono:
  Front Left: Playback 87 [100%] [0.00dB] [on]
  Front Right: Playback 87 [100%] [0.00dB] [on]
Simple mixer control 'PCM',0
  Capabilities: pvolume
  Playback channels: Front Left - Front Right
  Limits: Playback 0 - 255
  Mono:
  Front Left: Playback 255 [100%] [0.00dB]
  Front Right: Playback 255 [100%] [0.00dB]
Simple mixer control 'Mic',0
  Capabilities: pvolume pswitch
  Playback channels: Front Left - Front Right
  Limits: Playback 0 - 31
  Mono:
  Front Left: Playback 31 [100%] [12.00dB] [off]
  Front Right: Playback 31 [100%] [12.00dB] [off]
Simple mixer control 'Mic Boost',0
  Capabilities: volume
  Playback channels: Front Left - Front Right
  Capture channels: Front Left - Front Right
  Limits: 0 - 3
  Front Left: 0 [0%] [0.00dB]
  Front Right: 0 [0%] [0.00dB]
Simple mixer control 'IEC958',0
  Capabilities: pswitch pswitch-joined
  Playback channels: Mono
  Mono: Playback [off]
Simple mixer control 'IEC958',1
  Capabilities: pswitch pswitch-joined
  Playback channels: Mono
  Mono: Playback [on]
Simple mixer control 'IEC958',2
  Capabilities: pswitch pswitch-joined
  Playback channels: Mono
  Mono: Playback [on]
Simple mixer control 'Beep',0
  Capabilities: pvolume pswitch
  Playback channels: Front Left - Front Right
  Limits: Playback 0 - 31
  Mono:
  Front Left: Playback 0 [0%] [-34.50dB] [off]
  Front Right: Playback 0 [0%] [-34.50dB] [off]
Simple mixer control 'Capture',0
  Capabilities: cvolume cswitch
  Capture channels: Front Left - Front Right
  Limits: Capture 0 - 63
  Front Left: Capture 63 [100%] [30.00dB] [on]
  Front Right: Capture 63 [100%] [30.00dB] [on]
Simple mixer control 'Auto-Mute Mode',0
  Capabilities: enum
  Items: 'Disabled' 'Enabled'
  Item0: 'Enabled'
Simple mixer control 'Digital',0
  Capabilities: cvolume
  Capture channels: Front Left - Front Right
  Limits: Capture 0 - 120
  Front Left: Capture 120 [100%] [30.00dB]
  Front Right: Capture 120 [100%] [30.00dB]
Simple mixer control 'Dock Mic',0
  Capabilities: pvolume pswitch
  Playback channels: Front Left - Front Right
  Limits: Playback 0 - 31
  Mono:
  Front Left: Playback 31 [100%] [12.00dB] [off]
  Front Right: Playback 31 [100%] [12.00dB] [off]
Simple mixer control 'Dock Mic Boost',0
  Capabilities: volume
  Playback channels: Front Left - Front Right
  Capture channels: Front Left - Front Right
  Limits: 0 - 3
  Front Left: 0 [0%] [0.00dB]
  Front Right: 0 [0%] [0.00dB]
Simple mixer control 'Internal Mic Boost',0
  Capabilities: volume
  Playback channels: Front Left - Front Right
  Capture channels: Front Left - Front Right
  Limits: 0 - 3
  Front Left: 0 [0%] [0.00dB]
  Front Right: 0 [0%] [0.00dB]
Simple mixer control 'Loopback Mixing',0
  Capabilities: enum
  Items: 'Disabled' 'Enabled'
  Item0: 'Disabled'
-

I was also looking at the settings with the ncurses interface provided
by "alsamixer -c0". "Master", "PCM" and "Speaker" is at maximum, unless
I'm missing something. Here some screenshots:

https://ibin.co/3xx7l69DriYy.png
https://ibin.co/3xx8ERkqHJwW.png
https://ibin.co/3xx8ac8djtS4.png

I also tried setting "Internal" to the maximum, but it made no difference.


Thanks for your reply.

Kind regards,
Daniel



signature.asc
Description: OpenPGP digital signature

Status of Intel-related vulnerabilities and bugs?

[Niclas Arndt]

Hello,

I'm trying to get my head around all the recent Intel-related vulnerabilities 
and bugs and what they mean for the practical usefulness of my not-so-old and 
still under warranty motherboards in the role of a secure Debian internet 
server.

I have spent quite some time googling for both information about the technical 
problems and also what the motherboard manufacturers have done and plan to do 
about it.

It seems that many have rolled out BIOS updates for their 100-300 and x99-299 
series motherboards (Intel Management Engine (IME), hyperthreading, and Spectre 
variant 2).

For older motherboards there is a lot more uncertainty. ASRock (but not 
Gigabyte, ASUS, nor MSI) has released H97 / Z97 BIOS updates to Haswell CPU 
Microcode revision 24 and Broadwell revision 1D, but no update for IME. 
Gigabyte hasn't responded to my support request regarding their plans for 
97-series and older motherboards.

I have applied the Linux "microcode updated early" firmware from 
stretch-backports (https://wiki.debian.org/Microcode), but that leaves me with 
a few questions:

1. Can the latest microcode updates still in stretch-backports be trusted to 
run properly by now?
https://newsroom.intel.com/wp-content/uploads/sites/11/2018/04/microcode-update-guidance.pdf

2. What is really the deal with IME on pre 100-series motherboards? According 
to the "GIGABYTE Intel ME Critical FW Update Utility" there is "no need" to 
update my H97N-WIFI motherboards, but the "Intel-SA-00086 Detection Tool" says 
my Windows 7 machine is vulnerable. Some sources claim that certain consumer 
motherboards are indeed vulnerable to the IME holes. As far as I understand, 
the H97 and Z97 chipsets don't have vPro support (which I suppose means that 
AMT is not implemented?), but some motherboards were instead designed with 
Intel Small Business Advantage (SBA). For example, the Gigabyte H97N-WIFI / 
Z97N-WIFI boards have SBA support, but the ASRock H97E-ITX/ac / Z97E-ITX/ac 
don't, but does this mean that the Gigabyte boards are vulnerable but not the 
ASRock boards?
https://www.gigabyte.com/Support/Utility/Motherboard#mefw
https://www.intel.com/content/www/us/en/support/articles/25619/software.html

3. Assuming that the H97 / Z97 motherboards with SBA are vulnerable to the IME 
hole, what can be done to prevent exploits?

4. Has Microsoft decided only to apply their equivalent of the "microcode 
updated early" firmware to the latest version of Windows 10, leaving the still 
supported Windows 7 and 8.x with the Spectre 2 security hole?

Grateful for your input.

BR

Niclas

Re: transfer disk

[Felix Miata]

Pascal Hambourg composed on 2018-04-10 20:47 (UTC+0200):

> Felix Miata composed:

>> Putting a disk from an Intel system into a system with AMD, VIA or GeForce
>> chipset is almost certain to fail unless the initrd includes most drivers.

> This is the default (MODULES=most).

Likely it's one of the first things to go when someone wants to trim
installation size or speed up booting and/or updating.

>> This
>> leads me to believe that a minimal module set initrd created on one chipset 
>> type
>> and tried on any other chipset type is mostly likely doomed.

> Not if both chipsets use the same module. E.g. all SATA host controllers 
> in AHCI mode use the same ahci module regardless of the manufacturer.

I've seen a lot of BIOS since AHCI became commonplace where the string "AHCI" is
nowhere to be found in BIOS setup or motherboard or PC manual.
-- 
"Wisdom is supreme; therefore get wisdom. Whatever else you
get, get wisdom." Proverbs 4:7 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

Re: No sound in Debian Stretch

[Ben Caradoc-Davies]

On 11/04/18 10:15, Daniel Bareiro wrote:

 From one day to the next I ran out of sound in Debian Stretch. It's
strange because I don't remember making any changes and everything was
running without problem.
I installed pavucontrol to see if there is something muted, but that
does not seem to be the case. For example when I am playing a Youtube
video, in "Firefox: Audiostream" and in "Output devices" (I'm not sure
if that's what it says in the English version because I have the
interface in Spanish here) I see how the bottom bar fluctuates as if it
was reproducing something, but I am not able to hear any sound neither
by the speakers nor by the headset.
Has anyone experienced something like that and has some clue how to fix it?


Did the problem start when you plugged in your headset? What happens if 
you unplug your headset? Do you get sound from your speakers? How are 
your speakers connected? Is this a laptop? I have had a laptop with an 
Intel chipset for which headphone autoswitching was broken. I ended up 
disabling (commenting out) the switch-on-port-available module in 
/etc/pulse/default.pa .


On my current disktop chipset, my headset is detected as line out (not 
headphones). I am using "Analog Stereo Duplex" in Configuration and 
"Line Out" in "Output Devices". Do you have any HDMI devices connected 
or listed as Configuration options?


Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

Re: No sound in Debian Stretch

[deloptes]

Daniel Bareiro wrote:

> Has anyone experienced something like that and has some clue how to fix
> it?

try
alsamixer -c0
or
amixer -c0
and see if something is muted there
usually 0 is the alsacard driver - it might be other index for you though

regards

Re: graphic tablet controls

[deloptes]

Bruce Byfield wrote:

> I recently started using a Wacom Intuos Draw tablet. Its functions as a
> mouse substitute are available as soon as I plug it in, and the
> device is detected by the operating system. However, the tools
> available in desktop environments for configuring buttons and drawing
> functions don't detect the tablet, even though I can use the stylus in
> the testing area for the tools. Nor does xsetwacom work from the command
> line.
> 
> I have built and install the latest kernel modules for the tablet, and
> added the appropriate lines in xorg.conf. Neither has any noticeable
> effect. I have consulted the Debian wiki, as well as the Llinux Wacom
> project, but nothing changes the situation. Any idea where to go from
> here?

Hi,
First of all check if your Wacom device is supported by linux - not all of
them are.

For more check here

https://www.reddit.com/r/linuxquestions/comments/3yfz1v/wacom_intuos_draw_and_linux/

Re: No sound in Debian Stretch

[Michael Lange]

Hi,

On Tue, 10 Apr 2018 19:15:35 -0300
Daniel Bareiro  wrote:

> Hi all!
> 
> From one day to the next I ran out of sound in Debian Stretch. It's
> strange because I don't remember making any changes and everything was
> running without problem.
> 
> I installed pavucontrol to see if there is something muted, but that
> does not seem to be the case. For example when I am playing a Youtube
> video, in "Firefox: Audiostream" and in "Output devices" (I'm not sure
> if that's what it says in the English version because I have the
> interface in Spanish here) I see how the bottom bar fluctuates as if it
> was reproducing something, but I am not able to hear any sound neither
> by the speakers nor by the headset.
> 
> Has anyone experienced something like that and has some clue how to fix
> it?

here it has happened that pulseaudio changed its output from analog out
to hdmi without myself doing anything about it. For me it worked in such
cases to start pasystray, click on the tray icon to open the menu and go
to "Default sink" and change it back to the analog output.

Of course, this is just a shot into the dark, your problem might be
something entirely different.

Best regards,

Michael


.-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.

Intuition, however illogical, is recognized as a command prerogative.
-- Kirk, "Obsession", stardate 3620.7

No sound in Debian Stretch

[Daniel Bareiro]

Hi all!

From one day to the next I ran out of sound in Debian Stretch. It's
strange because I don't remember making any changes and everything was
running without problem.

I installed pavucontrol to see if there is something muted, but that
does not seem to be the case. For example when I am playing a Youtube
video, in "Firefox: Audiostream" and in "Output devices" (I'm not sure
if that's what it says in the English version because I have the
interface in Spanish here) I see how the bottom bar fluctuates as if it
was reproducing something, but I am not able to hear any sound neither
by the speakers nor by the headset.

Has anyone experienced something like that and has some clue how to fix it?


Thanks in advance.

Kind regards,
Daniel



signature.asc
Description: OpenPGP digital signature

Re: graphic tablet controls

[songbird]

Bruce Byfield wrote:
>
> I recently started using a Wacom Intuos Draw tablet. Its functions as a
> mouse substitute are available as soon as I plug it in, and the
> device is detected by the operating system. However, the tools
> available in desktop environments for configuring buttons and drawing
> functions don't detect the tablet, even though I can use the stylus in
> the testing area for the tools. Nor does xsetwacom work from the command
> line.
>
> I have built and install the latest kernel modules for the tablet, and
> added the appropriate lines in xorg.conf. Neither has any noticeable
> effect. I have consulted the Debian wiki, as well as the Llinux Wacom
> project, but nothing changes the situation. Any idea where to go from
> here? 

  how recent a kernel do you have?  what version of
Debian are you on?  what desktop?

  i'm not familiar at all with these devices but
the above questions may help someone else give a
better answer.

  in nosing around google i'm seeing some people
talk about them and that they are not new devices.

  one person says that after reboot it worked...
has that been tried?


  songbird

[solved] testing: today's upgrade of xserver-xorg-input-libinput breaks MATE mouse clicking

[songbird]

songbird wrote:
...

  fixed when tested after today's MATE updates.


  songbird

Re: transfer disk

[Pascal Hambourg]

Le 10/04/2018 à 06:18, Felix Miata a écrit :


Putting a disk from an Intel system into a system with AMD, VIA or GeForce
chipset is almost certain to fail unless the initrd includes most drivers.

This is the default (MODULES=most).


This
leads me to believe that a minimal module set initrd created on one chipset type
and tried on any other chipset type is mostly likely doomed.


Not if both chipsets use the same module. E.g. all SATA host controllers 
in AHCI mode use the same ahci module regardless of the manufacturer.

Re: transfer disk

[Pascal Hambourg]

Le 10/04/2018 à 05:48, Ben Caradoc-Davies a écrit :

On 10/04/18 14:01, mick crane wrote:
Can you pop a hard disk that boots with a Debian installation on it 
into another entirely different PC and will the kernel try to make 
sense of its new hardware ?


Mostly. I once had a disk that often moved between a desktop and laptop. 
If the architecture is compatible (e.g. not amd64 <-> arm64) then most 
likely it can be made to work. Common things that require fixing:


- Disk uses Legacy (BIOS) boot and partitioning but support is not 
enabled on the motherboard. Fix: turn on your motherboard Compatibility 
Support Module or similar.


The partitioning scheme has nothing to do with BIOS/UEFI boot.


- Disk uses UEFI but ancient motherboard does not support it. Unfixable.


Can be fixed, requires to install a BIOS boot loader on the disk.
Same if old disk and new PC have different UEFI architecture (32 and 64 
bits).


- Disk uses UEFI. Motherboard supports UEFI but has no boot entry and 
disk may need to be manually selected. Running update-grub should fix.


No it won't. update-grub just creates grub.cfg, it does not create an 
EFI boot entry. grub-install would, but most often you do not have to 
create an EFI boot entry, you can just install a copy of GRUB in the 
default ("removable device") path /boot/efi/efi/boot/boot{x64|ia32}.efi, 
manually or with grub-install --removable.

graphic tablet controls

[Bruce Byfield]

I recently started using a Wacom Intuos Draw tablet. Its functions as a
mouse substitute are available as soon as I plug it in, and the
device is detected by the operating system. However, the tools
available in desktop environments for configuring buttons and drawing
functions don't detect the tablet, even though I can use the stylus in
the testing area for the tools. Nor does xsetwacom work from the command
line.

I have built and install the latest kernel modules for the tablet, and
added the appropriate lines in xorg.conf. Neither has any noticeable
effect. I have consulted the Debian wiki, as well as the Llinux Wacom
project, but nothing changes the situation. Any idea where to go from
here? 

o ___o
Bruce Byfield (on Pacific time) 604-421-7189
Writer of "Designing with LibreOffice"
www.designingwithlibreoffice.com

Re: GPG and keyring issue

[john doe]

On 4/10/2018 4:33 PM, J.W. Foster wrote:

I just installed a new Debian 9 system on a reformatted disk in a multidisk 
system. I used the Netinstall cd from Debian. Installation went ok and I am 
sending this from the system. Problem is I tried to add the contrib and 
non-free repos to synaptic i.e. apt sources.list  I simply copied the 
sources.list file from a current working system that has no issues. The message 
below is what I get when I try to run apt update:
GPG error: http://deb.debian.org/debian stretch-updates InRelease: The 
following signatures couldn't be verified because the public key is not 
available: NO_PUBKEY 8B48AD6246925553 NO_PUBKEY 7638D0442B90D010The repository 
'http://deb.debian.org/debian stretch-updates InRelease' is not signed.Updating 
from such a repository can't be done securely, and is therefore disabled by 
default.See apt-secure(8) manpage for repository creation and user 
configuration details.GPG error: http://security.debian.org stretch/updates 
InRelease: The following signatures couldn't be verified because the public key 
is not available: NO_PUBKEY 9D6D8F6BC857C906 NO_PUBKEY 8B48AD6246925553The 
repository 'http://security.debian.org stretch/updates InRelease' is not 
signed.Updating from such a repository can't be done securely, and is therefore 
disabled by default.See apt-secure(8) manpage for repository creation and user 
configuration details.GPG error: http://deb.debian.org/debian stretch Release: 
The following signatures couldn't be verified because the public key is not 
available: NO_PUBKEY 8B48AD6246925553 NO_PUBKEY 7638D0442B90D010 NO_PUBKEY 
EF0F382A1A7B6500The repository 'http://deb.debian.org/debian stretch Release' 
is not signed.Updating from such a repository can't be done securely, and is 
therefore disabled by default.See apt-secure(8) manpage for repository creation 
and user configuration details.GPG error: http://ftp.debian.org/debian 
stretch-backports InRelease: The following signatures couldn't be verified 
because the public key is not available: NO_PUBKEY 8B48AD6246925553 NO_PUBKEY 
7638D0442B90D010The repository 'http://ftp.debian.org/debian stretch-backports 
InRelease' is not signed.
I have used Debian for years, and dont often use this list but this is a new 
issues to me and though I can find a lot of info, I have not found a solution. 
i did download the current keyrings and installed them, but that did not help. 
Just wondering if this is some new issue related to secure apt.ThanksJohn




I have added 'contrib non-free' to the end of all the lines in 
/etc/apt/sources.list.
I can do an 'apt update' without having gpg complaining and without 
having to do anything specific.


/etc/apt/sources.list:
deb http://ftp.us.debian.org/debian/ stretch main contrib non-free
deb-src http://ftp.us.debian.org/debian/ stretch main contrib non-free

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


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


# stretch-backports, previously on backports.debian.org
deb http://ftp.us.debian.org/debian/ stretch-backports main contrib non-free
deb-src http://ftp.us.debian.org/debian/ stretch-backports main contrib 
non-free


Note that this e-mail might be folded by my mailer.

--
John Doe

Re: how do i tell usb to leave keyboard alone?

[songbird]

songbird wrote:
...
still happening, collected more info as i was running udevadm this time...

  always starts with change from KERNEL, so yes, seems to me to
be a kernel issue, but the fun thing here is that i've told the
kernel to leave the USB keyboard alone via udev rules and i've 
verified that the settings are indeed in the /sys/ files along 
with setting usbcore.autosuspend to -1.

  also went back to earlier kernel trying to see where this may
have started.  no difference...


.

Apr 10 10:17:01 auntie CRON[2875]: pam_unix(cron:session): session opened for 
user root by (uid=0)
Apr 10 10:17:01 auntie CRON[2876]: (root) CMD (   cd / && run-parts --report 
/etc/cron.hourly)
Apr 10 10:17:01 auntie CRON[2875]: pam_unix(cron:session): session closed for 
user root
KERNEL[9590.068254] change   
/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/0003::.0002/input/input21/input21::numlock
 (leds)
KERNEL[9590.068320] remove   
/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/0003::.0002/input/input21/input21::numlock
 (leds)
KERNEL[9590.068352] change   
/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/0003::.0002/input/input21/input21::capslock
 (leds)
KERNEL[9590.068377] remove   
/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/0003::.0002/input/input21/input21::capslock
 (leds)
KERNEL[9590.068412] change   
/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/0003::.0002/input/input21/input21::scrolllock
 (leds)
KERNEL[9590.068435] remove   
/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/0003::.0002/input/input21/input21::scrolllock
 (leds)
KERNEL[9590.068454] remove   
/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/0003::.0002/input/input21/input21::compose
 (leds)
KERNEL[9590.068485] change   
/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/0003::.0002/input/input21/input21::kana
 (leds)
KERNEL[9590.068509] remove   
/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/0003::.0002/input/input21/input21::kana
 (leds)
UDEV  [9590.072802] change   
/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/0003::.0002/input/input21/input21::numlock
 (leds)
UDEV  [9590.072907] change   
/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/0003::.0002/input/input21/input21::capslock
 (leds)
UDEV  [9590.073289] change   
/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/0003::.0002/input/input21/input21::scrolllock
 (leds)
UDEV  [9590.073528] remove   
/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/0003::.0002/input/input21/input21::compose
 (leds)
UDEV  [9590.073544] remove   
/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/0003::.0002/input/input21/input21::capslock
 (leds)
UDEV  [9590.073556] remove   
/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/0003::.0002/input/input21/input21::numlock
 (leds)
UDEV  [9590.073766] remove   
/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/0003::.0002/input/input21/input21::scrolllock
 (leds)
UDEV  [9590.073939] change   
/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/0003::.0002/input/input21/input21::kana
 (leds)
UDEV  [9590.074331] remove   
/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/0003::.0002/input/input21/input21::kana
 (leds)
KERNEL[9590.088181] remove   
/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/0003::.0002/input/input21/event18
 (input)
UDEV  [9590.089052] remove   
/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/0003::.0002/input/input21/event18
 (input)
KERNEL[9590.116184] remove   
/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/0003::.0002/input/input21
 (input)
KERNEL[9590.116233] remove   
/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/0003::.0002/hidraw/hidraw1
 (hidraw)
KERNEL[9590.116266] unbind   
/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/0003::.0002 (hid)
KERNEL[9590.116301] remove   
/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/0003::.0002 (hid)
UDEV  [9590.118240] remove   
/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/0003::.0002/input/input21
 (input)
UDEV  [9590.118615] remove   
/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/0003::.0002/hidraw/hidraw1
 (hidraw)
UDEV  [9590.119778] unbind   
/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/0003::.0002 (hid)
UDEV  [9590.120761] remove   
/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/0003::.0002 (hid)
KERNEL[9590.132238] unbind   /devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0 
(usb)
KERNEL[9590.132319] remove   /devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0 
(usb)
KERNEL[9590.132870] unbind   /devices/pci:00/:00:14.0/usb1/1-6 (usb)
KERNEL[9590.132951] remove   /devices/pci:00/:00:14.0/usb1/1-6 (usb)
UDEV  [9590.134768] unbind   /devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0 
(usb)
UDEV  [9590.135884] remove   /devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0 
(usb)
UDEV  [9590.137535] unbind   /

Re: hdmi from cable box in a Linux window?

[Dan Ritter]

On Mon, Apr 09, 2018 at 04:14:09PM -0700, John Conover wrote:
> 
> Is there a good way of getting hdmi from a cable TV box into a window
> on the Linux screen? Anyone done it?

Yes, the most straightforward is a box that takes HDMI in,
connects to your network and makes an RTSP stream available for
VLC or whatever to display for you.

https://blog.benjojo.co.uk/post/cheap-hdmi-capture-for-linux

http://archive.is/ThNO1

-dsr-

Re: SSD's and many edits of a single file

[Celejar]

On Mon, 9 Apr 2018 05:53:18 -0400
Gene Heskett  wrote:

...

> What else is a good editor? And lets not start yet another vim vs emacs 
> war. kwrite and kate come to mind. I'm running Trinity Desktop, maybe I 
> should check them out. Whatever, needs to be able to have several files 
> open so I can just click back and forth on the tabs as I usually 
> separate the files into what uses which cutting tool.

I use bluefish (and sometimes geany). Bluefish is probably more
complicated and heavier than you need, but you can take a look for
yourself.

Celejar

GPG and keyring issue

[J.W. Foster]

I just installed a new Debian 9 system on a reformatted disk in a multidisk 
system. I used the Netinstall cd from Debian. Installation went ok and I am 
sending this from the system. Problem is I tried to add the contrib and 
non-free repos to synaptic i.e. apt sources.list  I simply copied the 
sources.list file from a current working system that has no issues. The message 
below is what I get when I try to run apt update:
GPG error: http://deb.debian.org/debian stretch-updates InRelease: The 
following signatures couldn't be verified because the public key is not 
available: NO_PUBKEY 8B48AD6246925553 NO_PUBKEY 7638D0442B90D010The repository 
'http://deb.debian.org/debian stretch-updates InRelease' is not signed.Updating 
from such a repository can't be done securely, and is therefore disabled by 
default.See apt-secure(8) manpage for repository creation and user 
configuration details.GPG error: http://security.debian.org stretch/updates 
InRelease: The following signatures couldn't be verified because the public key 
is not available: NO_PUBKEY 9D6D8F6BC857C906 NO_PUBKEY 8B48AD6246925553The 
repository 'http://security.debian.org stretch/updates InRelease' is not 
signed.Updating from such a repository can't be done securely, and is therefore 
disabled by default.See apt-secure(8) manpage for repository creation and user 
configuration details.GPG error: http://deb.debian.org/debian stretch Release: 
The following signatures couldn't be verified because the public key is not 
available: NO_PUBKEY 8B48AD6246925553 NO_PUBKEY 7638D0442B90D010 NO_PUBKEY 
EF0F382A1A7B6500The repository 'http://deb.debian.org/debian stretch Release' 
is not signed.Updating from such a repository can't be done securely, and is 
therefore disabled by default.See apt-secure(8) manpage for repository creation 
and user configuration details.GPG error: http://ftp.debian.org/debian 
stretch-backports InRelease: The following signatures couldn't be verified 
because the public key is not available: NO_PUBKEY 8B48AD6246925553 NO_PUBKEY 
7638D0442B90D010The repository 'http://ftp.debian.org/debian stretch-backports 
InRelease' is not signed.
I have used Debian for years, and dont often use this list but this is a new 
issues to me and though I can find a lot of info, I have not found a solution. 
i did download the current keyrings and installed them, but that did not help. 
Just wondering if this is some new issue related to secure apt.ThanksJohn

Re: SSD's and many edits of a single file

[Thomas Schmitt]

Hi,

Stefan Monnier wrote:
> I see no indication *at all* from Gene's description that the problem
> could have anything to do with the OS or the hardware.

I don't think so either. But since the discussion began to cycle,
i thought that it would be nice to have some tangible proof.

If the script runs fine for half a day while Gene does his editing and
CNCing and maybe experiences the problem with geany again, then we can
say that it's not the SSD or the kernel.


> My guess is rather that his editor ends up saving the file at location
> A and he looks at the state of a file at location B.

Yes. But who would want to explore the habits of a Gnome application ?
  https://github.com/geany/geany/issues/1774
  https://wiki.geany.org/config/all_you_never_wanted_to_know_about_file_saving


Have a nice day :)

Thomas

Re: can't access debian no more

[David Wright]

On Tue 10 Apr 2018 at 15:21:44 (+0200), mess-mate wrote:
> after an install of windows 10 (need it some a progran can't run on linux),
> somewhat seems to be changed on the hd.
> The startup lock on the disk control/fs.

Perhaps look back at your notes on how you fixed this problem.
https://lists.debian.org/debian-user/2018/03/msg00039.html
Here's looking forward to an OK/Solved message.

Cheers,
David.

Re: can't access debian no more

[mess-mate]

On 10-Apr-18 15:58, Brian wrote:

On Tue 10 Apr 2018 at 09:33:45 -0400, Forest Dean Feighner wrote:


On Tue, Apr 10, 2018 at 9:21 AM, mess-mate  wrote:


Hi,
after an install of windows 10 (need it some a progran can't run on linux),
somewhat seems to be changed on the hd.
The startup lock on the disk control/fs.
regards



Not much to go on but maybe reinstall grub from the installation CD? Boot
flag for debian partition?

I really don't know what things a Windows 10 install would do.

Windows has probably removed GRUB from the MBR. mess-mate should now go
to his favorite search engine and look for help with "unable to load
linux after installing windows".


Thanks Brian, but my disks are configured efi, no need for a MBR.
My rFIND config replace Grub and I saved it on an USB, so can't be 
corrupted.

Re: can't access debian no more

[likcoras]

On 04/10/2018 10:21 PM, mess-mate wrote:
> Hi,
> after an install of windows 10 (need it some a progran can't run on linux),
> somewhat seems to be changed on the hd.
> The startup lock on the disk control/fs.
> regards
> 

Usually the suggestion on installing both Debian and Windows is to
install Windows first, since it has a tendency to ignore other operating
systems on the disk and overwriting the bootloader with its own, which
is what I think has happened here.

Try reinstalling the Debian bootloader as suggested in the other reply,
see if that works. Grub is decent at detecting other operating systems
and should avoid breaking boot.

Re: can't access debian no more

[Brian]

On Tue 10 Apr 2018 at 09:33:45 -0400, Forest Dean Feighner wrote:

> On Tue, Apr 10, 2018 at 9:21 AM, mess-mate  wrote:
> 
> > Hi,
> > after an install of windows 10 (need it some a progran can't run on linux),
> > somewhat seems to be changed on the hd.
> > The startup lock on the disk control/fs.
> > regards
> >
> >
> Not much to go on but maybe reinstall grub from the installation CD? Boot
> flag for debian partition?
> 
> I really don't know what things a Windows 10 install would do.

Windows has probably removed GRUB from the MBR. mess-mate should now go
to his favorite search engine and look for help with "unable to load
linux after installing windows".

-- 
Brian.

Re: SSD's and many edits of a single file

[Stefan Monnier]

> Following is a bash script which challenges the disk's fidelity in
> respect to small writes on a relatively small file over a long time.

I see no indication *at all* from Gene's description that the problem
could have anything to do with the OS or the hardware.

My guess is rather that his editor ends up saving the file at location
A and he looks at the state of a file at location B.


Stefan

Re: can't access debian no more

[Forest Dean Feighner]

On Tue, Apr 10, 2018 at 9:21 AM, mess-mate  wrote:

> Hi,
> after an install of windows 10 (need it some a progran can't run on linux),
> somewhat seems to be changed on the hd.
> The startup lock on the disk control/fs.
> regards
>
>
Not much to go on but maybe reinstall grub from the installation CD? Boot
flag for debian partition?

I really don't know what things a Windows 10 install would do.

HTH

can't access debian no more

[mess-mate]

Hi,
after an install of windows 10 (need it some a progran can't run on linux),
somewhat seems to be changed on the hd.
The startup lock on the disk control/fs.
regards

Re: SSD's and many edits of a single file

[Thomas Schmitt]

Hi,

re-reading the original mail of Gene
  https://lists.debian.org/debian-user/2018/04/msg00237.html
i think it is time to collect some evidence.

Following is a bash script which challenges the disk's fidelity in
respect to small writes on a relatively small file over a long time.

Gene, please consider to run it and to report the outcome

Adjustable parameters are
  file_path , chunk_size , sleep_time , duration
Edit the script to change their values. No blanks or fancy characters.
(It is advisable to store it on an unsuspicious disk.)

With the given setting of chunk_size=8, the victim file will have a size
of 524,289 bytes.

The script will print a single dot to stdout for each successful write-read
cycle.  After 60 such dots, the cycle count and a newline character get
printed.

In case of a failed read-write cycle, an ALL-CAPS message will be emitted
to stderr and the script will abort immediately.

If there is no failure, then operating system and disk are working as
they should.

Start of script. Cut out after the "---" line, store as file
"random_writer.sh", and give execution permission by
  chmod u+x random_writer.sh
---
#!/bin/bash

# Which file to use
file_path=/home/test/random_writer_victim

# How many bytes to write in one try.
# (Write range is 65536 times chunk_size plus 1)
chunk_size=8

# Interval between writes
sleep_time=10

# Overall duration in seconds (here: half a day)
duration=43200

# Initialize file content by newline characters
echo "Victim file: $file_path"
length=$(expr 65536 '*' $chunk_size + 1)
yes "" | head -c $length | dd of="$file_path" conv=notrunc 2>/dev/null

start_time=$(date '+%s')
cycle=0
while test $(expr $(date '+%s') - $start_time) -lt $duration
do
  # Get a random write address in the range of 0 to 65535
  random_adr=$(dd if=/dev/urandom bs=1 count=2 2>/dev/null | od -d | \
   head -1 | awk '{print $2}' )
  cycle=$(expr $cycle + 1)
  text=$(printf '%'"$chunk_size"'d' $cycle)

  # Write to file (with trailing newline to keep the file editor friendly)
  echo "$text" | \
dd of="$file_path" seek="$random_adr" bs=$chunk_size count=1 conv=notrunc \
   2>/dev/null

  # Check-read
  reread=$(dd if="$file_path" skip="$random_adr" bs=$chunk_size count=1 \
  2>/dev/null)

  # <<< Simulated mismatch
  # test $cycle = 3 && reread=X_simulated_X

  if test "$text" != "$reread"
  then
echo
echo "CAUGHT MISMATCH OF WRITE AND READ !" >&2
echo "Written: '$text'" >&2
echo "Read   : '$reread'" >&2
exit 1
  fi 

  echo -n '.'
  if test $(expr $cycle % 60) = 0
  then
printf '%8d\n' $cycle
  fi
  sleep $sleep_time || break
done
printf '%8d\nDone. No errors detected.\n' $cycle
---
End of script. Cut out before the "---" line.

Have a nice day :)

Thomas

Re: SSD's and many edits of a single file

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Tue, Apr 10, 2018 at 08:10:07AM -0400, Gene Heskett wrote:
> On Tuesday 10 April 2018 07:08:03 to...@tuxteam.de wrote:
> 
> > On Tue, Apr 10, 2018 at 06:49:54AM -0400, Gene Heskett wrote:

[...]

> No such clues were evident.

Then I'd look for troubles elsewhere...

> What good does it do to partition an SSD? Because of the wear leveling, 
> if it goes read-only, I expect the whole thing is read-only.  Including 
> swap I expect.

Hm. sooner or later, yes. But the OS takes its decisions for each file
system separately.

That said, I wouldn't partition an SSD without a compelling reason.

> I rest my case with this thread [...]

> Haveing fresh input from different angles helps my ancient wet ram, 
> thanks Thomas.

That's what wet RAM thrives on, I think that is valid for everyone.
So -- glad to help, and to receive help :)

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

iEYEARECAAYFAlrMuDsACgkQBcgs9XrR2kYHfwCfaBahrZwupJwU69uDR4UKJv0U
1fIAn0nN4n+3Ye1QWQdW4+SudpCDa2hc
=2EJq
-END PGP SIGNATURE-

Re: SSD's and many edits of a single file

[Gene Heskett]

On Tuesday 10 April 2018 07:08:03 to...@tuxteam.de wrote:

> On Tue, Apr 10, 2018 at 06:49:54AM -0400, Gene Heskett wrote:
> > On Tuesday 10 April 2018 03:52:55 to...@tuxteam.de wrote:
>
> [...]
>
> > > The most typical symptom [of a failed write due to storage
> > > failure] would be that the file system gets remounted
> > > read-only because of write errors. And you tend to notice that.
> >
> > Does the mount command report that? It did not.
>
> If your logs are writable (because they are on a separate file
> system, or because they are remote),

They are neither.

> you'd see that there. If 
> not (because you have only one file system), you're bound to
> notice that anyway, because many applications are going to freak
> out on a failed write (*all* writes fail once the file system
> is read-only).

No such clues were evident.

> Cheers
> -- tomás

What good does it do to partition an SSD? Because of the wear leveling, 
if it goes read-only, I expect the whole thing is read-only.  Including 
swap I expect.

I rest my case with this thread, geany apparently is not taking care of 
its housekeeping and is running out of whatever is allocated to do the 
disk write, its the only conclusion that makes sense so far. There's a 
name for it, but oldtimers is at work here too. Dammit.

I'll change my default lcnc editor to nano --smooth, which gets rid of my 
scrolling complaint.  And see if it happens again. That will also tend 
to prevent my leaving it open forever if launched from lcnc as thats 
single-threaded. Either editor launched as a fresh action will probably 
solve the problem.

Haveing fresh input from different angles helps my ancient wet ram, 
thanks Thomas.

-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

Re: SSD's and many edits of a single file

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Tue, Apr 10, 2018 at 06:49:54AM -0400, Gene Heskett wrote:
> On Tuesday 10 April 2018 03:52:55 to...@tuxteam.de wrote:

[...]

> > The most typical symptom [of a failed write due to storage
> > failure] would be that the file system gets remounted
> > read-only because of write errors. And you tend to notice that.

> Does the mount command report that? It did not.

If your logs are writable (because they are on a separate file
system, or because they are remote), you'd see that there. If
not (because you have only one file system), you're bound to
notice that anyway, because many applications are going to freak
out on a failed write (*all* writes fail once the file system
is read-only).

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

iEYEARECAAYFAlrMmxMACgkQBcgs9XrR2kbtawCfRvDu3yYCEKvA69Nt+SXTW30h
dvYAnRqoB8pVenX4X8esrPavYDXstul5
=riS/
-END PGP SIGNATURE-

Re: install printer

[Gene Heskett]

On Tuesday 10 April 2018 05:45:46 Dan Purgert wrote:

> Gene Heskett wrote:
> > On Monday 09 April 2018 15:45:34 Brian wrote:
> >> Not really. It would be a poorer debian-user without
> >> well-intentioned engagement.
> >
> > Maybe so, Brian, but in cases like this it would improve the overall
> > quality of the answers. And that more often than not, is desirable.
>
> I find I learn more when people (not necessarily you) say something
> well-intended, and then get corrected.

I do too, because the correction is often accompanied by the reasoning 
behind it, going into more detail then "thats just how it is".

> Granted, *finding* those posts 
> in the sometimes unweildy (and by then, boring) threads can be a
> challenge :)

There is that too, makes it hard to find the goodies. I use kmails "mark 
as important", those msgs containing good info. They don't get deleted 
quite as easily by list expiry maintenance. 


-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

Re: SSD's and many edits of a single file

[Gene Heskett]

On Tuesday 10 April 2018 03:52:55 to...@tuxteam.de wrote:

> On Mon, Apr 09, 2018 at 06:25:34PM -0700, David Christensen wrote:
>
> [...]
>
> > One editor failing would also make me suspect the editor.
> >
> >
> > But two failing editors would make me suspect some common factor,
> > such as a shared library and/or the kernel.
> >
> >
> > Have you tested your hardware -- power supply, memory, and SSD?  Be
> > sure to test the SSD before you touch any cables.  If it fails,
> > re-seat and/or replace cables and test again.
>
> Folks: you're barking up the wrong tree. *If* some editor fails
> to write to a file because the hard disk goes on strike, chances
> are that you'll hear your OS *SCREAM LOUDLY* that something is
> wrong.
>
> The most typical symptom would be that the file system gets remounted
> read-only because of write errors. And you tend to notice that.
>
Does the mount command report that? It did not.

> Cheers
> -- tomás



-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

Re: install printer

[Dan Purgert]

Gene Heskett wrote:
> On Monday 09 April 2018 15:45:34 Brian wrote:
>> Not really. It would be a poorer debian-user without well-intentioned
>> engagement.
>
> Maybe so, Brian, but in cases like this it would improve the overall 
> quality of the answers. And that more often than not, is desirable.
>

I find I learn more when people (not necessarily you) say something
well-intended, and then get corrected.  Granted, *finding* those posts
in the sometimes unweildy (and by then, boring) threads can be a
challenge :)


-- 
|_|O|_| Registered Linux user #585947
|_|_|O| Github: https://github.com/dpurgert
|O|O|O| PGP: 05CA 9A50 3F2E 1335 4DC5  4AEE 8E11 DDF3 1279 A281

Re: hdmi from cable box in a Linux window?

[Erwan David]

On Tue, Apr 10, 2018 at 09:45:46AM CEST, Joe  said:
> On Mon, 9 Apr 2018 16:14:09 -0700
> cono...@rahul.net (John Conover) wrote:
> 
> > Is there a good way of getting hdmi from a cable TV box into a window
> > on the Linux screen? Anyone done it?
> 
> There are converters for below 100 Pounds/Dollars to USB3.0. I've seen
> 1080p/60 going into VLC on a (fast) Windows laptop, although it only
> manages 1-2fps on mine. The computer seems to need to do a lot of work.
> There are more expensive converters which presumably do more themselves.
> 
> I had the converter for a short time, and didn't try it with any Linux
> computers, so I don't know the state of USB3 video over here.

The problem that might appear would be if the source wants a HDCP
compatible HDMi display. Much more difficult to find an adapter for this.


-- 
Erwan

Re: SSD's and many edits of a single file

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Mon, Apr 09, 2018 at 06:25:34PM -0700, David Christensen wrote:

[...]

> One editor failing would also make me suspect the editor.
> 
> 
> But two failing editors would make me suspect some common factor,
> such as a shared library and/or the kernel.
> 
> 
> Have you tested your hardware -- power supply, memory, and SSD?  Be
> sure to test the SSD before you touch any cables.  If it fails,
> re-seat and/or replace cables and test again.

Folks: you're barking up the wrong tree. *If* some editor fails
to write to a file because the hard disk goes on strike, chances
are that you'll hear your OS *SCREAM LOUDLY* that something is
wrong.

The most typical symptom would be that the file system gets remounted
read-only because of write errors. And you tend to notice that.

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

iEYEARECAAYFAlrMbVcACgkQBcgs9XrR2kYDHQCbBbWJ05ZsCKnzao3k/F5/6VQG
Yd4An0o+M9R6tH8AOX0Uas7JvhwF0x9N
=Amez
-END PGP SIGNATURE-

Re: hdmi from cable box in a Linux window?

[Joe]

On Mon, 9 Apr 2018 16:14:09 -0700
cono...@rahul.net (John Conover) wrote:

> Is there a good way of getting hdmi from a cable TV box into a window
> on the Linux screen? Anyone done it?

There are converters for below 100 Pounds/Dollars to USB3.0. I've seen
1080p/60 going into VLC on a (fast) Windows laptop, although it only
manages 1-2fps on mine. The computer seems to need to do a lot of work.
There are more expensive converters which presumably do more themselves.

I had the converter for a short time, and didn't try it with any Linux
computers, so I don't know the state of USB3 video over here.

-- 
Joe