Re: dpkg-reconfigure keyboard-configuration (Swedish with "|")

[Erik Josefsson]

On 5/5/19 7:21 AM, Jonas Smedegaard wrote:

I don't know if there is a screw loose in your laptop, or
warewolves pissed on a USB plugs.


Well, what comes out of one of the keyboards now is p.

Could be warewolf p's, or baby drool.

It's magic either way.

//Erik

Re: Gene you poor soul

[Gene Heskett]

On Tuesday 21 May 2019 11:01:00 pm Martin McCormick wrote:

> Gene Heskett  writes:
> > On Tuesday 21 May 2019 08:07:17 pm Jude DaShiell wrote:
> > > If brltty is killing all other usb numbers, that's a bug that
> > > needs fixing!  Much of the other computer peripherals going into
> > > modern computers these days go in through usb ports.
> > > If that ran, my standard keyboard and speakers would be killed and
> > > if those two get killed, I can't use a computer since I use speech
> > > synthesis for output since I've never been able to see a screen.
> >
> > This only affected the seriel to usb dongles.  And I've at least 3
> > in this system.  Since x10 will never make another CM-11a, and a
> > firecracker is different enough it won't talk to any of the older
> > stuff, it either works or I build a whole new system to automate one
> > group of lights.
> >
> > > One time I remember the Navy went and fixed band width hogging
> > > bugs with their mandatory training and took out the requirement to
> > > position a mouse and click to move to the next slide.  This was
> > > done to support accessibility.  Its other effect was on all of the
> > > ships in the fleets. Sailors suddenly discovered it was easier to
> > > complete their mandatory training.
> > > That was one instance where accessibility improvement had a good
> > > effect on those in remote environments.
>
>   I found this thread accidentally and got interested in it
> so here are my two Cents worth.
>
>   When you run a program or application, that application
> may need kernel modules that aren't part of the kernel right now
> so it looks in a special directory which is
> /lib/modules/long_number.  In my case, long_number is
>
> 4.9.0-6-686-pae
>
>   Yours could be the same or more likely, it will be
> different and you find that out with the command
>
> uname -r
>
>   The output you get from uname -r is what you put after
> /lib/modules/
>
>   Your modules directory might have a module supporting
> brltty and you can find that out by cd
> /lib/modules/that_long_number and then doing ls |grep -i brltty.
>
>   What that does is list all the files in the directory and
> only print those containing brltty in their name and it won't
> matter if the brltty is all upper case, lower case or some crazy
> mixture.
>
>   If nothing is there, you have no brltty modules so you
> have found the bottom of that rabbit hole and don't need to dig
> any further.
>
>   If you do, however, then lookup how to keep your computer
> from using that module since you don't need brltty anyway.  That
> procedure is different with different versions of Linux so read
> how your version blacklists kernel modules to keep them from ever
> loading.
>
>   This is one of the many things about unix that are really
> useful since you can tweak your system to fix seemingly
> intractable problems at times.
>
> Martin McCormick

Its working now, and I have other irons in the fire, like how do I print 
to a printer shared by cups, from a win 10 Home edition that has taken a 
snapshot of its full screen window and has stored it on the win 10 box. 
I've been forced to buy a winderz box to do a job that will bill in the 
low 4 digit range.  And I'll need on site printouts so it looks as if I 
go spend another $40 on a cheap inkjet and carry it around.  And I can't 
even find the printer setup as I only had one other winbox in my life.. 
I started out in the nix camp in the middle 80's, went to amigados in 
the 90's, and to linux in '98 without ever having windows on the 
premises. So I'm the dummy they write all those yellow books for.

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: Can't Connect to Secure Wireless Network

[Cindy Sue Causey]

On 5/21/19, Cindy Sue Causey  wrote:
> On 5/21/19, Kent West  wrote:
>> I'm on a university campus; we have a secure network ("ACUsecure") to
>> which I'm trying to connect. Mac laptops and Windows laptops have no
>> problem. You connect to the network, and a pop-up appears asking for the
>> user's "campus" username/password, and connection is made.
>>
>> On my Debian sid laptop, using Gnome or Cinnamon as my DE (and not
>> knowing how to connect via console-only), I can click on the Network
>> Settings and get to the list of networks, and see "ACUsecure". I can try
>> to connect, and I get prompted for a username/password. But the
>> connection never succeeds.
>>
>> I've involved our network guru on campus; he's not very familiar with
>> Debian, but he spent an hour looking over things. From his side of the
>> network, it looks like I'm getting validated, but from the laptop, I've
>> found logs that say authentication failure. He's tried his credentials
>> also, in various forms. He believes we've got the settings right on
>> Debian:
>>
>>
>> WPA Enterprise
>>
>> Protected EAP (PEAP)
>>
>> Anonymous identity blank
>>
>> CA cert None
>>
>> No CA cert required
>>
>> Inner auth MSCHAPv2
>>
>> username
>>
>> password
>>
>>
>> When I try to follow the journalctl entries from first trying to switch
>> to ACUsecure until I cancel the pop-up asking again for creds, I get
>> this:
>>
>> http://goshen.acu.edu/westk/ACU-INTERNAL-USE/wireless.txt (IPs replaced
>> by "aaa.bbb.ccc.ddd"; yeah, just feel-good security on my part, I know,
>> but it helps a little)
>>
>> Any help would be appreciated. Thanks!
>
> I'm not quite grasping what package you're using to attempt this so my
> apologies in advance if you're using...
>
> Wicd? Have you tried that yet? I just peeked at mine. There IS a spot
> there for adding a username and password. I'd never used it so I had
> to double-check.


Well, I'm THRILLED I don't toss in bad words in drafts. That first
Send was NOT done. I don't know how that got sent. Every once in a
while, things go hinky on my end with the cursor having a mind of its
own. Glass half full, I'm very thankful I wasn't contemplating buying
something expensive and hadn't yet made up my mind... :)

Ok, what I had INTENDED to add was that if you had waited about 3 or 4
more days, I MIGHT have had some firsthand experience with it. I'm
just waiting for a couple of $5 USB dongles to get here.

What I've got right now has not worked properly with Wicd, but I don't
think it's Wicd's fault. I think my old ASUS laptop here doesn't play
well with the security we need to have these days. Am hoping maybe
those dongles fix that. (They ARE "dongles", right?) :)

When typing via command line on occasion, I use wicd-gtk to access it
in case that doesn't install by default if you go playing with it..

If you're using NetworkManager or something like that, it MIGHT get
uninstalled. That's business as usual... It's expected behavior. Just
have ALL the dotDebs (i.e. also the dependencies) hanging around
nearby in case you test drive Wicd and don't like it such that you
need to reinstall whatever it might uninstall. :)

If you're already using Wicd, my apologies for the noise.. TIMES TWO. :)

Cindy :)
-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA

* runs with birdseed *

Re: Gene you poor soul

[Martin McCormick]

Gene Heskett  writes:
> On Tuesday 21 May 2019 08:07:17 pm Jude DaShiell wrote:
> 
> > If brltty is killing all other usb numbers, that's a bug that needs
> > fixing!  Much of the other computer peripherals going into modern
> > computers these days go in through usb ports.
> > If that ran, my standard keyboard and speakers would be killed and if
> > those two get killed, I can't use a computer since I use speech
> > synthesis for output since I've never been able to see a screen.
> >
> This only affected the seriel to usb dongles.  And I've at least 3 in
> this system.  Since x10 will never make another CM-11a, and a
> firecracker is different enough it won't talk to any of the older stuff,
> it either works or I build a whole new system to automate one group of
> lights.
> 
> > One time I remember the Navy went and fixed band width hogging bugs
> > with their mandatory training and took out the requirement to position
> > a mouse and click to move to the next slide.  This was done to support
> > accessibility.  Its other effect was on all of the ships in the
> > fleets. Sailors suddenly discovered it was easier to complete their
> > mandatory training.
> > That was one instance where accessibility improvement had a good
> > effect on those in remote environments.
> >

I found this thread accidentally and got interested in it
so here are my two Cents worth.

When you run a program or application, that application
may need kernel modules that aren't part of the kernel right now
so it looks in a special directory which is
/lib/modules/long_number.  In my case, long_number is

4.9.0-6-686-pae

Yours could be the same or more likely, it will be
different and you find that out with the command

uname -r

The output you get from uname -r is what you put after
/lib/modules/

Your modules directory might have a module supporting
brltty and you can find that out by cd
/lib/modules/that_long_number and then doing ls |grep -i brltty.

What that does is list all the files in the directory and
only print those containing brltty in their name and it won't
matter if the brltty is all upper case, lower case or some crazy
mixture.

If nothing is there, you have no brltty modules so you
have found the bottom of that rabbit hole and don't need to dig
any further.

If you do, however, then lookup how to keep your computer
from using that module since you don't need brltty anyway.  That
procedure is different with different versions of Linux so read
how your version blacklists kernel modules to keep them from ever
loading.

This is one of the many things about unix that are really
useful since you can tweak your system to fix seemingly
intractable problems at times.

Martin McCormick

Re: Can't Connect to Secure Wireless Network

[Cindy Sue Causey]

On 5/21/19, Kent West  wrote:
> I'm on a university campus; we have a secure network ("ACUsecure") to
> which I'm trying to connect. Mac laptops and Windows laptops have no
> problem. You connect to the network, and a pop-up appears asking for the
> user's "campus" username/password, and connection is made.
>
> On my Debian sid laptop, using Gnome or Cinnamon as my DE (and not
> knowing how to connect via console-only), I can click on the Network
> Settings and get to the list of networks, and see "ACUsecure". I can try
> to connect, and I get prompted for a username/password. But the
> connection never succeeds.
>
> I've involved our network guru on campus; he's not very familiar with
> Debian, but he spent an hour looking over things. From his side of the
> network, it looks like I'm getting validated, but from the laptop, I've
> found logs that say authentication failure. He's tried his credentials
> also, in various forms. He believes we've got the settings right on Debian:
>
>
> WPA Enterprise
>
> Protected EAP (PEAP)
>
> Anonymous identity blank
>
> CA cert None
>
> No CA cert required
>
> Inner auth MSCHAPv2
>
> username
>
> password
>
>
> When I try to follow the journalctl entries from first trying to switch
> to ACUsecure until I cancel the pop-up asking again for creds, I get this:
>
> http://goshen.acu.edu/westk/ACU-INTERNAL-USE/wireless.txt (IPs replaced
> by "aaa.bbb.ccc.ddd"; yeah, just feel-good security on my part, I know,
> but it helps a little)
>
> Any help would be appreciated. Thanks!

I'm not quite grasping what package you're using to attempt this so my
apologies in advance if you're using...

Wicd? Have you tried that yet? I just peeked at mine. There IS a spot
there for adding a username and password. I'd never used it so I had
to double-check.

-- 
Cindy-Sue Causey
Backyard Pishing (Very active private birding adventure)
http://www.youtube.com/user/SilkWhispers
http://www.flickr.com/photos/mountainsplash/
Talking Rock, Pickens County, Georgia, USA

* runs with birdseed *

Re: Gene you poor soul

[Gene Heskett]

On Tuesday 21 May 2019 08:07:17 pm Jude DaShiell wrote:

> If brltty is killing all other usb numbers, that's a bug that needs
> fixing!  Much of the other computer peripherals going into modern
> computers these days go in through usb ports.
> If that ran, my standard keyboard and speakers would be killed and if
> those two get killed, I can't use a computer since I use speech
> synthesis for output since I've never been able to see a screen.
>
This only affected the seriel to usb dongles.  And I've at least 3 in 
this system.  Since x10 will never make another CM-11a, and a 
firecracker is different enough it won't talk to any of the older stuff, 
it either works or I build a whole new system to automate one group of 
lights.

> One time I remember the Navy went and fixed band width hogging bugs
> with their mandatory training and took out the requirement to position
> a mouse and click to move to the next slide.  This was done to support
> accessibility.  Its other effect was on all of the ships in the
> fleets. Sailors suddenly discovered it was easier to complete their
> mandatory training.
> That was one instance where accessibility improvement had a good
> effect on those in remote environments.
>

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: Gene you poor soul

[Jude DaShiell]

If brltty is killing all other usb numbers, that's a bug that needs
fixing!  Much of the other computer peripherals going into modern
computers these days go in through usb ports.
If that ran, my standard keyboard and speakers would be killed and if
those two get killed, I can't use a computer since I use speech
synthesis for output since I've never been able to see a screen.

One time I remember the Navy went and fixed band width hogging bugs with
their mandatory training and took out the requirement to position a
mouse and click to move to the next slide.  This was done to support
accessibility.  Its other effect was on all of the ships in the fleets.
Sailors suddenly discovered it was easier to complete their mandatory
training.
That was one instance where accessibility improvement had a good effect
on those in remote environments.

On Tue, 21 May 2019, Gene Heskett wrote:

> Date: Tue, 21 May 2019 19:56:58
> From: Gene Heskett 
> To: debian-user@lists.debian.org
> Subject: Re: Gene you poor soul
> Resent-Date: Tue, 21 May 2019 23:57:15 + (UTC)
> Resent-From: debian-user@lists.debian.org
>
> On Tuesday 21 May 2019 05:48:54 pm bw wrote:
>
> > In-Reply-To: <201905211726.13958.ghesk...@shentel.net>
> > subject=Re: Re: \got a new problem with heyu, and it is a bug in
> > bfltty that kills all /dev/ttyUSBnumber's
> >
> > >> Sorry to but in, but really Gene... don't you think that
> > >> accessibility for the blind is more important, than controlling the
> > >> lights in your house, or whatever you are using heyu for?  It's
> > >> only an initial setup, it's not permanent.  I mean really, have a
> > >> little compassion?
> > >
> > >Thats exactly why I am arguing for brltty to be fixed. Because it
> > > should be able to co-exist.  And it can't do that now.
> >
> > Gene you poor soul, I will pray for you.
>
> I appreciate it, but TBT I think I have made it this far because he's not
> ready to cope with a stubborn old fart that I can be.  He's had several
> chances over the last 50 years, and thrown me back everytime. Pulmonary
> embolisms are about 98% fatal, but 4 years later I'm still calling it
> like I see it. I will admit to thinking a little fuzzier since then as
> my brain suffered from lack of oxygen for 3 or 4 hours while the
> clotbuster shot was working.  And I sure don't recommend it as a way to
> die. Scary & terrifying is not an adequate description.
>
> Cheers, Gene Heskett
>

-- 

Re: got a new problem with heyu, and it is a bug in bfltty that kills all /dev/ttyUSBnumber's

[Gene Heskett]

On Tuesday 21 May 2019 07:44:51 pm David Wright wrote:

> On Tue 21 May 2019 at 17:21:33 (-0400), Gene Heskett wrote:
> > On Tuesday 21 May 2019 02:31:26 pm Curt wrote:
> > > On 2019-05-21, Gene Heskett  wrote:
> > > >> We are positively discriminating in favor of the blind.
> > > >
> > > > Then perhaps the better question is why was it running on a new
> > > > stretch install?   I think it probably could be fixed to keep
> > > > both camps happy.
> > >
> > > That I don't know. I don't have it here on my Stretch. It would be
> > > interesting to discover what dragged brltty into yours.
> >
> > Good question.
>
> And do you expect Curt to tell you?
>
> > The install image is supposed to be the latest straight
> > amd64 debian stretch, with a rt-preempt kernel and the latest stable
> > 2.7.4 linuxcnc.  Not much else is supposed to be changed.
>
> Changed from what? Wasn't this a two week old installation from
> scratch?
>
> Cheers,
> David.

No clue what else, download the "testing" image from linuxcnc.org and 
look it over. Not trying to be a smartass about it, I really don't know.


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: Gene you poor soul

[Gene Heskett]

On Tuesday 21 May 2019 05:48:54 pm bw wrote:

> In-Reply-To: <201905211726.13958.ghesk...@shentel.net>
> subject=Re: Re: \got a new problem with heyu, and it is a bug in
> bfltty that kills all /dev/ttyUSBnumber's
>
> >> Sorry to but in, but really Gene... don't you think that
> >> accessibility for the blind is more important, than controlling the
> >> lights in your house, or whatever you are using heyu for?  It's
> >> only an initial setup, it's not permanent.  I mean really, have a
> >> little compassion?
> >
> >Thats exactly why I am arguing for brltty to be fixed. Because it
> > should be able to co-exist.  And it can't do that now.
>
> Gene you poor soul, I will pray for you.

I appreciate it, but TBT I think I have made it this far because he's not 
ready to cope with a stubborn old fart that I can be.  He's had several 
chances over the last 50 years, and thrown me back everytime. Pulmonary 
embolisms are about 98% fatal, but 4 years later I'm still calling it 
like I see it. I will admit to thinking a little fuzzier since then as 
my brain suffered from lack of oxygen for 3 or 4 hours while the 
clotbuster shot was working.  And I sure don't recommend it as a way to 
die. Scary & terrifying is not an adequate description.

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: got a new problem with heyu, and it is a bug in bfltty that kills all /dev/ttyUSBnumber's

[David Wright]

On Tue 21 May 2019 at 17:21:33 (-0400), Gene Heskett wrote:
> On Tuesday 21 May 2019 02:31:26 pm Curt wrote:
> > On 2019-05-21, Gene Heskett  wrote:
> > >> We are positively discriminating in favor of the blind.
> > >>
> > > Then perhaps the better question is why was it running on a new
> > > stretch install?   I think it probably could be fixed to keep both
> > > camps happy.
> >
> > That I don't know. I don't have it here on my Stretch. It would be
> > interesting to discover what dragged brltty into yours.
> >
> Good question.

And do you expect Curt to tell you?

> The install image is supposed to be the latest straight 
> amd64 debian stretch, with a rt-preempt kernel and the latest stable 
> 2.7.4 linuxcnc.  Not much else is supposed to be changed.

Changed from what? Wasn't this a two week old installation from scratch?

Cheers,
David.

Re: got a new problem with heyu, and it is a bug in bfltty that kills all /dev/ttyUSBnumber's

[Gene Heskett]

On Tuesday 21 May 2019 02:37:57 pm bw wrote:

> In-Reply-To: <201905211405.01261.ghesk...@shentel.net>
>
> >> We are positively discriminating in favor of the blind.
> >
> >Then perhaps the better question is why was it running on a new
> > stretch install?   I think it probably could be fixed to keep both
> > camps happy.
>
> Because it is easier for a sighted person to remove brltty and setup
> their serial device than it is for a blind person to figure out what
> package to install without a braille device to read with?
>
> Sorry to but in, but really Gene... don't you think that accessibility
> for the blind is more important, than controlling the lights in your
> house, or whatever you are using heyu for?  It's only an initial
> setup, it's not permanent.  I mean really, have a little compassion?

Thats exactly why I am arguing for brltty to be fixed. Because it should 
be able to co-exist.  And it can't do that now.

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: got a new problem with heyu, and it is a bug in bfltty that kills all /dev/ttyUSBnumber's

[Gene Heskett]

On Tuesday 21 May 2019 02:31:26 pm Curt wrote:

> On 2019-05-21, Gene Heskett  wrote:
> >> We are positively discriminating in favor of the blind.
> >>
> >> > Cheers, Gene Heskett
> >
> > Then perhaps the better question is why was it running on a new
> > stretch install?   I think it probably could be fixed to keep both
> > camps happy.
>
> That I don't know. I don't have it here on my Stretch. It would be
> interesting to discover what dragged brltty into yours.
>
Good question. The install image is supposed to be the latest straight 
amd64 debian stretch, with a rt-preempt kernel and the latest stable 
2.7.4 linuxcnc.  Not much else is supposed to be changed.

> > Cheers, Gene Heskett


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: got a new problem with heyu

[Gene Heskett]

On Tuesday 21 May 2019 02:31:20 pm David Wright wrote:

> On Tue 21 May 2019 at 13:53:59 (-0400), Gene Heskett wrote:
> > On Tuesday 21 May 2019 05:13:45 am Curt wrote:
> > > On 2019-05-21, Gene Heskett  wrote:
> > > > I have no clue what brltty is, its new  to me.  Whats going on?
> > >
> > > https://brltty.app/
> > >
> > > There's some kind of conflict of interest between the kernel and
> > > brltty, the latter of which is claiming the device.
> > >
> > > If you're not visually impaired, uninstalling the brltty package
> > > might be a fix.
> > >
> > > All gleaned from the thread below (which looks analogous to your
> > > problem):
> > >
> > > https://forums.opensuse.org/showthread.php/520714-Bug-handling-USB
> > >-RS2 32-Serial-cable
> >
> > yup, same nail, same hammer, same log output. Since this reduces the
> > ability of a site impaired user to use these adapter devices, it
> > could be construed as discriminatory in a court of law. The way I
> > see it, this can be dumped in brltty's from yard with instructions
> > to fix it, asap.
>
> If you want to take this breathless view of bug-fixing, perhaps you
> should install sid; stretch was release virtually two years ago.
>
> And since when were people hailed into court for misconfiguring
> their software, particularly when it reminds you all the time of:
>
In this day and time David, you never can tell when some libtard might 
take the A.D.A. seriously enough to hire a lawyer who never heard of the 
GPL. If he is worth his hourly, he will read up on it, then go shoping 
for a co-operative judge. One thing I've learned in my 84 years is to 
rarely say never.  Somewhere there's an idiot plotting how to make some 
money from a lawsuit.  He has the mistaken idea its better than working 
for his 3 hots and a cot under a roof. I'm 200% with you, but I'd hate 
to see what little income debian purports to have, wasted on legal 
beagles.

> "The programs included with the Debian GNU/Linux system are free
> software; the exact distribution terms for each program are described
> in the individual files in /usr/share/doc/*/copyright.
>
> "Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
>  permitted by applicable law."
>
> Cheers,
> David.


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

Can't Connect to Secure Wireless Network

[Kent West]

I'm on a university campus; we have a secure network ("ACUsecure") to 
which I'm trying to connect. Mac laptops and Windows laptops have no 
problem. You connect to the network, and a pop-up appears asking for the 
user's "campus" username/password, and connection is made.


On my Debian sid laptop, using Gnome or Cinnamon as my DE (and not 
knowing how to connect via console-only), I can click on the Network 
Settings and get to the list of networks, and see "ACUsecure". I can try 
to connect, and I get prompted for a username/password. But the 
connection never succeeds.


I've involved our network guru on campus; he's not very familiar with 
Debian, but he spent an hour looking over things. From his side of the 
network, it looks like I'm getting validated, but from the laptop, I've 
found logs that say authentication failure. He's tried his credentials 
also, in various forms. He believes we've got the settings right on Debian:



WPA Enterprise

Protected EAP (PEAP)

Anonymous identity blank

CA cert None

No CA cert required

Inner auth MSCHAPv2

username

password


When I try to follow the journalctl entries from first trying to switch 
to ACUsecure until I cancel the pop-up asking again for creds, I get this:


http://goshen.acu.edu/westk/ACU-INTERNAL-USE/wireless.txt (IPs replaced 
by "aaa.bbb.ccc.ddd"; yeah, just feel-good security on my part, I know, 
but it helps a little)


Any help would be appreciated. Thanks!

--

Kent

Re: No Books in print on Systemd?

[Nicholas Geovanis]

On Sun, May 19, 2019 at 8:09 AM Boyan Penkov  wrote:

> --
> Boyan Penkov
> www.boyanpenkov.com
>
> +1 for the implicit sentiment that it may be time for a book-length
> elucidation of the system, as I was looking around the the same thing —
> even if it’s http://0pointer.net/blog/ posts cleaned up and laid out in a
> systematic (not temporally linear..)
>

That webpage is unfortunately the best doc I have found on SystemD. Its not
unfortunate because it's bad doc, it's good but some is a little out of
date. It's that there is nothing better from the makers of SystemD. In the
ideal world only "us" system administrators would care about SystemD and it
wouldn't be an issue for others. But SystemD is highly pervasive while
being difficult to administer. Last I saw, the Amazon AWS linux images had
removed it, using SysV-style init like the old days.

Re: got a new problem with heyu

[David Wright]

On Tue 21 May 2019 at 13:53:59 (-0400), Gene Heskett wrote:
> On Tuesday 21 May 2019 05:13:45 am Curt wrote:
> > On 2019-05-21, Gene Heskett  wrote:
> > > I have no clue what brltty is, its new  to me.  Whats going on?
> >
> > https://brltty.app/
> >
> > There's some kind of conflict of interest between the kernel and
> > brltty, the latter of which is claiming the device.
> >
> > If you're not visually impaired, uninstalling the brltty package
> > might be a fix.
> >
> > All gleaned from the thread below (which looks analogous to your
> > problem):
> >
> > https://forums.opensuse.org/showthread.php/520714-Bug-handling-USB-RS2
> >32-Serial-cable
> >
> 
> yup, same nail, same hammer, same log output. Since this reduces the 
> ability of a site impaired user to use these adapter devices, it could 
> be construed as discriminatory in a court of law. The way I see it, this 
> can be dumped in brltty's from yard with instructions to fix it, asap.

If you want to take this breathless view of bug-fixing, perhaps you
should install sid; stretch was release virtually two years ago.

And since when were people hailed into court for misconfiguring
their software, particularly when it reminds you all the time of:

"The programs included with the Debian GNU/Linux system are free software;
 the exact distribution terms for each program are described in the
 individual files in /usr/share/doc/*/copyright.

"Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
 permitted by applicable law."

Cheers,
David.

Re: got a new problem with heyu, and it is a bug in bfltty that kills all /dev/ttyUSBnumber's

[Curt]

On 2019-05-21, Gene Heskett  wrote:
>>
>> We are positively discriminating in favor of the blind.
>>
>> > Cheers, Gene Heskett
>
> Then perhaps the better question is why was it running on a new stretch 
> install?   I think it probably could be fixed to keep both camps happy.

That I don't know. I don't have it here on my Stretch. It would be
interesting to discover what dragged brltty into yours.

> Cheers, Gene Heskett

Re: got a new problem with heyu, and it is a bug in bfltty that kills all /dev/ttyUSBnumber's

[David Wright]

On Tue 21 May 2019 at 14:05:01 (-0400), Gene Heskett wrote:
> On Tuesday 21 May 2019 11:41:00 am Curt wrote:
> > On 2019-05-21, Gene Heskett  wrote:
> > > This to me is a bug that needs fixed.  No sense in denying someone
> > > using
> >
> > There are already oldenbugs flurrying around the question, Gene.
> >
> > Here's one from 2012:
> >
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667616
> >
> > tags 667616 + wontfix
> >
> >  Arthur Magill, le Thu 05 Apr 2012 13:10:27 +0200, a écrit :
> >  > Can brltty be convinced not to grab this connection?
> >
> >  It could, but we don't want to, as it would break brltty for people
> > who use the braille devices with chips using that ID, making the
> > computer completely unusable for them, really not a good thing.
> >
> > writes Monsieur THIBAULT
> >
> > > braile facilities being denied the use of such adapters.  Thats
> > > discriminatory.  And its a bug that could potentially generate a
> > > lawsuit. So I'm going to add the debian-user list to the CC: Maybe
> > > someone else with more experience at navigating their way thru
> > > bugzilla can do it based on what I've written here.
> >
> > We are positively discriminating in favor of the blind.
> >
> > > Cheers, Gene Heskett
> 
> Then perhaps the better question is why was it running on a new stretch 
> install?   I think it probably could be fixed to keep both camps happy.

Why not use   aptitude why   to find out. Are you running a DE?
Or are you installing Suggests perhaps?

Cheers,
David.

Re: No Books in print on Systemd?

[Kenneth Parker]

On Sun, May 19, 2019 at 3:24 AM Oliver Schode 
wrote:

> On Sat, 18 May 2019 23:11:42 -0400
> Kenneth Parker  wrote:
>
> > Did also see the following two:
> > >>
> > >> * How Linux Works, 2nd Edition (Paperback); Brian Ward; 2015..
> > >> Incidentally references systemd as one of the many topics covered.
> > >>
> > >
> > I'll  look, but this will, likely not have the detail I need.
>
> Nope, probably not. I read it a couple of years ago and Brian's book
> is huge, better still for a beginner I'd think. But if you're looking
> for something that roughly makes up for systemd's man pages, on paper,
> than this isn't it. I've been looking for one myself, no luck so far.
> About the best I might mention at this point is "Linux in Action" by
> David Clinton, Manning 2018, quite new. Be informed though it's more of
> your typical sysadmin guide: very broad in subject, goes into archiving,
> backups, hardening, webserver, devops, everything. Considering that,
> it's not particularly large, hence once again often lacking the depth.
> And then it doesn't have _a_ specific systemd part, or chapter; rather
> it's kind of smeared all over the place, perhaps as you might expect,
> a bit like systemd on Linux. ;)
>

Thanks.  The other Plus, about "Linux in Action", is that it's recent.

>
> I'm afraid, eventually there's (as yet) no replacement for the online
> manuals, and as drab as man pages can be, or whether you like systemd
> or not, I'd say the docs are quite decent. Not least considering its
> age. Almost overdone. If all free software was like that, we wouldn't
> need to kill too many trees.
>

I've been going over those Man Pages now (especially Systemctl and
systemd.*), and it's easy to get lost!

>
> Apart from that, and ongoing development, another hurdle could be that
> systemd is just too Linux specific, really.


One objection I'd like to add to the list is, "Systemd is not suited for
old, low-powered Hardware".  And one of my "Pet Projects", is using Linux
(and preferably Debian and/or Devuan) to rehabilitate old Hardware.

Here's a Bone for those reading this, who are "Anti SystemD":

https://ungleich.ch/en-us/cms/blog/2019/05/20/linux-distros-without-systemd/

What inspired me to bring this up on  *this*  List, is their First Entry:
Duvuan!  (I plan to get personally involved in the Devuan Project, mainly
to keep support for older Hardware, such as early i386 Processors, and
other Platforms, such as Power PC Chips [I own a G4 iMac "Desk Lamp", with
a bad hard drive, but otherwise good]).

And, by the way, I am, likely one of, only a few, who considers himself
"Neutral" on SystemD.  In fact, one of my "many Mottoes" is, "Neutrality
With Attitude"!  :-)

While even there clearly
> centered on the Desktop and enterprise environment. So while a book on
> the kernel is just about as relevant if you're doing Android, or Linux
> embedded, systemd isn't. Not to mention there haven't been a lot of
> titles on init scripting either.
>

Good Point.  I *definitely* plan to purchase the Kernel book, recommended
on an early part of this Thread.  And I'm getting it for *much* *more*,
than Systemd!  (Another thing I want to Master, is building my own,
personal Kernel, with Custom Options [not to mention small, because it
would have, only the Drivers and/only Modules, actually needed for my
Hardware]).

Best wishes,
> Oliver
>

Kenneth Parker
http://eyeblinkuniverse.com (Follow this, and its accompanying BLOG, to
find out more about me).
Note that I consider the Eye Blink Universe to be an Open Source Universe.

Re: got a new problem with heyu, and it is a bug in bfltty that kills all /dev/ttyUSBnumber's

[Gene Heskett]

On Tuesday 21 May 2019 11:41:00 am Curt wrote:

> On 2019-05-21, Gene Heskett  wrote:
> > This to me is a bug that needs fixed.  No sense in denying someone
> > using
>
> There are already oldenbugs flurrying around the question, Gene.
>
> Here's one from 2012:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667616
>
> tags 667616 + wontfix
>
>  Arthur Magill, le Thu 05 Apr 2012 13:10:27 +0200, a écrit :
>  > Can brltty be convinced not to grab this connection?
>
>  It could, but we don't want to, as it would break brltty for people
> who use the braille devices with chips using that ID, making the
> computer completely unusable for them, really not a good thing.
>
> writes Monsieur THIBAULT
>
> > braile facilities being denied the use of such adapters.  Thats
> > discriminatory.  And its a bug that could potentially generate a
> > lawsuit. So I'm going to add the debian-user list to the CC: Maybe
> > someone else with more experience at navigating their way thru
> > bugzilla can do it based on what I've written here.
>
> We are positively discriminating in favor of the blind.
>
> > Cheers, Gene Heskett

Then perhaps the better question is why was it running on a new stretch 
install?   I think it probably could be fixed to keep both camps happy.

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: got a new problem with heyu

[Gene Heskett]

On Tuesday 21 May 2019 05:13:45 am Curt wrote:

> On 2019-05-21, Gene Heskett  wrote:
> > I have no clue what brltty is, its new  to me.  Whats going on?
>
> https://brltty.app/
>
> There's some kind of conflict of interest between the kernel and
> brltty, the latter of which is claiming the device.
>
> If you're not visually impaired, uninstalling the brltty package
> might be a fix.
>
> All gleaned from the thread below (which looks analogous to your
> problem):
>
> https://forums.opensuse.org/showthread.php/520714-Bug-handling-USB-RS2
>32-Serial-cable
>

yup, same nail, same hammer, same log output. Since this reduces the 
ability of a site impaired user to use these adapter devices, it could 
be construed as discriminatory in a court of law. The way I see it, this 
can be dumped in brltty's from yard with instructions to fix it, asap.

I'm not blind although I do have plastic eyes, so I don't have a clue why 
it was even being ran on my machine.  It would have saved me several 
hours, but then there would not be yet another confirmation that brltty 
is indeed broken.

There is also a machine killer bug in hplip, the module hpfax, which can 
kill the usb stuff if it doesn't have anything to do when cron awakens 
it to send a fax. renaming the binary to hpfox so cron can't find it is 
the first fix,  So thats another buglet to be fixed. Both of these need 
to be filed and fixed before an official buster respin. 

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: hp inkjet printer

[didier gaumet]

Le 21/05/2019 à 18:15, Brian a écrit :

> A USB-connected  modern printer is likely not to be a problem; it should
> be capable of IPP-over-USB, for which Debian has the ippusbxd package.
> However, a user needs to be aware that using ippusbxd with an all-in-one
> renders scanning inoperable.

Excellent: impossibility to scan is a trade-off but nonetheless it is
great news and I wasn't even aware of this protocol

> You are correct regarding scanning. This process still requires a driver
> from the vendor, but there are plans to develop driverless scanning for
> Linux during the coming year. Actually, depending on the device, it is
> possible to do it now.

Another excellent perspective :-)

Re: hp inkjet printer

[Brian]

On Tue 21 May 2019 at 10:11:30 +0200, didier gaumet wrote:

> Le 20/05/2019 à 20:30, Brian a écrit :
> > On Mon 20 May 2019 at 17:40:18 +0200, didier gaumet wrote:
> > 
> >> there is a useful page on the HP website about HPLIP and all supported
> >> HP printers:
> >>  
> >> https://developers.hp.com/hp-linux-imaging-and-printing/supported_devices/index
> > 
> > This page is very useful for a legacy printer, which would require
> > HPLIP. A modern printer (which one presumes steef intends to purchase),
> > does not need HPLIP. Unfortunately, users still reach for a driver for
> > a recent HP printer - even though it is completely unnecessary. It is
> > will probably be ages before users catch on and clutching a blanket for
> > setting up printing disappears.
> > 
> 
> I would agree with you Brian, that a driver is unnecessary with a modern
> print-only network printer, but I suppose a driver would be appropriate
> if you prefer to use a USB cable or if the "printer" is a
> printer+scanner combo and you want to be able to scan? :-)

A USB-connected  modern printer is likely not to be a problem; it should
be capable of IPP-over-USB, for which Debian has the ippusbxd package.
However, a user needs to be aware that using ippusbxd with an all-in-one
renders scanning inoperable.

You are correct regarding scanning. This process still requires a driver
from the vendor, but there are plans to develop driverless scanning for
Linux during the coming year. Actually, depending on the device, it is
possible to do it now.

-- 
Brian.

Re: Debian Releases

[Francisco M Neto]

Hello!

On Tue, 2019-05-21 at 16:06 +0100, Paul Sutton wrote:
> On 21/05/2019 03:19, Francisco M Neto wrote:
> > 
> > I've writted the second part, and it should be going up tomorrow
> > morning:
> > 
> > http://fmneto.com.br/en/archives/2019/tracking-the-debian-release-cycle
> > 
> > I hope you like it. 
> > 
> > Cheers!
> Hi Francisco
> 
> Great work
> 
> Have updated my Getting started blog post to include links to both of
> these articles.

Thanks a lot for the shout out! It's a nice introduction guide you got
there as well!

Cheers!
Francisco

-- 
[]'s,

Francisco M Neto

GPG: 4096R/D692FBF0


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

Lectores de huellas biométricos

[Debian]

Buenos días lista:

Estoy con un proyecto para control de acceso de empleados mediante 
lectores biométricos de huellas digitales.
Los que estoy viendo al momento, o son autónomos (todo empaquetado en un 
equipo), o su enlace me obliga a utilizar sistemas ("software") 
privativos, no basados de *nix, si no en Windows.


Pregunta:
¿Conocen de algún equipo lector de huellas digitales de buena desempeño 
que pueda ser manejado desde un servidor Linux?
Manejado me refiero a que el mismo pueda recibir pedidos de un programa 
y emita la respuesta; hay algunos que pueden ser manejados desde una 
página web, y se pueden bajar los datos a mano. Lo que yo necesito es 
que de alguna manera, mediante el cableado UTP pueda leer lo que el 
equipo ha ido almacenando.
Que dentro de lo que el equipo trae en su documentación, esté la forma 
de acceder a, por ejemplo, requerimientos SQL de su motor de base de 
datos interno.


Gracias

JAP

Re: got a new problem with heyu, and it is a bug in bfltty that kills all /dev/ttyUSBnumber's

[Curt]

On 2019-05-21, Gene Heskett  wrote:
>
> This to me is a bug that needs fixed.  No sense in denying someone using 

There are already oldenbugs flurrying around the question, Gene.

Here's one from 2012:

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

tags 667616 + wontfix

 Arthur Magill, le Thu 05 Apr 2012 13:10:27 +0200, a écrit :

 > Can brltty be convinced not to grab this connection?

 It could, but we don't want to, as it would break brltty for people who
 use the braille devices with chips using that ID, making the computer
 completely unusable for them, really not a good thing.

writes Monsieur THIBAULT

> braile facilities being denied the use of such adapters.  Thats 
> discriminatory.  And its a bug that could potentially generate a 
> lawsuit. So I'm going to add the debian-user list to the CC: Maybe 
> someone else with more experience at navigating their way thru bugzilla 
> can do it based on what I've written here.

We are positively discriminating in favor of the blind.

> Cheers, Gene Heskett

Re: Debian Releases

[Paul Sutton]

On 21/05/2019 03:19, Francisco M Neto wrote:
> Thank you all for the answers!
>
> I've writted the second part, and it should be going up tomorrow
> morning:
>
> http://fmneto.com.br/en/archives/2019/tracking-the-debian-release-cycle
>
> I hope you like it. 
>
> Cheers!
Hi Francisco

Great work

Have updated my Getting started blog post to include links to both of
these articles.

Keep up the good work

Paul

Re: Is it possible to install Debian in such a case.

[David Wright]

On Fri 10 May 2019 at 16:18:51 (-0400), Felix Miata wrote:
> David Wright composed on 2019-05-10 13:32 (UTC-0500):
> > On Fri 10 May 2019 at 12:06:05 (-0400), Felix Miata wrote:
> 
> >> what I virtually always do, install from network, beginning with fetching
> >> 
> >> and
> >> 
> >> and placing them where Grub can find and load them.
> 
> > So I'm looking for the page that has those instructions. Do you know
> > where it is? 
> 
> It's not all on https://wiki.debian.org/Grub which only has the standard Grub2
> boilerplate, to get from A to B one must first divert to C and then D. :-p 
> There
> is a small piece of it hidden in its first FAQ (/etc/grub.d/40_custom).
> 
> > It would list the requirements, what to put where, and where in the
> > d-i process you arrive after booting.
> > (d-i ≡ debian-installer, for the OP.)   
> >
> 
> Try putting this in custom.cfg in a bootable stick directory containing 
> grub.cfg:
> 
> menuentry "Install Debian via HTTP" {
>   search --no-floppy --label --set=root 
>   linux   /boot/linux
>   initrd  /boot/initrd.gz
> }
> 
> Once that's done, the stick booted, and the selection made, the d-i app takes 
> over
> by asking the exact same questions as if having booted from the NET iso.
> 
> No USB stick (or OM, or PXE) is needed for linux and initrd.gz if the target
> system already has a loadable Grub (any bootloader really, syslinux, rEFInd,
> others) installed anywhere, which is the standard installation method in my 
> routine.

That's pretty much what I needed to get this sorted out. In my case,
using the hard disk itself, the USBSTICKLABEL is just the LABEL that's
used for the existing system itself, and I copied the files above
straight into /boot, along with all my normal kernels.

As this was new territory, I tried it out on a spare laptop. Checking
the files against the SHA256SUMS, I noticed a lot of different linux
kernels and initrd.gz files which I assume could do a similar job in
slightly different ways. I'm not sure where this is documented.

With your files, I indeed booted straight into the d-i, presumably in
the non-graphical expert version which suited me fully. One or two
wrinkles were:
. I don't know if one could get the remote install over ssh working,
. the firmware is needed on a stick, like in days of yore (or using
  "pure" Debian netinst),
. it appears important to remove the said stick at the earliest
  opportunity else the new system may be installed on the laptop's
  hard drive but with a kernel name of /dev/sdb, which is no good
  when you come to reboot into it.

I don't want to trust overwriting the MBR's boot code, so I said no
the question. I think it then asked for the device anyway, whereupon
I backed out of that screen and then selected 'Continue without
boot loader'. I think that meant that grub wasn't configured at all,
so /boot/grub/unicode.pf2 is the only file in that directory.

Before answering the clock/UTC question, I ran
/target/usr/bin/swaplabel and put back the LABEL on my swap
partition so that the original system would find it as normal.
AFAICT the new installation finds swap by its generated UUID and
my original uses LABEL, so both systems are happy.

After the installation, I used the "Classic Chroot Sequence" to test
the bootability of the new system:

# mount /dev/sda2 /mnt
# mount -o bind /proc /mnt/proc
# mount -o bind /sys /mnt/sys
# mount -o bind /dev /mnt/dev
# chroot /mnt grub-mkconfig > /boot/grub/grub.cfg
# chroot /mnt grub-install /dev/sda

before redoing the last two commands in the old system to restore
the status quo.

> Of course, this much detail shouldn't be needed by those who have more than a
> passing familiarity with using Grub.

Whether this technique is possible is something that depends on
details of booting details like how a kernel finds its root
filesystem, whether it has the wherewithal to read it, what's inside
the initrd.gz files (with their new format) etc, apart from details
of grub.

And I find recipes for grub can be very confusing, with Grub1, Grub2,
grub-pc, and those strange hybrid packages that claimed to be Grub2
but were numbered as version 1. Looking back at past postings here,
one rarely knows precisely which versions of what were being used.

> When I see "we" instead of "I" in an OP, as
> for this thread, I assume "we" means more than one person, a group, which 
> ought to
> possess more than a passing familiarity using Grub, hence my keeping my reply 
> short.

I think expressions like "What I have …" and "What we want …" are just
polite expressions. To me (relatively old), the latter means that the
writer is not wanting to do an 

GIMP on Jessie causes total freeze

[Дмитриев Александр]

Hello, I've encountered a problem with GIMP on Jessie. It causes total system freeze with latest available kernel, but not with the previous. This can be reproduced on at least 2 PCs.I've tried to file a bug via reportbug, but it returns error 500.What are my further steps? uname -a:Linux debian 3.16.0-8-amd64 #1 SMP Debian 3.16.64-2 (2019-04-01) x86_64 GNU/Linuxgimp -v:GNU Image Manipulation Program version 2.8.14git-describe: GIMP_2_8_12-2-ge62e6fe  Alexander. -- С уважением,Дмитриев Александр 

Re: favorites in KDE menu disappear

[Glenn Holmer]

>
> I have my menu set to the "Application Menu" option, with just two
> favorites set up: system settings and Dolphin. But every so often (maybe
> once a week or so), those favorites just disappear from the left side of
> the menu and I have to add them back again.
>

On Sun, May 19, 2019 at 10:06 AM bw  wrote:

> In-Reply-To:  ehjkh_...@mail.gmail.com>
>
> That's not good if the containment stuff is going screwy again, that was a
> bad problem last ver.  Does it seem to happen when you add widgets?  Do
> you have a lot of widgets or desktop icons and things?
>

No Plasma widgets on the screen at all, desktop set to "Desktop" layout
with eight virtual desktops. My setup is stable; I've had it just the way I
want it for quite some time, so it's hard to imagine what the trigger for
this could be.

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

Re: got a new problem with heyu, and it is a bug in bfltty that kills all /dev/ttyUSBnumber's

[Gene Heskett]

On Tuesday 21 May 2019 04:29:55 am you wrote:

> Gene Heskett composed on 2019-05-21 04:17 (UTC-0400):
> > I have no clue what brltty is, its new  to me.  Whats going on?
>
> Past bedtime. Google knew:
> https://github.com/brltty/brltty
> "BRLTTY is a background process (daemon) providing access to the
> Linux/Unix console (when in text mode) for a blind person using a
> refreshable braille display."

daytime again, and time to file a bug report, something I've not tried to 
negotiate since my last mind numbing encounter with the dumbest software 
out there, bugzilla.

It, brltty, should not disable /dev/ttyUSB# when its running. Thats what 
gave it away, when I couldn't make heyu run.  The CM-11a is a serial 
device, with a 4 pin telco plug on one end of its cable, and a db-9 for 
a simple serial port on the other, but since the serial port is already 
occupied, a usb to serial adapter is used and that creates 
a /dev/ttyUSBnumber according to how many there might be.

But between the CM-11a complaining that it needed serviced as it had 
stale data (about 2 weeks worth) to report, it hadn't had since wheezy, 
and brltty's erroring on the CM-11a data it sends once a second till it 
gets serviced when it has some status change to report, /dev/ttyUSB0 was 
being destroyed about 1 second after it was created, I assume by the 
CM-11a data being sent to udev as a string of errors instead of being 
given to heyu which has an automatic response to that sort of incoming 
data.

This to me is a bug that needs fixed.  No sense in denying someone using 
braile facilities being denied the use of such adapters.  Thats 
discriminatory.  And its a bug that could potentially generate a 
lawsuit. So I'm going to add the debian-user list to the CC: Maybe 
someone else with more experience at navigating their way thru bugzilla 
can do it based on what I've written here.

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: got a new problem with heyu

[Gene Heskett]

On Tuesday 21 May 2019 04:17:28 am Gene Heskett wrote:

> On Tuesday 21 May 2019 03:27:14 am Gene Heskett wrote:
> > Greetings all;
> >
> > I just got thru building and installing heyu. But it uses
> > /dev/ttyUSB# which does not exist on stretch.  So where is it moved
> > to?
> >
> > Cheers, Gene Heskett
>
> continued, it seems that the usb-serial adapters I have, all ft232's,
> are no longer recognized.
> I am logging essentially this for any usb to serial cable plugged in:
>
> May 21 04:12:56 coyote kernel: [233588.749172] usb 2-5: new full-speed
> USB device number 24 using ohci-pci
> May 21 04:12:56 coyote kernel: [233588.990150] usb 2-5: New USB device
> found, idVendor=0403, idProduct=6001
> May 21 04:12:56 coyote kernel: [233588.990154] usb 2-5: New USB device
> strings: Mfr=1, Product=2, SerialNumber=3
> May 21 04:12:56 coyote kernel: [233588.990156] usb 2-5: Product: USB
> FAST SERIAL ADAPTER
> May 21 04:12:56 coyote kernel: [233588.990158] usb 2-5: Manufacturer:
> FTDI
> May 21 04:12:56 coyote kernel: [233588.990159] usb 2-5: SerialNumber:
> FTOOS09N
> May 21 04:12:56 coyote kernel: [233588.998182] ftdi_sio 2-5:1.0: FTDI
> USB Serial Device converter detected
> May 21 04:12:56 coyote kernel: [233588.998224] usb 2-5: Detected
> FT232RL May 21 04:12:56 coyote kernel: [233589.004209] usb 2-5: FTDI
> USB Serial Device converter now attached to ttyUSB0
> May 21 04:12:56 coyote mtp-probe: checking bus 2, device
> 24: "/sys/devices/pci:00/:00:02.0/usb2/2-5"
> May 21 04:12:56 coyote mtp-probe: bus: 2, device: 24 was not an MTP
> device
> May 21 04:12:57 coyote kernel: [233589.409147] usb 2-5: usbfs:
> interface 0 claimed by ftdi_sio while 'brltty' sets config #1
> May 21 04:12:57 coyote brltty[523]: USB configuration set error 16:
> Device or resource busy.
> May 21 04:12:57 coyote brltty[523]: brltty: USB configuration set
> error 16: Device or resource busy.
> May 21 04:12:57 coyote brltty[523]: USB interface in use: 0 (ftdi_sio)
> May 21 04:12:57 coyote brltty[523]: brltty: USB interface in use: 0
> (ftdi_sio)
> May 21 04:12:57 coyote kernel: [233589.412361] ftdi_sio ttyUSB0: FTDI
> USB Serial Device converter now disconnected from ttyUSB0
> May 21 04:12:57 coyote kernel: [233589.412385] ftdi_sio 2-5:1.0:
> device disconnected
>
> I have no clue what brltty is, its new  to me.  Whats going on?

Its a braile utility.  I might have plastic eyes but I'm not blind so why 
is it running, and if I kill it, it comes back just by plugging in one 
of those cables.  What the hell sort of a virus is this thing called 
brltty?  Is it uninstallable?, yes, which now gives me a ttyUSB0 when 
one of these 232 adapter cables is plugged in. Now to find out why it 
really isn't working. Had to set perms to 0777 on the whole path to its 
log. ISTR I had to do something along those lines for wheezy too, years 
ago now. And now its working.
>
> Cheers, Gene Heskett


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: kvm win8 guest audio is terrible.

[Bob Weber]

On 5/20/19 10:35 PM, David Christensen wrote:

On 5/20/19 2:55 PM, R. Ramesh wrote:
I created a fresh install of debian stretch amd64. In that I created a 
qemu/kvm guess install of win8. It only accepted hda as a valid sound card. 
All others show us without drivers. So, I am limited to only HDA as -soundhw. 
Further HDA sounds so broken if I try to test with any sound file or youtube 
video. It is grainy/distorted and outright horrible.


Google searches mentions something about MSI and those approaches are simply 
not accepted by win8. So, I could not use them. I am wondering if there is 
something fundamentally wrong with windows guests or is there a setting that 
I missing.


Ramesh
Have you tried spice under Virtual Machine manager?  I used to have similar 
problems.  Let all 6 cores run at maximum speed helped some but still occasional 
dropouts in Win7 and Win10.  I switched to spice and audio and video improved 
greatly.

--


*...Bob*

Re: trouble with my network card

[Greg Wooledge]

On Tue, May 21, 2019 at 07:05:49AM -0400, BELAHCENE Abdelkader wrote:
> I have a trouble with my network card (extern card)
> lspci gives:
> 04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
> RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 02)
> mii-tool  enp4s0
> SIOCGMIIPHY on 'enp4s0' failed: No such device

I would suggest you try installing the firmware-realtek package (it's
non-free) if you haven't already done so.  Then reboot.

https://packages.debian.org/stretch/firmware-realtek

Re: trouble with my network card

[Pascal Hambourg]

Le 21/05/2019 à 13:05, BELAHCENE Abdelkader a écrit :

Hi,
I have a trouble with my network card (extern card)


What do you mean by "extern card" ? It looks like an internal PCIe card.


lspci gives:
04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 02)
mii-tool  enp4s0
SIOCGMIIPHY on 'enp4s0' failed: No such device


You may have better luck with ethtool instead of mii-tool.


ifconfig  enp4s0
enp4s0: flags=4098  mtu 1500


The interface is not UP.

trouble with my network card

[BELAHCENE Abdelkader]

Hi,
I have a trouble with my network card (extern card)
lspci gives:
04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 02)
mii-tool  enp4s0
SIOCGMIIPHY on 'enp4s0' failed: No such device

ifconfig  enp4s0
enp4s0: flags=4098  mtu 1500
inet 192.168.10.20  netmask 255.255.255.0  broadcast 192.168.10.255
ether 00:e0:4c:68:0d:d7  txqueuelen 1000  (Ethernet)
RX packets 32  bytes 1920 (1.8 KiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 0  bytes 0 (0.0 B)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
I can ping it in the local machine
but not from another machine,  the lightspot of the card is off !!!

What is happening ??  mii-tool doesn't find it but I can put an address??

thanks for help
regards

Re: got a new problem with heyu

[Curt]

On 2019-05-21, Gene Heskett  wrote:
>
> I have no clue what brltty is, its new  to me.  Whats going on?

https://brltty.app/

There's some kind of conflict of interest between the kernel and
brltty, the latter of which is claiming the device.

If you're not visually impaired, uninstalling the brltty package
might be a fix.

All gleaned from the thread below (which looks analogous to your
problem):

https://forums.opensuse.org/showthread.php/520714-Bug-handling-USB-RS232-Serial-cable

> Cheers, Gene Heskett

Re: got a new problem with heyu

[Jonas Smedegaard]

Quoting Gene Heskett (2019-05-21 10:17:28)
> On Tuesday 21 May 2019 03:27:14 am Gene Heskett wrote:
> I have no clue what brltty is, its new  to me.  Whats going on?

$ LANG=C apt-cache search brltty
brltty - Access software for a blind person using a braille display
brltty-espeak - Access software for a blind person - espeak driver
brltty-flite - Access software for a blind person - Flite speech driver
brltty-speechd - Access software for a blind person - Speech Dispatcher driver
brltty-x11 - Access software for a blind person using a braille display - X11 
drivers
cl-brlapi - Common Lisp bindings for BrlAPI
libbrlapi-dev - Library for communication with BRLTTY - static libs and headers
libbrlapi-java - Java bindings for BrlAPI
libbrlapi-jni - Java bindings for BrlAPI (native library)
libbrlapi0.6 - braille display access via BRLTTY - shared library
python-brlapi - Braille display access via BRLTTY - Python bindings
python3-brlapi - Braille display access via BRLTTY - Python3 bindings
xbrlapi - Access software for a blind person using a braille display - xbrlapi
cicero - French and English Text-To-Speech for MBROLA

https://duckduckgo.com/?q=brltty provides additional clueful hits.

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Re: got a new problem with heyu

[Gene Heskett]

On Tuesday 21 May 2019 03:27:14 am Gene Heskett wrote:

> Greetings all;
>
> I just got thru building and installing heyu. But it uses /dev/ttyUSB#
> which does not exist on stretch.  So where is it moved to?
>
> Cheers, Gene Heskett
continued, it seems that the usb-serial adapters I have, all ft232's, are 
no longer recognized.
I am logging essentially this for any usb to serial cable plugged in:

May 21 04:12:56 coyote kernel: [233588.749172] usb 2-5: new full-speed 
USB device number 24 using ohci-pci
May 21 04:12:56 coyote kernel: [233588.990150] usb 2-5: New USB device 
found, idVendor=0403, idProduct=6001
May 21 04:12:56 coyote kernel: [233588.990154] usb 2-5: New USB device 
strings: Mfr=1, Product=2, SerialNumber=3
May 21 04:12:56 coyote kernel: [233588.990156] usb 2-5: Product: USB FAST 
SERIAL ADAPTER
May 21 04:12:56 coyote kernel: [233588.990158] usb 2-5: Manufacturer: 
FTDI
May 21 04:12:56 coyote kernel: [233588.990159] usb 2-5: SerialNumber: 
FTOOS09N
May 21 04:12:56 coyote kernel: [233588.998182] ftdi_sio 2-5:1.0: FTDI USB 
Serial Device converter detected
May 21 04:12:56 coyote kernel: [233588.998224] usb 2-5: Detected FT232RL
May 21 04:12:56 coyote kernel: [233589.004209] usb 2-5: FTDI USB Serial 
Device converter now attached to ttyUSB0
May 21 04:12:56 coyote mtp-probe: checking bus 2, device 
24: "/sys/devices/pci:00/:00:02.0/usb2/2-5"
May 21 04:12:56 coyote mtp-probe: bus: 2, device: 24 was not an MTP 
device
May 21 04:12:57 coyote kernel: [233589.409147] usb 2-5: usbfs: interface 
0 claimed by ftdi_sio while 'brltty' sets config #1
May 21 04:12:57 coyote brltty[523]: USB configuration set error 16: 
Device or resource busy.
May 21 04:12:57 coyote brltty[523]: brltty: USB configuration set error 
16: Device or resource busy.
May 21 04:12:57 coyote brltty[523]: USB interface in use: 0 (ftdi_sio)
May 21 04:12:57 coyote brltty[523]: brltty: USB interface in use: 0 
(ftdi_sio)
May 21 04:12:57 coyote kernel: [233589.412361] ftdi_sio ttyUSB0: FTDI USB 
Serial Device converter now disconnected from ttyUSB0
May 21 04:12:57 coyote kernel: [233589.412385] ftdi_sio 2-5:1.0: device 
disconnected

I have no clue what brltty is, its new  to me.  Whats going on?

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: hp inkjet printer

[didier gaumet]

Le 20/05/2019 à 20:30, Brian a écrit :
> On Mon 20 May 2019 at 17:40:18 +0200, didier gaumet wrote:
> 
>> there is a useful page on the HP website about HPLIP and all supported
>> HP printers:
>>  
>> https://developers.hp.com/hp-linux-imaging-and-printing/supported_devices/index
> 
> This page is very useful for a legacy printer, which would require
> HPLIP. A modern printer (which one presumes steef intends to purchase),
> does not need HPLIP. Unfortunately, users still reach for a driver for
> a recent HP printer - even though it is completely unnecessary. It is
> will probably be ages before users catch on and clutching a blanket for
> setting up printing disappears.
> 

I would agree with you Brian, that a driver is unnecessary with a modern
print-only network printer, but I suppose a driver would be appropriate
if you prefer to use a USB cable or if the "printer" is a
printer+scanner combo and you want to be able to scan? :-)

(In fact the OP said he wants a simpler printer than his MP280 (a combo)
but I am at a loss to interpret this as a true print-only printer or a
more user-friendly and less cumbersome printer+scanner combo)

Re: Buster emacs crashes with doc-view-mode

[Curt]

On 2019-05-21, Boyan Penkov  wrote:
> Hello folks,
>
> In EMACS, I often switch between doc-view and pdf-view to read PDFs.
> Occasionally, EMACS crashes with this backtrace:
>
> Backtrace:
> emacs[0x5114ce]
> emacs[0x4f6eda]
> emacs[0x50f9ae]
> emacs[0x50fbc8]
> emacs[0x50fcb9]
> /lib/x86_64-linux-gnu/libpthread.so.0(+0x12730)[0x7fea71fd8730]
> /lib/x86_64-linux-gnu/libc.so.6(+0xa214f)[0x7fea71b5214f]
> /usr/lib/x86_64-linux-gnu/libMagickCore-6.Q16.so.6(ReadBlob+0x21e)[0x7fea72fd8fae]
> /usr/lib/x86_64-linux-gnu/ImageMagick-6.9.10/modules-Q16/coders/png.so(+0x4e9e)[0x7fea64b5be9e]
> /usr/lib/x86_64-linux-gnu/libpng16.so.16(+0x1a90f)[0x7fea7544f90f]
> /usr/lib/x86_64-linux-gnu/libpng16.so.16(+0x1a9ea)[0x7fea7544f9ea]
> /usr/lib/x86_64-linux-gnu/libpng16.so.16(+0x1f3b2)[0x7fea754543b2]
> /usr/lib/x86_64-linux-gnu/libpng16.so.16(png_read_row+0x10f)[0x7fea7544681f]
> /usr/lib/x86_64-linux-gnu/ImageMagick-6.9.10/modules-Q16/coders/png.so(+0xccdf)[0x7fea64b63cdf]
> /usr/lib/x86_64-linux-gnu/ImageMagick-6.9.10/modules-Q16/coders/png.so(+0xda9e)[0x7fea64b64a9e]
> /usr/lib/x86_64-linux-gnu/libMagickCore-6.Q16.so.6(ReadImage+0x320)[0x7fea7300fc20]
> /usr/lib/x86_64-linux-gnu/libMagickWand-6.Q16.so.6(MagickReadImage+0x6a)[0x7fea732f16aa]
> emacs[0x5e3dbd]
> emacs[0x5ecc4e]
> emacs[0x5ed150]
> emacs[0x56dc2c]
> emacs[0x5a5260]
> emacs[0x56dbab]
> emacs[0x5a5260]
> emacs[0x56dbab]
> emacs[0x5a5260]
> emacs[0x56dbab]
> emacs[0x56f92a]
> emacs[0x56dc2c]
> emacs[0x5a5260]
> emacs[0x56dbab]
> emacs[0x56dcea]
> emacs[0x4fd42f]
> emacs[0x4fd7e5]
> emacs[0x4fe2c8]
> emacs[0x500b28]
> emacs[0x5b03a8]
> emacs[0x4244ba]
> emacs[0x50319b]
> emacs[0x504900]
> emacs[0x505fd4]
> ...
>
> [1]  + bus error  emacs
>
> This is intensely annoying, since I usually have ~100 PDFs open.  Any ideas?
>
> Cheers!

Your backtrace looks quite similar to this:

http://codepad.org/juUbz33Q
https://www.reddit.com/r/emacs/comments/9xrjto/emacs_latex_docview_bug_crashes_emacs/

The OP believes his issue is related to the 'doc-view-resolution'
parameter (when reverting from 300 to a setting of 100 the crash doesn't
seem to occur for him).

got a new problem with heyu

[Gene Heskett]

Greetings all;

I just got thru building and installing heyu. But it uses /dev/ttyUSB# 
which does not exist on stretch.  So where is it moved to?

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: Keyboard not responding after exiting X

[Rodolfo Medina]

Brian  writes:

> On Mon 20 May 2019 at 21:29:44 +, Rodolfo Medina wrote:
>
>> Full-upgraded yesterday to Sid, it seems not technically possible to
>> downgrade now to Buster...
>
> I never said this was what you could do. The suggestion was to revert
> to systemd 241-3.

Yes, thanks...  But, as suggested here:

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


Am 19.05.19 um 21:13 schrieb S R Wright:
> Is this confined to systemd 241-4?  Will back-revving to 241-3 be a
> sufficient workaround?

It will. To satisfy dependencies, you'll need to downgrade libsystemd0
as well (and libpam-systemd, libnss-systemd, systemd-* in case you have
those installed)


it's a quite delicate issue...  After all, since I can shut off PC with
external button, I can survive with the problem until fixed...  rather than
facing such a delicate matter (so it seems to me to be).

Rodolfo