Re: ssh-keygen as a regular user

[Jeremy Ardley]

On 11/5/23 11:22, Igor Korot wrote:


[code]
igor@wxTest:~/wxwidgets$ ssh-keygem
bash: ssh-keygem: command not found
igor@wxTest:~/wxwidgets$ su
Password:
root@wxTest:/home/igor/wxwidgets# apt-get install openssh-client
Reading package lists... Done
Building dependency tree
Reading state information... Done
openssh-client is already the newest version (1:7.9p1-10+deb10u2).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@wxTest:/home/igor/wxwidgets# ssh-keygen
Generating public/private rsa key pair.
Enter file in which to save the key (/root/.ssh/id_rsa): ^C
root@wxTest:/home/igor/wxwidgets#
[/code]

[code]
igor@wxTest:~/wxwidgets$ ls -la ~/.ssh
ls: cannot access '/home/igor/.ssh': No such file or directory
igor@wxTest:~/wxwidgets$
[/code[


ssh-keygen usually works better than ssh-keygem

try

cd

mkdir .ssh

ssh-keygen


--
Jeremy
(Lists)

Re: ssh-keygen as a regular user

[Igor Korot]

Hi,

On Fri, May 12, 2023 at 12:19 AM Geert Stappers  wrote:
>
> On Fri, May 12, 2023 at 12:07:00AM -0500, Igor Korot wrote:
> > Hi, ALL,
> > Is there a reason I can't run "ssh-keygen" as a regular user?
>
> Several  :-)
>
>
> > I am able to do it as "root" though, but I think it shouldn't happen.
> >
> > Can someone shed some light?
>
> Find a better way to open a discussion as a closed question[1].
>
>
> > Thank you.
>
> Start with sharing information how to reproduce[2] the issue.

[code]
igor@wxTest:~/wxwidgets$ ssh-keygem
bash: ssh-keygem: command not found
igor@wxTest:~/wxwidgets$ su
Password:
root@wxTest:/home/igor/wxwidgets# apt-get install openssh-client
Reading package lists... Done
Building dependency tree
Reading state information... Done
openssh-client is already the newest version (1:7.9p1-10+deb10u2).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@wxTest:/home/igor/wxwidgets# ssh-keygen
Generating public/private rsa key pair.
Enter file in which to save the key (/root/.ssh/id_rsa): ^C
root@wxTest:/home/igor/wxwidgets#
[/code]

[code]
igor@wxTest:~/wxwidgets$ ls -la ~/.ssh
ls: cannot access '/home/igor/.ssh': No such file or directory
igor@wxTest:~/wxwidgets$
[/code[

This is on the brand new install.

And I need that to access Git...

Thank you.

>
>
> Groeten
> Geert Stappers
>
> [1] Avoid questions that can be answered with 'yes' or 'no'.
> [2] Describe what is happening at your side. Tell about
> commands used and "errors" seen.
> --
> Silence is hard to parse
>

Re: ssh-keygen as a regular user

[Geert Stappers]

On Fri, May 12, 2023 at 12:07:00AM -0500, Igor Korot wrote:
> Hi, ALL,
> Is there a reason I can't run "ssh-keygen" as a regular user?
 
Several  :-)


> I am able to do it as "root" though, but I think it shouldn't happen.
> 
> Can someone shed some light?
 
Find a better way to open a discussion as a closed question[1].


> Thank you.

Start with sharing information how to reproduce[2] the issue.


Groeten
Geert Stappers

[1] Avoid questions that can be answered with 'yes' or 'no'.
[2] Describe what is happening at your side. Tell about
commands used and "errors" seen.
-- 
Silence is hard to parse

Re: ssh-keygen as a regular user

[Jeremy Ardley]

On 12/5/23 13:07, Igor Korot wrote:

Hi, ALL,
Is there a reason I can't run "ssh-keygen" as a regular user?

I am able to do it as "root" though, but I think it shouldn't happen.


Check the file permissions and ownership of ~/.ssh files ?



--
Jeremy
(Lists)

ssh-keygen as a regular user

[Igor Korot]

Hi, ALL,
Is there a reason I can't run "ssh-keygen" as a regular user?

I am able to do it as "root" though, but I think it shouldn't happen.

Can someone shed some light?

Thank you.

Re: GIT problem

[tomas]

On Thu, May 11, 2023 at 07:05:21PM -0400, Stefan Monnier wrote:
> >   git remote remove origin
> >   # this re-adds it
> >   git remote add origin 
> 
> Better go with
> 
> git remote set-url origin 

Right :)

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: W: Possible missing firmware /lib/firmware/brand/yada*

[Felix Miata]

Sven Joachim composed on 2023-04-29 09:02 (UTC-+0200):

> On 2023-04-28 21:30 -0400, Felix Miata wrote:
 
>> # inxi -Gxx
>> Graphics:
>>   Device-1: Intel 82Q963/Q965 Integrated Graphics vendor: Dell driver: i915
>> v: kernel arch: Gen-4 ports: active: DVI-D-1 empty: VGA-1 bus-ID: 00:02.0
>> chip-ID: 8086:2992   # aka ancient
>> # grep MODULES /etc/initramfs-tools/initramfs.conf
>> # MODULES: [ most | netboot | dep | list ]
>> MODULES=dep
>> #

>> These many per transaction $SUBJECT initrd construction messages have been 
>> routine
>> for a long time in Bullseye and Bookworm regardless of active GPU installed, 
>> and
>> whether or not a firmware-brand-graphics .deb exists and is installed
>> for it.
 
> It would be useful to give an example of these messages, as well as a
> list of firmware packages you have installed.
 
>> Is there something that can be done to avoid this screen and log
>> litter?
 
> Install the package that contains the firmware files.  For Intel and
> NVidia graphics that is firmware-misc-nonfree, for AMD it is
> firmware-amd-graphics.
 
>> Can anyone
>> point to an existing meta-bug report on the subject of stopping the litter?
>> Searching seems to find only reports pointing to particular GPUs, e.g.
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016286
 
> It's the same for any GPUs, as well as for other hardware.  The
> update-initramfs script runs modinfo(8) to find out which firmware files
> a loaded module might request and issues a warning for any such file
> which is not there.  You can check the code for yourself[1].

> 1. https://sources.debian.org/src/initramfs-tools/0.142/hook-functions/#L109
 
# time apt-get full-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
  linux-image-5.17.0-1-amd64 linux-image-5.19.0-2-amd64
Use 'apt autoremove' to remove them.
The following NEW packages will be installed:
  linux-image-6.1.0-8-amd64
The following packages will be upgraded:
  linux-image-amd64
1 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 77.2 MB of archives.
After this operation, 575 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://ftp.debian.org/debian bookworm/main amd64 
linux-image-6.1.0-8-amd64 amd64 6.1.25-1 [77.2 MB]
Get:2 http://ftp.debian.org/debian bookworm/main amd64 linux-image-amd64 amd64 
6.1.25-1 [1,480 B]
Fetched 77.2 MB in 7s (11.1 MB/s)
Reading changelogs... Done
Selecting previously unselected package linux-image-6.1.0-8-amd64.
(Reading database ... 95624 files and directories currently installed.)
Preparing to unpack .../linux-image-6.1.0-8-amd64_6.1.25-1_amd64.deb ...
Unpacking linux-image-6.1.0-8-amd64 (6.1.25-1) ...
Preparing to unpack .../linux-image-amd64_6.1.25-1_amd64.deb ...
Unpacking linux-image-amd64 (6.1.25-1) over (6.1.20-1) ...
Setting up linux-image-6.1.0-8-amd64 (6.1.25-1) ...
I: /vmlinuz.old is now a symlink to boot/vmlinuz-6.1.0-7-amd64
I: /initrd.img.old is now a symlink to boot/initrd.img-6.1.0-7-amd64
I: /vmlinuz is now a symlink to boot/vmlinuz-6.1.0-8-amd64
I: /initrd.img is now a symlink to boot/initrd.img-6.1.0-8-amd64
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-6.1.0-8-amd64
W: Possible missing firmware /lib/firmware/i915/skl_huc_2.0.0.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/bxt_huc_2.0.0.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/kbl_huc_4.0.0.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/glk_huc_4.0.0.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/kbl_huc_4.0.0.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/kbl_huc_4.0.0.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/cml_huc_4.0.0.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/icl_huc_9.0.0.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/ehl_huc_9.0.0.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/ehl_huc_9.0.0.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.9.3.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.9.3.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/dg1_huc.bin for module i915
W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.9.3.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/tgl_huc.bin for module i915
W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.9.3.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/tgl_huc.bin for module i915
W: Possible missing firmware /lib/firmware/i915/skl_guc_70.1.1.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/bxt_guc_70.1.1.bin for module 
i915
W: Possible missing firmware /lib/firmware/i9

Re: SOLVED:Re: repeat of previous question that has goneunansweredseveraltimes.

[gene heskett]

On 5/11/23 19:41, Vincent Lefevre wrote:

On 2023-05-11 18:24:39 -0400, Greg Wooledge wrote:

On Thu, May 11, 2023 at 11:58:56PM +0200, Vincent Lefevre wrote:

On 2023-05-11 12:08:01 -0400, gene heskett wrote:

Aha Got it, geany evince okular etc can now print from bpi54! Removing
the Listen localhost:631 directive from /etc/cups/cupsd.conf and inserting a

Listen 192.168.xx.yy:631

made the localhost:631/printers on this machine show up in FF on bpi54, all
5 choices from this machine.


Any explanation?


Seems obvious enough to me.  CUPS on bpi54 was only listening to
loopback (localhost), but Gene wanted to print through it remotely.
So he had to make it listen to the network instead.


My question was more on why does this affect localhost:631/printers?


My questions would be:

1) Can you put *both* Listen lines in, to keep loopback working?


The cupsd.conf(5) man page says: "Multiple Listen directives can be
provided to listen on multiple addresses."


My results seem to indicate otherwise.


2) Failing that, can you use 0.0.0.0 as the Listen address, to listen on
all interfaces?  That's the normal convention.


According to the cupsd.conf(5) man page, you can use "Listen *:631".


The possibility exists that the star goes thru a different path, which 
works. untested here. But folks, that isn't a SWAG, its a plain old WAG.


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, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: SOLVED:Re: repeat of previous question that has goneunansweredseveraltimes.

[gene heskett]

On 5/11/23 18:25, Greg Wooledge wrote:

On Thu, May 11, 2023 at 11:58:56PM +0200, Vincent Lefevre wrote:

On 2023-05-11 12:08:01 -0400, gene heskett wrote:

Aha Got it, geany evince okular etc can now print from bpi54! Removing
the Listen localhost:631 directive from /etc/cups/cupsd.conf and inserting a

Listen 192.168.xx.yy:631

made the localhost:631/printers on this machine show up in FF on bpi54, all
5 choices from this machine.


Any explanation?


Seems obvious enough to me.  CUPS on bpi54 was only listening to
loopback (localhost), but Gene wanted to print through it remotely.
So he had to make it listen to the network instead.


Close, I wanted to be able to print from the bpi from any app on the bpi 
that had a print this option.  Now I can.


My questions would be:

1) Can you put *both* Listen lines in, to keep loopback working?


No, that kills the cups ability to query the network even with the 
Server named in client.conf. It even logs it as a failure, on the bpi5 
but doesn't say why.



2) Failing that, can you use 0.0.0.0 as the Listen address, to listen on
all interfaces?  That's the normal convention.


Untried, so can't say.  And I've not read far enough to see that as an 
example.


Thanks Greg.

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, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: SOLVED:Re: repeat of previous question that has goneunansweredseveraltimes.

[gene heskett]

On 5/11/23 17:59, Vincent Lefevre wrote:

On 2023-05-11 12:08:01 -0400, gene heskett wrote:

Aha Got it, geany evince okular etc can now print from bpi54! Removing
the Listen localhost:631 directive from /etc/cups/cupsd.conf and inserting a

Listen 192.168.xx.yy:631

made the localhost:631/printers on this machine show up in FF on bpi54, all
5 choices from this machine.


Any explanation?

My best guess is the Server directive in client.conf was rejected 
because there was already a couple "Listen" directives pointing at 
itself.  Remove the main one and the client.conf was able to take over.
Or the substition of a "Listen ipv4-address-of-server:631" is also a 
possibility.


Whatever, the point now is that it Just Works.

A lot of hacking on C-89 has taken place since the last C book was 
published by K&R, so I am not the C guru I was in the 1990's.


I'm now 88 yo and some of me has gone to the dogs too.  Take that as an 
admission that my diagnosis might be wrong, but I've been chasing 
electrons to make then do useful work since about 1948 when I quit 
school and went to work fixing them new fangled things called tv's.


Take care & stay well, Vincent.

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, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: SOLVED:Re: repeat of previous question that has gone unansweredseveraltimes.

[Vincent Lefevre]

On 2023-05-11 18:24:39 -0400, Greg Wooledge wrote:
> On Thu, May 11, 2023 at 11:58:56PM +0200, Vincent Lefevre wrote:
> > On 2023-05-11 12:08:01 -0400, gene heskett wrote:
> > > Aha Got it, geany evince okular etc can now print from bpi54! Removing
> > > the Listen localhost:631 directive from /etc/cups/cupsd.conf and 
> > > inserting a
> > > 
> > > Listen 192.168.xx.yy:631
> > > 
> > > made the localhost:631/printers on this machine show up in FF on bpi54, 
> > > all
> > > 5 choices from this machine.
> > 
> > Any explanation?
> 
> Seems obvious enough to me.  CUPS on bpi54 was only listening to
> loopback (localhost), but Gene wanted to print through it remotely.
> So he had to make it listen to the network instead.

My question was more on why does this affect localhost:631/printers?

> My questions would be:
> 
> 1) Can you put *both* Listen lines in, to keep loopback working?

The cupsd.conf(5) man page says: "Multiple Listen directives can be
provided to listen on multiple addresses."

> 2) Failing that, can you use 0.0.0.0 as the Listen address, to listen on
>all interfaces?  That's the normal convention.

According to the cupsd.conf(5) man page, you can use "Listen *:631".

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Re: GIT problem

[Stefan Monnier]

>   git remote remove origin
>   # this re-adds it
>   git remote add origin 

Better go with

git remote set-url origin 


-- Stefan

Re: SOLVED:Re: repeat of previous question that has gone unansweredseveraltimes.

[Greg Wooledge]

On Thu, May 11, 2023 at 11:58:56PM +0200, Vincent Lefevre wrote:
> On 2023-05-11 12:08:01 -0400, gene heskett wrote:
> > Aha Got it, geany evince okular etc can now print from bpi54! Removing
> > the Listen localhost:631 directive from /etc/cups/cupsd.conf and inserting a
> > 
> > Listen 192.168.xx.yy:631
> > 
> > made the localhost:631/printers on this machine show up in FF on bpi54, all
> > 5 choices from this machine.
> 
> Any explanation?

Seems obvious enough to me.  CUPS on bpi54 was only listening to
loopback (localhost), but Gene wanted to print through it remotely.
So he had to make it listen to the network instead.

My questions would be:

1) Can you put *both* Listen lines in, to keep loopback working?

2) Failing that, can you use 0.0.0.0 as the Listen address, to listen on
   all interfaces?  That's the normal convention.

Re: SOLVED:Re: repeat of previous question that has gone unansweredseveraltimes.

[Vincent Lefevre]

On 2023-05-11 12:08:01 -0400, gene heskett wrote:
> Aha Got it, geany evince okular etc can now print from bpi54! Removing
> the Listen localhost:631 directive from /etc/cups/cupsd.conf and inserting a
> 
> Listen 192.168.xx.yy:631
> 
> made the localhost:631/printers on this machine show up in FF on bpi54, all
> 5 choices from this machine.

Any explanation?

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Re: SOLVED:Re: repeat of previous question that has gone unansweredseveraltimes.

[Brian]

On Thu 11 May 2023 at 12:08:01 -0400, gene heskett wrote:

> On 5/11/23 07:07, Brian wrote:
> > On Wed 10 May 2023 at 16:02:43 -0400, gene heskett wrote:
> > 
> > > On 5/10/23 14:22, Brian wrote:
> > > > On Wed 10 May 2023 at 13:18:07 -0400, gene heskett wrote:
> > > > 
> > > > > On 5/10/23 11:29, Brian wrote:
> > > > > > On Wed 10 May 2023 at 10:04:47 -0400, gene heskett wrote:
> > > > > > 
> > > > > > > On 5/10/23 08:17, Brian wrote:
> > > > > 
> > > > > > [...]
> > > > 
> > > > > > Is /etc/cups/client,conf really, really needed?
> > > > > > 
> > > > > That is the first thing cups docs tell you to do, see "printer 
> > > > > sharing"
> > > > 
> > > > A link would be ever so useful.
> > > 
> > > send browser to cups.org, click help, in right pane, click "printer
> > > sharing", scroll down about a screenfull to Automatic using IPP
> > 
> > Thanks to you and debian-u...@howorth.org.uk. Note that this page is for 
> > Apple
> > CUPS. The one for Debian CUPS is at
> > 
> >https://openprinting.github.io/cups/doc/sharing.html
> > 
> Thank you for that link, the other Apple Cups link is first in a google
> search, and probably close in DDG too since the search was for cups, not
> openprinting as I was not then aware that Mike had moved.  Apple should be
> ashamed of themselves hanging onto the cups links when they are no longer
> writing the authors paychecks.
> 
> > Havong said that, it should also be noted that the /etc/cups/client.conf is 
> > used
> > when a local spooler is not required and is presented as to be used only as
> > absolutely necessary. Hardly "the first thing cups docs tell you to do". 
> > Why is
> > it absolutely necessary in your situation?
> > 
> > Additionally, a client.conf overrides the default local  server. All the 
> > analysis
> > in this thread has been carried out assuming a functional local  server, so 
> > I do
> > not know where that leaves us now if a client.conf has been in the mix all 
> > the time..
> > 
> I am wondering now if I shouldn't remove the other Listen directives from
> cupsd.conf, isolating their influence when there are no locally connected
> printers.
> 
> Aha Got it, geany evince okular etc can now print from bpi54! Removing
> the Listen localhost:631 directive from /etc/cups/cupsd.conf and inserting a
> 
> Listen 192.168.xx.yy:631
> 
> made the localhost:631/printers on this machine show up in FF on bpi54, all
> 5 choices from this machine.  All that as root of course, and the acid test
> was me as 1st user, calling up geany to edit that file, which complained it
> was not writable but to print it on the B&W laser, which it just did. I did
> have to leave active the "Listen /run/cups/cups.sock" line, it did not work
> w/o that.
> 
> I changed the LogLevel back to warn before it fills up a 64BG card, and it
> seems its all Just Working.
> 
> That warning in the paragraph above s/not be a show stopper when there is
> only one machine as the Server on this local network. IMO, it should be
> speced as applying to any machine that does NOT have any locally connected
> printers.
> 
> Your help, and some comments from Greg, have been very helpful.  Thank you
> both for bearing with me, most appreciated.

You are, as uaual, treading your own path. Sometimes, it touches on mine
or crosses it. Let's leave it there. The acknowledgement is gracious and
appreciated.

-- 
Brian.

KALARM not working

[Van Snyder]

I had been using KALARM for a very long time.

Now, it's stopped displaying anything, stopped reminding of anything,
and stopped allowing me to add alarms.

When I try to add a new alarm, it refuses to do it. It pops up an error
window "Failed to create alarm."

Do you know how to repair it? I've tried deleting all the akonadi files
and directories under ~/.local, but that doesn't repair it.


I don't understand the advantage of using Akonadi in place of cron.

What alternatives do you suggest?

I'm still using Debian 10, waiting for the problems to calm down. KDE
Plasma version is 5.14.5, Frameworks version is 5.54.0.

Re: repeat of previous question that has gone unansweredseveraltimes.

[gene heskett]

On 5/11/23 07:09, Brian wrote:

On Wed 10 May 2023 at 15:51:53 -0400, gene heskett wrote:


On 5/10/23 14:22, Brian wrote:


[...]


After appreciating that bpi51 has libnss-mdns installed, you might discard any
assumption that nsswitch.conf on bpi54 has the same contents.


I don't believe any of these 4 bpi's have libnss-mdns installed, locate
after a sudo updatedb, cannot find it on either of the 2 that are live on
this net ATM.


bpi51 has avahi-browse. avahi-browse depends on avahi-daemon. avahi-daemon
recommends libnss-mdns.
  

Now. I modified /etc/cups/cupsd.conf to change loglevel to debug2, and add
Listen 192.168.xx.yy:631, then restarted cups, getting this notice in
/var/log/cups/error_log:


This is on bpi54? I do not believe a change to /etc/cups/cupsd.conf is
necessary.

Yes, it was necessary, see my previous post. Not determined is the need 
for a client.conf file with its contents, I rather suspect it might 
still be required as its the only "Server" specification in the whole 
shebang.


Take care & stay well.

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, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

SOLVED:Re: repeat of previous question that has gone unansweredseveraltimes.

[gene heskett]

On 5/11/23 07:07, Brian wrote:

On Wed 10 May 2023 at 16:02:43 -0400, gene heskett wrote:


On 5/10/23 14:22, Brian wrote:

On Wed 10 May 2023 at 13:18:07 -0400, gene heskett wrote:


On 5/10/23 11:29, Brian wrote:

On Wed 10 May 2023 at 10:04:47 -0400, gene heskett wrote:


On 5/10/23 08:17, Brian wrote:



[...]



Is /etc/cups/client,conf really, really needed?


That is the first thing cups docs tell you to do, see "printer sharing"


A link would be ever so useful.


send browser to cups.org, click help, in right pane, click "printer
sharing", scroll down about a screenfull to Automatic using IPP


Thanks to you and debian-u...@howorth.org.uk. Note that this page is for Apple
CUPS. The one for Debian CUPS is at

   https://openprinting.github.io/cups/doc/sharing.html

Thank you for that link, the other Apple Cups link is first in a google 
search, and probably close in DDG too since the search was for cups, not 
openprinting as I was not then aware that Mike had moved.  Apple should 
be ashamed of themselves hanging onto the cups links when they are no 
longer writing the authors paychecks.



Havong said that, it should also be noted that the /etc/cups/client.conf is used
when a local spooler is not required and is presented as to be used only as
absolutely necessary. Hardly "the first thing cups docs tell you to do". Why is
it absolutely necessary in your situation?

Additionally, a client.conf overrides the default local  server. All the 
analysis
in this thread has been carried out assuming a functional local  server, so I do
not know where that leaves us now if a client.conf has been in the mix all the 
time..

I am wondering now if I shouldn't remove the other Listen directives 
from cupsd.conf, isolating their influence when there are no locally 
connected printers.


Aha Got it, geany evince okular etc can now print from bpi54! 
Removing the Listen localhost:631 directive from /etc/cups/cupsd.conf 
and inserting a


Listen 192.168.xx.yy:631

made the localhost:631/printers on this machine show up in FF on bpi54, 
all 5 choices from this machine.  All that as root of course, and the 
acid test was me as 1st user, calling up geany to edit that file, which 
complained it was not writable but to print it on the B&W laser, which 
it just did. I did have to leave active the "Listen /run/cups/cups.sock" 
line, it did not work w/o that.


I changed the LogLevel back to warn before it fills up a 64BG card, and 
it seems its all Just Working.


That warning in the paragraph above s/not be a show stopper when there 
is only one machine as the Server on this local network. IMO, it should 
be speced as applying to any machine that does NOT have any locally 
connected printers.


Your help, and some comments from Greg, have been very helpful.  Thank 
you both for bearing with me, most appreciated.


Take care & stay well.

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, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

AW: AW: EPSON ET M 1120 new printer: If You can read this, you are using the wrong driver

[Schwibinger Michael]

https://tutorialforlinux.com/2021/03/06/step-by-step-driver-epson-et-m1100-et-m1120-debian-installation/



Good afternoon

I did find this URL

https://tutorialforlinux.com/2021/03/06/step-by-step-driver-epson-et-m1100-et-m1120-debian-installation/
[https://mediaw.tutorialforlinux.com/printers/epson/intro/ET-M1100.png]
Step-by-step - Printer Epson ET-M1100/ET-M1120 Debian Installation • 
tutorialforlinux.com
GNU/Linux Debian Epson ET-M1100/ET-M1120 Printer Setup Guide Hi! The Tutorial 
shows you Step-by-Step How to Download and Install Epson EcoTank 
ET-M1100/ET-M1120 Printer in Debian GNU/Linux OldStable/Stable/Testing/Sid 
Desktops. And to Install Epson ET-M1100/ET-M1120 Printer on Debian you need to 
Setup the Proprietary Driver. Especially relevant: using the Epson Printer 
Utility Software, you can check Ink Levels, • Read More »
tutorialforlinux.com
Where xan I find the driver?

Thank You for help

Regards

Sophie




Von: David 
Gesendet: Sonntag, 7. Mai 2023 10:37
An: debian-user@lists.debian.org 
Betreff: Re: AW: EPSON ET M 1120 new printer: If You can read this, you are 
using the wrong driver

On Sun, 2023-05-07 at 09:26 +, Schwibinger Michael wrote:
>
> Good morning
>
> Thank You for help.
>
> There are some other messages from the printer.
>
> Are they important?
>
>
>
> The list gave me here a lot of URLS,
> but where ist the good driver?

Epson doesn't appear to have created one for this printer:

http://tech.epson.com.au/downloads/product.asp

http://download.ebz.epson.net/dsc/search/01/search/searchModule

and Openprinting appears to have nothing on it.
It appears you have purchased a boat anchor.
This leaves you with two options:
buy a very cheap desktop box off a recycler with Windows loaded to use
as a driver box, or
buy another printer, using the above links as reference points as to
what might be worth your money.
Cheers!

>
>
> Regards
>
> Sophie
>
>
>
> 
> Von: Thomas Schmitt 
> Gesendet: Dienstag, 2. Mai 2023 11:39
> An: debian-user@lists.debian.org 
> Betreff: Re: EPSON ET M 1120 new printer: If You can read this, you
> are using the wrong driver
>
> Hi,
>
> i wrote:
> > > i see 100% non-Hanlon opinions including a "sudo rm -R /"
> > > assassination
> > > attempt.
>
> to...@tuxteam.de wrote:
> > Murder by a Hanlon razor. Now that would be... something.
>
> It would only be deadly if the assassination target is indeed stupid
> and
> not just pretending.
>
>
> > Perhaps this is just a dark tentacle of ChatGPT, probing the
> > more fringe aspects of human psychology.
>
> Some german list members speculated about a psychology or sociology
> experiment going on. Nevertheless i think to have observed Sophie
> before
> ChatGPT (but after ELIZA).
>
>
> > It's coming from a Microsoft domain, after all.
>
> What is our position on Microsoft Inc. and Hanlon's Razor ?
>
>
> Have a nice day :)
>
> Thomas
>

--
A Kiwi in Australia,
doing my bit toward raising the national standard.

Re: cirrus/cs35l41 'Cannot Initialize Firmware. Error: -22'

[James Addison]

Hi Vladimir,

As you've found, Debian doesn't yet distribute firmware for the Cirrus
CS35L41, although there is an open bugreport to add support for it
that you can subscribe to:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031912

The recommended symlinks to create after installing firmware directly
from linux-firmware.git can be found in the 'WHENCE' file in the base
directory of that repository (this isn't yet documented in the wiki,
and the format of that file may change in the nearish future).

Please double-check the symlinks you've created against the 'cs35l41'
'Link' entries in that file, and if necessary, make any adjustments to
match.  Mismatches there are my best guess at the cause of the
firmware loading failures at the moment.

Thanks,
James