Thank you very much Gene,
You are the first person to ever mention that "the line was removed" for
security paranoia, not that I mistakenly removed it by mistake over the
past few months of it running under jessie and not running under
stretch. This is what I wanted to find out, why did this
Brian:
> On Sat 04 Feb 2017 at 14:55:18 +0900, Mark Fletcher wrote:
>> Indulge us, and add a line to your cupsd.conf as follows:
>>
>> Listen localhost:631
>>
>> and restart CUPS and see what happens.
>
> It would solve his problem.
>
> There is nothing in the postinst script for cups which
Yes, this worked without specifying an ip just localhost:631
The upgrade was from jessie to stretch and I had never edited this file,
yesterday I didn't even know where it was.
If this line is by default in this file and this file pre-existed on
jessie how could that line be omitted? Or was the
none
QuotaPeriod 0
PageLimit 0
KLimit 0
AllowUser
AllowUser
AllowUser
AllowUser xtxtxtx
OpPolicy default
ErrorPolicy retry-job
Option number-up 4
Roba:
> Let us see.
> I HAVE explained I have done nothing to alter what existed from "stock"
> in Jessie (when
user @SYSTEM
Order deny,allow
AuthType Default
Require user @OWNER @SYSTEM
Order deny,allow
Order deny,allow
JobPrivateAccess default
JobPrivateValues default
SubscriptionPrivateAccess default
SubscriptionPrivateValues default
PreserveJobHistory No
Roba:
>
Let us see.
I HAVE explained I have done nothing to alter what existed from "stock"
in Jessie (when cups) did work from the browser, right?
Now it does not and I HAVE DONE NOTHING other than upgrading from stable
to testing. And cups does not work. Now how would your question
address this issue?
Has anything relating to those files changed between jessie and stretch
to affect cups being blocked?
Would a line in the allow file ALL: localhost:631 help or is the syntax
incorrect?
Is there any difference between ext3 and ext4 in terms of backing up a
system? I can't recall the details but I run into a backup problem once
and remember reading that ext4 was under experimentation by the backup
developers and ext3 was supported fully but not ext4.
I am not sure if it was
:::*
963/rpc.mountd
udp6 0 0 :::49449:::*
963/rpc.mountd
udp6 0 0 :::41524:::*
963/rpc.mountd
> On Wed 01 Feb 2017 at 14:13:00 +0000, Roba wrote:
>
>> reaching CUPS, as I should be able to, is
reaching CUPS, as I should be able to, is the problem, not printing
(that is a personal problem).
Again, your help (Brian) is appreciated but it seems as the problem and
the reason I am bringing it up here is not just to solve my own printer
problem, as this I brought into myself last year by
Thanks for your help by the way, here is some other weird occurrence.
I run sudo firefox to see if it was a privilege problem and get this:
The screen came up but all links from the main page would run to a
denial page.
The screen was from a cached page from way back when it was 1.7.5, while
Sorry hear it is again, complete:
Device: uri = https
class = network
info = Internet Printing Protocol (https)
make-and-model = Unknown
device-id =
location =
Device: uri = socket
class = network
info = AppSocket/HP JetDirect
Device: uri = cups-pdf:/
class = file
info = CUPS-PDF
make-and-model = Virtual PDF Printer
device-id = MFG:Generic;MDL:CUPS-PDF Printer;DES:Generic
CUPS-PDF Printer;CLS:PRINTER;CMD:POSTSCRIPT;
location =
The rest on the list are pretty blank, nothing
Well I sure haven't changed anything other than upgrade packages. Now
if some other package interferes with cupsd I don't know. I know I
spent some days fighting :631 4-5 months ago to get it (the printer) to
work. Cups worked fine then. I have not tried any other printer since.
Obviously
On 2017-01-30 22:47, r...@openmailbox.org wrote:
And this is for trying to plug a ppd that was hacked from an other
Ricoh printer to fit an SP112 SP112-su
I figured what did not work for jessie may work for stretch
I had gotten the same printer to work on an other machine with
jessie somewhere
I used to try and set up a printer through localhost:631 in Jessie but
now in stretch it is impossible. I foung some link about
/etc/hosts.allow and deny and tried a few things but still no luck.
Maybe I am not using the correct statement and tried localhost and
127.0.0.1 but still no luck.
16 matches
Mail list logo
