On 02.12.2014 22:45, Robert Moskowitz wrote:
> I have made some headway on this printing problem. See below.
>
> On 11/14/2014 01:57 AM, poma wrote:
>> On 13.11.2014 22:04, Robert Moskowitz wrote:
>>> On 11/13/2014 10:40 AM, poma wrote:
On 13.11.2014 19:34, Robert Moskowitz wrote:
> On 1
I have made some headway on this printing problem. See below.
On 11/14/2014 01:57 AM, poma wrote:
On 13.11.2014 22:04, Robert Moskowitz wrote:
On 11/13/2014 10:40 AM, poma wrote:
On 13.11.2014 19:34, Robert Moskowitz wrote:
On 11/13/2014 12:44 AM, Tim Waugh wrote:
On Wed, 2014-11-12 at 23:5
On 14.11.2014 13:22, Robert Moskowitz wrote:
>
> On 11/14/2014 01:57 AM, poma wrote:
>> On 13.11.2014 22:04, Robert Moskowitz wrote:
>>> On 11/13/2014 10:40 AM, poma wrote:
On 13.11.2014 19:34, Robert Moskowitz wrote:
> On 11/13/2014 12:44 AM, Tim Waugh wrote:
>> On Wed, 2014-11-12 at
On 11/14/2014 04:05 AM, Tim Waugh wrote:
On Thu, 2014-11-13 at 08:34 -1000, Robert Moskowitz wrote:
su -c 'cupsctl --debug-logging'
Nope. Still no error_log.
Still not, after running that command and then trying to print again?
Is this Fedora 20? In Fedora 21, CUPS error logs are directed t
On 11/14/2014 01:57 AM, poma wrote:
On 13.11.2014 22:04, Robert Moskowitz wrote:
On 11/13/2014 10:40 AM, poma wrote:
On 13.11.2014 19:34, Robert Moskowitz wrote:
On 11/13/2014 12:44 AM, Tim Waugh wrote:
On Wed, 2014-11-12 at 23:51 -1000, Robert Moskowitz wrote:
No error_log, only an access_
On Thu, 2014-11-13 at 08:34 -1000, Robert Moskowitz wrote:
> > su -c 'cupsctl --debug-logging'
>
> Nope. Still no error_log.
Still not, after running that command and then trying to print again?
Is this Fedora 20? In Fedora 21, CUPS error logs are directed to the
systemd journal by default:
ht
On 13.11.2014 22:04, Robert Moskowitz wrote:
>
> On 11/13/2014 10:40 AM, poma wrote:
>> On 13.11.2014 19:34, Robert Moskowitz wrote:
>>> On 11/13/2014 12:44 AM, Tim Waugh wrote:
On Wed, 2014-11-12 at 23:51 -1000, Robert Moskowitz wrote:
> No error_log, only an access_log
Turn on verb
On 11/13/2014 10:40 AM, poma wrote:
On 13.11.2014 19:34, Robert Moskowitz wrote:
On 11/13/2014 12:44 AM, Tim Waugh wrote:
On Wed, 2014-11-12 at 23:51 -1000, Robert Moskowitz wrote:
No error_log, only an access_log
Turn on verbose logging:
su -c 'cupsctl --debug-logging'
Nope. Still no err
On 13.11.2014 19:34, Robert Moskowitz wrote:
>
> On 11/13/2014 12:44 AM, Tim Waugh wrote:
>> On Wed, 2014-11-12 at 23:51 -1000, Robert Moskowitz wrote:
>>> No error_log, only an access_log
>> Turn on verbose logging:
>>
>> su -c 'cupsctl --debug-logging'
>
> Nope. Still no error_log.
>
> In acc
On 11/13/2014 12:44 AM, Tim Waugh wrote:
On Wed, 2014-11-12 at 23:51 -1000, Robert Moskowitz wrote:
No error_log, only an access_log
Turn on verbose logging:
su -c 'cupsctl --debug-logging'
Nope. Still no error_log.
In access_log I see:
localhost - - [13/Nov/2014:13:23:49 -0500] "POST /p
On Wed, 2014-11-12 at 23:51 -1000, Robert Moskowitz wrote:
> No error_log, only an access_log
Turn on verbose logging:
su -c 'cupsctl --debug-logging'
Tim.
*/
signature.asc
Description: This is a digitally signed message part
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe
On 11/12/2014 11:40 PM, Tim Waugh wrote:
On Wed, 2014-11-12 at 23:13 -1000, Robert Moskowitz wrote:
Now why the 'Filter failed'? what 'simple' command line printing tools
should I test with?
The /var/log/cups/error_log file should tell you what went wrong.
No error_log, only an access_log
On Wed, 2014-11-12 at 23:13 -1000, Robert Moskowitz wrote:
> Now why the 'Filter failed'? what 'simple' command line printing tools
> should I test with?
The /var/log/cups/error_log file should tell you what went wrong.
Tim.
*/
signature.asc
Description: This is a digitally signed message pa
On 11/12/2014 10:47 PM, Tim Waugh wrote:
On Wed, 2014-11-12 at 12:54 -1000, Robert Moskowitz wrote:
It is TerminalRoom-8610 that only shows in the web interface.
That one isn't marked as 'shared', so remote views of the server won't
see it.
AH, that was the only difference I could see in the
On Wed, 2014-11-12 at 12:54 -1000, Robert Moskowitz wrote:
> It is TerminalRoom-8610 that only shows in the web interface.
That one isn't marked as 'shared', so remote views of the server won't
see it.
Tim.
*/
signature.asc
Description: This is a digitally signed message part
--
users mailing
On 11/13/14 09:37, Robert Moskowitz wrote:
> Ah. Interesting. Are only the two kept? Because both have my 2 printers
> and first I created one via the web interface, changed it, then created the
> second via system-config-printer remote and changed that. This implies
> either only a .0 being
On 11/12/2014 02:34 PM, Ed Greshko wrote:
On 11/13/14 06:54, Robert Moskowitz wrote:
On 11/12/2014 12:06 PM, poma wrote:
On 12.11.2014 20:25, Robert Moskowitz wrote:
This is interesting. system-config-printer on my notebook does NOT show
the printer I configured with CUPS via the http inter
On 11/13/14 06:54, Robert Moskowitz wrote:
>
> On 11/12/2014 12:06 PM, poma wrote:
>> On 12.11.2014 20:25, Robert Moskowitz wrote:
>>
>>> This is interesting. system-config-printer on my notebook does NOT show
>>> the printer I configured with CUPS via the http interface. So I did
>> ...
>>
>>
>>
On 12.11.2014 23:54, Robert Moskowitz wrote:
> Interestingly there is /etc/cups/printers.conf and /etc/cups/printers.conf.0
>
> Both define both printers that I can see with my notebook browser
> pointed to port 631 on the server. But when I use system-config-printer
> on my notebook to connec
On 11/12/2014 12:06 PM, poma wrote:
On 12.11.2014 20:25, Robert Moskowitz wrote:
This is interesting. system-config-printer on my notebook does NOT show
the printer I configured with CUPS via the http interface. So I did
...
All your printers are here
/etc/cups/printers.conf*
Interestin
On 12.11.2014 20:25, Robert Moskowitz wrote:
> This is interesting. system-config-printer on my notebook does NOT show
> the printer I configured with CUPS via the http interface. So I did
...
Dear Sir/Madam,
All your printers are here
/etc/cups/printers.conf*
man 5 printers.conf
--
user
On 11/11/2014 11:00 PM, Tim Waugh wrote:
On Tue, 2014-11-11 at 12:59 -1000, Robert Moskowitz wrote:
One, I don't see Sever>Connect on my F20 gnome notebook.
https://git.fedorahosted.org/cgit/system-config-printer.git/plain/data/screenshot-mainwindow.png
You don't see that "Server" entry in the
On 11/11/2014 11:00 PM, Tim Waugh wrote:
On Tue, 2014-11-11 at 12:59 -1000, Robert Moskowitz wrote:
One, I don't see Sever>Connect on my F20 gnome notebook.
https://git.fedorahosted.org/cgit/system-config-printer.git/plain/data/screenshot-mainwindow.png
You don't see that "Server" entry in the
On 11/11/2014 10:55 PM, Tim Waugh wrote:
On Tue, 2014-11-11 at 17:10 -1000, Robert Moskowitz wrote:
On 11/11/2014 02:53 PM, Ed Greshko wrote:
On 11/12/14 08:41, Robert Moskowitz wrote:
cupsctl _remote_admin=1
Is not enough.
Add -U root to that command
tried
cupsctl _remote_admin=1 -U root
On Tue, 2014-11-11 at 12:59 -1000, Robert Moskowitz wrote:
> One, I don't see Sever>Connect on my F20 gnome notebook.
https://git.fedorahosted.org/cgit/system-config-printer.git/plain/data/screenshot-mainwindow.png
You don't see that "Server" entry in the menu bar?
> Two, Remote Desktop, needs a
On Tue, 2014-11-11 at 13:01 -1000, Robert Moskowitz wrote:
> So you did not get any further than I. Seems like printer support is
> requiring a desktop to configure? That is sad.
No, it isn't.
You can use system-config-printer to configure a remote CUPS server.
Have you tried doing that?
Tim.
On Tue, 2014-11-11 at 17:10 -1000, Robert Moskowitz wrote:
> On 11/11/2014 02:53 PM, Ed Greshko wrote:
> > On 11/12/14 08:41, Robert Moskowitz wrote:
> >> cupsctl _remote_admin=1
> >>
> >> Is not enough.
> > Add -U root to that command
>
> tried
>
> cupsctl _remote_admin=1 -U root
>
> And still
On 12.11.2014 00:01, Robert Moskowitz wrote:
>
> On 11/11/2014 12:15 AM, poma wrote:
>> On 11.11.2014 04:15, Robert Moskowitz wrote:
>>> I have a server here that has no GUI installed.
>>>
>>> No gnome, xfce, or any other. And I want to install a printer. It is
>>> an HP8610 and I have the url f
On 11/12/14 11:10, Robert Moskowitz wrote:
>
> On 11/11/2014 02:53 PM, Ed Greshko wrote:
>> On 11/12/14 08:41, Robert Moskowitz wrote:
>>> cupsctl _remote_admin=1
>>>
>>> Is not enough.
>> Add -U root to that command
>
> tried
>
> cupsctl _remote_admin=1 -U root
>
> And still Forbidden.
>
> My note
On 11/11/2014 02:53 PM, Ed Greshko wrote:
On 11/12/14 08:41, Robert Moskowitz wrote:
cupsctl _remote_admin=1
Is not enough.
Add -U root to that command
With all this,
cupsctl _remote_any=1
got the web page up. Now to configure the printer, then see what is the
minimum to get this to wor
On 11/11/2014 02:53 PM, Ed Greshko wrote:
On 11/12/14 08:41, Robert Moskowitz wrote:
cupsctl _remote_admin=1
Is not enough.
Add -U root to that command
tried
cupsctl _remote_admin=1 -U root
And still Forbidden.
My notebook and the server are on different subnets.
--
users mailing list
u
On 11/11/2014 02:53 PM, Ed Greshko wrote:
On 11/12/14 08:41, Robert Moskowitz wrote:
cupsctl _remote_admin=1
Is not enough.
Add -U root to that command
Got to get back to the terminal room where there is ethernet, after the
core session...
--
users mailing list
users@lists.fedoraproject
On 11/12/14 08:41, Robert Moskowitz wrote:
> cupsctl _remote_admin=1
>
> Is not enough.
Add -U root to that command
--
If you can't laugh at yourself, others will gladly oblige.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fed
On 11/11/2014 01:17 PM, Ed Greshko wrote:
On 11/12/14 07:06, Robert Moskowitz wrote:
On 11/11/2014 12:32 PM, Ed Greshko wrote:
On 11/12/14 06:14, Robert Moskowitz wrote:
On 11/10/2014 10:19 PM, Dario Lesca wrote:
From console or a ssh shell run:
$ sudo cupsctl _remote_admin=1
After inst
On 11/12/14 07:06, Robert Moskowitz wrote:
>
> On 11/11/2014 12:32 PM, Ed Greshko wrote:
>> On 11/12/14 06:14, Robert Moskowitz wrote:
>>> On 11/10/2014 10:19 PM, Dario Lesca wrote:
From console or a ssh shell run:
$ sudo cupsctl _remote_admin=1
>>> After installing cups (not part
On Tue, Nov 11, 2014 at 01:06:37PM -1000, Robert Moskowitz wrote:
>
> On 11/11/2014 12:32 PM, Ed Greshko wrote:
> >On 11/12/14 06:14, Robert Moskowitz wrote:
> >>On 11/10/2014 10:19 PM, Dario Lesca wrote:
> >>> From console or a ssh shell run:
> >>>
> >>>$ sudo cupsctl _remote_admin=1
> >>After i
On 11/11/2014 12:32 PM, Ed Greshko wrote:
On 11/12/14 06:14, Robert Moskowitz wrote:
On 11/10/2014 10:19 PM, Dario Lesca wrote:
From console or a ssh shell run:
$ sudo cupsctl _remote_admin=1
After installing cups (not part of minimal), I got:
# cupsctl _remote_admin=1
cupsctl: Unable to
On 11/11/2014 12:15 AM, poma wrote:
On 11.11.2014 04:15, Robert Moskowitz wrote:
I have a server here that has no GUI installed.
No gnome, xfce, or any other. And I want to install a printer. It is
an HP8610 and I have the url for it. I strangely thought that
system-config-printer would wor
On 11/10/2014 10:46 PM, Tim Waugh wrote:
On Tue, 2014-11-11 at 09:19 +0100, Dario Lesca wrote:
From console or a ssh shell run:
$ sudo cupsctl _remote_admin=1
$ sudo firewall-cmd --permanent --add-port=631/tcp
$ sudo firewall-cmd --add-port=631/tcp
Then point your browser to https://ip.of.ou
On 11/12/14 06:14, Robert Moskowitz wrote:
> On 11/10/2014 10:19 PM, Dario Lesca wrote:
>> From console or a ssh shell run:
>>
>> $ sudo cupsctl _remote_admin=1
>
> After installing cups (not part of minimal), I got:
>
> # cupsctl _remote_admin=1
> cupsctl: Unable to connect to server: Bad file de
On 11/10/2014 10:19 PM, Dario Lesca wrote:
From console or a ssh shell run:
$ sudo cupsctl _remote_admin=1
After installing cups (not part of minimal), I got:
# cupsctl _remote_admin=1
cupsctl: Unable to connect to server: Bad file descriptor
$ sudo firewall-cmd --permanent --add-port=631
On Tue, 2014-11-11 at 00:59 -1000, Robert Moskowitz wrote:
> On 11/10/2014 10:19 PM, Dario Lesca wrote:
> > From console or a ssh shell run:
> >
> > $ sudo cupsctl _remote_admin=1
> > $ sudo firewall-cmd --permanent --add-port=631/tcp
> > $ sudo firewall-cmd --add-port=631/tcp
>
> Other than it i
On 11/10/2014 10:19 PM, Dario Lesca wrote:
From console or a ssh shell run:
$ sudo cupsctl _remote_admin=1
$ sudo firewall-cmd --permanent --add-port=631/tcp
$ sudo firewall-cmd --add-port=631/tcp
Other than it is port 9100 for the printer?
Then point your browser to https://ip.of.our.hos
On 11.11.2014 11:15, poma wrote:
> On 11.11.2014 04:15, Robert Moskowitz wrote:
>> I have a server here that has no GUI installed.
>>
>> No gnome, xfce, or any other. And I want to install a printer. It is
>> an HP8610 and I have the url for it. I strangely thought that
>> system-config-printe
On 11.11.2014 04:15, Robert Moskowitz wrote:
> I have a server here that has no GUI installed.
>
> No gnome, xfce, or any other. And I want to install a printer. It is
> an HP8610 and I have the url for it. I strangely thought that
> system-config-printer would work, but that also requires mo
On Tue, 2014-11-11 at 09:19 +0100, Dario Lesca wrote:
> From console or a ssh shell run:
>
> $ sudo cupsctl _remote_admin=1
> $ sudo firewall-cmd --permanent --add-port=631/tcp
> $ sudo firewall-cmd --add-port=631/tcp
>
> Then point your browser to https://ip.of.our.host:631/admin and add your
>
From console or a ssh shell run:
$ sudo cupsctl _remote_admin=1
$ sudo firewall-cmd --permanent --add-port=631/tcp
$ sudo firewall-cmd --add-port=631/tcp
Then point your browser to https://ip.of.our.host:631/admin and add your
printer.
Or to work only from command line use lpstat, lpinfo and lpa
On 11/10/2014 10:15 PM, Robert Moskowitz wrote:
> I have a server here that has no GUI installed.
>
> No gnome, xfce, or any other. And I want to install a printer. It is
> an HP8610 and I have the url for it. I strangely thought that
> system-config-printer would work, but that also requires m
I have a server here that has no GUI installed.
No gnome, xfce, or any other. And I want to install a printer. It is
an HP8610 and I have the url for it. I strangely thought that
system-config-printer would work, but that also requires more than just
a text window as I get:
# system-confi
49 matches
Mail list logo
